Base station device, communication device, control method, and program

The implementation of a mechanism to limit multi-hop configurations in IAB networks by rejecting connection requests from mobile IAB nodes addresses the challenge of maintaining communication services during node movement, ensuring stable network connectivity and reducing maintenance complexities.

WO2024232236A1PCT designated stage expired Publication Date: 2024-11-14CANON KK
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
PCT/JP2024/015511
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-10
Filing Date
2024-04-19
Publication Date
2024-11-14

AI Technical Summary

Technical Problem

Current IAB network specifications do not adequately address the challenge of maintaining communication services when mobile IAB nodes move, leading to difficulties in maintaining network connectivity and complexity in multi-hop configurations.

Method used

A mechanism is implemented in base station devices to limit multi-hop configurations by rejecting connection requests from mobile IAB nodes, using identification indicators in RRCSetupRequest and RRCSetupComplete messages to determine and manage connections, ensuring only single-hop configurations with mobile IAB nodes are allowed.

Benefits of technology

This approach reduces network maintenance complexities and ensures stable communication services by restricting multi-hop configurations, preventing disruptions when mobile IAB nodes move, and maintaining network stability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2024015511_14112024_PF_FP_ABST
    Figure JP2024015511_14112024_PF_FP_ABST
Patent Text Reader

Abstract

Disclosed is a base station device related to the provision of a communication service, characterized by including: an acquiring means for acquiring a connection request from an external device to one Integrated Access and Backhaul (IAB) node; and a processing means for performing processing to reject the connection request at least if the one IAB node is a mobile IAB node and the external device is another IAB node.
Need to check novelty before this filing date? Find Prior Art

Description

Base station device, communication device, control method, and program

[0001] The present disclosure relates to a base station device, a communication device, a control method, and a program.

[0002] In the 3rd Generation Partnership Project (3GPP) (registered trademark), standardization of IAB (Integrated Access and Backhaul) is underway as a communication technology for backhaul.

[0003] The IAB technology is a technology that uses millimeter-wave wireless communication such as the 28 GHz band used for access communication between a base station and user equipment (UE) as backhaul communication (Patent Document 1).

[0004] In a backhaul communication network using IAB technology (hereinafter referred to as an IAB network), a relay device called an IAB node relays (base station relays) communications from an IAB donor, which corresponds to a conventional base station, to the destination UE. The IAB node has the same functionality as a base station, accepting connections from UEs.

[0005] In its next release, 3GPP Release-18, it plans to develop specifications for Mobile IAB, which will enable Vehicle-Mounted Relay, in response to demand for improved 5G cellular coverage and connectivity. Vehicle-Mounted Relay is a technology in which an IAB node mounted on a vehicle relays signals from a base station.

[0006] In the discussions on the formulation of this specification, it is considered that requirements unique to mobility scenarios in which IAB nodes and UEs move relative to each other will arise, which cannot be met by conventional specifications.

[0007] Special Publication No. 2019-534625

[0008] For example, if a mobile IAB node allows a multi-hop configuration, an IAB node may be connected to the mobile IAB node in a state where an IAB network including the mobile IAB node is formed. In this state, if the upper-level mobile IAB node moves along with the vehicle, it may become difficult to maintain the IAB network. As a result, it may become impossible to continue communication services for the subordinate IAB node and UE. Furthermore, depending on the configuration of the IAB network, there may be other cases where it is undesirable to connect an IAB node to the subordinate. In this regard, the current standard does not propose a mechanism for restricting a multi-hop configuration in an IAB network environment that may include a mobile IAB.

[0009] The present invention has been made in consideration of at least one of the above-mentioned problems, and an object of one aspect of the present invention is to provide a mechanism for restricting a multi-hop configuration in an IAB network environment that may include a mobile IAB.

[0010] A base station device according to one aspect of the present invention is a base station device related to the provision of a communication service, characterized by comprising: an acquisition means for acquiring a connection request from an external device to one IAB (Integrated Access and Backhaul) node; and a processing means for performing processing to reject the connection request at least when the one IAB node is a mobile IAB node and the external device is another IAB node.

[0011] According to one aspect of the present invention, it is possible to provide a mechanism for restricting multi-hop configurations in an IAB network environment that may include mobile IABs.

