WO2022234817A1 - Dispositif de commande pour améliorer le processus de transfert intercellulaire d'une station de relais sans fil, dispositif de relais et procédé de commande - Google Patents

Dispositif de commande pour améliorer le processus de transfert intercellulaire d'une station de relais sans fil, dispositif de relais et procédé de commande Download PDF

Info

Publication number
WO2022234817A1
WO2022234817A1 PCT/JP2022/019319 JP2022019319W WO2022234817A1 WO 2022234817 A1 WO2022234817 A1 WO 2022234817A1 JP 2022019319 W JP2022019319 W JP 2022019319W WO 2022234817 A1 WO2022234817 A1 WO 2022234817A1
Authority
WO
WIPO (PCT)
Prior art keywords
relay
control device
handover
information
control
Prior art date
Application number
PCT/JP2022/019319
Other languages
English (en)
Japanese (ja)
Inventor
ヤンウェイ 李
洋樹 武田
Original Assignee
Kddi株式会社
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 Kddi株式会社 filed Critical Kddi株式会社
Publication of WO2022234817A1 publication Critical patent/WO2022234817A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/24—Cell structures
    • H04W16/26—Cell enhancers or enhancement, e.g. for tunnels, building shadow
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/10—Reselecting an access point controller
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/34—Modification of an existing route
    • H04W40/36—Modification of an existing route due to handover
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present invention relates to advanced technology for handover processing in wireless relay stations.
  • IAB Integrated Access and Backhaul
  • 3GPP 3rd Generation Partnership Project
  • IAB Integrated Access and Backhaul
  • an IAB node that operates as a relay device establishes a wireless access link with an IAB donor that is connectable to the core network and controls relay transmission, using the function of a terminal device.
  • multiple IAB nodes can be directly connected to one IAB donor.
  • an IAB node after an IAB node establishes a connection with an IAB donor, it can establish a connection with another IAB node acting as a terminal device. That is, multiple IAB nodes can be connected in series to one IAB donor.
  • the side of the IAB donor when viewed from the IAB node, the side of the IAB donor is called upstream, and the opposite side is called downstream. That is, in a configuration in which an IAB donor and IAB node A are directly connected, IAB node B is directly connected to IAB node A, and IAB node C is directly connected to IAB node B, from the perspective of IAB node B, IAB node A and IAB node A are directly connected.
  • the IAB donor is the upstream device and IAB node C is the downstream device.
  • An IAB donor can perform a handover to switch destination IAB donors or IAB nodes. This allows the IAB node to perform relay transmission with an IAB donor or IAB node having better radio quality as an upstream device.
  • the predetermined condition is, for example, when the wireless quality of the adjacent cell is better than the wireless quality of the connected cell by a predetermined level or more, or when the wireless quality of the connected cell is equal to or lower than a predetermined value.
  • a predetermined value for example, when the wireless quality of the adjacent cell is better than the wireless quality of the connected cell by a predetermined level or more, or when the wireless quality of the connected cell is equal to or lower than a predetermined value.
  • multiple IAB nodes may be connected in series.
  • the IAB donor to be connected may be switched to IAB nodes downstream from the IAB node.
  • handover is not prepared for the downstream IAB node, and communication disruption may occur in the downstream IAB node.
  • the present invention provides a technique for eliminating or reducing communication disruptions during IAB node handover.
  • a control device is a control device that controls relay transmission in accordance with the 3rd Generation Partnership Project (3GPP) standard, wherein a plurality of relay stations are wirelessly connected in series from another control device. transmitting a message to the other control device in response to a first relay device included in the plurality of relay stations satisfying a predetermined condition when a first communication path is formed; first information for enabling handover for switching a connection destination from under control of said other control device to under control of said control device, and from said first relay device among said plurality of relay stations; receiving means for receiving, from the other control device, second information indicating a second relay device connected on the opposite side of the control device in the first communication path, from the first control device; When the relay device is handed over under the control device, the first relay device and the second relay device form a second communication path by operating as a relay station for relaying the communication of the control device.
  • 3GPP 3rd Generation Partnership Project
  • generation means for generating setting information including settings for the above; transmission means for transmitting the setting information to the other control device; and said second relay device including said first relay device and said second relay device using said setting information in response to said first relay device being handed over under said control device. and setting means for setting two communication paths.
  • a control device performs relay transmission in a communication system in which a communication path is formed by serially wirelessly connecting a plurality of relay stations from the control device according to the 3rd Generation Partnership Project (3GPP) standards.
  • the control device to control the control device without transmitting a message to the control device in response to a first relay device included in the plurality of relay stations satisfying a predetermined condition; first information for enabling handover to switch a connection destination from a subordinate to a subordinate of another control device; a notification means for notifying the other control device of second information indicating a second relay device connected on the opposite side; receiving means for receiving setting information for operating the first relay device and the second relay device as relay stations for relaying communication of the other control device when handover is performed under the control of the control device; and transmission means for transmitting setting information to the first relay device.
  • 3GPP 3rd Generation Partnership Project
  • a relay device forms a communication path by serially wirelessly connecting a plurality of relay stations from a first control device that controls relay transmission according to the 3rd Generation Partnership Project (3GPP) standards.
  • a relay device included in the plurality of relay stations in a communication system Condition information indicating a condition under which the relay device should switch the connection destination of the wireless connection from under the control of the first control device to under control of the second control device, and setting information after the handover, wherein , first setting information including information for connecting to the second control device and operating as a relay station;
  • a second relay device including information for another relay device included in the plurality of relay stations to connect to the second control device after the handover and operate as a relay station.
  • the first execution means for executing a handover under control of the second control device; and in response to being connected under the control of the second control device by the handover, the second control device based on the first setting information.
  • FIG. 1 is a diagram illustrating a configuration example of a wireless communication system.
  • FIG. 2 is a diagram showing a hardware configuration example of an IAB donor and an IAB node.
  • FIG. 3 is a diagram illustrating a functional configuration example of an IAB donor that is a handover source.
  • FIG. 4 is a diagram showing an example of the functional configuration of the IAB donor of the handover destination.
  • FIG. 5 is a diagram showing a functional configuration example of an IAB node that executes handover.
  • FIG. 6 is a diagram illustrating an example of the flow of processing performed in a wireless communication system.
  • FIG. 1 shows a configuration example of a wireless communication system according to this embodiment.
  • This radio communication system is a radio relay transmission system using IAB (Integrated Access and Backhaul) defined by the 3GPP standards.
  • a wireless relay transmission system using IAB includes IAB donors (IAB donors X to Z) and IAB nodes (IAB nodes AH).
  • the IAB donor has a function (Central Unit, CU) as a control device that controls relay transmission and a function (Distributed Unit, DU) as a base station device that performs processing for transmission and reception of radio signals.
  • CU Central Unit
  • DU Distributed Unit
  • an IAB node has a function (Mobile Termination, MT) and DU to operate as a terminal device, and wirelessly connects to any IAB donor by MT, either directly or via another IAB node.
  • the IAB node then operates to relay communications between User Equipment (UE) and the IAB donor, performing relay transmissions under the control of the connected IAB donor's CU.
  • UE User Equipment
  • FIG. 1 shows a state in which IAB node A is directly wirelessly connected to IAB donor X.
  • IAB node A relays communications between IAB donor X and its directly connected UEs under the control of IAB donor X's CU.
  • the IAB node A establishes a connection with the MT of the IAB node F in a state in which the relay transmission of the IAB donor X can be executed in the same procedure as the connection procedure with the UE, and the IAB node F establishes a connection with the IAB donor X.
  • a communication path with relay transmission is established by executing the settings related to relay transmission between them.
  • an IAB node G is connected to the IAB node F
  • an IAB node H is connected to the IAB node G
  • a communication path involving relay transmission is established.
  • a communication path is established by wirelessly connecting a plurality of relay stations (IAB nodes) in series.
  • IAB node H may be directly connected to IAB node F
  • IAB node G and IAB node H may be connected to IAB node F in parallel.
  • the first communication path from the DU of IAB donor X to IAB node G and the second communication path from the DU of IAB donor X to IAB node H each have a plurality of relays. It can be said that the stations are arranged wirelessly connected in series.
  • a communication path configured by IAB donor Y and IAB node B , and communication paths formed by IAB donor Z and IAB nodes CE.
  • An IAB node can connect with DUs of IAB donors or other IAB nodes using MT, which functions as a terminal device as described above.
  • An IAB MT can perform a handover to switch the destination IAB donor/IAB node in the same way as a normal UE.
  • handover includes a conventional first method in which a terminal device switches connection destinations in accordance with an instruction from the network side, and a method in which a terminal device switches connection destinations from the network side when a predetermined condition is satisfied in the terminal device.
  • the terminal equipment to be handed over measures the surrounding radio quality and notifies it to the base station equipment. Based on the notified radio quality, the base station apparatus determines another base station apparatus as a candidate for handover of the terminal apparatus, and requests handover of the terminal apparatus to the other base station apparatus. Another base station apparatus executes settings for establishing connection with the terminal apparatus before handover is actually performed, generates setting information, and transmits the setting information to the base station apparatus to which the terminal apparatus is connected. Upon receiving the setting information, the base station apparatus notifies the terminal apparatus of the setting information and predetermined conditions for executing handover.
  • the configuration information can include, for example, a physical cell identity (PCI) that enables designation of the handover destination.
  • PCI physical cell identity
  • the predetermined condition may differ, for example, for each handover destination base station apparatus.
  • the predetermined condition for example, in the terminal device, the radio quality of the adjacent cell is better than the radio quality of the cell being connected to by a predetermined level or more, or the radio quality of the cell being connected is less than or equal to a predetermined value. can be determined to be satisfied if When the terminal device determines that the notified predetermined condition is satisfied, the terminal device disconnects the connection with the base station device without receiving an instruction message from the connected base station device, and performs preliminary handover. establishes a connection with another base station apparatus whose setting information is notified to.
  • the handover source base station apparatus receives a handover success notification from another handover destination base station apparatus to which connection with the terminal apparatus has been established, and another handover candidate set in advance as a handover candidate.
  • the base station apparatus can be notified of the cancellation of the handover and cleared of the preset information.
  • IAB node F performs a conditional handover from IAB node A to an IAB node under IAB donor Y or IAB donor Z will be described.
  • IAB node F performs a conditional handover from IAB node A to an IAB node under IAB donor Y or IAB donor Z.
  • IAB node F connects to IAB node B under IAB donor Y.
  • IAB donor Y sends IAB node F to the downstream side of IAB node B (opposite side of IAB donor Y when viewed from IAB node B) with respect to the communication path formed by connecting IAB node F to IAB node B.
  • a communication path in the downlink direction (direction from IAB donor Y to IAB node F) and a communication path in the uplink direction (direction from IAB node F to IAB donor Y) can be defined separately.
  • the IAB donor Y then associates the communication path with the identifier and notifies the IAB node F of the information.
  • IAB donor Y also determines an IP (Internet Protocol) address to be assigned to IAB node F and a BAP (Backhaul Adaptation Protocol) address for relay transmission, and notifies IAB node F of these addresses. Further, IAB donor Y may, for example, inform IAB node F of its own (and other IAB nodes as appropriate) IP and BAP addresses. Also, resource information available for the IAB may be notified to the IAB node F as configuration information.
  • IP Internet Protocol
  • BAP Backhaul Adaptation Protocol
  • the handover identification information (for example, CondReconfigID) associated with the IAB node B of the handover destination is notified to the IAB node F in association with the various information to be notified.
  • the IAB donor Y notifies the IAB node B of configuration information (for example, BAP configuration) such as route information after the IAB node F is connected.
  • IAB node F When IAB node F performs a conditional handover to IAB node B, these setting information should be set in advance by IAB donor Y and IAB node B, and notified to IAB node F. Since these configuration information are shared among IAB donor Y, IAB node B, and IAB node F before handover, IAB node F can start relay transmission immediately after establishing a connection with IAB node B. It can be performed. As a result, it is possible to shorten the time during which the communication of the UE connected to the IAB node F is interrupted.
  • IAB node F By the IAB node F handing over, the IAB node G and the IAB node H on the downstream side of the IAB node F (opposite side of the IAB donor X in the communication path from the IAB node F) are also connected to the IAB donor Y. Become. However, although IAB donor Y can pre-configure IAB node F, which is the entity that executes conditional handover, IAB node G and IAB node H, which are connected to its downstream side, do not exist. not recognized. For this reason, IAB donor Y cannot preconfigure IAB nodes G and H, and communication of UEs connected to IAB node G and IAB node H will be delayed until the handover of these IAB nodes is completed. It may be interrupted for a long time until the setting as a relay device is completed.
  • the handover source IAB donor sends the handover target IAB node to the handover destination candidate IAB donor (IAB donor who has the handover destination IAB node under its control).
  • the handover destination candidate IAB donor IAB donor who has the handover destination IAB node under its control.
  • the handover source IAB donor sends the handover target IAB node to the handover destination candidate IAB donor (IAB donor who has the handover destination IAB node under its control).
  • the handover destination candidate IAB donor IAB donor who has the handover destination IAB node under its control.
  • IAB donors Y and Z may be notified of the information to indicate. According to this, IAB donors Y and Z can recognize what kind of communication path will be configured including IAB nodes G and H when IAB node F performs handover. become.
  • the handover source IAB donor adds handover identification information to each IAB donor or another IAB node that is a candidate to which the IAB node to be handover is connected, and the above-mentioned first information and second information Along with this, the IAB donors of candidate handover destinations may be notified.
  • This notification is defined by the 3GPP standard, for example, when the IAB node F is in a state where handover may be executed, and is transmitted and received between the base station devices (IAB donors) after the candidate for the handover destination is determined. can be done using the HANDOVER REQUEST message.
  • the handover-related processing initiated by the IAB node here includes, for example, disconnection processing from the handover source IAB donor and random access processing to the handover destination IAB donor.
  • the handover destination candidate IAB donor is, for example, the IAB node indicated by the first information is connected to itself or another IAB node under itself, and the IAB node indicated by the second information further downstream. are connected in series to form a network topology.
  • BAP addresses and IP addresses are set for each of the IAB nodes specified by the first information and the second information. Also, for each communication path between the IAB donor and each IAB node, identification information that identifies the communication path for both uplink and downlink is set. Note that this setting is similar to the conventional IAB setting, so further details will not be described here.
  • IAB donor Y performs settings assuming that a network topology is formed in which MT of IAB node F is connected to DU of IAB node B, and IAB nodes G and H are further downstream connected in series. .
  • IAB donor Y sets BAP addresses and IP addresses for each of IAB nodes F to H, for example. Then, the IAB donor Y notifies the IAB node B, which is a candidate for the handover destination of the IAB node F, of information that associates the setting information obtained by this setting with the handover identification information notified from the IAB donor X. .
  • Identification information is set that identifies the communication path for both the link and the downlink.
  • the IAB donor Z is notified when the MT of the IAB node F is connected to the DU of the IAB node C, when the MT of the IAB node F is connected to the DU of the IAB node D, and when the DU of the IAB node E is connected.
  • similar settings are performed for each of . That is, for example, BAP addresses and IP addresses of IAB nodes FH are set for each connection type, and identification information for communication paths between IAB donor Z and IAB nodes FH are set.
  • Each setting is associated with the handover identification information notified from the IAB donor X according to which one of the IAB nodes C to E the IAB node F is connected to. Then, the IAB donor Z notifies the IAB node corresponding to the connection form of the setting information obtained by the setting for each connection form and the handover identification information corresponding to the connection form.
  • IAB donor Y for example, setting information for IAB node F when IAB node F is connected to IAB node B (communication path identification information, BAP address, and IP address), IAB node G and the combination of the configuration information for the IAB node H and the handover identification information corresponding to the IAB node B are sent to the IAB node B.
  • the IAB donor Z provides information that associates the setting information for each of the IAB nodes F to H when the IAB node F is connected to the IAB node C with the handover identification information corresponding to the IAB node C. to IAB node C.
  • IAB donor Z provides configuration information for each of IAB nodes F to H when IAB node F is connected to IAB node D, and the node next to IAB node C on the communication path (IAB node D ) and the handover identification information corresponding to IAB node D are sent to IAB node C.
  • IAB donor Z provides configuration information for each of IAB nodes FH when IAB node F is connected to IAB node E, and the node next to IAB node C in the communication path (IAB node D) and the handover identification information corresponding to the IAB node E is sent to the IAB node C.
  • the IAB donor Z provides information that associates the setting information for each of the IAB nodes F to H when the IAB node F is connected to the IAB node D with the handover identification information corresponding to the IAB node D. to IAB node D.
  • IAB donor Z provides configuration information for each of IAB nodes F to H when IAB node F is connected to IAB node E, and a node next to IAB node D on the communication path (IAB node E ) and the handover identification information corresponding to the IAB node E is sent to the IAB node D.
  • the IAB donor Z provides information that associates the configuration information for each of the IAB nodes F to H when the IAB node F is connected to the IAB node E with the handover identification information corresponding to the IAB node E. to IAB node E.
  • IAB donor Y and IAB donor Z can use the BAP MAPPING CONFIGURATION message when notifying IAB nodes B to E of configuration information.
  • IAB donor Y and IAB donor Z may use BAP control PDU (Protocol Data Unit) to notify IAB nodes BE of setting information.
  • BAP control PDU Protocol Data Unit
  • a new message different from these may be defined and used to notify this information.
  • each IAB donor/IAB node that is a candidate for the handover destination of the IAB node F when the IAB node F actually executes the handover process, the relay transmission setting is completed when the connection is established. Therefore, these IAB donors/IAB nodes can immediately perform relay communication.
  • IAB donors Y and Z can notify IAB donor X of information that associates the configuration information obtained as described above with handover identification information corresponding to each handover candidate device.
  • the IAB donors Y and Z reject the handover of the IAB node F when, for example, the handover of the IAB node F exceeds the limits of the communication capacity, processing capability, and resources that can be allocated to the IAB. may In this case, for example, a HANDOVER FAILURE message may be sent in response to the HANDOVER REQUEST message.
  • IAB donors Y and Z determine the conditions of radio quality to be achieved at IAB node F in order to accept the communication of IAB nodes F to H, for example, based on the relationship of communication capacity, etc.
  • IAB donor X may notify IAB donor X as a condition for handover of node F.
  • IAB donors Y and Z may notify IAB donor X of information that can specify handover conditions, such as information on available communication capacity. It should be noted that notification of the various types of information described above when the handover is acceptable can be performed, for example, by a HANDOVER REQUEST ACKNOWLEDGE message, which is a response to the HANDOVER REQUEST message.
  • the IAB donor X notifies the IAB node F of the information in which the handover identification information, the physical cell identifier, and the setting information are associated. At this time, the IAB donor X sets conditions for the IAB node F to execute the handover individually for each handover identification information, that is, for each IAB donor or IAB node that is a candidate for the connection destination of the IAB node F. may be notified to. Also, IAB donor X notifies IAB nodes G and H of information in which each handover identification information and configuration information are associated.
  • IAB donor X may provide the handover identification corresponding to IAB Node B, the conditions for handing over to that IAB Node B, the physical cell identifier of IAB Node B, and the IAB Node F's connection to IAB Node B Notifies the IAB node F of the first setting information related to the communication path with relay transmission in the case.
  • the first setting information is, for example, the BAP address or IP address of the IAB node F, the identification information of the communication path formed between the IAB donor Y and the IAB node F, the information of the resource that can be used for the IAB, etc. including.
  • the IAB node F can immediately perform relay transmission when handed over to the IAB node B.
  • the IAB donor X transmits to the IAB nodes F to H the second setting information regarding the communication path involving the relay transmission of the IAB nodes G and H when the IAB node F is connected to the IAB node B.
  • the IAB node F stores the route information of the communication route between the IAB donor Y and the IAB node G, the BAP address and IP address of the IAB node G, and the communication route between the IAB donor Y and the IAB node H. Acquire route information and information indicating the BAP address and IP address of the IAB node H.
  • IAB node F since IAB node F is involved in relay communication between IAB donor Y and IAB node G or H (functions as a relay station included in the communication path), it obtains information about those communication paths in advance. sell. Also, the IAB node G acquires the route information of the communication route between the IAB donor Y and the IAB node G, the physical cell identifier of the IAB node B, and the BAP address and IP address of the IAB node G as the first setting information. , route information of the communication route between the IAB donor Y and the IAB node H and information indicating the BAP address and IP address of the IAB node H can be obtained as the second setting information.
  • the IAB node H stores information indicating the physical cell identifier of the IAB node B, route information of the communication route between the IAB donor Y and the IAB node H, and the BAP address and IP address of the IAB node H as the first setting information. to get as Note that IAB node H is not involved in the communication paths between IAB donor Y and IAB nodes F and G, so it does not acquire information about these communication paths. Note that IAB nodes F through H may also obtain IAB donor Y's IP address and BAP address.
  • the above-mentioned second configuration information is sent to IAB node F via IAB donor X and IAB node A.
  • the configuration information notified to the IAB nodes G and H can be prepared separately from the IAB node F.
  • setting information for the IAB node F itself to operate as a relay device and setting information regarding the setting of the IAB node F when a communication path to the IAB node G or H is formed.
  • Prepared as the first setting information, and separately from that, the setting information for the IAB nodes G and H to operate as relay devices, and the setting information to be transferred to the IAB nodes G and H is the second setting information. can be provided as information.
  • the IAB node F then sends the second configuration information to IAB nodes G and H.
  • the setting information regarding the communication path to the IAB node G or H for the IAB node F and the second setting information transferred to the IAB nodes G and H are both the IAB nodes G and H and the IAB donor Y. Since the setting of the communication path between is common, it contains common information. That is, common information is redundantly notified to the IAB node F.
  • the IAB node F can transfer the second setting information to the IAB node G as it is without analyzing the information.
  • the setting information transferred to the IAB node G includes the setting information of the IAB node G regarding the communication path between the IAB donor Y and the IAB node G, and the communication path between the IAB donor Y and the IAB node H. Contains IAB node G configuration information, if any. Also, the configuration information transferred to the IAB node H includes configuration information of the IAB node H regarding the communication path between the IAB donor Y and the IAB node H. The setting information transferred to the IAB node H is transferred from the IAB node F to the IAB node G, and transferred from the IAB node G to the IAB node H as it is.
  • the IAB nodes G and H receive the setting information transmitted from the IAB donor X as it is, so that the setting can be completed quickly.
  • This setting information may be generated by IAB donor Y, and IAB donor X and IAB node A may transfer the setting information received from IAB donor Y to IAB node F as it is.
  • the setting information regarding the communication route between the IAB donor Y and the IAB nodes G to H is collectively transmitted. may be generated. That is, the IAB node F receives, for example, non-overlapping configuration information instead of receiving redundant configuration information notified to each IAB node as described above. Then, the IAB node F extracts its own setting information from the setting information, executes the setting process, generates information excluding the information on the communication route from the IAB node Y to the IAB node F, and It can be sent to G.
  • the IAB node G When the IAB node G receives this information, it extracts its own setting information and executes setting processing, generates information excluding the information on the communication route from the IAB node Y to the IAB node G, and sends it to the IAB node H. can send.
  • IAB donor Z generates setting information for IAB nodes F to H when IAB node F connects to each of IAB node C, IAB node D, and IAB node E, and IAB nodes C to E to IAB donor X along with the handover identification information associated with each of them. That is, a first combination of handover identification information and configuration information when IAB node F hands over to IAB node C, and a second combination of handover identification information and configuration information when IAB node F hands over to IAB node D. A combination and a third combination of handover identification information and configuration information when IAB node F hands over to IAB node E are sent from IAB donor Z to IAB donor X. These pieces of information are then transmitted from IAB donor X to IAB nodes FH in the form of the first configuration information and the second configuration information described above.
  • notification of information from IAB donor X and IAB node A to IAB nodes FH is performed by a radio resource control (RRC) message (eg, RRCReconfiguration message).
  • RRC radio resource control
  • IAB donors Y and Z configure the configuration information of each of IAB nodes F to H as an RRCReconfiguration message when IAB node F is connected to each of IAB nodes B to E that are candidates for handover destinations.
  • IAB donors Y and Z may then generate a combination of the set of messages and handover identification information (and possibly handover conditions) to send to IAB donor X. For example, IAB donor Y sends handover identification information corresponding to IAB Node B, conditions under which handover to IAB Node B should be performed (e.g.
  • RRCReconfiguration message for IAB node F in that case, IAB node Send the RRCReconfiguration message for G and the RRCReconfiguration message for IAB node H to IAB donor X.
  • IAB donor Z sends the handover identification information corresponding to IAB node C, the conditions under which handover to IAB node C should be performed, the RRCReconfiguration message for IAB node F in that case, the RRCReconfiguration for IAB node G and a RRCReconfiguration message for IAB node H to IAB donor X.
  • each IAB may contain only the identifier for specifying the conditions.
  • IAB donor Z transmits to IAB donor X setting information when IAB node D and IAB node E are handover destinations. IAB donor X, via IAB node A, may forward these information to IAB node F, and IAB node F may forward configuration information for IAB nodes G and H to IAB node G.
  • notification of information to IAB nodes FH may be performed using, for example, the BAP MAPPING CONFIGURATION message defined in the 3GPP standards.
  • information notification to IAB nodes FH may be performed using BAP control PDU (Protocol Data Unit) defined in the 3GPP standard.
  • BAP control PDU Protocol Data Unit
  • a new message different from these may be defined and used to notify this information.
  • notification of information to IAB node F is performed by RRC message, and configuration information is notified to IAB nodes G and H using BAP MAPPING CONFIGURATION message, BAP control PDU, and newly defined message may be performed.
  • the notification may be omitted for those addresses that do not change. According to this, setting for handover can be executed with a relatively small amount of information.
  • the IAB node F executes handover based on the handover conditions set in advance as described above. At this time, the IAB node F performs a random access procedure for handover. In the random access procedure, the IAB node F transmits a random access preamble in the resource for random access preamble transmission corresponding to the handover destination IAB node (IAB donor in some cases). At this time, the IAB node F notifies the handover destination IAB node of the handover identification information using a random access preamble. For example, sequences of usable random access preambles can be classified (defined) in advance for each handover identification information.
  • the IAB node F selects one sequence from among the random access preamble sequences associated with the handover identification information to be notified, and transmits that sequence as the random access preamble.
  • the IAB node F can notify the handover destination IAB node of the handover identification information using the random access preamble.
  • the handover destination IAB node can recognize which UE sent the random access preamble. Therefore, when the handover destination IAB node recognizes that the random access preamble was sent from IAB node F, the handover identification associated with the configuration information for when IAB node F connects to itself is generated. Information can be identified.
  • resources time/frequency resources for transmitting random access preambles may be set for each handover identification information.
  • the IAB node F may send the random access preamble using the resources associated with the handover identification to signal.
  • the handover destination IAB node can specify the handover identification information according to which resource the random access preamble was detected.
  • the IAB node F may notify the handover identification information by, for example, message 3 of the random access procedure or the RRCReconfigurationComplete message transmitted upon completion.
  • the handover destination IAB node does not succeed in the random access procedure and does not receive the RRCReconfigurationComplete message when notified of the handover identification information by the random access preamble, it does not receive the handover identification information. It can be treated as a thing.
  • the IAB node to which IAB node F is handed over validates the setting information associated with the notified handover identification information.
  • the IAB node can then delete configuration information associated with handover identities other than the notified handover identities.
  • the IAB node of the handover destination validates all the preset settings before executing the handover of the IAB node F, and operates to invalidate the setting information other than the setting information corresponding to the notified handover identification information. good too.
  • the handover destination IAB node can notify the handover identification information notified from the IAB node F to the IAB donor to which it is connected. This notification can be done, for example, by means of the UL RRC MESSAGE TRANSFER message defined in the 3GPP standards.
  • the IAB donor validates the configuration information corresponding to the notified handover identification information and invalidates/deletes the configuration information corresponding to the handover identification information different from the notified handover identification information. If another second IAB node is included between the handover destination first IAB node and the IAB donor, the first IAB node also notifies the second IAB node of the handover identification information. , the second IAB node can activate configuration information corresponding to the handover identity and deactivate/delete other configuration information. Note that this notification can be made by BAP control PDU, for example. Also, this notification may be from the IAB donor to the second IAB node instead of from the first IAB node to the second IAB node, for example.
  • the first IAB node notifies the IAB donor via UL RRC MESSAGE TRANSFER, and the IAB donor sends gNB-DU CONFIGURATION UPDATE message, BAP MAPPING CONFIGURATION message, etc. for relay transmission specified in 3GPP standards. message may be used to inform the second IAB node.
  • the IAB donor validates the setting information corresponding to the handover identification information in itself in response to receiving a notification that the setting information corresponding to the handover identification information has been validated from each IAB node under its control. It may be changed to That is, in response to the IAB node F handing over, the configuration information in the IAB donor may not be validated until each IAB node validates the corresponding configuration information.
  • the IAB donor which has the IAB node of the handover destination under its control, enables the relay communication with the IAB nodes FH by validating the setting information, or in parallel with this, to the IAB donor of the handover source. to that IAB node F is connected. Then, the handover source IAB donor can transmit a message requesting invalidation/deletion of the configuration information to the IAB donor that has the IAB node that was the handover destination candidate of the IAB node F under its control. Note that the IAB donor that has the handover destination IAB node under its control may notify the handover source IAB donor of the handover identification information corresponding to the handover destination IAB node.
  • the IAB donor of the handover source has an IAB node corresponding to the handover identification information that the setting information associated with the handover identification information different from the notified handover identification information should be invalidated/deleted. IAB donors may be notified.
  • This setting information invalidation/deletion instruction can be sent by, for example, a HANDOVER CANCEL message defined in the 3GPP standard.
  • the IAB donor receives a request to invalidate/delete the setting information, the IAB donor similarly notifies the IAB node under its control of information instructing invalidation/deletion of the setting information.
  • the IAB node may disable/delete the configuration information upon receiving this notification.
  • this instruction may be individually notified by an RRC message (for example, RRCReconfiguration message) for each IAB node, or sequentially notified to multiple IAB nodes that are connected in series using, for example, BAP control PDU may be
  • RRC message for example, RRCReconfiguration message
  • IAB donor Z sends a BAP control PDU to IAB node C to disable/delete the configuration information corresponding to the specified handover identification information.
  • the IAB node C then transmits a BAP control PDU to the IAB node D to invalidate/delete the setting information corresponding to the designated handover identification information.
  • the IAB node D sends a BAP control PDU to the IAB node E to invalidate/delete the configuration information corresponding to the designated handover identification information.
  • the IAB node F When the IAB node F connects to the handover destination IAB node, it can notify the subordinate IAB nodes G and H to validate the setting information associated with the handover identification information corresponding to the handover. As a result, the IAB node F can instruct the IAB nodes G and H to validate the setting as the relay station and perform control to operate as the relay station. The IAB nodes FH can then invalidate/delete the configuration information associated with the handover identity different from the handover identity.
  • messages such as HANDOVER CANCEL are used to delete unnecessary setting information, but this is not the only option.
  • the configuration information has a preconfigured expiration date, and the configuration information has not been validated after the expiration date, the IAB node The setting information can be discarded.
  • the validity period of the configuration information may be set by the handover source IAB donor, or may be set by the handover destination IAB donor, for example.
  • the expiration date is sent to the handover destination candidate IAB donor (and the handover target IAB node) from the handover target IAB node and its IAB node It is notified together with information indicating the configuration of the communication path formed by other IAB nodes connected downstream, and then the IAB donor who received the notification sets the setting information for each IAB node under , along with its configuration information to each IAB node under it.
  • the expiration date may be indicated by, for example, time information, or may be indicated by a timer value corresponding to the elapsed time from a predetermined timing.
  • the validity period may be set based on, for example, the load state of each IAB donor or each IAB node. In one example, a short expiration period can be set in a high load state, and a long expiration period can be set in a low load state.
  • the valid period may be set long in the high load state and set short in the low load state.
  • the IAB donor cancels the handover, and the IAB donor or IAB node is selected from the candidate for the handover destination. may be removed.
  • the IAB node F handed over to one of the IAB nodes B to E, but the MT of the IAB node F handed over to the DU of the IAB donor Y or Z Similar processing can be performed for cases. That is, the candidates for the handover of the IAB node may be IAB donors as well as IAB nodes. Then, each of the one or more candidate devices is notified of the information of the IAB node to be handed over and the information of other IAB nodes existing downstream of the IAB node, as described above. Configuration information is generated that includes settings related to relay transmission when the IAB node to be handed over is connected to each of the candidate devices.
  • the IAB donor and IAB node comprise a processor 201 , ROM 202 , RAM 203 , storage device 204 and communication circuitry 205 .
  • the processor 201 is a computer including one or more processing circuits such as a general-purpose CPU (Central Processing Unit) and ASIC (Application Specific Integrated Circuit). By reading and executing the program stored in the device, the overall processing of the device and each of the above-described processings are executed.
  • a ROM 202 is a read-only memory that stores information such as programs and various parameters related to processing executed by the apparatus.
  • a RAM 203 is a random access memory that functions as a work space when the processor 201 executes programs and stores temporary information.
  • the storage device 204 is configured by, for example, a detachable external storage device or the like.
  • the communication circuit 205 is configured by, for example, a circuit for 5G wireless communication. Note that although one communication circuit 205 is illustrated in FIG. 2, IAB donors and IAB nodes may have multiple communication circuits, such as wireless communication circuits for 5G and wireline communication circuits for wireline communication. I can. Note that IAB donors and IAB nodes may have separate communication circuitry 205 for each of the multiple available frequency bands, or common communication circuitry 205 for at least some of those frequency bands. You may
  • FIG. 3 is a diagram showing a functional configuration example of IAB donors (for example, IAB donors Y and Z) that are candidate handover destinations of the IAB node to be handed over in this embodiment.
  • the handover destination candidate IAB donor may be an IAB donor having a DU with which the handover target IAB node may be directly wirelessly connected, or another IAB donor with which the IAB node may be wirelessly connected. may be an IAB donor that has an IAB node under its control.
  • the IAB donor as a handover destination candidate has, for example, an information acquisition unit 301, a setting information generation unit 302, an expiration date setting unit 303, a setting information reply unit 304, a setting information notification unit 305, and a handover processing unit 306.
  • FIG. 3 shows only the functions of the handover destination candidate IAB donors that are relevant to the description of this embodiment, and the IAB donors are general IAB donors as CUs and DUs. It has functions of course. Also, the IAB donor may have functions other than the functions shown in FIG. 3 and the general function as an IAB donor. Note that the IAB donor that is a candidate for the handover destination can naturally operate as the IAB donor that is the handover source. Therefore, it can naturally have a processing function which will be described later with reference to FIG. Moreover, the functional blocks in FIG. 3 are shown schematically, and each functional block may be integrated and realized, or may be further subdivided. Each function in FIG.
  • the processor 201 may be realized by, for example, the processor 201 executing a program stored in the ROM 202 or the storage device 204, or for example, a processor existing inside the communication circuit 205 may execute predetermined software. It may be realized by executing It should be noted that although each processing unit can take variations as described above, only some of them will be described here, and exhaustive description will be omitted.
  • the information acquisition unit 301 receives the IAB from the other IAB donor.
  • Get node information The IAB node information includes first information that enables setting for handover of the IAB node that is the target of the handover.
  • the first information that enables setting for handover of the IAB node includes various information that enables setting after handover when a general UE performs CHO, and a general IAB node relaying It contains various information that enables settings for performing relay transmission as a device.
  • the first information includes, but is not limited to, the identification information of the IAB node, the parameters of the communication the IAB node is currently conducting, the BAP address and IP address of the IAB node, and the like.
  • the IAB node information indicates other IAB donors connected to the opposite side of the handover source IAB donor as seen from the IAB node in the communication path before the handover target IAB node executes CHO.
  • Contains the second information is information on the downstream communication path from the IAB donor among the communication paths formed by the IAB donor to be handed over.
  • This second information includes, for example, the identification information of another IAB node connected downstream of the IAB node to be handed over, the BAP address and the IP address, and the connection order of those IAB nodes. It may contain information indicating The information acquisition unit 301 can further acquire handover identification information set for each device to which the IAB node targeted for handover may connect. For example, in FIG. 1, IAB donor Y acquires handover identification information corresponding to IAB node B, in addition to the above-mentioned information such as the IAB node to be handed over.
  • the IAB donor Z provides handover identification information corresponding to the IAB node C, handover identification information corresponding to the IAB node D, and handover identification information corresponding to the IAB node E. Get information. If the handover destination candidate is uniquely determined, it is not necessary to obtain the handover identification information.
  • the setting information generation unit 302 Based on the information acquired by the information acquisition unit 301, the setting information generation unit 302 generates a first communication parameter including post-handover communication parameters of the IAB node to be handed over and settings for performing relay transmission as the IAB node. Generate configuration information for The communication parameters are the same as those reported by the handover destination candidate base station apparatus to the handover source base station apparatus in the conventional handover.
  • Settings for executing relay transmission as an IAB node include, for example, setting values of the BAP address and IP address that the IAB node to be handed over should use after handover, and communication route identification information when the IAB node is added.
  • the setting information generation unit 302 also generates setting information for the IAB nodes involved in the communication path when the IAB node targeted for handover is added among the currently connected IAB nodes. For example, in FIG. 1, if IAB node F is connected to IAB node D, configuration information is also generated for IAB nodes C and D. In this case, for example, as setting information for IAB node C, the identification information of a new communication path in the downlink direction and the transmission destination of the next signal on the communication path corresponding to the identification information is IAB node D; Then, identification information of a new communication path in the uplink direction and information indicating that the next signal transmission destination in the communication path corresponding to the identification information is IAB donor Z are generated.
  • setting information for the IAB node D identification information of a new communication path in the downlink direction and the transmission destination of the next signal in the communication path corresponding to the identification information is the IAB node F, and Identification information of a new communication path in the link direction and information indicating that the next signal transmission destination on the communication path corresponding to the identification information is IAB node C are generated.
  • the setting information generation unit 302 generates second setting information including settings for another IAB node connected downstream of the IAB node to be handed over to perform relay transmission as an IAB node. .
  • the second setting information is, for example, the BAP address or IP address of another IAB node connected downstream of the IAB node to be handed over, and a newly defined communication path including those IAB nodes.
  • the setting information generation unit 302 also generates communication path identification information and the next signal in the communication path for other IAB nodes involved in the newly defined communication path when these other IAB nodes are connected. setting information such as information indicating the combination with the transmission destination of In addition, the setting information generation unit 302, for the IAB node to be handed over and another IAB node connected downstream thereof, if the values of the BAP address and IP address before handover can be diverted, the values are You may make it divert.
  • the setting information generation unit 302 generates each of the above-described setting information for each candidate device to which the handover target IAB node may connect. For example, in FIG. 1, IAB donor Z provides configuration information for handover to IAB node C, handover to IAB node D, and handover to IAB node E. to generate
  • the expiration date setting unit 303 sets the expiration date of the setting information generated by the setting information generation unit 302 .
  • the validity period may be set by receiving a value determined by the handover source IAB donor, or may be determined by the validity period setting section 303 .
  • the expiration date may be specified, for example, by time, or may be specified by a timer that indicates the elapsed time from a predetermined timing (for example, the timing at which the setting information is stored). Note that when a timer is used, a value can be set in consideration of the time lag until the setting information reaches each device. That is, different timer values may be used for different devices.
  • the validity period setting unit 303 may set a different validity period for each device that is a candidate for the handover destination, for example.
  • the setting information replying unit 304 transmits the first setting information generated by the setting information generating unit 302 and Second configuration information (configuration information for the IAB node to be handed over and its downstream IAB node) is transmitted.
  • the setting information replying unit 304 sends the setting information to the handover source IAB donor as a reply (eg, HANDOVER REQUEST ACKNOWLEDGE message) to the message (eg, HANDOVER REQUEST message) received when the information acquisition unit 301 acquires information. to send.
  • the expiration date setting unit 303 determines the expiration date
  • the setting information reply unit 304 sends the information indicating the expiration date in addition to the first setting information and the second setting information to the IAB of the handover source. Send to donor.
  • the setting information returning unit 304 associates the setting information with the handover identification information and transmits the setting information to the IAB donor of the handover source.
  • the handover identification information corresponding to the device is associated with the setting information for each device that is a candidate for the connection destination of the IAB node to be handed over.
  • the setting information notification unit 305 notifies the setting information generated by the setting information generation unit 302 to subordinate IAB nodes.
  • IAB donor Y informs IAB node B of information indicating communication routing when IAB node F is connected to IAB node B.
  • IAB donor Z sends information indicating communication path setup when IAB node F is connected to IAB node C and communication path setup when IAB node F is connected to IAB node D to IAB node C. and information indicating communication path setting when the IAB node F is connected to the IAB node E.
  • IAB donor Z sends information indicating communication path setup when IAB node F is connected to IAB node D and communication path setup when IAB node F is connected to IAB node E to IAB node D. to notify you of the information shown.
  • IAB donor Z notifies IAB node E of information indicating communication path setup when IAB node F is connected to IAB node E.
  • the handover processing unit 306 executes processing for establishing connection of the IAB node when the IAB node targeted for handover executes CHO. Note that the handover processing unit 306 executes a random access procedure with the IAB node targeted for handover in response to detection of the random access preamble by the IAB node under its control. Note that the subordinate IAB node can identify the handover identification information based on the random access preamble and notify the handover identification information to the handover processing unit 306 of the IAB donor. Further, the handover processing unit 306 may specify handover identification information corresponding to the IAB node that has detected the random access preamble based on which IAB node under its control has detected the random access preamble. Further, the handover processing unit 306 may acquire handover identification information from a message (RRCReconfigurationComplete message) transmitted from the IAB node targeted for handover after the completion of the handover procedure.
  • a message RRCReconfigurationComplete message
  • the setting processing unit 307 validates the setting information generated by the setting information generating unit 302 in response to the handover processing unit 306 connecting the IAB node targeted for handover to itself or another IAB node under its control. This makes it possible to perform relay transmission after handover.
  • the setting processing unit 307 validates the setting information of the IAB donor itself, and the subordinate IAB node included in the communication path newly formed by the connection of the IAB node to be handed over (that is, from the IAB donor, Each device that relays communication on the communication path up to the subordinate IAB node connected to the IAB node to be handed over) is instructed to validate the setting information.
  • the setting processing unit 307 can specify, for example, the handover identification information specified by the handover processing unit 306, and perform processing/instruction to validate only the setting information corresponding to the handover identification information. Also, the setting processing unit 307 can process/instruct to invalidate or delete setting information corresponding to handover identification information different from the handover identification information. Also, the setting processing unit 307 invalidates/deletes its own setting information in response to an instruction from the handover source IAB donor, or in response to the expiration date set by the expiration date setting unit 303. and can instruct subordinate IAB nodes to invalidate/delete the setting information as necessary.
  • FIG. 4 is a diagram showing a functional configuration example of a handover source IAB donor (for example, IAB donor X) to which the handover target IAB node is connected in this embodiment.
  • the handover source IAB donor may be an IAB donor having a DU to which the handover target IAB node is directly wirelessly connected, or an IAB donor to which the IAB node is wirelessly connected.
  • IAB donors with The handover source candidate IAB donor has, for example, a CHO determination unit 401 , an information notification unit 402 , a setting information reception unit 403 , a setting information transmission unit 404 , and a setting information deletion instruction unit 405 as its functional configuration example. It should be noted that FIG.
  • FIG. 4 shows only the functions of the handover source IAB donor that are relevant to the description of this embodiment, and the IAB donor functions as a general IAB donor's CU and DU. Naturally have. Also, the IAB donor may have functions other than the functions shown in FIG. 4 and the general function as an IAB donor. Note that the handover source IAB donor can naturally operate as a handover destination candidate IAB donor. Therefore, it can naturally have the processing functions described above with reference to FIG. Moreover, the functional blocks in FIG. 4 are shown schematically, and each functional block may be integrated and realized, or may be further subdivided. Each function in FIG.
  • each processing unit may be implemented by, for example, the processor 201 executing a program stored in the ROM 202 or the storage device 204, or for example, a processor existing inside the communication circuit 205 may execute predetermined software. It may be realized by executing It should be noted that although each processing unit can take variations as described above, only some of them will be described here, and exhaustive description will be omitted.
  • the CHO decision unit 401 decides whether or not to cause the subordinate IAB node (connected in series from the IAB donor itself and controlled to relay communication) to execute CHO.
  • the CHO decision unit 401 decides that the IAB node under its control should make a CHO decision, for example, when the radio quality has deteriorated in an IAB node under its control.
  • the CHO determination unit 401 causes the IAB node to measure the radio quality, and determines that CHO should be executed in response to a predetermined state such as the radio quality falling below a predetermined value.
  • the CHO determination unit 401 determines that the subordinate IAB node is to execute CHO, the CHO determination unit 401 determines a predetermined condition under which the CHO should actually be performed, and, for example, if there are multiple devices that are connection destination candidates First, determine the handover identification information corresponding to each of the plurality of devices.
  • the information notification unit 402 notifies the IAB donor of the handover destination candidate of the information of the IAB node to be handed over and the IAB node connected downstream thereof. Since this information is as described above, the description here is omitted.
  • the information notification unit 402 determines handover identification information for each device that is a connection destination candidate after the handover of the IAB node, and sends it to each IAB donor of the handover destination candidate corresponding to the device under the control of the IAB donor. Notify the handover identification information to be performed.
  • the information notification unit 402 may determine the validity period of the configuration information associated with the CHO and notify each IAB donor as a candidate for the handover destination.
  • the configuration information receiving unit 403 receives configuration information for the handover target IAB node and another IAB node connected downstream from each IAB donor as a handover destination candidate. Since the details of the setting information are as described above, a description thereof will be omitted.
  • the setting information transmitting unit 404 transmits the setting information received by the setting information receiving unit 403 to the IAB node targeted for handover (and further IAB nodes connected downstream thereof).
  • the setting information transmitting unit 404 for example, together with the handover identification information, sets information associated with the handover identification information, expiration date information, and condition information indicating a predetermined condition for determining that the handover is actually executed. , to the IAB node to be handed over (and further IAB nodes connected downstream thereof).
  • the setting information deletion instructing unit 405 instructs, for example, an IAB donor different from the IAB donor to which the handover target IAB node is connected to delete the setting information related to the handover target IAB node.
  • the setting information deletion instruction unit 405 receives, for example, notification of handover identification information corresponding to the connection destination device by handover from the IAB donor to which the IAB node targeted for handover is connected, and the handover identification information different from the handover identification information is received.
  • Each IAB donor may be notified to delete the setting information corresponding to the identification information. In this case, even the IAB donor to which the IAB node is handed over may retain the setting information until the setting information deletion instruction unit 405 instructs deletion.
  • FIG. 5 is a diagram showing a functional configuration example of an IAB node to execute handover in this embodiment.
  • the IAB node to execute handover has, for example, an information receiving unit 501, a setting information transfer unit 502, a handover execution unit 503, a relay setting unit 504, a setting instruction unit 505, and an information deletion processing unit 506, as its functional configuration example.
  • FIG. 5 shows only the part related to the description of this embodiment of the functions of the IAB node to execute handover, and the IAB node is a general IAB node MT and DU naturally has the function of
  • the functional blocks in FIG. 5 are shown schematically, and each functional block may be integrated and realized, or may be further subdivided. Each function in FIG.
  • the processor 201 may be implemented by, for example, the processor 201 executing a program stored in the ROM 202 or the storage device 204, or for example, a processor existing inside the communication circuit 205 may execute predetermined software. It may be realized by executing It should be noted that although each processing unit can take variations as described above, only some of them will be described here, and exhaustive description will be omitted.
  • the information receiving unit 501 receives, for example, predetermined conditions for CHO, handover identification information, communication parameters to be used after handover, and relay operation as an IAB node after handover from the IAB donor currently connected (handover source). and receiving first setting information including settings to perform.
  • the information receiving unit 501 receives second setting information including settings for another IAB node connected downstream to perform a relay operation as an IAB node after the handover is completed from the handover source IAB donor. can be obtained.
  • the setting information transfer unit 502 transfers the received second setting information, for example, together with the corresponding handover identification information, to another IAB node connected downstream.
  • the IAB donor can perform post-handover settings for the IAB node to be handed over, and can also individually perform settings for another IAB node connected downstream of the IAB node.
  • the IAB donor can send RRC messages (eg, RRCReconfiguration messages) to each IAB node to perform individual configuration.
  • RRC messages eg, RRCReconfiguration messages
  • the IAB node does not need to acquire and transfer the information of another IAB node connected downstream. That is, the IAB node only transfers the RRC message as it is, and does not need to acquire the setting information included as its content.
  • Handover executing unit 503 uses a random access procedure with a device associated with the predetermined condition when a predetermined condition for executing handover received by information receiving unit 501 is satisfied, Execute handover processing.
  • the handover executing unit 503 can notify the connected device of the handover identification information corresponding to the device using a random access preamble when executing handover.
  • the handover execution unit 503 may transmit handover identification information corresponding to the device to the connection destination device in a message to be transmitted after completion of the handover. If the handover destination IAB donor or the like can identify the handover identification information by identifying the connection destination device, the handover execution unit 503 does not need to transmit the handover identification information.
  • the relay setting unit 504 validates the above-described first setting information associated with the handover identification information corresponding to the connection destination device, and performs settings for post-handover communication and relay transmission. to run.
  • the setting instruction unit 505 instructs another device connected downstream to validate the second setting information associated with the handover identification information corresponding to the connection destination device when the handover process is successful.
  • the information deletion processing unit 506 invalidates/deletes the first setting information associated with the handover identification information corresponding to the device different from the connection destination device when the handover processing is successful. Further, the information deletion processing unit 506 instructs to invalidate/delete the second setting information associated with the handover identification information corresponding to the device different from the connection destination device.
  • any identification information that can identify setting information to be enabled/disabled/deleted may be used.
  • the IAB node F is connected to the IAB donor X and is communicating by relay transmission (S601).
  • the IAB donor X autonomously performs handover (CHO) when the IAB node F satisfies a predetermined condition, for example, by receiving a radio quality measurement report from the IAB node F. should be executed.
  • the IAB donor X determines that the IAB node F should execute CHO, with the IAB nodes B to E as candidates for connection destination devices (S602).
  • IAB donor X sends to IAB donor Y a HANDOVER REQUEST message containing handover identification information corresponding to IAB node B and IAB nodes F to H, and IAB donor Z to IAB node C.
  • a HANDOVER REQUEST message containing handover identification information corresponding to each of IAB nodes F to E and information of IAB nodes F to H is transmitted (S603).
  • IAB donors Y and Z determine whether or not to accept this HANDOVER REQUEST (S604).
  • the IAB donor Y generates wireless communication parameters for the IAB node F to connect to the IAB node B and setting information for relay transmission.
  • the IAB donor Z generates wireless communication parameters for connecting the IAB node F to each of the IAB nodes C to E and setting information for relay transmission.
  • IAB donors Y and Z further generate setting information for relay transmission with respect to IAB nodes G and H connected downstream of IAB node F.
  • IAB donors Y and Z provide setting information for enabling IAB nodes B to E under their control to communicate on the new communication path for the communication path formed when IAB node F performs handover. Generate.
  • IAB donors Y and Z associate each setting information with the corresponding handover identification information, and notify IAB donor X of the handover source (S605).
  • This notification can be done, for example, by a HADOVER REQUEST ACKNOWLEDGE message.
  • IAB donors Y and Z notify the subordinate IAB nodes B to E of setting information for enabling communication on a newly formed communication path when IAB node F performs handover. (S606). Note that this notification can be made using, for example, a BAP MAPPING CONFIGURATION message, BAP control PDU, or the like.
  • the IAB donor X transmits the handover identification information corresponding to the connection destination device received in S605 and the setting information associated with the handover identification information to the IAB nodes F to H (S607).
  • this configuration information transmission can be performed in a format in which the IAB node F transfers information notified from the IAB node X using a BAP MAPPING CONFIGURATION message or BAP control PDU.
  • the IAB donor X may individually notify each of the IAB nodes F to H of the configuration information using an RRC message.
  • IAB donor X notifies information to IAB node F by an RRC message
  • BAP MAPPING CONFIGURATION message and BAP control PDU are used for information transmission from IAB node F to IAB nodes G and H.
  • the IAB node F satisfies a predetermined condition, such as the radio quality of the radio signal from the IAB node D being better than the radio quality of the radio signal from the IAB node A (S608), the IAB node F satisfies a predetermined condition (S608).
  • Random access processing with D is executed (S609).
  • the IAB node D accepts the handover by this random access process.
  • the IAB node F can notify the corresponding handover identification information to the IAB node D using a random access preamble, an RRC message after random access processing, or the like. If the IAB node D or the IAB donor Z can identify the handover identification information by connecting the IAB node F to the IAB node D, the IAB node F does not have to transmit the handover identification information.
  • the IAB node F instructs the downstream IAB nodes G and H to validate the setting information associated with the handover identification information corresponding to the destination IAB node D (S610).
  • the IAB nodes FH deactivate/delete the configuration information associated with the handover identities corresponding to IAB nodes B, C and E, for example.
  • the IAB nodes G and H may invalidate/delete the configuration information in response to an explicit instruction from the IAB node F, or validate the configuration information corresponding to the IAB node D.
  • Other setting information may be invalidated/deleted in response to receiving an instruction to do so. Note that this notification can be made using a BAP MAPPING CONFIGURATION message or BAP control PDU.
  • the IAB node D notifies IAB donor Z, for example, the handover identification information identified during the random access procedure to IAB donor Z (S611). At this time, the IAB node D may validate configuration information associated with the handover identity and invalidate/delete other configuration information. Also, since the IAB node D notifies the handover identification information via the IAB node C, the IAB node C can validate configuration information corresponding to this handover identification information and invalidate/delete other configuration information. . IAB donor Z then also validates configuration information corresponding to the received handover identification information and invalidates/deletes other configuration information. The IAB donor Z then instructs the IAB node E to delete all of the configuration information it holds (S612).
  • IAB nodes C and D may activate the configuration information after explicit instructions from IAB donor Z. That is, IAB nodes C and D do not validate the configuration information at the time of successful handover, but notify IAB donor Z of the handover identification information, and then receive an instruction from IAB donor Z before configuring. You may make it validate information. Similarly, each IAB node may continue to hold configuration information until a deletion instruction from IAB donor Z is received. On the other hand, if an expiration date is set, the setting information deletion instruction need not be transmitted. Note that even when an expiration date is set, an instruction to delete setting information may be transmitted and received. Transmission and reception of information between the IAB donor and each IAB node can be performed using, for example, BAP MAPPING CONFIGURATION messages and BAP control PDUs.
  • IAB donor Z Upon successful handover, IAB donor Z sends a HADOVER SUCCESS message to IAB donor X, the handover source (S613). IAB donor X can thereby recognize that IAB node F has joined IAB donor Z's control. Then, IAB donor X determines that CHO to IAB node B will not be performed, and transmits a HANDOVER CANCEL message to IAB donor Y, which has IAB node B under its control (S614). The IAB donor Y then instructs the IAB node B to delete the configuration information (S615). Note that if an expiration date is set, the setting information deletion instruction need not be transmitted. Further, even when an expiration date is set, an instruction to delete setting information may be transmitted and received. Transmission and reception of information between the IAB donor and each IAB node can be performed using, for example, BAP MAPPING CONFIGURATION messages and BAP control PDUs.
  • the setting for the relay transmission of the IAB node F is immediately completed, and furthermore, the IAB nodes G and H connected downstream of the IAB node F The setting for the relay transmission of the data is also immediately completed. As a result, it is possible to prevent the communication from being interrupted when the handover is performed.

Landscapes

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

Abstract

L'invention concerne un dispositif de commande qui, lorsqu'un premier trajet de communication est formé par l'établissement de connexions sans fil d'une pluralité de stations de relais à partir d'un autre dispositif de commande : reçoit, en provenance de l'autre dispositif de commande, des premières informations destinées à permettre un transfert intercellulaire faisant passer d'une commande sous l'autre dispositif de commande à une commande sous le dispositif de commande sans transmettre un message à l'autre dispositif de commande en réponse à ce qu'une condition prédéterminée soit satisfaite par un premier dispositif de relais inclus dans la pluralité de stations de relais, et des secondes informations indiquant un second dispositif de relais connecté sur le côté opposé au dispositif de commande dans le premier trajet de communication tel que vu depuis le premier dispositif de relais parmi la pluralité de stations de relais ; génère des informations de configuration servant à former un second trajet de communication par le premier dispositif de relais et à faire fonctionner le second dispositif de relais en tant que stations de relais pour relayer les communications du dispositif de commande si le premier dispositif de relais a été transféré pour être sous la commande du dispositif de commande ; et transmet les informations de configuration à l'autre dispositif de commande.
PCT/JP2022/019319 2021-05-06 2022-04-28 Dispositif de commande pour améliorer le processus de transfert intercellulaire d'une station de relais sans fil, dispositif de relais et procédé de commande WO2022234817A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2021078744A JP2022172681A (ja) 2021-05-06 2021-05-06 無線中継局のハンドオーバ処理を高度化する制御装置、中継装置、及び制御方法
JP2021-078744 2021-05-06

Publications (1)

Publication Number Publication Date
WO2022234817A1 true WO2022234817A1 (fr) 2022-11-10

Family

ID=83932740

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2022/019319 WO2022234817A1 (fr) 2021-05-06 2022-04-28 Dispositif de commande pour améliorer le processus de transfert intercellulaire d'une station de relais sans fil, dispositif de relais et procédé de commande

Country Status (2)

Country Link
JP (1) JP2022172681A (fr)
WO (1) WO2022234817A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020032127A1 (fr) * 2018-08-08 2020-02-13 京セラ株式会社 Dispositif de relais

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020032127A1 (fr) * 2018-08-08 2020-02-13 京セラ株式会社 Dispositif de relais

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
CATT: "Group Handover in Inter IAB donor-CU", 3GPP DRAFT; R3-204733, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. E-meeting; 20200817 - 20200828, 7 August 2020 (2020-08-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051915622 *
KDDI CORPORATION: "Considerations on reducing signal overhead during Inter-donor IAB node migration", 3GPP DRAFT; R3-204660, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. Online; 20200817 - 20200828, 6 August 2020 (2020-08-06), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051911226 *
ZTE, SANECHIPS: "Discussion on supporting R16 CHO and DAPS in IAB", 3GPP DRAFT; R3-206560, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. Online; 20201102 - 20201112, 23 October 2020 (2020-10-23), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051945944 *

Also Published As

Publication number Publication date
JP2022172681A (ja) 2022-11-17

Similar Documents

Publication Publication Date Title
US9883436B2 (en) Method and apparatus for performing mobile handover based on an indication flag
US9961707B2 (en) Terminal multiple connection management method, device and system
US20220182902A1 (en) Communication connection control procedure for supporting and conducting handover
US9521600B2 (en) Handover mechanism in cellular networks
US20160037421A1 (en) Handover of mobility management entity for load balancing
US9775073B2 (en) Gateway configured to provide a handover, converting and routing function
US11452157B2 (en) Communication connection control in a non-homogenous network scenario
KR101411968B1 (ko) 도너／중계 노드 관계의 자가―구성
US10660006B2 (en) Bearer handover control device and control method
US20150312810A1 (en) Radio communication system and communication control method
KR20050053172A (ko) Ｉｐ기반의 무선통신시스템에서의 서로 다른 무선인터페이스를 갖는 기지국간 핸드오프 방법
WO2007125593A1 (fr) Appareil terminal de communication et procédé de transfert
CN105992293B (zh) 一种进行网络间切换的方法和设备
CN116671246A (zh) 管理集成接入和回程移动性
CN111213404A (zh) 承载分离方法，用户装置和基站
US10945183B2 (en) Cell obtaining method, and terminal
WO2022234817A1 (fr) Dispositif de commande pour améliorer le processus de transfert intercellulaire d'une station de relais sans fil, dispositif de relais et procédé de commande
CN114071602A (zh) 一种节点切换配置方法及装置
WO2022234818A1 (fr) Dispositif de relais pour faire progresser un processus de transfert intercellulaire par une station de relais sans fil, procédé de commande et programme
WO2021029291A1 (fr) Dispositif de relais pour transférer un signal avec un trajet désigné, procédé de commande et programme
WO2019146203A1 (fr) Équipement terminal, dispositif de commande, procédé de commande et programme
CN115918245A (zh) 使中继装置的连接目的地变更处理高效化的中继装置、基站装置、控制方法以及程序
CN114071608A (zh) 一种信息传输方法及装置

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22798922

Country of ref document: EP

Kind code of ref document: A1