Managing network connectivity in wireless communication system

Abstract

A method for managing network connectivity in a wireless communication system comprising at least one mobile integrated access and backhaul (mIAB) node is disclosed. The method includes, at the mIAB node, providing a mobility message to the wireless communication device, where the mobility message includes at least one of: mobility profile information indicating mobility capabilities of the mIAB node; the guaranteed static time information is used for indicating the minimum time period when the mIAB node is kept at a certain place. The mobility configuration file information comprises at least one of the following information: speed information used for indicating the speed capability of the mIAB node; the range information is used for indicating a mobility area of the mIAB node; static information for indicating the duration of one or more static periods that the mIAB node can experience; travel information for indicating a sequence of mobility periods and static periods of a travel that the mIAB node can follow.

Description

Technical Field

[0001] The present invention generally relates to managing network connectivity in a wireless communication system. In particular, the present invention relates to managing network connectivity in a wireless communication system including at least one mobile Integrated Access and Backhaul (IAB) node. Background Art

[0002] Wireless communication systems are deployed in large numbers to address a wide range of applications from mobile broadband, massive machine type communications to Ultra Reliable Low Latency Communication (URLLC). Such systems allow multiple user equipments (UEs) or mobile terminals to share a wireless medium to exchange several types of data content (e.g., video, voice, messaging, ...) over a radio access network (RAN) through one or more base stations. Traditionally, base stations are wired to the core network (e.g., via optical fiber), forming an intermediate network called backhaul (BH).

[0003] Examples of such wireless multiple-access communication systems include systems based on the 3rd Generation Partnership Project (3GPP-RTM) standards such as fourth generation (4G) Long Term Evolution (LTE) or the more recent fifth generation (5G) New Radio (NR) systems, or systems based on the IEEE 802.11 standards such as WiFi.

[0004] Due to the increase in the number of users and higher throughput requirements, the need for network densification increases.

[0005] Faced with the problem of high deployment cost and time of wired backhaul networks with network densification, 3GPP proposed wireless backhaul, also known as integrated access and backhaul (IAB) in the recent Release 16 for 5GNR, where instead of optical fiber, a portion of the wireless (i.e., radio) spectrum is used for backhaul connections of base stations. Wireless backhaul communications (between base stations) can use the same radio resources as access communications (between base stations and UEs).

[0006] IAB is proven to be a competitive alternative to fiber-based backhaul in dense areas or hard-to-cover areas because IAB allows for scalable and rapid installation without the burden of wiring base stations.

[0007] The IAB will most likely operate in the millimeter wave (mmWave) frequency band to achieve the required Gbps (gigabits per second) data rates.

[0008] Urban environments are typically characterized by a high density of users and the presence of a large number of vehicles (e.g., public / private passenger transport, freight transport, food trucks, ...). The speed of some vehicles may be quite low or at least similar to pedestrian speed, and some of these vehicles may even be temporarily stationary. Some of these vehicles (e.g., buses, trains, or trams) may have predictable routes and / or restricted mobility areas (e.g., some vehicles (such as food trucks or promotional vehicles, etc.) may be located outside a stadium or show venue), while other vehicles may have predictable fixed locations (e.g., taxis).

[0009] 3GPP is considering that such vehicles can provide opportunities to increase network coverage and connectivity to UEs inside the vehicle or even to UEs near the vehicle by installing onboard base stations (or base station elements) that will act as repeaters on these vehicles. These repeaters will rely on 5G wireless backhaul (usually IAB, or integrated access and backhaul) for connecting to fixed donor devices. Thus, based on the fixed IAB foundations set forth in Release 16 and Release 17, 3GPP is now considering mobile IAB systems and architectures as part of the Release 18 framework to address scenarios focusing on mobile IAB nodes installed on vehicles (e.g., buses, trains, taxis). In such scenarios, mobile IAB nodes may also be referred to as vehicle-mounted repeaters (VMRs), thereby providing 5G coverage / capacity to UEs onboard and / or around them. The technical benefits of using vehicle repeaters include enabling relay vehicles to obtain better coverage than nearby UEs due to better RF / antenna capabilities, and others, thereby providing UEs with better links to the macro network. Additionally, vehicle relays are expected to have less stringent power / battery constraints than UEs.

[0010] Since VMR or mobile IAB (mIAB) nodes may be static at some times (e.g., a taxi in a parking lot or at a taxi stand, a bus in a parking lot or at a bus stop, a train at a station, or a temporary facility in an event or emergency / disaster situation) and moving at other times, the connection with the mobile IAB (mIAB) nodes or vehicle-mounted repeaters (VMRs) is likely to fluctuate based on their actual movement. Therefore, in order to benefit from the additional connectivity caused by the presence of mobile IAB nodes in the topology while mitigating the connectivity impact that may be caused by the actual mobility conditions of the mobile IAB nodes, the connection of child IAB nodes (fixed or mobile) via or through such mobile IAB nodes to the network should be carefully managed, which requires some dedicated signaling to other IAB nodes including the IAB donor for connection setup or dynamic mobility condition notification purposes.

[0011] Since a given IAB topology may at some point be composed of both legacy IAB devices (belonging to previous Releases 16 and 17) (which do not have any ability to distinguish mobile IAB nodes from fixed IAB nodes) and newer IAB devices (belonging to Releases 18 and future releases) that have the ability to handle mobile IAB connectivity, it is also necessary to consider managing the connectivity of different kinds of IAB devices (e.g., legacy IAB devices and newer IAB devices) to the network via or through mobile IAB devices.

[0012] Furthermore, given the above-mentioned fluctuations in connectivity associated with mobile IAB nodes, it may also be desirable to carefully manage connectivity for both onboard and / or surrounding user equipment (UE) that may be within range of the mobile IAB node.

[0013] Therefore, some new mechanisms are needed to address at least some of the above problems while limiting the complexity of the processing at the IAB node and the latency that will be caused by such processing. Summary of the invention

[0014] According to a first aspect of the present invention, a method for managing network connectivity in a wireless communication system is provided, wherein the wireless communication system includes at least one mobile integrated access and backhaul node, i.e., an mAB node. The method includes: at the mAB node, providing a mobility message to a wireless communication device, wherein the mobility message includes at least one of the following information: mobility profile information, used to indicate the mobility capability of the mAB node; and guaranteed static time information, used to indicate the minimum time period for the mAB node to remain at a certain location.

[0015] In an example, the mobility profile information includes at least one of the following information: speed information indicating the speed capability of the mIAB node, range information indicating the mobility area of ​​the mIAB node, static information indicating the duration of one or more static periods that the mIAB node can experience, and trip information (which may alternatively be referred to as trajectory information) indicating a sequence or continuation of mobility periods and static periods of a trip that the mIAB node can follow.

[0016] By providing mobility profile information and / or guaranteed static time information (e.g., at setup time and / or after one or more connections to the mobile IAB node have been established), a receiving wireless communication device (such as an IAB donor CU, a UE, or another IAB node, etc.) can receive information about the mobility capabilities and / or current static conditions of the mobile IAB node, and act accordingly using the additional information about the mobility of the mobile IAB node. In other words, the mIAB node can announce its mobility capabilities and / or static conditions to one or more UEs and one or more other IAB nodes near the mIAB node. Using the additional information and / or guaranteed static time information related to the mobility capabilities of the mIAB node, the UE and / or other IAB nodes and / or the IAB donor node have additional information and can therefore act more effectively. For example, the UE and / or another IAB node may decide not to connect to the network via the mIAB node due to the mobility of the mIAB node, or may decide to connect regardless of the mobility of the mIAB node (e.g., because the information indicates that the mIAB node is traveling slowly or in a restricted area). In another example, where the UE and / or another IAB node is already connected, the UE and / or another IAB node may decide to initiate a cell search procedure to find another IAB node to connect to or hand over to.

[0017] According to a second aspect of the present invention, there is provided a method at a wireless communication device of a wireless communication system as claimed in claim 19 of the accompanying claims.

[0018] According to a third aspect of the present invention, there is provided a method at an Integrated Access and Backhaul (IAB) donor node of a wireless communication system as claimed in claim 32 of the accompanying claims.

[0019] According to a fourth aspect of the present invention, there is provided a method at an Integrated Access and Backhaul (IAB) node for managing network connectivity in a wireless communication system as claimed in claim 49 of the accompanying claims.

[0020] According to a fifth aspect of the present invention, there is provided a method at a wireless communication device of a wireless communication system as claimed in claim 59 of the accompanying claims.

[0021] According to a sixth aspect of the present invention, there is provided an apparatus for an Integrated Access and Backhaul (IAB) node for a wireless communication system as claimed in claim 62 of the appended claims.

[0022] According to a seventh aspect of the present invention, there is provided an apparatus for an Integrated Access and Backhaul (IAB) donor node for a wireless communication system as claimed in claim 63 of the appended claims.

[0023] According to an eighth aspect of the present invention, there is provided an apparatus for a wireless communication device according to claim 64 of the accompanying claims.

[0024] Further exemplary features of the invention are described in the further independent and dependent claims.

[0025] Any feature in one aspect of the invention may be applied to other aspects of the invention in any appropriate combination. In particular, method aspects may be applied to apparatus / device / unit aspects, and vice versa.

[0026] In addition, features implemented in hardware may be implemented in software, and vice versa. Any reference to software features and hardware features herein should be interpreted accordingly. For example, according to other aspects of the present invention, there is provided a computer program including instructions and a computer-readable storage medium carrying the computer program, which instructions, when executed by a processing unit, cause the processing unit to perform any of the above aspects or examples of the method.

[0027] It should also be understood that specific combinations of the various features described and defined in any aspect of the invention may be independently implemented and / or provided and / or used. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] Various aspects of the invention will now be described, by way of example only, and with reference to the following drawings, in which:

[0029] Figure 1 is a schematic diagram illustrating an example wireless communication system in which the present invention may be implemented according to one or more embodiments;

[0030] Figure 2 A and Figure 2 b is a schematic diagram illustrating a stack of some protocol layers involved in IAB operation;

[0031] Figure 3 is a schematic diagram illustrating the format of a BAP protocol data unit (PDU) or packet;

[0032] Figure 4 is a schematic block diagram illustrating an example wireless communication system (or IAB network) in which the present invention may be implemented according to one or more embodiments;

[0033] Figure 5 is a schematic simplified diagram illustrating example message flows for managing network connectivity in a wireless communication system including at least one IAB node according to one or more embodiments of the present invention, and may be used to manage the IAB node's advertising of its mobility capabilities and status and its ability to support IAB connections with child IAB nodes;

[0034] Figure 6 is a flow chart of an example method for managing mobile IAB node connectivity according to one or more embodiments of the present invention;

[0035] Figure 7 is a schematic simplified diagram illustrating an example message flow for managing the connection of a wireless communication device (or network device) to a network of a wireless communication system via a mobile IAB node according to one or more embodiments of the present invention;

[0036] Figure 8 is a flow chart of an example method for managing the connection of a wireless communication device (or network device) to a network of a wireless communication system via a mobile IAB node according to one or more embodiments of the present invention;

[0037] Fig. 9 is a flow chart of an example method for enabling a wireless communication device (or network device) to manage its connection to a network of a wireless communication system via a mobile IAB node according to one or more embodiments of the present invention;

[0038] Fig.10 A schematic block diagram of a wireless communication device according to an embodiment of the present invention is shown;

[0039] Fig.11 is a flow chart of an example method for managing network connectivity in a wireless communication system including at least one mobile IAB node according to one or more embodiments of the present invention;

[0040] Fig.12 is a flow chart of an example method performed at a wireless communication device according to one or more embodiments of the present invention;

[0041] Fig.13 is a flow chart of an example method performed at an IAB donor node of a wireless communication system according to one or more embodiments of the present invention; and

[0042] Fig.14 is a flow chart of an example method for managing network connectivity in a wireless communication system including at least one mobile IAB node according to one or more embodiments of the present invention. DETAILED DESCRIPTION

[0043] Figure 1 An example communication system 100 is illustrated in which the present invention may be implemented in accordance with one or more embodiments.

[0044] As depicted, the example system 100 is a wireless communication system, in particular a mobile radio communication system such as a fifth generation (5G) new radio (NR) system including a wireless integrated access and backhaul (IAB) communication system or network. Although embodiments and examples of embodiments of the present invention will be described with respect to a 5G NR system in the following description, it will be understood that the present invention is not intended to be limited to a 5G NR system and may be used in any wireless communication system having an integrated access and backhaul communication system that shares radio resources used by a wireless access link and a wireless backhaul link.

[0045] The system 100 includes multiple UEs (user equipment) 132, 133, 131 and 134, a remote core network 110, a main base station 120, two fixed integrated access and backhaul (IAB) stations 121 and 122 or IAB nodes 121 and 122 (hereinafter also referred to as IAB nodes), and a mobile integrated access and backhaul (IAB) station or mobile IAB node 123 mounted on a vehicle 105 (e.g., a bus, a train, a taxi, a car, etc.).

[0046] The main base station 120 (also referred to as the IAB donor 120 (or IAB donor)) is connected to the core network 110 via a wired link 101 (preferably an optical fiber or any other wired component). In embodiments and examples of embodiments of the present invention, as defined in the 3GPP TS38.300v17.0.0 specification document, the IAB donor 120 is a 5G NR base station (referred to as a gNB) with additional functions to support IAB features.

[0047] In order to extend the network coverage of the IAB donor 120 and reach the remote UEs 132, 133 and 131, the operator installs IAB stations 121 and 122 (also referred to as IAB nodes 121 and 122). By acting as relay nodes between the IAB donor 120 and the UEs 132 and 133, the IAB nodes 121 and 122 allow to overcome the accessibility issues caused by the presence of the building 108, which is an obstacle for the propagation of radio waves and therefore for direct attachment and further communication between the UE and the IAB donor 120. This is especially true when the communication between the IAB donor 120 and the UEs 132 and 133 operates at millimeter wave frequencies that are highly sensitive to shadowing phenomena.

[0048] The IAB donor 120 also serves the UE 134 , which is directly connected to the IAB donor 120 .

[0049] The mobile IAB station 123 (also referred to as an IAB node 123 or mIAB node 123) mounted on the vehicle 105 also provides network coverage and capacity extension, allowing the IAB donor 120 to reach onboard remote UEs (such as remote UE 135), as well as surrounding UEs or UEs near the IAB node 123 (such as remote UE 136).

[0050] The IAB donor 120 and the IAB nodes 121, 122, and 123 thus form a backhaul network or IAB network (also referred to as an IAB topology) that accommodates UEs 131, 132, 133, 134, 135, and 136. The terms IAB network and IAB topology will be used interchangeably below. The IAB network forms a radio access network (RAN), or what is referred to as a next generation (NG) RAN for 5G.

[0051] The specifications for Integrated Access and Backhaul (IAB) extend across several 3GPP standard documents, including:

[0052] -TS 38.300 RAN Architecture (V17.0.0),

[0053] -TS 38.321 MAC protocol (V17.0.0),

[0054] -TS 38.331 Radio Resource Control (RRC) Protocol (V17.0.0),

[0055] -TS 38.340 Backhaul Adaptation Protocol Layer (V17.0.0),

[0056] -TS 38.401 RAN architecture (V17.0.0),

[0057] -TS 38.473F1 application protocol (V17.0.0).

[0058] Since IAB nodes 121, 122, and 123 are connected to UEs 131, 132, 133, 134, 135, and 136, respectively, these IAN nodes are considered to be access IAB nodes for the UEs to which they are respectively connected.

[0059] The IAB donor 120 is a logical node that provides NR-based wireless backhaul and consists of a central unit (CU or gNB-CU function) and connected (one or more) donor distributed units (DU or gNB-DU function). The IAB donor CU or donor CU (hereinafter also referred to as IAB donor CU (IAB-donor CU or IAB donor CU)) hosts higher layer protocols (such as PDCP (Packet Data Convergence Protocol) and RRC (Radio Resource Control) protocol, etc.) for controlling the operation of one or more DUs, and one or more IAB donor DUs or donor DUs (hereinafter also referred to as IAB donor DUs (IAB-donor DU or IABdonor DU)) each include lower layer protocols such as RLC, MAC and physical layer protocols. The IAB donor CU and the IAB donor DU may be located at a location remote from the other, or may be located in the same physical device. The gNB-DU function is defined in 3GPP TS 38.401. Its purpose is to terminate the NR access interface towards the UE and the next hop IAB node, and terminate the F1 protocol towards the IAB donor gNB-CU function.

[0060] The IAB nodes, which may serve multiple radio sectors, are wirelessly backhauled via one or more hops (eg, via one or more than one IAB nodes) to the IAB donor 120. They form a directed acyclic graph (DAG) topology with the IAB donor at the root.

[0061] Each IAB node consists of an IAB-DU (IAB Distributed Unit) and an IAB-MT (IAB Mobile Terminal). The gNB-DU functionality on an IAB node is also referred to as an IAB-DU and allows for a connection to a next hop IAB or downstream (towards the UE) to a UE. The IAB-MT functionality includes, for example, physical layer, layer 2, RRC, and non-access stratum (NAS) functionality to connect to the gNB-DU of an upstream IAB node, including the IAB donor 120, in this case, to the IAB donor gNB-DU and therefore to the core network 110 (e.g., for initialization, registration, and configuration).

[0062] In the DAG topology, the neighbor nodes on the IAB-DU interface are called child nodes, and the neighbor nodes on the IAB-MT interface are called parent nodes. The direction toward the child nodes is also called downstream, while the direction toward the parent node is called upstream.

[0063] The IAB donor 120 (eg, IAB donor CU) performs centralized resource, topology, and routing management for the entire IAB topology, including configuring IAB nodes according to the network topology, for example, to perform appropriate routing of data packets.

[0064] Figure 2A and Figure 2 FIG. 2 schematically illustrates a stack of some protocol layers involved in IAB operation.

[0065] The F1 interface supports the exchange of signaling information between endpoints and the transmission of data to each endpoint. From a logical point of view, the F1 interface is a point-to-point interface between endpoints.

[0066] In 5G NR, F1-C is a functional interface in the control plane (CP) between the IAB donor CU and the IAB node DU. F1-U is a functional interface in the user plane (UP) for the same unit. F1-C and F1-U are composed of Figure 2 212 in a. In this example, F1-U and F1-C are carried by two return hops (from IAB donor to IAB node 1, and then from IAB node 1 to IAB node 2).

