Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 38.413  Word version:  18.1.0

Top   Top   Up   Prev   Next
1…   4…   8…   8.2…   8.2.3…   8.3…   8.3.4…   8.4…   8.4.3…   8.5…   8.7…   8.8…   8.10…   8.12…   8.17…   9…   9.2…   9.2.2…   9.2.3…   9.2.4…   9.2.6…   9.2.7…   9.2.9…   9.2.11…   9.2.16…   9.2.17…   9.3…   9.3.1.21…   9.3.1.41…   9.3.1.61…   9.3.1.81…   9.3.1.101…   9.3.1.121…   9.3.1.141…   9.3.1.161…   9.3.1.181…   9.3.1.205…   9.3.1.222…   9.3.1.245…   9.3.2…   9.3.3…   9.3.3.21…   9.3.3.42…   9.3.4…   9.3.4.10…   9.3.5…   9.4…   9.4.4   9.4.5   9.4.6…   9.5…   10…

 

9.2.6  Interface Management Messagesp. 176

9.2.6.1  NG SETUP REQUESTp. 176

This message is sent by the NG-RAN node to transfer application layer information for an NG-C interface instance.
Direction:
NG-RAN node → AMF
IE/Group Name Pre­sence Range IE type and refe­rence Semantics description Criti­cality Assi­gned Criti­cality
Message TypeM 9.3.1.1YESreject
Global RAN Node IDM 9.3.1.5YESreject
RAN Node NameOPrintableString
(SIZE(1..150, …))
YESignore
Supported TA List1Supported TAs in the NG-RAN node.YESreject
>Supported TA Item1..<maxnoofTACs>-
>>TACM 9.3.3.10Broadcast TAC-
>>Broadcast PLMN List1-
>>>Broadcast PLMN Item1..<maxnoofBPLMNs>-
>>>>PLMN IdentityM 9.3.3.5Broadcast PLMN-
>>>>TAI Slice Support ListMSlice Support List
9.3.1.17
Supported S-NSSAIs per TAC, per PLMN or per SNPN.-
>>>>NPN SupportO 9.3.3.44If the NID IE is included, it identifies a SNPN together with the PLMN Identity IE.YESreject
>>>>Extended TAI Slice Support ListOExtended Slice Support List
9.3.1.191
Additional Supported S-NSSAIs per TAC, per PLMN or per SNPN.YESreject
>>>>TAI NSAG Support ListO 9.3.1.238NSAG information associated with the slices per TAC, per PLMN or per SNPN.YESignore
>>Configured TAC IndicationO 9.3.3.50YESignore
>>RAT InformationO 9.3.1.125RAT information associated with the TAC of the indicated PLMN(s).YESreject
Default Paging DRXMPaging DRX
9.3.1.90
YESignore
UE Retention InformationO 9.3.1.117YESignore
NB-IoT Default Paging DRXO 9.3.1.137YESignore
Extended RAN Node NameO 9.3.1.193YESignore
Range bound Explanation
maxnoofTACsMaximum no. of TACs. Value is 256.
maxnoofBPLMNsMaximum no. of Broadcast PLMNs. Value is 12.
Up

9.2.6.2  NG SETUP RESPONSEp. 177

This message is sent by the AMF to transfer application layer information for an NG-C interface instance.
Direction:
AMF → NG-RAN node
IE/Group Name Pre­sence Range IE type and refe­rence Semantics description Criti­cality Assi­gned Criti­cality
Message TypeM 9.3.1.1YESreject
AMF NameM 9.3.3.21YESreject
Served GUAMI List1YESreject
>Served GUAMI Item1..<maxnoofServedGUAMIs>-
>>GUAMIM 9.3.3.3-
>>Backup AMF NameOAMF Name
9.3.3.21
-
>>GUAMI TypeOENUMERATED (native, mapped, …)YESignore
Relative AMF CapacityM 9.3.1.32YESignore
PLMN Support List1YESreject
>PLMN Support Item1..<maxnoofPLMNs>-
>>PLMN IdentityM 9.3.3.5-
>>Slice Support ListM 9.3.1.17Supported S-NSSAIs per PLMN or per SNPN.-
>>NPN SupportO 9.3.3.44If NID IE is included, it identifies a SNPN together with the PLMN Identity IE.YESreject
>>Extended Slice Support ListO 9.3.1.191Additional Supported S-NSSAIs per PLMN or per SNPN.YESreject
>>Onboarding SupportOENUMERATED (true, ...)Indication of onboarding support.YESignore
Criticality DiagnosticsO 9.3.1.3YESignore
UE Retention InformationO 9.3.1.117YESignore
IAB SupportedOENUMERATED (true, ...)Indication of support for IAB.YESignore
Extended AMF NameO 9.3.3.51YESignore
Mobile IAB SupportedOENUMERATED (true, ...)Indication of support for mobile IAB.YESignore
Range bound Explanation
maxnoofServedGUAMIsMaximum no. of GUAMIs served by an AMF. Value is 256.
maxnoofPLMNsMaximum no. of PLMNs per message. Value is 12.
Up

