Device Trigger Parameters for 3GPP PRO-2014-0139-Device_triggering_for_3GPP_presentation Group Name: PRO Source: Tetsuo Inoue, Barbara Pareglio (NEC) , Syed Husain (NTT Docomo) Meeting Date: for discussion Agenda Item: input contribution

Architecture derived from 3GPP TS 23.682 V11.5.0 (2013-09) Check the specifications!

Tsp I/F protocol specification derived from 3GPP TS 29. 368 V11. 4 Tsp Submission, T4 Delivery Focus

Tsp I/F protocol specification derived from 3GPP TS 29. 368 V11. 4 Device-Action-Request (DAR) command Message Format: <DA-Request> ::= <Diameter Header: 8388639, REQ, PXY > < Session-Id > { Auth-Application-Id } { Auth-Session-State } { Origin-Host } { Origin-Realm } { Destination-Realm } [ Destination-Host ] [ Origin-State-Id ] [ Device-Action ] *[ Proxy-Info ] *[ Route-Record ] *[ AVP ] Mandatory and Fixed location for Diameter Based Protocol Mandatory for Diameter Based Protocol Mandatory for DAR command specific Optional for Diameter Based Protocol

Tsp I/F protocol specification derived from 3GPP TS 29. 368 V11. 4 Device-Action AVP AVP Format: Device-Action ::= < AVP Header: 3001 > [ External-Id ] [ MSISDN ] [ SCS-Identifier ] { Reference-Number } { Action-Type } [ Trigger-Data ] [ Validity-Time ] *[ AVP ] Mandatory and Fixed location for Diameter Based Protocol Conditional either for DAR command specific Optional for Diameter Based Protocol Mandatory for Diameter Based Protocol Optional for Diameter Based Protocol Focus

Tsp I/F protocol specification derived from 3GPP TS 29. 368 V11. 4 Action-Type AVP The Action-Type AVP (AVP code 3005) is of type Enumerated, and informs the MTC-IWF of what action type is required in the request and also informs the SCS of what action type is reported. The following values are defined: Device Trigger Request (1) This value indicates a device trigger request and is used: - in the Device-Action AVP of the Device-Action-Request command; - in the Device-Notification AVP of the Device-Action-Answer command. Delivery Report (2) This value indicates a delivery report sent from MTC-IWF to the SCS and is used: - in the Device-Notification AVP of the Device-Notification-Request command.

Tsp I/F protocol specification derived from 3GPP TS 29. 368 V11. 4 Trigger-Data AVP AVP Format: Trigger-Data ::= < AVP Header: 3003 > { Payload } [ Priority-Indication ] [ Application-Port-Identifier ] *[ AVP ]   Mandatory and Fixed location for Diameter Based Protocol Mandatory for Diameter Based Protocol Optional for Diameter Based Protocol Focus

Tsp I/F protocol specification derived from 3GPP TS 29. 368 V11. 4 Payload AVP The Payload AVP (AVP code 3004) is of type OctetString, and contains the payload to be transferred to the addressed device. Application-Port-Identifier AVP The Application-Port-Identifier AVP (AVP code 3010) is of type Unsigned32 and is used to uniquely identify the triggering application addressed in the device, see subclause 9.2.3.24.4 in 3GPP TS 23.040 [15] for further details. Check