[0067] In the user plane, the block 210 at the IAB donor CU and the IAB node DU refers to the GTP-U layer, and the block 211 refers to the UDP layer. GTP-U stands for the GPRS Tunneling Protocol User Plane. The GTP-U tunnel is used to carry encapsulated PDUs and signaling messages between a given pair of GTP-U tunnel endpoints (refer to 3GPP TS29.281 for more details), here the block 210 at the IAB donor CU and the IAB node DU. The well-known User Datagram Protocol (UDP) is a transport layer protocol that provides best-effort datagram services and is suitable for use with the IP protocol.

[0068] In the control plane, box 210 indicates the F1AP (F1 Application Protocol) layer, and box 211 indicates the SCTP (Stream Control Transmission Protocol) layer. The F1 Application Protocol (as defined in 3GPP TS 38.473 and TS 38.401) provides signaling services between the IAB donor CU and the IAB node DU, or UE association services. These services are, for example, initialization, configuration, etc. The well-known SCTP layer provides reliable in-order transmission of messages with congestion control.

[0069] F1-U and F1-C rely on the IP transport layer between the IAB Donor CU and the IAB Node DU as defined in 3GPP TS 38.401.

[0070] When the IAB donor CU is remote from the IAB donor DU, or is locally in a virtual instantiation where the IAB donor CU and the IAB donor DU are on the same physical machine, the transmission between the IAB donor DU and the IAB donor CU also uses the IP transport layer over various media (e.g., wire or optical fiber). The IAB-specific transmission between the IAB donor CU and the IAB donor DU is specified in 3GPP TS 38.401.

[0071] L1 and L2 on the diagram represent the transport layer and physical layer respectively, appropriate to the medium in use.

[0072] The IP layer can also be used for non-F1 traffic, such as operations, management, and maintenance traffic.

[0073] Over the wireless backhaul, the IP layer itself is carried over the Backhaul Adaptation Protocol (BAP) sublayer, which enables routing over multiple hops. The BAP sublayer is specified in TS 38.340.

[0074] The IP traffic of the IAB-DU is routed through the wireless backhaul via the BAP sublayer. In the downstream direction, the upper layer packets are encapsulated by the BAP sublayer at the IAB donor DU, thereby forming a BAP packet or packet data unit (PDU) or data unit. The BAP packet is routed by the BAP layer (and the corresponding BAP entities in the IAB-DU and IAB-MT) of the intermediate IAB nodes (if present). The BAP packet is finally decapsulated by the BAP sublayer at the destination IAB node (if the upper layer packets in the BAP packet are intended for the UE, the destination IAB node may be an access IAN-node).

[0075] In the upstream direction, the upper layer packets are encapsulated by the BAP sublayer at the initiator IAB node (if the upper layer packets come from the UE, the initiator IAB node can be the access IAB node), thereby forming a BAP packet or PDU or data unit. The BAP packet is routed by the BAP layer (and the corresponding BAP entity in IAB-DU and IAB-MT) of the intermediate IAB node (if any). The BAP packet is finally decapsulated by the BAP sublayer at the IAB donor DU.

[0076] On the BAP sublayer, packets are routed based on a BAP Routing ID, which is carried in the BAP header and set by the BAP sublayer of the network node in the IAB network that generates the BAP packet. Figure 3 The format of a BAP data protocol data unit (PDU) or packet is illustrated. The format is specified in the standardized version of 3GPP TS 38.340 version 17.0.0, paragraph 6.2.

[0077] Header 30 includes fields 301 to 306. Field 301 (referred to as the D / C field) is a Boolean value indicating whether the corresponding BAP packet is a BAP data packet or a BAP control packet. Fields 302 to 304 are 1-bit reserved fields, preferably set to 0 (ignored by the receiver).

[0078] Fields 305 and 306 together indicate the BAP routing ID of the BAP packet. The BAP address field 305 (also called the DESTINATION field) is located in the leftmost 10 bits, while the BAP path identification field 306 (also called the PATH field) is located in the rightmost 10 bits.

[0079] Field 305 carries the BAP address (i.e., on the BAP sublayer) of the destination IAB node or IAB donor DU of the BAP packet. For routing purposes, each IAB node and IAB donor DU is configured with a specified BAP address (either by the IAB donor CU that controls the IAB network or the topology to which the IAB nodes and IAB donor DUs belong). Field 306 carries the path ID that identifies the routing path that the BAP packet should follow in the IAB topology to reach that destination. Routing paths (including their path IDs) are configured in the same way that BAP addresses are configured.

[0080] When a packet reaches the BAP layer from the upper layers, a BAP header is added to the packet, and when the packet reaches its destination node, the BAP header is stripped off by the BAP sublayer. The selection of the BAP routing ID for a packet is configured by the IAB donor CU.

[0081] For example, when a BAP packet is generated by an IAB node (i.e., by an IAB donor for downstream transmission or by an initiator IAB node for upstream transmission (which may be an access IAB node in the case where the upper layer packet is from a UE)), a BAP header with a BAP routing ID is constructed by the IAB node according to a configuration table defined in 3GPP TS38.340. The table is referred to as a downlink traffic to routing ID mapping configuration table in an IAB donor or an uplink traffic to routing ID mapping configuration table in an initiator IAB node. In an intermediate IAB node, the BAP header fields are already specified in the BAP packet for forwarding.

[0082] As described above, these configuration tables defining the BAP paths (and thus the routing policies and configuration of the IAB nodes taking into account the IAB network topology) are typically defined by the IAB Donor CU controlling the IAB network and transmitted to the IAB nodes to configure them.

[0083] To handle the transmission of messages over the 5G NR radio medium, three additional sublayers (RLC, MAC, and PHY) are implemented at each IAB node below the BAP sublayer. The RLC (Radio Link Control) sublayer is responsible for the segmentation or reconstruction of packets. The RLC sublayer is also responsible for requesting retransmission of lost packets. The RLC layer is further described in TS38.322. The MAC (Media Access Channel) protocol sublayer is responsible for selecting an available transport format for user data and for mapping logical channels to transport channels. MAC also handles part of the hybrid automatic repeat request scheme. The MAC layer is detailed in TS 38.321. On the transmitter side or transmitter side, MAC encapsulates data packets sent from RLC. MAC adds a header carrying information required for MAC functions. On the receiver side, MAC decapsulates data packets sent from PHY, removes its header, and passes the remaining data to RLC. The PHY sublayer provides an electrical interface to the transmission medium (air) by converting the information stream into a physical modulation signal and modulating the carrier frequency on the transmitter side. On the receiver side, the PHY sublayer converts the physical modulation signal back into an information stream. The PHY layer is described in TS 38.201, TS 38.211, TS 38.212, TS 38.213, TS 38.214.

[0084] To deliver messages towards the user plane or control plane, two other sublayers are used in the UE and IAB donor CU: the PDCP (Packet Data Convergence Protocol) sublayer, and the SDAP (Service Data Adaptation Protocol) sublayer for user plane communication or the RRC (Radio Resource Control) sublayer for control plane communication.

[0085] The PDCP sublayer handles IP header compression / decompression, encryption / decryption, and when necessary, integrity of data packets. Mandatory, packets are numbered on the transmitter side, and packets are reordered on the receiver side. The PDCP sublayer is described in 3GPP TS 38.323.

[0086] The SDAP sublayer 220 of the user plane handles the quality of service. The SDAP sublayer is described in TS 38.324. On the UE side, the SDAP sublayer exchanges payload data with the user's applications (voice, video, etc., not shown in the figure). On the IAB donor side, the SDAP sublayer exchanges data with the core network 110 (Internet traffic, cloud, etc.).

[0087] The RRC sublayer 220 for the control plane handles the configuration of the protocol entities of the user plane protocol stack. The RRC sublayer is described in TS38.331. The RRC sublayer is responsible for handling: broadcasting information required for UE to communicate with the cell; transmitting paging messages, managing connections, including establishing bearers; mobility functions; measurement configuration and reporting; device capabilities; and others.

[0088] The interface between nodes (for both CP and UP) using layers PDCP, RLC, MAC and PHY is called NR-Uu. This mainly involves the interface with the UE.

[0089] The interface between nodes (for both CP and UP) using layers BAP, RLC, MAC and PHY is called Backhaul RLC channel (BH RLC channel). This mainly concerns the interface between IAB nodes.

[0090] NR-Uu is the interface between the UE and the Radio Access Network, ie its access IAB node (for both CP and UP).

[0091] Figure 2 The b comes from 3GPP TS 38.300v17.0.0 and illustrates the protocol stack for RRC and NAS connections to support IAB-MT. The non-access stratum (NAS) protocol handles messages between the core network and the user equipment (here is the IAB node). The NAS protocol manages the establishment of communication sessions and maintains communication with the user equipment when the user equipment moves. 5G NAS is described in 3GPP TS24.501. The 5G core access and mobility management function (AMF) is a function within the core network that is used to receive all connection and session related information from the UE connected to the IAB node, and receive similar information from the IAB node. The AMF is only responsible for handling connection and mobility management tasks.

[0092] The IAB-MT establishes a signaling radio bearer SRB (a bearer carrying RRC and NAS messages) with the IAB donor CU. These SRBs are transmitted between the IAB-MT and its parent node(s) over the NR-Uu interface(s).

[0093] Figure 4 An example of a wireless communication system 400 including an IAB network or an IAB network system is illustrated, in which embodiments of the present invention and examples of embodiments can be implemented. In one example implementation, the radio link between the IAB node and the IAB donor DU node (referred to as a BH radio link) operates on a millimeter wave frequency band (i.e., above 30 GHz) that is highly sensitive to radio channel interference. The IAB network will also be referred to as an IAB topology or topology, so in this application, the terms IAB network and IAB topology and topology will be used interchangeably.

[0094] Forming part of NG RAN Figure 4The IAB network system is composed of two IAB networks or IAB topologies 4001 and 4002, each of which includes a group of IAB nodes (for example, the group may include multiple IAB nodes or at least one IAB node) and an IAB donor CU for controlling or managing multiple IAB nodes. The group of IAB nodes may include one or more IAB nodes, such as an initiator IAB node that generates a BAP packet and an intermediate or relay IAB node. The group of IAB nodes may also include one or more IAB donor DUs. Each IAB node communicates with at least one other IAB node via a wireless backhaul (BH) link.

[0095] although Figure 4 Two IAB topologies 4001 and 4002 are shown, but the present invention is not limited to the two IAB topologies 4001 and 4002 and may be implemented in an IAB communication system including more than two IAB topologies (where each topology includes a set of IAB nodes and an IAB donor CU as described above).

