hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.5.6.4 Void
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.5.7 High latency communication
| Functions for High latency communication may be used to handle mobile terminated (MT) communication with UEs being unreachable while using power saving functions e.g. UE Power Saving Mode (see clause 4.5.4) or extended idle mode DRX (see clause 4.5.13) depending on operator configuration. "High latency" refers to the i... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.5.8 Support of informing about potential network issues
| The SCS/AS may request the SCEF for being notified about the network status in a geographical area. The SCS/AS can request for a one-time reporting of network status or a continuous reporting of network status changes.
|
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.5.9 Resource management of background data transfer
| The 3rd party SCS/AS requests a time window and related conditions from the SCEF for background data transfer to a set of UEs via the Nt interface. The SCS/AS request shall contain the SCS/AS identifier, SCS/AS Reference ID, the volume of data expected to be transferred per UE, the expected amount of UEs, the desired t... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.5.10 E-UTRAN network resource optimizations based on communication patterns provided to the MME
| Predictable communication patterns (CP) of a UE may be provided by the Application Server to the SCEF in order to enable network resource optimizations for such UE(s). The SCEF filters the CP parameters and forwards them to the HSS, which provides them to the MME. The MME may use the CP parameters as input to derive th... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.5.11 Support of setting up an AS session with required QoS
| The 3rd party SCS/AS may request that a data session to a UE that is served by the 3rd party service provider (AS session) is set up with a specific QoS (e.g. low latency or jitter) and priority handling. This functionality is exposed via the SCEF towards the SCS/AS.
The SCS/AS can request the network to provide QoS f... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.5.12 Change the chargeable party at session set-up or during the session
| The SCS/AS may request the SCEF to start or stop sponsoring a data session for a UE that is served by the 3rd party service provider (AS session), i.e. to realize that either the 3rd party service provider is charged for the traffic (start) or not (stop). The SCS/AS may request to be set as the chargeable party, i.e. s... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.5.13 Extended idle mode DRX
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.5.13.1 General
| The UE and the network may negotiate over non-access stratum signalling the use of extended idle mode DRX for reducing its power consumption, while being available for mobile terminating data and/or network originated procedures within a certain delay dependent on the DRX cycle value.
Applications that want to use ext... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.5.13.2 Paging for extended idle mode DRX in UTRAN
| The procedure makes use of the regular DRX cycle mechanism for determination of Paging Occasions (POs) (see TS 25.304 [34]) in conjunction with a new TeDRX timer and a means to synchronize the start of the TeDRX timer with a time reference referred to here as Tref. The TeDRX timer is set to the extended Idle mode DRX c... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.5.13.3 Paging for extended idle mode DRX in E-UTRAN
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.5.13.3.0 General
| For WB-E-UTRAN, the extended idle mode DRX value range will consist of values starting from 5.12s (i.e. 5.12s, 10.24s, 20.48s, etc.) up to a maximum of 2621.44s (almost 44 min). For NB-IoT, the extended idle mode DRX value range will start from 20.48s (i.e. 20.48s, 40.96s, 81.92, etc.) up to a maximum of 10485.76s (alm... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.5.13.3.1 Hyper SFN, Paging Hyperframe and Paging Time Window length
| A Hyper-SFN (H-SFN) frame structure is defined on top of the SFN used for regular idle mode DRX. Each H-SFN value corresponds to a cycle of the legacy SFN of 1024 radio frames, i.e. 10.24s. When extended idle mode DRX is enabled for a UE, the UE is reachable for paging in specific Paging Hyperframes (PH), which is a sp... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.5.13.3.2 Loose Hyper SFN synchronization
| NOTE: This clause applies for extended DRX cycle lengths of 10.24s or longer.
In order for the UE to be paged at roughly similar time, the H-SFN of all eNodeBs and MMEs should be loosely synchronized.
Each eNodeB and MME synchronizes internally the H-SFN counter so that the start of H-SFN=0 coincides with the same a ... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.5.13.3.3 MME paging and paging retransmission strategy
| NOTE: This clause applies for extended DRX cycle lengths of 10.24s or longer.
When the MME receives trigger for paging and the UE is reachable for paging, the MME sends the paging request. If the UE is not reachable for paging, then the MME pages the UE just before the next paging occasion.
The MME determines the Pag... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.5.14 Non-IP Data Delivery (NIDD)
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.5.14.1 General
| Functions for NIDD may be used to handle mobile originated (MO) and mobile terminated (MT) communication with UEs, where the data used for the communication is considered unstructured from the EPS standpoint (which we refer to also as Non-IP). The support of Non-IP data is part of the CIoT EPS optimizations. The Non-IP... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.5.14.2 Enhancements for reliable delivery of NIDD
| To ensure reliable delivery of Non-IP data (NIDD) between UE and SCEF using the Control Plane CIoT EPS Optimization, the following functions may be supported by the 3GPP system:
- Reliable delivery by acknowledgements on a hop-by-hop basis, i.e. the link layer protocol on each interface used for NIDD uses acknowledgme... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.5.14.3 Reliable Data Service
| The Reliable Data Service may be used by the UE and SCEF or P-GW when using PDN Connection of PDN Type 'Non-IP'. The service provides a mechanism for the SCEF or P-GW to determine if the data was successfully delivered to the UE and for UE to determine if the data was successfully delivered to the SCEF. When a requeste... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.5.15 Support of PFD management via SCEF
| The PFDs may be managed by the 3rd party SCS/AS via the SCEF, which ensures the secure access to the operator's network even from the 3rd party SCS/AS in untrusted domain. The 3rd party SCS/AS may request to create, update or remove PFDs in the PFDF via the SCEF.
The specific procedure for PFD management via SCEF is d... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.5.16 MSISDN-less MO-SMS via T4
| MSISDN-less MO-SMS via T4 is subscription based. The subscription provides the information whether a UE is allowed to originate MSISDN-less MO-SMS. Support for subscription without MSISDN is defined in TS 23.012 [36].
The UE is pre-configured with the Service Centre address that points to SMS-SC that performs this MO-... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.5.17 Enhanced Coverage Restriction Control via SCEF
| Restriction of use of the Enhanced Coverage is specified in TS 23.060 [6] and TS 23.401 [7]
The support for Enhanced Coverage Restriction Control via SCEF enables 3rd party service providers to query status of, enhanced coverage restriction or enable/disable enhanced coverage restriction per individual UEs. The specif... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.5.18 MBMS user service for UEs using power saving functions
| MBMS Bearer Services as defined in TS 23.246 [29] together with MBMS User Services defined in TS 26.346 [38], or MBMS Bearer Services accessed via the MB2 interface defined in TS 23.468 [30], provide means to deliver data or triggering payload over broadcast to multiple UEs at the same time. However, for UEs using powe... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.5.19 Enhancements to Location Services for CIoT
| Location Services (LCS) are defined in TS 23.271 [33]. In order to support Location Services for CIoT UEs, following enhancements to Location Services are defined (refer to TS 23.271 [33] for detailed procedures):
- Deferred location for the UE availability event:
- When extended idle mode DRX or PSM is used, a defer... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.5.20 MBMS user service for NB or M UE categories
| TS 36.306 [41] defines UE categories M1, M2 for WB-E-UTRAN and NB1, NB2 for NB-IoT that can only support limited bandwidth and transport block size. In order for UEs of these categories to be able to receive MBMS service, E-UTRAN needs to be able to determine the UE category that applies to the specific service indicat... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.5.21 Network Parameter Configuration via SCEF
| The SCS/AS may issue network parameter configuration requests to the network, via the SCEF, to suggest parameter values that may be used for Maximum Latency, Maximum Response Time and Suggested Number of Downlink Packets. By suggesting values for these parameters, the SCS/AS may influence certain aspects of UE/network ... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.5.22 RACS information provisioning
| The UCMF (UE radio Capability Management Function) stores all UE Radio Capability ID mappings in a PLMN and is responsible for assigning every PLMN-assigned UE Radio Capability ID in this PLMN, see TS 23.401 [7]. Provisioning of Manufacturer-assigned UE Radio Capability ID entries in the UCMF is performed from an AS th... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.5.23 Support of satellite access
| Support of satellite access for NB-IoT, WB-E-UTRAN and LTE-M is specified in TS 23.401 [7]. Unless otherwise stated in this specification, MTC functionality applies to NB-IoT, WB-E-UTRAN and LTE-M over satellite access. To support satellite access for NB-IoT, WB-E-UTRAN and LTE-M, the system enhancements including sate... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.6 Identifiers
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.6.1 General
| Identifiers relevant for the 3GPP network are specified in TS 23.003 [4].
|
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.6.2 External Identifier
| A subscription used for MTC has one IMSI and may have one or several External Identifier(s) that are stored in the HSS. If there are several External Identifiers, the HSS shall store one default External Identifier and one or more additional External Identifiers.
NOTE 1: If several External Identifiers are mapped to o... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.6.3 External Group Identifier
| A subscription used for MTC may be associated to one or several IMSI-Group Identifier(s) (see TS 23.003 [4]) that are stored in the HSS.
A subscription may be associated to one or several External Group Identifier(s) that are stored in the HSS. The External Group Identifier shall be formatted the same as the External ... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.7 Addressing
| For UEs used for Machine-Type Communications (MTC) IP Addressing principles and solutions for different scenarios are described in clause 5 of TS 23.221 [21].
|
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.8 Security Aspects
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.8.1 Security Requirements
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.8.1.0 General
| Security requirements are described in TS 33.187 [25].
|
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.8.1.1 Void
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.8.1.2 Void
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.9 SCEF - SCS/AS API Procedures
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.9.1 General
| This clause identifies commonalities (for both parameters and procedures) found on T8 interface.
|
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.9.2 Common Parameters
| This clause defines parameters which are required on T8 interface:
T8 Long Term Transaction Reference ID (TLTRI) is a parameter which refers to long term transaction (e.g. NIDD Configuration, Group Message Request, Monitoring Event configuration) between the SCEF and the SCS/AS when using T8 interface. Long term trans... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 4.10 Charging Principles
| Depending on operator configuration, accounting functionality for transactions over T8 may be supported by the SCEF.
NOTE: The details of the required accounting information are outside the scope of the present document.
Depending on operator configuration the MME, SGSN, SCEF and IWK-SCEF support accounting functiona... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5 Functional Description and Information Flow
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.1 Control and user plane
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.1.1 Control Plane
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.1.1.1 HSS – MTC-IWF
|
Legend:
- Diameter: This protocol supports transferring of subscription and UE related information for identifier mapping and serving node information retrieval between MTC-IWF and HSS (S6m). Diameter is defined in RFC 3588 [15].
- Stream Control Transmission Protocol (SCTP): This protocol transfers signalling mess... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.2 Device triggering procedures
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.2.1 Device triggering procedure over Tsp
|
Figure 5.2.1-1: Device triggering procedure over Tsp
1. The SCS determines the need to trigger the device. If the SCS has no contact details for an MTC-IWF, it may determine the IP address(es)/port(s) of the MTC-IWF by performing a DNS query using the External Identifier or using a locally configured MTC-IWF identif... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.2.2 Trigger Delivery using T4
|
Figure 5.2.2-1: T4 Trigger Delivery Flow
1. The MTC-IWF selects a suitable SMS-SC based on configured information. The MTC-IWF sends a Submit Trigger (External Identifier or MSISDN, IMSI, SCS Identifier, trigger reference number, validity period, priority, serving node ID(s) if available from HSS, SMS Application po... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.2.3 Device triggering recall/replace procedures
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.2.3.1 Device trigger recall/replace procedure over Tsp
|
Figure 5.2.3.1-1: Device trigger recall/replace procedure over Tsp
1. The SCS determines it needs to recall/replace a trigger message that it has previously submitted. The SCS sends Device Action Request (External Identifier or MSISDN, SCS Identifier, old trigger reference number, new trigger reference number, valid... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.2.3.2 Replace procedure for trigger delivery using T4
|
Figure 5.2.3.2-1: Replace procedure for trigger delivery using T4
1. Based on the Action type in Device Action Request message, the MTC-IWF sends a Submit Trigger Replace (External Identifier or MSISDN, IMSI, SCS Identifier, old trigger reference number, new trigger reference number, validity period, priority, servi... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.2.3.3 Recall procedure for trigger delivery using T4
|
Figure 5.2.3.3-1: Recall procedure for trigger delivery using T4
1. Based on the Action type in Device Action Request message, the MTC-IWF sends a Submit Trigger Recall (External Identifier or MSISDN, SCS Identifier, old trigger reference number) message to the SMS-SC. The MTC-IWF selects the SMS-SC to which the old... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.3 Information Storage
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.3.0 General
| This clause describes the context information that is stored in the different nodes for MTC device trigger procedure and NIDD procedures.
|
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.3.1 Trigger Information in SMS-SC (Triggering with T4)
| This table includes information that needs to be stored in SMS-SC for triggering with T4.
Table 5.3.1-1: SMS-SC trigger information
Field
Description
External Identifier/MSISDN
It is used to identify the corresponding External Identifiers in the delivery report. This can be also the MSISDN if used.
IMSI
It is us... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.3.2 SCEF
| The SCEF maintains the following EPS bearer context information for UEs. Table 5.3.2-1 shows the context fields for one UE.
Table 5.3.2-1: SCEF EPS bearer context
Field
Description
T6a
T6b
User Identity
(Multiple instances of this field may exist)
One of {IMSI, MSISDN, External Identifier}.
X
X
APN
An APN ... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.4 Security Procedures
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.4.0 General
| The security procedures are specified in TS 33.187 [25].
|
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.4.1 Void
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.4.2 Void
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.5 Group message delivery procedures
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.5.1 Group message delivery using MBMS
|
Figure 5.5.1-1: Group message delivery using MBMS
NOTE 1: Unless the SCS/AS wants to extend the expiration time for an allocated TMGI, steps 1-5 can be skipped if a valid TMGI allocation already exists or if the MBMS bearer activation is performed without TMGI pre-allocation.
If MB2 is used:
1. If there is no assi... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.5.2 Modification of previously submitted Group message
|
Figure 5.5.2-1: Modification of previously submitted Group Message
0. The pre-condition for this flow is the successful completion of step 11 from clause 5.5.1.
1. Application level interactions may be applied for the UEs of specific group to retrieve the related MBMS service information, e.g. TMGI, start time, etc... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.5.3 Group Message Delivery via unicast MT NIDD
|
Figure 5.5.3-1: Group Message Delivery via unicast MT NIDD
1. If SCS/AS has downlink non-IP data to send to a group of UEs, the SCS/AS sends a Group MT NIDD Submit Request (SCS/AS Identifier, External Group Identifier, TLTRI, non-IP data, Reliable Data Service Configuration, Maximum Latency, PDN Connection Establish... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6 Monitoring Procedures
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.0 Common Parameters
| This clause describes the common parameters required for Monitoring Event procedures.
SCEF Reference ID is a parameter created by the SCEF to associate a Monitoring Event report or a deletion of a Monitoring Event to a specific Monitoring Request and the associated context information within the SCEF. SCEF Reference I... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.1 Monitoring Event configuration and deletion via HSS
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.1.1 Configuration Procedure
| Figure 5.6.1.1-1 illustrates the procedure of configuring monitoring at the HSS or the MME/SGSN. The procedure is common for various Monitoring Event types. Common parameters for this procedure are detailed in clause 5.6.0. The steps and parameters specific to different Monitoring Event types are detailed in clauses 5.... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.1.2 Void
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.1.3 Specific Parameters for Monitoring Event: Loss of connectivity
| Loss of connectivity indicates when the 3GPP network detects that the UE is no longer reachable for either signalling or user plane communication. Such condition is identified when the mobile reachability timer expires in the MME or SGSN (see TS 23.401 [7], TS 23.060 [6], when the UE detaches and when an active UE is p... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.1.4 Specific Parameters for Monitoring Event: UE reachability
| For UE that is not reachable at the time of monitoring event configuration, UE reachability indicates when the UE becomes reachable for sending either SMS or downlink data to the UE, which is detected when the UE transitions to ECM-CONNECTED mode (for a UE using Power Saving Mode or extended idle mode DRX) or when the ... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.1.5 Specific Parameters for Monitoring Event: Location Reporting
| This monitoring event allows the SCS/AS to request either the Current Location or the Last Known Location of a UE. The supported Accuracy in the network may be at different levels, which are described in clause 4.9.2. Only One-time Reporting is supported for the Last Known Location. One-time and Continuous Location Rep... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.1.6 Specific Parameters for Monitoring Event: Change of IMSI-IMEI(SV) Association
| Change of IMSI-IMEI(SV) indicates a change of the ME (IMEI(SV)) that uses a specific subscription (IMSI). It is based on the HSS being informed by the MME about the UE's IMEI(SV) according to the procedures defined in TS 23.401 [7]. The support of this Monitoring Event by the SGSN requires the support of the Automatic ... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.1.7 Specific Parameters for Monitoring Event: Roaming Status
| This monitoring event allows the SCS/AS to query the UE's current roaming status (the serving PLMN and/or whether the UE is in its HPLMN) and to get notified when that status changes. It is based on the HSS being informed of the UE's serving PLMN by the MME according to TS 23.401 [7] and by the SGSN according to TS 23.... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.1.8 Specific Parameters for Monitoring Event: Communication failure
| This monitoring event allows the SCS/AS to be notified of communication failure events, identified by RAN/NAS Release Cause codes per TS 23.401 [7].
1. The SCS/AS sets Monitoring Type to "Communication Failure" prior to sending Monitoring Request to the SCEF as in step 1 of clause 5.6.1.1.
2. The SCEF executes step 2... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.1.9 Specific Parameters for Monitoring Event: Availability after DDN Failure
| This monitoring event allows the SCS/AS to be notified of availability of the UE after a DDN failure has occurred (see clause 5.7.1 Availability Notification after DDN Failure).
1. The SCS/AS sets Monitoring Type to "Availability after DDN Failure", and optionally Idle Status Indication prior to sending the Monitoring... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.1.10 Specific Parameters for Monitoring Event: PDN Connectivity Status
| This monitoring event allows the SCS/AS to be notified of the PDN Connectivity status when PDN Connections are created or deleted for the UE, and the existing PDN Connectivity status at the monitoring event configuration. The PDN Connectivity Status monitoring events report includes for each PDN Connection (that matche... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.1.11 Specific Parameters for Store and Forward Satellite operation information
| This monitoring event allows the SCS/AS to be notified of Store and Forward Satellite operation information, identified by EPS according to clause 4.13.9 of TS 23.401 [7].
1. The SCS/AS sets Monitoring Type to "Store and Forward Satellite operation information" prior to sending Monitoring Request to the SCEF as in ste... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.2 Monitoring Events configuration and deletion directly at the MME/SGSN
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.2.1 Configuration Procedure
| Figure 5.6.2.1-1 illustrates the procedure of configuring monitoring at the MME/SGSN. The procedure is common for various monitoring event types. Common parameters for this procedure are detailed in clause 5.6.2.2. The steps specific to different Monitoring Event types are detailed in clause 5.6.2.3. This procedure is ... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.2.2 Void
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.2.3 Specific Steps for Monitoring Event: Number of UEs present in a geographic area
| This monitoring event allows the SCS/AS to ask for the number of UEs that are in the geographic area described by the SCS/AS. The SCS/AS may ask for the UEs that the system knows by its normal operation to be within the area (Last Known Location) or the SCS/AS may request the system to also actively look for the UEs wi... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.3 Reporting of Monitoring Events from the HSS or the MME/SGSN
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.3.1 Reporting Procedure
| The following figure illustrates the common procedure flow of reporting Monitoring Events that are detected by the MME/SGSN or HSS. The steps specific to different Monitoring Event types are detailed in clauses 5.6.3.2 to 5.6.3.8.
Figure 5.6.3.1-1: Monitoring event reporting procedure
1a. A Monitoring Event is dete... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.3.2 Reporting Event: Loss of connectivity
| 1a. This monitoring event is detected as of step 1a of clause 5.6.3.1, which is when the mobile reachability timer expires, when an active UE is purged (see TS 29.272 [31]), when ISR is disabled and a UE, MME, SGSN, or HSS initiated detach occurs (see TS 23.401 [7], TS 23.060 [6]), or when ISR is enabled and a UE, MME,... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.3.3 Reporting Event: UE reachability
| 1a. This monitoring event is detected as of step 1a of clause 5.6.3.1, which is when the UE changes to connected mode or when the UE will become reachable for paging (for a UE using extended idle mode DRX).
If Maximum Response Time was included in step 5 of clause 5.6.1.4, then the MME/SGSN keeps the corresponding S1... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.3.4 Reporting Event: Location Reporting
| 1a. This monitoring event is detected as of step 1a of clause 5.6.3.1, which is when the MME/SGSN detects that the UE changes location with the granularity as requested by the monitoring event configuration.
2a. Step 2a of clause 5.6.3.1 is executed.
3. Step 3 of clause 5.6.3.1 is executed. Depending on operator conf... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.3.5 Reporting Event: Change of IMSI-IMEISV association
| 1b. This monitoring event is detected as of step 1b of clause 5.6.3.1, which is when the HSS receives from a serving node an IMEISV that is different from the IMEISV stored by the HSS for the IMSI.
2b. Step 2b of clause 5.6.3.1 is executed.
3. Step 3 of clause 5.6.3.1 is executed. The Monitoring Indication message in... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.3.6 Reporting Event: Roaming Status
| 1b. This monitoring event is detected as of step 1b of clause 5.6.3.1, which is when the HSS receives from a serving node a serving PLMN ID that is different from the one stored by the HSS.
2b. Step 2b of clause 5.6.3.1 is executed. If the UE is registered to different PLMNs via 3GPP and N3GPP Access Type, then the HS... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.3.7 Reporting Event: Communication failure
| 1a. This monitoring event is detected as of step 1a of clause 5.6.3.1, which is when the MME/SGSN becomes aware of a RAN or NAS failure event.
2a. Step 2a of clause 5.6.3.1 is executed.
3. Step 3 of clause 5.6.3.1 is executed. Based on operator configuration, the SCEF reports either the received failure cause code(s)... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.3.8 Reporting Event: Availability after DDN failure
| 1a. This monitoring event is detected as of step 1a of clause 5.6.3.1, which is when the MME/SGSN becomes aware of UE availability after DDN failure.
2a. Step 2a of clause 5.6.3.1 is executed.
3. Step 3 of clause 5.6.3.1 is executed.
|
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.3.9 Reporting Event: PDN Connectivity Status
| 1a. This monitoring event is detected as of step 1a of clause 5.6.3.1, which is when a new PDN connection is created for the UE, or when a PDN connection is deleted for the UE, or for PDN connections that exist when the PDN Connectivity Status monitoring event is configured in the MME/SGSN. Reporting is also done for P... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.3.10 Reporting Event: Store and Forward Satellite operation information
| 1a. This monitoring event is detected as of step 1a of clause 5.6.3.1, which is when the MME detects that:
- the UE is attached in a network operating in S&F Mode;
- - the UE is moving from a network operating in S&F Mode to a network not operating in S&F Mode (see clause 4.13.9 of TS 23.401 [7]); or
- there is chan... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.4 Monitoring events configuration and reporting via PCRF
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.4.1 Request of monitoring event reporting
| Figure 5.6.4-1 illustrates the procedure to request monitoring events reporting via PCRF with a reference to TS 23.203 [27]. The procedure is common for any monitoring event defined in clause 4.5.6.3 "Monitoring Events via PCRF".
Figure 5.6.4-1: Requesting monitoring via PCRF
1. The SCS/AS sends a Monitoring Reques... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.4.2 Common Parameters of the request reporting procedure
| The following parameters are applicable when the procedure for monitoring via PCRF is used: TLTRI, Monitoring Type, Priority and T8 Destination Address.
The Monitoring types are defined in clause 4.5.6. The Priority is relevant to the SCEF, not transferred over Rx or Nt.
For single UE monitoring, the following parame... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.4.3 Specific Parameters for Monitoring Event: Location Reporting
| This monitoring event allows the SCS/AS to request the Current Location. The supported Accuracy may be at different levels which are described in clause 4.9.2. The Monitoring Event Report delivers the subscriber location and may include a time stamp to indicate when the UE was last-known to be in that location, i.e. if... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.4.4 Specific Parameters for Monitoring Event: Communication Failure
| This monitoring event allows the SCS/AS to be notified of communication failure events, identified by RAN/NAS or TWAN/UWAN Release Cause codes, per TS 23.203 [27].
1. The SCS/AS sets Monitoring Type to "Communication Failure" in the Monitoring Request to the SCEF sent as in step 1 of 5.6.4.1.
2. The SCEF executes ste... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.5 Reporting of Monitoring Events from the PCRF
| The following figure illustrates the procedure to report Monitoring Events via PCRF. This procedure is applicable for reporting both user location information and communication failure for a single UE. This procedure does not apply to group monitoring. It is assumes that PCRF subscribes to Access Network Information re... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.