[0012] 1A is a diagram showing an example of a mobile communication system in this embodiment. FIG. 1B is an explanatory diagram showing another situation in the mobile communication system of FIG. 1A. FIG. 1C is a hardware functional block diagram of a mobile IAB node in this embodiment. FIG. 1D is a software functional block diagram of a mobile IAB node in this embodiment. FIG. 1E is a software functional block diagram of an IAB donor in this embodiment. FIG. 1F is a connection control processing sequence diagram of a mobile IAB node and an IAB node in embodiment 1. FIG. 1G is a processing flow of an IAB donor in response to a connection request from an external device in embodiment 1. FIG. 1H is a connection control processing sequence diagram of a mobile IAB node and an IAB node in embodiment 2. FIG. 1H is a processing flow of an IAB donor in response to a connection request from an external device in embodiment 2. FIG. 1I is a connection control processing flow of a mobile IAB node and an IAB node in embodiment 3. FIG. 1I is a processing flow of an IAB donor in response to a connection request from an external device in embodiment 3.

[0013] Each embodiment will be described in detail below with reference to the accompanying drawings.

[0014] First Embodiment FIG. 1A is a diagram showing an example of a mobile communication system according to this embodiment.

[0015] In the example shown in FIG. 1A, in a network providing public network communication services to cell coverages 101 and 102, there are IAB donors 103 and 104 that provide connectivity to a CN 100.

[0016] Within cell coverage 101, IAB nodes 105-107 and a mobile IAB node 108 are wirelessly connected to an IAB donor 103 to form an IAB network. In Figure 1A, CN stands for Core Network, and is responsible for various processes such as authentication of terminals UEs 109-114.

[0017] IAB donor 103 controls IAB nodes 105 to 107 and mobile IAB node 108 in an integrated manner, forming cell coverage 101. IAB donor 104 similarly forms cell coverage 102.

[0018] In the IAB network, communication packets conforming to the BAP data PDU format (hereinafter referred to as BAP data packets) are used. PDU is an abbreviation for Protocol Data Unit.

[0019] For example, an IP packet destined for UE 109 from CN 100 is encapsulated into a BAP data packet at IAB donor 103 and forwarded to IAB node 105. The forwarded BAP data packet is then converted back into an IP packet at IAB node 105 and delivered to destination UE 109.

[0020] Similarly, an IP packet from UE 109 is also encapsulated into a BAP data packet at IAB node 105. Then, it is converted back into an IP packet at IAB donor 103 and transferred to CN 100. Note that IP is an abbreviation for Internet Protocol.

[0021] IAB nodes 105 to 107 are fixed communication nodes and are connected to the IAB donor 103 .

[0022] The mobile IAB node 108 is also connected to the IAB donor 103. In this case, the IAB donor 103, the IAB nodes 105 to 107, and the mobile IAB node 108 form an IAB network.

[0023] The mobile IAB node 108 may be a communication node installed on a moving object such as a train, bus, or taxi. Note that the term "moving object" is not limited to an object that moves on the road, but also includes an air vehicle. When the mobile IAB node 108 moves beyond cell coverage 101 to cell coverage 102, it changes its connection to be under the control of the IAB donor 104. The transition between base stations is performed via the CN 100.

[0024] UEs 109-112 are connected to IAB nodes 105 and 107. UEs 113-114 are connected to mobile IAB node 108. A moving object equipped with mobile IAB node 108 may move (travel) within cell coverage 101 and cell coverage 102 according to a planned route.

[0025] FIG. 2 is a hardware functional block diagram of the mobile IAB node 108 in this embodiment.

[0026] The mobile IAB node 108 includes a control unit 201 , a storage unit 202 , a wireless communication unit 203 , and an antenna control unit 204 .

[0027] The control unit 201 is configured with one or more processors such as a CPU or an MPU, and controls the entire communication device by executing a control program read into the RAM, which is the storage unit 202. Note that each process performed by the control unit 201, which will be described in the flowcharts below, can also be realized using a hardware circuit such as an ASIC or an FPGA. Note that ASIC is an abbreviation for Application Specific Integrated Circuit. FPGA is an abbreviation for Field Programmable Gate Array. Also, the processes described in the flowcharts below can be realized by cooperation between a hardware circuit and a processor such as a CPU or an MPU.

[0028] The storage unit 202 stores information used for control by the control unit 201 and information related to communication. For example, the storage unit 202 stores a control program executed by the control unit 201, information about the UE to be connected, connection strength with the IAB donor 103, and various other information.

[0029] The storage unit 202 may include a main storage unit and an auxiliary storage unit. The main storage unit may be, for example, a read-only memory (ROM) or a random access memory (RAM). The main storage unit may store or temporarily store programs and data such as an operating system (OS), which is basic software executed by the control unit 201, and application software. The auxiliary storage unit may be, for example, a hard disk drive (HDD) or a solid state drive (SSD), and may store data related to application software. For example, a control program stored in a non-volatile storage area is expanded into random access memory (RAM) and executed by a processor constituting the control unit 201. In this way, the control unit 201 and the storage unit 202 may function as a so-called computer.

