Control unit, communication device, control method, and program

The control device facilitates dynamic adjustment of access restrictions in mobile IAB nodes through notifications from UEs or external devices, addressing the need for flexible network management and congestion relief in vehicular relay systems.

JP2024162066APending Publication Date: 2024-11-21CANON KK
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2023077247
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-09
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

Existing mechanisms lack a convenient switching mechanism for access restrictions in mobile IAB nodes, which are essential for flexible network expansion and congestion alleviation in vehicular relay systems.

Method used

A control device and method that includes a transmitting means to request mobile IAB nodes to lift access restrictions based on conditions such as 'no connectable base stations' notifications from UEs or external devices, using protocols like BAP, SIB, or F1AP, allowing dynamic adjustment of access restrictions.

Benefits of technology

Enables convenient switching of access restrictions in mobile IAB nodes, enhancing network flexibility and alleviating congestion by expanding coverage and managing access rights effectively.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024162066000001_ABST
    Figure 2024162066000001_ABST
Patent Text Reader

Abstract

To provide a mechanism that can achieve switching related to access restriction in a mobile IAB node in a mode highly convenient for a user and a common carrier.SOLUTION: A control unit is disclosed, which comprises transmission means that transmits, to a mobile IAB node to which access restriction is set, a request for demanding cancellation of the access restriction. Preferably, the transmission means transmits the request when a predetermined condition is satisfied. Preferably, the control unit further comprises first reception means that receives a notification including the fact that there is no base station connectable from user equipment (UE). The predetermined condition is satisfied upon reception of the notification.SELECTED DRAWING: Figure 4
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

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

[0002] The 3GPP (3rd Generation Partnership Project) (registered trademark) is currently working on standardizing IAB as a communication technology for backhaul. IAB is an abbreviation for Integrated Access and Backhaul.

[0003] The IAB technology is a technology that simultaneously uses millimeter wave wireless communication in the 28 GHz band or the like, which is used for access communication between a base station and user equipment (UE: User Equipment), as backhaul communication (Patent Document 1).

[0004] In backhaul communications using IAB technology, relay devices called IAB nodes relay communications from IAB donors, which are equivalent to conventional base stations, using millimeter wave communications. Furthermore, IAB nodes can form communication links with multiple other IAB nodes to form a network tree starting from the IAB donor, thereby expanding the coverage area.

[0005] In the IAB technology, communication between an IAB donor and an IAB node, and between IAB nodes, is controlled via a Backhaul Adaptation Protocol (BAP).

[0006] BAP is primarily defined as a protocol for routing data between multiple IAB nodes.

[0007] Up until Release-17, 3GPP's IAB-related specification discussions have focused on fixed base stations (IAB nodes that do not move).

[0008] Currently, 3GPP (registered trademark) is planning to develop a vehicle mounted relay, which will be a use case in Release-18, and specifications to realize this use case. [Prior art documents] [Patent documents]

[0009] [Patent Document 1] Special Publication No. 2019-534625 Summary of the Invention [Problem to be solved by the invention]

[0010] Vehicle-mounted relays are assumed to be equipped with functions equivalent to an IAB node in moving objects such as automobiles and trains. Due to their characteristic of being a moving IAB node, vehicle-mounted relays are also called mobile IAB or mobile IAB nodes. In order to actually operate such mobile IAB nodes, various requirements are required that cannot be met by the specifications that have been discussed so far, which are based on fixed base stations.

[0011] Meanwhile, the mobile IAB node is expected to play a role in flexibly adjusting the public network as a temporary node to expand the coverage area of ​​the public network and to alleviate congestion in the public network.

[0012] The mobile IAB node is also expected to play a role in restricting access by limiting the parties that can connect to the UE of certain related parties, such as the owner of the vehicle or their family, and to be used as an in-vehicle broadband line for personal use.

[0013] One possible use case would be to make it possible for a mobile IAB node to switch between the former and latter roles. A specific example will be explained. For example, if a mobile IAB node that operates as a personal broadband line with access restrictions is temporarily released from the access restrictions and allowed to be used as a public network, it would be possible to flexibly alleviate congestion in the public network.

[0014] However, there is a problem in that no mechanism has been devised that enables switching of access restrictions at a mobile IAB node in a manner that is highly convenient for users and telecommunications carriers.

[0015] The present invention has been made in consideration of at least one of the above problems. One aspect of the present invention aims to provide a switching mechanism that is highly convenient for users and communication carriers. [Means for solving the problem]

[0016] A control device according to one aspect of the present invention includes a transmission unit that transmits a request to a mobile IAB node, to which an access restriction is set, to request that the access restriction be lifted. Effect of the Invention

[0017] According to one aspect of the present invention, it is possible to provide a mechanism that enables switching of access restrictions in a mobile IAB node in a manner that is highly convenient for users and telecommunications carriers. [Brief description of the drawings]

[0018] [Figure 1] FIG. 2 is a hardware functional block diagram of an IAB donor and a mobile IAB node in the present invention. [Figure 2A] FIG. 2 is a software functional block diagram of an IAB donor according to the present invention. [Figure 2B]FIG. 2 is a software functional block diagram of a mobile IAB node in the present invention. [Diagram 3] FIG. 1 is a system configuration diagram according to a first embodiment. [Figure 4] FIG. 2 is a sequence diagram according to the first embodiment. [Diagram 5] FIG. 4 is a flow diagram showing the operation of a UE in the first embodiment. [Figure 6] FIG. 2 is a flow chart showing the operation of an IAB donor in embodiment 1. [Figure 7] FIG. 2 is a flow diagram showing the operation of a mobile IAB node in the present invention. [Figure 8] FIG. 11 is a system configuration diagram according to a second embodiment. [Figure 9] FIG. 11 is a sequence diagram according to the second embodiment. [Figure 10] FIG. 11 is a flow diagram showing the operation of an IAB donor in embodiment 2. [Figure 11] FIG. 11 is a sequence diagram according to the third embodiment. [Figure 12] FIG. 13 is a system configuration diagram according to a fourth embodiment. [Figure 13] FIG. 13 is a sequence diagram according to the fourth embodiment. [Figure 14] FIG. 11 is a flow diagram showing the operation of a UE in embodiment 4. [Figure 15] FIG. 2 is a flow diagram showing the operation of an IAB donor in this embodiment. [Figure 16] FIG. 4 is a flow diagram showing the operation of a mobile IAB node in this embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

