Configuration method of mobile node, mobile node and host equipment

Abstract

The embodiment of the invention provides a configuration method of a mobile node, the mobile node and host equipment. F1 connection of a distribution unit (DU) of the mobile node terminates at a first donor-CU, and the first donor-CU configures or reconfigures second information related to a first cell for the DU of the mobile node according to first information related to the position of the mobile node; and the first donor-CU sends the configured or reconfigured second information related to the first cell to the DU of the mobile node.

Description

Mobile node configuration method, mobile node and host device Technical Field

[0001] The embodiments of the present application relate to the field of communications. Background Art

[0002] Future seamless cellular network deployment requires highly flexible and ultra-dense new radio (NR) cell deployment. Ultra-dense networks are one of the goals of 5G, and deploying an NR network without wired backhaul is crucial to achieving these ultra-dense 5G networks. Because 5G millimeter waves reduce cell coverage, wireless self-backhaul systems require multiple hops to meet deployment requirements. 5G's high bandwidth, massive multiple-input multiple-output (MIMO), and beamforming make it easier to develop ultra-dense NR cell wireless self-backhaul systems for 5G than for LTE. To develop this multi-hop system with wireless self-backhaul, 3GPP initiated research and standardization of the Integrated Access and Backhaul (IAB) project in Rel-16.

[0003] Figure 1 is a schematic diagram of the IAB system. As shown in Figure 1, in the IAB system, access and backhaul adopt NR's Uu air interface wireless transmission. The relay node supports both access and backhaul functions. The relay node multiplexes the access link and backhaul link in the time domain, frequency domain, or spatial domain. The access link and backhaul link can use the same or different frequency bands.

[0004] In the IAB network architecture, the relay node is referred to as the IAB-node, which supports both access and backhaul functions. The last-hop access node on the network side is called the IAB-donor, which supports gNB functions and access to the IAB-node. All UE data is backhauled to the IAB-donor via one or more hops via the IAB-node.

[0005] The IAB-node's functionality is divided into two parts: gNB-DU functionality, known as the IAB-DU (distributed unit), and UE functionality, known as the IAB-MT (mobile terminal). The IAB-DU implements network-side device functions, serving one or more cells and connecting to downstream child IAB-nodes (child IAB nodes, or simply child nodes). It provides NR air interface access to the UE and downstream child IAB-nodes and establishes an F1 connection with the IAB donor-CU (host centralized unit). The IAB-MT implements some terminal device functions and connects to the upstream parent IAB-node (parent IAB node, or simply parent node) or IAB donor-DU. The IAB-MT includes physical layer, layer 2, radio resource control (RRC), and non-access stratum (NAS) layer functions, and is indirectly connected to the IAB donor-CU and the core network (CN).

[0006] In the IAB system, an IAB-node can access the network in either standalone (SA) or non-standalone (EN-DC) mode. Figure 2 shows the IAB architecture in SA mode. Figure 3 shows the IAB architecture in EN-DC mode.

[0007] Figure 4 illustrates an IAB node, its parent IAB node, and its child IAB node. As shown in Figure 4, the IAB-DU of the IAB node connects to the IAB-MT of the child node on the network side, while the IAB-MT of the IAB node connects to the IAB-DU of the parent node on the terminal side.

[0008] Figure 5 shows the F1 user plane (F1-U) protocol stack between the IAB-DU and the IAB donor-CU. Figure 6 shows the F1 control plane (F1-C) protocol stack between the IAB-DU and the IAB donor-CU. As shown in Figures 5 and 6, F1-U and F1-C are built on the transport (IP) layer between the IAB-DU and the IAB donor-CU. In these figures, the two-hop wireless backhaul and one-hop wired backhaul are used.

[0009] On the backhaul link, the transport (IP) layer is carried on the Backhaul Adaptation Protocol (BAP) sublayer. The BAP entity in the IAB node implements the routing function of the IAB system, and the IAB donor-CU provides the routing table. BAP PDUs (Protocol Data Units) are transmitted on the backhaul link's RLC (Radio Link Control) channel. The IAB donor can configure multiple RLC channels on the backhaul link to carry services of different priorities and QoS (Quality of Service). The BAP entity maps BAP PDUs to different backhaul RLC channels.

[0010] It should be noted that the above introduction to the technical background is only for the convenience of providing a clear and complete description of the technical solutions of this application and for the convenience of understanding by those skilled in the art. It cannot be considered that the above technical solutions are well known to those skilled in the art simply because these solutions are explained in the background technology part of this application.

[0011] Summary of the Invention

[0012] The inventors have discovered that currently the identification of an IAB node is related to its location, but in a mobile scenario, the cell information of a mobile node may conflict with adjacent cells, making it impossible for the network to support multiple mobile nodes working simultaneously.

[0013] In order to solve at least one of the above problems, embodiments of the present application provide a configuration method of a mobile node, a mobile node, and a host device.

[0014] According to one aspect of an embodiment of the present application, a configuration method for a mobile node is provided, wherein an F1 connection of a distributed unit (DU) of the mobile node is terminated at a first donor-CU, the method comprising:

[0015] The first donor-CU configures or reconfigures second information related to the first cell for the IAB-DU of the mobile node based on the first information related to the location of the mobile node; and

[0016] The first donor-CU sends the configured or reconfigured second information related to the first cell to the DU of the mobile node.

[0017] According to another aspect of an embodiment of the present application, a host device is provided, wherein an F1 connection of a distributed unit (DU) of a mobile node is terminated at the host device, and the host device includes:

[0018] a configuration unit configured to configure or reconfigure second information related to the first cell for the DU of the mobile node based on the first information related to the location of the mobile node; and

[0019] A communication unit transmits the configured or reconfigured second information related to the first cell to the IAB-DU of the mobile node.

[0020] According to another aspect of an embodiment of the present application, a configuration method for a mobile node is provided, wherein an F1 connection of a distributed unit (DU) of the mobile node is terminated at a first donor-CU, the method comprising:

[0021] The DU of the mobile node receives the second information related to the first cell sent by the first donor-CU; wherein the second information related to the first cell is configured or reconfigured by the first donor-CU according to the first information related to the location of the mobile node.

[0022] According to another aspect of an embodiment of the present application, a mobile node is provided, comprising a mobile terminal (MT) and a distribution unit (DU); the F1 connection of the distribution unit (IAB-DU) is terminated at a first host centralized unit (donor-CU), and the DU of the mobile node receives second information related to a first cell sent by the first donor-CU; wherein the second information related to the first cell is configured or reconfigured by the first donor-CU based on the first information related to the location of the mobile node.

[0023] According to another aspect of an embodiment of the present application, an IAB system is provided, including a host centralized unit and a mobile node; the F1 connection of a distribution unit (DU) of the mobile node is terminated at the host centralized unit, the host centralized unit configures or reconfigures second information related to a first cell for the DU of the mobile node based on first information related to the location of the mobile node; and sends the configured or reconfigured second information related to the first cell to the DU of the mobile node.

[0024] One of the beneficial effects of the embodiments of the present application is that: the first donor-CU configures or reconfigures second information for the DU of the mobile node based on the first information of the mobile node; and sends the second information to the DU of the mobile node. As a result, the first donor-CU can dynamically configure information within the mobile area for the mobile node based on the real-time location information of the mobile node; thereby avoiding conflicts between the mobile node and neighboring cells, and enabling the network to support the simultaneous operation of multiple mobile nodes.

[0025] With reference to the description and accompanying drawings that follow, specific embodiments of the present application are disclosed in detail, indicating how the principles of the present application can be employed. It should be understood that the embodiments of the present application are not limited in scope. Within the spirit and scope of the accompanying notes, the embodiments of the present application include many variations, modifications, and equivalents.

[0026] Features described and / or illustrated with respect to one embodiment may be used in the same or similar manner in one or more other embodiments, combined with features in other embodiments, or substituted for features in other embodiments.

