WO2023014087A1 - 무선 액세스 네트워크에서 e2 인터페이스 관련 정보를 제거하기 위한 장치 및 방법 - Google Patents
무선 액세스 네트워크에서 e2 인터페이스 관련 정보를 제거하기 위한 장치 및 방법 Download PDFInfo
- Publication number
- WO2023014087A1 WO2023014087A1 PCT/KR2022/011487 KR2022011487W WO2023014087A1 WO 2023014087 A1 WO2023014087 A1 WO 2023014087A1 KR 2022011487 W KR2022011487 W KR 2022011487W WO 2023014087 A1 WO2023014087 A1 WO 2023014087A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- node
- ric
- interface
- message
- smo
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 101
- 230000004044 response Effects 0.000 claims abstract description 60
- 230000005540 biological transmission Effects 0.000 claims abstract description 30
- 230000008569 process Effects 0.000 claims description 20
- 238000001514 detection method Methods 0.000 claims description 9
- 238000004891 communication Methods 0.000 abstract description 36
- 230000006870 function Effects 0.000 description 54
- 238000012790 confirmation Methods 0.000 description 44
- 238000005516 engineering process Methods 0.000 description 38
- 238000007726 management method Methods 0.000 description 26
- 239000013256 coordination polymer Substances 0.000 description 23
- 238000010295 mobile communication Methods 0.000 description 18
- 238000013473 artificial intelligence Methods 0.000 description 10
- 238000013468 resource allocation Methods 0.000 description 10
- 238000010801 machine learning Methods 0.000 description 9
- 230000015654 memory Effects 0.000 description 9
- 238000000926 separation method Methods 0.000 description 8
- 230000011664 signaling Effects 0.000 description 8
- 230000009977 dual effect Effects 0.000 description 7
- 101100194706 Mus musculus Arhgap32 gene Proteins 0.000 description 6
- 101100194707 Xenopus laevis arhgap32 gene Proteins 0.000 description 6
- 239000000969 carrier Substances 0.000 description 6
- 238000005457 optimization Methods 0.000 description 6
- 238000012217 deletion Methods 0.000 description 5
- 230000037430 deletion Effects 0.000 description 5
- 238000007630 basic procedure Methods 0.000 description 4
- 230000008901 benefit Effects 0.000 description 3
- 230000001276 controlling effect Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 230000002159 abnormal effect Effects 0.000 description 2
- 230000002776 aggregation Effects 0.000 description 2
- 238000004220 aggregation Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000014509 gene expression Effects 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 238000011160 research Methods 0.000 description 2
- 230000008685 targeting Effects 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 238000004873 anchoring Methods 0.000 description 1
- 230000003190 augmentative effect Effects 0.000 description 1
- 239000003795 chemical substances by application Substances 0.000 description 1
- 238000007405 data analysis Methods 0.000 description 1
- 238000013480 data collection Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000005259 measurement 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
- 238000007781 pre-processing Methods 0.000 description 1
- 230000009467 reduction Effects 0.000 description 1
- 230000001105 regulatory effect Effects 0.000 description 1
- 229910052710 silicon Inorganic materials 0.000 description 1
- 239000010703 silicon Substances 0.000 description 1
- 238000012549 training Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/30—Connection release
- H04W76/34—Selective release of ongoing connections
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/30—Connection release
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/30—Connection release
- H04W76/38—Connection release triggered by timers
-
- 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
Definitions
- the present disclosure relates to an apparatus and method for removing E2 interface related information in a radio access network. More specifically, the present disclosure relates to an apparatus and method for removing E2 node-related settings, RIC-related settings, or E2 interface settings conforming to the 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 ultra-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 that is 50 times faster than 5G mobile communication technology and ultra-low latency reduced to 1/10, tera Implementations in Terahertz (THz) bands (eg, 3 terahertz bands at 95 GHz) are being considered.
- THz Terahertz
- eMBB enhanced mobile broadband
- URLLC ultra-reliable low-latency communications
- mMTC massive machine-type communications
- Beamforming and Massive MIMO to mitigate the path loss of radio waves in the ultra-high frequency band and increase the propagation distance of radio waves, with the goal of satisfying service support and performance requirements, and efficient use of ultra-high frequency resources
- numerology support multiple subcarrier interval operation, etc.
- BWP Band-Width Part
- large capacity 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, and dedicated services specialized for specific services Standardization of network slicing that provides a network has been progressed.
- LDPC Low Density Parity Check
- NR-U New Radio Unlicensed
- UE Power Saving NR terminal low power consumption technology
- NTN non-terrestrial network
- IAB Intelligent Internet of Things
- IIoT Intelligent Internet of Things
- DAPS Dual Active Protocol Stack
- 2-step random access that simplifies the random access procedure
- RACH for Standardization in the field of air interface architecture/protocol for technologies such as NR
- an architecture eg, service based architecture, service based interface
- MEC mobile edge computing
- AR augmented reality
- VR virtual reality
- MR mixed reality
- XR extended reality
- AI artificial intelligence
- ML machine learning
- FD-MIMO Full Dimensional MIMO
- Array Antenna for guaranteeing coverage in the terahertz band of 6G mobile communication technology.
- multi-antenna transmission technologies such as large scale antennas, metamaterial-based lenses and antennas to improve coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), RIS ( Reconfigurable Intelligent Surface) technology, as well as full duplex technology to improve frequency efficiency and system network of 6G mobile communication technology, satellite, and AI (Artificial Intelligence) are utilized from the design stage and end-to-end (End-to-End) -to-End) Development of AI-based communication technology that realizes system optimization by internalizing AI-supported functions and next-generation distributed computing technology that realizes complex services beyond the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources could be the basis for
- Embodiments of the present disclosure are intended to address at least the problems and/or disadvantages noted above and provide at least the advantages described below.
- An embodiment of the present disclosure provides an apparatus and method for removing E2 interface related information in a wireless communication system.
- a method performed by a near-real time (RT) radio access network (RIC) intelligent controller (RIC) includes receiving an E2 removal request message indicating termination of the E2 node from an E2 node through an E2 interface, the termination of the E2 node is set by Service Management and Orchestration (SMO), and the E2 node It may include transmitting an E2 removal response message through the E2 interface, and removing a setting for the E2 node in the Near-RT RIC in response to the E2 removal request message.
- SMO Service Management and Orchestration
- a method performed by a near-real time (RT) radio access network (RAN) intelligent controller (RIC) detects release of an E2 node and a stream control transmission protocol (SCTP) connection. and starting a release timer in response to detection of the release, and removing settings for the E2 node in response to expiration of the release timer.
- RT near-real time
- RAN radio access network
- SCTP stream control transmission protocol
- a method performed by a near-real time (RT) radio access network (RIC) intelligent controller (RIC) includes a process of detecting a release of a stream control transmission protocol (SCTP) connection with an E2 node, and a message for inquiring a status of the E2 node to a Service Management and Orchestration (SMO) in response to the detection of the release.
- STP stream control transmission protocol
- SMO Service Management and Orchestration
- the process of transmitting through the O1 interface, the process of receiving a response message about the state of the E2 node from the SMO through the O1 interface, and when the response message indicates the end of termination of the E2 node, the A process of removing settings for the E2 node in the Near-RT RIC may be included.
- a method performed by a near-real time (RT) radio access network (RIC) intelligent controller (RIC) includes receiving a configuration message for termination of an E2 node connected to the Near-RT RIC from Service Management and Orchestration (SMO) through an O1 interface, and responding to the configuration message to the Near-RT RIC.
- SMO Service Management and Orchestration
- a process of removing settings for the E2 node may be included.
- an apparatus performed by a near-real time (RT) radio access network (RIC) intelligent controller (RIC) includes at least one transceiver and at least one processor, wherein the at least one processor receives an E2 removal request message indicating termination of the E2 node from an E2 node through an E2 interface, and Termination of the E2 node is set by Service Management and Orchestration (SMO), an E2 removal response message is transmitted to the E2 node through the E2 interface, and in response to the E2 removal request message, the E2 node in the Near-RT RIC It can be configured to perform the removal of settings for.
- SMO Service Management and Orchestration
- an apparatus performed by a near-real time (RT) radio access network (RIC) intelligent controller (RIC) includes at least one transceiver and at least one processor, wherein the at least one processor detects release of a stream control transmission protocol (SCTP) connection with an E2 node, and in response to detection of the release, Start a release timer and, in response to expiration of the release timer, perform a removal of the configuration for the E2 node.
- SCTP stream control transmission protocol
- an apparatus performed by a near-real time (RT) radio access network (RIC) intelligent controller (RIC) includes at least one transceiver and at least one processor, wherein the at least one processor detects release of a stream control transmission protocol (SCTP) connection with an E2 node, and in response to detection of the release, A message for inquiring the status of the E2 node is transmitted to SMO (Service Management and Orchestration) through an O1 interface, a response message about the status of the E2 node is received from the SMO through an O1 interface, and the response message is When indicating the termination of the termination of the E2 node, it may be configured to perform the removal of the setting for the E2 node in the Near-RT RIC.
- SCTP stream control transmission protocol
- an apparatus performed by a near-real time (RT) radio access network (RIC) intelligent controller (RIC) includes at least one transceiver and at least one processor, and the at least one processor is configured to provide information on termination of an E2 node connected to the Near-RT RIC from a Service Management and Orchestration (SMO) through an O1 interface. It may be configured to receive a configuration message and, in response to the configuration message, perform removal of configuration for the E2 node in the Near-RT RIC.
- SMO Service Management and Orchestration
- Apparatus and method according to embodiments of the present disclosure when the E2 node is terminated, by removing E2 node-related settings in a near-real-time (NRT) radio access network (RIC) intelligent controller (RAN), Allows the NRT RIC to function effectively.
- NRT near-real-time
- RIC radio access network intelligent controller
- Apparatus and method according to embodiments of the present disclosure enable the E2 node to operate effectively by removing NRT RIC-related settings in the E2 node when NRT RIC is terminated.
- FIG. 1 illustrates an example of a 4th generation (4G) Long Term Evolution (LTE) core system according to an embodiment 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 an embodiment of the present disclosure.
- 5G 5th generation
- NSA non-standard alone
- 2B illustrates an example of an architecture for O-RAN according to an embodiment of the present disclosure.
- FIG 3 illustrates a protocol stack of an E2 application protocol message in a radio 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 radio access network according to an embodiment of the present disclosure.
- 6a and 6b illustrate 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 a RIC according to an embodiment of the present disclosure.
- 8A illustrates an implementation example of an E2 node and RIC according to an embodiment of the present disclosure.
- 8B illustrates an interface between O-RAN components according to an embodiment of the present disclosure.
- 8C illustrates an example of an SMO framework according to an embodiment of the present disclosure.
- FIG. 9 is a diagram for explaining the necessity of removing E2 interface related information according to an embodiment of the present disclosure.
- 10A illustrates an embodiment of signaling between O-RAN entities for E2 node removal according to an embodiment of the present disclosure.
- 10B illustrates another embodiment of signaling between O-RAN entities for E2 node removal according to an embodiment of the present disclosure.
- 10C illustrates another embodiment of signaling between O-RAN entities for E2 node removal according to an embodiment of the present disclosure.
- 10D illustrates another embodiment of signaling between O-RAN entities for E2 node removal according to an embodiment of the present disclosure.
- 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.
- the present disclosure provides that the RIC transmits a RIC control request message to the E2 node on the E2 interface in a radio access network, and whether the RIC control request by the E2 node was correctly made or failed, and if it failed, the reason ( It is about procedures, messages, and methods for checking reason).
- an expression of more than or less than may be used to determine whether a specific condition is satisfied or fulfilled, but this is only a description for expressing an example, and more or less description not to exclude Conditions described as 'above' may be replaced with 'exceeds', conditions described as 'below' may be replaced with 'below', and conditions described as 'above and below' may be replaced with 'above and below'.
- 3GPP is a joint research project among mobile communication-related organizations, and aims to create a 3G mobile communication system specification - globally applicable - within the scope of the International Telecommunication Union (ITU)'s IMT-2000 project. 3GPP was established in December 1998, and the 3GPP specifications are based on the advanced GSM (global system for mobile communications) specifications, and cover all of the radio, core network, and service architecture. included in the scope of standardization.
- ITU International Telecommunication Union
- an open radio access network is a 3GPP network entity (NE) and nodes constituting a base station, such as a radio unit (RU), a digital unit (DU), a central unit (CU)-control plane (CP) ), CU-UP (user plane) is newly defined as O(O-RAN)-RU, O-DU, O-CU-CP, and O-CU-UP, respectively, and NRT (near-real- time) standardized RIC (radio access network intelligent controller).
- the present disclosure is to support an operator specific service model in an E2 interface in which a RIC requests a service from O-DU, O-CU-CP or O-CU-UP.
- O-RU, O-DU, O-CU-CP, and O-CU-UP can be understood as objects constituting a RAN capable of operating according to O-RAN specifications, and are referred to as E2 nodes. can be referred to.
- An interface with objects constituting a RAN capable of operating according to O-RAN specifications between RIC and E2 nodes uses E2 application protocol (AP) (E2AP).
- E2AP E2 application protocol
- the RIC is a logical node capable of collecting information on a cell site transmitted and received between the terminal and the O-DU, O-CU-CP or O-CU-UP.
- RIC can be implemented in the form of servers centrally located in one physical location. Connections can be made between O-DU and RIC, between O-CU-CP and RIC, and between O-CU-UP and RIC through Ethernet. To this end, 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- Message specifications such as UP and definition of procedures between O-DU, O-CU-CP, O-CU-UP and RIC are required.
- differentiated service support is required for users in a virtualized network
- E2-DU for supporting services for a wide range of cell coverage by concentrating call processing messages/functions generated in O-RAN into RIC, It is necessary to define the function of E2-CU-CP and E2-CU-UP messages.
- the RIC communicates with O-DU, O-CU-CP, and O-CU-UP using the E2 interface, and can set event occurrence conditions by generating and transmitting a subscription message.
- RIC can set call processing EVENT by generating an E2 subscription request message and forwarding it to an E2 node (eg, O-CU-CP, O-CU-UP, O-DU). there is.
- the E2 node transmits the Subscription Request Response message to the RIC.
- the E2 node may transmit the current status to the RIC via an E2 indication/report.
- 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 that transmits 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 resources transmitted from RIC to O-DU.
- FIG. 1 illustrates an example of a 4 th generation (4G) Long Term Evolution (LTE) core system according to an embodiment 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 wireless access to the terminal 120 .
- the base station 110 is a device that performs scheduling by collecting status information such as a buffer status, available transmit power, and channel status of the terminal 110 .
- the base station 110 has coverage defined as a certain geographical area based on a distance over which signals can be transmitted.
- the base station 110 is connected to the MME 150 through an S1-MME interface.
- the base station 110 includes an 'access point (AP)', an 'evolved Node B (eNodeB, eNB)', a 'wireless point', and a 'transmission point' in addition to a base station. /reception point, TRP)' or other terms having an equivalent technical meaning.
- AP 'access point
- eNodeB eNodeB
- eNB 'evolved Node B
- TRP transmission point
- the terminal 120 is a device used by a user and communicates with the base station 110 through a radio channel. In some cases, the terminal 120 may be operated without user involvement. That is, at least one of the terminal 120 and the terminal 130 is a device that performs machine type communication (MTC) and may not be carried by a user.
- the terminal 120 includes 'user equipment (UE)', 'mobile station (MS)', 'subscriber station', and customer-premises equipment (CPE) in addition to the terminal. ) may be referred to as 'remote terminal', 'wireless terminal', or 'user device' or other terms having equivalent technical meaning.
- the S-GW 130 provides a data bearer and creates or controls the data bearer under the control of the MME 150 .
- the S-GW 130 processes packets arriving from the base station 110 or packets to be forwarded to the base station 110 .
- the S-GW 130 may perform an anchoring role during handover of the terminal 120 between base stations.
- the P-GW 140 may function as a connection point with an external network (eg, 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 a Quality of Service (QoS) policy of the UE 120 and manage account data.
- QoS Quality of Service
- the MME 150 manages mobility of the terminal 120 .
- the MME 150 may perform authentication and bearer management for the terminal 120 . 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 general packet radio service (GPRS) support node (SGSN).
- GPRS general packet radio service
- the HSS 160 stores key information for authentication of the terminal 120 and a subscriber profile.
- the key information and subscriber profile are transferred from the HSS 160 to the MME 150 when the terminal 120 accesses the network.
- the PCRF 170 defines rules 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 (e.g., QoS management, billing, etc.) based on the information provided from the PCRF 180. ) can be performed.
- Carrier aggregation (hereinafter referred to as 'CA') technology combines a plurality of component carriers, and a terminal transmits and receives a signal using such a plurality of component carriers at the same time, thereby frequency from the viewpoint of a terminal or a base station. It is a technology that increases the efficiency of use. Specifically, according to CA technology, a terminal and a base station can transmit and receive signals using a wideband using a plurality of component carriers in uplink (UL) and downlink (DL), respectively. At this time, each component carrier are located in different frequency bands.
- UL uplink
- DL downlink
- uplink refers to a communication link through which a terminal transmits a signal to a base station
- downlink refers to a communication link through which a base station transmits a signal to a terminal.
- the number of uplink component carriers and downlink component carriers may be different from each other.
- Dual connectivity or multi connectivity is a technology in which a terminal is connected to a plurality of different base stations and transmits and receives signals simultaneously using carriers in a plurality of base stations located in different frequency bands. It is a technology that increases the frequency use efficiency of The terminal provides service using a first base station (eg, a base station that provides service using LTE technology or 4th generation mobile communication technology) and a second base station (eg, new radio (NR) technology or 5th generation (5G) mobile communication technology)
- NR new radio
- 5G 5th generation
- a base station that provides can be simultaneously connected to transmit and receive traffic.
- frequency resources used by each base station may be located in different bands.
- NSA non-standalone
- FIG. 2A illustrates an example of a 5G NSA system according to an embodiment of the present disclosure.
- the 5G NSA system includes an NR RAN 210a, an LTE RAN 210b, a terminal 220, and an evolved packet core (EPC) 250.
- the NR RAN 210a and the LTE RAN 210b are connected to the EPC 250, and the terminal 220 can simultaneously receive services from either or both of the NR RAN 210a and the LTE RAN 210b.
- 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 '5G node (5th generation node)', 'next generation nodeB (gNB)', or other terms having equivalent technical meaning.
- the NR base station may have a structure separated into a central unit (CU) and a digital unit (DU), and the CU is divided into a control plane (CU-CP) unit and a user plane (CU-UP) unit.
- CU-CP control 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 the control plane (e.g., connection management, mobility management, etc.) can be provided.
- the terminal 220 may be provided with additional radio resources 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 evolved universal terrestrial radio access (E-UTRA)-NR dual connectivity (EN-DC).
- E-UTRA evolved universal terrestrial radio access
- 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 various other forms of multi-connection and carrier aggregation technologies.
- various embodiments can be applied even when a first system using a first communication technology and a second system using a second communication technology are implemented in one device or when a first base station and a second base station are located in the same geographical location. can
- FIG. 2B illustrates an example of an architecture for O-RAN according to an embodiment of the present disclosure.
- KPI key performance indicator
- E2-SM-KPIMON key performance indicator monitoring
- E2 node O- in multi-connectivity operation using E-UTRA and NR radio access technology While RAN Non-stand alone mode is considered, the E2 node can be assumed to be in O-RAN Stand Alone mode.
- the eNB in the deployment of the O-RAN non-standalone mode, is connected to the EPC via the S1-C/S1-U interface, and is connected to the O-CU-CP via the X2 interface.
- O-CU-CP for deployment in O-RAN standalone mode can be connected to 5GC (5G core) through 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 transmit a subscription message, an indication message, a control message, a service update message, and a service query message, It is transmitted in a higher layer of SCTP (340) and IP (330).
- 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
- RIC 440 is connected to O-CU-CP 420, O-CU-UP 410, and O-DU 430.
- the RIC 440 is a device for customizing RAN functionality for new services or regional resource optimization.
- the RIC 440 is responsible for network intelligence (e.g. policy enforcement, handover optimization), resource assurance (e.g. radio-link management, enhancement It may provide functions such as advanced self-organized-network (SON) and 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.
- an interface between O-CU-CP and DU and between O-CU-UP and DU may be referred to as an F1 interface.
- DU and O-DU, CU-CP and O-CU-CP, and CU-UP and O-CU-UP may be used interchangeably.
- FIG. 4 illustrates one RIC 440
- a plurality of RICs may exist according to various embodiments.
- a plurality of RICs may be implemented with a plurality of hardware located in the same physical location or through virtualization using one hardware.
- FIG. 5 illustrates a configuration of an apparatus according to an embodiment of the present disclosure.
- the structure illustrated in FIG. 5 can be understood as a configuration of a device having at least one function of Near-RT RIC, non-RT RIC, O-CU-CP, O-CU-UP, and O-DU of FIG. .
- Terms such as '... unit' and '... unit' used below refer to a unit that processes at least one function or operation, which may be implemented by hardware or software, or a combination of hardware and software. there is.
- 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 communicating 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. At this time, the communication unit 510 enables the core network device to communicate with other devices or systems via a backhaul connection (eg, wired backhaul or wireless backhaul) or via a network.
- a backhaul connection eg, wired backhaul or wireless backhaul
- the storage unit 520 stores data such as basic programs, application programs, and setting information for the operation of the core network device.
- the storage unit 520 may include a volatile memory, a non-volatile memory, or a combination of volatile and non-volatile memories. And, 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 signals through the communication unit 510 . Also, the control unit 530 writes and reads data in the storage unit 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.
- 6a and 6b illustrate logical functions related to an E2 message of an E2 node and an RIC in a radio access network according to embodiments of the disclosure.
- the RIC 640 and the E2 node 610 may transmit or receive E2 messages to each other.
- the E2 node 610 may be an O-CU-CP, O-CU-UP, O-DU, or base station.
- a communication interface of the E2 node may be determined according to the type of the E2 node 610 .
- an E2 node 610 may communicate with another E2 node 616 via 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 access and mobility function (AMF)) there is.
- NGAP next generation application protocol
- AMF access and mobility function
- E2 node 610 may include 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
- KPI monitor collection S/W is installed in the RIC 640, and the E2 node 610 generates KPI parameters and sends an E2 message including the KPI parameters to the RIC ( E2 node function 612 forwarding to E2 termination 642 located at 640).
- E2 node 610 may include radio resource management (RRM) 614 .
- the E2 node 610 may manage 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, and performs a function of interpreting the E2 message delivered by the E2 node 610 and delivering it to the xApp 646. do.
- a DB (database) 644 located in the RIC 640 may be used for the E2 end 624 or xApp 616.
- the E2 node 610 shown in FIG. 6A is an end of at least one interface, and may be understood as an end of messages delivered to a terminal, a neighboring base station, and a core network.
- xAPP of RIC 640 may correspond to one or more E2 node functions of E2 node 610 .
- the E2 node function of E2 node 610 may correspond to one or more xAPPs of RIC 640 .
- E2 node functions of E2 node 610 may be managed by an E2 agent.
- the RIC 640 connected to the E2 node 610 through the E2 interface means a Near-RT RIC.
- Near-RT RIC performs data collection and control operation in units of about 10 ms (milliseconds)-1 second through the E2 interface, and the E2 node (O-CU-CP, O-CU-UP, O-DU, and O-eNB ) functions and resources can be controlled and optimized in real time, that is, near-RT.
- the RIC 640 may host one or more xApps that collect near-RT information (UE-based or cell-based) and provide services using the E2 interface.
- Near-RT RIC control for the E2 node can be adjusted based on policy and enrichment data provided through A1 in the non-RT RIC.
- the RRM function 614 between the Near-RT RIC 640 and the E2 node 610 is provided by interaction of functions of the E2 node exposed to the E2 interface through E2SM (Service Model).
- the O-RAN specification provides functional separation between the E2 node and the RIC.
- the E2 node may be a CU.
- RIC may be Near-RT RIC.
- the RIC may be connected to an open network automation platform (ONAP)/management and orchestration (MANO)/network management system (NMS) through an A1 interface.
- the RIC can be connected to the E2 node through the E2 interface.
- the E2 interface can deliver commands.
- Function separation options may include function separation 700 in which the entire radio resource management (RRM) is managed by the near-RT RIC, and function separation 750 in which RRM is selectively managed by the near-RT RIC.
- RRM radio resource management
- the Near-RT RIC will support E2 as an open logical interface targeting a multi-vendor environment independent of the specific RRC-RRM algorithm implementation located in the near-RT-RIC.
- E2SM-NI paired with an E2SM-NI capable of injecting/modifying/configurating Per UE RRC messages for each I/F and NE (network entity).
- RIC E2 Service Model Radio Interface Control
- the Near-RT RIC can be improved in the direction of functional separation 700 from functional separation 750 progressively.
- E2 is independent of any specific RRC-RRM algorithm implementation in near-RT-RIC and can evolve into an open logical interface targeting a multi-vendor environment.
- E2 nodes eg O-DU, O-CU
- RIC virtualized on a cloud platform (eg open chassis and blade specification edge cloud) and configured on a device (eg server) It can be.
- This scenario will support deployments in dense urban areas with abundant fronthaul capacity allowing BBU functions to be pooled to a central location, with low enough latency to meet O-DU latency requirements. can Thus, there may be no need to try to centralize the RIC closer to the RT beyond the limit of being able to centralize the O-DU function.
- E2SM-RIC can be optimized for O-RAN deployment scenarios in which Near-RT RIC, O-CU, and O-DU are implemented on the O-Cloud Platform.
- the Service Management and Orchestration (SMO) framework can be connected to the O-RAN NF (Network Function) and O-Cloud through the main interfaces used in the O-RAN, such as the A1 interface, the O1 interface, and the O2 interface.
- the O-RAN NF may be a Virtualized Network Function (VNF) on the O-Cloud.
- the O-RAN NF may be in the form of a containerized network function (CNF).
- the O-RAN NF may be a physical network function (PNF) utilizing customized hardware.
- SMO is responsible for RAN domain management and orchestration functions.
- the main function of SMO to provide RAN support in O-RAN is Fault, Configuration, Alarms, Performance and Security (FCAPS) interface to O-RAN NF, Non-Real Time RAN Intelligent Controller (RIC) for RAN Optimization ) framework, O-Cloud management, orchestration, and workflow management functions.
- FCAPS Fault, Configuration, Alarms, Performance and Security
- Non-RT RIC is an SMO internal function of the O-RAN architecture that provides an A1 interface to the Near-RT RIC (Near-Real Time RAN Intelligent Controller).
- the main goal of non-RT RIC is to provide policy-based guidance, ML model management and enrichment information to near-RT RIC so that RAN can optimize RRM under specific conditions. This is to support intelligent RAN optimization.
- Non-RT RIC can perform RAN optimization at non-real time (1 second or longer) intervals by using data analysis, AI (Artificial Intelligence)/ML (machine learning) training and inference.
- AI Artificial Intelligence
- ML machine learning
- 8C illustrates an example of an SMO framework according to an embodiment of the present disclosure.
- the non-RT RIC may include a UE Identity Management Function (IMF).
- IMF UE Identity Management Function
- the Non-RT RIC performs functions (or operations) of the UE IMF described later, such as a UE identifier management unit, a UE identifier control unit, a UE management unit, a UE control unit, a UE identity control unit, and a UE identification unit.
- the non-RT RIC may communicate with the SMO through the SMO internal interface. According to embodiments of the present disclosure, the non-RT RIC may communicate with an external source through an external interface. According to an embodiment, the non-RT RIC may perform communication with an external EI source through an external enrichment information (EI) interface. According to an embodiment, the non-RT RIC may communicate with an external EI source through an external artificial intelligence (AI)/machine learning (ML) interface. According to an embodiment, the non-RT RIC may perform communication with a local craft terminal through an external human machine (HM) interface.
- EI external enrichment information
- AI artificial intelligence
- ML machine learning
- HM human machine
- O-RAN brings openness, agility and scalability to the RAN.
- O-RAN enables support for open and interoperable interfaces, RAN virtualization, big data and AI-enabled RAN intelligence. It also maximizes the use of off-the-shelf hardware and off-the-shelf silicon and avoids the use of proprietary hardware.
- Embedded or back-end artificial intelligence (AI)/machine learning (ML) systems provide network intelligence through near real-time (NRT) and non-real-time (NRT) analytics.
- NRT near real-time
- NRT non-real-time
- O-RAN makes it possible to configure a virtualized intelligent network with standardized open interfaces.
- the interface between the Near-RT RIC and the E2 node is defined as the E2 interface.
- a radio network layer may use the E2AP protocol.
- the E2AP procedure consists of an E2AP Near-RT RIC functional procedure and an E2AP Global procedure.
- the E2AP Near-RT RIC functional procedure can be used to deliver application specific messages between xApp (Near-RT RIC applications) and the target function of the E2 node.
- E2AP Global procedure can be used for E2 interface management and service update.
- FIG. 9 is a diagram for explaining the necessity of removing E2 interface related information according to an embodiment of the present disclosure.
- the termination process of the E2 node is described.
- the figure below shows the termination process of the E2 node.
- the E2 termination process can be used to reduce waste of resources due to excessive deployment of E2 nodes.
- the E2 termination process is a necessary procedure to remove the old version of the E2 node due to the build-and-replace S/W upgrade method.
- SMO illustrates SMO 810 in FIG. 8 .
- O-cloud exemplifies a controller for controlling the O-cloud 815 of FIG. 8 .
- the Near-RT RIC illustrates the Near-RT RIC 640 of FIG. 6 .
- the E2 node illustrates the E2 node 610 of FIG. 6 .
- the SMO may determine to remove the E2 node.
- SMO can create settings for E2 node removal.
- the SMO may transmit configuration information for termination of the E2 node to the E2 node through the O1 interface.
- the SMO may deliver configuration information for termination to the corresponding E2 node.
- the E2 node may receive configuration information for termination of the E2 node from the SMO through the O1 interface.
- the E2 node may suspend ongoing traffic (or service). That is, the E2 node may stop traffic currently being served or service may be stopped.
- the E2 node may stop traffic or service based on the configuration information received in operation S903. For example, the E2 node may stop sending data traffic.
- the E2 node may stop transmitting traffic when receiving configuration information for termination of the E2 node.
- the E2 node may transmit an end confirmation (or notification) message (hereinafter referred to as an end confirmation message) to the SMO.
- the E2 node may send the termination confirmation message to the SMO through the O1 interface.
- SMO may receive a termination confirmation message from the E2 node.
- the confirmation message is described as being performed after operation S905 in FIG. 9, in some embodiments, the confirmation message may be performed immediately after operation S903.
- SMO may transmit a message for terminating the E2 node to O-Cloud.
- SMO can transmit a message for termination of E2 node to O-Cloud through O2 interface.
- the message for terminating the E2 node may mean a message for releasing resources of the E2 node.
- the SMO may transmit a message to release the resource of the E2 node to the O-Cloud.
- O-Cloud may receive a message for releasing E2 node resources from SMO.
- O-Cloud may transmit a message for releasing resource allocation to the E2 node.
- O-Cloud may notify the E2 node of resource deallocation through an application.
- O-Cloud may transmit a message informing that the termination of the E2 node has been completed to the SMO.
- the completion of the termination of the E2 node means that all resources allocated to the E2 node are released. That is, O-Cloud may release all resources of the E2 node and deliver a completion message to SMO.
- the E2 node may release all resources.
- the E2 node can release all resources based on O-Cloud's resource allocation. Since the E2 node can identify the termination of the E2 node through SMO and O-Cloud, the E2 node can perform procedures (eg, deletion of settings related to the E2 interface) according to the termination of the E2 node.
- the Near-RT RIC may maintain related information and the E2 interface instance.
- the Near-RT RIC does not know if the E2 node is down. Therefore, Near-RT RIC retains deleted E2 node related information (e.g. Global E2 node ID, RAN Function info, E2 node component configuration, and so on), E2 interface (e.g. SCTP connection) even if the E2 node is terminated. will continue to hold Although not shown in FIG. 9, even in the opposite case (eg, when the Near-RT RIC is removed), the E2 node continues to maintain Near-RT RIC related information and the E2 interface.
- E2 node related information e.g. Global E2 node ID, RAN Function info, E2 node component configuration, and so on
- E2 interface e.g. SCTP connection
- E2 interface-related settings e.g., E2 node-related information, Near-RT RIC-related information, or E2 interface settings
- E2 interface-related settings e.g., E2 node-related information, Near-RT RIC-related information, or E2 interface settings
- topology information may provide an incorrect result by reflecting data about a terminated E2 node.
- an error may occur because the configuration of the corresponding E2 node is duplicated in the Near-RT RIC.
- embodiments of the present disclosure provide, in an O-RAN (Open RAN) based mobile communication system, when the connection of the E2 interface between the Near-RT RIC and the E2 node is terminated, the Near-RT RIC and the E2 We propose a method for deleting (or releasing) related information, E2 interface, etc. stored in each node.
- the present disclosure when the E2 node is terminated, the present disclosure provides a method for normally deleting related information of the E2 node, E2 interface instance (eg SCTP), etc. in the Near-RT RIC Suggest.
- the present disclosure can normally delete related information of the Near-RT RIC, E2 interface instance (eg, SCTP), etc. from the E2 node when the Near-RT RIC is terminated, as in the opposite case. suggest a way to
- the E2 interface-related information may include settings related to the E2 node.
- the E2 interface related information may include Near-RT RIC related settings.
- the E2 interface-related information may include settings related to the E2 interface (eg, SCTP).
- an explicit E2AP message exchange procedure (eg, an E2 Removal Request message and an E2 Removal response message) may be defined between the E2 node and the Near-RT RIC.
- E2 AP message exchange procedure E2 interface related information may be removed. Specific operations according to the first method will be described with reference to FIG. 10A to be described later.
- a release timer may be defined. When the release timer expires, E2 interface related information may be removed. Specific operations according to the second method will be described with reference to FIG. 10B to be described later.
- an inquiry procedure to the SMO may be defined.
- the inquiry procedure to the SMO may include sending an inquiry and receiving a response by the E2 node or the Near-RT RIC.
- E2 interface related information may be removed based on a response according to an inquiry procedure to the SMO. Specific operations according to the third method will be described with reference to FIG. 10C to be described later.
- explicit configuration by SMO may be defined. Based on transmission of configuration information through the O1 interface of the SMO, E2 interface related information may be removed. Specific operations according to the fourth method will be described with reference to FIG. 10D to be described later.
- 10A illustrates an embodiment of signaling between O-RAN entities for E2 node removal according to an embodiment of the present disclosure.
- 10A shows a method for removing related information by an explicit E2AP message exchange method (E2 Removal Request/response) between an E2 node and a Near-RT RIC.
- E2 Removal Request/response E2 Removal Request/response
- the SMO may determine to remove the E2 node.
- SMO can create settings for E2 node removal.
- the SMO may transmit configuration information for termination of the E2 node to the E2 node through the O1 interface.
- the SMO may deliver configuration information for termination to the corresponding E2 node.
- the E2 node may receive configuration information for termination of the E2 node from the SMO through the O1 interface.
- the E2 node may transmit an E2 removal request message to the Near-RT RIC.
- the E2 node may send an E2 removal request to the Near-RT RIC through the E2 interface.
- an E2AP message for requesting removal of an E2 node may be defined on the E2 interface (eg, additionally defined in Table 1 or Table 2).
- the E2 node may explicitly transmit an E2 Removal Request message to the Near-RT RIC through the E2 interface.
- the Near-RT RIC can receive the E2 Removal Request message from the E2 node.
- the E2 removal request message may include an E2 node ID (identifier).
- the E2 node may notify the Near-RT RIC of the E2 node ID to be terminated.
- the E2 removal request message may include settings related to E2 node termination.
- the E2 node may additionally generate an E2 removal request message based on the configuration information received in operation S1003.
- the E2 removal response message may include the RIC node ID.
- the E2 removal response message may indicate confirmation of the removal result.
- the Near-RT RIC may transmit an E2 removal response message to the E2 node.
- an E2AP message for requesting removal of an E2 node may be defined on the E2 interface.
- the E2 node may receive the E2 removal response message from the Near-RT RIC.
- the Near-RT RIC Upon receiving the E2 Removal Request message from the E2 node, the Near-RT RIC responds with an E2 Removal Response message and then deletes information related to the corresponding E2 node.
- the Near-RT RIC may remove the E2 interface instance (eg, SCTP connection) to the corresponding E2 node in operation S1009.
- the E2 node may receive the E2 Removal Request message from the Near-RT RIC.
- the E2 node may delete E2 interface related information.
- the E2 interface-related information may include Near-RT-related settings and E2 interface instance settings connected through the E2 interface.
- the E2 node may delete the E2 interface instance after receiving the E2 Removal Response message.
- the E2 node may suspend ongoing traffic (or service). That is, the E2 node may stop traffic currently being served or service may be stopped. For example, the E2 node may stop sending data traffic. The E2 node may stop transmitting traffic when receiving configuration information for termination of the E2 node.
- the E2 node may transmit an end confirmation (or notification) message (hereinafter referred to as an end confirmation message) to the SMO.
- the E2 node may send the termination confirmation message to the SMO through the O1 interface.
- SMO may receive a termination confirmation message from the E2 node.
- SMO may transmit a message for terminating the E2 node to O-Cloud.
- SMO can transmit a message for termination of E2 node to O-Cloud through O2 interface.
- the message for terminating the E2 node may mean a message for releasing resources of the E2 node.
- the SMO may transmit a message to release the resource of the E2 node to the O-Cloud.
- O-Cloud may receive a message for releasing E2 node resources from SMO.
- O-Cloud may transmit a message for releasing resource allocation to the E2 node.
- O-Cloud may notify the E2 node of resource deallocation through an application.
- O-Cloud may transmit a message informing that the termination of the E2 node has been completed to the SMO.
- the completion of the termination of the E2 node means that all resources allocated to the E2 node are released. That is, O-Cloud may release all resources of the E2 node and deliver a completion message to SMO.
- the E2 node may release all resources.
- the E2 node can release all resources based on O-Cloud's resource allocation. Since the E2 node can identify the termination of the E2 node through SMO and O-Cloud, the E2 node can perform procedures (eg, deletion of settings related to the E2 interface) according to the termination of the E2 node.
- the Near-RT RIC since the Near-RT RIC knows the termination of the E2 node, the Near-RT RIC provides E2 node-related information (e.g., Global E2 node ID, RAN Function info, E2 node component configuration, etc.) even if the E2 node is terminated. ) may no longer be maintained. Also, Near-RT RICs do not maintain E2 interface setups (eg SCTP connections), so less unnecessary resources are wasted.
- E2 node-related information e.g., Global E2 node ID, RAN Function info, E2 node component configuration, etc.
- FIG. 10A a method for deleting E2 node-related settings and E2 interface settings from the Near-RT RIC according to the termination of the E2 node is described, but the embodiment of the present disclosure can be applied in the opposite case as well. That is, an operation of deleting Near-RT RIC-related settings and E2 interface settings in the E2 node as termination of the Near-RT RIC is determined may also be understood as an embodiment of the present disclosure.
- the Near-RT RIC when the Near-RT RIC is terminated, the Near-RT RIC may transmit a RIC removal request to the E2 node.
- the E2 node may transmit a RIC removal response to the Near-RT RIC in response to the RIC removal request.
- settings related to the E2 interface can be removed from each node.
- the E2 node may instruct the Near-RT RIC to terminate the E2 node. Without a separate response process, according to the instruction message of the E2 node, the Near-RT RIC can delete E2 node-related settings.
- transmission of the confirmation message according to operation S1013 is illustrated as being performed after operation S1011, but embodiments of the present disclosure are not unconditionally limited thereto. According to an embodiment, transmission of the confirmation message according to operation S1013 may be performed after operation S1007 and before operation S1011. According to an embodiment, transmission of the confirmation message according to operation S1013 may be performed after operation S1003.
- FIG. 10B illustrates another embodiment of signaling between O-RAN entities for E2 node removal according to an embodiment of the present disclosure.
- FIG. 10B shows a method of removing related information after releasing the SCTP connection between the E2 node and the Near-RT RIC and then terminating the release timer.
- the SMO may determine to remove the E2 node.
- SMO can create settings for E2 node removal.
- the SMO may transmit configuration information for termination of the E2 node to the E2 node through the O1 interface.
- the SMO may deliver configuration information for termination to the corresponding E2 node.
- the E2 node may receive configuration information for termination of the E2 node from the SMO through the O1 interface.
- the SCTP connection may be released.
- SCTP connection refers to the transport layer located below the E2AP layer, which is a radio network layer in the E2 interface.
- the E2 node when the E2 node receives configuration information for termination of the E2 node from the SMO, the E2 node establishes a normal release procedure (3 way handshake (SHUTDOWN/SHUTDOWN-ACK/SHUTDOWN/SHUTDOWN/SHUTDOWN/SHUTDOWN/SHUTDOWN-ACK/SHUTDOWN-ACK/SHUTDOWN -COMPLETE)).
- the SCTP connection may be terminated abnormally.
- the Near-RT RIC may delete E2 interface related information.
- the Near-RT RIC triggers a release timer when it detects a normal release or abnormal termination of the SCTP connection.
- the release timer expires, that is, after the release timer expires, the Near-RT RIC may delete related information about the corresponding E2 node and E2 interface instance information.
- the release timer may be predefined in the standard. Also, according to an embodiment, the release timer may be set through an O1 interface or an A1 interface.
- the E2 node may delete E2 interface related information.
- the E2 interface-related information may include Near-RT-related settings and E2 interface instance settings connected through the E2 interface. Additionally, the E2 node may suspend ongoing traffic (or service). That is, the E2 node may stop traffic currently being served or service may be stopped.
- the E2 node may transmit an end confirmation (or notification) message (hereinafter referred to as an end confirmation message) to the SMO.
- the E2 node may send the termination confirmation message to the SMO through the O1 interface.
- SMO may receive a termination confirmation message from the E2 node.
- SMO may transmit a message for terminating the E2 node to O-Cloud.
- SMO can transmit a message for termination of E2 node to O-Cloud through O2 interface.
- the message for terminating the E2 node may mean a message for releasing resources of the E2 node.
- the SMO may transmit a message to release the resource of the E2 node to the O-Cloud.
- O-Cloud may receive a message for releasing E2 node resources from SMO.
- O-Cloud may transmit a message for releasing resource allocation to the E2 node.
- O-Cloud may notify the E2 node of resource deallocation through an application.
- O-Cloud may transmit a message informing that termination of the E2 node has been completed to the SMO.
- the completion of the termination of the E2 node means that all resources allocated to the E2 node are released. That is, O-Cloud may release all resources of the E2 node and deliver a completion message to SMO.
- the E2 node may release all resources.
- the E2 node can release all resources based on O-Cloud's resource allocation. Since the E2 node can identify the termination of the E2 node through SMO and O-Cloud, the E2 node can perform procedures (eg, deletion of settings related to the E2 interface) according to the termination of the E2 node.
- the Near-RT RIC since the Near-RT RIC operates a release timer, the Near-RT RIC returns E2 node-related information (e.g., Global E2 node ID, RAN Function info, E2 node component configuration, etc.) when the SCTP connection is disconnected. may not hold any longer. Also, Near-RT RICs do not maintain E2 interface settings (eg SCTP connections). Due to the release timer, information about one or more E2 nodes related to the Near-RT RIC can be correctly collected, and less unnecessary resources can be wasted.
- E2 node-related information e.g., Global E2 node ID, RAN Function info, E2 node component configuration, etc.
- E2 interface settings eg SCTP connections
- the E2 node may start a release timer when the SCTP connection is released. When the release timer expires, the E2 node can remove Near-RT RIC-related settings and E2 interface instance settings.
- transmission of the confirmation message according to operation S1041 is illustrated as being performed after operation S1039, but embodiments of the present disclosure are not unconditionally limited thereto. According to an embodiment, transmission of the confirmation message according to operation S1041 may be performed after operation S1037 and before operation S1039. Alternatively, according to an embodiment, the transmission of the confirmation message according to operation S1041 may be performed after a predetermined time by a timer after the SCTP connection is released according to operation 1033 or operation S1035.
- FIG. 10C illustrates another embodiment of signaling between O-RAN entities for E2 node removal according to an embodiment of the present disclosure.
- FIG. 10C shows a method of inquiring about a peer node state through SMO after SCTP connection is disconnected between E2 node and Near-RT RIC, and then deleting related information through a response.
- the SMO may determine to remove the E2 node.
- SMO can create settings for E2 node removal.
- the SMO may transmit configuration information for termination of the E2 node to the E2 node through the O1 interface.
- the SMO may deliver configuration information for termination to the corresponding E2 node.
- the E2 node may receive configuration information for termination of the E2 node from the SMO through the O1 interface.
- SCTP connection refers to the transport layer located below the E2AP layer, which is a radio network layer in the E2 interface.
- the E2 node when the E2 node receives configuration information for termination of the E2 node from the SMO, the E2 node establishes a normal release procedure (3 way handshake (SHUTDOWN/SHUTDOWN-ACK/SHUTDOWN/SHUTDOWN/SHUTDOWN/SHUTDOWN/SHUTDOWN-ACK/SHUTDOWN-ACK/SHUTDOWN -COMPLETE)).
- a normal release procedure (3 way handshake (SHUTDOWN/SHUTDOWN-ACK/SHUTDOWN/SHUTDOWN/SHUTDOWN/SHUTDOWN/SHUTDOWN-ACK/SHUTDOWN -COMPLETE)
- the SCTP connection may be terminated abnormally.
- the Near-RT RIC may transmit a message for querying the status of the E2 node to the SMO.
- the Near-RT RIC detects a normal release or abnormal termination of the SCTP connection, it sends a query to SMO indicating whether the corresponding E2 node is in the process of termination.
- the inquiry message may be transmitted in response to detection of release of the SCTP connection.
- the Near-RT RIC may transmit the inquiry message to the SMO through the O1 interface.
- the SMO may receive a message for querying the status of the E2 node from the Near-RT RIC.
- the SMO may transmit a response message including the status of the E2 node to the Near-RT RIC.
- the Near-RT RIC may receive a response from the SMO indicating that the E2 node is in the process of being terminated.
- the Near-RT RIC may delete E2 interface related information. After the Near-RT RIC receives the response message, the Near-RT RIC may delete related information about the corresponding E2 node and E2 interface instance information.
- the E2 node may delete E2 interface related information.
- the E2 interface-related information may include Near-RT-related settings and E2 interface instance settings connected through the E2 interface. Additionally, the E2 node may suspend ongoing traffic (or service). That is, the E2 node may stop traffic currently being served or service may be stopped.
- the E2 node may transmit an end confirmation (or notification) message (hereinafter referred to as an end confirmation message) to the SMO.
- the E2 node may send the termination confirmation message to the SMO through the O1 interface.
- SMO may receive a termination confirmation message from the E2 node.
- SMO may transmit a message for terminating the E2 node to O-Cloud.
- SMO can transmit a message for termination of E2 node to O-Cloud through O2 interface.
- the message for terminating the E2 node may mean a message for releasing resources of the E2 node.
- the SMO may transmit a message to release the resource of the E2 node to the O-Cloud.
- O-Cloud may receive a message for releasing E2 node resources from SMO.
- O-Cloud may transmit a message for releasing resource allocation to the E2 node.
- O-Cloud may notify the E2 node of resource deallocation through an application.
- O-Cloud may transmit a message informing that the termination of the E2 node has been completed to the SMO.
- the completion of the termination of the E2 node means that all resources allocated to the E2 node are released. That is, O-Cloud may release all resources of the E2 node and deliver a completion message to SMO.
- the E2 node may release all resources.
- the E2 node can release all resources based on O-Cloud's resource allocation. Since the E2 node can identify the termination of the E2 node through SMO and O-Cloud, the E2 node can perform procedures (eg, deletion of settings related to the E2 interface) according to the termination of the E2 node.
- the Near-RT RIC since the Near-RT RIC directly inquires the SMO, the Near-RT RIC receives E2 node-related information (e.g., Global E2 node ID, RAN Function info, E2 node component configuration, etc.) when the SCTP connection is disconnected. ) may no longer be maintained. Also, Near-RT RICs do not maintain E2 interface settings (eg SCTP connections). Information on one or more E2 nodes related to the Near-RT RIC can be correctly collected and less unnecessary resources can be wasted through the E2 node exit status inquiry procedure through the O1 interface.
- E2 node-related information e.g., Global E2 node ID, RAN Function info, E2 node component configuration, etc.
- E2 interface settings eg SCTP connections
- the E2 node may inquire the SMO about the status of the Near-RT RIC through the O1 interface.
- the E2 node may receive a response message from the SMO indicating that the Near-RT RIC is being terminated.
- the E2 node may remove Near-RT RIC-related settings and E2 interface instance settings in response to the response message.
- transmission of the confirmation message according to operation S1065 is illustrated as being performed after operation S1063, but embodiments of the present disclosure are not unconditionally limited thereto. According to an embodiment, transmission of the confirmation message according to operation S1065 may be performed after operation S1061 and before operation S1063. Alternatively, according to an embodiment, transmission of the confirmation message according to operation S1041 may be performed after a predetermined time after the SCTP connection is released according to operation 1053 or operation S1055.
- 10D illustrates another embodiment of signaling between O-RAN entities for E2 node removal according to an embodiment of the present disclosure.
- 10D shows a method of deleting related information by explicitly transferring information to E2 node and Near-RT RIC by SMO.
- the SMO may determine to remove the E2 node.
- SMO can create settings for E2 node removal.
- the SMO may transmit configuration information for termination of the E2 node to the E2 node through the O1 interface.
- the SMO may deliver configuration information for termination to the corresponding E2 node.
- the E2 node may receive configuration information for termination of the E2 node from the SMO through the O1 interface.
- the SMO may transmit a configuration message regarding termination of the E2 node to the Near-RT RIC through the O1 interface.
- the SMO may transmit a configuration message notifying the Near-RT RIC that the E2 node is scheduled to be terminated.
- the SMO may transmit a configuration message including configuration information related to the E2 node to be terminated to the Near-RT RIC.
- the SMO may transmit a configuration message for instructing the E2 node to be terminated to the Near-RT RIC.
- SMO can identify the Near-RT RIC connected to the E2 node that is the target of termination. Since there may be one or more E2 nodes connected to the Near-RT RIC, the transport configuration message may include E2 node identification information (eg, E2 node ID) to indicate the E2 node that is the target of termination.
- E2 node identification information eg, E2 node ID
- SMO When SMO transfers configuration information to terminate an E2 node, SMO may send a message to the Near-RT RIC connected to the corresponding E2 node to remove related information of the E2 node and the E2 interface interface.
- the Near-RT RIC may delete E2 interface related information. Upon receiving the message, the Near-RT RIC deletes the information related to the corresponding E2 node.
- the E2 node may delete E2 interface related information.
- the E2 interface-related information may include Near-RT-related settings and E2 interface instance settings connected through the E2 interface. Additionally, the E2 node may suspend ongoing traffic (or service). That is, the E2 node may stop traffic currently being served or service may be stopped.
- the E2 node may transmit an end confirmation (or notification) message (hereinafter referred to as an end confirmation message) to the SMO.
- the E2 node may send the termination confirmation message to the SMO through the O1 interface.
- SMO may receive a termination confirmation message from the E2 node.
- the Near-RT RIC may transmit a message notifying confirmation of the termination of the E2 node to the SMO.
- the Near-RT RIC is a response message to the SMO operation (S1085) and may transmit a confirmation message.
- the Near-RT RIC may transmit a message notifying confirmation of the termination of the E2 node to the SMO through the O1 interface.
- SMO may receive termination confirmation message from Near-RT RIC.
- the Near-RT RIC may transmit a response message for operation S1085.
- the Near-RT RIC transmits a response message for the operation (S1085) to the E2 node immediately after the operation (S0183), or according to another embodiment, the Near-RT RIC transmits the operation (S1085) to the E2 node.
- a response message to ) may be transmitted after operation S1087.
- SMO may transmit a message for terminating the E2 node to O-Cloud.
- SMO can transmit a message for termination of E2 node to O-Cloud through O2 interface.
- the message for terminating the E2 node may mean a message for releasing resources of the E2 node.
- the SMO may transmit a message to release the resource of the E2 node to the O-Cloud.
- O-Cloud may receive a message for releasing E2 node resources from SMO.
- O-Cloud may transmit a message for releasing resource allocation to the E2 node.
- O-Cloud may notify the E2 node of resource deallocation through an application.
- O-Cloud may transmit a message informing that termination of the E2 node has been completed to the SMO.
- the completion of the termination of the E2 node means that all resources allocated to the E2 node are released. That is, O-Cloud may release all resources of the E2 node and deliver a completion message to SMO.
- the E2 node may release all resources.
- the E2 node can release all resources based on O-Cloud's resource allocation. Since the E2 node can identify the termination of the E2 node through SMO and O-Cloud, the E2 node can perform procedures (eg, deletion of settings related to the E2 interface) according to the termination of the E2 node.
- the Near-RT RIC transmits E2 node-related information (e.g., Global E2 node ID, RAN Function info, E2 node component configuration, etc.) may no longer be maintained. Also, Near-RT RICs do not maintain E2 interface settings (eg SCTP connections). As the termination setting of the E2 node through the O1 interface is transmitted to all the nodes of the E2 interface, information on the E2 nodes in progress is correctly collected, and unnecessary resources can be less wasted.
- E2 node-related information e.g., Global E2 node ID, RAN Function info, E2 node component configuration, etc.
- E2 interface settings eg SCTP connections
- FIG. 10D a method for deleting E2 node-related settings and E2 interface settings from the Near-RT RIC according to the termination of the E2 node is described, but the embodiment of the present disclosure can be applied in the opposite case as well. That is, an operation of deleting Near-RT RIC-related settings and E2 interface settings in the E2 node as termination of the Near-RT RIC is determined may also be understood as an embodiment of the present disclosure.
- the SMO when termination of the Near-RT RIC is determined, the SMO not only transmits a configuration message regarding termination to the corresponding Near-RT RIC, but also one or more E2s connected to the Near-RT RIC.
- a configuration message for termination of the Near-RT RIC may be transmitted to nodes.
- FIG. 10D it is shown that the confirmation message transmission according to operation S1091 is performed after operation S1089, but embodiments of the present disclosure are not unconditionally limited thereto. According to an embodiment, transmission of the confirmation message according to operation S1091 may be performed after operation S1087 and before operation S1089. Alternatively, according to an embodiment, transmission of the confirmation message according to operation S1091 may be performed after operation S1083.
- Embodiments of the present disclosure have proposed a method for deleting information stored in a peer node when one of the E2 node providing the E2 interface and the Near-RT RIC is terminated.
- the Near-RT RIC stores related information of the E2 node to be terminated stored in the Near-RT RIC (eg, Global E2 Node ID, RAN Function info, E2 Node component configuration, RIC services REPORT/INSERT information received during the RIC Indication procedure, etc.) and E2 I/F instance information (ie, E2 node Transport Layer information) can be deleted.
- related information of the Near-RT RIC to be terminated stored in the E2 node eg, Global RIC ID, RIC subscription information received during the subscription procedure (RIC services REPORT, INSERT and/or POLICY), RIC service CONTROL information received during the control procedure, etc.
- E2 I/F instance information ie, Transport Layer information of Near-RT RIC
- the E2 interface connection between the Near-RT RIC and the E2 node is terminated in an O-RAN (Open RAN) based mobile communication system
- O-RAN Open RAN
- Settings related to the E2 interface mentioned in the above-described FIGS. 10A to 10D may be defined as follows. If the E2 node shuts down, the Near-RT RIC may remove the configuration for the E2 node. Termination of the E2 node means that the SCTP connection from the E2 node is terminated. If the Near-RT RIC is terminated, the E2 node may remove the configuration for the Near-RT RIC. That is, the settings related to the E2 interface mentioned in this disclosure may include settings for the E2 node or Near-RT RIC.
- E2 node-related settings refer to information obtained by the Near-RT RIC performing elementary procedures (eg, Tables 1 and 2) with the corresponding E2 node.
- the settings related to the E2 interface to be removed may include information acquired through a RIC subscription procedure.
- information to be removed may include RIC request ID.
- the information to be removed may include a RAN function ID.
- information to be removed may include RIC Event Trigger Definition.
- the settings related to the E2 interface to be removed may include information obtained through a RIC indication procedure.
- information to be removed may include RIC request ID.
- the information to be removed may include a RAN function ID.
- information to be removed may include a RIC Action ID.
- the information to be removed may include a RIC Call process ID.
- information to be removed may include RIC Indication Message, Type, Header, and SN.
- the settings related to the E2 interface to be removed may include information acquired through a RIC control procedure.
- information to be removed may include RIC request ID.
- the information to be removed may include a RAN function ID.
- the information to be removed may include a RIC Call process ID.
- information to be removed may include a RIC Control Message.
- the settings related to the E2 interface to be removed may include information obtained through an E2 SETUP procedure.
- information to be removed may include Global E2 node ID.
- information to be removed may include information (item, ID, definition) about a RAN function.
- information to be removed may include E2 Node Component Configuration.
- the settings related to the E2 interface to be removed may include information obtained through an E2 CONFIGURATION UPDATE procedure.
- information to be removed may include Global E2 node ID.
- information to be removed may include information (item, ID, definition) about a RAN function.
- information to be removed may include E2 Node Component Configuration.
- the information to be removed may include E2 node TNL (transport network layer) related information (E2 Node TNL Association To Remove List).
- a computer readable storage medium storing one or more programs (software modules) may be provided.
- One or more programs stored in a computer-readable storage medium are configured for execution by one or more processors in an electronic device.
- the one or more programs include instructions that cause the electronic device to execute methods according to embodiments described in the claims or specification of the present disclosure.
- Such programs may include random access memory, non-volatile memory including flash memory, read only memory (ROM), and 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 can be stored on optical storage devices, magnetic cassettes. Alternatively, it may be stored in a memory composed of a combination of some or all of these. In addition, each configuration memory may be included in multiple numbers.
- non-volatile memory including flash memory, read only memory (ROM), and electrically erasable programmable ROM.
- EEPROM electrically erasable programmable read only memory
- CD-ROM compact disc-ROM
- DVDs digital versatile discs
- It can be stored on optical storage devices, magnetic cassettes. Alternatively, it may be stored in a memory composed of a combination of some or all of these.
- each configuration memory may be included in multiple numbers.
- the program is provided through 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 communication network consisting of a combination thereof. It can be stored on an attachable storage device that can be accessed. Such a storage device may be connected to a device performing an embodiment of the present disclosure through an external port. In addition, a separate storage device on a communication network may be connected to a device performing an 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 communication network consisting of a combination thereof. It can be stored on an attachable storage device that can be accessed. Such a storage device may be connected to a device performing an embodiment of the present disclosure through an external port. In addition, a separate storage device on a communication network may be connected to a device performing an embodiment of the present disclosure.
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Mobile Radio Communication Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
Claims (8)
- Near-RT(real time) RIC(RAN(radio access network) intelligent controller)에 의해 수행되는 방법에 있어서,E2 노드로부터 상기 E2 노드의 종료를 나타내기 위한 E2 제거 요청 메시지를 E2 인터페이스를 통해 수신하는 과정과, 상기 E2 노드의 종료는 SMO(Service Management and Orchestration)로부터 설정되고,상기 E2 노드에게 E2 제거 응답 메시지를 E2 인터페이스를 통해 전송하는 과정과,상기 E2 제거 요청 메시지에 대응하여, 상기 Near-RT RIC에서 상기 E2 노드에 대한 설정의 제거를 수행하는 과정을 포함하는 방법.
- Near-RT(real time) RIC(RAN(radio access network) intelligent controller)에 의해 수행되는 방법에 있어서,E2 노드와 SCTP(stream control transmission protocol) 연결의 해제를 검출하는 과정과,상기 해제의 검출에 대응하여, 해제 타이머를 시작하는 과정과,상기 해제 타이머의 만료에 대응하여, 상기 E2 노드에 대한 설정의 제거를 수행하는 과정을 포함하는 방법.
- Near-RT(real time) RIC(RAN(radio access network) intelligent controller)에 의해 수행되는 방법에 있어서,E2 노드와 SCTP(stream control transmission protocol) 연결의 해제를 검출하는 과정과,상기 해제의 검출에 대응하여, SMO(Service Management and Orchestration)에게 상기 E2 노드의 상태를 문의하기 위한 메시지를 O1 인터페이스를 통해 전송하는 과정과,상기 SMO로부터 상기 E2 노드의 상태에 대한 응답 메시지를 O1 인터페이스를 통해 수신하는 과정과,상기 응답 메시지가 상기 E2 노드의 종료(termination)의 종료를 가리키는 경우, 상기 Near-RT RIC에서의 상기 E2 노드에 대한 설정의 제거를 수행하는 과정을 포함하는 방법.
- Near-RT(real time) RIC(RAN(radio access network) intelligent controller)에 의해 수행되는 방법에 있어서,O1 인터페이스를 통해 SMO(Service Management and Orchestration)로부터 상기 Near-RT RIC와 연결되는 E2 노드의 종료에 대한 구성 메시지를 수신하는 과정과,상기 구성 메시지에 대응하여, 상기 Near-RT RIC에서 상기 E2 노드에 대한 설정의 제거를 수행하는 과정을 포함하는 방법.
- Near-RT(real time) RIC(RAN(radio access network) intelligent controller)에 의해 수행되는 장치에 있어서,적어도 하나의 송수신기와,적어도 하나의 프로세서를 포함하고,상기 적어도 하나의 프로세서는,E2 노드로부터 상기 E2 노드의 종료를 나타내기 위한 E2 제거 요청 메시지를 E2 인터페이스를 통해 수신하고, 상기 E2 노드의 종료는 SMO(Service Management and Orchestration)로부터 설정되고,상기 E2 노드에게 E2 제거 응답 메시지를 E2 인터페이스를 통해 전송하고,상기 E2 제거 요청 메시지에 대응하여, 상기 Near-RT RIC에서 상기 E2 노드에 대한 설정의 제거를 수행하도록 구성되는 장치.
- Near-RT(real time) RIC(RAN(radio access network) intelligent controller)에 의해 수행되는 장치에 있어서,적어도 하나의 송수신기와,적어도 하나의 프로세서를 포함하고,상기 적어도 하나의 프로세서는,E2 노드와 SCTP(stream control transmission protocol) 연결의 해제를 검출하고,상기 해제의 검출에 대응하여, 해제 타이머를 시작하고,상기 해제 타이머의 만료에 대응하여, 상기 E2 노드에 대한 설정의 제거를 수행하도록 구성되는 장치.
- Near-RT(real time) RIC(RAN(radio access network) intelligent controller)에 의해 수행되는 장치에 있어서,적어도 하나의 송수신기와,적어도 하나의 프로세서를 포함하고,상기 적어도 하나의 프로세서는,E2 노드와 SCTP(stream control transmission protocol) 연결의 해제를 검출하고,상기 해제의 검출에 대응하여, SMO(Service Management and Orchestration)에게 상기 E2 노드의 상태를 문의하기 위한 메시지를 O1 인터페이스를 통해 전송하고,상기 SMO로부터 상기 E2 노드의 상태에 대한 응답 메시지를 O1 인터페이스를 통해 수신하고,상기 응답 메시지가 상기 E2 노드의 종료(termination)의 종료를 가리키는 경우, 상기 Near-RT RIC에서의 상기 E2 노드에 대한 설정의 제거를 수행하도록 구성되는 장치.
- Near-RT(real time) RIC(RAN(radio access network) intelligent controller)에 의해 수행되는 장치에 있어서,적어도 하나의 송수신기와,적어도 하나의 프로세서를 포함하고,상기 적어도 하나의 프로세서는,O1 인터페이스를 통해 SMO(Service Management and Orchestration)로부터 상기 Near-RT RIC와 연결되는 E2 노드의 종료에 대한 구성 메시지를 수신하고,상기 구성 메시지에 대응하여, 상기 Near-RT RIC에서 상기 E2 노드에 대한 설정의 제거를 수행하도록 구성되는 장치.
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP22853463.2A EP4369853A1 (en) | 2021-08-03 | 2022-08-03 | Device and method for removing e2 interface-related information in radio access network |
AU2022322684A AU2022322684A1 (en) | 2021-08-03 | 2022-08-03 | Device and method for removing e2 interface-related information in radio access network |
CN202280054616.XA CN117796140A (zh) | 2021-08-03 | 2022-08-03 | 在无线接入网络中移除e2接口相关信息的设备和方法 |
BR112024002186A BR112024002186A2 (pt) | 2021-08-03 | 2022-08-03 | Dispositivo e método para remover informações relacionadas a interface de e2 em rede de acesso via rádio |
US18/540,079 US20240121049A1 (en) | 2021-08-03 | 2023-12-14 | Apparatus and method for removing e2 interface-relevant information in radio access network |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR1020210102248A KR20230020315A (ko) | 2021-08-03 | 2021-08-03 | 무선 액세스 네트워크에서 e2 인터페이스 관련 정보를 제거하기 위한 장치 및 방법 |
KR10-2021-0102248 | 2021-08-03 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US18/540,079 Continuation US20240121049A1 (en) | 2021-08-03 | 2023-12-14 | Apparatus and method for removing e2 interface-relevant information in radio access network |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2023014087A1 true WO2023014087A1 (ko) | 2023-02-09 |
Family
ID=85155875
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/KR2022/011487 WO2023014087A1 (ko) | 2021-08-03 | 2022-08-03 | 무선 액세스 네트워크에서 e2 인터페이스 관련 정보를 제거하기 위한 장치 및 방법 |
Country Status (7)
Country | Link |
---|---|
US (1) | US20240121049A1 (ko) |
EP (1) | EP4369853A1 (ko) |
KR (1) | KR20230020315A (ko) |
CN (1) | CN117796140A (ko) |
AU (1) | AU2022322684A1 (ko) |
BR (1) | BR112024002186A2 (ko) |
WO (1) | WO2023014087A1 (ko) |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2021071325A1 (ko) * | 2019-10-11 | 2021-04-15 | 삼성전자 주식회사 | 무선 액세스 네트워크 통신 시스템에서 e2 인터페이스를 통한 서비스 가입을 위한 장치 및 방법 |
WO2021118281A1 (ko) * | 2019-12-10 | 2021-06-17 | 삼성전자 주식회사 | 무선 접속 망에서 셀 정보를 포함하는 e2 인터페이스 설정을 위한 장치 및 방법 |
-
2021
- 2021-08-03 KR KR1020210102248A patent/KR20230020315A/ko unknown
-
2022
- 2022-08-03 AU AU2022322684A patent/AU2022322684A1/en active Pending
- 2022-08-03 WO PCT/KR2022/011487 patent/WO2023014087A1/ko active Application Filing
- 2022-08-03 EP EP22853463.2A patent/EP4369853A1/en active Pending
- 2022-08-03 CN CN202280054616.XA patent/CN117796140A/zh active Pending
- 2022-08-03 BR BR112024002186A patent/BR112024002186A2/pt unknown
-
2023
- 2023-12-14 US US18/540,079 patent/US20240121049A1/en active Pending
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2021071325A1 (ko) * | 2019-10-11 | 2021-04-15 | 삼성전자 주식회사 | 무선 액세스 네트워크 통신 시스템에서 e2 인터페이스를 통한 서비스 가입을 위한 장치 및 방법 |
WO2021118281A1 (ko) * | 2019-12-10 | 2021-06-17 | 삼성전자 주식회사 | 무선 접속 망에서 셀 정보를 포함하는 e2 인터페이스 설정을 위한 장치 및 방법 |
Non-Patent Citations (3)
Title |
---|
ANONYMOUS: "O-RAN Working Group 3, Near-Real-time RAN Intelligent Controller, E2 Application Protocol (E2AP). O-RAN.WG3.E2AP-v01.01", O-RAN ALLIANCE WG3, HTTPS://WWW.O-RAN.ORG/SPECIFICATION-ACCESS, O-RAN ALLIANCE, 15 July 2020 (2020-07-15), pages 1 - 84, XP009536365 * |
O-RAN WORKING GROUP 1: "O-RAN Working Group 1: Study on O-RAN Slicing", O-RAN.WG1.STUDY-ON-O-RAN-SLICING-V02.00 TECHNICAL REPORT, O-RAN WORKING GROUP 1, 31 March 2020 (2020-03-31), pages 1 - 29, XP009538605 * |
O-RAN Working Group 3 Near-Real-time RAN Intelligent Controller Near-RT RIC Architecture. O-RAN.WG3.RICARCH-v02.00. 30 June 2021 * |
Also Published As
Publication number | Publication date |
---|---|
AU2022322684A1 (en) | 2024-02-22 |
CN117796140A (zh) | 2024-03-29 |
KR20230020315A (ko) | 2023-02-10 |
US20240121049A1 (en) | 2024-04-11 |
BR112024002186A2 (pt) | 2024-04-30 |
EP4369853A1 (en) | 2024-05-15 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2021215794A1 (en) | Method and system to handle handover procedure in multi trp system | |
WO2021066587A1 (ko) | 무선 액세스 네트워크 통신 시스템에서 e2 인터페이스를 통한 서비스 가입을 위한 장치 및 방법 | |
WO2021066588A1 (ko) | 무선 액세스 네트워크 통신 시스템에서 e2 인터페이스를 통한 서비스 가입을 위한 장치 및 방법 | |
WO2019172629A1 (ko) | 무선 통신 시스템에서 무선 접속 기술을 스위칭하기 위한 장치 및 방법 | |
WO2020251240A1 (en) | Method and apparatus for improving service reliability in wireless communication system | |
WO2018174638A1 (ko) | 무선 통신 시스템에서 단말의 위치에 따라서 세션의 상태를 관리하는 방법 및 장치 | |
WO2022177333A1 (ko) | 무선 액세스 네트워크에서 셀 정보와 e2 인터페이스 셋업을 위한 장치 및 방법 | |
WO2020218863A1 (en) | Mobility enhancement for new radio access technology | |
WO2021141291A1 (ko) | 무선 통신 시스템에서 네트워크 트래픽을 수집하는 방법 및 장치 | |
WO2019209032A1 (ko) | 무선 통신 시스템에서 v2x 서비스를 통한 차량 단말들간의 v2x 메시지 전송을 제어하기 위한 차량 단말 및 그 통신 제어 방법 | |
WO2023146314A1 (en) | Communication method and device for xr service in wireless communication system | |
WO2017026849A1 (en) | Method and apparatus for self-configuration and self-optimization in a wireless communication system | |
WO2022039582A1 (ko) | 무선 통신 시스템에서 성능 측정을 위한 장치 및 방법 | |
WO2018084539A2 (ko) | 무선 통신 시스템에서 서비스 제공 방법 및 장치 | |
WO2023027531A1 (ko) | 무선 통신 시스템에서 e2 노드 제어 및 셀 제어를 위한 장치 및 방법 | |
WO2022211467A1 (ko) | 무선 통신 시스템에서 e2 노드 제어를 위한 장치 및 방법 | |
WO2023014087A1 (ko) | 무선 액세스 네트워크에서 e2 인터페이스 관련 정보를 제거하기 위한 장치 및 방법 | |
WO2023059036A1 (en) | Communication method and device in wireless communication system supporting unmanned aerial system service | |
WO2022231245A1 (ko) | 무선 통신 시스템에서 e2 노드 제어를 위한 장치 및 방법 | |
WO2022092981A1 (ko) | 무선 통신 시스템에서 e2 노드 제어를 위한 장치 및 방법 | |
WO2022220640A1 (ko) | 무선 통신 시스템에서 e2 노드 제어를 위한 장치 및 방법 | |
EP3286947A1 (en) | Method and apparatus for self-configuration and self-optimization in a wireless communication system | |
WO2024039028A1 (ko) | 규격 버전을 제공하기 위한 장치 및 방법 | |
WO2024053880A1 (ko) | 가입 절차를 위한 전자 장치 및 방법 | |
WO2024039027A1 (ko) | 규격 버전을 제공하기 위한 장치 및 방법 |
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: 22853463 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2024506803 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: AU2022322684 Country of ref document: AU |
|
WWE | Wipo information: entry into national phase |
Ref document number: 202280054616.X Country of ref document: CN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2022853463 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 2022853463 Country of ref document: EP Effective date: 20240208 |
|
REG | Reference to national code |
Ref country code: BR Ref legal event code: B01A Ref document number: 112024002186 Country of ref document: BR |
|
ENP | Entry into the national phase |
Ref document number: 2022322684 Country of ref document: AU Date of ref document: 20220803 Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2024105279 Country of ref document: RU |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 112024002186 Country of ref document: BR Kind code of ref document: A2 Effective date: 20240202 |