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.
External Identifier shall be globally unique. It shall have the following components:
Domain Identifier: identifies a domain that is under the control of a Mobile Network Operator (MNO). The Domain Identifier is used to identify where services provided by the operator network can be accessed (e.g. MTC-IWF or SCEF provided services). An operator may use different domain identifiers to provide access to different services and/or MTC Service Providers.
Local Identifier: Identifier used to derive or obtain the IMSI. The Local Identifier shall be unique within the applicable domain. It is managed by the Mobile Network Operator.
A subscription used for MTC may be associated to one or several IMSI-Group Identifier(s) (see TS 23.003) 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 Identifier that is described in clause 4.6.2. The Local Identifier is used to derive or obtain an IMSI-Group Identifier. An External Group Identifier maps to an IMSI-Group Identifier. An IMSI-Group Identifier maps to zero, one or several External Group Identifiers.
The External Group Identifier is used on the interface between the SCS/AS and the SCEF and on the interface between the SCEF and the HSS. This identifier is used in procedures such as group message delivery, communication pattern provisioning, and monitoring event configuration and deletion. When the External Group Identifier is used in the communication pattern provisioning or monitoring event configuration and deletion procedures, the HSS shall be able to resolve the External Group Identifier to an IMSI-Group Identifier and the associated External Identifier or MSISDN for each of the IMSIs in the IMSI-Group. The purpose of this association is to enable the SCEF to determine what UE Identifier to use (MSISDN or External Identifier) and derive APN from SCS/AS Identifier and the MSISDN or External Identifier to route non-IP data to the UE when non-IP data is sent to an External Group Identifier.
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 transactions consist of one or more request messages which may have one or more response messages. TLTRI is assigned by the SCEF and is unique through the duration of the transaction. It is stored on both the SCEF and the SCS/AS for the duration of the transaction.
T8 Destination Address is a parameter that is included by the SCS/AS in T8 messages where the SCS/AS can request response to a specific address.
Accuracy is an optional parameter which indicates the desired level of accuracy of the requested location information. It may be at cell level (CGI/ECGI) for GPRS/UTRAN/E-UTRAN, or (eNodeB-ID) eNodeB level, or (TAI/RAI) TA/RA level, or (PLMN-ID) PLMN-level, or TWAN identifier in TWAN access, or other formats, e.g. shapes (e.g. polygons, circles, etc.) or civic addresses (e.g. streets, districts etc.) or geographic co-ordinate (latitude, longitude), etc.
Idle Status Indication is an optional parameter that allows the SCS/AS to retrieve extra information, e.g. as specified in step 5 of clause 22.214.171.124, when a UE, for which PSM or extended idle mode DRX is enabled, transitions into idle mode.
TLTRI for Deletion identifies the TLTRI of the long-term transaction being requested for deletion.
Depending on operator configuration, accounting functionality for transactions over T8 may be supported by the SCEF.
Depending on operator configuration the MME, SGSN, SCEF and IWK-SCEF support accounting functionality for Monitoring Events, and NIDD via SCEF feature.
Accounting and charging information support for Monitoring Events is specified in TS 32.240 and TS 32.278.
Accounting and charging information support for NIDD via SCEF feature is specified in TS 32.240 and TS 32.253.