Message Editor
Click here to see this page in full context

Landslide Performance Test System – Release 24.3 September 2024

Message Editor

The Message Editor allows you to edit Landslide generated messages and or compose your proprietary messages to perform negative testing with invalid values or malformed messages or to add proprietary information.

The Message Editor (ME) is supported in the following protocols and test cases depending on your system license:

Message Editor supports multiple protocols with differing rules. The following describes the elements of Message Editor and it's usage. The protocol specific rules are included in Elements of Message Editor section below.

Additional details can be found in the Landslide Tcl API Object and Perform Function Reference , use it to learn about detailed descriptions of each API Object and Perform Function.

NOTE: Normally in a test case, the values provisioned in the control plane messages sent by Landslide are derived from the test case parameter settings, and the composition of the messages is determined by the applicable protocol standards.

A configured Message Editor is saved to the library and can be used in more than one test case. When you Open to select Custom Messages from a library, the list of messages displayed are always in the context of a specific Protocol stack or Test Case. You may also sort the list of custom messages by Protocol (Click the Protocol column).

The newly visible Column is sortable in the Save Dialog.

NOTES:
  • When you open a Message Editor, the dialog only shows the Message Editors for the protocol in which your Test Case parameter is interested.
  • From the ME Window, press Shift+Alt+A to display the Save ME as Tcl window. Click the Save to File button to save as Tcl file. See additional details on Using the Tcl API.

Message Editor - 5G

 

Elements of the Message Editor

The Message Editor consists of a split pane with a tree structure in the left pane and a display panel in the right pane. A new ME is essentially a blank slate populated only by the static tree nodes.

Messages node

The Messages node is a container for message definitions.

Master Values node

The Master Values node holds containers for the Master Information Elements (IEs) and Master Fields that can optionally be used in messages or other master elements.

Right-Click Menu Options

All tasks/actions are performed using a popup menu that appears when you right-click a tree node. The same menu displays always but the options available for any given node depend on the type of node and the current configuration.

New

displays a submenu of element types. When the element is selected, a new element is created and added to the elements contained in the tree node.

Add Master IE and Add Master Field

display submenus of the existing master elements. Selecting a master element creates a replica that is added to the tree node’s elements. Replicas are displayed on the tree structure in an Italic font.

NOTE: When there are more than 15 Master Fields or Master Information Elements, clicking the Add Master IE and Add Master Field menu item displays a Popup that allows you to select multiple items to add.

 

Sub IE

Select Master IE, Right-Click and New Information Element to add a sub IE belonging to the master IE.

Move

displays a submenu of First, Up, Down, and Last options that can be used to arrange elements within a container.

Expand All

expands all children of the selected node, down to the lowest level.

Find Master

selects a replica’s master element.

Delete

removes the selected node and any children. When a master element is deleted, all replicas are also deleted.

 

Save

The Save button saves the message types created and the Close button closed the Message Editor.

When you save a Message Editor, the dialog window shows you all the Message Editors in the libraryand identifies the protocol to which the other Message Editors/types belong.

NOTES: You may save the ME settings as a Tcl file:

  • Press Shift+Alt+A to display the    Save ME as Tcl window.

  • Click the Save to File button to save as Tcl file.

 

TIP:

For example, to construct a  S1AP-s1-setup Request message (between eNodeB and MME), to include multiple TACs (5 - Tracking Area Codes) in one IE (Information Element) and multiple (> 1 Broadcast PLMNs per TAC):

  • Create a sub IE for each {TAC, plmns} block
  • Make sure that each Sub IE has a unique type value {0, 1, 2, ..}
  • Create each TAC or plmn as a Field under the required Sub IE

IMPORTANT:

The Message Editor supports rules applicable for certain protocol. The following lists the rules applicable for S1-AP protocol for MME Nodal. Message Editor Protocol for MME node is "S1-AP MME", for MME Nodal it is "S1-AP". 

S1-AP ME rules:

 

^ Back to Top

Master Values

The body of a message contains elements of information that may be used in more than one type of message. Any element can be created as a master value and then added to multiple messages or nested within other master elements, creating replicas of the master. When the master element is changed, by altering its structure or editing its value, the changes ripple through all of its replicas.

Replica tree nodes are displayed with an italic font to distinguish them from elements that are locally defined.

Error Checking

Since the main purpose of the ME is to introduce invalid values or malformed messages in the test, error checking is limited to the requirements of the software rather than forcing compliance to the protocol standards. It is assumed that the user is familiar with the protocol and the structure of the messages.

^ Back to Top

Messages

You can create a new Message by right-clicking the Messages node and selecting New > Message from the menu. The message node and its static children, Header Fields and Body, are added to the tree and the message definition is displayed in the right pane.

The message definition is divided into two sections, Message Header and Message Body. The sections are in a split pane with a divider that can be moved up or down to adjust the visible portion of the sections.

Message Header
  • Select the message Type from the dropdown, which identifies the default message to be modified.
NOTE: A particular message Type can only be used once in the ME.
  • Select the Override Type checkbox to send that message with a different type value in the message header.
  • Enter the message Instance value to specify which message instance occurrence should be modified. This instance value along with the Override Type identifies the default message being modified.
  • GTP-C Dual Stack Address Swap - Supported in SGW Nodal Only. When selected, it will cause the GTPC IP Address to switch between the Primary and Alternate address for the Instance specified. However, it requires the Dual Stack Support to be enabled on the MME Control Node/Target MME Control Node , otherwise it will be ignored. This only applies to Message Type = Create Session Req, or Modify Bearer Req.

A combination of an Instance value and Override Type can appear only once in the Message Editor. Valid range is between 0  and 10. An Instance value 0 indicates all occurrences of that message Type and value 1-10 indications the nth occurrence of that message type only.

