Method for setting a mobile node, mobile node, and donor device

Abstract

In an embodiment of the present invention, a method for setting a mobile node, a mobile node, and a donor device are provided. The F1 connection of the distributed unit (DU) of the mobile node is terminated at a first donor-CU, and the first donor-CU sets or re-sets second information regarding a first cell for the DU of the mobile node based on first information regarding the position of the mobile node, and the first donor-CU transmits the second information regarding the first cell that has been set or re-set to the DU of the mobile node.

Description

Technical Field

[0001] The present invention relates to the technical field of communications.

Background Art

[0002] The deployment of future seamless cellular networks requires the deployment of very flexible and ultra-high-density new radio (NR) cells, and ultra-high-density networks are one of the goals of 5G. The deployment of one NR network that does not require a wired backhaul is very important for the realization of 5G ultra-high-density networks. Since the cell coverage is reduced by 5G millimeter waves, a wireless self-backhaul system requires multi-hop to meet the deployment needs. With the high bandwidth, massive multiple-input multiple-output (MIMO) and beam system of 5G, 5G makes it easier to develop a wireless self-backhaul system for ultra-high-density NR cells than LTE. To develop such a multi-hop system with wireless self-backhaul, the 3rd Generation Partnership Project (3GPP) has started the research and standardization of the Integrated Access and Backhaul (IAB) project in Release 16.

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

[0004] In the IAB network architecture, a relay node refers to an IAB-node (IAB node), which simultaneously supports access and backhaul functions. The access node at the last hop on the network side is called an IAB-donnor (IAB donor), which supports the functions of a gNB and also supports the access of IAB-nodes. All UE data can be backhauled to the IAB-donor via one hop or multiple hops through IAB-nodes.

[0005] The functions of an IAB-node are divided into two parts. One part is the gNB-DU function, called IAB-DU (Distributed Unit), and the other part is the UE function, called IAB-MT (Mobile Terminal). IAB-DU realizes the network-side device functions, serves one or more cells, and is connected to downstream child IAB-nodes (child IAB nodes (or abbreviated as child nodes)), provides NR air interface access to UEs and downstream child IAB-nodes, and also establishes an F1 connection with the IAB donor-CU (donor central unit). IAB-MT realizes some terminal device functions and is connected to the upstream parent IAB-node (parent IAB node (or abbreviated as parent node)) or IAB donor-DU. IAB-MT includes the functions of the physical layer, layer 2, RRC (Radio Resource Control), and NAS (Non-Access Stratum) layers, and is also indirectly connected to the IAB Donor-CU and the core network (CN).

[0006] In the IAB system, an IAB-node can access the network through the independent networking (SA, Standalone) mode or the non-independent networking (EN-DC, E-UTRA-NR Dual Connectivity) mode. Figure 2 is a diagram showing the IAB architecture in the SA mode. Figure 3 is a diagram showing the IAB architecture in the EN-DC mode.

[0007] Figure 4 is a diagram showing one IAB node (IAB-node), a parent IAB-node, and a child IAB-node. As shown in Figure 4, the IAB-DU of the IAB node is connected to the IAB-MT of the child node as the network side, and the IAB-MT of the IAB node is connected to the IAB-DU of the parent node as the terminal side.

[0008] Figure 5 is a diagram showing the F1 user plane (F1-U) protocol stack between the IAB-DU and the IAB donor-CU. Figure 6 is a diagram showing 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 established on top of the transport (IP) layer between the IAB-DU and the IAB donor-CU, and Figures 5 and 6 include a two-hop wireless backhaul and a one-hop wired backhaul.

[0009] In the backhaul link, the transport (IP) layer is carried by the Backhaul Adaptation Protocol (BAP) sublayer. The BAP entity in the IAB-node realizes the routing function of the IAB system, and the IAB donor-CU provides the routing table. The BAP PDU (Protocol Data Unit) is transmitted on the RLC (Radio Link Control) channel of the backhaul link. Multiple RLC channels of the backhaul link can be set by the IAB-donor to carry traffic with different priorities and QoS (Quality of Service), and the BAP entity maps the BAP PDU to different backhaul RLC channels.

[0010] It should be noted that the introduction of the above background technology is for clearly and completely explaining the technical solution of the present invention and for the person skilled in the art to easily understand it. These technical solutions should not be construed as well-known to those skilled in the art just because they are described in the background technology of the present invention.

Summary of the Invention

Problems to be Solved by the Invention

[0011] The inventors have discovered the following. That is, currently, the identifier (ID) of the IAB node is related to its location. However, in the case of a mobility scenario, since the cell information of the mobile node may collide with that of adjacent cells, the network may not be able to support multiple mobile nodes working simultaneously (abbreviated as simultaneous working).

[0012] To solve at least one of the above problems, embodiments of the present invention provide a method for setting a mobile node, a mobile node, and a donor device.

Means for Solving the Problem

[0013] According to one aspect of an embodiment of the present invention, there is provided a method for setting a mobile node, wherein the F1 connection of the distributed unit (DU) of the mobile node is terminated at a first donor-CU, and the method includes: the first donor-CU sets or re-sets second information regarding a first cell for the IAB-DU of the mobile node based on first information regarding the location of the mobile node; and transmitting the second information regarding the first cell set or re-set by the first donor-CU to the DU of the mobile node.

[0014] According to another aspect of an embodiment of the present invention, there is provided a donor device, wherein the F1 connection of the distributed unit (DU) of a mobile node is terminated at the donor device, and the donor device includes: a setting unit that sets or re-sets second information regarding a first cell for the DU of the mobile node based on first information regarding the location of the mobile node; and a communication unit that transmits the second information regarding the first cell set or re-set to the IAB-DU of the mobile node.

[0015] According to another aspect of an embodiment of the present invention, there is provided a method for setting a mobile node, wherein the F1 connection of the distributed unit (DU) of the mobile node is terminated at a first donor-CU, and the method includes: The DU of the mobile node receives second information regarding a first cell transmitted by the first donor-CU, wherein the second information regarding the first cell is set or reset by the first donor-CU based on first information regarding the location of the mobile node.

[0016] According to another aspect of an embodiment of the present invention, a mobile node is provided, which includes a mobile terminal (MT) and a distributed unit (DU), wherein an F1 connection of the distributed unit (IAB-DU) is terminated at a first donor central unit (donor-CU), and the DU of the mobile node receives second information regarding a first cell transmitted by the first donor-CU, wherein the second information regarding the first cell is set or reset by the first donor-CU based on first information regarding the location of the mobile node.

[0017] According to another aspect of an embodiment of the present invention, an IAB system is provided, which includes a donor central unit and a mobile node, wherein an F1 connection of a distributed unit (DU) of the mobile node is terminated at the donor central unit, and the donor central unit sets or resets second information regarding a first cell for the DU of the mobile node based on first information regarding the location of the mobile node, and transmits the set or reset second information regarding the first cell to the DU of the mobile node.

Advantages of the Invention

[0018] The advantageous effects of the embodiments of the present invention are at least as follows: namely, the first donor-CU sets or resets second information for the DU of the mobile node based on the first information of the mobile node, and transmits the second information to the DU of the mobile node. Thereby, the first donor-CU can dynamically set information within the mobile area for the mobile node based on the real-time location information of the mobile node, so that collisions between the mobile node and adjacent cells can be avoided, and the network can be enabled to support the simultaneous working of multiple mobile nodes.