[0030] The storage unit 202 may include a recording medium that stores a predetermined program. The program stored in this recording medium may be installed via a drive device or the like, and the installed predetermined program may be executable by the control unit 201. Various types of recording media can be used as the recording medium. For example, the recording medium may be a recording medium that records information optically, electrically, or magnetically, such as a CD (Compact Disc)-ROM, a flexible disk, or a magneto-optical disk. The recording medium may also be a semiconductor memory that records information electrically, such as a ROM or a flash memory. Note that the recording medium does not include a carrier wave.

[0031] The wireless communication unit 203 performs cellular network communication such as LTE and 5G that conform to the 3GPP standard.

[0032] The antenna control unit 204 controls the antenna used for wireless communication performed by the wireless communication unit 203 .

[0033] Although the hardware description here assumes the mobile IAB node 108, the IAB nodes 105 to 107 are also assumed to have a similar configuration. The IAB donors 103 and 104 are also assumed to have a similar configuration.

[0034] FIG. 3A is a software functional block diagram of the mobile IAB node 108 in this embodiment.

[0035] The software function block 301 is stored in the storage unit 202 and executed by the control unit 201. The software function block 301 includes a signal transmitting unit 302, a signal receiving unit 303, a data storage unit 304, a connection control unit 305, and a signal generating unit 308.

[0036] The signal transmitting unit 302 and the signal receiving unit 303 control the wireless communication unit 203 via the control unit 201, and perform cellular network communication such as LTE and 5G that conforms to the 3GPP standard between the IAB donor 103 and the UEs 113 to 114.

[0037] The data storage unit 304 controls and manages the storage unit 202, and stores and holds the software itself, connection information with the IAB donors 103 and 104, and information about the UEs 113 to 114. Information between IAB nodes can be collected by broadcast signals and communication packets accompanying various BAP control PDUs (hereinafter referred to as BAP control packets).

[0038] The connection control unit 305 controls the antenna control unit 204 via the control unit 201 during wireless communication.

[0039] The signal generating unit 308 manages and issues various signals generated by the connection control unit 305 .

[0040] Although the hardware description here assumes the mobile IAB node 108, the IAB nodes 105 to 107 are also assumed to have the same configuration.

[0041] 3B is a software functional block diagram of the IAB donor 103 in this embodiment. In the following description, the term "corresponding IAB network" refers to the IAB network formed by the IAB donor 103.

[0042] The software function block 401 is stored in the storage unit 202 and executed by the control unit 201. The software function block 401 includes a signal transmission unit 402, a signal reception unit 403, a data storage unit 404, a connection control unit 405, and a network configuration information management unit 406.

[0043] The signal transmitting unit 402 and the signal receiving unit 403 control the wireless communication unit 203 via the control unit 201. The signal transmitting unit 402 and the signal receiving unit 403 perform a process of transmitting signals and messages generated by the connection control unit 405, and a process of receiving messages from subordinate UEs.

[0044] The data storage unit 404 controls and manages the storage unit 202, and stores the software itself, connection information with the IAB nodes 105 to 108, information on the UEs 113 to 114, etc. Various types of information can be collected by broadcast signals, RRC messages, BAP data packets, etc. RRC stands for Radio Resource Control, and BAP stands for Backhaul Adaptation Protocol.

[0045] The connection control unit 405 controls the antenna control unit 204 via the control unit 201 during wireless communication. The connection control unit 405 controls connections in the corresponding IAB network based on information managed by the network configuration information management unit 406. Specifically, the connection control unit 405 controls connections between the IAB nodes 105-107, the mobile IAB node 108, and the UEs 113-114 in the corresponding IAB network based on the configuration information of the IAB network, etc.

[0046] The network configuration information management unit 406 manages the configuration information of the corresponding IAB network. The network configuration information management unit 406 may also manage type information of the UE, IAB node, and mobile IAB node making the connection request as part of the configuration information of the IAB network.

[0047] FIG. 4 is a sequence diagram of connection control processing between the IAB node 105 and the mobile IAB node 108 in the first embodiment.

[0048] In this embodiment, it is assumed that an IAB node 105 issues a connection change request to a mobile IAB node 108 that has moved closer. This section describes a process in which an IAB donor 103 grasps the identification information of an IAB node 105 that is attempting to issue a connection request to a mobile IAB node 108 and controls the connection.

[0049] In S400, the IAB node 105 transmits and receives a broadcast signal. The IAB node 105 can detect the presence of a mobile IAB node 108 approaching the node from the broadcast information received in S400. Note that the broadcast signal may be, for example, an SSB (SS / PBCH Block). The same applies to the broadcast signals in S401, S402, etc. below.

