Communication device, control method, and program

Abstract

Disclosed is a communication device characterized by comprising: a first acquisition means for acquiring type information which enables determining whether another communication device is a movable first-type integrated access and backhaul (IAB) node; a generation or acquisition means for generating or acquiring area information regarding an area where the first-type IAB node can provide a service; a determination means for determining whether to notify the other communication device of the area information, on the basis of the type information of the other communication device; and a transmission means for transmitting the area information to the other communication device on the basis of the determination result of the determination means.

Description

Communication device, control method, and program

[0001] The present disclosure relates to 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, repeaters called IAB nodes relay communications from IAB donors, which are base stations, using millimeter-wave communications. By using IAB technology, it is possible to expand area coverage at a lower cost than with conventional wired communications such as optical fiber.

[0005] Up until now, 3GPP (registered trademark) has been formulating specifications for fixed base stations (IAB nodes that do not move) up to Rel-17.

[0006] Currently, 3GPP (registered trademark) is planning to actively discuss Vehicle Mounted Relay, which will be a use case in the next Rel-18, and Mobile IAB Nodes as specifications for realizing this use case. Mobile IAB Nodes are also known as Mobile Base Station Relays (MBSRs), and will be referred to as MBSRs hereinafter.

[0007] Here, it is likely that various requirements will emerge that cannot be met by the specifications that have been discussed so far, which are based on fixed base stations.

[0008] One of the discussion topics is "Mobile Base Station Relay Authorization and Configuration," which considers the use of MBSRs temporarily installed in vehicles to act as relays and provide services to UEs in urban environments or during large-scale events in designated areas to achieve special coverage and connectivity.

[0009] The range in which the MBSR can operate as a repeater is called an authorized area, which is managed by a CN (Core Network). When the MBSR is in the authorized area, the MBSR provides services to nearby UEs, and when the MBSR moves out of the authorized area, the MBSR stops providing services.

[0010] In this regard, a technology is known that provides services by utilizing location information and movement information of mobile nodes (Patent Document 2).

[0011] Special table 2019-534625 publication Special table 2009-501453 publication

[0012] At present, there is no standard for the definition of allowed area information and the means for notifying the MBSR of the allowed area information. If the MBSR can be notified of the allowed area information, the MBSR can compare its own location information with the allowed area information and determine whether it can provide services.

[0013] The present invention has been made in consideration of at least one of the above problems, and an object of one aspect of the present invention is to provide a mechanism for efficiently notifying an MBSR of permitted area information.

[0014] A communication device according to one aspect of the present invention comprises: a first acquisition means for acquiring type information that can determine whether another communication device is a first type IAB (Integrated Access and Backhaul) node that involves movement; a generation or acquisition means for generating or acquiring area information regarding an area in which the first type IAB node can provide service; a determination means for determining whether to notify the other communication device of the area information based on the type information of the other communication device; and a transmission means for transmitting the area information to the other communication device based on the determination result of the determination means.

[0015] According to one aspect of the present invention, it is possible to provide a mechanism that can efficiently notify MBSR of permitted area information.

[0016] FIG. 1 is a hardware block diagram constituting a base station. FIG. 2 is a software functional block diagram of a base station in the present embodiment 1. FIG. 3 is an example diagram of a communication allowed area format in the present embodiment 1 (part 1). FIG. 4 is an example diagram of a communication allowed area format in the present embodiment 1 (part 3). FIG. 5 is an example diagram of a communication allowed area format in the present embodiment 1 (part 4). FIG. 6 is a flowchart of an initial connection process of a base station in the present embodiment 1. FIG. 7 is a software functional block diagram of a base station in the present embodiment 2. FIG. 8 is a sequence at the time of initial connection in the present embodiment 2. FIG. 9 is a flowchart of an initial connection process of a base station in the present embodiment 2. FIG. 10 is a sequence at the time of general connection reconfiguration in the 3GPP (registered trademark) standard. FIG. 11 is a flowchart of a connection reconfiguration process of a base station in the present embodiment 3.

[0017] [First embodiment] Each embodiment will be described in detail below with reference to the accompanying drawings. In the following description, the "number ***" in TS*** represents the number of the Technical Specification in the 3GPP (registered trademark) standard.

[0018] Figure 1 is a block diagram showing an example of the hardware configuration of an IAB donor (hereinafter also referred to as "gNB"), which is a base station, according to this embodiment.