[0019] Specific embodiments of the present invention are disclosed in detail by referring to the following description and drawings, showing aspects in which the principles of the present invention can be adopted. It should be noted that the embodiments of the present invention are not limited in scope by these. Within the scope of the appended claims, the embodiments of the present invention may include various changes, modifications, and alternatives.

[0020] Also, the features described and / or shown for one embodiment can be used in one or more other embodiments in the same or similar manner, combined with the features in other embodiments, or replace the features in other embodiments.

[0021] It should be noted that terms such as "comprising / including", when used in this specification, refer to the presence of features, elements, steps, or assemblies, but also refer to not excluding the presence or addition of one or more other features, elements, steps, or assemblies.

Brief Description of the Drawings

[0022] The elements and features described in one drawing or one embodiment of the present invention can be combined with the elements and features shown in one or more other drawings or embodiments. Also, in the drawings, similar reference numerals indicate corresponding parts in several drawings and are also used to indicate corresponding parts used in multiple embodiments.

[0023] The included drawings are used to provide a further understanding of the embodiments of the present invention. These drawings form a part of this specification, illustrate the embodiments of the present invention, and are used to explain the principles of the present invention together with the written description. Also, as is obvious, the drawings described below are only for showing some embodiments of the present invention, and those skilled in the art can obtain other drawings based on these drawings without creative labor.

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Mode for Carrying Out the Invention

[0024] By referring to the accompanying drawings and the following description, the foregoing and other features of the present invention will become apparent. Although specific embodiments of the present invention are disclosed in the specification and drawings, they are only some of the embodiments that can adopt the principles of the present invention. It should be understood that the present invention is not limited to the described embodiments, that is, the present invention also includes all changes, modifications, and substitutions within the scope of the appended patent claims.

[0025] In an embodiment of the present invention, the term "communication network" or "wireless communication network" may refer to a network conforming to any of the following communication standards, for example, New Radio (NR), Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA (registered trademark)), High-Speed Packet Access (HSPA), and the like.

[0026] Also, the communication between devices in a communication system may be performed according to a communication protocol at any stage. For example, it may include, but is not limited to, the following communication protocols, that is, 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G, 5G, New Radio (NR), and the like, and / or other conventional or future-developed communication protocols.

[0027] In an embodiment of the present invention, the term "network device" refers to, for example, a device that connects a terminal device to a communication network and provides services to the terminal device in a communication system. The network device may include, but is not limited to, the following, that is, "node" and / or "donor" in an IAB architecture, base station (BS), access point (AP), transmission reception point (TRP), broadcast transmitter, mobile management entity (MME), network gateway, server, radio network controller (RNC), base station controller (BSC), and the like.

[0028] Among them, the base station may include, but is not limited to, the following, that is, Node B (NodeB or NB), evolved Node B (eNodeB or eNB), 5G base station (gNB), etc., and may further include RRH (Remote Radio Head), RRU (Remote Radio Unit), relay or low-power node (for example, femto, pico, etc.). Also, the term "base station" may include some or all of their functions, and each base station can provide communication coverage for a specific geographical area. For example, the 5G base station gNB may include one gNB CU and one or more gNB DUs, where CU / DU is one logical node of the gNB that has some functions of the gNB. The term "cell" may refer to the base station and / or the area it covers, depending on the context in which the term is used.

[0029] In the embodiments of the present invention, the term "user equipment" (UE, User Equipment) or "terminal equipment" (TE, Terminal Equipment) refers to, for example, a device that accesses a communication network by a network device and receives services from the network. The user equipment may be fixed or mobile, and is also referred to as a mobile station (MS), terminal, subscriber station (SS), access terminal (AT), station, etc. For example, it is a terminal equipment served by an IAB node or an IAB donor under the IAB architecture.

[0030] Among them, the user equipment may include, but is not limited to, the following, for example, cellular phone, PDA (Personal Digital Assistant), wireless modem, wireless communication device, mobile device, machine type communication device, laptop computer, cordless telephone, smartphone, smartwatch, digital camera, etc.

[0031] Also, for example, in a scenario such as IoT (Internet of Things), the user device may further be a device or apparatus that performs monitoring or measurement. For example, it may include, but is not limited to, the following, namely, machine type communication (MTC) terminals, in-vehicle communication terminals, D2D (Device to Device) terminals, M2M (Machine to Machine) terminals, and the like.

[0032] Also, the term "network side" or "network device side" refers to the side of the network, or may be a base station, and may include one or more network devices as described above. The term "user side" or "terminal side" or "terminal device side" refers to the side of the user or terminal, or may be a UE, and may include one or more terminal devices as described above.

[0033] The routing function of the IAB system is realized by the BAP layer, and routing settings (BH routing configuration) and RLC channel mapping settings (BH RLC Channel Mapping Configuration) are stored in each IAB-node node. The BAP entity performs routing based on the routing settings, RLC channel mapping settings, and routing identifier (Routing ID) in the BAP layer data packet header. The Routing ID includes the destination (target) BAP address and the path identifier.

[0034] The routing settings include the mapping relationship between the Routing ID and the next-hop node BAP address. The RLC channel mapping settings include 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.

[0035] Figure 7 shows the routing of the IAB system. As shown in Figure 7, for each data packet, the next-hop node BAP address can be found from the routing settings based on the routing ID in the data packet header. The primary-hop node BAP address and the ingress link RLC channel ID are all known. In this way, after the next-hop node BAP address is determined, based on the RLC channel mapping settings, the egress link RLC channel ID can be found based on the primary-hop node BAP address + ingress link RLC channel ID + next-hop node BAP address.

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

[0037] For each downlink data packet reaching the IAB-donor DU, the IAB-donor DU can find the next-hop node address from the routing settings based on the Routing ID in the data packet header. In this way, after the next-hop node address is determined, based on the IP address and DSCP of the data packet, the egress link RLC channel ID can be found from the downlink RLC channel mapping settings.

[0038] Uplink backhaul information (BH information) is stored in the access IAB node, which includes the routing ID used by traffic, the uplink backhaul RLC channel ID, and the next-hop node address. The access IAB node sets the routing ID in the BAP layer data packet header of the uplink traffic based on the uplink BH information, and selects the BH RLC channel and the next-hop node for the uplink traffic transmission.

[0039] The routing and BH RLC channel mapping of the IAB system are exemplarily described above.

[0040] In Rel-17 NR, the scenario of the IAB node at rest has already been studied, and the process of the stationary IAB-node changing the transmission path (or called topology adaptation) between different donor-DUs under the F1-terminating donor-CU, and the flow (process) of changing the transmission path between the F1-terminating donor-CU and the non-F1-terminating donor-CU have been standardized. In Rel-18 NR, the mobile scenario is studied.

[0041] Figure 8 is a diagram showing a mobile scenario. As shown in Figure 8, for example, the IAB node 801 is installed in a moving vehicle to serve the in-vehicle user equipment. Therefore, it is necessary to standardize the flow of changing the transmission path when the mobile IAB node moves between multiple different donor-CUs.

[0042] In the case of a stationary IAB node, the physical cell identifier (PCI) and physical random access channel (PRACH) resource configuration of its serving cell may be fixed and unchangeable. The reason is as follows: namely, the network side can control that the PCI or PRACH resource of its serving cell does not collide with the PCI or PRACH of the surrounding adjacent cells by determining the adjacent cells (for example, macro cells or serving cells of other IAB nodes) of its serving cell based on its fixed position.