[0027] It should be emphasized that the term "include / comprising" when used herein refers to the presence of features, integers, steps or components, but does not exclude the presence or addition of one or more other features, integers, steps or components. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] The elements and features described in one figure or one embodiment of the present application can be combined with the elements and features shown in one or more other figures or embodiments. In addition, in the accompanying drawings, similar reference numerals represent corresponding parts in several figures and can be used to indicate corresponding parts used in more than one embodiment.

[0029] The included drawings are used to provide a further understanding of the embodiments of the present application, which constitute a part of the specification, are used to illustrate the implementation methods of the present application, and together with the text description, explain the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without inventive work. In the drawings:

[0030] FIG1 is a schematic diagram of an IAB system;

[0031] FIG2 is a schematic diagram of the IAB architecture in SA mode;

[0032] FIG3 is a schematic diagram of the IAB architecture of the EN-DC mode;

[0033] FIG4 is a schematic diagram of a parent IAB-node and a child IAB-node;

[0034] FIG5 is a schematic diagram of the F1-U protocol stack of the IAB system;

[0035] FIG6 is a schematic diagram of the F1-C protocol stack of the IAB system;

[0036] FIG7 is a schematic diagram of IAB system routing;

[0037] FIG8 is a schematic diagram of a mobility scenario;

[0038] FIG9 is another schematic diagram of a mobility scenario;

[0039] FIG10 is a schematic diagram of a method for configuring a mobile node according to an embodiment of the present application;

[0040] FIG11 is an exemplary diagram of a method for configuring a mobile node according to an embodiment of the present application;

[0041] FIG12 is a schematic diagram of an IAB integration method according to an embodiment of the present application;

[0042] FIG13 is a signaling flow chart of IAB integration according to an embodiment of the present application;

[0043] FIG14 is a schematic diagram of a host device according to an embodiment of the present application;

[0044] FIG15 is a schematic diagram of a mobile node according to an embodiment of the present application;

[0045] FIG16 is a schematic diagram of an IAB device according to an embodiment of the present application. DETAILED DESCRIPTION

[0046] The above and other features of the present application will become apparent through the following description with reference to the accompanying drawings. In the description and drawings, specific embodiments of the present application are disclosed in detail, which show some embodiments in which the principles of the present application can be adopted. It should be understood that the present application is not limited to the described embodiments. On the contrary, the present application includes all modifications, variations and equivalents that fall within the scope of the attached notes.

[0047] In the embodiments of the present application, the terms "first", "second", etc. are used to distinguish different elements from the name, but do not indicate the spatial arrangement or temporal order of these elements, and these elements should not be limited by these terms. The term "and / or" includes any one and all combinations of one or more of the associated listed terms. The terms "comprising", "including", "having", etc. refer to the presence of the stated features, elements, components or components, but do not exclude the presence or addition of one or more other features, elements, components or components.

[0048] In the embodiments of this application, the singular forms "a," "the," etc. include plural forms and should be broadly understood to mean "a" or "a type" rather than being limited to "one." Furthermore, the term "said" should be understood to include both singular and plural forms, unless the context clearly indicates otherwise. Furthermore, the term "according to" should be understood to mean "at least in part based on...", and the term "based on" should be understood to mean "at least in part based on...", unless the context clearly indicates otherwise.