The same message type can also appear with a 0 instance and an nth instance. In such a case, all instances of the message will be sent as defined by the 0 instance except for the nth instance, which will use its own definition.

NOTE: The counter that tracks messages sent will loop back/reset if the message is sent more than 255 times during the test, the counter will start over again.
  • Select the Replace Entire Message Body to indicate that the message body will only contain the elements that you define (the default message contents are ignored).

You can make additional modifications to the message header by modifying the values of individual header fields.

  • Right-click either the Message node or its Header Fields node, select New > Header Field. A Field element is added to the Message Header section of the message and a Field node is added to the Header Fields container on the left pane.
  • Select the type of header fieldtype of header field from the drop-down list and define its value using the Format list (see Fields below for an explanation of the different formats) and the Value field.

  • Select the Increment checkbox if the value should be incremented for each message.
   

PDU group index :

Range:  0 ~ N (max number of pdu per UE)

Default: 0

Description: 0: all, 1~N:nth pdu group only
Message Body

You may modify the message body as desired by adding new or master elements. Unless Replace Entire Message Body is selected, the only alterations to the default message body will be the elements that you define. See to define message body elements, see Information Elements and Defining Fields for more information.

NOTE: Only the GTPv2 protocol allows Information Elements in the message body.

 

^ Back to Top

Fields

Field elements represent the value portions of the message header, message body, and information element.

1.

Enter a name in the field provided. Default names are generated as you create new Fields, but entering a meaningful name will help to clarify your structure.
2.

Select the appropriate Format for the Field’s value. The Format determines how values are incremented and can determine the Field size.

  • UINT8, UINT16, and UINT32 indicate that the value is an integer occupying the selected number of bits.

  • ASCII String indicates that the value is a text string. These values cannot be incremented and will be padded as necessary to align to the next octet border.

  •  Hex String indicates that a hexadecimal value is provisioned. Hex values can be incremented and will also be padded as necessary.

  •  Bit indicates that the value occupies the number of bits defined. This format can be used for flags or for any field that is less than 8 bits, including spares.

  • IPv4 Address and IPv6 Address indicate that the value is an IP address and will be sized and incremented according to type.

  • BCD indicates that a binary-coded decimal value is provisioned.

3.

Enter the field’s (starting) value. The value must conform to the selected Format or a validation error will be generated.

4.

Check the Increment box if the value should be incremented.

 

Using Master Fields and Replicas

If you would wish to use the same field more than once, and if you would like all instances of the field to carry the same value, you can create a Master Field.

NOTE: The Add Master Menu will only display Scroll UP and Scroll Down, if you rename any existing Master Fields.
Master Fields The Master Fields must have names that are unique among all Master Fields since the name is used to match masters with their replicas. Replicas can be easily identified in the tree structure by the Italic font.
Replicas In the display pane all settings of the replica are disabled except for the Linked checkbox, which is enabled and selected. A replica can be converted to a local field by clearing the checkbox thereby enabling the other settings. Once that link is broken it cannot be restored.

 

^ Back to Top

Information Elements

Information Elements have a header of their own and their values are made up of Fields or other IEs. An IE may have nested Sub IEs and a Sub IE may also have nested IEs and fields.

1.

Enter a Name. As with Fields, the Name is only used by the editor and it provides the link between masters and replicas. You may edit/change the name of an IE or Sub IE as required. You are cannot change the label of a Master IE.

2.

Enter the Type of the IE to be altered or added.

Range : 0 to 65535

See additional details in NGAP_Msg_Edit_NGSetupRequestMessage_Template

 

   In TS 38.413, Message Type of NGAP message is defined as below:

 

 

3.

Select the Action (only applicable to top-level IEs not nested IEs).

  • Add – adds the IE to the message after any default IEs.

  • Override – replaces the default IE with the one you have defined, or adds IE with the same order in 3GPP if there is no default IE.

  • Remove – removes the default IE. Only the ID settings are available in this case.

NOTE: When using Override or Remove, the IE Type and Instance (when Instance is required) must match that of the default IE. Or for those IEs which are optional, get same orders as listed in specification.

 
4.

Select Presence: Options are: Optional/Conditional or Mandatory.  New for 5G Ngap. As defined in TS 38.413

Range: 0 to 1

Default :0

Description: 0 : Mandatory, 1 : Optional

The top IE with ProtocolIE-ID doesn’t need to set the presence.

 

Presence

IE presence value defined in TS 24.501 - 8.3 5GS session management messages (Sm/Mm - See Sm example below)

   

Range: 0 to 1

Default :0

  • If M is selected, Position should be set. Otherwise, Position should be grayed-out.
  • If M is selected, Type should be always 0.
  • If M is selected, Action should be always Override option.
5.

Enter Position. New for 5G Ngap. As defined in TS 38.413

Range: 0 to 65535

Default: 0

Value of 0: Not Used (in IE) or Invalid (in SubIE), 1~65535

The position (order) of sub IEs within the specific IE defined TS 38.413.

  • NGAP TS 38.413 defines ID of Top Level IE in NGAP messages but doesn’t define ID of sub IEs within the IE. The position will be used to distinguish sub IEs within the specific IE.

  • In the GUI, if IE defined in Master IE configuration is used as sub IE when editing the message body, Position value and Presence value should be set. Un-check “Linked” option and then configure the position value and the presence value.

  • The top IE with ProtocolIE-ID doesn’t need to set the position value.

 