[0020] [Embodiment 1] Fig. 1 is a hardware functional block diagram of an IAB donor in this embodiment. Note that Fig. 1 is a hardware functional block diagram of an IAB donor, but a hardware functional block diagram of a mobile IAB node may be similar. In the following, as an example, it is assumed that the IAB donor and the mobile IAB node have the same hardware configuration.

[0021] The hardware functional block 101 of the IAB donor and mobile IAB node includes a control unit 102 , a memory unit 103 , a wireless communication unit 104 , a wireless antenna control unit 105 , a GPS communication unit 106 , and a GPS antenna control unit 107 .

[0022] The control unit 102 controls the entire device by executing a control program stored in the storage unit 103. The control unit 102 is configured with one or more processors such as a CPU or MPU, and controls the entire communication device by executing a control program read into the RAM, which is the storage unit 103. 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 FPGA. ASIC is an abbreviation for Application Specific Integrated Circuit. FPGA is an abbreviation for Field Programmable Gate Array. The hardware circuit and a processor such as a CPU or MPU can cooperate to realize the process described in the flowcharts below.

[0023] The storage unit 103 stores the control program executed by the control unit 102 and various information such as a cell ID and connected UE information. The storage unit 103 may include a main storage unit and an auxiliary storage unit. The main storage unit is, for example, a ROM (Read Only Memory) or a RAM (Random Access Memory). The main storage unit may store or temporarily store programs and data such as an OS (Operating System) which is basic software executed by the control unit 102 and application software. The auxiliary storage unit is, for example, a HDD (Hard Disk Drive) or an SSD (Solid State Drive), and may store data related to application software. For example, the control program stored in the non-volatile storage area is expanded in a RAM (Random Access Memory) and executed by a processor constituting the control unit 102. In this manner, the control unit 102 and the storage unit 103 may function as a so-called computer.

[0024] The wireless communication unit 104 performs cellular network communication such as LTE (Long Term Evolution) and 5G NR (New Radio) that comply with the 3GPP (registered trademark) standard.

[0025] The radio antenna control unit 105 controls the antenna used for the wireless communication performed by the wireless communication unit 104 .

[0026] The GPS communication unit 106 receives satellite signals from GPS (Global Positioning System) satellites and acquires current location information including position specifying information such as longitude and latitude information. The GPS communication unit 106 may have a function of measuring (locating) the current location based on the satellite signals.

[0027] The GPS antenna control unit 107 controls an antenna (not shown) used for communication performed by the GPS communication unit 106 .

[0028] FIG. 2A is a software functional block diagram of the IAB donor in this embodiment.

[0029] The IAB donor software function block 201 is stored in the memory unit 103 and executed in the control unit 102.

[0030] The software functional block 201 includes a signal transmitting unit 202 , a signal receiving unit 203 , a data storage unit 204 , a connection control unit 205 , an access restriction removal request notification determining unit 206 , and a message generating unit 207 .

[0031] The signal transmitting unit 202 and the signal receiving unit 203 control the wireless communication unit 104 via the control unit 102, and perform cellular network communication such as LET and 5G that conforms to the 3GPP (registered trademark) standard with the UE and external devices.

[0032] The data storage unit 204 controls and manages the storage unit 103, which is the entity, and stores the software itself, cell information, information on UEs and mobile IAB nodes connected to IAB donors, etc. The connection control unit 205 controls the radio antenna control unit 105 via the control unit 102 during wireless communication.

[0033] The access restriction release request notification determination unit 206 determines whether to notify the mobile IAB node of an access restriction release request. In this embodiment, the unit determines to notify the mobile IAB node of the release request under the condition that a notification that there is no connectable base station is received from the UE and / or a request to notify the release request is received from an external device.

[0034] In addition, the access restriction release request notification determination unit 206 may add the state of its own station (IAB donor) to the determination criteria. For example, if the number of connectable devices (the number of UEs that can connect to itself) has not reached the upper limit when a notification that there is no base station that can be connected is received from the UE, it may determine not to notify the mobile IAB node of the release request. It may also determine to notify the mobile IAB node of the release request by itself by detecting that the number of connected devices frequently reaches the upper limit or that the communication quality is poor, such as a decrease in the throughput between itself and the UE.

[0035] The message generating unit 207 generates a message of an access restriction lift request to be notified to the mobile IAB node.

[0036] FIG. 2B is a software functional block diagram of a mobile IAB node in this embodiment.

[0037] The software function block 211 of the mobile IAB node includes a communication transmitting unit 212 , a communication receiving unit 213 , a data storage unit 214 , a connection control unit 215 , an access restriction control unit 216 , and an access restriction lift determination unit 217 .

[0038] The configuration of each of the units 212 to 215 is similar to that of each of the units 202 to 205 described above with reference to FIG. 2A, and therefore a description thereof will be omitted.

[0039] The access restriction control unit 216 controls the access restriction of UEs connected to itself. When the access restriction is enabled, access is permitted only for specific UEs, and when the access restriction is disabled, access is permitted from all UEs.

[0040] The access restriction release determination unit 217 determines whether to release the access restriction in response to an external access restriction release request. A possible condition for the release is permission for release from the mobile IAB node owner. A response to the release request may be set in advance, or the owner's UE or the like may confirm whether or not the release is permitted when the release request is notified.

[0041] The access restriction release determination unit 217 may also determine whether to resume the access restriction. Conditions for resuming the access restriction may include a certain period of time having passed since the last time a request to release the access restriction was received, an instruction from the owner to resume the access restriction, and the like.

[0042] FIG. 3 is a diagram showing an example of a system configuration according to this embodiment.

[0043] In a mobile communication system, there is an IAB donor 302 that connects to a CN (Core Network), and in the vicinity there are a UE 301, a mobile IAB node 303, a mobile IAB node 304, and a plurality of other UEs.