[0050] In S401, the mobile IAB node 108 transmits and receives a broadcast signal.

[0051] In S402, the IAB donor 103 transmits and receives a notification signal.

[0052] In S403, when the station detects the presence of a mobile IAB node 108 approaching the station, it attempts to connect to the mobile IAB node 108.

[0053] In S404, the IAB node 105 generates a connection request (RRCSetupRequest) to the mobile IAB node 108. The RRCSetupRequest is a message for requesting the establishment of an RRC connection. If this IAB node 105 is a mobile IAB node, it adds identification information indicating that the node is a mobile IAB node to the RRCSetupRequest. The additional field for the identification information can be spare of the RRCSetupRequest-IEs, randomValue of ue-identity, or spare1 to 6 of establishmentCause. For example, any of spare1 to 6 is newly defined as a field such as iab-TypeIndication. Then, when "1" is set in the iab-TypeIndication field, it may be configured to indicate that the device is a mobile node, i.e., a mobile IAB node. Note that when "0" is set, it may be configured to indicate that the device is a stationary IAB node, i.e., a fixed IAB node. In this way, by using a field such as iab-TypeIndication, it becomes possible to notify other devices of information identifying whether the device is a mobile IAB node.

[0054] In S405, the mobile IAB node 108 includes the RRCSetupRequest received from the IAB node 105 in an INITIAL UL RRC MESSAGE TRANSFER MESSAGE and transmits the message to the IAB donor 103 (S405, S406).

[0055] In S406, when the IAB donor 103 receives the UL RRC MESSAGE TRANSFER MESSAGE, it extracts the RRCSetupRequest.

[0056] In steps S407 to S409, the IAB donor 103 continues processing related to RRCSetup between the IAB node 105 and the mobile IAB node 108. The IAB donor 103 includes the RRCSetup message in a DL RRC MESSAGE TRANSFER MESSAGE and sends it to the mobile IAB node 108. The mobile IAB node 108 extracts the RRCSetup from the DL RRC MESSAGE TRANSFER MESSAGE and sends it to the IAB node 105.

[0057] Next, in S410, the IAB node 105 transmits RRCSetupComplete as a second connection request to the mobile IAB node 108. At this time, the IAB node 105 includes an iab-Node indication in the RRCSetupComplete. The mobile IAB node 108 transmits a UL RRC MESSAGE TRANSFER MESSAGE including the RRCSetupComplete to the IAB donor 103 (S411).

[0058] In S412, upon receiving the UL RRC MESSAGE TRANSFER MESSAGE, the IAB donor 103 extracts RRCSetupComplete. Then, the IAB donor 103 stores type information of the IAB node 105 based on the iab-Node indication included in the extracted RRCSetupComplete. That is, the IAB donor 103 obtains identification information indicating whether the node is an IAB node from the second connection request and stores the type information.

[0059] In S413, the IAB donor 103 confirms (determines) that the connection request is from an IAB node based on the type information obtained in S412. The IAB donor 103 also confirms (determines) the request destination based on the fact that RRCSetupComplete was included in the UL RRC MESSAGE TRANSFER MESSAGE from the mobile IAB node 108. That is, the IAB donor 103 confirms (determines) that the mobile IAB node 108 is the request destination (connection destination) of the connection request. As a result, in S414, the IAB donor 103 decides to reject the connection request from the IAB node 105. In a modified example, the processes from S407 to S412 may be omitted. In this case, in S413, the IAB donor 103 may confirm that the connection request is from an IAB node based on the type information obtained in S406.

[0060] In steps S415 to S417, the IAB donor 103 notifies the IAB node 105 via the mobile IAB node 108 that the connection is rejected by RRCReconfiguration. Note that the connection may also be rejected using RRCConnectionRelease.

[0061] In S418 and S419, the IAB node 105 notifies the mobile IAB node 108 that it has accepted the denial with an RRCReconfigurationComplete.

[0062] 5 shows a processing flow of the IAB donor 103 in response to a connection request from an external device in embodiment 1. Note that an external device refers to a device that does not form a corresponding IAB network.

[0063] In S500, the IAB donor 103 acquires type information related to the external device making the connection request. Note that, as described above with reference to FIG. 4, the type information can be acquired in S410 to S412 and confirmed in S413.

[0064] In S501, the IAB donor 103 determines whether the external device attempting the connection request is an IAB node based on the type information acquired in S500. The IAB donor 103 may determine that the external device is an IAB node if the above-mentioned RRCSetupComplete includes an iab-Node indication. On the other hand, the IAB donor 103 may determine that the external device is a UE if the above-mentioned RRCSetupComplete does not include an iab-Node indication.