[0049] In the embodiments of the present application, the term "communication network" or "wireless communication network" may refer to a network that complies with any of the following communication standards, such as New Radio (NR), Long Term Evolution (LTE), Enhanced Long Term Evolution (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

[0050] Furthermore, communication between devices in the communication system may be carried out according to communication protocols of any stage, for example, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and future 5G, 6G, etc., and / or other communication protocols currently known or to be developed in the future.

[0051] In the embodiments of the present application, the term "network device" refers to, for example, a device in a communication system that connects a terminal device to the communication network and provides services to the terminal device. Network devices may include, but are not limited to, the following devices: base station (BS), access point (AP), transmission reception point (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), etc.

[0052] Base stations may include, but are not limited to, NodeB (NB), evolved NodeB (eNodeB or eNB), and 5G base stations (gNB), among others. They may also include remote radio heads (RRHs), remote radio units (RRUs), relays, or low-power nodes (e.g., femto, pico, etc.). The term "base station" may include some or all of their functions, and each base station may provide communication coverage for a specific geographic area. The term "cell" may refer to a base station and / or its coverage area, depending on the context in which the term is used.

[0053] In the embodiments of the present application, the term "user equipment" (UE) refers to, for example, a device that accesses a communication network through a network device and receives network services, and may also be referred to as "terminal equipment" (TE). Terminal equipment may be fixed or mobile, and may also be referred to as a mobile station (MS), terminal, user, subscriber station (SS), access terminal (AT), station, etc.

[0054] Among them, terminal devices may include but are not limited to the following devices: cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptop computers, cordless phones, smart phones, smart watches, digital cameras, etc.

[0055] For another example, in scenarios such as the Internet of Things (IoT), the terminal device can also be a machine or device for monitoring or measurement, including but not limited to: machine type communication (MTC) terminal, vehicle-mounted communication terminal, device-to-device (D2D) terminal, machine-to-machine (M2M) terminal, and so on.

[0056] The routing function of the IAB system is implemented by the BAP layer. Each IAB node stores the routing configuration (BH routing configuration) and the RLC channel mapping configuration (BH RLC Channel Mapping Configuration). The BAP entity performs routing based on the routing configuration, RLC channel mapping configuration, and the routing ID in the BAP layer packet header. The Routing ID contains the destination BAP address and the path identifier.

[0057] The routing configuration includes the mapping relationship between the Routing ID and the next-hop node BAP address. The RLC channel mapping configuration includes the mapping relationship between the prior-hop node BAP address, the ingress link RLC channel ID, and the next-hop node BAP address and the egress link RLC channel ID.

[0058] Figure 7 is a schematic diagram of IAB system routing. As shown in Figure 7, for each data packet, the next-hop node BAP address can be found from the routing configuration using the routing ID in the packet header. The previous-hop node BAP address and the ingress link RLC channel ID are both known. Once the next-hop node BAP address is determined, the outgress link RLC channel ID can be found using the RLC channel mapping configuration based on the previous-hop node BAP address, the ingress link RLC channel ID, and the next-hop node BAP address.

[0059] The IAB-donor DU stores the routing configuration (BH routing configuration) and the downlink RLC channel mapping configuration (Downlink Traffic to BH RLC Channel Mapping Configuration). The IAB-donor DU is routed based on the routing configuration, RLC channel mapping configuration, and the Routing ID in the BAP layer packet header. The routing configuration includes the mapping between the Routing ID and the next-hop node address. The downlink RLC channel mapping configuration includes the mapping between the destination IP address, DSCP (Differentiated Services Code Point), and the next-hop node address and the egress link RLC channel ID.

[0060] For each downlink data packet arriving at the IAB-donor DU, the IAB-donor DU uses the Routing ID in the packet header to query the next-hop node address from the routing configuration. Once the next-hop node address is determined, the outbound link RLC channel ID is retrieved from the downlink RLC channel mapping configuration based on the packet's IP address and DSCP.

[0061] The access IAB node stores uplink backhaul information (BH information), including the routing ID used by the service, the uplink backhaul RLC channel ID, and the next-hop node address. Based on the uplink BH information, the access IAB node configures the routing ID in the BAP layer packet header of the uplink service and selects the BH RLC channel and next-hop node for uplink service transmission.

[0062] The above schematically illustrates the routing of the IAB system and the BH RLC channel mapping.

[0063] Rel-17 NR has studied scenarios where the IAB node is stationary. It has standardized the process for changing the transmission path (also known as topology adaptation) between different donor-DUs under an F1-terminating donor-CU, as well as the process for changing the transmission path between an F1-terminating donor-CU and a non-F1-terminating donor-CU. Rel-18 NR will also study mobility scenarios.

[0064] Figure 8 illustrates a mobility scenario. For example, an IAB node 801 is mounted on a moving vehicle to serve user equipment (UEs) on the vehicle. Therefore, it is necessary to standardize the process for changing the transmission path of a mobile IAB node when it moves between multiple donor-CUs.

[0065] For a stationary IAB node, the physical cell identity (PCI) and physical random access channel (PRACH) resource configuration of its serving cell can remain fixed, because the network side can determine the neighboring cells of its serving cell (such as the macro cell or the serving cell of another IAB node) based on its fixed location, thereby controlling the PCI or PRACH resources of its serving cell to avoid conflict with the PCI or PRACH of the surrounding neighboring cells.

[0066] Figure 9 is another schematic diagram of a mobility scenario. As shown in Figure 9, due to the mobility of a mobile IAB node, its movement trajectory may involve the control areas of multiple different donor-CUs. The method of fixed PCI and fixed PRACH resources is not feasible for mobile IAB nodes. This is because if the PCI or PRACH resources of a mobile IAB node are fixed, the network side must ensure that the neighboring cells involved in its movement trajectory cannot be configured with the same PCI or PRACH resources. In the case of a large number of mobile IAB nodes, the resources available for other cells will be greatly reduced, making it impossible for the network side to support multiple mobile IAB nodes working simultaneously. Therefore, a feasible solution is for the network side to dynamically configure the PCI or PRACH resources of its serving cell based on the mobile location of the IAB node to avoid conflicts with the resources of the neighboring cells where it is located. However, there is currently no technology that supports dynamic PCI or PRACH resource configuration for IAB nodes.

[0067] On the other hand, the location of the UE accessing the cell can be determined by the NR cell global identifier (NCGI) and tracking area (TA) of the serving cell. The core network usually locates the UE based on the NCGI and TA of the UE serving cell. Therefore, the NCGI and TA of the serving cell are configured by the network side according to the location of the cell.

[0068] For stationary IAB nodes, the network side can configure the NCGI and TA of their service cells based on their locations. However, due to the mobility of mobile IAB nodes, their movement trajectories may involve multiple different donor-CU control areas, and the locations of their service cells are changing in the network. The fixed NCGI and TA method is not feasible for mobile IAB nodes, because the fixed NCGI and TA cannot reflect the actual location of the service cell of the mobile IAB node, and thus cannot reflect the actual location of the UE accessing the cell, making it impossible for the network side to obtain the actual location of the UE accessing the mobile IAB node. Therefore, a feasible solution is for the network side to dynamically configure the NCGI and TA of its service cell based on the mobile location of the IAB node to reflect the actual location of the UE accessing the cell. However, there is currently no technology that supports dynamic NCGI configuration and / or TA configuration.

[0069] In the embodiments of the present application, unless otherwise specified, an IAB node device includes a migration node or its child nodes. Furthermore, while the PCI, NCGI, and TA are used as examples above, the present application is not limited thereto. For example, other information related to a mobile IAB node may also be used. The embodiments of the present application are also not limited to IAB nodes and are also applicable to network-controlled repeaters (NCRs), for example.

[0070] The following further describes the embodiments of the present application.

[0071] Embodiments of the first aspect

[0072] An embodiment of the present application provides a configuration method for a mobile node, wherein the F1 connection of the DU of the mobile node is terminated at a first donor-CU, that is, the first donor-CU is the F1-terminating donor-CU of the mobile node.

[0073] FIG10 is a schematic diagram of a method for configuring a mobile node according to an embodiment of the present application. As shown in FIG10 , the method includes:

[0074] 1001. A first donor-CU configures or reconfigures second information related to a first cell for a DU of a mobile node based on first information related to a location of the mobile node; and

[0075] 1002. The first donor-CU sends the configured or reconfigured second information related to the first cell to the DU of the mobile node.

[0076] Therefore, the first donor-CU of the embodiment of the present application can dynamically configure the second information related to the cell within the mobile area (such as the cell identifier) ​​for the mobile node based on the first information related to the location of the mobile node (such as the real-time location information); thereby avoiding the conflict between the mobile node and the adjacent cell, so that the network supports multiple mobile nodes to work simultaneously.

[0077] It is worth noting that FIG10 above is merely a schematic illustration of an embodiment of the present application, and the present application is not limited thereto. For example, the execution order of the various operations may be appropriately adjusted, and other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above description, and are not limited to the description of FIG10 above.

[0078] In some embodiments, the first donor-CU is an F1-terminating donor-CU for multiple mobile nodes within a designated area; when the multiple mobile nodes move within the designated area, the F1 connections of the IAB-DUs of the multiple mobile nodes always terminate at the first donor-CU.

[0079] For example, a carrier designates a specific donor-CU as the centrally controlled donor-CU for mobile IAB nodes within a designated area. The F1 connections of IAB nodes moving within the designated area always terminate at this centrally controlled donor-CU. IAB nodes can change the non-F1-terminating donor-CU based on their real-time location and migrate the transmission path to the donor-DU under the latest non-F1-terminating donor-CU without changing the F1-terminating donor-CU.

[0080] In some embodiments, the first donor-CU sends the configured or reconfigured second information related to the first cell to the DU of the mobile node through a first F1AP message.

[0081] For example, the first F1AP message includes an F1 setup response message or a gNB CU configuration update message.

[0082] In some embodiments, the second information includes at least one of the following: a physical cell identity (PCI), an NR cell global identity (NCGI), a tracking area code (TAC), and a physical random access channel (PRACH) resource configuration. The present application is not limited thereto, and for example, may include one or more of the above information, or may include other information.

[0083] In some embodiments, before the first donor-CU configures or reconfigures the second information related to the first cell for the DU of the mobile node, the first donor-CU may also receive the second information of the currently configured first cell sent by the DU of the mobile node through a second F1AP message, or the first donor-CU may also receive the second information of the third cell sent by the second donor-CU, wherein the second donor-CU is a non-F1 terminated donor-CU of the mobile node.

[0084] For example, the second F1AP message includes an F1 Setup Request message or a gNB DU Configuration Update message. By having the mobile node report the currently configured second information, the first donor-CU can better understand the current configuration information of the first cell of the mobile node, thereby more accurately configuring or reconfiguring the second information related to the first cell.

[0085] For another example, the current non-F1 terminated donor-CU of the mobile IAB node can send the PCI, NCGI, TAC and PRACH configuration of the neighboring cell of the DU of the mobile IAB node (for example, the cell detected by the mobile terminal it serves) to the F1 terminated donor-CU, so that the centrally controlled donor-CU can configure the PCI, NCGI, TAC and PRACH resources for the DU of the mobile node according to the PCI, NCGI, TAC and PRACH resources of the neighboring cell of the DU of the mobile IAB node, thereby avoiding the conflict between the cell of the DU of the mobile node and the PCI or PRACH resources of the neighboring cell, or making the TAC and NCGI of the cell of the DU of the mobile node consistent with those of the neighboring cell.

[0086] In some embodiments, the first location-related information of the mobile node includes: location information of the mobile node or information of the cell accessed by the mobile terminal (MT), and / or second information related to the second cell detected and reported by the mobile terminal (MT) served by the first cell.

[0087] For example, the centrally controlled donor-CU can configure the PCI, NCGI and TAC for the DU of the mobile IAB node based on the location information or network positioning information registered by the mobile IAB node in the core network, or based on the service cell accessed by the MT of the IAB node indicated by the current non-F1-terminating donor-CU (that is, the donor-CU to which the IAB-MT of the IAB node accesses). The configuration information can be sent to the mobile IAB node using an F1AP message.

[0088] For another example, the centrally controlled donor-CU can configure the PCI, NCGI, and TAC for the DU of the mobile IAB node based on the PCI, NCGI, TAC, and PRACH resources of the neighboring cells of the DU of the mobile IAB node. This ensures that the PCI and PRACH resources of the mobile IAB node do not conflict with those of neighboring cells, and that the NCGI and TAC of the mobile IAB node change according to its actual geographic location. This allows the network to obtain the actual location information of the UE accessing the mobile IAB node.

[0089] In some embodiments, the non-F1-terminating donor-CU of the mobile node is changed from the second donor-CU to the third donor-CU; the first donor-CU also receives the first location-related information of the mobile node sent by the second donor-CU or the third donor-CU.

[0090] In some embodiments, the physical cell identifier (PCI) configured or reconfigured for the first cell does not conflict with the PCI of the neighboring cell, the NR cell global identifier (NCGI) configured or reconfigured for the first cell is related to the NCGI of the neighboring cell, the tracking area code (TAC) configured or reconfigured for the first cell is the same as or related to the TAC of the neighboring cell, and the PRACH resources configured or reconfigured for the first cell do not conflict with the PRACH resources of the neighboring cell.

[0091] Figure 11 is an example diagram of a configuration method for a mobile node according to an embodiment of the present application. As shown in Figure 11 , the C donor-CU serves as a centralized control CU within the mobile range of the vehicle-mounted IAB node, and an F1 connection is established between the IAB node and the C donor-CU.

[0092] When donor-CU1 serves as a non-F1-terminating donor-CU, the parent node of the IAB node is donor-DU1, and the F1 transmission path passes through donor-DU1. At this time, according to the location of the IAB node (the serving cell of the parent node has PCI=1, TAC=A, and NCGI=k), the PCI configured by the C donor-CU for the serving cell of the IAB node is 2, TAC is A, and NCGI=k+1, and is configured to the IAB node through the F1AP message (GNB-CU CONFIGURATION UPDATE).

[0093] Therefore, the parent node's serving cell PCI is 1, while the IAB node's serving cell PCI is 2. These differences prevent the mobile IAB node's PCI from conflicting with neighboring cells. The parent node's serving cell TAC is A and NCGI is k, while the IAB node's serving cell TAC is A and NCGI is k+1. These two are identical or correlated, allowing the network to obtain the actual location information of the UE accessing the mobile IAB node.

[0094] When the IAB node moves to donor-DU2, donor-CU2 becomes the new non-F1-terminating CU, and the F1 transmission path migrates to donor-DU2. At this time, according to the location of the IAB node (the parent node's serving cell PCI = 2, TAC = B, NCGI = m), the C donor-CU configures the serving cell of the IAB node with PCI 1, TAC B, and NCGI = m+1, and configures it to the IAB node through the F1AP message (GNB-CU CONFIGURATION UPDATE).

[0095] Therefore, the parent node's serving cell PCI is 2, while the IAB node's serving cell PCI is 1. These differences prevent the mobile IAB node's PCI from conflicting with neighboring cells. The parent node's serving cell TAC is B and NCGI is m, while the IAB node's serving cell TAC is B and NCGI is m+1. These two are identical or correlated, allowing the network to obtain the actual location information of the UE accessing the mobile IAB node.

[0096] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0097] As can be seen from the above embodiment, the first donor-CU configures or reconfigures second information for the DU of the mobile node based on the first information of the mobile node, and sends the second information to the DU of the mobile node. Thus, the first donor-CU can dynamically configure information for the mobile node within the mobile area based on the real-time location information of the mobile node, thereby avoiding conflicts between the mobile node and neighboring cells, and enabling the network to support the simultaneous operation of multiple mobile nodes.

[0098] Embodiments of the second aspect

[0099] The embodiment of the present application provides an IAB integration method, which can be combined with the embodiment of the first aspect or implemented separately. The same contents as those of the embodiment of the first aspect will not be repeated here.

[0100] FIG12 is a schematic diagram of an IAB integration method according to an embodiment of the present application. As shown in FIG12 , the method includes:

[0101] 1201, the MT of the mobile node establishes an RRC connection with the second donor-CU;

[0102] 1202, the DU of the mobile node is configured with the IP address of the first donor-CU by the OAM entity;

[0103] 1203. After the MT of the mobile node receives the RRC connection reconfiguration message sent by the second donor-CU, the DU of the mobile node uses the IP address allocated by the second donor-CU to initiate F1 connection establishment with the first donor-CU; wherein, the RRC connection reconfiguration message includes the IP address and BAP layer address allocated by the second donor-CU to the mobile node, and the F1 connection establishment request message sent by the DU of the IAB node carries the BAP layer address.

[0104] It is worth noting that FIG12 above is merely a schematic illustration of an embodiment of the present application, and the present application is not limited thereto. For example, the execution order of the various operations may be appropriately adjusted, and other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above description, and are not limited to the description of FIG12 above.

[0105] In some embodiments, the first donor-CU is an F1-terminating donor-CU of the mobile node, and the second donor-CU is a non-F1-terminating donor-CU of the mobile node.

[0106] In some embodiments, the first donor-CU is an F1-terminating donor-CU for multiple mobile nodes within a designated area; when the multiple mobile nodes move within the designated area, the F1 connections of the IAB-DUs of the multiple mobile nodes always terminate at the first donor-CU.

[0107] In some embodiments, the DU of the mobile node reports to the first donor-CU through a gNB DU configuration update message an IP address selected for use from the IP addresses allocated by the second donor-CU.

[0108] In some embodiments, the first donor-CU determines the second donor-CU based on the IP address selected by the mobile node, and sends a transmission migration management request message to the second donor-CU; and the first donor-CU receives the transmission migration management response message sent by the second donor-CU.

[0109] The migration management request message includes the downlink transport network layer (TNL) information used by the second donor-CU to configure layer 2 mapping for the donor-DU and the BAP layer address of the mobile IAB node, so that the second donor-CU can identify which IAB node the migration management request message is for based on the BAP layer address.

[0110] The following further illustrates the IAB integration process of the embodiment of the present application through signaling interaction.

[0111] FIG13 is a signaling flow chart of IAB integration according to an embodiment of the present application.

[0112] As shown in Figure 13, during the IAB-MT setup phase, the IAB-MT connects to the network, similar to a UE, and completes RRC connection establishment to the donor-CU, IAB-MT context establishment, core network authentication, IAB-MT radio bearer configuration, and PDU session establishment related to OAM services. During RRC connection establishment, the IAB-MT indicates to the donor-CU that it has IAB node capabilities. The RRC connection reconfiguration message includes the IP address and BAP layer address assigned by the donor-CU to the IAB node.

[0113] During the backhaul RLC channel establishment phase, at least one default BH RLC channel for non-UP services is established, and a BAP address and a default uplink routing ID are configured for the IAB-node.

[0114] In the routing update phase, the routing table of the upstream node of the IAB-node is updated, and an IP address is allocated to the IAB-node.

[0115] During the IAB-DU setup phase, the IAB-DU is configured with the IP address of the F1-terminating CU (i.e., C donor-CU) by OAM. The IAB-DU uses the IP address assigned by the donor-CU to initiate an F1 connection with the C donor-CU. The F1 connection establishment request carries the BAP layer address assigned by the donor-CU to the IAB node.

[0116] When reporting TNL information to the C donor-CU for F1-U or non-UP traffic, the IAB-DU reports to the C donor-CU the actual IP addresses used from the IP addresses allocated by the donor-CU (e.g., via the gNB-DU CONFIGURATION UPDATE message), including the IP addresses used for F1-U or non-UP traffic.

[0117] As shown in Figure 13, the C donor-CU determines the donor-CU to which the IAB-MT accesses based on the IP address information reported by the IAB-DU, and sends an IAB TRANSPORT MIGRATION MANAGEMENT REQUEST to the donor-CU, which contains the context of the non-UP service, including the DL TNL information used by the donor-CU to configure downlink mapping for the donor-DU and the BAP layer address of the IAB node.

[0118] As shown in Figure 13 , the donor-CU determines that the IAB TRANSPORT MIGRATION MANAGEMENT REQUEST is for the IAB node based on the BAP layer address, and sends an IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE message to the C donor-CU, which includes the DSCP / IPv6 flow label for transmitting downlink non-UP services.

[0119] The above signaling process is merely an illustrative example of the present application, but the present application is not limited thereto. For more specific information about the signaling process, please refer to the relevant art. Furthermore, for example, the execution order of the various operations may be appropriately adjusted, and other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above content, and are not limited to the description in FIG. 13 above.

[0120] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0121] As can be seen from the above embodiment, the IAB-DU does not necessarily establish an F1 connection with the IAB-MT's initial access donor-CU, but rather with the centrally controlled CU (i.e., the first donor-CU or C donor-CU). Therefore, centralized control of the donor-CU can further improve the service stability of the mobile node.

