Control device, communication device, control method, and program
The control device and method address the lack of convenient access restriction switching in IAB technology by using protocols to dynamically manage mobile IAB nodes, enhancing network flexibility and congestion management.
Patent Information
- Application Number
- PCT/JP2024/015512
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-09
- Filing Date
- 2024-04-19
- Publication Date
- 2024-11-14
AI Technical Summary
Current specifications for IAB technology do not provide a convenient mechanism for users and carriers to switch access restrictions on mobile IAB nodes, which are essential for flexible network expansion and congestion management in mobile communication scenarios.
A control device and method that includes a transmitting means to request lifting of access restrictions on mobile IAB nodes, using protocols like BAP and RRC, allowing dynamic switching between access restriction modes to facilitate network expansion and congestion alleviation.
Enables convenient switching of access restrictions on mobile IAB nodes, improving network flexibility and congestion management by allowing temporary lifting of restrictions to expand coverage and alleviate network congestion.
Smart Images

Figure JP2024015512_14112024_PF_FP_ABST
Abstract
Description
Control device, communication device, control method, and program
[0001] The present disclosure relates to a control device, a communication device, a control method, and a program.
[0002] The 3rd Generation Partnership Project (3GPP) (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), 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, via millimeter wave communications. Furthermore, IAB nodes can form communication links with multiple other IAB nodes, forming 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 the 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 studies 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.
[0009] Special Publication No. 2019-534625
[0010] An on-board relay is intended to be equipped with functionality equivalent to an IAB node in a moving vehicle such as a car or train. Due to its characteristic of being a moving IAB node, an on-board relay is also called a mobile IAB or mobile IAB node. To actually operate such a mobile IAB node, 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 for expanding the coverage area of the public network and easing congestion in the public network.
[0012] In addition, the mobile IAB node is expected to play a role in restricting access by limiting the UEs that can connect to certain related parties, such as the owner of a vehicle or their family, and to be used as an in-vehicle broadband line for personal use.
[0013] One possible use case is to enable a mobile IAB node to switch its operating mode between the former role and the latter role. A specific example will be described. For example, if a mobile IAB node that operates as a personal broadband line with access restrictions is temporarily allowed to remove the access restrictions and be used as a public network, it is thought that congestion on the public network can be flexibly alleviated.
[0014] However, there is a problem in that no mechanism has been devised that enables switching of access restrictions in 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-mentioned problems, and an object of one aspect of the present invention is to provide a switching mechanism that is highly convenient for users and telecommunications carriers.
[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 for which an access restriction has been set, requesting that the access restriction be lifted.
[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.
[0018] 1 is a hardware functional block diagram of an IAB donor and a mobile IAB node according to the present invention. FIG. 2 is a software functional block diagram of an IAB donor according to the present invention. FIG. 3 is a software functional block diagram of a mobile IAB node according to the present invention. FIG. 4 is a system configuration diagram according to embodiment 1. FIG. 5 is a sequence diagram according to embodiment 1. FIG. 6 is a flow diagram showing the operation of a UE according to embodiment 1. FIG. 7 is a flow diagram showing the operation of an IAB donor according to embodiment 1. FIG. 8 is a flow diagram showing the operation of a mobile IAB node according to the present invention. FIG. 9 is a system configuration diagram according to embodiment 2. FIG. 10 is a sequence diagram according to embodiment 2. FIG. 11 is a flow diagram showing the operation of an IAB donor according to embodiment 2. FIG. 12 is a sequence diagram according to embodiment 3. FIG. 13 is a system configuration diagram according to embodiment 4. FIG. 14 is a sequence diagram according to embodiment 4. FIG. 15 is a flow diagram showing the operation of a UE according to embodiment 4. FIG. 16 is a flow diagram showing the operation of an IAB donor according to the present embodiment. FIG. 17 is a flow diagram showing the operation of a mobile IAB node according to the present embodiment.
[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 while Fig. 1 is a hardware functional block diagram of an IAB donor, 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 an MPU, and controls the entire communication device by executing a control program read into the RAM, which is the storage unit 103. 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 FPGA. Note that ASIC is an abbreviation for Application Specific Integrated Circuit. FPGA is an abbreviation for Field Programmable Gate Array. Furthermore, the processes described in the flowcharts below can also be realized by cooperation between a hardware circuit and a processor, such as a CPU or an MPU.
[0023] The storage unit 103 stores the control program executed by the control unit 102 and various information such as cell IDs 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 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 102, and application software. The auxiliary storage unit is, for example, a hard disk drive (HDD) or a solid state drive (SSD), and may store data related to application software, etc. For example, the control program stored in the non-volatile storage area is expanded into RAM (Random Access Memory) and executed by a processor constituting the control unit 102. In this way, 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 conform to the 3GPP (registered trademark) standard.
[0025] The radio antenna control unit 105 controls the antenna used for the radio communication performed by the radio 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 function 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 UEs and external devices.
[0032] The data storage unit 204 controls and manages the storage unit 103, which is the entity, and stores and holds the software itself, cell information, information on UEs and mobile IAB nodes connected to the IAB donor, etc. In addition, 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 determination is made to notify the mobile IAB node of the release request on the condition that a notification that there is no connectable base station has been received from the UE and / or a request to notify the release request has been received from an external device.
[0034] The access restriction release request notification determination unit 206 may also add the status of its own station (IAB donor) to its determination criteria. For example, when it receives a notification from a UE that there are no base stations available for connection, if the number of connectable devices (the number of UEs that can connect to it) has not reached its upper limit, it may determine not to notify the mobile IAB node of a release request. It may also detect that the number of connected devices frequently reaches its upper limit or that communication quality is poor, such as a decrease in throughput between itself and the UE, and determine to notify the mobile IAB node of a release request.
[0035] The message generation unit 207 generates a message requesting the lifting of access restrictions to be sent 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, only specific UEs are permitted to access, and when the access restriction is disabled, all UEs are permitted to access.
[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 condition for release may be permission from the owner of the mobile IAB node to release the access restriction. A response to the release request may be set in advance, or the owner's UE or the like may confirm whether or not to allow the release 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 whether a certain period of time has passed since the last time a request to release the access restriction was received, whether the owner has instructed the resumption of the access restriction, etc.
[0042] FIG. 3 is a diagram showing an example of a system configuration according to this embodiment.
[0043] In the mobile communication system, there is an IAB donor 302 connected to a CN (Core Network), and in its 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 UE 301 does not have access rights to mobile IAB nodes 303 and 304. In this embodiment, access restriction of mobile IAB nodes is assumed to use the CAG (Closed Access Group) function. The CAG function is one of the functions for non-public networks defined by 3GPP (registered trademark). A non-public network is also called a Non-Public Network, and hereinafter may be abbreviated as NPN. Specifically, the CAG function is a function by which base stations constituting an NPN control the access rights of UEs. The base station broadcasts a CAG ID, which is an identification ID of the NPN, and the UE that receives it compares it with a list of accessible CAGs stored within itself to confirm whether it has access rights. If it does not have access rights, that base station is excluded from the connection processing. In this situation, the only base station that UE 301 can detect is IAB donor 302, and since IAB donor 302 cannot be connected to due to the upper limit on the number of connections, UE 301 is in a state where "there is no base station that can be connected to."
[0046] In this 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 referred to as 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 UE 301 to connect because its own number of connections has reached its upper limit, and notifies the IAB donor 302 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 of the base stations that it can detect, and determines that "there are no base stations available for connection."
[0049] In S403, UE 301 notifies IAB donor 302 that "there is no base station available for connection." If there are multiple detectable base stations, the UE 301 notifies the base station with the strongest radio wave strength. In this embodiment, only IAB donor 302 is notified, but multiple base stations may be notified. As with the connection request, the notification method uses the RRC (Radio Resource Control) protocol. The RRC protocol is a layer 3 protocol used for communication between UEs and base stations in LTE and 5G systems. For 5G, it is specified in TS 38.331. The notification that "there is no base station available for connection" is notified using the message format of a connection request (RRC Setup Request). The RRC Setup Request has a field for entering the connection reason, "EstablishmentCase." By adding a new definition of "there is no base station available to connect" and including it in this item, a UE before connecting to a cellular network (RRC IDLE) can notify a base station that "there is no base station available to connect." In this embodiment, RRC Setup Request is used, but a new message format may also 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, two types of notification methods are possible. 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, since the notification is sent to the mobile IAB node connected to itself, the destination is clear. For example, notification can be sent using a BAP (Backhaul Adaptation Protocol) message to the BAP address of the mobile IAB node. A BAP message is a Layer 2 protocol used to route data to IAB nodes in 5G systems defined by 3GPP (registered trademark). BAP is defined in TS 38.340. Note that instead of a BAP message, notification to the mobile IAB node may be sent using F1AP (F1 Application Protocol). F1AP is defined in TS 38.473. The message to be notified here includes the following information items: Information Item 1: Request Content Information Item 2: Period The request content of Information Item 1 includes time information such as "start of access restriction release" and "stop of access restriction release." Although not mentioned in this embodiment, by including "start access restriction" and "stop access restriction," it becomes possible to externally enable access restriction on a mobile IAB node. The period in information item 2 includes the validity period of the change request. This is used by the mobile IAB in response to a request to remove access restriction to determine when to resume access restriction. If the period is short, the mobile IAB node can resume access restriction after the validity period has elapsed without waiting for a request to "stop removing access restriction." Note that the mobile IAB node can resume access restriction if it receives a request from the IAB donor to "stop removing access restriction" during this validity period.
[0053] The mobile IAB nodes to be notified by the first method may be a portion 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 a portion of the mobile IAB nodes, the portion may include mobile IAB nodes located near the UE (a UE that cannot connect to a base station).
[0054] In the second method, the notification is sent to a mobile IAB node that is not connected to the UE itself, so the destination is unknown. Therefore, the access control request is notified to surrounding mobile IAB nodes by broadcasting broadcast information to the UE itself. For example, an SIB (System Information Block) is used for the broadcast. As with the first method, the broadcast information in the second method also includes the following information items: Information item 1: Request content Information item 2: Period Steps 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 lifting request determines whether or not to lift the access restriction using a determination means described later, and if it determines to lift the restriction, the mobile IAB node lifts the access restriction in S405.
[0056] When the mobile IAB node releases the access restriction, UE 301 can detect the mobile IAB node, and UE 301 starts connection processing to the detected mobile IAB node. From then on, the UE establishes a connection to the mobile IAB node according to the UE connection establishment procedure described in 3GPP (registered trademark) specification TS 38.300.
[0057] In S406, UE 301 notifies the mobile IAB node of a connection request (RRC Setup Request). If connection is possible, in S407, the mobile IAB node notifies UE 301 of RRC Setup. This message includes cell configuration information and the like required for connection processing. Finally, in S408, UE 301 notifies the mobile IAB node of connection completion (RRC Setup Complete), and the connection processing is completed.
[0058] Next, the processing of each device in the above sequence will be explained using a flow chart.
[0059] FIG. 5 is a flow diagram showing the 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 are any candidate base stations for connection in the vicinity based on information broadcast by the base stations. If there are candidate base stations for connection, the UE proceeds to S502.
[0062] In S502, the UE performs connection processing to the candidate base stations in order of priority.
[0063] In S503, the UE checks the result of the connection process. If connection to all of the candidate base stations has failed, the process proceeds to S504. If connection to any of the base stations has been successful, the process ends.
[0064] In S504, the connection candidate base stations are notified that "there is no base station available for connection." The notification method is as explained in S403 of Fig. 4. Once the notification is complete, 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 lift request notification determination unit 206 of the IAB donor 302 determines whether to notify an "access restriction lift request." In this embodiment, the determination is made based on whether a notification that "there is no connectable base station" has been received from the UE. If a notification has been received, the process proceeds to S602.
[0067] In S602, an "access restriction release request" message is generated to be sent to the mobile IAB node. The generated message is as described in S404 of FIG. 4 . A BAP message is generated for the mobile IAB node connecting to itself, and broadcast information is generated for surrounding mobile IAB nodes. Note that if there are multiple mobile IAB nodes connecting to itself, a BAP message may be generated for some or all of them. In this embodiment, both a BAP message and broadcast information are generated, but only one of them may be generated. When a UE issues an access restriction release request to the mobile IAB based on a notification that "there is no connectable base station," the message contains the following information: Information Item 1: Request Content "Start of Access Restriction Release" and Information Item 2: Duration "Short Period." This is because the UE rescue is a temporary measure. In addition, a mobile IAB node can move outside the cell range of the IAB donor 302, and therefore may not necessarily receive the "access restriction suspension 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 generated "access restriction release request" message is notified to the mobile IAB node. Once 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, the process proceeds to S704, and if access restriction release is not in progress, the process proceeds 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 releasing the access restriction are met. In this embodiment, the determination is made based on whether permission to release the access restriction has been set in advance by the owner of the mobile IAB node. The permission setting for releasing the access restriction is stored in the data storage unit 214. If the conditions are met, the process proceeds to S703. If the conditions are not met, the process returns to S700 in the next processing cycle.
[0073] In S703, if access restriction is in effect, the access restriction control unit 216 of the mobile IAB node starts to remove the access restriction. 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 access restriction are met. In this embodiment, this determination is 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 an upper limit previously set by the owner has passed, it is determined that the conditions for resuming access restriction are met. In this case, the process proceeds to S705, where the access restriction release is stopped and the access restriction is resumed (S705). If it is determined that the conditions for resuming 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 a request to lift access restriction based on receiving a notification from the UE that "there is no base station available for connection." This makes it possible to externally lift the access restriction on the mobile IAB node, thereby rescuing the UE that cannot connect.
[0076] In the first embodiment, the IAB donor 302 notifies surrounding mobile IAB nodes of a request to lift access restriction based on the receipt of a notification from a UE that "there is no base station available for connection." In the present embodiment, a procedure for notifying surrounding mobile IAB nodes of a request to lift access restriction 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 alleviation of communication congestion by a telecommunications carrier.
[0078] When an event is held in a specific area and communication congestion is expected, the communication carrier identifies the base station (IAB donor) set up in that area based on the installation information of the base stations it manages. Then, it instructs the identified base station to notify surrounding mobile IAB nodes of a request to lift access restrictions. By doing so, it is possible to temporarily increase the number of base stations in the specific area and increase the number of UEs that can connect.
[0079] FIG. 8 is a diagram showing an example of a system configuration according to this embodiment.
[0080] There is an IAB donor 302 installed in a specific area, and in its vicinity there are mobile IAB nodes 303 and 304. Mobile IAB nodes 303 and 304 are the same as those in embodiment 1. An external device 801 can communicate with the IAB donor 302 via a mobile communication system.
[0081] In this situation, a procedure for releasing the access restriction on mobile IAB node 303 and mobile IAB node 304 from external device 801 via 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 removal.
[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 the 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. Application layer messages via the NG interface are specified in TS38.413. The access restriction release start request and the access restriction release stop request (described later) in this embodiment use newly defined messages in accordance with this specification. These requests use the same message and include the following information items: Information item 1: Request content; Information item 2: Period; Information item 3: Content to be included in the access restriction release request; Information item 1: 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 lift request includes information regarding the content to be included in the access restriction lift request message that the IAB donor 302, which has received the notification start request, will notify surrounding mobile IAB nodes. In this embodiment, Information Item 1: Request Content includes "Start of notification," Information Item 2: Period includes "Infinite," and Information Item 3: Content to be included in the access restriction lift request includes "Request Content (Start of access restriction lift), Period (Short period)." In this embodiment, the external device 801 and the IAB donor 302 are fixed devices and are permanently capable of communication. Therefore, in order to reduce the amount of communication between the external device 801 and the IAB donor 302, Information Item 2: Period is set to "Infinite," so that the notification start request only needs to be sent once. Upon receiving the notification start request, the IAB donor 302 notifies surrounding mobile IAB nodes of the access restriction lift request. The notification means and content are the same as those in the first embodiment. A description thereof will be omitted. The mobile IAB node that receives the access restriction lift request also lifts the access restriction in the same manner as in embodiment 1. The explanation will be omitted.The IAB donor 302 continues to periodically notify the request to lift the access restriction, and in S902 stops the notification of the access restriction lift request upon receiving a request to stop the notification of the access restriction lift from the external device 801. 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 surrounding mobile IAB nodes of a request to remove access restriction. In this case, the access restriction removal request may be broadcast to surrounding mobile IAB nodes rather than targeted at a specific mobile IAB node. In the example shown in FIG. 9 , even after a mobile IAB node removes access restriction, it continues to periodically notify the mobile IAB node of the access restriction removal request until S902. Note that the mobile IAB nodes located around the IAB donor 302 may change during the period from S901 to S902. For example, a mobile IAB node located around the IAB donor 302 at a certain point in time may no longer be located around the IAB donor 302 at a later point in time. In this regard, the process shown in FIG. 9 , in which the access restriction removal request is periodically notified, is suitable for situations in which the mobile IAB nodes located around the IAB donor 302 may dynamically change. 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; 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 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. Once the notification is complete, 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, this 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 to S1001 again and repeats the process. If it has not been received, the process proceeds to S1002 again 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 therefore a 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 IAB donor 302 to lift the access restriction from an external device to an unspecified number of mobile IAB nodes present in a specific area.
[0094] In the above embodiments, the IAB donor 302 notifies an unspecified number of surrounding mobile IAB nodes 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 when the owner of the mobile IAB node remotely changes the access restrictions of the mobile IAB node from his / her own UE or server.
[0095] In this embodiment, a method will be described in which an external device directly notifies a mobile IAB node of an access restriction release request.
[0096] An example of a system configuration in this embodiment is similar to that shown in FIG. 8 , except that the external device 801 is replaced with an external device 802. In a 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 lift 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) for the access restriction lift request to an AF (Application Function). The external device 802 and the IAB donor 302 are connected via 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 sent to the mobile IAB node via the IAB donor 302 using 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 sent from the external device 802 to the mobile IAB node. The content of the access restriction lift request is the same as the message sent by the IAB donor 302 to the mobile IAB node in embodiments 1 and 2. However, the access restriction lift request may be sent by unicast to a specific mobile IAB node.
[0099] In this case, "Start of access restriction release" is included in information item 1: request content, and "unlimited" is included in information item 2: period. This ensures that the setting will continue until the owner requests "stop of access restriction release." Upon receiving the release request, the mobile IAB node 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 message includes information item 1: "Stop access restriction release" in the change content, and information item 2: "Indefinite" in the period. Upon receiving the release stop request, the mobile IAB node stops the access restriction release in S1104.
[0101] The flow diagram showing the operation of the mobile IAB node in this embodiment is the same as that shown in Figure 7 described above in relation to embodiment 1, and a detailed 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 lift request." This allows the access restriction on a specific mobile IAB node to be lifted from an external device.
[0103] [Embodiment 4] In the above-described embodiments 1 and 2, an access restriction release request is notified to all of the unspecified number of mobile IAB nodes present in the cell of the IAB donor 302. However, if the area to be released is limited (for example, relatively small), the release request is notified to more mobile IAB nodes than necessary. In this embodiment, a method for limiting the area to be released is described. As an example of limiting the area, a method for issuing a restriction release request to an area limited to the vicinity of a UE in a state where there is no base station that can be connected, as described in embodiment 1, is described.
[0104] FIG. 12 is a diagram showing an example of a system configuration according to this embodiment.
[0105] In the example shown in FIG. 12 , a restriction lift request area 1200 is added to the system configuration of the first embodiment shown in FIG. 3 . The restriction lift request area 1200 is an area set to surround the UE 301 that has no connectable base stations. By lifting the access restriction only for mobile IAB nodes that are located near this area, the area in which the access restriction is lifted can be limited. This area information is generated by the IAB donor 302. Based on the UE location information notified by the UE, the range is set to include all UEs that have no connectable base stations, and the generated range information is notified to the mobile IAB nodes 303 and 304. Upon receiving the range information, the mobile IAB node compares its own location with the range information and determines whether to lift the access restriction. In this way, the area in which the access restriction is lifted 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 first embodiment described above, and therefore the description thereof will be omitted.
[0109] In S403A, UE 301 notifies IAB donor 302 that "there is no base station available for connection." At this time, its own location information is included in the message. The notification method does not use the RRC Setup Request format as in embodiment 1. In this case, a new message format is used in which the current UE location information is added to the RRC Setup Request. In this embodiment, a description will be given of IAB donor 302 specifying the location of UE 301 using the message notified by UE 301. However, the notification may not include location information, and IAB donor 302 may specify the UE location from information such as the signal strength of UE 301.
[0110] Upon receiving a notification from UE 301, IAB donor 302 sets a range based on the location information of UE 301 to include all UEs 301 that are not able to connect to a base station. If another notification is received from the same UE 301, IAB donor 302 updates the location information of UE 301 and sets the range information.
[0111] In S404A, an access restriction lift request is sent 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 removal request determines whether to remove the access restriction, and if it determines to remove the restriction, the mobile IAB node removes the access restriction in S405. The determination of whether to remove the access restriction is made using the received range information in addition to whether the owner has given permission as in the first embodiment. For example, if its own location is included in the area of the range information, it determines to remove the access restriction. The timing of the determination may be determined when the restriction removal 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 into the area included in the range information. The determination conditions may include its own radio wave performance, moving speed, expected stay time in the range, etc.
[0113] When the mobile IAB node releases the access restriction, the UE can detect the mobile IAB node and starts connection processing in the same manner as in embodiment 1. Steps S406 to S408 are the same as those in FIG. 4 of embodiment 1 described above, and therefore description thereof will be omitted.
[0114] The operation of each device will be described below, which is basically the same as in the first embodiment.
[0115] 14 is a flow diagram showing the operation of the UE in this embodiment. Steps S501 to S503 are the same as those in FIG. 5 of the first embodiment, and therefore the description thereof will be omitted.
[0116] In S504A, the UE notifies the IAB donor 302 that there is no base station available for connection. At this time, the UE notifies the IAB donor 302 by including the location information of the UE in the message.
[0117] FIG. 15 is a flow diagram showing the operation of the IAB donor 302 in this embodiment.
[0118] S601 is the same as in FIG. 6 of the first embodiment described above, and therefore a description thereof will be omitted.
[0119] In S602A, the IAB donor 302 generates an "Access Restriction Release Request" message to be sent to the mobile IAB node. The message includes range information set based on the UE's location information. S603 is the same as in FIG. 6 of the first embodiment, and therefore a detailed description is omitted.
[0120] FIG. 16 is a flow diagram showing the operation of the mobile IAB node in this embodiment.
[0121] S701 and S702 are similar to those in FIG. 7 of the first embodiment described above, and therefore description thereof will be omitted.
[0122] 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 also include 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 initiated. If the range information does not include the node's current location, the process returns to S700 in the next processing cycle.
[0123] S703 is the same as in FIG. 7 of the first embodiment described above, and therefore a description thereof will be omitted.
[0124] 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 time an "access restriction release request" was received (S704), the conditions also include whether the node's current location is included in the last received range information (S704A). If the node's current location is not included in the range information ("NO" in S704A), the process proceeds to S705; if not, the process returns to S700 in the next processing cycle.
[0125] S705 is the same as in FIG. 7 of the first embodiment described above, and therefore a description thereof will be omitted.
[0126] In the fourth embodiment, a procedure for limiting the range of a mobile IAB for which access restriction is to be lifted by including range information in an access restriction lift request has been described. This makes it possible to externally lift the access restriction of a mobile IAB node present in a specific area. In this embodiment, the range information is set based on the location information of the UE. However, by including range information in a notification request for an access restriction lift request from an external device as described in the second embodiment or in a message for an access restriction lift request from an external device as described in the third embodiment, it is also possible to directly specify (set) the range information from externally.
[0127] 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. Furthermore, the area indicated by the range information may change depending on whether an event is taking place, the time of day, the season, etc.
[0128] Although each embodiment has been described in detail above, it is not limited to a specific embodiment, and various modifications and changes are possible within the scope of the claims. It is also possible to combine all or a plurality of components of the above-described embodiments.
[0129] For example, in the above-described embodiment, the access restriction state of a mobile IAB node is limited to two states: a restricted state and a (completely) unrestricted state. However, this is not limiting. For example, the access restriction state of a mobile IAB node may be limited to three states: a restricted state, a partially unrestricted state, and a completely unrestricted state. In this case, in embodiment 1 (as well as other embodiments), the IAB donor 302 may transmit a request to the target mobile IAB node to partially unrestrict the access restriction. Alternatively, the mobile IAB node may establish a partially unrestricted state in response to a request from the IAB donor 302.
[0130] Furthermore, in the above-described embodiment, a mechanism may be added for providing incentives to mobile IAB nodes that accept access restriction lift requests. For example, incentives (such as points) may be provided to the owner of the mobile IAB node depending on the number of times or the length of time that the node accepts access restriction lift requests. In this case, an increase in mobile IAB nodes that accept access restriction lift requests can be expected, leading to improved communication efficiency.
[0131] The third embodiment illustrates a case in which the access restriction of an IAB node is changed by remote operation from an external device via an IAB donor. In addition, a configuration is also possible in which the owner of a mobile IAB node instructs the mobile IAB node to change its access restriction state via direct wireless communication from his or her UE to the mobile IAB node. In this case, the mobile IAB node and the UE are connected via a wireless communication method such as Bluetooth or the IEEE 802.11 standard series. The UE wirelessly connected to the mobile IAB node via a wireless communication method such as Bluetooth or the IEEE 802.11 standard series accepts an operation to change the access restriction state via a setting screen (not shown). The UE, upon detecting 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, upon receiving the change instruction, changes the access restriction state in cooperation with other IAB nodes, IAB donors, etc., in accordance with the change instruction.
[0132] 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.
[0133] This application claims priority based on Japanese Patent Application No. 2023-077247, filed on May 9, 2023, the entire contents of which are incorporated herein by reference.
[0134] 101 Hardware function block 102 Control unit 103 Memory unit 104 Wireless communication unit 105 Wireless antenna control unit 106 GPS communication unit 107 GPS antenna control unit 201 Software function block of IAB donor 202 Signal transmission unit (an example of a transmission means) 203 Signal reception unit (an example of a first or second reception 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 generation unit 211 Software function block of mobile IAB node 212 Signal transmission unit (an example of a processing means) 213 Signal reception unit (an example of a processing means) 214 Data storage unit 215 Connection control unit 216 Access restriction control unit (an example of a processing means, an access control means) 217 Access restriction release determination unit (an example of a processing means, an access control means, a determination means) 301 UE 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 release request area
Claims
1. A control device comprising: a transmission 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.
2. The control device according to claim 1, wherein said transmission means transmits said request when a predetermined condition is satisfied.
3. The control device according to claim 2, further comprising a first receiving means for receiving a notification from a UE (User Equipment) including a notification that there is no base station to which the device can be connected, and the predetermined condition is satisfied when the notification is received.
4. The control device according to claim 3, wherein the first receiving means receives the notification by an RRC message.
5. A control device as described in claim 3 or 4, wherein the notification includes location information of the UE, and the transmitting 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.
6. The control device according to any one of claims 2 to 5, further comprising a second receiving means for receiving a predetermined instruction from an external device, 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 owner of the mobile IAB node permits lifting of the access restriction.
8. The control device according to any one of claims 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.
9. A control device as described in any one of claims 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.
10. The control device according to any one of claims 1 to 9, wherein the transmission means transmits the request using the Backhaul Adaptation Protocol (BAP), the System Information Block (SIB), or the F1 Application Protocol (F1AP).
11. The control device according to any one of claims 1 to 10, wherein the transmission means repeatedly transmits the request to one or more unspecified mobile IAB nodes located in the vicinity.
12. The control device according to any one of claims 1 to 11, wherein the control device functions as an IAB donor for an IAB network associated with the mobile IAB node.
13. The control device according to any one of claims 1 to 11, wherein the control device is a control device located outside an IAB network associated with the mobile IAB node, and the transmitting means of the control device transmits the request via an IAB donor of the IAB network.
14. A communication device comprising a notification means for notifying at least one base station that there is no base station to which a connection can be made.
15. A communications device comprising: a processing means for switching a state regarding access restriction between a first state in which access restriction is set and a second state in which access restriction is not set or the degree of restriction is less severe than that of the first state; and 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 a restricted UE in the second state, wherein the processing means executes switching from the first state to the second state when it receives a first request to lift the access restriction in the first state.
16. The communication device according to claim 15, wherein said processing means, when receiving said first request, determines whether a condition for switching from said first state to said second state is met.
17. The communication device according to claim 15 or 16, 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. A communication device as described in any one of claims 15 to 17, wherein the first request includes range information regarding a location range to which the lifting of the access restriction applies, and further comprising a judgment means for judging whether the local station is located in the location range, and when the processing means receives the first request, performs switching from the first state to the second state if the local station is located in the location range based on a judgment result of the judgment means.
19. A method for controlling communications, comprising the step of transmitting, to a mobile IAB node for which an access restriction has been set, a request to lift the access restriction.
20. A program for causing a computer to execute a step of transmitting a request to a mobile IAB node for which an access restriction has been set, requesting that the access restriction be lifted.
21. A control method for controlling communications, comprising: a switching step of switching a state related to access restriction between a first state in which access restriction is set and a second state in which access restriction is not set or the degree of restriction is less severe than that of the first state; and a step of not accepting a connection request from a UE (User Equipment) that is subject to restriction in the first state, and accepting a connection request from a UE that is subject to restriction in the second state, wherein in the switching step, when a first request for lifting the access restriction is received in the first state, switching from the first state to the second state is executed.
22. A program for causing a computer to execute the following steps: a switching step of switching a state regarding access restriction between a first state in which access restriction is set and a second state in which access restriction is not set or the degree of restriction is less severe than that of the first state; and a step of not accepting a connection request from a UE (User Equipment) that is subject to restriction in the first state, and accepting a connection request from a UE that is subject to restriction in the second state, wherein in the switching step, when a first request for lifting the access restriction is received in the first state, switching from the first state to the second state is executed.
Citation Information
Patent Citations
Communication system, radio base station, network device and communication control method
JP2011234059A
Mobile communication relief method, monitoring system for mobile communication, base station, and terminal device
JP2012191550A