[0019] The hardware configuration 101 includes a control unit 102 , a storage unit 103 , a wireless communication unit 104 , a communication antenna control unit 105 , a GPS communication unit 106 , and a GPS antenna control unit 107 .

[0020] 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 102, which will be described in the flowcharts below, can also be realized using a hardware circuit, such as an ASIC or an FPGA. Note that ASIC is an abbreviation for Application Specific Integrated Circuit. FPGA is an abbreviation for Field Programmable Gate Array. 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.

[0021] The storage unit 103 stores the control program executed by the control unit 102, as well as various information such as cell information, connected terminal information, IAB routing information, and location 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.

[0022] The wireless communication unit 104 performs cellular network communication such as LTE (Long Term Evolution) conforming to the 3GPP (registered trademark) standard, 5G, etc. Note that although 5G will be described here, the present invention is also applicable to networks other than 5G (for example, 5G Advanced, 6G, etc.).

[0023] The communication antenna control unit 105 controls an antenna (not shown) for wireless communication performed by the wireless communication unit 104 .

[0024] The GPS communication unit 106 receives satellite signals from GPS (Global Positioning System) satellites to acquire current location information including location identification information such as longitude and latitude information, and current time information. The GPS communication unit 106 may have a function to measure (locate) the current location based on the satellite signals. Another GNSS (Global Navigation Satellite System) may be used instead of or in addition to GPS.

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

[0026] FIG. 2 is a block diagram showing an example of the configuration of software functional blocks of a base station that executes the communication control function according to this embodiment.

[0027] The software function 201 includes a signal transmitting unit 202, a signal receiving unit 203, a data storage unit 204, a connection control unit 205, a notification information detecting unit 206, an allowed area information notification determining unit 207, and an allowed area information generating unit 208. The software function 201 also includes a GPS signal receiving unit 209 and a GPS control unit 210.

[0028] The signal transmitting unit 202 and the signal receiving unit 203 perform cellular network communication such as LTE or 5G that conforms to the 3GPP (registered trademark) standard with the terminal device. Note that the control plane signal is received by the signal receiving unit 203. The cellular network communication performed by the signal transmitting unit 202 and the signal receiving unit 203 includes communication of the 5G NR (New Radio) and LTE RAN (Radio Access Network) layers. Furthermore, the cellular network communication performed by the signal transmitting unit 202 and the signal receiving unit 203 may include various communications for providing cellular network communication, such as communication of the RRC (Radio Resource Control) layer, which is an upper layer.

[0029] In this embodiment, when the allowed area information notification determination unit 207 (described later) determines that the opposite communication device (other communication device) should be notified of the allowed area information, the signal transmission unit 202 transmits the allowed area information to the opposite communication device. The method of transmitting the allowed area information will be described later.

[0030] In addition, in this embodiment, the signal receiving unit 203 acquires information that can determine whether the opposing communication device is an IAB node of a type that involves movement. That is, the signal receiving unit 203 acquires information that can determine whether the opposing communication device is an MBSR. Such information is arbitrary and may be, for example, information that explicitly indicates or suggests that the communication device is an MBSR, or information that explicitly indicates or suggests that the communication device is other than an MBSR. In this embodiment, such information is IAB node type information, the details of which will be described later.

[0031] The data storage unit 204 stores and holds the software itself, IAB routing information, information on connected terminals, current time information, location information, travel route information, and the like.

[0032] The connection control unit 205 controls the antenna for wireless communication performed by the wireless communication unit 104 .

[0033] The broadcast information detection unit 206 detects broadcast information from surrounding base stations and MBSRs.

[0034] The permitted area information notification determining unit 207 determines whether or not to notify the opposing communication device of the permitted area information.

[0035] The allowed area information generation unit 208 generates allowed area information to be notified to the opposing communication device and stores it in a predetermined storage area such as the data storage unit 204. This predetermined storage area functions as a storage means for storing the allowed area information. Note that instead of or in addition to generating the allowed area information, the allowed area information generation unit 208 may acquire the allowed area information from an external source and store it in the predetermined storage area. For example, the allowed area information may be generated by the CN, or may be generated by the gNB 300 based on information received from the CN. When generated by the CN, for example, allowed area information related to allowed areas around the own station or allowed area information related to allowed areas closest to the own station may be generated from all the allowed area information managed by the CN. The actual entity of this predetermined storage area may be a storage area in RAM or a storage area in an auxiliary storage unit.