[0044] Assume that a mobile IAB node 303 and multiple other UEs are connected to the IAB donor 302, and the number of connections to the IAB donor 302 has reached its upper limit. The mobile IAB node 303 is connected to the IAB donor 302, and access restriction is enabled. The mobile IAB node 304 is connected to a base station other than the IAB donor 302. Alternatively, the mobile IAB node 304 may currently be operating in an RRC idle state, i.e., not connected to any base station, and access restriction may be enabled.

[0045] It is assumed that UE301 does not have access rights to mobile IAB nodes 303 and 304. In this embodiment, the access restriction of the mobile IAB node uses a CAG (Closed Access Group) function. The CAG function is one of the functions for non-public networks defined by 3GPP (registered trademark). The non-public network is also called Non-Public Network, and may be abbreviated as NPN hereinafter. Specifically, the CAG function is a function in which a base station constituting an NPN controls the access rights of a UE. The base station broadcasts a CAG ID, which is an identification ID of the NPN, and the UE that receives the CAG checks whether or not it has access rights by comparing it with a list of accessible CAGs stored in itself. If the UE does not have access rights, the base station is excluded from the target of the connection process. In this situation, the only base station that UE301 can detect is IAB donor 302, and since IAB donor 302 cannot be connected due to the upper limit of the number of connections, UE301 is in a state of "there is no base station that can be connected."

[0046] In such a situation, a procedure for releasing the access restriction of mobile IAB node 303 and mobile IAB node 304 in order to connect UE 301 to the cellular network will be described.

[0047] FIG. 4 shows a sequence diagram in this embodiment.

[0048] In S401, the UE (hereinafter, UE 301) notifies the IAB donor 302 of a connection request (RRC Setup Request). The IAB donor 302 that has received the connection request determines that it will not allow the UE 301 to connect because its own number of connections has reached its upper limit, and notifies the UE of a connection rejection (RRC Reject) in S402. The UE 301 that has received the connection rejection is now in a situation where it cannot connect to any base station that it can detect, and determines that there is "no base station available for connection."

[0049] In S403, UE301 notifies IAB donor 302 that "there is no base station that can be connected". If there are multiple detectable base stations, the UE301 notifies the base station with the strongest signal strength. In this embodiment, only IAB donor 302 is notified, but multiple base stations may be notified. The notification method uses the RRC (Radio Resource Control) protocol as in the connection request. The RRC protocol is a layer 3 protocol used in communication between UEs and base stations in LTE and 5G systems. In the case of 5G, it is specified in TS 38.331. The notification of "there is no base station that can be connected" is notified using the message format of the connection request (RRC Setup Request). The RRC Setup Request has an item for entering a connection reason called "EstablishmentCase". By adding a new definition of "there is no base station that can be connected" and entering it in this item, it is possible for a UE before connection to a cellular network (RRC IDLE) to notify a base station that "there is no base station that can be connected". In this embodiment, the RRC Setup Request is used, but a new message format may be defined.

[0050] Upon receiving a notification from UE 301 that "there is no base station available for connection," IAB donor 302 notifies the mobile IAB node of a request to remove access restriction in S404.

[0051] Here, there are two possible notification methods. Specifically, the first method is to notify a mobile IAB node connected to itself (IAB donor 302), such as mobile IAB node 303. The second method is to notify a mobile IAB node not connected to itself, such as mobile IAB node 304.

[0052] In the first method, the notification is sent to the mobile IAB node connected to itself, so the destination is clear. For example, the notification can be sent to the BAP (Backhaul Adaptation Protocol) address of the mobile IAB node using a BAP message. The BAP message is a layer 2 protocol used to route data to an IAB node in a 5G system defined by 3GPP (registered trademark). BAP is defined in TS 38.340. Note that instead of the BAP message, F1AP (F1 Application Protocol) may be used to notify the mobile IAB node. F1AP is defined in TS 38.473. The message to be notified here includes the following information items. Information item 1: Request details Information item 2: Period The request content of information item 1 includes time information such as "start of release of access restriction" and "stop of release of access restriction". Although not mentioned in this embodiment, by including "start of access restriction" and "stop of access restriction", it becomes possible to enable access restriction for a mobile IAB node from outside. The period in information item 2 includes the validity period of the change request. It is used to determine when the mobile IAB will resume the access restriction in response to the access restriction lift request. If the period is short, the mobile IAB node can resume the access restriction after the validity period has elapsed without waiting for a request to "stop lifting the access restriction." Note that the mobile IAB node can resume the access restriction if it receives a request from the IAB donor to "stop lifting the access restriction" during the validity period.

[0053] The mobile IAB nodes to which the notification is sent by the first method may be some of all the mobile IAB nodes forming the IAB network, or may be all the mobile IAB nodes forming the IAB network. In the case of some of the mobile IAB nodes, the some of the mobile IAB nodes may include mobile IAB nodes located near the UE (UE that cannot connect to the base station).

[0054] In the second method, the notification is directed to a mobile IAB node that is not connected to the node itself, so the destination is unknown. Therefore, the node notifies the mobile IAB nodes in the vicinity of the node of an access control request by broadcasting notification information to the node. For example, a SIB (System Information Block) is used for the broadcast. As in the first method, the second method also includes the following in the broadcast information. The following information items are included: Information item 1: Request details Information item 2: Period S401 to S404 are repeated periodically while the UE cannot connect to the base station.

[0055] The mobile IAB node that has received the access restriction lift request determines whether or not to lift the access restriction using a determination means described below, and if it determines to lift the access restriction, the mobile IAB node lifts the access restriction in S405.

[0056] When the mobile IAB node releases the access restriction, the mobile IAB node becomes detectable from the UE 301, and the UE 301 starts connection processing to the detected mobile IAB node. After that, the UE establishes a connection to the mobile IAB node according to the UE connection establishment procedure described in the 3GPP (registered trademark) specification TS 38.300.

[0057] In S406, UE301 notifies the mobile IAB node of a connection request (RRC Setup Request). If connection is possible, in S407, the mobile IAB node notifies UE301 of RRC Setup. This message includes cell configuration information and the like required for connection processing. Finally, in S408, UE301 notifies the mobile IAB node of connection completion (RRC Setup Complete), and the connection processing is completed.