[0043] Figure 9 is a diagram showing another movement scenario. As shown in Figure 9, since the mobile IAB node has mobility, its movement trajectory may pass through the control regions of multiple different donor-CUs. Therefore, the method of fixed PCI or fixed PRACH resources cannot be applied to the mobile IAB node. The reason is as follows: namely, if the PCI or PRACH resource of the mobile IAB node is fixed, the network side needs to ensure that the same PCI or PRACH resource is not set in the adjacent cells through which its movement trajectory passes. When there are many mobile IAB nodes, the resources available for use by other cells will be significantly reduced, so there is a risk that the network side cannot support the simultaneous operation of multiple mobile IAB nodes. Therefore, as a feasible solution, a method can be considered in which the network side dynamically sets the PCI or PRACH resource of its serving cell based on the moving position of the IAB node to avoid collisions with the resources of the adjacent cells at its location. However, at present, there is still no technology to support the dynamic PCI or PRACH resource configuration of IAB nodes.

[0044] In addition, the position of the UE accessing the cell is determined by the NR cell global identifier (NCGI) of the serving cell and the tracking area (TA). Also, since the core network usually positions the UE based on the NCGI and TA of the UE's serving cell, the NCGI and TA of the serving cell are set by the network side based on the location where the cell is located.

[0045] In the case of a stationary IAB node, the network side can set the NCGI and TA of its serving cell based on its fixed position. However, in the case of a mobile IAB node, due to its mobility, the movement trajectory may pass through the control regions of multiple different donor-CUs, and the position of its serving cell can change in the network. The method of fixed NCGI and TA cannot be applied to mobile IAB nodes. The reason is as follows: that is, the fixed NCGI and TA cannot reflect the actual position of the serving cell of the mobile IAB node, nor can they reflect the actual position of the UE accessing the cell. Therefore, the network side cannot obtain the actual position of the UE accessing the mobile IAB node. Thus, as a feasible solution, a method of reflecting the actual position of the UE accessing the cell by the network side dynamically setting the NCGI and TA of its serving cell based on the moving position of the IAB node is considered. However, at present, there is still no technology that supports dynamic NCGI setting and / or TA setting.

[0046] In the embodiments of the present invention, unless otherwise specified, the IAB node device includes a migrating node or its child nodes. In addition, although the PCI, NCGI, and TA are used as examples for the description above, the present invention is not limited thereto. For example, other information related to the mobile IAB node may also be applicable. Also, the embodiments of the present invention are not limited to IAB nodes. For example, it can also be similarly applied to a network-controlled repeater (NCR).

[0047] Hereinafter, embodiments of the present invention will be described in more detail.

[0048] <Embodiment of the first side> In an embodiment of the present invention, a method for setting a mobile node is provided, and the F1 connection of the DU of the mobile node is terminated by a first donor-CU, that is, the first donor-CU is the F1-terminating donor-CU of the mobile node.

[0049] FIG. 10 is a diagram showing a method for setting a mobile node in an embodiment of the present invention. As shown in FIG. 10, the method includes the following steps (operations), that is, 1001: The first donor-CU sets or re-sets second information regarding a first cell for the DU of the mobile node based on first information regarding the position of the mobile node; and 1002: The first donor-CU transmits the second information regarding the first cell set or re-set by the first donor-CU to the DU of the mobile node.

[0050] Thereby, in the embodiment of the present invention, the first donor-CU can dynamically set second information (for example, cell identifier) regarding cells in the mobile area for the mobile node based on first information (for example, real-time position information) regarding the position of the mobile node. Therefore, collisions between the mobile node and adjacent cells can be avoided, and the network can be made to support the simultaneous working of multiple mobile nodes.

[0051] It should be noted that the above FIG. 10 is for illustrative explanation of the embodiments of the present invention, but the present invention is not limited thereto. For example, the execution order between each operation can be appropriately adjusted, or several operations can be increased or decreased. Those skilled in the art can make appropriate modifications based on the above content without being limited to the description of FIG. 10 above.

[0052] In some embodiments, the first donor-CU is the F1-terminating donor-CU of a plurality of mobile nodes within a specified (predetermined) area. When the plurality of mobile nodes move within the specified area, the F1 connection of the IAB-DU of the plurality of mobile nodes is always terminated by the first donor-CU.

[0053] For example, an operator designates a specific donor-CU as the centralized control donor-CU for mobile IAB nodes within a specified area, and the F1 connection start of the IAB nodes moving within the specified area is always terminated by the centralized control donor-CU. The IAB node can change the non-F1-terminating donor-CU based on its real-time position and shift the transmission path to the donor-DU under the latest non-F1-terminating donor-CU without changing the F1-terminating donor-CU.

[0054] In some embodiments, the first donor-CU transmits, to the DU of the mobile node, second information regarding the first cell that is set or reset by a first F1AP message.

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

[0056] In some embodiments, the second information includes at least one of the following, namely, 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. Note that the present invention is not limited thereto. For example, it may include one or more of these pieces of information, or may include other information.

[0057] In some embodiments, before the first donor-CU sets or resets the second information regarding the first cell for the DU of the mobile node, the first donor-CU may further receive the second information of the currently set first cell that the DU of the mobile node transmits by a second F1AP message, or the first donor-CU may further receive the second information of a third cell that a second donor-CU transmits, where the second donor-CU is a non-F1 terminated donor-CU of the mobile node.

[0058] For example, the second F1AP message includes an F1 establishment request message or a gNB DU configuration update message. By the mobile node reporting the currently set second information, the first donor-CU can better know the current configuration information of the first cell of the mobile node and can set or reset the second information regarding the first cell more accurately.

[0059] Also, for example, the current non-F1 terminated donor-CU of the mobile IAB node transmits the PCI, NCGI, TAC, and PRACH configurations of the adjacent cell of the DU of the mobile IAB node (for example, the cell detected by its served mobile terminal) to the F1 terminated donor-CU, and enables the centralized control donor-CU to set the PCI, NCGI, TAC, and PRACH resources for the DU of the mobile node based on the PCI, NCGI, TAC, and PRACH resources of the adjacent cell of the DU of the mobile IAB node, so as to avoid the collision of the PCI or PRACH resources between the cell of the DU of the mobile node and the adjacent cell, or to enable the TAC and NCGI of the cell of the DU of the mobile node to be consistent with those of the adjacent cell.

[0060] In some embodiments, the first information regarding the position of the mobile node includes the position information of the mobile node or the information of the cell accessed by the mobile terminal (MT), and / or the second information regarding the second cell detected and reported by the mobile terminal (MT) served by the first cell.

[0061] For example, the centralized control donor-CU can set the PCI, NCGI, and TAC for the DU of the mobile IAB node based on the location information of the mobile IAB node registered in the core network or the network positioning information, or based on the serving cell accessed by the MT of the IAB node as instructed by the current non-F1-terminating donor-CU (i.e., the donor-CU accessed by the IAB-MT of the IAB node), and the setting information can be sent to the mobile IAB node using the F1AP message.

[0062] Also, for example, the centralized control donor-CU can set the PCI, NCGI, and TAC for the DU of the mobile IAB node based on the PCI, NCGI, TAC, and PRACH resources of the adjacent cells of the DU of the mobile IAB node. In this way, it can be ensured that the PCI and PRACH resources of the mobile IAB node do not collide with those of the adjacent cells, and the NCGI and TAC of the mobile IAB node change based on its actual geographical location, enabling the network to obtain the actual location information of the UE accessing the mobile IAB node.