[0122] Embodiments of the third aspect

[0123] The present embodiment provides a host device, and the contents identical to those in the embodiment of the first aspect are not repeated here. The device may be, for example, an IAB donor-CU in an IAB system (such as the first donor-CU in the embodiments of the first and second aspects), or may be one or more components, assemblies, or modules configured in the IAB donor-CU.

[0124] FIG14 is a schematic diagram of a host device according to an embodiment of the present application. As shown in FIG14 , the host device 1400 includes:

[0125] a configuration unit 1401 configured to configure or reconfigure second information related to a first cell for a DU of the mobile node based on the first information related to the location of the mobile node; and

[0126] The communication unit 1402 sends the configured or reconfigured second information related to the first cell to the DU of the mobile node.

[0127] In some embodiments, the host device is an F1 termination donor centralized unit (donor-CU) for multiple mobile nodes within a designated area; when the multiple mobile nodes move within the designated area, the F1 connections of the DUs of the multiple mobile nodes always terminate at the host device.

[0128] In some embodiments, the host device sends the configured or reconfigured second information related to the first cell to the DU of the mobile node through a first F1AP message.

[0129] In some embodiments, the first F1AP message includes an F1 setup response message or a gNB CU configuration update message.

[0130] In some embodiments, the second information includes at least one of the following: physical cell identity (PCI), NR cell global identity (NCGI), tracking area code (TAC), and physical random access channel (PRACH) resource configuration.