[0096] The IAB topology 4001 includes an IAB donor CU 401 (in Figure 4 ), its associated IAB donor DU, IAB donor DU 403 (in Figure 4 404 (in Figure 4 1 to DU2), and a plurality of IAB nodes 410, 420, 430, 460, 480 similar to the IAB nodes 121 and 122, and an IAB node 470 similar to the mobile IAB node 123.

[0097] The IAB topology 4002 includes an IAB donor CU 402 (in Figure 4 ) and its associated IAB donor DU 405 (in Figure 4 1), and multiple IAB nodes 440 and 450 similar to IAB nodes 121 and 122. IAB network 400 may provide network path diversity through several IAB donor DUs and different IAB networks or topologies.

[0098] As described above, each IAB node includes a mobile terminal (MT) portion or unit controlled and configured by the IAB donor using RRC messaging as defined in 3GPP TS 38.331, and a distributed unit (DU) portion controlled and configured by the IAB donor using F1-AP messaging as defined in 3GPP TS 38.473. For example, IAB node 410 includes an MT portion or unit 411 and a DU portion 412.

[0099] The wired backhaul IP network interconnects IAB donor CUs 401 and 402 and IAB donor DUs 403, 404, and 405 through a wired link 406. For example, the wired link consists of (one or more than one) optical fiber cables.

[0100] IAB donor CU 401 , IAB donor DUs 403 and 404 , IAB nodes 410 , 420 , 430 , 460 , 470 , and IAB node 480 are part of the same IAB network or IAB topology 4001 that is controlled (eg, configured and / or managed) by IAB donor CU 401 .

[0101] IAB donor CU 402 , IAB donor DU 405 , and IAB nodes 440 and 450 are part of the same IAB network or IAB topology 4002 that is controlled (eg, configured and / or managed) by IAB donor CU 402 .

[0102] IAB node 470 is connected to parent IAB node 430 via BH link 4030. IAB node 470 is also connected to UE 390 via communication link or radio link 4031: IAB node 470 is acting as an access node for UE 390. Figure 4 Only one UE 390 is shown, but it will be understood that there will be multiple UEs connected to the IAB node of the wireless communication system. Although IAB node 470 belongs to IAB network 4001 (with IAB node 430 as a parent via BH link 4030), given its proximity to IAB network 4002 and in particular to IAB node 450, IAB node 470 may be connected to IAB node 450 via wireless BH link 4050 (which will act as a parent node for IAB node 470). In addition to or in lieu of a connection to IAB node 430, such a connection to IAB node 450 is also possible for fixed IAB nodes, and is very likely to occur for mobile IAB nodes (such as IAB node 470) that move in the direction of the IAB topology 4002, for example.

[0103] Each IAB node supports wireless communications in a coverage area called a cell. In other words, each IAB node is associated with a cell. Wireless communication devices located within a cell (such as UEs or other IAB nodes, etc.) can connect to the IAB node of the serving cell to communicate with other devices (e.g., other UEs, IAB nodes, servers providing access to the Internet, etc.) via the IAB node. Typically, the IAB node measures signals from IAB nodes of neighboring cells as part of a cell search process (e.g., as defined in 3GPP TS 38.300, upon initial connection to the network) or as part of a subsequent process. These measurements are reported to the IAB donor CU of the IAB node. For example, refer to Figure 4 , the IAB node 470 may report the existence of the new cell served by the IAB node 450 to its IAB donor CU 401 through a measurement report. Based on the analysis of the measurement report (e.g., the measurement result in the report indicates that the signal strength provided by the IAB node 450 is higher than the threshold for supporting communication), the IAB donor CU 401 may request the IAB donor CU 402 to which the IAB node 450 belongs to establish dual connectivity for the IAB node 470 with the additional connection through the IAB node 450. The IAB donor CU 402 may accept the request and continue to establish the connection of the IAB node 470 to the IAB node 450 according to the procedure described in Section 10.2 of TS37.340v17.0.0. As a result, the IAB node 470, which still belongs to the IAB topology 4001, is now also connected to the IAB node 450 belonging to the IAB topology 4002, and thus the IAB node 470 may be referred to as a boundary node between the IAB topology 4001 and the IAB topology 4002. In practice, IAB node 470 retains an F1 connection and an RRC connection to IAB donor CU 401 (which may be referred to as an F1 terminated IAB donor CU), and IAB node 470 has a second RRC connection with IAB donor CU 402 (which may be referred to as a non-F1 terminated IAB donor CU).

[0104] Since the IAB node or border node 470 is part of the IAB topology 4001 (from the perspective of the F1 connection), the IAB node or border node 470 is controlled (e.g., configured and / or managed) by the IAB donor CU 401 of the IAB topology 4001. Through the second RRC connection, the IAB donor CU 402 assigns a second BAP address to be used for routing packets through the IAB topology 4002. Thus, the IAB node 470 acting as a border node is assigned two BAP addresses: one BAP address for the IAB network 4001 and one BAP address for the IAB network 4002. Such a border node can help provide network path diversity by providing alternative routing paths through the IAB topologies 4001 and 4002.

[0105] Since IAB node 470 is a mobile IAB node (e.g., it is mounted on a vehicle), IAB node 470 will not always be stationary and will move, so that the connection to IAB nodes 430 and 450 may change over time. For example, if the movement of IAB node 470 is small, so that IAB node 470 and IAB nodes 430 and 450 are still close enough to each other to meet the minimum requirements to support communication (e.g., signal strength is above a threshold), then the connection to IAB nodes 430 and 450 may not change. However, if the movement of IAB node 470 causes IAB node 470 to move away from the cell associated with IAB node 430 and / or move away from the cell associated with IAB node 450, IAB node 470 may lose the connection with IAB node 430 and / or IAB node 450, respectively. In this case, the connection to the IAB node should be managed as the IAB node moves to avoid losing the connection to the wireless device connected to IAB node 470 (e.g., such as Figure 4 430 and UE 390). For example, to ensure continuity of service, a handover process may be initiated so that one or more connections of IAB node 470 (e.g., to IAB node 430) within the IAB communication system are handed over to a different cell. As described in the introduction, the use of mobile IAB nodes helps increase connectivity (e.g., capacity) in a wireless communication system, but the connection (or connections) to the mobile IAB node will need to be managed to account for the movement of the mobile IAB node.

[0106]

[0046] A process for managing one or more network connections in a wireless communication system including one or more mobile IAB nodes will now be described according to some embodiments of the present invention.

[0107] Fig.11The steps of an example method 1100 for managing network connectivity in a wireless communication system including at least one mobile integrated access and backhaul (mIAB) node according to an embodiment of the present invention are shown. The method 1100 may be used to manage a connection to a network (e.g., to a mobile integrated access and backhaul (mIAB) node) via or through the mIAB node. Figure 4 connection to the IAB network system or NG RAN (which provides connectivity towards the core network). Fig.11 The method 1100 is performed at the mAB node. Figure 4 As shown in and for Figure 4 In the wireless communication system, the mIAB node performing the method 1100 may be an IAB node 470 of an IAB topology 4001 controlled by an IAB donor CU 401. Fig.11 As shown in and for Fig.11 The method 1100 may be performed by software components and / or hardware components. Fig.10 As shown and referenced in Fig.10 The communication device 1000 is implemented as follows: Fig.11 As shown in and for Fig.11 The method described is performed by one or more processing units (such as central processing unit 1011, etc.).

[0108] In short, in step 1101, the mIAB node (e.g., IAB node 470) provides a mobility message to the wireless communication device, wherein the mobility message includes at least one of the following items: mobility profile information indicating the mobility capability of the mIAB node; guaranteed static time information indicating the minimum time period for the mIAB node to remain at a certain location. The wireless communication device may be an IAB donor node (e.g., an IAB donor CU) or a UE or another IAB node. More generally, the mIAB node may be a network node that can be moved in a communication network, and the wireless communication device may be a control node or a UE or another network node (e.g., a control network node) for managing the control plane and data plane of the wireless communication system. The following description also applies to this more general scenario.

[0109] In an example, the mobility profile information may include at least one of the following items: speed information indicating the speed capability of the mIAB node; range information indicating the mobility area of ​​the mIAB node; static information indicating the duration of one or more static periods that the mIAB node can experience; itinerary information indicating the sequence of mobility periods and static periods of the itinerary that the mIAB node can follow. The speed information may include one or more information indicating the minimum speed capability of the mIAB node, the average speed capability of the mIAB node, and the maximum speed capability of the mIAB node. The range information may include information indicating the area in which the mIAB node can move or the range of movement of the mIAB node. For example, the range information may include the type or category of the mobility area in which the mIAB node can move, and the mobility area may be an indication of the size or nature of the geographical area in which the mobile IAB node can move. For example, the type (or category) of the mobility area may indicate that the geographical area is a bus route, a train route, or a parking lot. The range information may additionally or alternatively include the size of the area (i.e., the mobility area) in which the mIAB node can move and / or a list of cell identifiers (IDs) of cells that the mIAB node can access or has previously visited. The range information may additionally or alternatively include the distance that the mIAB node can move. The static information may include static time information for indicating one or more of the minimum static period duration, the average static period duration, or the maximum static period duration. The static information may also include static location information for indicating the location where the mIAB will be static. The trip information may include information for indicating the duration of the period, the speed of the mIAB node during one or more mobility periods in the mobility period, and the location of the mIAB node during one or more static periods in the static period for each period in the mobility period and the static period.

[0110] Mobility profile information can be configured in the mAB node at the time of setting or subsequently. For example, the mobility profile information can be stored in the memory (such as ROM 1007 or data storage component 1004, etc.) of the mAB node. Setting can occur in the factory, or occur as part of the process of assembling the mAB node on a vehicle when the mAB node is a vehicle-mounted repeater (VMR). The mobility profile information can then be configured or updated based on some or known changes in the mobility of the mAB node (which can depend on some or known changes in the mobility of the vehicle equipped with the mAB node). The mobility profile information can be configured or updated based on tracking of previous movements of the mAB node and / or the vehicle equipped with or to be equipped with the mAB node.

[0111] It is ensured that static time information (or minimum static time information) indicates the minimum time period that the mIAB node remains at a certain place. For example, the information indicates that the mIAB node will remain static for the actual time period at a certain place for the currently static mIAB node. Thus, it is ensured that the static time information corresponds to the dynamic parameter. For example, for the mIAB node mounted on the train currently parked in the station, based on the train schedule and / or the route information of the train (for example, it is provided in the mobility profile information), it is ensured that the static time information can indicate the minimum time that the mIAB node will remain static. It is ensured that the static time information can be determined by the mIAB node when the mIAB is stationary based on the mobility profile information, and can be included in the mobility message. Thus, whenever the mIAB node is stationary at a certain place and the mIAB node determines that the mIAB node will remain static or static for the actual time period at the place, a mobility message including the guaranteed static time information can be provided.

[0112] The mobility message provided by the mIAB node may also include at least one of mobile node indication information indicating whether the mIAB node is a mobile IAB and mobility status indication information indicating the current status of the mobility of the mIAB node. The current status of mobility may include whether the mIAB node is currently moving or stationary, and may also include additional information related to the nature of the movement, such as the current speed, whether the mIAB node is accelerating or decelerating, etc.

[0113] In an example, the mAB node obtains (eg, from a memory) mobility profile information and / or static time information, and generates a mobility message based on the obtained information.

[0114] By providing mobility profile information and / or ensuring static time information (e.g., at setup and / or after establishing one or more connections to a mobile IAB node), a receiving wireless communication device (such as an IAB donor CU, a UE, or another IAB node, etc.) can receive information related to the mobility capabilities and / or current mobility conditions of the mobile IAB node and act accordingly using the additional information related to the mobility of the mobile IAB node. For example, the UE or another IAB node can decide not to initiate a call to a network (e.g., via or through the mobile IAB node) based on the provided information. Figure 4The UE or another IAB may decide to initiate a connection via a mobile IAB node, but may also initiate a cell search process to find another IAB node to connect to the network. In another example, due to the mobility of the mobile IAB node, the IAB donor CU may decide not to accept a connection request from the new IAB node (or UE) for a connection via a mobile IAB node. For example, in the case where the new UE / IAB node is a legacy device, the IAB donor CU may prevent the new UE / IAB node from connecting to the network via a mobile IAB node (this is referred to below in Figure 8 In another example, when a mobility message is provided after a connection is established, and the information in the mobility message indicates a change in the mobility of the mobile IAB node (e.g., a change in the mobility status and / or mobility capabilities of the mobile IAB (e.g., a change in the guaranteed static time information)), the wireless communication device may act accordingly using the additional information related to the mobility of the mobile IAB node. For example, if the change is significant, the IAB donor CU may decide to release the established connection.

[0115] The mobility message may be a mobility indication message (e.g., mobility indication message 521 as described in more detail below) provided or sent by the mIAB node to the IAB donor node (such as the IAB donor CU 401, etc.). The IAB donor node that receives the mobility message from the mIAB node (such as the IAB node 470, etc.) may be an IAB donor CU connected to the mIAB node: for example, an IAB donor CU that is connected to and is controlling the mIAB node (such as the IAB donor CU 401 that controls the IAB node 470, etc.), or when the mIAB node acts as a border node, the IAB donor CU may be one or more IAB donor CUs to which the mIAB node is connected (such as the IAB donor CUs 401 and / or 402 that are connected to the IAB node 470 when the IAB node acts as a border node, etc.). Additionally or alternatively, the mobility message may be a mobility information message (e.g., mobility information message 531 as described in more detail below) provided or sent by the mIAB node to one or more other IAB nodes (such as IAB nodes 430, 450, etc.) or one or more UEs (such as UE 390, etc.). For example, the mIAB node (such as IAB node 470, etc.) may send a mobility indication message to an IAB donor CU (such as IAB donor CU 401, etc.) connected to the mIAB node, and may also send a mobility information message to one or more other IAB nodes and / or one or more UEs.

[0116] The mobility indication message provided by the mIAB node to the IAB donor node may also include at least one of mobile node indication information indicating whether the mIAB node is a mobile IAB and mobility status indication information indicating the current status of the mobility of the mIAB node. The current status of mobility may include whether the mIAB node is currently moving or stationary, and may also include additional information related to the nature of the movement, such as the current speed, whether the mIAB node is accelerating or decelerating, etc.

[0117] In response to one of the following events, the mIAB node may provide a mobility indication message to the IAB donor node (e.g., the IAB donor CU 401 when the mIAB node is the IAB node 470 controlled by the IAB donor CU 401, etc.): 1) the mIAB node initiates an IAB node setup procedure (such as a connection establishment procedure (e.g., an RRC connection establishment procedure as specified in 3GPP TS 38.331 and 3GPP TS 38.401, or an F1 setup procedure, as described below for Figure 5 and Figure 6 1) after the mIAB node determines a change in the mobility of the mIAB node (e.g., there is a change in mobility status and / or a change in mobility capability, such as a change in speed, etc., and / or there is a change in mobility profile information, such as a change in itinerary, etc., and / or there is a change in guaranteed static time information, such as when the mIAB stops at a certain location and the mIAB determines a new time period for how long the mIAB will remain static at the location); 2) in response to the mIAB node determining a change in the mobility of the mIAB node (e.g., there is a change in mobility status and / or a change in mobility capability, such as a change in speed, etc., and / or there is a change in mobility profile information, such as a change in itinerary, etc.); 3) after a certain time period has expired since the last time the mobility indication message was sent, the time period may be the same or variable between transmissions, so that the mobility indication message is provided periodically; 4) in response to a request from an IAB donor node (such as the IAB donor CU 401, etc.). For example, as described in more detail below, the IAB donor node may send a request for the latest mobility status information, and in response to the request, provide a mobility indication message including the latest mobility status information (e.g., the latest mobility profile information and / or guaranteed static time information and may also include mobility status indication information).

[0118] The mobility information message provided (e.g., sent) by the mIAB node to one or more UEs (such as UE 390, etc.) and / or one or more other IAB nodes (such as IAB nodes 430, 450, 460, 480, etc.) may be provided in response to one of the following events: 1) during an IAB node setup procedure (e.g., an RRC connection establishment procedure or an F1 setup procedure, as described below for Figure 5 and Figure 61) after the mIAB node determines a change in the mobility of the mIAB node (e.g., there is a change in the mobility condition and / or mobility capability, such as a change in speed, etc., and / or there is a change in the mobility profile information, such as a change in itinerary, etc., and / or there is a change in the guaranteed static time information, such as when the mIAB stops at a certain location and the mIAB determines a new time period for how long the mIAB will remain static at that location); 2) in response to the mIAB node determining a change in the mobility of the mIAB node (e.g., there is a change in the mobility condition and / or mobility capability, such as a change in speed, etc., and / or there is a change in the mobility profile information, such as a change in itinerary, etc., and / or there is a change in the guaranteed static time information, such as when the mIAB stops at a certain location and the mIAB determines a new time period for how long the mIAB will remain static at that location); 3) after a certain time period has expired since the last time the mobility information message was sent, the time period can be the same or variable between transmissions, so that the mobility information message is provided periodically.

[0119] By providing or sending a mobility information message with mobility profile information and / or guaranteed static time information, the mIAB node can notify one or more UEs and one or more other IAB nodes near the mIAB node of its mobility capabilities and / or status. Upon receiving the mobility information provided in the mobility information message, the UE and / or other IAB nodes can determine how to act based on the mobility of the mIAB node as indicated by the provided mobility information. Using additional information related to the mobility capabilities of the mIAB node and / or guaranteed static time information, the UE and / or other IAB nodes have additional information and can therefore act more effectively. For example, the UE and / or another IAB node may decide not to connect to the network via the mIAB node due to the mobility of the mIAB node, or may decide to connect regardless of the mobility of the mIAB node (for example, because the information indicates that the mIAB node is traveling slowly or in a restricted area). In another example, in the case where the UE and / or another IAB node is already connected, the UE and / or another IAB node may decide to initiate a cell search process to find another IAB node to be connected to or handed over to.

[0120] The mIAB node may provide mobility information messages to one or more UEs (such as UE 390, etc.) and / or one or more other IAB nodes (such as IAB nodes 430, 450, 460, 480, etc.) by broadcasting: for example, in a SIB1 message.

[0121] The mobility information message provided by the mIAB node to one or more UEs and / or one or more other IAB nodes may also include a connectivity support indicator (also referred to as an IAB support indicator or IAB support information or connectivity support information) for indicating whether the mIAB node can support network connectivity for a wireless communication device (such as a UE or another IAB node, etc.). The ability of the mIAB node to support network connectivity for other wireless communication devices (e.g., whether a reliable radio link can be established and maintained between the mIAB node and the other wireless communication devices) will depend on the mobility of the mIAB node (e.g., the mobility capability and / or current mobility status of the mIAB node). In some cases, the mobility of the mIAB node may mean that the mIAB node cannot support network connectivity. In an example, when the mIAB node can support network connectivity, the mIAB node sets or enables a connectivity support indicator or IAB or connectivity support information by including the IAB support information or connectivity support information in a mobility information message (e.g., in a field of the mobility information message) to indicate that the mIAB node can support network connectivity. The IAB or connectivity support information may include information for indicating that the mIAB node can support network connectivity and / or that the cell associated with the mIAB node can be considered as a candidate for cell (re)selection. When the mIAB node cannot support network connectivity, the mIAB node does not set or disable the connectivity support indicator or the IAB or connectivity support information by not including the IAB support information or the connectivity support information in the mobility information message to indicate that the mIAB node cannot support network connectivity. For example, when the mIAB node can support network connectivity, the fields indicating both the support and the cell status of the mIAB node are included in the mobility information message, and when the mIAB node cannot support network connectivity and / or the cell associated with the mIAB node is prohibited from being used for wireless communication devices, the field is not included. Therefore, the presence or absence of the field in the mobility information message provided by the mIAB node indicates whether network connectivity is supported, respectively. In other words, the mIAB node performs conditional IAB support management to determine whether the mIAB node can support network connectivity, and includes or does not include the IAB support information in the mobility information message based on the determination. In an alternative arrangement, the mobility information message may include a connectivity support indicator, which may be set to one value indicating that the mIAB node cannot support network connectivity and another value indicating that the mIAB node can support network connectivity.

[0122] The mIAB node may determine whether it can support network connectivity based on the mobility of the mIAB node (e.g., based on the mobility capabilities of the mIAB node (e.g., as indicated in the mobility profile information of the mIAB node), and / or the guaranteed static time information and / or current mobility status of the mIAB node), and therefore determine whether the mIAB node is to set a connectivity support indicator or IAB support information or connectivity support information. As described above, the mobility profile information and / or guaranteed static time information and any subsequent updates (if necessary) may be stored in the IAB node (e.g., at the time of setup or subsequently) and used to determine whether the IAB node can support network connectivity.

[0123] In another arrangement, an IAB donor node (such as IAB donor CU 401, etc.) connected to an IAB node (e.g., an IAB node 470 managed by an IAB donor CU 401) may determine whether the mIAB node can support network connectivity based on the mobility of the mIAB node, and thus determine whether the mIAB node is to set a connectivity support indicator or IAB support information or connectivity support information (e.g., whether to include a field with IAB or connectivity support information in a mobility information message). The IAB donor node may determine the mobility of the mIAB node based on mobility information (such as mobility profile information and / or guaranteed static time information) received from the mIAB node. The mobility information may be provided by the mIAB node to the IAB donor node when the IAB node is set up or subsequently in a mobility indication message as described above, and based on the mobility information provided in the mobility indication message, the IAB donor node may determine whether the mIAB node can support network connectivity, and may send a connectivity or IAB support configuration message (e.g., as described below with reference to FIG. 1 ) to the mIAB node indicating whether the mIAB node can support network connectivity. Figure 5 The mIAB node may then determine whether it can support network connectivity based on the received connectivity or IAB support configuration message, and thus determine whether the mIAB node is to set a connectivity support indicator or IAB support information or connectivity support information.

[0124] In response to determining that the mIAB node can support network connectivity, the mIAB node may provide a mobility information message including IAB support information to indicate that the IAB node can support network connectivity for the wireless communication device.

[0125] In an example, when the mIAB node or IAB donor node determines that the mIAB node is static or will be static for a period of time greater than a certain threshold (e.g., the threshold can be as low as tens of seconds) or when the mIAB node is moving with limited mobility, it is determined that the mIAB node can support network connectivity. The mobility of the mIAB node is limited when at least one of the following criteria or conditions is met: the speed of the mIAB node is lower than a certain threshold (e.g., the actual speed of the mIAB node (e.g., as indicated by the speed-related information in the mobility status indication information or the mobility profile information) is lower than a predefined threshold); the mobility area in which the mIAB node is moving or will move is geographically restricted; the mobility area is within a topology or a network cell (e.g., the information in the mobility profile information indicates that the mIAB node remains under the same topology or the same network cell). The geographically restricted mobility area may include an area in which the mIAB node is moving or will move and whose size is lower than a certain or predefined threshold, or may include an area having a type or category belonging to a type or category that is considered to be geographically restricted (i.e., having a size lower than a certain threshold). Such types or categories of restricted size may include parking lots.

[0126] In another example, when it is determined that the mlAB node is moving or is a mobile node (ie, has the capability to move), it is determined that the mlAB node cannot support network connectivity.

[0127] The mobility information message may also include at least one of the following items: mobile node indication information, used to indicate whether the mIAB node is a mobile IAB node; mobility status indication information, used to indicate the current status of the mobility of the mIAB node; mobile IAB cell indication information, used to indicate the cell associated with the mobile IAB node (for example, the cell ID may be included in the mobility information message). The current status of mobility may include whether the mIAB node is currently moving or stationary, and may also include additional information related to the nature of the movement, such as the current speed and / or whether the mIAB node is accelerating or decelerating, etc.

[0128] More details on the mobility indication message sent to the IAB donor node and the mobility information message sent to other IAB nodes or UEs are given below.

[0129] Now also refer to Fig.12 , Fig.12The steps of an example method 1200 performed at a wireless communication device upon receiving a mobility information message sent by an IAB node of a wireless communication system according to an embodiment of the present invention are shown, wherein the IAB node is controlled by an IAB donor node. The method 1200 may be used to manage network connectivity in a wireless communication system including at least one mobile integrated access and backhaul (mIAB). The wireless communication device performing the method 1200 may be another IAB node or a UE in the wireless communication system, either of which may be operating in the vicinity of the IAB node so that they receive the mobility information message. For example, referring to Figure 4 As shown in and for Figure 4 In the wireless communication system, the wireless communication device performing the method 1200 may be an IAB node 460 of an IAB topology 4001 controlled by an IAB donor CU 401 or an IAB node 440 of an IAB topology 4002 controlled by an IAB donor CU 402, or a UE 390, and the IAB node providing the mobility message may be a mobile IAB node (an IAB node 470 controlled by an IAB donor CU 401). Fig.12 As shown in and for Fig.12 The method 1200 may be performed by software components and / or hardware components. The wireless communication device performing the method 1200 may be configured as follows: Fig.10 As shown and referenced in Fig.10 The communication device 1000 is implemented as follows: Fig.12 As shown in and for Fig.12 The method described is performed by one or more processing units (such as central processing unit 1011, etc.).

[0130] Briefly, at step 1201, a wireless communication device receives a mobility information message from an IAB node. Then, at step 1202, the wireless communication device takes action based at least in part on information provided by the received mobility information message. The IAB node that sends the mobility information message may be a mobile IAB node or a fixed IAB node (in the sense that the IAB node is fixed in one location).

