[go: up one dir, main page]

WO2022211467A1 - Dispositif et procédé de commande d'un nœud e2 dans un système de communication sans fil - Google Patents

Dispositif et procédé de commande d'un nœud e2 dans un système de communication sans fil Download PDF

Info

Publication number
WO2022211467A1
WO2022211467A1 PCT/KR2022/004458 KR2022004458W WO2022211467A1 WO 2022211467 A1 WO2022211467 A1 WO 2022211467A1 KR 2022004458 W KR2022004458 W KR 2022004458W WO 2022211467 A1 WO2022211467 A1 WO 2022211467A1
Authority
WO
WIPO (PCT)
Prior art keywords
ric
control
ran
message
node
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/KR2022/004458
Other languages
English (en)
Korean (ko)
Inventor
송준혁
류선희
옥정엽
이충근
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Samsung Electronics Co Ltd
Original Assignee
Samsung Electronics Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from KR1020210045524A external-priority patent/KR20220135129A/ko
Application filed by Samsung Electronics Co Ltd filed Critical Samsung Electronics Co Ltd
Priority to CN202280025861.8A priority Critical patent/CN117204012A/zh
Priority to EP22781586.7A priority patent/EP4247043A4/fr
Publication of WO2022211467A1 publication Critical patent/WO2022211467A1/fr
Priority to US18/189,768 priority patent/US20230239710A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • 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
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • 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/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 RIC in a radio access network (RAN).
  • RAN radio access network
  • the present disclosure relates to an apparatus and method for controlling an E2 node through an E2 message conforming to an open RAN (O-RAN) standard of a wireless communication system.
  • OF-RAN open RAN
  • the 5G communication system or the pre-5G communication system is called a 4G network after (Beyond 4G Network) communication system or an LTE (Long Term Evolution) system after (Post LTE) system.
  • the 5G communication system is being considered for implementation in a very high frequency (mmWave) band (eg, such as a 60 gigabyte (60 GHz) band).
  • mmWave very high frequency
  • FD-MIMO Full Dimensional MIMO
  • array antenna, analog beam-forming, and large scale antenna technologies are being discussed.
  • an evolved small cell in the 5G communication system, an evolved small cell, an advanced small cell, a cloud radio access network (cloud radio access network, cloud RAN), an ultra-dense network (ultra-dense network) , Device to Device communication (D2D), wireless backhaul, moving network, cooperative communication, Coordinated Multi-Points (CoMP), and reception interference cancellation (interference cancellation) Technology development is underway.
  • cloud radio access network cloud radio access network
  • ultra-dense network ultra-dense network
  • D2D Device to Device communication
  • wireless backhaul moving network
  • cooperative communication Coordinated Multi-Points (CoMP), and reception interference cancellation (interference cancellation) Technology development is underway.
  • CoMP Coordinated Multi-Points
  • FQAM Hybrid Frequency Shift Keying and Quadrature Amplitude Modulation
  • SWSC Sliding Window Superposition Coding
  • ACM Advanced Coding Modulation
  • FBMC Filter Bank Multi Carrier
  • NOMA Non Orthogonal Multiple Access
  • SCMA Sparse Code Multiple Access
  • 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 aspect of the present disclosure is to provide an apparatus and method for making a message and transmitting an error that occurs when a radio access network (RAN) intelligent controller (RIC) performs control of an E2 node in a wireless communication system.
  • RAN radio access network
  • RIC radio controller
  • Another aspect of the present disclosure is to provide an apparatus and method for configuring an E2 node by an RIC such that the E2 node forwards an error message under the control of the RIC.
  • a method performed by a radio access network (RAN) intelligent controller includes the steps of receiving a configuration request message including RAN function information specific to a service model from an E2 node, and the RAN function information includes one or more control operations ( action), the process of sending a configuration response message to the E2 node, the process of sending a RIC control request message to the E2 node, and receiving a RIC control acknowledgment message from the E2 node
  • the RIC control request message includes identification information of a control action among the one or more control actions
  • the RIC control confirmation message includes a RIC control result for the control action. outcome) information
  • the RIC control result information may include a reason (reason) of an event for the control operation in a specific protocol (protocol).
  • a method performed by an E2 node includes a process of transmitting a configuration request message including radio access network (RAN) function information specific to a service model to a RAN intelligent controller (RIC), and the RAN function
  • the information includes information on one or more control actions, a process of receiving a configuration response message from the RIC, a process of transmitting a RIC control request message to the RIC, and a process of RIC control acknowledgment ) receiving a message from the RIC
  • the RIC control request message includes identification information of a control action among the one or more control actions
  • the RIC control confirmation message includes the control action
  • Includes RIC control outcome information for, the RIC control result information may include a reason (reason) of the event (event) for the control operation in a specific protocol (protocol).
  • an apparatus of a radio access network (RAN) intelligent controller (RIC) comprises at least one transceiver and at least one processor, wherein the at least one processor, via the at least one transceiver, is a RAN function specific to a service model.
  • the RIC control confirmation message includes RIC control result information for the control operation, the RIC control result information, the event for the control operation in a specific protocol (protocol) (event) ) may be included.
  • an apparatus of an E2 node includes at least one transceiver and at least one processor, wherein the at least one processor, via the at least one transceiver, is specific to a service model to radio access (RAN).
  • RAN radio access
  • a RAN intelligent controller RIC
  • the RAN function information includes information about one or more control actions
  • a setup response message receive from the RIC, send a RIC control request message to the RIC, and receive a RIC control acknowledgment message from the RIC, wherein the RIC control request message is the one or more control actions ), including the identification information of the control operation from among, the RIC control confirmation message includes RIC control result information for
  • a method performed by a Near-RT (real time) RIC is a RIC control request message including identification information of a control action to the E2 node, and as a response to the RIC control request message, receiving a RIC control acknowledgment message or a RIC control failure message from the E2 node, the RIC control confirmation
  • the message or the RIC control failure message includes RIC control outcome information
  • the RIC control outcome information includes one or more RAN parameter sets
  • each of the one or more RAN parameter sets is a RAN parameter ID and RAN parameter value.
  • the method performed by the E2 node transmits a RIC control request message including identification information of a control action to a Near-RT (real time) RIC (radio access network (RAN)) intelligent controller), and as a response to the RIC control request message, transmitting a RIC control acknowledgment message or RIC control failure message to the Near-RT RIC, wherein the RIC The control acknowledgment message or the RIC control failure message includes RIC control outcome information, the RIC control outcome information includes one or more RAN parameter sets, and each of the one or more RAN parameter sets is a RAN parameter ID and RAN It can contain parameter values.
  • an apparatus of 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
  • a RIC control request message including identification information of a control action is transmitted to the E2 node, and as a response to the RIC control request message, a RIC control acknowledge message or RIC control failure (failure) configured to receive a message from the E2 node, wherein the RIC control acknowledgment message or the RIC control failure message includes RIC control outcome information, and the RIC control outcome information includes one or more RAN parameter sets
  • Each of the one or more RAN parameter sets may include a RAN parameter ID and a RAN parameter value.
  • a control action configured to receive a RIC control request message including identification information of a Near-RT (real time) RIC (radio access network (RAN) intelligent controller), and in response to the RIC control request message, RIC control confirmation ( acknowledge) message or RIC control failure (failure) message is configured to transmit to the Near-RT RIC, the RIC control acknowledgment message or the RIC control failure message includes RIC control result (control outcome) information, the RIC control
  • the result information may include one or more RAN parameter sets, and each of the one or more RAN parameter sets may include a RAN parameter ID and a RAN parameter value.
  • the apparatus and method according to the embodiments of the present disclosure enable a radio access network (RAN) intelligent controller (RIC) to know a reason according to an event occurrence (eg, failure) of an 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 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
  • FIG 2B illustrates an example of an architecture for an O-RAN, according to an embodiment 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 an embodiment of the present disclosure.
  • 13A illustrates signaling of a setup procedure between an E2 node and an RIC according to an embodiment 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.
  • 13C illustrates signaling according to a subscription 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 control request message according to an embodiment of the present disclosure.
  • FIG. 14B illustrates an example of a format of a RIC control acknowledgment message according to an embodiment of the present disclosure.
  • E2SM 'E2 service model
  • RC RAN control
  • Control Outcome' IE information element
  • 16A to 16C illustrate an example of a RIC control acknowledgment message for delivering a Cause IE according to embodiments of the present disclosure.
  • FIG 17 illustrates an example of a subsequent operation of an RIC operation according to an embodiment of the present disclosure.
  • FIG. 18 illustrates an example of a RIC style type according to an embodiment of the present disclosure.
  • FIG. 19 illustrates another example of a RIC control acknowledgment message for delivering a Cause IE in 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. 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 in the scope of standardization.
  • an open radio access network is a 3GPP NE (network entity) and nodes constituting a base station, RU (radio unit), DU (digital unit), CU (central unit)-CP (control plane) ) and CU-UP (user plane) are newly defined as O(O-RAN)-RU, O-DU, O-CU-CP, and O-CU-UP, respectively, and in addition, Near RT (near-real -time) RIC (radio access network intelligent controller) was standardized.
  • the present disclosure is to support an operator specific service model in the E2 interface where the RIC requests a service from the O-DU, O-CU-CP, or O-CU-UP.
  • 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 the 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 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 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 120 .
  • 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 includes an 'access point (AP)', an 'evolved NodeB (eNodeB), an eNB)', a 'wireless point', a 'transmission and reception point (transmission). /reception point, TRP)' or may be referred to as another term having an equivalent technical meaning.
  • 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).
  • 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 an embodiment 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 from 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 an embodiment of the present disclosure.
  • E2-SM service model
  • KPIMON key performance indicator
  • O-RAN Non-stand alone mode in operation is considered, while the E2 node may be assumed to be in O-RAN Stand Alone mode.
  • 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) layer 330 , and a stream control transmission protocol (SCTP) 340 .
  • IP Internet protocol
  • SCTP stream control transmission protocol
  • the radio network layer includes an E2 application protocol (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 an embodiment 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 an embodiment 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 .
  • Terms such as '... unit' and '... group' used below mean a unit that processes at least one function or operation, which may be implemented as hardware or software, or a combination of hardware and software. have.
  • the core network device includes a communication unit 510 (eg, a transceiver), a storage unit 520 (eg, a memory), and a control unit 530 (eg, a processor).
  • a communication unit 510 eg, a transceiver
  • a storage unit 520 eg, a memory
  • a control unit 530 eg, a processor
  • 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 an embodiment 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 access and mobility function (AMF)) interface.
  • NGAP next generation application protocol
  • AMF access and mobility function
  • 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 624 or 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 will support E2 as an open logical interface targeting multi-vendor environments regardless of the specific RRC-RRM algorithm implementation located on the 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 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.
  • E2 nodes eg, O-DU, O-CU
  • RIC are virtualized on a cloud platform (eg, open chassis and blade specification edge cloud) and configured on a device (eg, a server).
  • a cloud platform eg, open chassis and blade specification edge cloud
  • a device eg, a server
  • 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.
  • FIG. 10 illustrates an example 1000 of mobility load balancing (MLB) control for different vendors according to an embodiment of the present disclosure.
  • MLB mobility load balancing
  • 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 RIC 1050 may be configured to perform RRM.
  • the RIC 1050 may generate messages for controlling each E2 node, as well as simply receiving measurements from each E2 node.
  • the RIC 1050 may transmit a control message to each E2 node (eg, DU, CU-CP, CU-UP).
  • FIG. 11A illustrates an example of MLB control for different vendors according to an embodiment 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 an embodiment 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.
  • a procedure of transferring the RIC indication message and the RIC control message is shown.
  • the E2 node may transmit an E2 SET UP REQUEST message to the RIC.
  • the E2 NODE FUNCTION 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 for indicating a specific terminal (hereinafter, terminal ID/UE Id).
  • the transmission of the subscription request message and the transmission of the E2 setup 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 secondary gNB (SgNB) additional request message).
  • measurement 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 1200 and 1250 for RIC-based RRM control according to 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 13C in order to perform the RIC control procedure according to embodiments of the present disclosure, a setup procedure and a subscription procedure between the E2 node and the RIC, and the RIC control procedure are described. .
  • RIC may mean near-RT RIC.
  • the E2 node may transmit an E2 SET UP REQUEST message to the RIC.
  • the E2 NODE FUNCTION 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 setup request message may include information on a RAN function supported by the E2 node (eg, RAN Function Definition), E2 node ID information, and the like.
  • the RAN Function Definition value is a value set to OAM.
  • the RAN Function Definition value may include a STYLE ID value.
  • the RIC may determine which call processing function the E2 node supports based on the RAN Function Definition value by receiving information on the set value through OAM.
  • the RAN Function Definition may be configured in the IE format shown in FIG. 13A .
  • the RAN Function Definition may include information on the RIC event trigger style and information on the RIC control (CONTROL) style.
  • the RAN Function Definition of the E2 setup request message is a capability of the E2 node, and may include information on allowed control actions.
  • RAN Function Definition is an ID for an allowed Control Action (eg Allowed Control Action ID), a name for an allowed Control Action (eg Allowed Control Action Name), and information about parameters related to an allowed Control Action (eg, : Sequence of Associated RAN Parameters).
  • the corresponding SgNB control action (eg, SgNB Addition/SgNB Modification/SgNB Release) is the Control Action ID and can be defined together.
  • the table shown in FIG. 13A only shows an example of the RAN Function Definition IE included in the E2 SETUP REQUEST message of the present disclosure, and is not construed as limiting other embodiments of the present disclosure.
  • the RIC may receive an E2 SETUP RESPONSE message from the E2 node.
  • the RIC may determine whether it is acceptable to accept the E2 setup request message sent by the E2 node.
  • the RIC may transmit an E2 setup response message to the E2 node if the E2 setup request message can be accepted.
  • one or more functions for the RIC to control the E2 node may be configured. Through this, the RIC can provide a control service to the E2 node. The RIC may control the E2 node to perform at least one of allowed (or configured) Control Actions through the E2 SETUP procedure.
  • 13B illustrates signaling of a control procedure between an E2 node and an RIC according to embodiments of the present disclosure.
  • 13 shows the RIC CONTROL REQUEST procedure defined in the O-RAN standard.
  • the RIC may transmit a RIC CONTROL REQUEST message to the E2 node.
  • the RIC may be a Near-RT RIC.
  • the RIC sends a RIC CONTROL REQUEST message to the E2 node when called.
  • RIC CONTROL REQUEST acknowledge support can be selected when sending messages.
  • the E2 node must transmit a CONTROL REQUEST ACKNOWLEDGEMENT message to the RIC.
  • the E2 node may transmit a RIC control acknowledgment message (RIC CONTOL ACKNOWLEDGE) to the RIC.
  • RIC CONTOL ACKNOWLEDGE a RIC control acknowledgment message
  • the E2 Node shall respond with a RIC CONTROL ACKNOWLEDGE message. .
  • RIC may stop timer T RICcontrol and end the RIC Control procedure.
  • the RIC may use the information included in the RIC Control status IE and the RIC Control Outcome result IE to determine a follow-up action.
  • the RIC control result IE may be optional.
  • the RIC control procedure in FIG. 13B may be performed in connection with the E2 subscription procedure as well as the E2 setup procedure of FIG. 13A .
  • an example of a situation in which the RIC control procedure is performed in connection with the E2 subscription procedure will be described with reference to FIG. 13C.
  • 13C illustrates signaling according to a subscription procedure between an E2 node and an RIC according to embodiments of the present disclosure.
  • 13C illustrates signaling of an entire control procedure between an E2 node, an RIC, and a Non-RT RIC according to embodiments of the present disclosure.
  • the Non-RT RIC may transmit a Policy for the Near-RT RIC to control 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 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 For REPORT service and CONTROL service subscription, one RIC subscription procedure (one RIC Subscription Request and RIC Subscription Response) may be used. However, unlike shown in FIG. 13c , RIC Subscription Request and RIC Subscription Response are exchanged between RIC and E2 node for subscription of REPORT service, and for subscription of CONTROL service, RIC Subscription Request and RIC Subscription Response are additionally RIC and may be exchanged between E2 nodes.
  • the E2 node may transmit a RIC indication (or RIC Control Indication) to the RIC.
  • the E2 node may include related measurement data in the RIC Indication message and transmit the RIC Indication message to the RIC.
  • the E2 node 610 may transmit an E2 RIC indication message to the RIC 640 .
  • a message container of the RIC indication message may include a KPI reporting service model in units of UEs.
  • 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.
  • the RIC control procedure may correspond to the control procedure of FIG. 13B .
  • RIC may deliver a RIC CONTROL REQUEST message to the E2 node when the received measurement data (Measurement data) meets the subscribed CONTROL SERVICE condition.
  • RIC CONTROL REQUEST may include settings necessary to control the E2 node. For example, IEs related to SgNB addition Request defined in 3GPP, target cell IE, etc. may be delivered for dual connectivity configuration. Also, for example, for DRB control, a DRB ID and an IE related to an F1 Interface message may be transmitted.
  • the E2 node may transmit the RIC CONTROL ACKNOWLEDGE message according to embodiments of the present disclosure to the RIC.
  • 14A illustrates an example of a format of a RIC control request message according to an embodiment of the present disclosure.
  • 14A shows the RIC CONTROL REQUEST message format specified in the O-RAN specification.
  • Message Type 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
  • RAN Function ID is an ID that identifies functions that are the target of CONTROL in E2 Node.
  • the RIC Call Process ID which is optionally sent, is an ID that identifies a related process in progress.
  • a message for controlling the RAN function is carried in the RIC Control Header and RIC Control Message and transmitted.
  • the RIC may selectively request a RIC Control Acknowledge message for transmitting whether the corresponding control operation is successful to the E2 Node as the RIC Control Ack Request IE.
  • the RIC Control Ack Request IE may be included in the RIC control request message. If the RIC does not include the RIC Control Ack Request IE in the RIC control request message, it may be interpreted that the RIC does not request the RIC control acknowledgment message from the E2 node.
  • 14B illustrates an example of a format of a RIC control acknowledgment message according to an embodiment of the present disclosure.
  • 14B illustrates Control Acknowledged, which is a response message of the Control Message defined in the O-RAN standard.
  • Message Type 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
  • RAN Function ID is an ID that identifies functions that are the target of CONTROL in E2 Node.
  • the RIC Call Process ID which is optionally sent, is an ID that identifies a related process in progress.
  • RIC CONTROL STATUS may indicate a status in the previously requested RIC CONTROL REQUEST message.
  • the message status may be displayed as one of Success, Rejected, or Failure, or Partial Success status.
  • the E2 node may transmit the result of the corresponding control operation through the RIC Control Outcome (the corresponding IE may be referred to as the RIC control result).
  • the result of the actual control operation can be defined in the E2 Service model in the form of OCTET STRING Container of RIC Control Outcome.
  • the IE of RIC Control Outcome may be exemplified as shown in Table 1 below.
  • E2SM O-RAN Working Group 3, Near-Real-time RAN Intelligent Controller, E2 Service Model (E2SM). Services indicated by RIC Control Outcome” is associated with the RAN function, where the RAN function may depend on the E2 service model (E2SM).
  • 15 illustrates an example of the format of an 'E2SM-RC Control Outcome' IE (information element) in the RIC control acknowledgment message according to an embodiment of the present disclosure.
  • 15 shows the Control Outcomes message format 1 delivered in the form of a single Octet String Container regardless of Success or Failed to RIC CONTROL ACKNOWLEDGE defined in the present disclosure, and the fields of Successful Cause and Failed Cause are independently configured and can be delivered together. It shows an example of Control Outcomes message format 2 designed in the form.
  • the Control Outcomes message format can be extended, so additional formats can be defined later.
  • the RAN function specific E2 service model (E2SM) specification may be recommended to include a description of the IE to be used for the RIC control service.
  • a CHOICE format listing one or more RIC control result formats may be adopted.
  • 16A to 16C illustrate an example of a RIC control acknowledgment message for delivering a Cause IE according to embodiments of the present disclosure.
  • Control Outcome Format1 can be defined repeatedly as many as the number of Control Outcomes defined in maxnoofControlOutcome in the form of a sequence.
  • RAN Parameter ID and RAN Parameter Container for one user equipment may be repeatedly defined as many as the number defined in maxnoofControlAckRANResources.
  • the Parameter ID shown in FIG. 16B is a function that is a target of RAN Control defined in the standard for each RAN CONTROL.
  • the RAN parameter ID can be defined as an integer value from 1 to 4294967296.
  • 16c shows failure causes defined in 3GPP defined for each Parameter ID.
  • 16C may indicate a RAN parameter ID and information on a RAN parameter container corresponding to the parameter ID.
  • the table shown in FIG. 16 is exemplary, and should not be construed as limiting the embodiments of the present disclosure. In addition to 12, an additional value may be defined for the RAN parameter ID, and some contents of the table may be changed according to specification addition/change/modification.
  • the RAN parameter ID may indicate 'QoS Flow Failed to Setup List' (eg, '1').
  • the RAN parameter Container may include a QoS Flow ID of 'QoS Flow Failed to Setup List'.
  • the RAN parameter ID may indicate 'QoS Flow Failed to Modify List' (eg, '2').
  • the RAN parameter Container may include a QoS Flow Failed to Modify List IE of 'QoS Flow Failed to Modify List'.
  • the RAN parameter ID may indicate 'QoS Flow Failed to Setup List' (eg, '3').
  • the RAN parameter container may include a DRB Failed to Setup List IE of the 'DRB Failed to Setup List'.
  • the RAN parameter ID may indicate a 'DRB Failed to be Modified List' (eg, '4').
  • RAN parameter Container may include 'DRB Failed to be Modified List IE' of 'DRB Failed to be Modified List'.
  • the RAN parameter ID may indicate 'F1AP Cause' (eg, '5').
  • the RAN parameter Container may include a Cause IE defined in 3GPP TS 38.473.
  • the RAN parameter ID may indicate 'E1AP Cause' (eg, '6').
  • the RAN parameter container may include a Cause IE defined in 3GPP TS 38.463.
  • the RAN parameter ID may indicate 'XnAP Cause' (eg, '7').
  • the RAN parameter Container may include a Cause IE defined in 3GPP TS 38.423.
  • the RAN parameter ID may indicate 'NGAP Cause' (eg, '8').
  • the RAN parameter Container may include a Cause IE defined in 3GPP TS 38.413.
  • the RAN parameter ID may indicate 'X2AP Cause' (eg, '9').
  • the RAN parameter container may include a Cause IE defined in 3GPP TS 36.423.
  • the RAN parameter ID may indicate 'W1AP Cause' (eg, '10').
  • the RAN parameter container may include a Cause IE defined in 3GPP TS 37.473.
  • the RAN parameter ID may indicate 'S1AP Cause' (eg, '11').
  • the RAN parameter container may include a Cause IE defined in 3GPP TS 36.473.
  • the RAN parameter ID may indicate an Interface Name. Even if it is not defined in the 3GPP standard (eg, set by implementation), a Cause value to indicate the cause of failure may be defined. In this case, in order to refer to an interface associated with a corresponding cause, an 'Interface Name' may be defined. The 'Interface Name' may be configured to indicate an interface such as F1/E1/Xn/X2/W1.
  • FIG. 17 illustrates an example of a subsequent operation of an RIC operation according to an embodiment of the present disclosure.
  • the RIC can support a more intelligent follow-up operation using this message format.
  • DRB #1 it is assumed that two QoS Flows are mapped to DRB #1.
  • QoS Flow #2 from among the two QoS Flows has to communicate with a separate CU-UP through a separate DRB (eg, midhaul between DU and CU-UP and between CU-UP and UPF)
  • a separate DRB eg, midhaul between DU and CU-UP and between CU-UP and UPF
  • DRB #2 is additionally created in the DU (Action 1)
  • it is required to re-mapping QoS Flow and DRB #2 (Action 2).
  • This operation is linked to several entities (operations in conjunction with DU, CU-UP#2, CU-CP, and 5GC) from the RIC's point of view, and the failure of the operation may occur in various locations.
  • recovery may be delayed due to repeated failures unless the cause of the failure is accurately communicated to the RIC.
  • the RIC can solve the failure cause more efficiently. For example, when DRB setup fails due to CAC failure in a DU, the RIC may prevent CAC failure by enabling DRB setup with another DU instead of the corresponding DU.
  • the RIC adjusts the SDN (software defined network) controller through interaction with the entity in charge of transport to induce readjustment of the user plane.
  • SDN software defined network
  • it may help to perform coverage optimization through additional analysis of RRC reconfiguration failure behavior.
  • the RIC may perform DU control, DU bandwidth control, and service-specific control in the CU-DU separation structure as well as DRB and QoS mapping.
  • FIG. 18 illustrates an example of a RIC style type according to an embodiment of the present disclosure.
  • RIC Control Service Style in which the RIC can control the E2 node with RAN Control is described.
  • a supportable RIC Control Service Style may be additionally considered.
  • FIG. 19 illustrates another example of a RIC control acknowledgment message for delivering a Cause IE in an embodiment of the present disclosure.
  • An example of a message of E2SM-RC Control Outcome Format 2 will be described in detail with reference to FIG. 19 .
  • a control action corresponding to a Control Action ID for which control is requested through the RIC Control Request may be associated with one or more RAN parameter IDs.
  • success or failure (or rejection) may be determined for each RAN parameter ID.
  • one control operation of SgNB Addition/Modify/Release may be configured.
  • Success or failure (or rejection) may be determined for each gNB to be added.
  • the cause for FIG. 16C may be equally included in the RAN parameter container of the embodiment described with reference to FIG. 19 . That is, the embodiment described with reference to FIG. 19 may refer to Cause-related IEs and RAN parameter ID of FIG. 16C.
  • the message may include information on the RIC Style Type. That is, the message may be dependent on the RIC Style Type.
  • the message may include a set of maxnoofControlOutcome number for each style of RIC Control Service.
  • Each piece of information in the set may include one UE ID and a sequence set of Success and a sequence set of Failure related to the UE.
  • Each piece of information in the sequence set may include a RAN parameter ID and a RAN parameter container.
  • the sequence set of Success may include maxnoofControlAckRANResources1 number of RAN parameter IDs and RAN parameter containers.
  • the sequence set of Failure may include RAN parameter IDs and RAN parameter containers of maxnoofControlAckRANResources2 number.
  • the message (eg, RIC Control Outcome of RIC Control Confirmation message) may include only a sequence set of Success. At this time, RIC Control Status may be configured to indicate Success. Also, according to an embodiment, the message (eg, RIC Control Outcome of the RIC Control Confirmation message) may include only a sequence set of Failure. At this time, the RIC Control Status may be configured to indicate Failure (or Rejected).
  • the message (eg, RIC Control Outcome of the RIC control confirmation message) may include both a sequence set of Success and a sequence set of Failure.
  • the number of RAN parameter IDs and RAN parameter containers included in the sequence set is independent between the sequence set of Success and the sequence set of Failure. That is, maxnoofControlAckRANResources1 may be the same as maxnoofControlAckRANResources2 or different from maxnoofControlAckRANResources2.
  • the RIC Control Status may be configured to indicate partial success.
  • Control Outcomes according to Control Outcome Format2 can be repeatedly defined as many as the number defined in maxnoofControlOutcome in the form of 'Sequence of Successful outcome of RAN CONTROL' and 'Sequence of Failed outcome of RAN CONTROL' sequence.
  • RAN Parameter ID and RAN Parameter Container can be repeatedly defined for Success RAN CONTROL and Failed RAN CONTROL as many as the number defined in maxnoofControlAckRANResources (or maxnoofControlAckRANResources1 and maxnoofControlAckRANResources2).
  • the RIC may detect that the service of the UE in the DU is difficult due to insufficient cell capacity. In this case, the RIC may change the DU for access, rather than repeatedly controlling access through the DU.
  • the RIC may detect that a currently provided cell is insufficient to support the corresponding QCI. In order to provide a service of sufficient quality, the RIC may control to handover the UE or to change a CU or DU to a CU and DU determined to be more adjacent to the UE.
  • the RIC may configure an additional cell.
  • the RIC may perform an addition procedure of a secondary node (SN) for DC connection, or may perform a modification procedure of the SN.
  • the RIC may control the E2 node to provide a service to a cell having a relatively wide bandwidth through reconfiguration of the cell group.
  • the RIC may control the E2 node to handover to another target cell.
  • the RIC may control the CU to service a specific UE with a new DU to support inter-DU mobility.
  • the RIC can control the E2 node more efficiently.
  • a required RIC operation may be triggered through the Cause IE (or failure information) of the RIC control confirmation message reported by the E2 node.
  • 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 method performed by a radio access network (RAN) intelligent controller (RIC) is a setting request including RAN function information specific to a service model (service model)
  • the process of receiving a message from the E2 node, the RAN function information includes information on one or more control actions, and the process of transmitting a configuration response message to the E2 node, the RIC control request message transmitting to the E2 node, and receiving a RIC control acknowledgment message from the E2 node, wherein the RIC control request message is a control operation from among the one or more control actions.
  • the RIC control confirmation message includes RIC control result information for the control operation, the RIC control result information, the event for the control operation in a specific protocol (protocol) ( The reason for the event) may be included.
  • the event for the control operation may include failure or rejection of the control operation.
  • the RIC control result information includes a RAN parameter ID and a RAN parameter container
  • the RAN parameter ID is the specific protocol, quality of service (QoS) flow, or DRB. (data radio bearer)
  • the RAN parameter container may include information on the reason.
  • the RIC control result information includes information about the style of the RIC control service, and the style of the RIC control service includes radio bearer control, radio resource allocation, At least one of connected mode mobility, radio access control, dual connectivity, carrier aggregation, and idle mode mobility control may be indicated. have.
  • the RIC control result information includes at least one of success sequence information for a style of the RIC control service or failure sequence information for a style of the RIC control service
  • the success sequence information includes: may include a RAN parameter ID and a RAN parameter container for each control operation performed by
  • the failure sequence information may include a RAN parameter ID and a RAN parameter container for each failed control operation.
  • the method performed by the E2 node transmits a configuration request message including radio access network (RAN) function information specific to a service model to RIC (
  • RAN radio access network
  • the process of transmitting to the RAN intelligent controller, the RAN function information includes information about one or more control actions, the process of receiving a setup response message from the RIC, and the RIC control request message transmitting to the RIC and receiving a RIC control acknowledgment message from the RIC, wherein the RIC control request message is identification information of a control operation among the one or more control actions
  • the RIC control confirmation message includes RIC control result (control outcome) information for the control operation, the RIC control result information, the event for the control operation in a specific protocol (protocol) of the event (event)
  • a reason may be included.
  • the event for the control operation may include failure or rejection of the control operation.
  • the RIC control result information includes a RAN parameter ID and a RAN parameter container
  • the RAN parameter ID is the specific protocol, quality of service (QoS) flow, or DRB. (data radio bearer)
  • the RAN parameter container may include information on the reason.
  • the RIC control result information includes information about the style of the RIC control service, and the style of the RIC control service includes radio bearer control, radio resource allocation, At least one of connected mode mobility, radio access control, dual connectivity, carrier aggregation, and idle mode mobility control may be indicated. have.
  • the RIC control result information includes at least one of success sequence information for a style of the RIC control service or failure sequence information for a style of the RIC control service
  • the success sequence information includes: may include a RAN parameter ID and a RAN parameter container for each control operation performed by
  • the failure sequence information may include a RAN parameter ID and a RAN parameter container for each failed control operation.
  • an apparatus of a radio access network (RAN) intelligent controller includes at least one transceiver and at least one processor, wherein the at least one processor is configured to control the at least one transceiver.
  • RAN radio access network
  • RIC radio access network intelligent controller
  • the request message includes identification information of a control action among the one or more control actions (action), and the RIC control confirmation message includes RIC control outcome information for the control action, and the RIC
  • the control result information may include a reason of an event for the control operation in a specific protocol.
  • the event for the control operation may include failure or rejection of the control operation.
  • the RIC control result information includes a RAN parameter ID and a RAN parameter container
  • the RAN parameter ID is the specific protocol, quality of service (QoS) flow, or DRB. (data radio bearer)
  • the RAN parameter container may include information on the reason.
  • the RIC control result information includes information about the style of the RIC control service, and the style of the RIC control service includes radio bearer control, radio resource allocation, At least one of connected mode mobility, radio access control, dual connectivity, carrier aggregation, and idle mode mobility control may be indicated. have.
  • the RIC control result information includes at least one of success sequence information for a style of the RIC control service or failure sequence information for a style of the RIC control service
  • the success sequence information includes: may include a RAN parameter ID and a RAN parameter container for each control operation performed by
  • the failure sequence information may include a RAN parameter ID and a RAN parameter container for each failed control operation.
  • the device of the E2 node includes at least one transceiver and at least one processor, and the at least one processor, through the at least one transceiver, provides a service model. Transmits a configuration request message including specific to radio access network (RAN) function information to a RAN intelligent controller (RIC), and the RAN function information includes one or more control actions is configured to include information about, receive a setup response message from the RIC, send a RIC control request message to the RIC, and receive a RIC control acknowledgment message from the RIC, the RIC control request message comprising: Including identification information of a control action among the one or more control actions (action), the RIC control confirmation message includes RIC control outcome information for the control action, the RIC control result information , may include a reason of an event for the control operation in a specific protocol.
  • RAN radio access network
  • RIC RAN intelligent controller
  • the event for the control operation may include failure or rejection of the control operation.
  • the RIC control result information includes a RAN parameter ID and a RAN parameter container
  • the RAN parameter ID is the specific protocol, quality of service (QoS) flow, or DRB. (data radio bearer)
  • the RAN parameter container may include information on the reason.
  • the RIC control result information includes information about the style of the RIC control service, and the style of the RIC control service includes radio bearer control, radio resource allocation, At least one of connected mode mobility, radio access control, dual connectivity, carrier aggregation, and idle mode mobility control may be indicated. have.
  • the RIC control result information includes at least one of success sequence information for a style of the RIC control service or failure sequence information for a style of the RIC control service
  • the success sequence information includes: may include a RAN parameter ID and a RAN parameter container for each control operation performed by
  • the failure sequence information may include a RAN parameter ID and a RAN parameter container for each failed control operation.
  • a method performed by a Near-RT (real time) RIC is a RIC control request message including identification information of a control action to the E2 node, and as a response to the RIC control request message, receiving a RIC control acknowledgment message or a RIC control failure message from the E2 node, the RIC control confirmation
  • the message or the RIC control failure message includes RIC control outcome information
  • the RIC control outcome information includes one or more RAN parameter sets
  • each of the one or more RAN parameter sets is a RAN parameter ID and RAN parameter value.
  • the RIC control request message includes information on the style of the RIC control service, and the style of the RIC control service includes radio bearer control, radio resource allocation, and connection.
  • Multiple styles including connected mode mobility, radio access control, dual connectivity, carrier aggregation, or idle mode mobility control can be one of them.
  • the RAN parameter ID of the RIC control result information indicates a data radio bearer (DRB) ID
  • the RAN parameter value of the RIC control result information is the It may include the value of DRB ID.
  • the method includes a process of receiving a setup request message including information on a RAN function definition specific to a service model from the E2 node and transmitting a configuration response message to the E2 node, wherein the information of the RAN function definition may include, for each control operation, a control operation ID, a control operation name, and a sequence of related RAN parameters. have.
  • the RIC control result information may include information on a failure reason when the request fails.
  • the method performed by the E2 node transmits a RIC control request message including identification information of a control action to a Near-RT (real time) RIC (radio access network (RAN)) intelligent controller), and as a response to the RIC control request message, transmitting a RIC control acknowledgment message or RIC control failure message to the Near-RT RIC, wherein the RIC The control acknowledgment message or the RIC control failure message includes RIC control outcome information, the RIC control outcome information includes one or more RAN parameter sets, and each of the one or more RAN parameter sets is a RAN parameter ID and RAN It can contain parameter values.
  • the RIC control request message includes information on the style of the RIC control service, and the style of the RIC control service includes radio bearer control, radio resource allocation, and connection.
  • Multiple styles including connected mode mobility, radio access control, dual connectivity, carrier aggregation, or idle mode mobility control can be one of them.
  • the RAN parameter ID of the RIC control result information indicates a data radio bearer (DRB) ID
  • the RAN parameter value of the RIC control result information is the It may include the value of DRB ID.
  • the method transmits a setup request message including information on a RAN function definition specific to a service model to the Near-RT RIC. and receiving a configuration response message from the Near-RT RIC, wherein the information of the RAN function definition includes, for each control operation, a control operation ID, a control operation name, and a sequence of related RAN parameters.
  • the information of the RAN function definition includes, for each control operation, a control operation ID, a control operation name, and a sequence of related RAN parameters.
  • the RIC control result information may include information on a failure reason when the request fails.
  • an apparatus of 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
  • a RIC control request message including identification information of a control action is transmitted to the E2 node, and as a response to the RIC control request message, a RIC control acknowledge message or RIC control failure (failure) configured to receive a message from the E2 node, wherein the RIC control acknowledgment message or the RIC control failure message includes RIC control outcome information, and the RIC control outcome information includes one or more RAN parameter sets
  • Each of the one or more RAN parameter sets may include a RAN parameter ID and a RAN parameter value.
  • the RIC control request message includes information on the style of the RIC control service, and the style of the RIC control service includes radio bearer control, radio resource allocation, and connection.
  • Multiple styles including connected mode mobility, radio access control, dual connectivity, carrier aggregation, or idle mode mobility control can be one of them.
  • the RAN parameter ID of the RIC control result information indicates a data radio bearer (DRB) ID
  • the RAN parameter value of the RIC control result information is the It may include the value of DRB ID.
  • the at least one processor through the at least one transceiver, a service model-specific (service model)-specific (to) RAN function (function) definition (definition) information including information (definition) setup) receive a request message from the E2 node, and send a setup response message to the E2 node, wherein the information of the RAN function definition includes, for each control operation, a control operation ID, a control operation name, and related It may include a sequence of RAN parameters.
  • the RIC control result information may include information on a failure reason when the request fails.
  • a control action configured to receive a RIC control request message including identification information of a Near-RT (real time) RIC (radio access network (RAN) intelligent controller), and in response to the RIC control request message, RIC control confirmation ( acknowledge) message or RIC control failure (failure) message is configured to transmit to the Near-RT RIC, the RIC control acknowledgment message or the RIC control failure message includes RIC control result (control outcome) information, the RIC control
  • the result information may include one or more RAN parameter sets, and each of the one or more RAN parameter sets may include a RAN parameter ID and a RAN parameter value.
  • the RIC control request message includes information on the style of the RIC control service, and the style of the RIC control service includes radio bearer control, radio resource allocation, and connection.
  • Multiple styles including connected mode mobility, radio access control, dual connectivity, carrier aggregation, or idle mode mobility control can be one of them.
  • the RAN parameter ID of the RIC control result information indicates a data radio bearer (DRB) ID
  • the RAN parameter value of the RIC control result information is the It may include the value of DRB ID.
  • the at least one processor through the at least one transceiver, a service model-specific (service model)-specific (to) RAN function (function) definition (definition) information including information (definition) setup) sending a request message to the Near-RT RIC, and further configured to receive a setup response message from the Near-RT RIC, the information of the RAN function definition, for each control operation, a control operation ID, a control operation name, and a sequence of associated RAN parameters.
  • a service model-specific (service model)-specific (to) RAN function (function) definition (definition) information including information (definition) setup) sending a request message to the Near-RT RIC, and further configured to receive a setup response message from the Near-RT RIC, the information of the RAN function definition, for each control operation, a control operation ID, a control operation name, and a sequence of associated RAN parameters.
  • the RIC control result information may include information on a failure reason when the request fails.
  • 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)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne un système de communication de 5ème génération (5G) ou pré-5G destiné à prendre en charge des débits de transmission de données supérieurs aux systèmes de 4ème génération (4G). Selon les modes de réalisation de la présente invention, le procédé mis en oeuvre par un contrôleur intelligent de réseau d'accès radio (RAN) (RIC) en temps quasi-réel (RT) peut comprendre les étapes suivantes : transmettre à un noeud E2 un message de demande de commande de RIC comprenant des informations d'identification relatives à une action de commande ; et recevoir, en provenance du noeud E2, un message d'accusé de réception de commande de RIC ou un message d'échec de commande de RIC en réponse au message de demande de commande de RIC, le message d'accusé de réception de commande de RIC ou le message d'échec de commande de RIC comprenant des informations de résultat de commande de RIC, les informations de résultat de commande de RIC comprenant au moins un ensemble de paramètres de RAN, chaque ensemble de paramètres de RAN comprenant un identifiant de paramètre de RAN et une valeur de paramètre de RAN.