[0131] In some embodiments, before the configuration unit 1401 configures or reconfigures the second information related to the first cell for the DU of the mobile node, the communication unit 1402 receives the second information of the currently configured first cell sent by the DU of the mobile node via a second F1AP message.

[0132] In some embodiments, the second F1AP message includes an F1 setup request message or a gNB DU configuration update message.

[0133] In some embodiments, before the configuration unit 1401 configures or reconfigures the second information related to the first cell for the DU of the mobile node, the communication unit 1402 also receives second information of the third cell sent by the second donor-CU, wherein the second donor-CU is a non-F1-terminating donor-CU of the mobile node.

[0134] In some embodiments, the first location-related information of the mobile node includes: location information of the mobile node or information of the cell accessed by the MT, and / or second information related to the second cell detected and reported by the mobile terminal (MT) served by the first cell.

[0135] In some embodiments, the communication unit 1402 sends the second information related to the second cell or the second information related to the third cell to the DU of the mobile node through a third F1AP message, so that the DU of the mobile node autonomously adjusts the configuration of PCI, PRACH, TAC and NCGI.

[0136] In some embodiments, the non-F1-terminating donor-CU of the mobile node changes from the second donor-CU to the third donor-CU; the communication unit 1402 receives the first information related to the location of the mobile node sent by the second donor-CU or the third donor-CU.

[0137] In some embodiments, the physical cell identifier (PCI) configured or reconfigured for the first cell does not conflict with the PCI of the neighboring cell, the NR cell global identifier (NCGI) configured or reconfigured for the first cell is related to the NCGI of the neighboring cell, the tracking area code (TAC) configured or reconfigured for the first cell is the same as or related to the TAC of the neighboring cell, and the PRACH resources configured or reconfigured for the first cell do not conflict with the PRACH resources of the neighboring cell.

[0138] In some embodiments, the communication unit 1402 establishes an F1 connection with the DU of the mobile node;

[0139] The MT of the mobile node establishes an RRC connection with the second donor-CU; the DU of the mobile node is configured with the IP address of the first donor-CU by the OAM entity; and after the MT of the mobile node receives the RRC connection reconfiguration message sent by the second donor-CU, the DU of the mobile node uses the IP address allocated by the second donor-CU to initiate an F1 connection establishment with the host device; wherein the RRC connection reconfiguration message includes the IP address and BAP layer address allocated by the second donor-CU to the mobile node, and the F1 connection establishment request sent by the DU of the mobile node carries the BAP layer address.

[0140] In some embodiments, the communication unit 1402 further receives an IP address selected for use from the IP addresses allocated by the second donor-CU, which is reported by the DU of the mobile node through a gNB DU configuration update message.

[0141] In some embodiments, the communication unit 1402 determines the second donor-CU based on the IP address selected by the mobile node, and sends a transmission migration management request message to the second donor-CU, wherein the migration management request message includes the downlink transmission network layer (TNL) information and the BAP layer address used by the second donor-CU to configure layer 2 mapping for the donor-DU; and receives the transmission migration management response message sent by the second donor-CU.

[0142] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0143] It is worth noting that the above only describes the components or modules related to the present application, but the present application is not limited thereto. The host device 1400 of the embodiment of the present application may also include other components or modules. For the specific contents of these components or modules, reference may be made to the relevant art.

[0144] In addition, for the sake of simplicity, FIG14 only illustrates the connection relationship or signal direction between various components or modules. However, it should be clear to those skilled in the art that various related technologies such as bus connection can be used. The above-mentioned components or modules can be implemented by hardware facilities such as processors, memories, transmitters, and receivers; the implementation of this application is not limited to this.

[0145] As can be seen from the above embodiment, the host device configures or reconfigures second information for the mobile node's DU based on the mobile node's first information and sends the second information to the mobile node's DU. Thus, the host device can dynamically configure information for the mobile node within its mobile area based on the mobile node's real-time location information, thereby preventing the mobile node from conflicting with neighboring cells and enabling the network to support the simultaneous operation of multiple mobile nodes.

[0146] Embodiments of the fourth aspect

[0147] The present application provides a mobile node. The same contents as those in the first and second aspects of the present application are not further described. The mobile node may be, for example, an IAB node in an IAB system (such as the mobile IAB node in the first and second aspects of the present application), or may be one or more components, assemblies, or modules configured in the IAB node.

[0148] Figure 15 is a schematic diagram of a mobile node according to an embodiment of the present application. As shown in Figure 15, the mobile node 1500 includes a mobile terminal (MT) and a distributed unit (DU);

[0149] The F1 connection of the distribution unit (DU) is terminated at a first host centralized unit (donor-CU), and the DU of the mobile node receives the second information related to the first cell sent by the first donor-CU; wherein the second information related to the first cell is configured or reconfigured by the first donor-CU according to the first information related to the location of the mobile node.

[0150] In some embodiments, the first donor-CU is an F1-terminating donor-CU for multiple mobile nodes within a designated area; when the multiple mobile nodes move within the designated area, the F1 connections of the DUs of the multiple mobile nodes always terminate at the first donor-CU.

[0151] In some embodiments, the second information includes at least one of the following: a physical cell identity (PCI), an NR cell global identity (NCGI), a tracking area code (TAC), and a physical random access channel (PRACH) resource configuration;

[0152] The first location-related information of the mobile node includes: location information of the mobile node or information of a cell accessed by the MT, and / or second information related to a second cell detected and reported by a mobile terminal (MT) served by the first cell.