9.2.6.3  NG SETUP FAILUREp. 178

This message is sent by the AMF to indicate NG setup failure.
Direction:
AMF → NG-RAN node
IE/Group Name Pre­sence Range IE type and refe­rence Semantics description Criti­cality Assi­gned Criti­cality
Message TypeM 9.3.1.1YESreject
CauseM 9.3.1.2YESignore
Time to WaitO 9.3.1.56YESignore
Criticality DiagnosticsO 9.3.1.3YESignore
Up

9.2.6.4  RAN CONFIGURATION UPDATEp. 178

This message is sent by the NG-RAN node to transfer updated application layer information for an NG-C interface instance.
Direction:
NG-RAN node → AMF
IE/Group Name Pre­sence Range IE type and refe­rence Semantics description Criti­cality Assi­gned Criti­cality
Message TypeM 9.3.1.1YESreject
RAN Node NameOPrintableString
(SIZE(1..150, …))
YESignore
Supported TA List0..1Supported TAs in the NG-RAN node.YESreject
>Supported TA Item1..<maxnoofTACs>-
>>TACM 9.3.3.10Broadcast TAC-
>>Broadcast PLMN List1-
>>>Broadcast PLMN Item1..<maxnoofBPLMNs>-
>>>>PLMN IdentityM 9.3.3.5Broadcast PLMN-
>>>>TAI Slice Support ListMSlice Support List
9.3.1.17
Supported S-NSSAIs per TAC, per PLMN or per SNPN.-
>>>>NPN SupportO 9.3.3.44If the NID IE is included, it identifies a SNPN together with the PLMN Identity IE.YESreject
>>>>Extended TAI Slice Support ListOExtended Slice Support List
9.3.1.191
Additional Supported S-NSSAIs per TAC, per PLMN or per SNPN.YESreject
>>>>TAI NSAG Support ListO 9.3.1.238NSAG information associated with the slices per TAC, per PLMN or per SNPN.YESignore
>>Configured TAC IndicationO 9.3.3.50YESignore
>>RAT InformationO 9.3.1.125RAT information associated with the TAC of the indicated PLMN(s).YESreject
Default Paging DRXOPaging DRX
9.3.1.90
YESignore
Global RAN Node IDO 9.3.1.5YESignore
NG-RAN TNL Association to Remove List 0..1YESreject
>NG-RAN TNL Association to Remove Item1..<maxnoofTNLAssociations>-
>>TNL Association Transport Layer Address MCP Transport Layer Information
9.3.2.6
Transport layer address of the NG-RAN node.-
>>TNL Association Transport Layer Address at AMFOCP Transport Layer Information
9.3.2.6
Transport layer address of the AMF.-
NB-IoT Default Paging DRXO 9.3.1.137YESignore
Extended RAN Node NameO 9.3.1.193YESignore
Range bound Explanation
maxnoofTACsMaximum no. of TACs. Value is 256.
maxnoofBPLMNsMaximum no. of Broadcast PLMNs. Value is 12.
maxnoofTNLAssociationsMaximum no. of TNL Associations between the NG-RAN node and the AMF. Value is 32.
Up

9.2.6.5  RAN CONFIGURATION UPDATE ACKNOWLEDGEp. 180

This message is sent by the AMF to acknowledge the NG-RAN node transfer of updated information for an NG-C interface instance.
Direction:
AMF → NG-RAN node
IE/Group Name Pre­sence Range IE type and refe­rence Semantics description Criti­cality Assi­gned Criti­cality
Message TypeM 9.3.1.1YESreject
Criticality DiagnosticsO 9.3.1.3YESignore
Up

9.2.6.6  RAN CONFIGURATION UPDATE FAILUREp. 180