PCT/KR2022/004458 2021-03-29 2022-03-29 Dispositif et procédé de commande d'un nœud e2 dans un système de communication sans fil Ceased WO2022211467A1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
CN202280025861.8A CN117204012A (zh) 2021-03-29 2022-03-29 用于在无线通信系统中控制e2节点的设备和方法
EP22781586.7A EP4247043A4 (fr) 2021-03-29 2022-03-29 Dispositif et procédé de commande d'un noeud e2 dans un système de communication sans fil
US18/189,768 US20230239710A1 (en) 2021-03-29 2023-03-24 Apparatus and method for e2 node control in wireless communication system

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
KR10-2021-0040762 2021-03-29
KR20210040762 2021-03-29
KR10-2021-0045524 2021-04-07
KR1020210045524A KR20220135129A (ko) 2021-03-29 2021-04-07 무선 통신 시스템에서 e2 노드 제어를 위한 장치 및 방법

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/189,768 Continuation US20230239710A1 (en) 2021-03-29 2023-03-24 Apparatus and method for e2 node control in wireless communication system

Publications (1)

Publication Number Publication Date
WO2022211467A1 true WO2022211467A1 (fr) 2022-10-06

Family

ID=83459482

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2022/004458 Ceased WO2022211467A1 (fr) 2021-03-29 2022-03-29 Dispositif et procédé de commande d'un nœud e2 dans un système de communication sans fil

