MME side of the S1-AP Service Access Point (SAP), provides the MME methods to be called when an S1-AP message is received by the MME. More...
#include "epc-s1ap-sap.h"
 Inheritance diagram for ns3::EpcS1apSapMme:
 Collaboration diagram for ns3::EpcS1apSapMme:Classes | |
| struct | ErabSetupItem | 
| E-RAB Setup Item IEs, see 3GPP TS 36.413 9.1.4.2.  More... | |
| struct | ErabSwitchedInDownlinkItem | 
| E-RABs Switched in Downlink Item IE, see 3GPP TS 36.413 9.1.5.8.  More... | |
| struct | ErabToBeReleasedIndication | 
| E-RAB Release Indication Item IEs, 3GPP TS 36.413 version 9.8.0 section 9.1.3.7.  More... | |
Public Member Functions | |
| virtual void | ErabReleaseIndication (uint64_t mmeUeS1Id, uint16_t enbUeS1Id, std::list< ErabToBeReleasedIndication > erabToBeReleaseIndication)=0 | 
| As per 3GPP TS 23.401 Release 9 V9.5.0 Figure 5.4.4.2-1 eNB sends indication of Bearer Release to MME.  More... | |
| virtual void | InitialContextSetupResponse (uint64_t mmeUeS1Id, uint16_t enbUeS1Id, std::list< ErabSetupItem > erabSetupList)=0 | 
| INITIAL CONTEXT SETUP RESPONSE message, see 3GPP TS 36.413 9.1.4.2.  More... | |
| virtual void | InitialUeMessage (uint64_t mmeUeS1Id, uint16_t enbUeS1Id, uint64_t stmsi, uint16_t ecgi)=0 | 
| virtual void | PathSwitchRequest (uint64_t enbUeS1Id, uint64_t mmeUeS1Id, uint16_t gci, std::list< ErabSwitchedInDownlinkItem > erabToBeSwitchedInDownlinkList)=0 | 
| PATH SWITCH REQUEST message, see 3GPP TS 36.413 9.1.5.8.  More... | |
  Public Member Functions inherited from ns3::EpcS1apSap | |
| virtual | ~EpcS1apSap () | 
MME side of the S1-AP Service Access Point (SAP), provides the MME methods to be called when an S1-AP message is received by the MME.
Definition at line 53 of file epc-s1ap-sap.h.
      
  | 
  pure virtual | 
As per 3GPP TS 23.401 Release 9 V9.5.0 Figure 5.4.4.2-1 eNB sends indication of Bearer Release to MME.
As per 3GPP TS version 9.8.0 section 8.2.3.2.2, the eNB initiates the procedure by sending an E-RAB RELEASE INDICATION message towards MME
| mmeUeS1Id | in practice, we use the IMSI | 
| enbUeS1Id | in practice, we use the RNTI | 
| erabToBeReleaseIndication | the List of bearers to be deactivated | 
Implemented in ns3::MemberEpcS1apSapMme< C >.
Referenced by ns3::EpcEnbApplication::DoReleaseIndication().
 Here is the caller graph for this function:
      
  | 
  pure virtual | 
INITIAL CONTEXT SETUP RESPONSE message, see 3GPP TS 36.413 9.1.4.2.
| mmeUeS1Id | in practice, we use the IMSI | 
| enbUeS1Id | in practice, we use the RNTI | 
| erabSetupList | 
Implemented in ns3::MemberEpcS1apSapMme< C >.
      
  | 
  pure virtual | 
| mmeUeS1Id | in practice, we use the IMSI | 
| enbUeS1Id | in practice, we use the RNTI | 
| stmsi | in practice, the imsi | 
| ecgi | in practice, the cell Id | 
Implemented in ns3::MemberEpcS1apSapMme< C >.
Referenced by ns3::EpcEnbApplication::DoInitialUeMessage().
 Here is the caller graph for this function:
      
  | 
  pure virtual | 
PATH SWITCH REQUEST message, see 3GPP TS 36.413 9.1.5.8.
| enbUeS1Id | in practice, we use the RNTI | 
| mmeUeS1Id | in practice, we use the IMSI | 
| gci | |
| erabToBeSwitchedInDownlinkList | 
Implemented in ns3::MemberEpcS1apSapMme< C >.
Referenced by ns3::EpcEnbApplication::DoPathSwitchRequest().
 Here is the caller graph for this function: