ShareTechnote

IP Network - NGAP

NGAP is the protocol(an Application Layer Protocol) being used in the communication between between gNB and AMF as illustrated below.

What I am going to do in this note is to provide details of NG Interface and NGAP (Protocol for NG Interface). Followings are the list of the topics on this note.

Overall Protocol Stack
General Principles of NG Interface
NGAP Capabilities
NGAP Elementary Procedure
NGAP Packet Structure
NGAP Establish
NR SA Registration
PDU Session Resource Setup

Overall Protocol Stack

Structure of the protocol stack for this interface is illustrated as below. Overall description and requirement of NGAP specified in 38.412 (very short specification). Since NGAP packet is encapsulated by IP and SCTP which are more of generic purpose (i.e, not 3GPP only), further details are specified in various RFC documents (Refer to 38.412 to know which RFC document you have to refer to). For the details of signaling procedure over NGAP, refer to 38.413.

General Principles of NG Interface

General principles of NG Interface is described in 38.410 - 4.2 as follows :

the NG interface is open;
the NG interface supports the exchange of signalling information between the NG-RAN and 5GC;
from a logical standpoint, the NG is a point-to-point interface between an NG-RAN node and a 5GC node. A point-to-point logical interface is feasible even in the absence of a physical direct connection between the NGRAN and 5GC;
the NG interface supports control plane and user plane separation;
the NG interface separates Radio Network Layer and Transport Network Layer;
the NG interface is future proof to fulfil different new requirements and support of new services and new functions;
the NG interface is decoupled with the possible NG-RAN deployment variants;
the NG Application Protocol supports modular procedures design and uses a syntax allowing optimized encoding /decoding efficiency.

NGAP Capabilities

According to 38.410-4.4, NGAP support following capabilities :

procedures to establish, maintain and release NG-RAN part of PDU sessions;
procedures to perform intra-RAT handover and inter-RAT handover;
the separation of each UE on the protocol level for user specific signalling management;
the transfer of NAS signalling messages between UE and AMF;
mechanisms for resource reservation for packet data streams.

NGAP Elementary Procedure

Followings are the list of signaling messages (Elementary Procedure) of NGAP. There are two types of elementary procedure classified into Class 1 and Class 2. The definition of Class 1 and Class 2 is stated in 38.413 - 3.1 as follows :

Class 1: Elementary Procedures with response (success and/or failure).
Class 2: Elementary Procedures without response.

The list of NGAP Elementary procedure and corresponding signaling message is defined in 38.413-8.1 as follows.

< 38.413 v16.7- Table 8.1-1: Class 1 procedures >

Elementary Procedure	Initiating Message	Successful Outcome	Unsuccessful Outcome	Examples
Elementary Procedure	Initiating Message	Response Message	Response Message	Examples
AMF Configuration Update	AMF CONFIGURATION UPDATE	AMF CONFIGURATION UPDATE ACKNOWLEDGE	AMF CONFIGURATION UPDATE FAILURE
RAN Configuration Update	RAN CONFIGURATION UPDATE	RAN CONFIGURATION UPDATE ACKNOWLEDGE	RAN CONFIGURATION UPDATE FAILURE
Handover Cancellation	HANDOVER CANCEL	HANDOVER CANCEL ACKNOWLEDGE
Handover Preparation	HANDOVER REQUIRED	HANDOVER COMMAND	HANDOVER PREPARATION FAILURE
Handover Resource Allocation	HANDOVER REQUEST	HANDOVER REQUEST ACKNOWLEDGE	HANDOVER FAILURE
Initial Context Setup	INITIAL CONTEXT SETUP REQUEST	INITIAL CONTEXT SETUP RESPONSE	INITIAL CONTEXT SETUP FAILURE
NG Reset	NG RESET	NG RESET ACKNOWLEDGE
NG Setup	NG SETUP REQUEST	NG SETUP RESPONSE	NG SETUP FAILURE
Path Switch Request	PATH SWITCH REQUEST	PATH SWITCH REQUEST ACKNOWLEDGE	PATH SWITCH REQUEST FAILURE
PDU Session Resource Modify	PDU SESSION RESOURCE MODIFY REQUEST	PDU SESSION RESOURCE MODIFY RESPONSE
PDU Session Resource Modify Indication	PDU SESSION RESOURCE MODIFY INDICATION	PDU SESSION RESOURCE MODIFY CONFIRM
PDU Session Resource Release	PDU SESSION RESOURCE RELEASE COMMAND	PDU SESSION RESOURCE RELEASE RESPONSE
PDU Session Resource Setup	PDU SESSION RESOURCE SETUP REQUEST	PDU SESSION RESOURCE SETUP RESPONSE
UE Context Modification	UE CONTEXT MODIFICATION REQUEST	UE CONTEXT MODIFICATION RESPONSE	UE CONTEXT MODIFICATION FAILURE
UE Context Release	UE CONTEXT RELEASE COMMAND	UE CONTEXT RELEASE COMPLETE
Write-Replace Warning	WRITE-REPLACE WARNING REQUEST	WRITE-REPLACE WARNING RESPONSE
PWS Cancel	PWS CANCEL REQUEST	PWS CANCEL RESPONSE
UE Radio Capability Check	UE RADIO CAPABILITY CHECK REQUEST	UE RADIO CAPABILITY CHECK RESPONSE
UE Context Suspend	UE CONTEXT SUSPEND REQUEST	UE CONTEXT SUSPEND RESPONSE	UE CONTEXT SUSPEND FAILURE
UE Context Resume	UE CONTEXT RESUME REQUEST	UE CONTEXT RESUME RESPONSE	UE CONTEXT RESUME FAILURE
UE Radio Capability ID Mapping	UE RADIO CAPABILITY ID MAPPING REQUEST	UE RADIO CAPABILITY ID MAPPING RESPONSE

< 38.413 - v16.7 :Table 8.1-2: Class 2 procedures >

Elementary Procedure	Message	Examples
Downlink RAN Configuration Transfer	DOWNLINK RAN CONFIGURATION TRANSFER
Downlink RAN Status Transfer	DOWNLINK RAN STATUS TRANSFER
Downlink NAS Transport	DOWNLINK NAS TRANSPORT
Error Indication	ERROR INDICATION
Uplink RAN Configuration Transfer	UPLINK RAN CONFIGURATION TRANSFER
Uplink RAN Status Transfer	UPLINK RAN STATUS TRANSFER
Handover Notification	HANDOVER NOTIFY
Initial UE Message	INITIAL UE MESSAGE
NAS Non Delivery Indication	NAS NON DELIVERY INDICATION
Paging	PAGING
PDU Session Resource Notify	PDU SESSION RESOURCE NOTIFY
Reroute NAS Request	REROUTE NAS REQUEST
UE Context Release Request	UE CONTEXT RELEASE REQUEST
Uplink NAS Transport	UPLINK NAS TRANSPORT
AMF Status Indication	AMF STATUS INDICATION
PWS Restart Indication	PWS RESTART INDICATION
PWS Failure Indication	PWS FAILURE INDICATION
Downlink UE Associated NRPPa Transport	DOWNLINK UE ASSOCIATED NRPPA TRANSPORT
Uplink UE Associated NRPPa Transport	UPLINK UE ASSOCIATED NRPPA TRANSPORT
Downlink Non UE Associated NRPPa Transport	DOWNLINK NON UE ASSOCIATED NRPPA TRANSPORT
Uplink Non UE Associated NRPPa Transport	UPLINK NON UE ASSOCIATED NRPPA TRANSPORT
Trace Start	TRACE START
Trace Failure Indication	TRACE FAILURE INDICATION
Deactivate Trace	DEACTIVATE TRACE
Cell Traffic Trace	CELL TRAFFIC TRACE
Location Reporting Control	LOCATION REPORTING CONTROL
Location Reporting Failure Indication	LOCATION REPORTING FAILURE INDICATION
Location Report	LOCATION REPORT
UE TNLA Binding Release	UE TNLA BINDING RELEASE REQUEST
UE Radio Capability Info Indication	UE RADIO CAPABILITY INFO INDICATION
RRC Inactive Transition Report	RRC INACTIVE TRANSITION REPORT
Overload Start	OVERLOAD START
Overload Stop	OVERLOAD STOP
Secondary RAT Data Usage Report	SECONDARY RAT DATA USAGE REPORT
Uplink RIM Information Transfer	UPLINK RIM INFORMATION TRANSFER
Downlink RIM Information Transfer	DOWNLINK RIM INFORMATION TRANSFER
Retrieve UE Information	RETRIEVE UE INFORMATION
UE Information Transfer	UE INFORMATION TRANSFER
RAN CP Relocation Indication	RAN CP RELOCATION INDICATION
Connection Establishment Indication	CONNECTION ESTABLISHMENT INDICATION
AMF CP Relocation Indication	AMF CP RELOCATION INDICATION
Handover Success	HANDOVER SUCCESS
Uplink RAN Early Status Transfer	UPLINK RAN EARLY STATUS TRANSFER
Downlink RAN Early Status Transfer	DOWNLINK RAN EARLY STATUS TRANSFER

NGAP Packet Structure

If you take packet capture (e.g, Wireshark capture) over the interface, you would get the packet structure as below.

Following is SCTP initial setup process captured with Wireshark from Amarisoft Callbox. (a),(b),(c),(d) is the initial setup of SCTP which is explained in this note , the procedure (1)~(13) is the procedure that will be described in this note.

NGAP Establish

This procedure is to establish the signaling connection between gNB and AMF (i.e, the first connection process). This is not UE specific and this will apply to every UE that are connected to the specified AMF. This process is specified in 38.413-8.7.1. The overall procedure is simple two way handshaking as illustrated below.

< 38.413-Figure 8.7.1.2-1: NG setup: successful operation >

For the description of some important IEs in NG SETUP REQUEST and NG SETUP RESPONSE message, refer to 38.413-8.7.1.2. I think it is relatively clearly described in this specification. The IEs with the description as per 38.413 v16.7 is listed as below. Most of these IEs are optional, so you may not see all of these IEs configured in NGAP log.

NGSetupRequest

Configured TAC Indication
UE Retention Information

NGSetupResponse

IAB Supported
Backup AMF Name
GUAMI Type
RAN Node Name
Extended RAN Node Name
NB-IoT Default Paging DRX
RAT Information
Broadcast PLMN Item->NPN Support->NID
PLMN Support Item->NPN Support->NID

In most cases, AMF accept NGSetupRequest from gNB and send NGSetupReponse, but if any of the following IE does not match with what AMF expects, it would refuse the connection.

pLMNIdentity
tAC

NOTE : It seems that different AMF applies a little bit of different rules for accepting the SETUP REQUEST. For example, Amarisoft AMF is checking only on pLMNIdentity but free5GC AMF seems to check both pLMNIdentity and tAC.

Following is the message structure and requirement of NG SETUP REQUEST from 48.413-9.2.6.1

Following is the message structure and requirement of NG SETUP RESPONSE from 48.413-9.2.6.2

Followings are statements from 38.413-8.7.1.2 that are related to processing the information elements in NG SETUP REQUEST message.

If the Configured TAC Indication IE set to "true� is included for a Tracking Area contained in the Supported TA List IE in the NG SETUP REQUEST message, the AMF may take it into account to optimise NG-C signalling towards this NG-RAN node.
If the UE Retention Information IE set to �ues-retained� is included in the NG SETUP REQUEST message, the AMF may accept the proposal to retain the existing UE related contexts and signalling connections by including the UE Retention Information IE set to �ues-retained� in the NG SETUP RESPONSE message.
If the RAN Node Name IE is included in the NG SETUP REQUEST message, the AMF may use this IE as a human readable name of the NG-RAN node. If the Extended RAN Node Name IE is included in the NG SETUP REQUEST message, the AMF may use this IE as a human readable name of the NG-RAN node and shall ignore the RAN Node Name IE if also included.
If the NB-IoT Default Paging DRX IE is included in the NG SETUP REQUEST message, the AMF shall take it into account for paging.
If the RAT Information IE is included in the NG SETUP REQUEST message, the AMF shall handle this information as specified in TS 23.502.
If the NID IE within the NPN Support IE is included within a Broadcast PLMN Item IE in the NG SETUP REQUEST message, the AMF shall consider that the NG-RAN node supports the indicated S-NSSAI(s) for the corresponding tracking area code for the SNPN identified by the PLMN Identity IE and the NID IE.

Followings are statements from 38.413-8.7.1.2 that are related to processing the information elements in NG SETUP RESPONSE message.

If the UE Retention Information IE set to �ues-retained� is included in the NG SETUP REQUEST message, the AMF may accept the proposal to retain the existing UE related contexts and signalling connections by including the UE Retention Information IE set to �ues-retained� in the NG SETUP RESPONSE message.
If the AMF supports IAB, the AMF shall include the IAB Supported IE in the NG SETUP RESPONSE message.
The AMF shall include the Backup AMF Name IE, if available, in the Served GUAMI List IE in the NG SETUP RESPONSE message. The NG-RAN node shall, if supported, consider the AMF as indicated by the Backup AMF Name IE when performing AMF reselection, as specified in TS 23.501.
If the GUAMI Type IE is included in the NG SETUP RESPONSE message, the NG-RAN node shall store the received value and use it for further AMF selection as defined in TS 23.501.
If the AMF Name IE is included in the NG SETUP RESPONSE message, the NG-RAN node may use this IE as a human readable name of the AMF. If the Extended AMF Name IE is included in the NG SETUP RESPONSE message, the NG-RAN node may use this IE as a human readable name of the AMF and shall ignore the AMF Name IE if also included.
If the NID IE within the NPN Support IE is included within a PLMN Support Item IE in the NG SETUP RESPONSE message, the NG-RAN node shall consider that the AMF supports the SNPN identified by the PLMN Identity IE and the NID IE.

(1) NG Setup Request

Internet Protocol Version 4, Src: 10.0.0.185, Dst: 10.0.0.162

0100 .... = Version: 4

.... 0101 = Header Length: 20 bytes (5)

Differentiated Services Field: 0x02 (DSCP: CS0, ECN: ECT(0))

0000 00.. = Differentiated Services Codepoint: Default (0)

.... ..10 = Explicit Congestion Notification: ECN-Capable Transport codepoint '10' (2)

Total Length: 108

Identification: 0x0001 (1)

Flags: 0x40, Don't fragment

0... .... = Reserved bit: Not set

.1.. .... = Don't fragment: Set

..0. .... = More fragments: Not set

Fragment Offset: 0

Time to Live: 64

Protocol: SCTP (132)

Header Checksum: 0x24b1 [validation disabled]

[Header checksum status: Unverified]

Source Address: 10.0.0.185

Destination Address: 10.0.0.162

Stream Control Transmission Protocol, Src Port: 48041 (48041), Dst Port: 38412 (38412)

Source port: 48041

Destination port: 38412

Verification tag: 0x790ad620

[Association index: 65535]

Checksum: 0x3dba6023 [unverified]

[Checksum Status: Unverified]

DATA chunk(ordered, complete segment, TSN: 3757580128, SID: 0, SSN: 0, PPID: 60,

payload length: 58 bytes)

Chunk type: DATA (0)

0... .... = Bit: Stop processing of the packet

.0.. .... = Bit: Do not report

Chunk flags: 0x03

.... 0... = I-Bit: Possibly delay SACK

.... .0.. = U-Bit: Ordered delivery

.... ..1. = B-Bit: First segment

.... ...1 = E-Bit: Last segment

Chunk length: 74

Transmission sequence number: 3757580128

[This chunk is acked in frame: 138]

[The RTT to SACK was: 0.000032008 seconds]

Stream identifier: 0x0000

Stream sequence number: 0

Payload protocol identifier: NGAP (60)

Chunk padding: 0000

NG Application Protocol

NGAP-PDU: initiatingMessage (0)

initiatingMessage

procedureCode: id-NGSetup (21)

criticality: reject (0)

value

NGSetupRequest

protocolIEs: 4 items

Item 0: id-GlobalRANNodeID

ProtocolIE-Field

id: id-GlobalRANNodeID (27)

criticality: reject (0)

value

GlobalRANNodeID: globalGNB-ID (0)

globalGNB-ID

pLMNIdentity: 00f110

Mobile Country Code (MCC): Unknown (1)

Mobile Network Code (MNC): Unknown (01)

gNB-ID: gNB-ID (0)

gNB-ID: 00123450 [bit length 28, 4 LSB pad bits,

....]

Item 1: id-RANNodeName

ProtocolIE-Field

id: id-RANNodeName (82)

criticality: ignore (1)

value

RANNodeName: gnb0012345

Item 2: id-SupportedTAList

ProtocolIE-Field

id: id-SupportedTAList (102)

criticality: reject (0)

value

SupportedTAList: 1 item

Item 0

SupportedTAItem

tAC: 100 (0x000064)

broadcastPLMNList: 1 item

Item 0

BroadcastPLMNItem

pLMNIdentity: 00f110

Mobile Country Code (MCC):

Unknown (1)

Mobile Network Code (MNC):

Unknown (01)

tAISliceSupportList: 1 item

Item 0

SliceSupportItem

s-NSSAI

sST: 01

Item 3: id-DefaultPagingDRX

ProtocolIE-Field

id: id-DefaultPagingDRX (21)

criticality: ignore (1)

value

PagingDRX: v128 (2)

(2) NG Setup Response

Internet Protocol Version 4, Src: 10.0.0.162, Dst: 10.0.0.185

0100 .... = Version: 4

.... 0101 = Header Length: 20 bytes (5)

Differentiated Services Field: 0x02 (DSCP: CS0, ECN: ECT(0))

0000 00.. = Differentiated Services Codepoint: Default (0)

.... ..10 = Explicit Congestion Notification: ECN-Capable Transport codepoint '10' (2)

Total Length: 140

Identification: 0xadd1 (44497)

Flags: 0x40, Don't fragment

0... .... = Reserved bit: Not set

.1.. .... = Don't fragment: Set

..0. .... = More fragments: Not set

Fragment Offset: 0

Time to Live: 64

Protocol: SCTP (132)

Header Checksum: 0x76c0 [validation disabled]

[Header checksum status: Unverified]

Source Address: 10.0.0.162

Destination Address: 10.0.0.185

Stream Control Transmission Protocol, Src Port: 38412 (38412), Dst Port: 48041 (48041)

Source port: 38412

Destination port: 48041

Verification tag: 0x8d10a6cf

[Association index: 65535]

Checksum: 0x5a3ac41a [unverified]

[Checksum Status: Unverified]

DATA chunk(ordered, complete segment, TSN: 4169966867, SID: 0, SSN: 0, PPID: 60,

payload length: 89 bytes)

Chunk type: DATA (0)

0... .... = Bit: Stop processing of the packet

.0.. .... = Bit: Do not report

Chunk flags: 0x03

.... 0... = I-Bit: Possibly delay SACK

.... .0.. = U-Bit: Ordered delivery

.... ..1. = B-Bit: First segment

.... ...1 = E-Bit: Last segment

Chunk length: 105

Transmission sequence number: 4169966867

[This chunk is acked in frame: 140]

[The RTT to SACK was: 0.004556150 seconds]

Stream identifier: 0x0000

Stream sequence number: 0

Payload protocol identifier: NGAP (60)

Chunk padding: 000000

NG Application Protocol

NGAP-PDU: successfulOutcome (1)

successfulOutcome

procedureCode: id-NGSetup (21)

criticality: reject (0)

value

NGSetupResponse

protocolIEs: 4 items

Item 0: id-AMFName

ProtocolIE-Field

id: id-AMFName (1)

criticality: reject (0)

value

AMFName: amarisoft.amf.5gc.mnc001.mcc001.3gppnetwork.org

Item 1: id-ServedGUAMIList

ProtocolIE-Field

id: id-ServedGUAMIList (96)

criticality: reject (0)

value

ServedGUAMIList: 1 item

Item 0

ServedGUAMIItem

gUAMI

pLMNIdentity: 00f110

Mobile Country Code (MCC): Unknown (1)

Mobile Network Code (MNC): Unknown (01)

aMFRegionID: 80 [bit length 8,

1000 0000 decimal value 128]

aMFSetID: 0100 [bit length 10,

6 LSB pad bits, 0000 0001 00.. ....

decimal value 4]

aMFPointer: 04 [bit length 6, 2 LSB pad bits,

0000 01.. decimal value 1]

Item 2: id-RelativeAMFCapacity

ProtocolIE-Field

id: id-RelativeAMFCapacity (86)

criticality: ignore (1)

value

RelativeAMFCapacity: 50

Item 3: id-PLMNSupportList

ProtocolIE-Field

id: id-PLMNSupportList (80)

criticality: reject (0)

value

PLMNSupportList: 1 item

Item 0

PLMNSupportItem

pLMNIdentity: 00f110

Mobile Country Code (MCC): Unknown (1)

Mobile Network Code (MNC): Unknown (01)

sliceSupportList: 1 item

Item 0

SliceSupportItem

s-NSSAI

sST: 01

NR SA Registration

The Initial UE Message procedure is used when the NG-RAN node has received from the radio interface the first uplink NAS message to be forwarded to an AMF.

< 38.413-Figure 8.6.1.2-1: Initial UE message >

Following is from 38.413 - 9.2.5.1 about the message structure and requirement for INITIAL UE MESSAGE.

Followings are statements from 38.413-8.6.1.2 that are related to processing the information elements in this message.

The NG-RAN node initiates the procedure by sending an INITIAL UE MESSAGE message to the AMF. The NG-RAN node shall allocate a unique RAN UE NGAP ID to be used for the UE and the NG-RAN node shall include this identity in the INITIAL UE MESSAGE message.
The NAS-PDU IE contains a UE � AMF message that is transferred without interpretation in the NG-RAN node.
In case of network sharing, the selected PLMN is indicated by the PLMN Identity IE within the TAI IE included in the INITIAL UE MESSAGE message.
When the NG-RAN node has received from the radio interface the 5G-S-TMSI IE, it shall include it in the INITIAL UE MESSAGE message.
If the AMF Set ID IE is included in the INITIAL UE MESSAGE message this indicates that the message is a rerouted message and the AMF shall, if supported, use the IE as described in TS 23.502.
If the UE Context Request IE is included in the INITIAL UE MESSAGE message the AMF shall trigger an Initial Context Setup procedure towards the NG-RAN node.
If the Allowed NSSAI IE is included in the INITIAL UE MESSAGE message the AMF shall use the IE as defined in TS 23.502.
If the Source to Target AMF Information Reroute IE is included in the INITIAL UE MESSAGE message the AMF shall use the IE as defined in TS 23.502.
If the IAB Node Indication IE is included in the INITIAL UE MESSAGE message, the AMF shall consider that the message is related to an IAB node.
If the CE-mode-B Support Indicator IE is included in the INITIAL UE MESSAGE message and set to "supported", the AMF shall, if supported, use the extended NAS timer settings for the UE as specified in TS 23.501.
If the LTE-M indication IE is included in the INITIAL UE MESSAGE message the AMF shall, if supported, use it according to TS 23.501.
If the EDT Session IE set to "true" is included in the INITIAL UE MESSAGE message and the NG-RAN node is an ngeNB,the AMF shall, if supported, consider that the message has been received as a result of an EDT session initiated by the UE.
If PNI-NPN related information within the NPN Access Information IE is received in the INITIAL UE MESSAGE message, the AMF shall, if supported, consider that the included information is associated to the cell via which the UE has sent the first NAS message, and to the PLMN Identity which is indicated within the TAI IE, and use the included information as specified in TS 23.501.
In case of network sharing for SNPNs, the selected SNPN is indicated within the User Location Information IE included in the INITIAL UE MESSAGE message by the PLMN Identity IE within the TAI IE and the NID IE.

(3) InitialUEMessage

Internet Protocol Version 4, Src: 10.0.0.185, Dst: 10.0.0.162

0100 .... = Version: 4

.... 0101 = Header Length: 20 bytes (5)

Differentiated Services Field: 0x02 (DSCP: CS0, ECN: ECT(0))

0000 00.. = Differentiated Services Codepoint: Default (0)

.... ..10 = Explicit Congestion Notification: ECN-Capable Transport codepoint '10' (2)

Total Length: 188

Identification: 0x0009 (9)

Flags: 0x40, Don't fragment

0... .... = Reserved bit: Not set

.1.. .... = Don't fragment: Set

..0. .... = More fragments: Not set

Fragment Offset: 0

Time to Live: 64

Protocol: SCTP (132)

Header Checksum: 0x2459 [validation disabled]

[Header checksum status: Unverified]

Source Address: 10.0.0.185

Destination Address: 10.0.0.162

Stream Control Transmission Protocol, Src Port: 48041 (48041), Dst Port: 38412 (38412)

Source port: 48041

Destination port: 38412

Verification tag: 0x790ad620

[Association index: 65535]

Checksum: 0xdd43ee10 [unverified]

[Checksum Status: Unverified]

DATA chunk(ordered, complete segment, TSN: 3757580129, SID: 1, SSN: 0, PPID: 60,

payload length: 137 bytes)

Chunk type: DATA (0)

0... .... = Bit: Stop processing of the packet

.0.. .... = Bit: Do not report

Chunk flags: 0x03

.... 0... = I-Bit: Possibly delay SACK

.... .0.. = U-Bit: Ordered delivery

.... ..1. = B-Bit: First segment

.... ...1 = E-Bit: Last segment

Chunk length: 153

Transmission sequence number: 3757580129

[This chunk is acked in frame: 886]

[The RTT to SACK was: 0.000119970 seconds]

Stream identifier: 0x0001

Stream sequence number: 0

Payload protocol identifier: NGAP (60)

Chunk padding: 000000

NG Application Protocol

NGAP-PDU: initiatingMessage (0)

initiatingMessage

procedureCode: id-InitialUEMessage (15)

criticality: ignore (1)

value

InitialUEMessage

protocolIEs: 5 items

Item 0: id-RAN-UE-NGAP-ID

ProtocolIE-Field

id: id-RAN-UE-NGAP-ID (85)

criticality: reject (0)

value

RAN-UE-NGAP-ID: 1

Item 1: id-NAS-PDU

ProtocolIE-Field

id: id-NAS-PDU (38)

criticality: reject (0)

value

NAS-PDU: 7e017d335df8077e004109000bf200f110...�

Non-Access-Stratum 5GS (NAS)PDU

Security protected NAS 5GS message

Extended protocol discriminator:

5G mobility management messages (126)

0000 .... = Spare Half Octet: 0

.... 0001 = Security header type:

Integrity protected (1)

Message authentication code: 0x7d335df8

Sequence number: 7

Plain NAS 5GS Message

Extended protocol discriminator:

5G mobility management messages (126)

0000 .... = Spare Half Octet: 0

.... 0000 = Security header type:

Plain NAS message, not security protected (0)

Message type: Registration request (0x41)

5GS registration type

.... 1... = Follow-On Request bit (FOR):

Follow-on request pending

.... .001 = 5GS registration type:

initial registration (1)

NAS key set identifier

0... .... = Type of security context flag(TSC):

Native security context (for KSIAMF)

.000 .... = NAS key set identifier: 0

5GS mobile identity

Length: 11

.... 0... = Odd/even indication:

Even number of identity digits

.... .010 = Type of identity: 5G-GUTI (2)

Mobile Country Code (MCC): Unknown (1)

Mobile Network Code (MNC): Unknown (01)

AMF Region ID: 128

0000 0001 00.. .... = AMF Set ID: 4

..00 0001 = AMF Pointer: 1

5G-TMSI: 3776478432 (0xe1187ce0)

UE security capability

Element ID: 0x2e

Length: 4

1... .... = 5G-EA0: Supported

.1.. .... = 128-5G-EA1: Supported

..1. .... = 128-5G-EA2: Supported

...1 .... = 128-5G-EA3: Supported

.... 0... = 5G-EA4: Not supported

.... .0.. = 5G-EA5: Not supported

.... ..0. = 5G-EA6: Not supported

.... ...0 = 5G-EA7: Not supported

0... .... = 5G-IA0: Not supported

.1.. .... = 128-5G-IA1: Supported

..1. .... = 128-5G-IA2: Supported

...1 .... = 128-5G-IA3: Supported

.... 0... = 5G-IA4: Not supported

.... .0.. = 5G-IA5: Not supported

.... ..0. = 5G-IA6: Not supported

.... ...0 = 5G-IA7: Not supported

1... .... = EEA0: Supported

.1.. .... = 128-EEA1: Supported

..1. .... = 128-EEA2: Supported

...1 .... = 128-EEA3: Supported

.... 0... = EEA4: Not supported

.... .0.. = EEA5: Not supported

.... ..0. = EEA6: Not supported

.... ...0 = EEA7: Not supported

0... .... = EIA0: Not supported

.1.. .... = 128-EIA1: Supported

..1. .... = 128-EIA2: Supported

...1 .... = 128-EIA3: Supported

.... 0... = EIA4: Not supported

.... .0.. = EIA5: Not supported

.... ..0. = EIA6: Not supported

.... ...0 = EIA7: Not supported

NAS message container

Element ID: 0x71

Length: 56

Non-Access-Stratum 5GS (NAS)PDU

Plain NAS 5GS Message

Extended protocol discriminator:

5G mobility management messages (126)

0000 .... = Spare Half Octet: 0

.... 0000 = Security header type:

Plain NAS message,

not security protected (0)

Message type:

Registration request (0x41)

5GS registration type

.... 1... = Follow-On Request bit

(FOR): Follow-on request pending

.... .001 = 5GS registration type:

initial registration (1)

NAS key set identifier

0... .... =

Type of security context flag(TSC)

: Native security context

(for KSIAMF)

.000 ....=NAS key set identifier:0

5GS mobile identity

Length: 11

.... 0... = Odd/even indication:

Even number of identity digits

.... .010 = Type of identity:

5G-GUTI (2)

Mobile Country Code (MCC):

Unknown (1)

Mobile Network Code (MNC):

Unknown (01)

AMF Region ID: 128

0000 0001 00.. .... = AMF Set ID: 4

..00 0001 = AMF Pointer: 1

5G-TMSI: 3776478432 (0xe1187ce0)

5GMM capability

Element ID: 0x10

Length: 1

0... .... = Spare: 0

.0.. .... = Spare: 0

..0. .... = Spare: 0

...0 .... = Spare: 0

.... 0... = Spare: 0

.... .0.. = LTE PositioningProtocol

(LPP) capability: Not Requested

.... ..1. = HO attach: Supported

.... ...1 = S1 mode: Requested

UE security capability

Element ID: 0x2e

Length: 4

1... .... = 5G-EA0: Supported

.1.. .... = 128-5G-EA1: Supported

..1. .... = 128-5G-EA2: Supported

...1 .... = 128-5G-EA3: Supported

.... 0... = 5G-EA4: Not supported

.... .0.. = 5G-EA5: Not supported

.... ..0. = 5G-EA6: Not supported

.... ...0 = 5G-EA7: Not supported

0... .... = 5G-IA0: Not supported

.1.. .... = 128-5G-IA1: Supported

..1. .... = 128-5G-IA2: Supported

...1 .... = 128-5G-IA3: Supported

.... 0... = 5G-IA4: Not supported

.... .0.. = 5G-IA5: Not supported

.... ..0. = 5G-IA6: Not supported

.... ...0 = 5G-IA7: Not supported

1... .... = EEA0: Supported

.1.. .... = 128-EEA1: Supported

..1. .... = 128-EEA2: Supported

...1 .... = 128-EEA3: Supported

.... 0... = EEA4: Not supported

.... .0.. = EEA5: Not supported

.... ..0. = EEA6: Not supported

.... ...0 = EEA7: Not supported

0... .... = EIA0: Not supported

.1.. .... = 128-EIA1: Supported

..1. .... = 128-EIA2: Supported

...1 .... = 128-EIA3: Supported

.... 0... = EIA4: Not supported

.... .0.. = EIA5: Not supported

.... ..0. = EIA6: Not supported

.... ...0 = EIA7: Not supported

NSSAI - Requested NSSAI

Element ID: 0x2f

Length: 2

S-NSSAI 1

Length: 1

Slice/service type (SST): 1

5GS tracking area identity -

Last visited registered TAI

Element ID: 0x52

Mobile Country Code (MCC):

Unknown (1)

Mobile Network Code (MNC):

Unknown (01)

TAC: 100

UE network capability

Element ID: 0x17

Length: 7

1... .... = EEA0: Supported

.1.. .... = 128-EEA1: Supported

..1. .... = 128-EEA2: Supported

...1 .... = 128-EEA3: Supported

.... 0... = EEA4: Not supported

.... .0.. = EEA5: Not supported

.... ..0. = EEA6: Not supported

.... ...0 = EEA7: Not supported

0... .... = EIA0: Not supported

.1.. .... = 128-EIA1: Supported

..1. .... = 128-EIA2: Supported

...1 .... = 128-EIA3: Supported

.... 0... = EIA4: Not supported

.... .0.. = EIA5: Not supported

.... ..0. = EIA6: Not supported

.... ...0 = EIA7: Not supported

1... .... = UEA0: Supported

.1.. .... = UEA1: Supported

..0. .... = UEA2: Not supported

...0 .... = UEA3: Not supported

.... 0... = UEA4: Not supported

.... .0.. = UEA5: Not supported

.... ..0. = UEA6: Not supported

.... ...0 = UEA7: Not supported

0... .... = UCS2 support (UCS2):

The UE has a preference

for the default alphabet

.1.. .... = UIA1: Supported

..0. .... = UIA2: Not supported

...0 .... = UIA3: Not supported

.... 0... = UIA4: Not supported

.... .0.. = UIA5: Not supported

.... ..0. = UIA6: Not supported

.... ...0 = UIA7: Not supported

0... .... = ProSe direct discovery:

Not supported

.0.. .... = ProSe: Not supported

..0. .... = H.245 After SRVCC

Handover: Not supported

...1 .... = Access class control

for CSFB: Supported

.... 1... = LTE Positioning

Protocol: Supported

.... .0.. = Location services (LCS)

notification mechanisms:

Not supported

.... ..0. = SRVCC from E-UTRAN to

cdma2000 1xCS: Not supported

.... ...1 = Notification procedure:

Supported

1... .... = Extended protocol

configuration options: Supported

.0.. .... = Header compression

for control plane CIoT EPS

optimization: Not supported

..0. .... = EMM-REGISTERED w/o

PDN connectivity: Not supported

...0 .... = S1-U data transfer:

Not supported

.... 0... = User plane CIoT EPS

optimization: Not supported

.... .0.. = Control plane CIoT EPS

optimization: Not supported

.... ..0. = ProSe UE-to-network

relay: Not supported

.... ...0 = ProSe direct

communication: Not supported

1... .... = Signalling for a max number of 15 EPS bearer

contexts: Supported

.0.. .... = Service gap control:

Not supported

..1. .... = N1 mode: Supported

...1 .... = Dual connectivity

with NR: Supported

.... 0... = Control plane data

backoff: Not supported

.... .0.. = Restriction on use of

enhanced coverage:Not supported

.... ..0. = V2X communication over

PC5: Not supported

.... ...0 = Multiple DRB:

Not supported

UE's usage setting

Element ID: 0x18

Length: 1

.... 0... = Spare: 0

.... .0.. = Spare: 0

.... ..0. = Spare: 0

.... ...1 = UE's usage setting:

Data centric

LADN indication

Element ID: 0x74

Length: 0

Network slicing indication

1001 .... = Element ID: 0x9-

.... 0... = Spare: 0

.... .0.. = Spare: 0

.... ..0. = Default configuredNSSAI

indication (DCNI): Requested

NSSAI not created from default

configured NSSAI

.... ...0 = Network slicing

subscription change indication

(NSSCI): Not Changed

5GS update type

Element ID: 0x53

Length: 1

.... 0... = Spare: 0

.... .0.. = Spare: 0

.... ..0. = NG-RAN Radio Capability

Update (NG-RAN-RCU): Not Needed

.... ...1 = SMS requested: SMS over

NAS supported

Item 2: id-UserLocationInformation

ProtocolIE-Field

id: id-UserLocationInformation (121)

criticality: reject (0)

value

UserLocationInformation: userLocationInformationNR (1)

userLocationInformationNR

nR-CGI

pLMNIdentity: 00f110

Mobile Country Code (MCC): Unknown (1)

Mobile Network Code (MNC): Unknown (01)

nRCellIdentity: 0x0001234501

tAI

pLMNIdentity: 00f110

Mobile Country Code (MCC): Unknown (1)

Mobile Network Code (MNC): Unknown (01)

tAC: 100 (0x000064)

Item 3: id-RRCEstablishmentCause

ProtocolIE-Field

id: id-RRCEstablishmentCause (90)

criticality: ignore (1)

value

RRCEstablishmentCause: mo-Signalling (3)

Item 4: id-UEContextRequest

ProtocolIE-Field

id: id-UEContextRequest (112)

criticality: ignore (1)

value

UEContextRequest: requested (0)

(4) DownlinkNasTransport

Internet Protocol Version 4, Src: 10.0.0.162, Dst: 10.0.0.185

0100 .... = Version: 4

.... 0101 = Header Length: 20 bytes (5)

Differentiated Services Field: 0x02 (DSCP: CS0, ECN: ECT(0))

0000 00.. = Differentiated Services Codepoint: Default (0)

.... ..10 = Explicit Congestion Notification: ECN-Capable Transport codepoint '10' (2)

Total Length: 116

Identification: 0xadd8 (44504)

Flags: 0x40, Don't fragment

0... .... = Reserved bit: Not set

.1.. .... = Don't fragment: Set

..0. .... = More fragments: Not set

Fragment Offset: 0

Time to Live: 64

Protocol: SCTP (132)

Header Checksum: 0x76d1 [validation disabled]

[Header checksum status: Unverified]

Source Address: 10.0.0.162

Destination Address: 10.0.0.185

Stream Control Transmission Protocol, Src Port: 38412 (38412), Dst Port: 48041 (48041)

Source port: 38412

Destination port: 48041

Verification tag: 0x8d10a6cf

[Association index: 65535]

Checksum: 0xe5d8cd9f [unverified]

[Checksum Status: Unverified]

SACK chunk (Cumulative TSN: 3757580129, a_rwnd: 106496, gaps: 0, duplicate TSNs: 0)

Chunk type: SACK (3)

0... .... = Bit: Stop processing of the packet

.0.. .... = Bit: Do not report

Chunk flags: 0x00

.... ...0 = Nounce sum: 0

Chunk length: 16

Cumulative TSN ACK: 3757580129

[Acknowledges TSN: 3757580129]

[Acknowledges TSN in frame: 885]

[The RTT since DATA was: 0.000119970 seconds]

Advertised receiver window credit (a_rwnd): 106496

Number of gap acknowledgement blocks: 0

Number of duplicated TSNs: 0

DATA chunk(ordered, complete segment, TSN: 4169966868, SID: 1, SSN: 0, PPID: 60,

payload length: 50 bytes)

Chunk type: DATA (0)

0... .... = Bit: Stop processing of the packet

.0.. .... = Bit: Do not report

Chunk flags: 0x03

.... 0... = I-Bit: Possibly delay SACK

.... .0.. = U-Bit: Ordered delivery

.... ..1. = B-Bit: First segment

.... ...1 = E-Bit: Last segment

Chunk length: 66

Transmission sequence number: 4169966868

[This chunk is acked in frame: 893]

[The RTT to SACK was: 0.046143403 seconds]

Stream identifier: 0x0001

Stream sequence number: 0

Payload protocol identifier: NGAP (60)

Chunk padding: 0000

NG Application Protocol

NGAP-PDU: initiatingMessage (0)

initiatingMessage

procedureCode: id-DownlinkNASTransport (4)

criticality: ignore (1)

value

DownlinkNASTransport

protocolIEs: 3 items

Item 0: id-AMF-UE-NGAP-ID

ProtocolIE-Field

id: id-AMF-UE-NGAP-ID (10)

criticality: reject (0)

value

AMF-UE-NGAP-ID: 102

Item 1: id-RAN-UE-NGAP-ID

ProtocolIE-Field

id: id-RAN-UE-NGAP-ID (85)

criticality: reject (0)

value

RAN-UE-NGAP-ID: 1

Item 2: id-NAS-PDU

ProtocolIE-Field

id: id-NAS-PDU (38)

criticality: reject (0)

value

NAS-PDU: 7e034cd87aa9067e005d020004f070f070e157021904f070c040

Non-Access-Stratum 5GS (NAS)PDU

Security protected NAS 5GS message

Extended protocol discriminator:

5G mobility management messages (126)

0000 .... = Spare Half Octet: 0

.... 0011 = Security header type:

Integrity protected

with new 5GS security context (3)

Message authentication code: 0x4cd87aa9

Sequence number: 6

Plain NAS 5GS Message

Extended protocol discriminator:

5G mobility management messages (126)

0000 .... = Spare Half Octet: 0

.... 0000 = Security header type:

Plain NAS message, not security protected (0)

Message type: Security mode command (0x5d)

NAS security algorithms

0000 .... = Type of ciphering algorithm:

5G-EA0 (null ciphering algorithm) (0)

.... 0010 = Type of integrity protection

algorithm: 128-5G-IA2 (2)

0000 .... = Spare Half Octet: 0

NAS key set identifier - ngKSI

.... 0... = Type of security context flag(TSC):

Native security context (for KSIAMF)

.... .000 = NAS key set identifier: 0

UE security capability -

Replayed UE security capabilities

Length: 4

1... .... = 5G-EA0: Supported

.1.. .... = 128-5G-EA1: Supported

..1. .... = 128-5G-EA2: Supported

...1 .... = 128-5G-EA3: Supported

.... 0... = 5G-EA4: Not supported

.... .0.. = 5G-EA5: Not supported

.... ..0. = 5G-EA6: Not supported

.... ...0 = 5G-EA7: Not supported

0... .... = 5G-IA0: Not supported

.1.. .... = 128-5G-IA1: Supported

..1. .... = 128-5G-IA2: Supported

...1 .... = 128-5G-IA3: Supported

.... 0... = 5G-IA4: Not supported

.... .0.. = 5G-IA5: Not supported

.... ..0. = 5G-IA6: Not supported

.... ...0 = 5G-IA7: Not supported

1... .... = EEA0: Supported

.1.. .... = 128-EEA1: Supported

..1. .... = 128-EEA2: Supported

...1 .... = 128-EEA3: Supported

.... 0... = EEA4: Not supported

.... .0.. = EEA5: Not supported

.... ..0. = EEA6: Not supported

.... ...0 = EEA7: Not supported

0... .... = EIA0: Not supported

.1.. .... = 128-EIA1: Supported

..1. .... = 128-EIA2: Supported

...1 .... = 128-EIA3: Supported

.... 0... = EIA4: Not supported

.... .0.. = EIA5: Not supported

.... ..0. = EIA6: Not supported

.... ...0 = EIA7: Not supported

IMEISV request

1110 .... = Element ID: 0xe-

.... 0... = Spare bit(s): 0x00

.... .001 = IMEISV request: IMEISV requested(1)

NAS security algorithms - Selected EPS NAS

security algorithms

Element ID: 0x57

0... .... = Spare bit(s): 0x00

.000 .... = Type of ciphering algorithm:

EPS encryption algorithm EEA0

.... 0... = Spare bit(s): 0x00

.... .010 = Type of integrity protection

algorithm: EPS integrity algorithm 128-EIA2

UE security capability -

Replayed S1 UE security capabilities

Element ID: 0x19

Length: 4

1... .... = EEA0: Supported

.1.. .... = 128-EEA1: Supported

..1. .... = 128-EEA2: Supported

...1 .... = 128-EEA3: Supported

.... 0... = EEA4: Not supported

.... .0.. = EEA5: Not supported

.... ..0. = EEA6: Not supported

.... ...0 = EEA7: Not supported

0... .... = EIA0: Not supported

.1.. .... = 128-EIA1: Supported

..1. .... = 128-EIA2: Supported

...1 .... = 128-EIA3: Supported

.... 0... = EIA4: Not supported

.... .0.. = EIA5: Not supported

.... ..0. = EIA6: Not supported

.... ...0 = EIA7: Not supported

1... .... = UEA0: Supported

.1.. .... = UEA1: Supported

..0. .... = UEA2: Not supported

...0 .... = UEA3: Not supported

.... 0... = UEA4: Not supported

.... .0.. = UEA5: Not supported

.... ..0. = UEA6: Not supported

.... ...0 = UEA7: Not supported

0... .... = Spare bit(s): 0x0

.1.. .... = UIA1: Supported

..0. .... = UIA2: Not supported

...0 .... = UIA3: Not supported

.... 0... = UIA4: Not supported

.... .0.. = UIA5: Not supported

.... ..0. = UIA6: Not supported

.... ...0 = UIA7: Not supported

(5) UplinkNasTransport

Internet Protocol Version 4, Src: 10.0.0.185, Dst: 10.0.0.162

0100 .... = Version: 4

.... 0101 = Header Length: 20 bytes (5)

Differentiated Services Field: 0x02 (DSCP: CS0, ECN: ECT(0))

0000 00.. = Differentiated Services Codepoint: Default (0)

.... ..10 = Explicit Congestion Notification: ECN-Capable Transport codepoint '10' (2)

Total Length: 132

Identification: 0x000a (10)

Flags: 0x40, Don't fragment

0... .... = Reserved bit: Not set

.1.. .... = Don't fragment: Set

..0. .... = More fragments: Not set

Fragment Offset: 0

Time to Live: 64

Protocol: SCTP (132)

Header Checksum: 0x2490 [validation disabled]

[Header checksum status: Unverified]

Source Address: 10.0.0.185

Destination Address: 10.0.0.162

Stream Control Transmission Protocol, Src Port: 48041 (48041), Dst Port: 38412 (38412)

Source port: 48041

Destination port: 38412

Verification tag: 0x790ad620

[Association index: 65535]

Checksum: 0xb39a1aad [unverified]

[Checksum Status: Unverified]

SACK chunk (Cumulative TSN: 4169966868, a_rwnd: 106496, gaps: 0, duplicate TSNs: 0)

Chunk type: SACK (3)

0... .... = Bit: Stop processing of the packet

.0.. .... = Bit: Do not report

Chunk flags: 0x00

.... ...0 = Nounce sum: 0

Chunk length: 16

Cumulative TSN ACK: 4169966868

[Acknowledges TSN: 4169966868]

[Acknowledges TSN in frame: 886]

[The RTT since DATA was: 0.046143403 seconds]

Advertised receiver window credit (a_rwnd): 106496

Number of gap acknowledgement blocks: 0

Number of duplicated TSNs: 0

DATA chunk(ordered, complete segment, TSN: 3757580130, SID: 1, SSN: 1, PPID: 60,

payload length: 65 bytes)

Chunk type: DATA (0)

0... .... = Bit: Stop processing of the packet

.0.. .... = Bit: Do not report

Chunk flags: 0x03

.... 0... = I-Bit: Possibly delay SACK

.... .0.. = U-Bit: Ordered delivery

.... ..1. = B-Bit: First segment

.... ...1 = E-Bit: Last segment

Chunk length: 81

Transmission sequence number: 3757580130

[This chunk is acked in frame: 894]

[The RTT to SACK was: 0.000370058 seconds]

Stream identifier: 0x0001

Stream sequence number: 1

Payload protocol identifier: NGAP (60)

Chunk padding: 000000

NG Application Protocol

NGAP-PDU: initiatingMessage (0)

initiatingMessage

procedureCode: id-UplinkNASTransport (46)

criticality: ignore (1)

value

UplinkNASTransport

protocolIEs: 4 items

Item 0: id-AMF-UE-NGAP-ID

ProtocolIE-Field

id: id-AMF-UE-NGAP-ID (10)

criticality: reject (0)

value

AMF-UE-NGAP-ID: 102

Item 1: id-RAN-UE-NGAP-ID

ProtocolIE-Field

id: id-RAN-UE-NGAP-ID (85)

criticality: reject (0)

value

RAN-UE-NGAP-ID: 1

Item 2: id-NAS-PDU

ProtocolIE-Field

id: id-NAS-PDU (38)

criticality: reject (0)

value

NAS-PDU: 7e04d3e72791087e005e7700098596500765532619f3

Non-Access-Stratum 5GS (NAS)PDU

Security protected NAS 5GS message

Extended protocol discriminator:

5G mobility management messages (126)

0000 .... = Spare Half Octet: 0

.... 0100 = Security header type:

Integrity protected and ciphered

with new 5GS security context (4)

Message authentication code: 0xd3e72791

Sequence number: 8

Encrypted data

Item 3: id-UserLocationInformation

ProtocolIE-Field

id: id-UserLocationInformation (121)

criticality: ignore (1)

value

UserLocationInformation: userLocationInformationNR (1)

userLocationInformationNR

nR-CGI

pLMNIdentity: 00f110

Mobile Country Code (MCC): Unknown (1)

Mobile Network Code (MNC): Unknown (01)

nRCellIdentity: 0x0001234501

tAI

pLMNIdentity: 00f110

Mobile Country Code (MCC): Unknown (1)

Mobile Network Code (MNC): Unknown (01)

tAC: 100 (0x000064)

(6) InitialContextSetupRequest

Internet Protocol Version 4, Src: 10.0.0.162, Dst: 10.0.0.185

0100 .... = Version: 4

.... 0101 = Header Length: 20 bytes (5)

Differentiated Services Field: 0x02 (DSCP: CS0, ECN: ECT(0))

0000 00.. = Differentiated Services Codepoint: Default (0)

.... ..10 = Explicit Congestion Notification: ECN-Capable Transport codepoint '10' (2)

Total Length: 216

Identification: 0xadd9 (44505)

Flags: 0x40, Don't fragment

0... .... = Reserved bit: Not set

.1.. .... = Don't fragment: Set

..0. .... = More fragments: Not set

Fragment Offset: 0

Time to Live: 64

Protocol: SCTP (132)

Header Checksum: 0x766c [validation disabled]

[Header checksum status: Unverified]

Source Address: 10.0.0.162

Destination Address: 10.0.0.185

Stream Control Transmission Protocol, Src Port: 38412 (38412), Dst Port: 48041 (48041)

Source port: 38412

Destination port: 48041

Verification tag: 0x8d10a6cf

[Association index: 65535]

Checksum: 0x564117e2 [unverified]

[Checksum Status: Unverified]

SACK chunk (Cumulative TSN: 3757580130, a_rwnd: 106496, gaps: 0, duplicate TSNs: 0)

Chunk type: SACK (3)

0... .... = Bit: Stop processing of the packet

.0.. .... = Bit: Do not report

Chunk flags: 0x00

.... ...0 = Nounce sum: 0

Chunk length: 16

