WO2022220640A1 - 무선 통신 시스템에서 e2 노드 제어를 위한 장치 및 방법 - Google Patents
무선 통신 시스템에서 e2 노드 제어를 위한 장치 및 방법 Download PDFInfo
- Publication number
- WO2022220640A1 WO2022220640A1 PCT/KR2022/005457 KR2022005457W WO2022220640A1 WO 2022220640 A1 WO2022220640 A1 WO 2022220640A1 KR 2022005457 W KR2022005457 W KR 2022005457W WO 2022220640 A1 WO2022220640 A1 WO 2022220640A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- ric
- node
- message
- present disclosure
- ran
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 107
- 238000004891 communication Methods 0.000 title abstract description 45
- 230000004044 response Effects 0.000 claims abstract description 47
- 230000008569 process Effects 0.000 claims abstract description 16
- 239000013256 coordination polymer Substances 0.000 claims description 100
- 230000005540 biological transmission Effects 0.000 abstract description 13
- 230000007774 longterm Effects 0.000 abstract description 3
- 230000006870 function Effects 0.000 description 60
- 238000005516 engineering process Methods 0.000 description 36
- 230000011664 signaling Effects 0.000 description 18
- 238000010295 mobile communication Methods 0.000 description 15
- 230000009977 dual effect Effects 0.000 description 14
- 238000007726 management method Methods 0.000 description 14
- 230000009471 action Effects 0.000 description 11
- 238000000926 separation method Methods 0.000 description 11
- 238000013473 artificial intelligence Methods 0.000 description 8
- 238000012986 modification Methods 0.000 description 8
- 230000004048 modification Effects 0.000 description 8
- 238000005259 measurement Methods 0.000 description 7
- 239000000969 carrier Substances 0.000 description 6
- 230000001276 controlling effect Effects 0.000 description 6
- 238000012937 correction Methods 0.000 description 6
- 238000012545 processing Methods 0.000 description 6
- 238000005457 optimization Methods 0.000 description 5
- 238000012546 transfer Methods 0.000 description 5
- 101100194706 Mus musculus Arhgap32 gene Proteins 0.000 description 4
- 101100194707 Xenopus laevis arhgap32 gene Proteins 0.000 description 4
- 230000006872 improvement Effects 0.000 description 4
- 238000012384 transportation and delivery Methods 0.000 description 4
- 230000008901 benefit Effects 0.000 description 3
- 230000002776 aggregation Effects 0.000 description 2
- 238000004220 aggregation Methods 0.000 description 2
- 238000013459 approach Methods 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 238000010801 machine learning Methods 0.000 description 2
- 230000008685 targeting Effects 0.000 description 2
- 241000700159 Rattus Species 0.000 description 1
- 238000004873 anchoring Methods 0.000 description 1
- 230000003190 augmentative effect Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000003111 delayed effect Effects 0.000 description 1
- 238000002716 delivery method Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000007717 exclusion Effects 0.000 description 1
- 239000002360 explosive Substances 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000001151 other effect Effects 0.000 description 1
- 238000007781 pre-processing Methods 0.000 description 1
- 230000001105 regulatory effect Effects 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 238000013468 resource allocation Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/60—Subscription-based services using application servers or record carriers, e.g. SIM application toolkits
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
- H04W8/20—Transfer of user or subscriber data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/08—Access point devices
- H04W88/085—Access point devices with remote components
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/12—Access point controller devices
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W92/00—Interfaces specially adapted for wireless communication networks
- H04W92/04—Interfaces between hierarchically different network devices
- H04W92/12—Interfaces between hierarchically different network devices between access points and access point controllers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W92/00—Interfaces specially adapted for wireless communication networks
- H04W92/16—Interfaces between hierarchically similar devices
- H04W92/20—Interfaces between hierarchically similar devices between access points
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W92/00—Interfaces specially adapted for wireless communication networks
- H04W92/16—Interfaces between hierarchically similar devices
- H04W92/24—Interfaces between hierarchically similar devices between backbone network devices
Definitions
- the present disclosure relates to an apparatus and method for E2 node control by a RAN intelligent controller (RIC) in a radio access network (RAN).
- the present disclosure relates to an apparatus and method for controlling an E2 node through an E2 message conforming to an open radio access network (O-RAN) standard of a wireless communication system.
- OF-RAN open radio access network
- 5G mobile communication technology defines a wide frequency band to enable fast transmission speed and new services. It can also be implemented in the very high frequency band ('Above 6GHz') called Wave).
- 6G mobile communication technology which is called a system after 5G communication (Beyond 5G)
- Beyond 5G in order to achieve transmission speed 50 times faster than 5G mobile communication technology and ultra-low latency reduced by one-tenth, Tera Implementations in the Terahertz band (such as, for example, the 95 GHz to 3 THz band) are being considered.
- ultra-wideband service enhanced Mobile BroadBand, eMBB
- high reliability / ultra-low latency communication Ultra-Reliable Low-Latency Communications, URLLC
- massive-scale mechanical communication massive Machine-Type Communications, mMTC
- Beamforming and Massive MIMO to increase the propagation distance and mitigate the path loss of radio waves in the ultra-high frequency band with the goal of service support and performance requirements, and efficient use of ultra-high frequency resources
- various numerology eg, operation of multiple subcarrier intervals
- New channel coding methods such as LDPC (Low Density Parity Check) code for data transmission and polar code for reliable transmission of control information, L2 pre-processing, dedicated dedicated to specific services Standardization of network slicing that provides a network has progressed.
- LDPC Low Density Parity Check
- the Intelligent Factory Intelligent Internet of Things, IIoT
- IAB Intelligent Internet of Things
- IAB Intelligent Internet of Things
- 5G baseline for the grafting of Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies Standardization of the system architecture/service field for architecture (eg, Service based Architecture, Service based Interface), Mobile Edge Computing (MEC) receiving services based on the location of the terminal, etc.
- NFV Network Functions Virtualization
- SDN Software-Defined Networking
- the 5G system To meet the demand for wireless data traffic, the 5G system, NR (new radio or next radio), has been commercialized, providing high data rate services to users through the 5G system like 4G, and also for the Internet of Things and specific purposes. It is expected that wireless communication services for various purposes, such as services requiring high reliability, can be provided.
- O-RAN open radio access network
- O-RAN open radio access network
- an E2 node to transmit a user equipment (UE) ID (identifier) to a radio access network (RAN) intelligent controller (RIC) in a wireless communication system.
- UE user equipment
- RAN radio access network
- RIC radio access network intelligent controller
- the present disclosure provides an apparatus and method for a message format related to a UE ID management service model applied in Near-RT.
- the method performed by the E2 node includes a process of receiving a subscription request message from a radio access network (RAN) intelligent controller (RIC), and a process of transmitting a subscription response message to the RIC; , when an event according to the subscription response message occurs, transmitting an RIC indication message to the RIC, wherein the RIC indication message is a user equipment (UE) operated in an upper node associated with the E2 node. ID (identifier) may be included.
- RAN radio access network
- RIC radio access network intelligent controller
- ID identifier
- the method performed by a radio access network (RAN) intelligent controller includes a process of transmitting a subscription request message to an E2 node, and a process of receiving a subscription response message from the E2 node and receiving an RIC indication message from the E2 node, which is transmitted when an event according to the subscription response message occurs, wherein the RIC indication message is a UE operating in an upper node associated with the E2 node ID may be included.
- RAN radio access network
- RIC radio access network intelligent controller
- an apparatus performed by an E2 node includes at least one transceiver and at least one processor, wherein the at least one processor is configured to allow the at least one transceiver to receive a subscription request message.
- Receive from a radio access network (RAN) intelligent controller (RIC) transmit a subscription response message to the RIC, and control to transmit a RIC indication message to the RIC when an event according to the subscription response message occurs
- the RIC indication message may include a UE ID operated in a higher node associated with the E2 node.
- an apparatus performed by a radio access network (RAN) intelligent controller (RIC) includes at least one transceiver and at least one processor, wherein the at least one processor comprises the at least one One transceiver transmits a subscription request message to the E2 node, receives a subscription response message from the E2 node, and sends a RIC indication message, which is transmitted when an event according to the subscription response message occurs to the E2 node control to be received from, and the RIC indication message may include a UE ID operated in a higher node associated with the E2 node.
- RAN radio access network
- RIC radio access network intelligent controller
- the apparatus and method according to embodiments of the present disclosure enable a radio access network (RAN) intelligent controller (RIC) to know the UE ID applied according to the event and service model being used in the corresponding E2 node.
- RAN radio access network
- RIC radio access network intelligent controller
- FIG. 1 illustrates an example of a 4th generation (4G) Long Term Evolution (LTE) core system according to various embodiments of the present disclosure.
- 4G 4th generation
- LTE Long Term Evolution
- FIG. 2A illustrates an example of a 5th generation (5G) non-standard alone (NSA) system according to various embodiments of the present disclosure.
- 5G 5th generation
- NSA non-standard alone
- FIG 2B illustrates an example of an architecture for an O-RAN according to various embodiments of the present disclosure.
- FIG 3 illustrates a protocol stack of an E2 application protocol message in a wireless access network according to an embodiment of the present disclosure.
- FIG. 4 illustrates an example of a connection between a base station and a radio access network intelligence controller (RIC) in a radio access network according to an embodiment of the present disclosure.
- RIC radio access network intelligence controller
- FIG. 5 illustrates a configuration of a device in a wireless access network according to an embodiment of the present disclosure.
- FIG. 6 illustrates logical functions related to an E2 message of an E2 node and an RIC in a radio access network according to an embodiment of the present disclosure.
- FIG. 7 illustrates examples of functional separation between an E2 node and an RIC in an embodiment of the present disclosure.
- FIG 8 illustrates an implementation example of an E2 node and RIC according to an embodiment of the present disclosure.
- FIG 9 illustrates examples of functional separation between a centralized unit (CU) and an RIC according to an embodiment of the present disclosure.
- MLB mobility load balancing
- 11A illustrates an example of MLB control for different vendors according to an embodiment of the present disclosure.
- 11B illustrates signaling for radio resource management (RRM) control setting of near-RT RIC according to an embodiment of the present disclosure.
- RRM radio resource management
- 12A and 12B illustrate signaling for RIC-based RRM control according to various embodiments of the present disclosure.
- 13A illustrates signaling of a subscription procedure and RIC indication between an E2 node and an RIC according to embodiments of the present disclosure.
- 13B illustrates signaling of a control procedure between an E2 node and an RIC according to an embodiment of the present disclosure.
- FIG. 14A illustrates an example of a format of a RIC event trigger definition according to an embodiment of the present disclosure.
- FIG. 14B illustrates an example of a format of a RIC action definition according to an embodiment of the present disclosure.
- FIG. 15 shows an example of a format of a RIC indication header according to an embodiment of the present disclosure.
- 16A, 16B, 16C and 16D show examples of a format of an RIC indication message according to various embodiments of the present disclosure.
- 17A, 17B, 17C, 17D, 17E, 17F, 17G, and 17H illustrate examples of an E2 service model (E2SM)-IDM indication message format according to various embodiments of the present disclosure.
- E2SM E2 service model
- 18A, 18B, and 18C illustrate examples of signaling for transmitting an E2 indication in call setup according to various embodiments of the present disclosure.
- 19A, 19B, and 19C illustrate examples of signaling for transmitting an E2 indication according to call release according to various embodiments of the present disclosure.
- 20A, 20B, and 20C illustrate examples of signaling for transmitting an E2 indication through a RAN UE ID according to various embodiments of the present disclosure.
- 21 illustrates a principle of designing a UE ID structure according to an embodiment of the present disclosure.
- a method performed by an E2 node includes a process of receiving a subscription request message from a radio access network (RAN) intelligent controller (RIC), and a process of transmitting a subscription response message to the RIC; , when an event according to the subscription response message occurs, transmitting an RIC indication message to the RIC, wherein the RIC indication message is a user equipment (UE) operated in an upper node associated with the E2 node.
- ID identifier
- a method performed by a radio access network (RAN) intelligent controller includes a process of transmitting a subscription request message to an E2 node, a process of receiving a subscription response message from the E2 node, and , receiving an RIC indication message from the E2 node, which is transmitted when an event according to the subscription response message occurs, wherein the RIC indication message is a UE operating in an upper node associated with the E2 node ( user equipment) may include an identifier (ID).
- ID identifier
- an apparatus performed by an E2 node includes at least one transceiver and at least one processor, wherein the at least one processor is configured to allow the at least one transceiver to receive a subscription request message.
- Receive from a radio access network (RAN) intelligent controller (RIC) transmit a subscription response message to the RIC, and control to transmit a RIC indication message to the RIC when an event according to the subscription response message occurs and, the RIC indication message may include a user equipment (UE) identifier (ID) operated in a higher node associated with the E2 node.
- RAN radio access network
- RIC radio access network intelligent controller
- an apparatus implemented by a radio access network (RAN) intelligent controller includes at least one transceiver and at least one processor, wherein the at least one processor includes the at least one Transceiver of , transmits a subscription request message to the E2 node, receives a subscription response message from the E2 node, and sends an RIC indication message, which is transmitted when an event according to the subscription response message occurs, from the E2 node control to be received, and the RIC indication message may include a user equipment (UE) identifier (ID) operated in an upper node associated with the E2 node.
- UE user equipment
- the present disclosure relates to a control procedure between a device in a radio access network (RAN) and a device controlling the RAN in a wireless communication system. Specifically, the present disclosure discloses whether the RIC transmits a RIC control request message to the E2 node on the E2 interface in the radio access network, and whether the RIC control request is correctly made or failed by the E2 node, and if it fails, the reason ( A procedure, message, and method for confirming reason).
- RAN radio access network
- an expression of greater than or less than may be used, but this is only a description for expressing an example. It's not about exclusion. Conditions described as 'more than' may be replaced with 'more than', conditions described as 'less than', and conditions described as 'more than and less than' may be replaced with 'more than and less than'.
- the present disclosure describes various embodiments using terms used in some communication standards (eg, 3rd Generation Partnership Project (3GPP), open radio access network (O-RAN)), but this is an example for description Various embodiments of the present disclosure may be easily modified and applied in other communication systems.
- 3GPP 3rd Generation Partnership Project
- OFDRAN open radio access network
- 3GPP is a joint research project between mobile communication-related organizations and aims to create a 3G mobile communication system standard - applicable worldwide - within the scope of the IMT-2000 project of the International Telecommunication Union (ITU). 3GPP was established in December 1998, and the 3GPP standard is based on the advanced GSM standard, and includes radio, core network, and service architecture all within the scope of standardization.
- O-RAN open radio access network
- RU radio unit
- DU distributed unit
- CU central unit
- CU-UP user plane
- O(O-RAN)-RU O-DU
- O-CU-CP control plane
- CU-UP user plane
- NRT near-real-time
- RIC radio access network intelligent controller
- O-RU, O-DU, O-CU-CP, and O-CU-UP may be understood as objects constituting a RAN that can operate according to the O-RAN standard, and as an E2 node (node). may be referred to.
- An interface with objects constituting the RAN that can operate according to the O-RAN standard between RIC and E2 nodes uses an E2AP (application protocol).
- the RIC is a logical node capable of collecting information on a cell site transmitted/received between the UE and the O-DU, O-CU-CP, or O-CU-UP.
- RIC may be implemented in the form of a server centrally located in one physical location. Connections can be made through Ethernet between O-DU and RIC, between O-CU-CP and RIC, and between O-CU-UP and RIC. For this, interface standards for communication between O-DU and RIC, between O-CU-CP and RIC, and between O-CU-UP and RIC were required, and E2-DU, E2-CU-CP, E2-CU- The definition of message standards such as UP and procedures between O-DU, O-CU-CP, O-CU-UP and RIC is required.
- differentiated service support is required for users in a virtualized network, and by concentrating call processing messages/functions generated in O-RAN on RIC, E2-DU to support services for a wide range of cell coverage, It is necessary to define the function of the messages of E2-CU-CP and E2-CU-UP.
- the RIC may communicate with the O-DU, O-CU-CP, and O-CU-UP using the E2 interface, and may set an event generation condition by generating and transmitting a subscription message.
- the RIC can set the call processing EVENT by generating an E2 subscription request message and delivering it to an E2 node (eg, O-CU-CP, O-CU-UP, O-DU).
- an E2 node eg, O-CU-CP, O-CU-UP, O-DU.
- the E2 node transmits the Subscription Request Response message delivered to the RIC.
- the E2 node may transmit the current state to the RIC through an E2 indication/report.
- the RIC may provide control for O-DU, O-CU-CP, and O-CU-UP using an E2 control message.
- Various embodiments of the present disclosure propose an E2 indication message for transmitting UE-unit measurement information for each period set in a subscription event condition in O-DU.
- various embodiments of the present disclosure propose a message for controlling a resource transmitted from the RIC to the O-DU.
- FIG. 1 illustrates an example of a 4 th generation (4G) Long Term Evolution (LTE) core system according to various embodiments of the present disclosure.
- the LTE core system includes a base station 110 , a terminal 120 , a serving gateway (S-GW) 130 , a packet data network gateway (P-GW) 140 , and a mobility management entity (MME). 150 , a home subscriber server (HSS) 160 , and a policy and charging rule function (PCRF) 170 .
- S-GW serving gateway
- P-GW packet data network gateway
- MME mobility management entity
- HSS home subscriber server
- PCRF policy and charging rule function
- the base station 110 is a network infrastructure that provides a wireless connection to the terminal 120 .
- the base station 110 is a device that performs scheduling by collecting state information such as a buffer state, available transmission power, and channel state of the terminal 110 .
- the base station 110 has coverage defined as a certain geographic area based on a distance capable of transmitting a signal.
- the base station 110 is connected to the MME 150 through an S1-MME interface.
- the base station 110 is an 'access point (AP)', an 'eNodeB (eNodeB)', a 'wireless point', a 'transmission/reception point, TRP)' or other terms having an equivalent technical meaning may be referred to.
- AP 'access point
- eNodeB eNodeB
- TRP 'transmission/reception point
- the terminal 120 is a device used by a user and performs communication with the base station 110 through a wireless channel. In some cases, the terminal 120 may be operated without the user's involvement. That is, at least one of the terminal 120 and the S-GW 130 is a device that performs machine type communication (MTC) and may not be carried by the user.
- the terminal 120 is a terminal other than 'user equipment (UE)', 'mobile station', 'subscriber station', customer-premises equipment (CPE) ' It may be referred to as a 'remote terminal', 'wireless terminal', or 'user device' or other terms having an equivalent technical meaning.
- the S-GW 130 provides a data bearer, and creates or controls the data bearer according to the control of the MME 150 .
- the S-GW 130 processes a packet arriving from the base station 110 or a packet to be forwarded to the base station 110 .
- the S-GW 130 may perform an anchoring role during handover between base stations of the terminal 120 .
- the P-GW 140 may function as a connection point with an external network (eg, an Internet network).
- the P-GW 140 allocates an Internet Protocol (IP) address to the terminal 120 and serves as an anchor for the S-GW 130 .
- the P-GW 140 may apply the QoS (Quality of Service) policy of the terminal 120 and manage account data.
- IP Internet Protocol
- the MME 150 manages the mobility of the terminal 120 .
- the MME 150 may perform authentication for the terminal 120 , bearer management, and the like. That is, the MME 150 is in charge of mobility management and various control functions for the terminal.
- the MME 150 may interwork with a serving GPRS support node (SGSN) 155 .
- SGSN serving GPRS support node
- the HSS 160 stores key information and a subscriber profile for authentication of the terminal 120 .
- the key information and the subscriber profile are transmitted from the HSS 160 to the MME 150 when the terminal 120 accesses the network.
- the PCRF 170 defines a rule for policy and charging.
- the stored information is transferred from the PCRF 180 to the P-GW 140, and the P-GW 140 controls the terminal 120 based on the information provided from the PCRF 180 (eg, QoS management, charging, etc.). ) can be done.
- a carrier aggregation (hereinafter, 'CA') technology a plurality of component carriers are combined, and one terminal transmits and receives a signal using the plurality of component carriers at the same time. It is a technology that increases the efficiency of use.
- the terminal and the base station can transmit and receive signals using a wideband using a plurality of component carriers in uplink (UL) and downlink (DL), respectively, and at this time, each component carrier are located in different frequency bands.
- the uplink refers to a communication link in which the terminal transmits a signal to the base station
- the downlink refers to a communication link in which the base station transmits a signal to the terminal.
- the number of uplink component carriers and downlink component carriers may be different from each other.
- one terminal is connected to a plurality of different base stations and transmits and receives signals simultaneously using carriers in each of a plurality of base stations located in different frequency bands. It is a technology to increase the frequency use efficiency of The terminal provides a service using a first base station (eg, a base station that provides services using LTE technology or 4G mobile communication technology) and a second base station (eg, NR (new radio) technology or 5G ( 5th generation) mobile communication technology) can be simultaneously connected to a base station that provides In this case, the frequency resources used by each base station may be located in different bands.
- a method operating based on the dual connectivity method of LTE and NR may be referred to as 5G non-standalone (NSA).
- FIG. 2A illustrates an example of a 5G NSA system according to various embodiments of the present disclosure.
- the 5G NSA system includes an NR RAN 210a , an LTE RAN 210b , a terminal 220 , and an EPC 250 .
- the NR RAN 210a and the LTE RAN 210b are connected to the EPC 250, and the terminal 220 may receive a service from any one or both of the NR RAN 210a and the LTE RAN 210b at the same time.
- the NR RAN 210a includes at least one NR base station
- the LTE RAN 210b includes at least one LTE base station.
- the NR base station may be referred to as a '5G node (5th generation node)', a 'next generation nodeB (gNB)', or other terms having an equivalent technical meaning.
- the NR base station may have a structure divided into a CU (central unit) and a DU (digital unit), and the CU has a structure separated into a CU-CP (control plane) unit and a CU-UP (user plane) unit.
- CU-CP control plane
- CU-UP user plane
- the terminal 220 performs radio resource control (RRC) access through a first base station (eg, a base station belonging to the LTE RAN 210b), and functions provided in a control plane. (eg, connection management, mobility management, etc.) can be serviced.
- RRC radio resource control
- the terminal 220 may be provided with an additional radio resource for transmitting and receiving data through the second base station (eg, a base station belonging to the NR RAN 210a).
- This dual connectivity technology using LTE and NR may be referred to as EN-DC (evolved universal terrestrial radio access (E-UTRA) - NR dual connectivity).
- EN-DC evolved universal terrestrial radio access
- NR-E-UTRA dual connectivity a dual connectivity technology in which a first base station uses NR technology and a second base station uses LTE technology is referred to as NR-E-UTRA dual connectivity (NE-DC).
- NE-DC NR-E-UTRA dual connectivity
- various embodiments may be applied to other various types of multi-connection and carrier aggregation technologies.
- various embodiments are applicable even when the first system using the first communication technology and the second system using the second communication technology are implemented in one device or when the first base station and the second base station are located in the same geographic location. can
- FIG. 2B illustrates an example of an architecture for an O-RAN according to various embodiments of the present disclosure.
- E2-SM-KPIMON key performance indicator (KPI) monitoring
- KPI key performance indicator
- the eNB in the deployment of the O-RAN non-standalone mode, the eNB is connected to the EPC through the S1-C/S1-U interface, and is connected to the O-CU-CP and the X2 interface.
- O-CU-CP for O-RAN standalone mode deployment (deployment) may be connected to the 5GC (5G core) through the N2 / N3 interface.
- the control plane includes a transport network layer and a radio network layer.
- the transport network layer includes a physical layer 310 , a data link layer 320 , an internet protocol (IP) 330 , and a stream control transmission protocol (SCTP) 340 .
- IP internet protocol
- SCTP stream control transmission protocol
- the radio network layer includes the E2AP (350).
- the E2AP 350 is used to deliver a subscription message, an indication message, a control message, a service update message, and a service query message, SCTP 340 and IP 330 are transmitted in a higher layer (higher layer).
- FIG. 4 illustrates an example of a connection between a base station and a radio access network intelligence controller (RIC) in a radio access network according to embodiments of the present disclosure.
- RIC radio access network intelligence controller
- the RIC 440 is connected to the O-CU-CP 420 , the O-CU-UP 410 , and the O-DU 430 .
- RIC 440 is a device for customizing RAN functionality (functionality) for a new service or regional resource optimization (regional resource optimization).
- RIC 440 is a network intelligence (network intelligence) (eg, policy enforcement (policy enforcement), handover optimization (handover optimization)), resource assurance (resource assurance) (eg, radio-link management), improvement functions such as advanced self-organized-network (SON) and resource control (eg, load balancing, slicing policy) and the like.
- network intelligence network intelligence
- policy enforcement policy enforcement
- handover optimization handover optimization
- resource assurance resource assurance
- SON advanced self-organized-network
- resource control eg, load balancing, slicing policy
- the RIC 440 may communicate with the O-CU-CP 420 , the O-CU-UP 410 , and the O-DU 430 .
- the RIC 440 can be connected to each node through E2-CP, E2-UP, and E2-DU interfaces.
- E2-CP E2-CP
- E2-UP E2-UP
- E2-DU interface between the O-CU-CP and the DU and between the O-CU-UP and the DU
- F1 interface an interface between the O-CU-CP and the DU and between the O-CU-UP and the DU
- DU and O-DU, CU-CP and O-CU-CP, and CU-UP and O-CU-UP may be used interchangeably.
- a plurality of RICs may exist according to various embodiments.
- the plurality of RICs may be implemented as a plurality of hardware located in the same physical location or may be implemented through virtualization using one piece of hardware.
- FIG. 5 illustrates a configuration of an apparatus according to embodiments of the present disclosure.
- the structure illustrated in FIG. 5 may be understood as a configuration of a device having at least one function among RIC, O-CU-CP, O-CU-UP, and O-DU of FIG. 5 .
- RIC RIC
- O-CU-CP O-CU-CP
- O-CU-UP O-CU-UP
- O-DU O-DU of FIG. 5
- '... wealth' '...
- 'group' means a unit for processing at least one function or operation, which may be implemented as hardware or software, or a combination of hardware and software.
- the core network device includes a communication unit 510 , a storage unit 520 , and a control unit 530 .
- the communication unit 510 provides an interface for performing communication with other devices in the network. That is, the communication unit 510 converts a bit string transmitted from the core network device to another device into a physical signal, and converts a physical signal received from the other device into a bit string. That is, the communication unit 510 may transmit and receive signals. Accordingly, the communication unit 510 may be referred to as a modem, a transmitter, a receiver, or a transceiver. In this case, the communication unit 510 enables the core network device to communicate with other devices or systems through a backhaul connection (eg, a wired backhaul or a wireless backhaul) or through a network.
- a backhaul connection eg, a wired backhaul or a wireless backhaul
- the storage unit 520 stores data such as a basic program, an application program, and setting information for the operation of the core network device.
- the storage unit 520 may be configured as a volatile memory, a non-volatile memory, or a combination of a volatile memory and a non-volatile memory.
- the storage unit 520 provides the stored data according to the request of the control unit 530 .
- the controller 530 controls overall operations of the core network device. For example, the control unit 530 transmits and receives a signal through the communication unit 510 . Also, the controller 530 writes and reads data in the storage 520 . To this end, the controller 530 may include at least one processor. According to various embodiments, the controller 530 may control the device to perform operations according to various embodiments described in the present disclosure.
- FIG. 6 illustrates logical functions related to an E2 message of an E2 node and an RIC in a radio access network according to embodiments of the present disclosure.
- the RIC 640 and the E2 node 610 may transmit or receive an E2 message to each other.
- the E2 node 610 may be an O-CU-CP, an O-CU-UP, an O-DU, or a base station.
- the communication interface of the E2 node may be determined according to the type of the E2 node 610 .
- the E2 node 610 may communicate with another E2 node 616 through an E1 interface or an F1 interface.
- the E2 node 610 may communicate with the E2 node 616 through an X2 interface or an XN interface.
- the E2 node 610 may perform communication through an S1 interface or a next generation application protocol (NGAP) interface (ie, an interface between a next generation (NG) RAN node and an AMF).
- NGAP next generation application protocol
- the E2 node 610 may include an E2 node function 612 .
- the E2 node function 612 is a function corresponding to a specific xApp (application S/W) 646 installed in the RIC 640 .
- application S/W application S/W
- the KPI monitor collection S/W is installed in the RIC 640, and the E2 node 610 generates the KPI parameters and then sends the E2 message including the KPI parameters to the RIC ( E2 node function 612 forwarding to E2 termination 642 located at 640 .
- the E2 node 610 may include a radio resource management (RRM) 614 .
- the E2 node 610 may manage the resources provided to the wireless network for the terminal.
- the E2 end 642 located in the RIC 640 is the end of the RIC 640 for the E2 message, interprets the E2 message delivered by the E2 node 610, and then delivers the function to the xApp 646. do.
- a DB (database) 644 located in the RIC 640 may be used for the E2 end 642 or the xApp 646 .
- the E2 node 610 illustrated in FIG. 6 is an end of at least one interface, and may be understood as an end of messages transmitted to a terminal, a neighboring base station, and a core network.
- the O-RAN specification provides separation of functions between the E2 node and the RIC.
- the E2 node may be a CU.
- the RIC may be a Near RT RIC.
- the RIC may be connected to an open network automation platform (ONAP)/managmenet and orchestration (MANO)/network management system (NMS) through an A1 interface.
- the RIC may be connected to the E2 node through the E2 interface.
- the E2 interface may transmit commands.
- the function separation option may include a function separation 700 that manages the entire radio resource management (RRM) in the near-RT RIC, and a function separation 750 that selectively manages the RRM in the near-RT RIC.
- RRM radio resource management
- Near-RT RIC is to make E2 an open logical interface targeting multi-vendor environments regardless of implementation of the specific RRC-RRM algorithm located in nRT-RIC.
- E2SM-NI paired with E2SM-NI capable of inserting / modifying / configuring Per UE RRC messages for each I / F and NE (network entity).
- E2 Service Model Radio Interface Control (RIC) may be proposed.
- the Near RT RIC may be improved gradually in the direction of the functional separation 700 from the functional separation 750 .
- E2 is independent of the specific RRC-RRM algorithm implementation found in nRT-RIC and can be developed as an open logical interface targeting multi-vendor environments.
- FIG 8 illustrates an implementation example of an E2 node and RIC according to embodiments of the present disclosure.
- E2 nodes eg, O-DU, O-CU
- RIC virtualized on a cloud platform (eg, open chassis and blade specification edge cloud), and the device (e.g. server).
- This scenario would support deployment in densely populated urban areas with abundant fronthaul capacity allowing BBU functions to be pooled in a central location, with low enough latency to meet O-DU latency requirements. can Therefore, it may not be necessary to attempt to centralize RICs close to RT beyond the limit to which O-DU functions can be centralized.
- E2SM-RIC may be optimized for O-RAN deployment scenarios in which Near-RT RIC, O-CU, and O-DU are implemented in O-Cloud Platform.
- function separation may be performed according to deployment scenario #1 900 or function deployment scenario #2 950 .
- Deployment Scenario #1 (900): RICs are located on separate sites or only exist in other NEs, replacing or recommending some intelligence essential functions.
- Deployment Scenario #2 (950): RIC can replace almost all functions of CU except 3GPP I/F management.
- the mobility function may be performed by the RIC rather than the CU.
- the UE context function may be performed by the RIC rather than the CU.
- the session establishment function may be performed by the RIC rather than the CU.
- MLB mobility load balancing
- this MLB may be performed by RRM control.
- the first CU and the first DU may be provided by vendor A.
- the second CU and the second DU may be provided by vendor B.
- the first DU may provide a service area of vendor A.
- RUs connected to the first DU may provide a service area of vendor A.
- the second DU may provide a service area of Vendor B.
- the RUs connected to the second DU may provide the service area of the vendor B.
- the terminal When the terminal moves, it may be performed through load balancing with respect to which cell is optimal. If such load balancing is performed by different vendors, it may be difficult to smoothly perform load balancing in a space where service areas of the vendors overlap. That is, it is required to perform interworking between vendors in an inter vendor zone or an inter CU-CP area. For interworking between these vendors, RRM control may be required to be performed in a centralized form. Accordingly, the RIC according to various embodiments of the present disclosure may be configured to perform RRM. The RIC can generate messages to control each E2 node, as well as simply receive measurements from each E2 node. The RIC may transmit a control message to each E2 node (eg, DU, CU-CP, CU-UP).
- each E2 node eg, DU, CU-CP, CU-UP
- FIG. 11A illustrates an example of MLB control for different vendors according to embodiments of the present disclosure.
- the RAN context may be identified in the Near-RT RIC.
- trigger events/REPORT, INSERT, POLICY conditions can be activated.
- Control actions also work, and the generic sub-function definition approach can work as well.
- the RAN context cannot be confirmed in the Near-RT RIC.
- trigger event/REPORT, INSERT, and POLICY conditions do not work. The control action does not work or has to depend on the implementation due to the conflict of the local RRM.
- RAN function parity means a difference in characteristics related to RRM functions (eg, quality of service (QoS) handover, load balancing (LB) handover, etc.).
- RAN operation parity means a difference in characteristics related to RAN operations (eg, EN-DC SCG bearer change procedure).
- the operations for REPORT/INSERT/CONTROL/POLICY cannot identify the correct RAN CONTEXT.
- REPORT/INSERT/CONTROL/POLICY operations cannot identify trigger events/conditions according to REPORT/INSERT/POLICY.
- a wireless communication environment 1100 illustrates network entities configured through a total of three vendors.
- Vendor A may be an NR provider.
- Vendor B may be an LTE provider.
- Vendor C may be a RIC supplier.
- the near-RT RIC can collect all of their measurement information, so the near-RT RIC can manage and control it more easily than other entities. Accordingly, as the near-RT RIC performs RRM in a centralized manner, differences between vendors and compatibility issues can be resolved. In addition, even with different RATs, differences between vendors and compatibility issues can be resolved.
- the centralized RRM by the near-RT RIC is referred to by terms such as RIC-based RRM control or zombie mode of E2 node, zombie mode of E2SM-RIC, and E2SM-RIC-only mode.
- RIC-based RRM control or zombie mode of E2 node zombie mode of E2SM-RIC
- E2SM-RIC-only mode E2SM-RIC-only mode
- 11B illustrates signaling for setting RRM control of near-RT RIC according to embodiments of the present disclosure.
- 11B shows an example of a signaling procedure between the E2 node and the RIC.
- FIG. 11B shows a setup procedure of E2 I/F between an E2 node and an RIC and a procedure of transferring a RIC subscription message.
- FIG. 11B a procedure of transferring the RIC indication message and the RIC control message is shown.
- the E2 node may include transmitting an E2 SET UP REQUEST message to the RIC.
- the E2 NODE FUNCTION located in the E2 node may search for the RIC using the IP address of the RIC set as operation-administration-maintenance (OAM) and transmit the E2 setup request message.
- the E2 node may request RIC-based RRM control.
- the E2 node may transmit an E2 SET UP REQUEST message including that the E2 node is capable of a zombie mode operation to the RIC.
- the RIC may receive an E2 SETUP RESPONSE message from the E2 node.
- the RIC may determine, from the E2 node, whether the E2 node supports the zombie mode, that is, full RRM control by the RIC is possible.
- the RIC may transmit a subscription request (RIC SUBSCRIPTION REQUEST) message to the E2 node.
- a specific xApp located in the RIC requests the RIC E2 end function to subscribe (or subscribe) to the specific RAN Function Definition function supported by E2.
- the subscription request message may include information for indicating whether the RIC performs RIC-based RRM control.
- the subscription request message may include information for indicating whether the RIC operates as an E2SM-RIC.
- the RIC may transmit a subscription request message including a zombie mode indicator.
- RIC-based RRM control may be performed in units of a terminal or a terminal group including terminals.
- the RIC-based RRM control may be performed for a terminal located in an area between vendors or a common service area of CU-UPs or a group including the terminal, as shown in FIGS. 10 and 11A .
- the subscription request message may include an ID indicating a group (hereinafter, group identifier) or an ID indicating a specific terminal (hereinafter, terminal ID/UE ID).
- the transmission of the subscription request message and the E2 setting response message may be transmitted separately.
- the subscription request message of the step may be transmitted together by being included in the E2 SETUP RESPONSE message of the step.
- the E2 node may transmit a subscription request response (RIC SUBSCRIPTION RESPONSE) to the RIC.
- the E2 node function of the E2 node may decode the subscription request message.
- the E2 node may identify whether the RIC is an E2SM RIC.
- the E2 node can check whether the RIC operates in the zombie mode or whether the E2 node operates in the zombie mode.
- the E2 node may transmit an E2 RIC indication message to the RIC.
- the E2 node and the RIC may perform the RIC indication procedure.
- the RIC indication message may include a KPI report per UE.
- a message container of the RIC indication message may include a KPI reporting service model in units of UEs.
- the RIC may perform RRM for the corresponding UE.
- the RIC may perform RRM and generate a control message including specific information related to a resource allocation procedure. Through this, the RIC can control each E2 node.
- E2SM RIC control CONTROL
- the E2 node 610 and the RIC 640 may perform a RIC control procedure.
- the RIC 640 may generate an E2SM-RIC RIC control message for a control procedure of the E2 node.
- the E2SM-RIC RIC control message may include a message container.
- the message container may include an RRC message for each interface (eg, an X2 SgNB addition request message).
- measurements may be performed and reported in various units such as a group/network slice of the UE, and RIC control may be performed.
- the E2 node and the RIC may independently perform the E2 configuration procedure.
- the E2 node and the RIC may independently perform the subscription procedure.
- the E2 setup response message may include a subscription request message.
- the E2 node and the RIC may independently perform the RIC indication procedure.
- the E2 node and the RIC may independently perform the RIC control procedure.
- the E2 node and the RIC may perform at least some of the above-described procedures together or separately.
- FIGS. 12A and 12B illustrate signaling for RIC-based RRM control according to various embodiments of the present disclosure.
- Load balancing eg MLB
- FIGS. 12A to 12B the same may be applied to a plurality of E2 nodes, particularly E2 nodes having different vendors. Even if the vendors are different, the RRM control can be more efficiently performed through the control by the RIC (CONTROL).
- the RIC may process the following messages/procedures to perform the functions of the E2 node instead.
- the E2 node may forward the message to the RIC. That is, in order for the RIC to perform interpretation/processing/judgment of the corresponding message, the E2 node may bypass the corresponding message and deliver it to the RIC.
- the blanks shown in FIGS. 12A and 12B mean that the near-RT RIC performs a function that should have been performed by each existing E2 node.
- an intelligence-aided function may be improved in order to perform operations for RRM, such as interpretation/processing/judgment of a message.
- FIGS. 12A and 12B are listed in chronological order, this is only for explaining the operation of the E2SM-RIC according to various embodiments of the present disclosure, and a specific signaling is an essential component. It is limited to be performed before other signaling. doesn't mean to That is, according to another exemplary embodiment, some of the procedures illustrated in FIGS. 12A and 12B may be omitted. According to another embodiment, some signaling may be performed by the RIC at a time.
- FIGS. 12A and 12B an example of processing the messages of (1) to (12) is illustrated in FIGS. 12A and 12B , embodiments of the present disclosure are not limited thereto. Some of the above-described examples may be interpreted/determined/processed by the RIC, but others may be performed by the E2 node as before.
- FIGS. 13A to 13B in order to perform a RIC control procedure according to an embodiment of the present disclosure, a setup procedure and a subscription procedure between the E2 node and the RIC, and a UE ID list REPORT procedure are It is described.
- 13A illustrates signaling of a subscription procedure and RIC indication between an E2 node and an RIC according to embodiments of the present disclosure.
- 13A illustrates a subscription procedure and a RIC Indication (REPORT) procedure between an E2 node and an RIC according to embodiments of the present disclosure.
- REPORT RIC Indication
- the RIC may transmit a RIC subscription request message to the E2 node.
- the E2 node may be O-CU-CP, O-CU-UP, or O-CU-DU.
- the E2 node may transmit a RIC subscription response message (RIC Subscription Response) to the RIC.
- the E2 node may transmit a RIC indication message to the Near RT RIC.
- Each E2 node may identify an event set for the corresponding E2 node through a subscription procedure.
- the RIC indication message may include a UE ID list.
- the UE ID list may include one or more UE IDs.
- 13B illustrates signaling of a control procedure between an E2 node and an RIC according to embodiments of the present disclosure.
- 13B illustrates an overall message flow between an E2 node, RIC, and Non-RT RIC according to embodiments of the present disclosure, and a procedure in which an E2 node reports a UE ID list using a RIC Indication message according to an embodiment of the present disclosure.
- the Non-RT RIC may transmit a Policy for controlling the Near-RT RIC to the E2 Node by using the A1 Interface to the RIC.
- An A1 interface may be defined between the Non-RT RIC and the Near RT RIC.
- the A1 Policy includes at least one of a policy for each UE, a policy for each group, a policy for each cell, and a policy for each slice, and may be variously configured for each service.
- the RIC may perform the RIC subscription procedure based on the A1 Policy received in the A1 Policy message.
- the A1 policy create message may include, for example, a JavaScript Object Notation (JSON) message format.
- JSON JavaScript Object Notation
- the A1 policy creation message when setting a policy for a specific UE, may include a UE ID. Also, for example, when setting a policy for a specific cell, the A1 policy creation message may include a cell ID. Also, for example, when controlling QoS, the A1 policy creation message may include a GBR related to QoS.
- the RIC may transmit a RIC subscription request message (RIC Subscription Request) to the E2 node.
- the E2 node may transmit a RIC subscription response message (RIC Subscription Response) to the RIC.
- RIC creates a RIC Subscription request in the subscription process.
- the RIC Subscription request is a message for actually setting a SERVICE for controlling the E2 node.
- the RIC may request subscription of the REPORT service and the CONTROL service for receiving measurement measurement and UE ID list) from the E2 node.
- a specific xApp located in the RIC requests a RIC E2 end function to subscribe (or subscribe) to a specific RAN Function Definition function supported by E2.
- the E2 node function of the E2 node may decode the subscription request message. After the E2 node function of the E2 node successfully sets the event condition requested by the RIC to the E2 node function, the event trigger condition is successfully set through the RIC Subscription Response. It can be communicated to RIC that it has been established.
- RIC Subscription Request and RIC Subscription Response are exchanged between RIC and E2 nodes for subscription of REPORT service
- RIC Subscription Request and RIC Subscription Response are additionally transmitted between RIC and E2 nodes for subscription of CONTROL service.
- the E2 node may transmit a RIC indication (or RIC Policy Indication) to the RIC.
- the E2 node may include, in the RIC Indication message, related measurement data, UE state information, UE ID list, and the like, and transmit it to the RIC.
- the E2 node 610 may transmit an E2 RIC indication message to the RIC 640 .
- the message container of the RIC indication message may include a KPI reporting service model in units of UE, UE ID list information, and the like.
- the RIC may perform a RIC control procedure.
- the RIC may transmit a control request message (RIC CONTORL REQUEST) to the E2 node.
- the E2 node may send a RIC control acknowledgment (RIC CONTROL ACKNOWLEDGE) to the RIC.
- 14A illustrates an example of a format of a RIC event trigger definition according to embodiments of the present disclosure.
- 14A illustrates an example of a RIC service subscription request (RIC Subscription Request) procedure and message according to embodiments of the present disclosure.
- the near-RT RIC may transmit a RIC subscription request message to a base station (eg, gNB).
- RIC subscription request message may include a message type (message type), RIC request (request) ID, RAN function (function) ID, RIC subscription details (RIC subscription details).
- Information on RIC subscription details may include a RIC event trigger definition. That is, in FIG. 14A, the format of the RIC Event Trigger Definition is shown in the RIC SUBSCRIPTION REQUEST message specified in the O-RAN standard. RIC Event Trigger Definition may be defined according to each RIC and SERVICE MODEL supported by RAN. Embodiments of the present disclosure propose a procedure for selecting an ID LIST of a UE that satisfies the TRIGGERING CONDITION from among UE IDs that vary according to the UE state of the RAN.
- a Message Type of the subscription message is the type number specified in the specification for each message type.
- RIC Request ID is an ID that uniquely manages the corresponding message in RIC.
- the RAN Function ID is an ID that identifies the FUNCTION that is the target of CONTROL in the E2 Node.
- the RIC Event Trigger Definition IE is defined in the form of the Event Trigger Definition Format defined in the Service Model in detail for the message. In this disclosure, the IE for the Event Trigger Definition Format is exemplified as E2SM-IDM Event Trigger Definition Format 1, but the IE name may be different depending on the Service Model.
- Event Trigger Definition Format 1 indicates a list of conditions for designating a terminal of a specific group, and the present disclosure exemplifies the IE as UE ID Report Triggering Condition, but the IE name is different depending on the Service Model can do.
- UE ID Report Triggering Condition is composed of a Triggering Condition ID that specifies the condition, a Triggering Condition that specifies the relationship between the conditions, and a Triggering Condition Value that specifies the condition value.
- the Triggering Condition ID can be defined as a service profile identifier (SPID) or a value in the NGAP Interface specified in the 3GPP standard.
- Triggering Condition can be interpreted in an arithmetic/logical way with respect to the condition value such as Equal, Greater than, Less than, Present, etc.
- Triggering Condition Value is a comparison value in arithmetic/logical calculation, and may be deleted in some cases. Detailed examples are as follows.
- Triggering Condition "Equal” (Triggering Condition Value, '255') If Triggering Condition (SPID) "Greater Than” (Triggering Condition Value, '5')
- FIG. 14B illustrates an example of a format of a RIC action definition according to an embodiment of the present disclosure.
- An example of a RIC Action Definition message in a RIC service subscription request procedure according to embodiments of the present disclosure is described through FIG. 14B.
- the near-RT RIC may transmit a RIC subscription request message to a base station (eg, gNB).
- RIC subscription request message may include a message type (message type), RIC request (request) ID, RAN function (function) ID, RIC subscription details (RIC subscription details).
- RIC Action Definition is a service service method in which RIC requests a specific action to E2 Node in the subscription request procedure.
- Each Service Model optionally defines Action Definition in the subscription request procedure as needed.
- E2SM-IDM Action Definition Format 1 is defined. Format 1 consists of a RAN Parameter ID and a RAN Parameter Value, and in the example of the present disclosure, two parameters, AddTimestamp and Group ID, are defined.
- AddTimestamp can be selectively used to request the E2 Node to add Timestamp in the RIC REPORT service (RIC Indication) procedure.
- the Group ID can be controlled to load the Group ID selected by the E2 Node in the RIC Service Subscription Request procedure and deliver it to the RIC.
- FIG. 15 shows an example of a format of a RIC indication header according to an embodiment of the present disclosure.
- RIC Indication Header message in a RIC REPORT service (RIC Indication) procedure is described.
- a base station may transmit an E2 RIC indication message to the Near-RT RIC.
- the RIC Indication message specified in the O-RAN standard may include RIC Indication header information.
- the RIC Indication message may be different for each E2 service model, and may be defined for each E2 service model.
- the RIC Indication Header may include an E2SM Indication header format defined as a detailed message in the Service Model.
- the RIC Indication Header according to embodiments of the present disclosure may be defined as E2SM-IDM Indication Header Format 1.
- the detailed E2SM-IDM Indication Header Format 1 may include the ID of the E2 node that transmits the E2 Indication message, the Network Interface Timestamp, and the Group ID.
- the Network Interface Timestamp and the Group ID may be the items requested by the RIC in the E2SM-IDM Action Definition Format 1 of FIG. 14B .
- the E2 node may transmit the Network Interface Timestamp and Group ID to the Near-RT RIC through the E2 Indication header.
- 16A, 16B, 16C, and 16D show examples of a format of a RIC indication message according to various embodiments of the present disclosure.
- the E2 node eg, gNB
- the E2 node may transmit an E2 indication message to the Near-RT RIC.
- gNB is shown as an example of an E2 node, if it is an E2 node defined by RIC and E2 interfaces, such as eNB, ng-eNB, en-gNB, O-CU, O-DU, O-CU-CP, O-CU-UP, this Of course, the embodiments of the disclosure may be applied.
- the E2 indication message may include Message Type, RIC Request ID, RIC Function ID, RIC Action ID, RIC Indication SN (optional), RIC Indication Type, RIC Indication Header, RIC Indication message, RIC Call process ID (optional).
- RIC indication message (RIC Indication message) may include a UE ID defined according to the E2SM-IDM indication format.
- the RIC indication message may include an O-RAN UE ID structure (O-RAN UE ID structure).
- the IE of the O-RAN UE ID structure (“O-RAN UE ID structure”) may have a format designed to include all types of UE IDs that may be defined in the E2 node.
- the O-RAN UE ID structure may be used in a call setup procedure.
- the O-RAN UE ID structure may be in the format of FIGS. 17A and 17B .
- gNB-CU-CP, gNB-CU-UP, and gNB-DU send an E2 indication message including a UE ID to the Near-RT RIC for call setup, respectively. can be transmitted
- gNB-CU-CP and gNB-CU-UP #2 each provide a UE ID to the Near-RT RIC.
- E2 indication message may transmit an E2 indication message including Also, according to an embodiment, in case of adding a secondary node (SN) in dual connectivity (DC) (eg, SgNB Addition), gNB-CU-CP of master node (MN), gNB-CU-CP of SN , gNB-CU-UP, and gNB-DU may transmit an E2 indication message including a UE ID to the Near-RT RIC, respectively.
- SN secondary node
- DC dual connectivity
- the RIC indication message may include a Key UE ID structure (Key UE ID structure).
- the IE of the Key UE ID structure (“Key UE ID structure”) may have a format designed to include the UE ID managed by the upper node of the E2 node.
- the Key UE ID structure may be used in the release procedure.
- gNB-CU-CP, gNB-CU-UP, and gNB-DU each include a UE ID to the Near-RT RIC for call release.
- E2 indication message can be transmitted.
- gNB-CU-CP and gNB-CU-UP #2 are each directed to the Near-RT RIC.
- An E2 indication message including the UE ID may be transmitted.
- gNB-CU-CP, gNB-CU-UP, and gNB-DU each include a UE ID to the Near-RT RIC. E2 indication message can be transmitted.
- the RIC indication message may include a Key UE ID structure (Key UE ID structure) and an update UE ID part.
- the update UE ID part means a format defined so that only changed information can be delivered to the RIC.
- the Key UE ID structure may be in the format of FIGS. 17C and 17D .
- the updated UE ID part may be in the format of FIGS. 17E and 17F .
- the RIC indication message of the E2SM-IDM indication format 3-1 may be used in both the call setup procedure or the call release procedure. To this end, the RIC indication message of the E2SM-IDM indication format 3-1 may include an IE for indicating whether the E2 node is added (add) or released (release).
- the RIC indication message is a partial update-based O-RAN UE ID structure (O-RAN UIE ID Structure for Partial Update) may include.
- O-RAN UIE ID Structure for Partial Update may include.
- the partial update-based O-RAN UE ID structure may be in the format of FIGS. 17G and 17H .
- the RIC indication message of the E2SM-IDM indication format 3-2 may be used in both the call setup procedure or the call release procedure.
- the RIC indication message of the E2SM-IDM indication format 3-1 may include an IE for indicating whether the E2 node is added (add) or released (release).
- the number of the E2SM-IDM indication format according to the embodiments of the present disclosure is exemplary, and is not construed as limiting the embodiments of the present disclosure.
- FIGS. 17A, 17B, 17C, 17D, 17E, 17F, 17G, and 17H illustrate examples of an E2 service model (E2SM)-IDM indication message format according to various embodiments of the present disclosure.
- E2SM E2 service model
- FIGS. 17A and 17B are the format of the O-RAN UE ID structure
- FIGS. 17C and 17D are the format of the Key UE ID structure
- FIGS. 17E and 17F are the format of the updated UE ID part
- FIGS. 17G and 17D 17h illustrates the message format of the partial update based O-RAN UE ID structure.
- FIGS. 18a to 18c, 19a to 19c, and 20a to 20c illustrate a UE ID report procedure according to various embodiments of the present disclosure.
- the UE ID may be delivered to the RIC from the E2 node through RIC Indication.
- a REPORT service may be configured for RIC Indication transmission.
- 18A, 18B, and 18C illustrate examples of signaling for transmitting an E2 indication in call setup according to various embodiments of the present disclosure.
- FIG. 18A shows a UE ID report operation at the time of call setup.
- the DU may receive the DL RRC Message Transfer from the gNB CU-CP in response to the Initial UL RRC Message Transfer.
- DL RRC Message Transfer may include gNB-CU UE F1AP ID.
- the DU may deliver the gNB-CU UE F1AP ID to the RIC.
- the time of receiving the DL RRC Message Transfer is the time of acquiring the UE ID for the first time from the standpoint of the gNB-DU.
- the DU is the UE Context
- the operation of reporting the UE ID by E2 Indication may be delayed until the first setup request is received and then performed.
- the UE ID may be reported as E2 Indication. In general, this time is the point at which the Initial Context Setup Request is received, but if the AMF UE NGAP ID is obtained for the first time through DL NAS Transfer, the condition can be checked by receiving the Initial Context Setup Request and checking the relevant parameters as described in the previous DU. UE ID Report operation may be deferred until the time when the first possible message is received. Thereafter, when the condition is satisfied, the CU-CP may report the UE IE to the Near-RT RIC.
- the gNB CU-CP is a gNB-CU UE F1AP ID and a gNB-CU-CP UE E1AP ID
- E2 Indication may be transmitted to the RIC by including them.
- the gNB CU-CP is connected to the AMF.
- the gNB CU-CP may transmit AMF UE NGAP ID, which is a UE ID operated by AMF, and GUAMI, which is AMF, to RIC.
- the CU-UP may acquire the first gNB-CU-CP UE E1AP ID at the time of receiving the Bearer Context Setup Request. Since additional parameters can also be acquired at the time point, the CU-CP can report the UE ID with the E2 Indication message after the point point.
- each E2 node may report to the RIC by further including the RAN UE ID.
- the RAN UE ID may be generated by the gNB CU-CP.
- the gNB CU-CP may share the RAN UE ID by delivering the RAN UE ID to the gNB CU-UP and the gNB DU.
- gNB CU-CP is AMF (Access and Mobility management Function) UE NGAP ID, GUAMI (Globally Unique AMF ID), gNB-CU UE F1AP ID, gNB-CU-CP UE E1AP ID, in addition to the RAN UE IE RIC can report to
- the gNB CU-UP may report the RAN UE IE to the RIC in addition to the gNB-CU-CP UE E1AP ID.
- the gNB DU may report the RAN UE IE to the RIC in addition to the gNB CU F1AP ID.
- FIG. 18B shows a procedure for setting an additional PDU SESSION for a separate CU-UP #2 in a state in which call setup is performed and one PDU SESSION is preset.
- the CU-UP can report that the UE ID is set up through the normal E2 indication procedure because the E1AP logical connection is first created.
- the E1AP link is additionally setup, in this case, there is no need to re-report the previously reported part in duplicate.
- the gNB CU-CP may update the UE ID of the RIC by additionally transmitting only the added gNB-CU-CP UE E1AP ID#2 in addition to the AMF UE NGAP ID that may be the key.
- the gNB CU-CP is the message format 3-1 of FIGS. 17C, 17D, 17E, and 17F or the message format of FIGS. 17A and 17B, 17C and 17D, 17E and 17F. 3-2 may be used to update the UE ID to the RIC.
- FIG. 18c shows a case in which an SN gNB is added due to a dual connectivity procedure after call setup. If SN Addition is performed through Dual Connectivity in the CU-CP of the MN gNB, the M-NG-RAN node UE XnAP ID is transmitted through the XnAP S-NODE ADDITION REQUEST message. At that point, the MN CU-CP is set to DC, so the AMF UE NGAP ID, which is its own key id, and the M-NG_RAN node UE XnAP ID to be added are transmitted through E2 Indication through E2 Indication, and the near-RT RIC You can receive it and update it.
- the CU-CP of the SN gNB may perform call setup in its own node.
- the CU-CP of the SN gNB is near the ID generated for the F1AP logical connection and E1AP logical connection created in this process, the M-NG-RAN node UE XnAP ID that can specify itself, and its own gNB ID.
- DU and CU-UP receive F1AP UE Context Setup Request and E1AP Bearer Context Setup Request, respectively, and after the first logical connection is established and the relevant AP ID is received, the corresponding UE ID can be reported with near-RT RIC through E2 Indication. have.
- FIGS. 19A, 19B, and 19C show examples of signaling for transmitting an E2 indication according to call release according to various embodiments of the present disclosure.
- a UE ID release procedure according to call release is illustrated through FIGS. 19A to 19C .
- the time point is generally after the point at which the AP ID assigned to each node is retrieved, and in some cases, it may be triggered even when the UE ID report condition is not satisfied.
- the gNB CU-CP receives UE Context Release Complete or Bearer Context Release Complete from each DU and CU-UP, or the related timer takes a timeout to release the call.
- E2 Indication can be transmitted to the near RT RIC immediately after the point in time or when the NGAP logical connection is cut by reporting UE Context Release Complete to AMF.
- the corresponding E2 Indication may be configured to indicate that the corresponding UE ID is released. At this time, even if release is processed by sending only the AMF UE NGAP ID corresponding to the key of the UE ID, there is no problem in bundling and deleting other UE ID related parts of the CU-CP. For efficiency, only the AMF UE NGAP ID, which is the key ID, is used. A report is sufficient.
- the embodiments of the present disclosure are characterized by using the UE ID of the upper node of the specific E2 node as the Key UE ID of the specific E2 node.
- the operation principle of the upper node and the lower node is described in detail with reference to FIG. 21 .
- the CU-UP after receiving the Bearer Context Release Command and recovering the E1AP ID, the CU-UP reports the UE ID release to the Near-RT RI through E2 Indication.
- 19B shows a case in which the E1AP logical connection between a specific CU-UP#2 and a CU-CP is disconnected through PDU SESSION Release.
- CU-UP reports UE ID release with E2 Indication, but CU-CP deletes one of several E1 links, so gNB-CU for E1 link in which change occurs through Partial Update - Only the CP UE E1AP ID#2 may be deleted through the E2 Indication message.
- other parts of the UE ID of the CU-CP are not changed. Therefore, by transmitting the E2 Indication using only the AMF UE NGAP ID corresponding to the key instead of the entire ID, efficiency can be maximized.
- FIG. 19C illustrates a case in which NR-DC is released, and a case in which UE Context Release is transmitted through XnAP.
- a partial update operation may be performed to delete the M-NG-RAN node UE XnAP ID through E2 Indication.
- each E2 node may report release of UE ID through E2 Indication when related release.
- 20A to 20C illustrate examples of signaling for transmitting an E2 indication through a RAN UE ID according to various embodiments of the present disclosure.
- the gNB-CU-CP may generate a RAN UE ID and share it with other E2 nodes (eg, gNB-CU-UP, gNB-DU).
- E2 nodes eg, gNB-CU-UP, gNB-DU.
- the RAN UE ID as a Key, it is possible to increase the efficiency of message delivery.
- 20a to 20c show SN CU-CP, DU, CU-UP according to SgNB release due to call release, E1 link release with CU-UP due to PDU Session Release, and SgNB release due to NR-DC release as previously described in FIGS. 19a to 19c.
- the UE ID structure according to the embodiments of the present disclosure indicates the association between UE IDs for each E2 node as UE IDs managed for each E2 node are defined.
- the E2 node may be O-DU, O-CU, O-CU-CP, or O-CU-UP. Meanwhile, this exemplifies the distributed base station deployment of gNB, and according to another embodiment, the E2 node may include base stations such as eNB, ng-eNB, and en-gNB.
- the UE ID structure according to the embodiments of the present disclosure may provide high efficiency of E2 Indication delivery through the Key UE ID defined in the E2 node. That is, when establishing or releasing a call, instead of always reporting all UE IDs of each of the related E2 nodes to the RIC, if possible, by transmitting the Key UE ID, the efficiency of E2 Indication delivery can be increased. Near RT RIC can efficiently acquire desired information by acquiring a Key UE ID.
- the Key UE ID delivery method can be supplemented by separately or through the same field to obtain information on the updated UE ID in addition to the Key UE ID.
- the O-CU-CP of the MN may be connected through the AMF and the NGAP interface.
- the MN's O-CU-CP may use the RAN UE NGAP ID as a Key UE ID.
- the O-DU of the MN may be connected to the O-CU-CP through the F1AP interface.
- the MN's O-DU may use the RAN UE F1AP ID as a Key UE ID.
- the RAN UE F1AP ID may be managed in the form of a list.
- the list may include one or a plurality of RAN UE F1AP IDs.
- the MN's O-CU-UP may be connected to the O-CU-CP through an E1AP interface.
- the MN's O-CU-UP may use the RAN UE E1AP ID as a Key UE ID.
- the RAN UE E1AP ID may be managed in the form of a list.
- the list may include one or a plurality of RAN UE E1AP IDs.
- the SN when Dual Connectivity is configured, the SN may be connected to the MN.
- the upper node of the SN may be the MN.
- the O-CU-CP of the SN may be connected to the O-CU-CP of the MN through an XnAP interface.
- the O-CU-CP of the SN may use the M-NG RAN node UE XnAP ID as a Key UE ID.
- MN may mean gNB (or gNB-CU/gNB-DU).
- the RAN UE ID generated by the O-CU-CP may be used as the Key UE ID according to embodiments of the present disclosure. That is, the RAN UE ID generated by the O-CU-CP may be delivered to the lower nodes O-DU and O-CU-UP. The RAN UE ID may serve as a Key ID for each E2 node. Each E2 node may report the RAN UE ID to the Near RT RIC. However, since the RAN UE ID is not transmitted on the XnAP or X2AP interface, in a situation such as dual connectivity, the MN and the SN may include independent UE IDs. That is, referring to FIG.
- the MN's O-CU-CP, O-CU-UP, and O-D each key the RAN UE ID for the MN (that is, the UE ID generated by the MN's O-CU-CP).
- the O-CU-CP, O-CU-UP, and O-D of the SN each use the RAN UE ID for the SN (that is, the UE ID generated by the O-CU-CP of the SN) as the Key UE ID. is available as
- IPC cost may be reduced.
- the cost for message relay may be reduced. Since RIC performs everything except message delivery, interoperability problems between vendors can be resolved.
- an intelligent function of the RIC may be upgraded to replace a specific function between DUs and CU-UPs.
- a computer-readable storage medium storing one or more programs (software modules) may be provided.
- One or more programs stored in the computer-readable storage medium are configured to be executable by one or more processors in an electronic device (device).
- One or more programs include instructions for causing an electronic device to execute methods according to embodiments described in a claim or specification of the present disclosure.
- Such programs include random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable ROM (electrically erasable programmable read only memory, EEPROM), magnetic disc storage device, compact disc-ROM (CD-ROM), digital versatile discs (DVDs), or other It may be stored in an optical storage device or a magnetic cassette. Alternatively, it may be stored in a memory composed of a combination of some or all thereof. In addition, each configuration memory may be included in plurality.
- non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable ROM (electrically erasable programmable read only memory, EEPROM), magnetic disc storage device, compact disc-ROM (CD-ROM), digital versatile discs (DVDs), or other It may be stored in an optical storage device or a magnetic cassette. Alternatively, it may be stored in a memory composed of a combination of some or all thereof. In addition, each configuration memory may be included in plurality.
- the program is transmitted through a communication network consisting of a communication network such as the Internet, an intranet, a local area network (LAN), a wide area network (WAN), or a storage area network (SAN), or a combination thereof. It may be stored on an attachable storage device that can be accessed. Such a storage device may be connected to a device implementing an embodiment of the present disclosure through an external port. In addition, a separate storage device on the communication network may be connected to the device implementing the embodiment of the present disclosure.
- a communication network such as the Internet, an intranet, a local area network (LAN), a wide area network (WAN), or a storage area network (SAN), or a combination thereof. It may be stored on an attachable storage device that can be accessed.
- Such a storage device may be connected to a device implementing an embodiment of the present disclosure through an external port.
- a separate storage device on the communication network may be connected to the device implementing the embodiment of the present disclosure.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
도 17a, 17b, 17c, 17d, 17e, 17f, 17g 및 17h는 본 개시의 다양한 실시 예들에 따른 E2SM(E2 service model)-IDM 지시(indication) 메시지 포맷의 예들을 도시한다.
If Triggering Condition (SPID) | "Equal" | (Triggering Condi tion Value, '255') |
If Triggering Condition (SPID) | "Greater Than" | (Triggering Condition Value, '5') |
도 16a를 참고하면, 본 개시의 실시 예들에 따라, E2SM-IDM indication 포맷 1의 경우, RIC 지시 메시지는 O-RAN UE ID 구조(O-RAN UE ID structure)를 포함할 수 있다. O-RAN UE ID 구조의 IE("O-RAN UE ID structure")는 E2 노드에서 정의될 수 있는 모든 유형의 UE ID를 포함하도록 설계된 포맷을 가질 수 있다. O-RAN UE ID 구조는 호 설정(call setup) 절차에서 이용될 수 있다. 일 실시 예에 따라, O-RAN UE ID 구조는 도 17a 및 17b의 포맷일 수 있다.
도 16c를 참고하면, 본 개시의 실시 예들에 따를 때, E2SM-IDM indication 포맷 3-1의 경우, RIC 지시 메시지는 Key UE ID 구조(Key UE ID structure)와 업데이트 UE ID 파트를 포함할 수 있다. 여기서, 업데이트 UE ID 파트란, 변경된 정보만을 RIC에게 전달할 수 있도록 정의된 포맷을 의미한다. 일 실시 예에 따라, Key UE ID 구조(Key UE ID structure)는 도 17c, 도 17d의 포맷일 수 있다. 또한, 일 실시 예에 따라, 업데이트 UE ID 파트는 도 17e 및 도 17f의 포맷일 수 있다. E2SM-IDM indication 포맷 3-1의 RIC 지시 메시지는 호 설정 절차 혹은 호 해제 절차 모두에서 이용될 수 있다. 이를 위해, E2SM-IDM indication 포맷 3-1의 RIC 지시 메시지는 E2 노드의 추가(add)인지 해제(release)인지를 나타내기 위한 IE를 포함할 수 있다.
도 16d를 참고하면, 본 개시의 실시 예들에 따를 때, E2SM-IDM indication 포맷 3-2의 경우, RIC 지시 메시지는 부분 업데이트 기반 O-RAN UE ID 구조(O-RAN UIE ID Structure for Partial Update)를 포함할 수 있다. 포맷 3-1의 Key UE ID 구조와 업데이트 UE ID 파트는 별도의 필드로 정의되는 대신에, 포맷 3-2에서는 두 정보들이 하나의 필드에 정의될 수 있다. 일 실시 예에 따라, 부분 업데이트 기반 O-RAN UE ID 구조는 도 17g 및 도 17h의 포맷일 수 있다. E2SM-IDM indication 포맷 3-2의 RIC 지시 메시지는 호 설정 절차 혹은 호 해제 절차 모두에서 이용될 수 있다. 이를 위해, E2SM-IDM indication 포맷 3-1의 RIC 지시 메시지는 E2 노드의 추가(add)인지 해제(release)인지를 나타내기 위한 IE를 포함할 수 있다.
도 17a, 도 17b, 도 17c, 도 17d, 도 17e, 도 17f, 도 17g, 및 도 17h는 본 개시의 다양한 실시 예들에 따른 E2SM(E2 service model)-IDM 지시(indication) 메시지 포맷의 예들을 도시한다. 상술한 바와 같이, 도 17a 및 도 17b는 O-RAN UE ID 구조의 포맷, 도 17c 및 도 17d는 Key UE ID 구조의 포맷, 도 17e 및 도 17f는 업데이트 UE ID 파트의 포맷, 도 17g 및 도 17h는 부분 업데이트 기반 O-RAN UE ID 구조의 메시지 포맷을 예시한다.
도 18b를 참고하면, 도 18b는 먼저 Call setup 이 되고 1개의 PDU SESSION이 기 설정된 상태에서, 추가적인 PDU SESSION을 별도의 CU-UP #2에 대해 설정하는 절차를 도시한다. 이 경우 CU-UP는 최초로 E1AP logical connection 이 생성되므로 통상적인 E2 Indication 절차를 통해 UE ID 가 setup 되었음을 report 할 수 있다. 다만 CU-CP의 경우는 E1AP link 가 추가 setup 되므로, 이 경우 기존에 이미 report 했던 부분은 중복으로 다시 report 할 필요가 없게 된다. 따라서, gNB CU-CP는 key 가 될 수 있는 AMF UE NGAP ID 외에, 추가되는 gNB-CU-CP UE E1AP ID#2 만 부가적으로 전송함으로써, RIC의 UE ID를 update할 수 있다. 일 실시 예에 따라, gNB CU-CP는 도 17c, 도 17d, 도 17e, 및 도 17f의 메시지 포맷 3-1 혹은 도 17a 및 도 17b, 도 17c 및 도 17d, 도 17e 및 도 17f의 메시지 포맷 3-2를 이용하여, RIC에게 UE ID를 업데이트할 수 있다.
Node | Key ID for E2 UE ID |
AMF | N/A for RIC |
O-CU-CP | AMF UE NGAP ID, GUAMI (key) gNB-CU UE F1AP ID list gNB-CU-CP UE E1AP ID list M-NG-RAN node UE XnAP ID |
O-CU-UP | gNB-CU-CP UE E1AP ID (key) |
O-DU | gNB-CU UE F1AP ID (key) |
SgNB (CU-CP) | M-NG-RAN node UE XnAP ID, gNB ID (key) |
MN / SN gNB (CP,UP,DU) | RAN UE ID (if exist) |
Claims (8)
- E2 노드에 의해 수행되는 방법에 있어서,가입 요청 메시지를 RIC(RAN(radio access network) intelligent controller)로부터 수신하는 과정과,가입 응답 메시지를 상기 RIC에게 전송하는 과정과,상기 가입 응답 메시지에 따른 이벤트가 발생하는 경우, RIC 지시(indication) 메시지를 상기 RIC에게 전송하는 과정과 포함하고,상기 RIC 지시 메시지는 상기 E2 노드와 연관된 상위 노드에서 운용되는 UE(user equipment) ID(identifier)를 포함하는 방법.
- 청구항 1에 있어서,상기 E2 노드가 CU(central unit)-CP(control plane)인 경우, 상기 상위 노드는 상기 CU-CP가 연결된 AMF(Access and Mobility management Function)이고,상기 E2 노드가 CU-UP(user plane)인 경우, 상기 상위 노드는 상기 CU-UP가 연결된 CU-CP이고,상기 E2 노드가 DU(distributed unit)인 경우, 상기 상위 노드는 상기 DU가 연결된 CU-CP인 방법.
- RIC(RAN(radio access network) intelligent controller)에 의해 수행되는 방법에 있어서,가입 요청 메시지를 E2 노드에게 전송하는 과정과,가입 응답 메시지를 상기 E2 노드로부터 수신하는 과정과,상기 가입 응답 메시지에 따른 이벤트가 발생하는 경우 전송되는, RIC 지시(indication) 메시지를 상기 E2 노드로부터 수신하는 과정을 포함하고,상기 RIC 지시 메시지는 상기 E2 노드와 연관된 상위 노드에서 운용되는 UE(user equipment) ID(identifier)를 포함하는 방법.
- 청구항 3에 있어서,상기 E2 노드가 CU(central unit)-CP(control plane)인 경우, 상기 상위 노드는 상기 CU-CP가 연결된 AMF(Access and Mobility management Function)이고,상기 E2 노드가 CU-UP(user plane)인 경우, 상기 상위 노드는 상기 CU-UP가 연결된 CU-CP이고,상기 E2 노드가 DU(distributed unit)인 경우, 상기 상위 노드는 상기 DU가 연결된 CU-CP인 방법.
- E2 노드에 의해 수행되는 장치에 있어서,적어도 하나의 송수신기와,적어도 하나의 프로세서를 포함하고,상기 적어도 하나의 프로세서는, 상기 적어도 하나의 송수신기가,가입 요청 메시지를 RIC(RAN(radio access network) intelligent controller)로부터 수신하고,가입 응답 메시지를 상기 RIC에게 전송하고,상기 가입 응답 메시지에 따른 이벤트가 발생하는 경우, RIC 지시(indication) 메시지를 상기 RIC에게 전송하도록 제어하고,상기 RIC 지시 메시지는 상기 E2 노드와 연관된 상위 노드에서 운용되는 UE(user equipment) ID(identifier)를 포함하는 장치.
- 청구항 5에 있어서,상기 E2 노드가 CU(central unit)-CP(control plane)인 경우, 상기 상위 노드는 상기 CU-CP가 연결된 AMF(Access and Mobility management Function)이고,상기 E2 노드가 CU-UP(user plane)인 경우, 상기 상위 노드는 상기 CU-UP가 연결된 CU-CP이고,상기 E2 노드가 DU(distributed unit)인 경우, 상기 상위 노드는 상기 DU가 연결된 CU-CP인 장치.
- RIC(RAN(radio access network) intelligent controller)에 의해 수행되는 장치에 있어서,적어도 하나의 송수신기와,적어도 하나의 프로세서를 포함하고,상기 적어도 하나의 프로세서는, 상기 적어도 하나의 송수신기가,가입 요청 메시지를 E2 노드에게 전송하고,가입 응답 메시지를 상기 E2 노드로부터 수신하고,상기 가입 응답 메시지에 따른 이벤트가 발생하는 경우 전송되는, RIC 지시(indication) 메시지를 상기 E2 노드로부터 수신하도록 제어하고,상기 RIC 지시 메시지는 상기 E2 노드와 연관된 상위 노드에서 운용되는 UE(user equipment) ID(identifier)를 포함하는 장치.
- 청구항 7에 있어서,상기 E2 노드가 CU(central unit)-CP(control plane)인 경우, 상기 상위 노드는 상기 CU-CP가 연결된 AMF(Access and Mobility management Function)이고,상기 E2 노드가 CU-UP(user plane)인 경우, 상기 상위 노드는 상기 CU-UP가 연결된 CU-CP이고,상기 E2 노드가 DU(distributed unit)인 경우, 상기 상위 노드는 상기 DU가 연결된 CU-CP인 장치.
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP22788495.4A EP4301055A1 (en) | 2021-04-16 | 2022-04-15 | Device and method for controlling e2 node in wireless communication system |
CN202280028584.6A CN117204069A (zh) | 2021-04-16 | 2022-04-15 | 无线通信系统中用于控制e2节点的设备和方法 |
US18/149,979 US20230133083A1 (en) | 2021-04-16 | 2023-01-04 | Apparatus and method for controlling e2 node in wireless communication system |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR1020210050167A KR20220143533A (ko) | 2021-04-16 | 2021-04-16 | 무선 통신 시스템에서 e2 노드 제어를 위한 장치 및 방법 |
KR10-2021-0050167 | 2021-04-16 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US18/149,979 Continuation US20230133083A1 (en) | 2021-04-16 | 2023-01-04 | Apparatus and method for controlling e2 node in wireless communication system |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022220640A1 true WO2022220640A1 (ko) | 2022-10-20 |
Family
ID=83640844
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/KR2022/005457 WO2022220640A1 (ko) | 2021-04-16 | 2022-04-15 | 무선 통신 시스템에서 e2 노드 제어를 위한 장치 및 방법 |
Country Status (5)
Country | Link |
---|---|
US (1) | US20230133083A1 (ko) |
EP (1) | EP4301055A1 (ko) |
KR (1) | KR20220143533A (ko) |
CN (1) | CN117204069A (ko) |
WO (1) | WO2022220640A1 (ko) |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20210039311A (ko) * | 2019-10-01 | 2021-04-09 | 삼성전자주식회사 | 무선 액세스 네트워크 통신 시스템에서 e2 인터페이스를 통한 서비스 가입을 위한 장치 및 방법 |
WO2021071324A1 (ko) * | 2019-10-08 | 2021-04-15 | 삼성전자 주식회사 | 무선 액세스 네트워크 통신 시스템에서 e2 인터페이스를 통한 서비스 가입 이벤트의 릴레이를 위한 장치 및 방법 |
-
2021
- 2021-04-16 KR KR1020210050167A patent/KR20220143533A/ko active Search and Examination
-
2022
- 2022-04-15 EP EP22788495.4A patent/EP4301055A1/en active Pending
- 2022-04-15 WO PCT/KR2022/005457 patent/WO2022220640A1/ko active Application Filing
- 2022-04-15 CN CN202280028584.6A patent/CN117204069A/zh active Pending
-
2023
- 2023-01-04 US US18/149,979 patent/US20230133083A1/en active Pending
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20210039311A (ko) * | 2019-10-01 | 2021-04-09 | 삼성전자주식회사 | 무선 액세스 네트워크 통신 시스템에서 e2 인터페이스를 통한 서비스 가입을 위한 장치 및 방법 |
WO2021071324A1 (ko) * | 2019-10-08 | 2021-04-15 | 삼성전자 주식회사 | 무선 액세스 네트워크 통신 시스템에서 e2 인터페이스를 통한 서비스 가입 이벤트의 릴레이를 위한 장치 및 방법 |
Non-Patent Citations (3)
Title |
---|
ANONYMOUS: "O-RAN Working Group 3, Near-Real-time RAN Intelligent Controller E2 Service Model (E2SM), RAN Function Network Interface (NI)", ORAN-WG3.E2SM-NI-V01.00.00 TECHNICAL SPECIFICATION, O-RAN, no. ORAN-WG3.E2SM-NI-v01.00.00, 31 January 2020 (2020-01-31), pages 1 - 45, XP009539594 * |
ANONYMOUS: "ORAN-WG3.E2AP-v01.00.00 Technical Specification; O-RAN Working Group 3, Near-Real-time RAN Intelligent Controller, E2 Application Protocol (E2AP)", O-RAN TECHNICAL SPECIFICATION WG3: NEAR-REAL-TIME RIC AND E2 INTERFACE WORKGROUP; ORAN-WG3.E2AP-V01.00.00, O-RAN, 1 February 2020 (2020-02-01), pages 1 - 67, XP055977471, Retrieved from the Internet <URL:https://orandownloadsweb.azurewebsites.net/specifications> [retrieved on 20221103] * |
AT&T: "Traffic Steering xApp and Data Design – Bronze Release", RIC APPLICATIONS, O-RAN SOFTWARE COMMUNITY, 26 March 2020 (2020-03-26), pages 1 - 19, XP055977465, Retrieved from the Internet <URL:https://wiki.o-ran-sc.org/display/RICA/Traffic+Steering+Use+Case+xApps> [retrieved on 20221103] * |
Also Published As
Publication number | Publication date |
---|---|
CN117204069A (zh) | 2023-12-08 |
EP4301055A1 (en) | 2024-01-03 |
US20230133083A1 (en) | 2023-05-04 |
KR20220143533A (ko) | 2022-10-25 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2021066587A1 (ko) | 무선 액세스 네트워크 통신 시스템에서 e2 인터페이스를 통한 서비스 가입을 위한 장치 및 방법 | |
WO2021066588A1 (ko) | 무선 액세스 네트워크 통신 시스템에서 e2 인터페이스를 통한 서비스 가입을 위한 장치 및 방법 | |
WO2019172629A1 (ko) | 무선 통신 시스템에서 무선 접속 기술을 스위칭하기 위한 장치 및 방법 | |
WO2021118281A1 (ko) | 무선 접속 망에서 셀 정보를 포함하는 e2 인터페이스 설정을 위한 장치 및 방법 | |
WO2021101355A1 (ko) | 무선 접속 망에서 운영자 특정 서비스를 지원하기 위한 장치 및 방법 | |
WO2022177333A1 (ko) | 무선 액세스 네트워크에서 셀 정보와 e2 인터페이스 셋업을 위한 장치 및 방법 | |
WO2017026849A1 (en) | Method and apparatus for self-configuration and self-optimization in a wireless communication system | |
EP3482576A1 (en) | Method and apparatus for controlling or paging a user equipment | |
WO2018030859A1 (en) | Method and apparatus for controlling or paging a user equipment | |
WO2023027531A1 (ko) | 무선 통신 시스템에서 e2 노드 제어 및 셀 제어를 위한 장치 및 방법 | |
WO2023153662A1 (ko) | 무선 통신 시스템에서, 네트워크 슬라이스 경로 품질을 측정 및 모니터링하기 위한 장치 및 방법 | |
WO2023146314A1 (en) | Communication method and device for xr service in wireless communication system | |
WO2022220640A1 (ko) | 무선 통신 시스템에서 e2 노드 제어를 위한 장치 및 방법 | |
WO2023059036A1 (en) | Communication method and device in wireless communication system supporting unmanned aerial system service | |
WO2022039582A1 (ko) | 무선 통신 시스템에서 성능 측정을 위한 장치 및 방법 | |
WO2022240185A1 (en) | Method and apparatus to enhance on quality of experience in the mobile communications | |
WO2022098174A1 (ko) | 무선 통신 시스템에서 e2 노드 제어를 위한 장치 및 방법 | |
WO2022211467A1 (ko) | 무선 통신 시스템에서 e2 노드 제어를 위한 장치 및 방법 | |
WO2022092981A1 (ko) | 무선 통신 시스템에서 e2 노드 제어를 위한 장치 및 방법 | |
EP3286947A1 (en) | Method and apparatus for self-configuration and self-optimization in a wireless communication system | |
WO2023014087A1 (ko) | 무선 액세스 네트워크에서 e2 인터페이스 관련 정보를 제거하기 위한 장치 및 방법 | |
WO2024039028A1 (ko) | 규격 버전을 제공하기 위한 장치 및 방법 | |
WO2024071762A1 (ko) | 가입 검사를 위한 전자 장치 및 방법 | |
WO2023282584A1 (ko) | 무선 통신 시스템에서 사용자 장비를 관리하기 위한 장치 및 방법 | |
WO2022231245A1 (ko) | 무선 통신 시스템에서 e2 노드 제어를 위한 장치 및 방법 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 22788495 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2022788495 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 2022788495 Country of ref document: EP Effective date: 20230928 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 202280028584.6 Country of ref document: CN |
|
NENP | Non-entry into the national phase |
Ref country code: DE |