5.3 Information Storage
23.6823GPPArchitecture enhancements to facilitate communications with packet data networks and applicationsRelease 17TS
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.
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 used to indicate the UE used for MTC that is required to be triggered. |
Trigger reference number |
This is to co-relate the trigger request with trigger response. |
SCS ID |
It is used to allow the SMS SC to send the trigger response back to the appropriate SCS. |
Trigger payload |
The SMSC will store the Trigger payload until it receives the delivery confirmation. |
Routing Information for SMS |
The identities of the serving node(s). |
Priority |
It is used to indicate the priority of trigger request. |
Validity period |
To indicate the time period for which the trigger request is valid. |
SMS Application Port ID |
It is used to route the short message to the triggering function in the UE. |
NOTE 1: The Trigger Payload is stored as user data in SMS-SC.
NOTE 2: Priority, Validity period and SMS Application Port ID are included in the Trigger payload.
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 that uniquely identifies an SCEF connection. |
X |
X |
APN Rate Control |
The APN Rate Control limits the maximum number of uplink/downlink packets and the maximum number of additional exception report packets per a specific time unit (e.g. minute, hour, day, week) for this APN. It includes an indication as to whether or not Exception reports may still be sent when the limit has been met (see clause 4.7.7 of TS 23.401 [7]). |
X |
X |
NIDD Charging ID |
Charging identifier included in charging records generated by the MME/SGSN, the SCEF and IWK-SCEF. |
X |
X |
EPS Bearer ID |
An EPS bearer identity that uniquely identifies an EPS bearer for the UE and a context in the SCEF. |
X |
X (NOTE 1) |
Serving Node Information |
MME/SGSN address being used for the SCEF connection. |
X |
X |
Serving PLMN ID |
MCC + MNC of the serving PLMN |
X |
X |
IMEISV |
IMEISV for inclusion in CDR |
X |
X |
Serving PLMN Rate Control |
The Serving PLMN Rate Control limits the maximum number of uplink/downlink NAS Data PDUs in deci hour. For SCEF use with APN Rate Control and for inclusion on SCEF CDR to allow post processing of CDRs and permit detection of abusive UEs (see clause 4.7.7 of TS 23.401 [7]). |
X |
X |
NOTE 1: The SGSN uses the NSAPI of the PDP Context used for SCEF communication as an EPS Bearer ID when T6b is used.