[0065] Also, in S501, the IAB donor 103 determines whether the connection destination related to the connection request is a mobile IAB (mobile IAB node 108 in this example). The method for this determination may be as described above. More specifically, if the iab-TypeIndication included in the second connection request is a value indicating a mobile IAB node (e.g., "1"), the IAB donor 103 determines that the connection destination related to the connection request is a mobile IAB node.

[0066] If the external device making the connection request is the IAB node 105 and the connection destination of the connection request is the mobile IAB (in this example, the mobile IAB node 108), the process proceeds to S502. In S502, the IAB donor 103 identifies the external device as an IAB node and rejects the connection. In this case, the IAB donor 103 notifies the IAB node 105 of the rejection of the connection by RRCReconfiguration, as described above with reference to FIG. 4.

[0067] In S503, the IAB donor 103 identifies that the external device making the connection request is not an IAB node and allows the connection. For example, if the external device making the connection request is a UE, the IAB donor 103 ends the process without sending RRCReconfiguration.

[0068] Meanwhile, in the upcoming Release-18, discussions are being held on the premise that a mobile IAB node will adopt a single-hop configuration that allows only UEs to connect to the mobile IAB node itself. As with conventional IAB technology, a multi-hop configuration in which a mobile IAB node has an IAB node or a relay node is not rejected. However, it is expected that adopting a multi-hop configuration will increase the complexity of network maintenance.

[0069] As a comparative example different from the present embodiment, if a connection request from IAB node 105 to mobile IAB node 108 is permitted, the following inconvenience may occur. That is, in a state where an IAB network including mobile IAB node 108 has been formed, IAB node 105 will be connected to mobile IAB node 108. In this state, if the upper-level mobile IAB node 108 moves, it may become difficult to maintain the IAB network. As a result, it will be impossible to continue communication services for the subordinate IAB node 105 and UEs 109, 109.

[0070] In contrast, according to the present embodiment, it is possible to reduce the inconvenience that may occur in such a comparative example. That is, by rejecting a connection request from IAB node 105 to mobile IAB node 108, it is possible to reduce the inconvenience that may occur in such a comparative example.

[0071] In this way, according to this embodiment, a mechanism for appropriately restricting multi-hop configurations in an IAB network environment including the mobile IAB node 108 can be established.

[0072] Second Embodiment In FIG. 1A, an IAB network is formed by the IAB donor 103 and IAB nodes 105 to 107, and a mobile IAB node 108 attempts to join the IAB network and connect to the IAB node 105. This process will be described.

[0073] The premise of this embodiment is as follows: The IAB network is operating under a load condition close to the allowable load upper limit, and it is defined that the IAB network as a whole will reject connections of mobile IAB nodes 108.

[0074] FIG. 6A is a sequence diagram of a connection control process between the IAB node 105 and the mobile IAB node 108 in the second embodiment.

[0075] In steps S600 to S602, the IAB donor 103, the IAB node 105, and the mobile IAB node 108 transmit and receive broadcast signals in the same manner as in the first embodiment.

[0076] In S600, the mobile IAB node 108 learns from the broadcast signal that the IAB node 105 exists as a neighboring node.

[0077] At S603, the mobile IAB node 108 attempts to connect to the IAB node 105.

[0078] In S604 and S605, a rule (an example of a specific setting) that does not permit connection of a mobile IAB node is shared among the IAB donors 103 and IAB nodes 105 that form the IAB network. Note that, in a modified example, S604 and S605 may be omitted.

[0079] In S606, the mobile IAB node 108 makes a connection request to the IAB node 105. At this time, the mobile IAB node 108 adds its own identification information to the RRCSetupRequest signal it issues as a connection request signal. The information added here is as defined in the first embodiment.

[0080] Specifically, the mobile IAB node 108 transmits an RRCSetupRequest to the IAB node 105. Then, the IAB node 105 transmits an INITIAL UL RRC MESSAGE TRANSFER MESSAGE including the RRCSetupRequest to the IAB donor 103 (S606, S607).

[0081] In S608, upon receiving the UL RRC MESSAGE TRANSFER MESSAGE, the IAB donor 103 extracts the RRCSetupRequest and stores connection type identification information based on the identification information in the additional field of the extracted RRCSetupRequest.

[0082] In S609, the IAB donor 103 confirms that the connection request is from an IAB node based on the identification information obtained in S608. That is, in S609, the IAB donor 103 confirms that the external device attempting the connection request is a mobile IAB node (mobile IAB node 108) based on the type information obtained in S608. As a result, in S610, the IAB donor 103 decides to reject the connection request from the mobile IAB node 108 to the IAB node 105. Then, in S611, the IAB donor 103 rejects the connection to the mobile IAB node 108 using RRCReject (S612, S613).

