hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.2.2.3 Unsuccessful Operation | Figure 8.2.2.3-1: RIC Subscription Delete procedure, unsuccessful operation If a failure occurs during the RIC Subscription Delete procedure, the E2 Node shall send the RIC SUBSCRIPTION DELETE FAILURE message to the Near-RT RIC containing an appropriate cause value. ETSI ETSI TS 104 039 V4.0.0 (2024-10) 17 If the RIC Request ID IE included in the RIC SUBSCRIPTION DELETE REQUEST message is unknown, the E2 Node shall send the RIC SUBSCRIPTION DELETE FAILURE message to the Near-RT RIC containing an appropriate cause value Upon reception of the RIC SUBSCRIPTION DELETE FAILURE message the Near-RT RIC shall stop timer TRICEVENTdelete and terminate the RIC Subscription Delete procedure. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.2.2.4 Abnormal Conditions | If the E2 Node receives a RIC SUBSCRIPTION DELETE REQUEST message contains an unknown RAN Function ID IE, the E2 Node shall send the RIC SUBSCRIPTION DELETE FAILURE message to the Near-RT RIC containing an appropriate cause value. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.2.2A RIC Subscription Delete Required procedure | |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.2.2A.1 General | This procedure is used to enable the E2 Node to request deletion of the existing RIC Subscriptions in the E2 Node previously created for the Near-RT RIC. This procedure shall be initiated by the E2 Node. This procedure uses RIC Service signalling. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.2.2A.2 Successful Operation | Figure 8.2.2A.2-1: RIC Subscription Delete Required procedure, successful operation The E2 Node initiates the procedure by sending a RIC SUBSCRIPTION DELTE REQUIRED message, containing RIC Request ID IE that was previously assigned by the Near-RT RIC during a successful RIC Subscription procedure, to the Near-RT RIC. The message shall contain an appropriate cause value for each RIC Subscription requesting to remove. At reception of the RIC SUBSCRIPTION DELETE REQUIRED message, for each RIC Subscription associated with the included RIC Request ID IE and RAN Function ID IE, the Near-RT RIC may initiate the RIC Subscription Delete procedure toward the E2 Node. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.2.2A.3 Abnormal Conditions | If the Near-RT RIC receives a RIC SUBSCRIPTION DELETE REQUIRED message which contains an unknown RIC Request ID IE and RAN Function ID IE, the Near-RT RIC shall ignore the message. ETSI ETSI TS 104 039 V4.0.0 (2024-10) 18 |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.2.3 RIC Indication procedure | |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.2.3.1 General | The purpose of the RIC Indication procedure is to transfer Report and/or Insert RIC Service Action associated with a RIC Subscription procedure. This procedure shall be initiated by the E2 Node. This procedure uses RIC Service signalling. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.2.3.2 Successful Operation | Figure 8.2.3.2-1: RIC Indication procedure, successful operation An E2 Node initiates the procedure by sending RIC INDICATION message to the Near-RT RIC containing the RIC Request ID IE, that was previously assigned by the Near-RT RIC during a successful RIC Subscription procedure. If the RIC Indication message is in response to an Insert RIC Service Action, then the E2 Node shall provide the RIC Call Process ID IE within the RIC INDICATION message, and the E2 Node shall store current call state, start the associated RIC Time to Wait timer, and suspend further processing of the associated RAN function. Near-RT RIC may use the RIC Call Process ID IE in a subsequent RIC Control procedure. If an RIC Subsequent Action IE was associated to the RIC Service Action then, after successful transmission of the RIC INDICATION message, the originating E2 Node shall progress accordingly: - If the RIC Subsequent Action Type IE was set to Continue or Halt, and the associated RIC Time to Wait timer has not expired, and a RIC CONTROL REQUEST message is received with the same RIC Call Process ID IE, then the E2 Node shall use the RIC CONTROL REQUEST information along with the stored call state and continue to execute any remaining actions in the sequence of RIC Actions defined in the RIC Subscription procedure prior to resuming normal functionality of the associated RAN function. - If the RIC Subsequent Action Type IE was set to Continue and the associated RIC Time to Wait timer has expired, then the E2 Node shall use the stored call state and continue to execute any remaining RIC Service Actions in the sequence of RIC Service Actions defined in the RIC Subscription procedure. - If the RIC Subsequent Action Type IE was set to Halt and the associated RIC Time to Wait timer has expired, then the E2 Node shall abort further processing of the associated RAN function. In this case, any remaining RIC Service Actions in the sequence of RIC Actions defined in the RIC Subscription procedure shall also be aborted. ETSI ETSI TS 104 039 V4.0.0 (2024-10) 19 Table 8.2.3.2-1: RIC Indication procedure, successful operation Subsequent Action RIC Time to Wait timer Condition Outcome Continue or Halt required E2 Node detected the event trigger in the RIC Event Trigger Definition IE. RIC INDICATION message shall provide the RIC Call Process ID IE and E2 Node shall store current call state, start the associated RIC Time to Wait timer, and suspend further processing of the associated RAN function. Continue or Halt not yet expired E2 Node received the RIC CONTROL REQUEST message with the same RIC call process ID IE. E2 Node shall use the RIC CONTROL information along with the stored call state and continue to execute any remaining actions in the sequence of RIC Actions defined in the RIC Subscription procedure. Continue expired E2 Node shall use the stored call state and continue to execute any remaining actions in the sequence of RIC Actions defined in the RIC Subscription procedure. Halt expired E2 Node shall abort normal functionality of the associated RAN function. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.2.3.3 Unsuccessful Operation | Not applicable. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.2.3.4 Abnormal Conditions | Not applicable. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.2.4 RIC Control procedure | |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.2.4.1 General | The purpose of the RIC Control procedure is to initiate or resume a specific functionality in the E2 Node. This procedure shall be initiated by the Near-RT RIC. This procedure uses RIC Service signalling. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.2.4.2 Successful Operation | Figure 8.2.4.2-1: RIC Control procedure, successful operation The Near-RT RIC initiates the procedure by sending a RIC CONTROL REQUEST message containing a unique RIC Request ID IE, assigned by the Near-RT RIC. When the Near-RT RIC sends the RIC CONTROL REQUEST message and the optional RIC Control Ack Request IE has been set to "Ack", or is not present, the Near-RT RIC, it shall start the timer TRICcontrol. ETSI ETSI TS 104 039 V4.0.0 (2024-10) 20 At reception of the RIC CONTROL REQUEST message the E2 Node shall: - Determine the target RAN Function using the information in the RAN Function ID IE and initiate the requested RIC Control procedure action using information in the RIC Control Message IE. - If the RIC Call Process ID IE is included in the RIC CONTROL REQUEST message, the E2 Node shall use this IE to identify a specific call process that was indicated in the RIC INDICATION message. - If the RIC CONTROL REQUEST message contains the optional RIC Control Ack Request IE set to "Ack", or if the optional RIC Control Ack Request IE is not present, and the E2 Node has successfully processed the requested RIC Control procedure action, then the E2 Node shall respond with the RIC CONTROL ACKNOWLEDGE message. - If the RIC CONTROL REQUEST message contains the optional RIC Control Ack Request IE set to "NoAck" and the E2 Node has successfully processed the requested RIC Control procedure action, then the E2 Node shall not send the RIC CONTROL ACKNOWLEDGE message. Upon reception of the RIC CONTROL ACKNOWLEDGE message, the Near-RT RIC shall stop timer TRICcontrol and terminate the RIC Control procedure. The Near-RT RIC may use the information contained in the optional RIC Control Outcome IE to determine subsequent actions. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.2.4.3 Unsuccessful Operation | Figure 8.2.4.3-1: RIC Control procedure, unsuccessful operation If the RIC CONTROL REQUEST message contains an invalid RIC Call Process ID IE, then the E2 Node shall respond with the RIC CONTROL FAILURE message with an appropriate cause value. If the RIC CONTROL REQUEST message contains the optional RIC Call Process ID IE for which the associated RIC Time to Wait timer had expired, then the E2 Node shall respond with the RIC CONTROL FAILURE message with an appropriate cause value. If the E2 Node fails to execute the requested RIC Control procedure E2SM specific action, then the E2 Node shall respond with the RIC CONTROL FAILURE message with an appropriate cause value. If the E2 Node detects an encoding or functional error in the E2SM specific IEs contained in the RIC CONTROL REQUEST message, then the E2 Node shall respond with the RIC CONTROL FAILURE message with an appropriate cause value. If the E2 Node receives a RIC CONTROL REQUEST message which contains an unknown RAN Function ID IE the E2 Node shall respond with the RIC CONTROL FAILURE message containing an appropriate cause value. If the E2 Node does not support the specific RIC Control procedure action, then the E2 Node shall respond with the RIC CONTROL FAILURE message containing an appropriate cause value. Upon reception of the RIC CONTROL FAILURE message the Near-RT RIC shall stop timer TRICcontrol, if running, and terminate the RIC Control procedure. The Near-RT RIC may use the information contained in the Cause IE and optional RIC Control Outcome IE to determine subsequent actions. ETSI ETSI TS 104 039 V4.0.0 (2024-10) 21 |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.2.4.4 Abnormal Conditions | Upon reception of the ERROR INDICATION message including the RIC Request ID IE associated to the RIC CONTROL REQUEST message, the Near-RT RIC shall stop timer TRICcontrol, if running, and terminate the RIC Control procedure. If timer TRICcontrol was set when sending the RIC CONTROL REQUEST message and there was no response from the E2 node before the timer expiry, the Near-RT RIC shall send an ERROR INDICATION with the appropriate value for the Cause IE. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.2.5 RIC Subscription Modification procedure | |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.2.5.1 General | The purpose of the RIC Subscription Modification procedure is to modify an existing RIC subscription on an E2 node, in terms of its event trigger definition and/or the sequence of actions. This procedure shall be initiated by the Near-RT RIC. This procedure uses RIC Service signalling. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.2.5.2 Successful Operation | Figure 8.2.5.2-1: RIC Subscription Modification procedure, successful operation The Near-RT RIC initiates this procedure by sending the RIC SUBSCRIPTION MODIFICATION REQUEST message to the E2 node, containing the RIC Request ID IE to uniquely identify the existing RIC Subscription in the E2 node. When the Near-RT RIC sends the RIC SUBSCRIPTION MODIFICATION REQUEST message, it shall start timer TRICEVENTmodify. Upon reception of the RIC SUBSCRIPTION MODIFICATION REQUEST message, the E2 node shall determine the existing RIC Subscription and the target RAN Function from the RIC Request ID IE and the RAN Function ID IE, respectively. If the RIC Event Trigger Definition to be Modified IE is included, then the E2 node shall validate and modify the event trigger defined for the existing RIC subscription based on the contents of the IE. If the RIC Actions to be Removed List IE is included, then for every RIC Action ID IE included in the list, the E2 node shall delete the requested action and release the corresponding necessary resources. If the RIC Actions to be Modified List IE is included, then for every RIC Action ID IE included in the list for which there exists a corresponding RIC Action Definition IE and/or RIC Subsequent Action IE, the E2 node shall modify the existing behaviour for the action with the requested modification in the respective IEs and modify the corresponding necessary resources. If the RIC Actions to be Modified List IE is included, then for every RIC Action ID IE included in the list for which there exists a RIC Action Execution Order IE, the E2 node shall replace the current execution order for the action in the sequence of actions with the new execution order for the action in the sequence, as given in the RIC Action Execution Order IE. ETSI ETSI TS 104 039 V4.0.0 (2024-10) 22 If the RIC Actions to be Added List IE is included, then the E2 node shall validate and add the requested actions to the existing sequence of RIC Actions in order of the RIC Action Execution Order IE and reserve the necessary resources for the new actions. The E2 node shall send the RIC SUBSCRIPTION MODIFICATION RESPONSE message back to the Near-RT RIC when one of the following cases is successfully executed: - if the RIC Event Trigger Definition to be Modified IE is present in the RIC SUBSCRIPTION MODIFICATION REQUEST message and if the requested modification for the event trigger definition was successfully performed by the E2 node; or - if the RIC Event Trigger Definition to be Modified IE is not present (i.e. no modification to the event trigger definition was requested) in the RIC SUBSCRIPTION MODIFICATION REQUEST message and if at least one of the requested actions to be added or modified or removed as requested by the Near-RT RIC in RIC Actions To Be Added List IE or RIC Actions to be Modified List IE or RIC Actions to be Removed List IE, respectively, in the RIC SUBSCRIPTION MODIFICATION REQUEST message, was successfully performed by the E2 node. The E2 node shall report the result of all the requested modifications to the sequence of actions, if any, back to the Near-RT RIC in the RIC SUBSCRIPTION MODIFICATION RESPONSE message as follows: - A list of actions requested to be removed, indexed by the RIC Action ID IE, which are successfully removed by the E2 node, shall be included in the RIC Actions Removed List IE. - A list of actions requested to be removed, indexed by the RIC Action ID IE, which failed to get removed from the sequence by the E2 node, shall be included in the RIC Actions Failed to be Removed List IE, with appropriate cause values. - A list of actions requested to be modified, indexed by the RIC Action ID IE, which are successfully modified by the E2 node, shall be included in the RIC Actions Modified List IE. - A list of actions requested to be modified, indexed by the RIC Action ID IE, which failed to get modified by the E2 node, shall be included in the RIC Actions Failed to be Modified List IE with appropriate cause values. - A list of actions requested to be added, indexed by the RIC Action ID IE, which are successfully added by the E2 node, shall be included in the RIC Actions Added List IE. - A list of actions requested to be added, indexed by the RIC Action ID IE, which failed to get added to the sequence by the E2 node, shall be included in the RIC Actions Failed to be Added List IE with appropriate cause values. If, for a given RIC Action ID IE in the RIC Actions to be Modified List IE, more than one modification to the RIC Service Action is requested in the form of RIC Action Definition IE and/or RIC Action Execution Order IE and/or RIC Subsequent Action IE, then the E2 node shall report that the requested action modification is successfully performed and shall include the action in the RIC Actions Modified List IE, if and only if, all the requested modifications to the action are successfully performed by the E2 node. If one of the requested modifications to the RIC Service Action is not successfully performed by the E2 node, then the E2 node shall include the RIC Service Action in the RIC Actions Failed to be Modified List IE, along with an appropriate cause, to indicate failure for the requested modification to the RIC Service Action. If, for a given RIC Action ID IE in the RIC Actions to be Added IE, either the action type in the RIC Action Type IE or the action definition in the RIC Action Definition IE or the action execution order in the RIC Action Execution Order IE or the subsequent action, if included, in the RIC Subsequent Action IE is not successfully processed by the E2 node, then the E2 node shall include the action in the RIC Actions Failed to be Added List IE with an appropriate cause, indicating failure to add the requested action to the existing sequence of actions. If, after processing the RIC Subscription Modification procedure, more than one RIC Service Action remains accepted by the E2 Node then, at each occurrence of the common Event Trigger, the sequence of RIC Service Actions shall be executed according to the considerations defined in clause 8.2.1.2. Upon reception of the RIC SUBSCRIPTION MODIFICATION RESPONSE message, the Near-RT RIC shall stop timer TRICEVENTmodify and terminate the RIC Subscription Modification procedure. ETSI ETSI TS 104 039 V4.0.0 (2024-10) 23 |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.2.5.3 Unsuccessful Operation | Figure 8.2.5.3-1: RIC Subscription Modification procedure, unsuccessful operation If a failure occurs during the RIC Subscription Modification procedure, the E2 node shall send a RIC SUBSCRIPTION MODIFICATION FAILURE message to the Near-RT RIC with an appropriate cause value. If the RIC Event Trigger Definition to be Modified IE is present in the RIC SUBSCRIPTION MODIFICATION REQUEST message and if the requested modification for the event trigger definition are not accepted by the E2 node, the E2 node shall send a RIC SUBSCRIPTION MODIFICATION FAILURE message to the Near-RT RIC with an appropriate cause value. If the RIC Event Trigger Definition to be Modified IE is present in the RIC SUBSCRIPTION MODIFICATION REQUEST message and if the modification in the event trigger definition is inconsistent or disparate from the event trigger definition in the existing subscription, the E2 node shall send a RIC SUBSCRIPTION MODIFICATION FAILURE message to the Near-RT RIC with an appropriate cause value. If the RIC Event Trigger Definition to be Modified IE is not present (i.e. no modification to the event trigger definition was requested) and if none of the requested modifications to the sequence of actions were successfully performed, that is if all of the following apply, the E2 node shall send a RIC SUBSCRIPTION MODIFICATION FAILURE message to the Near-RT RIC with an appropriate cause value: - RIC Actions to be Added List IE was present in the RIC SUBSCRIPTION MODIFICATION REQUEST message and if none of the requested additions were successfully performed. - RIC Actions to be Modified List IE was present in the RIC SUBSCRIPTION MODIFICATION REQUEST message and if none of the requested modifications were successfully performed. - RIC Actions to be Removed List IE was present in the RIC SUBSCRIPTION MODIFICATION REQUEST message and if none of the requested removals were successfully performed. If the RIC Event Trigger Definition to be Modified IE is not present (i.e. no modification to the event trigger definition was requested) and if the E2 node detects an inconsistency across the sequence of actions and/or the subsequent actions in RIC Actions to be Added List IE and/or RIC Actions to be Modified List IE and/or RIC Actions to be Removed List IE, the E2 node shall send a RIC SUBSCRIPTION MODIFICATION FAILURE message to the Near-RT RIC with an appropriate cause value. If all RIC Service Action in the existing RIC Subscription are proposed for removal, the E2 node shall send a RIC SUBSCRIPTION MODIFICATION FAILURE message to the Near-RT RIC with an appropriate cause value. Upon reception of the RIC SUBSCRIPTION FAILURE message, the Near-RT RIC shall stop the timer TRICEVENTmodify and terminate the RIC Subscription Modification procedure. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.2.5.4 Abnormal Conditions | If the E2 node receives a RIC SUBSCRIPTION MODIFICATION REQUEST message including an unknown RAN Function ID IE, the E2 node shall send the RIC SUBSCRIPTION MODIFICATION FAILURE message to the Near-RT RIC with an appropriate cause value. If the E2 node receives a RIC SUBSCRIPTION MODIFICATION REQUEST message including an unknown RIC Request ID IE, the E2 node shall send the RIC SUBSCRIPTION MODIFICATION FAILURE message to the Near-RT RIC with an appropriate cause value. ETSI ETSI TS 104 039 V4.0.0 (2024-10) 24 If the E2 node receives a RIC SUBSCRIPTION MODIFICATION REQUEST message containing the same RIC Action ID IE value across the RIC Actions to be Added List IE , RIC Actions to be Modified List IE and/or RIC Actions to be Removed List IE, then the E2 node shall send the RIC SUBSCRIPTION MODIFICATION FAILURE message to the Near-RT RIC with an appropriate cause value. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.2.6 RIC Subscription Modification Required procedure | |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.2.6.1 General | This procedure is used by the E2 Node to request the Near-RT RIC for modifying an existing RIC Subscription in the E2 Node. This procedure shall be initiated by the E2 Node. This procedure uses RIC Service signalling. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.2.6.2 Successful Operation | Figure 8.2.6.2-1: RIC Subscription Modification Required procedure, successful operation The E2 Node initiates the procedure by sending the RIC SUBSCRIPTION MODIFICATION REQUIRED message, containing RIC Request ID IE that was previously assigned by the Near-RT RIC during a successful RIC Subscription procedure, to the Near-RT RIC. Upon reception of the RIC SUBSCRIPTION MODIFICATION REQUIRED message, the Near-RT RIC shall determine the RIC Subscription from the RIC Request ID IE and the target RAN Function from the RAN Function ID IE. If at least one of the requested actions in RIC Actions Required to be Modified List IE or RIC Actions Required to be Removed List IE is successfully confirmed by the Near-RT RIC, then the Near-RT RIC shall perform the required procedures to update the RIC Subscription and shall send the RIC SUBSCRIPTION MODIFICATION CONFIRM message to the E2 node. The Near-RT RIC shall report the result to the E2 node in the RIC SUBSCRIPTION MODIFICATION CONFIRM as follows: - A list of actions requested to be modified, indexed by the RIC Action ID IE, which are successfully confirmed for modification by the Near-RT RIC, shall be included in the RIC Actions Confirmed for Modification List IE. - A list of actions requested to be modified, indexed by the RIC Action ID IE, which are refused to be modified by the Near-RT RIC, shall be included in the RIC Actions Refused to be Modified List IE with appropriate cause values. - A list of actions requested to be removed, indexed by the RIC Action ID IE, which are successfully confirmed for removal by the Near-RT RIC, shall be included in the RIC Actions Confirmed for Removal List IE. - A list of actions requested to be removed, indexed by the RIC Action ID IE, which are refused to be removed by the Near-RT RIC, shall be included in the RIC Actions Refused for Removal List IE with appropriate cause values. ETSI ETSI TS 104 039 V4.0.0 (2024-10) 25 If, after processing the RIC Subscription Modification Required procedure, more than one RIC Service Action remains in effect at the E2 node, then at each occurrence of the common Event Trigger, the sequence of RIC Service Actions shall be executed according to the considerations defined in clause 8.2.1.2. Upon reception of the RIC SUBSCRIPTION MODIFICATION CONFIRM message, the E2 Node shall release the necessary resources for the actions that are confirmed for removal in the RIC Actions Confirmed for Removal List IE, if present, and shall modify the necessary resources for the actions that are confirmed for modification in the RIC Actions Confirmed for Modification List IE, if present. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.2.6.3 Unsuccessful Operation | Figure 8.2.6.3-1: RIC Subscription Modification Required procedure, unsuccessful operation If a failure occurs during the RIC Subscription Modification Required procedure the Near-RT RIC shall send the RIC SUBSCRIPTION MODIFICATION REFUSE message to the E2 node. If none of the requested modifications to the actions in the RIC SUBSCRIPTION MODIFICATION REQUIRED message (i.e. in the RIC Actions Required to be Modified List IE and the RIC Actions Required to be Removed List IE, if present) is successfully confirmed, the Near-RT RIC shall send the RIC SUBSCRIPTION MODIFICATION REFUSE message to the E2 node with an appropriate cause. If the Near-RT RIC detects an inconsistency across the requested sequence of actions to be modified and removed in RIC Actions Required to be Modified List IE and the RIC Actions Required to be Removed List IE respectively, if present, the Near-RT RIC shall send the RIC SUBSCRIPTION MODIFICATION REFUSE message to the E2 node with an appropriate cause. If all RIC Service Action in the existing RIC Subscription are proposed for removal, the Near-RT RIC shall send a RIC SUBSCRIPTION MODIFICATION REFUSE message to the E2 Node with an appropriate cause value. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.2.6.4 Abnormal Conditions | If the Near-RT RIC receives a RIC SUBSCRIPTION MODIFICATION REQUIRED message which contains an unknown RAN Function ID IE, the Near-RT RIC shall send the RIC SUBSCRIPTION MODIFICATION REFUSE message to the E2 Node with an appropriate cause value. If the Near-RT RIC receives a RIC SUBSCRIPTION MODIFICATION REQUIRED message containing an unknown RIC Request ID IE, the Near-RT RIC shall send the RIC SUBSCRIPTION MODIFICATION REFUSE message to the E2 Node with an appropriate cause value. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.2.7 RIC Query procedure | |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.2.7.1 General | This procedure is initiated by Near-RT RIC to request RAN and/or UE related information from E2 Node. This procedure shall be initiated by the Near-RT RIC. This procedure uses RIC Service signalling. ETSI ETSI TS 104 039 V4.0.0 (2024-10) 26 |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.2.7.2 Successful Operation | Figure 8.2.7.2-1: RIC Query procedure, successful operation The Near-RT RIC initiates the procedure by sending the RIC QUERY REQUEST message, which shall contain a unique RIC Request ID IE, assigned by the Near-RT RIC, to the E2 Node. When the Near-RT RIC sends the RIC QUERY REQUEST message, it shall start timer TRICquery. At reception of the RIC QUERY REQUEST message the E2 Node shall: - Determine the target RAN Function using the information in the RAN Function ID IE. - Validate the RIC Query Header IE and RIC Query Definition IE and if the requested information is available at E2 Node, then E2 Node shall respond back with RIC QUERY RESPONSE message containing the requested information. Upon reception of the RIC QUERY RESPONSE message the Near-RT RIC shall stop timer TRICquery and terminate the RIC Query procedure. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.2.7.3 Unsuccessful Operation | Figure 8.2.7.3-1: RIC Query procedure, unsuccessful operation If the RAN Function ID IE in the RIC QUERY REQUEST message is not supported by E2 Node, then the E2 Node shall respond with the RIC QUERY FAILURE message to Near-RT RIC with an appropriate cause value. If all of the requested information in the RIC Query Definition IE are invalid, then the E2 Node shall respond with the RIC QUERY FAILURE message to Near-RT RIC with an appropriate cause value. If none of the requested information in the RIC Query Definition IE are available at E2 Node, then E2 Node shall respond with the RIC QUERY FAILURE message to Near-RT RIC with an appropriate cause value. Upon reception of the RIC QUERY FAILURE message the Near-RT RIC shall stop timer TRICquery and terminate the RIC Query Procedure. ETSI ETSI TS 104 039 V4.0.0 (2024-10) 27 |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.2.7.4 Abnormal Conditions | Upon reception of the ERROR INDICATION message including the RIC Request ID IE corresponding to the previous RIC QUERY REQUEST message, the Near-RT RIC shall stop timer TRICquery, if running, and terminate the RIC Query procedure. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.3 Global Procedures | |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.3.1 E2 Setup procedure | |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.3.1.1 General | The purpose of the E2 Setup procedure is to exchange application level data needed for the E2 Node and Near-RT RIC to correctly interoperate on the E2 interface. This procedure shall be the first E2AP procedure triggered after the TNL association has become operational. This procedure erases any existing application level configuration data in the two nodes and replace it by the one received. This procedure shall be initiated by the E2 Node. This procedure uses E2 Support Function signalling. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.3.1.2 Successful Operation | Figure 8.3.1.2-1: E2 Setup procedure, successful operation The E2 Node initiates the procedure by sending the E2 SETUP REQUEST message including the appropriate data to a Near-RT RIC. If the Near-RT RIC has successfully processed the RAN Functions Added List IE then Near-RT RIC shall contain, in the E2 SETUP RESPONSE message, the RAN Functions Accepted List IE and/or the RAN Functions Rejected List IE. If the Near-RT RIC has successfully processed the E2 Node Component Configuration Addition List IE then Near-RT RIC shall contain, in the E2 SETUP RESPONSE message, the E2 Node Component Configuration Addition Acknowledge List IE. ETSI ETSI TS 104 039 V4.0.0 (2024-10) 28 |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.3.1.3 Unsuccessful Operation | Figure 8.3.1.3-1: E2 Setup procedure, unsuccessful operation If the Near-RT RIC cannot accept the setup it shall respond with an E2 SETUP FAILURE message with an appropriate cause value. The Near-RT RIC may provide an alternative Transport Layer Information IE in the E2 SETUP FAILURE message for the E2 Node to use when reinitiating the E2 Setup procedure towards the Near-RT RIC. If the E2 SETUP FAILURE message includes the Time To Wait IE, the E2 node shall wait at least for the indicated time before reinitiating the E2 Setup procedure towards the Near-RT RIC. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.3.1.4 Abnormal Conditions | If the first message received for a specific TNL association is not an E2 SETUP REQUEST, E2 SETUP RESPONSE, E2 SETUP FAILURE or E2 NODE CONFIGURATION UPDATE message then this shall be treated as a logical error. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.3.2 Reset procedure | |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.3.2.1 General | The purpose of the Reset procedure is to initialize or re-initialize the E2 Node in the event of Near-RT RIC failure or vice-versa. This procedure does not affect the application level data exchanged during the E2 Setup procedure, E2 Node Configuration Update procedure and RIC Service Update procedure. This procedure shall be initiated by the E2 Node or the Near-RT RIC. This procedure uses E2 Support Function signalling. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.3.2.2 Successful Operation | This procedure may be initiated by either Near-RT RIC or E2 Node. Figure 8.3.2.2-1: Reset, successful operation (E2 Node Initiated) ETSI ETSI TS 104 039 V4.0.0 (2024-10) 29 Figure 8.3.2.2-2: Reset, successful operation (Near-RT RIC Initiated) When the Reset procedure is initiated, the Near-RT RIC and E2 Node shall: - Delete any pre-established RIC Subscriptions. - Gracefully terminate any ongoing Near-RT RIC call processes using Insert, Control or Policy RIC Service Actions while ensuring that impact to ongoing calls for connected UE is minimized. After the Reset has been completed, the Near-RT RIC may re-issue any required RIC Subscriptions. Interactions with other procedures: If the RESET REQUEST message is received, any other ongoing procedure (except for another Reset procedure) on the same E2 interface related to ongoing RIC Services shall be aborted. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.3.2.3 Unsuccessful Operation | Void. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.3.2.4 Abnormal Conditions | Void. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.3.3 Error Indication | |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.3.3.1 General | The Error Indication procedure is initiated by either the E2 Node or the Near-RT RIC to report detected errors in one incoming message, provided they cannot be reported by an appropriate failure message. This procedure shall be initiated by the E2 Node or the Near-RT RIC. If the error situation arises due to reception of a message utilizing RIC Service signalling, then the Error Indication procedure uses RIC Service signalling. Otherwise the procedure uses E2 Support Function signalling. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.3.3.2 Successful Operation | Figure 8.3.3.2-1: Error Indication, (E2 Node initiated) successful operation ETSI ETSI TS 104 039 V4.0.0 (2024-10) 30 Figure 8.3.3.2-2: Error Indication, (Near-RT RIC Initiated) successful operation When the conditions defined in clause 10 are fulfilled, the Error Indication procedure shall be initiated by an ERROR INDICATION message sent from the node detecting the error situation. The ERROR INDICATION message shall contain at least either the Cause IE or the Criticality Diagnostics IE and may include RAN Function ID IE and RIC Request ID IE. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.3.3.3 Unsuccessful Operation | Not applicable. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.3.3.4 Abnormal Conditions | Not applicable. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.3.4 RIC Service Update procedure | |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.3.4.1 General | The purpose of the RIC Service Update procedure is to update application level RIC Service related data needed for E2 Node and Near-RT RIC to interoperate correctly over the E2 interface. This procedure shall be initiated by the E2 Node. This procedure uses E2 Support Function signalling. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.3.4.2 Successful Operation | Figure 8.3.4.2-1: RIC Service Update procedure, successful operation An E2 Node initiates the procedure by sending a RIC SERVICE UPDATE message to the Near-RT RIC. If the E2 Node has taken into operational use one or more RAN Functions supporting RIC Services, the RIC SERVICE UPDATE message shall include the RAN Functions Added List IE. ETSI ETSI TS 104 039 V4.0.0 (2024-10) 31 If the E2 Node has modified one or more RAN Functions supporting RIC Services, the RIC SERVICE UPDATE message shall include the RAN Functions Modified List IE. If the E2 Node has removed from operational use one or more RAN Functions supporting RIC Services, the RIC SERVICE UPDATE message shall include the RAN Functions Deleted List IE. Upon reception of a RIC SERVICE UPDATE message, Near-RT RIC shall update the application level data for E2 Node as follows: - If the RAN Function Added List IE is contained in the RIC SERVICE UPDATE message, Near-RT RIC shall add each listed accepted RAN Function according to the information in the RAN Function ID IE and RAN Function Definition IE and store the corresponding RAN Function Revision IE. - If the RAN Function Modified List IE is contained in the RIC SERVICE UPDATE message, Near-RT RIC shall modify accepted information of supported RAN Functions according to the information in the RAN Function Definition IE and update the corresponding RAN Function Revision IE. - If the RAN Function Deleted List IE is contained in the RIC SERVICE UPDATE message, Near-RT RIC shall delete information of RAN Function indicated by the RAN Function ID IE along with the corresponding RAN Function Revision IE. These changes may be processed in the Near-RT-RIC and may be used when issuing RIC SUBSCRIPTION REQUEST and RIC CONTROL to provide valid RAN Function ID IE. If at least one RAN Function update request present in the RIC SERVICE UPDATE message is successful, then the Near-RT RIC shall send the RIC SERVICE UPDATE ACKNOWLEDGE message to the initiating E2 Node with: - RAN Functions Accepted List IE indicating accepted requests to add, modify, and/or delete the corresponding RAN Function information. - If required, the RAN Functions Rejected List IE indicating rejected requests to add, modify, and/or delete the corresponding RAN Function information. If the Near-RT RIC receives a RIC SERVICE UPDATE message without any IE except for Message Type IE, then the Near-RT RIC shall reply with RIC SERVICE UPDATE ACKNOWLEDGE message without any IE except for Message Type IE, and shall not perform any updates to the existing application level data. Optionally, the RIC SERVICE UPDATE message to the Near-RT RIC may have been sent as a response to the Near-RT RIC initiated RIC SERVICE QUERY message. Upon reception of the RIC SERVICE QUERY message: - If the RAN Function Accepted List IE is not present, the E2 Node shall send the RIC SERVICE UPDATE message with the complete list of supported RAN Functions in the RAN Function Added List IE. - If the RAN Function Accepted List IE is present and aligns with the list of supported RAN Functions at the E2 Node, the E2 Node shall send the RIC SERVICE UPDATE message without the RAN Function Added List IE, RAN Function Modified List IE and RAN Function Deleted List IE. - If the RAN Function Accepted List IE is present and the list of RAN Functions in the RAN Function Accepted List IE does not align with the list of supported RAN Functions at the E2 node, the E2 Node shall send the RIC SERVICE UPDATE message with the RAN Function Added List IE, RAN Function Modified List IE and/or RAN Function Deleted List IE to ensure realignment of RAN Functions between the E2 Node and the Near-RT RIC. ETSI ETSI TS 104 039 V4.0.0 (2024-10) 32 |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.3.4.3 Unsuccessful Operation | Figure 8.3.4.3-1: RIC Service Update procedure, unsuccessful operation If the Near-RT RIC cannot accept the update it shall respond with a RIC SERVICE UPDATE FAILURE message with an appropriate cause value. If the RIC SERVICE UPDATE FAILURE message includes the Time To Wait IE, the E2 Node shall wait at least for the indicated time before reinitiating the RIC Service Update procedure towards the same Near-RT RIC. Both nodes shall continue to operate the E2 with their existing RIC Service data. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.3.4.4 Abnormal Conditions | Void. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.3.5 E2 Node Configuration Update procedure | |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.3.5.1 General | The purpose of the E2 Node Configuration Update procedure is to update application level E2 Node configuration data needed for E2 Node and Near-RT RIC to interoperate correctly over the E2 interface and to support E2 Node initiated TNL association removal. This procedure shall be initiated by the E2 Node. This procedure uses E2 Support Function signalling. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.3.5.2 Successful Operation | Figure 8.3.5.2-1: E2 Node Configuration Update procedure, successful operation An E2 Node initiates the procedure by sending a E2 NODE CONFIGURATION UPDATE message to the Near-RT RIC. The message shall include an appropriate set of up-to-date E2 Node-related configuration data that the E2 Node has just taken into operational use. ETSI ETSI TS 104 039 V4.0.0 (2024-10) 33 Upon reception of the E2 NODE CONFIGURATION UPDATE message, Near-RT RIC shall update the application level data for the E2 Node as follows: Update of E2 Node configuration information in Near-RT RIC: - If E2 Node Component Configuration Addition List IE is contained in the E2 NODE CONFIGURATION UPDATE message, Near-RT RIC shall add the E2 Node Component Configuration information accordingly. - If E2 Node Component Configuration Update List IE is contained in the E2 NODE CONFIGURATION UPDATE message, Near-RT RIC shall modify the E2 Node Component Configuration information accordingly. - If E2 Node Component Configuration Removal List IE is contained in the E2 NODE CONFIGURATION UPDATE message, Near-RT RIC shall remove the E2 Node Component Configuration information accordingly. If Global E2 Node ID IE is contained in the E2 NODE CONFIGURATION UPDATE message for a newly established SCTP association, the Near-RT RIC shall associate the TNL association with the related E2 Node. If the E2 NODE CONFIGURATION UPDATE message includes E2 Node TNL Association To Remove List IE, and the Endpoint IP address IE and the Port Number IE for both TNL endpoints of the TNL association(s) are included in the E2 Node TNL Association To Remove List IE, the Near-RT RIC shall, if supported, consider that the TNL association(s) indicated by both received TNL endpoints will be removed by the E2 Node. If the E2 NODE CONFIGURATION UPDATE message includes E2 Node TNL Association To Remove List IE, and the Endpoint IP address IE, or the Endpoint IP address IE and the Port Number IE for one or both of the TNL endpoints is included in the E2 Node TNL Association To Remove List IE in E2 NODE CONFIGURATION UPDATE message, the Near-RT RIC shall, if supported, consider that the TNL association(s) indicated by the received endpoint IP address(es) will be removed by the E2 Node. After successful update of requested information, Near-RT RIC shall reply with the E2 NODE CONFIGURATION UPDATE ACKNOWLEDGE message to inform the initiating E2 Node that the requested update of application level data was performed successfully. If the Near-RT RIC receives an E2 NODE CONFIGURATION UPDATE message without any IE except for Message Type IE and Transaction ID IE, the Near-RT RIC shall reply with the E2 NODE CONFIGURATION UPDATE ACKNOWLEDGE message without performing any updates to the existing configuration. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.3.5.3 Unsuccessful Operation | Figure 8.3.5.3-1: E2 Node Configuration Update procedure, unsuccessful operation If Near-RT RIC cannot accept the E2 NODE CONFIGURATION UPDATE message it shall respond with the E2 NODE CONFIGURATION UPDATE FAILURE message with an appropriate cause value. If the E2 NODE CONFIGURATION UPDATE FAILURE message includes the Time To Wait IE the E2 Node shall wait at least for the indicated time before reinitiating the E2 Node Configuration Update procedure towards the same Near-RT RIC. ETSI ETSI TS 104 039 V4.0.0 (2024-10) 34 If the Near-RT RIC receives an E2 NODE CONFIGURATION UPDATE message containing an E2 Node Component Configuration Update Item IE for an E2 Node component that was not previously declared by an E2 Node Component Configuration Addition Item IE then the Near-RT RIC shall indicate to the E2 Node that the update failed with appropriate cause value. If the E2 Node Configuration Update procedure failure occurs, the Near-RT RIC and E2 Node shall continue to operate with their existing configuration data. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.3.5.4 Abnormal Conditions | Void. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.3.6 E2 Connection Update procedure | |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.3.6.1 General | The purpose of the E2 Connection Update procedure is to allow the Near-RT RIC to update the TNL information associated with the E2 interface connection between the E2 Node and Near-RT RIC. This procedure shall be initiated by the Near-RT RIC. This procedure uses E2 Support Function signalling. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.3.6.2 Successful Operation | Figure 8.3.6.2-1: E2 Connection Update procedure, successful operation The Near-RT RIC initiates the procedure by sending a E2 CONNECTION UPDATE message to the E2 Node. The message shall include an appropriate set of up-to-date E2 interface connection data that the E2 Node shall take into account when modifying the E2 interface connection. Upon reception of a E2 CONNECTION UPDATE message, the E2 Node shall update as follows: - If E2 Connection To Add List IE is contained in the E2 CONNECTION UPDATE message, then the E2 Node shall, if supported, use the information to establish additional TNL Association(s) and configure for use for RIC services and/or E2 support functions according to the TNL Association Usage IE in the message. - If E2 Connection To Modify List IE is contained in the E2 CONNECTION UPDATE message, then the E2 Node shall, if supported, use the information to modify the existing usage for RIC services and/or E2 support functions, according to the TNL Association Usage IE in the message. - If E2 Connection To Remove List IE is contained in the E2 CONNECTION UPDATE message, then the E2 Node shall, if supported, use the information to remove the existing connection(s). If only one connection remains after successful removal of other connections, the E2 Node shall use this remaining connection for all the RIC services and E2 support functions. After successful update of E2 interface connection(s), the E2 Node shall reply with the E2 CONNECTION UPDATE ACKNOWLEDGE message to inform the initiating Near-RT RIC that the requested E2 connection update was performed successfully. ETSI ETSI TS 104 039 V4.0.0 (2024-10) 35 If the E2 Node receives a E2 CONNECTION UPDATE message without any IE except for Message Type IE and Transaction ID IE, the E2 Node shall reply with the E2 CONNECTION ACKNOWLEDGE message without performing any updates to the existing connections. E2 NODE CONFIGURATION UPDATE procedure shall be the first E2AP procedure triggered on an additional TNLA of an already setup E2 interface instance after the TNL association has become operational, and the Near-RT RIC shall associate the TNLA to the E2 interface instance using the included Global E2 Node ID. An empty E2 NODE CONFIGURATION UPDATE message (i.e. without any IE expect for Message Type IE and Transaction ID IE) shall be sent by the Near-RT RIC as the first E2AP procedure on the new TNLA, if the E2 Node does not have any Configuration to be updated to Near-RT RIC. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.3.6.3 Unsuccessful Operation | Figure 8.3.6.3-1: E2 Connection Update procedure, unsuccessful operation If the E2 Node cannot accept the update, it shall respond with a E2 CONNECTION UPDATE FAILURE message with an appropriate cause value. If the E2 CONNECTION UPDATE FAILURE message includes the Time To Wait IE, the Near-RT RIC shall wait at least for the indicated time before reinitiating the E2 Connection Update procedure towards the same E2 Node. Both nodes shall continue to operate with their existing connection(s). |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.3.6.4 Abnormal Conditions | Void. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.3.7 E2 Removal procedure | |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.3.7.1 General | The purpose of the E2 removal procedure is to remove the E2 signalling connection between the Near-RT RIC and the E2 node in a controlled manner. This procedure shall be initiated by the E2 Node or the Near-RT RIC. This procedure uses E2 Support Function signalling. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.3.7.2 Successful Operation | This procedure may be initiated by either Near-RT RIC or E2 Node. ETSI ETSI TS 104 039 V4.0.0 (2024-10) 36 Successful E2 Removal, E2 Node initiated Figure 8.3.7.2-1: E2 Removal, successful operation (E2 Node Initiated) The E2 Node shall initiate the procedure by sending the E2 REMOVAL REQUEST message to the Near-RT RIC. Upon reception of the E2 REMOVAL REQUEST message, the Near-RT RIC shall reply with the E2 REMOVAL RESPONSE message. After receiving the E2 REMOVAL RESPONSE message, the E2 Node shall initiate removal of the TNL association towards the Near-RT RIC, and shall release all resources associated with that E2 signalling connection. The Near-RT RIC shall then release all resources associated with that E2 signalling connection and erase all application level data. Successful E2 Removal, Near-RT RIC initiated Figure 8.3.7.2-2: E2 Removal, successful operation (Near-RT RIC Initiated) The Near-RT RIC shall initiate the procedure by sending the E2 REMOVAL REQUEST message to the E2 node. Upon reception of the E2 REMOVAL REQUEST message, the E2 node shall reply with the E2 REMOVAL RESPONSE message. After receiving the E2 REMOVAL RESPONSE message, the Near-RT RIC may initiate removal of the TNL association towards the E2 node, and shall release all resources associated with that E2 signalling connection and erase all application level data. The E2 node shall then release all resources associated with that E2 signalling connection. Interactions with other procedures: If the E2 REMOVAL REQUEST message is received, any other ongoing procedure on the same E2 interface related to ongoing RIC Services shall be aborted. ETSI ETSI TS 104 039 V4.0.0 (2024-10) 37 |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.3.7.3 Unsuccessful Operation | Figure 8.3.7.3-1: E2 Removal procedure (E2 Node Initiated), unsuccessful operation Figure 8.3.7.3-2: E2 Removal procedure (Near-RT RIC Initiated), unsuccessful operation If the E2 Node cannot accept the E2 REMOVAL REQUEST it shall respond with E2 REMOVAL FAILURE message with an appropriate cause value. If the Near-RT RIC cannot accept the E2 REMOVAL REQUEST it shall respond with E2 REMOVAL FAILURE message with an appropriate cause value. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.3.7.4 Abnormal Conditions | Void. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9 Elements for E2AP Communication | |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.0 General | Clauses 9.1 and 9.2 describe the structure of the messages and information elements required for the E2AP protocol in tabular format. Clause 9.3 provides the corresponding ASN.1 definition. The following attributes are used for the tabular description of the messages and information elements: Presence, Range Criticality and Assigned Criticality. Their definition and use can be found in ETSI TS 136 413 [24]. NOTE: The messages have been defined in accordance with the guidelines specified in ETSI TR 125 921 [i.2]. ETSI ETSI TS 104 039 V4.0.0 (2024-10) 38 |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.1 Message Functional Definition and Content | |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.1.1 Messages for RIC Functional Procedures | |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.1.1.1 RIC SUBSCRIPTION REQUEST | This message is sent by the Near-RT RIC to an E2 Node to create a new RIC Subscription in the E2 Node. Direction: Near-RT RIC β E2 Node. IE/Group Name Presence Range IE type and reference Semantics description Criticality Assigned Criticality Message Type M 9.2.3 YES reject RIC Request ID M 9.2.7 YES reject RAN Function ID M 9.2.8 YES reject RIC Subscription Details M YES reject >RIC Event Trigger Definition M 9.2.9 - >Sequence of Actions 1.. <maxofRICactionID> EACH ignore >>RIC Action ID M 9.2.10 - >>RIC Action Type M 9.2.11 - >>RIC Action Definition O 9.2.12 - >>RIC Subsequent Action O 9.2.13 - >>RIC Action Execution Order O 9.2.35 Used to define a specific execution order - RIC Subscription Start Time O 9.2.34 YES reject RIC Subscription End Time O 9.2.34 YES reject Range bound Explanation maxofRICActionID Maximum no. of Actions to be requested by Near-RT RIC. Value is 16. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.1.1.2 RIC SUBSCRIPTION RESPONSE | This message is sent by the E2 Node to accept the request from the Near-RT RIC to create a new RIC Subscription in the E2 Node. Direction: E2 Node β Near-RT RIC. IE/Group Name Presence Range IE type and reference Semantics description Criticality Assigned Criticality Message Type M 9.2.3 YES reject RIC Request ID M 9.2.7 YES reject RAN Function ID M 9.2.8 YES reject RIC Actions Admitted List 1.. <maxofRICactionID> YES reject >RIC Action ID M 9.2.10 - RIC Actions Not Admitted List 0.. <maxofRICactionID> YES reject >RIC Action ID M 9.2.10 - >Cause M 9.2.1 - Range bound Explanation maxofRICActionID Maximum no. of Actions to be requested by Near-RT RIC. Value is 16. ETSI ETSI TS 104 039 V4.0.0 (2024-10) 39 |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.1.1.3 RIC SUBSCRIPTION FAILURE | This message is sent by the E2 Node to inform the Near-RT RIC that the request to create a new RIC Subscription in the E2 Node failed. Direction: E2 Node β Near-RT RIC. IE/Group Name Presence Range IE type and reference Semantics description Criticality Assigned Criticality Message Type M 9.2.3 YES reject RIC Request ID M 9.2.7 YES reject RAN Function ID M 9.2.8 YES reject Cause M 9.2.1 YES reject Criticality Diagnostics O 9.2.2 YES ignore |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.1.1.4 RIC SUBSCRIPTION DELETE REQUEST | This message is sent by the Near-RT RIC to an E2 Node to request the deletion of an existing Subscription in the E2 Node. Direction: Near-RT RIC β E2 Node. IE/Group Name Presence Range IE type and reference Semantics description Criticality Assigned Criticality Message Type M 9.2.3 YES reject RIC Request ID M 9.2.7 YES reject RAN Function ID M 9.2.8 YES reject |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.1.1.5 RIC SUBSCRIPTION DELETE RESPONSE | This message is sent by the E2 Node to accept the request from a Near-RT RIC to delete an existing RIC Subscription in the E2 Node Direction: E2 Node β Near-RT RIC. IE/Group Name Presence Range IE type and reference Semantics description Criticality Assigned Criticality Message Type M 9.2.3 YES reject RIC Request ID M 9.2.7 YES reject RAN Function ID M 9.2.8 YES reject |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.1.1.6 RIC SUBSCRIPTION DELETE FAILURE | This message is sent by the E2 Node to inform the Near-RT RIC that the request to delete an existing RIC Subscription in the E2 Node failed. Direction: E2 Node β Near-RT RIC. IE/Group Name Presence Range IE type and reference Semantics description Criticality Assigned Criticality Message Type M 9.2.3 YES reject RIC Request ID M 9.2.7 YES reject RAN Function ID M 9.2.8 YES reject Cause M 9.2.1 YES ignore Criticality Diagnostics O 9.2.2 YES ignore ETSI ETSI TS 104 039 V4.0.0 (2024-10) 40 |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.1.1.6A RIC SUBSCRIPTION DELETE REQUIRED | This message is sent by the E2 Node to request deletion of the existing RIC Subscriptions in the E2 Node. Direction: E2 Node β Near-RT RIC. IE/Group Name Presence Range IE type and reference Semantics description Criticality Assigned Criticality Message Type M 9.2.3 YES reject List of RIC Subscriptions To Be Removed 1.. <maxofRICreque stID> EACH ignore >RIC Request ID M 9.2.7 - - >RAN Function ID M 9.2.8 - - >Cause M 9.2.1 - - Range bound Explanation maxofRICrequestID Maximum no. of RIC subscription requests supported by Near-RT RIC toward an E2 Node. Value is <1024>. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.1.1.7 RIC INDICATION | This message is sent by an E2 Node to transfer Report and Insert RIC Service Action information to a Near-RT RIC. Direction: E2 Node β Near-RT RIC. IE/Group Name Presence Range IE type and reference Semantics description Criticality Assigned Criticality Message Type M 9.2.3 YES reject RIC Request ID M 9.2.7 YES reject RAN Function ID M 9.2.8 YES reject RIC Action ID M 9.2.10 YES reject RIC Indication SN O 9.2.14 YES reject RIC Indication Type M 9.2.15 YES reject RIC Indication Header M 9.2.17 YES reject RIC Indication Message M 9.2.16 YES reject RIC Call process ID O 9.2.18 YES reject |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.1.1.8 RIC CONTROL REQUEST | This message is sent by a Near-RT RIC to an E2 Node to initiate or resume a control function logic. Direction: Near-RT RIC β E2 Node. IE/Group Name Presence Range IE type and reference Semantics description Criticality Assigned Criticality Message Type M 9.2.3 YES reject RIC Request ID M 9.2.7 YES reject RAN Function ID M 9.2.8 YES reject RIC Call Process ID O 9.2.18 YES reject RIC Control Header M 9.2.20 YES reject RIC Control Message M 9.2.19 YES reject RIC Control Ack Request O 9.2.21 YES reject ETSI ETSI TS 104 039 V4.0.0 (2024-10) 41 |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.1.1.9 RIC CONTROL ACKNOWLEDGE | This message is sent by the E2 Node to inform the Near-RT RIC that the RIC CONTROL REQUEST message was received and to provide information on the outcome of the request. Direction: E2 Node β Near-RT RIC. IE/Group Name Presence Range IE type and reference Semantics description Criticality Assigned Criticality Message Type M 9.2.3 YES reject RIC Request ID M 9.2.7 YES reject RAN Function ID M 9.2.8 YES reject RIC Call process ID O 9.2.18 YES reject RIC Control Outcome O 9.2.25 YES reject |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.1.1.10 RIC CONTROL FAILURE | This message is sent by the E2 Node to inform the Near-RT RIC that the RIC CONTROL REQUEST message has failed to be executed. Direction: E2 Node β Near-RT RIC. IE/Group Name Presence Range IE type and reference Semantics description Criticality Assigned Criticality Message Type M 9.2.3 YES reject RIC Request ID M 9.2.7 YES reject RAN Function ID M 9.2.8 YES reject RIC Call process ID O 9.2.18 YES reject Cause M 9.2.1 YES ignore RIC Control Outcome O 9.2.25 YES Reject Criticality Diagnostics O 9.2.2 YES ignore ETSI ETSI TS 104 039 V4.0.0 (2024-10) 42 |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.1.1.11 RIC SUBSCRIPTION MODIFICATION REQUEST | This message is sent by the Near-RT RIC to an E2 Node to modify an existing Subscription in the E2 Node. Direction: Near-RT RIC β E2 Node. IE/Group Name Presence Range IE type and reference Semantics description Criticality Assigned Criticality Message Type M 9.2.3 YES reject RIC Request ID M 9.2.7 YES reject RAN Function ID M 9.2.8 YES reject RIC Event Trigger Definition to be Modified O 9.2.9 YES ignore RIC Actions to be Removed List 0..1 YES ignore >Action to be Removed Item IEs 1..<maxofRICacti onID> EACH ignore >>RIC Action ID M 9.2.10 - RIC Actions to be Modified List 0..1 YES ignore >Action to be Modified Item IEs 1..<maxofRICacti onID> EACH ignore >>RIC Action ID M 9.2.10 - >>RIC Action Definition O 9.2.12 - >>RIC Action Execution Order O 9.2.35 >>RIC Subsequent Action O 9.2.13 - RIC Actions to be Added List 0..1 YES ignore >Action to be Added Item IEs 1..<maxofRICacti onID> EACH ignore >>RIC Action ID M 9.2.10 - >>RIC Action Type M 9.2.11 - >>RIC Action Definition M 9.2.12 - >>RIC Action Execution Order M 9.2.35 >>RIC Subsequent Action O 9.2.13 - Range bound Explanation maxofRICActionID Maximum no. of Actions to be requested by Near-RT RIC. Value is 16. ETSI ETSI TS 104 039 V4.0.0 (2024-10) 43 |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.1.1.12 RIC SUBSCRIPTION MODIFICATION RESPONSE | This message is sent by the E2 Node to accept the request from the Near-RT RIC to modify an existing E2 subscription in the E2 Node. Direction: E2 Node β Near-RT RIC. IE/Group Name Presence Range IE type and reference Semantics description Criticality Assigned Criticality Message Type M 9.2.3 YES reject RIC Request ID M 9.2.7 YES reject RAN Function ID M 9.2.8 YES reject RIC Actions Removed List 0..1 YES ignore >Action Removed Item IEs 1..<maxofRICacti onID> EACH ignore >>RIC Action ID M 9.2.10 - RIC Actions Failed to be Removed List 0..1 YES ignore >Action Failed to be Removed Item IEs 1..<maxofRICacti onID> EACH ignore >>RIC Action ID M 9.2.10 - >>Cause M 9.2.1 - RIC Actions Modified List 0..1 YES ignore >Action Modified Item IEs 1..<maxofRICacti onID> EACH ignore >>RIC Action ID M 9.2.10 - RIC Actions Failed to be Modified List 0..1 YES ignore >Action Failed to be Modified Item IEs 1..<maxofRICacti onID> EACH ignore >>RIC Action ID M 9.2.10 - >>Cause M 9.2.1 - RIC Actions Added List 0..1 YES ignore >Action Added Item IEs 1..<maxofRICacti onID> EACH ignore >>RIC Action ID M 9.2.10 - RIC Actions Failed to be Added List 0..1 YES ignore >Action Failed to be Added Item IEs 1..<maxofRICacti onID> EACH Ignore >>RIC Action ID M 9.2.10 - >>Cause M 9.2.1 - Range bound Explanation maxofRICActionID Maximum no. of Actions to be requested by Near-RT RIC. Value is 16. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.1.1.13 RIC SUBSCRIPTION MODIFICATION FAILURE | This message is sent by the E2 Node to inform the Near-RT RIC that the request to modify an existing E2 subscription in the E2 Node failed. Direction: E2 Node β Near-RT RIC. IE/Group Name Presence Range IE type and reference Semantics description Criticality Assigned Criticality Message Type M 9.2.3 YES reject RIC Request ID M 9.2.7 YES reject RAN Function ID M 9.2.8 YES reject Cause M 9.2.1 YES reject Criticality Diagnostics O 9.2.2 YES ignore ETSI ETSI TS 104 039 V4.0.0 (2024-10) 44 |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.1.1.14 RIC SUBSCRIPTION MODIFICATION REQUIRED | This message is sent by the E2 Node to request the Near-RT RIC to modify an existing E2 subscription in the E2 Node. Direction: E2 Node β Near-RT RIC. IE/Group Name Presence Range IE type and reference Semantics description Criticality Assigned Criticality Message Type M 9.2.3 YES reject RIC Request ID M 9.2.7 YES reject RAN Function ID M 9.2.8 YES reject RIC Actions Required to be Modified List 0..1 YES ignore >Action Required to be Modified Item IEs EACH ignore >>RIC Action ID M 9.2.10 - >>RIC Time to Wait before subsequent action M ENUMERATED (1ms, 2ms, 5ms, 10ms, 20ms, 30ms, 40ms, 50ms, 100ms, 200ms, 500ms, 1s, 2s, 5s, 10s, 20s, 60s, β¦) - RIC Actions Required to be Removed List 0..1 YES ignore >Action Required to be Removed Item IEs 1..<maxofRICacti onID> EACH ignore >>RIC Action ID M 9.2.10 - >>Cause M 9.2.1 - Range bound Explanation maxofRICActionID Maximum no. of Actions to be requested by Near-RT RIC. Value is 16. ETSI ETSI TS 104 039 V4.0.0 (2024-10) 45 |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.1.1.15 RIC SUBSCRIPTION MODIFICATION CONFIRM | This message is sent by the Near-RT RIC to accept the request from the E2 Node to modify an existing E2 subscription in the E2 Node. Direction: Near-RT RIC β E2 Node. IE/Group Name Presence Range IE type and reference Semantics description Criticality Assigned Criticality Message Type M 9.2.3 YES reject RIC Request ID M 9.2.7 YES reject RAN Function ID M 9.2.8 YES reject RIC Actions Confirmed for Modification List 0..1 YES ignore >RIC Action Confirmed for Modification Item IEs 1..<maxofRICacti onID> EACH ignore >>RIC Action ID M 9.2.10 - RIC Actions Refused to be Modified List 0..1 YES ignore >Action Refused to be Modified Item IEs 1..<maxofRICacti onID> EACH ignore >>RIC Action ID M 9.2.10 - >>Cause M 9.2.1 - RIC Actions Confirmed for Removal List 0..1 YES ignore >Action Confirmed for Removal Item IEs 1..<maxofRICacti onID> EACH ignore >>RIC Action ID M 9.2.10 - RIC Actions Refused to be Removed List 0..1 YES ignore >Action Refused to be Removed Item IEs 1..<maxofRICacti onID> EACH ignore >>RIC Action ID M 9.2.10 - >>Cause M 9.2.1 - Range bound Explanation maxofRICActionID Maximum no. of Actions to be requested by Near-RT RIC. Value is 16. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.1.1.16 RIC SUBSCRIPTION MODIFICATION REFUSE | This message is sent by the Near-RT RIC to deny the request from the E2 Node to modify an existing E2 subscription in the E2 Node. Direction: Near-RT RIC β E2 Node. IE/Group Name Presence Range IE type and reference Semantics description Criticality Assigned Criticality Message Type M 9.2.3 YES reject RIC Request ID M 9.2.7 YES reject RAN Function ID M 9.2.8 YES reject Cause M 9.2.1 YES reject Criticality Diagnostics O 9.2.2 YES ignore ETSI ETSI TS 104 039 V4.0.0 (2024-10) 46 |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.1.1.17 RIC QUERY REQUEST | This message is sent by the Near-RT RIC to an E2 Node to request RAN and/or UE related information from the E2 Node. Direction: Near-RT RIC β E2 Node. IE/Group Name Presence Range IE type and reference Semantics description Criticality Assigned Criticality Message Type M 9.2.3 YES reject RIC Request ID M 9.2.7 YES reject RAN Function ID M 9.2.8 YES reject RIC Query Header M 9.2.36 YES reject RIC Query Definition M 9.2.37 YES reject |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.1.1.18 RIC QUERY RESPONSE | This message is sent by the E2 Node to Near-RT RIC in response to RAN and/or UE related information requested by Near-RT RIC. Direction: E2 Node β Near-RT RIC. IE/Group Name Presence Range IE type and reference Semantics description Criticality Assigned Criticality Message Type M 9.2.3 YES reject RIC Request ID M 9.2.7 YES reject RAN Function ID M 9.2.8 YES reject RIC Query Outcome M 9.2.38 YES reject |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.1.1.19 RIC QUERY FAILURE | This message is sent by the E2 Node to inform the Near-RT RIC that the requested RAN and/or UE related Information has failed. Direction: E2 Node β Near-RT RIC. IE/Group Name Presence Range IE type and reference Semantics description Criticality Assigned Criticality Message Type M 9.2.3 YES reject RIC Request ID M 9.2.7 YES reject RAN Function ID M 9.2.8 YES reject Cause M 9.2.1 YES reject Criticality Diagnostics O 9.2.2 YES ignore ETSI ETSI TS 104 039 V4.0.0 (2024-10) 47 |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.1.2 Messages for Global Procedures | |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.1.2.1 ERROR INDICATION | This message is used to indicate that some error has been detected in the E2 Node or Near-RT RIC. Direction: E2 Node β Near-RT RIC or Near-RT RIC β E2 Node. IE/Group Name Presence Range IE type and reference Semantics description Criticality Assigned Criticality Message Type M 9.2.3 YES ignore Transaction ID O 9.2.33 Required if RIC Request ID IE is not present YES reject RIC Request ID O 9.2.7 Required if Transaction ID IE is not present YES reject RAN Function ID O 9.2.8 YES reject Cause O 9.2.1 YES ignore Criticality Diagnostics O 9.2.2 YES ignore |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.1.2.2 E2 SETUP REQUEST | This message is sent by an E2 Node to a Near-RT RIC to transfer the initialization information. Direction: E2 Node ο Near-RT RIC. IE/Group Name Presence Range IE type and reference Semantics description Criticality Assigned Criticality Message Type M 9.2.3 YES reject Transaction ID M 9.2.33 . YES reject Global E2 Node ID M 9.2.6 YES reject RAN Functions Added List 1 List of RAN functions in E2 node YES reject >RAN Function item 1.. <maxofRANfuncti onID> >>RAN Function ID M 9.2.8 Id of the declared Function - >>RAN Function Definition M 9.2.23 Definition of Function - >>RAN Function Revision M 9.2.24 Revision counter - >>RAN Function OID M 9.2.31 Object identifier of corresponding E2SM - E2 Node Component Configuration Addition List 1 List of E2 Node component configuration information YES reject >E2 Node Component Configuration Addition Item 1.. <maxofE2nodeCo mponents> EACH reject >>E2 Node Component Interface Type M 9.2.26 E2 Node component interface type - >>E2 Node Component ID O 9.2.32 E2 Node Component Identifier - >>E2 Node Component Configuration M 9.2.27 Contents depends on component interface type - ETSI ETSI TS 104 039 V4.0.0 (2024-10) 48 Range bound Explanation maxofRANfunctionID Maximum no. of RAN Functions supported by E2 Node. Value is 256. maxofE2nodeComponents Maximum no. of E2 Node components supported by E2 Node. Value is 1024. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.1.2.3 E2 SETUP RESPONSE | This message is sent by a Near-RT RIC to an E2 Node to transfer the initialization information. Direction: Near-RT RIC βE2 Node. IE/Group Name Presence Range IE type and reference Semantics description Criticality Assigned Criticality Message Type M 9.2.3 YES reject Transaction ID M 9.2.33 . YES reject Global RIC ID M 9.2.4 YES reject RAN Functions Accepted List 0..1 Complete list of Functions accepted by Near-RT RIC >RAN Functions ID item 1 .. <maxofRANfuncti onID> YES Reject >>RAN Function ID M 9.2.8 Id of the declared Function - >>RAN Function Revision M 9.2.24 Revision counter - RAN Functions Rejected List 0..1 Complete list of Functions not accepted by Near-RT RIC RAN Functions ID Cause Item 1 .. <maxofRANfuncti onID> YES reject >>RAN Function ID M 9.2.8 Id of the declared Function - >>Cause M 9.2.1 Reason for not accepting function - E2 Node Component Configuration Addition Acknowledge List 1 Complete list of E2 Node Components in the E2 SETUP REQUEST message YES reject >E2 Node Component Configuration Addition Acknowledge Item 1.. <maxofE2nodeCo mponents> EACH reject >>E2 Node Component Interface Type M 9.2.26 E2 Node component interface type - >>E2 Node Component ID M 9.2.32 E2 Node Component Identifier - >>E2 Node Component Configuration Acknowledge M 9.2.28 Success or failure with Cause - Range bound Explanation maxofRANfunctionID Maximum no. of RAN Functions supported by E2 Node. Value is 256. maxofE2nodeComponents Maximum no. of E2 Node components supported by E2 Node. Value is 1024. ETSI ETSI TS 104 039 V4.0.0 (2024-10) 49 |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.1.2.4 E2 SETUP FAILURE | This message is sent by the Near-RT RIC to indicate E2 Setup failure. Direction: Near-RT RIC β E2 Node. IE/Group Name Presence Range IE type and reference Semantics description Criticality Assigned Criticality Message Type M 9.2.3 YES reject Transaction ID M 9.2.33 . YES reject Cause M 9.2.1 YES ignore Time To Wait O 9.2.5 YES ignore Criticality Diagnostics O 9.2.2 YES Ignore Transport Layer Information O 9.2.29 YES ignore |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.1.2.5 RESET REQUEST | This message is sent from a Near-RT RIC to an E2 Node or from an E2 Node to a Near-RT RIC and is used to request the E2 interface between the E2 node and the Near-RT RIC to be reset. Direction: Near-RT RIC β E2 Node, or E2 Node β Near-RT RIC. IE/Group Name Presence Range IE type and reference Semantics description Criticality Assigned Criticality Message Type M 9.2.3 YES reject Transaction ID M 9.2.33 YES reject Cause M 9.2.1 YES ignore |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.1.2.6 RESET RESPONSE | This message is sent by an E2 Node to a Near-RT RIC or from a Near-RT RIC to an E2 Node as a response to a RESET REQUEST message. Direction: Near-RT RIC β E2 Node, or E2 Node β Near-RT RIC. IE/Group Name Presence Range IE type and reference Semantics description Criticality Assigned Criticality Message Type M 9.2.3 YES reject Transaction ID M 9.2.33 . YES reject Criticality Diagnostics O 9.2.2 YES ignore ETSI ETSI TS 104 039 V4.0.0 (2024-10) 50 |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.1.2.7 RIC SERVICE UPDATE | This message is sent by an E2 Node to the Near-RT RIC to transfer updated information on RIC Services supported by the E2 Node. Direction: E2 Node β Near-RT RIC. IE/Group Name Presence Range IE type and reference Semantics description Criticality Assigned Criticality Message Type M 9.2.3 YES reject Transaction ID M 9.2.33 . YES reject RAN Functions Added List 0..1 List of added RAN functions in E2 node >RAN Functions Item 1 .. <maxofRANfuncti onID> YES reject >>RAN Function ID M 9.2.8 Id of the declared Function - >>RAN Function Definition M 9.2.23 Definition of Function - >>RAN Function Revision M 9.2.24 Revision counter - >>RAN Function OID M 9.2.31 Object identifier of corresponding E2SM - RAN Functions Modified List 0..1 List of Modified RAN functions in E2 node >RAN Functions Item 1 .. <maxofRANfuncti onID> YES reject >>RAN Function ID M 9.2.8 Id of the declared Function - >>RAN Function Definition M 9.2.23 Definition of Function - >>RAN Function Revision M 9.2.24 Revision counter - >>RAN Function OID M 9.2.31 Object identifier of corresponding E2SM - RAN Functions Deleted List 0..1 List of deleted RAN functions in E2 node >RAN Functions ID Item 1 .. <maxofRANfuncti onID> YES reject >>RAN Function ID M 9.2.8 Id of the declared Function - >>RAN Function Revision M 9.2.24 Revision counter - Range bound Explanation maxofRANfunctionID Maximum no. of Functions accepted by Near-RT RIC. Value is 256. ETSI ETSI TS 104 039 V4.0.0 (2024-10) 51 |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.1.2.8 RIC SERVICE UPDATE ACKNOWLEDGE | This message is sent by the Near-RT RIC to the E2 Node to acknowledge update of RIC Services supported by the E2 Node. Direction: Near-RT RIC β E2 Node. IE/Group Name Presence Range IE type and reference Semantics description Criticality Assigned Criticality Message Type M 9.2.3 YES reject Transaction ID M 9.2.33 . YES reject RAN Functions Accepted List 0..1 List of Functions accepted by Near-RT RIC >RAN Functions ID Item 1 .. <maxofRANfuncti onID> YES reject >>RAN Function ID M 9.2.8 Id of the declared Function - >>RAN Function Revision M 9.2.24 Revision counter - RAN Functions Rejected List 0..1 List of Functions not accepted by Near-RT RIC >RAN Functions Cause Item 1 .. <maxofRANfuncti onID> YES reject >>RAN Function ID M 9.2.8 Id of the declared Function - >>Cause M 9.2.1 Reason for not accepting function - Range bound Explanation maxofRANfunctionID Maximum no. of Functions accepted by Near-RT RIC. Value is 256. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.