[0063] In some embodiments, the non-F1-terminating donor-CU of the mobile node changes from the second donor-CU to the third donor-CU, and the first donor-CU further receives first information regarding the location of the mobile node transmitted by the second donor-CU or the third donor-CU.

[0064] In some embodiments, the physical cell identifier (PCI) set or reset for the first cell does not collide with the PCI of the adjacent cells, the NR cell global identifier (NCGI) set or reset for the first cell is related to the NCGI of the adjacent cells, the tracking area code (TAC) set or reset for the first cell is the same as or related to the TAC of the adjacent cells, and the PRACH resource set or reset for the first cell does not collide with the PRACH resource of the adjacent cells.

[0065] FIG. 11 is a diagram showing an example of a method for setting a mobile node in an embodiment of the present invention. As shown in FIG. 11, C donor-CU is a centralized control CU within the moving range of the in-vehicle IAB node, and the IAB node has established an F1 connection with the C donor-CU.

[0066] When donor-CU1 is 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, based on the position of the IAB node (PCI = 1, TAC = A, NCGI = k of the serving cell of the parent node), the PCI set by the C donor-CU for the serving cell of the IAB node is 2, the TAC is A, and the NCGI is k + 1, and it is set for the IAB node by an F1AP message (GNB-CU CONFIGURATION UPDATE).

[0067] Thereby, since the PCI of the serving cell of the parent node is 1 and the PCI of the serving cell of the IAB node is 2, and the two are different, it is possible to prevent the PCI of the moving IAB node from colliding with adjacent cells. The TAC of the serving cell of the parent node is A and the NCGI is k, and the TAC of the serving cell of the IAB node is A and the NCGI is k + 1, and the two are the same or related, so the network can obtain the actual location information of the UE accessing the moving IAB node.

[0068] 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, based on the location of the IAB node (PCI = 2, TAC = B, NCGI = m of the serving cell of the parent node), the PCI set by C donor-CU for the serving cell of the IAB node is 1, the TAC is B, and the NCGI is m + 1, and it is set for the IAB node by the F1AP message (GNB-CU CONFIGURATION UPDATE).

[0069] As a result, the PCI of the serving cell of the parent node is 2, and the PCI of the serving cell of the IAB node is 1. Since the two are different, it is possible to prevent the PCI of the moving IAB node from colliding with adjacent cells. The TAC of the serving cell of the parent node is B and the NCGI is m, and the TAC of the serving cell of the IAB node is B and the NCGI is m + 1. Since the two are the same or related, the network can obtain the actual location information of the UE accessing the moving IAB node.

[0070] The above embodiments are for illustrative purposes to explain the embodiments of the present invention, but the present invention is not limited thereto, and appropriate modifications can also be made based on the above embodiments. For example, each of the above embodiments can be used alone, or a plurality of the above embodiments can be combined and used.

[0071] As can be seen from the above embodiments, the first donor-CU sets or re-sets the second information for the DU of the moving node based on the first information of the moving node, and transmits the second information to the DU of the moving node. Thereby, the first donor-CU can dynamically set the information in the moving area for the moving node based on the real-time location information of the moving node, so that collisions between the moving node and adjacent cells can be avoided, and the network can be made to support the simultaneous working of multiple moving nodes.

[0072] <Embodiment of the second side> In an embodiment of the present invention, an IAB integration method is provided, which may be used in combination with the embodiment of the first aspect or implemented alone. Here, the description of the same content as in the embodiment of the first aspect is omitted.

[0073] FIG. 12 is a diagram showing the IAB integration method in an embodiment of the present invention. As shown in FIG. 12, the method includes the following steps, that is, 1201: The MT of the mobile node establishes an RRC connection with the second donor-CU; 1202: Set the IP address of the first donor-CU by the OAM entity for the DU of the mobile node; and 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 starts the F1 connection establishment with the first donor-CU using the IP address assigned by the second donor-CU. Among them, the RRC connection reconfiguration message includes the IP address and the BAP layer address assigned by the second donor-CU for the mobile node, and the BAP layer address is carried in the F1 connection establishment request message sent by the DU of the IAB node.

[0074] It should be noted that the above FIG. 12 is for illustrative explanation of the embodiment of the present invention, but the present invention is not limited thereto. For example, the execution order between each operation can be appropriately adjusted, or several operations can be increased or decreased. Those skilled in the art can make appropriate modifications based on the above content without being limited to the description of FIG. 12 above.

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

[0076] In some embodiments, the first donor-CU is the F1-terminating donor-CU of a plurality of mobile nodes within a specified area, and when the plurality of mobile nodes move within the specified area, the F1 connections of the IAB-DUs of the plurality of mobile nodes are always terminated by the first donor-CU.

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

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

[0079] Among them, the migration management request message includes downlink transmission network layer (TNL) information for the second donor-CU to set up layer 2 mapping for the donor-DU and the BAP layer address of the mobile IAB node. In this way, the second donor-CU can identify, based on the BAP layer address, for which IAB node the migration management request message is.

[0080] Hereinafter, the IAB integration process in the embodiments of the present invention will be further described by signaling interaction.

[0081] FIG. 13 is a signaling flowchart for IAB integration in an embodiment of the present invention.

[0082] As shown in FIG. 13, at the setup stage of the IAB-MT, the IAB-MT and the UE are similarly connected to the network, completing the establishment of the RRC connection to the donor-CU, the establishment of the IAB-MT context, the core network authentication, the radio bearer configuration for the IAB-MT, and the PDU session establishment for the OAM traffic. During the RRC connection establishment, the IAB-MT can instruct the donor-CU that it has the IAB node capabilities. The RRC connection reconfiguration message includes the IP address and the BAP layer address assigned by the donor-CU for the IAB node.

[0083] At the backhaul RLC channel establishment stage, at least one default BH RLC channel for non-UP traffic is established, and the BAP address and the default uplink routing ID are set for the IAB-node.

[0084] At the routing update stage, the upstream node routing table of the IAB-node is updated, and an IP address is assigned for the IAB-node.

[0085] At the setup stage of the IAB-DU, the IP address of the F1-terminating CU (i.e., the C donor-CU) is set for the IAB-DU by OAM. The IAB-DU starts the F1 connection establishment with the C donor-CU using the IP address assigned by the donor-CU, and the F1 connection establishment request carries the BAP layer address assigned by the donor-CU for the IAB node.

[0086] At the stage of 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 IP address actually used, selected from among the IP addresses assigned by the donor-CU (for example, by means of a gNB-DU CONFIGURATION UPDATE message), and the IP address includes the IP address for F1-U or non-UP traffic.

[0087] As shown in Figure 13, based on the IP address information reported by the IAB-DU, the C donor-CU determines the donor-CU accessed by the IAB-MT, and sends an IAB TRANSPORT MIGRATION MANAGEMENT REQUEST to the donor-CU, which includes the context of non-UP traffic, which includes the DL TNL information for the donor-CU to set the downlink mapping to the donor-DU and the BAP layer address of the IAB node.

[0088] As shown in Figure 13, based on the BAP layer address, the donor-CU determines that the IAB TRANSPORT MIGRATION MANAGEMENT REQUEST is for the IAB node, 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 traffic.