[0083] FIG. 6B shows a processing flow of the IAB donor 103 in response to a connection request from an external device in the second embodiment.

[0084] The process shown in FIG. 6B differs from the process shown in FIG. 5 relating to the first embodiment in that S501 is replaced with S501A.

[0085] In S501A, the IAB donor 103 determines, based on the identification information acquired in S500, whether the external device attempting the connection request is a mobile IAB node 108. If the external device making the connection request is a mobile IAB node 108, the IAB donor 103 identifies the external device as a mobile IAB node 108 and rejects the connection (S502). On the other hand, if the external device making the connection request is an IAB node (a fixed communication node), the IAB donor 103 permits the current connection request (S503).

[0086] As a comparative example different from the present embodiment, if a connection request from the mobile IAB node 108 to the IAB node 105 is permitted, the following inconvenience may occur. That is, the mobile IAB node 108 will be connected in a state where an IAB network including the IAB node 105 has been formed. If the mobile IAB node 108 moves in this state, it may become difficult to maintain the IAB network.

[0087] In contrast, according to the present embodiment, it is possible to reduce the inconvenience that may occur in such a comparative example. That is, by rejecting a connection request from the mobile IAB node 108 to the IAB node, it is possible to reduce the inconvenience that may occur in such a comparative example.

[0088] In this way, according to the second embodiment, similar to the first embodiment described above, it is possible to establish a mechanism for appropriately restricting a multi-hop configuration in an IAB network environment including the mobile IAB node 108. Furthermore, according to the second embodiment, it is possible to appropriately restrict a multi-hop configuration based on a pre-set rule (specifically, a rule that does not permit connection of the mobile IAB node 108 to the IAB network). Note that the second embodiment illustrates an example in which an iab-TypeIndication is included in an RRC SetupRequest, which is an example of a connection request, and an iab-NodeIndication is included in an RRC SetupComplete, which is also an example of a connection request. However, the present invention is not limited to this, and it is also possible to configure the RRC SetupRequest to include both an iab-TypeIndication and an iab-NodeIndication. Furthermore, it is also possible to configure the RRC SetupComplete message to include both iab-TypeIndication and iab-NodeIndication. If the former is adopted, it is possible to determine whether or not a connection can be established at an early stage of the connection process, thereby reducing computational costs. If the latter is adopted, it is possible to determine whether or not a connection can be established without significantly modifying the current communication standard. In other words, it is possible to transmit information regarding whether or not a connection can be established by simply adding iab-TypeIndication to an RRC SetupComplete message that is already defined to include the iab-NodeIndication format.

[0089] Note that this second embodiment can be effectively combined with the first embodiment described above. In this case, if the request source of the connection request is the mobile IAB node 108 and the request destination is the mobile IAB node 108, the connection request may be rejected. Note that this embodiment illustrates a case where the IAB donor 103 rejects the connection request, but a configuration is also possible in which the lower node makes the rejection decision. In this case, the IAB node 105, which has a pre-shared rule that does not allow mobile IAB node connections, refers to the contents of the connection request (RRC SetupRequest) received from the IAB node 108. Next, the IAB node 105 determines to reject the connection request if the iab-TypeIndication included in the connection request is a value indicating a mobile IAB node (e.g., "1"). If it is determined to reject the connection request, the IAB node 105 rejects the connection request by transmitting an RRC reject message, which is a response message to the mobile IAB node 108. On the other hand, if the iab-TypeIndication included in the connection request does not have a value indicating a mobile IAB node (e.g., "1"), the IAB node 105 forwards the connection request to the IAB donor 105, which is the upper IAB node. The subsequent connection process may be the same as that described in the above embodiment. According to this modification of the second embodiment, the downstream IAB node can appropriately restrict the multi-hop configuration based on a rule shared in advance (specifically, a rule that does not allow the mobile IAB node 108 to connect to the IAB network).

[0090] Third Embodiment In FIG. 1B, an IAB network is formed by the IAB donor 103 and IAB nodes 105 to 107, and a mobile IAB node 108 attempts to join the IAB network and connect to the IAB node 107. This process will be described.

[0091] In the IAB network formed in this embodiment, a number of IAB node hops, N, is defined. The "N" in the number of IAB node hops, N, is a natural number equal to or greater than 2, and means that the mobile IAB node 108 is not permitted to connect to IAB nodes at the Nth tier or later.