Position of Mandatory IE in each message content defined in TS 24.501 - 8.3 5GS session management messages (Sm/Mm - See Sm example below0

 

Range: 0 to 65535

Default: 0

Position of Mandatory IE in each message content defined in TS 24.501 - 8.3 5GS session management messages.

Ex) In PDU SESSION ESTABLISHMENT ACCEPT message content, the position of the mandatory IE –“Selected PDU session type” is 5.

 

  • If Presence is O/C, Position should be grayed-out.
  • The Mandatory IE with position 1 ~ 4 is not allowed to be edited.

The Position option for NAS MME on MME Node is 4 to 255.
6.

Enter Choice. New for 5G Ngap. As defined in TS 38.413

Range: 0 to 255

Default : 0

The CHOICE order of the chosen sub IE defined in the specific IE defined in TS 38.413.

If CHOICE of sub IE is defined in TS38.413, it's value should start from 1. Otherwise, its value should be set to 0.

 
7.

Fields

Field elements represent the value portions of the message header, message body, and information element.

1.

Enter a name in the field provided. Default names are generated as you create new Fields, but entering a meaningful name will help to clarify your structure.

2.

Select the appropriate Format for the Field’s value. The Format determines how values are incremented and can determine the Field size.

  • UINT8, UINT16, and UINT32 indicate that the value is an integer occupying the selected number of bits.

  • ASCII String indicates that the value is a text string. These values cannot be incremented and will be padded as necessary to align to the next octet border.

  • Hex String indicates that a hexadecimal value is provisioned. Hex values can be incremented and will also be padded as necessary.

  • Bit indicates that the value occupies the number of bits defined. This format can be used for flags or for any field that is less than 8 bits, including spares.

  • IPv4 Address and IPv6 Address indicate that the value is an IP address and will be sized and incremented according to type.

  • BCD indicates that a binary-coded decimal value is provisioned.

3.

Enter the field’s (starting) value. The value must conform to the selected Format or a validation error will be generated.

4.

Check the Increment box if the value should be incremented.

 

=> Bit format is used only for the "message header" configuration.

The format of IEs in each message content defined in TS 24.501 - 8.3 5GS session management messages (Sm/Mm - See Sm example below)

Range: 1~8 (T: 1, V_1/2: 2, V: 3, TV: 4, LV: 5, TLV: 6, LV-E: 7, TLV-E: 8)

Default : TLV

Description: The format of IEs in each message content defined in TS 24.501 - 8.3 5GS session management messages.

 

Ex) In PDU SESSION ESTABLISHMENT ACCEPT message content, the format of the mandatory IE –“Selected PDU session type” is V_1.2.

 

T: Type only

V_1/2:  Value only with length Half octet(1/2)

V: Value only

LV: Length and Value

TLV: Type, Length and Value

LV-E: Length (2 bytes) and Value

TLV-E: Type, Legnth(2 bytes) and Value

 

      If Action is set to “Remove”, Presence should be set to “O/C” and all parameters except for Name and Type should be grayed-out.
8.

If the protocol requires an IE Instance it will also be mandatory in the ME. Otherwise, it will be optional and a checkbox is displayed. If the Action is Override and Instance is included, you can select Override Instance and override the Instance in the default IE.
9.

If the protocol requires an Occurrence and if the Action is Override, select the Occurrence from 0 to 255. (Available in the PFCP (Sxa/Sxb Interfaces) on PGW/SGW Node Test Cases)
10.

If the protocol requires an IE Length it will also be mandatory in the ME. Otherwise, it will be optional and a checkbox is displayed. When Length is included, you can choose Calculate to let Landslide calculate the correct length or choose Set and the provisioned Length will be used regardless of its accuracy.
11.

If the Action is Add or Override, provision the IE’s Values by adding Fields and nested IEs.

 

Using Master IEs and Replicas

Master IEs You can use Master IEs in much the same way that you use Master Fields. The IE Values can be made up of local elements, master elements, or both.
Replica If you convert a replica IE to a local IE, the elements that were local to the master become local to the IE and elements that were replicas themselves will remain replicas unless you also convert them to local elements.

 

5G supported Messages by the Message Editor in red.

SM

Message Type Name

Type value (Decimal)

Supported in Landslide

PDU Session Establishment Request

193

Y

PDU Session Establishment Accept

194

Y

PDU Session Modification Request

 

Y

PDU Session Modification Reject

 

Y

PDU Session Modification Command

 

Y

PDU Session Modification Complete

 

Y

PDU Session Modification Command Reject

 

Y

PDU Session Release Request

209

Y

PDU Session Release Command

211

Y

PDU Session Release Complete

212

Y

MM

Message Type Name

Type value (Decimal)

Supported in Landslide

Registration Request

65

Y

Registration Accept

66

Y

Registration Complete

67

Y

Deregistration Request (UE originating)

69

Y

Deregistration Accept (UE originating)

70

Y

Deregistration Request (UE terminated)

71

Y

Deregistration Accept (UE terminated)

72

Y

Authentication Request

86

Y

Authentication Response

87

Y

Authentication Reject

88

Y

Authentication Failure

89

Y

Identity Request

91

Y

Identity Response

92

Y

UL NAS transport

103

Y

DL NAS transport

104

Y
Service Request

76

Y
Service Accept

78

Y
Security Mode Command

93

Y
Security Mode Complete

94

Y
Security Mode Reject

95

Y

NGAP

Message Type Name

Type value (Decimal)

Supported in Landslide

AMFConfigurationUpdate

1

Y

AMFConfigurationUpdateAcknowledge

2

Y

AMFConfigurationUpdateFailure

3

Y

DownlinkNASTransport

1025

Y

InitialContextSetupRequest         (per TS38.413 v 15.0.0 section 9.2.2.1)

3585

Y

InitialContextSetupResponse      (per TS38.413 v 15.0.0 section 9.2.2.2)

3586

Y

