hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.1.2.9 RIC SERVICE UPDATE FAILURE | This message is sent by the Near-RT RIC to the E2 Node to indicate RIC SERVICE Update 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 Reason for failure YES reject Time To Wait O 9.2.5 YES ignore Criticality Diagnostics O 9.2.2 YES ignore ETSI ETSI TS 104 039 V4.0.0 (2024-10) 52 |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.1.2.10 RIC SERVICE QUERY | This message is sent by a Near-RT RIC to an E2 Node to request a E2 Node initiated RIC Service Update procedure. 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 Complete list of Functions previously 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 - 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) 53 |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.1.2.11 E2 NODE CONFIGURATION UPDATE | This message is sent by an E2 Node to the Near-RT RIC to transfer updated information on the E2 Node Configuration 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 O 9.2.6 Required when sent as first message on new TNL association. YES reject E2 Node Component Configuration Addition List 0..1 YES reject >E2 Node Component Configuration Addition Item 1.. <maxofE2nodeC omponents> 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 M 9.2.27 Contents depends on component type. - E2 Node Component Configuration Update List 0..1 YES reject >E2 Node Component Configuration Update Item 1.. <maxofE2nodeC omponents> 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 M 9.2.27 Contents depends on component type. - E2 Node Component Configuration Removal List 0..1 YES reject >E2 Node Component Configuration Removal Item 1.. <maxofE2nodeC omponents> 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 TNL Association To Remove List 0..1 YES reject >E2 Node TNL Association To Remove Item IEs 1..<maxofTNLA> EACH reject >> Transport Layer Information M 9.2.29 Transport Layer Address of the E2 node. - - >> Transport Layer Information Near-RT RIC O 9.2.29 Transport Layer Address of the Near-RT RIC. - - ETSI ETSI TS 104 039 V4.0.0 (2024-10) 54 Range bound Explanation maxofE2nodeComponents Maximum no. of E2 Node components supported by E2 Node. Value is 1024. maxofTNLA Maximum no. of TNL Associations supported by E2 Node. Value is 32. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.1.2.12 E2 NODE CONFIGURATION UPDATE ACKNOWLEDGE | This message is sent by Near-RT RIC to E2 Node to acknowledge update of E2 Node Configuration 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 E2 Node Component Configuration Addition Acknowledge List 0..1 YES reject >E2 Node Component Configuration Addition Acknowledge Item 1.. <maxofE2nodeC omponents> 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 - E2 Node Component Configuration Update Acknowledge List 0..1 YES reject >E2 Node Component Configuration Update Acknowledge Item 1.. <maxofE2nodeC omponents> 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 Update Acknowledge M 9.2.28 Success or failure with Cause - E2 Node Component Configuration Removal Acknowledge List 0..1 YES reject >E2 Node Component Configuration Removal Acknowledge Item 1.. <maxofE2nodeC omponents> 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 maxofE2nodeComponents Maximum no. of E2 Node components supported by E2 Node. Value is 1024. ETSI ETSI TS 104 039 V4.0.0 (2024-10) 55 |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.1.2.13 E2 NODE CONFIGURATION UPDATE FAILURE | This message is sent by Near-RT RIC to E2 Node to indicate E2 Node Configuration Update 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 |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.2.1 Cause | YES reject Time To Wait O 9.2.5 YES ignore Criticality Diagnostics O 9.2.2 YES ignore |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.1.2.14 E2 CONNECTION UPDATE | This message is sent by Near-RT RIC to E2 Node to initiate update of E2 Connection 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 E2 Connection To Add List 0..1 YES ignore >E2 Connection to Add Item IEs 1.. <maxofTNLA> EACH ignore >>Transport Layer Information M 9.2.29 Transport layer address and port number of Near-RT RIC >>TNL Association Usage M 9.2.30 Indicates how E2 connection is to be used E2 Connection To Remove List 0..1 YES ignore >E2 Connection to Remove Item IEs 1.. <maxofTNLA> EACH ignore >>Transport Layer Information M 9.2.29 Transport layer address and port number of Near-RT RIC E2 Connection To Modify List 0..1 YES ignore >E2 Connection to Modify Item IEs 1.. <maxofTNLA> EACH ignore >>Transport Layer Information M 9.2.29 Transport layer address and port number of Near-RT RIC >>TNL Association Usage M 9.2.30 Indicates how E2 connection is to be used Range bound Explanation maxofTNLA Maximum no. of TNL Associations supported by E2 Node. Value is 32. ETSI ETSI TS 104 039 V4.0.0 (2024-10) 56 |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.1.2.15 E2 CONNECTION UPDATE ACKNOWLEDGE | This message is sent by E2 Node to the Near-RT RIC to acknowledge update of E2 Connection 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 E2 Connection Setup List 0..1 YES ignore >E2 Connection Setup Item IEs 1.. <maxofTNLA> EACH ignore >>Transport Layer Information M 9.2.29 Transport layer address and port number of Near-RT RIC >>TNL Association Usage M 9.2.30 Indicates how E2 connection is to be used E2 Connection Failed to Setup List 0..1 YES ignore >E2 Connection failed to setup Item IEs 1.. <maxofTNLA> EACH ignore >>Transport Layer Information M 9.2.29 Transport layer address and port number of Near-RT RIC >>Cause M 9.2.1 Range bound Explanation maxofTNLA Maximum no. of TNL Associations supported by E2 Node. Value is 32. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.1.2.16 E2 CONNECTION UPDATE FAILURE | This message is sent by E2 Node to the Near-RT RIC to inform failure of the requested E2 Connection updates. 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 Cause M 9.2.1 YES reject Time To Wait O 9.2.5 YES ignore Criticality Diagnostics O 9.2.2 YES ignore |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.1.2.17 E2 REMOVAL REQUEST | This message is sent by either the E2 Node or the Near-RT RIC to initiate the removal of the E2 signalling connection and the related resources. 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 ETSI ETSI TS 104 039 V4.0.0 (2024-10) 57 |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.1.2.18 E2 REMOVAL RESPONSE | This message is sent by either the E2 Node or the Near-RT RIC to acknowledge the initiation of removal of the E2 signalling connection and the related resources. 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 |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.1.2.19 E2 REMOVAL FAILURE | This message is sent by either the E2 Node or the Near-RT RIC to indicate that removing the E2 signalling connection and the related resources cannot be accepted. 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 Criticality Diagnostics O 9.2.2 YES ignore |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.2 Information Element definitions | |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.2.0 General | When specifying information elements which are to be represented by bit strings, if not otherwise specifically stated in the semantics description of the concerned IE or elsewhere, the following principle applies with regards to the ordering of bits: - The first bit (leftmost bit) contains the Most Significant Bit (MSB); - The last bit (rightmost bit) contains the Least Significant Bit (LSB); - When importing bit strings from other specifications, the first bit of the bit string contains the first bit of the concerned information. 9.2.1 Cause The purpose of the Cause IE is to indicate the reason for a particular event for the E2AP protocol. ETSI ETSI TS 104 039 V4.0.0 (2024-10) 58 IE/Group Name Presence Range IE Type and Reference Semantics Description CHOICE Cause Group M >RIC services >>RIC Request O ENUMERATED (RAN Function ID invalid, Action not supported, Excessive actions, Duplicate action, Duplicate Event Trigger, Function resource limit, RIC Request ID unknown, Inconsistent Action/subsequent Action sequence, Control message invalid, RIC Call process ID invalid, Control timer expired, Control failed to execute, System not ready, unspecified, …, RIC Subscription End Time expired, RIC Subscription Time invalid, Duplicate RIC Request ID, Event Trigger not supported, Requested Information Unavailable, Invalid Information Request) >>RIC Service O ENUMERATED RAN Function not supported, Excessive functions, RIC resource limit, …) >>E2 Node O ENUMERATED (E2 node component unknown, …) >Transport Layer >>Transport Layer Cause M ENUMERATED (Unspecified, Transport Resource Unavailable, …) >Protocol >>Protocol Cause M ENUMERATED (Transfer Syntax Error, Abstract Syntax Error (Reject), Abstract Syntax Error (Ignore and Notify), Message not Compatible with Receiver State, Semantic Error, Abstract Syntax Error (Falsely Constructed Message), Unspecified, …) >Misc >>Miscellaneous Cause M ENUMERATED (Control Processing Overload, Hardware Failure, O&M Intervention, Unspecified, …) The meaning of the different cause values is described in the following table. In general, "not supported" cause values indicate that the related capability is missing. On the other hand, "not available" cause values indicate that the related capability is present, but insufficient resources are available to perform the requested action. ETSI ETSI TS 104 039 V4.0.0 (2024-10) 59 RIC Request cause Meaning Unspecified Sent for RIC service cause when none of the specified cause values applies. RAN Function ID invalid Requested function Id invalid or not known by E2 Node. Action not supported Requested Action not supported by RAN function. Excessive actions Excessive number of actions requested for RAN Function. Duplicate action Same action requested more than once in same subscription request. Duplicate Event Trigger Subscription request has same event trigger as previously accepted subscription request. Function resource limit RAN function has reached resource limit. RIC Request ID unknown RIC Request ID sent to Near-RT RIC is unknown. Inconsistent Action/subsequent Action sequence RAN Function has detected inconsistent sequence of requested Action and Subsequent Action. Control message invalid RAN Function has detected invalid RIC CONTROL REQUEST message. RIC Call process ID invalid RAN function has detected invalid RIC Call Process ID in RIC CONTROL REQUEST. Control timer expired RIC Control Request received by E2 Node after the associated RIC Time to Wait timer had expired. Control failed to execute Requested control procedure initiated by RIC Control Request failed to be executed in the E2 Node. System not ready RAN Function is not ready to receive RIC Subscription or RIC Control message. RIC Subscription End Time expired RIC SUBSCRIPTION DELETE REQUIRED is triggered to inform Near-RT RIC that end time has expired. RIC Subscription Time invalid E2 Node received RIC SUBSCRIPTION REQUEST containing an invalid RIC Subscription Start Time and/or RIC Subscription End Time. Duplicate RIC Request ID E2 node does not support handling of same RIC Request ID as previously accepted subscription request. Event Trigger not supported Requested event trigger definition or modification - not supported by RAN function. Requested Information Unavailable Information requested by Near-RT RIC is not available at E2 Node. Invalid Information Request Information requested by Near-RT RIC is invalid. RIC Service cause Meaning RAN Function not supported The RAN Function described by E2 Node is not supported by Near-RT RIC. Excessive functions RIC has reached a limit on the number of declared RAN functions. RIC resource limit RIC has reached a resource limit. E2 Node configuration cause Meaning E2 Node component unknown The received message refers to an unknown E2 Node component. Transport Layer cause Meaning Unspecified Sent when none of the cause values below applies but still the cause is Transport Network Layer related. Transport Resource Unavailable The required transport resources are not available. Protocol cause Meaning Transfer Syntax Error The received message included a transfer syntax error. Abstract Syntax Error (Reject) The received message included an abstract syntax error and the concerning criticality indicated "reject". Abstract Syntax Error (Ignore And Notify) The received message included an abstract syntax error and the concerning criticality indicated "ignore and notify". Message Not Compatible With Receiver State The received message was not compatible with the receiver state. Semantic Error The received message included a semantic error. Abstract Syntax Error (Falsely Constructed Message) The received message contained IEs or IE groups in wrong order or with too many occurrences. Unspecified Sent when none of the above cause values applies but still the cause is Protocol related. ETSI ETSI TS 104 039 V4.0.0 (2024-10) 60 Miscellaneous cause Meaning Control Processing Overload Control processing overload. Not Enough User Plane Processing Resources Available Not enough resources are available related to user plane processing. Hardware Failure Action related to hardware failure. O&M Intervention The action is due to O&M intervention. Unspecified Failure Sent when none of the above cause values applies and the cause is not related to any of the categories Radio Network Layer, Transport Network Layer, NAS or Protocol. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.2.2 Criticality Diagnostics | The Criticality Diagnostics IE is sent by the E2 Node or the Near-RT RIC when parts of a received message have not been comprehended, or were missing, or if the message contained logical errors. When applicable, it contains information about which IEs were not comprehended or were missing. For further details on how to use the Criticality Diagnostics IE see clause 10. The conditions for inclusion of the Transaction ID IE are described in clause 10. IE/Group Name Presence Range IE type and reference Semantics description Procedure Code O INTEGER (0..255) Procedure Code is to be used if Criticality Diagnostics is part of Error Indication procedure, and not within the response message of the same procedure that caused the error. Triggering Message O ENUMERATED (initiating message, successful outcome, unsuccessful outcome) The Triggering Message is used only if the Criticality Diagnostics is part of Error Indication procedure. Procedure Criticality O ENUMERATED (reject, ignore, notify) This Procedure Criticality is used for reporting the Criticality of the Triggering message (Procedure). RIC Request ID O 9.2.7 Information Element Criticality Diagnostics 0 .. <maxnoof Errors> >IE Criticality M ENUMERATED (reject, ignore, notify) The IE Criticality is used for reporting the criticality of the triggering IE. The value 'ignore' shall not be used. >IE ID M INTEGER (0..65535) The IE ID of the not understood or missing IE. >Type of Error M ENUMERATED (not understood, missing, …) Range bound Explanation maxnoofErrors Maximum no. of IE errors allowed to be reported with a single message. The value for maxnoofErrors is 256. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.2.3 Message Type | The Message Type IE uniquely identifies the message being sent. It is mandatory for all messages. IE/Group Name Presence Range IE type and reference Semantics description Message Type >Procedure Code M INTEGER (0..255) >Type of Message M CHOICE (Initiating Message, Successful Outcome, Unsuccessful Outcome, …) ETSI ETSI TS 104 039 V4.0.0 (2024-10) 61 |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.2.4 Global RIC ID | This IE is used to globally identify the Near-RT RIC. IE/Group Name Presence Range IE type and reference Semantics description PLMN Identity M ETSI TS 138 423 [20] clause 9.2.2.4 Near-RT RIC ID M BIT STRING (SIZE(20)) |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.2.5 Time to wait | This IE defines the minimum allowed waiting times. IE/Group Name Presence Range IE type and reference Semantics description Time to wait M ENUMERATED (1s, 2s, 5s, 10s, 20s, 60s) |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.2.6 Global E2 Node ID | This IE is used to globally identify an E2 node. IE/Group Name Presence Range IE type and reference Semantics description CHOICE M >gNB To be used when E2 Node supports gNB mode or both gNB and en-gNB modes. >>Global gNB ID M ETSI TS 138 423 [20] clause 9.2.2.1 >>Global en-gNB ID O ETSI TS 136 423 [25] clause 9.2.112 Required when E2 node also supports NR with en-gNB mode. >>gNB-CU-UP ID O ETSI TS 137 483 [21] clause 9.3.1.15 Required when E2 Node supports only gNB-CU-UP functionality. >>gNB-DU ID O ETSI TS 138 473 [22] clause 9.3.1.9 Required when E2 Node supports only gNB-DU functionality. >en-gNB To be used when E2 Node supports en-gNB mode only. >>Global en-gNB ID M ETSI TS 136 423 [25] clause 9.2.112 >>en-gNB-CU-UP ID O ETSI TS 137 483 [21] clause 9.3.1.15 Required when E2 Node supports only gNB-CU-UP functionality. >>en-gNB-DU ID O ETSI TS 138 473 [22] clause 9.3.1.9 Required when E2 Node supports only gNB-DU functionality. >ng-eNB To be used when E2 Node supports ng-eNB mode or both ng-eNB and eNB modes. >>Global ng-eNB ID M ETSI TS 138 423 [20] clause 9.2.2.2 >>Global eNB ID O ETSI TS 136 423 [25] clause 9.2.22 Required when E2 Node also supports E-UTRA with eNB mode. >>ng-eNB-DU ID O ETSI TS 137 473 [23] clause 9.3.1.9 Required when E2 node supports only ng-eNB DU functionality. >eNB To be used when E2 Node supports eNB mode only. >>Global eNB ID M ETSI TS 136 423 [25] clause 9.2.22 ETSI ETSI TS 104 039 V4.0.0 (2024-10) 62 |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.2.7 RIC Request ID | This information element indicates the RIC Request ID, and shall be unique for a given E2 Node. IE/Group Name Presence Range IE type and reference Semantics description RIC Requestor ID M INTEGER (0..65535) RIC Instance ID M INTEGER (0..65535) |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.2.8 RAN Function ID | This information element indicates the RAN Function ID, and shall be unique within a given E2 Node. IE/Group Name Presence Range IE type and reference Semantics description RAN Function ID M INTEGER (0..4095) Value 0 reserved for Near-RT RIC internal usage. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.2.9 RIC Event Trigger Definition | This information element indicates the RIC event trigger description used by the RIC Subscription procedure. IE/Group Name Presence Range IE type and reference Semantics description RIC Event Trigger Definition M OCTET STRING Defined in RAN Function specific E2 Service Model [3]. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.2.10 RIC Action ID | This information element indicates the Action ID number for a RIC Service Action, and shall be unique within the given RIC Request ID. IE/Group Name Presence Range IE type and reference Semantics description RIC Action ID M INTEGER (0..255) |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.2.11 RIC Action Type | This IE defines the type of RIC Service Action to be executed. IE/Group Name Presence Range IE type and reference Semantics description RIC Action Type M ENUMERATED (Insert, Report, Policy, …) |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.2.12 RIC Action Definition | This information element provides parameters to used when executed a Report, Insert or Policy RIC Service Actions. IE/Group Name Presence Range IE type and reference Semantics description RIC Action Definition M OCTET STRING Defined in RAN Function specific E2 Service Model [3]. ETSI ETSI TS 104 039 V4.0.0 (2024-10) 63 |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.2.13 RIC Subsequent Action | This IE defines the subsequent action to be taken after completing a particular RIC Service Action and shall be present when RIC Action Type set to Insert. IE/Group Name Presence Range IE type and reference Semantics description RIC Subsequent Action Type M ENUMERATED (Continue, Halt, …) RIC Time to Wait M ENUMERATED (1ms, 2ms, 5ms, 10ms, 20ms, 30ms, 40ms, 50ms, 100ms, 200ms, 500ms, 1s, 2s, 5s, 10s, 20s, 60s, …) |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.2.14 RIC Indication Sequence Number (SN) | This information element indicates the Indication Sequence Number (SN). IE/Group Name Presence Range IE type and reference Semantics description RIC Indication SN M INTEGER (0..65535) |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.2.15 RIC Indication Type | This IE defines the Indication Type. IE/Group Name Presence Range IE type and reference Semantics description RIC Indication Type M ENUMERATED (Insert, Report, …) |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.2.16 RIC Indication message | This information element carries the RIC indication message used for Insert and Report RIC Service Actions. IE/Group Name Presence Range IE type and reference Semantics description RIC Indication message M OCTET STRING Defined in RAN Function specific E2 Service Model [3]. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.2.17 RIC Indication header | This information element carries the RIC indication header used for Insert and Report RIC Service Actions. IE/Group Name Presence Range IE type and reference Semantics description RIC Indication header M OCTET STRING Defined in RAN Function specific E2 Service Model [3]. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.2.18 RIC Call Process ID | This information element carries the RIC Call Process ID used for the Insert and Control RIC Service Actions. The RIC Call Process ID shall be unique within a given RAN Function on a given E2 Node. IE/Group Name Presence Range IE type and reference Semantics description RIC Call Process ID M OCTET STRING Defined in RAN Function specific E2 Service Model [3]. ETSI ETSI TS 104 039 V4.0.0 (2024-10) 64 |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.2.19 RIC Control message | This information element carries the RIC Control message. IE/Group Name Presence Range IE type and reference Semantics description RIC Control Message M OCTET STRING Defined in RAN Function specific E2 Service Model [3]. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.2.20 RIC Control header | This information element carries the RIC Control Header. IE/Group Name Presence Range IE type and reference Semantics description RIC Control header M OCTET STRING Defined in RAN Function specific E2 Service Model [3]. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.2.21 RIC Control Ack Request | This IE defines whether and when the RIC CONTROL ACKNOWLEDGE message shall be sent by the E2 Node as described in the table below. IE/Group Name Presence Range IE type and reference Semantics description RIC Control Ack Request M ENUMERATED (NoAck, Ack, …) The meaning of the different values is described in the following table. RIC Service cause Meaning NoAck Optional RIC Control Acknowledgement is not required. Ack Optional RIC Control Acknowledgement is required. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.2.22 Void | |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.2.23 RAN Function Definition | This information element carries the RAN Function Definition. IE/Group Name Presence Range IE type and reference Semantics description RAN Function Definition M OCTET STRING Defined in RAN Function specific E2 Service Model [3]. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.2.24 RAN Function Revision | This information element carries the RAN Function Revision. IE/Group Name Presence Range IE type and reference Semantics description RAN Function Revision M INTEGER (0..4095) ETSI ETSI TS 104 039 V4.0.0 (2024-10) 65 |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.2.25 RIC Control Outcome | This information element carries the RIC Control Outcome. IE/Group Name Presence Range IE type and reference Semantics description RIC Control Outcome M OCTET STRING Defined in RAN Function specific E2 Service Model [3]. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.2.26 E2 Node Component Interface Type | This IE is used to identify an E2 node component type. IE/Group Name Presence Range IE type and reference Semantics description E2 node component interface type M ENUMERATED (ng, xn, e1, f1, w1, s1, x2, …) |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.2.27 E2 Node Component Configuration | This IE is used to carry the E2 Node component configuration update information of a specific E2 Node component. IE/Group Name Presence Range IE type and reference Semantics description SEQUENCE M >E2 Node Component Request Part M OCTET STRING Contents depend on component type and used to carry new or updated component configuration. See the table below. >E2 Node Component Response Part M OCTET STRING Contents depend on component type and used to carry new or updated component configuration. See the table below. NOTE: E2 node may generate the content of this IE using information derived from prior messages sent or received over the corresponding 3GPP Interfaces. For the E2 SETUP REQUEST message, the E2 node may derive the content of this IE from the prior messages pertaining to the Request part and the Response part of the Component Addition list in the following table and/or the Request part and the Response part of the Component Update list in the following table. In all cases the information is a data structure defined by the applicable 3GPP specification as specified in the following table. Component Addition list Component Update list E2 Node component message content Request part Response part Request part Response part gNB case >NG (AMF Name) NG SETUP REQUEST, ETSI TS 138 413 [19] clause 9.2.6.1 NG SETUP RESPONSE, ETSI TS 138 413 [19] clause 9.2.6.2 RAN CONFIGURATION UPDATE, ETSI TS 138 413 [19] clause 9.2.6.4 Or AMF CONFIGURATION UPDATE, ETSI TS 138 413 [19] clause 9.2.6.7 RAN CONFIGURATION UPDATE ACKNOWLEDGE, ETSI TS 138 413 [19] clause 9.2.6.5 Or AMF CONFIGURATION UPDATE ACKNOWLEDGE, 3GPP TS 138 413 [19] clause 9.2.6.8 ETSI ETSI TS 104 039 V4.0.0 (2024-10) 66 Component Addition list Component Update list E2 Node component message content Request part Response part Request part Response part >Xn (Neighbour Global NG-RAN Node ID) XN SETUP REQUEST, ETSI TS 138 423 [20] clause 9.1.3.1 XN SETUP RESPONSE, ETSI TS 138 423 [20] clause 9.1.3.2 NG-RAN NODE CONFIGURATION UPDATE, ETSI TS 138 423 [20] clause 9.1.3.4 NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE, ETSI TS 138 423 [20] clause 9.1.3.5 >E1 (gNB-CU-UP ID) GNB-CU-UP E1 SETUP REQUEST, ETSI TS 137 483 [21] clause 9.2.1.4 Or GNB-CU-CP E1 SETUP REQUEST, ETSI TS 137 483 [21] clause 9.2.1.7 GNB-CU-UP E1 SETUP RESPONSE, ETSI TS 137 483 [21] clause 9.2.1.5 Or GNB-CU-CP E1 SETUP RESPONSE, ETSI TS 137 483 [21] clause 9.2.1.8 GNB-CU-UP CONFIGRATION UPDATE, ETSI TS 137 483 [21] clause 9.2.1.10 Or GNB-CU-CP CONFIGURATION UPDATE, ETSI TS 137 483 [21] clause 9.2.1.13 GNB-CU-UP CONFIGRATION UPDATE ACKNOWLEDGE, ETSI TS 137 483 [21] clause 9.2.1.11 Or GNB-CU-CP CONFIGURATION UPDATE ACKNOWLEDGE, ETSI TS 137 483 [21] clause 9.2.1.14 >F1 (gNB-DU ID) F1 SETUP REQUEST, ETSI TS 138 473 [22] clause 9.2.1.4 F1 SETUP RESPONSE, ETSI TS 138 473 [22] clause 9.2.1.5 GNB-DU CONFIGRATION UPDATE, ETSI TS 138 473 [22] clause 9.2.1.7 Or GNB-CU CONFIGURATION UPDATE, 3GPP TS 138 473 [22] clause 9.2.1.10 GNB-DU CONFIGRATION UPDATE ACKNOWLEDGE, ETSI TS 138 473 [22] clause 9.2.1.8 Or GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE, 3GPP TS 138 473 [22] clause 9.2.1.11 >X2 (Neighbour Global eNB ID) EN-DC X2 SETUP REQUEST, ETSI TS 136 423 [25] clause 9.1.2.31 EN-DC X2 SETUP RESPONSE, ETSI TS 136 423 [25] clause 9.1.2.32 EN-DC CONFIGURATION UPDATE, ETSI TS 136 423 [25] clause 9.1.2.34 EN-DC CONFIGURATION UPDATE ACKNOWLEDGE, ETSI TS 136 423 [25] clause 9.1.2.35 eNB case >NG (AMF Name) NG SETUP REQUEST, ETSI TS 138 413 [19] clause 9.2.6.1 NG SETUP RESPONSE, ETSI TS 138 413 [19] clause 9.2.6.2 RAN CONFIGURATION UPDATE, ETSI TS 138 413 [19] clause 9.2.6.4 Or AMF CONFIGURATION UPDATE, 3GPP TS 138 413 [19] clause 9.2.6.7 RAN CONFIGURATION UPDATE ACKNOWLEDGE, ETSI TS 138 413 [19] clause 9.2.6.5 Or AMF CONFIGURATION UPDATE ACKNOWLEDGE, 3GPP TS 138 413 [19] clause 9.2.6.8 >Xn (Neighbour Global NG-RAN Node ID) XN SETUP REQUEST, ETSI TS 138 423 [20] clause 9.1.3.1 XN SETUP RESPONSE, ETSI TS 138 423 [20] clause 9.1.3.2 NG-RAN NODE CONFIGURATION UPDATE, ETSI TS 138 423 [20] clause 9.1.3.4 NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE, ETSI TS 138 423 [20] clause 9.1.3.5 ETSI ETSI TS 104 039 V4.0.0 (2024-10) 67 Component Addition list Component Update list E2 Node component message content Request part Response part Request part Response part >W1 (ng-eNB-DU ID) W1 SETUP REQUEST, ETSI TS 137 473 [23] clause 9.2.1.4 W1 SETUP RESPONSE, ETSI TS 137 473 [23] clause 9.2.1.5 NG-ENB-DU CONFIGURATION UPDATE, ETSI TS 137 473 [23] clause 9.2.1.7 Or NG-ENB-CU CONFIGURATION UPDATE, ETSI TS 137 473 [23] clause 9.2.1.10 NG-ENB-DU CONFIGURATION UPDATE ACKNOWLEDGE, ETSI TS 137 473 [23] clause 9.2.1.8 Or NG-ENB-CU CONFIGURATION UPDATE ACKNOWLEDGE, ETSI TS 137 473 [23] clause 9.2.1.11 >S1 (MME Name) S1 SETUP REQUEST, ETSI TS 136 413 [24] clause 9.1.8.4 S1 SETUP RESPONSE, ETSI TS 136 413 [24] clause 9.1.8.5 ENB CONFIGURATION UPDATE, ETSI TS 136 413 [24] clause 9.1.8.7 Or MME CONFIGURATION UPDATE, ETSI TS 136 413 [24] clause 9.1.8.10 ENB CONFIGRATION UPDATE ACKNOWLEDGE, ETSI TS 136 413 [24] clause 9.1.8.8 Or MME CONFIGURATION UPDATE ACKNOWLEDGE, ETSI TS 136 413 [24] clause 9.1.8.11 >X2 (when neighbour is eNB) (Neighbour Global eNB ID) X2 SETUP REQUEST, ETSI TS 136 423 [25] clause 9.1.2.3 X2 SETUP RESPONSE, ETSI TS 136 423 [25] clause 9.1.2.4 ENB CONFIGURATION UPDATE, ETSI TS 136 423 [25] clause 9.1.2.8 ENB CONFIGRATION UPDATE ACKNOWLEDGE, ETSI TS 136 423 [25] clause 9.1.2.9 >X2 (when neighbour is en-gNB) (Neighbour Global eNB ID) EN-DC X2 SETUP REQUEST, ETSI TS 136 423 [25] clause 9.1.2.31 EN-DC X2 SETUP RESPONSE, ETSI TS 136 423 [25] clause 9.1.2.32 EN-DC CONFIGURATION UPDATE, ETSI TS 136 423 [25] clause 9.1.2.34 EN-DC CONFIGURATION UPDATE ACKNOWLEDGE, ETSI TS 136 423 [25] clause 9.1.2.35 |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.2.28 E2 Node Component Configuration Acknowledge | This IE is used to carry the E2 Node component configuration update acknowledge of a specific E2 Node component. IE/Group Name Presence Range IE type and reference Semantics description Outcome M ENUMERATED (success, failure, …) Cause O 9.2.1 Cause for failure. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.2.29 Transport Layer Information | This information element provides Near-RT RIC address and optionally port number to be used by an E2 Node. IE/Group Name Presence Range IE type and reference Semantics description Transport Layer Address M BIT STRING (SIZE(1..160, …)) To be passed to transport layer without interpretation. Transport Layer Port O BIT STRING (SIZE(16)) To be passed to transport layer without interpretation. ETSI ETSI TS 104 039 V4.0.0 (2024-10) 68 |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.2.30 TNL Association Usage | This information element provides TNL association usage. IE/Group Name Presence Range IE type and reference Semantics description TNL Association Usage M ENUMERATED (ric service, support functions, both, …) Indicates whether E2 connection to be used for RIC services only, or E2 support functions only, or both. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.2.31 RAN Function OID | This information element carries the RAN Function OID and shall uniquely refer to a specific E2 Service Model (E2SM). IE/Group Name Presence Range IE type and reference Semantics description RAN Function Service Model OID M PrintableString(SIZE(1..1000, …)) Object Identifier of the specific RAN Function definition. Formatted as per OID. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.2.32 E2 Node Component ID | This IE is used to locally identify an E2 node component. IE/Group Name Presence Range IE type and reference Semantics description CHOICE E2 node component interface type M >NG >>AMF name M ETSI TS 138 413 [19] clause 9.3.3.21 Serving AMF. >Xn >>Global NG-RAN Node ID M ETSI TS 138 423 [20] clause 9.2.2.3 Neighbour gNB or ng-eNB. >E1 >>gNB-CU-UP ID M ETSI TS 137 483 [21] clause 9.3.1.15 >F1 >>gNB-DU ID M ETSI TS 138 473 [22] clause 9.3.1.9 >W1 >>ng-eNB-DU ID M ETSI TS 137 473 [23] clause 9.3.1.9 >S1 >>MME name M ETSI TS 136 413 [24], clause 9.1.8.5 Serving MME. >X2 >>Global eNB ID O ETSI TS 136 423 [25] clause 9.2.22 Neighbour eNB. >>Global en-gNB ID O ETSI TS 136 423 [25] clause 9.2.112 Neighbour en-gNB. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.2.33 Transaction ID | The Transaction ID IE uniquely identifies a procedure among all ongoing parallel procedures of the same type initiated by the same protocol peer. Messages belonging to the same procedure shall use the same Transaction ID. The Transaction ID is determined by the initiating peer of a procedure. IE/Group Name Presence Range IE type and reference Semantics description Transaction ID M INTEGER (0..255, …) ETSI ETSI TS 104 039 V4.0.0 (2024-10) 69 |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.2.34 RIC Subscription Time | The RIC Subscription Time IE is used to set the start and end time of a RIC Subscription. IE/Group Name Presence Range IE type and reference Semantics description RIC Subscription time M OCTET STRING (SIZE(8)) Encoded using the 64-bit timestamp format as defined in clause 6 of IETF RFC 5905 [26]. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.2.35 RIC Action Execution Order | This IE is used to modify the default RIC service action execution order. IE/Group Name Presence Range IE type and reference Semantics description RIC Action Execution Order M INTEGER (0..255, …) 0 used to indicate "Any-order" 1..255 Used to enforce a specific execution order. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.2.36 RIC Query Header | This information element carries the RIC Query Header. IE/Group Name Presence Range IE type and reference Semantics description RIC Query Header M OCTET STRING Defined in RAN Function specific E2 Service Model [3]. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.2.37 RIC Query Definition | This information element carries the RIC Query Definition. IE/Group Name Presence Range IE type and reference Semantics description RIC Query Definition M OCTET STRING Defined in RAN Function specific E2 Service Model [3]. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.2.38 RIC Query Outcome | This information element carries the RIC Query Outcome. IE/Group Name Presence Range IE type and reference Semantics description RIC Query Outcome M OCTET STRING Defined in RAN Function specific E2 Service Model [3]. 9.3 Message and Information Element Abstract Syntax (with ASN.1) |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.3.1 General | E2AP ASN.1 definition conforms to Recommendation ITU-T X.691 [15], Recommendation ITU-T X.680 [16] and Recommendation ITU-T X.681 [17]. ETSI ETSI TS 104 039 V4.0.0 (2024-10) 70 The ASN.1 definition specifies the structure and content of E2AP messages. E2AP messages can contain any IEs specified in the object set definitions for that message without the order or number of occurrences being restricted by ASN.1. However, for this version of the standard, a sending entity shall construct an E2AP message according to the PDU definitions module and with the following additional rules: - IEs shall be ordered (in an IE container) in the order they appear in object set definitions. - Object set definitions specify how many times IEs may appear. An IE shall appear exactly once if the presence field in an object has value "mandatory". An IE may appear at most once if the presence field in an object has value "optional" or "conditional". If in a tabular format there is multiplicity specified for an IE (i.e. an IE list) then in the corresponding ASN.1 definition the list definition is separated into two parts. The first part defines an IE container list where the list elements reside. The second part defines list elements. The IE container list appears as an IE of its own. For this version of the standard an IE container list may contain only one kind of list elements. NOTE: In the above "IE" means an IE in the object set with an explicit ID. If one IE needs to appear more than once in one object set, then the different occurrences will have different IE IDs. If an E2AP message that is not constructed as defined above is received, this shall be considered as Abstract Syntax Error, and the message shall be handled as defined for Abstract Syntax Error in clause 10.3.6. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.3.2 Usage of private message mechanism for non-standard use | The private message mechanism for non-standard use is not supported with E2AP. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.3.3 Elementary Procedure Definitions | -- ASN1START -- ************************************************************** -- -- Elementary Procedure definitions -- Derived from 3GPP 38.413 NGAP -- ************************************************************** E2AP-PDU-Descriptions { iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) oran(53148) e2(1) version2 (2) e2ap(1) e2ap-PDU-Descriptions (0) } DEFINITIONS AUTOMATIC TAGS ::= BEGIN -- ************************************************************** -- -- IE parameter types from other modules. -- -- ************************************************************** IMPORTS Criticality, ProcedureCode FROM E2AP-CommonDataTypes E2connectionUpdate, E2connectionUpdateAcknowledge, E2connectionUpdateFailure, E2nodeConfigurationUpdate, E2nodeConfigurationUpdateAcknowledge, E2nodeConfigurationUpdateFailure, E2RemovalRequest, E2RemovalResponse, E2RemovalFailure, E2setupFailure, E2setupRequest, E2setupResponse, ErrorIndication, ResetRequest, ResetResponse, RICcontrolAcknowledge, ETSI ETSI TS 104 039 V4.0.0 (2024-10) 71 RICcontrolFailure, RICcontrolRequest, RICindication, RICserviceQuery, RICserviceUpdate, RICserviceUpdateAcknowledge, RICserviceUpdateFailure, RICsubscriptionFailure, RICsubscriptionRequest, RICsubscriptionResponse, RICsubscriptionDeleteFailure, RICsubscriptionDeleteRequest, RICsubscriptionDeleteResponse, RICsubscriptionDeleteRequired, RICsubscriptionModificationRequest, RICsubscriptionModificationResponse, RICsubscriptionModificationFailure, RICsubscriptionModificationRequired, RICsubscriptionModificationConfirm, RICsubscriptionModificationRefuse, RICqueryRequest, RICqueryResponse, RICqueryFailure FROM E2AP-PDU-Contents id-E2connectionUpdate, id-E2nodeConfigurationUpdate, id-E2removal, id-E2setup, id-ErrorIndication, id-Reset, id-RICcontrol, id-RICindication, id-RICserviceQuery, id-RICserviceUpdate, id-RICsubscription, id-RICsubscriptionDelete, id-RICsubscriptionDeleteRequired, id-RICsubscriptionModification, id-RICsubscriptionModificationRequired, id-RICquery FROM E2AP-Constants; -- ************************************************************** -- -- Interface Elementary Procedure Class -- -- ************************************************************** E2AP-ELEMENTARY-PROCEDURE ::= CLASS { &InitiatingMessage , &SuccessfulOutcome OPTIONAL , &UnsuccessfulOutcome OPTIONAL , &procedureCode ProcedureCode UNIQUE , &criticality Criticality DEFAULT ignore } WITH SYNTAX { INITIATING MESSAGE &InitiatingMessage [SUCCESSFUL OUTCOME &SuccessfulOutcome] [UNSUCCESSFUL OUTCOME &UnsuccessfulOutcome] PROCEDURE CODE &procedureCode [CRITICALITY &criticality] } -- ************************************************************** -- -- Interface PDU Definition -- -- ************************************************************** E2AP-PDU ::= CHOICE { initiatingMessage InitiatingMessage, successfulOutcome SuccessfulOutcome, unsuccessfulOutcome UnsuccessfulOutcome, … } ETSI ETSI TS 104 039 V4.0.0 (2024-10) 72 InitiatingMessage ::= SEQUENCE { procedureCode E2AP-ELEMENTARY-PROCEDURE.&procedureCode ({E2AP-ELEMENTARY-PROCEDURES}), criticality E2AP-ELEMENTARY-PROCEDURE.&criticality ({E2AP-ELEMENTARY- PROCEDURES}{@procedureCode}), value E2AP-ELEMENTARY-PROCEDURE.&InitiatingMessage ({E2AP-ELEMENTARY- PROCEDURES}{@procedureCode}) } SuccessfulOutcome ::= SEQUENCE { procedureCode E2AP-ELEMENTARY-PROCEDURE.&procedureCode ({E2AP-ELEMENTARY-PROCEDURES}), criticality E2AP-ELEMENTARY-PROCEDURE.&criticality ({E2AP-ELEMENTARY- PROCEDURES}{@procedureCode}), value E2AP-ELEMENTARY-PROCEDURE.&SuccessfulOutcome ({E2AP-ELEMENTARY- PROCEDURES}{@procedureCode}) } UnsuccessfulOutcome ::= SEQUENCE { procedureCode E2AP-ELEMENTARY-PROCEDURE.&procedureCode ({E2AP-ELEMENTARY-PROCEDURES}), criticality E2AP-ELEMENTARY-PROCEDURE.&criticality ({E2AP-ELEMENTARY- PROCEDURES}{@procedureCode}), value E2AP-ELEMENTARY-PROCEDURE.&UnsuccessfulOutcome ({E2AP-ELEMENTARY- PROCEDURES}{@procedureCode}) } -- ************************************************************** -- -- Interface Elementary Procedure List -- -- ************************************************************** E2AP-ELEMENTARY-PROCEDURES E2AP-ELEMENTARY-PROCEDURE ::= { E2AP-ELEMENTARY-PROCEDURES-CLASS-1 | E2AP-ELEMENTARY-PROCEDURES-CLASS-2, … } E2AP-ELEMENTARY-PROCEDURES-CLASS-1 E2AP-ELEMENTARY-PROCEDURE ::= { ricSubscription | ricSubscriptionDelete | ricSubscriptionModification | ricSubscriptionModificationRequired | ricQuery | ricServiceUpdate | ricControl | e2setup | e2nodeConfigurationUpdate | e2connectionUpdate | reset | e2removal, … } E2AP-ELEMENTARY-PROCEDURES-CLASS-2 E2AP-ELEMENTARY-PROCEDURE ::= { ricIndication | ricServiceQuery | errorIndication | ricSubscriptionDeleteRequired, … } -- ************************************************************** -- -- Interface Elementary Procedures -- -- ************************************************************** -- New for v01.01 e2connectionUpdate E2AP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE E2connectionUpdate SUCCESSFUL OUTCOME E2connectionUpdateAcknowledge UNSUCCESSFUL OUTCOME E2connectionUpdateFailure PROCEDURE CODE id-E2connectionUpdate CRITICALITY reject } e2nodeConfigurationUpdate E2AP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE E2nodeConfigurationUpdate SUCCESSFUL OUTCOME E2nodeConfigurationUpdateAcknowledge ETSI ETSI TS 104 039 V4.0.0 (2024-10) 73 UNSUCCESSFUL OUTCOME E2nodeConfigurationUpdateFailure PROCEDURE CODE id-E2nodeConfigurationUpdate CRITICALITY reject } -- New for v02.01 e2removal E2AP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE E2RemovalRequest SUCCESSFUL OUTCOME E2RemovalResponse UNSUCCESSFUL OUTCOME E2RemovalFailure PROCEDURE CODE id-E2removal CRITICALITY reject } e2setup E2AP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE E2setupRequest SUCCESSFUL OUTCOME E2setupResponse UNSUCCESSFUL OUTCOME E2setupFailure PROCEDURE CODE id-E2setup CRITICALITY reject } errorIndication E2AP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE ErrorIndication PROCEDURE CODE id-ErrorIndication CRITICALITY ignore } reset E2AP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE ResetRequest SUCCESSFUL OUTCOME ResetResponse PROCEDURE CODE id-Reset CRITICALITY reject } ricControl E2AP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE RICcontrolRequest SUCCESSFUL OUTCOME RICcontrolAcknowledge UNSUCCESSFUL OUTCOME RICcontrolFailure PROCEDURE CODE id-RICcontrol CRITICALITY reject } ricIndication E2AP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE RICindication PROCEDURE CODE id-RICindication CRITICALITY ignore } ricServiceQuery E2AP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE RICserviceQuery PROCEDURE CODE id-RICserviceQuery CRITICALITY ignore } ricServiceUpdate E2AP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE RICserviceUpdate SUCCESSFUL OUTCOME RICserviceUpdateAcknowledge UNSUCCESSFUL OUTCOME RICserviceUpdateFailure PROCEDURE CODE id-RICserviceUpdate CRITICALITY reject } ricSubscription E2AP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE RICsubscriptionRequest SUCCESSFUL OUTCOME RICsubscriptionResponse UNSUCCESSFUL OUTCOME RICsubscriptionFailure PROCEDURE CODE id-RICsubscription CRITICALITY reject } ricSubscriptionDelete E2AP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE RICsubscriptionDeleteRequest SUCCESSFUL OUTCOME RICsubscriptionDeleteResponse UNSUCCESSFUL OUTCOME RICsubscriptionDeleteFailure PROCEDURE CODE id-RICsubscriptionDelete CRITICALITY reject } ETSI ETSI TS 104 039 V4.0.0 (2024-10) 74 ricSubscriptionDeleteRequired E2AP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE RICsubscriptionDeleteRequired PROCEDURE CODE id-RICsubscriptionDeleteRequired CRITICALITY ignore } ricSubscriptionModification E2AP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE RICsubscriptionModificationRequest SUCCESSFUL OUTCOME RICsubscriptionModificationResponse UNSUCCESSFUL OUTCOME RICsubscriptionModificationFailure PROCEDURE CODE id-RICsubscriptionModification CRITICALITY reject } ricSubscriptionModificationRequired E2AP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE RICsubscriptionModificationRequired SUCCESSFUL OUTCOME RICsubscriptionModificationConfirm UNSUCCESSFUL OUTCOME RICsubscriptionModificationRefuse PROCEDURE CODE id-RICsubscriptionModificationRequired CRITICALITY reject } ricQuery E2AP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE RICqueryRequest SUCCESSFUL OUTCOME RICqueryResponse UNSUCCESSFUL OUTCOME RICqueryFailure PROCEDURE CODE id-RICquery CRITICALITY reject } END -- ASN1STOP |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.3.4 PDU definitions | -- ASN1START -- ************************************************************** -- -- PDU definitions for E2AP -- Derived from 3GPP 38.413 (NGAP) -- -- ************************************************************** E2AP-PDU-Contents { iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) oran(53148) e2(1) version2 (2) e2ap(1) e2ap-PDU-Contents (1) } DEFINITIONS AUTOMATIC TAGS ::= BEGIN -- ************************************************************** -- -- IE parameter types from other modules. -- -- ************************************************************** IMPORTS Cause, CriticalityDiagnostics, E2nodeComponentConfiguration, E2nodeComponentConfigurationAck, E2nodeComponentID, E2nodeComponentInterfaceType, GlobalE2node-ID, GlobalRIC-ID, RANfunctionDefinition, RANfunctionID, RANfunctionOID, RANfunctionRevision, RICactionDefinition, RICactionExecutionOrder, RICactionID, RICactionType, RICcallProcessID, RICcontrolAckRequest, ETSI ETSI TS 104 039 V4.0.0 (2024-10) 75 RICcontrolHeader, RICcontrolMessage, RICcontrolOutcome, RICeventTriggerDefinition, RICindicationHeader, RICindicationMessage, RICindicationSN, RICindicationType, RICrequestID, RICsubsequentAction, RICsubscriptionTime, RICqueryHeader, RICqueryDefinition, RICqueryOutcome, RICtimeToWait, TimeToWait, TNLinformation, TNLusage, TransactionID FROM E2AP-IEs ProtocolIE-Container{}, ProtocolIE-ContainerList{}, ProtocolIE-SingleContainer{}, E2AP-PROTOCOL-IES, E2AP-PROTOCOL-IES-PAIR FROM E2AP-Containers id-Cause, id-CriticalityDiagnostics, id-E2connectionSetup, id-E2connectionSetupFailed, id-E2connectionSetupFailed-Item, id-E2connectionFailed-Item, id-E2connectionUpdate-Item, id-E2connectionUpdateAdd, id-E2connectionUpdateModify, id-E2connectionUpdateRemove, id-E2connectionUpdateRemove-Item, id-E2nodeComponentConfigAddition, id-E2nodeComponentConfigAddition-Item, id-E2nodeComponentConfigAdditionAck, id-E2nodeComponentConfigAdditionAck-Item, id-E2nodeComponentConfigRemoval, id-E2nodeComponentConfigRemoval-Item, id-E2nodeComponentConfigRemovalAck, id-E2nodeComponentConfigRemovalAck-Item, id-E2nodeComponentConfigUpdate, id-E2nodeComponentConfigUpdate-Item, id-E2nodeComponentConfigUpdateAck, id-E2nodeComponentConfigUpdateAck-Item, id-E2nodeTNLassociationRemoval, id-E2nodeTNLassociationRemoval-Item, id-GlobalE2node-ID, id-GlobalRIC-ID, id-RANfunctionID, id-RANfunctionID-Item, id-RANfunctionIEcause-Item, id-RANfunction-Item, id-RANfunctionsAccepted, id-RANfunctionsAdded, id-RANfunctionsDeleted, id-RANfunctionsModified, id-RANfunctionsRejected, id-RICaction-Admitted-Item, id-RICactionID, id-RICaction-NotAdmitted-Item, id-RICactions-Admitted, id-RICactions-NotAdmitted, id-RICaction-ToBeSetup-Item, id-RICactionsToBeRemovedForModification-List, id-RICaction-ToBeRemovedForModification-Item, id-RICactionsToBeModifiedForModification-List, id-RICaction-ToBeModifiedForModification-Item, id-RICactionsToBeAddedForModification-List, id-RICaction-ToBeAddedForModification-Item, id-RICactionsRemovedForModification-List, id-RICaction-RemovedForModification-Item, ETSI ETSI TS 104 039 V4.0.0 (2024-10) 76 id-RICactionsFailedToBeRemovedForModification-List, id-RICaction-FailedToBeRemovedForModification-Item, id-RICactionsModifiedForModification-List, id-RICaction-ModifiedForModification-Item, id-RICactionsFailedToBeModifiedForModification-List, id-RICaction-FailedToBeModifiedForModification-Item, id-RICactionsAddedForModification-List, id-RICaction-AddedForModification-Item, id-RICactionsFailedToBeAddedForModification-List, id-RICaction-FailedToBeAddedForModification-Item, id-RICactionsRequiredToBeModified-List, id-RICaction-RequiredToBeModified-Item, id-RICactionsRequiredToBeRemoved-List, id-RICaction-RequiredToBeRemoved-Item, id-RICactionsConfirmedForModification-List, id-RICaction-ConfirmedForModification-Item, id-RICactionsRefusedToBeModified-List, id-RICaction-RefusedToBeModified-Item, id-RICactionsConfirmedForRemoval-List, id-RICaction-ConfirmedForRemoval-Item, id-RICactionsRefusedToBeRemoved-List, id-RICaction-RefusedToBeRemoved-Item, id-RICcallProcessID, id-RICcontrolAckRequest, id-RICcontrolHeader, id-RICcontrolMessage, id-RICcontrolOutcome, id-RICeventTriggerDefinitionToBeModified, id-RICindicationHeader, id-RICindicationMessage, id-RICindicationSN, id-RICindicationType, id-RICrequestID, id-RICserviceQuery, id-RICsubscriptionDetails, id-RICsubscriptionToBeRemoved, id-RICsubscription-withCause-Item, id-RICsubscriptionStartTime, id-RICsubscriptionEndTime, id-RICqueryHeader, id-RICqueryDefinition, id-RICqueryOutcome, id-TimeToWait, id-TNLinformation, id-TransactionID, maxofE2nodeComponents, maxofRANfunctionID, maxofRICactionID, maxofRICrequestID, maxofTNLA FROM E2AP-Constants; -- ************************************************************** -- -- MESSAGES FOR RIC FUNCTIONAL PROCEDURES -- -- ************************************************************** -- ************************************************************** -- -- RIC Subscription Elementary Procedure -- -- ************************************************************** -- ************************************************************** -- -- RIC SUBSCRIPTION REQUEST -- -- ************************************************************** RICsubscriptionRequest ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RICsubscriptionRequest-IEs}}, … } RICsubscriptionRequest-IEs E2AP-PROTOCOL-IES ::= { { ID id-RICrequestID CRITICALITY reject TYPE RICrequestID PRESENCE mandatory}| ETSI ETSI TS 104 039 V4.0.0 (2024-10) 77 { ID id-RANfunctionID CRITICALITY reject TYPE RANfunctionID PRESENCE mandatory}| { ID id-RICsubscriptionDetails CRITICALITY reject TYPE RICsubscriptionDetails PRESENCE mandatory}, …, { ID id-RICsubscriptionStartTime CRITICALITY reject TYPE RICsubscriptionTime PRESENCE optional}| { ID id-RICsubscriptionEndTime CRITICALITY reject TYPE RICsubscriptionTime PRESENCE optional} } RICsubscriptionDetails ::= SEQUENCE { ricEventTriggerDefinition RICeventTriggerDefinition, ricAction-ToBeSetup-List RICactions-ToBeSetup-List, … } RICactions-ToBeSetup-List ::= SEQUENCE (SIZE(1..maxofRICactionID)) OF ProtocolIE-SingleContainer { {RICaction-ToBeSetup-ItemIEs} } RICaction-ToBeSetup-ItemIEs E2AP-PROTOCOL-IES ::= { { ID id-RICaction-ToBeSetup-Item CRITICALITY ignore TYPE RICaction-ToBeSetup-Item PRESENCE mandatory }, … } RICaction-ToBeSetup-Item ::= SEQUENCE { ricActionID RICactionID, ricActionType RICactionType, ricActionDefinition RICactionDefinition OPTIONAL, ricSubsequentAction RICsubsequentAction OPTIONAL, …, ricActionExecutionOrder RICactionExecutionOrder OPTIONAL -- New in E2APv03.00 } -- ************************************************************** -- -- RIC SUBSCRIPTION RESPONSE -- -- ************************************************************** RICsubscriptionResponse ::= SEQUENCE { protocolIEs ProtocolIE-Container{{RICsubscriptionResponse-IEs}}, … } RICsubscriptionResponse-IEs E2AP-PROTOCOL-IES ::= { { ID id-RICrequestID CRITICALITY reject TYPE RICrequestID PRESENCE mandatory } | { ID id-RANfunctionID CRITICALITY reject TYPE RANfunctionID PRESENCE mandatory } | { ID id-RICactions-Admitted CRITICALITY reject TYPE RICaction-Admitted-List PRESENCE mandatory } | { ID id-RICactions-NotAdmitted CRITICALITY reject TYPE RICaction-NotAdmitted-List PRESENCE optional }, … } RICaction-Admitted-List ::= SEQUENCE (SIZE(1..maxofRICactionID)) OF ProtocolIE- SingleContainer{{RICaction-Admitted-ItemIEs}} RICaction-Admitted-ItemIEs E2AP-PROTOCOL-IES ::= { { ID id-RICaction-Admitted-Item CRITICALITY ignore TYPE RICaction-Admitted-Item PRESENCE mandatory }, … } RICaction-Admitted-Item ::= SEQUENCE { ricActionID RICactionID, … } RICaction-NotAdmitted-List ::= SEQUENCE (SIZE(0..maxofRICactionID)) OF ProtocolIE-SingleContainer { {RICaction-NotAdmitted-ItemIEs} } ETSI ETSI TS 104 039 V4.0.0 (2024-10) 78 RICaction-NotAdmitted-ItemIEs E2AP-PROTOCOL-IES ::= { { ID id-RICaction-NotAdmitted-Item CRITICALITY ignore TYPE RICaction-NotAdmitted-Item PRESENCE mandatory }, … } RICaction-NotAdmitted-Item ::= SEQUENCE { ricActionID RICactionID, cause Cause, … } -- ************************************************************** -- -- RIC SUBSCRIPTION FAILURE -- -- ************************************************************** RICsubscriptionFailure ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RICsubscriptionFailure-IEs}}, … } RICsubscriptionFailure-IEs E2AP-PROTOCOL-IES ::= { { ID id-RICrequestID CRITICALITY reject TYPE RICrequestID PRESENCE mandatory }| { ID id-RANfunctionID CRITICALITY reject TYPE RANfunctionID PRESENCE mandatory }| { ID id-Cause CRITICALITY reject TYPE Cause PRESENCE mandatory }| { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, … } -- ************************************************************** -- -- RIC Subscription Delete Elementary Procedure -- -- ************************************************************** -- ************************************************************** -- -- RIC SUBSCRIPTION DELETE REQUEST -- -- ************************************************************** RICsubscriptionDeleteRequest ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RICsubscriptionDeleteRequest-IEs}}, … } RICsubscriptionDeleteRequest-IEs E2AP-PROTOCOL-IES ::= { { ID id-RICrequestID CRITICALITY reject TYPE RICrequestID PRESENCE mandatory }| { ID id-RANfunctionID CRITICALITY reject TYPE RANfunctionID PRESENCE mandatory }, … } -- ************************************************************** -- -- RIC SUBSCRIPTION DELETE RESPONSE -- -- ************************************************************** RICsubscriptionDeleteResponse ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RICsubscriptionDeleteResponse-IEs}}, … } RICsubscriptionDeleteResponse-IEs E2AP-PROTOCOL-IES ::= { { ID id-RICrequestID CRITICALITY reject TYPE RICrequestID PRESENCE mandatory }| { ID id-RANfunctionID CRITICALITY reject TYPE RANfunctionID PRESENCE mandatory }, … } -- ************************************************************** -- -- RIC SUBSCRIPTION DELETE FAILURE -- -- ************************************************************** ETSI ETSI TS 104 039 V4.0.0 (2024-10) 79 RICsubscriptionDeleteFailure ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RICsubscriptionDeleteFailure-IEs}}, … } RICsubscriptionDeleteFailure-IEs E2AP-PROTOCOL-IES ::= { { ID id-RICrequestID CRITICALITY reject TYPE RICrequestID PRESENCE mandatory }| { ID id-RANfunctionID CRITICALITY reject TYPE RANfunctionID PRESENCE mandatory }| { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }| { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, … } -- ************************************************************** -- -- RIC Subscription Delete Required Elementary Procedure -- -- ************************************************************** -- ************************************************************** -- -- RIC SUBSCRIPTION DELETE REQUIRED -- -- ************************************************************** RICsubscriptionDeleteRequired ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RICsubscriptionDeleteRequired-IEs}}, … } RICsubscriptionDeleteRequired-IEs E2AP-PROTOCOL-IES ::= { { ID id-RICsubscriptionToBeRemoved CRITICALITY ignore TYPE RICsubscription-List-withCause PRESENCE mandatory }, … } RICsubscription-List-withCause ::= SEQUENCE (SIZE(1..maxofRICrequestID)) OF ProtocolIE- SingleContainer { {RICsubscription-withCause-ItemIEs} } RICsubscription-withCause-ItemIEs E2AP-PROTOCOL-IES ::= { { ID id-RICsubscription-withCause-Item CRITICALITY ignore TYPE RICsubscription-withCause-Item PRESENCE mandatory }, … } RICsubscription-withCause-Item ::= SEQUENCE { ricRequestID RICrequestID, ranFunctionID RANfunctionID, cause Cause, … } -- ************************************************************** -- -- RIC Subscription Modification Elementary Procedure -- -- ************************************************************** -- ************************************************************** -- -- RIC SUBSCRIPTION MODIFICATION REQUEST -- -- ************************************************************** RICsubscriptionModificationRequest ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RICsubscriptionModificationRequest-IEs}}, … } RICsubscriptionModificationRequest-IEs E2AP-PROTOCOL-IES ::= { { ID id-RICrequestID CRITICALITY reject TYPE RICrequestID PRESENCE mandatory}| { ID id-RANfunctionID CRITICALITY reject TYPE RANfunctionID PRESENCE mandatory}| { ID id-RICeventTriggerDefinitionToBeModified CRITICALITY ignore TYPE RICeventTriggerDefinition PRESENCE optional}| ETSI ETSI TS 104 039 V4.0.0 (2024-10) 80 { ID id-RICactionsToBeRemovedForModification-List CRITICALITY ignore TYPE RICactions- ToBeRemovedForModification-List PRESENCE optional}| { ID id-RICactionsToBeModifiedForModification-List CRITICALITY ignore TYPE RICactions- ToBeModifiedForModification-List PRESENCE optional}| { ID id-RICactionsToBeAddedForModification-List CRITICALITY ignore TYPE RICactions- ToBeAddedForModification-List PRESENCE optional}, … } RICactions-ToBeRemovedForModification-List ::= SEQUENCE (SIZE(0..maxofRICactionID)) OF ProtocolIE- SingleContainer {{RICaction-ToBeRemovedForModification-ItemIEs} } RICaction-ToBeRemovedForModification-ItemIEs E2AP-PROTOCOL-IES ::= { { ID id-RICaction-ToBeRemovedForModification-Item CRITICALITY ignore TYPE RICaction- ToBeRemovedForModification-Item PRESENCE mandatory }, … } RICaction-ToBeRemovedForModification-Item ::= SEQUENCE { ricActionID RICactionID, … } RICactions-ToBeModifiedForModification-List ::= SEQUENCE (SIZE(0..maxofRICactionID)) OF ProtocolIE- SingleContainer {{RICaction-ToBeModifiedForModification-ItemIEs} } RICaction-ToBeModifiedForModification-ItemIEs E2AP-PROTOCOL-IES ::= { { ID id-RICaction-ToBeModifiedForModification-Item CRITICALITY ignore TYPE RICaction- ToBeModifiedForModification-Item PRESENCE mandatory }, … } RICaction-ToBeModifiedForModification-Item ::= SEQUENCE { ricActionID RICactionID, ricActionDefinition RICactionDefinition OPTIONAL, ricActionExecutionOrder RICactionExecutionOrder OPTIONAL, ricSubsequentAction RICsubsequentAction OPTIONAL, … } RICactions-ToBeAddedForModification-List ::= SEQUENCE (SIZE(0..maxofRICactionID)) OF ProtocolIE- SingleContainer {{RICaction-ToBeAddedForModification-ItemIEs} } RICaction-ToBeAddedForModification-ItemIEs E2AP-PROTOCOL-IES ::= { { ID id-RICaction-ToBeAddedForModification-Item CRITICALITY ignore TYPE RICaction- ToBeAddedForModification-Item PRESENCE mandatory }, … } RICaction-ToBeAddedForModification-Item ::= SEQUENCE { ricActionID RICactionID, ricActionType RICactionType, ricActionDefinition RICactionDefinition, ricActionExecutionOrder RICactionExecutionOrder, ricSubsequentAction RICsubsequentAction OPTIONAL, … } -- ************************************************************** -- -- RIC SUBSCRIPTION MODIFICATION RESPONSE -- -- ************************************************************** RICsubscriptionModificationResponse ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RICsubscriptionModificationResponse-IEs}}, … } RICsubscriptionModificationResponse-IEs E2AP-PROTOCOL-IES ::= { { ID id-RICrequestID CRITICALITY reject TYPE RICrequestID PRESENCE mandatory}| { ID id-RANfunctionID CRITICALITY reject TYPE RANfunctionID PRESENCE mandatory}| { ID id-RICactionsRemovedForModification-List CRITICALITY ignore TYPE RICactions- RemovedForModification-List PRESENCE optional}| { ID id-RICactionsFailedToBeRemovedForModification-List CRITICALITY ignore TYPE RICactions- FailedToBeRemovedForModification-List PRESENCE optional}| ETSI ETSI TS 104 039 V4.0.0 (2024-10) 81 { ID id-RICactionsModifiedForModification-List CRITICALITY ignore TYPE RICactions- ModifiedForModification-List PRESENCE optional}| { ID id-RICactionsFailedToBeModifiedForModification-List CRITICALITY ignore TYPE RICactions- FailedToBeModifiedForModification-List PRESENCE optional}| { ID id-RICactionsAddedForModification-List CRITICALITY ignore TYPE RICactions- AddedForModification-List PRESENCE optional}| { ID id-RICactionsFailedToBeAddedForModification-List CRITICALITY ignore TYPE RICactions- FailedToBeAddedForModification-List PRESENCE optional}, … } RICactions-RemovedForModification-List ::= SEQUENCE (SIZE(0..maxofRICactionID)) OF ProtocolIE- SingleContainer {{RICaction-RemovedForModification-ItemIEs} } RICaction-RemovedForModification-ItemIEs E2AP-PROTOCOL-IES ::= { { ID id-RICaction-RemovedForModification-Item CRITICALITY ignore TYPE RICaction- RemovedForModification-Item PRESENCE mandatory }, … } RICaction-RemovedForModification-Item ::= SEQUENCE { ricActionID RICactionID, … } RICactions-FailedToBeRemovedForModification-List ::= SEQUENCE (SIZE(0..maxofRICactionID)) OF ProtocolIE-SingleContainer {{RICaction-FailedToBeRemovedForModification-ItemIEs} } RICaction-FailedToBeRemovedForModification-ItemIEs E2AP-PROTOCOL-IES ::= { { ID id-RICaction-FailedToBeRemovedForModification-Item CRITICALITY ignore TYPE RICaction- FailedToBeRemovedForModification-Item PRESENCE mandatory }, … } RICaction-FailedToBeRemovedForModification-Item ::= SEQUENCE { ricActionID RICactionID, cause Cause, … } RICactions-ModifiedForModification-List ::= SEQUENCE (SIZE(0..maxofRICactionID)) OF ProtocolIE- SingleContainer {{RICaction-ModifiedForModification-ItemIEs} } RICaction-ModifiedForModification-ItemIEs E2AP-PROTOCOL-IES ::= { { ID id-RICaction-ModifiedForModification-Item CRITICALITY ignore TYPE RICaction- ModifiedForModification-Item PRESENCE mandatory }, … } RICaction-ModifiedForModification-Item ::= SEQUENCE { ricActionID RICactionID, … } RICactions-FailedToBeModifiedForModification-List ::= SEQUENCE (SIZE(0..maxofRICactionID)) OF ProtocolIE-SingleContainer {{RICaction-FailedToBeModifiedForModification-ItemIEs} } RICaction-FailedToBeModifiedForModification-ItemIEs E2AP-PROTOCOL-IES ::= { { ID id-RICaction-FailedToBeModifiedForModification-Item CRITICALITY ignore TYPE RICaction- FailedToBeModifiedForModification-Item PRESENCE mandatory }, … } RICaction-FailedToBeModifiedForModification-Item ::= SEQUENCE { ricActionID RICactionID, cause Cause, … } RICactions-AddedForModification-List ::= SEQUENCE (SIZE(0..maxofRICactionID)) OF ProtocolIE- SingleContainer {{RICaction-AddedForModification-ItemIEs} } RICaction-AddedForModification-ItemIEs E2AP-PROTOCOL-IES ::= { { ID id-RICaction-AddedForModification-Item CRITICALITY ignore TYPE RICaction- AddedForModification-Item PRESENCE mandatory }, … } RICaction-AddedForModification-Item ::= SEQUENCE { ETSI ETSI TS 104 039 V4.0.0 (2024-10) 82 ricActionID RICactionID, … } RICactions-FailedToBeAddedForModification-List ::= SEQUENCE (SIZE(0..maxofRICactionID)) OF ProtocolIE-SingleContainer {{RICaction-FailedToBeAddedForModification-ItemIEs} } RICaction-FailedToBeAddedForModification-ItemIEs E2AP-PROTOCOL-IES ::= { { ID id-RICaction-FailedToBeAddedForModification-Item CRITICALITY ignore TYPE RICaction- FailedToBeAddedForModification-Item PRESENCE mandatory }, … } RICaction-FailedToBeAddedForModification-Item ::= SEQUENCE { ricActionID RICactionID, cause Cause, … } -- ************************************************************** -- -- RIC SUBSCRIPTION MODIFICATION FAILURE -- -- ************************************************************** RICsubscriptionModificationFailure ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RICsubscriptionModificationFailure-IEs}}, … } RICsubscriptionModificationFailure-IEs E2AP-PROTOCOL-IES ::= { { ID id-RICrequestID CRITICALITY reject TYPE RICrequestID PRESENCE mandatory}| { ID id-RANfunctionID CRITICALITY reject TYPE RANfunctionID PRESENCE mandatory}| { ID id-Cause CRITICALITY reject TYPE Cause PRESENCE mandatory}| { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional}, … } -- ************************************************************** -- -- RIC Subscription Modification Required Elementary Procedure -- -- ************************************************************** -- ************************************************************** -- -- RIC SUBSCRIPTION MODIFICATION REQUIRED -- -- ************************************************************** RICsubscriptionModificationRequired ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RICsubscriptionModificationRequired-IEs}}, … } RICsubscriptionModificationRequired-IEs E2AP-PROTOCOL-IES ::= { { ID id-RICrequestID CRITICALITY reject TYPE RICrequestID PRESENCE mandatory}| { ID id-RANfunctionID CRITICALITY reject TYPE RANfunctionID PRESENCE mandatory}| { ID id-RICactionsRequiredToBeModified-List CRITICALITY ignore TYPE RICactions- RequiredToBeModified-List PRESENCE optional}| { ID id-RICactionsRequiredToBeRemoved-List CRITICALITY ignore TYPE RICactions- RequiredToBeRemoved-List PRESENCE optional}, … } RICactions-RequiredToBeModified-List ::= SEQUENCE (SIZE(0..maxofRICactionID)) OF ProtocolIE- SingleContainer {{RICaction-RequiredToBeModified-ItemIEs} } RICaction-RequiredToBeModified-ItemIEs E2AP-PROTOCOL-IES ::= { { ID id-RICaction-RequiredToBeModified-Item CRITICALITY ignore TYPE RICaction- RequiredToBeModified-Item PRESENCE mandatory }, … } RICaction-RequiredToBeModified-Item ::= SEQUENCE { ricActionID RICactionID, ETSI ETSI TS 104 039 V4.0.0 (2024-10) 83 ricTimeToWait RICtimeToWait, … } RICactions-RequiredToBeRemoved-List ::= SEQUENCE (SIZE(0..maxofRICactionID)) OF ProtocolIE- SingleContainer {{RICaction-RequiredToBeRemoved-ItemIEs} } RICaction-RequiredToBeRemoved-ItemIEs E2AP-PROTOCOL-IES ::= { { ID id-RICaction-RequiredToBeRemoved-Item CRITICALITY ignore TYPE RICaction- RequiredToBeRemoved-Item PRESENCE mandatory }, … } RICaction-RequiredToBeRemoved-Item ::= SEQUENCE { ricActionID RICactionID, cause Cause, … } -- ************************************************************** -- -- RIC SUBSCRIPTION MODIFICATION CONFIRM -- -- ************************************************************** RICsubscriptionModificationConfirm ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RICsubscriptionModificationConfirm-IEs}}, … } RICsubscriptionModificationConfirm-IEs E2AP-PROTOCOL-IES ::= { { ID id-RICrequestID CRITICALITY reject TYPE RICrequestID PRESENCE mandatory}| { ID id-RANfunctionID CRITICALITY reject TYPE RANfunctionID PRESENCE mandatory}| { ID id-RICactionsConfirmedForModification-List CRITICALITY ignore TYPE RICactions- ConfirmedForModification-List PRESENCE optional}| { ID id-RICactionsRefusedToBeModified-List CRITICALITY ignore TYPE RICactions- RefusedToBeModified-List PRESENCE optional}| { ID id-RICactionsConfirmedForRemoval-List CRITICALITY ignore TYPE RICactions- ConfirmedForRemoval-List PRESENCE optional}| { ID id-RICactionsRefusedToBeRemoved-List CRITICALITY ignore TYPE RICactions- RefusedToBeRemoved-List PRESENCE optional}, … } RICactions-ConfirmedForModification-List ::= SEQUENCE (SIZE(0..maxofRICactionID)) OF ProtocolIE- SingleContainer {{RICaction-ConfirmedForModification-ItemIEs} } RICaction-ConfirmedForModification-ItemIEs E2AP-PROTOCOL-IES ::= { { ID id-RICaction-ConfirmedForModification-Item CRITICALITY ignore TYPE RICaction- ConfirmedForModification-Item PRESENCE mandatory }, … } RICaction-ConfirmedForModification-Item ::= SEQUENCE { ricActionID RICactionID, … } RICactions-RefusedToBeModified-List ::= SEQUENCE (SIZE(0..maxofRICactionID)) OF ProtocolIE- SingleContainer {{RICaction-RefusedToBeModified-ItemIEs} } RICaction-RefusedToBeModified-ItemIEs E2AP-PROTOCOL-IES ::= { { ID id-RICaction-RefusedToBeModified-Item CRITICALITY ignore TYPE RICaction- RefusedToBeModified-Item PRESENCE mandatory }, … } RICaction-RefusedToBeModified-Item ::= SEQUENCE { ricActionID RICactionID, cause Cause, … } RICactions-ConfirmedForRemoval-List ::= SEQUENCE (SIZE(0..maxofRICactionID)) OF ProtocolIE- SingleContainer {{RICaction-ConfirmedForRemoval-ItemIEs} } RICaction-ConfirmedForRemoval-ItemIEs E2AP-PROTOCOL-IES ::= { ETSI ETSI TS 104 039 V4.0.0 (2024-10) 84 { ID id-RICaction-ConfirmedForRemoval-Item CRITICALITY ignore TYPE RICaction- ConfirmedForRemoval-Item PRESENCE mandatory }, … } RICaction-ConfirmedForRemoval-Item ::= SEQUENCE { ricActionID RICactionID, … } RICactions-RefusedToBeRemoved-List ::= SEQUENCE (SIZE(0..maxofRICactionID)) OF ProtocolIE- SingleContainer {{RICaction-RefusedToBeRemoved-ItemIEs} } RICaction-RefusedToBeRemoved-ItemIEs E2AP-PROTOCOL-IES ::= { { ID id-RICaction-RefusedToBeRemoved-Item CRITICALITY ignore TYPE RICaction- RefusedToBeRemoved-Item PRESENCE mandatory }, … } RICaction-RefusedToBeRemoved-Item ::= SEQUENCE { ricActionID RICactionID, cause Cause, … } -- ************************************************************** -- -- RIC SUBSCRIPTION MODIFICATION REFUSE -- -- ************************************************************** RICsubscriptionModificationRefuse ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RICsubscriptionModificationRefuse-IEs}}, … } RICsubscriptionModificationRefuse-IEs E2AP-PROTOCOL-IES ::= { { ID id-RICrequestID CRITICALITY reject TYPE RICrequestID PRESENCE mandatory}| { ID id-RANfunctionID CRITICALITY reject TYPE RANfunctionID PRESENCE mandatory}| { ID id-Cause CRITICALITY reject TYPE Cause PRESENCE mandatory}| { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional}, … } -- ************************************************************** -- -- RIC Indication Elementary Procedure -- -- ************************************************************** -- ************************************************************** -- -- RIC INDICATION -- -- ************************************************************** RICindication ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RICindication-IEs}}, … } RICindication-IEs E2AP-PROTOCOL-IES ::= { { ID id-RICrequestID CRITICALITY reject TYPE RICrequestID PRESENCE mandatory }| { ID id-RANfunctionID CRITICALITY reject TYPE RANfunctionID PRESENCE mandatory }| { ID id-RICactionID CRITICALITY reject TYPE RICactionID PRESENCE mandatory }| { ID id-RICindicationSN CRITICALITY reject TYPE RICindicationSN PRESENCE optional }| { ID id-RICindicationType CRITICALITY reject TYPE RICindicationType PRESENCE mandatory }| { ID id-RICindicationHeader CRITICALITY reject TYPE RICindicationHeader PRESENCE mandatory }| { ID id-RICindicationMessage CRITICALITY reject TYPE RICindicationMessage PRESENCE mandatory }| ETSI ETSI TS 104 039 V4.0.0 (2024-10) 85 { ID id-RICcallProcessID CRITICALITY reject TYPE RICcallProcessID PRESENCE optional }, … } -- ************************************************************** -- -- RIC Control Elementary Procedure -- -- ************************************************************** -- ************************************************************** -- -- RIC CONTROL REQUEST -- -- ************************************************************** RICcontrolRequest ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RICcontrolRequest-IEs}}, … } RICcontrolRequest-IEs E2AP-PROTOCOL-IES ::= { { ID id-RICrequestID CRITICALITY reject TYPE RICrequestID PRESENCE mandatory }| { ID id-RANfunctionID CRITICALITY reject TYPE RANfunctionID PRESENCE mandatory }| { ID id-RICcallProcessID CRITICALITY reject TYPE RICcallProcessID PRESENCE optional }| { ID id-RICcontrolHeader CRITICALITY reject TYPE RICcontrolHeader PRESENCE mandatory }| { ID id-RICcontrolMessage CRITICALITY reject TYPE RICcontrolMessage PRESENCE mandatory }| { ID id-RICcontrolAckRequest CRITICALITY reject TYPE RICcontrolAckRequest PRESENCE optional }, … } -- ************************************************************** -- -- RIC CONTROL ACKNOWLEDGE -- -- ************************************************************** RICcontrolAcknowledge ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RICcontrolAcknowledge-IEs}}, … } RICcontrolAcknowledge-IEs E2AP-PROTOCOL-IES ::= { { ID id-RICrequestID CRITICALITY reject TYPE RICrequestID PRESENCE mandatory }| { ID id-RANfunctionID CRITICALITY reject TYPE RANfunctionID PRESENCE mandatory }| { ID id-RICcallProcessID CRITICALITY reject TYPE RICcallProcessID PRESENCE optional }| { ID id-RICcontrolOutcome CRITICALITY reject TYPE RICcontrolOutcome PRESENCE optional }, … } -- ************************************************************** -- -- RIC CONTROL FAILURE -- -- ************************************************************** RICcontrolFailure ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RICcontrolFailure-IEs}}, … } RICcontrolFailure-IEs E2AP-PROTOCOL-IES ::= { { ID id-RICrequestID CRITICALITY reject TYPE RICrequestID PRESENCE mandatory }| { ID id-RANfunctionID CRITICALITY reject TYPE RANfunctionID PRESENCE mandatory }| { ID id-RICcallProcessID CRITICALITY reject TYPE RICcallProcessID PRESENCE optional }| { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }| { ID id-RICcontrolOutcome CRITICALITY reject TYPE RICcontrolOutcome PRESENCE optional }, …, ETSI ETSI TS 104 039 V4.0.0 (2024-10) 86 { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional } } -- ************************************************************** -- -- RIC QUERY Elementary Procedure -- -- ************************************************************** -- ************************************************************** -- -- RIC QUERY REQUEST -- -- ************************************************************** RICqueryRequest ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RICqueryRequest-IEs}}, … } RICqueryRequest-IEs E2AP-PROTOCOL-IES ::= { { ID id-RICrequestID CRITICALITY reject TYPE RICrequestID PRESENCE mandatory }| { ID id-RANfunctionID CRITICALITY reject TYPE RANfunctionID PRESENCE mandatory }| { ID id-RICqueryHeader CRITICALITY reject TYPE RICqueryHeader PRESENCE mandatory }| { ID id-RICqueryDefinition CRITICALITY reject TYPE RICqueryDefinition PRESENCE mandatory }, … } -- ************************************************************** -- -- RIC QUERY RESPONSE -- -- ************************************************************** RICqueryResponse ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RICqueryResponse-IEs}}, … } RICqueryResponse-IEs E2AP-PROTOCOL-IES ::= { { ID id-RICrequestID CRITICALITY reject TYPE RICrequestID PRESENCE mandatory }| { ID id-RANfunctionID CRITICALITY reject TYPE RANfunctionID PRESENCE mandatory }| { ID id-RICqueryOutcome CRITICALITY reject TYPE RICqueryOutcome PRESENCE mandatory }, … } -- ************************************************************** -- -- RIC QUERY FAILURE -- -- ************************************************************** RICqueryFailure ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RICqueryFailure-IEs}}, … } RICqueryFailure-IEs E2AP-PROTOCOL-IES ::= { { ID id-RICrequestID CRITICALITY reject TYPE RICrequestID PRESENCE mandatory }| { ID id-RANfunctionID CRITICALITY reject TYPE RANfunctionID PRESENCE mandatory }| { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }| { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, … } -- ************************************************************** -- -- MESSAGES FOR GLOBAL PROCEDURES -- -- ************************************************************** ETSI ETSI TS 104 039 V4.0.0 (2024-10) 87 -- ************************************************************** -- -- Error Indication Elementary Procedure -- -- ************************************************************** -- ************************************************************** -- -- ERROR INDICATION -- -- ************************************************************** ErrorIndication ::= SEQUENCE { protocolIEs ProtocolIE-Container {{ErrorIndication-IEs}}, … } ErrorIndication-IEs E2AP-PROTOCOL-IES ::= { { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE optional }| { ID id-RICrequestID CRITICALITY reject TYPE RICrequestID PRESENCE optional }| { ID id-RANfunctionID CRITICALITY reject TYPE RANfunctionID PRESENCE optional }| { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE optional }| { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, … } -- ************************************************************** -- -- E2 Setup Elementary Procedure -- -- ************************************************************** -- ************************************************************** -- -- E2 SETUP REQUEST -- -- ************************************************************** E2setupRequest ::= SEQUENCE { protocolIEs ProtocolIE-Container { {E2setupRequestIEs} }, … } E2setupRequestIEs E2AP-PROTOCOL-IES ::= { { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| { ID id-GlobalE2node-ID CRITICALITY reject TYPE GlobalE2node-ID PRESENCE mandatory }| { ID id-RANfunctionsAdded CRITICALITY reject TYPE RANfunctions-List PRESENCE mandatory }| { ID id-E2nodeComponentConfigAddition CRITICALITY reject TYPE E2nodeComponentConfigAddition- List PRESENCE mandatory }, … } -- ************************************************************** -- -- E2 SETUP RESPONSE -- -- ************************************************************** E2setupResponse ::= SEQUENCE { protocolIEs ProtocolIE-Container { {E2setupResponseIEs} }, … } E2setupResponseIEs E2AP-PROTOCOL-IES ::= { { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| { ID id-GlobalRIC-ID CRITICALITY reject TYPE GlobalRIC-ID PRESENCE mandatory }| { ID id-RANfunctionsAccepted CRITICALITY reject TYPE RANfunctionsID-List PRESENCE optional }| { ID id-RANfunctionsRejected CRITICALITY reject TYPE RANfunctionsIDcause-List PRESENCE optional }| ETSI ETSI TS 104 039 V4.0.0 (2024-10) 88 { ID id-E2nodeComponentConfigAdditionAck CRITICALITY reject TYPE E2nodeComponentConfigAdditionAck-List PRESENCE mandatory }, … } -- ************************************************************** -- -- E2 SETUP FAILURE -- -- ************************************************************** E2setupFailure ::= SEQUENCE { protocolIEs ProtocolIE-Container { {E2setupFailureIEs} }, … } E2setupFailureIEs E2AP-PROTOCOL-IES ::= { { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }| { ID id-TimeToWait CRITICALITY ignore TYPE TimeToWait PRESENCE optional }| { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }| { ID id-TNLinformation CRITICALITY ignore TYPE TNLinformation PRESENCE optional }, … } -- ************************************************************** -- -- E2 Connection Update Elementary Procedure -- -- ************************************************************** -- ************************************************************** -- -- E2 CONNECTION UPDATE -- -- ************************************************************** E2connectionUpdate ::= SEQUENCE { protocolIEs ProtocolIE-Container {{E2connectionUpdate-IEs}}, … } E2connectionUpdate-IEs E2AP-PROTOCOL-IES ::= { { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| { ID id-E2connectionUpdateAdd CRITICALITY reject TYPE E2connectionUpdate-List PRESENCE optional }| { ID id-E2connectionUpdateRemove CRITICALITY reject TYPE E2connectionUpdateRemove-List PRESENCE optional }| { ID id-E2connectionUpdateModify CRITICALITY reject TYPE E2connectionUpdate-List PRESENCE optional }, … } E2connectionUpdate-List ::= SEQUENCE (SIZE(1..maxofTNLA)) OF ProtocolIE-SingleContainer { {E2connectionUpdate-ItemIEs} } E2connectionUpdate-ItemIEs E2AP-PROTOCOL-IES ::= { { ID id-E2connectionUpdate-Item CRITICALITY ignore TYPE E2connectionUpdate-Item PRESENCE mandatory }, … } E2connectionUpdate-Item ::= SEQUENCE { tnlInformation TNLinformation, tnlUsage TNLusage, … } E2connectionUpdateRemove-List ::= SEQUENCE (SIZE(1..maxofTNLA)) OF ProtocolIE-SingleContainer { {E2connectionUpdateRemove-ItemIEs} } E2connectionUpdateRemove-ItemIEs E2AP-PROTOCOL-IES ::= { { ID id-E2connectionUpdateRemove-Item CRITICALITY ignore TYPE E2connectionUpdateRemove-Item PRESENCE mandatory }, ETSI ETSI TS 104 039 V4.0.0 (2024-10) 89 … } E2connectionUpdateRemove-Item ::= SEQUENCE { tnlInformation TNLinformation, … } -- ************************************************************** -- -- E2 CONNECTION UPDATE ACKNOWLEDGE -- -- ************************************************************** E2connectionUpdateAcknowledge ::= SEQUENCE { protocolIEs ProtocolIE-Container {{E2connectionUpdateAck-IEs}}, … } E2connectionUpdateAck-IEs E2AP-PROTOCOL-IES ::= { { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| { ID id-E2connectionSetup CRITICALITY reject TYPE E2connectionUpdate-List PRESENCE optional }| { ID id-E2connectionSetupFailed CRITICALITY reject TYPE E2connectionSetupFailed-List PRESENCE optional }, … } E2connectionSetupFailed-List ::= SEQUENCE (SIZE(1..maxofTNLA)) OF ProtocolIE-SingleContainer { {E2connectionSetupFailed-ItemIEs} } E2connectionSetupFailed-ItemIEs E2AP-PROTOCOL-IES ::= { { ID id-E2connectionSetupFailed-Item CRITICALITY ignore TYPE E2connectionSetupFailed-Item PRESENCE mandatory }, … } E2connectionSetupFailed-Item ::= SEQUENCE { tnlInformation TNLinformation, cause Cause, … } -- ************************************************************** -- -- E2 CONNECTION UPDATE FAILURE -- -- ************************************************************** E2connectionUpdateFailure ::= SEQUENCE { protocolIEs ProtocolIE-Container {{E2connectionUpdateFailure-IEs}}, … } E2connectionUpdateFailure-IEs E2AP-PROTOCOL-IES ::= { { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| { ID id-Cause CRITICALITY reject TYPE Cause PRESENCE optional }| { ID id-TimeToWait CRITICALITY ignore TYPE TimeToWait PRESENCE optional }| { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, … } -- ************************************************************** -- -- E2 Node Configuration Update Elementary Procedure -- -- ************************************************************** -- ************************************************************** -- -- E2 NODE CONFIGURATION UPDATE -- -- ************************************************************** E2nodeConfigurationUpdate ::= SEQUENCE { ETSI ETSI TS 104 039 V4.0.0 (2024-10) 90 protocolIEs ProtocolIE-Container {{E2nodeConfigurationUpdate-IEs}}, … } E2nodeConfigurationUpdate-IEs E2AP-PROTOCOL-IES ::= { { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| { ID id-GlobalE2node-ID CRITICALITY reject TYPE GlobalE2node-ID PRESENCE optional }| { ID id-E2nodeComponentConfigAddition CRITICALITY reject TYPE E2nodeComponentConfigAddition- List PRESENCE optional }| { ID id-E2nodeComponentConfigUpdate CRITICALITY reject TYPE E2nodeComponentConfigUpdate- List PRESENCE optional }| { ID id-E2nodeComponentConfigRemoval CRITICALITY reject TYPE E2nodeComponentConfigRemoval- List PRESENCE optional }| { ID id-E2nodeTNLassociationRemoval CRITICALITY reject TYPE E2nodeTNLassociationRemoval- List PRESENCE optional }, … } E2nodeComponentConfigAddition-List ::= SEQUENCE (SIZE(1..maxofE2nodeComponents)) OF ProtocolIE- SingleContainer { {E2nodeComponentConfigAddition-ItemIEs} } E2nodeComponentConfigAddition-ItemIEs E2AP-PROTOCOL-IES ::= { { ID id-E2nodeComponentConfigAddition-Item CRITICALITY reject TYPE E2nodeComponentConfigAddition-Item PRESENCE mandatory }, … } E2nodeComponentConfigAddition-Item ::= SEQUENCE { e2nodeComponentInterfaceType E2nodeComponentInterfaceType, e2nodeComponentID E2nodeComponentID, e2nodeComponentConfiguration E2nodeComponentConfiguration, … } E2nodeComponentConfigUpdate-List ::= SEQUENCE (SIZE(1..maxofE2nodeComponents)) OF ProtocolIE- SingleContainer { {E2nodeComponentConfigUpdate-ItemIEs} } E2nodeComponentConfigUpdate-ItemIEs E2AP-PROTOCOL-IES ::= { { ID id-E2nodeComponentConfigUpdate-Item CRITICALITY reject TYPE E2nodeComponentConfigUpdate-Item PRESENCE mandatory }, … } E2nodeComponentConfigUpdate-Item ::= SEQUENCE { e2nodeComponentInterfaceType E2nodeComponentInterfaceType, e2nodeComponentID E2nodeComponentID, e2nodeComponentConfiguration E2nodeComponentConfiguration, … } E2nodeComponentConfigRemoval-List ::= SEQUENCE (SIZE(1..maxofE2nodeComponents)) OF ProtocolIE- SingleContainer { {E2nodeComponentConfigRemoval-ItemIEs} } E2nodeComponentConfigRemoval-ItemIEs E2AP-PROTOCOL-IES ::= { { ID id-E2nodeComponentConfigRemoval-Item CRITICALITY reject TYPE E2nodeComponentConfigRemoval-Item PRESENCE mandatory }, … } E2nodeComponentConfigRemoval-Item ::= SEQUENCE { e2nodeComponentInterfaceType E2nodeComponentInterfaceType, e2nodeComponentID E2nodeComponentID, … } E2nodeTNLassociationRemoval-List ::= SEQUENCE (SIZE(1..maxofTNLA)) OF ProtocolIE-SingleContainer { {E2nodeTNLassociationRemoval-ItemIEs} } E2nodeTNLassociationRemoval-ItemIEs E2AP-PROTOCOL-IES ::= { { ID id-E2nodeTNLassociationRemoval-Item CRITICALITY reject TYPE E2nodeTNLassociationRemoval-Item PRESENCE mandatory }, … } E2nodeTNLassociationRemoval-Item ::= SEQUENCE { tnlInformation TNLinformation, ETSI ETSI TS 104 039 V4.0.0 (2024-10) 91 tnlInformationRIC TNLinformation, … } -- ************************************************************** -- -- E2 NODE CONFIGURATION UPDATE ACKNOWLEDGE -- -- ************************************************************** E2nodeConfigurationUpdateAcknowledge ::= SEQUENCE { protocolIEs ProtocolIE-Container {{E2nodeConfigurationUpdateAcknowledge- IEs}}, … } E2nodeConfigurationUpdateAcknowledge-IEs E2AP-PROTOCOL-IES ::= { { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| { ID id-E2nodeComponentConfigAdditionAck CRITICALITY reject TYPE E2nodeComponentConfigAdditionAck-List PRESENCE optional }| { ID id-E2nodeComponentConfigUpdateAck CRITICALITY reject TYPE E2nodeComponentConfigUpdateAck-List PRESENCE optional }| { ID id-E2nodeComponentConfigRemovalAck CRITICALITY reject TYPE E2nodeComponentConfigRemovalAck-List PRESENCE optional }, … } E2nodeComponentConfigAdditionAck-List ::= SEQUENCE (SIZE(1..maxofE2nodeComponents)) OF ProtocolIE- SingleContainer { {E2nodeComponentConfigAdditionAck-ItemIEs} } E2nodeComponentConfigAdditionAck-ItemIEs E2AP-PROTOCOL-IES ::= { { ID id-E2nodeComponentConfigAdditionAck-Item CRITICALITY reject TYPE E2nodeComponentConfigAdditionAck-Item PRESENCE mandatory }, … } E2nodeComponentConfigAdditionAck-Item ::= SEQUENCE { e2nodeComponentInterfaceType E2nodeComponentInterfaceType, e2nodeComponentID E2nodeComponentID, e2nodeComponentConfigurationAck E2nodeComponentConfigurationAck, … } E2nodeComponentConfigUpdateAck-List ::= SEQUENCE (SIZE(1..maxofE2nodeComponents)) OF ProtocolIE- SingleContainer { {E2nodeComponentConfigUpdateAck-ItemIEs} } E2nodeComponentConfigUpdateAck-ItemIEs E2AP-PROTOCOL-IES ::= { { ID id-E2nodeComponentConfigUpdateAck-Item CRITICALITY reject TYPE E2nodeComponentConfigUpdateAck-Item PRESENCE mandatory }, … } E2nodeComponentConfigUpdateAck-Item ::= SEQUENCE { e2nodeComponentInterfaceType E2nodeComponentInterfaceType, e2nodeComponentID E2nodeComponentID, e2nodeComponentConfigurationAck E2nodeComponentConfigurationAck, … } E2nodeComponentConfigRemovalAck-List ::= SEQUENCE (SIZE(1..maxofE2nodeComponents)) OF ProtocolIE- SingleContainer { {E2nodeComponentConfigRemovalAck-ItemIEs} } E2nodeComponentConfigRemovalAck-ItemIEs E2AP-PROTOCOL-IES ::= { { ID id-E2nodeComponentConfigRemovalAck-Item CRITICALITY reject TYPE E2nodeComponentConfigRemovalAck-Item PRESENCE mandatory }, … } E2nodeComponentConfigRemovalAck-Item ::= SEQUENCE { e2nodeComponentInterfaceType E2nodeComponentInterfaceType, e2nodeComponentID E2nodeComponentID, e2nodeComponentConfigurationAck E2nodeComponentConfigurationAck, … } -- ************************************************************** -- -- E2 NODE CONFIGURATION UPDATE FAILURE ETSI ETSI TS 104 039 V4.0.0 (2024-10) 92 -- -- ************************************************************** E2nodeConfigurationUpdateFailure ::= SEQUENCE { protocolIEs ProtocolIE-Container {{E2nodeConfigurationUpdateFailure-IEs}}, … } E2nodeConfigurationUpdateFailure-IEs E2AP-PROTOCOL-IES ::= { { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }| { ID id-TimeToWait CRITICALITY ignore TYPE TimeToWait PRESENCE optional }| { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, … } -- ************************************************************** -- -- Reset Elementary Procedure -- -- ************************************************************** -- ************************************************************** -- -- RESET REQUEST -- -- ************************************************************** ResetRequest ::= SEQUENCE { protocolIEs ProtocolIE-Container { {ResetRequestIEs} }, … } ResetRequestIEs E2AP-PROTOCOL-IES ::= { { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }, … } -- ************************************************************** -- -- RESET RESPONSE -- -- ************************************************************** ResetResponse ::= SEQUENCE { protocolIEs ProtocolIE-Container { {ResetResponseIEs} }, … } ResetResponseIEs E2AP-PROTOCOL-IES ::= { { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, … } -- ************************************************************** -- -- RIC Service Update Elementary Procedure -- -- ************************************************************** -- ************************************************************** -- -- RIC SERVICE UPDATE -- -- ************************************************************** RICserviceUpdate ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RICserviceUpdate-IEs}}, … } ETSI ETSI TS 104 039 V4.0.0 (2024-10) 93 RICserviceUpdate-IEs E2AP-PROTOCOL-IES ::= { { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| { ID id-RANfunctionsAdded CRITICALITY reject TYPE RANfunctions-List PRESENCE optional }| { ID id-RANfunctionsModified CRITICALITY reject TYPE RANfunctions-List PRESENCE optional }| { ID id-RANfunctionsDeleted CRITICALITY reject TYPE RANfunctionsID-List PRESENCE optional }, … } RANfunctions-List ::= SEQUENCE (SIZE(1..maxofRANfunctionID)) OF ProtocolIE-SingleContainer { {RANfunction-ItemIEs} } RANfunction-ItemIEs E2AP-PROTOCOL-IES ::= { { ID id-RANfunction-Item CRITICALITY ignore TYPE RANfunction-Item PRESENCE mandatory }, … } RANfunction-Item ::= SEQUENCE { ranFunctionID RANfunctionID, ranFunctionDefinition RANfunctionDefinition, ranFunctionRevision RANfunctionRevision, ranFunctionOID RANfunctionOID, … } RANfunctionsID-List ::= SEQUENCE (SIZE(1..maxofRANfunctionID)) OF ProtocolIE- SingleContainer{{RANfunctionID-ItemIEs}} RANfunctionID-ItemIEs E2AP-PROTOCOL-IES ::= { { ID id-RANfunctionID-Item CRITICALITY ignore TYPE RANfunctionID-Item PRESENCE mandatory }, … } RANfunctionID-Item ::= SEQUENCE { ranFunctionID RANfunctionID, ranFunctionRevision RANfunctionRevision, … } -- ************************************************************** -- -- RIC SERVICE UPDATE ACKNOWLEDGE -- -- ************************************************************** RICserviceUpdateAcknowledge ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RICserviceUpdateAcknowledge-IEs}}, … } RICserviceUpdateAcknowledge-IEs E2AP-PROTOCOL-IES ::= { { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| { ID id-RANfunctionsAccepted CRITICALITY reject TYPE RANfunctionsID-List PRESENCE optional }| { ID id-RANfunctionsRejected CRITICALITY reject TYPE RANfunctionsIDcause-List PRESENCE optional }, … } RANfunctionsIDcause-List ::= SEQUENCE (SIZE(1..maxofRANfunctionID)) OF ProtocolIE-SingleContainer { {RANfunctionIDcause-ItemIEs} } RANfunctionIDcause-ItemIEs E2AP-PROTOCOL-IES ::= { { ID id-RANfunctionIEcause-Item CRITICALITY ignore TYPE RANfunctionIDcause-Item PRESENCE mandatory }, … } RANfunctionIDcause-Item ::= SEQUENCE { ranFunctionID RANfunctionID, cause Cause, ETSI ETSI TS 104 039 V4.0.0 (2024-10) 94 … } -- ************************************************************** -- -- RIC SERVICE UPDATE FAILURE -- -- ************************************************************** RICserviceUpdateFailure ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RICserviceUpdateFailure-IEs}}, … } RICserviceUpdateFailure-IEs E2AP-PROTOCOL-IES ::= { { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| { ID id-Cause CRITICALITY reject TYPE Cause PRESENCE mandatory }| { ID id-TimeToWait CRITICALITY ignore TYPE TimeToWait PRESENCE optional }| { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, … } -- ************************************************************** -- -- RIC Service Query Elementary Procedure -- -- ************************************************************** -- ************************************************************** -- -- RIC SERVICE QUERY -- -- ************************************************************** RICserviceQuery ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RICserviceQuery-IEs}}, … } RICserviceQuery-IEs E2AP-PROTOCOL-IES ::= { { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| { ID id-RANfunctionsAccepted CRITICALITY reject TYPE RANfunctionsID-List PRESENCE optional }, … } -- ************************************************************** -- -- E2 Removal Elementary Procedure -- -- ************************************************************** -- ************************************************************** -- -- E2 REMOVAL REQUEST -- -- ************************************************************** E2RemovalRequest ::= SEQUENCE { protocolIEs ProtocolIE-Container { {E2RemovalRequestIEs} }, … } E2RemovalRequestIEs E2AP-PROTOCOL-IES ::= { { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }, … } -- ************************************************************** -- -- E2 REMOVAL RESPONSE -- -- ************************************************************** E2RemovalResponse ::= SEQUENCE { ETSI ETSI TS 104 039 V4.0.0 (2024-10) 95 protocolIEs ProtocolIE-Container { {E2RemovalResponseIEs} }, … } E2RemovalResponseIEs E2AP-PROTOCOL-IES ::= { { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, … } -- ************************************************************** -- -- E2 REMOVAL FAILURE -- -- ************************************************************** E2RemovalFailure ::= SEQUENCE { protocolIEs ProtocolIE-Container { {E2RemovalFailureIEs} }, … } E2RemovalFailureIEs E2AP-PROTOCOL-IES ::= { { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }| { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, … } END -- ASN1STOP |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.3.5 Information Element Definitions | -- ASN1START -- ************************************************************** -- E2AP -- Information Element Definitions -- -- ************************************************************** E2AP-IEs { iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) oran(53148) e2(1) version2 (2) e2ap(1) e2ap-IEs (2)} DEFINITIONS AUTOMATIC TAGS ::= BEGIN IMPORTS Criticality, Presence, ProcedureCode, ProtocolIE-ID, TriggeringMessage FROM E2AP-CommonDataTypes maxnoofErrors, maxProtocolIEs FROM E2AP-Constants; -- A -- ************************************************************** -- [New for E2AP v02.00] copied from 3GPP 38.413 (NGAP) IEs -- ************************************************************** AMFName ::= PrintableString (SIZE(1..150, …)) -- B -- C Cause ::= CHOICE { ricRequest CauseRICrequest, ricService CauseRICservice, ETSI ETSI TS 104 039 V4.0.0 (2024-10) 96 e2Node CauseE2node, transport CauseTransport, protocol CauseProtocol, misc CauseMisc, … } CauseE2node ::= ENUMERATED { e2node-component-unknown, … } CauseMisc ::= ENUMERATED { control-processing-overload, hardware-failure, om-intervention, unspecified, … } CauseProtocol ::= ENUMERATED { transfer-syntax-error, abstract-syntax-error-reject, abstract-syntax-error-ignore-and-notify, message-not-compatible-with-receiver-state, semantic-error, abstract-syntax-error-falsely-constructed-message, unspecified, … } CauseRICrequest ::= ENUMERATED { ran-function-id-invalid, action-not-supported, excessive-actions, duplicate-action, duplicate-event-trigger, function-resource-limit, request-id-unknown, inconsistent-action-subsequent-action-sequence, control-message-invalid, ric-call-process-id-invalid, control-timer-expired, control-failed-to-execute, system-not-ready, unspecified, … , ric-subscription-end-time-expired, ric-subscription-end-time-invalid, duplicate-ric-request-id, eventTriggerNotSupported, requested-information-unavailable, invalid-information-request } CauseRICservice ::= ENUMERATED{ ran-function-not-supported, excessive-functions, ric-resource-limit, … } CauseTransport ::= ENUMERATED { unspecified, transport-resource-unavailable, … } -- ************************************************************** -- copied from 3GPP 38.413 (NGAP) IEs -- note: ie-Extensions removed -- ************************************************************** CriticalityDiagnostics ::= SEQUENCE { procedureCode ProcedureCode OPTIONAL, triggeringMessage TriggeringMessage OPTIONAL, procedureCriticality Criticality OPTIONAL, ricRequestorID RICrequestID OPTIONAL, iEsCriticalityDiagnostics CriticalityDiagnostics-IE-List OPTIONAL, … ETSI ETSI TS 104 039 V4.0.0 (2024-10) 97 } CriticalityDiagnostics-IE-List ::= SEQUENCE (SIZE(1..maxnoofErrors)) OF CriticalityDiagnostics-IE- Item CriticalityDiagnostics-IE-Item ::= SEQUENCE { iECriticality Criticality, iE-ID ProtocolIE-ID, typeOfError TypeOfError, … } -- D -- E -- Following IE used to carry 3GPP defined SETUP and RAN Configuration messages defined in F1AP, E1AP, XnAP, etc. E2nodeComponentConfiguration ::= SEQUENCE{ e2nodeComponentRequestPart OCTET STRING, e2nodeComponentResponsePart OCTET STRING, … } E2nodeComponentConfigurationAck ::= SEQUENCE{ updateOutcome ENUMERATED {success, failure, …}, failureCause Cause OPTIONAL, … } E2nodeComponentInterfaceType ::= ENUMERATED {ng, xn, e1, f1, w1, s1, x2, …} E2nodeComponentID ::= CHOICE{ e2nodeComponentInterfaceTypeNG E2nodeComponentInterfaceNG, e2nodeComponentInterfaceTypeXn E2nodeComponentInterfaceXn, e2nodeComponentInterfaceTypeE1 E2nodeComponentInterfaceE1, e2nodeComponentInterfaceTypeF1 E2nodeComponentInterfaceF1, e2nodeComponentInterfaceTypeW1 E2nodeComponentInterfaceW1, e2nodeComponentInterfaceTypeS1 E2nodeComponentInterfaceS1, e2nodeComponentInterfaceTypeX2 E2nodeComponentInterfaceX2, … } E2nodeComponentInterfaceE1 ::= SEQUENCE{ gNB-CU-UP-ID GNB-CU-UP-ID, … } E2nodeComponentInterfaceF1 ::= SEQUENCE{ gNB-DU-ID GNB-DU-ID, … } E2nodeComponentInterfaceNG ::= SEQUENCE{ amf-name AMFName, … } E2nodeComponentInterfaceS1 ::= SEQUENCE{ mme-name MMEname, … } E2nodeComponentInterfaceX2 ::= SEQUENCE{ global-eNB-ID GlobalENB-ID OPTIONAL, global-en-gNB-ID GlobalenGNB-ID OPTIONAL, … } E2nodeComponentInterfaceXn ::= SEQUENCE{ global-NG-RAN-Node-ID GlobalNG-RANNode-ID, … } E2nodeComponentInterfaceW1 ::= SEQUENCE{ ng-eNB-DU-ID NGENB-DU-ID, … } ETSI ETSI TS 104 039 V4.0.0 (2024-10) 98 -- ************************************************************** -- copied from 3GPP 36.423 (X2AP) IEs -- note: ie-Extensions removed -- ************************************************************** ENB-ID ::= CHOICE { macro-eNB-ID BIT STRING (SIZE (20)), home-eNB-ID BIT STRING (SIZE (28)), … , short-Macro-eNB-ID BIT STRING (SIZE(18)), long-Macro-eNB-ID BIT STRING (SIZE(21)) } -- ************************************************************** -- copied from 3GPP 38.423 (XnAP) IEs -- note: choice-extension removed -- ************************************************************** ENB-ID-Choice ::= CHOICE { enb-ID-macro BIT STRING (SIZE(20)), enb-ID-shortmacro BIT STRING (SIZE(18)), enb-ID-longmacro BIT STRING (SIZE(21)), … } -- ************************************************************** -- copied from 3GPP 36.423 (X2AP) IEs -- note: ie-Extensions removed -- Note: to avoid duplicate names with XnAP, GNB-ID renamed ENGNB-ID, GlobalGNB-ID renamed GlobalenGNB-ID -- ************************************************************** ENGNB-ID ::= CHOICE { gNB-ID BIT STRING (SIZE (22..32)), … } -- F -- G GlobalE2node-ID ::= CHOICE{ gNB GlobalE2node-gNB-ID, en-gNB GlobalE2node-en-gNB-ID, ng-eNB GlobalE2node-ng-eNB-ID, eNB GlobalE2node-eNB-ID, … } GlobalE2node-en-gNB-ID ::= SEQUENCE{ global-en-gNB-ID GlobalenGNB-ID, en-gNB-CU-UP-ID GNB-CU-UP-ID OPTIONAL, en-gNB-DU-ID GNB-DU-ID OPTIONAL, … } GlobalE2node-eNB-ID ::= SEQUENCE{ global-eNB-ID GlobalENB-ID, … } GlobalE2node-gNB-ID ::= SEQUENCE{ global-gNB-ID GlobalgNB-ID, global-en-gNB-ID GlobalenGNB-ID OPTIONAL, gNB-CU-UP-ID GNB-CU-UP-ID OPTIONAL, gNB-DU-ID GNB-DU-ID OPTIONAL, … } GlobalE2node-ng-eNB-ID ::= SEQUENCE{ global-ng-eNB-ID GlobalngeNB-ID, global-eNB-ID GlobalENB-ID OPTIONAL, ngENB-DU-ID NGENB-DU-ID OPTIONAL, … } -- ************************************************************** -- copied from 3GPP 36.423 (X2AP) IEs -- note: ie-Extensions removed -- ************************************************************** GlobalENB-ID ::= SEQUENCE { pLMN-Identity PLMN-Identity, eNB-ID ENB-ID, … } -- ************************************************************** -- copied from 3GPP 36.423 (X2AP) IEs ETSI ETSI TS 104 039 V4.0.0 (2024-10) 99 -- Note: to avoid duplicate names with XnAP, GNB-ID renamed ENGNB-ID, GlobalGNB-ID renamed GlobalenGNB-ID -- ************************************************************** GlobalenGNB-ID ::= SEQUENCE { pLMN-Identity PLMN-Identity, gNB-ID ENGNB-ID, … } -- ************************************************************** -- copied from 3GPP 38.423 (XnAP) IEs -- note: choice-extension removed -- ************************************************************** GlobalgNB-ID ::= SEQUENCE { plmn-id PLMN-Identity, gnb-id GNB-ID-Choice, … } -- ************************************************************** -- copied from 3GPP 38.423 (XnAP) IEs -- note: choice-extension removed -- ************************************************************** GlobalngeNB-ID ::= SEQUENCE { plmn-id PLMN-Identity, enb-id ENB-ID-Choice, … } -- ************************************************************** -- [NEW for E2AP v02.00] copied from 3GPP 38.423 (XnAP) IEs -- Note: extension field removed -- ************************************************************** GlobalNG-RANNode-ID ::= CHOICE { gNB GlobalgNB-ID, ng-eNB GlobalngeNB-ID, … } GlobalRIC-ID ::= SEQUENCE{ pLMN-Identity PLMN-Identity, ric-ID BIT STRING (SIZE (20)), … } -- ************************************************************** -- copied from 3GPP 37.483 (E1AP) IEs -- ************************************************************** GNB-CU-UP-ID::= INTEGER (0..68719476735) -- ************************************************************** -- copied from 3GPP 38.473 (F1AP) IEs -- ************************************************************** GNB-DU-ID::= INTEGER (0..68719476735) -- ************************************************************** -- copied from 3GPP 38.423 (XnAP) IEs -- note: choice-extension removed -- ************************************************************** GNB-ID-Choice ::= CHOICE { gnb-ID BIT STRING (SIZE(22..32)), … } -- H -- I -- J -- K -- L -- M -- ************************************************************** -- [New for E2AP v02.00] copied from 3GPP 36.413 (S1AP) IEs -- ************************************************************** MMEname ::= PrintableString (SIZE (1..150, …)) -- N ETSI ETSI TS 104 039 V4.0.0 (2024-10) 100 -- ************************************************************** -- copied from 3GPP 37.473 (W1AP) IEs -- ************************************************************** NGENB-DU-ID ::= INTEGER (0..68719476735) -- O -- P -- ************************************************************** -- copied from 3GPP 36.423 (X2AP) IEs -- ************************************************************** PLMN-Identity ::= OCTET STRING (SIZE(3)) -- Q -- R -- ************************************************************** -- Following IE defined in E2SM -- ************************************************************** RANfunctionDefinition ::= OCTET STRING RANfunctionID ::= INTEGER (0..4095) RANfunctionOID ::= PrintableString(SIZE(1..1000, …)) RANfunctionRevision ::= INTEGER (0..4095) -- ************************************************************** -- Following IE defined in E2SM -- ************************************************************** RICactionDefinition ::= OCTET STRING -- new in E2AP-v03.00 RICactionExecutionOrder ::= INTEGER (0..255, …) RICactionID ::= INTEGER (0..255) RICactionType ::= ENUMERATED{ report, insert, policy, … } -- ************************************************************** -- Following IE defined in E2SM -- ************************************************************** RICcallProcessID ::= OCTET STRING RICcontrolAckRequest ::= ENUMERATED{ noAck, ack, … } -- ************************************************************** -- Following IE defined in E2SM -- ************************************************************** RICcontrolHeader ::= OCTET STRING -- ************************************************************** -- Following IE defined in E2SM -- ************************************************************** RICcontrolMessage ::= OCTET STRING -- ************************************************************** -- Following IE defined in E2SM -- ************************************************************** RICcontrolOutcome ::= OCTET STRING -- ************************************************************** -- Following IE defined in E2SM -- ************************************************************** RICeventTriggerDefinition ::= OCTET STRING -- ************************************************************** -- Following IE defined in E2SM -- ************************************************************** RICindicationHeader ::= OCTET STRING ETSI ETSI TS 104 039 V4.0.0 (2024-10) 101 -- ************************************************************** -- Following IE defined in E2SM -- ************************************************************** RICindicationMessage ::= OCTET STRING RICindicationSN ::= INTEGER (0..65535) RICindicationType ::= ENUMERATED{ report, insert, … } RICrequestID ::= SEQUENCE { ricRequestorID INTEGER (0..65535), ricInstanceID INTEGER (0..65535), … } RICsubscriptionTime ::= OCTET STRING (SIZE(8)) RICsubsequentAction ::=SEQUENCE{ ricSubsequentActionType RICsubsequentActionType, ricTimeToWait RICtimeToWait, … } RICsubsequentActionType ::= ENUMERATED{ continue, wait, … } -- ************************************************************** -- Following IE defined in E2SM -- ************************************************************** RICqueryHeader ::= OCTET STRING -- ************************************************************** -- Following IE defined in E2SM -- ************************************************************** RICqueryDefinition ::= OCTET STRING -- ************************************************************** -- Following IE defined in E2SM -- ************************************************************** RICqueryOutcome ::= OCTET STRING RICtimeToWait ::= ENUMERATED{ w1ms, w2ms, w5ms, w10ms, w20ms, w30ms, w40ms, w50ms, w100ms, w200ms, w500ms, w1s, w2s, w5s, w10s, w20s, w60s, … } -- S -- T -- ************************************************************** -- copied from 3GPP 38.413 (NGAP) IEs -- ************************************************************** TimeToWait ::= ENUMERATED {v1s, v2s, v5s, v10s, v20s, v60s, …} ETSI ETSI TS 104 039 V4.0.0 (2024-10) 102 TNLinformation ::= SEQUENCE{ tnlAddress BIT STRING (SIZE(1..160, …)), tnlPort BIT STRING (SIZE(16)) OPTIONAL, … } TNLusage ::= ENUMERATED{ric-service, support-function, both, …} TransactionID ::= INTEGER (0..255, …) -- ************************************************************** -- copied from 3GPP 38.413 (NGAP) IEs -- ************************************************************** TypeOfError ::= ENUMERATED { not-understood, missing, … } -- U -- V -- W -- X -- Y -- Z END -- ASN1STOP |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.3.6 Common definitions | -- ASN1START -- ************************************************************** -- -- Common definitions -- Derived from 3GPP 38.413 (NGAP) -- -- ************************************************************** E2AP-CommonDataTypes { iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) oran(53148) e2(1) version2 (2) e2ap(1) e2ap-CommonDataTypes (3) } DEFINITIONS AUTOMATIC TAGS ::= BEGIN Criticality ::= ENUMERATED { reject, ignore, notify } Presence ::= ENUMERATED { optional, conditional, mandatory } ProcedureCode ::= INTEGER (0..255) ProtocolIE-ID ::= INTEGER (0..65535) TriggeringMessage ::= ENUMERATED { initiating-message, successful-outcome, unsuccessfull-outcome } END -- ASN1STOP |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.3.7 Constant definitions | -- ASN1START -- ************************************************************** -- -- Constant definitions -- -- ************************************************************** E2AP-Constants { iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) oran(53148) e2(1) version2 (2) e2ap(1) e2ap-Constants (4) } DEFINITIONS AUTOMATIC TAGS ::= ETSI ETSI TS 104 039 V4.0.0 (2024-10) 103 BEGIN IMPORTS ProcedureCode, ProtocolIE-ID FROM E2AP-CommonDataTypes; -- ************************************************************** -- -- Elementary Procedures -- -- ************************************************************** id-E2setup ProcedureCode ::= 1 id-ErrorIndication ProcedureCode ::= 2 id-Reset ProcedureCode ::= 3 id-RICcontrol ProcedureCode ::= 4 id-RICindication ProcedureCode ::= 5 id-RICserviceQuery ProcedureCode ::= 6 id-RICserviceUpdate ProcedureCode ::= 7 id-RICsubscription ProcedureCode ::= 8 id-RICsubscriptionDelete ProcedureCode ::= 9 id-E2nodeConfigurationUpdate ProcedureCode ::= 10 id-E2connectionUpdate ProcedureCode ::= 11 id-RICsubscriptionDeleteRequired ProcedureCode ::= 12 id-E2removal ProcedureCode ::= 13 id-RICsubscriptionModification ProcedureCode ::= 14 id-RICsubscriptionModificationRequired ProcedureCode ::= 15 id-RICquery ProcedureCode ::= 16 -- ************************************************************** -- -- Extension constants -- -- ************************************************************** maxProtocolIEs INTEGER ::= 65535 -- ************************************************************** -- -- Lists -- -- ************************************************************** maxnoofErrors INTEGER ::= 256 maxofE2nodeComponents INTEGER ::= 1024 maxofRANfunctionID INTEGER ::= 256 maxofRICactionID INTEGER ::= 16 maxofTNLA INTEGER ::= 32 maxofRICrequestID INTEGER ::= 1024 -- ************************************************************** -- -- IEs -- -- ************************************************************** id-Cause ProtocolIE-ID ::= 1 id-CriticalityDiagnostics ProtocolIE-ID ::= 2 id-GlobalE2node-ID ProtocolIE-ID ::= 3 id-GlobalRIC-ID ProtocolIE-ID ::= 4 id-RANfunctionID ProtocolIE-ID ::= 5 id-RANfunctionID-Item ProtocolIE-ID ::= 6 id-RANfunctionIEcause-Item ProtocolIE-ID ::= 7 id-RANfunction-Item ProtocolIE-ID ::= 8 id-RANfunctionsAccepted ProtocolIE-ID ::= 9 id-RANfunctionsAdded ProtocolIE-ID ::= 10 id-RANfunctionsDeleted ProtocolIE-ID ::= 11 id-RANfunctionsModified ProtocolIE-ID ::= 12 id-RANfunctionsRejected ProtocolIE-ID ::= 13 id-RICaction-Admitted-Item ProtocolIE-ID ::= 14 id-RICactionID ProtocolIE-ID ::= 15 id-RICaction-NotAdmitted-Item ProtocolIE-ID ::= 16 id-RICactions-Admitted ProtocolIE-ID ::= 17 id-RICactions-NotAdmitted ProtocolIE-ID ::= 18 id-RICaction-ToBeSetup-Item ProtocolIE-ID ::= 19 id-RICcallProcessID ProtocolIE-ID ::= 20 id-RICcontrolAckRequest ProtocolIE-ID ::= 21 id-RICcontrolHeader ProtocolIE-ID ::= 22 ETSI ETSI TS 104 039 V4.0.0 (2024-10) 104 id-RICcontrolMessage ProtocolIE-ID ::= 23 id-RICcontrolStatus ProtocolIE-ID ::= 24 id-RICindicationHeader ProtocolIE-ID ::= 25 id-RICindicationMessage ProtocolIE-ID ::= 26 id-RICindicationSN ProtocolIE-ID ::= 27 id-RICindicationType ProtocolIE-ID ::= 28 id-RICrequestID ProtocolIE-ID ::= 29 id-RICsubscriptionDetails ProtocolIE-ID ::= 30 id-TimeToWait ProtocolIE-ID ::= 31 id-RICcontrolOutcome ProtocolIE-ID ::= 32 id-E2nodeComponentConfigUpdate ProtocolIE-ID ::= 33 id-E2nodeComponentConfigUpdate-Item ProtocolIE-ID ::= 34 id-E2nodeComponentConfigUpdateAck ProtocolIE-ID ::= 35 id-E2nodeComponentConfigUpdateAck-Item ProtocolIE-ID ::= 36 id-E2connectionSetup ProtocolIE-ID ::= 39 id-E2connectionSetupFailed ProtocolIE-ID ::= 40 id-E2connectionSetupFailed-Item ProtocolIE-ID ::= 41 id-E2connectionFailed-Item ProtocolIE-ID ::= 42 id-E2connectionUpdate-Item ProtocolIE-ID ::= 43 id-E2connectionUpdateAdd ProtocolIE-ID ::= 44 id-E2connectionUpdateModify ProtocolIE-ID ::= 45 id-E2connectionUpdateRemove ProtocolIE-ID ::= 46 id-E2connectionUpdateRemove-Item ProtocolIE-ID ::= 47 id-TNLinformation ProtocolIE-ID ::= 48 id-TransactionID ProtocolIE-ID ::= 49 id-E2nodeComponentConfigAddition ProtocolIE-ID ::= 50 id-E2nodeComponentConfigAddition-Item ProtocolIE-ID ::= 51 id-E2nodeComponentConfigAdditionAck ProtocolIE-ID ::= 52 id-E2nodeComponentConfigAdditionAck-Item ProtocolIE-ID ::= 53 id-E2nodeComponentConfigRemoval ProtocolIE-ID ::= 54 id-E2nodeComponentConfigRemoval-Item ProtocolIE-ID ::= 55 id-E2nodeComponentConfigRemovalAck ProtocolIE-ID ::= 56 id-E2nodeComponentConfigRemovalAck-Item ProtocolIE-ID ::= 57 id-E2nodeTNLassociationRemoval ProtocolIE-ID ::= 58 id-E2nodeTNLassociationRemoval-Item ProtocolIE-ID ::= 59 id-RICsubscriptionToBeRemoved ProtocolIE-ID ::= 60 id-RICsubscription-withCause-Item ProtocolIE-ID ::= 61 id-RICsubscriptionStartTime ProtocolIE-ID ::= 62 id-RICsubscriptionEndTime ProtocolIE-ID ::= 63 id-RICeventTriggerDefinitionToBeModified ProtocolIE-ID ::= 64 id-RICactionsToBeRemovedForModification-List ProtocolIE-ID ::= 65 id-RICaction-ToBeRemovedForModification-Item ProtocolIE-ID ::= 66 id-RICactionsToBeModifiedForModification-List ProtocolIE-ID ::= 67 id-RICaction-ToBeModifiedForModification-Item ProtocolIE-ID ::= 68 id-RICactionsToBeAddedForModification-List ProtocolIE-ID ::= 69 id-RICaction-ToBeAddedForModification-Item ProtocolIE-ID ::= 70 id-RICactionsRemovedForModification-List ProtocolIE-ID ::= 71 id-RICaction-RemovedForModification-Item ProtocolIE-ID ::= 72 id-RICactionsFailedToBeRemovedForModification-List ProtocolIE-ID ::= 73 id-RICaction-FailedToBeRemovedForModification-Item ProtocolIE-ID ::= 74 id-RICactionsModifiedForModification-List ProtocolIE-ID ::= 75 id-RICaction-ModifiedForModification-Item ProtocolIE-ID ::= 76 id-RICactionsFailedToBeModifiedForModification-List ProtocolIE-ID ::= 77 id-RICaction-FailedToBeModifiedForModification-Item ProtocolIE-ID ::= 78 id-RICactionsAddedForModification-List ProtocolIE-ID ::= 79 id-RICaction-AddedForModification-Item ProtocolIE-ID ::= 80 id-RICactionsFailedToBeAddedForModification-List ProtocolIE-ID ::= 81 id-RICaction-FailedToBeAddedForModification-Item ProtocolIE-ID ::= 82 id-RICactionsRequiredToBeModified-List ProtocolIE-ID ::= 83 id-RICaction-RequiredToBeModified-Item ProtocolIE-ID ::= 84 id-RICactionsRequiredToBeRemoved-List ProtocolIE-ID ::= 85 id-RICaction-RequiredToBeRemoved-Item ProtocolIE-ID ::= 86 id-RICactionsConfirmedForModification-List ProtocolIE-ID ::= 87 id-RICaction-ConfirmedForModification-Item ProtocolIE-ID ::= 88 id-RICactionsRefusedToBeModified-List ProtocolIE-ID ::= 89 id-RICaction-RefusedToBeModified-Item ProtocolIE-ID ::= 90 id-RICactionsConfirmedForRemoval-List ProtocolIE-ID ::= 91 id-RICaction-ConfirmedForRemoval-Item ProtocolIE-ID ::= 92 id-RICactionsRefusedToBeRemoved-List ProtocolIE-ID ::= 93 id-RICaction-RefusedToBeRemoved-Item ProtocolIE-ID ::= 94 id-RICqueryHeader ProtocolIE-ID ::= 95 id-RICqueryDefinition ProtocolIE-ID ::= 96 id-RICqueryOutcome ProtocolIE-ID ::= 97 END -- ASN1STOP ETSI ETSI TS 104 039 V4.0.0 (2024-10) 105 |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.3.8 Container definitions | -- ASN1START -- ************************************************************** -- -- Container definitions -- -- derived from 3GPP 38.413 (NGAP) -- ************************************************************** E2AP-Containers { iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) oran(53148) e2(1) version2 (2) e2ap(1) e2ap-Containers (5) } DEFINITIONS AUTOMATIC TAGS ::= BEGIN -- ************************************************************** -- -- IE parameter types from other modules. -- -- ************************************************************** IMPORTS Criticality, Presence, ProtocolIE-ID FROM E2AP-CommonDataTypes maxProtocolIEs FROM E2AP-Constants; -- ************************************************************** -- -- Class Definition for Protocol IEs -- -- ************************************************************** E2AP-PROTOCOL-IES ::= CLASS { &id ProtocolIE-ID UNIQUE, &criticality Criticality, &Value, &presence Presence } WITH SYNTAX { ID &id CRITICALITY &criticality TYPE &Value PRESENCE &presence } -- ************************************************************** -- -- Class Definition for Protocol IEs -- -- ************************************************************** E2AP-PROTOCOL-IES-PAIR ::= CLASS { &id ProtocolIE-ID UNIQUE, &firstCriticality Criticality, &FirstValue, &secondCriticality Criticality, &SecondValue, &presence Presence } WITH SYNTAX { ID &id FIRST CRITICALITY &firstCriticality FIRST TYPE &FirstValue SECOND CRITICALITY &secondCriticality SECOND TYPE &SecondValue PRESENCE &presence } ETSI ETSI TS 104 039 V4.0.0 (2024-10) 106 -- ************************************************************** -- -- Container for Protocol IEs -- -- ************************************************************** ProtocolIE-Container {E2AP-PROTOCOL-IES : IEsSetParam} ::= SEQUENCE (SIZE (0..maxProtocolIEs)) OF ProtocolIE-Field {{IEsSetParam}} ProtocolIE-SingleContainer {E2AP-PROTOCOL-IES : IEsSetParam} ::= ProtocolIE-Field {{IEsSetParam}} ProtocolIE-Field {E2AP-PROTOCOL-IES : IEsSetParam} ::= SEQUENCE { id E2AP-PROTOCOL-IES.&id ({IEsSetParam}), criticality E2AP-PROTOCOL-IES.&criticality ({IEsSetParam}{@id}), value E2AP-PROTOCOL-IES.&Value ({IEsSetParam}{@id}) } -- ************************************************************** -- -- Container for Protocol IE Pairs -- -- ************************************************************** ProtocolIE-ContainerPair {E2AP-PROTOCOL-IES-PAIR : IEsSetParam} ::= SEQUENCE (SIZE (0..maxProtocolIEs)) OF ProtocolIE-FieldPair {{IEsSetParam}} ProtocolIE-FieldPair {E2AP-PROTOCOL-IES-PAIR : IEsSetParam} ::= SEQUENCE { id E2AP-PROTOCOL-IES-PAIR.&id ({IEsSetParam}), firstCriticality E2AP-PROTOCOL-IES-PAIR.&firstCriticality ({IEsSetParam}{@id}), firstValue E2AP-PROTOCOL-IES-PAIR.&FirstValue ({IEsSetParam}{@id}), secondCriticality E2AP-PROTOCOL-IES-PAIR.&secondCriticality ({IEsSetParam}{@id}), secondValue E2AP-PROTOCOL-IES-PAIR.&SecondValue ({IEsSetParam}{@id}) } -- ************************************************************** -- -- Container Lists for Protocol IE Containers -- -- ************************************************************** ProtocolIE-ContainerList {INTEGER : lowerBound, INTEGER : upperBound, E2AP-PROTOCOL-IES : IEsSetParam} ::= SEQUENCE (SIZE (lowerBound..upperBound)) OF ProtocolIE-SingleContainer {{IEsSetParam}} ProtocolIE-ContainerPairList {INTEGER : lowerBound, INTEGER : upperBound, E2AP-PROTOCOL-IES-PAIR : IEsSetParam} ::= SEQUENCE (SIZE (lowerBound..upperBound)) OF ProtocolIE-ContainerPair {{IEsSetParam}} END -- ASN1STOP |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.4 Message transfer syntax | E2AP shall use the ASN.1 Basic Packed Encoding Rules (BASIC-PER) Aligned Variant as transfer syntax, as specified in Recommendation ITU-T X.691 [15]. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 9.5 Timers | The following Timers are defined for use over the E2 interface in Near-RT RIC and E2 Node. TRICEVENTcreate - Specifies the maximum time for the RIC Subscription procedure in the Near-RT RIC. ETSI ETSI TS 104 039 V4.0.0 (2024-10) 107 TRICEVENTdelete - Specifies the maximum time for the RIC Subscription Deletion procedure in the Near-RT RIC. TRICEVENTmodify - Specifies the maximum time for the RIC Subscription Modification procedure in the Near-RT RIC. TRICcontrol - Specifies the maximum time for the RIC Control procedure in the Near-RT RIC. TRICquery - Specifies the maximum time for the RIC Query procedure in the Near-RT RIC. 10 Handling of Unknown, Unforeseen and Erroneous Protocol Data Clause 10 of ETSI TS 136 413 [24] is applicable for the purposes of the present document. ETSI ETSI TS 104 039 V4.0.0 (2024-10) 108 Annex A (informative): Change history Date Version Information about changes February 2020 01.00 Initial version October 2020 01.01 Editorial and functional corrections October 2021 02.00 New features: RIC Subscription Delete, TNLA Removal. Corrections to all RIC service procedures. Change to ASN.1 version March 2022 02.01 New feature: E2 removal. Editorial and functional corrections July 2022 02.02 Clarification to RIC Service Update, RIC Control. Editorial and functional corrections October 2022 02.03 Editorial and functional corrections March 2023 03.00 New features: RIC Subscription Modification, RIC Query. Clarifications to RIC Subscription. Editorial and functional corrections June 2023 03.01 Alignment of O-RAN Drafting Rules (ODR) in preparation for ETSI PAS submission October 2023 04.00 Clarification on E2 Node components configuration. Editorial and functional corrections ETSI ETSI TS 104 039 V4.0.0 (2024-10) 109 History Document history V4.0.0 October 2024 Publication |
6f4f3fe4c8f381f9f44b5940e215757c | 105 174-1 | 1 Scope | The present document gives an overview of this multi-part deliverable covering energy management and broadband deployment. Clause 2 and clause 3 contain references, definitions and abbreviations which relate to this part; similar information will be included in the corresponding clauses of the other parts, thus ensuring that each document can be used on a "stand-alone" basis. Clause 6 describes the network sub-systems applicable to broadband deployment and their interconnections. Clause 7 considers the measures which may be taken to optimize energy management of the end-to-end network and introduces the concept of key performance indicators (KPI) to enable consistent monitoring of energy management for each of the network sub-systems described in clause 5. Clause 8 contains details of the subsequent parts and sub-parts of this multi-part deliverable which, for each of the network sub-systems described in clause 5: • identify the standardization bodies working on the design and installation of the cabling within and between the network sub-systems and the relevant interfaces; • provide a more strategic analysis of energy consumption trends, in a range of different broadband deployment scenarios; • outline further work needed to ensure the improvement of energy efficiency in communication networks. This will enable the proper implementation of services, applications and content using an energy efficient infrastructure, though it is not the goal of this multi-part deliverable to provide detailed standardized solutions for the power distribution systems or physical design of data centres. |
6f4f3fe4c8f381f9f44b5940e215757c | 105 174-1 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. |
6f4f3fe4c8f381f9f44b5940e215757c | 105 174-1 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] Void. [2] CENELEC EN 50173-2: "Information technology - Generic cabling systems - Part 2: Office premises". [3] CENELEC EN 50173-3: "Information technology - Generic cabling systems - Part 3: Industrial premises". [4] CENELEC EN 50173-4: "Information technology - Generic cabling systems - Part 4: Homes". [5] CENELEC EN 50173-5: "Information technology - Generic cabling systems - Part 5: Data centres". [6] CENELEC TR 50173-99-2: "Information technology - Implementation of BCT applications using cabling in accordance with EN 50173-4". ETSI ETSI TS 105 174-1 V1.2.1 (2014-09) 7 [7] CENELEC EN 50174-1: "Information technology - Cabling installation - Part 1: Installation specification and quality assurance". [8] CENELEC EN 50174-2: "Information technology - Cabling installation - Part 2: Installation planning and practices inside buildings". [9] CENELEC EN 50174-3: "Information technology - Cabling installation - Part 3: Installation planning and practices outside buildings". [10] CENELEC EN 60728 series: "Cable networks for television signals, sound signals and interactive services". [11] Void. [12] Void. [13] Recommendation ITU-T I.113: "Vocabulary of terms for broadband aspects of ISDN". [14] CENELEC EN 50600 series: "Information technology - Data centre facilities and infrastructures". [15] ETSI ES 205 200-1: "Access, Terminals, Transmission and Multiplexing (ATTM); Energy management; Global KPIs; Operational infrastructures; Part 1: General requirements". [16] ETSI ES 205 200-2-1: "Access, Terminals, Transmission and Multiplexing (ATTM); Energy management; Global KPIs; Operational infrastructures; Part 2: Specific requirements; Sub-part 1: Data centres". [17] ETSI GS OEU 001: "Operational energy Efficiency for Users (OEU); Technical Global KPIs for Data Centres". [18] ETSI GS OEU 008: "Operational energy Efficiency for Users (OEU); Global KPI for Information and Communication Technology Nodes". |
6f4f3fe4c8f381f9f44b5940e215757c | 105 174-1 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] Directive 1999/5/EC of the European Parliament and of the Council of 9 March 1999 on radio equipment and telecommunications terminal equipment and the mutual recognition of their conformity (R&TTE Directive). [i.2] Directive 2002/22/EC of the European Parliament and of the Council of 7 March 2002 on universal service and users' rights relating to electronic communications networks and services (Universal Service Directive). [i.3] ETSI TS 102 973: "Access Terminals, Transmission and Multiplexing (ATTM); Network Termination (NT) in Next Generation Network architectures". [i.4] ETSI EG 201 730 (all parts): "Terminals' access to Public Telecommunications Networks; Application of the Directive 1999/5/EC (R&TTE), article 4.2; Guidelines for the publication of interface specifications". [i.5] ETSI EG 202 306: "Transmission and Multiplexing (TM); Access networks for residential customers". [i.6] ETSI TS 105 174-2: "Access, Terminals, Transmission and Multiplexing (ATTM); Broadband Deployment and Energy Management; Part 2: Operator sites and data centres". [i.7] Void. [i.8] ETSI TS 105 174-3: "Access, Terminals, Transmission and Multiplexing (ATTM); Broadband Deployment and Energy Management; Part 3: Core, regional metropolitan networks". ETSI ETSI TS 105 174-1 V1.2.1 (2014-09) 8 [i.9] ETSI TS 105 174-4-1: "Access, Terminals, Transmission and Multiplexing (ATTM); Broadband Deployment and Energy Management; Part 4: Access Networks; Sub-part 1: Fixed access networks (excluding cable)". [i.10] ETSI TS 105 174-4-2: "Access, Terminals, Transmission and Multiplexing (ATTM); Broadband Deployment and Energy Management; Part 4: Access Networks; Sub-part 2: Mobile access networks". [i.11] ETSI TS 105 174-5-1: "Access, Terminals, Transmission and Multiplexing (ATTM); Broadband Deployment and Energy Management; Part 5: Customer network infrastructures; Sub-part 1: Homes (single-tenant)". [i.12] ETSI TS 105 174-5-2: "Access, Terminals, Transmission and Multiplexing (ATTM); Broadband Deployment and Energy Management; Part 5: Customer network infrastructures; Sub-part 2: Office premises (single-tenant)". [i.13] ETSI TS 105 174-5-3: "Access, Terminals, Transmission and Multiplexing (ATTM); Broadband Deployment and Energy Management; Part 5: Customer network infrastructures; Sub-part 3: Industrial premises (single-tenant)". [i.14] ETSI TS 105 174-5-4: "Access, Terminals, Transmission and Multiplexing (ATTM); Broadband Deployment and Energy Management; Part 5: Customer network infrastructures; Sub-part 4: Multi-tenant premises (residential and commercial)". [i.15] ETSI TR 105 174-6: "CABLE; Broadband Deployment and Energy Management; Part 6: Cable Access Networks". [i.16] European Commission: "DG-JRC Code of Conduct on Data Centres Energy Efficiency". [i.17] European Commission: "DG-JRC Code of Conduct on Energy Consumption of Broadband Equipment". [i.18] CENELEC EN 61784 series: "Industrial communication networks - Profiles". [i.19] CENELEC EN 61918: "Industrial communication networks - Installation of communication networks in industrial premises". [i.20] ETSI ES 205 200-2-2: "Access, Terminals, Transmission and Multiplexing (ATTM); Energy management; Global KPIs; Operational infrastructures: Fixed (excluding cable) access networks". [i.21] ETSI ES 205 200-2-3: "Access, Terminals, Transmission and Multiplexing (ATTM); Energy management; Global KPIs; Operational infrastructures; Part 2: Specific requirements; Sub-part 3: Mobile access networks". |
6f4f3fe4c8f381f9f44b5940e215757c | 105 174-1 | 3 Definitions and abbreviations | |
6f4f3fe4c8f381f9f44b5940e215757c | 105 174-1 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: access network: functional elements (that is equipment and infrastructure) that enable communication between the core network and a customer network core network: functional elements (that is equipment and infrastructure) that enable communication between operator sites and/or network data centres customer network: functional elements (that is equipment and infrastructure) that enable communication between an NTP or ENTI, as appropriate, and one or more attached terminal equipments distribution infrastructure: sub-part of the access network comprising the functional elements that enable communication between the last cabinet and a customer network ETSI ETSI TS 105 174-1 V1.2.1 (2014-09) 9 External Network Test Interface (ENTI): point in or near the customer premises (inside or outside the customer network) accessible to the network operator for testing purposes Network Termination Point (NTP): physical point(s) at which a subscriber is provided with access to the operator network (this may be co-located with an external network test interface) NOTE: The schematic of figure 1 helps understanding many of the definitions related with relevant points and areas of the installation. operator site: premises accommodating network telecommunications equipment providing direct connection to the core and access networks and which may also accommodate information technology equipment transport infrastructure: sub-part of the access network comprising the functional elements that enable communication between the core network and the last cabinet and a customer network |
6f4f3fe4c8f381f9f44b5940e215757c | 105 174-1 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ATTM Access, Terminals, Transmission and Multiplexing BEF Building Entrance Facility CENELEC European Committee for Electrotechnical Standardization CGIC Co-ordination Group on Installations and Cabling CLC European Electrotechnical Standardisation Committee (CENELEC / Comité Européen de Normalisation ELECtrotechnique) CP Customer Premises DC (Network) Data Centre DG-JRC European Commission Direction General Joint Research Centre ENTI External Network Test Interface FTTB Fibre To The Building FTTC Fibre To The Cabinet FTTH Fibre To The Home FTTx Fibre To The (various) NOTE: See FTTB, FTTC and FTTH. HEF Home Entrance Facility HFC Hybrid Fibre Coaxial HV High Voltage ICT Information Communications Technology ISDN Integrated Service Digital Network KPI Key Performance Indicator LC Last Cabinet NOTE: Before the customer premises in the access network. NGN Next Generation Networks NTP Network Termination Point OS Operator Site POTS Plain Old Telephone Service TxRx Transceiver equipment |
6f4f3fe4c8f381f9f44b5940e215757c | 105 174-1 | 4 Generalities | In order to monitor the implementation and operation of energy management of deployed broadband, certain documents will also focus on the possible consequences of standardization of installations, cabling techniques and equipment. In particular, the study will investigate possibilities and suggest solutions for development of processes for optimization in installation techniques and energy consumption. Operational monitoring of energy management will be done by means of Objective and Global Key Performance Indicators (KPIs). These KPIs are defined in ES 205 200 Series [15], [16], [i.20] and [i.21] and supported by several Position Papers (e.g. GS OEU 001 [17] and GS OEU 008 [18]) from Industrial Specification Group Operational energy Efficiency for Users (ISG OEU). ETSI ETSI TS 105 174-1 V1.2.1 (2014-09) 10 |
6f4f3fe4c8f381f9f44b5940e215757c | 105 174-1 | 5 Broadband deployment | Broadband access equipment is defined by its incorporation of a transmission technology capable of providing more than 2 048 kbit/s (Recommendation ITU-T I.113 [13]) full-rate capacity in at least one direction. On this basis, ISDN is not considered to be a broadband technology and is not addressed in the present document. |
6f4f3fe4c8f381f9f44b5940e215757c | 105 174-1 | 6 Network sub-systems of broadband deployment | |
6f4f3fe4c8f381f9f44b5940e215757c | 105 174-1 | 6.1 General | This clause will identify and explain the elements of the network sub-systems employed in broadband deployment. |
6f4f3fe4c8f381f9f44b5940e215757c | 105 174-1 | 6.2 Network sub-systems | Figure 1 is a technology agnostic diagram depicting a segment of a broadband network showing the interconnection of network data centres, operator sites and customer premises installations. In principle, every operator network can contain any number of each of these elements and may be connected to any number of other operator networks. Core network 1 OS DC DC DC Core network 2 CP CP CP CP CP CP OS OS OS OS OS Customer premises connected to two operator sites for resilience Customer premises connected to two operator networks Access network 1 Access network 2 Figure 1: Network sub-systems of broadband deployment |
6f4f3fe4c8f381f9f44b5940e215757c | 105 174-1 | 6.2.1 Data centre | A network data centre is the network sub-system that supports one or more operator core networks. Its functions include the storage, processing and dissemination of data as required to fulfil customer expectations, the hosting of the necessary applications, content hosting, etc. In this context, data centres do not include sites containing only servers and their related hardware that are used required solely for administrative functions such as customer management functions, billing, etc. ETSI ETSI TS 105 174-1 V1.2.1 (2014-09) 11 To enable their functionality, all data centres have to be connected to at least one core network operator site. For reasons of network resilience, data centres will invariably be connected to more than one operator site and to several other data centres. Data centres may serve core networks operated by several network operators, thus enabling traffic between customers of different network operators. |
6f4f3fe4c8f381f9f44b5940e215757c | 105 174-1 | 6.2.2 Operator site | An operator site is the network sub-system in the core network that enables the connectivity between network data centres and customer premises over which the required services can be delivered, using the access network. In turn, operator sites also enable indirect connectivity between customer premises. Operator sites will almost invariably serve many thousands of customer connections. Each customer connection may be comprised of multiple communication paths and serve a variety of applications. |
6f4f3fe4c8f381f9f44b5940e215757c | 105 174-1 | 6.2.3 Customer premises | Customer premises are connected to at least one operator site in the core network and contain the terminal equipment required to provide those services to which the customer has chosen to subscribe, together with the local network equipment necessary to distribute those services amongst the customers' families or employees at that location. Customer premises may be connected to two or more operator sites on one or more core networks in order to provide the desired service diversity. However, the domestic customer premises (that is, homes) will be connected to fewer operator sites as convergence allows multi-service packages to be delivered over a common infrastructure. The connection of customer premises to multiple operator sites will be restricted to businesses where the connections provided are intended to a contracted level of service resilience. This highlights the distinction between the need of high speed data provision and the requirement for service availability: the demand for high speed data in homes is expected to increase but the criticality of that provision is low since much of the increases are related to entertainment services. In comparison, businesses may demand high levels of service availability, independent of the amount of data transmitted. |
6f4f3fe4c8f381f9f44b5940e215757c | 105 174-1 | 6.2.4 Primary power requirements | Both data centres and operator sites will always be critically dependent upon an adequate supply of primary power both for operation of the network equipment and usually for providing environmental control (for example, temperature and humidity) and housekeeping services (for example, lighting and domestic services) for the equipment accommodation. Power is typically provided by one or more feeds from a public supply supplemented almost invariably by on-site generation equipment in case of supply failure. These sites also require some form of uninterruptible power supply, at least sufficient to cover the generator start-up period, in the event of failure of the public supply. Energy from the HV supply invariably needs conversion to a lower voltage for connection to the equipment; this conversion will always incur some losses. Customer premises are also dependent on external power in all but the simplest of installations. In the majority of cases this dependency will be business critical, thus needing similar provisions as those at the main network sites, albeit on a smaller scale. In considering overall energy management, the losses incurred in the power conversion equipment for both public and on-site supplies shall be taken into account. |
6f4f3fe4c8f381f9f44b5940e215757c | 105 174-1 | 6.3 Network sites | Figure 2 shows the content and external connectivity of the data centres and operator sites in a little more detail though this diagram is intended only to illustrate the types of equipment employed, not its internal connectivity. For the purposes of the present study, the boxes marked "TxRx" will be regarded as part of the access or core network, as appropriate and their power requirements included in the assessments for those networks. ETSI ETSI TS 105 174-1 V1.2.1 (2014-09) 12 Servers Arrays Libraries Switches Routers Switches Routers TxRx TxRx Switches Routers TxRx TxRx TxRx Core network Core network Access network DC OS Servers Servers Figure 2: Simplified schematic of operator data centres and operator sites |
6f4f3fe4c8f381f9f44b5940e215757c | 105 174-1 | 6.4 Customer premises | Figure 3 shows the types of premises served by the majority of access networks. TxRx OS LC Customer Data Centre Office premises Industrial premises Enterprise Data Centre Multi-tenant premises Multi-tenant premises Offices Homes Single-tenant premises Access network Customer network NOTE: an ENTI for an operator network may be connected to more than one NTP, within the premises, each of which is service-specific HEF NTP ENTI Home BEF NTP ENTI BEF NTP ENTI BEF NTP ENTI Customer Data Centre BEF Single-tenant homes NTP Home HEF ENTI NTP Home HEF ENTI HEF NTP Home ENTI NTP Home HEF Figure 3: Customer premises served by the access network Customer premises can be defined as being single-tenant or multi-tenant. Single-tenant premises include offices premises and industrial premises that will usually be equipped with their own customer premises distribution network served by one or more data centres within the premises connected to at least one operator network via one or more Network Termination Points (NTPs). It should be noted that an ENTI for each of the operator networks may be connected to more than one, service-specific NTP within the premises. Single-tenant premises also include dedicated customer data centres that have limited, or no, other distribution networks. ETSI ETSI TS 105 174-1 V1.2.1 (2014-09) 13 Multi-tenant premises can house homes and/or offices and in both cases can take two forms: a) one or more NTPs serve(s) each home or office within which there is a customer network; b) one or more NTPs serve(s) connects to a customer data centre from which services are distributed to each of the homes and/or offices via a third party - normally acting on behalf of the building owner. In such cases the customer network includes both the network within the individual homes and/or offices together with the building distribution network. As detailed in clause 6.2.3 a given customer network may be serviced by a number of NTPs providing broadband delivery from a number of operator networks, thus providing resilience in the case of failure of one of the access networks. The reasons for this may be commercial or strategic (to provide resilience in the case of access network failure). |
6f4f3fe4c8f381f9f44b5940e215757c | 105 174-1 | 6.5 Fixed Access networks | |
6f4f3fe4c8f381f9f44b5940e215757c | 105 174-1 | 6.5.1 Schematic | Figure 4 shows options for access network implementations based on FTTx. NOTE: an ENTI for an operator network may be connected to more than one NTP, within the premises, each of which is service-specific FTTH Transport Distribution Access network Customer network Access network (internal) Access network (external) NTP ENTI NTP ENTI BEF Last cabinet NOTE 1: dotted line indicates non-optical fibre media , that is metallic (balanced or coaxial) cabling or wireless transmission NTP ENTI Customer network Access network Access network (internal) Access network (external) Transport Distribution FTTC1 FTTB1 ENTI HEF NTP HEF BEF HEF Last cabinet Operator site Operator site Multi-tenant premises Single tenant premises Large single tenant premises Multi-tenant premises Figure 4: FTTx access network implementations |
6f4f3fe4c8f381f9f44b5940e215757c | 105 174-1 | 6.5.2 Infrastructures and technologies | TS 105 174-4-1 [i.9] describes access networks using a variety of transmission media. Figure 5 shows the general access network topologies reviewed in TS 105 174-4-1 [i.9]. ETSI ETSI TS 105 174-1 V1.2.1 (2014-09) 14 The transmission media addressed comprise balanced and coaxial metallic cabling, optical fibre cabling and wireless solutions. TS 105 174-4-1 [i.9] covers "point-to-point" networks in all transmission media. Where the access network is divided at the last cabinet between transport and distribution infrastructures, the transport infrastructure is implemented using optical fibre and the distribution infrastructure is: • all supported media for point-to-point systems; • optical fibre only for point-to-point (virtual) systems; • optical fibre only for point-to-multi-point (passive) systems; • optical fibre only for point-to-multi-point (virtual and passive) systems. Last cabinet TxRx TxRx TxRx TxRx TxRx WDM splitter WDM splitter TxRx TxRx TxRx TxRx TxRx TxRx TxRx Passive splitter Operator site Point to point access network Point to point (virtual) (passive at LC) Point to multi-point access network (passive at LC) TxRx TxRx TxRx TxRx TxRx Point to point (transport) and Point to point (distribution) (active at LC) Optical fibre Optical fibre Any medium Any medium Figure 5: Access network technology options |
6f4f3fe4c8f381f9f44b5940e215757c | 105 174-1 | 6.6 Mobile access networks | This clause will be updated as soon as TS 105 174-4-2 will be available [i.10]. |
6f4f3fe4c8f381f9f44b5940e215757c | 105 174-1 | 7 Energy management | Broadband provision is an enabling technology capable of supporting a reduction of global energy consumption (for example, by providing facilities such as home working and video conferencing to reduce travel demands) and use of renewable energy and re-use of energy. For this reason, it may not be the case that the total energy consumption of broadband networks will be reduced, though the application of effective energy management measures will minimize any increases due to predicted service evolution. For the purposes of the present document, "energy management" relates to the operational energy management of broadband network sub-systems described in clause 5. ETSI ETSI TS 105 174-1 V1.2.1 (2014-09) 15 It is not the intention of the present document to take into consideration the following aspects of the broadband network sub-systems: • comparative costs and environmental impacts of different energy sources; • resources used to construct the sub-systems. Possible energy management gains from the design of new network sub-systems are expected to differ from, and generally offer greater outcomes than, those that may be applied to existing infrastructures. The scale of energy management gains and the measurable impact also varies between the different network sub- systems. The outcomes of energy management measures at network sites as identified in TS 105 174-2 [i.6] are expected to be substantial but apply in only a relatively small number of locations and may prove vital where availability of power is restricted. In comparison, the saving within individual access and customer networks will be very much smaller, their totality may very well outweigh the energy management gains elsewhere due to the very large number of customers, thus justifying their consideration and implementation. The communities served by customer networks are the recipients of the "energy management enabling" technologies provided by broadband deployment and the relevant parts of this multi-part deliverable serve to indicate strategies/approaches that maximize the opportunities presented. Furthermore, it is the customer rather than the operator that funds the energy costs within customer networks. Potential reductions in energy consumption may well be identifiable in design terms but they are generally not individually quantifiable due to the diversity of customer networks. 8 Overview of the multi-part deliverable: Energy management and broadband deployment |
6f4f3fe4c8f381f9f44b5940e215757c | 105 174-1 | 8.1 Part 1: Overview, common and generic aspects | The present document, is intended to provide and maintain an overview of all the other parts of the series to facilitate the correct and consistent application of the complete multi-part deliverable. NOTE 1: The following clauses give an overview of the different parts and sub-parts of this multi-part deliverable. For detailed information each one of the sub-parts should be consulted. NOTE 2: New parts and sub-parts may be created in the future and any changes will be reflected in the present document. In particular, the extension of the set of documents to cover new areas or specific sub-areas might be useful but needs additional collaboration from an extended base of experts. This multi-part deliverable focuses on the best practice for cabling and installations and transmission implementation independently from the ownership of these infrastructures or systems. Should the ownership of the installations or equipment be a matter for analysis it is strongly recommended to take in consideration TS 102 973 [i.3] and the EG 201 730 [i.4] series of documents which study the regulatory implications associated with the definition of the network termination (NT/NTP) for different technologies. NOTE 3: Requirements for, and the definition of, NTP are specified in Universal Service (2002/22/EC [i.2]) and R&TTE (1999/5/EC [i.1]) Directives. See also the series of EG 201 730 [i.4] offering guidance on the requirements applicable to the NTP. |
6f4f3fe4c8f381f9f44b5940e215757c | 105 174-1 | 8.2 Part 2: Network sites | The energy management of network sites (e.g. data centre, operator sites) is discussed in TS 105 174-2 [i.6] which: • reviews the opportunity for energy management gains within operator sites in the following areas: - selection and use of network telecommunications equipment and information technology equipment; - environmental control (including temperature, humidity and lighting); ETSI ETSI TS 105 174-1 V1.2.1 (2014-09) 16 - support infrastructures (for example, network telecommunications cabling and information technology cabling); - power distribution; • states requirements and recommendations for conformance to TS 105 174-2 [i.6]. TS 105 174-2 [i.6] makes reference to: • contributions made by governmental agencies (including the European Commission, DG-JRC Code of Conduct on Data Centres Energy Management [i.16] and [i.17]); • the activities and publications of major industry associations and fora; • standardization available and in development in ETSI, CENELEC, IEC, and ITU-T. The significance of the different standards (and current work) is discussed and proposals for any useful new standardization are made where relevant. TS 105 174-2 [i.6] also makes reference to standardization available and in development in ETSI, CENELEC, IEC, and ITU-T. The significance of the different standards (and current work) is discussed and proposals for any useful new standardization are made where relevant. Standards for the design and specification of information technology cabling that may be applied within network sites have been developed by CENELEC TC215 (EN 50173-2 [2], EN 50173-5 [5]). Standards for site design and the installation of cabling within network sites have been developed by CENELEC TC215 (EN 50600 series [14], EN 50174-1 [7], EN 50174-2 [8] clauses 8 to 11, EN 50174-3 [9]). |
6f4f3fe4c8f381f9f44b5940e215757c | 105 174-1 | 8.3 Part 3: Core networks | The energy management of core networks is discussed in TS 105 174-3 [i.8] which: • reviews the opportunity for energy management gains within the core networks in the selection and use of network telecommunications equipment; • states requirements and recommendations for conformance to TS 105 174-3 [i.8]. TS 105 174-3 [i.8] also makes reference to standardization available and in development in ETSI, CENELEC, IEC, and ITU-T. The significance of the different standards (and current work) is discussed and proposals for any useful new standardization are made where relevant. |
6f4f3fe4c8f381f9f44b5940e215757c | 105 174-1 | 8.4 Part 4: Access networks | |
6f4f3fe4c8f381f9f44b5940e215757c | 105 174-1 | 8.4.1 Overview | The energy management of access networks is discussed in TS 105 174-4 (all sub-parts) [i.9] and [i.10] which: • reviews the opportunity for energy management gains within the access networks in the selection and use of network telecommunications equipment and its accommodation within the access network; • states requirements and recommendations for conformance to TS 105 174-4 (all sub-parts) [i.9] and [i.10]. TS 105 174-4 (all sub-parts) [i.9] and [i.10] also makes reference to standardization available and in development in ETSI, CENELEC, IEC, and ITU-T. The significance of the different standards (and current work) is discussed and proposals for any useful new standardization are made where relevant. ETSI ETSI TS 105 174-1 V1.2.1 (2014-09) 17 |
6f4f3fe4c8f381f9f44b5940e215757c | 105 174-1 | 8.4.2 Sub-part 1: Fixed access networks (excluding cable) | A previous study by ETSI, published as EG 202 306 [i.5] covering a wide range of access technologies also contains some useful and relevant information but is thought not to be sufficiently up to date in some areas. A variety of access network technologies and topologies are addressed as described in clause 6.5.2. Certain existing operator networks, both metallic and Hybrid Fibre Coaxial (HFC), have the potential to support broadband services in the access network. As a result some historical installations may remain in service but limitations in their capability may have a detrimental impact the availability of some types of services. It should also be considered that although new technologies may better fit users' needs, operators may be obliged to support some level of POTS or ISDN service using legacy installations. These infrastructures will be studied only as far, and in as much depth, as is relevant to the present work. |
6f4f3fe4c8f381f9f44b5940e215757c | 105 174-1 | 8.4.3 Sub-part 2: Mobile access networks | Sub-part 2 details will be provided as soon as the TS 105 174-4-2 [i.10] will be available. |
6f4f3fe4c8f381f9f44b5940e215757c | 105 174-1 | 8.5 Part 5: Customer network infrastructures | |
6f4f3fe4c8f381f9f44b5940e215757c | 105 174-1 | 8.5.1 Overview | TS 105 174-5 sub-parts 1 [i.11] to 4 [i.14] review the opportunity for energy management gains within customer networks, supported by the access networks of TS 105 174-4 (all sub-parts) [i.9] and [i.10], in the selection of network terminal equipment and its accommodation within the customer premises. TS 105 174-5 sub-parts 1 [i.11] to 4 [i.14] makes reference to: • contributions made by governmental agencies; • standardization available and in development in ETSI, CENELEC, IEC, and ITU-T. The significance of the different standards (and current work) is discussed and proposals for any useful new standardization are made where relevant. |
6f4f3fe4c8f381f9f44b5940e215757c | 105 174-1 | 8.5.2 Sub-part 1: Homes (single-tenant) | Standards for the design and specification of customer network cabling within homes are developed by: • generic cabling: TC215 (EN 50173-4 [4], CLC TR 50173-99-2 [6]); • home and Building Electronic Systems: TC205; • cable networks for television signals, sound signals and interactive services: TC209 (EN 60728 series [10]). Standards for the planning and installation of customer network cabling in support of all the above design standards activity are developed by CENELEC TC215 (EN 50174-1 [7], EN 50174-2 [8], clause 11) and TC209 (EN 60728 series [10]). |
6f4f3fe4c8f381f9f44b5940e215757c | 105 174-1 | 8.5.3 Sub-part 2: Office premises (single-tenant) | Standards for the design and specification of customer network cabling within office premises are developed by CENELEC TC215 (EN 50173-2 [2]). Standards for the installation of customer network cabling in support of the above design standards activity are developed by CENELEC TC215 (EN 50174-1 [7], EN 50174-2 [8], clause 8, EN 50174-3 [9]). ETSI ETSI TS 105 174-1 V1.2.1 (2014-09) 18 |
6f4f3fe4c8f381f9f44b5940e215757c | 105 174-1 | 8.5.4 Sub-part 3: Industrial premises (single-tenant) | Standards for the design and specification of customer network cabling within industrial premises are developed by a number of different Technical Committees within CENELEC: • generic cabling: TC215 (EN 50173-3 [3]); • industrial automation: SC65CX (EN 61784 series [i.18]). Standards for the installation of customer network cabling in support of the above design standards activity are developed by CENELEC TC215 (EN 50174-1 [7], EN 50174-2 [8], clause 9, EN 50174-3 [9]) and SC65CX (EN 61918 [i.19]) respectively. |
6f4f3fe4c8f381f9f44b5940e215757c | 105 174-1 | 8.5.5 Sub-part 4: Multi-tenant premises (residential and commercial) | Standards for the design and specification of customer network cabling within multi-tenant premises are developed by CENELEC TC215 (see clauses 7.5.2 and 7.5.3). Standards for the installation of customer network cabling in support of the above design standards activity are developed by CENELEC TC215 (see clauses 7.5.2 and 7.5.3). |
6f4f3fe4c8f381f9f44b5940e215757c | 105 174-1 | 8.6 Part 6: Cable networks | The energy management of cable networks is discussed in TR 105 174-6 [i.15] which: • reviews the opportunity for energy management gains within the Legacy HFC networks in the selection and use of network equipment; • states requirements and recommendations for conformance to TR 105 174-6 [i.15]. TR 105 174-6 [i.15] also makes reference to standardization available and in development in ETSI, CENELEC, IEC, and ITU-T. The significance of the different standards (and current work) is discussed and proposals for any useful new standardization are made where relevant. |
6f4f3fe4c8f381f9f44b5940e215757c | 105 174-1 | 9 Future developments in the series of documents | New parts and sub-parts of the present multi-part deliverable may be created in the future and any changes will be reflected in the Foreword and clause 8 of a future version of the present document. ETSI ETSI TS 105 174-1 V1.2.1 (2014-09) 19 Annex A (informative): Bibliography • Directive 2002/19/EC of the European Parliament and of the Council of 7 March 2002 on access to, and interconnection of, electronic communications networks and associated facilities (Access Directive). • Directive 2002/21/EC of the European Parliament and of the Council of 7 March 2002 on a common regulatory framework for electronic communications networks and services (Framework Directive). ETSI ETSI TS 105 174-1 V1.2.1 (2014-09) 20 History Document history V1.1.1 September 2006 Publication as TR 105 174-1-1 V1.1.1 October 2009 Publication V1.2.1 September 2014 Publication |
1a78e9090133dfd7ab8c19db79ccb9ca | 104 224 | 1 Scope | The present document identifies steps to be taken by designers and implementers of AI platforms in order to give assurance of the explicability and transparency of AI processing. AI processing includes AI decision making and AI data processing. NOTE: The present document uses the term explicability but recognizes that many other publications use the term explainability as a synonym. The terms are interchangeable with the proviso that the latter term is not a commonly accepted UK English word but that it has been used in the specific context of AI (see also clause 3.1 of the present document). |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.