Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 29.502  Word version:  18.7.0

Top   Top   Up   Prev   Next
1…   5…   5.2.2…   5.2.2.2.4…   5.2.2.3…   5.2.2.3.2…   5.2.2.3.3…   5.2.2.3.6…   5.2.2.3.8…   5.2.2.3.10…   5.2.2.3.17…   5.2.2.3.23…   5.2.2.4…   5.2.2.8…   5.2.2.8.2…   5.2.2.8.2.7…   5.2.2.8.2.12…   5.2.2.8.2.20…   5.2.2.8.3…   5.2.2.8.3.6…   5.2.2.9…   5.2.3…   6…   6.1.2…   6.1.3…   6.1.3.3…   6.1.3.5…   6.1.3.6…   6.1.3.7…   6.1.4…   6.1.6…   6.1.6.2…   6.1.6.2.5…   6.1.6.2.11…   6.1.6.2.18…   6.1.6.2.27…   6.1.6.2.40…   6.1.6.2.54…   6.1.6.2.65…   6.1.6.3…   6.1.6.4…   6.1.7…   A…   B…   C… 
6.1.6.4 Binary data  6.1.6.4.1 Introduction  6.1.6.4.2 N1 SM Message  6.1.6.4.3 N2 SM Information  6.1.6.4.4 n1SmInfoFromUe, n1SmInfoToUe, unknownN1SmInfo  6.1.6.4.5 N4 Message Payload  6.1.6.4.6 Mobile Originated Data  6.1.6.4.7 Mobile Terminated Data 
...

 

6.1.6.4  Binary data  p. 282

