Content for  TS 38.413  Word version:  17.6.0

The purpose of the NG Setup procedure is to exchange application level data needed for the NG-RAN node and the AMF to correctly interoperate on the NG-C interface. This procedure shall be the first NGAP procedure triggered after the TNL association has become operational. The procedure uses non-UE associated signalling. This procedure erases any existing application level configuration data in the two nodes, replaces it by the one received and clears AMF overload state information at the NG-RAN node. If the NG-RAN node and AMF do not agree on retaining the UE contexts this procedure also re-initialises the NGAP UE-related contexts (if any) and erases all related signalling connections in the two nodes like an NG Reset procedure would do.

The NG-RAN node initiates the procedure by sending an NG SETUP REQUEST message including the appropriate data to the AMF. The AMF responds with an NG SETUP RESPONSE message including the appropriate data. 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 AMF supports IAB, the AMF shall include the IAB Supported IE in the NG SETUP RESPONSE message. If the IAB Supported IE is included in the NG SETUP RESPONSE message, the NG-RAN node shall, if supported, store this information and use it for further AMF selection for the IAB-MT. 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 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 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 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. 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. If the Onboarding Support IE is also included within the same PLMN Support Item IE, the NG-RAN node shall, if supported, consider that the AMF supports UE onboarding for the identified SNPN, as specified in TS 23.501. If the TAI NSAG Support List IE is included in the Broadcast PLMN Item IE in the NG SETUP REQUEST message, the AMF shall, if supported, use this information as specified in TS 23.501.

If the AMF cannot accept the setup, it should respond with an NG SETUP FAILURE message and appropriate cause value. If the NG SETUP FAILURE message includes the Time to Wait IE, the NG-RAN node shall wait at least for the indicated time before reinitiating the NG Setup procedure towards the same AMF.

If the AMF does not identify any of the PLMNs/SNPNs indicated in the NG SETUP REQUEST message, it shall reject the NG Setup procedure with an appropriate cause value. If none of the RATs indicated by the NG-RAN node in the NG SETUP REQUEST message is supported by the AMF, then the AMF shall fail the NG Setup procedure with an appropriate cause value.

The purpose of the RAN Configuration Update procedure is to update application level configuration data needed for the NG-RAN node and the AMF to interoperate correctly on the NG-C interface. This procedure does not affect existing UE-related contexts, if any. The procedure uses non UE-associated signalling.

The NG-RAN node initiates the procedure by sending a RAN CONFIGURATION UPDATE message to the AMF including an appropriate set of updated configuration data that it has just taken into operational use. The AMF responds with a RAN CONFIGURATION UPDATE ACKNOWLEDGE message to acknowledge that it successfully updated the configuration data. If an information element is not included in the RAN CONFIGURATION UPDATE message, the AMF shall interpret that the corresponding configuration data is not changed and shall continue to operate the NG-C interface with the existing related configuration data. If the Supported TA List IE is included in the RAN CONFIGURATION UPDATE message, the AMF shall overwrite the whole list of supported TAs and the corresponding list of supported slices for each TA, and use them for subsequent registration area management of the UE. If the Configured TAC Indication IE set to "true" is included for a Tracking Area contained in the Supported TA List IE in the RAN CONFIGURATION UPDATE message, the AMF may take it into account to optimise NG-C signalling towards this NG-RAN node. If the Global RAN Node ID IE is included in the RAN CONFIGURATION UPDATE message, the AMF shall associate the TNLA to the NG-C interface instance using the Global RAN Node ID. If the RAN CONFIGURATION UPDATE message includes the NG-RAN TNL Association to Remove List IE, the AMF shall, if supported, initiate removal of the TNL association(s) indicated by NG-RAN TNL endpoint(s) and AMF TNL endpoint(s) if the TNL Association Transport Layer Address at AMF IE is present, or the TNL association(s) indicated by NG-RAN TNL endpoint(s) if the TNL Association Transport Layer Address at AMF IE is absent:

• if the received TNL Association Transport Layer Address IE includes the Port Number IE, the NG-RAN TNL endpoint is identified by the Endpoint IP Address IE and the Port Number IE. Otherwise, the NG-RAN TNL endpoints correspond to all NG-RAN TNL endpoints identified by the Endpoint IP Address IE and any port number(s).
• if the received TNL Association Transport Layer Address at AMF IE includes the Port Number IE, the AMF TNL endpoint is identified by the Endpoint IP Address IE and the Port Number IE. Otherwise, the AMF TNL endpoints correspond to all AMF TNL endpoints identified by the Endpoint IP Address IE and any port number(s).