[0153] In some embodiments, the MT of the mobile node establishes an RRC connection with the second donor-CU; the DU of the mobile node is configured with the IP address of the first donor-CU by the OAM entity; and after the MT of the mobile node receives the RRC connection reconfiguration message sent by the second donor-CU, the DU of the mobile node initiates an F1 connection establishment with the first donor-CU using the IP address allocated by the second donor-CU; wherein the RRC connection reconfiguration message includes the IP address and BAP layer address allocated by the second donor-CU to the mobile node, and the F1 connection establishment request sent by the DU of the mobile node carries the BAP layer address.

[0154] In some embodiments, the DU of the mobile node reports to the first donor-CU through a gNB DU configuration update message an IP address selected for use from the IP addresses allocated by the second donor-CU; the IP address selected for use by the mobile node is used by the first donor-CU to determine the second donor-CU.

[0155] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0156] It is worth noting that the above only describes the components or modules related to the present application, but the present application is not limited thereto. The mobile node 1500 of the embodiment of the present application may also include other components or modules. For the specific contents of these components or modules, reference may be made to the relevant art.

[0157] In addition, for the sake of simplicity, FIG15 only illustrates the connection relationship or signal direction between various components or modules. However, it should be clear to those skilled in the art that various related technologies such as bus connection can be used. The above-mentioned components or modules can be implemented by hardware facilities such as processors, memories, transmitters, and receivers; the implementation of this application is not limited to this.

[0158] As can be seen from the above embodiment, the host device configures or reconfigures second information for the mobile node's DU based on the mobile node's first information and sends the second information to the mobile node's DU. Thus, the host device can dynamically configure information for the mobile node within its mobile area based on the mobile node's real-time location information, thereby preventing the mobile node from conflicting with neighboring cells and enabling the network to support the simultaneous operation of multiple mobile nodes.

[0159] Embodiments of the fifth aspect

[0160] An embodiment of the present application provides a communication system, including a donor device and a mobile node (eg, an IAB-node). For details about the network architecture and specific contents of the donor device and the IAB node, reference may be made to related technologies, which will be omitted here.

[0161] In some embodiments, the IAB system includes: a host centralized unit and a mobile node; an F1 connection of a distribution unit (DU) of the mobile node is terminated at the host centralized unit;

[0162] The host centralized unit configures or reconfigures second information related to the first cell for the DU of the mobile node based on the first information related to the location of the mobile node; and sends the configured or reconfigured second information related to the first cell to the DU of the mobile node.

[0163] An embodiment of the present application further provides an IAB device, which may be an IAB host device or an IAB node (a migration node or a child node).

[0164] Figure 16 is a schematic diagram of an IAB device according to an embodiment of the present application. As shown in Figure 16 , IAB device 1600 may include a processor (e.g., a central processing unit (CPU)) 1601 and a memory 1602 ; the memory 1602 is coupled to the processor 1601 . The memory 1602 may store various data and may also store an information processing program 1605 , which is executed under the control of the CPU 1601 .

[0165] For example, the processor 1601 may be configured to execute a program to implement the configuration method of the mobile node in the embodiment of the first aspect. For example, the processor 1601 may be configured to perform the following control: configuring or reconfiguring second information related to the first cell for the DU of the mobile node based on the first information related to the location of the mobile node; and sending the configured or reconfigured second information related to the first cell to the DU of the mobile node.

[0166] For another example, the processor 1601 may be configured to execute a program to implement the IAB integration method in the embodiment of the second aspect. For example, the processor 1601 may be configured to perform the following control: the mobile node's mobile operator (MT) establishes an RRC connection with the second donor-CU; the mobile node's DU is configured with the IP address of the first donor-CU by the OAM entity; and after the mobile node's MT receives an RRC connection reconfiguration message sent by the second donor-CU, the mobile node's DU initiates an F1 connection establishment with the first donor-CU using the IP address allocated by the second donor-CU; wherein the RRC connection reconfiguration message includes the IP address and BAP layer address allocated by the second donor-CU to the mobile node, and the F1 connection establishment request sent by the mobile node's DU carries the BAP layer address.

[0167] Furthermore, as shown in FIG16 , IAB device 1600 may further include a transceiver 1603 and an antenna 1604. The functions of these components are similar to those in the prior art and are not further described here. It is worth noting that IAB device 1600 does not necessarily include all of the components shown in FIG16 . Furthermore, IAB device 1600 may also include components not shown in FIG16 , for which reference may be made to the prior art.

[0168] An embodiment of the present application further provides a computer-readable program, wherein when the program is executed in an IAB device, the program causes the computer to execute the mobile node configuration method of the embodiment of the first aspect or the IAB integration method of the embodiment of the second aspect in the IAB device.

[0169] An embodiment of the present application further provides a storage medium storing a computer-readable program, wherein the computer-readable program enables a computer to execute the mobile node configuration method of the first embodiment or the IAB integration method of the second embodiment in an IAB device.

[0170] The above devices and methods of the present application can be implemented by hardware or by a combination of hardware and software. The present application relates to such a computer-readable program that, when executed by a logic component, enables the logic component to implement the devices or components described above, or enables the logic component to implement the various methods or steps described above. The logic component is, for example, a field programmable logic component, a microprocessor, a processor used in a computer, etc. The present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.

[0171] The method / device described in conjunction with the embodiments of the present application can be directly embodied as hardware, a software module executed by a processor, or a combination of the two. For example, one or more of the functional block diagrams shown in the figure and / or one or more combinations of functional block diagrams can correspond to various software modules of the computer program flow or to various hardware modules. These software modules can respectively correspond to the various steps shown in the figure. These hardware modules can be implemented by solidifying these software modules, for example, using a field programmable gate array (FPGA).

[0172] The software module may be located in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. A storage medium may be coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium; or the storage medium may be an integral part of the processor. The processor and the storage medium may be located in an ASIC. The software module may be stored in the memory of the mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a large-capacity MEGA-SIM card or a large-capacity flash memory device, the software module may be stored in the MEGA-SIM card or the large-capacity flash memory device.

[0173] One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may be implemented as a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or any appropriate combination thereof for performing the functions described in this application. One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.

[0174] The present application has been described above in conjunction with specific embodiments. However, those skilled in the art should understand that these descriptions are merely illustrative and are not intended to limit the scope of protection of the present application. Those skilled in the art may make various modifications and variations to the present application based on the spirit and principles of the present application, and such modifications and variations are also within the scope of the present application.

[0175] Regarding the above implementation methods disclosed in this embodiment, the following additional notes are also disclosed:

[0176] 1. A method for configuring a mobile node, wherein an F1 connection of a distributed unit (DU) of the mobile node is terminated at a first donor-CU, the method comprising:

[0177] The first donor-CU configures or reconfigures second information related to the first cell for the DU of the mobile node based on the first information related to the location of the mobile node; and

[0178] The first donor-CU sends the configured or reconfigured second information related to the first cell to the DU of the mobile node.

[0179] 2. The method according to Note 1, wherein the first donor-CU is an F1-terminating donor-CU for multiple mobile nodes within a specified area; when the multiple mobile nodes move within the specified area, the F1 connections of the IAB-DUs of the multiple mobile nodes always terminate at the first donor-CU.

[0180] 3. The method according to Note 1 or 2, wherein the first donor-CU sends the configured or reconfigured second information related to the first cell to the DU of the mobile node through a first F1AP message.

[0181] 4. The method according to Note 3, wherein the first F1AP message includes an F1 establishment response message or a gNB CU configuration update message.

[0182] 5. A method according to any one of Notes 1 to 4, wherein the second information includes at least one of the following: a physical cell identifier (PCI), an NR cell global identifier (NCGI), a tracking area code (TAC), and a physical random access channel (PRACH) resource configuration.

[0183] 6. The method according to any one of Notes 1 to 5, wherein, before the first donor-CU configures or reconfigures the second information related to the first cell for the DU of the mobile node, the method further includes:

[0184] The first donor-CU receives second information of the currently configured first cell sent by the DU of the mobile node through a second F1AP message.