Cumulative TSN ACK: 3757580130

[Acknowledges TSN: 3757580130]

[Acknowledges TSN in frame: 893]

[The RTT since DATA was: 0.000370058 seconds]

Advertised receiver window credit (a_rwnd): 106496

Number of gap acknowledgement blocks: 0

Number of duplicated TSNs: 0

DATA chunk(ordered, complete segment, TSN: 4169966869, SID: 1, SSN: 1, PPID: 60,

payload length: 152 bytes)

Chunk type: DATA (0)

0... .... = Bit: Stop processing of the packet

.0.. .... = Bit: Do not report

Chunk flags: 0x03

.... 0... = I-Bit: Possibly delay SACK

.... .0.. = U-Bit: Ordered delivery

.... ..1. = B-Bit: First segment

.... ...1 = E-Bit: Last segment

Chunk length: 168

Transmission sequence number: 4169966869

[This chunk is acked in frame: 901]

[The RTT to SACK was: 0.131696577 seconds]

Stream identifier: 0x0001

Stream sequence number: 1

Payload protocol identifier: NGAP (60)

NG Application Protocol

NGAP-PDU: initiatingMessage (0)

initiatingMessage

procedureCode: id-InitialContextSetup (14)

criticality: reject (0)

value

InitialContextSetupRequest

protocolIEs: 8 items

Item 0: id-AMF-UE-NGAP-ID

ProtocolIE-Field

id: id-AMF-UE-NGAP-ID (10)

criticality: reject (0)

value

AMF-UE-NGAP-ID: 102

Item 1: id-RAN-UE-NGAP-ID

ProtocolIE-Field

id: id-RAN-UE-NGAP-ID (85)

criticality: reject (0)

value

RAN-UE-NGAP-ID: 1

Item 2: id-GUAMI

ProtocolIE-Field

id: id-GUAMI (28)

criticality: reject (0)

value

GUAMI

pLMNIdentity: 00f110

Mobile Country Code (MCC): Unknown (1)

Mobile Network Code (MNC): Unknown (01)

aMFRegionID: 80 [bit length 8, 1000 0000 decimal value 128]

aMFSetID: 0100 [bit length 10, 6 LSB pad bits,

0000 0001 00.. .... decimal value 4]

aMFPointer: 04 [bit length 6, 2 LSB pad bits,

0000 01.. decimal value 1]

Item 3: id-AllowedNSSAI

ProtocolIE-Field

id: id-AllowedNSSAI (0)

criticality: reject (0)

value

AllowedNSSAI: 1 item

Item 0

AllowedNSSAI-Item

s-NSSAI

sST: 01

Item 4: id-UESecurityCapabilities

ProtocolIE-Field

id: id-UESecurityCapabilities (119)

criticality: reject (0)

value

UESecurityCapabilities

nRencryptionAlgorithms: e000 [bit length 16,

1110 0000 0000 0000 decimal value 57344]

1... .... .... .... = 128-NEA1: Supported

.1.. .... .... .... = 128-NEA2: Supported

..1. .... .... .... = 128-NEA3: Supported

...0 0000 0000 0000 = Reserved: 0x0000

nRintegrityProtectionAlgorithms: e000 [bit length 16,

1110 0000 0000 0000 decimal value 57344]

1... .... .... .... = 128-NIA1: Supported

.1.. .... .... .... = 128-NIA2: Supported

..1. .... .... .... = 128-NIA3: Supported

...0 0000 0000 0000 = Reserved: 0x0000

eUTRAencryptionAlgorithms: e000 [bit length 16,

1110 0000 0000 0000 decimal value 57344]

1... .... .... .... = 128-EEA1: Supported

.1.. .... .... .... = 128-EEA2: Supported

..1. .... .... .... = 128-EEA3: Supported

...0 0000 0000 0000 = Reserved: 0x0000

eUTRAintegrityProtectionAlgorithms: e000 [bit length 16,

1110 0000 0000 0000 decimal value 57344]

1... .... .... .... = 128-EIA1: Supported

.1.. .... .... .... = 128-EIA2: Supported

..1. .... .... .... = 128-EIA3: Supported

...0 0000 0000 0000 = Reserved: 0x0000

Item 5: id-SecurityKey

ProtocolIE-Field

id: id-SecurityKey (94)

criticality: reject (0)

value

SecurityKey: 0cf3d559d8db4b4cb2193a8bbda7... [bit length 256]

Item 6: id-NAS-PDU

ProtocolIE-Field

id: id-NAS-PDU (38)

criticality: ignore (1)

value

NAS-PDU: 7e02989f23dc077e0042010977000bf200f110800101�

Non-Access-Stratum 5GS (NAS)PDU

Security protected NAS 5GS message

Extended protocol discriminator:

5G mobility management messages (126)

0000 .... = Spare Half Octet: 0

.... 0010 = Security header type:

Integrity protected and ciphered (2)

Message authentication code: 0x989f23dc

Sequence number: 7

Encrypted data

Item 7: id-RedirectionVoiceFallback

ProtocolIE-Field

id: id-RedirectionVoiceFallback (146)

criticality: ignore (1)

value

RedirectionVoiceFallback: possible (0)

(7) UERadioCapabilityInformation

This carries Rrc UE capability Information message. This part is not printed in this note since this is more like Rrc Information.

(8) InitialContextSetupRequest

Internet Protocol Version 4, Src: 10.0.0.185, Dst: 10.0.0.162

0100 .... = Version: 4

.... 0101 = Header Length: 20 bytes (5)

Differentiated Services Field: 0x02 (DSCP: CS0, ECN: ECT(0))

0000 00.. = Differentiated Services Codepoint: Default (0)

.... ..10 = Explicit Congestion Notification: ECN-Capable Transport codepoint '10' (2)

Total Length: 68

Identification: 0x000d (13)

Flags: 0x40, Don't fragment

0... .... = Reserved bit: Not set

.1.. .... = Don't fragment: Set

..0. .... = More fragments: Not set

Fragment Offset: 0

Time to Live: 64

Protocol: SCTP (132)

Header Checksum: 0x24cd [validation disabled]

[Header checksum status: Unverified]

Source Address: 10.0.0.185

Destination Address: 10.0.0.162

Stream Control Transmission Protocol, Src Port: 48041 (48041), Dst Port: 38412 (38412)

Source port: 48041

Destination port: 38412

Verification tag: 0x790ad620

[Association index: 65535]

Checksum: 0x2c975cf3 [unverified]

[Checksum Status: Unverified]

DATA chunk(ordered, complete segment, TSN: 3757580133, SID: 1, SSN: 3, PPID: 60,

payload length: 19 bytes)

Chunk type: DATA (0)

0... .... = Bit: Stop processing of the packet

.0.. .... = Bit: Do not report

Chunk flags: 0x03

.... 0... = I-Bit: Possibly delay SACK

.... .0.. = U-Bit: Ordered delivery

.... ..1. = B-Bit: First segment

.... ...1 = E-Bit: Last segment

Chunk length: 35

Transmission sequence number: 3757580133

[This chunk is acked in frame: 907]

[The RTT to SACK was: 0.000376547 seconds]

Stream identifier: 0x0001

Stream sequence number: 3

Payload protocol identifier: NGAP (60)

Chunk padding: 00

NG Application Protocol

NGAP-PDU: successfulOutcome (1)

successfulOutcome

procedureCode: id-InitialContextSetup (14)

criticality: reject (0)

value

InitialContextSetupResponse

protocolIEs: 2 items

Item 0: id-AMF-UE-NGAP-ID

ProtocolIE-Field

id: id-AMF-UE-NGAP-ID (10)

criticality: ignore (1)

value

AMF-UE-NGAP-ID: 102

Item 1: id-RAN-UE-NGAP-ID

ProtocolIE-Field

id: id-RAN-UE-NGAP-ID (85)

criticality: ignore (1)

value

RAN-UE-NGAP-ID: 1

(9) UplinkNASTransport

Internet Protocol Version 4, Src: 10.0.0.185, Dst: 10.0.0.162

0100 .... = Version: 4

.... 0101 = Header Length: 20 bytes (5)

Differentiated Services Field: 0x02 (DSCP: CS0, ECN: ECT(0))

0000 00.. = Differentiated Services Codepoint: Default (0)

.... ..10 = Explicit Congestion Notification: ECN-Capable Transport codepoint '10' (2)

Total Length: 104

Identification: 0x000e (14)

Flags: 0x40, Don't fragment

0... .... = Reserved bit: Not set

.1.. .... = Don't fragment: Set

..0. .... = More fragments: Not set

Fragment Offset: 0

Time to Live: 64

Protocol: SCTP (132)

Header Checksum: 0x24a8 [validation disabled]

[Header checksum status: Unverified]

Source Address: 10.0.0.185

Destination Address: 10.0.0.162

Stream Control Transmission Protocol, Src Port: 48041 (48041), Dst Port: 38412 (38412)

Source port: 48041

Destination port: 38412

Verification tag: 0x790ad620

[Association index: 65535]

Checksum: 0x4643a66d [unverified]

[Checksum Status: Unverified]

DATA chunk(ordered, complete segment, TSN: 3757580134, SID: 1, SSN: 4, PPID: 60,

payload length: 53 bytes)

Chunk type: DATA (0)

0... .... = Bit: Stop processing of the packet

.0.. .... = Bit: Do not report

Chunk flags: 0x03

.... 0... = I-Bit: Possibly delay SACK

.... .0.. = U-Bit: Ordered delivery

.... ..1. = B-Bit: First segment

.... ...1 = E-Bit: Last segment

Chunk length: 69

Transmission sequence number: 3757580134

[This chunk is acked in frame: 907]

[The RTT to SACK was: 0.000018275 seconds]

Stream identifier: 0x0001

Stream sequence number: 4

Payload protocol identifier: NGAP (60)

Chunk padding: 000000

NG Application Protocol

NGAP-PDU: initiatingMessage (0)

initiatingMessage

procedureCode: id-UplinkNASTransport (46)

criticality: ignore (1)

value

UplinkNASTransport

protocolIEs: 4 items

Item 0: id-AMF-UE-NGAP-ID

ProtocolIE-Field

id: id-AMF-UE-NGAP-ID (10)

criticality: reject (0)

value

AMF-UE-NGAP-ID: 102

Item 1: id-RAN-UE-NGAP-ID