[0131] When the IAB node is a mobile IAB node (mIAB node), the mobility information message includes at least one of the following items: mobility profile information indicating the mobility capability of the IAB node; guaranteed static time information indicating the minimum time period for the IAB node to remain at a certain location. The mobility profile information may include at least one of the following items: speed information indicating the speed capability of the IAB node; range information indicating the mobility area of ​​the IAB node; static information indicating the duration of one or more static periods that the IAB node can experience; itinerary information indicating the sequence of mobility periods and static periods of a itinerary that the mIAB node can follow. The mobility information message may also include at least one of the following items: mobile node indication information, used to indicate whether the IAB node is a mobile IAB node; mobility status indication information, used to indicate the current status of the mobility of the IAB node; mobile IAB cell indication information, used to indicate that the cell is associated with the mobile IAB node (for example, the cell ID is included in the mobility information message); IAB support information or connectivity support information (also called connectivity indicator), used to indicate whether the IAB node can support network connectivity for a wireless communication device (such as a UE or another IAB node, etc.). Fig.11 Further details are given of the mobility information included in the mobility information message provided by the IAB node and received at the wireless communication device.

[0132] When the IAB node is a fixed IAB node, the mobility information message may include mobile node indication information for indicating that the IAB node is not a mobile IAB node.

[0133] Upon receiving the mobility information provided in the mobility information message, the UE and / or other IAB nodes may determine how to act based on the mobility of the mIAB node as indicated by the provided mobility information. With the additional information about the mobility capabilities of the mIAB node and / or the guaranteed static time information, the UE and / or other IAB nodes have additional information and may therefore act more effectively as described above.

[0134] In an example, performing actions at step 1202 may include: determining whether to initiate a connection establishment procedure or to set up a connection to a network (eg, Figure 4The wireless communication device may determine not to initiate a connection establishment process when the information provided by the mobility information message indicates that the IAB node is a mobile IAB node. The wireless communication device may determine to initiate a connection establishment process when the information provided by the mobility information message indicates that certain criteria are met. Certain criteria include: 1) the IAB node is not a mobile IAB node; 2) the IAB node is a mobile IAB node and is static or will be static for a time period greater than a certain threshold; 3) the IAB node is a mobile IAB node and is moving with restricted mobility. As described above, the criteria for restricted mobility include: the speed of the mIAB node is lower than a certain threshold; the mobility area is geographically restricted; the mobility area is within a topology or a network cell.

[0135] When the wireless communication device determines to initiate a connection establishment process, the actions at step 1202 may also include: sending a request to an IAB donor node (e.g., IAB donor CU 401) via an IAB node (e.g., IAB node 470) to request to establish a connection via the IAB node (IAB node 470). The request is sent as part of a connection establishment process (such as an RRC connection establishment process, etc.). When the wireless communication device is a UE (such as UE 390, etc.), the requested connection is an IAB topology (e.g., topology 4001 managed by donor CU 401) using an IAB node (IAB node 470) managed by the IAB donor node, and when the connection process is completed, the UE will be connected to the IAB node (IAB node 470) via a communication link or a radio link. When the wireless communication device is an IAB node (such as IAB node 460), the requested connection is an IAB topology (e.g., topology 4001 managed by donor CU 401) using an IAB node (IAB node 470) managed by an IAB donor node, and when the connection process is completed, the IAB node (such as IAB node 460) or other IAB nodes will be connected to the IAB node (IAB node 470) via a backhaul (BH) communication link or a BH link. In response to the request, the wireless communication device receives a configuration message from the IAB donor node (e.g., donor CU 401). For example, as specified in 3GPP TS 38.331, the configuration message received at the wireless communication device (UE or IAB node) to indicate that the connection via the IAB node has been accepted may be an RRCSetup message, or the configuration message to indicate that the connection via the IAB node has been rejected may be an RRCReject message instead of an RRCSetup message. In the case where the wireless communication device is an IAB node (such as IAB node 460) and after the IAB node 460 is connected to the IAB node 470, the configuration message may indicate that the BH link between the IAB node and the mobile IAB node has been rejected or configured, and in this case, the configuration message may be an RRCReconfiguration message (such as RRCReconfiguration) as defined in 3GPP TS38.331. Figure 7 CONFIGURATION INFORMATION message 732, etc.)

[0136] In an example, when the connection via the IAB node is rejected because the IAB node is a mobile IAB node or the cell associated with the IAB node (or the requested connection cell) is a mobile cell, the configuration message includes IAB configuration rejection cause information, which is used to indicate why the connection has been rejected (for example, indicating that the connection has been rejected because the IAB node is a mobile IAB node or the cell associated with the IAB node (or the requested connection cell) is a mobile cell). As shown below for Figure 7 In more detail, when the UE sends a request to establish a connection via an IAB node as part of a connection establishment procedure, the rejection cause information may include MobileCellConnectionReject or mobile cell connection rejection information, which indicates to the UE that the connection request is rejected because the UE attempts to connect to the network via a mobile IAB node. Figure 7 In more detail, when the IAB node sends a request to establish a connection via the IAB node as part of the connection establishment process, the rejection cause information may include iab-configRejectCause or IAB configuration rejection cause information. The configuration message may also include an IAB configuration rejection information indication that the connection has been rejected.

[0137] When the connection via the IAB node has been accepted, the configuration message includes an IAB configuration acceptance information indication that the connection has been accepted. When the IAB node is a mobile IAB node, whether the connection via the IAB node has been accepted or rejected, the configuration message can include mobility profile information for indicating the mobility capabilities of the IAB node. The details of the mobility profile information are discussed above. Such cause information and (if provided) mobility profile information can help the wireless communication device efficiently determine what to do next: for example, without using resources to try to connect to the mobile IAB node again, select an alternative IAB node through which to try to establish a connection; or if the provided information indicates that the mobile IAB node will move slowly or in a restricted area, the wireless communication device can try to establish a connection via the mobile IAB node again.

[0138] When the IAB node is a mobile IAB node and the wireless communication device is another IAB node (eg, a child IAB node), the configuration message may further include mobile parent IAB node indication information indicating that the parent IAB node is a mobile IAB node and the associated cell is a mobile cell.

[0139] When the wireless communication device is another IAB node (i.e., a child IAB node) connected to an IAB node (i.e., a parent IAB node) (e.g., the MT portion of the IAB node 460 is connected to the DU portion of the IAB node 470 after the connection establishment process is completed), performing an action may include: providing a mobility capability message (such as the following reference 1 to the example embodiment) based on information provided by a received mobility information message received from the IAB node. Figure 5 The mobility capability message includes information indicating the mobility capability of the IAB node. Based on the information provided by the received mobility information message received from the IAB node, the mobility capability message includes information indicating the mobility capability of the IAB node. The mobility capability message can be sent (for example, via broadcast) to all nodes (for example, UE and IAB node) near the child IAB node. The mobility capability message may include all or part of the information received from the IAB node in the mobility information message, such as the mobility profile information and / or the guaranteed static time information as described above, and / or the mobile node indication information and / or the mobility status indication information and / or the IAB support information, etc. In addition, the mobility capability message may also include identifier information for identifying the IAB node, such as the unique BAP address of the IAB node, etc. If the IAB node is a border node, the BAP address included in the mobility capability message is a BAP address configured by the IAB donor CU controlling the sub IAB node (ie, a BAP address of the same topology to which the sub IAB node belongs).

[0140] When the wireless communication device is another IAB node (i.e., a child IAB node) connected to an IAB node (i.e., a parent IAB node) (e.g., the MT portion of the IAB node 460 is connected to the DU portion of the IAB node 470 after the connection establishment process is completed), the action may include: determining a radio link failure, i.e., RLF, for a radio link (i.e., a BH link) with the parent IAB node based on information provided by a received mobility information message, and sending an RLF indication message. The RLF indication message includes information indicating that the cause of the RLF is related to the mobility of the parent IAB node. For example, the information provided by the received mobility information message may indicate that the parent IAB node is a mobile IAB node, or has recently become a mobile IAB node, or was previously a mobile IAB node but has recently changed its mobility status or capabilities (e.g., is moving out of range) so that an RLF occurs on the BH link between the child IAB node and the parent IAB node. The RLF indication message will be received by the child IAB node(s) of the child IAB node (which is now acting as the parent node), and the child IAB node(s) may act accordingly.

[0141] Another example method performed at a wireless communication device in a wireless communication system according to an embodiment of the present invention will now be described. The wireless communication system also includes an IAB node controlled by an IAB donor node. As with the previous method, the method can be used to manage network connectivity in a wireless communication system including at least one mobile integrated access and backhaul (mIAB) node. The wireless communication device can be another IAB node in the wireless communication system, or a UE. The wireless communication device decides to initiate a connection establishment procedure to connect to a network (e.g., Figure 4 IAB network system or NG RAN): For example, the wireless communication device is operating in the vicinity of an IAB node, or was operating in the vicinity of an IAB node that has now moved at some previous time. For example, refer to Figure 4 As shown in and for Figure 4 In the wireless communication system, the wireless communication device may be an IAB node 460 of an IAB topology 4001 controlled by an IAB donor CU 401 or an IAB node 440 of an IAB topology 4002 controlled by an IAB donor CU 402, or a UE 390, and the IAB node through which the wireless communication device wishes to connect may be a mobile IAB node (an IAB node 470 controlled by an IAB donor CU 401). The method may be performed by software components and / or hardware components. The wireless communication device performing the method may be configured as follows: Fig.10 As shown and referenced in Fig.10 The communication device 1000 is implemented, wherein the method is performed by one or more processing units (such as a central processing unit 1011, etc.).

[0142] The wireless communication device sends a request to an IAB donor node (e.g., IAB donor CU401) via an IAB node (e.g., IAB node 470) to request establishment of a connection via the IAB node (IAB node 470). The request is sent as part of a connection establishment process (such as an RRC connection establishment process, etc.). In response to the request, the wireless communication device receives a configuration message from the IAB donor node (e.g., donor CU 401). As described below, the configuration message may be an RRCSetup message or an RRCReject message or an RRCReconfiguration message. In the example, when a connection to an IAB node has been rejected, the configuration message includes IAB configuration rejection reason information indicating why the connection has been rejected (e.g., indicating that the connection has been rejected because the IAB node is a mobile IAB node or the cell associated with the IAB node (or the requested connection cell) is a mobile cell). As described below for Figure 7In more detail, when the UE sends a request to establish a connection via an IAB node as part of a connection establishment procedure, the rejection cause information may include MobileCellConnectionReject or mobile cell connection rejection information, which indicates to the UE that the connection request is rejected because the UE attempts to connect to the network via a mobile IAB node. Figure 7 In more detail, when the IAB node sends a request to establish a connection via the IAB node as part of the connection establishment process, the rejection cause information may include iab-configRejectCause or IAB configuration rejection cause information. The configuration message may also include an IAB configuration rejection information indication that the connection has been rejected.

[0143] When the connection to the IAB node has been accepted, the configuration message includes IAB configuration acceptance information indicating that the connection has been accepted (e.g., the BH link has been configured). When the IAB node is a mobile IAB node, whether the connection to the IAB node has been accepted or rejected, the configuration message may include mobility profile information indicating the mobility capabilities of the IAB node. The details of the mobility profile information are discussed above. The benefits of providing such reason information and (if provided) the mobility profile information are discussed above.

[0144] When the IAB node is a mobile IAB node and the wireless communication device is another IAB node (eg, a child IAB node), the configuration message may further include mobile parent IAB node indication information indicating that the parent IAB node is a mobile IAB node and the associated cell is a mobile cell.

[0145] Now also refer to Fig.13 , Fig.13 The steps of an example method 1300 performed at an IAB donor node of a wireless communication system upon receiving a mobility indication message sent by an IAB node according to an embodiment of the present invention are shown, wherein the IAB node is connected to an IAB donor node. The IAB donor node may be an IAB donor CU that is connected to the IAB node and controls the IAB node (such as IAB donor CU 401 that controls IAB node 470, etc.), or when the IAB node acts as a border node, the IAB donor CU may be one or more IAB donor CUs to which the IAB node is connected (such as IAB donor CU 401 and / or 402 that are both connected to IAB node 470 when IAB node 470 acts as a border node, etc.). Method 1300 may be used to manage network connectivity in a wireless communication system including at least one mobile integrated access and backhaul (mIAB). The IAB donor node may be an IAB donor CU. For example, referring to Figure 4 shown in and for Figure 4 In the wireless communication system, the IAB donor node may be the IAB donor CU 401, and the IAB node may be the IAB node 470 controlled by the IAB donor CU 401. Fig.13 As shown in and for Fig.13 The method 1300 may be performed by software components and / or hardware components. The IAB donor node performing the method 1300 may be configured as follows: Fig.10 As shown and referenced in Fig.10 The communication device 1000 is implemented as follows: Fig.13 As shown in and for Fig.13 The method described is performed by one or more processing units (such as central processing unit 1011, etc.).

[0146] In brief, at step 1301, the IAB donor node receives a mobility indication message from an IAB node. Then, at step 1302, the IAB donor node performs an action based at least in part on information provided by the received mobility indication message. The mobility indication message is received at a CU portion of the IAB donor node (i.e., the IAB donor CU), and the IAB donor CU performs an action. For example, the IAB donor CU 401 receives a mobility indication message from the IAB node 470.

[0147] The mobility indication message includes at least one of the following items: mobility profile information indicating the mobility capability of the IAB node; guaranteed static time information indicating the minimum time period for the IAB node to remain at a certain location. The mobility profile information may include at least one of the following items: speed information indicating the speed capability of the IAB node; range information indicating the mobility area of ​​the IAB node; static information indicating the duration of one or more static periods that the IAB node may experience; itinerary information indicating the sequence of mobility periods and static periods of a itinerary that the IAB node may follow.

[0148] The mobility indication message may also include at least one of the following items: mobile node indication information, used to indicate whether the IAB node is a mobile IAB node; mobility status indication information, used to indicate the current status of the mobility of the IAB node. Fig.11 More details are given of the information included in the mobility indication message provided by the IAB node and received at the IAB donor node (eg, mobility profile information, guaranteed static time information, etc.).

[0149] Upon receiving the mobility information provided in the mobility indication message, the IAB donor node or IAB donor CU may determine how to act based on the mobility of the IAB node as indicated by the provided mobility information. With the additional information about the mobility capabilities of the IAB node and / or the guaranteed static time information, the IAB donor node has additional information and may therefore act more effectively as described above.

[0150] In an example, performing actions at step 1302 may include: sending, by the IAB donor node, a notification message for indicating that the IAB node is a mobile IAB node based on information provided in the mobility indication message to one or more of the following: another IAB node (e.g., IAB node 430); a UE (e.g., UE 390); a CU of an IAB donor node of another IAB topology different from the topology controlled by the IAB donor node (e.g., IAB donor CU 401 sends a notification to IAB donor CU 402 of IAB topology 4002). By sending the notification, the IAB donor node can provide other wireless communication devices in the wireless communication system with information related to the mobility of the IAB node, which can help other devices act accordingly. By providing a notification message indicating the mobility of the IAB node to the CU of the IAB donor node of another IAB topology (e.g., the IAB donor CU 402), if the IAB node moves into the coverage of another IAB topology (e.g., the IAB node 470 moves into the coverage of the IAB topology 4002), the mobility information can be used by the IAB donor CU of the other topology to manage the migration of the IAB node to the other topology.

[0151] The IAB donor node may receive the mobility indication message as part of an IAB node setup procedure with the IAB node (e.g., an RRC connection establishment procedure as specified in 3GPP TS 38.331, or an F1 setup procedure, as described below for Figure 5 and Figure 6As described in more detail below). Alternatively or additionally, the IAB donor node may receive the mobility indication message in response to a message sent by the IAB donor node. For example, as described in more detail below, the IAB donor node may send a request for the latest mobility status information and provide a mobility indication message including the latest mobility status information (e.g., the latest mobility profile information and / or guaranteed static time information and may also include mobility status indication information) in response to the request. Alternatively or additionally, the IAB donor node may receive the mobility indication message in response to the IAB node determining a change in mobility (e.g., there is a change in mobility status, such as a change in speed, etc., and / or there is a change in mobility profile information, such as a change in itinerary, etc., and / or there is a change in guaranteed static time information). Alternatively or additionally, the IAB donor node may periodically receive the mobility indication message from the IAB node, wherein the time between receipts of the mobility indication messages is the same or variable.

[0152] In an example, when a mobility indication message is received as part of an IAB node setup procedure, the IAB donor node completes the IAB node setup procedure with the IAB node. The information provided in the mobility indication message is stored by the IAB donor node for use by the IAB node. When a request to establish a connection via the IAB node is subsequently received from a wireless communication device (which may be a UE or another IAB node) as part of a connection establishment procedure (e.g., an RRC connection establishment procedure), performing action 1302 may include: determining whether to accept or reject (i.e., allow or not allow) the connection via the IAB node based at least in part on the mobility of the IAB node. In response to determining whether to accept or reject the connection request, the IAB donor node then sends a configuration message to the wireless communication device (e.g., a UE or another IAB node) indicating whether the connection using the IAB node has been accepted or rejected. For example, as specified in 3GPP TS 38.331, the configuration message indicating that the connection via the IAB node has been accepted may be an RRCSetup message, or the configuration message indicating that the connection via the IAB node has been rejected may be an RRCReject message instead of an RRCSetup message. In the case where the wireless communication device is an IAB node (such as IAB node 460) and after the IAB node 460 is connected to the IAB node 470, the configuration message may indicate that the BH link between the IAB node and the mobile IAB node has been rejected or configured, and in this case, as defined in 3GPP TS 38.331, the configuration message may be an RRCReconfiguration message (such as Figure 7 CONFIGURATION INFORMATION message 732, etc.)