[0058] Next, the process of each device in the above sequence will be described with reference to a flow chart.

[0059] FIG. 5 is a flow diagram showing an operation of the UE (UE 301) in the first embodiment.

[0060] S501 to S503 are UE connection procedures described in 3GPP (registered trademark) specification TS 38.300.

[0061] In S501, the UE determines whether there is a base station nearby that is a connection candidate based on information broadcast by the base station. If there is a base station nearby that is a connection candidate, the UE proceeds to S502.

[0062] In S502, the UE performs connection processing to the connection candidate base stations in order of priority.

[0063] In S503, the UE checks the result of the connection process. If the UE is unable to connect to all of the candidate base stations, the process proceeds to S504. If the UE is able to connect to any of the base stations, the process ends.

[0064] In S504, the connection candidate base stations are notified that "there is no base station to which connection can be made." The notification method is as explained in S403 of Fig. 4. When the notification is completed, the process returns to S501 and the process is repeated.

[0065] FIG. 6 is a flow diagram showing the operation of the IAB donor 302 in the first embodiment.

[0066] In S601, the access restriction release request notification determination unit 206 of the IAB donor 302 determines whether to notify an "access restriction release request." In this embodiment, the determination is made based on whether a "there is no connectable base station" notification has been received from the UE. If a notification has been received, the process proceeds to S602.

[0067] In S602, a message of "access restriction release request" to be notified to the mobile IAB node is generated. The message to be generated is as described in S404 of FIG. 4. A BAP message is generated for the mobile IAB node to which it connects, and notification information is generated for the mobile IAB nodes in the vicinity. If there are multiple mobile IAB nodes to which it connects, a BAP message may be generated for some or all of them. In this embodiment, both the BAP message and the notification information are generated, but only one of them may be generated. When an access restriction release request is issued to the mobile IAB based on a notification from the UE that "there is no base station that can be connected", the information to be included in the message is information item 1: request content "start of access restriction release" and information item 2: period "short period". This is because the rescue of the UE is a temporary measure. In addition, the mobile IAB node can move outside the cell range of the IAB donor 302, and it is not necessarily possible to receive the "access restriction stop request" from the IAB donor 302. An expiration date is set so that the access restriction can be resumed at the discretion of the mobile IAB node without waiting for a "request to stop access restriction" from the IAB donor 302.

[0068] In S603, the mobile IAB node is notified of the generated "access restriction release request" message. When the notification is complete, the process returns to S601 and repeats the process.

[0069] FIG. 7 is a flow diagram showing the operation of the mobile IAB node in this embodiment.

[0070] In S700, the access restriction release determination unit 217 of the mobile IAB node determines whether or not access restriction release is in progress. If access restriction release is in progress, proceed to S704, and if access restriction release is not in progress, proceed to S701.

[0071] In S701, it is confirmed whether or not an "access restriction release request" has been received from the IAB donor 302. If it has been received, the process proceeds to S702. If it has not been received, the process returns to S700 in the next processing cycle.

[0072] In S702, the access restriction release determination unit 217 of the mobile IAB node determines whether the conditions for access restriction release are met. In this embodiment, the determination is made based on the condition of whether permission to release access restriction has been set in advance by the owner of the mobile IAB node. The permission setting for access restriction release is stored in the data storage unit 214. If the conditions are met, proceed to S703. If the conditions are not met, return to the process from S700 in the next processing cycle.

[0073] In S703, the access restriction control unit 216 of the mobile IAB node starts to release the access restriction if the access restriction is in effect. In this case, the process returns to S700 in the next processing cycle.

[0074] In S704, the access restriction release determination unit 217 of the mobile IAB node determines whether the conditions for resuming the access restriction are met. In this embodiment, the determination is made based on whether a certain period of time has passed since the last "access restriction release request" was received. The certain period of time is the value of the "period" included in the last received "access restriction release request." The owner may set an upper limit on the certain period of time. If either the value of the "period" in the release request or the upper limit previously set by the owner has passed, it is determined that the conditions for resuming the access restriction are met. In this case, the process proceeds to S705, where the release of the access restriction is stopped and the access restriction is resumed (S705). If it is determined that the conditions for resuming the access restriction are not met, the process returns to S700 in the next processing cycle.

[0075] In the first embodiment, a procedure has been described in which the IAB donor 302 notifies surrounding mobile IAB nodes of an access restriction lift request based on receiving a "connectable base station not available" notification from the UE. This makes it possible to externally lift the access restriction of the mobile IAB node, thereby rescuing the UE that cannot connect.

[0076] [Embodiment 2] In the first embodiment, the IAB donor 302 notifies surrounding mobile IAB nodes of an access restriction lift request based on receiving a notification from the UE that "there is no base station that can be connected." In this embodiment, a procedure for notifying surrounding mobile IAB nodes of an access restriction lift request based on a notification from an external device other than the UE will be described.

[0077] A possible use case for the second embodiment is, for example, the elimination of communication congestion by a communication carrier.

[0078] When an event is held in a specific area and communication congestion is expected, the communication carrier identifies the base stations (IAB donors) set up in that area based on the installation information of the base stations that the carrier manages. The carrier then issues instructions to the identified base stations to notify surrounding mobile IAB nodes of a request to lift access restrictions. This makes it possible to temporarily increase the number of base stations in a specific area, thereby increasing the number of UEs that can be connected.

[0079] FIG. 8 is a diagram showing an example of a system configuration in this embodiment.

[0080] There is an IAB donor 302 installed in a specific area, and in the vicinity there are a mobile IAB node 303 and a mobile IAB node 304. The mobile IAB node 303 and the mobile IAB node 304 are the same as those in the first embodiment. An external device 801 is capable of communicating with the IAB donor 302 via a mobile communication system.

[0081] In such a situation, a procedure for releasing the access restriction on the mobile IAB node 303 and the mobile IAB node 304 from the external device 801 via the IAB donor 302 will be described.

[0082] FIG. 9 shows a sequence diagram in this embodiment.

[0083] In step S901, the external device 801 notifies the IAB donor 302 of a request to start notification of access restriction lift.