[0036] The GPS signal receiving unit 209 performs communication in accordance with the GPS standard. The GPS control unit 210 controls the antenna for GPS communication performed by the GPS communication unit 106, and calculates the current position and time from the received GPS information. The GPS control unit 210 then outputs information in a format such as NMEA (National Marine Electronics Association)-0183, and stores the current position and time in the data storage unit 204 as necessary.

[0037] Next, a method for notifying permission area information in this embodiment will be described.

[0038] In this first embodiment, a method for notifying allowed area information based on IAB node type information received from an MBSR using a general initial connection sequence in the 3GPP (registered trademark) standard will be described. The IAB node type information and allowed area information are transmitted and received using control plane signals in a 5G system. A specific control plane signal uses an RRC (Radio Resource Control) message. More specifically, an RRCSetupComplete message is used for the IAB node type information, and an RRC Reconfiguration message is used for the allowed area information.

[0039] 3 shows the initial connection sequence of this embodiment based on the general initial connection sequence in the 3GPP (registered trademark) standard. In addition to MBSR, fixed IAB nodes and UEs also connect to the 5G system via the base station (gNB) according to this sequence.

[0040] First, MBSR600 sends an RRCSetupRequest message (S301) to gNB300 as a connection request.

[0041] If gNB300 receives the message and allows MBSR600 to connect, it sends an RRCSetup message (S302) to MBSR600.

[0042] Upon receiving the message, MBSR 600 transmits an RRCSetupComplete message (S303) to gNB 300 as a connection completion notification. At this time, MBSR 600 includes information called Mobile IAB Indication in the RRCSetupComplete message. This information indicates whether or not the MBSR 600 is an MBSR (Mobile IAB) and is scheduled to be standardized in Release 18. In this embodiment, gNB 300 determines whether or not the opposing communication device is an MBSR by checking whether or not this information is included in RRCSetupComplete.

[0043] After the RRC connection between the MBSR and gNB300 is established, the RRC reconfiguration process of MBSR600 is performed.

[0044] The gNB 300 transmits an RRC Reconfiguration message (S304) to the MBSR 600. In this embodiment, if the opposite communication device determines that it is an MBSR, the gNB 300 includes the permitted area information in the RRC Reconfiguration message. Details of the permitted area information will be described later. The MBSR 600 that receives this message performs an RRC reconfiguration process based on the information included in the RRC Reconfiguration message, and determines whether to provide a service to the UE based on the permitted area information and its own location information.

[0045] After the reconfiguration process is completed, the MBSR 600 sends an RRC Reconfiguration Complete message (S305).

[0046] 4A to 4D show various examples of the communication allowed area format 301 included in the RRC Setup message and the RRC Reconfiguration message.

[0047] 4A shows an example of a communication allowed area format 401. The communication allowed area format 401 is a basic format that indicates a communication allowed area in which MBSR can operate.

[0048] This information may be incorporated as a new field into the RRC Reconfiguration message field or the RRC Setup message field specified in TS 38.331. This information is notified to the MBSR.

[0049] The communication permitted area is composed of the permitted area information number and permitted area information.

[0050] The number of permitted area information pieces stores the number of permitted area information pieces included in this message.

[0051] The number of allowed area information stored corresponds to the number of allowed area information, such as allowed area information 1, allowed area information 2, etc. MBSR is capable of providing services within a single or multiple allowed areas indicated by the allowed area information. Note that, although one allowed area information is information relating to one allowed area here, one allowed area information may also be information relating to two or more allowed areas. Furthermore, a unit of allowed area may be a set of physically contiguous areas. Furthermore, allowed areas may be separated according to the difference in any one of the radio parameter information (upper device), radio parameter information (lower device), and validity period information, which will be described later.

[0052] Here, the services provided by the MBSR within the authorized area include, for example, various communication services provided by the IAB node to the UE. In this case, the concept of communication service includes creating a state in which access from the UE can be accepted.

[0053] 4A, the allowed area information format 402 is an example of the configuration of allowed area information 1. The same may be true for allowed area information 2, etc.

[0054] The permitted area information 1 includes area information, wireless parameter information (higher-level device), wireless parameter information (lower-level device), and validity period information.