ProtocolIE-Field

id: id-RAN-UE-NGAP-ID (85)

criticality: reject (0)

value

RAN-UE-NGAP-ID: 1

Item 2: id-NAS-PDU

ProtocolIE-Field

id: id-NAS-PDU (38)

criticality: reject (0)

value

NAS-PDU: 7e021bc4e845097e0043

Non-Access-Stratum 5GS (NAS)PDU

Security protected NAS 5GS message

Extended protocol discriminator:

5G mobility management messages (126)

0000 .... = Spare Half Octet: 0

.... 0010 = Security header type:

Integrity protected and ciphered (2)

Message authentication code: 0x1bc4e845

Sequence number: 9

Encrypted data

Item 3: id-UserLocationInformation

ProtocolIE-Field

id: id-UserLocationInformation (121)

criticality: ignore (1)

value

UserLocationInformation: userLocationInformationNR (1)

userLocationInformationNR

nR-CGI

pLMNIdentity: 00f110

Mobile Country Code (MCC): Unknown (1)

Mobile Network Code (MNC): Unknown (01)

nRCellIdentity: 0x0001234501

tAI

pLMNIdentity: 00f110

Mobile Country Code (MCC): Unknown (1)

Mobile Network Code (MNC): Unknown (01)

tAC: 100 (0x000064)

(10) DownlinkNASTransport

Internet Protocol Version 4, Src: 10.0.0.162, Dst: 10.0.0.185

0100 .... = Version: 4

.... 0101 = Header Length: 20 bytes (5)

Differentiated Services Field: 0x02 (DSCP: CS0, ECN: ECT(0))

0000 00.. = Differentiated Services Codepoint: Default (0)

.... ..10 = Explicit Congestion Notification: ECN-Capable Transport codepoint '10' (2)

Total Length: 124

Identification: 0xaddc (44508)

Flags: 0x40, Don't fragment

0... .... = Reserved bit: Not set

.1.. .... = Don't fragment: Set

..0. .... = More fragments: Not set

Fragment Offset: 0

Time to Live: 64

Protocol: SCTP (132)

Header Checksum: 0x76c5 [validation disabled]

[Header checksum status: Unverified]

Source Address: 10.0.0.162

Destination Address: 10.0.0.185

Stream Control Transmission Protocol, Src Port: 38412 (38412), Dst Port: 48041 (48041)

Source port: 38412

Destination port: 48041

Verification tag: 0x8d10a6cf

[Association index: 65535]

Checksum: 0xd913f52a [unverified]

[Checksum Status: Unverified]

DATA chunk(ordered, complete segment, TSN: 4169966870, SID: 1, SSN: 2, PPID: 60,

payload length: 76 bytes)

Chunk type: DATA (0)

0... .... = Bit: Stop processing of the packet

.0.. .... = Bit: Do not report

Chunk flags: 0x03

.... 0... = I-Bit: Possibly delay SACK

.... .0.. = U-Bit: Ordered delivery

.... ..1. = B-Bit: First segment

.... ...1 = E-Bit: Last segment

Chunk length: 92

Transmission sequence number: 4169966870

[This chunk is acked in frame: 909]

[The RTT to SACK was: 0.299073623 seconds]

Stream identifier: 0x0001

Stream sequence number: 2

Payload protocol identifier: NGAP (60)

NG Application Protocol

NGAP-PDU: initiatingMessage (0)

initiatingMessage

procedureCode: id-DownlinkNASTransport (4)

criticality: ignore (1)

value

DownlinkNASTransport

protocolIEs: 3 items

Item 0: id-AMF-UE-NGAP-ID

ProtocolIE-Field

id: id-AMF-UE-NGAP-ID (10)

criticality: reject (0)

value

AMF-UE-NGAP-ID: 102

Item 1: id-RAN-UE-NGAP-ID

ProtocolIE-Field

id: id-RAN-UE-NGAP-ID (85)

criticality: reject (0)

value

RAN-UE-NGAP-ID: 1

Item 2: id-NAS-PDU

ProtocolIE-Field

id: id-NAS-PDU (38)

criticality: reject (0)

value

NAS-PDU: 7e02708c9be0087e0054431081c176589e9ebfcd�

Non-Access-Stratum 5GS (NAS)PDU

Security protected NAS 5GS message

Extended protocol discriminator:

5G mobility management messages (126)

0000 .... = Spare Half Octet: 0

.... 0010 = Security header type:

Integrity protected and ciphered (2)

Message authentication code: 0x708c9be0

Sequence number: 8

Encrypted data

(11) UplinkNASTransport

Internet Protocol Version 4, Src: 10.0.0.185, Dst: 10.0.0.162

0100 .... = Version: 4

.... 0101 = Header Length: 20 bytes (5)

Differentiated Services Field: 0x02 (DSCP: CS0, ECN: ECT(0))

0000 00.. = Differentiated Services Codepoint: Default (0)

.... ..10 = Explicit Congestion Notification: ECN-Capable Transport codepoint '10' (2)

Total Length: 228

Identification: 0x0010 (16)

Flags: 0x40, Don't fragment

0... .... = Reserved bit: Not set

.1.. .... = Don't fragment: Set

..0. .... = More fragments: Not set

Fragment Offset: 0

Time to Live: 64

Protocol: SCTP (132)

Header Checksum: 0x242a [validation disabled]

[Header checksum status: Unverified]

Source Address: 10.0.0.185

Destination Address: 10.0.0.162

Stream Control Transmission Protocol, Src Port: 48041 (48041), Dst Port: 38412 (38412)

Source port: 48041

Destination port: 38412

Verification tag: 0x790ad620

[Association index: 65535]

Checksum: 0x39273ca9 [unverified]

[Checksum Status: Unverified]

DATA chunk(ordered, complete segment, TSN: 3757580135, SID: 1, SSN: 5, PPID: 60,

payload length: 180 bytes)

Chunk type: DATA (0)

0... .... = Bit: Stop processing of the packet

.0.. .... = Bit: Do not report

Chunk flags: 0x03

.... 0... = I-Bit: Possibly delay SACK

.... .0.. = U-Bit: Ordered delivery

.... ..1. = B-Bit: First segment

.... ...1 = E-Bit: Last segment

Chunk length: 196

Transmission sequence number: 3757580135

[This chunk is acked in frame: 911]

[The RTT to SACK was: 0.000140996 seconds]

Stream identifier: 0x0001

Stream sequence number: 5

Payload protocol identifier: NGAP (60)

NG Application Protocol

NGAP-PDU: initiatingMessage (0)

initiatingMessage

procedureCode: id-UplinkNASTransport (46)

criticality: ignore (1)

value

UplinkNASTransport

protocolIEs: 4 items

Item 0: id-AMF-UE-NGAP-ID

ProtocolIE-Field

id: id-AMF-UE-NGAP-ID (10)

criticality: reject (0)

value

AMF-UE-NGAP-ID: 102

Item 1: id-RAN-UE-NGAP-ID

ProtocolIE-Field

id: id-RAN-UE-NGAP-ID (85)

criticality: reject (0)

value

RAN-UE-NGAP-ID: 1

Item 2: id-NAS-PDU

ProtocolIE-Field

id: id-NAS-PDU (38)

criticality: reject (0)

value

NAS-PDU: 7e02c3faa3fa0a7e006701006b2e0114c1000093280100�

Non-Access-Stratum 5GS (NAS)PDU

Security protected NAS 5GS message

Extended protocol discriminator:

5G mobility management messages (126)

0000 .... = Spare Half Octet: 0

.... 0010 = Security header type:

Integrity protected and ciphered (2)

Message authentication code: 0xc3faa3fa

Sequence number: 10

Encrypted data

Item 3: id-UserLocationInformation

ProtocolIE-Field

id: id-UserLocationInformation (121)

criticality: ignore (1)

value

UserLocationInformation: userLocationInformationNR (1)

userLocationInformationNR

nR-CGI

pLMNIdentity: 00f110

Mobile Country Code (MCC): Unknown (1)

Mobile Network Code (MNC): Unknown (01)

nRCellIdentity: 0x0001234501

tAI

pLMNIdentity: 00f110

Mobile Country Code (MCC): Unknown (1)

Mobile Network Code (MNC): Unknown (01)

tAC: 100 (0x000064)

PDU Session Resource Setup

The purpose of the PDU Session Resource Setup is as follows :

assign resources on Uu and NG-U for one or several PDU sessions and the corresponding QoS flows
setup corresponding DRBs for a given UE

Overall signaling procecedure is as follows and the details are described in 38.413 - 8.2.1.

< 38.413 - Figure 8.2.1.2-1: PDU session resource setup: successful operation >

This process is the one that get a huge list of parameters involved. The details are described in 38.413-8.2.1, but it doesn't make clear sense to me yet. I would need more study and log analysis for deeper understanding. The list of parameters explained in this specification is as follows to give you some generic idea.

PDU SESSION RESOURCE SETUP REQUEST

PDU Session Resource Setup Request List

DUSessionNAS-PDU
PDU Session ID

RAN Paging Priority
PDU Session Resource Setup Request Transfer IE

UL NG-U UP TNL Information
Additional UL NG-U UP TNL Information
Common Network Instance
Network Instance
UP Transport Layer Information List
Redundant UL NG-U UP TNL Information
Redundant QoS Flow per TNL Information
Additional Redundant DL QoS Flow per TNL Information
TSC Traffic Characteristics
PDU Session Type
Security Indication

Integrity Protection Indication
Confidentiality Protection Indication
Maximum Integrity Protected Data Rate Downlink
Maximum Integrity Protected Data Rate Uplink

PDU Session Aggregate Maximum Bit Rate
QoS Flow Level QoS Parameters

Additional QoS Flow Information
QoS Monitoring Request
Flow Level QoS Parameters

GBR QoS Flow Information

Alternative QoS Parameters Set List

Redundant QoS Flow Indicator
Redundant PDU Session Information
PDU Session Expected UE Activity Behaviour

PDU SESSION RESOURCE SETUP RESPONSE

PDU Session Resource Setup Response Transfer

Integrity Protection Result
Confidentiality Protection Result IE
Current QoS Parameters Set Index
Global RAN Node ID of Secondary NG-RAN Node
QoS Flow per TNL Information
QoS Flow Failed to Setup List
PDU Session Resource Setup Unsuccessful Transfer