[0084] The access restriction release notification start request is a request to the IAB donor 302 to start a request to the mobile IAB node. The access restriction release notification start request is a request to the IAB donor 302 to start a process of notifying the mobile IAB node of an "access restriction release request". When the external device 801 is a core network (5GC), the 5GC and the base station are connected via an NG interface. Messages of the application layer via the NG interface are specified in TS38.413. The access restriction release start request of this embodiment and the access restriction release stop request described later use messages newly defined in accordance with this specification. These requests use the same message and include the following information items. Information item 1: Request details Information item 2: Period Information Item 3: What to include in your request to lift access restrictions Information item 1: The request content includes information such as "start notification" and "stop notification". Information item 2: The period includes the expiration date of the notification request. Information item 3: The content to be included in the access restriction release request includes information on the content to be included in the access restriction release request message that the IAB donor 302 that received the notification start request notifies surrounding mobile IAB nodes. In this embodiment, information item 1: The request content includes "start notification", information item 2: The period is "unlimited", and information item 3: The content to be included in the access restriction release request includes "request content (start of access restriction release), period (short time)". In this embodiment, the external device 801 and the IAB donor 302 are fixed devices and can communicate permanently. Therefore, in order to reduce the amount of communication between the external device 801 and the IAB donor 302, information item 2: The period is set to "unlimited" so that the notification start request is sent only once. The IAB donor 302 that received the notification start request notifies the surrounding mobile IAB nodes of the access restriction release request. The notification means and contents are the same as in embodiment 1. Explanation will be omitted. The mobile IAB node that received the access restriction lift request also lifts the access restriction in the same manner as in embodiment 1. Explanation will be omitted. The IAB donor 302 continues to periodically notify the access restriction lift request, and stops notifying the access restriction lift request upon receiving a request to stop notifying the access restriction lift from the external device 801 in S902. The request to notify the access restriction lift from the external device 801 includes "stop notification" in information item 1: change content and "unlimited" in information item 2: period.

[0085] In FIG. 9, the IAB donor 302 notifies the mobile IAB nodes around it of an access restriction release request. In this case, the access restriction release request may be broadcast to the mobile IAB nodes around it, not to a specific mobile IAB node. In the example shown in FIG. 9, even after a mobile IAB node releases the access restriction, the access restriction release request is periodically notified until S902. Here, during the period from S901 to S902, the mobile IAB nodes around the IAB donor 302 may change. For example, a mobile IAB node that is around the IAB donor 302 at a certain point in time may no longer be around the IAB donor 302 at a certain point in time. In this regard, the process shown in FIG. 9 is suitable for a situation in which the mobile IAB nodes around the IAB donor 302 may dynamically change, since the access restriction release request is periodically notified. That is, according to the process shown in FIG. 9, even under such circumstances, the access restriction lift request can be notified to one or more mobile IAB nodes around the IAB donor 302 with high reliability.

[0086] Next, the processing of each device in the above sequence will be described.

[0087] FIG. 10 is a flow diagram showing the operation of the IAB donor 302 in this embodiment.

[0088] In S1001, the access restriction release request notification determination unit 206 of the IAB donor 302 determines whether to notify an "access restriction release request." In this embodiment, the determination is made based on whether an "access restriction release notification start request" has been received from the external device 801. If it has been received, the process proceeds to S1002, and if not, the process enters a reception standby state.

[0089] In S1002, the message generation unit 207 of the IAB donor 302 generates an "access restriction lift request" message to be notified to the mobile IAB node. The generated message is the same as that in S602. The content to be included in the message is determined based on information item 3: "content to be included in the access restriction lift request" included in the notification start request received from the external device 801 in S1001. Once the message is generated, the process proceeds to S1003.

[0090] In S1003, the mobile IAB node is notified of an "access restriction release request." The processing content is the same as in S603. When the notification is completed, the process proceeds to S1004.

[0091] In S1004, the access restriction release request notification determination unit 206 determines whether or not to stop the notification of the "access restriction release request." In this embodiment, the determination is made based on the condition of whether or not an "access restriction release notification stop request" has been received from the external device 801. If it has been received, the process proceeds again to S1001 and repeats the process. If it has not been received, the process proceeds again to S1002 and performs notification processing of the restriction release request.

[0092] The operation of the mobile IAB node is the same as that shown in FIG. 7 in relation to the first embodiment, and the description thereof will be omitted.

[0093] In the second embodiment, a procedure was described in which the IAB donor 302 notifies surrounding mobile IAB nodes of an access restriction lift request based on receiving an "access restriction lift notification start request" from the external device 801. This allows the access restriction to be lifted from outside for an unspecified number of mobile IAB nodes existing in a specific area.

[0094] [Embodiment 3] In the above embodiments, the IAB donor 302 notifies an unspecified number of mobile IAB nodes in the vicinity of the node of the release of access restrictions. However, there may be a use case where the owner of a mobile IAB node wishes to change the access restrictions of only a specific mobile IAB node, such as changing the access restrictions of the mobile IAB node remotely from the UE or server owned by the owner of the mobile IAB node.

[0095] In this embodiment, a method of notifying an access restriction lift request directly from an external device to a mobile IAB node will be described.

[0096] An example of the system configuration in this embodiment is the same as that in FIG. 8, but the external device 801 is replaced with an external device 802. In the case of the use case according to the third embodiment, the external device 802 is a server device or the like that receives an instruction from the owner of the mobile IAB node and transmits a restriction release request to the mobile IAB node. The instruction from the owner of the mobile IAB node is obtained, for example, by publishing an API (Application Programming Interface) of the access restriction release request to an AF (Application Function). The external device 802 and the IAB donor 302 are connected by an NG interface, similar to the external device 801 and the IAB donor 302 according to the second embodiment. A notification from the external device 802 to the mobile IAB node is notified to the mobile IAB node via the IAB donor 302 by a routing protocol such as a BAP message.

[0097] FIG. 11 shows a sequence diagram in this embodiment.

[0098] In S1101, an access restriction lift request is notified to the mobile IAB node from the external device 802. The contents of the access restriction lift request are the same as the message notified to the mobile IAB node by the IAB donor 302 in the first and second embodiments. However, the access restriction lift request may be transmitted to a specific mobile IAB node by unicast.

