The present invention relates to a handover technique of a relay apparatus that relays communication between a base station apparatus and a terminal apparatus.
In 3rd Generation Partnership Project (3GPP), a technique for applying, to a backhaul link, a method for a terminal apparatus to access a network, and making the method usable has been considered (see 3GPP, TR38.874, V16.0.0, December, 2018). This technique is called “Integrated Access and Backhaul (IAB)”. A relay apparatus called “IAB node” establishes connection to a 5G base station apparatus (IAB donor) using a wireless link, for example. At this time, the IAB node may be directly connected to the IAB donor by establishing a wireless link, or may be indirectly connection to the IAB donor by establishing a wireless link to another IAB node connected directly or indirectly to the IAB donor. At this time, the IAB node functions as a terminal apparatus connected to the base station apparatus, and thereby establishes wireless connection to the above-mentioned other apparatus (upstream apparatus) on the IAB donor side. In addition, after connection to the IAB donor has been established, the IAB node can establish connection to another IAB node or a terminal apparatus that is to be connected to the IAB donor. In this case, the IAB node operates in a similar manner to the base station apparatus, and establishes wireless connection to a terminal apparatus or another IAB node that operates as a terminal apparatus (downstream apparatus). In this manner, the IAB node has a terminal function (MT, Mobile Termination) and a function (DU, Distributed Unit) for performing an operation similar to that of a base station apparatus, and can relay communication between an upstream apparatus and a downstream apparatus using these functions.
In 3GPP release 17, starting consideration on a topology change technique that is accompanied by a switch of an IAB donor, namely a connection partner of an IAB node has been proposed (3GPP, RP-193251, December, 2019). With this technique, when an IAB node installed in a mobile object such as a train or a bus moves, it is possible to maintain communication of the IAB donor itself and communication of another apparatus connected to the IAB donor.
The present invention provides a technique for streamlining processing that is performed when an IAB node switches a connection destination thereof, namely an IAB donor.
A base station apparatus according to one mode of the present invention includes: one or more processors; and one or more memories that store a computer-readable instruction for causing, when executed by the one or more processors, the base station apparatus to: specify, in a case where a relay apparatus connected to the base station apparatus performs a handover to another base station apparatus, a communication apparatus connected to the base station apparatus via the relay apparatus, and execute processing for performing a handover of the relay apparatus to the other base station apparatus, and, when performing a handover of the relay apparatus to the other base station apparatus, the base station apparatus executes processing for performing a handover of also the specified communication apparatus to the other base station apparatus, and the processing that is executed by the base station apparatus includes transmitting, to the other base station apparatus, a control signal in which control data for a handover of the relay apparatus and control data for the communication apparatus are multiplexed.
A base station apparatus according to another mode of the present invention includes: one or more processors; and one or more memories that store a computer-readable instruction for causing, when executed by the one or more processors, the base station apparatus to: execute, in a case where a relay apparatus connected to another base station apparatus performs a handover to the base station apparatus, handover processing for the relay apparatus, and the processing that is executed by the base station apparatus includes: receiving, from the other base station apparatus, control data for a handover of the relay apparatus and control data for a handover of a communication apparatus connected to the base station apparatus via the relay apparatus, generating a response signal in which response data for the relay apparatus and response data for the communication apparatus are multiplexed, in accordance with receiving the control data for the relay apparatus and the communication apparatus, and transmitting the response signal to the other base station apparatus.
A relay apparatus according to one mode of the present invention includes: one or more processors; and one or more memories that store a computer-readable instruction for causing, when executed by the one or more processors, the relay apparatus to: receive, from a first base station apparatus connected to the relay apparatus, a control message in which first control information for a handover of the relay apparatus and second control information for a communication apparatus connected to the first base station apparatus via the relay apparatus are multiplexed, in a case where a handover is performed from the first base station apparatus to a second base station apparatus, extract the first control information and the second control information by separating the control message, execute a handover to the second base station apparatus based on the first control information, and transmit the second control information to the communication apparatus.
Further features of the present invention will become apparent from the following description of exemplary embodiments with reference to the attached drawings.
The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate embodiments of the invention and, together with the description, serve to explain principles of the invention.
Hereinafter, embodiments will be described in detail with reference to the attached drawings. Note, the following embodiments are not intended to limit the scope of the claimed invention, and limitation is not made to an invention that requires a combination of all features described in the embodiments. Two or more of the multiple features described in the embodiments may be combined as appropriate. Furthermore, the same reference numerals are given to the same or similar configurations, and redundant description thereof is omitted.
The terminal apparatus 121 and the terminal apparatus 122 are connected to the IAB donor 101 via the IAB node 111. Therefore, in accordance with the IAB node 111 performing a handover to the IAB donor 102, the terminal apparatus 121 and the terminal apparatus 122 also require processing for changing a connection destination. At this time, conventionally, for processing for changing a connection destination of each terminal apparatuses, various messages need to be individually transmitted/received for the terminal apparatus. Therefore, particularly, if a large number of terminal apparatuses and other IAB nodes are connected downstream of the IAB node 111, the signaling overhead may increase to too high a degree to ignore.
Therefore, in the present embodiment, when there is a need to change an IAB donor, namely a connection destination of the IAB node 111, the IAB donor 101 that is a handover source multiplexes control data for performing a handover of the IAB node 111 and control data for a handover of the terminal apparatuses and other IAB nodes connected downstream of the IAB node 111, to generate a control signal for a handover, and transmits the control signal to the IAB donor 102 that is a handover destination. That is to say, when following a conventional procedure, the IAB donor 101 separately generates and transmits a control signal for a handover of the IAB node 111 and control signals for a handover of the terminal apparatuses and other IAB nodes connected downstream of the IAB node 111 and, on the other hand, in the present embodiment, one control signal in which these control signals are multiplexed is generated and transmitted. Note that, control data for a handover may include identification information (ID) and the name of each of the terminal apparatuses (the IAB node 111, the terminal apparatus 121, and the terminal apparatus 122), and information regarding a connection parameter that has been used by the terminal apparatus. In addition, a configuration may be adopted in which, for example, if there are a large number of IAB nodes and terminal apparatuses that are to perform a handover, the IAB donor 101 multiplexes control data for a predetermined number of IAB nodes and terminal apparatuses to generate one control signal, and generates another control signal for control data for the rest of the IAB nodes and terminal apparatuses. Note that this control signal may correspond to a HANDOVER REQUEST message that is transmitted from a base station apparatus that is a handover source to a base station apparatus that is a handover destination, in a conventional method. Note that, having transmitted this control signal, the IAB donor 101 may erase information regarding the IAB node 111, and the terminal apparatuses and other IAB nodes connected downstream of the IAB node 111.
Note that the above-mentioned identification information (ID) can be a ReestabUE-Identity derived (calculated, for example) from Cell Radio Network Temporary Identifier (C-RNTI), or C-RNTI and physical cell ID (physCellId), which is an identifier that is allocated to each of the terminal apparatuses and IAB nodes by the base station apparatus. In addition, if a communication apparatus connected downstream of the IAB node 111 is an IAB node, Global NG-RAN Node ID or IP address allocated to the IAB node (as a 5G wireless access network node) may be used as identification information (ID).
On receiving a control signal in which control data for a handover of IAB nodes and terminal apparatuses is multiplexed, the IAB donor 102 that is a handover destination transmits a response signal to the control signal in which data is multiplexed, to the IAB donor 101. Note that, in this response signal, response data for the IAB node 111 and response data for the terminal apparatuses and other IAB nodes connected downstream of the IAB node 111 may be multiplexed. The response data here may include, for the IAB nodes and terminal apparatuses, information regarding connection parameters that are to be used after a handover and that are determined, for example, based on connection parameters that have been used. Note that this response signal may correspond to a Handover Request Acknowledge message that is transmitted from a base station apparatus that is a handover destination to a base station apparatus that is a handover source in a conventional method.
Note that the IAB donor 102 may multiplex response data on the condition that control data for the IAB node 111 and control data for the terminal apparatuses and other IAB nodes connected downstream of the IAB node 111 are multiplexed to the control signal received from the IAB donor 101, for example. In addition, a configuration may also be adopted in which the IAB donors 101 and 102 exchange information regarding the capability thereof in advance, and if the partner apparatus of each of the IAB donors 101 and 102 supports processing that is performed on multiplexed control data for a handover and multiplexed response data, the IAB donor transmits a control signal or response signal in which data is multiplexed, to the partner apparatus.
On receiving a response signal in which response data is multiplexed, the IAB donor 101 transmits, to the IAB node 111, a control message in which control information for a handover for the IAB node 111 and control information for a handover for the terminal apparatuses and other IAB nodes connected downstream of the IAB node 111 are multiplexed. At this time, when receiving a response signal in which response data is multiplexed, the IAB donor 101 may transmit information for each of the terminal apparatuses as is to the IAB node 111, or may decode each pieces of the information once and then reconfigure the information so as to generate a control message. In addition, when receiving a response signal in which response data is multiplexed, the IAB donor 101 may separate the response data so as to individually prepare control information for a handover for the IAB node 111 and control information for a handover for the terminal apparatuses and other IAB nodes connected downstream of the IAB node 111, and transmit the control information to the IAB node 111. That is to say, control information for a handover of apparatuses may be separated by the IAB node 111, or may be separated by the IAB donor 101. Note that, here, the control information for a handover corresponds to a conventional RRC Reconfiguration message, for example. Here, the control information for the IAB node 111 may include information indicating that processing (for example, random access processing) for establishing synchronization with the connection destination to which a switch is to be made (IAB donor B) is necessary. On the other hand, there is no change in the partner apparatus (for example, the IAB node 111, for the terminal apparatus 121 and the terminal apparatus 122) to which the terminal apparatuses and other IAB nodes connected downstream of the IAB node 111 are directly connected, and thus control information for these apparatuses may include information indicating that synchronization establishment processing is not necessary. Note that a configuration may be adopted in which control information includes predetermined information only when synchronization establishment processing is necessary, and the predetermined information not being included implicitly indicates that synchronization establishment processing is not necessary. On the contrary, a configuration may also be adopted in which control information includes predetermined information only when synchronization establishment processing is not necessary, and the predetermined information not being included implicitly indicates that synchronization establishment processing is necessary. Note that, if the IAB node 111 supports processing that is performed on multiplexed control messages, the IAB donor 101 may transmit multiplexed control messages to the IAB node 111. In addition, the IAB donor 101 may multiplex control information for the terminal apparatus 121 and control information for the terminal apparatus 122 within one FIAP message that is to be transmitted from the IAB donor 101 to the IAB node 111. In this case, the control information for the IAB node 111 is transmitted by using an RRC Reconfiguration message, and the control information for the terminal apparatus 121 and the terminal apparatus 122 may be transmitted using RRC Reconfiguration messages of the terminal apparatus 121 and the terminal apparatus 122 that are multiplexed in the FlAP message.
Upon receiving this control message, the IAB node 111 extracts control information for the IAB node itself from the control message, and executes necessary processing such as synchronization establishment processing. In addition, the IAB node 111 individually transmits control messages (for example, the RRC Reconfiguration messages) included in the received control message, to the terminal apparatuses and other IAB nodes connected downstream of the IAB node 111. Note that, when transmitting a control message to another IAB node, the IAB node 111 may transmit a control message in which control information for terminal apparatuses and yet other IAB nodes connected downstream of the other IAB node is multiplexed. In this case, if the other IAB node supports processing that is performed on multiplexed control messages, the IAB node 111 may transmit multiplexed control messages.
The IAB node 111 then receives a response message (RRC Reconfiguration Complete message) to the control message, from the terminal apparatuses and other IAB nodes connected downstream of the IAB node 111. Note that a response message in which response messages from terminal apparatuses and yet other IAB nodes connected downstream of another IAB node are multiplexed may be received from the other IAB node. The IAB node 111 may then multiplex the response messages received from the terminal apparatuses and other IAB nodes connected downstream of the IAB node 111, and transmit the multiplexed response messages to the IAB donor 102 that is a handover destination.
Note that, when various signals (messages) are multiplexed and transmitted, information for only one signal out of information common to a plurality of signals to be multiplexed may be transmitted. If, for example, connection parameter common to a plurality of IAB nodes and terminal apparatuses is transmitted using a HANDOVER REQUEST message or a Handover Request Acknowledge message, a signal for one of the apparatuses that correspond to the common connection parameter may include a value indicating the connection parameter, and signals for the other apparatuses may include a value (for example, one-bit value) indicating that the connection parameter for the one apparatus is to be used. Accordingly, it is possible to prevent an increase in the information amount resulting from the same information being repeatedly transmitted. Note that, for example, regarding information indicating reference values for connection parameters and connection parameters for the IAB nodes and terminal apparatuses, information indicating the difference between a connection parameter and a reference value may be transmitted/received. The IAB node 111 and the terminal apparatuses and other IAB nodes connected downstream of the IAB node 111 may be configured to use CellGroupConfig as a common parameter, for example. In this case, only one value indicating CellGroupConfig is included in a signal, and information regarding parameters for a plurality of apparatuses does not need to include information regarding this value. Note that a signal may have any format as long as necessary information is transmitted/received.
Note that there is a need to perform setting of a relay path between the IAB donor 102 and the IAB node 111 (and other IAB nodes), using IAB. Also in a message that is used in this case, multiplexing may be used. A configuration may also be adopted in which, for example, when information regarding the IAB donor 102 (for example, information regarding the Central Unit) is notified to the IAB node 111 and the other IAB nodes connected downstream of the IAB node 111, one Fl message in which information is multiplexed is transmitted to the IAB node 111 and the other IAB nodes.
In this manner, when an IAB node performs a handover, a signal for the IAB node and signals for apparatuses (terminal apparatuses and IAB nodes) connected downstream of the IAB node are multiplexed and transmitted, and thereby the signaling amount can be reduced. In addition, as a result, for example, it is possible to prevent a time for transmitting/receiving a signal from being extended, and to shorten a period during which a communication service that is being provided to a terminal apparatus is disconnected.
Note that
Apparatus Configuration
Next, the configuration of an IAB donor and an IAB node that execute processing such as that described above will be described.
The processor 201 of the IAB donor or the IAB node controls the communication circuit 205 so as to perform communication with a partner apparatus (an IAB donor, an IAB node, a terminal apparatus, or the like), for example. Note that
First, a case will be described in which the IAB donor is a handover source. The handover target specifying unit 301 determines whether or not to perform a handover of a terminal apparatus or an IAB node connected to the IAB donor based on a measurement result of wireless quality and the like of the terminal apparatus or the IAB node, for example. If it is determined that, for the handover, the IAB node is to perform a handover to another IAB donor, the handover target specifying unit 301 specifies the terminal apparatuses and other IAB nodes connected downstream of the IAB node as handover targets. The control data generation unit 302 generates handover request data for each of the apparatuses specified by the handover target specifying unit 301. This data may include information such as identification information (ID) and the name of each of the apparatuses, and a connection parameter that is currently used by the apparatus. The control data multiplexing unit 303 multiplexes the generated data, and the signal transmitting/receiving unit 305 transmits the multiplexed data (control signal) to the other IAB donor that is a handover destination.
Moreover, the signal transmitting/receiving unit 305 receives a response signal in response to the transmitted control signal, from the other IAB donor that is a handover destination. At this time, if, in the received response signal, for example, response data for the IAB node that is a handover target and response data for the terminal apparatuses and other IAB nodes connected downstream of the IAB node are multiplexed, the control data separating unit 304 separates the response data. That is to say, the control data separating unit 304 separates and extracts the response data for each of the apparatuses that are handover targets, in the received response signal. This response data may include identification information and the name of the apparatus, a connection parameter to be used between the apparatus and the IAB donor that is a handover destination, for example. At this time, the control data separating unit 304 may refer to response data for a second apparatus in which connection parameters are written, and obtain a connection parameter for response data for a first apparatus in which at least some of the common connection parameters are omitted during multiplexing. The control data generation unit 302 then generates control messages (for example, RRC Reconfiguration messages) to be transmitted to the apparatuses that are handover targets, based on the obtained data. The control data multiplexing unit 303 multiplexes the control messages, and the signal transmitting/receiving unit 305 transmits the multiplexed control messages to the IAB node that is to execute a handover. Note that the signal transmitting/receiving unit 305 may transmit information such as a connection parameter included in a response signal received from other IAB donor that is a handover destination, to the IAB node that transparently executes a handover. In this case, the IAB donor that is a handover source does not need to generate control data for the apparatuses again.
Next, a case will be described in which the IAB donor is a handover destination. The signal transmitting/receiving unit 305 receives, from another IAB donor that is a handover source, a control signal in which handover requests for respective apparatuses that are handover targets are multiplexed, as described above. The control data separating unit 304 then separates the multiplexed handover requests, and obtains the handover requests for the respective apparatuses. The control data separating unit 304 may refer to a handover request for a second apparatus in which connection parameters are written, and obtain a connection parameter for a handover request for a first apparatus in which at least some of common connection parameters are omitted during multiplexing, for example. In addition, for example, when a connection parameter of each apparatus is represented as a reference value of a connection parameter and a difference value for the apparatus during multiplexing, the control data separating unit 304 may specify a connection parameter based on the reference value and the difference value. The control data generation unit 302 then determines, based on the obtained data, a connection parameter to be used by each apparatus after a handover, and generates response data that includes the connection parameter in response to the handover request. The control data multiplexing unit 303 multiplexes the response data for the apparatuses, and generates a response signal, and the signal transmitting/receiving unit 305 transmits the response signal to the IAB donor that is a handover source.
Note that the signal transmitting/receiving unit 305 establishes connection to an IAB node based on random access processing executed for a handover by the IAB node. Thereafter, the signal transmitting/receiving unit 305 may receive, from the IAB node, a control message in which an RRC Reconfiguration Complete message of the IAB node and RRC Reconfiguration Complete messages of terminal apparatuses and other IAB nodes connected downstream of the IAB are multiplexed. The control data separating unit 304 then separates messages for the respective apparatuses from the received control message, and obtains the messages. Note that the IAB donor transmits/receives messages to/from the IAB node using an Fl interface in order to set a relay path after a handover, for example, but may be configured to multiplex signals and separate multiplexed signals at this time.
Next, an exemplary functional configuration of the IAB node will be described with reference to
When, for example, a control signal in which an RRC Reconfiguration message for the IAB node and RRC Reconfiguration messages for the terminal apparatuses and other IAB nodes connected downstream of the IAB nodes are multiplexed is received from the IAB donor that is a handover source via the signal transmitting/receiving unit 404, the control data separating unit 401 separates and extracts the messages. The signal transmitting/receiving unit 404 then transmits the separated messages to the terminal apparatuses and other IAB nodes connected downstream of the IAB node. The handover processing unit 403 executes processing such as random access processing in accordance with the RRC Reconfiguration message for the IAB node, in order to establish connection to the IAB donor that is a handover destination. Meanwhile, the signal transmitting/receiving unit 404 receives the RRC Reconfiguration Complete messages from the terminal apparatuses and other IAB nodes connected downstream of the IAB node, for example. The control data multiplexing unit 402 then multiplexes the received messages, and transmits the multiplexed messages, to the IAB donor to which connection has been established by the handover processing unit 403, via the signal transmitting/receiving unit 404.
Next, an example of flow of processing that is executed by the wireless communication system will be described with reference to
In this processing, first, the IAB donor 101 connected to the IAB node 111 determines that a handover of the IAB node 111 is to be performed, in accordance with deterioration in first wireless quality of a signal received by the IAB node 111 from the IAB donor 101, second wireless quality of a signal received by the IAB node 111 from the IAB donor 102 exceeding the first wireless quality by more than a predetermined level, or the like. The IAB donor 101 then specifies the terminal apparatuses and other IAB nodes connected downstream of the IAB node 111, and generates Handover Request messages for the apparatuses, and a Handover Request message for the IAB node 111. The IAB donor 101 then multiplexes the Handover Request messages, and transmits the multiplexed messages to the IAB donor 102 that is a handover destination (step S501). The IAB donor 102 separates the multiplexed Handover Request messages for the respective apparatuses, and obtains information such as connection parameters that are being used by the apparatuses. The IAB donor 102 then determines connection parameters to be used by the apparatuses after a handover, and the like, and generates Handover Request Acknowledge messages for the respective apparatuses, the messages including the information. The IAB donor 102 then multiplexes the messages, and transmits the multiplexed messages to the IAB donor 101 that is a handover source (step S502).
Upon receiving the multiplexed Handover Request Acknowledge messages, the IAB donor 101 generates RRC Reconfiguration messages for the IAB node 111 and the terminal apparatuses and other IAB nodes connected downstream of the IAB node 111, based on the received messages. The IAB donor 101 then multiplexes the generated messages, and transmits the multiplexed messages to the IAB node 111 (step S503). At this time, the RRC Reconfiguration message for the IAB node 111 may indicate that synchronization establishment processing such as random access processing is to be executed. On the other hand, the RRC Reconfiguration messages for the terminal apparatuses and other IAB nodes connected downstream of the IAB node 111 may indicate that synchronization establishment processing such as random access processing is not to be executed. Note that, in
Upon receiving the multiplexed RRC Reconfiguration messages, the IAB node 111 separates, extracts, and obtains the messages for the respective apparatuses, and transmits the obtained messages to the terminal apparatuses and other IAB nodes connected downstream of the IAB node 111 (step S504). In addition, the IAB node 111 executes random access processing and establishes synchronization with the IAB donor 102, based on the RRC Reconfiguration message for the IAB node 111 (steps 5505 and S506). Upon receiving the RRC Reconfiguration Complete messages from the terminal apparatuses and other IAB nodes connected downstream of the IAB node 111 (step S507), the IAB node 111 multiplexes the messages and an RRC Reconfiguration Complete message that the IAB node 111 is to transmit, and transmits the multiplexed messages to the IAB donor 102 (step S508).
A handover is performed successfully by performing this series of processing. The IAB node 111 and the other IAB nodes connected downstream of the IAB node 111 then set a relay path to the IAB donor 102, by transmitting/receiving messages via the F1 interface. Accordingly, the terminal apparatuses and other IAB nodes connected downstream of the IAB node 111 can communicate with the IAB donor 102.
With the technique according to the present embodiment, it is possible to reduce the amount of signaling messages when an IAB node performs a handover between IAB donors as described above, which makes it possible to prevent a time for transmitting/receiving signals from being extended, for example, and to shorten a period during which a communication service provided to a terminal apparatus is disconnected.
While the present invention has been described with reference to exemplary embodiments, it is to be understood that the invention is not limited to the disclosed exemplary embodiments. The scope of the following claims is to be accorded the broadest interpretation so as to encompass all such modifications and equivalent structures and functions.
Number | Date | Country | Kind |
---|---|---|---|
2020-110807 | Jun 2020 | JP | national |
This application is a continuation of International Patent Application No. PCT/JP2021/024129 filed on Jun. 25, 2021, which claims priority to and the benefit of Japanese Patent Application No. 2020-110807 filed Jun. 26, 2020, the entire disclosures of which are incorporated herein by reference.
Number | Date | Country | |
---|---|---|---|
Parent | PCT/JP2021/024129 | Jun 2021 | US |
Child | 18080318 | US |