[0089] The above signaling process is for illustrative purposes to explain the embodiments of the present invention, but the present invention is not limited thereto, and related technologies can also be referred to for more specific content of the signaling. Also, for example, the execution order between each operation can be appropriately adjusted, or several operations can be increased or decreased. Those skilled in the art can make appropriate modifications based on the above content, not limited to the description of Figure 13 above.

[0090] The above embodiments are for illustrative purposes to explain the embodiments of the present invention, but the present invention is not limited thereto, and appropriate modifications can also be made based on the above embodiments. For example, each of the above embodiments can be used alone, or a plurality of the above embodiments can be combined and used.

[0091] As can be seen from the above embodiments, the IAB-DU does not necessarily establish an F1 connection with the donor-CU to which the IAB-MT initially accesses, but establishes an F1 connection with the centralized control CU (i.e., the first donor-CU or the C donor-CU). In this way, the stability of the services of the mobile nodes can be further improved by the centralized control donor-CU.

[0092] <Embodiment of the third aspect> In the embodiments of the present invention, a donor device is provided, and the description of the same content as in the embodiments of the first aspect is omitted here. The device may be, for example, an IAB donor-CU in an IAB system (e.g., the first donor-CU in the embodiments of the first and second aspects), or one or more components or assemblies or modules provided in the IAB donor-CU.

[0093] FIG. 14 is a diagram showing the donor device in the embodiments of the present invention. As shown in FIG. 14, the donor device 1400 includes the following, that is, Setting unit 1401: setting or resetting second information regarding a first cell for the DU of the mobile node based on first information regarding the position of the mobile node; and Communication unit 1402: transmitting the second information regarding the set or reset first cell to the DU of the mobile node.

[0094] In some embodiments, the donor device is an F1 termination donor centralized unit (donor-CU) of a plurality of mobile nodes within a specified area, and when the plurality of mobile nodes move within the specified area, the F1 connections of the DUs of the plurality of mobile nodes are always terminated by the donor device.

[0095] In some embodiments, the donor device transmits, to the DU of the mobile node, second information regarding the first cell that has been set or reset by a first F1AP message.

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

[0097] In some embodiments, the second information includes at least one of the following, namely, 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.

[0098] In some embodiments, before the setting unit 1401 sets or resets the second information regarding the first cell for the DU of the mobile node, the communication unit 1402 receives the second information of the current configuration of the first cell that the DU of the mobile node transmits by a second F1AP message.

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

[0100] In some embodiments, before the setting unit 1401 sets or resets the second information regarding the first cell for the DU of the mobile node, the communication unit 1402 further receives the second information of a third cell transmitted by a second donor-CU, where the second donor-CU is a non-F1-terminating donor-CU of the mobile node.

[0101] In some embodiments, the first information regarding the position of the mobile node includes the position information of the mobile node or cell information accessed by the MT, and / or second information regarding a second cell detected and reported by a mobile terminal (MT) served by the first cell.

[0102] In some embodiments, the communication unit 1402 transmits, by a third F1AP message, second information regarding the second cell or second information regarding the third cell to the DU of the mobile node, so that the DU of the mobile node spontaneously adjusts the settings of PCI, PRACH, TAC, and NCGI.

[0103] In some embodiments, the non-F1-terminating donor-CU of the mobile node changes from a second donor-CU to a third donor-CU, and the communication unit 1402 receives first information regarding the position of the mobile node transmitted by the second donor-CU or the third donor-CU.

[0104] In some embodiments, the physical cell identifier (PCI) set or reset for the first cell does not collide with the PCI of adjacent cells, the NR cell global identifier (NCGI) set or reset for the first cell is related to the NCGI of adjacent cells, the tracking area code (TAC) set or reset for the first cell is the same as or related to the TAC of adjacent cells, and the PRACH resource set or reset for the first cell does not collide with the PRACH resource of adjacent cells.

[0105] In some embodiments, the communication unit 1402 establishes an F1 connection with the DU of the mobile node. Among them, the MT of the mobile node establishes an RRC connection with the second donor-CU. The IP address of the first donor-CU is set for the DU of the mobile node by the OAM entity. After the MT of the mobile node receives an RRC connection reconfiguration message transmitted by the second donor-CU, the DU of the mobile node starts to establish an F1 connection with the donor device using the IP address assigned by the second donor-CU. Among them, the RRC connection reconfiguration message includes the IP address and the BAP layer address assigned by the second donor-CU for the mobile node, and the BAP layer address is carried in the F1 connection establishment request transmitted by the DU of the mobile node.

[0106] In some embodiments, the communication unit 1402 further receives an IP address selected and used from among the IP addresses reported by the DU of the mobile node in a gNB DU configuration update message.

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

[0108] Each of the above embodiments is for illustratively explaining the embodiments of the present invention, but the present invention is not limited thereto, and appropriate modifications can also be made based on each of the above embodiments. For example, each of the above embodiments can be used alone, or a plurality of the above embodiments can be combined and used.

[0109] It should be noted that only the components or modules according to the present invention have been described above, but the present invention is not limited thereto. The donor device 1400 in the embodiments of the present invention may further include other components or modules, and the specific content of these components or modules can refer to related technologies.

[0110] Also, for the sake of convenience, only the connection relationship or signal direction between each component or module is shown in FIG. 14, but as those skilled in the art can understand, various related technologies such as bus connection may be adopted. Each of the above components or modules may be implemented by hardware such as a processor, a memory, a transmitter, and a receiver, but the implementation of the present invention is not limited thereto.

[0111] As can be seen from the above embodiments, the donor device sets or re-sets the second information for the DU of the mobile node based on the first information of the mobile node, and transmits the second information to the DU of the mobile node. Thereby, the donor device can dynamically set the information in the mobile area for the mobile node based on the real-time position information of the mobile node, so that collisions between the mobile node and adjacent cells can be avoided, and the network can be enabled to support the simultaneous working of multiple mobile nodes.

[0112] <Embodiment of the fourth aspect> In the embodiments of the present invention, a mobile node is provided, and the description of the same content as in the embodiments of the first and second aspects is omitted here. The mobile node may be, for example, an IAB node in an IAB system (for example, the mobile IAB node in the embodiments of the first and second aspects), or one or more components or assemblies or modules provided in the IAB node.

[0113] FIG. 15 is a diagram showing a mobile node in an embodiment of the present invention. As shown in FIG. 15, the mobile node 1500 includes a mobile terminal (MT) 1501 and a distributed unit (DU) 1502.

[0114] The F1 connection of the distributed unit (DU) is terminated by a first donor central unit (donor-CU), and the DU of the mobile node receives the second information regarding the first cell transmitted by the first donor-CU. Among them, the second information regarding the first cell is set or re-set by the first donor-CU based on the first information regarding the position of the mobile node.

[0115] In some embodiments, the first donor-CU is an F1 terminating donor-CU for a plurality of mobile nodes within a specified area. When the plurality of mobile nodes move within the specified area, the F1 connections of the DUs of the plurality of mobile nodes are always terminated by the first donor-CU.

[0116] In some embodiments, the second information includes at least one of the following, namely, 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.

[0117] The first information regarding the position of the mobile node includes the position information of the mobile node or the cell information accessed by the MT, and / or the second information regarding the second cell detected and reported by the mobile terminal (MT) served by the first cell.