[0099] In this case, include "Start of access restriction release" in information item 1: request content, and "unlimited" in information item 2: period. This ensures that the setting will continue until the owner requests "stop of access restriction release." The mobile IAB node that received the release request releases the access restriction in S1102.

[0100] In S1103, the external device notifies the mobile IAB node of a request to stop the access restriction release. The message is the same as the message in S1101. The contents of the message include information item 1: "Stop access restriction release" in the change content, and information item 2: "Unlimited" in the period. The mobile IAB node that received the request to stop the release stops the access restriction release in S1104.

[0101] The flow diagram showing the operation of the mobile IAB node in this embodiment is similar to that shown in Fig. 7 above in relation to embodiment 1. The description will be omitted.

[0102] In the third embodiment, a procedure has been described in which an external device notifies a specific mobile IAB node of an "access restriction release request." This allows an external device to release access restriction on a specific mobile IAB node.

[0103] [Embodiment 4] In the above-mentioned first and second embodiments, an access restriction lift request is notified to all of the unspecified number of mobile IAB nodes present in the cell of the IAB donor 302. However, when the area to be lifted is limited (for example, when it is relatively small), the lift request is notified to more mobile IAB nodes than necessary. In this embodiment, a method for limiting the area to be lifted is described. As an example of limiting the area, a method for issuing a restriction lift request to an area limited to the vicinity of a UE in a state where there is no base station to which the UE can connect, as described in the first embodiment, is described.

[0104] FIG. 12 is a diagram showing an example of a system configuration in this embodiment.

[0105] In the example shown in FIG. 12, a restriction release request area 1200 is added to the system configuration of the first embodiment shown in FIG. 3. The restriction release request area 1200 is an area set to surround the UE 301 in a state where there is no base station to which the access restriction can be released. The area in which the access restriction is released can be limited by releasing the access restriction only for the mobile IAB nodes existing near this area. The information on this area is generated by the IAB donor 302. Based on the location information of the UE notified by the UE, the range is set so as to include all UEs in a state where there is no base station to which the access restriction can be released, and the generated range information is notified to the mobile IAB nodes 303 and 304. The mobile IAB node that receives the range information compares its own location with the range information and determines whether or not to release the access restriction. In this way, the area in which the access restriction is released can be limited.

[0106] Next, the sequence of this embodiment will be described with reference to FIG.

[0107] FIG. 13 shows a sequence diagram in this embodiment.

[0108] S401 and S402 are similar to those in FIG. 4 of the above-mentioned first embodiment, and therefore the description thereof will be omitted.

[0109] In S403A, UE301 notifies IAB donor 302 that "there is no base station to which it can connect". At this time, its own location information is included in the message. The notification method does not use the format of the RRC Setup Request as in the first embodiment. In this case, a new message format in which the current UE location information is added to the RRC Setup Request is used. In this embodiment, the IAB donor 302 specifies the location of UE301 based on the message notified by UE301. However, the notification may not include location information, and IAB donor 302 may specify the location of the UE based on information such as the signal strength of UE301.

[0110] The IAB donor 302 that receives the notification from the UE 301 sets the range to include all UEs 301 that are not able to connect to a base station, based on the location information of the UE 301. When the IAB donor 302 receives another notification from the same UE 301, the IAB donor 302 updates the location information of the UE 301 and sets the range information.

[0111] In S404A, an access restriction lift request is notified to the mobile IAB node. The previously set range information is included in this request. The notification method is the same as in the first embodiment.

[0112] The mobile IAB node that has received the access restriction release request determines whether to release the access restriction, and if it is determined that the restriction should be released, the mobile IAB node releases the access restriction in S405. The determination of whether to release the access restriction is performed using the received range information in addition to the presence or absence of the owner's permission in the first embodiment. For example, if the mobile IAB node's own location is included in the area of ​​the range information, the mobile IAB node determines that the access restriction should be released. The timing of the determination may be when the restriction release request is received, or the received range information may be temporarily stored and the determination may be made again when the mobile IAB node moves to the area included in the range information. The determination conditions may include the mobile IAB node's own radio wave performance, moving speed, expected stay time in the range, and the like. When the mobile IAB node releases the access restriction, the UE becomes able to detect the mobile IAB node, and starts connection processing in the same manner as in embodiment 1. Since steps S406 to S408 are the same as those in FIG. 4 of embodiment 1 described above, a description thereof will be omitted.

[0113] The operation of each device will be described below. It is basically the same as in the first embodiment.

[0114] Fig. 14 is a flow diagram showing the operation of the UE in this embodiment. Since steps S501 to S503 are similar to those in Fig. 5 of the first embodiment, the description thereof will be omitted.

[0115] In S504A, the UE notifies the IAB donor 302 that "there is no base station available for connection." At this time, the UE's location information is included in the message.

[0116] FIG. 15 is a flow diagram showing the operation of the IAB donor 302 in this embodiment.

[0117] S601 is similar to that in FIG. 6 of the above-mentioned first embodiment, and therefore the description will be omitted.

[0118] In S602A, the IAB donor 302 generates an "Access Restriction Release Request" message to be notified to the mobile IAB node. At this time, the message includes range information set based on the location information of the UE. Since S603 is the same as FIG. 6 in the above-mentioned embodiment 1, the description will be omitted.

[0119] FIG. 16 is a flow diagram showing the operation of a mobile IAB node in this embodiment.

[0120] S701 and S701 are similar to those in FIG. 7 of the above-mentioned first embodiment, and therefore the description thereof will be omitted.

[0121] In S702 and S702A, the access restriction release determination unit 217 determines whether the conditions for releasing the access restriction are met. In this embodiment, in addition to whether permission to release the access restriction has been set in advance by the owner of the mobile IAB node (S702), the conditions are whether the received range information includes the node's current location (S702A). If the range information includes the node's current location, the process proceeds to S703 and access restriction release is started. If the range information does not include the node's current location, the process returns to S700 in the next processing cycle.

[0122] S703 is similar to that in FIG. 7 of the above-mentioned first embodiment, and therefore the description will be omitted.