This message is sent by the AMF to indicate RAN configuration update failure.
Direction:
AMF → NG-RAN node
IE/Group Name Pre­sence Range IE type and refe­rence Semantics description Criti­cality Assi­gned Criti­cality
Message TypeM 9.3.1.1YESreject
CauseM 9.3.1.2YESignore
Time to WaitO 9.3.1.56YESignore
Criticality DiagnosticsO 9.3.1.3YESignore
Up

9.2.6.7  AMF CONFIGURATION UPDATEp. 180

This message is sent by the AMF to transfer updated information for an NG-C interface instance.
Direction:
AMF → NG-RAN node
IE/Group Name Pre­sence Range IE type and refe­rence Semantics description Criti­cality Assi­gned Criti­cality
Message TypeM 9.3.1.1YESreject
AMF NameO 9.3.3.21YESreject
Served GUAMI List0..1YESreject
>Served GUAMI Item1..<maxnoofServedGUAMIs>-
>>GUAMIM 9.3.3.3-
>>Backup AMF NameOAMF Name
9.3.3.21
-
>>GUAMI TypeOENUMERATED (native, mapped, …)YESignore
Relative AMF CapacityO 9.3.1.32YESignore
PLMN Support List0..1YESreject
>PLMN Support Item1..<maxnoofPLMNs>-
>>PLMN IdentityM 9.3.3.5-
>>Slice Support ListM 9.3.1.17Supported S-NSSAIs per PLMN or per SNPN.-
>>NPN SupportO 9.3.3.44If the NID IE is included, it identifies a SNPN together with the PLMN Identity IE.YESreject
>>Extended Slice Support ListO 9.3.1.191Additional Supported S-NSSAIs per PLMN or per SNPN.YESreject
>>Onboarding SupportOENUMERATED (true, ...)Indication of onboarding support.YESignore
AMF TNL Association to Add List 0..1YESignore
>AMF TNL Association to Add Item1..<maxnoofTNLAssociations>-
>>AMF TNL Association AddressMCP Transport Layer Information
9.3.2.6
AMF Transport Layer information used to set up the new TNL association.-
>>TNL Association UsageO 9.3.2.9-
>>TNL Address Weight FactorM 9.3.2.10-
AMF TNL Association to Remove List 0..1YESignore
>AMF TNL Association to Remove Item1..<maxnoofTNLAssociations>-
>>AMF TNL Association AddressMCP Transport Layer Information
9.3.2.6
Transport Layer Address of the AMF.-
>>TNL Association Transport Layer Address NG-RANOCP Transport Layer Address
9.3.2.6
Transport Layer Address of the NG-RAN node.YESreject
AMF TNL Association to Update List 0..1YESignore
>AMF TNL Association to Update Item1..<maxnoofTNLAssociations>-
>>AMF TNL Association AddressMCP Transport Layer Information
9.3.2.6
AMF Transport Layer information used to identify the TNL association to be updated.-
>>TNL Association UsageO 9.3.2.9-
>>TNL Address Weight FactorO 9.3.2.10-
Extended AMF NameO 9.3.3.51YESignore
Range bound Explanation
maxnoofServedGUAMIsMaximum no. of GUAMIs served by an AMF. Value is 256.
maxnoofPLMNsMaximum no. of PLMNs per message. Value is 12.
maxnoofTNLAssociationsMaximum no. of TNL Associations between the NG-RAN node and the AMF. Value is 32.
Up

9.2.6.8  AMF CONFIGURATION UPDATE ACKNOWLEDGEp. 182

This message is sent by the NG-RAN node to acknowledge the AMF transfer of updated information for an NG-C interface instance.
Direction:
NG-RAN node → AMF
IE/Group Name Pre­sence Range IE type and refe­rence Semantics description Criti­cality Assi­gned Criti­cality
Message TypeM 9.3.1.1YESreject
AMF TNL Association Setup List 0..1YESignore
>AMF TNL Association Setup Item1..<maxnoofTNLAssociations>-
>>AMF TNL Association AddressMCP Transport Layer Information
9.3.2.6
Previously received AMF Transport Layer information for the TNL association.-
AMF TNL Association Failed to Setup List OTNL Association List
9.3.2.7
YESignore
Criticality DiagnosticsO 9.3.1.3YESignore
Range bound Explanation
maxnoofTNLAssociationsMaximum no. of TNL Associations between the NG-RAN node and the AMF. Value is 32.
Up

9.2.6.9  AMF CONFIGURATION UPDATE FAILUREp. 182