[0118] In some embodiments, the MT of the mobile node establishes an RRC connection with the second donor-CU, the DU of the mobile node has the IP address of the first donor-CU set 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 starts to establish an F1 connection with the first donor-CU using the IP address assigned by the second donor-CU. Among them, the RRC connection reconfiguration message includes the IP address and the BAP layer address assigned by the second donor-CU for the mobile node, and the BAP layer address is carried in the F1 connection establishment request sent by the DU of the mobile node.

[0119] In some embodiments, the DU of the mobile node reports to the first donor-CU, via a gNB DU configuration update message, an IP address selected and used from among the IP addresses assigned by the second donor-CU, and the IP address selected and used by the mobile node is used by the first donor-CU to determine the second donor-CU.

[0120] Each of the above embodiments is for illustrative purposes to explain the embodiments of the present invention, but the present invention is not limited thereto, and appropriate modifications can also be made based on each of the above embodiments. For example, each of the above embodiments can be used alone, or a plurality of the above embodiments can be combined and used.

[0121] Note that only the components or modules according to the present invention have been described above, but the present invention is not limited thereto. The mobile node 1500 in the embodiments of the present invention may further include other components or modules, and specific details of these components or modules can be referred to related technologies.

[0122] Also, for the sake of convenience, only the connection relationship or signal direction between each component or module is shown in FIG. 15. However, as can be understood by those skilled in the art, various related technologies such as bus connection may be adopted. Each of the above-described components or modules may be implemented by hardware such as a processor, a memory, a transmitter, a receiver, etc., but the implementation of the present invention is not limited thereto.

[0123] As can be seen from the above embodiments, the donor device sets or re-sets the second information for the DU of the mobile node based on the first information of the mobile node, and transmits the second information to the DU of the mobile node. Thereby, the donor device can dynamically set the information in the mobile area for the mobile node based on the real-time location information of the mobile node, so that the collision between the mobile node and the adjacent cell can be avoided, and the network can be made to support the simultaneous working of multiple mobile nodes.

[0124] <Embodiment of the Fifth Aspect> In an embodiment of the present invention, a communication system is provided, which includes a donor device and a mobile node (e.g., an IAB-node). Note that for the network structure (configuration) and specific details of the donor device and the IAB node, related technologies can also be referred to, and detailed descriptions thereof are omitted here.

[0125] In some embodiments, the IAB system includes a donor centralized unit and a mobile node, and the F1 connection of the distributed unit (DU) of the mobile node is terminated at the donor centralized unit.

[0126] The donor concentration type unit sets or re-sets second information regarding a first cell for the DU of the mobile node based on first information regarding the position of the mobile node; and transmits the set or re-set second information regarding the first cell to the DU of the mobile node.

[0127] In an embodiment of the present invention, an IAB device is further provided, and the IAB device may be an IAB donor device or an IAB node (migration node or child node).

[0128] FIG. 16 is a diagram showing an IAB device in an embodiment of the present invention. As shown in FIG. 16, the IAB device 1600 may include a processor (for example, a central processing unit CPU) 1601 and a memory 1602, and the memory 1602 is connected to the processor 1601. Among them, the memory 1602 can store various data, can also store a program 1605 for information processing, and can execute the program 1605 under the control of the central processing unit 1601.

[0129] For example, the processor 1601 may be configured to execute a program to implement a method for setting a mobile node in an embodiment of the first aspect. For example, the processor 1601 may be configured to perform the following control, that is, based on first information regarding the position of the mobile node, set or re-set second information regarding a first cell for the DU of the mobile node; and transmit the set or re-set second information regarding the first cell to the DU of the mobile node.

[0130] Also, for 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 controls, that is, the MT of the mobile node establishes an RRC connection with the second donor-CU, and the IP address of the first donor-CU is set for the DU of the mobile node 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 starts to establish an F1 connection with the first donor-CU using the IP address assigned by the second donor-CU, wherein the RRC connection reconfiguration message includes the IP address and the BAP layer address assigned by the second donor-CU for the mobile node, and the BAP layer address is carried in the F1 connection establishment request sent by the DU of the mobile node.

[0131] Also, as shown in FIG. 16, the IAB device 1600 may further include a transceiver 1603, an antenna 1604, etc. Since the functions of the above-mentioned components are similar to those of the prior art, the detailed description thereof is omitted here. Note that the IAB device 1600 does not necessarily include all the components shown in FIG. 16. Also, the IAB device 1600 may further include components not shown in FIG. 16, and for this, reference can be made to the prior art.

[0132] In an embodiment of the present invention, a computer-readable program is further provided. When the program is executed on the IAB device, the program causes the computer to execute the method for setting a mobile node in the embodiment of the first aspect or the IAB integration method in the embodiment of the second aspect on the IAB device.

[0133] In an embodiment of the present invention, a storage medium storing a computer-readable program is further provided. The computer-readable program causes the computer to execute the method for setting a mobile node in the embodiment of the first aspect or the IAB integration method in the embodiment of the second aspect on the IAB device.

[0134] In addition, the above-described apparatus and method may be implemented by software or hardware, or may be implemented by a combination of hardware and software. The present invention further relates to a computer-readable program as follows, that is, when the program is executed by a logic component, the logic component realizes the above-described apparatus or component, or realizes each of the above-described methods or steps in the logic component. The logic component may be, for example, an FPGA (Field Programmable Gate Array), a microprocessor, a processor used in a computer, or the like. The present invention further relates to a storage medium storing the above-described program, such as a hard disk, a magnetic disk, an optical hard disk, a DVD, a flash memory, or the like.

[0135] Furthermore, one or more combinations of the functional blocks described in the drawings and / or one or more combinations of the functional blocks 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 components, discrete gates or transistor logic components, discrete hardware assemblies, or any other suitable combination for performing the functions described herein. Also, one or more combinations of the functional blocks described in the drawings and / or one or more combinations of the functional blocks may be further configured as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors connected communicatively to the DSP, or any other configuration combination.

[0136] The preferred embodiments of the present invention have been described above. However, the present invention is not limited to such embodiments, and any changes to the present invention belong to the technical scope of the present invention as long as the spirit of the present invention is not departed from.

[0137] In addition, with respect to the above-described embodiments and the like, the following supplementary notes are further disclosed.

[0138] (Appendix 1) A method for setting a mobile node, wherein the F1 connection of the distributed unit (DU) of the mobile node is terminated by a first donor-CU, and the method comprises: the first donor-CU sets or re-sets second information regarding a first cell for the DU of the mobile node based on first information regarding the position of the mobile node; and transmitting, by the first donor-CU, the second information regarding the first cell set or re-set to the DU of the mobile node.

[0139] (Appendix 2) The method according to Appendix 1, wherein the first donor-CU is an F1-terminating donor-CU for a plurality of mobile nodes within a specified area, and when the plurality of mobile nodes move within the specified area, the F1 connection of the IAB-DU of the plurality of mobile nodes is always terminated by the first donor-CU.

[0140] (Appendix 3) The method according to Appendix 1 or 2, wherein the first donor-CU transmits, by a first F1AP message, the second information regarding the first cell set or re-set to the DU of the mobile node.

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

[0142] (Appendix 5) The method according to any one of Appendices 1 to 4, The second information includes at least one of the following, namely, a physical cell identifier (PCI), an NR cell global identifier (NCGI), a tracking area code (TAC), and a physical random access channel (PRACH) resource setting.

