WO2023132359A1 - Nœud de ran et procédé - Google Patents

Nœud de ran et procédé Download PDF

Info

Publication number
WO2023132359A1
WO2023132359A1 PCT/JP2023/000150 JP2023000150W WO2023132359A1 WO 2023132359 A1 WO2023132359 A1 WO 2023132359A1 JP 2023000150 W JP2023000150 W JP 2023000150W WO 2023132359 A1 WO2023132359 A1 WO 2023132359A1
Authority
WO
WIPO (PCT)
Prior art keywords
ran node
handover
ran
cell
report
Prior art date
Application number
PCT/JP2023/000150
Other languages
English (en)
Japanese (ja)
Inventor
スタニスラフ フィリン
貞福 林
Original Assignee
日本電気株式会社
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
Application filed by 日本電気株式会社 filed Critical 日本電気株式会社
Publication of WO2023132359A1 publication Critical patent/WO2023132359A1/fr

Links

Images

Classifications

    • 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
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/20—Interfaces between hierarchically similar devices between access points

Definitions

  • the present disclosure relates to RAN nodes and methods.
  • Non-Patent Document 1 defines a signaling procedure of the radio network layer of the control plane between NG-RAN nodes in NG-RAN (Next Generation-Radio access network).
  • 3GPP TS 38.423 V16.7.0 (2021-10), "3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; Xn application protocol (XnAP) (Release 16)".
  • 3GPP TS 38.331 V16.6.0 (2021-09), "3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification (Release 16)”.
  • One of the purposes of the present disclosure is to provide a RAN node and method that contribute to gathering useful information for RAN nodes to provide cells. It should be noted that this objective is only one of the objectives that the embodiments disclosed herein seek to achieve. Other objects or problems and novel features will become apparent from the description of the specification or the accompanying drawings.
  • a radio access network (RAN) node comprising: at least one memory; and at least one processor coupled to said at least one memory, said User Equipment (UE) said RAN node: When handing over from a serving first cell to a serving second cell provided by another RAN node, the at least one processor generates a HO (Handover) REPORT regardless of whether the handover is successful or unsuccessful. from said other RAN node.
  • UE User Equipment
  • a radio access network (RAN) node comprising at least one memory and at least one processor coupled to said at least one memory, wherein User Equipment (UE) performs from the first cell served by the RAN node to the second cell served by the RAN node, the at least one processor, regardless of whether the handover is successful or unsuccessful, HO (Handover) REPORT to said other RAN node.
  • UE User Equipment
  • a method according to a third aspect is a method performed by a Radio Access Network (RAN) node, wherein a User Equipment (UE) is sent from a first cell served by said RAN node to a cell served by another RAN node. receiving a HO (Handover) REPORT from the other RAN node, regardless of whether the handover is successful or unsuccessful, when handover to a second cell to which the second cell is connected.
  • RAN Radio Access Network
  • UE User Equipment
  • a method according to a fourth aspect is a method performed by a Radio Access Network (RAN) node, in which User Equipment (UE) receives from a first cell served by another RAN node, sending a HO (Handover) REPORT to the other RAN node, regardless of whether the handover is successful or unsuccessful, when handover to a second cell to which the second cell is connected.
  • RAN Radio Access Network
  • UE User Equipment
  • FIG. 1 is a diagram illustrating a configuration example of a communication system according to a first embodiment
  • FIG. FIG. 3 is a diagram illustrating a configuration example of a RAN node
  • FIG. 10 is a diagram showing an example in which HO occurs in a communication system
  • 4 is a diagram illustrating an operation example of the communication system according to the first embodiment
  • FIG. FIG. 7 is a diagram showing a configuration example of a communication system according to a second embodiment
  • FIG. FIG. 9 is a diagram showing an operation example of the communication system according to the second embodiment
  • FIG. 10 illustrates a Resource Status Reporting initiation procedure
  • FIG. 10 illustrates a Resource Status Reporting procedure
  • FIG. 2 is a schematic diagram showing definitions of dedicated, preferred and shared resources
  • FIG. 10 is a diagram illustrating a structural example of detailed slice load information
  • FIG. 10 illustrates a case where a RAN node transmits HO REPORT
  • 2 is a block diagram showing a configuration example of a RAN node according to each embodiment
  • FIG. 1 is a diagram illustrating a configuration example of a communication system according to a first embodiment;
  • the communication system 1 is, for example, a fifth generation mobile communication system (5G system).
  • the 5G System is NR (New Radio Access), the fifth generation radio access technology.
  • the communication system 1 is not limited to the fifth generation mobile communication system, and may be a different mobile communication system such as an LTE (Long Term Evolution) system, an LTE-Advanced system, a sixth generation mobile communication system, or the like.
  • the communication system 1 may be another radio communication system including at least a radio access network (RAN) node and a user equipment (UE).
  • the communication system 1 may be a communication system in which ng-eNB (LTE evolved NodeB), which is a base station in LTE (Long Term Evolution), connects to a 5G core network (5GC) via an NG interface.
  • ng-eNB LTE evolved NodeB
  • a communication system 1 includes a RAN node 2 and a RAN node 3. Although only two RAN nodes are illustrated in FIG. 1, the communication system 1 may include three or more RAN nodes.
  • RAN node 2 and RAN node 3 may be gNBs.
  • the gNB is a node that terminates the NR user plane and control plane protocols for the UE and connects to the 5GC via the NG interface.
  • RAN node 2 and RAN node 3 may be ng-eNBs.
  • the ng-eNB is a node that terminates E-UTRA (Evolved Universal Terrestrial Radio Access) user plane and control plane protocols for the UE and connects with 5GC via the NG interface.
  • the RAN node 2 and the RAN node 3 may be CUs (Central Units) in a C-RAN (cloud RAN) configuration, or may be gNB-CUs.
  • gNB-CU is a logical node that hosts gNB's RRC (Radio Resource Control) protocol, SDAP (Service Data Adaptation Protocol) protocol and PDCP (Packet Data Convergence Protocol) protocol.
  • a gNB-CU is a logical node that hosts en-gNB's RRC and PDCP protocols that control the operation of one or more gNB-DUs (gNB-Distributed Units).
  • the gNB-CU terminates the F1 interface connecting with the gNB-DU.
  • RAN node 2 and RAN node 3 may be CP (Control Plane) Unit or gNB-CU-CP.
  • gNB-CU-CP (gNB-CU-Control Plane) is a logical node that hosts the RRC protocol and the control plane part of the PDCP protocol of gNB-CU for en-gNB or gNB.
  • gNB-CU-CP terminates the E1 interface connecting with gNB-CU-UP (gNB-CU-User Plane) and the F1-C interface connecting with gNB-DU.
  • gNB-CU-UP is a logical node that hosts the user plane part of the PDCP protocol of gNB-CU for en-gNB.
  • gNB-CU-UP terminates the E1 interface connecting with gNB-CU-CP and the F1-U interface connecting with gNB-DU.
  • the RAN node 2 and the RAN node 3 may be eNBs or eNB-CUs. Also, the RAN node 2 and the RAN node 3 may be EUTRAN (Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network) nodes or NG-RAN (Next generation Radio Access Network) nodes. EUTRAN nodes may be eNBs or en-gNBs. NG-RAN nodes may be gNBs or ng-eNBs. The en-gNB provides NR user plane and control plane protocol termination for the UE and acts as a secondary node in the EN-DC (NR Dual Connectivity).
  • UMTS Universal Mobile Telecommunications System
  • NG-RAN Next generation Radio Access Network
  • EUTRAN nodes may be eNBs or en-gNBs.
  • NG-RAN nodes may be gNBs or ng-eNBs.
  • the en-gNB provides NR user plane and control plane protocol termination for the UE and acts as
  • the inter-node interface may be the Xn interface (the network interface between NG-RAN nodes), the X2 interface, or other inter-node interfaces.
  • FIG. 2 is a diagram showing a configuration example of a RAN node.
  • RAN node 2 and RAN node 3 are collectively described as RAN node 100 .
  • RAN node 100 includes communication unit 101 and control unit 102 .
  • the communication unit 101 and the control unit 102 may be software or modules whose processing is executed by a processor executing a program stored in memory. Also, the communication unit 101 and the control unit 102 may be hardware such as circuits or chips.
  • the communication unit 101 connects and communicates with one or more other RAN nodes and core network nodes included in the access network.
  • the communication unit 101 also connects with the UE and performs communication. More specifically, the communication unit 101 receives various information from other RAN nodes, core network nodes, and UEs. Also, the communication unit 101 transmits various types of information to other RAN nodes, core network nodes, and UEs.
  • the control unit 102 executes various processes of the RAN node 100 by reading and executing various information and programs stored in the memory.
  • the control unit 102 performs processing according to any or all of setting information such as various information elements (IE: Information Elements), various fields, various conditions, etc. included in the message received by the communication unit 101 .
  • the control unit 102 is configured to be able to process multiple layers.
  • the multiple layers may include a physical layer, a MAC (Media Access Control) layer, an RLC (Radio Link Control) layer, a PDCP layer, an RRC layer, a NAS (non Access Stratum) layer, and the like.
  • RAN node 2 serves at least one cell 4-1 (first cell).
  • RAN node 2 operates cell 4-1 and connects and communicates with UEs in cell 4-1.
  • RAN node 3 provides at least one cell 4-2 (second cell).
  • RAN node 3 operates cell 4-2 and connects and communicates with UEs in cell 4-2.
  • the UE 5 is handed over from the cell 4-1 provided by the RAN node 2 to the cell 4-2 provided by the RAN node 3.
  • Cell 4-1 may be referred to as the source cell and cell 4-2 may be referred to as the target cell.
  • RAN node 2 may be referred to as a source RAN node and RAN node 3 may be referred to as a target RAN node.
  • Cell 4-2 is the serving cell after handover, and cell 4-1 may be referred to as the last serving cell.
  • Cells 4-1 and 4-2 may be adjacent cells. Here, the cells in adjacent positions may indicate a state in which the cells 4-1 and 4-2 are in contact with each other, or a state in which the cell 4-1 partially overlaps the cell 4-2. You may indicate that you are
  • RAN node 2, RAN node 3, and UE 5 execute a handover procedure as UE 5 moves from cell 4-1, which is the source cell, to cell 4-2, which is the target cell.
  • UE 5 communicates with RAN node 3 serving cell 4-2 after the handover procedure is complete.
  • FIG. 4 is a diagram illustrating an operation example of the communication system according to the first embodiment
  • step S1 the RAN node 3 transmits HO REPORT, which is information on handover, to the RAN node 2 regardless of whether there is a failure or not.
  • the RAN node 2 receives HO (Handover) REPORT, which is information on handover, from the RAN node 3 regardless of whether the handover has succeeded or failed.
  • the HO REPORT includes, for example, radio link state information of at least one of the RAN node 2 and the RAN node 3 at the timing after the handover, HO setting information set in the UE 5, and the cell 4-2 provided by the RAN node 3.
  • At least one of the IEs of cell load information at the timing after handover and an indicator indicating the type of handover may be included, but the included information is not limited to this.
  • the radio link state information of at least one of the RAN node 2 and the RAN node 3 will be described later in detail in paragraphs 0098 and 0101.
  • the HO setting information set in UE5 will be described later in detail in paragraphs 0059 and 0102.
  • the cell load information at the timing after handover for cell 4-2 provided by RAN node 3 will be detailed later in paragraph 0099.
  • the handover type indicators are detailed below in paragraphs 0063, 0097 and 0115.
  • the information that the RAN node 2 receives from the RAN node 3 is not limited to the name "HO REPORT", and may be other types of messages.
  • RAN node 2 may receive an IE from RAN node 3 that indicates information about the handover, regardless of whether the handover was successful or unsuccessful.
  • a specific example of IE is described above.
  • unsuccessful HO here means, for example, due to an unintended event, the target cell or beam is overloaded, or one or more slices required by this UE are not available.
  • the target RAN node may be overloaded.
  • Unintended events during handover may be, for example, Too Late Handover, Too Early Handover, Handover to Wrong Cell. Such unintended events are caused by Radio Link Failure of source or target RAN node. As an example of radio link failure, it is assumed that the reference signal value received from the RAN node by the UE performing handover is less than a predetermined threshold.
  • a UE receives a reference signal from a source cell (source RAN node) or a target cell (target RAN node) in response to the occurrence of an unintended event.
  • the reference signal value is represented by either RSRP (Reference Signal Received Power), RSRQ (Reference Signal Received Quality), or SINR (Signal to Interference plus Noise Ratio).
  • Beam failure is also assumed as another example of radio link failure.
  • radio link failure means that the quality of the signal from the source or target cell is so poor (eg, the SINR is below a threshold) that communication with this cell or beam cannot be continued. good too.
  • the details of 'failed handover' are further explained in paragraph 0063.
  • "successful handover" here may indicate that there was no unintended event, no cell/beam overload, no slice overload, and the handover was successful.
  • Another possible method of transmitting handover information is to trigger a UE measurement and then a SHO (successful HO) Report on a successful handover if any of the above-mentioned radio link failures occur in the handover. .
  • SHO uccessful HO
  • the RAN nodes do not acquire information about the handover.
  • the RAN nodes will not be able to obtain useful information for providing cells.
  • RAN node 3 transmits information regarding handover to RAN node 2, regardless of whether there is a failure or not, and RAN node 2 receives the information. Therefore, Embodiment 1 contributes to gathering useful information for RAN nodes to provide cells.
  • At least one of the RAN nodes 2 and 3 may be an AI-compatible RAN node (RAN AI/ML node).
  • An AI-enabled RAN node may be referred to as an AI-capable RAN node or an AI-capable RAN node.
  • a detailed description of the AI-compatible RAN node will be given later in paragraphs 0035 to 0040 in the second embodiment.
  • Embodiment 2 provides a specific example of the communication system shown in Embodiment 1.
  • FIG. 1 A block diagram illustrating an exemplary computing system.
  • FIG. 5 is a diagram showing a configuration example of a communication system according to the second embodiment.
  • the communication system 10 is a 5G system and comprises a RAN node 20 and a RAN node 30 which are gNBs or gNB-CUs.
  • the RAN node 20 provides cells 41-43. Specifically, the RAN node 20 operates cells 41-43 and connects and communicates with UEs in each cell. In this example, RAN node 20 is connected with UE 51 in cell 43 and UE 52 in cell 41 . Also in FIG. 5, RAN node 30 serves cells 44-46. Specifically, RAN node 30 serves cells 44-46 and connects and communicates with UEs in each cell. The RAN node 20 and the RAN node 30 establish an inter-node Xn interface and communicate with each other via the inter-node interface.
  • a cell 43 provided by the RAN node 20 is adjacent to a cell 44 provided by the RAN node 30.
  • adjacent cells refer to two or more cells that have at least partially overlapping coverage areas.
  • two or more RAN nodes with neighboring cells are called “neighboring RAN nodes”.
  • RAN nodes 20 and 30 are neighboring RAN nodes.
  • the UE 51 is handed over from the cell 43 provided by the RAN node 20 to the cell 44 provided by the RAN node 30.
  • Cell 43 may be referred to as the source cell and cell 44 may be referred to as the target cell.
  • RAN node 20 may be referred to as a source RAN node and RAN node 30 may be referred to as a target RAN node.
  • Cell 43 is the serving cell after handover, and cell 44 may be referred to as the last serving cell.
  • RAN node 20 executes a handover procedure as UE 51 moves from cell 43, which is the source cell, to cell 44, which is the target cell.
  • the UE 51 communicates with the RAN node 30 serving the cell 44 after the handover procedure is completed.
  • the RAN node 20 is an AI-compatible RAN node (RAN AI/ML node).
  • the RAN node 20 may be referred to as an AI-equipped RAN node or an AI-equipped RAN node.
  • the RAN node 20 is referred to as an AI-enhanced RAN node.
  • the RAN node 20 has an AI function that performs communication control based on information received from other devices (other network elements) including UEs such as the RAN node 30 and UE 51.
  • the AI function Equipped with machine learning (ML).
  • the AI/ML function executes HO performance optimization processing in this example, but the executed processing is not limited to this.
  • AI-enabled RAN node refers to, based on information received from other devices (other network elements), A RAN node that uses an AI/ML model for communication control.
  • the RAN node 20 may operate as an AI-capable RAN node, for example, by communicating with a RAN intelligence device (not shown) and using an AI/ML model held by the RAN intelligence device.
  • the RAN node 20 may have the function of a RAN intelligence device and operate as a RAN node equipped with an AI function by using an AI/ML model held by the RAN intelligence device.
  • the RAN node 20 may acquire an AI/ML model from the RAN intelligence device, and the RAN node 20 may operate as an AI-equipped RAN node by using the AI/ML model.
  • the RAN intelligence device is, for example, a control device responsible for making the RAN intelligent, and a control device that controls RAN communication.
  • the RAN intelligence device may be, for example, an RIC (RAN Intelligent Controller) defined by O-RAN (Open-RAN).
  • the RAN intelligence device performs mobility management such as policy management, analysis of various RAN information, AI-based function management, load balancing for each UE, radio resource management, QoS (Quality of Service) management, and handover control. conduct.
  • a configuration example of the RAN nodes 20 and 30 is as shown in FIG.
  • the communication unit 101 connects to and communicates with the RAN intelligence device.
  • the communication unit 101 may communicate with the RAN intelligence device, and the control unit 102 may use the AI/ML model held by the RAN intelligence device.
  • the communication unit 101 may communicate with the RAN intelligence device and acquire the AI/ML model held by the RAN intelligence device.
  • the control unit 102 may perform RAN communication control based on the information received by the communication unit 101 using the AI/ML model. Specifically, the control unit 102 inputs the information received by the communication unit 101 into the AI/ML model, various information related to RAN communication control, and/or various information related to UE communication control. You can output. The control unit 102 may control the RAN and the UE by transmitting such various information to the RAN node and the UE. The control unit 102 may machine-learn the AI/ML model based on the information received by the communication unit 101 . It should be noted that "learning”, “training” and “training” in the present disclosure have the meaning of automatically adjusting the parameters of an AI/ML model and constructing the model.
  • Embodiment 2 provides a deployment scenario in which AI functions in RAN nodes only serve one gNB or gNB-CU, which provides a fully distributed and autonomous solution.
  • an AI function in a RAN node may serve multiple gNBs or gNB-CUs.
  • the CN (Core Network) node 60 in FIG. 5 is NWDAF (Network Data Analytic Function) in this example.
  • NWDAF Network Data Analytic Function
  • the CN node 60 has a function of collecting and analyzing various data acquired by the network in 5GC.
  • OAM Operations, Administration and Management
  • an OAM (Operations, Administration and Management) device 70 has an operation management function of the communication system 10 .
  • FIG. 6 is a diagram illustrating an operation example of the communication system according to the second embodiment; Hereinafter, an overview of the processing performed by the communication system 10 will be described with reference to FIG. 6 .
  • the RAN node 20 knows the neighboring RAN node 30, and that the RAN node 20, the RAN node 30, the CN node 60 and the OAM device 70 have mutually established an interface between nodes. do.
  • the order of each step shown below is not limited unless otherwise specified. Further, the presence or absence of each step or the presence or absence of detailed processing of each step can be changed as appropriate.
  • the RAN node 20 acquires pre-HO adjacent load information from the adjacent RAN node 30 .
  • the adjacent load information here means load information about the adjacent RAN node 30 .
  • the RAN node 20 may acquire pre-HO neighbor load information from the neighbor RAN node 30 using the Resource Status Reporting procedure. Specifically, the RAN node 20 may acquire the pre-HO neighbor load information from the neighbor RAN node 30 using the Resource Status Update message.
  • This neighbor load information may include load information in each cell and/or each beam served by the RAN node 30 .
  • This load information may be information indicating traffic or information about traffic. Also, the load information may indicate the bit rate, or may be information related to the bit rate.
  • the load information may be information indicating GBR (Guaranteed Bit Rate) or non-GBR for at least one of DL (Downlink)/UL (UPlink).
  • the load information may be information indicating the amount of resource block usage, or may be information about the usage amount.
  • the load information may be information indicating the usage of total PRBs (Physical Resource Blocks).
  • the load information may be information indicating at least one of the following.
  • the load information includes information on dedicated, prioritized, and shared resources per cell and per slice defined by the OAM policy as detailed slice load information. may be included. Details of this will be described later.
  • the load information may also include information about the capacity of the cell.
  • a “slice” in this disclosure is a network slice provided by a core network (e.g., 5GC), as defined in 16.3.1 of Non-Patent Document 7, for example.
  • network slicing can be realized in NG-RAN of NR connected to 5GC and E-UTRA connected to 5GC.
  • a slice consists of a RAN part and a CN part, and slice support is based on the principle that traffic of different slices is handled by different PDU sessions.
  • a network can implement different slices by scheduling or providing different L1/L2 configurations.
  • a Network Slice Selection Assistance Information contains one or more S-NSSAIs, where the S-NSSAI is a combination of: ⁇ A mandatory SST (Slice/Service Type) field consisting of 8 bits (range 0 to 255) that identifies the slice type. ⁇ An optional 24-bit field that distinguishes slices with the same SST field. SD (Slice Differentiator) Field This list contains up to 8 S-NSSAIs.
  • the UE provides NSSAI for slice selection in RRCSetupComplete if the NAS provides it.
  • a network may support a large number (hundreds) of slices, but a UE need not support more than 8 slices simultaneously.
  • a Bandwidth reduced Low complexity (BL) UE or Narrow Band Internet of Things (NB-IoT) UE supports up to eight slices simultaneously.
  • slices are notified from the core network (e.g., 5GC) to the NAS layer of the UE, and from the NAS layer of the UE to the AS layer (e.g., RRC).
  • the UE selected and intended network slices may be referred to as selected NSSAI and intended NSSAI, respectively.
  • a selected NSSAI may be called an allowed NSSAI to mean a network slice that is allowed to be used by the core network.
  • the SST may be included in the S-NSSAI (that is, the S-NSSAI may contain the information of the SST).
  • Each network slice selected or intended by the UE may be identified by an identifier S-NSSAI.
  • the selected or intended network slice may be the S-NSSAI(s) included in the Configured NSSAI or the S-NSSAI(s) included in the Allowed NSSAI.
  • the S-NSSAIs in the Requested NSSAI included in the NAS registration request message should be part of the Configured NSSAI and/or Allowed NSSAI. Therefore, the intended network slice may be the S-NSSAI(s) included in the Requested NSSAI.
  • Such network slicing uses Network Function Virtualization (NFV) and software-defined networking (SDN) technologies, allowing multiple virtualized logical networks to be created on top of the physical network. do.
  • NFV Network Function Virtualization
  • SDN software-defined networking
  • Each virtualized logical network called a network slice or network slice instance, contains logical nodes and functions, and can handle specific traffic and used for signaling.
  • NG RAN or NG Core or both have a Slice Selection Function (SSF).
  • SSF Slice Selection Function
  • the SSF selects one or more suitable network slices for the NG UE based on information provided by the NG UE and/or the NG Core.
  • a plurality of slices are distinguished, for example, by services or use cases provided to UEs on each network slice.
  • Use cases include, for example, enhanced Mobile Broad Band (eMBB), Ultra-Reliable and Low Latency Communication (URLLC), and massive Machine Type Communication (mMTC). .
  • eMBB enhanced Mobile Broad Band
  • URLLC Ultra-Reliable and Low Latency Communication
  • mMTC massive Machine Type Communication
  • a RAN node providing communication to a UE uses the RAN slice and radio slice associated with the network slice of the core network selected for the UE to provide end-to-end network slicing to the UE. may be assigned to that UE.
  • the RAN node 20 acquires a measurement report including parameters related to HO determination from a UE (eg, UE51) located in the cell served by the RAN node 20.
  • this parameter may include quality information measured for the cell to which this UE belongs, for RAN node 20 and RAN node 30 .
  • the quality information may include at least one of RSRP, RSRQ, and SINR.
  • a specific example of "quality information measured about the cell to which this UE belongs” includes quality information (RSRP, etc.) of the cell where the UE is (located) and quality information (RSRP, etc.) of neighboring cells. good.
  • the former is cell 43 quality information and the latter is cell 44 quality information.
  • step S ⁇ b>1003 the RAN node 20 decides to hand over one of the UEs located in the cell served by the RAN node 20 to the RAN node 30 .
  • UE51 is handed over from cell 43 to cell 44 as shown in FIG.
  • step S1003 may be a normal handover decision without using AI/ML functions.
  • step S1004 after each handover determined in step S1003, the UE 51 sends a measurement report (state information detected before and after handover) to the RAN node 30.
  • the measurement report includes, for example, at least one of the following information.
  • ⁇ Radio link state of RAN node 20 before or after HO ⁇ Radio link state of RAN node 30 (adjacent RAN node) before or after HO ⁇ HO setting information of UE here
  • Before HO means, for example, within a set time (for example, 200 ms) before handover.
  • after HO means, for example, within a set time (for example, 200 ms) after handover. Specific examples of radio link status are described in paragraphs 0098 and 0101.
  • step S1005 corresponds to the operation example described in the first embodiment.
  • the RAN node 30 when multiple UEs transmit the state information of each UE to the RAN node 30 which is the target RAN node, the RAN node 30 generates a HO REPORT corresponding to each state information and transmits it to the RAN node 20.
  • a plurality of pieces of state information may be combined and transmitted to the RAN node 20 as a single HO REPORT.
  • the HO REPORT shown above may be, for example, a message similar to a Successful HO (SHO) REPORT.
  • This SHO REPORT is defined in Non-Patent Document 6, for example.
  • the HO REPORT described in the present disclosure differs from the SHO REPORT defined in Non-Patent Document 6 in at least one of the following points.
  • Sending HO REPORT from RAN node 30 to RAN node 20 after each UE handover from RAN node 20 to RAN node 30 Contents of HO REPORT it is defined that a SHO Report is provided when handover is successful with some radio link failure.
  • the definition of radio link failure is as described in paragraph 0026.
  • the RAN node 20 in embodiment 2 even if the handover is successful or after the handover fails due to other reasons mentioned in paragraph 0026, e.g. cell/beam/slice overload.
  • HO REPORT is provided.
  • the RAN node 20 can acquire at least one of the following information for AI/ML training in the RAN node 20 .
  • ⁇ Radio link state of RAN node 20 before or after HO ⁇ Radio link state of RAN node 30 (neighboring RAN node) before or after HO ⁇ HO setting information of UE ⁇ RAN node 20 load information (known at RAN node 20) before and/or after HO - Load information of the RAN node 30 at least either before or after HO
  • the RAN node 20 may receive the following information as the IE of the HO REPORT. ⁇ Radio link state of RAN node 20 before or after HO ⁇ Radio link state of RAN node 30 (neighboring RAN node) before or after HO ⁇ HO setting information of UE ⁇ Load information of the RAN node 30 before or after the HO
  • the RAN node 30 adds load information of the RAN node 30 before or after the HO to the state information received in step S1004.
  • the added information may be sent to the RAN node 20 as HO REPORT.
  • the HO configuration information of the UE is a description of the event used to trigger this handover with the corresponding HO trigger parameters (e.g., those defined in 5.5.4.2-5.5.4.7 of Non-Patent Document 2). be.
  • the RAN node 30 may acquire the HO setting information of the UE from the UE.
  • the RAN node 20 may refer to the HO configuration information of the UE using a kind of index during handover and send it to the RAN node 30 .
  • the index for example, an existing mobility information IE (Mobility Information IE) may be used.
  • the existing mobility information IE has the same meaning as the HO configuration information, and may be already specified RRC parameters.
  • the mobility information shown in 9.1.1.1 of Non-Patent Document 1 may be applied, as shown in Table 1 below.
  • step S1001 the neighbor load information of the RAN node 30 is reported to the RAN node 20 via the Resource Status Reporting procedure.
  • this is a generic, periodic report of load parameters, not sent just before and after each handover.
  • the HO REPORT may contain information indicating whether the handover is a successful handover (Successful HO) or an unsuccessful handover (Unsuccessful HO). This information may be called an HO report type indicator. When information indicating unsuccessful HO is included, it may further include information indicating the reason for unsuccessful HO. The reason for the HO failure may indicate an unintended event, cell and/or beam overload, and/or slice overload.
  • An example of HO REPORT is shown below. ">" indicates the hierarchy of data.
  • an unintended event during handover may be, for example, too early HO, too late HO, or HO to wrong cell. good.
  • Cell/beam overload indicates that the handover failed due to overloading of the target cell or beam.
  • Sample overload indicates that the handover failed due to overloading one or more slices needed by the UE in the target RAN node.
  • the RAN node 20 can obtain and use network information from the CN node 60 (NWDAF).
  • Network information transmitted from the CN node 60 may include, for example, network function load, slice load, and service experience.
  • Network information may include network performance.
  • the network information may also include UE mobility.
  • the network performance includes statistics or predictions of RAN node states such as gNBs, resource usage, communication and mobility performance, the number of UEs in the area of interest, and successful handovers ( may include the average percentage of successful handovers.
  • UE mobility may also be a time series of statistics or predictions of the location of a particular UE or group of UEs.
  • the RAN node 20 may acquire such network information from a device on the 5GC that is not limited to the CN node 60.
  • step S1007 since the RAN node 20 is an AI-enhanced RAN node, network information can be obtained from the OAM device 70 and used.
  • the network information transmitted from the OAM device 70 may include area information such as the cell in which the UE is located, traffic information, and statistical information.
  • the statistical information may include statistical information on handovers and statistical information on call processing such as call connection and call disconnection. Note that step S1006 may be performed before step S1007, after step S1007, or simultaneously with step S1007.
  • the RAN node 20 can receive network information from the CN node 60 and the OAM device 70.
  • a system including RAN nodes 20 , CN nodes 60 and OAM devices 70 contributes to AI-enabled RAN nodes 20 sending and receiving information to and from CN nodes 60 and OAM devices 70 .
  • the RAN node 20 can further optimize RAN communication control using the AI function that the RAN node 20 has based on the network information.
  • the RAN node 20 creates an AI/ML model held by the RAN intelligence device or an AI/ML model acquired from the RAN intelligence device based on the various information (for example, measured values) received in steps S1001 to S1007. Conduct initial or periodic training.
  • the AI/ML model inputs information received from other devices (other network elements: RAN node 30 in this example) and performs RAN communication control (machine learning: ML). is a model.
  • the AI/ML model inputs information received from other devices in steps S1001 to S1007, and outputs at least one of optimized HO setting information and handover-related support information.
  • the RAN node 20 sends HO related information including feedback from failed HO events (i.e. negative HO events) and successful HO events (i.e. positive HO events) to other RAN nodes (e.g. RAN node 30). Therefore, in steps S1001 to S1007, the RAN node 20 updates the AI/ML model by performing reinforcement learning based on information received from other devices.
  • HO related information including feedback from failed HO events (i.e. negative HO events) and successful HO events (i.e. positive HO events) to other RAN nodes (e.g. RAN node 30). Therefore, in steps S1001 to S1007, the RAN node 20 updates the AI/ML model by performing reinforcement learning based on information received from other devices.
  • the RAN node 20 inputs the information received in steps S1001-S1007 to, for example, a training device for updating the AI/ML model.
  • the RAN node 20 may also input the handover results associated with the measurement report containing the results measured by the UE into the training device for AI/ML model training, e.g. using reinforcement learning. can.
  • the RAN node 20 determines whether the handover related to the measurement report from the UE was a successful HO (successful HO) or a reason for the unsuccessful HO (unsuccessful HO) (for example, an unintended event or slice/cell/beam overload) into the training device.
  • Unintended events include "Too Late Handover”, “Too Early Handover”, and “Handover to Wrong Cell”. So, if the failed handover is due to an unintended event, the RAN node 20 also inputs to the training device information about which unintended event it fell under.
  • the RAN node 20 first performs AI/ML model training using the above-described input information received from other network elements and the results of the HO. Since the handover result is reported from the UE after handover, the RAN node 20 can perform reinforcement learning on the AI/ML model.
  • the RAN node 20 inputs the above information newly received by the RAN node 20 into the AI/ML model, and the AI/ML model, for the given information, trains from one cell X to another Predict the outcome of HO to cell Y, which is a cell.
  • the AI/ML model also predicts the probability of the HO outcome in case of handover from cell X to cell Y.
  • the AI/ML model inputs the above information newly received by the RAN node 2 and outputs information about the probability of handover from cell X to cell Y and what result it will have.
  • the AI/ML model compares the handover result probabilities of cells configured with different HO configuration information.
  • the AI/ML model proposes (outputs) HO parameters for a specific set of neighboring cells that can increase the probability of successful HO among cells provided by RAN nodes managed by the RAN node 20 .
  • the RAN node 20 receives various information related to the result of the actual handover by performing steps S1001 to S1007 described above.
  • the RAN node 20 further improves the AI/ML model by performing reinforcement learning on the AI/ML model based on the received information using a trainer.
  • the AI/ML models used in this disclosure may be novel or may be known ML models (eg, described in Non-Patent Documents 8-10).
  • step S1009 the RAN node 20 uses the information received in steps S1001-S1007 to generate the following information when the AI/ML is sufficiently trained.
  • the RAN node 20 improves the probability of normal HO by transmitting the generated information to the RAN node 30 and the UE 51 .
  • ⁇ UE HO setting parameters provided by the RAN node 20 ⁇ HO decision parameters used by the RAN node 20 for HO decision
  • HO configuration parameters (configuration information) of the UE are used to trigger this handover using the corresponding HO trigger parameters, for example as defined in 5.5.4.2-5.5.4.7 of Non-Patent Document 2 event description.
  • the UE HO configuration information is information related to the radio link state.
  • step S1010 the RAN node 20 transmits the HO configuration parameters generated in step S1009 to the UE (for example, UE52) served by the RAN node 20.
  • step S1011 when a new handover is triggered, the HO configuration parameters and HO decision parameters generated in step S1009 are used for HO decision based on AI/ML. As a result, the RAN node 20 can more accurately determine whether handover to the target UE is possible or not according to the situation.
  • the RAN node 20 can use some algorithm to make the HO decision.
  • HO decision parameters are used in this HO decision algorithm.
  • the HO decision algorithm considers the UE QoS flow, the QoS parameters and their mapping on slices, the load information of neighboring RAN node cells, etc. in addition to the radio link conditions as HO decision parameters. It may be determined whether there are sufficient resources for the required slices for the target UE in cells of neighboring RAN nodes (eg, RAN node 30).
  • step S1001 the RAN node 20 acquires pre-HO neighbor load information from the neighbor RAN node 30 using the Resource Status Reporting procedure.
  • the Resource Status Reporting procedure itself is described in Non-Patent Document 1, 8.4.10 and 8.4.11.
  • FIG. 7 shows the Resource Status Reporting Initiation procedure used to set the cell load report.
  • NG-RAN node 200 sends a RESOURCE STATUS REQUEST message to NG-RAN node 300 in step S2001, and in response, NG-RAN node 300 sends a RESOURCE STATUS RESPONSE message to NG-RAN node 300 in step S2002.
  • Send to node 200 .
  • a parameter e.g., indicator
  • FIG. 8 shows the Resource Status Reporting procedure used to obtain information on cell load.
  • a RESOURCE STATUS UPDATE message is sent from NG-RAN node 300 to NG-RAN node 200 as shown in FIG.
  • the RAN node 20 acquires pre-HO neighbor load information from the neighbor RAN node 30.
  • FIG. 8 shows the Resource Status Reporting procedure used to obtain information on cell load.
  • the RESOURCE STATUS UPDATE message in FIG. 8 contains information on the capacity and load of the cell, as described in step S1001 above. For example, at least one of the following may be included. At least one of DL (Downlink) / UL (UPlink), GBR (Guaranteed Bit Rate), non-GBR, or total PRB (Physical Resource Block) in at least one of each cell or each beam provided by RAN node 30 ) usage amount ⁇ Individual load information in at least one of NUL (Normal UL) / SUL (Supplementary UL) ⁇ GBR per cell, non-GBR, or total for each DL/UL of slice PRB usage and/or Information on dedicated, prioritized and shared resources per cell and per slice defined by OAM policy, which is detailed slice load information (hereinafter simply dedicated, prioritized and (Also described as shared resource)
  • FIG. 9 is a schematic diagram showing definitions of dedicated, priority and shared resources.
  • FIG. 9 shows the structure of RRM Policy Ratio defined in 4.3.36 of Non-Patent Document 4, showing rRMPolicyMaxRatio, rRMPolicyMinRatio and rRMPolicyDedicatedRatio.
  • the definition shown in 4.3.36.1 of Non-Patent Document 4 is described below.
  • the attribute rRMPolicyMaxRatio defines the maximum resource usage quota of the associated rRMPolicyMemberList, including at least one of shared, priority and dedicated resources.
  • the sum of the "rRMPolicyMaxRatio" values assigned to all RRMPolicyRatio(s) names contained in the same MangedEntity can be greater than 100.
  • the attribute rRMPolicyMinRatio defines the minimum resource usage quota of the associated RRMPolicyMemberList, including at least one of priority and dedicated resources, meaning the resource quota that must be guaranteed to be used by the associated rRMPolicyMemberList. do.
  • the sum of the "rRMPolicyMaxRatio" values assigned to all RRMPolicyRatio(s) names contained in the same MangedEntity must be 100 or less.
  • the attribute rRMPolicyDedicatedRatio defines the dedicated resource usage quota of the RRMPolicyMemberList containing dedicated resources.
  • rRMPolicyDedicatedRatio means a resource shared with other rRMPolicyMemberList(s) (ie rRMPolicyMemberList(s) defined with RRMPolicyRatio(s) name by the same ManagedEntity).
  • a shared resource does not guarantee the use of the associated rRMPolicyMemberList.
  • the shared resource quota is represented by [rRMPolicyMaxRatio-rRMPolicyMinRatio].
  • Preferred resource means the resource that the associated RRMPolicyMemberList uses preferentially.
  • RRMPolicyMemberList ie rRMPolicyMemberList(s) defined with the RRMPolicyRatio(s) name by the same ManagedEntity.
  • the priority resource allocation is represented by [rRMPolicyMinRatio-rRMPolicyDedicatedRatio].
  • Dedicated Resource Means that the resource is for the exclusive use of the associated RRMPolicyMemberList. These resources cannot be shared even if not used by the associated RRMPolicyMember.
  • the dedicated resource allocation is represented by [rRMPolicyDedicatedRatio].
  • Detailed slice load information may be information about resources for each slice ID.
  • Information about resources includes, for example, information indicating assigned shared resources/information indicating shared resources in use/information indicating assigned priority resources/information indicating priority resources in use/allocated dedicated It may be a combination of one or more of information indicating resources/information indicating dedicated resources in use.
  • detailed slice load information may have the following example structure. > Slice ID 1 to S >> Allocated shared resource >> Used shared resource >> Allocated prioritized resource >> Used prioritized resource >> Allocated dedicated resource >> Used dedicated resource
  • FIG. 10 is a diagram showing a structural example of this detailed slice load information. FIG. 10 shows that the above six resources are included in the total resources of the cell.
  • the shared resource in use constitutes part or all of the allocated shared resource
  • the priority resource in use constitutes and uses part or all of the allocated priority resource.
  • Dedicated resources constitute part or all of the dedicated resources assigned.
  • Radio Resource Status is defined as IE in the RESOURCE STATUS UPDATE message.
  • the radio resource status IE indicates the usage of PRBs in each cell, each Synchronization Signal Block (SSB) area, and each slice for all downlink and uplink traffic, and for downlink and uplink scheduling. indicates the usage status of the PDCCH CCE (Control Channel Element).
  • SSB Synchronization Signal Block
  • PDCCH CCE Control Channel Element
  • Table 3 An example of a more detailed report is shown in Table 3 below.
  • the underlined IEs in Table 3 relate to dedicated, priority and shared resources.
  • the Presence of each IE for dedicated, priority, and shared resources is described as "O”, but the Presence of any part or all of these IEs may be "M”. .
  • all the IEs need not be included in the radio resource status IE, and any one or more IEs may be included.
  • steps S1002-S1004 are omitted since it is as described above.
  • step S1005 the RAN node 30 transmits a HO REPORT to the RAN node 20 after the handover.
  • Step S1005 corresponds to the operation example described in the first embodiment.
  • multiple HO REPORTs from multiple UEs are combined into a single HO REPORT by a RAN node (e.g. RAN node 30) adjacent to RAN node 20 before being sent to RAN node 20, and then It may be sent to the RAN node 20 .
  • a RAN node e.g. RAN node 30
  • FIG. 11 is a diagram showing a case where NG-RAN node 200 sends HO REPORT to NG-RAN node 300 using the ACCESS AND MOBILITY INDICATION procedure.
  • the procedure described in this disclosure has two main points. The first is that after each HO from RAN node 20 to RAN node 30, a HO REPORT is sent from RAN node 30 to RAN node 20 as an ACCESS AND MOBILITY INDICATION message (where signaling is optimized (You can also combine multiple reports to create a more comprehensive view.)
  • the HO REPORT can be provided to the RAN node 20 in Embodiment 2 even if the handover is successful. Examples of definitions of successful HO and unsuccessful HO are described in paragraph 0026.
  • the following options are also possible when the process that provides the HO REPORT is performed. send a HO REPORT after each handover reduce signaling by combining and sending a set number (e.g. 10) of HO REPORTs together HO within a set time interval (e.g. 1 second) Reduce signaling by combining REPORTs and sending them together Other options, and combinations of these options
  • the second point concerns the content of the HO REPORT.
  • the HO REPORT may include, for example, any of the following items. ⁇ Radio link state of RAN node 20 before or after HO ⁇ Radio link state of RAN node 30 (neighboring RAN node) before or after HO ⁇ HO setting information of UE ⁇ The timing of the load information “before HO” and “after HO” of the RAN node 30 at least either before HO or after HO is as described above.
  • the content of the HO REPORT may be illustrated by the following example structure.
  • the HO REPORT is the UE HO REPORT type indicator, RAN AI/ML node cell ID and/or neighbor RAN node cell ID information is included for each UE distinguished by ID.
  • the RAN AI/ML node cell ID is the ID of the source RAN node and the neighbor RAN node cell ID is the ID of the target RAN node.
  • the RAN AI/ML node cell ID IE may include at least one of radio link state or UE HO configuration information
  • the adjacent RAN node cell ID IE may include at least radio link state or load information. Either may be included.
  • the radio link state IE of the RAN AI/ML node cell ID may have pre-HO and post-HO information
  • at least one of the radio link state or load information IE of the neighboring RAN node cell ID may include: It may have pre-HO and post-HO information.
  • a specific example of each IE of HO REPORT will be described below.
  • the HO REPORT type indicator may include, for example, at least one of the following information.
  • >Successful HO (unsuccessful HO)/Unsuccessful HO (unsuccessful HO) Reason for HO failure if HO fails >>> Unintended event 1 (e.g. HO too early, HO too late, HO to wrong cell) >>>...
  • Unintended event N e.g. HO too early, HO too late, HO to wrong cell
  • Unintended event N >>> cell and/or beam overload >>> slice overload
  • the radio link state includes at least one of RSRP, RSRQ, and SINR, which are quality information measured by the UE.
  • the values may also include UE uplink reference signal measurements, if available.
  • the load information includes information about cell capacity and load. For example, at least one of the following information may be included. - At least one of DL (Downlink) / UL (UPlink), GBR (Guaranteed Bit Rate), non-GBR, or total PRB (Physical Resource Block) usage in at least one of each cell or each beam At least one ⁇ Individual load information in at least one of NUL (Normal UL) / SUL (Supplementary UL) ⁇ At least of GBR, non-GBR, and total PRB usage per cell for each DL/UL of slice Information about dedicated, prioritized, and shared resources per cell and per slice defined by OAM policies, which is detailed slice load information where the detailed slice load information is represented in the example structure below be able to. > Slice ID 1 to S >> Allocated shared resource >> Used shared resource >> Allocated prioritized resource >> Used prioritized resource >> Allocated dedicated resource >> Used dedicated resource This detailed slice load information may be the same as the detailed slice load information shown in step S1001.
  • Table 4 shows an example of each IE in the HO REPORT.
  • the Presence of each IE related to slice load information is described as "M”, but the Presence of any part or all of these IEs may be "O". Also, among the IEs related to slice load information listed in Table 4, not all IEs need to be included in the UE HO setting information, and any one or more IEs may be included.
  • the pre-HO and post-HO radio link states may be indicated, for example, as follows.
  • Presence of each IE is described as "M”, but Presence may be "O" for any part or all of these IEs.
  • Presence may be "O" for any part or all of these IEs.
  • not all IEs need to be included in the radio link state, and one or more arbitrary IEs may be included in the radio link state.
  • the UE HO configuration information listed in Table 4 can be represented in the following configuration example.
  • UE HO setting information ⁇ HO event ID ⁇ HO trigger parameters
  • the HO event ID is one of events A1, ..., A6 specified in 5.5.4.2-5.5.4.7 of Non-Patent Document 2.
  • the HO trigger parameter is the actual value of this event parameter that the UE uses when triggering this event.
  • Condition A1-1 below is used for the UE to enter the event report, and condition A1-2 is used for the UE to leave the event report.
  • ⁇ Inequality A1-1 (Condition to enter) Ms - Hys > Thresh ⁇ Inequality A1-2 (withdrawal condition) Ms + Hys ⁇ Thresh
  • Ms the serving cell measurement result without considering the offset.
  • Hys is the hysteresis parameter for this event (ie the hysteresis defined in reportConfigNR for this event).
  • Thresh is the threshold parameter for this event (ie the a1-threshold defined in reportConfigNR for this event).
  • Ms is expressed in dBm for RSRP and in dB for RSRQ and RS-SINR. Hys is expressed in dB and Thresh is expressed in the same units as Ms.
  • This event may be used when a UE moves towards the edge of a cell, triggers a mobility procedure, but then returns to good coverage before the mobility procedure is complete.
  • Condition A2-1 is used for the UE to enter the event report and condition A2-2 is used for the UE to leave the event report.
  • ⁇ Inequality A2-1 (Condition to enter) Ms + Hys ⁇ Thresh ⁇ Inequality A2-2 (withdrawal condition) Ms - Hys > Thresh
  • Ms - Hys > Thresh
  • Ms is the serving cell measurement result without considering the offset.
  • Hys is the hysteresis parameter for this event (ie the hysteresis defined in reportConfigNR for this event).
  • Thresh is the threshold parameter for this event (ie the a2-threshold defined in reportConfigNR for this event).
  • Ms is expressed in dBm for RSRP and in dB for RSRQ and RS-SINR. Hys is expressed in dB and Thresh is expressed in the same units as Ms.
  • Event A2 is typically used to trigger mobility procedures when the UE moves towards the edge of the cell.
  • Event A3 when neighbor cell is offset better than SpCell
  • Condition A3-1 below is used for the UE to enter the event report
  • condition A3-2 is used for the UE to leave the event report.
  • ⁇ Inequality A3-1 (Condition to enter) Mn + Ofn + Ocn - Hys > Mp + Ofp + Ocp + Off
  • Mn + Ofn + Ocn + Hys ⁇ Mp + Ofp + Ocp + Off
  • Ocn is the cell-specific offset of the neighbor cell (ie cellIndividualOffset defined in measObjectNR corresponding to the frequency of the neighbor cell) and is set to 0 if not set in the neighbor cell.
  • ⁇ Mp is the measurement result of SpCell without considering the offset.
  • Ofp is the SpCell measurement object-specific offset (ie, offsetMO defined in the measObjectNR corresponding to the SpCell).
  • Ocp is the cell-specific offset of the SpCell (ie cellIndividualOffset defined in the measObjectNR corresponding to the SpCell) and is set to 0 if not set for the SpCell.
  • Hys is the hysteresis parameter for this event (ie the hysteresis defined in reportConfigNR for this event).
  • Off is the offset parameter for this event (ie the a3-offset defined in reportConfigNR for this event).
  • - Mn, Mp are expressed in dBm for RSRP and in dB for RSRQ and RS-SINR.
  • Ocn, Ofp, Ocp, Hys, and Off are expressed in dB. This event is typically used for intra- or inter-frequency handover procedures.
  • Condition A4-1 below is used for the UE to enter the event report, and condition A4-2 is used for the UE to leave the event report.
  • ⁇ Inequality A4-1 (Condition to enter) Mn + Ofn + Ocn - Hys > Thresh
  • ⁇ Inequality A4-2 (withdrawal condition) Mn + Ofn + Ocn + Hys ⁇ Thresh
  • Mn is the measurement result of neighboring cells without considering the offset.
  • Ofn is the measurement object specific offset of the neighboring cell (ie offsetMO defined in the measObjectNR corresponding to the neighboring cell).
  • Ocn is the measurement target specific offset of the neighbor cell (ie cellIndividualOffset defined in the measObjectNR corresponding to the neighbor cell) and is set to 0 if not set in the neighbor cell.
  • Hys is the hysteresis parameter for this event (ie the hysteresis defined in reportConfigNR for this event).
  • Thresh is the threshold parameter for this event (ie the a4-threshold defined in reportConfigNR for this event).
  • - Mn is expressed in dBm for RSRP and in dB for RSRQ and RS-SINR.
  • Ocn, and Hys are expressed in dB
  • Thresh is expressed in the same unit as Mn. This event can be used for serving cell coverage independent handover procedures, eg load balancing.
  • Event A5 (SpCell worse than threshold 1 and neighbor better than threshold 2) Conditions A5-1 and A5-2 below are used for the UE to enter the event report, and conditions A5-3 and A5-4 are used for the UE to leave the event report.
  • ⁇ Inequality A5-1 (entry condition 1) Mp + Hys ⁇ Thresh1 ⁇ Inequality A5-2 (entry condition 2) Mn + Ofn + Ocn - Hys > Thresh2
  • Inequality A5-3 (withdrawal condition 1)
  • Mp-Hys > Thresh1 ⁇ Inequality A5-4 (withdrawal condition 2) Mn + Ofn + Ocn + Hys ⁇ Thresh2
  • the variables in the above formula are defined as follows.
  • - Mp is the measurement result of NR SpCell without considering the offset.
  • Mn is the measurement result of neighboring cells without considering the offset.
  • Ofn is the measurement object specific offset of the neighboring cell (ie offsetMO defined in the measObjectNR corresponding to the neighboring cell).
  • Ocn is the cell-specific offset of the neighbor cell (ie cellIndividualOffset defined in the measObjectNR corresponding to the neighbor cell) and is set to 0 if not set in the neighbor cell.
  • Hys is the hysteresis parameter for this event (ie the hysteresis defined in reportConfigNR for this event).
  • Thresh1 is the threshold parameter for this event (ie a5-threshold1 defined in reportConfigNR for this event).
  • Thresh2 is the threshold parameter for this event (ie a5-threshold2 defined in reportConfigNR for this event).
  • - Mn, Mp are expressed in dBm for RSRP and in dB for RSRQ and RS-SINR. Ofn, Ocn, and Hys are expressed in dB.
  • Thresh1 is expressed in the same units as Mp and Thresh2 is expressed in the same units as Mn. This event is typically used for intra- or inter-frequency handover procedures.
  • Condition A6-1 is used for the UE to enter the event report, and condition A6-2 is used for the UE to leave the event report.
  • ⁇ Inequality A6-1 (Condition for entry) Mn + Ocn - Hys > Ms + Ocs + Off
  • Mn + Ocn + Hys ⁇ Ms + Ocs + Off
  • Ocn is the cell-specific offset of the neighboring cell (ie cellIndividualOffset defined in the associated measObjectNR) and is set to 0 if not set in the neighboring cell.
  • • Ms is the serving cell measurement result without considering the offset.
  • Ocs is the cell-specific offset of the serving cell (ie cellIndividualOffset defined in the associated measObjectNR) and is set to 0 if not set for the serving cell.
  • Hys is the hysteresis parameter for this event (ie the hysteresis defined in reportConfigNR for this event).
  • Off is the offset parameter for this event (ie the a6-offset defined in reportConfigNR for this event).
  • Mn Ms are expressed in dBm for RSRP and in dB for RSRQ and RS-SINR. Ocn, Ocs, Hys, and Off are expressed in dB.
  • steps S1006-S1007 are omitted since it is as described above.
  • the RAN node 20 performs initial and periodic training of the AI/ML model based on the received information (eg measurements).
  • the received information eg measurements.
  • the input parameters to the model are the information from steps S1005-1007 and additional information.
  • HO REPORT > UE ID 1..I >>UE HO REPORTID 1..I >>> HO REPORT TYPE INDICATOR >>> RAN AI/ML NODE CELL ID >>>>Radio link status>>>>>Before HO>>>>>After HO>>>>UE HO setting information>>>Adjacent RAN node cell ID >>>> Wireless link status >>>>> Before HO >>>>> After HO >>>>>> Load information >>>>>> Before HO >>>>>> After HO Step S1006: Network information from NWDAF Step S1007: Additional network information from OAM includes UE QoS flows and QoS parameters and their mapping on slices.
  • a QoS flow is a set of QoS parameters associated with a downlink or uplink data transmission session (eg, one downlink or uplink application).
  • QoS parameters are parameters that specify, for example, the minimum data rate or maximum delay that must be met when transmitting data associated with this QoS flow.
  • the HO REPORT type indicator indicates whether the handover was successful or unsuccessful for a given input parameter and, in case of a failed handover, also indicates the reason for the failed handover. This is used for supervised/reinforcement learning.
  • the AI/ML model of the RAN node 20 can predict whether the HO from the cell of the RAN node 20 to the neighboring RAN node 30 will succeed or fail for a given new set of input parameters. can. Also, the AI/ML model can predict the probability of successful HO and failed HO during HO from the cell of RAN node 20 to the cell of RAN node 30 .
  • the AI/ML model can predict the probabilities of successful HO and unsuccessful HO for different values of the HO configuration parameters and HO decision parameters of the RAN node 20, which are the HO configuration parameters of the RAN node 20 and the HO Allows to choose the best values for the decision parameters.
  • Any known or new model can be used for the accurate AI/ML model used in AI/ML. Examples of known models and how to implement them are described, for example, in Non-Patent Documents 8-10.
  • the AI/ML model starts working after training and generates two sets of parameters. ⁇ UE HO setting parameters provided by the RAN node 20 ⁇ HO decision parameters used by the RAN node 20 for HO decision
  • the AI/ML model predicts the probabilities of successful HO and unsuccessful HO for different values of HO setup parameters of cells of the RAN node 20, thereby predicting the HO setup of the cells of the RAN node 20.
  • Optimal values for the parameters can be selected.
  • the UE HO configuration information is information about the state of the radio link.
  • RAN node 20 uses some algorithm to make HO decision.
  • HO decision parameters are used in this HO decision algorithm. Adequate resources for the required slices for a given UE are available in neighboring RAN node cells, considering UE QoS flows and QoS parameters and their mapping on slices, loading information of neighboring RAN node cells, etc., in addition to radio link conditions. It is possible to determine whether the The AI/ML model can choose the best values for the HO decision parameters in a similar way, eg by maximizing the HO success probability.
  • step S1010 the RAN node 20 transmits the HO configuration parameters generated to be optimized in step S1009 to the UEs served by the RAN node 20.
  • step S1011 the HO setting parameters and HO decision parameters generated to be optimized are used for HO decision based on AI/ML.
  • RAN node 20 when handover occurs, RAN node 20 receives information on handover from RAN node 30 regardless of whether HO was successful or unsuccessful. Conversely, the RAN node 30 also transmits information regarding handover to the RAN node 20 regardless of whether the HO was successful or unsuccessful. Therefore, the RAN node 20 can gather useful information for serving cells.
  • the HO REPORT may also include radio link state information of at least one of the RAN node 20 and the RAN node 30 at the timing after the handover. This allows the RAN node 20 to gather information that is particularly important for serving cells.
  • the HO REPORT may include HO setting information set in the UE. This allows the RAN node 20 to gather information that is particularly important for serving cells.
  • the HO REPORT may also include cell load information at the timing after the handover regarding the cells provided by the RAN node 30. This allows the RAN node 20 to gather information that is particularly important for serving cells.
  • the HO REPORT may also include an indicator indicating the type of handover. This allows the RAN node 20 to collect important information regarding handover control.
  • This indicator may include a parameter indicating SHO (successful HO) if the handover is successful. This allows the RAN node 20 to collect important information regarding handover control.
  • This indicator may include parameters that indicate cell or beam overload or slice overload as the reason for the failed HO. This allows the RAN node 20 to collect important information regarding handover control.
  • the HO REPORT may further include cell load information regarding the cells provided by the RAN node 20 at the timing after handover. This allows the RAN node 20 to gather information that is particularly important for serving cells.
  • the RAN node 30 includes the state information of the radio link of at least one of the RAN node 20 and the RAN node 30 at the timing after the handover received from the UE 51 in the HO REPORT and transmits it to the RAN node 20. good too. This allows the RAN node 20 to collect important information that particularly contributes to improving UE communication.
  • the RAN node 20 may receive the HO REPORT as part of the Access And Mobility Indication message each time a handover is made, regardless of whether the HO was successful or unsuccessful. Conversely, the RAN node 30 sends the HO REPORT as part of the Access And Mobility Indication message to the RAN node 20 every time a handover is made, regardless of whether the HO was successful or unsuccessful. good too. This allows the RAN node 20 to collect information necessary for handover control.
  • the RAN node 20 learns the AI function of the RAN node 20 that performs communication control. It may be generated by a function. This allows the RAN node 20 to more accurately control handover.
  • the RAN node 20 or the RAN node 20 at the timing after the handover 30 HO setting information set in the UE 51, cell load information at the timing after the handover regarding the second cell provided by the RAN node 30, and an indicator indicating the type of handover.
  • a HO REPORT containing at least one of them may be received from the RAN node 30 .
  • RAN node 30 sends the above-mentioned HO REPORT to RAN node 20. You may send. This allows the RAN node 20 to collect information necessary for handover control.
  • the present disclosure is not limited to the above embodiments, and can be modified as appropriate without departing from the scope.
  • the technology described in the present disclosure is not limited to dedicated communication devices, and can be applied to any device having a communication function.
  • FIG. 12 is a block diagram illustrating a configuration example of a RAN node according to each embodiment;
  • RAN node 100 includes RF (Radio Frequency) transceiver 1001 , network interface 1003 , processor 1004 and memory 1005 .
  • RF transceiver 1001 performs analog RF signal processing to communicate with the UE.
  • RF transceiver 1001 may include multiple transceivers.
  • RF transceiver 1001 is coupled with antenna 1002 and processor 1004 .
  • RF transceiver 1001 receives modulation symbol data (or OFDM (Orthogonal Frequency Division Multiplexing) symbol data) from processor 1004 , generates a transmit RF signal, and provides the transmit RF signal to antenna 1002 .
  • RF transceiver 1001 also generates a baseband received signal based on the received RF signal received by antenna 1002 and provides it to processor 1004 .
  • the network interface 1003 is used to communicate with network nodes (e.g., other core network nodes).
  • the network interface 1003 may include, for example, an IEEE (Institute of Electrical and Electronics Engineers) 802.3 series compliant network interface card (NIC).
  • IEEE Institutee of Electrical and Electronics Engineers
  • NIC network interface card
  • a processor 1004 performs data plane processing and control plane processing including digital baseband signal processing for wireless communication.
  • digital baseband signal processing by the processor 1004 may include MAC layer and Physical layer signal processing.
  • the processor 1004 may include multiple processors.
  • the processor 1004 includes a modem processor (e.g., DSP (digital signal processor)) that performs digital baseband signal processing, and a protocol stack processor (e.g., CPU (central processing unit) or MPU (micro processor unit))).
  • DSP digital signal processor
  • protocol stack processor e.g., CPU (central processing unit) or MPU (micro processor unit)
  • the memory 1005 is configured by a combination of volatile memory and nonvolatile memory.
  • Memory 1005 may include multiple physically independent memory devices. Volatile memory is, for example, Static Random Access Memory (SRAM) or Dynamic RAM (DRAM) or a combination thereof.
  • the non-volatile memory is masked Read Only Memory (MROM), Electrically Erasable Programmable ROM (EEPROM), flash memory, or hard disk drive, or any combination thereof.
  • Memory 1005 may include storage remotely located from processor 1004 . In this case, processor 1004 may access memory 1005 via network interface 1003 or an I/O interface (not shown).
  • the memory 1005 may store software modules (computer programs) including instructions and data for processing by the RAN node 100 described in the above embodiments.
  • processor 1004 may be configured to retrieve and execute such software modules from memory 1005 to perform the processing of RAN node 100 described in the above embodiments.
  • processors included in each device in the above-described embodiments execute one or more programs containing instructions for causing a computer to execute the algorithms described with reference to the drawings. .
  • the signal processing method described in each embodiment can be realized.
  • a program includes a set of instructions (or software code) that, when read into a computer, cause the computer to perform one or more of the functions described in the embodiments.
  • the program may be stored in a non-transitory computer-readable medium or tangible storage medium.
  • non-transitory computer readable media or tangible storage media may include random-access memory (RAM), read-only memory (ROM), flash memory, solid-state drives (SSD), or other Including memory technology, CD-ROM, digital versatile disk (DVD), Blu-ray disc or other optical disk storage, magnetic cassette, magnetic tape, magnetic disk storage or other magnetic storage device.
  • the program may be transmitted on a transitory computer-readable medium or communication medium.
  • transitory computer readable media or communication media include electrical, optical, acoustic, or other forms of propagated signals.
  • UE User Equipment
  • mobile station mobile terminal, mobile device, wireless device, etc.
  • wireless device a wireless An entity connected to a network through an interface.
  • a radio access network (RAN) node The RAN node is at least one memory; at least one processor coupled to said at least one memory; When User Equipment (UE) is handed over from a first cell served by the RAN node to a second cell served by another RAN node, the at least one processor indicates whether the handover has succeeded or failed. configured to receive HO (Handover) REPORT from said other RAN node, regardless of whether RAN node.
  • UE User Equipment
  • the HO REPORT includes radio link state information of at least one of the RAN node and/or another RAN node at a timing after the handover; The RAN node according to Appendix 1.
  • the HO REPORT includes HO configuration information configured in the UE, The RAN node according to Appendix 1 or 2.
  • the HO REPORT further includes cell load information for a second cell served by another RAN node at a timing after the handover; 4.
  • the HO REPORT includes an indicator indicating the type of handover, 5.
  • the indicator includes a parameter indicating SHO (successful HO) when the handover is successful, The RAN node according to Supplementary Note 5.
  • the indicators include parameters indicating cell or beam overload or slice overload if the handover fails.
  • the at least one processor is further configured to receive the HO REPORT as an Access And Mobility Indication message each time a handover is made regardless of whether the handover is successful or unsuccessful. 8. The RAN node according to any one of Appendixes 1-7.
  • the at least one processor learns the AI function of the RAN node that performs communication control based on the received HO REPORT, and after learning, the HO setting information set to the UE to which the RAN node provides communication services. Generated by said AI function, 9.
  • the RAN node according to any one of Appendixes 1-8.
  • Appendix 10 A radio access network (RAN) node, at least one memory; at least one processor coupled to said at least one memory; When User Equipment (UE) is handed over from a first cell served by another RAN node to a second cell served by the RAN node, the at least one processor indicates whether the handover has succeeded or failed.
  • UE User Equipment
  • the HO REPORT includes radio link state information of at least one of the RAN node and/or another RAN node at a timing after the handover; The RAN node according to Supplementary Note 10.
  • the HO REPORT includes HO configuration information configured in the UE, 12.
  • the HO REPORT further includes cell load information for a second cell served by the RAN node at a timing after the handover; 13.
  • the RAN node according to any one of appendices 10-12.
  • the at least one processor includes, in the HO REPORT, radio link state information of at least one of the RAN node or another RAN node at a timing after the handover received from the UE, and the other configured to transmit to a RAN node, 14.
  • the RAN node according to any one of appendices 10-13.
  • the HO REPORT includes an indicator indicating the type of handover, 15.
  • the RAN node according to any one of appendices 10-14.
  • the indicator includes a parameter indicating SHO (successful HO) when the handover is successful, 16.
  • the RAN node according to Supplementary Note 15.
  • the indicators include parameters indicating cell or beam overload or slice overload if the handover fails. 17.
  • the RAN node according to Supplementary Note 15 or 16.
  • the at least one processor is further configured to send the HO REPORT as an Access And Mobility Indication message each time a handover is made regardless of whether the handover is successful or unsuccessful. 18.
  • the RAN node according to any one of clauses 11-17.
  • UE User Equipment
  • a method performed by a radio access network (RAN) node comprising: The method determines whether handover is successful or unsuccessful when a User Equipment (UE) is handed over from a first cell served by another RAN node to a second cell served by the RAN node. regardless of sending a HO (Handover) REPORT to said other RAN node; method including.
  • RAN radio access network
  • a radio access network (RAN) node The RAN node is at least one memory; at least one processor coupled to said at least one memory;
  • UE user equipment
  • the RAN node or another RAN at the timing after the handover State information of at least one radio link of a node, HO configuration information configured in the UE, cell load information at the timing after the handover regarding the second cell provided by the other RAN node, the type of the handover an indicator indicating the HO (Handover) REPORT from the other RAN node.
  • RAN node When user equipment (UE) is handed over from a first cell provided by the RAN node to a second cell provided by another RAN node, the RAN node or another RAN at the timing after the handover State information of at least one radio link of a node, HO configuration information configured in the UE, cell load information at the timing after the handover regarding the second cell provided by the other RAN node, the type of the handover an indicator indicating the HO (Handover) REPORT
  • a radio access network (RAN) node at least one memory; at least one processor coupled to said at least one memory;
  • UE User Equipment
  • the at least one processor performs Radio link state information of at least one of the RAN node and other RAN nodes, HO configuration information configured in the UE, cell load information at the timing after the handover for a second cell provided by the RAN node. , an indicator indicating the type of handover, to the other RAN node.
  • RAN node A radio access network (RAN) node, at least one memory; at least one processor coupled to said at least one memory;
  • UE User Equipment
  • the at least one processor performs Radio link state information of at least one of the RAN node and other RAN nodes, HO configuration information configured in the UE, cell load information at the timing after the handover for a second cell provided by the RAN node.
  • an indicator indicating the type of handover, to the other RAN node.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente divulgation concerne un nœud de RAN et un procédé qui contribuent à la collecte d'informations utiles pour qu'un nœud de RAN fournisse une cellule. Un nœud de réseau d'accès radio (RAN) (2) selon un aspect comprend au moins une mémoire, ainsi qu'au moins un processeur couplé à ladite au moins une mémoire. Lorsque un équipement utilisateur (UE) passe d'une première cellule fournie par le nœud de RAN (2) à une seconde cellule fournie par un autre nœud de RAN (3), ledit au moins un processeur est configuré pour recevoir un rapport de transfert intercellulaire (HO) en provenance de l'autre nœud de RAN (3), indépendamment du fait que le transfert intercellulaire est réussi ou non.
PCT/JP2023/000150 2022-01-06 2023-01-06 Nœud de ran et procédé WO2023132359A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2022-001091 2022-01-06
JP2022001091 2022-01-06

Publications (1)

Publication Number Publication Date
WO2023132359A1 true WO2023132359A1 (fr) 2023-07-13

Family

ID=87073680

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2023/000150 WO2023132359A1 (fr) 2022-01-06 2023-01-06 Nœud de ran et procédé

Country Status (1)

Country Link
WO (1) WO2023132359A1 (fr)

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; Xn general aspects and principles (Release 16)", 3GPP TS 38.420, no. V16.0.0, 16 July 2020 (2020-07-16), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , pages 1 - 16, XP051925470 *
ANONYMOUS: "3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on RAN-centric data collection and utilization for LTE and NR (Release 16)", 3GPP TR 37.816, no. V16.0.0, 23 July 2019 (2019-07-23), pages 1 - 35, XP051754712 *
ERICSSON: "AI/ML Load Balancing TP", 3GPP TSG RAN WG3 #114-E R3-216114, 9 November 2021 (2021-11-09), XP052082753 *
QUALCOMM INC.: "Inter-system Load Balancing", 3GPP TSG RAN WG3 #110-E R3-206185, 23 October 2020 (2020-10-23), XP051945758 *
SHARP: "Discussion on HO type indicator for CHO and DAPS", 3GPP TSG RAN WG2 #116-E R2-2111016, 22 October 2021 (2021-10-22), XP052067454 *

Similar Documents

Publication Publication Date Title
EP3596969B1 (fr) Commande de transfert intercellulaire conforme à la tranche
US8934902B2 (en) Method of notifying switching information and base station
JP7150756B2 (ja) システムメッセージ通知、送信方法および装置
US20210243839A1 (en) Data analysis and configuration of a distributed radio access network
US8817752B2 (en) Method and apparatus for determining matching of inter-cell reselection parameters and handover parameters
KR20200019221A (ko) Nr에서의 통합 rlf 검출, 다중 빔 rlm 및 풀-다이버시티 bfr 메커니즘
US11412414B2 (en) Communication methods and communications apparatuses
EP2645774B1 (fr) Procédés et dispositifs de libération de ressources relatives au contexte d'un équipement utilisateur
US9717031B2 (en) Management of resources amongst parties sharing the same radio access network
WO2012041043A1 (fr) Procédé et système de rapport de résultat de mesure supplémentaire
JP2017518683A (ja) Ｂｂｕプールにおける仮想基地局移行のための方法及び装置
RU2732736C1 (ru) Способ связи, вторичный узел сети и терминал
JP7132336B2 (ja) 多重アップリンクキャリアが関与する無線リンクの維持
WO2022044908A1 (fr) Terminal et système de communication sans fil
US11064406B2 (en) Method for using a short signal identity in communication between a radio terminal and a radio access node, a radio terminal and a radio access node
CN113225750B (zh) 一种信息上报、获取方法、终端及网络侧设备
US9668180B1 (en) Systems and methods for identifying and resolving cell ID confusion between neighboring cells in a wireless network
CN111132210B (zh) 测量事件中的SpCell确定方法和装置
WO2023132359A1 (fr) Nœud de ran et procédé
CN106688269B (zh) 用于确定无线设备是否是由于负载平衡原因而切换到目标小区的合适候选者的无线电网络节点和方法
WO2023171198A1 (fr) Nœud ran et procédé
WO2023171201A1 (fr) Nœud ran et procédé
JP2022540592A (ja) 無線通信ネットワークの条件付き構成
WO2023171210A1 (fr) Nœud de ran et procédé
WO2023132326A1 (fr) Nœud ran et procédé

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

Country of ref document: EP

Kind code of ref document: A1