[0055] Fig. 4B shows an example of the area information 403. In the example shown in Fig. 4B, the area information 403 includes the number of area information items and coordinates.

[0056] The number of area information items stores the number of coordinate points that form the coordinate group included in this message.

[0057] One coordinate point includes latitude and longitude information (a set of coordinates) as shown in format 404. Here, we will explain format 404. The latitude and longitude information stored here may be coded in 24 bits each, in accordance with the coordinate information representation format specified in TS23.032.

[0058] Such coordinate points are stored in a number corresponding to the number of area information items. The area connecting these coordinate points may be treated as a communication-permitted area in which MBSR can operate.

[0059] 4C shows an example of a radio parameter information format 405. The radio parameter information format 405 relates to the radio parameter information (host device) and the radio parameter information (lower device) of the allowed area information format 402. The radio parameter information (host device) and the radio parameter information (lower device) of the allowed area information format 402 each indicate radio parameters for operating MBSR in the associated communication allowed area.

[0060] Various parameters related to wireless settings are stored in the wireless parameter information format 405. The various parameters related to wireless settings are preferably, but not limited to, a beacon frequency, a data transmission frequency, a transmission power, and the like.

[0061] The setting values ​​of various parameters related to the radio settings are used for the radio operation settings of the MBSR. Specifically, the radio settings set in the radio parameter information (host device) are applied as radio settings for a device that is a host device of the MBSR. The device that is a host device of the MBSR may be a gNB or the like. Furthermore, the radio settings set in the radio parameter information (lower device) are applied as radio settings for a device that is a lower device of the MBSR. The device that is a lower device of the MBSR may be a UE or the like.

[0062] Here, beacon frequency, data transmission frequency, transmission power, etc. have been cited as examples of various parameters related to wireless settings, but the present invention is not limited to these. For example, various parameters related to wireless settings may include SL-V2X-Preconfiguration parameters and SL-PreconfigurationNR parameters indicated in TS36.331. Furthermore, wireless parameters for MBSR may be used by establishing new parameters in the future instead of or in addition to SL-PreconfigurationNR.

[0063] The validity period information includes a start time and an end time, as indicated by reference numeral 406 in Fig. 4D. This information sets the time at which the permission area associated with the validity period information becomes valid. For example, the validity period information may be stored as a character string such as YYYY-MM-DD HH:MM:SS, or may be set according to the time information format used in SIB9 specified in TS 38.331.

[0064] While specific examples of communication permission area formats have been given so far, other formats are also possible. For example, the wireless parameter information (host device), wireless parameter information (subordinate device), and validity period information included in the permission area information shown in permission area information format 402 may be optional information in this format. Furthermore, if no specific wireless settings associated with the specified permission area are required, this field may not be included. Similarly, if no validity period for the permission area is required, this field may not be included.

[0065] Next, the processing performed when gNB300 notifies permitted area information will be explained using a flow chart.

[0066] Figure 5 shows the flow of the initial connection process of gNB300 in this embodiment.

[0067] At S501, gNB300 receives the RRCSetupComplete message sent by MBSR600.

[0068] At S502, gNB300 analyzes the received RRCSetupComplete message and confirms the information contained in the message.

[0069] In S503, the gNB 300 checks whether the received information includes an IAB node type. In this embodiment, the presence or absence of a Mobile IAB Indication is checked. If it is not included, proceed to S506, and send a normal RRC Reconfiguration message that does not include allowed area information to the opposite communication device, and end the process. On the other hand, if it is included, proceed to S504.

[0070] In S504, the gNB 300 determines whether the IAB node type is MBSR. In this embodiment, if the value of Mobile IAB Indication is True, it is determined to be MBSR. If it is not MBSR, proceed to S506, and send a normal RRC Reconfiguration message that does not include allowed area information to the opposite communication device, and end the processing. If it is MBSR, proceed to S505.

[0071] At S505, gNB300 generates an RRC Reconfiguration message including allowed area information and transmits it to the opposing communication device.

