Content for TS 29.368 Word version: 18.0.0
1 Scope
2 References
3 Definitions, symbols and abbreviations
3.1 Definitions
3.2 Symbols
3.3 Abbreviations
4 Tsp reference point
4.1 Tsp Reference model
4.2 Functional elements
...
...
1 Scope p. 5
The present document provides the stage 3 specification of the Tsp reference point for the present release. The functional requirements and the stage 2 specifications of the Tsp reference point are contained in TS 23.682. The Tsp reference point lies between the Service Capability Server (SCS) and the Machine Type Communication Inter Working Function (MTC-IWF).
2 References p. 5
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.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications".
[3]
TS 29.329: "Sh Interface based on the Diameter protocol".
[4]
RFC 791: "Transmission Control Protocol".
[5]
RFC 2234: "Augmented BNF for syntax specifications".
[6]
RFC 3588: "Diameter Base Protocol".
[7]
RFC 4006: "Diameter Credit Control Application".
[8]
RFC 4960: "Stream Control Transmission Protocol".
[9]
RFC 5719: "Updated IANA Considerations for Diameter Command Code Allocations".
[10]
TS 33.210: "Network Domain Security (NDS); IP network layer security".
[11]
TS 33.310: "Network Domain Security (NDS); Authentication Framework (AF)".
[12]
TS 29.336: "Home Subscriber Server (HSS) diameter interfaces for interworking with packet data networks and applications".
[13]
TS 29.303: "Domain Name System Procedures; Stage 3".
[14]
TS 23.003: "Numbering, addressing and identification".
[15]
TS 23.040: "Technical realization of the Short Message Service (SMS)".
[16]
TS 29.229: "Cx and Dx interfaces based on the Diameter protocol".
[17]
TS 29.337: "Diameter-based T4 interface for communications with packet data networks and applications".
[18]
RFC 6733: "Diameter Base Protocol".
[19]
RFC 8583:"Diameter Load Information Conveyance".
[20]
TS 29.338: "Diameter based protocols to support SMS capable MMEs".
3 Definitions, symbols and abbreviations p. 6
3.1 Definitions p. 6
For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
3.2 Symbols p. 6
For the purposes of the present document, no symbols are defined.
3.3 Abbreviations p. 6
For the purposes of the present document, the abbreviations given in TR 21.905 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.
AVP
Attribute Value Pair
CEA
Capabilities-Exchange-Answer
CER
Capabilities-Exchange-Request
DAA
Device-Action-Answer
DAR
Device-Action-Request
DNA
Device-Notification-Answer
DNR
Device-Notification-Request
DNS
Domain Name System
ESP
Encapsulating Security Payload
IKE
Internet Key Exchange
IWF
Inter Working Function
MTC
Machine Type Communication
PKI
Public key infrastructure
SCS
Service Capability Server
TLS
Transport Layer Security
4 Tsp reference point p. 7
4.1 Tsp Reference model p. 7
The Tsp reference point is defined between the Service Capability Server (SCS) and the Machine Type Communication Inter Working Function (MTC-IWF). The relationships between the different functional entities involved are depicted in Figure 4.1.1.
Figure 4.1.1: Tsp reference point at 3GPP Architecture for Machine -Type Communication
(⇒ copy of original 3GPP image)
(⇒ copy of original 3GPP image)
4.2 Functional elements p. 7
4.2.1 SCS p. 7
The SCS is the entity which connects MTC application servers to the 3GPP network to enable them to communicate through specific 3GPP defined services with UEs used for MTC and with the MTC-IWF in the HPLMN. The SCS offers capabilities for use by one or multiple MTC application servers.
An SCS can be connected to one or more MTC-IWFs.
The SCS is controlled by the operator of the HPLMN or by a MTC Service Provider.
4.2.2 MTC-IWF p. 7
The MTC-IWF resides in the HPLMN. An MTC-IWF could be a standalone entity or a functional entity of another network element. The MTC-IWF hides the internal PLMN topology and relays or translates information sent over Tsp to invoke specific functionality in the PLMN.
An MTC-IWF can be connected to one or more SCSs.
The functionality of the MTC-IWF includes the following:
- terminates the Tsp, S6m, T4 and Rf/Ga reference points;
- supports ability to authorize the SCS before communication establishment with the 3GPP network;
- supports ability to authorize control plane requests from an SCS;
-
supports the following device trigger functionality:
- reception of a device trigger request from SCS;
- reception of a device trigger recall/replace request from SCS;
- reporting to the SCS the acceptance or non-acceptance of the device trigger request;
- reporting to the SCS the acceptance or non-acceptance of the device trigger recall/replace request;
- reports to the SCS the success, failure or unconfirmed outcome of a device trigger delivery;
- reports to the SCS the success, failure or unconfirmed outcome of the device trigger recall/replace request;
- provides load control information to SCS as part of the response to trigger requests;
- for MSISDN-less MO-SMS, delivers a payload and application port ID and the external ID of the UE to the SCS;
- supports ability for secure communication between the 3GPP network and the SCS.