If the RAN CONFIGURATION UPDATE message includes the RAN Node Name IE, the AMF may store it or update this IE value if already stored, and use it as a human readable name of the NG-RAN node. If the RAN CONFIGURATION UPDATE message includes the Extended RAN Node Name IE, the AMF may store it or update this IE value if already stored, and use it 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 RAN CONFIGURATION UPDATE message, the AMF shall overwrite any previously stored NB-IoT default paging DRX value for the NG-RAN node. If the RAT Information IE is included in the RAN CONFIGURATION UPDATE 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 RAN CONFIGURATION UPDATE 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. If the TAI NSAG Support List IE is included in the Broadcast PLMN Item IE in the RAN CONFIGURATION UPDATE message, the AMF shall, if supported, use this information as specified in TS 23.501.

If the AMF cannot accept the update, it shall respond with a RAN CONFIGURATION UPDATE FAILURE message and appropriate cause value. If the Time to Wait IE is included in the RAN CONFIGURATION UPDATE FAILURE message, the NG-RAN node shall wait at least for the indicated time before reinitiating the RAN Configuration Update procedure towards the same AMF.

If the NG-RAN node, after initiating the RAN Configuration Update procedure, receives neither a RAN CONFIGURATION UPDATE ACKOWLEDGE nor a RAN CONFIGURATION UPDATE FAILURE message, the NG-RAN node may reinitiate a further RAN Configuration Update procedure towards the same AMF, provided that the content of the new RAN CONFIGURATION UPDATE message is identical to the content of the previously unacknowledged RAN CONFIGURATION UPDATE message.

The purpose of the AMF Configuration Update procedure is to update application level configuration data needed for the NG-RAN node and AMF to interoperate correctly on the NG-C interface. This procedure does not affect existing UE-related contexts, if any. The procedure uses non UE-associated signalling.

The AMF initiates the procedure by sending an AMF CONFIGURATION UPDATE message including the appropriate updated configuration data to the NG-RAN node. The NG-RAN node responds with an AMF CONFIGURATION UPDATE ACKNOWLEDGE message to acknowledge that it successfully updated the configuration data. Unless stated otherwise, if an information element is not included in the AMF CONFIGURATION UPDATE message, the NG-RAN node shall interpret that the corresponding configuration data is not changed and shall continue to operate the NG-C interface with the existing related configuration data. If the PLMN Support List IE is included in the AMF CONFIGURATION UPDATE message, the NG-RAN node shall overwrite the whole list of supported PLMN/SNPN Identities and the corresponding list of AMF slices and, if present, other associated information for each PLMN/SNPN Identity and use the received values for further network slice selection and AMF selection. If the AMF TNL Association to Add List IE is included in the AMF CONFIGURATION UPDATE message, the NG-RAN node shall, if supported, use it to establish the TNL association(s) with the AMF. If the AMF TNL Association to Add List IE is included in the AMF CONFIGURATION UPDATE message, and if the AMF TNL Association Address IE does not include the Port Number IE, the NG-RAN node shall assume that port number value 38412 is used for the endpoint. The NG-RAN node shall report to the AMF, in the AMF CONFIGURATION UPDATE ACKNOWLEDGE message, the successful establishment of the TNL association(s) with the AMF as follows:

• A list of successfully established TNL associations shall be included in the AMF TNL Association Setup List IE;
• A list of TNL associations that failed to be established shall be included in the AMF TNL Association Failed to Setup List IE.

If the AMF CONFIGURATION UPDATE message includes the AMF TNL Association to Remove List IE, the NG-RAN node shall, if supported, initiate removal of the TNL association(s) indicated by AMF TNL endpoint(s) and NG-RAN node TNL endpoint(s) if the TNL Association Transport Layer Address NG-RAN IE is present, or the TNL association(s) indicated by AMF TNL endpoint(s) if the TNL Association Transport Layer Address NG-RAN IE is absent:

• if the received AMF TNL Association Address IE includes the Port Number IE, the AMF TNL endpoint is identified by the Endpoint IP Address IE and the Port Number IE. Otherwise, the AMF TNL endpoints correspond to all AMF TNL endpoints identified by the Endpoint IP Address IE and any port number(s).
• if the received TNL Association Transport Layer Address NG-RAN IE includes the Port Number IE, the NG-RAN node TNL endpoint is identified by the Endpoint IP Address IE and the Port Number IE. Otherwise, the NG-RAN node TNL endpoints correspond to all NG-RAN node TNL endpoints identified by the Endpoint IP Address IE and any port number(s).

If the AMF Name IE is included in the AMF CONFIGURATION UPDATE message, the NG-RAN node shall overwrite the previously stored AMF name and use it to identify the AMF. If the AMF CONFIGURATION UPDATE message includes the AMF Name IE, the NG-RAN node may store it or update this IE value if already stored, and use it as a human readable name of the AMF. If the AMF CONFIGURATION UPDATE message includes the Extended AMF Name IE, the NG-RAN node may store it or update this IE value if already stored, and use it as a human readable name of the AMF and shall ignore the AMF Name IE if also included. If the Served GUAMI List IE is included in the AMF CONFIGURATION UPDATE message, the NG-RAN node shall overwrite the whole list of GUAMIs served by the AMF by the new list and use the received values for further AMF management and AMF selection as defined in TS 23.501. If the Relative AMF Capacity IE is included in the AMF CONFIGURATION UPDATE message, the NG-RAN node may use it as defined in TS 23.501. If the AMF TNL Association to Update List IE is included in the AMF CONFIGURATION UPDATE message the NG-RAN node shall, if supported, update the TNL association(s) indicated by the received AMF Transport Layer information towards the AMF:

• if the received AMF TNL Association Address IE includes the Port Number IE, the AMF TNL endpoint is identified by the Endpoint IP Address IE and the Port Number IE. Otherwise, the AMF TNL endpoints correspond to all AMF TNL endpoints identified by the Endpoint IP Address IE and any port number(s).

If the TNL Association Usage IE or the TNL Address Weight Factor IE is included in the AMF TNL Association to Add List IE or the AMF TNL Association to Update List IE, the NG-RAN node shall, if supported, consider it as defined in TS 23.502. If the NID IE within the NPN Support IE is included within a PLMN Support Item IE in the AMF CONFIGURATION UPDATE message, the NG-RAN node shall consider that the AMF supports the SNPN identified by the PLMN Identity IE and the NID IE. If the Onboarding Support IE is also included within the same PLMN Support Item IE, the NG-RAN node shall, if supported, consider that the AMF supports UE onboarding for the identified SNPN, as specified in TS 23.501.

If the NG-RAN node cannot accept the update, it shall respond with an AMF CONFIGURATION UPDATE FAILURE message and appropriate cause value. If the Time to Wait IE is included in the AMF CONFIGURATION UPDATE FAILURE message, the AMF shall wait at least for the indicated time before reinitiating the AMF Configuration Update procedure towards the same NG-RAN node.

If the AMF receives neither an AMF CONFIGURATION UPDATE ACKOWLEDGE nor an AMF CONFIGURATION UPDATE FAILURE message, the AMF may reinitiate the AMF Configuration Update procedure towards the same NG-RAN node provided that the content of the new AMF CONFIGURATION UPDATE message is identical to the content of the previously unacknowledged AMF CONFIGURATION UPDATE message.

The purpose of the NG Reset procedure is to initialise or re-initialise the RAN, or part of RAN NGAP UE-related contexts, in the event of a failure in the 5GC or vice versa. This procedure does not affect the application level configuration data exchanged during, e.g., the NG Setup procedure. The procedure uses non-UE associated signalling.

Not applicable.

The Error Indication procedure is initiated by a node in order to report detected errors in one incoming message, provided they cannot be reported by an appropriate failure message. If the error situation arises due to reception of a message utilising UE-associated signalling, then the Error Indication procedure uses UE-associated signalling. Otherwise the procedure uses non-UE associated signalling.

When the conditions defined in clause 10 are fulfilled, the Error Indication procedure is initiated by an ERROR INDICATION message sent from the receiving node. The ERROR INDICATION message shall contain at least either the Cause IE or the Criticality Diagnostics IE. In case the Error Indication procedure is triggered by utilising UE-associated signalling the AMF UE NGAP ID IE and the RAN UE NGAP ID IE shall be included in the ERROR INDICATION message. If one or both of the AMF UE NGAP ID IE and the RAN UE NGAP ID IE are not correct, the cause shall be set to an appropriate value, e.g., "Unknown local UE NGAP ID" or "Inconsistent remote UE NGAP ID".