[0072] In this embodiment, whether the opposite communication device is an MBSR is determined from the IAB node type information included in the RRCSetupComplete message. The base station has been described as notifying the allowed area information using an RRC Reconfiguration message only in the case of an MBSR. Here, the RRC message notifying the allowed area information does not have to be an RRC Reconfiguration message. For example, the allowed area information can be included in an RRCSetup message to notify the MBSR. In this case, the IAB node type does not have to be acquired using the RRCSetupComplete message. For example, information that can be used to determine whether the communication device is an MBSR may be included in an RRCSetupRequest message or broadcast information in SIB (system information block) 1.

[0073] However, as described above, the method of simply using control plane signals in a 5G system as a means for a base station to notify an MBSR of allowed area information causes the following problem. That is, the above initial connection sequence is also used by fixed IAB nodes and UEs (User Equipment) other than the MBSR. If allowed area information is added to an existing RRC message, the allowed area information will also be notified to fixed IAB nodes and UEs that do not require it.

[0074] In contrast, according to this embodiment, as described above, the gNB 300 can determine whether the opposing communication device is an MBSR based on the IAB node type information obtained via the control plane signal. This reduces the possibility that the allowed area information is notified to fixed IAB nodes or UEs that do not require the allowed area information. As a result, the information processing load and communication load caused by essentially unnecessary notifications (notifications to fixed IAB nodes or UEs) can be substantially eliminated. In this way, according to this embodiment, a mechanism can be provided that can efficiently notify the MBSR of the allowed area information.

[0075] [Second Embodiment] In the first embodiment, a base station was described that determines whether to notify allowed area information based on IAB node type information included in RRCSetupComplete. Here, the allowed area information notified by a single base station is the same for all MBSRs. However, unlike fixed IAB nodes, MBSRs can move freely. Depending on the behavior of the MBSR, such as moving faster than expected, the notified allowed area information may be insufficient. Therefore, a method will be described in which status information such as movement speed and movement direction is obtained from the MBSR, and the notified allowed area information is changed to match the status of the MBSR. This makes it possible to provide optimal allowed area information for each MBSR.

[0076] FIG. 6A is a block diagram showing an example of the configuration of software functional blocks of a base station that executes the communication control function according to this embodiment.

[0077] The software function 201A according to this embodiment differs from the software function 201 (FIG. 2) according to the first embodiment in that an allowed area selection unit 211 is added.

[0078] The allowed area selector 211 selects an allowed area to be notified to the MBSR 600 from among the area group. The area group is a collection of multiple allowed areas in which the MBSR can provide service. That is, the number of allowed areas in which the MBSR can provide service is not limited to one, but may be multiple. In this case, the allowed area selector 211 selects an allowed area in which each MBSR can provide service from among the multiple allowed areas (area group). Note that typically, only one allowed area in which one MBSR can provide service is selected, but two or more may also be selected.

[0079] In this embodiment, the allowed area information generation unit 208 generates or acquires area information related to the allowed areas to be notified, selected by the allowed area selection unit 211. For example, the allowed area information generation unit 208 may generate area information related to the allowed areas to be notified based on area group information that may be acquired from the CN. In this case, the area group information may be a collection of allowed area information related to multiple allowed areas. In this case, the multiple allowed areas may be multiple allowed areas that belong to a relatively wide range, or may be a predetermined number or fewer of adjacent allowed areas. Furthermore, when the area group information is generated by the CN, the multiple allowed areas may be, for example, all allowed areas managed by the CN. In either case, the generated or acquired allowed areas may be stored in a predetermined storage area, such as the data storage unit 204, managed by the allowed area information generation unit.

[0080] The processing sequence in this embodiment will be described with reference to FIG. 6B.

[0081] S301 and S302 are the same as those in the first embodiment described above with reference to FIG. 3, and therefore a description thereof will be omitted.

[0082] At S303A, MBSR 600 transmits an RRCSetupComplete message to gNB 300. At this time, MBSR 600 includes Mobile IAB Indication as IAB node type information in the RRCSetupComplete message, as well as information indicating the status of the MBSR. Hereinafter, information indicating the status of the MBSR will also be referred to as "MBSR status information." The status of the MBSR includes, for example, the current location of the MBSR, movement speed, movement direction, stop time, planned stop time, planned movement route, operation route, etc.

[0083] In this embodiment, allowed area information to be notified is generated in accordance with this MBSR status information. The generated allowed area information is notified in an RRC Reconfiguration message (S304), as in the first embodiment. Upon receiving the message, the MBSR 600 transmits an RRC Reconfiguration Complete message (S305).