[0153] The IAB donor node may determine whether to accept or reject a connection via the IAB node based on information provided by a mobility indication message received at the IAB donor node (e.g., received as part of a setup process or subsequently received). As described above, the mobility indication message includes mobility profile information and / or guaranteed static time information, which may be used to determine whether to accept or reject the connection. For example, the IAB donor node may make a determination based on the mobility profile information. The mobility indication message (e.g., received as part of a setup process or subsequently received, such as received in response to a request from an IAB donor CU, received periodically from the IAB node, received when the IAB node detects a change in the mobility of the IAB node (such as a change in mobility status and / or mobility capabilities, etc.)) may additionally include mobility status information indicating the current status of the mobility of the IAB node, and in this case, the IAB donor node may determine whether to accept or reject a connection via the IAB node based on the current status of the mobility of the IAB node. In an example, the IAB donor node may determine whether to accept or reject a connection via the IAB node based on a current condition of the mobility of the IAB node and the mobility capability of the IAB node as indicated by the mobility profile information. When the IAB node is a mobile IAB node or when the IAB node is a mobile IAB node with mobility capability and / or a current mobility condition that may cause a connection problem (e.g., the area of ​​the IAB node's mobility is large, the average speed is higher than a threshold, the current speed is higher than a threshold, etc.), the IAB donor node may determine to reject the connection request.

[0154] In an example, when a connection via the IAB node has been rejected based on the mobility of the IAB node (e.g., because the IAB node is a mobile IAB node or a cell associated with the IAB node is a mobile cell), the configuration message includes IAB configuration rejection reason information indicating why the connection has been rejected (e.g., indicating that the connection has been rejected because the IAB node is a mobile IAB node or a cell associated with the IAB node is a mobile cell). Figure 7 In more detail, when the UE sends a request to establish a connection via an IAB node as part of a connection establishment procedure, the rejection cause information may include MobileCellConnectionReject or mobile cell connection rejection information, which indicates to the UE that the connection request is rejected because the UE attempts to connect to the network via a mobile IAB node. Figure 7In more detail, when the IAB node sends a request to establish a connection via the IAB node as part of the connection establishment process, the rejection cause information may include iab-configRejectCause or IAB configuration rejection cause information. The configuration message may also include an IAB configuration rejection information indication that the connection has been rejected.

[0155] When the connection via the IAB node has been accepted, the configuration message includes an IAB configuration acceptance information indication that the connection has been accepted. When the IAB node is a mobile IAB node, whether the connection via the IAB node has been accepted or rejected, the configuration message may include mobility profile information indicating the mobility capabilities of the IAB node. The details of the mobility profile information are discussed above. The benefits of providing such reason information and (if provided) the mobility profile information are discussed above.

[0156] When the IAB node is a mobile IAB node and the wireless communication device is another IAB node (eg, a child IAB node), the configuration message may further include mobile parent IAB node indication information indicating that the IAB node is a mobile parent IAB node and the associated cell is a mobile cell.

[0157] In an example, the action 1302 performed by the IAB donor node may include determining whether to enable or disable network connectivity support for the IAB node based at least in part on the mobility of the IAB node, and sending a connectivity or IAB support configuration message to the IAB node (e.g., as described below with reference to Figure 5 The RRC reconfiguration message described above), the connectivity or IAB support configuration message is used to indicate whether the IAB node can support network connectivity for the wireless communication device based on the determination. The wireless communication device can be a UE or another IAB node. The IAB donor node can make this determination based on information provided by the mobility indication message. In an example, the IAB donor node can make this determination based on the current status of the mobility of the IAB node (if the information is included in the mobility indication message) and / or the mobility capability of the IAB node as indicated by the mobility profile information and / or the guaranteed static time information. The above reference Fig.11 Further details of the connectivity or IAB support configuration messages are discussed.

[0158] The IAB donor node may determine to disable network connectivity support when the IAB node is a mobile IAB node or when the IAB node is a mobile IAB node with mobility capabilities and / or current mobility conditions that may cause connectivity issues (e.g., the area of ​​mobility of the IAB node is large, the average speed is above a threshold, the current speed is above a threshold, etc.). The IAB donor node may determine to enable network connectivity support when the IAB node is or will be static for a time period greater than a certain threshold or when the IAB node is moving with restricted mobility. In an example, the mobility of the IAB node is restricted when at least one of the following criteria or conditions is met: the speed of the IAB node is below a certain threshold; the mobility area is geographically restricted; the mobility area is within a topology or a network cell. For more details on restricted mobility criteria, see above (e.g., Fig.11 ).

[0159] In an example in which the IAB donor node receives a new mobility indication message including updated information compared to a previously received mobility indication message (e.g., mobility profile information has been updated and / or mobility status information indicating a current status of the mobility of the IAB node), performing an action may include determining whether one or more wireless communication devices (e.g., one or more UEs and / or one or more other IAB nodes) connected to the IAB node should be released based on the information provided by the new mobility indication message, and in response to determining that the one or more wireless communication devices should be released, sending a release notification to the one or more wireless communication devices.

[0160] Fig.14 The steps of an example method 1400 for managing network connectivity in a wireless communication system including at least one integrated access and backhaul (IAB) node of the wireless communication system according to an embodiment of the present invention are shown. Fig.14 Method 1400. For example, referring to Figure 4 As shown in and for Figure 4 In the wireless communication system, the IAB node performing the method 1400 may be an IAB node 470 of an IAB topology 4001 controlled by an IAB donor CU 401. Fig.14 As shown in and for Fig.14 The method 1400 described may be performed by software components and / or hardware components. Fig.10 Shown and referenced Fig.10 The communication device 1000 is implemented as follows: Fig.14 As shown in and for Fig.14 The method described is performed by one or more processing units (such as central processing unit 1011, etc.).

[0161] In brief, at step 1401, the IAB node (e.g., the IAB node 470) determines whether the IAB node can support network connectivity for a wireless communication device (e.g., another IAB node or a UE) based on the mobility of the IAB node. In response to determining that the IAB node can support network connectivity, at step 1402, the IAB node provides a mobility information message including IAB support information or connectivity support information (also referred to as an IAB support indicator) to indicate that the IAB node can support network connectivity for a wireless communication device (such as a UE or another IAB node, etc.). As described above with reference to Fig.11 As described above, the ability of the IAB node to support network connectivity for other wireless communication devices (e.g., whether a reliable radio link can be established and maintained between the IAB node and the other wireless communication devices) will depend on the mobility of the IAB node (e.g., the mobility capability and / or current mobility status of the IAB node). The mobility information message may be provided or sent to one or more wireless communication devices, such as one or more other IAB nodes or one or more UEs, etc. For example, the mobility information message may be broadcast in a SIB1 message.

[0162] The mobility information message may also include at least one of the following items: mobility profile information, used to indicate the mobility capability of the IAB node; guaranteed static time information, used to indicate the minimum time period for the IAB node to remain in a certain place; mobile node indication information, used to indicate whether the IAB node is a mobile IAB node; mobility status indication information, used to indicate the current status of the mobility of the IAB node; mobile IAB cell indication information, used to indicate that the cell is associated with the mobile IAB node (for example, the cell ID may be included in the mobility information message). In the example, the mobility profile information may include at least one of the following items: speed information, used to indicate the speed capability of the mIAB node; range information, used to indicate the mobility area of ​​the mIAB node; static information, used to indicate the duration of one or more static periods that the mIAB node can experience; itinerary information, used to indicate the sequence of mobility periods and static periods of the itinerary that the mIAB node can follow. The above for Fig.11 More details are given regarding the mobility information messages sent to other IAB nodes or UEs.

[0163] In an example, when the IAB node can support network connectivity, the IAB node sets or enables IAB support information or connectivity support information or connectivity support indicator by including the IAB support information or connectivity support information in a mobility information message (e.g., in a field of the mobility information message) to indicate that the IAB node can support network connectivity. The IAB support information or connectivity support information may include information indicating that the IAB node can support network connectivity and / or that a cell associated with the IAB node can be considered as a candidate for cell (re)selection. When the IAB node cannot support network connectivity, the IAB node does not set or disable the IAB support information or connectivity support information or connectivity support indicator of the mobility information message by not including the IAB support information or connectivity support information in the mobility information message to indicate that the IAB node cannot support network connectivity. For example, when the IAB node can support network connectivity, a field indicating both support and cell status of the IAB node is included in the mobility information message, and when the IAB node cannot support network connectivity and / or a cell associated with the IAB node is prohibited from being used by a wireless communication device, the field is not included. Therefore, the presence or absence of this field in the mobility information message provided by the IAB node indicates whether network connectivity is supported, respectively. In an alternative arrangement, the mobility information message may include a connectivity support indicator, which may be set to one value indicating that the mIAB node cannot support network connectivity and another value indicating that the mIAB node can support network connectivity.

[0164] The IAB node may determine whether it can support network connectivity based on the mobility of the IAB node (e.g., based on the mobility capabilities of the IAB node (e.g., as indicated in the mobility profile information of the IAB node) and / or the guaranteed static time information and / or current mobility conditions of the IAB node. As described above, the mobility profile information and / or the guaranteed static time information and any subsequent updates (if necessary) may be stored in the IAB node (e.g., at setup or subsequently) and used to determine whether the IAB node can support network connectivity.

[0165] In another example, the IAB node (e.g., the IAB node 470) may receive a connectivity or IAB support configuration message (e.g., described below in reference to the configuration message) indicating whether the IAB node can support network connectivity from a donor CU node (e.g., the IAB donor CU 401) connected to the IAB node (e.g., the IAB donor CU controlling the IAB node). Figure 5The IAB node determines whether the IAB node can support network connectivity based on the received connectivity or IAB support configuration message. In this example, an IAB donor node (such as IAB donor CU 401, etc.) connected to an IAB node (e.g., an IAB node 470 managed by an IAB donor CU 401) can determine whether the IAB node can support network connectivity based on the mobility of the IAB node, and thus determine whether the IAB node is to include connectivity support information in a mobility information message (e.g., whether to include a field in the mobility information message). For example, as described above with reference to Fig.11 and / or Fig.13 As described above, the IAB donor node (e.g., IAB donor CU 401) may determine the mobility of the IAB node based on the mobility information (such as mobility profile information and / or guaranteed static time information, etc.) received from the IAB node. The mobility information may be provided to the IAB donor node by the IAB node when the IAB node is set up or subsequently in a mobility indication message sent by the IAB node to the IAB donor node as described above, and based on the mobility information provided in the mobility indication message, the IAB donor node may determine whether the IAB node can support network connectivity.

[0166] In an example, the IAB node determines that the IAB node can support network connectivity when the IAB node determines that the IAB node is static or will be static for a period of time greater than a certain threshold, or when the IAB node is moving with limited mobility. The mobility of the IAB node is limited when at least one of the following criteria or conditions is met: the speed of the IAB node is below a certain threshold; the mobility area is geographically limited; the mobility area is within a topology or a network cell. For more details on the limited mobility criteria, see above (e.g., Fig.11 and / or Fig.13 ).

[0167] In another example, when it is determined that the mlAB node is moving or is a mobile node (ie, has the capability to move), it is determined that the mlAB node cannot support network connectivity.

[0168] When it is determined that the mIAB node cannot support network connectivity, although the IAB support information may be disabled or not set in the mobility information message (for example, the IAB support information is not included in the mobility information message), the mobility information message may still include at least one of the following items: mobility profile information; guaranteed static time information; mobile node indication information; mobility status indication information; mobile IAB cell indication information.

[0169] Now also refer to Figure 5 , Figure 5 is a schematic simplified diagram illustrating some example message flows for managing network connectivity in a wireless communication system including at least one IAB node according to one or more embodiments of the present invention, and can be used to manage the IAB node's announcement of its mobility capabilities and status and its ability to support IAB connections utilizing child IAB nodes.

[0170] According to an example, the mobile IAB node 501 (which may be connected to the mobile IAB node 501 as described above) Figure 1 IAB node 123 and Figure 4 470) can communicate with its IAB donor 502 (which can communicate with Figure 1 The IAB donor node 120 and Figure 4 The MOBILITY INDICATION message 521 is the same as the one in the above reference. Figures 11 to 14 An example of the mobility indication message.

[0171] According to one example, the mobility information sharing may be performed when the mobile IAB node 501 is set. According to another example, the mobility information sharing may be performed intentionally. In this regard, the mobility information sharing may be triggered by a change in the mobility status of the mobile IAB node 501, or may be performed periodically, or may be performed according to a request from the IAB donor 502 (e.g., the IAB donor CU 401).

[0172] In the case where mobility information sharing is performed when the mobile IAB node is set up and according to one example, as specified in 3GPP TS 38.331, such mobility information sharing is performed when the RRC connection is established, and the MOBILITYINDICATION message 521 is an RRCSetupComplete message for completing the RRC connection establishment process.

[0173] In case of mobility information sharing at the time of mobile IAB node setup and according to another example, as specified in 3GPP TS 38.473, the aforementioned mobility information sharing is performed as a part of the F1 setup procedure and the MOBILITY INDICATION message 521 is a F1 SETUP REQUEST message.

[0174] In the case where mobility information sharing is intentionally performed and according to an example, the MOBILITYINDICATION message 521 is any one of the MeasurementReport, FailureInformation, IAB OtherInformation and UEInformationResponse messages as specified in 3GPP TS 38.331, or the GNB-DU CONFIGURATION UPDATE message as specified in 3GPP TS 38.473.

[0175] According to an example, the MOBILITY INDICATION message 521 includes all or part of the following IAB node mobility information (eg, information indicating the mobility of the IAB node):

[0176] -mobileiab-NodeIndication or mobile IAB node indication information (also called mobile node indication information). This information is used to indicate that the device sending the MOBILITY INDICATION message 521 is a mobile IAB node (i.e., an IAB node with mobility capabilities) and is used during the connection establishment.

[0177] In this case, the connection is being established by the mobile IAB node;

[0178] -mobility-StatusIndication or mobility status indication information. This information is used to indicate the current status of the mobility of the mobile IAB node, such as whether the mobile IAB node is currently moving. This information may also include additional information related to the nature of the mobility, such as the

[0179] speed;

[0180] - guaranteedStaticTime or guaranteed static time information. This information indicates the minimum guaranteed time period that the mobile IAB node will remain at a fixed location. For example, a bus that has previously stopped at a bus stop can indicate the remaining time before it moves to the next bus stop;

[0181] -mobility-Profile or mobility profile information. This information provides an indication of the mobility capabilities of the mobile IAB node. The mobility profile information may include at least

[0182] One less:

[0183] o Speed ​​related information or speed information is used to indicate the speed capability of the mobile IAB node, such as minimum speed, average speed, maximum speed, etc.

[0184] o Information related to the mobility area or mobility range of the mobile IAB node (e.g., range information for indicating the mobility area of ​​the mobile IAB node), such as the type of the mobility area, the size of the mobility area, or a list of cell IDs of several cells that the mobile IAB node has previously visited or may visit, etc. The type (or category) of the mobility area may be an indication of the size or nature of the geographical area in which the mobile IAB node may move. For example, the type (or category) of the mobility area may indicate that the geographical area is a bus route, a train route, or a parking lot.

[0185] o Information (e.g., static information) indicating the duration of the static period(s) that the mobile IAB node may experience, such as a minimum static period duration, an average static period duration, or a maximum static period duration, etc. The static information may also include static location information indicating where the mIAB will be static.

[0186] o Itinerary information, which will consist of a sequence of mobility periods and static periods (eg, indicating a itinerary that an mIAB node may follow).

[0187] The trip information may be for each of the mobility period and the static period, including the duration of the period and the speed of the mobile IAB node during the period.

[0188] According to an example, once the mobile IAB node 501 (e.g., the IAB node 470) completes the connection establishment process with the IAB donor 502 (e.g., the IAB donor CU 401), the mobile IAB node 501 may send (e.g., via broadcast) a notification to other wireless communication devices in its vicinity (in the example of FIG. 1 ). Figure 5 The MOBILITY INFORMATION message 531 is a message that is referred to as a network device in the above reference. Figures 11 to 14 An example of the mobility information message described.

[0189] According to one example, the network device 503 is an IAB node: such as Figure 1 IAB node 121 or 123 and Figure 4 IAB nodes 430, 450, 460, 480, etc.

[0190] According to another example, the network device 503 is a UE, such as Figure 1UE 135 or 136 and Figure 4 UE 390, etc.

[0191] The MOBILITY INFORMATION message 531 may be sent periodically.

[0192] In one aspect, the MOBILITY INFORMATION message 531 is a SIB1 message as defined in 3GPP TS 38.331.

[0193] According to an example of an embodiment of the present invention, the MOBILITY INFORMATION message 531 includes all or part of the following IAB node mobility information:

[0194] -iab-support or IAB support information. For example, IAB support information (or connectivity support information) may indicate whether an IAB node can support network connectivity for a wireless communication device. As defined in 3GPP TS 38.331, this information combines both the support of IAB and the cell status for IAB. If this information is present in the MOBILITYINFORMATION message 531, the cell supports IAB and the cell is also considered a candidate for cell (re)selection of an IAB node; if this field is not present, the cell does not support IAB and / or the cell is prohibited for IAB.

[0195] node.

[0196] -mobileiab-NodeIndication or mobile IAB node indication information (also called mobile node indication information). This information is used to indicate that the device sending the MOBILITY INFORMATION message 531 is a mobile IAB node (i.e., an IAB node with mobility capabilities) and the associated cell is a mobile cell;

[0197] -mobility-StatusIndication or mobility status indication information. This information is used to indicate the current status of the mobility of the mobile IAB node, such as whether the mobile IAB node is currently moving. This information may also include additional information related to the nature of the mobility, such as the

[0198] speed;

[0199] - guaranteedStaticTime or guaranteed static time information. This information indicates the minimum guaranteed time period that the mobile IAB node will remain at a fixed location. For example, a bus that has previously stopped at a bus stop can indicate the remaining time before it moves to the next bus stop;

[0200] -mobility-Profile or mobility profile information. This information provides an indication of the mobility capabilities of the mobile IAB node. The mobility profile information may include at least

[0201] One less:

[0202] o Speed ​​related information or speed information is used to indicate the speed capability of the mobile IAB node, such as minimum speed, average speed, maximum speed, etc.

[0203] o Information related to the mobility area or mobility range of the mobile IAB node (e.g., range information for indicating the mobility area of ​​the mobile IAB node), such as the type of the mobility area, the size of the mobility area, or a list of cell IDs of several cells that the mobile IAB node has previously visited or may visit, etc. The type (or category) of the mobility area may be an indication of the size or nature of the geographical area in which the mobile IAB node may move. For example, the type (or category) of the mobility area may indicate that the geographical area is a bus route, a train route, or a parking lot.

[0204] o Information (e.g., static information) indicating the duration of the static period(s) that the mobile IAB node may experience, such as a minimum static period duration, an average static period duration, or a maximum static period duration, etc. The static information may also include static location information indicating where the mIAB will be static.

[0205] o Itinerary information, which will consist of a sequence of mobility periods and static periods (eg, indicating a itinerary that an mIAB node may follow).

[0206] The trip information may be for each of the mobility period and the static period, including the duration of the period and the speed of the mobile IAB node during the period.

[0207] Based on the previously received IAB node mobility information in the MOBILITY INDICATION message 521, the IAB donor 502 may decide to enable or disable the presence of the iab-support information in the MOBILITY INFORMATION message 531 by sending an IAB SUPPORT CONFIGURATION message 522 to the mobile IAB node 501. The IAB SUPPORT CONFIGURATION message 522 is a message sent to the mobile IAB node 501 to enable or disable the presence of the iab-support information in the MOBILITY INFORMATION message 531. Figures 11 to 14 Examples of connectivity or IAB support configuration messages.

[0208] According to an example, the IAB SUPPORT CONFIGURATION message 522 is a RRCReconfiguration message as defined in 3GPP TS 38.331.

[0209] According to an example, in the case where the network device 503 is an IAB node connected to the mobile IAB node 501 as a child IAB node, the IAB node 503 may also provide or send a MOBILITY INFORMATION message 541 to some potential IAB nodes (and / or UEs) in its vicinity for notification purposes (e.g., via broadcast). The MOBILITY INFORMATION message 541 may include all or part of the IAB node mobility information carried by the MOBILITY INFORMATION message 531 previously received from the mobile IAB node 501. In addition, the MOBILITY INFORMATION message 541 may include some information indicating an identifier of the mobile IAB node 501 or identifier information for identifying the IAB node 501, such as a BAP address (as defined in 3GPP TS 38.340), etc. The MOBILITY INFORMATION message 541 is a message sent to the mobile IAB node 501 as described above. Fig.12 An example of the mobility capability message.

[0210] According to another example, in the case where the network device 503 is an IAB node connected to the mobile IAB node 501 as a child IAB node, for example, when the mobile IAB node 501 is moving too far and out of range, the IAB node 503 may experience some kind of backhaul (BH) radio link failure (RLF). The IAB node 503 may then send a RLF INDICATION message 542 to its respective child IAB nodes, thereby adding some information within the message to inform the child IAB nodes that the radio link failure is caused by the mobility of its parent IAB node 501. For example, the RLF INDICATION message 542 may include information indicating that the cause of the RLF is related to the mobility of the parent IAB node.

[0211] Figure 6 An example method for managing connectivity of a mobile IAB node according to some embodiments of the present invention is illustrated using a flowchart 600. Flowchart 600 shows the steps performed at a mobile IAB node and an IAB donor node, and is as described above with reference to Figures 11 to 14 The steps described above are examples of steps performed at the mobile IAB node and the IAB donor node. Figure 6 As shown in and for Figure 6 The method described may be performed by software elements and / or hardware elements.

[0212] The process begins at step 601 where a mobile IAB node (such as Figure 5 The mobile IAB node 501 and Figure 4 IAB node 470, etc.) initiates a connection with an IAB donor CU (such as Figure 5 IAB Donor 502 and Figure 4 connection setup (eg, initiating an IAB node setup procedure) with an IAB donor CU 401, etc.), or detecting changes in mobility conditions and / or capabilities.

[0213] According to an example, at step 601, the mobile IAB node 470 may initiate a connection setup process by sending an RRCSetupRequest message to the IAB donor CU 401 as part of the RRC connection establishment process specified in 3GPP TS 38.331. According to another example, at step 601, the mobile IAB node 470 may initiate a connection setup process by sending an F1 SETUP REQUEST message to the IAB donor CU 401 as part of the F1 setup process specified in 3GPP TS 38.473, which is used to exchange application-level data required for the gNB-DU and the gNB-CU to properly interoperate on the F1 interface. According to another example, at step 601, the mobile IAB node 470 may detect a change in its mobility, such as a change in mobility status and / or capabilities. The change may include a change in speed, a change in its guaranteed static duration, or an update of its mobility profile (as described above, for example, with respect to Figure 5 described above).

[0214] In step 601, the mobile IAB node 470 may also send a MOBILITY INDICATION message 521 (such as reference 521). Figure 5 The CU 404 sends some IAB node mobility information to an IAB donor (eg, the IAB donor CU 401).

[0215] In the case where the mobile IAB node sends some IAB node mobility information to the IAB donor through the MOBILITY INDICATION message 521 at step 601, the IAB donor can determine at step 602 whether the IAB support or connectivity support of the mobile IAB node should be enabled (e.g., when the IAB node can support network connectivity for the wireless communication device) or disabled (e.g., when the IAB node cannot support network connectivity for the wireless communication device), and further determine whether the mobile IAB node supports the IAB node or the connectivity support by sending the IAB SUPPORT CONFIGURATION message 522 (e.g., referring to FIG. 5 ). Figure 5As described above, in the case where the mobile IAB node indication information (mobileiab-NodeIndication) in the MOBILITY INDICATION message 521 sent by the IAB node indicates that it is a mobile IAB node, the IAB donor can determine to disable the IAB support of the IAB node. The IAB donor can determine to enable the IAB support of the mobile IAB node as long as the mobile IAB node is static or will remain static for a significant duration (i.e., a duration exceeding a threshold value that can be as low as tens of seconds) as determined based on the information provided in the MOBILITY INDICATION message 521 at step 601 (such as the mobility status indication information and / or the guaranteed static time information, etc.).

[0216] In an example, the IAB donor may determine to enable IAB support for a mobile IAB node regardless of the actual mobility of the mobile IAB node as long as its mobility is limited as determined based on the information provided in the MOBILITY INDICATION message 521 at step 601. For more details on limited mobility criteria / conditions, see above (e.g., Fig.11 and / or Fig.13 and Fig.14 ).

[0217] At step 603, the mobile IAB node 470 sends a MOBILITY INFORMATION message 531 (eg, a reference message 532). Figure 5 The mobile IAB node 470 may perform conditional IAB support management and notification of associated mobility information to potential child IAB nodes (and / or UEs) as described above. The mobile IAB node 470 may disable transmission of the IAB support information in the MOBILITY INFORMATION message 531 (e.g., by not including the IAB support information in the MOBILITY INFORMATION message 531) as long as the mobile IAB node is actually moving. The mobile IAB node 470 may enable notification of its IAB support information in the MOBILITY INFORMATION message 531 (e.g., by including the IAB support information in the MOBILITY INFORMATION message 531) even if it is currently moving, as long as its mobility remains restricted. For more details on the restricted mobility criteria / conditions that the mobile IAB node 470 may consider when determining whether its mobility is restricted, see above (e.g., Fig.11 and / or Fig.13 and Fig.14 ).

[0218] According to another example, the mobile IAB node 470 may be based on the IAB SUPPORT CONFIGURATION message 522 (eg, referenced to, for example, the IAB donor CU 401) received from the IAB donor at step 602. Figure 5 ) to determine whether to enable or disable the notification of the IAB support information of the mobile IAB node 470 in the MOBILITY INFORMATION message 531.

[0219] In an example implementation, when IAB support notification is enabled (i.e., when IAB support information in MOBILITY INFORMATION message 531 is sent), mobile IAB node 470 may advertise the mobility profile of mobile IAB node 470 in MOBILITY INFORMATION message 531 at step 603. For example, when IAB node 470 may support network connectivity for wireless communication devices (such as IAB node / UE, etc.), MOBILITY INFORMATION message 531 may include mobility profile information and IAB support information. In another example implementation, when IAB support is disabled (i.e., when IAB support information in MOBILITY INFORMATION message 531 is not sent), mobile IAB node 470 may advertise the mobility profile of mobile IAB node 470 in MOBILITY INFORMATION message 531 at step 603. For example, when the IAB node 470 cannot support network connectivity for a wireless communication device (such as an IAB node / UE, etc.), the MOBILITY INFORMATION message 531 sent by the mobile IAB node 470 may still include mobility profile information even if the IAB support information is set (e.g., not included in the MOBILITY INFORMATION message 531).

[0220] Now also refer to Figure 7 , Figure 7 is an example of a method for managing a wireless communication device (in Figure 7 A schematic simplified diagram of some example message flows for a connection from a mobile IAB node to a mobile IAB node. The network device or wireless communication device may be an IAB node (where the mobile IAB node is a parent mobile IAB node) or a UE (such as a mobile IAB node as described above). Figure 1 UE 135 or 136 and Figure 4 UE 390, etc.) (wherein the mobile IAB node is an access node).

[0221] According to an example, the mobile IAB node 701 (which may be connected to the mobile IAB node 701 as described above) Figure 1IAB node 123 and Figure 4 470) can communicate with the IAB donor 702 (which can be the same as the IAB node 470 described above) by sending a MOBILITY INDICATION message 521. Figure 1 The IAB donor node 120 and Figure 4 The IAB donor CU 401 corresponds to the IAB node mobility information shared by the IAB node. MOBILITY INDICATION message 521 is the same as the one mentioned above. Figure 5 , Figures 11 to 14 An example of the mobility indication message.