[0123] In S704 and S704A, the access restriction release determination unit 217 of the mobile IAB node determines whether the conditions for resuming access restriction are met. In this embodiment, in addition to whether a certain period of time has passed since the last reception of an "access restriction release request" (S704), the conditions are whether the current location of the node is included in the last received range information (S704A). If the current location of the node is not included in the range information ("NO" in S704A), the process proceeds to S705, and if not, the process returns to S700 in the next processing cycle.

[0124] S705 is similar to that in FIG. 7 of the above-mentioned first embodiment, and therefore the description will be omitted.

[0125] In the fourth embodiment, a procedure for limiting the range of the mobile IAB for which the access restriction is to be lifted by including range information in the access restriction lift request has been described. This makes it possible to lift the access restriction of a mobile IAB node in a specific area from outside. In this embodiment, the range information is set based on the location information of the UE, but it is also possible to directly specify (set) the range information from outside by including the range information in the notification request for the access restriction lift request from the external device described in the second embodiment or in the message of the access restriction lift request from the external device described in the third embodiment.

[0126] In this embodiment, the size of the area indicated by the range information may be constant or variable. For example, the area indicated by the range information may be dynamically changed to cover an area where UEs are located at a relatively high density. The area indicated by the range information may be changed depending on the presence or absence of an event, the time period, the season, etc.

[0127] Although each embodiment has been described above in detail, the present invention is not limited to the specific embodiment, and various modifications and changes are possible within the scope of the claims. In addition, it is also possible to combine all or a plurality of the components of the above-described embodiments.

[0128] For example, in the above-described embodiment, the state related to the access restriction in the mobile IAB node is two types, a state in which the restriction is set and a state in which the restriction is (completely) released, but is not limited thereto. For example, the state related to the access restriction in the mobile IAB node may have three types, a state in which the restriction is set, a state in which the restriction is partially released, and a state in which the restriction is released. In this case, in the first embodiment (as in the other embodiments), the IAB donor 302 may transmit a request to the target mobile IAB node to partially release the access restriction. Alternatively, the mobile IAB node may create a state in which the restriction is partially released in response to a request from the IAB donor 302.

[0129] In addition, in the above-described embodiment, a mechanism may be added for giving incentives to mobile IAB nodes that accept access restriction lift requests. For example, incentives (points, etc.) may be given to owners of mobile IAB nodes according to the number of times or time that they accept access restriction lift requests. In this case, an increase in mobile IAB nodes that accept access restriction lift requests can be expected, and communication efficiency can be improved.

[0130] In the third embodiment, a case where the access restriction of the IAB node is changed by remote control from an external device via an IAB donor is exemplified. In addition, the mobile IAB node owner can instruct the mobile IAB node to change the access restriction state by direct wireless communication from his / her UE to the mobile IAB node. In this case, the mobile IAB node and the UE are connected by a wireless communication method such as Bluetooth or the IEEE802.11 standard series. The UE wirelessly connected to the mobile IAB node by a wireless communication method such as Bluetooth or the IEEE802.11 standard series accepts an operation to change the access restriction state via a setting screen (not shown). The UE that detects that the change operation has been accepted transmits an instruction to change the access restriction state to the mobile IAB node. The mobile IAB node that receives the change instruction changes the access restriction state in cooperation with other IAB nodes, IAB donors, etc. according to the change instruction.

[0131] In addition, the following supplementary notes are disclosed regarding the above embodiment.

[0132] [Appendix 1] A control device comprising: a transmitting means for transmitting a request to a mobile IAB node for which an access restriction is set, to request that the access restriction be lifted.

[0133] [Appendix 2] 2. The control device according to claim 1, wherein the transmission means transmits the request when a predetermined condition is satisfied.

[0134] [Appendix 3] The method further includes a first receiving means for receiving a notification including a notification that there is no base station that can be connected from a UE (User Equipment), 3. The control device according to claim 2, wherein the predetermined condition is satisfied when the notification is received.

[0135] [Appendix 4] The control device according to claim 3, wherein the receiving means receives the notification by an RRC message.

[0136] [Appendix 5] The notification includes location information of the UE; The control device according to claim 3 or 4, wherein the transmission means generates range information regarding a location range to which the lifting of the access restriction applies based on the location information, and includes the range information in the request.

[0137] [Appendix 6] Further comprising a second receiving means for receiving a predetermined instruction from an external device, 6. The control device according to claim 2, wherein the predetermined condition is satisfied when the predetermined instruction is received.

[0138] [Appendix 7] The control device according to claim 6, wherein the predetermined instruction is generated when an administrator or owner of the mobile IAB node permits the lifting of the access restriction.

[0139] [Appendix 8] The control device according to any one of appendixes 2 to 5, wherein the predetermined condition is satisfied when a state of an IAB donor of an IAB network related to the mobile IAB node is in a predetermined state.

[0140] [Appendix 9] A control device as described in any one of appendices 1 to 8, wherein the request includes at least one of information regarding the start time of the lifting of the access restriction, information regarding the end time of the lifting of the access restriction if executed, and range information regarding the location range to which the lifting of the access restriction applies.

[0141] [Appendix 10] 10. The control device according to claim 1, wherein the transmission means transmits the request using a Backhaul Adaptation Protocol (BAP), a System Information Block (SIB), or an F1 Application Protocol (F1AP).

[0142] [Appendix 11] The control device according to any one of Supplementary Notes 1 to 10, wherein the transmission means repeatedly transmits the request to one or more unspecified mobile IAB nodes located in the vicinity.

[0143] [Appendix 12] The control device according to any one of claims 1 to 11, provided at an IAB donor of an IAB network associated with the mobile IAB node.

[0144] [Appendix 13] the control device is a control device located outside an IAB network associated with the mobile IAB node; 13. The control device according to any one of claims 1 to 12, wherein the sending means of the control device sends the request via an IAB donor of the IAB network.

[0145] [Appendix 14] A communication device that transmits a notification to an IAB donor of the IAB network that no base station is available for connection.

[0146] [Appendix 15] A processing means for switching a state regarding an access restriction between a first state in which an access restriction is set and a second state in which no access restriction is set or a degree of restriction is looser than that of the first state; an access control means for not accepting a connection request from a restricted UE (User Equipment) in the first state and for accepting a connection request from the restricted UE in the second state; The communication device, wherein the processing means executes switching from the first state to the second state when a first request for lifting access restriction in the first state is received.