6.1.6.4.1  Introduction  p. 282
This clause defines the binary data that shall be supported in a binary body part in an HTTP multipart message (see clauses 6.1.2.2.2 and 6.1.2.4).
Name Clause defined Content type
N1 SM Message 6.1.6.4.2vnd.3gpp.5gnas
N2 SM Information 6.1.6.4.3vnd.3gpp.ngap
n1SmInfoFromUe 6.1.6.4.4vnd.3gpp.5gnas
n1SmInfoToUe 6.1.6.4.4vnd.3gpp.5gnas
unknownN1SmInfo 6.1.6.4.4vnd.3gpp.5gnas
N4 Message Payload 6.1.6.4.5vnd.3gpp.pfcp
Up
6.1.6.4.2  N1 SM Message  p. 283
N1 SM Message shall encode a 5GS NAS SM message as specified in TS 24.501, using the vnd.3gpp.5gnas content-type.
N1 SM Message may encode any 5GS NAS SM message specified in TS 24.501, as summarized in Table 6.1.6.4.2-1.
5GS NAS message Reference
(TS 24.501)
PDU session establishment request 8.3.1
PDU session establishment accept 8.3.2
PDU session establishment reject 8.3.3
PDU session authentication command 8.3.4
PDU session authentication complete 8.3.5
PDU session authentication result 8.3.6
PDU session modification request 8.3.7
PDU session modification reject 8.3.8
PDU session modification command 8.3.9
PDU session modification complete 8.3.10
PDU session modification command reject 8.3.11
PDU session release request 8.3.12
PDU session release reject 8.3.13
PDU session release command 8.3.14
PDU session release complete 8.3.15
5GSM status 8.3.16
Service-level authentication command 8.3.17
Service-level authentication complete 8.3.18
Remote UE Report 8.3.19
Remote UE Report Response 8.3.20
Up
6.1.6.4.3  N2 SM Information  p. 283
N2 SM Information shall encode NG Application Protocol (NGAP) IEs, as specified in clause 9.3 of TS 38.413 (ASN.1 encoded), using the vnd.3gpp.ngap content-type.
N2 SM Information may encode any NGAP SMF related IE specified in TS 38.413, as summarized in Table 6.1.6.4.3-1.
N2 SM IE Reference
(TS 38.413)		 Related NGAP message
PDU Session Resource Setup Request Transfer 9.3.4.1PDU SESSION RESOURCE SETUP REQUEST
INITIAL CONTEXT SETUP REQUEST
HANDOVER REQUEST
PDU Session Resource Setup Response Transfer 9.3.4.2PDU SESSION RESOURCE SETUP RESPONSE
INITIAL CONTEXT SETUP RESPONSE
PDU Session Resource Setup Unsuccessful Transfer 9.3.4.16PDU SESSION RESOURCE SETUP RESPONSE
INITIAL CONTEXT SETUP RESPONSE
PDU Session Resource Release Command Transfer 9.3.4.12PDU SESSION RESOURCE RELEASE COMMAND
PDU Session Resource Release Response Transfer 9.3.4.21PDU SESSION RESOURCE RELEASE RESPONSE
UE CONTEXT RELEASE COMPLETE
PDU Session Resource Modify Request Transfer 9.3.4.3PDU SESSION RESOURCE MODIFY REQUEST
PDU Session Resource Modify Response Transfer 9.3.4.4PDU SESSION RESOURCE MODIFY RESPONSE
PDU Session Resource Modify Unsuccessful Transfer 9.3.4.17PDU SESSION RESOURCE MODIFY RESPONSE
PDU Session Resource Notify Transfer 9.3.4.5PDU SESSION RESOURCE NOTIFY
PDU Session Resource Notify Released Transfer 9.3.4.13PDU SESSION RESOURCE NOTIFY
PDU Session Resource Modify Indication Transfer 9.3.4.6PDU SESSION RESOURCE MODIFY INDICATION
PDU Session Resource Modify Confirm Transfer 9.3.4.7PDU SESSION RESOURCE MODIFY CONFIRM
PDU Session Resource Modify Indication Unsuccessful Transfer 9.3.4.22PDU SESSION RESOURCE MODIFY CONFIRM
Path Switch Request Transfer 9.3.4.8PATH SWITCH REQUEST
Path Switch Request Setup Failed Transfer 9.3.4.15PATH SWITCH REQUEST
Path Switch Request Acknowledge Transfer 9.3.4.9PATH SWITCH REQUEST ACKNOWLEDGE
Path Switch Request Unsuccessful Transfer 9.3.4.20PATH SWITCH REQUEST ACKNOWLEDGE
PATH SWITCH REQUEST FAILURE
Handover Required Transfer 9.3.4.14HANDOVER REQUIRED
Handover Request Acknowledge Transfer 9.3.4.11HANDOVER REQUEST ACKNOWLEDGE
Handover Resource Allocation Unsuccessful Transfer 9.3.4.19HANDOVER REQUEST ACKNOWLEDGE
Handover Command Transfer 9.3.4.10HANDOVER COMMAND
Handover Preparation Unsuccessful Transfer 9.3.4.18HANDOVER COMMAND
Secondary RAT Data Usage Report Transfer 9.3.4.23SECONDARY RAT DATA USAGE REPORT
UE Context Resume Request Transfer 9.3.4.24UE CONTEXT RESUME REQUEST
UE Context Resume Response Transfer 9.3.4.25UE CONTEXT RESUME RESPONSE
UE Context Suspend Request Transfer 9.3.4.26UE CONTEXT SUSPEND REQUEST
Up
6.1.6.4.4  n1SmInfoFromUe, n1SmInfoToUe, unknownN1SmInfo  p. 284
n1SmInfoFromUe, n1SmInfoToUe and unknownN1SmInfo shall encode one or more NAS SM IEs, including the Type and Length fields, as specified in TS 24.501, using the vnd.3gpp.5gnas content-type.
Clause 5.2.3.1 specifies the information that shall be included in these payloads.
n1SmInfoFromUe and n1SmInfoToUe may encode the 5GS NAS IEs listed in Table 6.1.6.4.4-1 and Table 6.1.6.4.4-2.
5GS NAS IE Reference
(TS 24.501)		 Related NAS SM message
Message type 9.7All NAS SM messages
PDU session type 9.11.4.11PDU Session Establishment Request
SSC mode 9.11.4.16PDU Session Establishment Request
Maximum number of supported packet filters 9.11.4.9PDU Session Establishment Request
PDU Session Modification Request
Integrity protection maximum data rate 9.11.4.7PDU Session Modification Request
(NOTE 3)
SM PDU DN request container 9.11.4.15PDU Session Establishment Request
Extended protocol configuration options 9.11.4.6PDU Session Establishment Request
PDU Session Authentication Complete
PDU Session Modification Request
PDU Session Modification Complete
PDU Session Modification Command Reject
PDU Session Release Request
PDU Session Release Complete
EAP message 9.11.2.2PDU Session Authentication Complete
Requested QoS rules 9.11.4.13PDU Session Modification Request
Requested QoS flow descriptions 9.11.4.12PDU Session Modification Request
5GSM cause 9.11.4.2PDU Session Modification Request
PDU Session Release Request
PDU Session Release Complete
(NOTE 2)
5GSM capability 9.11.4.1PDU Session Establishment Request
PDU Session Modification Request
(NOTE 1)
Mapped EPS bearer contexts 9.11.4.8PDU Session Modification Request
Remote UE context connected 9.11.4.29Remote UE Report
Remote UE context disconnected 9.11.4.29Remote UE Report
Non-3GPP delay budget 9.11.4.37PDU Session Modification Request
NOTE 1:
The 5GSM capability IE shall be encoded as received from the UE. It may contain UE capabilities that the V-SMF (or I-SMF) only needs to transfer to the H-SMF (or SMF), e.g. support of reflective QoS, or support of multi-homed IPv6 PDU session, and/or capabilities to be interpreted and used by the V-SMF (or I-SMF).
NOTE 2:
The 5GSM cause IE shall be encoded as received from the UE.
This information is defined as a "V" IE (i.e. without a Type field) in other NAS messages, e.g. PDU Session Modification Command Reject message, in which case it shall be sent as a separate n1SmCause IE over N16/N16a and not within the n1SmInfoToUE binary data.
NOTE 3:
This information is defined as a "V" IE (i.e. without a Type field) in other NAS messages, e.g. PDU Session Establishment Request, in which case it shall be sent as separate maximum integrity protected data rate IEs over N16/N16a and not within the n1SmInfoFromUE binary data.
5GS NAS IE Reference
(TS 24.501)		 Related NAS SM message
Message type 9.7All NAS SM messages
RQ timer value 9.11.2.3PDU Session Establishment Accept
PDU Session Modification Command
EAP message 9.11.2.2PDU Session Establishment Accept
PDU Session Establishment Reject
PDU Session Authentication Command
PDU Session Authentication Result
PDU Session Release Command
Allowed SSC mode 9.11.4.5PDU Session Establishment Reject
Extended protocol configuration options 9.11.4.6PDU Session Establishment Accept
PDU Session Establishment Reject
PDU Session Authentication Command
PDU Session Authentication Result
PDU Session Modification Reject
PDU Session Modification Command
PDU Session Release Reject
PDU Session Release Command
5GSM cause 9.11.4.2PDU Session Establishment Accept
PDU Session Modification Command
(NOTE 1)
Mapped EPS bearer contexts 9.11.4.8PDU Session Establishment Accept
PDU Session Modification Command
ATSSS container 9.11.4.22PDU Session Establishment Accept
PDU Session Modification Command
N3QAI 9.11.4.36PDU Session Establishment Accept
PDU Session Modification Command
(NOTE 2)
NOTE 1:
This IE indicates the 5GSM cause the H-SMF (or SMF) requires the V-SMF (or I-SMF) to send to the UE. The V-SMF (or I-SMF) shall transfer the received value to the UE without interpretation.
This information is defined as a "V" IE (i.e. without a Type field) in other NAS messages, e.g. PDU Session Establishment Reject message, in which case it shall be sent as a separate n1SmCause IE over N16/N16a and not within the n1SmInfoToUE binary data.
NOTE 2:
N3QAI is configured in SMF based on the S-NSSAI and DNN for PIN service (see clause 5.44.3.3 of TS 23.501).
The Message Type shall be present and encoded as the first 5GS NAS IE in any n1SmInfoFromUe, n1SmInfoToUe and unknownN1SmInfo binary data, to enable the receiver to decode the 5GS NAS IEs.
Up
6.1.6.4.5  N4 Message Payload |R16|  p. 286
The N4 Message Payload shall encode a PFCP session related message as specified in TS 29.244, using the vnd.3gpp.pfcp content-type.
6.1.6.4.6  Mobile Originated Data |R16|  p. 286
Mobile Originated Data shall encode the Data Contents of the CIoT small data container or Payload Container specified in TS 24.501, using the vnd.3gpp.5gnas content-type, as summarized in Table 6.1.6.4.6-1.
Mobile Originated Data Reference
(TS 24.501)		 Related NAS SM message
Data contents in octet 4 to octet up to 257 of CIoT small data container contents. 9.11.3.18B
(Figure 9.11.3.18B.2)		Control Plane Service Request
Payload container contents in octets 4 to n 9.11.3.39
(Figure 9.11.3.39.1)		Control Plane Service Request
UL NAS Transport
Up
6.1.6.4.7  Mobile Terminated Data |R16|  p. 287
Mobile Terminated Data shall encode the Data Contents of the Payload Container specified in TS 24.501, using the vnd.3gpp.5gnas content-type, as summarized in Table 6.1.6.4.7-1.
Mobile Terminated Data Reference
(TS 24.501)		 Related NAS SM message
Payload container contents in octets 4 to n 9.11.3.39 (Figure 9.11.3.39.1)DL NAS Transport
Up

Up   Top   ToC