[0185] 7. The method according to Note 6, wherein the second F1AP message includes an F1 establishment request message or a gNB DU configuration update message.

[0186] 8. The method according to any one of Notes 1 to 5, wherein, before the first donor-CU configures or reconfigures the second information related to the first cell for the DU of the mobile node, the method further includes:

[0187] The first donor-CU receives second information of a third cell sent by a second donor-CU, wherein the second donor-CU is a non-F1-terminating donor-CU of the mobile node.

[0188] 9. A method according to any one of Notes 1 to 8, wherein the first location-related information of the mobile node includes: the location information of the mobile node or the cell information accessed by the MT, and / or the second information related to the second cell detected and reported by the mobile terminal (MT) served by the first cell.

[0189] 10. The method according to Supplementary Note 9, further comprising:

[0190] The first donor-CU sends the second information related to the second cell or the second information related to the third cell to the DU of the mobile node through a third F1AP message.

[0191] 11. The method according to any one of Notes 1 to 10, wherein the non-F1 termination donor-CU of the mobile node is changed from the second donor-CU to the third donor-CU;

[0192] The method further comprises:

[0193] The first donor-CU receives first information related to the location of the mobile node sent by the second donor-CU or the third donor-CU.

[0194] 12. The method according to Note 11, wherein the physical cell identifier (PCI) configured or reconfigured for the first cell does not conflict with the PCI of the adjacent cell, the NR cell global identifier (NCGI) configured or reconfigured for the first cell is related to the NCGI of the adjacent cell, the tracking area code (TAC) configured or reconfigured for the first cell is the same as or related to the TAC of the adjacent cell, and the PRACH resources configured or reconfigured for the first cell do not conflict with the PRACH resources of the adjacent cell.

[0195] 13. The method according to any one of Notes 1 to 12, wherein the method further comprises:

[0196] The first donor-CU establishes an F1 connection with the DU of the mobile node;

[0197] The MT of the mobile node establishes an RRC connection with the second donor-CU; the DU of the mobile node is configured with the IP address of the first donor-CU by the OAM entity; and after the MT of the mobile node receives the RRC connection reconfiguration message sent by the second donor-CU, the DU of the mobile node initiates an F1 connection establishment with the first donor-CU using the IP address allocated by the second donor-CU; the RRC connection reconfiguration message includes the IP address and BAP layer address allocated by the second donor-CU to the mobile node, and the F1 connection establishment request sent by the DU of the mobile node carries the BAP layer address.

[0198] 14. The method according to Supplementary Note 13, further comprising:

[0199] The first donor-CU also receives an IP address reported by the DU of the mobile node through a gNB DU configuration update message, and is selected for use from the IP addresses allocated by the second donor-CU.

[0200] 15. The method according to Supplement 14, further comprising:

[0201] The first donor-CU determines the second donor-CU according to the IP address selected by the mobile node, and sends a transport migration management request message to the second donor-CU, wherein the migration management request message includes downlink transport network layer (TNL) information and the BAP layer address used by the second donor-CU to configure layer 2 mapping for the donor-DU; and

[0202] The first donor-CU receives the transmission migration management response message sent by the second donor-CU.

[0203] 16. A method for configuring a mobile node, wherein an F1 connection of a distributed unit (DU) of the mobile node is terminated at a first donor-CU, the method comprising:

[0204] The DU of the mobile node receives second information related to the first cell sent by the first donor-CU;

[0205] The second information related to the first cell is configured or reconfigured by the first donor-CU according to the first information related to the location of the mobile node.

[0206] 17. The method according to Note 16, wherein the first donor-CU is an F1-terminating donor-CU of multiple mobile nodes within a specified area; when the multiple mobile nodes move within the specified area, the F1 connections of the DUs of the multiple mobile nodes always terminate at the first donor-CU.

[0207] 18. The method according to Note 16 or 17, wherein the DU of the mobile node receives the configured or reconfigured second information related to the first cell through a first F1AP message.

[0208] 19. The method according to Note 18, wherein the first F1AP message includes an F1 establishment response message or a gNB CU configuration update message.

[0209] 20. A method according to any one of Notes 16 to 19, wherein the second information includes at least one of the following: a physical cell identifier (PCI), an NR cell global identifier (NCGI), a tracking area code (TAC), and a physical random access channel (PRACH) resource configuration.

[0210] 21. The method according to any one of Notes 16 to 20, wherein, before the first donor-CU configures or reconfigures the second information related to the first cell for the DU of the mobile node, the method further comprises:

[0211] The DU of the mobile node sends second information of the currently configured first cell to the first donor-CU through a second F1AP message.

[0212] 22. The method according to Note 21, wherein the second F1AP message includes an F1 establishment request message or a gNB DU configuration update message.

[0213] 23. A method according to any one of Notes 16 to 22, wherein the first location-related information of the mobile node includes: the location information of the mobile node or the cell information accessed by the MT, and / or the second information related to the second cell detected and reported by the mobile terminal (MT) served by the first cell.

[0214] 24. The method according to Supplementary Note 23, further comprising:

[0215] The DU of the mobile node receives the second information related to the second cell or the second information related to the third cell sent by the first donor-CU through a third F1AP message.

[0216] 25. The method according to any one of Notes 16 to 24, wherein the non-F1-terminating donor-CU of the mobile node is changed from the second donor-CU to the third donor-CU.

[0217] 26. The method according to Note 25, wherein the physical cell identifier (PCI) configured or reconfigured for the first cell does not conflict with the PCI of the adjacent cell, the NR cell global identifier (NCGI) configured or reconfigured for the first cell is related to the NCGI of the adjacent cell, the tracking area code (TAC) configured or reconfigured for the first cell is the same as or related to the TAC of the adjacent cell, and the PRACH resources configured or reconfigured for the first cell do not conflict with the PRACH resources of the adjacent cell.

[0218] 27. The method according to any one of Notes 16 to 26, wherein the method further comprises:

[0219] The MT of the mobile node establishes an RRC connection with the second donor-CU;

[0220] The DU of the mobile node is configured with the IP address of the first donor-CU by the OAM entity; and

[0221] After the MT of the mobile node receives the RRC connection reconfiguration message sent by the second donor-CU, the DU of the mobile node uses the IP address allocated by the second donor-CU to initiate F1 connection establishment with the first donor-CU; wherein the RRC connection reconfiguration message includes the IP address allocated by the second donor-CU to the mobile node.

[0222] 28. The method according to Supplementary Note 27, further comprising:

[0223] The DU of the mobile node reports to the first donor-CU through a gNB DU configuration update message an IP address selected for use from the IP addresses allocated by the second donor-CU.

[0224] 29. The method according to Note 28, wherein the IP address selected for use by the mobile node is used by the first donor-CU to determine the second donor-CU.

[0225] 30. An IAB integration method comprising:

[0226] The MT of the mobile node establishes an RRC connection with the second donor-CU;

[0227] The DU of the mobile node is configured with the IP address of the first donor-CU by the OAM entity; and

[0228] After the MT of the mobile node receives the RRC connection reconfiguration message sent by the second donor-CU, the DU of the mobile node uses the IP address allocated by the second donor-CU to initiate F1 connection establishment with the first donor-CU; wherein, the RRC connection reconfiguration message includes the IP address and BAP layer address allocated by the second donor-CU to the mobile node, and the F1 connection establishment request sent by the DU of the mobile node carries the BAP layer address.

[0229] 31. The method according to Supplementary Note 30, further comprising:

[0230] The DU of the mobile node reports to the first donor-CU through a gNB DU configuration update message an IP address selected for use from the IP addresses allocated by the second donor-CU.

[0231] 32. An IAB integration method comprising:

[0232] The second donor-CU establishes an RRC connection with the MT of the mobile node;