[0222] New network device 703 may wish to join a topology managed by IAB donor 702 (e.g., IAB topology or network 4001 managed by IAB donor 401). According to one example, network device 703 is an IAB node similar to IAB node 121 or 123. According to another example, network device 703 is a UE similar to UE 135 or 136.

[0223] In order to join the topology managed by the IAB donor 702, as specified in 3GPP TS 38.331 and 3GPP TS 38.401, the network device 703 may attempt to connect to the topology via the mobile IAB node 701 (which will act as the parent IAB node of the network device 703 if the network device 703 is an IAB node) by performing an RRC connection establishment procedure 731 with the IAB donor 702 via the mobile IAB node 701. During this procedure, the network device 703 will exchange RRCSetupRequest, RRCSetup, and RRCSetupComplete messages with the DU portion of the mobile IAB node 701 over the Uu interface, and the DU portion of the mobile IAB node 701 will deliver these messages to the CU portion of the IAB donor 702 using the F1AP protocol.

[0224] As specified in 3GPP TS 38.331, IAB donor 702 may reject the connection of network device 703 by sending an RRCReject message instead of an RRCSetup message.

[0225] Once the connection between the IAB node 703 and the network is established, in the case where the network device 703 is an IAB node, the IAB donor 702 may decide to configure or reject the configuration of the BH link between the IAB node 703 and the mobile IAB node 701 by sending a CONFIGURATION INFORMATION message 732 to the IAB node 703 .

[0226] According to one example, the CONFIGURATION INFORMATION message 732 is a RRCReconfiguration message as defined in 3GPP TS 38.331.

[0227] CONFIGURATION INFORMATION message 732 and RRCReject message / RRCSetup message are referenced above Figures 11 to 14 An example of the configuration message described.

[0228] The CONFIGURATION INFORMATION message 732 (or RRCReject message / RRCSetup message) sent to the network device 703 may include at least one of the following information (which information is included depends on whether the network device 703 is an IAB node or a UE):

[0229] -iab-configReject or IAB configuration rejection message. If present in CONFIGURATION

[0230] INFORMATION message 732 , the information indicates to IAB node 703 that IAB donor 702 does not allow IAB node 703 to become a child IAB node of mobile IAB node 701 .

[0231] - MobileCellConnectionReject or mobile cell connection reject information. If present in the CONFIGURATION INFORMATION message 732, this information indicates to the UE 703 that the connection request was rejected because the UE attempted to connect to the network via a mobile IAB node.

[0232] -iab-configRejectCause or IAB configuration rejection cause information. If present in the CONFIGURATIONINFORMATION message 732, this information indicates to the IAB node 703 that the iab-configReject information is present in the CONFIGURATIONINFORMATION message.

[0233] The reason in the INFORMATION message 732, i.e., why the IAB donor 702 does not allow the IAB node 703 to become a child IAB node of the mobile IAB node 701. In an example, the IAB configuration rejection reason information may inform the IAB node 703 that the IAB donor CU 702 does not allow the IAB node 703 to become a child IAB node of the mobile IAB node 701 because the IAB node 701 is a mobile IAB node.

[0234] -mobility-Profile or mobility profile information. This information provides an indication of the mobility capabilities of the mobile IAB node 701. The mobility profile information may include at least one of the following information:

[0235] o Speed ​​related information or speed information is used to indicate the speed capability of the mobile IAB node, such as minimum speed, average speed, maximum speed, etc.

[0236] o Information related to the mobility area or mobility range of the mobile IAB node (e.g., range information for indicating the mobility area of ​​the mobile IAB node), such as the type of the mobility area, the size of the mobility area, or a list of cell IDs of several cells that the mobile IAB node has previously visited or may visit, etc. The type (or category) of the mobility area may be an indication of the size or nature of the geographical area in which the mobile IAB node may move. For example, the type (or category) of the mobility area may indicate that the geographical area is a bus route, a train route, or a parking lot.

[0237] o Information (eg, static information) indicating the duration of a static period(s) that a mobile IAB node may experience, such as a minimum static period duration, an average static period duration, or a maximum static period duration.

[0238] o Itinerary information, which will consist of a sequence of mobility periods and static periods (eg, indicating a itinerary that an mIAB node may follow).

[0239] The trip information may be for each of the mobility period and the static period, including the duration of the period and the speed of the mobile IAB node during the period.

[0240] -mobileParentiab-NodeIndication or mobile parent IAB node indication information. This information is used to indicate that the parent IAB node (ie, IAB node 701) is a mobile IAB node (ie, an IAB node with mobility capability) and the associated cell is a mobile cell.

[0241] Figure 8 Flowchart 800 is used to illustrate a method for managing a wireless communication device (for example, a wireless communication device) according to some embodiments of the present invention. Figure 8 800 illustrates an example method for connecting a wireless communication device (or network device) to a network (e.g., an IAB network or topology) of a wireless communication system via a mobile IAB node. Flowchart 800 illustrates steps performed at a wireless communication device (or network device) and an IAB donor node, and is as described above with reference to Figures 11 to 14The network device or wireless communication device may be an IAB node or a UE (such as the one described above). Figure 1 UE 135 or 136 and Figure 4 UE 390, etc.), where the mobile IAB node is an access node. Figure 8 As shown in and for Figure 8 The method described may be performed by software elements and / or hardware elements.