InitialContextSetupFailure

3587

Y

InitialUEMessage                         (per TS38.413 v 15.0.0 section 9.2.5.1)

3841

Y

NGSetupRequest                        (per TS38.413 v 15.0.0 section 9.2.6.1)

5377

Y

NGSetupResponse                     (per TS38.413 v 15.0.0 section 9.2.6.2)

5378

Y

NGSetupFailure

5379

Y

Paging

5633

Y

PDUSessionResourceModifyRequest

6145

Y

PDUSessionResourceModifyResponse

6146

Y

 

PDUSessionResourceSetupRequest  (per TS38.413 v 15.0.0 section 9.2.1.1)

6913

Y

PDUSessionResourceSetupResponse  (per TS38.413 v 15.0.0 section 9.2.1.2)

6914

Y

RANConfigurationUpdate     (per TS38.413 v v 15.0.0 section 8.7.2 )

8449

 

Y

RANConfigurationUpdateAcknowledge     (per TS38.413 v v 15.0.0 section 8.7.2 )

8450

Y

RANConfigurationUpdateFailure     (per TS38.413 v v 15.0.0 section 8.7.2)

8451

Y

UECapabilityInfoIndication      (per TS38.413 v 15.0.0 section 9.2.13.1)

9473

Y

UEContextReleaseCommand    (per TS38.413 v 15.0.0 section 9.2.2.5)

9985

Y

UEContextReleaseComplete     (per TS38.413 v 15.0.0 section 9.2.2.6)

9986

Y

UEContextReleaseRequest       (per TS38.413 v 15.0.0 section 9.2.2.4)

10241

Y

UERadioCapabilityCheckRequest

10497

Y

UERadioCapabilityCheckResponse

10498

Y

UplinkNASTransport                 (per TS38.413 v 15.0.0 section 9.2.5.3)

11009

Y

 

Constant Definitions defined in TS 38.413 (5G)

Type of Message and Procedure Code defined in TS 38.413 v 16.2.0   (Disclaimer: Not all messages listed below are supported by Landslide)

< Type of Message Value >

Type Of Message

Value (Decimal)

Initiating_Message

1

Successful_Outcome

2

Unsuccessful_Outcome

3

Procedure Code

Value (Decimal)

id_AMFConfigurationUpdate

0

Id_AMFStatusIndication

1

id_CellTrafficTrace

2

id_DeactivateTrace

3

id_DownlinkNASTransport

4

id_DownlinkNonUEAssociatedNRPPaTransport

5

id_DownlinkRANConfigurationTransfer

6

id_DownlinkRANStatusTransfer

7

id_DownlinkUEAssociatedNRPPaTransport

8

id_ErrorIndication

9

id_HandoverCancel

10

id_HandoverNotification

11

id_HandoverPreparation

12

id_HandoverResourceAllocation

13

id_InitialContextSetup

14

id_InitialUEMessage

15

id_LocationReportingControl

16

id_LocationReportingFailureIndication

17

id_LocationReport

18

id_NASNonDeliveryIndication

19

id_NGReset

20

id_NGSetup

21
id-OverloadStart 22
id-OverloadStop 23

id_Paging

24

id_PathSwitchRequest

25

id_PDUSessionResourceModify

26

id_PDUSessionResourceModifyIndication

27

id_PDUSessionResourceRelease

28

id_PDUSessionResourceSetup

29

id_PDUSessionResourceNotify

30

id_PrivateMessage

31

id_PWSCancel

32

id_PWSFailureIndication

33

id_PWSRestartIndication

34

id_RANConfigurationUpdate

35

id_RerouteNASRequest

36
id-RRCInactiveTransitionReport 37

id_TraceFailureIndication

38

id_TraceStart

39

id_UEContextModification

40

id_UEContextRelease

41

id_UEContextReleaseRequest

42

id_UERadioCapabilityCheck

43
id-UERadioCapabilityInfoIndication 44

id_UETNLABindingRelease

45

id_UplinkNASTransport

46

id_UplinkNonUEAssociatedNRPPaTransport

47

id_UplinkRANConfigurationTransfer

48

id_UplinkRANStatusTransfer

49

id_UplinkUEAssociatedNRPPaTransport

50

id_WriteReplaceWarning

51
id-SecondaryRATDataUsageReport 52
id-UplinkRIMInformationTransfer 53
id-DownlinkRIMInformationTransfer 54
id-RetrieveUEInformation 55
id-UEInformationTransfer 56
id-RANCPRelocationIndication 57
id-UEContextResume 58
id-UEContextSuspend 59
id-UERadioCapabilityIDMapping 60
id-HandoverSuccess 61
id-UplinkRANEarlyStatusTransfer 62
id-DownlinkRANEarlyStatusTransfer 63
id-AMFCPRelocationIndication 64
id-ConnectionEstablishmentIndication 65

 