[0147] [Appendix 16] 16. The communication device according to claim 15, wherein the processing means, when receiving the first request, determines whether a switching condition from the first state to the second state is met.

[0148] [Appendix 17] 17. The communication device according to claim 15, wherein the processing means, when receiving a second request to stop lifting the access restriction in the second state, executes switching from the second state to the first state.

[0149] [Appendix 18] the first request includes range information regarding a location range to which the removal of the access restriction applies; A determination means for determining whether the own station is located in the location range, 18. The communication device according to any one of appendices 15 to 17, wherein when the processing means receives the first request, and based on a determination result of the determination means, the processing means executes switching from the first state to the second state when the station is located in the location range. [Explanation of symbols]

[0150] 101 Hardware Function Blocks 102 Control section 103 Storage section 104 Wireless Communication Section 105 Radio antenna control unit 106 GPS communication unit 107 GPS antenna control unit 201 IAB Donor Software Functional Blocks 202 Signal transmission unit (an example of a transmission means) 203 Signal receiving unit (an example of the first and second receiving means) 204 Data storage unit 205 Connection control unit (an example of a transmission means) 206 Access restriction release request notification determination unit (an example of a transmission means) 207 Message Creation Unit 211 Software Functional Blocks of Mobile IAB Node 212 Signal transmission unit (an example of a processing means) 213 Signal receiving unit (an example of a processing means) 214 Data storage unit 215 Connection control section 216 Access restriction control unit (processing means, an example of access control means) 217 Access restriction release determination unit (an example of a processing means, an access control means, or a determination means) 301UE 302 IAB Donor (an example of a control device) 303 Mobile IAB Node 304 Mobile IAB Node 801 External device 802 External device (an example of a control device) 1200 Access restriction lift request area

Claims

1. A control device comprising: a transmission means for transmitting a request to a mobile IAB node to which an access restriction is set, for requesting that the access restriction be lifted.

2. The control device according to claim 1 , wherein the transmission means transmits the request when a predetermined condition is satisfied.

3. The method further includes a first receiving means for receiving a notification including a notification that there is no base station that can be connected from a UE (User Equipment), The control device according to claim 2 , wherein the predetermined condition is satisfied when the notification is received.

4. The control device according to claim 3 , wherein the receiving means receives the notification by an RRC message.

5. The notification includes location information of the UE; The control device according to claim 3 , wherein the transmission means generates range information relating to a location range to which the lifting of the access restriction applies based on the location information, and includes the range information in the request.

6. Further comprising a second receiving means for receiving a predetermined instruction from an external device, The control device according to claim 2 , wherein the predetermined condition is satisfied when the predetermined instruction is received.

7. The control device according to claim 6 , wherein the predetermined instruction is generated when an administrator or an owner of the mobile IAB node permits the lifting of the access restriction.

8. The control device according to claim 2 , wherein the predetermined condition is satisfied when a state of an IAB donor of an IAB network related to the mobile IAB node is in a predetermined state.

9. The control device according to claim 1 , wherein the request includes at least one of information regarding the start time of the lifting of the access restriction, information regarding the end time of the lifting of the access restriction if the lifting of the access restriction is executed, and range information regarding the location range to which the lifting of the access restriction applies.

10. The control device according to claim 1 , wherein the transmission means transmits the request using a Backhaul Adaptation Protocol (BAP), a System Information Block (SIB), or an F1 Application Protocol (F1AP).

11. The control device according to claim 1 , wherein the transmission means repeatedly transmits the request to one or more unspecified mobile IAB nodes located in the vicinity.

12. The control device of claim 1 , provided at an IAB donor of an IAB network associated with the mobile IAB node.

13. the control device is a control device located outside an IAB network associated with the mobile IAB node, The control device of claim 1 , wherein the transmitting means of the control device transmits the request via an IAB donor of the IAB network.

14. A communication device that transmits a notification to an IAB donor of an IAB network that there is no base station available for connection.

15. a processing means for switching a state regarding an access restriction between a first state in which an access restriction is set and a second state in which no access restriction is set or a degree of restriction is looser than that of the first state; an access control means for not accepting a connection request from a restricted UE (User Equipment) in the first state and for accepting a connection request from the restricted UE in the second state; The processing means executes switching from the first state to the second state when a first request for lifting access restriction in the first state is received.

16. The communication device according to claim 15 , wherein the processing means, when receiving the first request, determines whether a condition for switching from the first state to the second state is met.

17. The communication device according to claim 15 , wherein the processing means executes switching from the second state to the first state when a second request for stopping the lifting of the access restriction is received in the second state.

18. the first request includes range information regarding a location range to which the removal of the access restriction applies; A determination means for determining whether the own station is located in the location range, 18. The communication device according to claim 15, wherein when the processing means receives the first request, the processing means executes switching from the first state to the second state when the station is located in the location range based on a determination result of the determination means.

19. A control method for controlling communication, comprising: A control method comprising the step of transmitting a request to a mobile IAB node having an access restriction set thereon to request that the access restriction be lifted.

20. On the computer, A program for executing a step of transmitting a request to a mobile IAB node for which an access restriction is set, requesting that the access restriction be lifted.

21. A control method for controlling communication, comprising: a switching step of switching a state related to an access restriction between a first state in which an access restriction is set and a second state in which no access restriction is set or a degree of restriction is looser than that of the first state; not accepting a connection request from a restricted User Equipment (UE) in the first state, and accepting a connection request from the restricted User Equipment (UE) in the second state; A control method characterized in that, in the switching process, switching from the first state to the second state is executed when a first request to lift access restriction in the first state is received.

22. On the computer, a switching step of switching a state related to an access restriction between a first state in which an access restriction is set and a second state in which no access restriction is set or a degree of restriction is looser than that of the first state; A program for executing a step of not accepting a connection request from a restricted UE (User Equipment) in the first state and accepting a connection request from the restricted UE in the second state, A program characterized in that, in the switching process, switching from the first state to the second state is executed when a first request to release access restriction in the first state is received.

Citation Information

Patent Citations

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

    JP2019534625A