[0143] (Appendix 6) The method according to any one of Appendices 1 to 5, before the first donor-CU sets or re-sets the second information regarding the first cell for the DU of the mobile node, the method further includes the first donor-CU receiving the second information of the currently set first cell that the DU of the mobile node transmits by a second F1AP message.

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

[0145] (Appendix 8) The method according to any one of Appendices 1 to 5, before the first donor-CU sets or re-sets the second information regarding the first cell for the DU of the mobile node, the method further includes the first donor-CU receiving the second information of a third cell transmitted by a second donor-CU, wherein the second donor-CU is a non-F1-terminating donor-CU of the mobile node.

[0146] (Appendix 9) The method according to any one of Appendices 1 to 8, the first information regarding the position of the mobile node includes the position information of the mobile node or the cell information accessed by the MT, and / or the second information regarding a second cell detected and reported by a mobile terminal (MT) served by the first cell.

[0147] (Appendix 10) The method according to Appendix 9, wherein the method further comprises the first donor-CU transmits, by a third F1AP message, second information regarding the second cell or second information regarding the third cell to the DU of the mobile node.

[0148] (Appendix 11) The method according to any one of Appendices 1 to 10, wherein the non-F1 terminating donor-CU of the mobile node changes from a second donor-CU to a third donor-CU, and the method further comprises the first donor-CU receiving first information regarding the position of the mobile node transmitted by the second donor-CU or the third donor-CU.

[0149] (Appendix 12) The method according to Appendix 11, wherein the physical cell identifier (PCI) set or reset for the first cell does not conflict with the PCI of an adjacent cell, the NR cell global identifier (NCGI) set or reset for the first cell is associated with the NCGI of an adjacent cell, the tracking area code (TAC) set or reset for the first cell is the same as or associated with the TAC of an adjacent cell, and the PRACH resource set or reset for the first cell does not conflict with the PRACH resource of an adjacent cell.

[0150] (Appendix 13) The method according to any one of Appendices 1 to 12, wherein the method further comprises the first donor-CU establishing an F1 connection with the DU of the mobile node, the MT of the mobile node establishing an RRC connection with the second donor-CU, and the IP address of the first donor-CU is set for the DU of the mobile node by an OAM entity. 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 further starts to establish an F1 connection with the first donor-CU using the IP address assigned by the second donor-CU. The RRC connection reconfiguration message includes the IP address and the BAP layer address assigned by the second donor-CU for the mobile node, and the BAP layer address is carried in the F1 connection establishment request sent by the DU of the mobile node.

[0151] (Appendix 14) The method according to Appendix 13, wherein the method further includes the first donor-CU further receiving an IP address selected and used from among the IP addresses assigned by the second donor-CU and reported by the DU of the mobile node through a gNB DU configuration update message.

[0152] (Appendix 15) The method according to Appendix 14, wherein the method further includes the first donor-CU determining the second donor-CU based on the IP address selected and used by the mobile node, and sending a transmission migration management request message to the second donor-CU, wherein the transmission migration management request message includes downlink transmission network layer (TNL) information and the BAP layer address for the second donor-CU to configure layer 2 mapping for the donor-DU; and the first donor-CU receiving a transmission migration management response message sent by the second donor-CU.

[0153] (Appendix 16) A method for configuring a mobile node, wherein the F1 connection of the distributed unit (DU) of the mobile node is terminated at a first donor-CU, and the method includes The DU of the mobile node receives second information regarding the first cell transmitted by the first donor-CU, wherein the second information regarding the first cell is set or reset by the first donor-CU based on first information regarding the position of the mobile node.

[0154] (Appendix 17) The method according to Appendix 16, wherein the first donor-CU is an F1 terminating donor-CU of a plurality of mobile nodes within a specified area, and when the plurality of mobile nodes move within the specified area, the F1 connection of the DUs of the plurality of mobile nodes is always terminated by the first donor-CU.

[0155] (Appendix 18) The method according to Appendix 16 or 17, wherein the DU of the mobile node receives the second information regarding the first cell set or reset by a first F1AP message.

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

[0157] (Appendix 20) The method according to any one of Appendices 16 to 19, wherein the second information includes at least one of the following, namely, 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.

[0158] (Appendix 21) The method according to any one of Appendices 16 to 20, Before the first donor-CU sets or resets the second information regarding the first cell for the DU of the mobile node, the method further includes the DU of the mobile node transmitting the second information of the currently set first cell to the first donor-CU by a second F1AP message.

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

[0160] (Appendix 23) The method according to any one of Appendices 16 to 22, wherein the first information regarding the position of the mobile node includes the position information of the mobile node or the cell information accessed by the MT, and / or the second information regarding a second cell detected and reported by a mobile terminal (MT) served by the first cell.

[0161] (Appendix 24) The method according to Appendix 23, wherein the method further includes the DU of the mobile node receiving the second information regarding the second cell or the second information regarding the third cell transmitted by the first donor-CU by a third F1AP message.

[0162] (Appendix 25) The method according to any one of Appendices 16 to 24, wherein the non-F1-terminating donor-CU of the mobile node changes from a second donor-CU to a third donor-CU.

[0163] (Appendix 26) The method according to Appendix 25, wherein The physical cell identifier (PCI) configured or reconfigured for the first cell does not collide with the PCI of adjacent cells, the NR cell global identifier (NCGI) configured or reconfigured for the first cell is associated with the NCGI of adjacent cells, the tracking area code (TAC) configured or reconfigured for the first cell is the same as or associated with the TAC of adjacent cells, and the PRACH resource configured or reconfigured for the first cell does not collide with the PRACH resource of adjacent cells.

[0164] (Appendix 27) The method according to any one of Appendices 16 to 26, The method further includes the MT of the mobile node establishing an RRC connection with a second donor-CU, the DU of the mobile node having the IP address of the first donor-CU set by an OAM entity, after the MT of the mobile node receives an RRC connection reconfiguration message sent from the second donor-CU, the DU of the mobile node further establishing an F1 connection with the first donor-CU using the IP address assigned by the second donor-CU, the RRC connection reconfiguration message including the IP address assigned by the second donor-CU for the mobile node.

[0165] (Appendix 28) The method according to Appendix 27, The method further includes the DU of the mobile node reporting to the first donor-CU, via a gNB DU configuration update message, the IP address selected from among the IP addresses assigned by the second donor-CU for use.

[0166] (Appendix 29) The method according to Appendix 28, The IP address selected and used by the mobile node is the one used by the first donor-CU to determine the second donor-CU.

[0167] (Appendix 30) An IAB integration method, The MT of the mobile node establishes an RRC connection with the second donor-CU; The IP address of the first donor-CU is set for the DU of the mobile node 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 starts the F1 connection establishment with the first donor-CU using the IP address assigned by the second donor-CU, The RRC connection reconfiguration message includes the IP address and the BAP layer address assigned by the second donor-CU for the mobile node, and the BAP layer address is carried in the F1 connection establishment request sent by the DU of the mobile node.

[0168] (Appendix 31) The method according to Appendix 30, The method further includes The DU of the mobile node reports to the first donor-CU, via a gNB DU configuration update message, the IP address selected and used from among the IP addresses assigned by the second donor-CU.