Protocol IE-ID (IE type) defined in TS 38.413 v 16.2.0   (Disclaimer: Not all messages listed below are supported by Landslide)

    id-AllowedNSSAI                                           ProtocolIE-ID ::= 0

    id-AMFName                                                 ProtocolIE-ID ::= 1

    id-AMFOverloadResponse                               ProtocolIE-ID ::= 2

    id-AMFSetID                                                 ProtocolIE-ID ::= 3

    id-AMF-TNLAssociationFailedToSetupList          ProtocolIE-ID ::= 4

    id-AMF-TNLAssociationSetupList                      ProtocolIE-ID ::= 5

    id-AMF-TNLAssociationToAddList                     ProtocolIE-ID ::= 6

    id-AMF-TNLAssociationToRemoveList               ProtocolIE-ID ::= 7

    id-AMF-TNLAssociationToUpdateList                 ProtocolIE-ID ::= 8

    id-AMFTrafficLoadReductionIndication              ProtocolIE-ID ::= 9

    id-AMF-UE-NGAP-ID                                       ProtocolIE-ID ::= 10

    id-AssistanceDataForPaging                            ProtocolIE-ID ::= 11

    id-BroadcastCancelledAreaList                         ProtocolIE-ID ::= 12

    id-BroadcastCompletedAreaList                       ProtocolIE-ID ::= 13

    id-CancelAllWarningMessages                          ProtocolIE-ID ::= 14

    id-Cause                                                       ProtocolIE-ID ::= 15

    id-CellIDListForRestart                                   ProtocolIE-ID ::= 16

    id-ConcurrentWarningMessageInd                   ProtocolIE-ID ::= 17

    id-CoreNetworkAssistanceInformationForInactive  ProtocolIE-ID ::= 18

    id-CriticalityDiagnostics                                  ProtocolIE-ID ::= 19

    id-DataCodingScheme                                    ProtocolIE-ID ::= 20

    id-DefaultPagingDRX                                      ProtocolIE-ID ::= 21

    id-DirectForwardingPathAvailability                  ProtocolIE-ID ::= 22

    id-EmergencyAreaIDListForRestart                  ProtocolIE-ID ::= 23

    id-EmergencyFallbackIndicator                        ProtocolIE-ID ::= 24

    id-EUTRA-CGI                                                ProtocolIE-ID ::= 25

    id-FiveG-S-TMSI                                            ProtocolIE-ID ::= 26

    id-GlobalRANNodeID                                      ProtocolIE-ID ::= 27

    id-GUAMI                                                      ProtocolIE-ID ::= 28

    id-HandoverType                                           ProtocolIE-ID ::= 29

    id-IMSVoiceSupportIndicator                          ProtocolIE-ID ::= 30

    id-IndexToRFSP                                             ProtocolIE-ID ::= 31

    id-InfoOnRecommendedCellsAndRANNodesForPaging        ProtocolIE-ID ::= 32

    id-LocationReportingRequestType                    ProtocolIE-ID ::= 33

    id-MaskedIMEISV                                           ProtocolIE-ID ::= 34

    id-MessageIdentifier                                       ProtocolIE-ID ::= 35

    id-MobilityRestrictionList                                 ProtocolIE-ID ::= 36

    id-NASC                                                        ProtocolIE-ID ::= 37

    id-NAS-PDU                                                   ProtocolIE-ID ::= 38

    id-NASSecurityParametersFromNGRAN             ProtocolIE-ID ::= 39

    id-NewAMF-UE-NGAP-ID                                 ProtocolIE-ID ::= 40

    id-NewSecurityContextInd                               ProtocolIE-ID ::= 41

    id-NGAP-Message                                           ProtocolIE-ID ::= 42

    id-NGRAN-CGI                                               ProtocolIE-ID ::= 43

    id-NGRANTraceID                                           ProtocolIE-ID ::= 44

    id-NR-CGI                                                      ProtocolIE-ID ::= 45

    id-NRPPa-PDU                                                ProtocolIE-ID ::= 46

    id-NumberOfBroadcastsRequested                   ProtocolIE-ID ::= 47

    id-OldAMF                                                     ProtocolIE-ID ::= 48

    id-OverloadStartNSSAIList                              ProtocolIE-ID ::= 49

    id-PagingDRX                                                ProtocolIE-ID ::= 50

    id-PagingOrigin                                              ProtocolIE-ID ::= 51

    id-PagingPriority                                            ProtocolIE-ID ::= 52

    id-PDUSessionResourceAdmittedList                ProtocolIE-ID ::= 53

    id-PDUSessionResourceFailedToModifyListModRes      ProtocolIE-ID ::= 54

    id-PDUSessionResourceFailedToSetupListCxtRes        ProtocolIE-ID ::= 55

    id-PDUSessionResourceFailedToSetupList                 ProtocolIE-ID ::= 55

    id-PDUSessionResourceFailedToSetupListHOAck        ProtocolIE-ID ::= 56

    id-PDUSessionResourceFailedToSetupListPSReq        ProtocolIE-ID ::= 57

    id-PDUSessionResourceFailedToSetupListSURes        ProtocolIE-ID ::= 58

    id-PDUSessionResourceHandoverList                       ProtocolIE-ID ::= 59

    id-PDUSessionResourceListCxtRelCpl                       ProtocolIE-ID ::= 60

    id-PDUSessionResourceListHORqd                           ProtocolIE-ID ::= 61

    id-PDUSessionResourceModifyListModCfm                ProtocolIE-ID ::= 62

    id-PDUSessionResourceModifyListModInd                 ProtocolIE-ID ::= 63

    id-PDUSessionResourceModifyListModReq                ProtocolIE-ID ::= 64

    id-PDUSessionResourceModifyListModRes                ProtocolIE-ID ::= 65

    id-PDUSessionResourceNotifyList                            ProtocolIE-ID ::= 66

    id-PDUSessionResourceReleasedListNot                   ProtocolIE-ID ::= 67

    id-PDUSessionResourceReleasedListPSAck               ProtocolIE-ID ::= 68

    id-PDUSessionResourceReleasedListPSFail                ProtocolIE-ID ::= 69

    id-PDUSessionResourceReleasedListRelRes               ProtocolIE-ID ::= 70

    id-PDUSessionResourceSetupListCxtReq                  ProtocolIE-ID ::= 71

    id-PDUSessionResourceSetupListCxtRes                   ProtocolIE-ID ::= 72

    id-PDUSessionResourceSetupListHOReq                   ProtocolIE-ID ::= 73

    id-PDUSessionResourceSetupListSUReq                   ProtocolIE-ID ::= 74    

    id-PDUSessionResourceSetupListSURes                   ProtocolIE-ID ::= 75

    id-PDUSessionResourceToBeSwitchedDLList              ProtocolIE-ID ::= 76

    id-PDUSessionResourceSwitchedList                        ProtocolIE-ID ::= 77

    id-PDUSessionResourceToReleaseListHOCmd            ProtocolIE-ID ::= 78

    id-PDUSessionResourceToReleaseListRelCmd            ProtocolIE-ID ::= 79

    id-PLMNSupportList                                                ProtocolIE-ID ::= 80

    id-PWSFailedCellIDList                                            ProtocolIE-ID ::= 81

    id-RANNodeName                                                   ProtocolIE-ID ::= 82

    id-RANPagingPriority                                               ProtocolIE-ID ::= 83

    id-RANStatusTransfer-TransparentContainer              ProtocolIE-ID ::= 84

    id-RAN-UE-NGAP-ID                                               ProtocolIE-ID ::= 85

    id-RelativeAMFCapacity                                           ProtocolIE-ID ::= 86

    id-RepetitionPeriod                                                 ProtocolIE-ID ::= 87

    id-ResetType                                                          ProtocolIE-ID ::= 88

    id-RoutingID                                                          ProtocolIE-ID ::= 89

    id-RRCEstablishmentCause                                     ProtocolIE-ID ::= 90

    id-RRCInactiveTransitionReportRequest                    ProtocolIE-ID ::= 91

    id-RRCState                                                          ProtocolIE-ID ::= 92

    id-SecurityContext                                                 ProtocolIE-ID ::= 93

    id-SecurityKey                                                       ProtocolIE-ID ::= 94

    id-SerialNumber                                                    ProtocolIE-ID ::= 95

    id-ServedGUAMIList                                               ProtocolIE-ID ::= 96

    id-SliceSupportList                                                 ProtocolIE-ID ::= 97

    id-SONConfigurationTransferDL                               ProtocolIE-ID ::= 98

    id-SONConfigurationTransferUL                               ProtocolIE-ID ::= 99

    id-SourceAMF-UE-NGAP-ID                                     ProtocolIE-ID ::= 100

    id-SourceToTarget-TransparentContainer                  ProtocolIE-ID ::= 101

    id-SupportedTAList                                                ProtocolIE-ID ::= 102

    id-TAIListForPaging                                                ProtocolIE-ID ::= 103

    id-TAIListForRestart                                               ProtocolIE-ID ::= 104

    id-TargetID                                                           ProtocolIE-ID ::= 105

    id-TargetToSource-TransparentContainer                 ProtocolIE-ID ::= 106

    id-TimeToWait                                                       ProtocolIE-ID ::= 107

    id-TraceActivation                                                 ProtocolIE-ID ::= 108

    id-TraceCollectionEntityIPAddress                           ProtocolIE-ID ::= 109

    id-UEAggregateMaximumBitRate                            ProtocolIE-ID ::= 110

    id-UE-associatedLogicalNG-connectionList               ProtocolIE-ID ::= 111

    id-UEContextRequest                                             ProtocolIE-ID ::= 112

    id-UE-NGAP-IDs                                                    ProtocolIE-ID ::= 114

    id-UEPagingIdentity                                               ProtocolIE-ID ::= 115

    id-UEPresenceInAreaOfInterestList                          ProtocolIE-ID ::= 116

    id-UERadioCapability                                              ProtocolIE-ID ::= 117

    id-UERadioCapabilityForPaging                                ProtocolIE-ID ::= 118

    id-UESecurityCapabilities                                        ProtocolIE-ID ::= 119

    id-UnavailableGUAMIList                                        ProtocolIE-ID ::= 120

    id-UserLocationInformation                                    ProtocolIE-ID ::= 121

    id-WarningAreaList                                                ProtocolIE-ID ::= 122

    id-WarningMessageContents                                   ProtocolIE-ID ::= 123

    id-WarningSecurityInfo                                           ProtocolIE-ID ::= 124

    id-WarningType                                                     ProtocolIE-ID ::= 125

    id-AdditionalUL-NGU-UP-TNLInformation                  ProtocolIE-ID ::= 126

    id-DataForwardingNotPossible                                 ProtocolIE-ID ::= 127

    id-DL-NGU-UP-TNLInformation                                ProtocolIE-ID ::= 128

    id-NetworkInstance                                                ProtocolIE-ID ::= 129

    id-PDUSessionAggregateMaximumBitRate                ProtocolIE-ID ::= 130

    id-PDUSessionResourceFailedToModifyListModCfm     ProtocolIE-ID ::= 131

    id-PDUSessionResourceFailedToSetupListCxtFail        ProtocolIE-ID ::= 132

    id-PDUSessionResourceListCxtRelReq                       ProtocolIE-ID ::= 133

    id-PDUSessionType                                                 ProtocolIE-ID ::= 134

    id-QosFlowAddOrModifyRequestList                          ProtocolIE-ID ::= 135

    id-QosFlowSetupRequestList                                    ProtocolIE-ID ::= 136

    id-QosFlowToReleaseList                                          ProtocolIE-ID ::= 137

    id-SecurityIndication                                               ProtocolIE-ID ::= 138

    id-UL-NGU-UP-TNLInformation                                 ProtocolIE-ID ::= 139

    id-UL-NGU-UP-TNLModifyList                                    ProtocolIE-ID ::= 140

    id-WarningAreaCoordinates                                     ProtocolIE-ID ::= 141

    id-PDUSessionResourceSecondaryRATUsageList         ProtocolIE-ID ::= 142

    id-HandoverFlag                                                     ProtocolIE-ID ::= 143

    id-SecondaryRATUsageInformation                           ProtocolIE-ID ::= 144

    id-PDUSessionResourceReleaseResponseTransfer       ProtocolIE-ID ::= 145

    id-RedirectionVoiceFallback                                      ProtocolIE-ID ::= 146

    id-UERetentionInformation                                      ProtocolIE-ID ::= 147

    id-S-NSSAI                                                            ProtocolIE-ID ::= 148

    id-PSCellInformation                                               ProtocolIE-ID ::= 149

    id-LastEUTRAN-PLMNIdentity                                   ProtocolIE-ID ::= 150

    id-MaximumIntegrityProtectedDataRate-DL               ProtocolIE-ID ::= 151

    id-AdditionalDLForwardingUPTNLInformation             ProtocolIE-ID ::= 152

    id-AdditionalDLUPTNLInformationForHOList               ProtocolIE-ID ::= 153

    id-AdditionalNGU-UP-TNLInformation                        ProtocolIE-ID ::= 154

    id-AdditionalDLQosFlowPerTNLInformation                ProtocolIE-ID ::= 155

    id-SecurityResult                                                    ProtocolIE-ID ::= 156

    id-ENDC-SONConfigurationTransferDL                       ProtocolIE-ID ::= 157

    id-ENDC-SONConfigurationTransferUL                       ProtocolIE-ID ::= 158

    id-OldAssociatedQosFlowList-ULendmarkerexpected   ProtocolIE-ID ::= 159

    id-CNTypeRestrictionsForEquivalent                          ProtocolIE-ID ::= 160

    id-CNTypeRestrictionsForServing                              ProtocolIE-ID ::= 161

    id-NewGUAMI                                                         ProtocolIE-ID ::= 162

    id-ULForwarding                                                     ProtocolIE-ID ::= 163

    id-ULForwardingUP-TNLInformation                          ProtocolIE-ID ::= 164

    id-CNAssistedRANTuning                                         ProtocolIE-ID ::= 165

    id-CommonNetworkInstance                                   ProtocolIE-ID ::= 166

    id-NGRAN-TNLAssociationToRemoveList                    ProtocolIE-ID ::= 167

    id-TNLAssociationTransportLayerAddressNGRAN        ProtocolIE-ID ::= 168

    id-EndpointIPAddressAndPort                                   ProtocolIE-ID ::= 169

    id-LocationReportingAdditionalInfo                           ProtocolIE-ID ::= 170

    id-SourceToTarget-AMFInformationReroute                ProtocolIE-ID ::= 171

    id-AdditionalULForwardingUPTNLInformation             ProtocolIE-ID ::= 172

    id-SCTP-TLAs                                                          ProtocolIE-ID ::= 173

    id-DataForwardingResponseERABList                        ProtocolIE-ID ::= 174

    id-RIMInformationTransfer                                       ProtocolIE-ID ::= 175

    id-GUAMIType                                                        ProtocolIE-ID ::= 176

    id-SRVCCOperationPossible                                      ProtocolIE-ID ::= 177

    id-TargetRNC-ID                                                      ProtocolIE-ID ::= 178

    id-RAT-Information                                                  ProtocolIE-ID ::= 179

    id-ExtendedRATRestrictionInformation                       ProtocolIE-ID ::= 180

    id-QosMonitoringRequest                                          ProtocolIE-ID ::= 181

    id-SgNB-UE-X2AP-ID                                                ProtocolIE-ID ::= 182

    id-AdditionalRedundantDL-NGU-UP-TNLInformation    ProtocolIE-ID ::= 183

    id-AdditionalRedundantDLQosFlowPerTNLInformation  ProtocolIE-ID ::= 184

    id-AdditionalRedundantNGU-UP-TNLInformation         ProtocolIE-ID ::= 185

    id-AdditionalRedundantUL-NGU-UP-TNLInformation     ProtocolIE-ID ::= 186

    id-CNPacketDelayBudgetDL                                      ProtocolIE-ID ::= 187

    id-CNPacketDelayBudgetUL                                      ProtocolIE-ID ::= 188

    id-ExtendedPacketDelayBudget                                 ProtocolIE-ID ::= 189

    id-RedundantCommonNetworkInstance                     ProtocolIE-ID ::= 190

    id-RedundantDL-NGU-TNLInformationReused             ProtocolIE-ID ::= 191

    id-RedundantDL-NGU-UP-TNLInformation                   ProtocolIE-ID ::= 192

    id-RedundantDLQosFlowPerTNLInformation                ProtocolIE-ID ::= 193

    id-RedundantQosFlowIndicator                                  ProtocolIE-ID ::= 194

    id-RedundantUL-NGU-UP-TNLInformation                   ProtocolIE-ID ::= 195

    id-TSCTrafficCharacteristics                                       ProtocolIE-ID ::= 196

    id-RedundantPDUSessionInformation                         ProtocolIE-ID ::= 197

    id-UsedRSNInformation                                            ProtocolIE-ID ::= 198

    id-IAB-Authorized                                                    ProtocolIE-ID ::= 199

    id-IAB-Supported                                                     ProtocolIE-ID ::= 200

    id-IABNodeIndication                                                ProtocolIE-ID ::= 201

    id-NB-IoT-PagingDRX                                                ProtocolIE-ID ::= 202

    id-NB-IoT-Paging-eDRXInfo                                       ProtocolIE-ID ::= 203

    id-NB-IoT-DefaultPagingDRX                                      ProtocolIE-ID ::= 204

    id-Enhanced-CoverageRestriction                               ProtocolIE-ID ::= 205

    id-Extended-ConnectedTime                                      ProtocolIE-ID ::= 206

    id-PagingAssisDataforCEcapabUE                               ProtocolIE-ID ::= 207

    id-WUS-Assistance-Information                                  ProtocolIE-ID ::= 208

    id-UE-DifferentiationInfo                                            ProtocolIE-ID ::= 209

    id-NB-IoT-UEPriority                                                  ProtocolIE-ID ::= 210

    id-UL-CP-SecurityInformation                                     ProtocolIE-ID ::= 211

    id-DL-CP-SecurityInformation                                     ProtocolIE-ID ::= 212

    id-TAI                                                                       ProtocolIE-ID ::= 213

    id-UERadioCapabilityForPagingOfNB-IoT                      ProtocolIE-ID ::= 214

    id-LTEV2XServicesAuthorized                                     ProtocolIE-ID ::= 215

    id-NRV2XServicesAuthorized                                      ProtocolIE-ID ::= 216

    id-LTEUESidelinkAggregateMaximumBitrate                 ProtocolIE-ID ::= 217

    id-NRUESidelinkAggregateMaximumBitrate                  ProtocolIE-ID ::= 218

    id-PC5QoSParameters                                               ProtocolIE-ID ::= 219

    id-AlternativeQoSParaSetList                                      ProtocolIE-ID ::= 220

    id-CurrentQoSParaSetIndex                                       ProtocolIE-ID ::= 221

    id-CEmodeBrestricted                                                ProtocolIE-ID ::= 222

    id-PagingeDRXInformation                                         ProtocolIE-ID ::= 223

    id-CEmodeBSupport-Indicator                                    ProtocolIE-ID ::= 224

    id-LTEM-Indication                                                    ProtocolIE-ID ::= 225

    id-EndIndication                                                       ProtocolIE-ID ::= 226

    id-EDT-Session                                                         ProtocolIE-ID ::= 227

    id-UECapabilityInfoRequest                                       ProtocolIE-ID ::= 228

    id-PDUSessionResourceFailedToResumeListRESReq      ProtocolIE-ID ::= 229

    id-PDUSessionResourceFailedToResumeListRESRes      ProtocolIE-ID ::= 230

    id-PDUSessionResourceSuspendListSUSReq                ProtocolIE-ID ::= 231

    id-PDUSessionResourceResumeListRESReq                 ProtocolIE-ID ::= 232

    id-PDUSessionResourceResumeListRESRes                 ProtocolIE-ID ::= 233

    id-UE-UP-CIoT-Support                                             ProtocolIE-ID ::= 234

    id-Suspend-Request-Indication                                  ProtocolIE-ID ::= 235

    id-Suspend-Response-Indication                               ProtocolIE-ID ::= 236

    id-RRC-Resume-Cause                                              ProtocolIE-ID ::= 237

    id-RGLevelWirelineAccessCharacteristics                     ProtocolIE-ID ::= 238

    id-W-AGFIdentityInformation                                     ProtocolIE-ID ::= 239

    id-GlobalTNGF-ID                                                     ProtocolIE-ID ::= 240

    id-GlobalTWIF-ID                                                     ProtocolIE-ID ::= 241

    id-GlobalW-AGF-ID                                                   ProtocolIE-ID ::= 242

    id-UserLocationInformationW-AGF                             ProtocolIE-ID ::= 243

    id-UserLocationInformationTNGF                               ProtocolIE-ID ::= 244

    id-AuthenticatedIndication                                        ProtocolIE-ID ::= 245

    id-TNGFIdentityInformation                                      ProtocolIE-ID ::= 246

    id-TWIFIdentityInformation                                       ProtocolIE-ID ::= 247

    id-UserLocationInformationTWIF                               ProtocolIE-ID ::= 248

    id-SelectedPLMNIdentity                                           ProtocolIE-ID ::= 249

    id-IntersystemSONConfigurationTransferDL                ProtocolIE-ID ::= 250

    id-IntersystemSONConfigurationTransferUL                ProtocolIE-ID ::= 251

    id-SONInformationReport                                         ProtocolIE-ID ::= 252

    id-UEHistoryInformationFromTheUE                          ProtocolIE-ID ::= 253

    id-ManagementBasedMDTPLMNList                           ProtocolIE-ID ::= 254

    id-MDTConfiguration                                                ProtocolIE-ID ::= 255

    id-PrivacyIndicator                                                  ProtocolIE-ID ::= 256

    id-TraceCollectionEntityURI                                       ProtocolIE-ID ::= 257

    id-NPN-Support                                                       ProtocolIE-ID ::= 258

    id-NPN-AccessInformation                                       ProtocolIE-ID ::= 259

    id-NPN-PagingAssistanceInformation                        ProtocolIE-ID ::= 260

    id-NPN-MobilityInformation                                      ProtocolIE-ID ::= 261

    id-TargettoSource-Failure-TransparentContainer         ProtocolIE-ID ::= 262

    id-NID                                                                   ProtocolIE-ID ::= 263

    id-UERadioCapabilityID                                            ProtocolIE-ID ::= 264

    id-UERadioCapability-EUTRA-Format                         ProtocolIE-ID ::= 265

    id-DAPSRequestInfo                                                ProtocolIE-ID ::= 266

    id-DAPSResponseInfoList                                         ProtocolIE-ID ::= 267

    id-EarlyStatusTransfer-TransparentContainer             ProtocolIE-ID ::= 268

    id-NotifySourceNGRANNode                                     ProtocolIE-ID ::= 269

    id-ExtendedSliceSupportList                                    ProtocolIE-ID ::= 270

    id-ExtendedTAISliceSupportList                                ProtocolIE-ID ::= 271

^ Back to Top

© 2024 Spirent Communications Inc. All Rights Reserved.