[0242] The process begins at step 801, where a network device 703 (such as Figure 4 The new network device similar to the IAB node 460 or UE 390 of the mobile IAB node 701 (such as Figure 4 The mobile IAB node 470 (also referred to as the connecting IAB node 701) joins the topology managed by the IAB donor 702 (such as the CU section or CU of the IAB donor 702, etc.) (e.g., by Figure 4 The topology or network 4001 managed by the IAB donor 401).

[0243] According to an example, new network device 703 is an IAB node similar to IAB node 121 or 123 or IAB node 460 .

[0244] According to another example, the new network device 703 is a UE similar to the UE 135 or 136 or the UE 390 .

[0245] In order to join a topology or network managed by the CU of the IAB donor 702, the new network device 703 may conduct an RRC connection establishment procedure with the IAB donor 702 as specified in 3GPP TS 38.331 and attempt to connect to the network via the connecting IAB node 701 (which will act as the parent IAB node of the network device 703 if the network device 703 is an IAB node) by sending a request to the IAB donor 702.

[0246] In step 802, the CU of the IAB donor 702 (e.g., the IAB donor CU 401) performs a connection process with the new network device 703, and checks the mobility capability and status information associated with the connecting IAB node 701 to determine whether the network device 703 is allowed to connect to the network via the connecting IAB node 701. In the case where the network device 703 is an IAB node, the CU of the IAB donor 702 determines whether to allow the BH link to be configured between the new network device 703 and the connecting IAB node 701 (which will serve as the parent IAB node of the new network device 703).

[0247] In the example, the CU of the IAB donor 702 (e.g., the IAB donor CU 401) checks the IAB node mobility information embedded in the MOBILITY INDICATION message 521 previously received from the connecting IAB node 701 to determine whether to allow or reject the connection, and, if the new network device 703 is an IAB node, determines whether to allow the configuration of a BH link between the new network device 703 and the connecting IAB node 701 (which will act as the parent IAB node of the new network device 703).

[0248] The CU of the IAB donor 702 may request to send a MOBILITY INDICATION message 521 to the connected IAB node 701 to obtain the latest IAB node mobility information. In the example, the MOBILITY INDICATION message 521 is a UEInformationResponse message sent by the connected IAB node 701 to the CU of the IAB donor node 702 in response to a UEInformationRequest message (as defined in 3GPP TS 38.331) sent by the IAB donor 702 to the connected IAB node 701.

[0249] In an example, if the mobile IAB-Node Indication information in the MOBILITY INDICATION message 521 previously received from the connected IAB node indicates that the connected IAB node 701 is a mobile IAB node, the CU of the IAB donor 702 may not allow the new network device 703 to connect to the topology or network it manages.

[0250] In another example where the new network device 703 is an IAB node, the CU of the IAB donor 702 may not allow a BH link to be configured between the new network device 703 and the connected IAB node when the mobile IAB node indication information (mobileiab-NodeIndication) in the MOBILITY INDICATION message 521 previously received from the connected IAB node indicates that the requested parent IAB node 701 is a mobile IAB node.

[0251] In another example, the CU of the IAB donor 702 may allow the new device 703 to connect to the network via the connecting IAB node 701, or in the case where the network device 703 is an IAB node, even if the connecting IAB node 701 is a mobile IAB node, as long as the mobile IAB node 701 is static or will remain static for a time period greater than a certain threshold (for example, the threshold may be as low as tens of seconds) as determined based on the mobility status indication information and / or the guaranteed static time information in the MOBILITY INDICATION message 521 previously received from the connecting IAB node 701, the CU of the IAB donor 702 may allow a BH link to be configured between the new IAB node 703 and the connecting IAB node 701 (which will act as a parent IAB node).

[0252] According to another example, the CU of the IAB donor 702 may allow the new device 703 to connect to the network via the connecting IAB node 701, or in the case where the network device 703 is an IAB node, even if the connecting IAB node 701 is a mobile IAB node, as long as the mobility of the mobile IAB node 701 is limited (in other words, as long as the connecting IAB node 701 is moving with limited mobility), the CU of the IAB donor 702 may allow a BH link to be configured between the new IAB node 703 and the connecting IAB node 701 (which will act as a parent IAB node).

[0253] If the above conditions are met (for example, in Fig.11 and / or Fig.13 and Fig.14 If one or any combination of the restricted mobility criteria / conditions described in the description of FIG. 10 is met, the mobility of the mobile IAB node may be considered to be restricted.

[0254] In step 803, in the example where the CU of the IAB donor 702 decides not to allow the configuration of the BH link between the new IAB node 703 and the connecting IAB node 701, as described above with reference to Figure 7 As defined, the CU of the IAB donor 702 sends a CONFIGURATION INFORMATION message 732 to the new IAB node 703. The CONFIGURATION INFORMATION message 732 includes all or part of the following information:

[0255] -iab-configReject or IAB configuration reject message, used to indicate that the connection or configuration has been rejected;

[0256] -iab-configRejectCause or IAB configuration reject reason information to indicate why the connection was

[0257] is rejected (e.g., because the connecting IAB node 701 is a mobile IAB node);

[0258] -mobility-Profile or mobility profile information, used to indicate the mobility capability of the connected IAB node 701.

[0259] In step 803, in an example where the CU of the IAB donor 702 decides to allow configuration of a BH link between the new IAB node and the requested parent IAB node, Figure 7 As defined in the above, the CU of the IAB donor 702 sends a CONFIGURATION INFORMATION message 732 to the new IAB node 703. The CONFIGURATION INFORMATION message 732 does not include the following information:

[0260] -iab-configReject or IAB configuration rejection information;

[0261] -iab-configRejectCause or IAB configuration reject reason information.

[0262] Furthermore, in this latter case, as mentioned above with reference to Figure 7 As defined, the CONFIGURATION INFORMATION message 732 sent to the new IAB node 703 may include the following information:

[0263] -mobility-Profile or mobility profile information, used to indicate the mobility capability of the connected IAB node 701.

[0264] In step 803, in the example where the CU of the IAB donor 702 decides not to allow the new network device 703 to connect to the network, the CU of the IAB donor 702 may send an RRCReject message to the network device 703 and add all or part of the following information to the message:

[0265] -RRCRejectCause or RRC rejection cause information. If present in the RRCReject message, this information indicates to the network device 703 why the connection of the network device 703 to the network was rejected. According to an example, the RRC rejection cause indicates that the network device 703 attempted to connect to the network via a mobile node (such as a mobile IAB node or a mobile IAB donor DU, etc.).

[0266] MobileCellConnectionReject or Mobile Cell Connection Reject information is a message that may be included in a message sent to a UE when a connection request is rejected due to the UE attempting to connect to the network via a mobile IAB node.

[0267] Example of RRCRejectCause or RRC rejection reason information in the RRCReject message of 703.

[0268] -mobility-Profile or mobility profile information, used to indicate as referenced above Figure 7 The mobility capabilities of the connected IAB node 701 are defined.

[0269] Fig. 9 Flowchart 900 is used to illustrate a method for enabling a wireless communication device (for Fig. 9 An example method for managing a connection of a mobile IAB node to a network (eg, an IAB network or topology) of a wireless communication system via a mobile IAB node based on the mobility capabilities and status of the mobile IAB node is disclosed. Fig. 9 As shown in and for Fig. 9 The method described may be performed by software elements and / or hardware elements.

[0270] Processing begins at step 901 where a connection is established with a network device 703 (such as Figure 4 A new network device similar to the IAB node 460 or UE 390 of the present invention is obtained from a nearby mobile IAB node (such as the mobile IAB node 701 (e.g., Figure 4 The mobile IAB node 470) etc.) (also called the connecting IAB node 701) receives some mobility information.

[0271] According to an example, new network device 703 is an IAB node similar to IAB node 121 or 123 or IAB node 460 .

[0272] According to another example, the new network device 703 is a UE similar to the UE 135 or 136 or the UE 390 .

[0273] In the example implementation, as referenced Figure 5 The mobility information is related to all or part of the IAB node mobility information carried in the MOBILITY INFORMATION message 531. The MOBILITY INFORMATION message 531 is the same as the one described above. Figures 11 to 14 In step 902, based on the mobility information received in step 901, as described above with reference to Figure 7 As described, the new network device 703 determines whether it should attempt to connect to the network via the mobile IAB 701 node by initiating an RRC connection establishment procedure 731 .

[0274] According to an example, in the case where the mobile IAB node indication information (mobileiab-NodeIndication) in the MOBILITY INFORMATION message 531 indicates that the IAB node 701 is a mobile IAB node, the new network device 703 may not attempt to connect to the network via the connecting IAB node 701 .

[0275] According to another example, even if the connection IAB node 701 is a mobile IAB node, as long as the mobile IAB node 701 is static or will remain static for a time period greater than a certain threshold (for example, the threshold can be as low as tens of seconds) as determined based on the mobility status indication information and / or the guaranteed static time information in the MOBILITY INFORMATION message 531 previously received from the connection IAB node 701, the new network device 703 can attempt to connect to the network via the connection IAB node 701.

[0276] According to another example, even if the connecting IAB node 701 is a mobile IAB node, as long as the mobility of the mobile IAB node 701 is limited (in other words, as long as the connecting IAB node 701 is moving with limited mobility), the new network device 703 may attempt to connect to the network via the connecting IAB node 701. Fig.11 and / or Fig.13 and Fig.14 If one or any combination of the restricted mobility criteria / conditions described in the description of FIG. 7A and FIG. 8A ) is met, the mobility of the mobile IAB node 701 may be considered to be restricted.

[0277] For clarity, an illustration of some aspects of the invention is provided below.

[0278] During recent discussions in 3GPP (RAN3#117e meeting), it was agreed that the IAB donor CU should be aware of the "mobile" capabilities of the IAB node. Meanwhile, RAN2 initiated some discussions on whether the mobile IAB-MT needs to send mobile IAB indications (capabilities or mobility) to the IAB donor CU.

[0279] Therefore, some specific mobility signaling towards the IAB donor CU may be considered at the mobile IAB node level to allow efficient network connectivity management at the IAB donor CU.

[0280] It is proposed in 3GPP: For example, the mobile IAB node reports mobility-related information to the network so that the CU can include such information in the UE handover decision, simplify some RRC procedures, allow the network to create a mobile IAB mobility history, reject the connection request of the IAB node with the mobile IAB node as the parent node... Understanding the mobile nature of the IAB node can also allow the IAB donor CU to decide on full migration rather than partial migration in the context of topology adaptation.

[0281] The mobility related information to be shared with the IAB donor CU may include:

[0282] - speed (minimum, average or maximum);

[0283] - mobility range (e.g., mobility area type or distance);

[0284] - Trajectory (including a series of moving periods and static periods).

[0285] Thus, along with informing the IAB donor CU of its mobility capabilities, the mobile IAB node may share some mobility profiles with the IAB donor CU. Such mobility profiles may include information related to the nature of the IAB node mobility, such as speed, mobility range or trajectory, and the like.

[0286] The RRC setup procedure has allowed the IAB-MT to indicate to its IAB donor CU that the connection is being established by the IAB node. In the same way, mobile capability signaling can be done as part of the mobile IAB node RRC setup procedure and will then be done by the IAB-MT. In other words, the IAB node indication has been sent by the IAB-MT to the IAB donor CU using RRC (iab-NodeIndication information in the RRCSetupComplete message).

[0287] Therefore, the IAB-MT shall send the mobile IAB Node Indication together with the existing iab-NodeIndication and some mobility capability information to the IAB donor CU using RRC.

[0288] Since some mobility parameters (eg, speed) of an IAB node may evolve, it may be beneficial to inform the IAB donor CU of such evolution.Thus, a mobile IAB node may issue some mobility capability signaling upon detecting a change in the IAB node mobility condition or periodically.

[0289] Thus, mobility capability signaling may be performed as part of the mobile IAB node setup process. In addition, some mobility signaling may also be performed periodically or when a change in the mobility status of the IAB node is detected.

[0290] Since Release 18 introduces the concept of mobile IAB cells, it may be beneficial for the UE to have some knowledge of the fixed or mobile nature of these surrounding cells in the event that it wants to connect to one of these surrounding cells. This will not apply to legacy UEs (i.e., UEs that do not support Release (Rel.) 18 specifications). For example, when connecting to a new cell, the UE may prefer to connect to a fixed cell rather than a mobile cell. Knowing the nature of the mobile IAB cell may allow the need for cell reselection or measurement reporting for handover to be alleviated. In other words, the UE can benefit from knowledge about the mobile nature of the IAB nodes in its vicinity (so that the UE can decide whether it should connect to a mobile cell or try to find some other fixed cell).

[0291] Therefore, the mobile IAB node may broadcast some mobility capability signaling towards UEs in its vicinity using SIB signaling. The mobility capability signaling may include a mobility profile similar to the mobility profile shared with the IAB donor CU, thus including some information such as speed, mobility range or trajectory, etc.

[0292] Since some UEs may prefer to connect to fixed cells rather than mobile cells (e.g., to avoid the need for some handovers where the UE is static and the mobile IAB node is moving away), a mobile IAB node that is not currently moving (e.g., a parked taxi, a bus or subway train waiting at a station) can advertise its static status and the duration that it will remain static to nearby UEs.

[0293] Therefore, the mobile IAB node may broadcast some mobility capability signaling towards UEs in its vicinity using SIB signaling. The mobility capability signaling may include a mobility profile similar to the mobility profile shared with the IAB donor CU.

[0294] Furthermore, in the case where the mobile IAB node is static, the mobile IAB node may inform UEs in its vicinity of its static status and the duration for which it will remain static.

[0295] Considering the scope of Release 18 Mobile IAB framework, a Mobile IAB node should not have descendant IAB nodes, i.e., a Mobile IAB node only serves UEs. In this regard, it is agreed in 3GPP that the approach of not broadcasting the "IAB Supported" indication is sufficient to prevent other IAB nodes from accessing the Mobile IAB (without further normative impact).

[0296] However, a mobile IAB node may become static at some point in time and remain static for a period of time, which duration may even be predictable. For example, a bus may stay at a bus stop for a duration of 30 seconds to 1 minute, a train may remain idle at an intermediate stop at a railway station for up to 5 minutes, or even at its terminal stop at a railway station for 30 minutes to 1 hour and more.

[0297] Mobile IAB nodes can also restrict their movement to a very limited geographic area, such as a promotional vehicle circling a stadium at the Olympics.

[0298] In summary, a mobile IAB node may become static at some point in time and remain static for some period of time, which duration may be predictable. A mobile IAB node may also restrict its movement to a very limited geographical area.

[0299] In both cases, the mobile nature of the IAB node will have zero or very limited impact on its potential connectivity with other surrounding IAB nodes. Therefore, a mobile IAB node that becomes static or has a very limited range of movement can be considered a fixed IAB node and therefore has temporary descendant IAB nodes as long as the mobile IAB node remains static or within a limited geographical area.

[0300] Therefore, a mobile IAB node that becomes static may be considered a fixed IAB node and may therefore have temporary descendant IAB nodes as long as the mobile IAB node remains static.

[0301] Similarly, a mobile IAB node whose movement is restricted to a small geographic area may be considered a fixed IAB node, and thus may have temporary descendant IAB nodes as long as the mobile IAB node remains static.

[0302] Fig.10 Schematic representations showing example communication apparatus (device) or stations according to one or more example embodiments of the present disclosure.

[0303] The communication device 1000 may be a device such as a microcomputer, a workstation, or a light portable device. The communication device 1000 may include a communication bus 1013, which is connected with:

[0304] - a central processing unit 1011, denoted CPU, such as a microprocessor or the like. The central processing unit 1011 may be a single processing unit or processor, or may include two or more processing units or processors that perform the processing required for the operation of the communication device 1000. The number of processors and the allocation of processing functions to the central processing unit 1011 is a matter of design choice for the skilled person;

[0305] - a memory for storing data and a computer program containing instructions for the operation of the communication device 1000. The computer program may contain a number of different program elements (modules) or subroutines containing instructions for the various operations and for implementing the method according to one or more embodiments of the invention; and

[0306] - at least one communication interface 1002 for communicating with a wireless communication system (such as Figure 1 or Figure 4 At least one communication interface 1002 may be connected to a radio communication network 1003, such as a wireless communication network used by 5G NR (e.g., according to Release 16 and / or subsequent releases), over which digital data packets or frames or control frames are transmitted. Frames are written from a FIFO transmit memory in RAM 1012 to the communication interface for transmission, or read from the communication interface for reception and written to a FIFO receive memory in RAM 1012, under the control of a software application running in CPU 1011.

[0307] Each of the donor CU, the donor DU, the IAB node, and the UE may include such a communication device 1000 .

[0308] The memory may include:

[0309] - a read-only memory 1007, denoted ROM, for storing a computer program for implementing the method according to one or more embodiments of the invention;

[0310] A random access memory 1012, represented as a RAM, for storing executable codes of a method according to one or more embodiments of the present invention, and registers adapted to record variables and parameters required for implementing a method according to one or more embodiments of the present invention.

[0311] Optionally (and depending on the function of the communication device), the communication device 1000 may also include the following components:

[0312] - a data storage component 1004 (such as a hard disk, etc.) for storing a computer program for implementing the method according to one or more embodiments of the present invention;

[0313] a disk drive 1005 for a disk 1006, the disk drive being adapted to read data from the disk 1006 or to write data onto said disk;

[0314] - A screen 1009 for displaying the decoded data and / or for use as a graphical interface with the user using a keyboard 1010 or any other input / output means.

[0315] In an example arrangement, a communication bus provides communication and interoperability between various elements included in or connected to the communication device 1000. The representation of a bus is not limiting, and in particular, the central processing unit is operable to communicate instructions to any element of the communication device 1000, either directly or through other elements of the communication device 1000.

[0316] Disk 1006 can optionally be replaced by any information medium (such as a rewritable or non-rewritable compact disk (CD-ROM), a ZIP disk, a USB key or a memory card, etc.), and in general, by an information storage component that can be read by a microcomputer or a microprocessor, is integrated or not integrated into a communication device, may be removable, and is adapted to store one or more programs (the execution of which enables the method according to an embodiment of the invention to be performed).

[0317] The executable code may optionally be stored in a read-only memory 1007, on a hard disk 1004 or on a removable digital medium (e.g., disk 1006 as previously described, etc.). According to an optional variant, the executable code of the program may be received via the communication network 1003, via the interface 1002, to be stored in one of the storage components of the communication device 1000 (such as the hard disk 1004, etc.) before being executed.

[0318] The central processing unit 1011 is adapted to control and guide the execution of instructions or partial software codes of one or more programs according to an embodiment of the present invention, which are stored in one of the above-mentioned storage components. When powered on, one or more programs stored in a non-volatile memory (for example, stored in a hard disk 1004 or a read-only memory 1007) are transferred to a random access memory 1012, which then contains executable codes of one or more programs and registers for storing variables and parameters required to implement the present invention.

[0319] In an example implementation, the communication device (equipment) is a programmable device / equipment that implements the present invention using software. Instructions may be executed by one or more processors (such as one or more digital signal processors (DSPs), general-purpose microprocessors, application-specific integrated circuits (ASICs), field programmable logic arrays (FPGAs), or other equivalent integrated or discrete logic circuit systems, etc.). Therefore, the term "central processing unit" as used herein may refer to any of the aforementioned structures or any other structure suitable for implementing the techniques described herein. However, alternatively, the present invention may be implemented in hardware (e.g., in the form of an application-specific integrated circuit or ASIC or other circuit element).

[0320] Although the present invention has been described with reference to the embodiments, it should be understood that the present invention is not limited to the disclosed embodiments. It will be appreciated by those skilled in the art that various changes and modifications may be made without departing from the scope of the present invention as defined in the appended claims. All features disclosed in this specification (including any appended claims, abstracts and drawings) and / or all steps of any method or process so disclosed may be combined in any combination other than at least some mutually exclusive combinations of such features and / or steps. Unless otherwise expressly stated, each feature disclosed in this specification (including any appended claims, abstracts and drawings) may be replaced by an alternative feature serving the same, equivalent or similar purpose. Thus, unless otherwise expressly stated, each feature disclosed is only an example of an equivalent or similar feature of a general series.

[0321] In the claims, the word "comprising" does not exclude other elements or steps, and the indefinite article "a" or "an" does not exclude a plurality. The mere fact that different features are recited in mutually different dependent claims does not indicate that a combination of these features cannot be used to advantage.

[0322] In the foregoing embodiments, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored as one or more instructions or codes on or transmitted through a computer-readable medium and executed by a hardware-based processing unit.

[0323] Computer-readable media may include computer-readable storage media corresponding to tangible media such as data storage media, or communication media, including any media that facilitates the transfer of a computer program from one location to another, for example, according to a communication protocol. In this manner, computer-readable media may generally correspond to (1) non-transitory tangible computer-readable storage media or (2) communication media such as signals or carrier waves. Data storage media may be any available media that can be accessed by one or more computers or one or more processors to retrieve instructions, codes, and / or data structures to implement the techniques described in the present disclosure. A computer program product may include computer-readable media.

[0324] As an example and not limitation, such computer-readable storage media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage or other magnetic storage devices, flash memory, or any other medium that can be used to store the desired program code in the form of an instruction or data structure and can be accessed by a computer. In addition, any connection is appropriately referred to as a computer-readable medium. For example, if a coaxial cable, optical fiber cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave are used to transmit instructions from a website, server or other remote source, then the coaxial cable, optical fiber cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of the medium. However, it should be understood that computer-readable storage media and data storage media do not include connection, carrier wave, signal or other transient media, but point to non-transient tangible storage media. As used herein, disk (disk and disc) includes compact disk (CD), laser disk, optical disk, digital versatile disk (DVD), floppy disk and blue disc, wherein disk (disk) usually reproduces data magnetically, and disk (disc) reproduces data optically with laser. Combinations of the above should also be included within the scope of computer-readable media.

Claims

1. A method for managing network connectivity in a wireless communication system, the wireless communication system comprising at least one mobile integrated access and backhaul node (mIAB node), the method comprising: At the mAB node, providing a mobility message to a wireless communication device, The mobility message includes at least one of the following information: Mobility profile information, used to indicate the mobility capability of the mIAB node; The static time information is guaranteed to indicate the minimum time period for the mIAB node to remain at a certain location.

2. The method according to claim 1, wherein: The mobility profile information includes at least one of the following information: Speed ​​information, used to indicate the speed capability of the mAB node, Range information, used to indicate the mobility area of ​​the mAB node, Static information, used to indicate the duration of one or more static periods that the mAB node can experience, The trip information is used to indicate a sequence of mobility periods and static periods of a trip that the mIAB node can follow.

3. The method according to claim 1 or 2, wherein: The mobility message further includes at least one of the following information: Mobile node indication information, used to indicate that the mIAB node is a mobile IAB; The mobility status indication information is used to indicate the current status of the mobility of the mIAB node.

4. The method according to any one of claims 1 to 3, wherein: The wireless communication apparatus is an IAB donor node and the mobility message is a mobility indication message, and wherein the providing comprises providing the mobility indication message to the IAB donor node.

5. The method according to claim 4, wherein: The provision includes: After the mIAB node initiates an IAB node setup process for the IAB node, providing the mobility indication message; providing the mobility indication message in response to the mIAB node determining a change in the mobility of the IAB node; Periodically providing the mobility indication message; The mobility indication message is provided in response to a request from the IAB donor node.

6. The method according to any one of claims 1 to 3, wherein: The wireless communication device is an IAB node or a UE of the wireless communication system, the mobility message is a mobility information message, and wherein the providing comprises: providing the mobility information message to the IAB node or the UE.

7. The method according to claim 6, wherein: The provision includes: After the IAB node setup process is completed, providing the mobility information message; providing the mobility information message in response to the mIAB node determining a change in mobility; The mobility information message is provided periodically.

8. The method according to claim 6 or 7, wherein: The providing includes broadcasting the mobility information message.

9. The method according to any one of claims 6 to 8, wherein: The mobility information message also includes: A connectivity support indicator is used to indicate whether the mIAB node can support network connectivity for the wireless communication device.

10. The method according to any one of claims 6 to 9, wherein: In case the mIAB node is capable of supporting network connectivity, IAB support information is included in the mobility information message to indicate that network connectivity can be supported by the mIAB node.

11. The method according to any one of claims 6 to 10, wherein: In case the mIAB node cannot support network connectivity, IAB support information is not included in the mobility information message to indicate that network connectivity cannot be supported by the mIAB node.

12. The method according to any one of claims 9 to 11, further comprising: A connectivity support configuration message is received from the IAB donor node, the connectivity support configuration message being used to indicate whether the mlAB node is capable of supporting network connectivity, wherein the mlAB node determines whether the mlAB node is capable of supporting network connectivity based on the received connectivity support configuration message.

13. The method according to any one of claims 9 to 11, further comprising: Whether the mlAB node can support network connectivity is determined by the mlAB node based on mobility of the mlAB node.

14. The method according to claim 13, further comprising: In a case where the mlAB node is static for a period of time greater than a threshold or in a case where the mlAB node is moving with restricted mobility, it is determined that the mlAB node is capable of supporting network connectivity.

15. The method of claim 14, wherein the mobility of the mAB node is restricted if at least one of the following criteria is met: The speed of the mAB node is below a certain threshold, The mobility area is geographically restricted, The mobility area is within a topology or a network cell.

16. The method according to any one of claims 12 to 15, wherein: In response to determining that the mIAB node is capable of supporting network connectivity, a mobility information message including IAB support information is provided to indicate that network connectivity for the wireless communication device is capable of being supported by the IAB node.

17. The method according to claim 12 or 13, further comprising: In the event that the mlAB node is moving, it is determined that the mlAB node cannot support network connectivity.

18. A method according to any one of the preceding claims, wherein: The mobility message also includes: The mobile IAB cell indication information is used to indicate that the cell is associated with the mobile IAB node.

19. A method at a wireless communication device of a wireless communication system, the wireless communication system further comprising an IAB node controlled by an integrated access and backhaul donor node (IAB donor node), the method comprising: At the wireless communication device, receiving a mobility information message from the IAB node; taking action based at least in part on information provided by a received mobility information message, The mobility information message includes at least one of the following information: Mobility profile information, used to indicate the mobility capability of the IAB node; The static time information is guaranteed to indicate the minimum time period for the IAB node to remain at a certain location.

20. The method according to claim 19, wherein: The mobility profile information includes at least one of the following information: Speed ​​information, used to indicate the speed capability of the IAB node, Range information, used to indicate the mobility area of ​​the IAB node, Static information, used to indicate the duration of one or more static periods that the IAB node can experience, The itinerary information is used to indicate a sequence of mobility periods and static periods of a itinerary that the IAB node can follow.

21. The method according to claim 19 or 20, wherein: The mobility information message further includes at least one of the following information: Mobile node indication information, used to indicate that the IAB node is a mobile IAB node, namely, an mIAB node; Mobility status indication information, used to indicate the current status of the mobility of the IAB node; Mobile IAB cell indication information, used to indicate that a cell is associated with a mobile IAB node; The IAB support information is used to indicate whether the IAB node can support network connectivity for the wireless communication device.

22. The method according to any one of claims 19 to 21, wherein: The wireless communication device is another IAB node or a UE.

23. The method according to any one of claims 19 to 22, wherein: The actions include: A determination is made based on the mobility information message whether to initiate a connection establishment procedure for establishing a connection via the IAB node.

24. The method according to claim 23, wherein: The determining includes: determining not to initiate a connection establishment procedure if the information provided by the mobility information message indicates that the IAB node is a mobile IAB node.

25. The method according to claim 23, wherein: The determination includes: determining to initiate a connection establishment process when the information provided by the mobility information message indicates that certain criteria are met, the certain criteria including: the IAB node is not a mobile IAB node; the IAB node is a mobile IAB node and is static for a time period greater than a certain threshold; the IAB node is a mobile IAB node and is moving with restricted mobility.

26. The method according to claim 25, wherein: The mobility of the IAB node is restricted if at least one of the following criteria is met: The speed of the IAB node is below a certain threshold, The mobility area is geographically restricted, The mobility area is within a topology or a network cell.

27. The method according to any one of claims 23 to 26, wherein: The actions also include: In response to determining to initiate a connection establishment process, sending, via the IAB node, to the IAB donor node a request for requesting establishment of a connection via the IAB node; receiving a configuration message from the IAB donor node in response to the request, Wherein, in the case that the connection via the IAB node has been rejected because the IAB node is a mobile IAB node, the configuration message includes IAB configuration rejection reason information, and the IAB configuration rejection reason information is used to indicate that the connection has been rejected because the IAB node is a mobile IAB node.

28. The method according to any one of claims 19 to 21, wherein: The wireless communication device is a child IAB node of the IAB node, wherein the actions include: After a connection via the IAB node has been established, a mobility capability message is provided by the child IAB node based on information provided by a received mobility information message received from the IAB node, the mobility capability message including mobility capability information indicating mobility capabilities of the IAB node.

29. The method according to claim 28, wherein: The mobility capability information included in the mobility capability message includes at least one of the following information: Speed ​​information, used to indicate the speed capability of the IAB node; Range information, used to indicate the mobility area of ​​the IAB node; Static information, used to indicate the duration of one or more static periods that the IAB node can experience; The itinerary information is used to indicate a sequence of mobility periods and static periods of a itinerary that the IAB node can follow.

30. The method according to claim 28 or 29, wherein: The mobility capability message further includes at least one of the following information: Mobile node indication information, used to indicate whether the IAB node is a mobile IAB node, i.e., an mIAB node; Mobility status indication information, used to indicate the current status of the mobility of the IAB node; Mobile IAB cell indication information, used to indicate that a cell is associated with a mobile IAB node; IAB support information, used to indicate whether the IAB node can support network connectivity for the wireless communication device; Ensure static time information, which is used to indicate the minimum time period for the IAB node to remain at a certain location; The identifier information is used to identify the IAB node.

31. The method according to any one of claims 19 to 21, wherein: The wireless communication device is a child IAB node of the IAB node acting as a parent IAB node, and the actions include: determining a radio link failure (RLF) for a radio link with the parent IAB node based on information provided by the received mobility information message; A RLF indication message is sent, where the RLF indication message includes information indicating that a cause of the RLF is related to the mobility of the parent IAB node.

32. A method at an integrated access and backhaul donor node (IAB donor node) of a wireless communication system, the wireless communication system comprising an IAB node controlled by the IAB donor node, the method comprising: receiving a mobility indication message from the IAB node; performing an action based at least in part on information provided by a received mobility indication message, The mobility indication message includes at least one of the following information: Mobility profile information, used to indicate the mobility capability of the IAB node; The static time information is guaranteed to indicate the minimum time period for the IAB node to remain at a certain location.

33. The method of claim 32, wherein: The mobility profile information includes at least one of the following information: Speed ​​information, used to indicate the speed capability of the IAB node; Range information, used to indicate the mobility area of ​​the IAB node; Static information, used to indicate the duration of one or more static periods that the IAB node can experience; The itinerary information is used to indicate a sequence of mobility periods and static periods of a itinerary that the IAB node can follow.

34. The method according to claim 32 or 33, wherein: The mobility indication message further includes at least one of the following information: Mobile node indication information, used to indicate whether the IAB node is a mobile IAB node, i.e., an mIAB node; The mobility status indication information is used to indicate the current status of the mobility of the IAB node.

35. The method according to any one of claims 32 to 34, wherein: Receiving the mobility indication message includes: receiving the mobility indication message as part of an IAB node setup procedure with the IAB node; receiving the mobility indication message in response to the message sent by the IAB donor node; The mobility indication message is received periodically.

36. The method according to any one of claims 32 to 35, wherein: The actions include: sending a notification message indicating that the IAB node is a mobile IAB node based on the information provided in the mobility indication message to one or more of the following: an IAB donor node of another IAB topology; Another IAB node; UE.

37. The method according to any one of claims 32 to 35, wherein: The method further comprises: receiving, from a wireless communication device, a request to establish a connection via the IAB node as part of a connection establishment process; The actions include: determining whether to accept or reject a connection via the IAB node based at least in part on mobility of the IAB node; A configuration message is sent to the wireless communication device indicating whether connection via the IAB node has been accepted or rejected.

38. The method of claim 37, determining whether to accept or reject a connection via the IAB node comprises: A determination is made whether to accept or reject a connection via the IAB node based at least in part on information provided by the mobility indication message.

39. The method according to claim 37 or 38, wherein: The received mobility indication message includes information indicating a current status of the mobility of the IAB node; Wherein, determining whether to accept or reject the connection via the IAB node includes: determining whether to accept or reject the connection via the IAB node based at least in part on a current status of mobility of the IAB node.

40. The method according to any one of claims 37 to 39, wherein: In a case where a connection via the IAB node has been rejected based on mobility of the IAB node, the configuration message includes IAB configuration reject cause information indicating why the connection has been rejected.

41. The method according to any one of claims 37 to 40, wherein: In a case where the connection via the IAB node has been rejected because the IAB node is a mobile IAB node, the configuration message includes IAB configuration reject cause information indicating that the connection has been rejected because the IAB node is a mobile IAB node.

42. The method according to any one of claims 37 to 41, wherein: In case the connection via the IAB node has been rejected or accepted, the configuration message includes mobility profile information indicating the mobility capabilities of the IAB node, The mobility profile information includes at least one of the following information: Speed ​​information, used to indicate the speed capability of the IAB node; Range information, used to indicate the mobility area of ​​the IAB node; Static information, used to indicate the duration of one or more static periods that the IAB node can experience; The itinerary information is used to indicate a sequence of mobility periods and static periods of a itinerary that the IAB node can follow.

43. The method according to any one of claims 37 to 42, wherein, when the IAB node is a mobile IAB node and the wireless communication device is another IAB node, the configuration message further includes mobile parent IAB node indication information for indicating that the IAB node is a mobile parent IAB node.

44. The method according to any one of claims 32 to 35, wherein: The actions include: determining whether to enable or disable network connectivity support utilizing the IAB node based at least in part on mobility of the IAB node; A connectivity support configuration message is sent to the IAB node, where the connectivity support configuration message is used to indicate whether the IAB node can support network connectivity for the wireless communication device.

45. The method of claim 44, further comprising: A determination is made as to whether to enable or disable network connectivity support based on information provided by the mobility indication message.

46. ​​The method according to claim 44 or 45, wherein: In a case where the IAB node is static for a period of time greater than a threshold or in a case where the IAB node is moving with restricted mobility, it is determined to enable network connectivity support.

47. The method of claim 46, wherein: The mobility of the IAB node is restricted if at least one of the following criteria is met: The speed of the IAB node is lower than a certain threshold; The mobility area is geographically restricted; The mobility area is within a topology or a network cell.

48. The method according to any one of claims 32 to 35, wherein: Receiving the mobility indication message includes: receiving a new mobility indication message including updated information compared to a previously received mobility indication message, The actions include: determining whether one or more wireless communication devices connected to the IAB node should be released based on information provided by the new mobility indication message; and In response to determining that the one or more wireless communication devices should be released, a release notification is sent to the one or more wireless communication devices.

49. A method for managing network connectivity in a wireless communication system, the wireless communication system comprising at least one integrated access and backhaul node (IAB node), the method comprising: At the IAB node, determining whether the IAB node is capable of supporting network connectivity for the wireless communication device based on the mobility of the IAB node; In response to determining that the IAB node is capable of supporting the network connectivity, a mobility information message including IAB support information is provided to indicate that the network connectivity for the wireless communication device is capable of being supported by the IAB node.

50. The method of claim 49, wherein: The mobility information message further includes at least one of the following information: Mobility profile information, used to indicate the mobility capability of the IAB node; Ensure static time information, which is used to indicate the minimum time period for the IAB node to remain at a certain location; Mobile node indication information, used to indicate that the IAB is a mobile IAB; Mobility status indication information, used to indicate the current status of the mobility of the IAB node; The mobile IAB cell indication information is used to indicate that the cell is associated with the mobile IAB node.

51. The method of claim 50, wherein: The mobility profile information includes at least one of the following information: Speed ​​information, used to indicate the speed capability of the IAB node, Range information, used to indicate the mobility area of ​​the IAB node, Static information, used to indicate the duration of one or more static periods that the IAB node can experience, The itinerary information is used to indicate a sequence of mobility periods and static periods of a itinerary that the IAB node can follow.

52. The method according to any one of claims 49 to 51, wherein: determining whether the IAB node is capable of supporting network connectivity for the wireless communication device based on at least one of the following: The mobility capability of the IAB node; and the current mobility status of the IAB node.

53. A method according to any one of claims 49 to 52, wherein: In response to determining that the IAB node cannot support network connectivity, not including IAB support information in the mobility information message to indicate that the IAB node cannot support network connectivity.

54. The method according to any one of claims 49 to 53, further comprising: In the case where the IAB node is static for a period of time greater than a certain threshold or in the case where the IAB node is moving with restricted mobility, it is determined that network connectivity can be supported by the IAB node.

55. The method of claim 54, wherein: The mobility of the IAB node is restricted if at least one of the following criteria is met: The speed of the IAB node is below a certain threshold, The mobility area is geographically restricted, The mobility area is within a topology or a network cell.

56. The method according to any one of claims 49 to 51, further comprising: A connectivity support configuration message is received from an IAB donor node connected to the IAB node, the connectivity support configuration message being used to indicate whether the IAB node is capable of supporting network connectivity, wherein the IAB node determines whether the IAB node is capable of supporting network connectivity based on the received connectivity support configuration message.

57. The method according to any one of claims 49 to 56, further comprising: Sending a mobility indication message to an IAB donor node connected to the IAB node, the mobility indication message including at least one of the following information: Mobility profile information, used to indicate the mobility capability of the IAB node; Ensure static time information, which is used to indicate the minimum time period for the IAB node to remain at a certain location; Mobile node indication information, used to indicate that the IAB is a mobile IAB; The mobility status indication information is used to indicate the current status of the mobility of the IAB node.

58. The method of claim 57, wherein: The mobility profile information includes at least one of the following information: Speed ​​information, used to indicate the speed capability of the IAB node, Range information, used to indicate the mobility area of ​​the IAB node, Static information, used to indicate the duration of one or more static periods that the IAB node can experience, The itinerary information is used to indicate a sequence of mobility periods and static periods of a itinerary that the IAB node can follow.

59. A method at a wireless communication device of a wireless communication system, the wireless communication system further comprising an integrated access and backhaul node (IAB node) controlled by an IAB donor node, the method comprising: At the wireless communication device, sending, via the IAB node, to the IAB donor node a request for requesting establishment of a connection via the IAB node; receiving a configuration message from the IAB donor node in response to the request, Wherein, in a case where the connection via the IAB node has been rejected because the IAB node is a mobile IAB node, the configuration message includes IAB configuration rejection cause information for indicating that the connection has been rejected because the IAB node is a mobile IAB node.

60. The method of claim 59, wherein: In the case that the connection via the IAB node has been rejected, the configuration message further includes an IAB configuration rejection information indication that the connection has been rejected.

61. The method of claim 59 or 60, wherein: In the case where the IAB node is a mobile IAB node, the configuration message includes mobility profile information for indicating the mobility capability of the IAB node, The mobility profile information includes at least one of the following information: Speed ​​information, used to indicate the speed capability of the IAB node; Range information, used to indicate the mobility area of ​​the IAB node; Static information, used to indicate the duration of one or more static periods that the IAB node can experience; The itinerary information is used to indicate a sequence of mobility periods and static periods of a itinerary that the IAB node can follow.

62. A device for an integrated access and backhaul node (IAB node) of a wireless communication system, the device comprising: One or more central processing units configured to perform a method according to any one of claims 1 to 18, 49 to 58.

63. A device for an integrated access and backhaul donor node (IAB donor node) for a wireless communication system, the device comprising: One or more processing units configured to perform a method according to any one of claims 32 to 48.

64. An apparatus for a wireless communication device, comprising: One or more processing units configured to perform a method according to any one of claims 19 to 31, 59 to 61.

65. A computer program comprising instructions which, when the program is executed by a computer, cause the computer to execute the control method according to any one of claims 1 to 61.

66. A computer readable medium carrying a computer program according to claim 65.

Images