hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.13.158 Delay Tolerant Connection Indication | Delay Tolerant Connection Indication is defined in the 3GPP TS 23.401 [74] and 3GPP TS 23.060 [21]. Delay Tolerant Connection Indication is permanent data conditionally stored in MME, S4-SGSN, Gn/Gp-SGSN, PGW and GGSN. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.13.159 Pending Network Initiated PDN Connection Signalling Indication | Pending Network Initiated PDN Connection Signalling Indication is defined in the 3GPP TS 23.401 [74] and 3GPP TS 23.060 [21]. Pending Network Initiated PDN Connection Signalling Indication is temporary data conditionally stored in MME, S4-SGSN and Gn/Gp-SGSN. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.13.160 UE Radio Capability for Paging information | UE Radio Capability for Paging information is defined in the clause 5.11.4 of 3GPP TS 23.401 [74]. UE Radio Capability for Paging information is temporary data conditionally stored in MME. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.13.161 Information on Recommended Cells and ENBs for Paging | Information on Recommended Cells and ENBs for Paging is defined in 3GPP TS 23.401 [74].
Information on Recommended Cells and ENBs for Paging is temporary data conditionally stored in the MME. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.13.162 Paging Attempt Count | Paging Attempt Count is defined in 3GPP TS 23.401 [74].
Paging Attempt Count is temporary data conditionally stored in the MME. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.13.163 User Plane Integrity Protection Indicator | User Plane Integrity Protection Indicator is defined in 3GPP TS 43.020 [31].
User Plane Integrity Protection Indicator is permanent data conditionally stored in the HSS and SGSN. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.13.164 Non-IP-PDN-Type-Indicator | Non-IP-PDN-Type-Indicator is defined in 3GPP TS 29.272 [81]. It indicates whether the PDN type of the corresponding APN is Non-IP.
Non-IP-PDN-Type-Indicator is permanent subscriber data conditionally stored in the HSS and MME. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.13.165 Non-IP-Data-Delivery-Mechanism | Non-IP-Data-Delivery-Mechanism is defined in 3GPP TS 29.272 [81]. It indicates the mechanism to be used for Non-IP Data Delivery over a certain APN.
The parameter takes either of the following values:
- SGi-Based-Data-Delivery;
- SCEF-Based-Data-Delivery.
Non-IP-Data-Delivery-Mechanism is permanent subscriber data conditionally stored in the HSS and MME. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.13.166 SCEF-ID | SCEF-ID is defined in 3GPP TS 29.272 [81]. It indicates the identity (FQDN) of the SCEF to be used for Non-IP Data Delivery over a certain APN, when the selected data delivery mechanism is SCEF-based.
SCEF-ID is permanent subscriber data conditionally stored in the HSS and MME. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.13.167 PDN Type | PDN Type is defined in 3GPP TS 29.274 [81]. It indicates whether the PDN type is IPv4, IPv6, IPv4v6, Non-IP, or Ethernet.
PDN Type is permanent subscriber data conditionally stored in the HSS, S4-SGSN, MME, SGW and PGW.
NOTE: The S4-SGSN doesn't support Ethernet PDN type. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.13.168 PDN-Connection-Restricted flag | The PDN-Connection-Restricted flag is defined in 3GPP TS 29.272 [81]. It indicates whether a registration without a PDN connection is enforced for this user when applicable.
The PDN-Connection-Restricted flag is permanent subscriber data conditionally stored in the HSS and MME. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.13.169 Preferred-Data-Mode | Preferred-Data-Mode is defined in 3GPP TS 29.272 [81]. It indicates, for an SGi PDN connection, whether it is preferred to transmit the user's traffic associated to the APN over the User Plane or the Control Plane.
Preferred-Data-Mode is permanent subscriber data conditionally stored in the HSS and MME. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.13.170 IOV_updates counter | IOV_updates counter is defined in the 3GPP TS 29.060 [29]. IOV_updates counter is temporary data conditionally stored in a Gn/Gp-SGSN and S4-SGSN. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.13.171 Emergency Info | Emergency Info is defined in 3GPP TS 29.272 [81]. It contains the identity of the PGW dynamically allocated for emergency services.
Emergency Info is temporary subscriber data conditionally stored in the HSS, 3GPP AAA Server, MME and ePDG. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.13.172 Dedicated Core Network Identifier | Dedicated Core Network Identifier is defined in the 3GPP TS 23.003 [5]. Dedicated Core Network Identifier is temporary data conditionally stored in a Gn/Gp-SGSN, S4-SGSN and MME. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.13.173 Acknowledgements Of Downlink NAS Data PDUs flag | The Acknowledgement Of Downlink NAS Data PDUs flag is defined in 3GPP TS 29.272 [81]. It indicates whether acknowledgement of downlink NAS data PDUs for Control Plane CIoT Optimization is disabled for the UE.
The Acknowledgement Of Downlink NAS Data PDUs flag is permanent subscriber data conditionally stored in the HSS and MME. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.13.174 Service Gap Time | The Service Gap Time is defined in 3GPP TS 29.272 [81]. It indicates the minimum number of seconds during which the UE shall stay in ECM-IDLE mode, after leaving the ECM-CONNECTED mode, before being allowed to send a subsequent connection request to enter ECM-CONNECTED mode again.
The Service Gap Time is permanent subscriber data conditionally stored in the HSS and MME. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.13.175 Subscribed Additional RRM Policy Index | The Subscribed Additional RRM Policy Index (see 3GPP TS 23.401 [74]) is permanent data conditionally stored in HSS and MME. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.13.176 Additional RRM Policy Index in Use | The Additional RRM Policy Index in Use (see 3GPP TS 23.401 [74]) is temporary data conditionally stored in MME. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.13.177 Ethernet-PDN-Type-Indicator | Ethernet-PDN-Type-Indicator is defined in 3GPP TS 29.272 [81]. It indicates whether the PDN type of the corresponding APN is Ethernet.
Ethernet-PDN-Type-Indicator is permanent subscriber data conditionally stored in the HSS and MME. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.13.178 Time-Reference-Information-Distribution-Indication | Time-Reference-Information-Distribution-Indication is defined in 3GPP TS 29.272 [81]. It indicates whether the UE is subscribed to receive time reference information in access stratum.
Time-Reference-Information-Distribution-Indication is permanent subscriber data and conditionally stored in the HSS and MME. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.14 Data related to CAMEL | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.14.1 Subscriber Data stored in HLR | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.14.1.1 Originating CAMEL Subscription Information (O-CSI) | This data defines the contents of the Originating CAMEL subscription information used to interwork with the gsmSCF for MO and MF call. It consists of:
- A TDP list. The TDP list is a list of TDP descriptions. Each TDP description contains the following elements:
1. DP Value. The DP value identifies the DP in the MO State Model where service triggering may take place.
For O-CSI, the allowed DP value are DP Collected_info, DP Route_Select_Failure.
2. A gsmSCF address. It is the gsmSCF address ( E.164 number) where the CAMEL service is treated for the subscriber. A gsmSCF address is associated to each serviceKey.
3. A serviceKey. The serviceKey identifies to the gsmSCF the service logic. A serviceKey is associated to each TDP.
4. A default Call Handling. The default call handling indicates whether the call shall be released or continued as requested in case of error in the gsmSSF to gsmSCF dialogue. A default Call Handling is associated to each serviceKey.
5. DP criteria. The DP criteria indicates on which criteria the gsmSSF shall access the gsmSCF. DP criteria is associated to each TDP.
TDP
Triggering Criteria (see note)
ServiceKey
gsmSCF address
Default Call Handling
DP Collected_ Info
No Criterion
Number criteria
Basic service code criteria
Call type criteria
One ServiceKey
One E.164 gsmSCF address
One Default call handling
DP Route_Select_
Failure
No criterion
Cause value criteria
One ServiceKey
One E.164 gsmSCF address
One Default call handling
NOTE: One or more TDP criteria shall be applicable. All applicable triggering criteria must be satisfied before the dialogue is established with the gsmSCF.
- CAMEL capability handling. It gives the CAMEL phase associated to the O-CSI (CAMEL phase 1, phase 2, phase 3, or phase 4).
- The CSI state. The CSI state indicates whether the O-CSI is active or not.
- The notification flag, the notification flag indicates whether changes of the O-CSI shall trigger Notification on Change of Subscriber Data. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.14.1.2 Terminating CAMEL Subscription Information (T-CSI) and VMSC Terminating CAMEL Subscription Information (VT-CSI)); | This data defines the contents of the terminating CAMEL subscription information used to interwork with the gsmSCF for MT call. It consists of:
- A TDP list. The TDP list is a list of TDP descriptions. Each TDP description contains the following elements:
1. DP Value. The DP value identifies the DP in the MT State Model where service triggering may take place. For T-CSI, the allowed DP value are DP Terminating_Attempt_Authorised, DP T_Busy, DP T_No_Answer.
2. A gsmSCF address. It is the gsmSCF address (E.164 number) where the CAMEL service is treated for the subscriber. A gsmSCF address is associated to each serviceKey.
3. A serviceKey. The serviceKey identifies to the gsmSCF the service logic. A serviceKey is associated to each TDP.
4. A default Call Handling. The default call handling indicates whether the call shall be released or continued as requested in case of error in the gsmSSF to gsmSCF dialogue. A default Call Handling is associated to each serviceKey.
5. DP criteria. The DP criteria indicates on which criteria the gsmSSF shall access the gsmSCF. DP criteria is associated to each TDP.
TDP
Triggering Criteria (see note)
ServiceKey
gsmSCF address
Default Call Handling
DP Terminating_ Attempt_Authorised
No Criterion
Basic service criteria
One serviceKey
One E.164 gsmSCF address
One Default call handling
DP T_Busy
No criterion
Cause value criteria
One serviceKey
One E.164 gsmSCF address
One Default call handling
DP T_No_Answer
No criterion
Cause value criteria
One
service Key
One E.164 gsmSCF address
One Default call handling
NOTE: One or more TDP criteria shall be applicable. All applicable triggering criteria must be satisfied before the dialogue is established with the gsmSCF.
- CAMEL capability handling. It gives the CAMEL phase associated to the T-CSI/VT-CSI (CAMEL phase1, phase2, or phase3, or phase4).
- The CSI state indicates whether the T-CSI/VT-CSI is active or not.
- Notification flag. The notification flag indicates whether the change of the T-CSI/VT-CSI shall trigger Notification on Change of Subscriber data. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.14.1.3 Location information/Subscriber state interrogation. | This data item indicates whether or not the HLR shall send the location information and state of the called subscriber, as available, when a GMSC requests routeing information for an MT call. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.14.1.4 USSD CAMEL subscription information(U-CSI) | This data is used on USSD request receipt from the MS. It consists of a list of:
- a service code: the service code defines a specific application in the gsmSCF;
- a gsmSCFaddress: it is the gsmSCF address (E.164 number) where the USSD application is treated for this subscriber. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.14.1.5 Supplementary Service invocation notification(SS-CSI) | This data is used to notify the gsmSCF about Supplementary service invocation. It consists of:
- notification criterion, which may be a list of Supplementary Service(s). The possible Supplementary Services are: ECT, CD or MPTY, CCBS;
- a gsmSCFaddress: it is the gsmSCF address (E.164 number) where the notification of the Supplementary Service invocation is treated for this subscriber;
- CSI state, indicates whether the SS-CSI is active or not;
- notification flag: it indicates whether the change of the SS-CSI shall trigger Notification on Change of Subscriber data. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.14.1.6 Translation Information flag (TIF-CSI) | - TIF-CSI flag is used to indicate that the HLR shall not attempt to perform any actions on the FTN (translation, prohibited FTN checks, call barring checks) at the registration procedure.
- Notification flag. The notification flag indicates whether the change of TIF-CSI flag shall trigger Notification on Change of Subscriber data. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.14.1.7 Mobility Management event notification (M-CSI) | This data indicates which Mobility Management events shall be reported to the gsmSCF. It consists of:
- gsmSCF address: this is the address of the gsmSCF where the Mobility Management event notification shall be sent to. The gsmSCF address is in E.164 format.
- ServiceKey: the serviceKey is included in the notification to the gsmSCF and indicates to the gsmSCF which Service Logic shall be applied.
- Mobility Management Triggers: these triggers define which Mobility Managements events shall be reported to the gsmSCF. The mobility managements triggers may contain one or any combination of the following elements:
- Location update in the same VLR service area;
- Location update to another VLR service area;
- IMSI attach;
- MS initiated IMSI detach (explicit detach);
- Network initiated IMSI detach (implicit detach).
- The CSI state, indicates whether the M-CSI is active or not.
- Notification flag. The notification flag indicates whether the change of M-CSI shall trigger Notification on Change of Subscriber data. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.14.1.8 Mobile Originated Short Message Service CAMEL Subscription Information (MO-SMS-CSI) | This data defines the contents of the MO SMS CAMEL subscription information. The MO SMS CAMEL Subscription Information is used for the following interworking:
- Interworking between gsmSCF and gsmSSF, for CAMEL control of circuit switched MO SMS;
- Interworking between gsmSCF and gprsSSF, for CAMEL control of packet switched MO SMS.
MO-SMS-CSI consists of the following data items:
- TDP List. The TDP list is a list of SMS TDP descriptions. Each TDP description contains the following elements:
1. DP Value. The DP value identifies the DP in the MO SMS State Model where service triggering may take place.
For MO-SMS-CSI, the only allowed DP value is SMS_Collected_Info.
2. gsmSCF Address. The gsmSCF address is the address (E.164 number) of the gsmSCF where the MO SMS CAMEL Service associated with this TDP, is located for this subscriber.
3. ServiceKey. The serviceKey identifies to the gsmSCF the service logic that shall be applied.
4. Default SMS handling. The default SMS handling indicates whether the MO SMS submission request shall be rejected or continued in the case of error in the dialogue between the gsmSSF and gsmSCF or between the gprsSSF and gsmSCF;
- CAMEL Capability Handling. CAMEL Capability Handling indicates the CAMEL Phase that is required for the MO SMS service. The CAMEL Capability Handling for MO-SMS-CSI shall have the value CAMEL phase 3.
- CSI state: indicates whether the MO-SMS-CSI is active or not.
- Notification flag indicates whether the change of the SMS-CSI shall trigger Notification on change of subscriber Data or not. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.14.1.9 Mobile Terminating Short Message Service CAMEL Subscription Information (MT-SMS-CSI) | This data defines the contents of the mobile terminating short message service CAMEL subscription information. The MT-SMS-CSI CAMEL Subscription Information is used for the following interworking:
- Interworking between gsmSCF and gsmSSF, for CAMEL control of circuit switched MT SMS;
- Interworking between gsmSCF and gprsSSF, for CAMEL control of packet switched MT SMS.
MT-SMS-CSI consists of the following data items:
- TDP List. The TDP list is a list of MT SMS TDP descriptions. Each TDP description contains the following elements:
1. DP Value. The DP value identifies the DP in the MT SMS State Model where service triggering may take place.
For MT-SMS-CSI, the only allowed DP value is DP SMS-Delivery-Request
2. gsmSCF Address. The gsmSCF address is the address (E.164 number) of the gsmSCF where the MT SMS CAMEL Service associated with this TDP, is located for this subscriber.
3. ServiceKey. The serviceKey identifies to the gsmSCF the service logic that shall be applied.
4. Default SMS handling. The default SMS handling indicates whether the MT SMS delivery request shall be rejected or continued in the case of error in the dialogue between the gsmSSF and gsmSCF or between the gprsSSF and gsmSCF.
5. DP criterion. The DP criterion indicates on which criterion the gsmSSF shall access the gsmSCF. A DP criterion is associated with each TDP. For MT-SMS the DP criterion is the TDPU type. The criterion may be absent.
TDP
Triggering Criterion
ServiceKey
gsmSCF address
Default SMS Handling
DP SMS-Delivery Request
TDPU type
One serviceKey
One E.164 gsmSCF address
One Default SMS handling
- CAMEL Capability Handling. CAMEL Capability Handling indicates the CAMEL Phase that is required for the MT SMS service. The CAMEL Capability Handling for MT-SMS-CSI shall have the value CAMEL phase 4.
- CSI state: indicates whether the MT-SMS-CSI is active or not.
- Notification flag indicates whether the change of the MT-SMS-CSI shall trigger Notification on change of subscriber Data or not. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.14.1.10 GPRS CAMEL Subscription Information (GPRS-CSI) | This data defines the contents of the GPRS CAMEL subscription information. The GPRS CAMEL Subscription Information is used for the interworking between gsmSCF and gprsSSF, for CAMEL control of packet switch call.
GPRS-CSI consists of the following data items:
- TDP List. The TDP list is a list of GPRS TDP descriptions. Each TDP description contains the following elements:
1. DP Value. The DP value identifies the DP in the GPRS State Model where service triggering may take place.
2. gsmSCF Address. The gsmSCF address is the address (E.164 number) of the gsmSCF where the GPRS CAMEL Service associated with this TDP, is located for this subscriber.
3. Service Key. The service key identifies to the gsmSCF the service logic that shall be applied.
4. Default GPRS handling. The default GPRS handling indicates whether the GPRS submission request shall be rejected or continued in the case of error in the dialogue between the gprsSSF and gsmSCF.
- CAMEL Capability Handling. CAMEL Capability Handling indicates the CAMEL Phase that is required for the GPRS service. The CAMEL Capability Handling for GPRS-CSI shall have the value CAMEL phase 3.
- The CSI state indicates whether the GPRS-CSI is active or not.
- The notification flag indicates whether the change of the GPRS-CSI shall trigger Notification on change of subscriber Data or not. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.14.1.11 Dialled service CAMEL Subscription Information (D-CSI) | This data defines the contents of the dialled service CAMEL subscription information used to interwork with the gsmSCF for MO and MF call. It is applicable at TDP Analysed Info. It consists of:
- DP Criteria list. This consists of 1 to 10 entries. Each entry shall contain the following items:
1. DP Criterion. It indicates when the gsmSSF shall request gsmSCF for instructions. It is a destination number.
2. A gsmSCF address. It is the gsmSCF address (E.164 number) where this Subscribed Dialled CAMEL service is treated for the subscriber. A gsmSCF address is associated to each DP Criterion.
3. A serviceKey. The serviceKey identifies to the gsmSCF the service logic. A serviceKey is associated to each DP Criterion.
4. A default Call Handling. It indicates whether the call shall be released or continued as requested in case of error in the gsmSSF to gsmSCF dialogue. A default Call Handling is associated to each DP Criterion.
- CAMEL capability handling. It indicates the CAMEL phase associated to the D-CSI (CAMEL phase3, or Camel phase4 shall be indicated).
- CSI state: indicates whether the D-CSI is active or not.
- Notification Flag. It indicates whether the change of the D-CSI shall trigger the Notification on Change of Subscriber Data. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.14.1.12 Mobility Management for GPRS event notification (MG-CSI) | This data indicates which Mobility Management for GPRS subscriber events shall be reported to the gsmSCF. It consists of:
- gsmSCF address: this is the address of the gsmSCF where the Mobility Management event notification shall be sent to. The gsmSCF address is in E.164 format.
- Service Key: the service key is included in the notification to the gsmSCF and indicates to the gsmSCF which Service Logic shall be applied.
- Mobility Management Triggers: these triggers define which Mobility Managements events shall be reported to the gsmSCF. The mobility management triggers may contain one or any combination of the following elements:
- Routeing area update of MS to a different SGSN service area;
- Routeing area update of MS within the same SGSN service area;
- GPRS attach (e.g. MS switched on, successful routeing area update after network initiated detach);
- MS-initiated GPRS detach (e.g. MS switched off);
- Network-initiated transfer to the "not reacheable for paging" state (the network has not received a periodic routeing area update from the MS and assumes that the MS is unreacheable).
- The CSI state indicates whether the MG-CSI is active or not.
- Notification flag. The notification flag indicates whether the change of MG-CSI shall trigger Notification on Change of Subscriber data. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.14.2 Other Data stored in the HLR | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.14.2.1 Negotiated CAMEL Capability Handling | The HLR shall have a set of negotiated CAMEL Capability Handling variables. Each CSI that may be downloaded to the VLR or to the SGSN shall have a negotiated CAMEL Capability Handling (CCH) variable associated with it.
The negotiated CCH variable for a CSI indicates what CAMEL Phase is indicated in that CSI in the VLR or SGSN.
When the negotiated CCH variable has a value NULL, it indicates that the given CSI has not been downloaded to the VLR or SGSN.
The following table shows the negotiated CAMEL Capability Handling variables.
Variable name
Associated CSI
CSI stored in
Allowable values for negotiated CCH
O-CSI Negotiated CAMEL Capability Handling
O-CSI
VLR
NULL, 1, 2, 3, 4
D-CSI Negotiated CAMEL Capability Handling
D-CSI
VLR
NULL, 3, 4
SS-CSI Negotiated CAMEL Capability Handling
SS-CSI
VLR
NULL, 2
VT-CSI Negotiated CAMEL Capability Handling
VT-CSI
VLR
NULL, 3, 4
MO-SMS-CSI VLR Negotiated CAMEL Capability Handling
MO-SMS-CSI
VLR
NULL, 3
MT-SMS-CSI VLR Negotiated CAMEL Capability Handling
MT-SMS-CSI
VLR
NULL, 4
M-CSI Negotiated CAMEL Capability Handling
M-CSI
VLR
NULL, 3
MG-CSI Negotiated CAMEL Capability Handling
MG-CSI
SGSN
NULL, 4
MO-SMS-CSI SGSN Negotiated CAMEL Capability Handling
MO-SMS-CSI
SGSN
NULL, 3
MT-SMS-CSI SGSN Negotiated CAMEL Capability Handling
MT-SMS-CSI
SGSN
NULL, 4
GPRS-CSI Negotiated CAMEL Capability Handling
GPRS-CSI
SGSN
NULL, 3
There is no negotiated CAMEL Capability Handling variable associated with TIF-CSI.
The HLR does not store a Negotiated CAMEL Capability Handling for CSIs that are sent to the GMSC, since a subscriber is not permanently registered in a GMSC. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.14.2.2 Supported CAMEL Phases | The HLR shall store the supported CAMEL Phases of the VLR where the subscriber is currently registered and the SGSN where the subscriber is currently attached.
The following variables are required:
- VLR Supported CAMEL Phases
- SGSN Supported CAMEL Phases
The HLR does not store the Supported CAMEL Phases of the GMSC, since a subscriber is not permanently registered at a GMSC.
2.14.2.2A Offered CAMEL4 CSIs
The HLR shall store the offered CAMEL4 CSIs of the VLR where the subscriber is currently registered and the SGSN where the subscriber is currently attached.
The following variables are required:
- VLR Offered CAMEL4 CSIs
- SGSN Offered CAMEL4 CSIs
The HLR does not store the Offered CAMEL4 CSIs of the GMSC, since a subscriber is not permanently registered at a GMSC. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.14.2.3 UG-CSI | The USSD general CAMEL service(UG-CSI) is also stored in the HLR. This data is used on USSD request receipt from the MS. It consists of a list of:
- a service code. The service code defines a specific application in the gsmSCF;
- a gsmSCFaddress. It is the gsmSCF address (E.164 number) where the USSD application is treated for this subscriber. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.14.2.4 gsmSCF address for CSI | This information element contains the list of gsmSCF address (E.164 address) to which Notification on Change of Subscriber Data is to be sent. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.14.3 Subscriber data stored in VLR | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.14.3.1 Originating CAMEL Subscription Information (O-CSI) | The Originating CAMEL Subscription Information (O-CSI) are stored in the VLR.
This data defines the contents of the originating CAMEL subscription information used to interwork with the gsmSCF for MO and CF calls. It consists of:
- A TDP list: The TDP list is a list of TDP descriptions. Each TDP description contains the following elements:
1. DP Value. The DP value identifies the DP in the MO State Model where service triggering may take place.
For O-CSI, the allowed DP value are DP Collected_info, DP Route_Select_Failure.
2. A gsmSCF address. It is the gsmSCF address (E.164 number) where the CAMEL service is treated for the subscriber. A gsmSCF address is associated to each serviceKey.
3. A serviceKey. The serviceKey identifies to the gsmSCF the service logic.. A serviceKey is associated to each TDP.
4. A default Call Handling. The default call handling indicates whether the call shall be released or continued as requested in case of error in the gsmSSF to gsmSCF dialogue. A default Call Handling is associated to each serviceKey.
5. DP criteria: The DP criteria indicates on which criteria the gsmSSF shall access the gsmSCF. DP criteria is associated to each TDP.
- CAMEL capability handling. It gives the CAMEL phase associated to the O-CSI (CAMEL phase1, or phase2, phase3, or phase4). |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.14.3.2 VMSC Terminating CAMEL Subscription Information (VT-CSI) | This data defines the contents of the visited terminating CAMEL subscription information used by the VMSC to interwork with the gsmSCF for an MT call. It consists of:
- A TDP list. The TDP list is a list of TDP descriptions. Each TDP description contains the following elements:
1. DP Value. The DP value identifies the DP in the MT State Model where service triggering may take place. For VT-CSI, the allowed DP value are DP Terminating Attempt Authorised, DP T_Busy, DP T_No_Answer.
2. A gsmSCF address. It is the gsmSCF address (E.164 number) where the CAMEL service is treated for the subscriber. A gsmSCF address is associated to each serviceKey.
3. A serviceKey. The serviceKey identifies to the gsmSCF the service logic. A serviceKey is associated to each TDP.
4. A default Call Handling. The default call handling indicates whether the call shall be released or continued as requested in case of error in the gsmSSF to gsmSCF dialogue. A default Call Handling is associated to each serviceKey.
5. DP criteria: The DP criteria indicates on which criteria the gsmSSF shall access the gsmSCF.
- CAMEL capability handling. It gives the CAMEL phase associated to the VT-CSI. It is set to CAMEL phase3 or phase4. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.14.3.3 Supplementary Service invocation notification(SS-CSI) | This data is used to notify the gsmSCF about Supplementary Service invocation. It consists of :
- a notification criterion, which may be ECT, CD or MPTY
- a gsmSCFaddress. It is the gsmSCF address (E.164 number) where the notification of the Supplementary service invocation is treated for this subscriber. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.14.3.4 Mobility Management event notification (M-CSI) | This data indicates which Mobility Management events shall be reported to the gsmSCF. It consists of:
- gsmSCF address : This is the address of the gsmSCF where the Mobility Management event notification shall be sent to. The gsmSCF address must be in E.164 format.
- ServiceKey: The serviceKey is included in the notification to the gsmSCF and indicates to the gsmSCF which Service Logic shall be applied.
- Mobility Management Triggers. These triggers define which Mobility Managements events shall be reported to the gsmSCF. The mobility managements triggers may contain one or any combination of the following elements:
- Location update in the same VLR service area;
- Location update to another VLR service area;
- IMSI attach;
- MS initiated IMSI detach (explicit detach);
- Network initiated IMSI detach (implicit detach). |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.14.3.5 Mobile Originating Short Message Service CAMEL Subscription Information (MO-SMS-CSI) | This data defines the contents of the MO SMS CAMEL subscription information used for the interworking between gsmSCF and gsmSSF, for CAMEL control of circuit switched MO SMS.
MO-SMS-CSI consists of the following data items:
- TDP List. The TDP list is a list of SMS TDP descriptions. Each TDP description contains the following elements:
1. DP Value. The DP value identifies the DP in the MO SMS State Model where service triggering may take place.
For MO-SMS-CSI, the only allowed DP value is SMS_Collected_Info.
2. gsmSCF Address. The gsmSCF addess is the address (E.164 number) of the gsmSCF.
3. ServiceKey. The serviceKey identifies to the gsmSCF the service logic that shall be applied.
4. Default SMS handling. The default SMS handling indicates whether the MO SMS submission request shall be rejected or continued in the case of error in the dialogue between the gsmSSF and gsmSCF or between the gprsSSF and gsmSCF;
- CAMEL Capability Handling. CAMEL Capability Handling indicates the CAMEL Phase that is required for the MO SMS service.
The CAMEL Capability Handling for MO-SMS-CSI shall have the value CAMEL phase 3. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.14.3.6 Mobile Terminating Short Message Service CAMEL Subscription Information (MT-SMS-CSI) | This data defines the contents of the mobile terminating short message service CAMEL subscription information. The MT-SMS-CSI CAMEL Subscription Information is used for interworking between gsmSCF and gsmSSF, for CAMEL control of circuit switched MT SMS.
MT-SMS-CSI consists of the following data items:
- TDP List. The TDP list is a list of MT SMS TDP descriptions. Each TDP description contains the following elements:
1. DP Value. The DP value identifies the DP in the MT SMS State Model where service triggering may take place.
For MT-SMS-CSI, the only allowed DP value is SMS-Delivery-Request
2. gsmSCF Address. The gsmSCF address is the address (E.164 number) of the gsmSCF where the MT SMS CAMEL Service associated with this TDP, is located for this subscriber.
3. Service Key. The service key identifies to the gsmSCF the service logic that shall be applied.
4. Default SMS handling. The default SMS handling indicates whether the MT SMS delivery request shall be rejected or continued in the case of error in the dialogue between the gsmSSF and gsmSCF or between the gprsSSF and gsmSCF
5. DP criterion. The DP criterion indicates on which criterion the gsmSSF shall access the gsmSCF. A DP criterion is associated with each TDP. For MT-SMS the DP criterion is the TDPU type. The criterion may be absent.
TDP
Triggering Criterion
ServiceKey
gsmSCF address
Default SMS Handling
DP SMS-Delivery Request
TDPU type
One serviceKey
One E.164 gsmSCF address
One Default SMS handling
- CAMEL Capability Handling. CAMEL Capability Handling indicates the CAMEL Phase that is required for the MT SMS service. The CAMEL Capability Handling for MT-SMS-CSI shall have the value CAMEL phase 4. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.14.3.7 Dialled service CAMEL Subscription Information (D-CSI) | This data defines the contents of the dialled service CAMEL subscription information used to interwork with the gsmSCF for MO and MF call. It is applicable at TDP Analysed Info. It consists of:
- DP Criteria list, this consists of 1 to 10 entries containing : DP Criterion: It indicates when the gsmSSF shall request gsmSCF for instructions.
1. A gsmSCF address. It is the gsmSCF address (E.164 number) where this Subscribed Dialled CAMEL service is treated for the subscriber. A gsmSCF address is associated to each DP Criterion.
2. A serviceKey. The serviceKey identifies to the gsmSCF the service logic. A serviceKey is associated to each DP Criterion.
3. A default Call Handling. It indicates whether the call shall be released or continued as requested in case of error in the gsmSSF to gsmSCF dialogue. A default Call Handling is associated to each DP Criterion.
- CAMEL capability handling. It indicates the CAMEL phase associated to the D-CSI (CAMEL phase3 or CAMEL phase4 shall be indicated). |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.14.3.8 Translation Information flag (TIF-CSI) | This flag is used to indicate that the VLR shall not attempt to perform any actions on the deflected to number (DTN). |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.14.4 Data stored in SGSN | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.14.4.1 Mobile Originating Short Message Service CAMEL Subscription Information (MO-SMS-CSI) | This data defines the contents of the MO SMS CAMEL subscription information. The MO-SMS-CSI in SGSN is used for the Interworking between SGSN and gsmSCF, for CAMEL control of packet switched MO SMS.
MO-SMS-CSI consists of the following data items:
- TDP List. The TDP list is a list of SMS TDP descriptions. Each TDP description contains the following elements:
1. DP Value. The DP value identifies the DP in the MO SMS State Model where service triggering may take place.
For MO-SMS-CSI, the only allowed DP value is SMS_Collected_Info.
2. gsmSCF Address. The gsmSCF addess is the address (E.164 number) of the gsmSCF where the MO SMS CAMEL Service associated with this TDP, is located for this subscriber.
3. ServiceKey. The serviceKey identifies to the gsmSCF the service logic that shall be applied.
4. Default SMS handling. The default SMS handling indicates whether the MO SMS submission request shall be rejected or continued in the case of error in the dialogue between the gprsSSF and gsmSCF.
- CAMEL Capability Handling. CAMEL Capability Handling indicates the CAMEL Phase that is required for the MO SMS service.
The CAMEL Capability Handling for MO-SMS-CSI in SGSN shall have the value CAMEL phase 3. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.14.4.2 Mobile Terminating Short Message Service CAMEL Subscription Information (MT-SMS-CSI) | This data defines the contents of the mobile terminating short message service CAMEL subscription information. The MT-SMS-CSI CAMEL Subscription Information is used for the Interworking between gsmSCF and gprsSSF, for CAMEL control of packet switched MT SMS.
MT-SMS-CSI consists of the following data items:
- TDP List. The TDP list is a list of MT SMS TDP descriptions. Each TDP description contains the following elements:
1. DP Value. The DP value identifies the DP in the MT SMS State Model where service triggering may take place.
For MT-SMS-CSI, the only allowed DP value is SMS-Delivery-Request
2. gsmSCF Address. The gsmSCF address is the address (E.164 number) of the gsmSCF where the MT SMS CAMEL Service associated with this TDP, is located for this subscriber.
3. ServiceKey. The serviceKey identifies to the gsmSCF the service logic that shall be applied.
4. Default SMS handling. The default SMS handling indicates whether the MT SMS delivery request shall be rejected or continued in the case of error in the dialogue between the gprsSSF and gsmSCF.
5. DP criterion. The DP criterion indicates on which criterion the gsmSSF shall access the gsmSCF. A DP criterion is associated with each TDP. For MT-SMS the DP criterion is the TDPU type. The criterion may be absent.
TDP
Triggering Criterion
ServiceKey
gsmSCF address
Default SMS Handling
DP SMS-Delivery Request
TDPU type
One serviceKey
One E.164 gsmSCF address
One Default SMS handling
- CAMEL Capability Handling. CAMEL Capability Handling indicates the CAMEL Phase that is required for the MT SMS service. The CAMEL Capability Handling for MT-SMS-CSI shall have the value CAMEL phase 4. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.14.4.3 GPRS CAMEL Subscription Information (GPRS-CSI) | This data defines the contents of the GPRS CAMEL subscription information. The GPRS CAMEL Subscription Information is used for the interworkingbetween gsmSCF and gprsSSF, for CAMEL control of packet switch call.
The GPRS-CSI consists of the following data items:
- TDP List. The TDP list is a list of GPRS TDP descriptions. Each TDP description contains the following elements:
1. DP Value. The DP value identifies the DP in the GPRS State Model where service triggering may take place.
2. gsmSCF Address. The gsmSCF address is the address (E.164 number) of the gsmSCF where the GPRS CAMEL Service associated with this TDP, is located for this subscriber.
3. Service Key. The service key identifies to the gsmSCF the service logic that shall be applied.
4. Default GPRS handling. The default GPRS handling indicates whether the GPRS submission request shall be rejected or continued in the case of error in the dialogue between the gprsSSF and gsmSCF.
- CAMEL Capability Handling. CAMEL Capability Handling indicates the CAMEL Phase that is required for the GPRS service. The CAMEL Capability Handling for GPRS-CSI in SGSN shall have the value CAMEL phase 3. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.14.4.4 Mobility Management for GPRS event notification (MG-CSI) | This data indicates which Mobility Management for GPRS events shall be reported to the gsmSCF. It consists of:
- gsmSCF address : This is the address of the gsmSCF where the Mobility Management for GPRS event notification shall be sent to. The gsmSCF address must be in E.164 format.
- Service Key: The service key is included in the notification to the gsmSCF and indicates to the gsmSCF which Service Logic shall be applied.
- Mobility Management Triggers. These triggers define which Mobility Management events shall be reported to the gsmSCF. The mobility management triggers may contain one or any combination of the following elements:
- Routeing area update of MS to a different SGSN service area;
- Routeing area update of MS within the same SGSN service area;
- GPRS attach (e.g. MS switched on, successful routeing area update after network initiated detach);
- MS-initiated GPRS detach (e.g. MS switched off);
- Network-initiated transfer to the "not reacheable for paging" state (the network has not received a periodic routeing area update from the MS and assumes that the MS is unreacheable). |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.15 Data related to IST | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.15.1 IST Alert Timer | The IST Alert Timer indicates the timer value that the VMSC and the GMSC shall use to inform the HLR about each of the call activities that an IST non-CAMEL subscriber performs.
This parameter is only sent to the VLRs which support the non-CAMEL IST functionality. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.16 Data related to Location Services | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.16.1 Subscriber Data stored in HLR | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.16.1.1 Privacy Exception List | This data contains the privacy classes for any target MS that identify the LCS clients permitted to locate the MS. For a detailed definition of this data, refer to 3GPP TS 23.271 [56]. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.16.1.2 GMLC Numbers | This data contains the GMLC addresses for an MS subscriber. These addresses may be used to verify that a location request from specific LCS clients is authorized for the target MS. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.16.1.3 MO-LR List | This data contains the classes of MO-LR that are permitted for the MS subscriber. For a detailed definition of this data, refer to 3GPP TS 23.271 [56]. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.16.1.4 Service Types | This data contains the privacy settings for any target MS that identify the permitted service types for LCS clients requesting positioning of the MS. For a detailed definition of this data, refer to 3GPP TS 23.271 [56]. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.16.2 Data stored in GMLC | The GMLC stores data related to LCS clients. Refer to 3GPP TS 23.271 [56] for a detailed description. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.16.3 Data stored in SMLC (GSM only) | The SMLC stores data related to associated Type A and Type B LMUs from which location measurements may be received. Refer to GSM 23.271 [56] for a detailed description. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.16.4 Data stored in LMU (GSM only) | The LMU stores data related to its LCS measurement and O&M capabilities and may store data related to LCS measurements and O&M reports that it is required to provide to its controlling SMLC. The nature and content of this data is not defined in GSM. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.16.5 Data stored in the MSC (GSM only) | In order to support routing of connectionless LCS messages to an SMLC or a Type B LMU, the MSC may store permanent routing data for an SMLC or a Type B LMU in association with a specific location area identifier or location area identifier plus cell identifier. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.16.6 Data stored in the BSC (GSM only) | In order to support routing of connectionless LCS messages to an SMLC or a Type B LMU, the BSC may store permanent routing data for an SMLC or a Type B LMU in association with a specific location area identifier or location area identifier plus cell identifier. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.16.7 Subscriber Data stored in HSS | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.16.7.1 List of Broadcast Location Assistance Data Types | This data contains information used to determine which ciphering key data should be provided to the UE if requested by the UE, when location assistance data is broadcast in E-UTRAN using ciphering. For a detailed definition of this data, refer to 3GPP TS 23.271 [56]. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.17 Data related to Super-Charger | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.17.1 Age Indicator | This data indicates the age of the subscription data provided by the HLR, e.g. the date and time at which the subscriber data was last modified in the HLR. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.18 Data related to bearer service priority | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.18.1 CS Allocation/Retention priority | The Circuit Switched ( CS ) Allocation/Retention priority corresponds to the allocation/retention priority which is defined in 3GPP TS 23.107 [93]. It specifies the relative importance compared to other UMTS bearers for allocation and retention of the UMTS bearer in the CS domain.
The parameter is permanent subscriber data and is conditionally stored in the HLR and VLR. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.19 Data related to charging | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.19.1 Subscribed Charging Characteristics | Subscribed Charging Characteristics are specified in 3GPP TS 32.251[84], for example whether the subscriber is a normal, prepaid, flat rate and/or hot billing subscriber.
Subscribed Charging Characteristics is permanent subscriber data and conditionally stored in HSS/HLR, SGSN, MME and ePDG (for GTP-based S2b only) (see 3GPP TS 23.060 [21], 3GPP TS 23.401 [74] and 3GPP TS 29.273[78]). |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.20 Data related to IMS Centralized Service | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.20.1 ICS Indicator | The ICS Indicator specifies whether or not the subscriber is an ICS user (see 3GPP TS 23.292 [71]).
The ICS Indicator is permanent subscriber data and is conditionally stored in the HSS, MME, VLR and SGSN.
NOTE: The value of ICS Indicator is unique for a given subscriber, for both CS and PS, so its value is the same when sent by the HSS/HLR to the MME/SGSN/VLR over the different interfaces. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.21 Data related to SRVCC | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.21.1 STN-SR | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.21.1.1 General | The STN-SR identifies the Session Transfer Number for SRVCC or 5G-SRVCC (see 3GPP TS 23.003 [5]).
The STN-SR is temporary data and is conditionally stored in the UDM, HSS, AMF, MME and SGSN (see 3GPP TS 23.216 [80]). |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.21.1.2 STN-SR in EPS or GPRS | The existence or absence of a STN-SR data in the HSS indicates that the user is SRVCC subscribed or not SRVCC subscribed. This information on SRVCC subscription is independent of the STN-SR value. The creation or deletion of the STN-SR data in the HSS is ensured by provisioning.
NOTE: Backward compatibility cases (e.g. Pre-Release 10 AS) can still require provisioning of the STN-SR. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.21.1.3 STN-SR in 5GS | The existence or absence of a STN-SR data in the UDM indicates that the user is 5G-SRVCC subscribed or not 5G-SRVCC subscribed. This information on SRVCC subscription is independent of the STN-SR value. The creation or deletion of the STN-SR data in the UDM is ensured by provisioning. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.21.2 UE SRVCC Capability | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.21.2.1 General | This information element indicates the SRVCC capability of the UE and is described in 3GPP TS 23.237 [87]. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.21.2.2 UE SRVCC Capability in EPS | The UE SRVCC Capability is temporary data conditionally stored in the HSS, MME and SGSN. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.21.2.3 UE SRVCC Capability in 5GS | The UE 5G SRVCC Capability is temporary data conditionally stored in the UDM and AMF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.21.3 Subscribed vSRVCC | The Subscribed vSRVCC is permanent data and is conditionally stored in the HSS and MME (see 3GPP TS 23.216 [80]). The Subscribed vSRVCC indicates that the user is subscribed to the Single Radio Video Call Continuity (vSRVCC) or not. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.21.4 CS to PS SRVCC Allowed | The CS to PS SRVCC Allowed indicator is permanent data and is conditionally stored in the HSS and VLR (see 3GPP TS 23.216 [80]). The CS to PS SRVCC Allowed indicator indicates per PLMN whether the user is allowed to have CS to PS Single Radio Voice Call Continuity or not. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.22 Data related to MBMS | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.22.1 MBMS GW F-TEID for Sm (Control Plane) | The MBMS GW F-TEID for Sm (Control Plane) is defined in 3GPP TS 29.274 [75]. MBMS GW F-TEID for Sm (control plane) is temporary data conditionally stored in MBMS GW and MME. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.22.2 MBMS GW F-TEID for Sn (Control Plane) | The MBMS GW F-TEID for Sn (Control Plane) is defined in 3GPP TS 29.274 [75]. MBMS GW F-TEID for Sn (control plane) is temporary data conditionally stored in MBMS GW and SGSN. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.22.3 Temporary Mobile Group Identity | Temporary Mobile Group Identity (TMGI) (see 3GPP TS 23.246 [85]) is permanent data stored in MBMS GW, MME, SGSN and BM-SC. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.22.4 MBMS Flow Identifier | The MBMS Flow Identifier is defined in 3GPP TS 23.246 [85]. MBMS Flow Identifier is permanent data conditionally stored in MBMS GW, MME, SGSN and BM-SC. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.22.5 MBMS IP Multicast Distribution | The MBMS IP Multicast Distribution is defined in 3GPP TS 29.274 [75]. MBMS IP Multicast Distribution is temporary data conditionally stored in MBMS GW, MME and SGSN. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.22.6 MBMS Service Area | The MBMS Service Area is defined in 3GPP TS 23.246 [85]. MBMS Service Area is permanent data conditionally stored in MBMS GW, MME, SGSN and BM-SC. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.22.7 MME F-TEID for Sm (Control Plane) | The MME F-TEID for Sm (Control Plane) is defined in 3GPP TS 29.274 [75]. This is temporary data conditionally stored in MBMS GW and MME. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.22.8 SGSN F-TEID for Sn (Control Plane) | The SGSN F-TEID for Sn (Control Plane) is defined in 3GPP TS 29.274 [75]. This is temporary data conditionally stored in MBMS GW and S4-SGSN. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.22.9 SGSN F-TEID for Sn (User Plane) | The SGSN F-TEID for Sn (User Plane) is defined in 3GPP TS 23.246 [85]. This is temporary data stored in MBMS GW and S4-SGSN. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.22.10 MBMS session identifier | The MBMS Session identifier is defined in 3GPP TS 23.246 [85]. This is permanent data conditionally stored in MBMS GW, MME, SGSN and BM-SC. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.22.11 MBMS session duration | MBMS session duration is defined in 3GPP TS 23.246 [85]. This is permanent data conditionally stored in MBMS GW, MME, SGSN and BM-SC. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.