Country Status (3)

Country Link
US (1) US20230239710A1 (fr)
EP (1) EP4247043A4 (fr)
WO (1) WO2022211467A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024120277A1 (fr) * 2022-12-06 2024-06-13 大唐移动通信设备有限公司 Procédé et appareil de commande d'économie d'énergie, et support de stockage
EP4398626A1 (fr) * 2023-01-05 2024-07-10 Nokia Solutions and Networks Oy Déclenchement d'événement sur la base d'événements de commande d'attribution de liste d'équipement utilisateur explicite

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20250106694A1 (en) * 2023-09-25 2025-03-27 Verizon Patent And Licensing Inc. Systems and methods for controlling a radio access network using one or more controls
US20250106722A1 (en) * 2023-09-25 2025-03-27 Mavenir Systems, Inc. Method and apparatus for encoding ran parameters over e2 interface using e2sm-rc for traffic steering-based sla optimization upon cell shutdown for energy savings activation
US20250238727A1 (en) * 2024-01-23 2025-07-24 Nokia Solutions And Networks Oy Federated learning with e2 node
US20250374120A1 (en) * 2024-05-29 2025-12-04 Dish Wireless L.L.C. Signaling storm mitigation

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200329381A1 (en) * 2019-07-19 2020-10-15 Joey Chou Orchestration and configuration of e2e network slices across 3gpp core network and oran

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200329381A1 (en) * 2019-07-19 2020-10-15 Joey Chou Orchestration and configuration of e2e network slices across 3gpp core network and oran

