hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
b647d725f39317e667005befaa44b373 | 23.632 | 5.6.2 Configuration of Monitoring Events in MME
| Figure 5.6.2-1 shows the scenario where the UDM receives a request from a combined SCEF+NEF to configure a monitoring event that needs to be reported by EPC (e.g. location change).
Figure 5.6.2-1: Configuration of Monitoring Events in MME
1. The UDM receives a request from a combined SCEF+NEF to configure a monitor... |
b647d725f39317e667005befaa44b373 | 23.632 | 5.6.3 Synchronization of Status of Monitoring Event between HSS and UDM
| The status of some specific monitoring events that are detected locally at the HSS and UDM (e.g. IMEI(SV)/PEI change, roaming status change) is kept synchronized between UDM and HSS as defined in this clause. This is, when the HSS detects e.g. that the IMEI(SV) for a UE changes (e.g. during an Update Location in EPS), ... |
b647d725f39317e667005befaa44b373 | 23.632 | 5.7 Common External Parameter Provisioning
| |
b647d725f39317e667005befaa44b373 | 23.632 | 5.7.1 General
| A combined SCEF+NEF can provision UE subscription parameters applicable to both EPC and 5GC using only 5GC procedures towards UDM. In this case, the SCEF+NEF indicates that parameters to be provisioned are also applicable to EPC, i.e. the subscription parameters must be conveyed to 5GC and EPC serving nodes.
If the HS... |
b647d725f39317e667005befaa44b373 | 23.632 | 5.7.2 Parameter Provisioning towards MME
| Figure 5.7.2-1 shows the scenario where the UDM receives a request from a combined SCEF+NEF to provision UE subscription parameters that needs to be provisioned also in EPC.
Figure 5.7.2-1: Common Parameter Provisioning
1. The UDM receives a request from a combined SCEF+NEF to provision UE subscription parameters. ... |
b647d725f39317e667005befaa44b373 | 23.632 | 6 Network Function Service procedures
| |
b647d725f39317e667005befaa44b373 | 23.632 | 6.1 HSS Services
| |
b647d725f39317e667005befaa44b373 | 23.632 | 6.1.1 General
| The following table illustrates the HSS Services.
Table 6.1.1-1: NF services provided by HSS
NF service
Service Operations
Operation Semantics
Example Consumer(s)
UE Authentication
Get
Request/Response
UDM
UECM
SNDeregistration
Request/Response
UDM
Update
Request/Response
UDM
SDM
Get
Request/Respon... |
b647d725f39317e667005befaa44b373 | 23.632 | 6.1.2 Nhss_UEAuthentication service
| |
b647d725f39317e667005befaa44b373 | 23.632 | 6.1.2.1 Nhss_UEAuthentication_Get service operation
| Service operation name: Nhss_UEAuthentication_Get
Description: Requester NF gets the authentication vector from HSS. For AKA based authentication, this operation can be also used to recover from synchronization failure situations.
Inputs, Required: IMSI, authentication method, serving network name.
Inputs, Optional:... |
b647d725f39317e667005befaa44b373 | 23.632 | 6.1.3 Nhss_UECM service
| |
b647d725f39317e667005befaa44b373 | 23.632 | 6.1.3.1 Nhss_UECM_SNDeregistration service operation
| Service operation name: Nhss_UECM_SNDeregistration.
Description: The NF consumer requests the HSS to initiate cancel location to the Serving Node registered in HSS serving the UE in EPS and/or PS, if any.
Inputs, Required: IMSI, deregistration reason.
Inputs, Optional: None.
Outputs, Required: Result Indication.
O... |
b647d725f39317e667005befaa44b373 | 23.632 | 6.1.3.2 Nhss_UECM_Update service operation
| Service operation name: Nhss_UECM_Update.
Description: The NF consumer informs the HSS about an update in the UE Context (e.g. a change in the IMEI).
Inputs, Required: IMSI.
Inputs, Optional: IMEI(SV), serving PLMN.
Outputs, Required: Result Indication.
Outputs, Optional: None.
|
b647d725f39317e667005befaa44b373 | 23.632 | 6.1.4 Nhss_SDM service
| |
b647d725f39317e667005befaa44b373 | 23.632 | 6.1.4.1 Nhss_SDM_Get service operation
| Service operation name: Nhss_SDM_Get
Description: The consumer NF gets the subscriber data indicated by the requested data type from HSS. In this release, only the PGW-C+SMF FQDN for S5/S8/S2b interface information is supported as requested data type.
Inputs, Required: IMSI, requested data.
Inputs, Optional: None.
... |
b647d725f39317e667005befaa44b373 | 23.632 | 6.1.4.2 Nhss_SDM_Notification service operation
| Service or service operation name: Nhss_SDM_Notification
Description: The HSS notifies NF consumer of the updates of the subscriber data indicated by the "subscription data Type" input. In this release, only the PGW-C+SMF FQDN for S5/S8/S2b interface information is supported as subscription data type.
Inputs, Require... |
b647d725f39317e667005befaa44b373 | 23.632 | 6.1.4.3 Nhss_SDM_Subscribe service operation
| Service operation name: Nhss_SDM_Subscribe
Description: The NF consumer subscribes for updates to the subscriber data indicated by the 'subscription data type' input. The HSS shall check the requested consumer is authorized to subscribe to requested updates. In this release, only the PGW-C+SMF FQDN for S5/S8/S2b inter... |
b647d725f39317e667005befaa44b373 | 23.632 | 6.1.4.4 Nhss_SDM_Unsubscribe service operation
| Service operation name: Nhss_SDM_Unsubscribe
Description: The NF consumer unsubscribes from updates to the subscriber data indicated by the 'subscription data type' input. In this release, only the PGW-C+SMF FQDN for S5/S8 interface information is supported as subscription data type.
Inputs, Required: IMSI, Subscript... |
b647d725f39317e667005befaa44b373 | 23.632 | 6.1.5 Nhss_EE service
| |
b647d725f39317e667005befaa44b373 | 23.632 | 6.1.5.1 Nhss_EE_Subscribe service operation
| Service operation name: Nhss_EE_Subscribe.
Description: The NF consumer request the HSS to subscribe to notifications for monitoring events as described in 3GPP TS 23.682 [16] (e.g. location change).
Inputs, Required: IMSI, monitoring event type(s), notification address.
Inputs, Optional: -
Outputs, Required: Resul... |
b647d725f39317e667005befaa44b373 | 23.632 | 6.1.5.2 Nhss_EE_Unsubscribe service operation
| Service operation name: Nhss_EE_Unsubscribe.
Description: The NF consumer request the HSS to delete the subscription of a monitoring event.
Inputs, Required: Subscription ID.
Inputs, Optional: -
Outputs, Required: Operation execution result indication.
Outputs, Optional: None.
|
b647d725f39317e667005befaa44b373 | 23.632 | 6.1.5.3 Nhss_EE_Notify service operation
| Service operation name: Nhss_EE_Notify.
Description: The HSS reports the monitoring event to the consumer that has previously subscribed.
Inputs, Required: Event ID, Notification Correlation Information, time stamp.
Inputs, Optional: Event specific parameters list.
Outputs, Required: None.
Outputs, Optional: None.... |
b647d725f39317e667005befaa44b373 | 23.632 | 6.1.6 Nhss_PP service operations
| |
b647d725f39317e667005befaa44b373 | 23.632 | 6.1.6.1 Nhss_PP_Create service operation
| Service operation name: Create
Description: Creates externally provisioned UE parameters applicable to EPC.
Inputs, Required: SUPI, AF Instance Id, Provisioned parameters.
Inputs, Optional: None.
Outputs, Required: Success/Failure indication.
Outputs, Optional: None.
|
b647d725f39317e667005befaa44b373 | 23.632 | 6.1.6.2 Nhss_PP_Update service operation
| Service operation name: Update
Description: Updates externally provisioned UE parameters applicable to EPC.
Inputs, Required: SUPI, AF Instance Id, Provisioned parameters.
Inputs, Optional: None.
Outputs, Required: Success/Failure indication.
Outputs, Optional: None.
|
b647d725f39317e667005befaa44b373 | 23.632 | 6.1.6.3 Nhss_PP_Delete service operation
| Service operation name: Delete
Description: Deletes externally provisioned UE parameters applicable to EPC.
Inputs, Required: SUPI, AF Instance Id.
Inputs, Optional: None.
Outputs, Required: Success/Failure indication.
Outputs, Optional: None.
|
b647d725f39317e667005befaa44b373 | 23.632 | 6.1.6.4 Nhss_PP_Get service operation
| Service operation name: Get
Description: Retrieves externally provisioned UE parameters applicable to EPC.
Inputs, Required: SUPI, AF Instance Id.
Inputs, Optional: None.
Outputs, Required: Success, Provisioned UE parameters, Failure indication.
Outputs, Optional: None.
|
b647d725f39317e667005befaa44b373 | 23.632 | 6.2 UDM Services
| |
b647d725f39317e667005befaa44b373 | 23.632 | 6.2.1 General
| The following table illustrates the UDM Services.
Table 6.2.1-1: NF services provided by UDM
NF service
Service Operations
Operation Semantics
Example Consumer(s)
UECM
P-CscfRestorationTrigger
Request/Response
HSS
Get
Request/Response
HSS
AMFDeregistration
Request/Response
HSS
Update
Request/Resp... |
b647d725f39317e667005befaa44b373 | 23.632 | 6.2.2 Nudm_UECM service operation
| |
b647d725f39317e667005befaa44b373 | 23.632 | 6.2.2.1 Nudm_UECM_P-CscfRestorationTrigger service operation
| Service operation name: Nudm_UECM_P-CscfRestorationTrigger
Description: Requester NF (HSS) triggers the UDM to notify all NFs (AMF, SMF) that have previously subscribed to receive notifications for P-CSCF restoration.
Inputs, Required: SUPI.
Inputs, Optional: None.
Outputs, Required: None.
Outputs, Optional: None.... |
b647d725f39317e667005befaa44b373 | 23.632 | 6.2.2.2 Nudm_UECM_Get service operation
| See 3GPP TS 23.502 [5] clause 5.2.3.2.4.
|
b647d725f39317e667005befaa44b373 | 23.632 | 6.2.2.3 Nudm_UECM_AMFDeregistration service operation
| Service operation name: Nudm_UECM_AMFDeregistration.
Description: The NF consumer requests the UDM to initiate deregistration of the AMF serving the UE, if any.
Inputs, Required: SUPI, deregistration reason.
Inputs, Optional: None.
Outputs, Required: Result Indication.
Outputs, Optional: None.
|
b647d725f39317e667005befaa44b373 | 23.632 | 6.2.2.4 Nudm_UECM_Update service operation
| See 3GPP TS 23.502 [5] clause 5.2.3.2.5.
|
b647d725f39317e667005befaa44b373 | 23.632 | 6.2.3 Nudm_MT Service
| |
b647d725f39317e667005befaa44b373 | 23.632 | 6.2.3.1 Nudm_MT_ProvideDomainSelectionInfo Service
| Service operation name: Nudm_MT_ProvideDomainSelectionInfo
Description: Provides the UE information for terminating domain selection of IMS voice in 5G to the consumer NF (HSS).
Inputs, Required: SUPI.
Inputs, Optional: None.
Outputs, Required: Success/Failure indication.
Outputs, Optional: Indication of supportin... |
b647d725f39317e667005befaa44b373 | 23.632 | 6.2.3.2 Nudm_MT_ProvideUserState service operation
| Service operation name: Nudm_MT_ProvideUserState
Description: Provides the UE's 5GS PS User State to the consumer NF (HSS).
Inputs, Required: SUPI.
Inputs, Optional: None.
Outputs, Required: Success/Failure indication.
Outputs, Optional: 5GS User State.
|
b647d725f39317e667005befaa44b373 | 23.632 | 6.2.3.3 Nudm_MT_ProvideLocationInfo service operation
| Service operation name: Nudm_MT_ProvideLocationInfo
Description: Provides the UE's 5GS location information to the consumer NF (HSS).
Inputs, Required: SUPI, Current Location Indicator, Serving Node Indication, Local Time Zone Indication, and RAT-Type requested Indicator.
Inputs, Optional: None.
Outputs, Required: ... |
b647d725f39317e667005befaa44b373 | 23.632 | 6.2.3.4 Nudm_MT_Provide5GSRVCCInfo Operation
| Service operation name: Nudm_MT_ProvideSRVCCInfo
Description: Provides the UE PS to CS SRVCC capability for the UE to the consumer NF (HSS).
Inputs, Required: SUPI.
Inputs, Optional: None.
Outputs, Required: Success/Failure indication.
Outputs, Optional: Indication of the UE supporting SRVCC capability or not, If ... |
b647d725f39317e667005befaa44b373 | 23.632 | 6.2.4 Nudm_EE Service
| |
b647d725f39317e667005befaa44b373 | 23.632 | 6.2.4.1 Nudm_EventExposure_Subscribe service operation
| See 3GPP TS 23.502 [5] clause 5.2.3.5.2.
When used by the HSS in MT-SMS delivery failure scenarios (see clause 4.6.3) the subscribe request shall be a one-time subscription for UE-reachability for SMS and shall indicate whether it is applicable to 3GPP access, Non3GPP access or both.
|
b647d725f39317e667005befaa44b373 | 23.632 | 6.2.4.2 Nudm_EventExposure_Notify service operation
| See 3GPP TS 23.502 [5] clause 5.2.3.5.4.
When used by the HSS in SMS Alerting scenarios (see clause 4.6.4) the notify request shall indicate whether it is applicable to 3GPP access or Non3GPP access.
|
b647d725f39317e667005befaa44b373 | 23.632 | 6.2.5 Nudm_UEAuthentication service
| |
b647d725f39317e667005befaa44b373 | 23.632 | 6.2.5.1 Nudm_UEAuthentication_GetHssAv service operation
| Service operation name: Nudm_UEAuthentication_GetHssAv
Description: Requester NF gets the authentication vector from UDM. For AKA based authentication, this operation can be also used to recover from synchronization failure situations.
Inputs, Required: SUPI, authentication method (e.g. EAP-AKA', EPS-AKA, IMS-AKA, GB... |
b647d725f39317e667005befaa44b373 | 23.632 | 6.2.6 Nudm_SDM service operations
| |
b647d725f39317e667005befaa44b373 | 23.632 | 6.2.6.1 Nudm_SDM_Get service operation
| See 3GPP TS 23.502 [5] clause 5.2.3.3.2.
|
b647d725f39317e667005befaa44b373 | 23.632 | 6.2.6.2 Nudm_SDM_Subscribe service operation
| See 3GPP TS 23.502 [5] clause 5.2.3.3.4.
|
b647d725f39317e667005befaa44b373 | 23.632 | 6.2.6.3 Nudm_SDM_Unsubscribe service operation
| See 3GPP TS 23.502 [5] clause 5.2.3.3.5.
|
b647d725f39317e667005befaa44b373 | 23.632 | 6.2.6.4 Nudm_SDM_Notify service operation
| See 3GPP TS 23.502 [5] clause 5.2.3.3.3.
|
b647d725f39317e667005befaa44b373 | 23.632 | 6.2.7 Nudm_PP service operations
| |
b647d725f39317e667005befaa44b373 | 23.632 | 6.2.7.1 Nudm_PP_Update service operation
| Service operation name: Update
Description: Removes, provides or modifies the STN-SR, CMSISDN, if the 5GS support 5G-SRVCC.
Inputs, Required: None.
Inputs, Optional: SUPI, STN-SR, CMSISDN.
Outputs, Required: Success/Failure indication.
Outputs, Optional: None.
|
b647d725f39317e667005befaa44b373 | 23.632 | 6.3 UDR Services
| The UDM and optionally the HSS shall make use of the Nudr_DataRepository Query service operations specified in 3GPP TS 23.502 [5] to retrieve Authentication Subscription Data. If the subscribed authentication method is 5G_AKA or EAP_AKA_PRIME, the AuthenticationSubscriptionData shall include an indicator indicating whe... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 1 Scope
| The present document specifies architecture enhancements to facilitate communications with packet data networks and applications (e.g. Machine Type Communication (MTC) applications on the (external) network/MTC servers) according to the use cases and service requirements defined in TS 22.368 [2], TS 22.101 [3], and rel... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 2 References
| The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
-... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 3 Definitions and abbreviations
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 3.1 Definitions
| For the purposes of the present document, the terms and definitions given in TR 21.905 [1] apply.
For the purposes of the present document, the following terms and definitions given in TS 23.401 [7] apply:
RACS
WB-E-UTRAN
LTE-M
|
88801ef891f5fda814c6a759927a12ca | 23.682 | 3.2 Abbreviations
| For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
AS Application Server
CDR Charging Data Record
CDF Charging Data Functio... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4 Architecture Model and Concepts
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.1 General Concept
| The end-to-end communications, between the MTC Application in the UE and the MTC Application in the external network, uses services provided by the 3GPP system, and optionally services provided by a Services Capability Server (SCS).
The MTC Application in the external network is typically hosted by an Application Serv... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.2 Architectural Reference Model
| Figures 4.2-1a and 4.2-1b show the architecture for a UE used for MTC connecting to the 3GPP network (UTRAN, WB-E-UTRAN, NB-IoT, GERAN, etc.) via the Um/Uu/LTE-Uu interfaces or satellite access interface for NB-IoT, WB-E-UTRAN and LTE-M. They also show the 3GPP network service capability exposure to SCS and AS. The arc... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.3 Reference points
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.3.1 General
| The following 3GPP reference points support the Indirect and Hybrid models of MTC and Service Capability Exposure.
NOTE: As further development of the MTC architecture takes place as well as when additional MTC common functionality and features are addressed, further reference points may be added.
|
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.3.2 List of Reference Points
| The description of the MTC and Service Capability Exposure related reference points:
Tsms: Reference point used by an entity outside the 3GPP network to communicate with UEs used for MTC via SMS.
Tsp: Reference point used by a SCS to communicate with the MTC-IWF related control plane signalling.
T4: Reference point ... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.3.3 Reference Point Requirements
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.3.3.1 Tsp Reference Point Requirements
| The Tsp reference point shall fulfil the following requirements:
- connects a MTC-IWF to one or more SCSs;
- supports the following device trigger functionality:
- reception of a device trigger request from SCS that includes an Application Port ID used by the UE to route the trigger internally to the appropriate tri... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.3.3.2 T4 Reference Point Requirements
| The T4 reference point shall fulfil the following requirements:
- connects the MTC-IWF, taking the role of the SME, to SMS-SC inside HPLMN domain;
- supports the following device trigger functionality:
- transfer of device trigger, addressed by either an MSISDN or the IMSI, from MTC-IWF to SMS-SC inside HPLMN domain... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.3.3.3 Void
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.3.3.4 S6m Reference Point Requirements
| The S6m reference point shall fulfil the following requirements:
- connect the MTC-IWF to HSS/HLR containing subscription and UE related information; and
- support interrogation of HSS/HLR to:
- map E.164 MSISDN or external identifier to IMSI;
- map IMSI and Application Port ID to external identifier;
- retrieve s... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.3.3.5 S6n Reference Point Requirements
| The S6n reference point shall fulfil the following requirements:
- support communication between MTC-AAA and HSS/HLR containing subscription and UE related information; and
- support interrogation of HSS/HLR to:
- map between IMSI and External Identifier(s).
|
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.3.3.6 T6a/T6b Reference Point Requirements
| The T6a and T6b reference points shall fulfil the following requirements:
- T6a connects the SCEF to the serving MME;
- T6b connects the SCEF to the serving SGSN;
- supports the following functionality:
- monitoring event configuration by the SCEF at the serving MME/SGSN;
- monitoring event reporting by the servin... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.3.3.7 S6t Reference Point Requirements
| The S6t reference point shall fulfil the following requirements:
- connect the SCEF to HSS containing subscription and UE related information;
- monitoring event configuration/deletion by the SCEF at the HSS; and
- monitoring event reporting by the HSS to the SCEF.
- configuration/deletion of communication pattern ... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.3.3.8 T6ai/T6bi Reference Point Requirements
| The T6ai and T6bi reference points shall fulfil the following requirements:
- T6ai connects the IWK-SCEF to the serving MME;
- T6bi connects the IWK-SCEF to the serving SGSN;
- T6ai/T6bi support the following functionality:
- Monitoring Event reporting by the serving MME/SGSN to the IWK-SCEF;
- Forwarding of the M... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.3.3.9 T7 Reference Point Requirements
| The T7 reference point shall fulfil the following requirements:
- connect the IWK-SCEF to the SCEF for Monitoring Event reporting.
- connect the IWK-SCEF to the SCEF for NIDD service.
|
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.3.3.10 Ns Reference Point Requirements
| The Ns reference points shall fulfil the following requirements:
- Ns connects the SCEF to the RCAF;
- Ns supports the following functionality:
- request for network status by the SCEF;
- report of network status by the RCAF to the SCEF.
|
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.3.3.11 Nu Reference Point Requirements
| The Nu reference point shall fulfil the following requirements:
- Nu connects the SCEF to the PFDF;
- Nu supports the following functionality:
- Provision, modification and removal of a subset or all of the Packet Flow Descriptions (PFDs) in the PFDF according to the instructions received from the SCS/AS.
|
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.3.3.12 T8 Reference Point Requirements
| The T8 reference points shall fulfil the following requirements:
- connect one or more SCEF to one or more SCS/AS;
- use API-based communication model;
NOTE: The details of API aspects are left to Stage 3.
|
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.3.3.13 T9a/T9b Reference Point Requirements
| The T9a and T9b reference points shall fulfil the following requirements:
- T9a connects the UCMF to an AS;
- T9b connects the UCMF to the SCEF;
- supports the following functionality:
- provisioning of RACS database information to the UCMF.
|
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.4 Network Elements
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.4.1 General
| The following 3GPP network elements provide functionality to support the Indirect and Hybrid models of MTC.
NOTE: As further development of the MTC architecture takes place as well as when additional MTC common functionality and features are addressed, further network elements may be defined.
|
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.4.2 MTC-IWF
| To support the Indirect and Hybrid models of MTC, one or more instances of an MTC InterWorking Function (MTC-IWF) reside in the HPLMN. A MTC-IWF may be a standalone entity or a functional entity of another network element. The MTC-IWF hides the internal PLMN topology and relays or translates signalling protocols used o... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.4.3 HSS/HLR
| An HSS/HLR supporting device triggering shall support the following functionalities:
- termination of the S6m reference point where MTC-IWFs connect to the HLR/HSS;
- stores and provides to MTC-IWF (and optionally to MTC AAA) the mapping/lookup of E.164 MSISDN or external identifier(s) to IMSI and subscription inform... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.4.4 GGSN/P-GW
| A GGSN or P-GW supporting the Indirect or Hybrid model of MTC may support the following functionality
- Based on APN configuration and unavailability of MSISDN and External Identifiers(s) in the GGSN/PGW, the GGSN/PGW either queries a MTC AAA server for retrieval of External Identifier(s) based on IMSI or routes RADIU... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.4.5 SGSN/MME/MSC
| SGSN and MME specific functionality to support the Indirect and Hybrid models of MTC includes the following:
- MME terminates the T6a reference point;
- SGSN terminates the T6b reference point;
- may provide SGSN/MME congestion/load information to the MTC-IWF;
- monitoring event configuration by the SCEF; and
- mo... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.4.6 SMS-SC
| SMS-SC specific functionality to support the Indirect and Hybrid models of MTC includes the following:
- terminates the T4 reference point where MTC-IWFs connect to the SMS-SC; and
- supports PS-only MT-SMS that can be delivered with IMSI in lieu of E.164 MSISDN;
- provides the routing information it received from M... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.4.7 MTC AAA
| To support translation of the IMSI to External Identifier(s) at the network egress, an AAA function (MTC AAA) is used in the HPLMN. The MTC AAA may be deployed to return the External Identifier(s) based on IMSI. Alternatively the MTC AAA may be deployed as a RADIUS/Diameter proxy between the GGSN/PGW and the AAA server... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.4.8 Service Capability Exposure Function
| The Service Capability Exposure Function (SCEF) provides a means to securely expose the services and capabilities provided by 3GPP network interfaces. The SCEF provides a means for the discovery of the exposed services and capabilities. The SCEF provides access to network capabilities through homogenous network applica... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.4.9 Interworking SCEF
| The Interworking SCEF (IWK-SCEF) is optional. When deployed, the IWK-SCEF is located in the VPLMN for inter-connection with the SCEF of the HPLMN. The Interworking SCEF receives the Monitoring Event Reports from the underlying entities and sends them to the SCEF. The IWK-SCEF relays the non-IP data between the MME/SGSN... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.4.10 RAN Congestion Awareness Function
| A RCAF supporting network status reporting shall support the following functionalities:
- termination of the Ns reference point where SCEF connects to the RCAF;
- request for one-time or continuous reporting of network status changes by the SCEF; and
- report of one-time or continuous network status changes to the S... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.4.11 Packet Flow Description Function
| A Packet Flow Description Function (PFDF) shall support the following functionalities:
- Termination of the Nu reference point where SCEF connects to the PFDF;
- Management of Packet Flow Descriptions (PFDs) (i.e. provision, modification and removal) according to the instructions received from the SCS/AS via the SCEF... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.4.12 UE radio Capabilities Management Function
| UCMF specific functionality to support provisioning of RACS information includes the following:
- UCMF terminates the T9a reference point;
- UCMF terminates the T9b reference point.
The services and capabilities offered by UCMF to SCEF and SCS/AS include:
- RACS information provisioning.
|
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.5 High Level Function
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.5.1 Device Triggering Function
| Device Triggering is the means by which a SCS sends information to the UE via the 3GPP network to trigger the UE to perform application specific actions that include initiating communication with the SCS for the indirect model or an AS in the network for the hybrid model. Device Triggering is required when an IP addres... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.5.2 PS-only Service Provision
| PS-only service provision is providing a UE with all subscribed services via PS domain. PS-only service provision implies a subscription that allows only for services exclusively provided by the PS domain, i.e. packet bearer services and SMS services. The support of SMS services via PS domain NAS is a network deploymen... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.5.3 Core Network assisted RAN parameters tuning
| Core Network assisted RAN parameters tuning aids the RAN in optimizing the setting of RAN parameters. See TS 23.401 [7] for details.
|
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.5.4 UE Power Saving Mode
| A UE may adopt the PSM for reducing its power consumption. That mode is similar to power-off, but the UE remains registered with the network and there is no need to re-attach or re-establish PDN connections. A UE in PSM is not immediately reachable for mobile terminating services. A UE using PSM is available for mobile... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.5.5 Group Message Delivery
| The Group Message Delivery feature allows an SCS/AS to deliver a payload to a group of UEs. Two methods of Group Message Delivery are specified:
- Group Message Delivery via MBMS which is intended to efficiently distribute the same content to the members of a group that are located in a particular geographical area wh... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.5.6 Monitoring Events
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.5.6.1 General
| The Monitoring Events feature is intended for monitoring of specific events in 3GPP system and making such monitoring events information available via the SCEF. It is comprised of means that allow the identification of the 3GPP network element suitable for configuring the specific events, the event detection, and the e... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.5.6.2 Monitoring Events via HSS and MME/SGSN
| Monitoring Events via the HSS and the MME/SGSN enables SCEF to configure a given Monitor Event at HSS or MME/SGSN, and reporting of the event via HSS and/or MME/SGSN. Depending on the specific monitoring event or information, it is either the MME/SGSN or the HSS that is aware of the monitoring event or information and ... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.5.6.3 Monitoring Events via PCRF
| Monitoring Events via the PCRF enables the SCEF to retrieve the location information and to report communication failure of a UE. When not performing group monitoring, the SCEF acting as AF shall have an active Rx session to enable the PCRF to report these events. The procedure is defined in clause 6.2.3 of TS 23.203 [... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.