[0092] In the third embodiment, the number of hops forming an IAB node N is set to 2 (an example of a threshold value).

[0093] FIG. 7A is a sequence diagram of connection control processing between the mobile IAB node 108 and the IAB node 107 in the third embodiment.

[0094] In steps S700 to S703, the IAB donor 103, the IAB node 107, and the mobile IAB node 108 transmit and receive broadcast signals in the same manner as in the first embodiment.

[0095] In S704, the IAB node 107 notifies the IAB donor 103 of the number of IAB hops in the IAB network of the node.

[0096] To determine the number of hops, you can use Phase 2-2: Routing update of the IAB-node Integration Procedure defined in TS38.401 8.12. In other words, in Phase 2-2: Routing update, you can determine the number of hops in your IAB network by executing, for example, Traceroute when acquiring an IP address.

[0097] This information can be communicated to the IAB donor 103 through the BAP.

[0098] In S705, the number of hops N constituting the IAB network is defined as 2, and this is notified to the IAB nodes 105 to 107 constituting the IAB network.

[0099] Next, the mobile IAB node 108 transmits an RRCSetupRequest to the IAB node 107. Then, the IAB node 107 transmits an INITIAL UL RRC MESSAGE TRANSFER MESSAGE including the RRCSetupRequest to the IAB donor 103 (S706, S707).

[0100] In S708, when the IAB donor 103 receives the UL RRC MESSAGE TRANSFER MESSAGE, it extracts the RRCSetupRequest.

[0101] In S709, the IAB donor 103 determines the hop count of the IAB node 107 and determines whether to reject the connection based on the identification information of the mobile IAB node 108 attempting the connection request. For example, when the IAB donor 103 receives an INITIAL UL RRC MESSAGE TRANSFER MESSAGE including an RRCSetupRequest from the IAB node 107, the following may occur: First, the IAB donor 103 may determine that the hop count of the IAB node that sent the RRCSetupRequest is the hop count of the IAB node 107 + 1 (i.e., 2 in the example of FIG. 7A ). Then, if the current hop count is the configured hop count N, the IAB donor 103 determines to reject the connection request from the mobile IAB node 108 to the IAB node 107. As a result, in S710, the IAB donor 103 decides to reject the connection request from the mobile IAB node 108 to the IAB node 107. Then, in S711, the IAB donor 103 rejects the connection to the mobile IAB node 108 using RRCReject (S712, S713). Note that if the external device attempting the connection request is not the mobile IAB node 108 but a UE, the IAB donor 103 may accept the connection request.

[0102] FIG. 7B shows the processing flow of the IAB donor 103 in response to a connection request from an external device in the third embodiment.

[0103] The process shown in FIG. 7B differs from the process shown in FIG. 5 relating to the first embodiment in that if the determination result in S501 is "YES", the process proceeds to S700 instead of S502.

[0104] In S700, the IAB donor 103 determines whether the current hop count is equal to the configured hop count N. If the current hop count is equal to the configured hop count N, the IAB donor 103 rejects the current connection request (S502). On the other hand, if the current hop count is smaller than the configured hop count N, the IAB donor 103 accepts the current connection request (S503).

[0105] 7B, the determination process of S501 is the same as the process shown in FIG. 5 in relation to the first embodiment, but may be different. For example, in FIG. 7B, as a process instead of S501, the IAB donor 103 may simply determine whether the external device attempting the connection request is an IAB node based on the type information acquired in S500. In other words, in FIG. 7B, it is not necessary to determine whether the connection destination related to the connection request is the mobile IAB node 108.

[0106] In a comparative example different from the present embodiment, if a connection request is permitted based on a condition that does not take the number of hops into consideration, the following inconvenience may occur: An IAB network with an excessive number of hops may be formed, and in such a state, network maintenance may become more complex, making it difficult to maintain a stable IAB network.

[0107] In contrast, according to the present embodiment, it is possible to reduce the inconvenience that may occur in such a comparative example. That is, by rejecting a connection request in which the number of hops exceeds the number of configured hops N, it is possible to reduce the inconvenience that may occur in such a comparative example.

[0108] In this way, according to the third embodiment, similar to the first embodiment described above, it is possible to establish a mechanism for appropriately restricting a multi-hop configuration in an IAB network environment including the mobile IAB node 108. Furthermore, according to the third embodiment, it is possible to appropriately restrict a multi-hop configuration based on a pre-set rule (specifically, a rule that does not permit connection of an IAB node whose number of hops exceeds the number of configured hops N).

[0109] Note that the present embodiment 3 can be effectively combined with the above-described embodiment 2. For example, when the present embodiment 3 and embodiment 2 are effectively combined, if the request source of the connection request is the mobile IAB node 108 and the current hop count is the configured hop count N, the connection request may be rejected.