(12) PDUSessionResourceSetupRequest

Internet Protocol Version 4, Src: 10.0.0.162, Dst: 10.0.0.185

0100 .... = Version: 4

.... 0101 = Header Length: 20 bytes (5)

Differentiated Services Field: 0x02 (DSCP: CS0, ECN: ECT(0))

0000 00.. = Differentiated Services Codepoint: Default (0)

.... ..10 = Explicit Congestion Notification: ECN-Capable Transport codepoint '10' (2)

Total Length: 292

Identification: 0xaddd (44509)

Flags: 0x40, Don't fragment

0... .... = Reserved bit: Not set

.1.. .... = Don't fragment: Set

..0. .... = More fragments: Not set

Fragment Offset: 0

Time to Live: 64

Protocol: SCTP (132)

Header Checksum: 0x761c [validation disabled]

[Header checksum status: Unverified]

Source Address: 10.0.0.162

Destination Address: 10.0.0.185

Stream Control Transmission Protocol, Src Port: 38412 (38412), Dst Port: 48041 (48041)

Source port: 38412

Destination port: 48041

Verification tag: 0x8d10a6cf

[Association index: 65535]

Checksum: 0xf21498ba [unverified]

[Checksum Status: Unverified]

SACK chunk (Cumulative TSN: 3757580135, a_rwnd: 106496, gaps: 0, duplicate TSNs: 0)

Chunk type: SACK (3)

0... .... = Bit: Stop processing of the packet

.0.. .... = Bit: Do not report

Chunk flags: 0x00

.... ...0 = Nounce sum: 0

Chunk length: 16

Cumulative TSN ACK: 3757580135

[Acknowledges TSN: 3757580135]

[Acknowledges TSN in frame: 910]

[The RTT since DATA was: 0.000140996 seconds]

Advertised receiver window credit (a_rwnd): 106496

Number of gap acknowledgement blocks: 0

Number of duplicated TSNs: 0

DATA chunk(ordered, complete segment, TSN: 4169966871, SID: 1, SSN: 3, PPID: 60,

payload length: 228 bytes)

Chunk type: DATA (0)

0... .... = Bit: Stop processing of the packet

.0.. .... = Bit: Do not report

Chunk flags: 0x03

.... 0... = I-Bit: Possibly delay SACK

.... .0.. = U-Bit: Ordered delivery

.... ..1. = B-Bit: First segment

.... ...1 = E-Bit: Last segment

Chunk length: 244

Transmission sequence number: 4169966871

[This chunk is acked in frame: 914]

[The RTT to SACK was: 0.035658957 seconds]

Stream identifier: 0x0001

Stream sequence number: 3

Payload protocol identifier: NGAP (60)

NG Application Protocol

NGAP-PDU: initiatingMessage (0)

initiatingMessage

procedureCode: id-PDUSessionResourceSetup (29)

criticality: reject (0)

value

PDUSessionResourceSetupRequest

protocolIEs: 4 items

Item 0: id-AMF-UE-NGAP-ID

ProtocolIE-Field

id: id-AMF-UE-NGAP-ID (10)

criticality: reject (0)

value

AMF-UE-NGAP-ID: 102

Item 1: id-RAN-UE-NGAP-ID

ProtocolIE-Field

id: id-RAN-UE-NGAP-ID (85)

criticality: reject (0)

value

RAN-UE-NGAP-ID: 1

Item 2: id-PDUSessionResourceSetupListSUReq

ProtocolIE-Field

id: id-PDUSessionResourceSetupListSUReq (74)

criticality: reject (0)

value

PDUSessionResourceSetupListSUReq: 1 item

Item 0

PDUSessionResourceSetupItemSUReq

pDUSessionID: 1

pDUSessionNAS-PDU: 7e02ba31020b097e006801�

Non-Access-Stratum 5GS (NAS)PDU

Security protected NAS 5GS message

Extended protocol discriminator:

5G mobility management messages (126)

0000 .... = Spare Half Octet: 0

.... 0010 = Security header type:

Integrity protected and ciphered (2)

Message authentication code: 0xba31020b

Sequence number: 9

Encrypted data

s-NSSAI

sST: 01

pDUSessionResourceSetupRequestTransfer: 0000040082�

PDUSessionResourceSetupRequestTransfer

protocolIEs: 4 items

Item 0: id-PDUSessionAggregateMaximumBitRate

ProtocolIE-Field

id: id-PDUSessionAggregateMaximumBitRate

criticality: reject (0)

value

PDUSessionAggregateMaximumBitRate

pDUSessionAggregateMaximumBitRateDL:

3000000000bits/s

pDUSessionAggregateMaximumBitRateUL:

1000000000bits/s

Item 1: id-UL-NGU-UP-TNLInformation

ProtocolIE-Field

id: id-UL-NGU-UP-TNLInformation (139)

criticality: reject (0)

value

UPTransportLayerInformation: gTPTunnel(0)

gTPTunnel

transportLayerAddress:

0a0000a2]

TransportLayerAddress

(IPv4): 10.0.0.162

gTP-TEID: 4f485cc3

Item 2: id-PDUSessionType

ProtocolIE-Field

id: id-PDUSessionType (134)

criticality: reject (0)

value

PDUSessionType: ipv4 (0)

Item 3: id-QosFlowSetupRequestList

ProtocolIE-Field

id: id-QosFlowSetupRequestList (136)

criticality: reject (0)

value

QosFlowSetupRequestList: 1 item

Item 0

QosFlowSetupRequestItem

qosFlowIdentifier: 1

qosFlowLevelQosParameters

qosCharacteristics:

nonDynamic5QI (0)

nonDynamic5QI

fiveQI: 9

allocationAndRetentionPriority

priorityLevelARP: 15

pre-emptionCapability:

shall-not-trigger-

pre-emption

preemptionVulnerability:

not-pre-emptable (0)

e-RAB-ID: 5

Item 3: id-UEAggregateMaximumBitRate

ProtocolIE-Field

id: id-UEAggregateMaximumBitRate (110)

criticality: ignore (1)

value

UEAggregateMaximumBitRate

uEAggregateMaximumBitRateDL: 3000000000bits/s

uEAggregateMaximumBitRateUL: 1000000000bits/s

(13) PDUSessionResourceSetupResponse

Internet Protocol Version 4, Src: 10.0.0.185, Dst: 10.0.0.162

0100 .... = Version: 4

.... 0101 = Header Length: 20 bytes (5)

Differentiated Services Field: 0x02 (DSCP: CS0, ECN: ECT(0))

0000 00.. = Differentiated Services Codepoint: Default (0)

.... ..10 = Explicit Congestion Notification: ECN-Capable Transport codepoint '10' (2)

Total Length: 104

Identification: 0x0011 (17)

Flags: 0x40, Don't fragment

0... .... = Reserved bit: Not set

.1.. .... = Don't fragment: Set

..0. .... = More fragments: Not set

Fragment Offset: 0

Time to Live: 64

Protocol: SCTP (132)

Header Checksum: 0x24a5 [validation disabled]

[Header checksum status: Unverified]

Source Address: 10.0.0.185

Destination Address: 10.0.0.162

Stream Control Transmission Protocol, Src Port: 48041 (48041), Dst Port: 38412 (38412)

Source port: 48041

Destination port: 38412

Verification tag: 0x790ad620

[Association index: 65535]

Checksum: 0x1ef6563e [unverified]

[Checksum Status: Unverified]

SACK chunk (Cumulative TSN: 4169966871, a_rwnd: 106496, gaps: 0, duplicate TSNs: 0)

Chunk type: SACK (3)

0... .... = Bit: Stop processing of the packet

.0.. .... = Bit: Do not report

Chunk flags: 0x00

.... ...0 = Nounce sum: 0

Chunk length: 16

Cumulative TSN ACK: 4169966871

[Acknowledges TSN: 4169966871]

[Acknowledges TSN in frame: 911]

[The RTT since DATA was: 0.035658957 seconds]

Advertised receiver window credit (a_rwnd): 106496

Number of gap acknowledgement blocks: 0

Number of duplicated TSNs: 0

DATA chunk(ordered, complete segment, TSN: 3757580136, SID: 1, SSN: 6, PPID: 60,

payload length: 40 bytes)

Chunk type: DATA (0)

0... .... = Bit: Stop processing of the packet

.0.. .... = Bit: Do not report

Chunk flags: 0x03

.... 0... = I-Bit: Possibly delay SACK

.... .0.. = U-Bit: Ordered delivery

.... ..1. = B-Bit: First segment

.... ...1 = E-Bit: Last segment

Chunk length: 56

Transmission sequence number: 3757580136

[This chunk is acked in frame: 931]

[The RTT to SACK was: 0.201436229 seconds]

Stream identifier: 0x0001

Stream sequence number: 6

Payload protocol identifier: NGAP (60)

NG Application Protocol

NGAP-PDU: successfulOutcome (1)

successfulOutcome

procedureCode: id-PDUSessionResourceSetup (29)

criticality: reject (0)

value

PDUSessionResourceSetupResponse

protocolIEs: 3 items

Item 0: id-AMF-UE-NGAP-ID

ProtocolIE-Field

id: id-AMF-UE-NGAP-ID (10)

criticality: ignore (1)

value

AMF-UE-NGAP-ID: 102

Item 1: id-RAN-UE-NGAP-ID

ProtocolIE-Field

id: id-RAN-UE-NGAP-ID (85)

criticality: ignore (1)

value

RAN-UE-NGAP-ID: 1

Item 2: id-PDUSessionResourceSetupListSURes

ProtocolIE-Field

id: id-PDUSessionResourceSetupListSURes (75)

criticality: ignore (1)

value

PDUSessionResourceSetupListSURes: 1 item

Item 0

PDUSessionResourceSetupItemSURes

pDUSessionID: 1

pDUSessionResourceSetupResponseTransfer:

0003e00a0000b9a968d0db0001

PDUSessionResourceSetupResponseTransfer

dLQosFlowPerTNLInformation

uPTransportLayerInformation: gTPTunnel (0)

gTPTunnel

transportLayerAddress: 0a0000b9

TransportLayerAddress (IPv4):

10.0.0.185

gTP-TEID: a968d0db

associatedQosFlowList: 1 item

Item 0

AssociatedQosFlowItem

qosFlowIdentifier: 1

Videos