[0084] Next, the processing performed when gNB300 notifies permitted area information will be explained using a flow chart.

[0085] Figure 6C shows the flow of the initial connection process of gNB300 in this embodiment.

[0086] At S601, gNB300 receives the RRCSetupComplete message sent by MBSR600.

[0087] At S602, gNB300 analyzes the received RRCSetupComplete message and confirms the information contained in the message.

[0088] In S603, the gNB 300 checks whether the received information includes an IAB node type. In this embodiment, the presence or absence of a Mobile IAB Indication is checked. If it is not included, the process proceeds to S609, where a normal RRC Reconfiguration message that does not include permitted area information is sent to the opposing communication device, and the process ends. If it is included, the process proceeds to S604.

[0089] In S604, the gNB 300 determines whether the IAB node type is MBSR. In this embodiment, if the value of Mobile IAB Indication is True, it determines that the IAB node type is MBSR. In this case, proceed to S605. If it is not MBSR, proceed to S609 and send a normal RRC Reconfiguration message that does not include allowed area information to the opposing communication device, and then end the process.

[0090] In S605, the gNB 300 checks whether the received information includes MBSR status information. If MBSR status information is included, the process proceeds to S606, where the allowed area selection unit 211 selects allowed area information to be notified to the MBSR according to the status of the MBSR. For example, it is possible to select an allowed area that exists in the direction of movement of the MBSR, select a farther allowed area if the MBSR's movement speed is fast, or select an allowed area along the planned movement route or driving route. After selecting the allowed area to be notified, the process proceeds to S608. If MBSR status information is not included, the process proceeds to S607, selects default area information, and then proceeds to S608.

[0091] In S608, gNB300 generates an RRC Reconfiguration message including the allowed area information selected in S606 and S607 and transmits it to the opposing communication device.

[0092] Third Embodiment In the first and second embodiments, the method of notifying the permitted area information using the initial connection sequence has been described.

[0093] Although the RRC Reconfiguration message has been used to notify the allowed area information, this message is also notified from the base station at times other than the initial connection. For example, it is also notified when the MBSR moves and changes its connection destination to another base station. In this embodiment, a method for updating and notifying the allowed area information will be described using a sequence when the MBSR moves and connects to another base station.

[0094] Furthermore, in this embodiment, updating of the MBSR status information used in the second embodiment will also be described.

[0095] 7 shows the sequence when MBSR 600 moves and changes the connection destination from the source base station (Source gNB-DU) to the destination base station (Target gNB-DU). Here, it is assumed that the two gNB-DUs are in the same gNB-CU. Since the sequence itself is the same as that defined in TS 38.401 8.2.1.1, a detailed description of each message will be omitted. Only the key points in this embodiment will be described.

[0096] First, the MBSR 600 notifies the Source gNB-DU of a Measurement Report (S701). In this embodiment, the MBSR 600 includes MBSR status information in the message. The MBSR status information is the same as that described in the second embodiment. The MBSR 600 updates the MBSR status information according to the current status and notifies the base station. This allows the base station to know the latest status of the notified MBSR and to update the permitted area information to be notified accordingly.

[0097] The Source gNB-DU transmits the received Measurement Report to the gNB-CU as a UL RRC MESSAGE TRANSFER (S702).

[0098] The gNB-CU selects the allowed area information based on the received MBSR status information. When the gNB-DU to which the MBSR is connected is changed as in this embodiment, the gNB-CU selects MBSR status information corresponding to the allowed area information based on the target base station (Target gNB-DU).

[0099] The gNB-CU generates an RRC Reconfiguration message including the selected allowed area information and transmits it to the Source gNB-DU as a UE CONTEXT MODIFICATION REQUEST (S705). Finally, the Source gNB-DU notifies the MBSR 600 of RRC Reconfiguration (706). The MBSR 600 performs RRC reconfiguration and updates the allowed area information in accordance with the received RRC Reconfiguration message.

[0100] Next, we will use a flow diagram to explain the processing performed when base stations (gNB-CU, Source gNB-DU, and Target gNB-DU) update and notify allowed area information.

[0101] FIG. 8 shows a flow of RRC reconfiguration processing (connection reconfiguration processing) of a base station in this embodiment.

[0102] In S801, the base station receives the Measurement Report transmitted by the MBSR 600.