[0233] The DU of the mobile node is configured with the IP address of the first donor-CU by the OAM entity; and after the MT of the mobile node receives the RRC connection reconfiguration message sent by the second donor-CU, the DU of the mobile node uses the IP address allocated by the second donor-CU to initiate F1 connection establishment with the first donor-CU; the RRC connection reconfiguration message includes the IP address and BAP layer address allocated by the second donor-CU to the mobile node, and the F1 connection establishment request sent by the DU of the mobile node carries the BAP layer address.

[0234] 33. The method according to Supplementary Note 32, further comprising:

[0235] The second donor-CU receives the transport migration management request message sent by the first donor-CU; wherein the first donor-CU determines the second donor-CU according to the IP address selected by the mobile node, and the migration management request message includes downlink transport network layer (TNL) information and the BAP layer address used by the second donor-CU to configure layer 2 mapping for the donor-DU; and

[0236] The second donor-CU sends a transmission migration management response message to the first donor-CU.

[0237] 34. The method according to Supplement 32, wherein the method further comprises:

[0238] The second donor-CU sends second information of the third cell to the first donor-CU, wherein the second donor-CU is a non-F1-terminating donor-CU of the mobile node.

[0239] 35. An IAB node, comprising a memory and a processor, wherein the memory stores a computer program, wherein the processor is configured to execute the computer program to implement the mobile node configuration method as described in any one of Notes 16 to 29, or the IAB integration method as described in Note 30 or 31.

[0240] 36. An IAB donor device, comprising a memory and a processor, wherein the memory stores a computer program, wherein the processor is configured to execute the computer program to implement the mobile node configuration method as described in any one of Notes 1 to 15, or the IAB integration method as described in any one of Notes 32 to 34.

Claims

1. A host device, wherein: The F1 connection of the distribution unit of the mobile node is terminated at the host device, and the host device includes: a configuration unit configured to configure or reconfigure second information related to the first cell for the distribution unit of the mobile node based on the first information related to the location of the mobile node; and The communication unit sends the configured or reconfigured second information related to the first cell to the distribution unit of the mobile node.

2. The host device according to claim 1, wherein: The host device is an F1 termination host centralized unit for multiple mobile nodes in a designated area; when the multiple mobile nodes move within the designated area, the F1 connections of the distribution units of the multiple mobile nodes always terminate at the host device.

3. The device according to claim 1, wherein The host device sends the configured or reconfigured second information related to the first cell to the distribution unit of the mobile node through a first F1AP message.

4. The device according to claim 3, wherein The first F1AP message includes an F1 setup response message or a gNB CU configuration update message.

5. The apparatus according to claim 1, wherein The second information includes at least one of the following: a physical cell identifier, an NR cell global identifier, a tracking area code, and a physical random access channel resource configuration.

6. The apparatus according to claim 1, wherein Before the configuration unit configures or reconfigures the second information related to the first cell for the distribution unit of the mobile node, the communication unit receives the second information of the currently configured first cell sent by the distribution unit of the mobile node through a second F1AP message, or receives the second information of the third cell sent by a second host concentration unit, where the second host concentration unit is a non-F1 termination host concentration unit of the mobile node.

7. The apparatus according to claim 6, wherein The second F1AP message includes an F1 setup request message or a gNB DU configuration update message.

8. The apparatus according to claim 1, wherein The first information related to the location of the mobile node includes: the location information of the mobile node or the cell information accessed by the mobile terminal, and / or the second information related to the second cell detected and reported by the mobile terminal served by the first cell.

9. The apparatus according to claim 8, wherein The communication unit sends the second information related to the second cell or the second information related to the third cell to the distribution unit of the mobile node through a third F1AP message.

10. The apparatus according to claim 1, wherein The non-F1 termination host centralized unit of the mobile node changes from the second host centralized unit to the third host centralized unit; The communication unit receives first information related to the location of the mobile node sent by the second host concentration unit or the third host concentration unit.

11. The apparatus according to claim 10, wherein The physical cell identifier configured or reconfigured for the first cell does not conflict with the physical cell identifier of the adjacent cell, the NR cell global identifier configured or reconfigured for the first cell is related to the NR cell global identifier of the adjacent cell, the tracking area code configured or reconfigured for the first cell is the same as or related to the tracking area code of the adjacent cell, and the physical random access channel resources configured or reconfigured for the first cell do not conflict with the physical random access channel resources of the adjacent cell.

12. The apparatus according to claim 1, wherein The communication unit establishes an F1 connection with the distribution unit of the mobile node; In which, the mobile terminal of the mobile node establishes a wireless resource control connection with the second host centralized unit; the distribution unit of the mobile node is configured with the IP address of the first host centralized unit by the OAM entity; and after the mobile terminal of the mobile node receives the wireless resource control connection reconfiguration message sent by the second host centralized unit, the distribution unit of the mobile node uses the IP address allocated by the second host centralized unit to initiate the establishment of an F1 connection with the host device; wherein, the wireless resource control connection reconfiguration message includes the IP address and BAP layer address allocated by the second host centralized unit to the mobile node, and the F1 connection establishment request sent by the distribution unit of the mobile node carries the BAP layer address.

13. The apparatus according to claim 12, wherein The communication unit also receives an IP address selected for use from the IP addresses allocated by the second host centralized unit, reported by the distribution unit of the mobile node through a gNB DU configuration update message.

14. The apparatus according to claim 13, wherein The communication unit determines the second host centralized unit based on the IP address selected by the mobile node, and sends a transmission migration management request message to the second host centralized unit, wherein the migration management request message includes the downlink transmission network layer information and the BAP layer address used by the second host centralized unit to configure layer 2 mapping for the host distribution unit; and receives the transmission migration management response message sent by the second host centralized unit.

15. A mobile node comprising a mobile terminal and a distribution unit; an F1 connection of the distribution unit is terminated at a first host centralized unit, and the distribution unit of the mobile node receives second information related to a first cell sent by the first host centralized unit; in, The second information related to the first cell is configured or reconfigured by the first host central unit according to the first information related to the location of the mobile node.

16. The mobile node according to claim 15, wherein: The first host centralized unit is an F1 termination host centralized unit for multiple mobile nodes in a designated area; when the multiple mobile nodes move within the designated area, the F1 connections of the distribution units of the multiple mobile nodes always terminate at the first host centralized unit.

17. The mobile node according to claim 15, wherein: The second information includes at least one of the following: a physical cell identifier, an NR cell global identifier, a tracking area code, and a physical random access channel resource configuration; The first information related to the location of the mobile node includes: the location information of the mobile node or the cell information accessed by the mobile terminal, and / or the second information related to the second cell detected and reported by the mobile terminal served by the first cell.

18. The mobile node according to claim 15, wherein: The mobile terminal of the mobile node establishes a radio resource control connection with the second host centralized unit; The distribution unit of the mobile node is configured by the OAM entity with the IP address of the first host centralized unit; as well as After the mobile terminal of the mobile node receives the radio resource control connection reconfiguration message sent by the second host centralized unit, the distribution unit of the mobile node initiates F1 connection establishment with the first host centralized unit using the IP address allocated by the second host centralized unit; wherein, the radio resource control connection reconfiguration message includes the IP address and BAP layer address allocated to the mobile node by the second host centralized unit, and the F1 connection establishment request sent by the distribution unit of the mobile node carries the BAP layer address.

19. The mobile node according to claim 15, wherein: The distribution unit of the mobile node reports the IP address selected for use from the IP addresses allocated by the second host centralized unit to the first host centralized unit through a gNB DU configuration update message; the IP address selected for use by the mobile node is used by the first host centralized unit to determine the second host centralized unit.

20. An integrated access and backhaul IAB system comprising a host centralized unit and a mobile node; the F1 connection of the distribution unit of the mobile node is terminated at the host centralized unit, The host centralized unit configures or reconfigures second information related to the first cell for the distribution unit of the mobile node based on the first information related to the location of the mobile node; and sends the configured or reconfigured second information related to the first cell to the distribution unit of the mobile node.

Images