Non-Patent Citations (12)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; E1 Application Protocol (E1AP) (Release 16)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 38.463, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. V16.4.0, 4 January 2021 (2021-01-04), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , pages 1 - 237, XP051999716 *
3GPP TS 36.423
3GPP TS 36.473
3GPP TS 37.473
3GPP TS 38.413
3GPP TS 38.423
3GPP TS 38.463
3GPP TS 38.473
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: "O-RAN Working Group 3, Near-Real-time RAN Intelligent Controller, Architecture & E2 General Aspects and Principles", TECHNICAL SPECIFICATION O-RAN ALLIANCE, HTTPS://ORANDOWNLOADSWEB.AZUREWEBSITES.NET/SPECIFICATIONS, no. O-RAN.WG3.E2GAP-v01.01, 1 October 2020 (2020-10-01), pages 1 - 37, XP009539265 *
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 *
See also references of EP4247043A4

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024120277A1 (fr) * 2022-12-06 2024-06-13 大唐移动通信设备有限公司 Procédé et appareil de commande d'économie d'énergie, et support de stockage
EP4398626A1 (fr) * 2023-01-05 2024-07-10 Nokia Solutions and Networks Oy Déclenchement d'événement sur la base d'événements de commande d'attribution de liste d'équipement utilisateur explicite