[0103] In S802, the base station analyzes the received Measurement Report and checks the information contained in the message.

[0104] In S803, the base station determines whether the opposite communication device is an MBSR. For this determination, the IAB node type information received at the initial connection may be used, or the IAB node type information may be included in the Measurement Report. If it is not an MBSR, the base station proceeds to S808, where it transmits a normal RRC Reconfiguration message that does not include allowed area information to the opposite communication device, and ends the process. If it is an MBSR, the base station proceeds to S804.

[0105] In S804, the base station checks whether the received information includes MBSR status information. If MBSR status information is included, the process proceeds to S805, where allowed area information to be notified to the MBSR is selected according to the MBSR status. The selection method is the same as in the second embodiment. At this time, if the MBSR is moving base stations (i.e., if the MBSR is changing the base station to which it is connected), the allowed area information is selected taking into account the location of the base station to which it is connected. After selecting the allowed area to be notified, the process proceeds to S807. If MBSR status information is not included, the process proceeds to S806, where default area information is selected, and the process proceeds to S807. At this time, if the MBSR is moving base stations, the default allowed area information of the base station to which it is connected is selected.

[0106] In S807, the base station generates an RRC Reconfiguration message including the allowed area information selected in S805 and S806, and transmits the message to the peer communication device.

[0107] 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.

[0108] Upon completion of the processing procedure of S303 or S305 in Figure 3, the gNB300 and the MBSR600 execute the F1 establishment procedure. Specifically, the MBSR600 transmits an F1 Setup Request to the gNB300, and the gNB300 transmits an F1 Setup Response to the MBSR600. Therefore, the gNB300 may transmit the permitted area information to the MBSR600 by including it in the F1 Setup Response instead of in an RRC message.

[0109] In addition, the following supplementary notes are disclosed regarding the above-described embodiment.

[0110] [Supplementary Note 1] A communication device comprising: a first acquisition means for acquiring type information capable of determining whether another communication device is a first type IAB (Integrated Access and Backhaul) node that involves movement; a generation or acquisition means for generating or acquiring area information regarding an area in which the first type IAB node can provide service; a determination means for determining whether to notify the other communication device of the area information based on the type information of the other communication device; and a transmission means for transmitting the area information to the other communication device based on a determination result of the determination means.

[0111] [Supplementary Note 2] The communication device according to Supplementary Note 1, wherein the transmitting means transmits the area information using an RRC (Radio Resource Control) message.

[0112] [Supplementary Note 3] The communication device according to Supplementary Note 1 or 2, wherein the RRC message is an RRC Reconfiguration message or an RRC Setup message.

[0113] [Supplementary Note 4] The communication device according to any one of Supplementary Notes 1 to 3, wherein the type information is acquired using broadcast information or an RRC message.

[0114] [Supplementary Note 5] The communication device according to any one of Supplementary Notes 2 and 3, wherein the RRC message is an RRC SetupComplete message.

[0115] [Supplementary Note 6] The communication device according to any one of Supplementary Notes 1 to 5, characterized in that the transmitting means transmits the area information to the other communication device when the determining means determines that the other communication device is the first type IAB node based on the type information of the other communication device.

[0116] [Supplementary Note 7] The communication device according to Supplementary Note 6, wherein the transmitting means does not transmit the area information to the other communication device when the determining means determines, based on the type information of the other communication device, that the other communication device is a second type IAB node or UE (User Equipment) that does not involve movement.

[0117] [Supplementary Note 8] The communication device according to any one of Supplementary Notes 1 to 7, wherein the generating or acquiring means generates or acquires the area information based on location information of the own station.

[0118] [Supplementary Note 9] The communication device according to Supplementary Note 8, wherein the area related to the area information is located around the own station.

[0119] [Supplementary Note 10] The communication device according to any one of Supplementary Notes 1 to 9, further comprising: a second acquisition means for acquiring area group information relating to a plurality of permitted areas that form the area from a CN (Core Network); and a selection means for selecting, from the plurality of permitted areas, one or more permitted areas related to the area information to be notified to the other communication device.

[0120] [Supplementary Note 11] The communication device according to Supplementary Note 10, further comprising a third acquisition means for acquiring status information regarding a status of the other communication device whose type information indicates the first type IAB node, and wherein the selection means selects the one or more allowed areas based on the status information.