Void.

The purpose of the AMF Status Indication procedure is to support AMF management functions. The procedure uses non UE-associated signalling.

The AMF initiates the procedure by sending an AMF STATUS INDICATION message to the NG-RAN node. Upon receipt of the AMF STATUS INDICATION message, the NG-RAN node shall consider the indicated GUAMI(s) will be unavailable and perform AMF reselection as defined in TS 23.501. The NG-RAN node shall, if supported, act accordingly as specified in TS 23.501, based on the presence or absence of the Timer Approach for GUAMI Removal IE. If the Backup AMF Name IE is included in the AMF STATUS INDICATION message, the NG-RAN node shall, if supported, perform AMF reselection considering the AMF as indicated by the Backup AMF Name IE as specified in TS 23.501.

Void.

The purpose of the Overload Start procedure is to inform an NG-RAN node to reduce the signalling load towards the concerned AMF. The procedure uses non-UE associated signalling.

The NG-RAN node receiving the OVERLOAD START message shall assume the AMF from which it receives the message as being in an overloaded state. If the Overload Action IE is included the AMF Overload Response IE within the OVERLOAD START message, the NG-RAN node shall use it to identify the related signalling traffic. When the Overload Action IE is set to

• "reject RRC connection establishments for non-emergency mobile originated data transfer" (i.e., reject traffic corresponding to RRC cause "mo-data", "mo-SMS", "mo-VideoCall" and "mo-VoiceCall" in TS 38.331 or "mo-data" and "mo-VoiceCall" in TS 36.331), or
• "reject RRC connection establishments for signalling" (i.e., reject traffic corresponding to RRC cause "mo-data", "mo-SMS", "mo-signalling", "mo-VideoCall" and "mo-VoiceCall" in TS 38.331 or "mo-data", "mo-signalling" and "mo-VoiceCall" in TS 36.331), or
• "only permit RRC connection establishments for emergency sessions and mobile terminated services" (i.e., only permit traffic corresponding to RRC cause "emergency" and "mt-Access" in TS 38.331 or in TS 36.331), or
• "only permit RRC connection establishments for high priority sessions and mobile terminated services" (i.e., only permit traffic corresponding to RRC cause "highPriorityAccess", "mps-PriorityAccess", "mcs-PriorityAccess" and "mt-Access" in TS 38.331 or "highPriorityAccess", "mo-ExceptionData" and "mt-Access" in TS 36.331),

the NG-RAN node shall:

• if the AMF Traffic Load Reduction Indication IE is included in the OVERLOAD START message, reduce the signalling traffic by the indicated percentage,
• otherwise ensure that only the signalling traffic not indicated as to be rejected is sent to the AMF.

If the Overload Start NSSAI List IE is included in the OVERLOAD START message, the NG-RAN node shall:

• if the Slice Traffic Load Reduction Indication IE is present, reduce the signalling traffic by the indicated percentage for the UE(s) whose requested NSSAI only include S-NSSAI(s) contained in the Overload Start NSSAI List IE, and the signalling traffic indicated as to be reduced by the Overload Action IE in the Slice Overload Response IE if the IE is present,
• otherwise ensure that only the signalling traffic from UE(s) whose requested NSSAI includes S-NSSAI(s) other than the ones contained in the Overload Start NSSAI List IE, or the signalling traffic not indicated as to be reduced by the Overload Action IE in the Slice Overload Response IE for the UE(s) if the requested NSSAI matched, is sent to the AMF.

If an overload control is ongoing and the NG-RAN node receives a further OVERLOAD START message, the NG-RAN node shall replace the contents of the previously received information with the new one.

Void.

The purpose of the Overload Stop procedure is to signal to an NG-RAN node the AMF is connected to that the overload situation at the AMF has ended and normal operation shall resume. The procedure uses non-UE associated signalling.

The NG-RAN node receiving the OVERLOAD STOP message shall assume that the overload situation at the AMF from which it receives the message has ended and shall resume normal operation for the applicable traffic towards this AMF.

Void.