Also Published As

Publication number Publication date
EP4247043A4 (fr) 2024-07-10
EP4247043A1 (fr) 2023-09-20
US20230239710A1 (en) 2023-07-27

Similar Documents

Publication Publication Date Title
WO2022211467A1 (fr) Dispositif et procédé de commande d'un nœud e2 dans un système de communication sans fil
WO2021141335A1 (fr) Appareil et procédé de commande de débit de données de coupe de réseau dans un système de communication sans fil
WO2023075214A1 (fr) Procédé et appareil pour la prise en charge d'un service d'informatique en périphérie pour un équipement utilisateur en itinérance dans un système de communication sans fil
WO2018110952A2 (fr) Appareil et procédé de commande de flux de données dans un système de communication sans fil
WO2021091225A1 (fr) Procédé et dispositif pour fournir un service à un dispositif utilisateur en utilisant une tranche de réseau dans un système de communication
WO2021091270A1 (fr) Procédé et appareil de sélection de tranches de réseau dans un système de communication sans fil
WO2018016853A1 (fr) Améliorations apportées et relatives à l'interconnectivité entre des réseaux
WO2021054747A1 (fr) Appareil et procédé de relocalisation d'upf psa dans un système de communication sans fil
WO2021066588A1 (fr) Appareil et procédé d'abonnement à un service, utilisant une interface e2 dans un système de communication de réseau d'accès sans fil
WO2022220640A1 (fr) Dispositif et procédé de commande d'un nœud e2 dans un système de communication sans fil
WO2022092981A1 (fr) Appareil et procédé de commande de nœud e2 dans un système de communication sans fil
WO2021091321A1 (fr) Dispositif et procédé permettant de prendre en charge la qualité de service dans un système de communication sans fil
WO2019172629A1 (fr) Appareil et procédé de commutation de technologie d'accès sans fil dans un système de communication sans fil
WO2015163743A1 (fr) Procédé et dispositif pour commander un trafic de données durant un accès à un réseau local (lan) sans fil et à un réseau cellulaire
WO2021091298A1 (fr) Procédé et appareil de prise en charge de l'auto-optimisation dans un système de communication sans fil
WO2015152659A1 (fr) Procédé et appareil pour orienter un trafic entre un réseau cellulaire et un réseau de réseau local (lan) sans fil dans un système de communication mobile
WO2022177333A1 (fr) Dispositif et procédé destinés à des informations de cellules et à une initialisation d'une interface de e2 dans un réseau d'accès radio
WO2023027531A1 (fr) Appareil et procédé de commande de nœud e2 et de commande de cellule dans un système de communication sans fil
WO2023282584A1 (fr) Procédé et dispositif de gestion d'équipement utilisateur dans un système de communication sans fil
WO2022039582A1 (fr) Procédé et dispositif de mesure de performances dans un système de communication sans fil
EP3482576A1 (fr) Procédé et appareil de commande ou de radiomessagerie d'un équipement d'utilisateur
WO2022086225A1 (fr) Procédé destiné à prendre en charge un transfert intercellulaire
WO2023014087A1 (fr) Dispositif et procédé de suppression d'informations relatives à une interface e2 dans un réseau d'accès radio
WO2022231245A1 (fr) Dispositif et procédé de commande d'un nœud e2 dans un système de communication sans fil
WO2020027630A1 (fr) Dispositif et procédé de sélection d'une cellule dans un système de communication sans fil

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: 22781586

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2022781586

Country of ref document: EP

Effective date: 20230616

WWE Wipo information: entry into national phase

Ref document number: 202280025861.8

Country of ref document: CN

WWE Wipo information: entry into national phase

Ref document number: 202317073125

Country of ref document: IN

NENP Non-entry into the national phase

Ref country code: DE