Note-3 sm rp oa is set as scs identifier assumed by mtc-iwf

Yüklə 526 b.

tarix	01.01.2018
ölçüsü	526 b.
	#36785

Note-3 SM RP OA is set as SCS Identifier assumed by MTC-IWF.
Note-10 oneM2M might define how to use this parameter or left for implementation.

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-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.

Yüklə 526 b.

Dostları ilə paylaş:

Note-3 sm rp oa is set as scs identifier assumed by mtc-iwf

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-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-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.