[0169] (Appendix 32) An IAB integration method, The second donor-CU establishes an RRC connection with the MT of the mobile node, and the IP address of the first donor-CU is set for the DU of the mobile node 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 starts the F1 connection establishment with the first donor-CU using the IP address assigned by the second donor-CU, The RRC connection reconfiguration message includes an IP address and a BAP layer address assigned by the second donor-CU for the mobile node, and the BAP layer address is carried in an F1 connection establishment request message sent by the DU of the mobile node.

[0170] (Appendix 33) The method according to Appendix 32, wherein the method further comprises: the second donor-CU receives a transmission migration management request message sent by the first donor-CU, the first donor-CU determines the second donor-CU based on an IP address selected and used by the mobile node, and the migration management request message includes downlink transmission network layer (TNL) information and the BAP layer address for the second donor-CU to set up layer 2 mapping for the donor-DU; and the second donor-CU sending a transmission migration management response message to the first donor-CU.

[0171] (Appendix 34) The method according to Appendix 32, wherein the method further comprises: the second donor-CU sending second information of a third cell to the first donor-CU, wherein the second donor-CU is a non-F1-terminating donor-CU of the mobile node.

[0172] (Appendix 35) An IAB node, including a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to execute the computer program to implement the method for setting up a mobile node according to any one of Appendices 16 to 29, or the IAB integration method according to Appendix 30 or 31.

[0173] (Appendix 36) An IAB donor device, comprising a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to execute the computer program to implement the method for setting a mobile node according to any one of Appendices 1 to 15, or the IAB integration method according to any one of Appendices 32 to 34.

Claims

1. A donor device, wherein the F1 connection of the distributed unit of the mobile node is terminated at the donor device, the donor device includes a setting unit configured to set or reset second information regarding a first cell for the distributed unit of the mobile node based on first information regarding the position of the mobile node; and a communication unit configured to transmit the second information regarding the first cell that is set or reset to the distributed unit of the mobile node.

2. The donor device according to claim 1, wherein the donor device is an F1 termination donor centralized unit for a plurality of mobile nodes within a specified area, and when the plurality of mobile nodes move within the specified area, the F1 connection of the distributed units of the plurality of mobile nodes is always terminated at the donor device.

3. The donor device according to claim 1, wherein the donor device transmits, by a first F1AP message, the second information regarding the first cell that is set or reset to the distributed unit of the mobile node.

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

5. The donor device 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 donor device according to claim 1, wherein before the setting unit sets or resets the second information regarding the first cell for the distributed unit of the mobile node, the communication unit receives the second information of the currently set first cell transmitted by the distributed unit of the mobile node by a second F1AP message, or receives the second information of a third cell transmitted by a second donor centralized unit, and the second donor centralized unit is a non-F1 termination donor centralized unit of the mobile node.

7. The donor device according to claim 6, wherein the second F1AP message includes an F1 establishment request message or a gNB DU configuration update message.

8. The donor device according to claim 1, wherein The first information regarding the position of the mobile node includes the position information of the mobile node or cell information accessed by the mobile terminal, and / or second information regarding a second cell detected and reported by a mobile terminal served by the first cell, the donor device.

9. The donor device according to claim 8, wherein the communication unit transmits second information regarding the second cell or second information regarding a third cell to the distributed unit of the mobile node by a third F1AP message, the donor device.

10. The donor device according to claim 1, wherein the non-F1 terminated donor centralized unit of the mobile node changes from a second donor centralized unit to a third donor centralized unit, and the communication unit receives first information regarding the position of the mobile node transmitted by the second donor centralized unit or the third donor centralized unit, the donor device.

11. The donor device according to claim 10, wherein the physical cell identifier set or reset for the first cell does not collide with the physical cell identifiers of adjacent cells, the NR cell global identifier set or reset for the first cell is related to the NR cell global identifiers of adjacent cells, the tracking area code set or reset for the first cell is the same as or related to the tracking area codes of adjacent cells, and the physical random access channel resources set or reset for the first cell do not collide with the physical random access channel resources of adjacent cells, the donor device.

12. The donor device according to claim 1, The communication unit establishes an F1 connection with the distributed unit of the mobile node. The mobile terminal of the mobile node establishes a radio resource control connection with the second donor centralized unit. The IP address of the first donor centralized unit is set for the distributed unit of the mobile node by the OAM entity. After the mobile terminal of the mobile node receives a radio resource control connection reconfiguration message sent by the second donor centralized unit, the distributed unit of the mobile node starts establishing an F1 connection with the donor device using the IP address assigned by the second donor centralized unit. The radio resource control connection reconfiguration message includes the IP address and the BAP layer address assigned by the second donor centralized unit for the mobile node. The BAP layer address is carried in the F1 connection establishment request sent by the distributed unit of the mobile node. Donor device.

13. The donor device according to claim 12, wherein the communication unit further receives an IP address selected and used from among the IP addresses reported by the distributed unit of the mobile node in a gNB DU configuration update message and assigned by the second donor centralized unit. Donor device.

14. The donor device according to claim 13, wherein the communication unit establishes the second donor centralized unit based on the IP address selected and used by the mobile node, and transmits a transmission migration management request message to the second donor centralized unit. The transmission migration management request message includes downlink transmission network layer information and the BAP layer address for the second donor centralized unit to set layer 2 mapping for the donor distributed unit; and receives a transmission migration management response message sent by the second donor centralized unit. Donor device.

15. A mobile node, including a mobile terminal and a distributed unit, the F1 connection of the distributed unit is terminated at the first donor centralized unit, and the distributed unit of the mobile node receives second information about the first cell transmitted by the first donor centralized unit, the second information about the first cell is set or reconfigured by the first donor centralized unit based on the first information about the location of the mobile node. Mobile node.

16. The mobile node according to claim 15, The first donor centralized unit is an F1 termination donor centralized unit of a plurality of mobile nodes within a specified area. When the plurality of mobile nodes move within the specified area, the F1 connection of the distributed units of the plurality of mobile nodes is always terminated by the first donor centralized unit. Mobile node.

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

18. The mobile node according to claim 15, wherein The mobile terminal of the mobile node establishes a radio resource control connection with a second donor centralized unit. The IP address of the first donor centralized unit is set for the distributed unit of the mobile node by an OAM entity. After the mobile terminal of the mobile node receives a radio resource control connection reconfiguration message sent by the second donor centralized unit, the distributed unit of the mobile node starts establishing an F1 connection with the first donor centralized unit using the IP address assigned by the second donor centralized unit. The radio resource control connection reconfiguration message includes the IP address and BAP layer address assigned by the second donor centralized unit for the mobile node. The BAP layer address is carried in the F1 connection establishment request sent by the distributed unit of the mobile node. Mobile node.

19. The mobile node according to claim 15, wherein The distributed unit of the mobile node reports to the first donor centralized unit, via a gNB DU configuration update message, an IP address selected from among the IP addresses assigned by the second donor centralized unit for use. The IP address selected and used by the mobile node is used by the first donor centralized unit to determine the second donor centralized unit. Mobile node.

20. An integrated access and backhaul (IAB) system, comprising A donor centralized unit and a mobile node. The F1 connection of the distributed unit of the mobile node is terminated at the donor centralized unit, The donor centralized unit sets or re-sets second information regarding a first cell for the distributed unit of the mobile node based on first information regarding the position of the mobile node, and transmits the second information regarding the first cell to be set or re-set to the distributed unit of the mobile node, an integrated access and backhaul (IAB) system.

Images