Tsp AVPs
Tsp (application id: 16777346)
Tsp interface facilitates communication between the Service Capability Server (SCS) and the Machine Type Communication Interworking Function (MTC-IWF) within the 3GPP network, specifically for Machine-Type Communication (MTC) services. The Tsp interface enables the SCS, which manages MTC applications, to interact with the MTC-IWF to perform actions like device triggers, message forwarding, and notifications within the network.
The Tsp interface connects the SCS and MTC-IWF, allowing for the secure and efficient exchange of signaling messages related to MTC services. The SCS is responsible for handling MTC applications, enabling them to communicate with the 3GPP network through the MTC-IWF. The MTC-IWF acts as an intermediary that translates and forwards commands from the SCS to the appropriate network elements, ensuring that the MTC services are executed as intended.
Key functional elements:
- Service Capability Server (SCS): The SCS is the interface between MTC applications and the 3GPP network. It facilitates the initiation of service requests and actions related to MTC devices and applications. The SCS can connect to multiple MTC-IWFs, and it is controlled by the HPLMN operator or an MTC service provider.
- MTC Interworking Function (MTC-IWF): The MTC-IWF resides within the HPLMN and handles communications between the SCS and the network. It supports multiple interfaces, including Tsp, S6m, T4, and others, to provide functions such as device triggering, session management, and secure communication.
Tsp interface workflow:
- Session Initialization: The SCS initiates a connection to the MTC-IWF over the Tsp interface to perform actions related to MTC services, such as sending a device trigger or managing notifications.
- Request Handling: Upon receiving a request from the SCS, the MTC-IWF processes the command. This could involve triggering a device, forwarding a message, or executing other MTC-related actions within the network.
- The MTC-IWF may need to interact with other network elements, such as the HSS, to retrieve necessary information or to complete the requested action.
- Command Execution: The MTC-IWF executes the command received over the Tsp interface. For instance, it might send a device trigger request to a connected device or forward a notification back to the SCS about the status of the action.
- The execution of these commands is based on the Diameter base protocol, ensuring reliable communication and processing.
- Notification and Response: After executing the command, the MTC-IWF sends a response back to the SCS, notifying it of the outcome. This could include success, failure, or additional information related to the request.
- The notification is sent using Diameter messages that are securely transported over the Tsp interface.
- Session Termination: Once the transaction is complete, the session between the SCS and MTC-IWF is implicitly terminated. The Tsp interface does not maintain session state information beyond the completion of the current transaction, ensuring efficient resource usage.
For complete technical specification of Tsp interface in Diameter protocol please refer to: [3GPP TS 29.368]
package com.mobius.software.telco.protocols.diameter.primitives.tsp
|
Name |
AVP Code |
Data Type |
Vendor |
|
Action-Type |
3005 |
Enumerated |
3GPP |
|
Defines the specific type of action that is being requested or reported in Tsp interface signaling between MTC-IWF (Machine Type Communication InterWorking Function) and SCS (Service Capability Server). Enumerated Values: 1: DEVICE_TRIGGER_REQUEST: A device trigger request; used in Device-Action-Request and Device-Action-Answer. 2: DELIVERY_REPORT: A delivery report from MTC-IWF to the SCS; used in Device-Notification-Request. 3: DEVICE_TRIGGER_RECALL: A request to recall a previously sent device trigger; used in Device-Action-Request and Answer. 4: DEVICE_TRIGGER_REPLACE: A request to replace a previously sent device trigger; used in Device-Action-Request and Answer. 5: MSISDN_LESS_MO_SMS_DELIVERY: Indicates the delivery of a Mobile-Originated SMS without MSISDN; used in Device-Notification-Request. |
|||
|
Application-Port-Identifier |
3010 |
Unsigned32 |
3GPP |
|
Used to uniquely identify the triggering application addressed in the device, see clause 9.2.3.24.4 in [TS 23.040] for further details. |
|||
|
Delivery-Outcome |
3009 |
Enumerated |
3GPP |
|
Communicates the result of a device action request to the SCS (Service Capability Server). It indicates whether the request was delivered to the device, failed, or could not be confirmed. The Delivery-Outcome AVP can be included in Device-Notification-Request command. Enumerated Values: 0: SUCCESS: The device action request was successfully completed. Corresponds to SUCCESSFUL_TRANSFER in [TS 29.337]. 1: EXPIRED: The validity period expired before the trigger could be delivered. Corresponds to VALIDITY_TIME_EXPIRED (temporary error). 2: TEMPORARYERROR: A temporary network error prevented the trigger delivery. 3: UNDELIVERABLE: Permanent failure. Trigger is deemed undeliverable (e.g., ABSENT_SUBSCRIBER or UE_MEMORY_CAPACITY_EXCEEDED in [TS 29.337]). 4: UNCONFIRMED: The delivery outcome is unknown; no confirmation was received. Note: The Absent-Subscriber-Diagnostic-T4 AVP specified in [TS 29.337], clause 6.3.2 is connected with the ABSENT_SUBSCRIBER value in the SM-Delivery-Outcome-T4 AVP. The Absent-Subscriber-Diagnostic-T4 AVP values will not be forwarded via the Tsp interface. |
|||
|
Device-Action |
3001 |
Grouped |
3GPP |
|
Used by the Service Capability Server (SCS) to request a specific action to be performed on a device via the MTC-IWF (Machine-Type Communication Interworking Function). The AVP structure is defined as follows: External-Id (Optional): Contains an external identifier for the UE. MSISDN (Optional): Contains the MSISDN of the device. SCS-Identity (Optional): Identifies the SCS making the request. Reference-Number (Mandatory): Unique identifier for the action. Old-Reference-Number (Optional): Used when this action replaces or refers to a previous one. Action-Type (Mandatory): Specifies the kind of action to be taken. Trigger-Data (Optional): Contains the payload for the device action trigger. Validity-Time (Optional): Specifies until when the action is valid. Optional additional AVPs may be included as extensions. |
|||
|
Device-Notification |
3002 |
Grouped |
3GPP |
|
Used by the MTC-IWF (Machine-Type Communication Interworking Function) to notify the Service Capability Server (SCS) about the outcome or status of a previously requested action (typically sent via a Device-Action AVP). The AVP structure is defined as follows: External-Id (Optional): External identifier of the UE. MSISDN (Optional): MSISDN of the device. SCS-Identity (Optional): Identity of the SCS that made the request. Reference-Number (Mandatory): Identifies the original trigger request. Action-Type (Mandatory): Describes the action being reported. Request-Status (Optional): Status of the request if still pending or in progress. MTC-Error-Diagnostic (Optional): Contains diagnostic info if an error occurred. Delivery-Outcome (Optional): Describes the final result of the action (e.g., success, failed). SM-RP-UI (Optional): Short Message Relay Protocol User Information (e.g., SMS payload). Application-Port-Identifier (Optional): Identifies the specific application targeted on the device. Optional additional AVPs may be included. |
|||
|
Feature-Supported-In-Final-Target |
3012 |
Unsigned32 (Bitmask) |
3GPP |
|
Used in the Tsp interface to indicate the features supported by the final target node (e.g., the SMS-SC). Bitmask Definitions: 0: Device-Trigger-Recall-Replace: Indicates that the SMS-SC supports device trigger recall and device trigger replace operations. If this bit is not set, the SCS must not send recall requests and must treat trigger replace as a new trigger. Actual encoding and applicability described in clause 6.4.13 of 3GPP [TS 29.368]. |
|||
|
Old-Reference-Number |
3011 |
Unsigned32 |
3GPP |
|
Used to uniquely identify a transaction which is intended to be replaced. |
|||
|
Payload |
3004 |
OctetString |
3GPP |
|
Contains the payload to be transferred to the addressed device. |
|||
|
Priority-Indication |
3006 |
Enumerated |
3GPP |
|
Specifies whether a device trigger is treated as priority or non-priority. This information helps the network distinguish between triggers that require immediate attention and those that can be processed with standard priority. Enumerated Values: 0: Non-Priority: Indicates the device trigger has non-priority. 1: Priority: Indicates the device trigger has priority. |
|||
|
Reference-Number |
3007 |
Unsigned32 |
3GPP |
|
Used to uniquely identify a transaction. The reference number is allocated by the initiator of a transaction and is used in all subsequent messages related to that transaction. |
|||
|
Request-Status |
3008 |
Enumerated |
3GPP |
|
The Request-Status AVP is used to inform the SCS (Service Capability Server) about the status or outcome of a device action request. It can include the result of MTC-IWF checks, the HSS/HLR interrogation and the SMS-SC submission trigger. The Request-Status AVP can be included in the Device-Action-Answer command. Enumerated Values: 0: SUCCESS: The device action request was successfully confirmed. 101: INVPAYLOAD: The payload is invalid due to exceeding implementation limits (e.g., max length). 102: INVEXTID: External Identifier is valid but unknown or rejected by the network. 103: INVSCSID: SCS Identity is valid but unexpected or not recognized. 104: INVPERIOD: Validity period exceeds the allowed duration or is otherwise rejected. 105: NOTAUTHORIZED: SCS is not authorized to perform the action for this UE. 106: SERVICEUNAVAILABLE: Trigger service is not available for the UE. 107: PERMANENTERROR: Permanent error occurred; general mapping from TS 29.337. 108: QUOTAEXCEEDED: SCS has exceeded the allowed quota. 109: RATEEXCEEDED: Tsp request rate limit exceeded. 110: REPLACEFAIL: Device trigger replace failed due to reasons other than message already sent. 111: RECALLFAIL: Device trigger recall failed due to reasons other than message already sent. 112: ORIGINALMESSAGESENT: This value indicates that the message which was intended to be recalled or replaced has already been sent. The result code DIAMETER_ERROR_ORIGINAL_MESSAGE_NOT_PENDING specified in [TS 29.337], clause 7.3.7 shall be mapped to this value. |
|||
|
Trigger-Data |
3003 |
Grouped |
3GPP |
|
Used by the Service Capability Server (SCS) to supply all required parameters for a device trigger request. The AVP structure is defined as follows: Payload (Mandatory): Contains the actual payload to be delivered to the device. Priority-Indication (Optional): Indicates whether the trigger is of high priority. Application-Port-Identifier (Optional): Identifies the triggering application in the device. |
|||
Start innovating with Mobius
What's next? Let's talk!