[0110] [Other Embodiments] As described in the above embodiment, the transmission and reception of identification information is assumed to be an identification process performed by adding an identification signal in the RRC. That is, this is described as a processing method corresponding to Phase 1: IAB-MT setup in the IAB-node Integration Procedure, an IAB node connection sequence according to the 3GPP standard defined in TS38.401 8.12. However, identification may also be performed in each phase, such as Phase 2-1: BH RLC channel establishment, Phase 2-2: Routing update, or Phase 3: IAB-DU setup.

[0111] Furthermore, although the above-described embodiment relates to public network communication services, it may also be applied to local 5G or the like.

[0112] The present invention is not limited to the above-described embodiments, and various modifications and variations can be made without departing from the spirit and scope of the present invention. Therefore, the following claims are appended to apprise the public of the scope of the present invention.

[0113] This application claims priority based on Japanese Patent Application No. 2023-078127, filed on May 10, 2023, the entire contents of which are incorporated herein by reference.

[0114] 101 Cell coverage 102 Cell coverage 103 IAB donor (an example of a base station device) 104 IAB donor 105 IAB node (an example of a communication device) 106 IAB node (an example of a communication device) 107 IAB node (an example of a communication device) 108 Mobile IAB node (an example of a communication device) 109 to 114 UE 201 Control unit (an example of a processing means and a request means) 202 Storage unit 203 Wireless communication unit (an example of an acquisition means) 204 Antenna control unit 301 Software function block 302 Signal transmission unit 303 Signal reception unit 304 Data storage unit 305 Connection control unit 308 Signal generation unit 401 Software function block 402 Signal transmission unit 403 Signal reception unit 404 Data storage unit 405 Connection control unit 406 Network configuration information management unit

Claims

1. A base station device related to the provision of a communication service, comprising: an acquisition means for acquiring a connection request from an external device to an IAB (Integrated Access and Backhaul) node; and a processing means for performing processing to reject the connection request at least when the one IAB node is a mobile IAB node and the external device is another IAB node.

2. The base station device according to claim 1, wherein the processing means accepts the connection request when the external device is a UE (User Equipment).

3. The base station device according to claim 1 or 2, wherein the connection request includes type information indicating whether the external device is an IAB node or not.

4. A base station device as claimed in any one of claims 1 to 3, characterized in that the processing means is further configured to reject the connection request when a specific setting is made in the base station device and the external device is a mobile IAB node, and to accept the connection request when the specific setting is made in the base station device and the external device is a UE (User Equipment) or a fixed IAB node.

5. The base station device according to claim 4, wherein the connection request includes identification information indicating whether the external device is a mobile IAB node.

6. The base station device according to any one of claims 1 to 5, wherein the processing means is further characterized in that, when the external device is another IAB node, and when accepting the connection request would result in a hop count to the other IAB node exceeding a threshold, the processing means rejects the connection request.

7. A communications device mounted on a mobile body or in the form of a mobile body, capable of forming an IAB network, comprising: a requesting means for making a connection request to an IAB node; and a processing means for providing a communications service to a subordinate UE (User Equipment) via the IAB node when the connection request is accepted, wherein the requesting means includes identification information indicating that the node is a mobile IAB node in the connection request.

8. A control method for controlling communications, comprising: an acquisition step of acquiring a connection request from an external device to an IAB (Integrated Access and Backhaul) node; and a processing step of rejecting the connection request at least when the IAB node is a mobile IAB node and the external device is another IAB node.

9. A program for causing a computer to execute the steps of: acquiring a connection request from an external device to an IAB (Integrated Access and Backhaul) node; and, at least when the one IAB node is a mobile IAB node and the external device is another IAB node, performing processing to reject the connection request.

10. A method for controlling a communications device, comprising the steps of: transmitting a connection request to an IAB (Integrated Access and Backhaul) node, the connection request including identification information indicating that the node is a mobile IAB node; and, if the connection request is accepted, providing a wireless connection to a subordinate UE (User Equipment) via the IAB node.

11. A program for causing a computer of a communications device to execute the steps of: sending a connection request to an IAB node, the connection request including identification information indicating that the IAB node is a mobile IAB node; and, if the connection request is accepted, providing a wireless connection to a subordinate UE (User Equipment) via the IAB node.

Citation Information

Patent Citations

  • Initial access and radio resource management for integrated access and backhaul (IAB) wireless networks

    JP2019534625A

  • Methods directed to crystalline biomolecules

    JP2023078127A

  • Signaling to support mobile integrated access and backhaul

    JP2022543810A