This message is sent by the NG-RAN node to indicate AMF configuration update failure.
Direction:
NG-RAN node → AMF
IE/Group Name Pre­sence Range IE type and refe­rence Semantics description Criti­cality Assi­gned Criti­cality
Message TypeM 9.3.1.1YESreject
CauseM 9.3.1.2YESignore
Time to WaitO 9.3.1.56YESignore
Criticality DiagnosticsO 9.3.1.3YESignore
Up

9.2.6.10  AMF STATUS INDICATIONp. 183

This message is sent by the AMF to support AMF management functions.
Direction:
AMF → NG-RAN node
IE/Group Name Pre­sence Range IE type and refe­rence Semantics description Criti­cality Assi­gned Criti­cality
Message TypeM 9.3.1.1YESignore
Unavailable GUAMI List1Indicates the GUAMIs configured to be unavailable at the AMFYESreject
>Unavailable GUAMI Item1..<maxnoofServedGUAMIs>-
>>GUAMIM 9.3.3.3-
>>Timer Approach for GUAMI RemovalOENUMERATED (apply timer, ...)-
>>Backup AMF NameOAMF Name
9.3.3.21
-
Range bound Explanation
maxnoofServedGUAMIsMaximum no. of GUAMIs served by an AMF. Value is 256.
Up

9.2.6.11  NG RESETp. 183

This message is sent by both the NG-RAN node and the AMF to request that the NG interface, or parts of the NG interface, be reset.
Direction:
NG-RAN node → AMF and AMF → NG-RAN node
IE/Group Name Pre­sence Range IE type and refe­rence Semantics description Criti­cality Assi­gned Criti­cality
Message TypeM 9.3.1.1YESreject
CauseM 9.3.1.2YESignore
CHOICE Reset TypeMYESreject
>NG interface
>>Reset AllMENUMERATED (Reset all, …)-
>Part of NG interface
>>UE-associated Logical NG-connection ListM 9.3.3.25-
Up

9.2.6.12  NG RESET ACKNOWLEDGEp. 183

This message is sent by both the NG-RAN node and the AMF as a response to an NG RESET message.
Direction:
NG-RAN node → AMF and AMF → NG-RAN node
IE/Group Name Pre­sence Range IE type and refe­rence Semantics description Criti­cality Assi­gned Criti­cality
Message TypeM 9.3.1.1YESreject
UE-associated Logical NG-connection ListO 9.3.3.25YESignore
Criticality DiagnosticsO 9.3.1.3YESignore
Up

9.2.6.13  ERROR INDICATIONp. 184

This message is sent by both the NG-RAN node and the AMF to indicate that some error has been detected in the node.
Direction:
NG-RAN node → AMF and AMF → NG-RAN node
IE/Group Name Pre­sence Range IE type and refe­rence Semantics description Criti­cality Assi­gned Criti­cality
Message TypeM 9.3.1.1YESignore
AMF UE NGAP IDO 9.3.3.1YESignore
RAN UE NGAP IDO 9.3.3.2YESignore
CauseO 9.3.1.2YESignore
Criticality Diagnostics O 9.3.1.3YESignore
5G-S-TMSIO 9.3.3.20YESignore
Up

9.2.6.14  OVERLOAD STARTp. 184

This message is sent by the AMF and is used to indicate to the NG-RAN node that the AMF is overloaded.
Direction:
AMF → NG-RAN node
IE/Group Name Pre­sence Range IE type and refe­rence Semantics description Criti­cality Assi­gned Criti­cality
Message TypeM 9.3.1.1YESignore
AMF Overload ResponseOOverload Response
9.3.1.104
YESreject
AMF Traffic Load Reduction IndicationOTraffic Load Reduction Indication
9.3.1.106
YESignore
Overload Start NSSAI List0..1YESignore
>Overload Start NSSAI Item1..<maxnoofSliceItems>-
>>Slice Overload ListM 9.3.1.107-
>>Slice Overload ResponseOOverload Response
9.3.1.104
-
>>Slice Traffic Load Reduction IndicationOTraffic Load Reduction Indication
9.3.1.106
-
Range bound Explanation
maxnoofSliceItemsMaximum no. of signalled slice support items. Value is 1024.
Up

9.2.6.15  OVERLOAD STOPp. 184

This message is sent by the AMF and is used to indicate that the AMF is no longer overloaded.
Direction:
AMF → NG-RAN node
IE/Group Name Pre­sence Range IE type and refe­rence Semantics description Criti­cality Assi­gned Criti­cality
Message TypeM 9.3.1.1YESreject
Up

Up   Top   ToC