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

Content for  TS 38.423  Word version:  18.2.0

Top   Top   Up   Prev   Next
1…   4…   8…   8.2…   8.2.3…   8.3…   8.3.3…   8.3.4…   8.3.6…   8.4…   8.4.4…   8.5…   9…   9.2.3   9.3…   10… 
4 General  4.1 Procedure specification principles  4.2 Forwards and backwards compatibility  4.3 Specification notations  5 XnAP services  5.1 XnAP procedure modules  5.2 Parallel transactions  6 Services expected from signalling transport  7 Functions of XnAP 
...

 

4  General  p. 21

4.1  Procedure specification principles  p. 21

The principle for specifying the procedure logic is to specify the functional behaviour of the terminating NG-RAN node exactly and completely. Any rule that specifies the behaviour of the originating NG-RAN node shall be possible to be verified with information that is visible within the system.
The following specification principles have been applied for the procedure text in clause 8:
  • The procedure text discriminates between:
    1. Functionality which "shall" be executed
      The procedure text indicates that the receiving node "shall" perform a certain function Y under a certain condition. If the receiving node supports procedure X but cannot perform functionality Y requested in the initiating message of a Class 1 EP, the receiving node shall respond with the message used to report unsuccessful outcome for this procedure, containing an appropriate cause value.
    2. Functionality which "shall, if supported" be executed
      The procedure text indicates that the receiving node "shall, if supported," perform a certain function Y under a certain condition. If the receiving node supports procedure X, but does not support functionality Y, the receiving node shall proceed with the execution of the EP, possibly informing the requesting node about the not supported functionality.
  • Any required inclusion of an optional IE in a response message is explicitly indicated in the procedure text. If the procedure text does not explicitly indicate that an optional IE shall be included in a response message, the optional IE shall not be included. For requirements on including Criticality Diagnostics IE, see clause 10.
Up

4.2  Forwards and backwards compatibility  p. 21

The forwards and backwards compatibility of the protocol is assured by a mechanism where all current and future messages, and IEs or groups of related IEs, include ID and criticality fields that are coded in a standard format that will not be changed in the future. These parts can always be decoded regardless of the standard version.

4.3  Specification notations  p. 21

For the purposes of the present document, the following notations apply:
Procedure
When referring to an elementary procedure in the specification the Procedure Name is written with the first letters in each word in upper case characters followed by the word "procedure", e.g. Handover Preparation procedure.
Message
When referring to a message in the specification the MESSAGE NAME is written with all letters in upper case characters followed by the word "message", e.g. HANDOVER REQUEST message.
IE
When referring to an information element (IE) in the specification the Information Element Name is written with the first letters in each word in upper case characters and all letters in Italic font followed by the abbreviation "IE", e.g. PDU Session ID IE.
Value of an IE
When referring to the value of an information element (IE) in the specification the "Value" is written as it is specified in sub clause 9.2 enclosed by quotation marks, e.g. "Value".
Up

5  XnAP services  p. 22

The present clause describes the services an NG-RAN node offers to its neighbours.

5.1  XnAP procedure modules  p. 22

The Xn interface XnAP procedures are divided into two modules as follows:
  1. XnAP Basic Mobility Procedures;
  2. XnAP Global Procedures;
The XnAP Basic Mobility Procedures module contains procedures used to handle the UE mobility within NG-RAN.
The Global Procedures module contains procedures that are not related to a specific UE. The procedures in this module are in contrast to the above module involving two peer NG-RAN nodes.

5.2  Parallel transactions  p. 22

Unless explicitly indicated in the procedure specification, at any instance in time one protocol peer shall have a maximum of one ongoing XnAP procedure related to a certain UE.

6  Services expected from signalling transport  p. 22

The signalling connection shall provide in sequence delivery of XnAP messages. XnAP shall be notified if the signalling connection breaks.
Xn signalling transport is specified in TS 38.422.

7  Functions of XnAP  p. 22

The functions of XnAP are specified in TS 38.420.

Up   Top   ToC