[0121] [Supplementary Note 12] The communication device according to Supplementary Note 11, wherein the state indicated by the state information is related to movement of the other communication device.

[0122] [Supplementary Note 13] The communication device according to Supplementary Note 11 or 12, wherein the state indicated by the state information includes at least one of a current location, a moving speed, a moving direction, a stopping time, a planned stopping time, a planned moving route, and a driving route.

[0123] [Supplementary Note 14] The communication device according to any one of Supplementary Notes 11 to 13, wherein the third acquisition means acquires the status information by MeasurementReport.

[0124] The present invention can also be realized by supplying a program that realizes one or more functions of the above-described embodiments to a system or device via a network or a storage medium, and having one or more processors in the computer of the system or device read and execute the program. The present invention can also be realized by a circuit (e.g., an ASIC or FPGA) that realizes one or more functions.

[0125] 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.

[0126] This application claims priority based on Japanese Patent Application No. 2023-132240, filed on August 15, 2023, the entire contents of which are incorporated herein by reference.

Claims

1. A communication device comprising: a first acquisition means for acquiring type information capable of determining whether or not another communication device is a first type IAB (Integrated Access and Backhaul) node that involves movement; a storage means for storing area information generated or acquired, the area information being related to an area in which the first type IAB node can provide service; a determination means for determining whether or not to notify the other communication device of the area information based on the type information of the other communication device; and a transmission means for transmitting the area information to the other communication device based on a determination result of the determination means.

2. The communication device according to claim 1, wherein said transmitting means transmits said area information using an RRC (Radio Resource Control) message.

3. The communication device according to claim 2, wherein the RRC message is an RRC Reconfiguration message or an RRC Setup message.

4. The communication device according to claim 1, wherein the first acquisition means acquires the type information by using broadcast information or an RRC message.

5. The communication device according to claim 4, wherein the RRC message is an RRC SetupComplete message.

6. A communication device as described in any one of claims 1 to 5, characterized in that the transmitting means transmits the area information to the other communication device when the determining means determines that the other communication device is an IAB node of the first type based on the type information of the other communication device.

7. The communication device described in claim 6, characterized in that the transmission means does not transmit the area information to the other communication device when the determination means determines, based on the type information of the other communication device, that the other communication device is a second type IAB node or UE (User Equipment) that does not involve movement.

8. The communication device according to claim 1, characterized in that the storage means stores the area information generated by the local station based on its own location information or the area information generated by an external device based on the location information of the local station and acquired from outside.

9. The communication device according to claim 8, wherein the area related to the area information is an area located in the vicinity of the own station.

10. A communication device as described in claim 1, further comprising: a second acquisition means for acquiring area group information regarding a plurality of permitted areas that form said area from a CN (Core Network); and a selection means for selecting, from among the plurality of permitted areas indicated by the area group information, one or more permitted areas related to the area information to be notified to said other communication device, wherein said storage means stores the permitted areas selected by said selection means.

11. The communication device described in claim 10, further comprising a third acquisition means for acquiring status information regarding the status of the other communication device whose type information indicates the first type of IAB node, and wherein the selection means selects the one or more permitted areas based on the status information.

12. The communication device according to claim 11, wherein the state indicated by the state information relates to a movement of the other communication device.

13. The communication device of claim 12, wherein the status indicated by the status information includes at least one of a current location, a moving speed, a moving direction, a stopping time, a planned stopping time, a planned moving route, and a driving route.

14. The communication device according to claim 11, wherein the third acquisition means acquires the status information by a Measurement Report.

15. A control method for controlling communications, comprising the steps of: acquiring type information capable of determining whether or not another communications device is a first type IAB (Integrated Access and Backhaul) node that involves movement; generating or acquiring area information relating to an area in which the first type IAB node can provide services, and storing the area information in a specified memory area; determining whether or not to notify the other communications device of the area information based on the type information of the other communications device; and transmitting the area information to the other communications device based on the determination result of the determination step.

16. A program for causing a computer to execute the steps of: acquiring type information capable of determining whether or not another communication device is a first type IAB (Integrated Access and Backhaul) node that involves movement; generating or acquiring area information regarding an area in which the first type IAB node can provide service, and storing the area information in a specified memory area; determining whether or not to notify the other communication device of the area information based on the type information of the other communication device; and transmitting the area information to the other communication device based on the determination result of the determination step.

Images