Technical realization of the SMS 3GPP TS 23.040 V11.5.0 (2013-03) Protocols and protocol architecture 9.2 Service provided by the SM‑TL 9.2.3 Definition of the TPDU parameters 9.2.3.24 TP‑User Data (TP‑UD) 9.2.3.24.4 Application Port Addressing 16 bit address VALUE (port number) MEANING 0 ‑ 15999 UDP/TCP port numbers assigned by IANA without the need to refer to 3GPP. For the procedure, use and assignment of port numbers in this range – refer to the IANA database. (http://www.IANA.com/). See Note 1. 16000 ‑ 16999 Available for allocation by SMS applications without the need to refer to 3GPP or IANA. See Note 2. 17000 ‑ 49151 UDP/TCP port numbers assigned by IANA. For the procedure, use and assignment of port numbers in this range – refer to the IANA database. (http://www.IANA.com/). See Note 1. 49152 – 65535 Reserved for future allocation by 3GPP. For a port number in this range an application must be made to 3GPP.

T4 I/F protocol specification derived from 3GPP TS 29. 337 V11. 3 Device Trigger Request Information Element Name Mapping to Diameter AVP Cat. Description User Identifier (See 3GPP TS 29.336 [12]) User-Identifier M This information element shall contain the IMSI of the UE the trigger is to be applied, formatted according to 3GPP TS 23.003 [8], clause 2.2. This Information Element may contain the international ISDN number of the UE the device trigger was delivered, formatted according to 3GPP TS 23.003 [8], clause 3.3. The ISDN number shall be present if it is available to the MTC-IWF. This Information Element may contain the external identifier of the UE the device trigger was delivered, formatted according to 3GPP TS 23.003 [8], clause 19.7.2. The external identifier shall be present if it is available to the MTC-IWF. SM RP OA   SCS-Identity This Information Element shall contain the identity of the Service Capability Server that is requesting a device trigger to the UE. SM RP UI (See 3GPP TS 29.338 [13]) SM-RP-UI This information element shall contain short message transfer protocol data unit for device trigger. Serving Node Identity (See 3GPP TS 29.173 [14]) Serving-Node C This information element shall contain the serving node identity, i.e. SGSN/MME/MSC identity serving the UE. It shall be present if it is available to the MTC-IWF, e.g. the MTC-IWF retrieved this information from the HSS. Additional Serving Node Identity Additional-Serving-Node This information element shall contain another serving node identity, e.g. SGSN/MME/MSC identity, if there is any serving the UE. There may be multiple instances of this information elements. Trigger Reference Number (See 3GPP TS 29.368 [15]) Reference-Number This information element shall contain the Reference Number related to the device trigger request. It shall be present if it is available to the MTC-IWF, e.g. the MTC-IWF received this information over Tsp. Validity Period Validity-Period This information element shall contain the validity period of the device trigger request. Priority Indication Priority-Indication This information element shall contain the priority of the device trigger request.. SMS Application Port ID SMS-Application-Port-ID This information element shall contain the Application Port ID of the triggering application for the device trigger request. Supported Features (See 3GPP TS 29.229 [6]) Supported-Features O If present, this information element shall contain the list of features supported by the origin host. Focus

T4 I/F protocol specification derived from 3GPP TS 29. 337 V11. 3 Device-Trigger-Request (DTR) Command Message Format < Device-Trigger-Request > ::= < Diameter Header: 8388643, REQ, PXY, 16777311 > < Session-Id > { Auth-Session-State } { Origin-Host } { Origin-Realm } { Destination-Host } { Destination-Realm } { User-Identifier } { SCS-Identity } { SM-RP-UI } [ Serving-Node ] *[ Additional-Serving-Node ] [ Reference-Number ] [ Validity-Period ] [ Priority-Indication ] [ SMS-Application-Port-ID ] *[ Supported-Features ] *[ AVP ] *[ Proxy-Info ] *[ Route-Record ] Mandatory and Fixed location for Diameter Based Protocol Mandatory for Diameter Based Protocol Focus Optional for Diameter Based Protocol

SMS capable MME specification derived from 3GPP TS 29. 338 V11. 1 MT Forward Short Message Request Information element name Mapping to Diameter AVP Cat. Description SM RP DA   User-Name (See IETF RFC 3588 [6]) M This information element shall contain an IMSI SM RP OA SC-Address This information element shall contain the Service Centre address. SM RP UI SM-RP-UI This information element shall contain the short message transfer protocol data unit. MME Number for MT SMS MME-Number-for-MT-SMS This Information Element contains the ISDN number of the MME, see 3GPP TS 23.003 [3]. TFR-Flags C This information element shall contain a bit mask. Bit 0 indicates when set if the Service Centre has more messages to send SM Delivery Timer SM-Delivery-Timer O This information element, when present, shall indicate the SM Delivery Timer value set in the SMS-GMSC to the IP-SM-GW. SM Delivery Start Time SM-Delivery- Start-Time This information element, when present, shall indicate the timestamp (in UTC) at which the SM Delivery Supervision Timer was started in the SMS-GMSC. Supported Features Supported-Features (See 3GPP TS 29.229 [5]) If present, this information element shall contain the list of features supported by the origin host. Focus

SMS capable MME specification derived from 3GPP TS 29. 338 V11. 1 MT-Forward-Short-Message-Request (TFR) Command Message Format < MT-Forward-Short-Message-Request > ::= < Diameter Header: 8388646, REQ, PXY, 16777313 > < Session-Id > [ Vendor-Specific-Application-Id ] { Auth-Session-State } { Origin-Host } { Origin-Realm } [ Destination-Host ] { Destination-Realm } { User-Name } *[ Supported-Features ] { SC-Address } { SM-RP-UI } [ MME-Number-for-MT-SMS ] [ TFR-Flags ] [ SM-Delivery-Timer ] [ SM-Delivery-Start-Time ] *[ AVP ] *[ Proxy-Info ] *[ Route-Record ] Focus

SMS capable MME specification derived from 3GPP TS 29. 338 V11. 1 6.3.3.3 SM-RP-UI The SM-RP-UI is of type OctetString and it shall contain a short message transfer protocol data unit (TPDU) which is defined in 3GPP TS 23.040 [3] and represents the user data field carried by the short message service relay sub-layer protocol. Its maximum length is of 200 octets. Focus

Technical realization of the SMS 3GPP TS 23.040 V11.5.0 (2013-03) Protocols and protocol architecture 9.2 Service provided by the SM‑TL 9.2.3 Definition of the TPDU parameters 9.2.3.9 TP‑Protocol‑Identifier (TP‑PID) In the case where bit 7 = 0, bit 6 = 1, bits 5..0 are used as defined below 5 .. . .0 001000 Device Triggering Short Message It is a Mandatory parameter for “Device Triggering” in TP-PID/TPDU/SM-RP-UI/DTR Command of T4 IF. But other part of TPDU/SM-RP-UI is NOT mandatory. Payload (user data) should be mapped to the other part. Trigger-Data AVP including Payload AVP in DAR command of Tsp IF is optional. Because, MTC-IWF is able to set TP-PID for T4 IF as “Device Triggering SM” by checking Action-Type AVP received via Tsp IF.

Mapping between oneM2M and 3GPP (1/4) 3GPP Specifications oneM2M TS23.040 (SMS) Ref. section 9.2.2.1 TS29.338 (SMS in MME) Ref. section 6.2.2 TS29.337 (T4 i/f) Ref. section 5.2.1 TS29.368 (Tsp i/f) Ref. section 6 TS-0001 (Architecture) Ref. v0.4.2 section 7 Parameter’s Name in “TPDU” M/O Parameter’s Name Parameter’s Name for DAR Command TP‑MTI M SM RP UI (See 3GPP TS 29.338 ) TP‑MMS TP-LP O TP‑RP (Note-8) TP‑UDHI (Note-9) TP‑SRI TP‑OA TP‑PID =b’01001000’ (Device Trigger SM) Action-Type AVP = “1” of DAR Command Device Triggering request TP‑DCS TP‑SCTS TP‑UDL TP‑UD (Note-1) Payload AVP (Note-7) Application Port Addressing 16 bit address in TP-UD SMS Application Port ID (See 3GPP TS 29.368) C Application-Port-Identifier AVP Trigger-Recipient-ID (Note-6)

Mapping between oneM2M and 3GPP (2/4) 3GPP Specifications oneM2M TS23.040 (SMS) Ref. section 9.2.2.1 TS29.338 (SMS in MME) Ref. section 6.2.2 TS29.337 (T4 i/f) Ref. section 5.2.1 TS29.368 (Tsp i/f) Ref. section 6 TS-0001 (Architecture) Ref. v0.4.2 section 7 Parameter’s Name in “TPDU” M/O Parameter’s Name Parameter’s Name for DAR Command SM RP DA (Note-2)  M User Identifier (See 3GPP TS 29.336) External-ID AVP or MSISDN AVP M2M-Ext-ID SM RP OA   (Note-3) SCS-Identifier AVP (Note-5) C M2M-Node-ID for IN?? MME Number for MT SMS (Note-4) Serving Node Identity (See 3GPP TS 29.173) TFR-Flags (Note-4) SM Delivery Timer O SM Delivery Start Time (Note-4) Supported Features Additional Serving Node Identity Trigger Reference Number Reference-Number AVP M2M-Request-ID?? Validity Period Validity-Time AVP (Note-10) Priority Indication Priority-Indication AVP (Note-11)

Mapping between oneM2M and 3GPP (3/4) 3GPP Specifications oneM2M TS23.040 (SMS) Ref. section 9.2.2.1 TS29.338 (SMS in MME) Ref. section 6.2.2 TS29.337 (T4 i/f) Ref. section 5.2.1 TS29.368 (Tsp i/f) Ref. section 6 TS-0001 (Architecture) Ref. v0.4.2 section 7 Parameter’s Name in “TPDU” M/O Parameter’s Name Parameter’s Name for DAR Command Diameter Header: 8388639, REQ, PXY M Session-Id AVP (Note-12) Auth-Application-Id AVP 16777309 (Ref. TS29.368 section 6.1.3) Auth-Session-State AVP Origin-Host AVP M2M-Node-ID for IN?? Origin-Realm AVP M2M-SP-ID?? Destination-Realm AVP UNetwork-ID?? Destination-Host AVP O (Note-13) Origin-State-Id AVP Proxy-Info AVP Route-Record AVP

Mapping between oneM2M and 3GPP (4/4) Note-1 If TP-UDL is set as other than 0, TP-UD is presented. If TP-UDHI is set as ‘1’, TP-UD contains a header field at the beginning. Refer to TS23.040 section 9.2.3.24. Note-2 In case of SMS in MME, the SM RP DA is set as the IMSI. But it is converted from MSISDN or External ID by 3GPP NW entities. Note-3 SM RP OA is set as SCS Identifier assumed by MTC-IWF. Note-4 These parameters are set appropriate values assumed by 3GPP NW entities based on local policy. Note-5 SCS-Identifier AVP may be needed when the Origin-Host AVP received by the MTC-IWF is different from the SCS-Identifier administrated by HSS for authorizing Device Trigger request to the target UE. It depends local policy and topology. Note-6 Trigger-Recipient-ID may be needed when the target UE has multiple applications and can not set the ASN/MN-CSE as only one for the dedicated recipient of the trigger. Note-7 Payload AVP may be set if IN-AE or IN-CSE requires. The format is FFS. The oneM2M should define it if standardized format is required. Note-8 oneM2M needs to confirm if these parameters (TP-RP, TP-SCTS) are left to be set the value as optional on the Payload including one of TPDU parameters by oneM2M. Note-9 Same note as above Note-8 for parameters (TP-UDHI, TP-DCS, TP-UDL). These parameters are related to the TP-UD (User Data). Note-10 oneM2M might define how to use this parameter or left for implementation. Note-11 oneM2M might define how to use this parameter or left for implementation. Note-12 Session-ID AVP should be for different purpose from Reference-Number AVP. Session-ID is used for a pair of a Diameter Request and the Answer. And Reference-Number may be used for a pair of a DAR (Device Action Request) and DNR (Device Notification Request, i.e. Reporting the Trigger result). So oneM2M might define other ID than M2M-Request-ID or left for implementation. Note-13 If 3GPP NW provider has multiple MTC-IWFs for load balancing or some other reasons, Destination-Host AVP may be needed to be set. But it depends on local policy or topology.