Message forwarding method and apparatus

Abstract

Embodiments of the present application provide a message forwarding method and apparatus. The method comprises: a source NG-RAN node and a target NG-RAN node forward an XnAP message via a core network by means of NGAP signaling. According to the embodiments of the present application, the problem of lacking signaling interaction via an Xn interface between universal RAN nodes is solved, and information interaction between RAN nodes is supported.

Description

Message forwarding method and device Technical Field

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

[0002] Integrated access and backhaul (IAB) implements the wireless relay function in the next generation radio access network (NG-RAN). This relay node is called an IAB-node, which supports both access and backhaul (BH) through 5G NR (new radio). All IAB nodes are connected to an IAB-donor node through one or more hops. These multi-hop connections form a directed acyclic graph (DAG) topology with the IAB-donor node as the root node. The IAB-donor node is responsible for performing centralized resource management, topology management, and routing management in the IAB network topology.

[0003] An IAB node supports gNB functions and is called an IAB-DU (distributed unit). It can serve standard UEs (user equipment) and IAB child nodes. An IAB node also supports some UE functions and is called an IAB-MT (mobile termination). The IAB-MT supports functions such as the UE physical layer, access stratum (AS), radio resource control (RRC), and non-access stratum (NAS), and can connect to an IAB parent node. The network-side termination node is called an IAB-donor, which provides network access for the IAB-MT or UE via backhaul or access links. The IAB-donor is further divided into the IAB-donor-CU (central unit) and the IAB-donor-DU. The IAB-DU and IAB-donor-CU are connected via the F1 interface. In a standalone network scenario, the gNB and IAB-donor-CU are connected via the Xn interface.

[0004] To support multi-hop routing of data packets, IAB introduces the BAP (Backhaul Adaptation Protocol) sublayer. Located above the RLC (radio link control) sublayer and below the IP (Internet Protocol) layer, the BAP sublayer supports functions such as selecting the destination node and path for data packets, routing and forwarding data packets, bearer mapping, flow control feedback, and notification of backhaul link failures.

[0005] In multi-hop scenarios, to relay data packets, the IAB node needs to determine the destination node for the packet, then determine the next hop corresponding to the destination node based on the routing table and send the packet. In this scenario, the IAB-donor-CU configures the mapping of each F1-U tunnel, each non-UE-associated F1AP message, each UE-associated F1AP message, and each non-F1 traffic message to a BAP routing identifier for uplink transmissions initiated from the IAB node via F1AP (F1 Application Protocol) signaling. The IAB node determines the BAP routing identifier corresponding to different types of uplink IP packets initiated from the IAB node based on this routing identifier mapping information and encapsulates these uplink IP packets with a BAP subheader containing the BAP routing identifier information. The IAB-donor-CU (abbreviated as donor-CU, CU, or gNB-CU) configures the mapping of different types of downlink data packets to BAP routing identifiers for the IAB-donor-DU via F1AP signaling. The IAB-donor-DU (abbreviated as donor-DU) determines the BAP routing identifier corresponding to the received downlink IP packets according to the routing identifier mapping information, and encapsulates the BAP subheader containing the BAP routing identifier information for these downlink IP packets.

[0006] The BAP routing identifier includes the destination BAP address and the path identity from the IAB node to the IAB-donor-DU. The BAP address is also called the destination in the BAP header. Each IAB node and IAB-donor-DU is configured with a BAP address.

[0007] The IAB node integration process, also known as the startup process, involves the IAB-MT accessing the network, obtaining IAB-related configuration information, and activating the DU functions to provide services to the UE. During IAB mobility, due to geographic changes or traffic management requirements, the MT and / or DU of an IAB node can migrate, changing the MT's and / or DU's termination host. These migration processes are called MT migration and DU migration, respectively.

[0008] It should be noted that the above introduction to the technical background is merely intended to provide a clear and complete description of the technical solutions of this application and facilitate understanding by those skilled in the art. Simply because these solutions are described in the background technology section of this application, it should not be assumed that the above technical solutions are well known to those skilled in the art.

[0009] Summary of the Invention

[0010] The inventors discovered that when an IAB node is in an inter-CU topology, inter-CU signaling interaction is essential. Currently, IAB-donor-CU signaling interaction is performed via the Xn interface between the IAB-donor-CU. However, without the Xn interface between the IAB-donor-CU, this signaling interaction cannot occur, and the inter-CU IAB topology cannot be supported, thus affecting the mobility performance of the IAB node.

[0011] In response to the above problems or similar problems or similar problems in other scenarios, an embodiment of the present application provides a message forwarding method and device.

[0012] According to one aspect of an embodiment of the present application, a message forwarding device is provided, configured at a source NG-RAN node, the device comprising:

[0013] A sending unit, which sends a first XnAP message to a target NG-RAN node, where the first XnAP message is forwarded via a core network through NGAP signaling.

[0014] According to another aspect of an embodiment of the present application, a message forwarding device is provided, configured at a target NG-RAN node, the device comprising:

[0015] A receiving unit receives a first XnAP message from a source NG-RAN node, where the first XnAP message is forwarded via a core network through NGAP signaling.

[0016] According to another aspect of an embodiment of the present application, a message forwarding device is provided, configured in an AMF (Access and Mobility Management Function) entity, the device comprising:

[0017] a first receiving unit, configured to receive a first message sent by a source NG-RAN node, where the first message includes a first XnAP message;

[0018] A first sending unit sends a second message to the source NG-RAN node, where the second message includes a second XnAP message if the first XnAP message is forwarded successfully.

[0019] According to another aspect of an embodiment of the present application, a message forwarding device is provided, configured in an IAB node in an IAB network, the device comprising:

[0020] a receiving unit configured to receive a fifth message from the first host CU, wherein the fifth message includes the first XnAP message;

[0021] A sending unit sends a sixth message to the second host CU, where the sixth message includes the first XnAP message.

[0022] According to another aspect of an embodiment of the present application, a message forwarding device is provided, which is configured in an IAB host node in an IAB network, and includes:

[0023] a sending unit configured to send a fifth message and / or a seventh message to the IAB node, wherein the fifth message includes the first XnAP message, and the seventh message includes the second XnAP message;

[0024] A receiving unit receives a sixth message and / or an eighth message sent by the IAB node, wherein the sixth message includes the first XnAP message, and the eighth message includes the second XnAP message.

[0025] One of the beneficial effects of the embodiments of the present application is that, according to the embodiments of the present application, the signaling interaction issue between IAB and donor nodes without an Xn interface is resolved, thereby supporting inter-CU integration of IAB nodes and IAB migration. Furthermore, the embodiments of the present application also resolve the signaling interaction issue between general RAN nodes without an Xn interface, thereby supporting information exchange between RAN nodes.

[0026] With reference to the following description and accompanying drawings, specific embodiments of the present application are disclosed in detail, indicating the manner in which 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 appended claims, the embodiments of the present application include many variations, modifications and equivalents.

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

[0028] 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

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

[0030] 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:

[0031] FIG1 is a schematic diagram of an example of an IAB network topology;

[0032] FIG2 is a schematic diagram of an example of a topology scenario of IAB-MT migration;

[0033] FIG3 is a schematic diagram of an example topology scenario of IAB-DU migration;

[0034] FIG4 is a schematic diagram of a message forwarding method according to an embodiment of the first aspect of the present application;

[0035] FIG5 is a schematic diagram of the first process;

[0036] FIG6 is a schematic diagram of the second process.

[0037] FIG7 is another schematic diagram of the message forwarding method according to the embodiment of the first aspect of the present application;

[0038] FIG8 is another schematic diagram of the message forwarding method according to the embodiment of the first aspect of the present application;

[0039] FIG9 is a schematic diagram of the NG-based IAB-MT migration process;

[0040] FIG10 is a schematic diagram of the NG-based IAB-DU migration process;

[0041] FIG11 is a schematic diagram of the NG-based IAB integration process;

[0042] FIG12 is a schematic diagram of a message forwarding method according to an embodiment of the second aspect of the present application;

[0043] FIG13 is a schematic diagram of information interaction according to a method according to an embodiment of the present application;

[0044] FIG14 is a schematic diagram of XnAP message forwarding based on RRC / F1AP;

[0045] FIG15 is a schematic diagram of an example of IAB integration without an Xn interface;

[0046] FIG16 is another schematic diagram of the message forwarding method according to the second aspect of the present application;

[0047] FIG17 is another schematic diagram of the message forwarding method according to the embodiment of the second aspect of the present application;

[0048] FIG18 is a schematic diagram of a message forwarding device according to an embodiment of the present application;

[0049] FIG19 is another schematic diagram of the message forwarding device according to an embodiment of the present application;

[0050] FIG20 is another schematic diagram of a message forwarding device according to an embodiment of the present application;

[0051] FIG21 is another schematic diagram of a message forwarding device according to an embodiment of the present application;

[0052] FIG22 is another schematic diagram of a message forwarding device according to an embodiment of the present application;

[0053] FIG23 is another schematic diagram of a message forwarding device according to an embodiment of the present application;

[0054] FIG24 is a schematic diagram of an NG-RAN node according to an embodiment of the present application;

[0055] FIG25 is a schematic diagram of an IAB host node according to an embodiment of the present application. DETAILED DESCRIPTION

[0056] 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 the accompanying drawings, specific embodiments of the present application are disclosed in detail, which illustrate 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 appended claims.

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

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

[0059] 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 Long Term Evolution (LTE), enhanced Long Term Evolution (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

[0060] 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, New Radio (NR), etc., and / or other currently known or future communication protocols to be developed.

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

[0062] Base stations may include, but are not limited to, NodeB (NB), evolved NodeB (eNodeB or eNB), 5G base stations (gNB), RAN nodes, IAB-donors, and the like. 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.

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

[0064] Terminal devices may include, but are not limited to, cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptop computers, cordless phones, smartphones, smart watches, digital cameras, and IAB-MT, etc.

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

[0066] In the embodiments of the present application, the core network includes the 5G core network (5GC) and also includes core networks of other communication protocol versions. The 5G core network includes control plane network elements and user plane network elements. In addition to the access and mobility management function (AMF), the control plane network elements also include the session management function (SMF) and the location management function (LMF). The embodiments of the present application are not limited to which network element of the core network is used for forwarding, and the AMF is used as an example for illustration.

[0067] In the embodiments of the present application, the NG-RAN node and 5GC are connected via an NG interface. The NG-RAN node in the embodiments of the present application can be replaced by any network device, and the Xn interface can be replaced by any interface between network devices, such as the X2 interface and network device interfaces in future communication protocols. XnAP can be replaced by an interface application protocol between corresponding network devices. The NG interface can be replaced by an interface between any network device and the core network. NGAP can be replaced by an interface application protocol between corresponding network devices and the core network.

[0068] FIG1 is a schematic diagram of an example of an IAB network topology structure, showing a situation where the MT and DU of an IAB are terminated to different donor-CUs.

[0069] The inventors discovered that the mobility of a mobile IAB (mIAB) or mobile relay in a larger area faces a challenge. That is, when it is on the move, based on the needs of network coverage and QoS support, the F1 termination host and non-F1 termination host of the IAB node may be different, that is, the MT and DU of the IAB may terminate at different IAB-donor-CUs.

[0070] An F1-terminating node is a donor-CU that terminates the F1 interface of an IAB node, such as donor-CU2 (in Figure 1, the F1 of IAB-DU1 terminates at donor-CU2). An F1-terminating donor-CU is also called the donor-CU of an IAB-DU because the IAB-DU is configured by this CU.

[0071] A non-F1-terminating node is a CU with host functionality that is not terminated by an IAB node's F1 interface, such as donor-CU1. Because non-F1-terminating nodes have an RRC connection with the IAB-MT, they can also be called IAB-MT host nodes. A non-F1-terminating host CU can also be called an IAB-MT host CU or an RRC-terminating donor-CU of an IAB node.

[0072] In Figure 1, IAB-MT1 is connected to its parent node, IAB Node 2, which then connects to donor-DU1 and donor-CU1. IAB-DU1 and donor-CU2 establish an F1 connection, but this F1 connection passes through IAB Node 2, donor-DU1, and ultimately to CU2.

[0073] Since the RRC interface and the F1 interface of the IAB node 1 are terminated at different donor-CUs, the IAB node 1 is a boundary IAB node.

[0074] The inventors discovered that when IAB node 1 is in the inter-CU topology scenario shown in Figure 1, inter-CU signaling interaction is necessary. Currently, IAB-donor-CU signaling interaction is performed via the Xn interface between IAB-donor-CU. Without the Xn interface between IAB-donor-CU, this signaling interaction would not be possible, and the inter-CU IAB topology would not be supported, thus affecting the mobility performance of the IAB node.

[0075] In this embodiment of the present application, taking a 5G multi-hop IAB network deployment as an example, multiple UEs connect to an IAB-donor through a multi-hop IAB node and ultimately access the 5G network. The IAB node to which the UE is connected is mobile. The MT and DU of the IAB node can be integrated into different donor-CUs, and the IAB node can perform MT and DU migration. However, this application is not limited to this, and this embodiment of the present application is also applicable to other non-IAB scenarios.

[0076] As can be seen from the above description of Figure 1, during the integration and mobility of the mobile IAB node, inter-CU scenarios may exist, that is, the MT and DU may terminate at different donor-CUs at a certain stage, that is, they are configured by different donor-CUs. Figure 1 can be seen as an integration scenario where the MT and DU of the IAB node are connected to different donor-CUs. Among them, donor-CU1 is the RRC-terminated donor-CU, referred to as CU1; donor-CU2 is the F1-terminated donor-CU, referred to as CU2. CU1 needs to perform signaling interaction with CU2 to perform IAB-related configurations.

[0077] Figure 2 is a schematic diagram of an example topology scenario for MT migration. In Figure 2, donor-CU1 is the source RRC-terminated donor-CU, donor-CU2 is the target RRC-terminated donor-CU, and there is also an F1-terminated donor-CU, which remains unchanged during the MT migration process. IAB-MT3 switches from donor-CU1 to donor-CU2. The transmission path of the F1 connection of IAB node 3 also changes from the topology passing through donor-CU1 to the topology passing through donor-CU2. The F1-terminated donor-CU and donor-CU1 need to perform signaling interaction to modify and release the traffic offloading association between them (that is, the binding relationship for traffic transmission migration). The F1-terminated donor-CU and donor-CU2 also need to perform signaling interaction to establish and modify the traffic offloading association between them and / or IAB resource coordination.

[0078] Figure 3 is a schematic diagram of an example topology scenario for DU migration. In Figure 3, donor-CU1 is the source F1-terminated donor-CU, donor-CU3 is the target F1-terminated donor-CU, and donor-CU2 is the RRC-terminated donor-CU, which remain unchanged during the DU migration process. An IAB-DU3 (DU3a and DU3b in Figure 3 are the two logical DU entities of DU3) migrates from donor-CU1 to donor-CU3. The endpoint of the F1 connection of IAB node 3 migrates from donor-CU1 to donor-CU3. Donor-CU1 and donor-CU2 need to perform signaling interaction to modify or release their traffic offload association. Donor-CU3 and donor-CU2 also need to perform signaling interaction to establish or modify their traffic offload association and / or IAB resource coordination. Donor-CU1 switches the UE served by IAB node 3 to donor-CU3.

[0079] In the aforementioned scenarios, the donor-CU needs to exchange various IAB-related messages and some required identification information, such as base station identification, IAB node identification, etc. In the case where some donor-CU (base station) do not have an Xn interface, how to forward the above-mentioned IAB-related messages (not limited to this, other non-IAB-related messages can also be used for different network architectures) is a research direction of the embodiments of this application.

[0080] Various embodiments of the present application are described below with reference to the accompanying drawings. These embodiments are merely illustrative and are not intended to limit the present application. In the following description, expressions such as "if...", "in the case of...", and "when..." have the same meaning and are interchangeable.

[0081] Embodiments of the first aspect

[0082] An embodiment of the present application provides a message forwarding method.

[0083] Figure 4 is a schematic diagram of a message forwarding method according to an embodiment of the present application, which is explained from the side of a source NG-RAN node. The source NG-RAN node is, for example, donor-CU 1 or donor-CU 2 in the scenario shown in Figure 2. There is no Xn interface between the source NG-RAN node and the F1-terminating donor-CU in the scenario shown in Figure 2, but XnAP messages need to be exchanged therewith. In this case, the F1-terminating donor-CU in the scenario shown in Figure 2 is the target NG-RAN node, and vice versa. Alternatively, the source NG-RAN node is, for example, donor-CU 1 or donor-CU 3 in the scenario shown in Figure 3. There is no Xn interface between the source NG-RAN node and the donor-CU 2 in the scenario shown in Figure 3, but XnAP messages need to be exchanged therewith. In this case, donor-CU 2 in the scenario shown in Figure 3 is the target NG-RAN node, and vice versa.

[0084] Referring to FIG. 4 , the method includes:

[0085] 401: The source NG-RAN node and the target NG-RAN node forward the XnAP message via the core network using NGAP signaling.

[0086] According to an embodiment of the present application, in the scenario shown in Figures 1 to 3, when there is no Xn interface between the CUs that need to exchange information, the source CU and the target CU can forward XnAP messages that originally need to be transmitted through the Xn interface through NGAP (NG Application Protocol) signaling of the NG interface. This solves the problem of the MT and DU of the mobile IAB node connecting to different IAB-donors in the scenario where there is no Xn interface between IAB-donors.

[0087] The above uses the IAB scenario as an example. The embodiments of the present application can also be extended to other scenarios. For example, when there is no Xn interface between certain base stations (RAN nodes), the source base station and the target base station can forward XnAP messages that originally need to be transmitted through the Xn interface through the core network via NGAP signaling of the NG interface. For ease of explanation, the following only uses the IAB scenario as an example.

[0088] In the embodiment of the present application, "source" and "target" refer to the source and target that need to exchange information. For example, when donor-CU1 wants to initiate a process to send a message to donor-CU2, the donor-CU1 is the source donor-CU and the donor-CU2 is the target donor-CU; on the contrary, when donor-CU2 wants to initiate a process to send a message to donor-CU1, donor-CU2 is the source donor-CU and donor-CU1 is the target donor-CU.

[0089] In this embodiment of the present application, there is no Xn interface between the source NG-RAN node and the target NG-RAN node. That is, when there is no Xn interface between the source NG-RAN node and the target NG-RAN node, the source NG-RAN node and the target NG-RAN node forward XnAP messages via the core network using NGAP signaling.

[0090] In some embodiments, the source NG-RAN is, for example, a host CU of an IAB node, which may be an F1-terminated host CU or a non-F1-terminated host CU. The target NG-RAN is, for example, a host CU of an IAB node, which may be a non-F1-terminated host CU or a F1-terminated host CU.

[0091] In the above embodiment, the method can be used in the integration and / or migration process of IAB nodes, such as the scenarios shown in Figures 1 to 3. However, the present application is not limited thereto, and the above method in the embodiment of the present application can also be used in non-IAB scenarios.

[0092] In some embodiments, the forwarding of the XnAP message can reuse existing NG interface-based handover procedures. For example, if the signaling interaction is related to UE handover, the existing NG interface-based handover procedures, i.e., UE mobility management procedures, such as handover preparation procedures, handover resource allocation procedures, and handover notification procedures, can be reused.

[0093] In other embodiments, a new procedure may be used to forward the XnAP message. For example, if it is not a signaling interaction related to UE handover, that is, other Xn procedures, the forwarding of the XnAP message may be achieved by establishing a new NGAP (NG Application Protocol) procedure on the NG interface.

[0094] For example, two new general NGAP processes may be added, namely a first process and a second process. Figure 5 is a schematic diagram of the first process, and Figure 6 is a schematic diagram of the second process.

[0095] As shown in Figure 5, the first process is for the source NG-RAN node to forward a message (called the first XnAP message) that was originally required to be sent on the Xn interface to the target NG-RAN node via the AMF (Access and Mobility Management Function). The source NG-RAN node here is, for example, the donor-CU of the IAB node, which can be an F1-terminating donor-CU or a non-F1-terminating donor-CU. Depending on the initiator of the message of this first process, the initiator is the source NG-RAN node and the recipient is the target NG-RAN node.

[0096] In some embodiments, as shown in Figure 5, the source NG-RAN node sends a first message to the AMF, where the first message includes a first XnAP message; the source NG-RAN node receives a second message from the AMF, where the second message includes a second XnAP message if the first XnAP message is forwarded successfully.

[0097] In the above embodiment, the source NG-RAN node initiates the first process by sending a first message (NGAP message) to the serving AMF. In some embodiments, when the source NG-RAN node sends the first message, a first timer may be started. The function of the first timer is to determine whether to continue waiting for the AMF's response. Because the AMF needs to forward the message to the target NG-RAN node, receive a response from the target NG-RAN, and then reply with a second message to the source NG-RAN node, there may be message failures or delays. In this way, when the first timer times out, the source NG-RAN node considers that the forwarding of the first XnAP message has failed. When the source NG-RAN node receives the second message from the AMF, the first timer may be stopped. In addition, when the source NG-RAN node considers that the forwarding of the first XnAP message has failed, it may also send a cancel command to the AMF to inform the AMF to cancel the forwarding of the first XnAP message.

[0098] In the above embodiment, the first message may further include an identifier, such as a global RAN node identifier plus a selected tracking area identifier, to indicate the target NG-RAN node. Furthermore, the first message may also include information that the source NG-RAN node intends to send to the target NG-RAN node, namely, the aforementioned first XnAP message.

[0099] In the above embodiment, the first XnAP message can be placed in an Xn container, for example, called a first container. The first container, as an IE, contains information (the first XnAP message) transparently transmitted from the source IAB-donor to the target IAB-donor via the core network. The first XnAP message is generated by the source NG-RAN node, sent to the target NG-RAN node, and decoded by the target NG-RAN node.

[0100] In some implementations, the first container is in an octet string format and may include an IAB-related Xn message initiated by the source IAB-donor, such as IAB TRANSPORT MIGRATION MANAGEMENT REQUEST, IAB TRANSPORT MIGRATION MODIFICATION REQUEST, IAB RESOURCE COORDINATION REQUEST, etc. In addition, the first container is transparent to the core network.

[0101] In the above embodiment, the first container may also be placed in the Source to Target Transparent Container IE or the Source NG-RAN Node to Target NG-RAN Node Transparent Container IE, and the above IE may be enhanced to include the first container. Therefore, the first message may include the Source to Target Transparent Container IE or the Source NG-RAN Node to Target NG-RAN Node Transparent Container IE.

[0102] In the above embodiment, the second message may be a reply message from the AMF to the source NG-RAN node. If the AMF receives a reply from the target NG-RAN node through the second process, it may place the second container in the reply (containing the information that the target NG-RAN node wants to send to the source NG-RAN node, referred to as a second XnAP message) into the second message and send it to the source NG-RAN node. In this case, the second message may be a confirmation message. If the AMF does not receive a reply from the target NG-RAN node or receives a failure message in the target NG-RAN node's reply, the second message may be a failure message.

[0103] In the above embodiment, similar to the first container, the second container may contain information transparently transmitted from the target IAB-donor to the source IAB-donor via the core network, referred to as a second XnAP message. Furthermore, the second container may be formatted as an octal string and contain an IAB-related Xn message replied by the target IAB-donor. Specifically, the second XnAP message is an IAB-related Xn message replied by the target IAB-donor, such as an IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE, an IAB TRANSPORT MIGRATION MODIFICATION RESPONSE, or an IAB RESOURCE COORDINATION RESPONSE.

[0104] As shown in Figure 6, the second process is for the AMF to forward to the target NG-RAN node the information received from the source NG-RAN node that was originally required to be sent on the Xn interface (i.e., the first Xn message described above). Optionally, the AMF may also forward to the target NG-RAN node the identification information of the target NG-RAN node obtained from the first process.

[0105] In some embodiments, as shown in Figure 6, the AMF determines the target NG-RAN node based on the identification information and sends a third message to the target NG-RAN node, the third message including the first XnAP information. The AMF also receives a fourth message from the target NG-RAN node, the fourth message including a second XnAP message. The second XnAP message is generated by the target NG-RAN node and indicates information that the target NG-RAN node wants to send to the source NG-RAN node.

[0106] In the above embodiment, the AMF initiates the second process by sending a third message (NGAP message) to the target NG-RAN node. This third message may include the first container received by the AMF from the first process. The first container has been described above and is not described here.

[0107] In the above embodiment, the target NG-RAN node can generate a reply Xn message (second XnAP message) by decoding the content of the first container, put it into the second container, and then put it into the fourth message to reply to the AMF.

[0108] In the above embodiment, the format of the second container is, for example, an octet string, and may include an IAB-related Xn message replied by the target IAB-donor, such as IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE, IAB TRANSPORT MIGRATION MODIFICATION RESPONSE, IAB RESOURCE COORDINATION RESPONSE, etc.

[0109] In the above embodiment, similar to the first container, the second container can be placed in the Target to Source Transparent Container IE or the Target NG-RAN Node to Source NG-RAN Node Transparent Container IE. By enhancing the above IE, the second Xn container is added. Therefore, the fourth message can include the Target to Source Transparent Container IE or the Target NG-RAN Node to Source NG-RAN Node Transparent Container IE.

[0110] FIG7 is another schematic diagram of a message forwarding method according to an embodiment of the present application, which is described from the perspective of a target NG-RAN node. The same contents as in the previous embodiment will not be repeated. As shown in FIG7 , the method includes:

[0111] 701: The target NG-RAN node and the source NG-RAN node forward the XnAP message via the core network using NGAP signaling.

[0112] In some embodiments, the target NG-RAN node receives a third message sent by the AMF, where the third message includes the aforementioned first XnAP information; the target NG-RAN node sends a fourth message to the AMF, where the fourth message includes the aforementioned second XnAP message.

[0113] In the above embodiment, the third message may include a first container, where the first container includes the above-mentioned first XnAP message transparently transmitted by the source IAB-donor to the target IAB-donor through the core network; the target NG-RAN node generates the above-mentioned second XnAP message by decoding the content of the first container.

[0114] In the above embodiment, the fourth message may include a second container, where the second container includes the second XnAP message transparently transmitted by the target IAB-donor to the source IAB-donor through the core network.

[0115] In the above embodiment, the first XnAP information can be transparently transmitted through the first container; the second XnAP information can be transparently transmitted through the second container. The details have been explained above and will not be repeated here.

[0116] Figure 8 is another schematic diagram of the message forwarding method according to an embodiment of the present application, illustrating the method from the perspective of the AMF. The same contents as the previous embodiment will not be repeated here. As shown in Figure 8, the method includes:

[0117] 801: AMF forwards the XnAP message between the source NG-RAN node and the target NG-RAN node via NGAP signalling.

[0118] In some embodiments, the AMF receives a first message sent by a source NG-RAN node, where the first message includes a first XnAP message; the AMF sends a second message to the source NG-RAN node, where the second message includes a second XnAP message if the first XnAP message is forwarded successfully.

[0119] In some embodiments, when the AMF receives a confirmation message from the target NG-RAN node, the second message is confirmation information that the first XnAP message is successfully forwarded; when the AMF does not receive a reply from the target NG-RAN node or receives a failure message from the target NG-RAN node, the second message is confirmation information that the first XnAP message fails to be forwarded.

[0120] In some embodiments, the AMF determines the target NG-RAN node based on the identification information included in the first message, and sends a third message to the target NG-RAN node, where the third message includes the aforementioned first XnAP information; the AMF receives a fourth message from the target NG-RAN node, where the fourth message includes the aforementioned second XnAP message.

[0121] In the above embodiment, the first XnAP information can be transparently transmitted through the first container; the second XnAP information can be transparently transmitted through the second container. The details have been explained above and will not be repeated here.

[0122] Figure 9 is a schematic diagram of the NG-based MT migration process, showing the MT migration process based on NG interface message forwarding. In addition, Figure 9 only shows the process of forwarding XnAP messages based on the NG interface, and other migration-related signaling processes can occur at any step.

[0123] As shown in Figure 9, the first to fourth steps implement the Xn IAB process between the RRC-terminating IAB donor (source NG-RAN node) and the F1-terminating IAB-donor (target NG-RAN node) through the first and second processes, such as the IAB Transport Migration Modification process, which can implement functions such as modification and release of IAB transport migration.

[0124] In the first step, IAB-donor CU1 sends a first message to the AMF. The first message contains a first container, the base station identifier of IAB-donor CU3, and may also contain the UE XnAP ID (Target NG-RAN node UE XnAP ID) of the IAB node in IAB-donor CU3. In the second step, the AMF sends a third message to IAB-donor CU3. The third message contains the first container and may also contain the UE XnAP ID of the IAB node in IAB-donor CU3. The first container contains an Xn IAB TRANSPORT MIGRATION MODIFICATION REQUEST message. In the third step, IAB-donor CU3 replies to the AMF with a fourth message containing a second container. The second container contains an Xn IAB TRANSPORT MIGRATION MODIFICATION RESPONSE message. In the fourth step, the AMF sends a second message to IAB-donor CU1. The second message may also contain the second container. Depending on the message forwarding situation, the second message type or name can be confirmation information or failure information.

[0125] As shown in Figure 9, steps 5 to 8 are similar to steps 1 to 4. The first and second procedures implement the Xn IAB process between the F1-terminating IAB-donor (source NG-RAN node) and the RRC-terminating IAB donor (target NG-RAN node), such as the IAB Transport Migration Management process, to implement the IAB transport migration management function.

[0126] Figure 10 is a schematic diagram of the DU migration process based on NG, showing the DU migration process based on NG interface message forwarding. In Figure 10, only the process of forwarding Xn messages based on NG interface is shown, and other migration-related signaling processes can occur at any step.

[0127] As shown in Figure 10, each step can be performed similarly to the signaling flow for MT migration described above. The main difference is that IAB-donor CU1, IAB-donor CU, and IAB-donor CU3 in Figure 10 represent different donor-CU and MT migrations. For example, steps 1 through 4 are the NGAP-based IAB transfer migration management process from the target F1-terminating donor to the RRC-terminating donor.

[0128] FIG11 is a schematic diagram of an NG-based IAB integration process, illustrating an IAB integration process based on message forwarding of an NG interface.

[0129] As shown in Figure 11, after the F1 setup from the IAB-DU to the IAB-donor CU2 is completed in step 5, the F1-terminating donor-CU (source NG-RAN node) can exchange IAB-related management and coordination information with the RRC-terminating donor-CU (target NG-RAN node). Steps 6 to 9 implement the Xn IAB procedures, such as the IAB transport migration management procedures, between the F1-terminating IAB-donor (source NG-RAN node) and the RRC-terminating IAB donor (target NG-RAN node), using the first and second NGAP procedures, when there is no Xn interface between IAB-donor CU1 and IAB-donor CU2.

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

[0131] The method according to the embodiment of the present application solves the signaling interaction problem between common RAN nodes without an Xn interface, thereby supporting information interaction between RAN nodes. For example, in scenarios where no Xn interface exists between IAB-donors, the method solves the problem of integrating the MT and DU of a mobile IAB node into different IAB-donors, as well as the MT and DU migration issues. This supports the configuration flexibility of IAB nodes, supports the mobility of IAB nodes across a wide area, and can provide high-quality services to UEs served by mobile IAB nodes.

[0132] Embodiments of the second aspect

[0133] An embodiment of the present application provides a message forwarding method, which is applied to an IAB network.

[0134] FIG12 is a schematic diagram of a message forwarding method according to an embodiment of the present application, illustrating the method from the perspective of an IAB node in an IAB network. FIG13 is a schematic diagram of information interaction according to an embodiment of the present application. Referring to FIG12 and FIG13 , the method includes:

[0135] 1201: The IAB node receives a fifth message from the first host CU, where the fifth message includes the first XnAP message.

[0136] 1202: The IAB node sends a sixth message to the second host CU, where the sixth message includes the first XnAP message.

[0137] In the embodiment of the present application, there is no Xn interface between the first host CU and the second host CU. That is, in the absence of an Xn interface between the first host CU and the second host CU, the XnAP message between the first host CU and the second host CU is forwarded by the IAB node. This solves the problem of integrating the MT and DU of the mobile IAB node into different IAB-donors, as well as the MT migration and DU migration problems, in the scenario where there is no Xn interface between IAB-donors. This supports the configuration flexibility of the IAB node, supports the mobility of the IAB node in a wide area, and can provide high-quality services for UEs served by the mobile IAB node.

[0138] In the embodiments of the present application, similar to the embodiments of the first aspect, the method of the embodiments of the present application can be applied to IAB scenarios or non-IAB scenarios, and the present application does not limit this.

[0139] In some embodiments, the fifth message is an RRC message and the sixth message is an F1AP message, or the fifth message is an F1AP message and the sixth message is an RRC message; in addition, the fifth message and the sixth message respectively include a first container, which first container includes the above-mentioned first XnAP message transparently transmitted by the first host CU to the second host CU through the IAB node.

[0140] For example, if the first host CU is an RRC-terminating donor-CU and the second host CU is an F1-terminating donor-CU, the fifth message is an RRC message and the sixth message is an F1AP message. For another example, if the first host CU is an F1-terminating donor-CU and the second host CU is an RRC-terminating donor-CU, the fifth message is an F1AP message and the sixth message is an RRC message.

[0141] According to the above embodiment, RRC and F1AP are enhanced to include XnAP messages, and these IAB-related coordination messages are transparently forwarded through the IAB node.

[0142] Figure 14 is a schematic diagram of XnAP message forwarding based on RRC / F1AP. As shown in Figure 14, between the RRC-terminating donor-CU (Donor-CU1) and the IAB-MT, the RRC layer is enhanced to put the first XnAP message as the first container into the RRC message for transmission; between the F1-terminating donor-CU (Donor-CU2) and the IAB-DU, the F1AP is enhanced to put the first XnAP message as the first container into the F1AP message for transmission.

[0143] In the above example, when Donor-CU 1 is the first host CU and Donor-CU 2 is the second host CU, the IAB node can put the first container in the RRC message (fifth message) received from Donor-CU1 into the F1AP message (sixth message) and forward it to Donor-CU2; when Donor-CU2 is the first host CU and Donor-CU1 is the second host CU, the IAB node can put the first container in the F1AP message (fifth message) received from Donor-CU2 into the RRC message (sixth message) and forward it to Donor-CU1.

[0144] In the above embodiment, the meaning of the first container is the same as that in the embodiment of the first aspect and will not be repeated here.

[0145] In some embodiments, as shown in FIG13 , the IAB node may also receive a seventh message from the second host CU, the seventh message including the second XnAP message, and the IAB node sends an eighth message to the first host CU, the eighth message including the second XnAP message.

[0146] In the above embodiment, similar to the fifth and sixth messages, the seventh message can be an F1AP message or an RRC message, or the eighth message is an RRC message or an F1AP message; in addition, the seventh message and the eighth message respectively include a second container, which includes the above-mentioned second XnAP message transparently transmitted by the second host CU to the first host CU through the IAB node.

[0147] Still taking the scenario shown in Figure 14 as an example, when Donor-CU 1 is the first host CU and Donor-CU 2 is the second host CU, the IAB node can put the second container in the F1AP message (seventh message) received from Donor-CU2 into the RRC message (eighth message) and forward it to Donor-CU1; when Donor-CU2 is the first host CU and Donor-CU1 is the second host CU, the IAB node can put the second container in the RRC message (seventh message) received from Donor-CU1 into the F1AP message (eighth message) and forward it to Donor-CU2.

[0148] In the aforementioned embodiments, the enhancement to the RRC layer is, for example, to add information about the first container and the second container to the downlink RRC message (the fifth or seventh message), such as the RRCReconfiguration message or the DLInformationTransfer message, and the uplink RRC message (the sixth or eighth message), such as the ULInformationTransfer and IAB0therInformation. These containers can be defined as new IEs in the above messages.

[0149] When the RRC message (fifth message or seventh message) received by the IAB-MT includes the first container or the second container, the juxtaposed IAB-DU includes the received first container or the second container in the F1AP message (sixth message or eighth message) and sends it to the donor-CU of the DU.

[0150] In the aforementioned embodiments, the F1AP enhancements include, for example, including information about the first and second containers in the F1AP message (the sixth or eighth message) in the gNB-DU to gNB-CU direction; and / or including information about the first and second containers in the F1AP message (the fifth or seventh message) in the gNB-CU to gNB-DU direction. These containers can be defined as new IEs in the aforementioned messages. A new F1AP process can be defined to include newly defined fifth, sixth, seventh, and eighth messages. Because the aforementioned F1AP messages already include IEs representing the first and second containers, the F1AP process can merge the messages. That is, the message direction need not be distinguished, only whether the message is for initiation or response. This allows the F1AP process to require only two messages, such as the fifth and eighth messages. The messages use either the first or second container as needed.

[0151] When the F1AP message (fifth message) received by the IAB-DU includes the first container or the second container, the collocated IAB-MT includes the received first container or the second container in the RRC message (sixth message) and sends it to the donor-CU of the MT.

[0152] In the above embodiment, existing messages may be reused, for example, the fifth message may be CU-DU RADIO INFORMATION TRANSFER, etc., and the eighth message may be DU-CU RADIO INFORMATION TRANSFER, etc. These containers are defined as new IEs in the above messages.

[0153] Figure 15 is a schematic diagram of an example of IAB integration without an Xn interface, illustrating the use of RRC and F1AP for Xn message forwarding. As shown in Figure 15, steps 6 to 9 describe the Xn message forwarding process between two donor-CUs. Similar steps can be used in other IAB migration scenarios.

[0154] FIG16 is another schematic diagram of the message forwarding method according to an embodiment of the present application, which is described from the perspective of the first host CU in the IAB network. The same contents as the previous embodiment will not be repeated. Referring to FIG16 , the method includes:

[0155] 1601: The first host CU sends a fifth message to the IAB node, where the fifth message includes a first XnAP message; so that the IAB node sends a sixth message to the second host CU, where the sixth message includes the first XnAP message.

[0156] In some embodiments, the IAB node further receives a seventh message from the second host CU, where the seventh message includes the second XnAP message; then the first host CU may further receive an eighth message sent by the IAB node, where the eighth message includes the second XnAP message.

[0157] FIG17 is another schematic diagram of a message forwarding method according to an embodiment of the present application, which is described from the perspective of a second host CU in an IAB network. The same contents as in the previous embodiment will not be repeated. Referring to FIG17 , the method includes:

[0158] 1701: The second host CU receives a sixth message sent by the IAB node, where the sixth message includes a first XnAP message. The first XnAP message comes from a fifth message received by the IAB node from the first host CU, where the fifth message includes the first XnAP message.

[0159] In some embodiments, the second host CU may further send a seventh message to the IAB node, where the seventh message includes the second XnAP message; so that the IAB node sends an eighth message to the first host CU, where the eighth message includes the second XnAP message.

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

[0161] The method according to the embodiment of the present application solves the signaling interaction problem between common RAN nodes without an Xn interface, thereby supporting information interaction between RAN nodes. For example, in scenarios where no Xn interface exists between IAB-donors, the method solves the problem of integrating the MT and DU of a mobile IAB node into different IAB-donors, as well as the MT and DU migration issues. This supports the configuration flexibility of IAB nodes, supports the mobility of IAB nodes across a wide area, and can provide high-quality services to UEs served by mobile IAB nodes.

[0162] Embodiments of the third aspect

[0163] An embodiment of the present application provides a message forwarding method.

[0164] Figure 18 is a schematic diagram of a message forwarding device 1800 according to an embodiment of the present application. This device may be, for example, a source NG-RAN node, or one or more components or assemblies configured within the source NG-RAN node. Because the principles underlying the problem solved by this device are similar to those of the embodiment of the first aspect, the common details will not be repeated.

[0165] As shown in FIG18 , the apparatus 1800 includes:

[0166] The processing unit 1801 forwards the XnAP message with the target NG-RAN node via the core network through NGAP signaling.

[0167] In some embodiments, the source NG-RAN node is a host CU of an IAB node, and the host CU is an F1 termination host CU or a non-F1 termination host CU.

[0168] In some embodiments, there is no Xn interface between the source NG-RAN node and the target NG-RAN node.

[0169] In some embodiments, the apparatus 1800 is used for integration and / or migration of IAB nodes.

[0170] In some embodiments, the processing unit 1801 sends a first message to the AMF, where the first message includes a first XnAP message; the processing unit 1801 receives a second message from the AMF, where the second message includes a second XnAP message if the first XnAP message is forwarded successfully.

[0171] In the above embodiment, the processing unit 1801 may start the first timer when sending the first message, and when the first timer times out, it is considered that the forwarding of the first XnAP message has failed; when the second message from the AMF is received, the first timer is stopped.

[0172] In the above embodiment, when the forwarding of the first XnAP message fails, the processing unit 1801 may send a cancel command to the AMF.

[0173] In the above embodiment, the first message may further include identification information indicating the target NG-RAN node, for example, the identification information is a global RAN node identifier and a selected tracking area identifier.

[0174] In the above embodiment, the first message may include a first container, where the first container includes the above first XnAP message transparently transmitted from the source IAB-donor to the target IAB-donor through the core network.

[0175] In the above embodiment, the format of the first container may be an octal string, and the first XnAP message is an IAB-related Xn message initiated by the source IAB-donor. The Xn message may include at least one of the following:

[0176] IAB TRANSPORT MIGRATION MANAGEMENT REQUEST,

[0177] IAB TRANSPORT MIGRATION MODIFICATION REQUEST,

[0178] IAB RESOURCE COORDINATION REQUEST.

[0179] In some embodiments, when the AMF receives a confirmation message from the target NG-RAN node, the second message is confirmation information that the first XnAP message is successfully forwarded; when the AMF does not receive a reply from the target NG-RAN node or receives a failure message from the target NG-RAN node, the second message is confirmation information that the first XnAP message fails to be forwarded.

[0180] In the above embodiment, the second message may include a second container, where the second container includes the second XnAP message transparently transmitted by the target IAB-donor to the source IAB-donor through the core network.

[0181] In the above embodiment, the format of the second container may be an octal string, and the second XnAP message is the IAB-related Xn message replied by the target IAB-donor. The Xn message may include at least one of the following:

[0182] IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE,

[0183] IAB TRANSPORT MIGRATION MODIFICATION RESPONSE,

[0184] IAB RESOURCE COORDINATION RESPONSE.

[0185] In some embodiments, the AMF may determine the target NG-RAN node based on the above-mentioned identification information, and send a third message to the target NG-RAN node, where the third message includes the above-mentioned first XnAP information; the AMF also receives a fourth message from the target NG-RAN node, where the fourth message includes the second XnAP message.

[0186] In the above embodiment, the third message may include a first container, where the first container includes the above-mentioned first XnAP message transparently transmitted by the source IAB-donor to the target IAB-donor through the core network; the target NG-RAN node may generate the above-mentioned second XnAP message by decoding the content of the first container.

[0187] In the above embodiment, the fourth message may include a second container, where the second container includes the second XnAP message transparently transmitted by the target IAB-donor to the source IAB-donor through the core network.

[0188] In the above embodiment, the format of the second container may be an octal string, and the second XnAP message is an IAB-related Xn message replied by the target IAB-donor. The Xn message may include at least one of the following:

[0189] IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE,

[0190] IAB TRANSPORT MIGRATION MODIFICATION RESPONSE,

[0191] IAB RESOURCE COORDINATION RESPONSE.

[0192] Figure 19 is another schematic diagram of a message forwarding apparatus 1900 according to an embodiment of the present application. This apparatus may be, for example, a target NG-RAN node, or one or more components or assemblies configured within the target NG-RAN node. Because the principles underlying the problem solved by this apparatus are similar to those of the embodiment of the first aspect, the common details will not be repeated.

[0193] As shown in FIG. 19 , the apparatus 1900 includes:

[0194] The processing unit 1901 forwards the XnAP message with the source NG-RAN node via the core network through NGAP signaling.

[0195] In some embodiments, the source NG-RAN node is a host CU of an IAB node, and the host CU is an F1 termination host CU or a non-F1 termination host CU.

[0196] In some embodiments, there is no Xn interface between the source NG-RAN node and the target NG-RAN node.

[0197] In some embodiments, the apparatus 1900 is used for an integration and / or migration process of an IAB node.

[0198] In some embodiments, the processing unit 1901 receives a third message sent by the AMF, where the third message includes the first XnAP information; the processing unit 1901 sends a fourth message to the AMF, where the fourth message includes the second XnAP message.

[0199] In the above embodiment, the third message may include a first container, which includes the first XnAP message transparently transmitted from the source IAB-donor to the target IAB-donor through the core network; the processing unit 1901 generates the second XnAP message by decoding the content of the g5 first container.

[0200] In the above embodiment, the fourth message may include a second container, where the second container includes the second XnAP message transparently transmitted by the target IAB-donor to the source IAB-donor through the core network.

[0201] In the above embodiment, the format of the second container may be an octal string, and the above second XnAP message is an IAB-related Xn message replied by the target IAB-donor. The Xn message may include at least one of the following:

[0202] IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE,

[0203] IAB TRANSPORT MIGRATION MODIFICATION RESPONSE,

[0204] IAB RESOURCE COORDINATION RESPONSE.

[0205] Figure 20 is another schematic diagram of a message forwarding device 2000 according to an embodiment of the present application. This device may be, for example, an AMF or one or more components or assemblies configured within the AMF. Because the principles for solving the problem addressed by this device are similar to those of the embodiment of the first aspect, the details will not be repeated.

[0206] As shown in FIG20 , the apparatus 2000 includes:

[0207] The processing unit 2001 forwards the XnAP message between the source NG-RAN node and the target NG-RAN node through NGAP signaling.

[0208] In some embodiments, the source NG-RAN node is a host CU of an IAB node, and the host CU is an F1 termination host CU or a non-F1 termination host CU.

[0209] In some embodiments, there is no Xn interface between the source NG-RAN node and the target NG-RAN node.

[0210] In some embodiments, the apparatus 2000 is used for integration and / or migration of IAB nodes.

[0211] In some embodiments, the processing unit 2001 receives a first message sent by the source NG-RAN node, where the first message includes a first XnAP message; the processing unit 2001 sends a second message to the source NG-RAN node, where the second message includes a second XnAP message when the first XnAP message is forwarded successfully.

[0212] In the above embodiment, the first message may further include identification information indicating the target NG-RAN node, such as a global RAN node identifier and a selected tracking area identifier.

[0213] In the above embodiment, the first message may include a first container, where the first container includes the above first XnAP message transparently transmitted from the source IAB-donor to the target IAB-donor through the core network.

[0214] In the above embodiment, the format of the first container may be an octal string, and the above first XnAP message is an IAB-related Xn message initiated by the source IAB-donor. The Xn message may include at least one of the following:

[0215] IAB TRANSPORT MIGRATION MANAGEMENT REQUEST,

[0216] IAB TRANSPORT MIGRATION MODIFICATION REQUEST,

[0217] IAB RESOURCE COORDINATION REQUEST.

[0218] In some embodiments, when the processing unit 2001 receives a confirmation message from the target NG-RAN node, the above-mentioned second message is confirmation information that the first XnAP message is successfully forwarded; when the processing unit 2001 does not receive a reply from the target NG-RAN node or receives a failure message from the target NG-RAN node, the above-mentioned second message is confirmation information that the first XnAP message is not forwarded.

[0219] In the above embodiment, the second message may include a second container, where the second container includes the above second XnAP message transparently transmitted by the target IAB-donor to the source IAB-donor through the core network.

[0220] In the above embodiment, the format of the second container may be an octal string, and the above second XnAP message is an IAB-related Xn message replied by the target IAB-donor. The Xn message may include at least one of the following:

[0221] IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE,

[0222] IAB TRANSPORT MIGRATION MODIFICATION RESPONSE,

[0223] IAB RESOURCE COORDINATION RESPONSE.

[0224] In some embodiments, the processing unit 2001 determines the target NG-RAN node based on the above-mentioned identification information, and sends a third message to the target NG-RAN node, where the third message includes the above-mentioned first XnAP information; the processing unit 2001 receives a fourth message from the target NG-RAN node, where the fourth message includes the above-mentioned second XnAP message.

[0225] In the above embodiment, the third message may include a first container, where the first container includes the above-mentioned first XnAP message transparently transmitted by the source IAB-donor to the target IAB-donor through the core network; the target NG-RAN node generates the above-mentioned second XnAP message by decoding the content of the first container.

[0226] In the above embodiment, the fourth message may include a second container, where the second container includes the second XnAP message transparently transmitted by the target IAB-donor to the source IAB-donor through the core network.

[0227] In the above embodiment, the format of the second container may be an octal string, and the second XnAP message is an IAB-related Xn message replied by the target IAB-donor. The Xn message may include at least one of the following:

[0228] IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE,

[0229] IAB TRANSPORT MIGRATION MODIFICATION RESPONSE,

[0230] IAB RESOURCE COORDINATION RESPONSE.

[0231] FIG21 is another schematic diagram of a message forwarding device 2100 according to an embodiment of the present application. The device may be, for example, an IAB node, or one or more components or assemblies configured in an IAB node. Since the principle of solving the problem of this device is similar to that of the embodiment of the second aspect, the same contents will not be repeated here.

[0232] As shown in FIG. 21 , the apparatus 2100 includes:

[0233] A receiving unit 2101 receives a fifth message from a first host CU, where the fifth message includes a first XnAP message;

[0234] The sending unit 2102 sends a sixth message to the second host CU, where the sixth message includes the first XnAP message.

[0235] In some embodiments, the receiving unit 2101 further receives a seventh message from the second host CU, where the seventh message includes a second XnAP message; the sending unit 2102 further sends an eighth message to the first host CU, where the eighth message includes the second XnAP message.

[0236] In some embodiments, there is no Xn interface between the first host CU and the second host CU.

[0237] In some embodiments, the apparatus 2100 may be used in an integration and / or migration process of an IAB node.

[0238] In some embodiments, the fifth message is an RRC message, the sixth message is an F1AP message, and the fifth message and the sixth message respectively contain a first container; the first container contains the above-mentioned first XnAP message transparently transmitted by the first host CU to the second host CU through the IAB node.

[0239] In some embodiments, the fifth message is an F1AP message, the sixth message is an RRC message, and the fifth message and the sixth message respectively contain a first container; the first container contains the above-mentioned first XnAP message transparently transmitted by the first host CU to the second host CU through the IAB node.

[0240] In the above embodiment, the format of the first container may be an octal string, and the above first XnAP message is an IAB-related Xn message initiated by the first host CU. The Xn message may include, for example, at least one of the following:

[0241] IAB TRANSPORT MIGRATION MANAGEMENT REQUEST,

[0242] IAB TRANSPORT MIGRATION MODIFICATION REQUEST,

[0243] IAB RESOURCE COORDINATION REQUEST.

[0244] In some embodiments, the seventh message is an F1AP message, the eighth message is an RRC message, and the seventh message and the eighth message respectively contain a second container; the second container contains a second XnAP message transparently transmitted by the second host CU to the first host CU through the IAB node.

[0245] In some embodiments, the seventh message is an RRC message, the eighth message is an F1AP message, and the seventh message and the eighth message respectively contain a second container; the second container contains the above-mentioned second XnAP message transparently transmitted by the second host CU to the first host CU through the IAB node.

[0246] In the above embodiment, the format of the second container can be an octal string, and the above second XnAP message is an IAB-related Xn message replied by the second host CU. The Xn message can include at least one of the following:

[0247] IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE,

[0248] IAB TRANSPORT MIGRATION MODIFICATION RESPONSE,

[0249] IAB RESOURCE COORDINATION RESPONSE.

[0250] FIG22 is another schematic diagram of a message forwarding device 2200 according to an embodiment of the present application. The device may be, for example, a first host CU, or one or more components or assemblies configured within the first host CU. Because the principles of this device for solving problems are similar to those of the embodiment of the second aspect, the same details will not be repeated.

[0251] As shown in FIG. 22 , the apparatus 2200 includes:

[0252] The sending unit 2201 sends a fifth message to the IAB node, wherein the fifth message includes the first XnAP message; so that the IAB node sends a sixth message to the second host CU, wherein the sixth message includes the first XnAP message.

[0253] In some embodiments, the IAB node further receives a seventh message from the second host CU, where the seventh message includes a second XnAP message. As shown in FIG22 , the apparatus 2200 further includes:

[0254] The receiving unit 2202 receives an eighth message sent by the IAB node, where the eighth message includes the second XnAP message.

[0255] FIG23 is another schematic diagram of a message forwarding device 2300 according to an embodiment of the present application. This device may be, for example, a second host CU, or one or more components or assemblies configured within the second host CU. Because the principles of this device for solving problems are similar to those of the first aspect, the same details will not be repeated.

[0256] As shown in FIG. 23 , the apparatus 2300 includes:

[0257] The receiving unit 2301 receives a sixth message sent by the IAB node, where the sixth message includes a first XnAP message. The first XnAP message comes from a fifth message received by the IAB node from a first host CU, where the fifth message includes the first XnAP message.

[0258] In some embodiments, as shown in FIG23 , the apparatus 2300 further includes:

[0259] The sending unit 2401 sends a seventh message to the IAB node, where the seventh message includes the second XnAP message, so that the IAB node sends an eighth message to the first host CU, where the eighth message includes the second XnAP message.

[0260] 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 devices 1800, 1900, 2000, 2100, 2200, and 2300 of the embodiments 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.

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

[0262] The apparatus according to the embodiment of the present application solves the signaling interaction problem between common RAN nodes without an Xn interface, thereby supporting information interaction between RAN nodes.

[0263] Embodiments of the fourth aspect

[0264] An embodiment of the present application provides a communications system, including a source NG-RAN node and a target NG-RAN second node. The source NG-RAN node and the target NG-RAN node are configured to perform the method described in the embodiment of the first aspect. The behaviors of the source NG-RAN node and the target NG-RAN node have been described in detail in the embodiment of the first aspect, and the content thereof is incorporated herein and will not be repeated here.

[0265] The present application also provides an IAB communication system, including a first host node, a second host node, and an IAB node. The first host node, the second host node, and the IAB node are configured to perform the method described in the embodiment of the second aspect. The behavior of the first host node, the second host node, and the IAB node has been described in detail in the embodiment of the second aspect, and the content thereof is incorporated herein and will not be repeated here.

[0266] An embodiment of the present application also provides an NG-RAN node, which includes a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the method according to any one of the first to third aspects.

[0267] Figure 24 is a schematic diagram of an NG-RAN node according to an embodiment of the present application. As shown in Figure 24 , NG-RAN node 2400 may include a processor 2401 and a memory 2402. Memory 2402 stores data and programs and is coupled to processor 2401. It should be noted that this figure is exemplary; other types of structures may be used to supplement or replace this structure to implement telecommunications or other functions.

[0268] For example, the processor 2401 may be configured to execute a program to implement a method as performed by a source NG-RAN node or a target NG-RAN node in an embodiment of the first aspect, or to implement a method as performed by an IAB node in an embodiment of the second aspect.

[0269] As shown in Figure 24 , the IAB node 2400 may further include: a communication module 2403, an input unit 2404, a display 2405, and a power supply 2406. The functions of these components are similar to those in the prior art and are not described here in detail. It is worth noting that the NG-RAN node 2400 does not necessarily include all of the components shown in Figure 24 , and these components are not essential. Furthermore, the NG-RAN node 2400 may also include components not shown in Figure 24 , for which reference may be made to the prior art.

[0270] An embodiment of the present application further provides an IAB host node, which includes a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the method according to the embodiment of the fourth aspect.

[0271] Figure 25 is a schematic diagram of an IAB host node according to an embodiment of the present application. As shown in Figure 25 , IAB host node 2500 may include a central processing unit (CPU) 2501 and a memory 2502 ; the memory 2502 is coupled to the CPU 2501 . The memory 2502 may store various data and information processing programs, which are executed under the control of the CPU 2501 to receive various information from IAB nodes and send various information to IAB nodes.

[0272] For example, the processor 2501 may be configured to execute a program to implement the method performed by the first host CU or the second host CU in the embodiment of the second aspect.

[0273] Furthermore, as shown in FIG25 , the IAB host node 2500 may further include a transceiver 2503 and an antenna 2504, among others. The functions of these components are similar to those in the prior art and are not further described here. It is worth noting that the IAB host node 2500 does not necessarily include all of the components shown in FIG25 ; furthermore, the IAB host node 2500 may also include components not shown in FIG25 , for which reference may be made to the prior art.

[0274] An embodiment of the present application also provides a computer-readable program, wherein when the program is executed in an NG-RAN node, the program causes the computer to execute in the NG-RAN node the method performed by the source NG-RAN node or the target NG-RAN in the embodiment of the first aspect or the method performed by the IAB node in the embodiment of the second aspect.

[0275] An embodiment of the present application also provides a storage medium storing a computer-readable program, wherein the computer-readable program enables a computer to execute in an NG-RAN node the method performed by the source NG-RAN node or the target NG-RAN in the embodiment of the first aspect or the method performed by the IAB node in the embodiment of the second aspect.

[0276] An embodiment of the present application further provides a computer-readable program, wherein when the program is executed in an IAB host node, the program enables a computer to execute in the IAB host node the method performed by the first host CU or the second host CU in the embodiment of the second aspect.

[0277] 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, in an IAB host node, the method performed by the first host CU or the second host CU in the embodiment of the second aspect.

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

[0279] 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).

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

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

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

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

[0284] 1. A message forwarding method, wherein the method comprises:

[0285] The source NG-RAN node and the target NG-RAN node forward the XnAP message via the core network using NGAP signaling.

[0286] 2. The method according to Supplement 1, wherein:

[0287] The source NG-RAN node is a host CU of an IAB node, and the host CU is an F1 termination host CU or a non-F1 termination host CU.

[0288] 3. The method according to Supplement 1, wherein:

[0289] There is no Xn interface between the source NG-RAN node and the target NG-RAN node.

[0290] 4. The method according to Note 2, wherein the method is used in the integration and / or migration process of IAB nodes.

[0291] 5. The method according to Supplementary Note 1, wherein the method comprises:

[0292] The source NG-RAN node sends a first message to the AMF, where the first message includes a first XnAP message;

[0293] The source NG-RAN node receives a second message from the AMF, where the second message includes a second XnAP message if the first XnAP message is forwarded successfully.

[0294] 6. The method according to Supplementary Note 5, wherein:

[0295] The source NG-RAN node starts a first timer when sending the first message, and when the first timer times out, the source NG-RAN node considers that forwarding of the first XnAP message has failed;

[0296] When receiving the second message from the AMF, the source NG-RAN node stops the first timer.

[0297] 7. The method according to Supplementary Note 6, wherein:

[0298] When forwarding of the first XnAP message fails, the source NG-RAN node sends a cancel command to the AMF.

[0299] 8. The method according to any one of Notes 5 to 7, wherein:

[0300] The first message further includes identification information, where the identification information indicates the target NG-RAN node.

[0301] 9. The method according to Supplementary Note 8, wherein:

[0302] The identification information is a global RAN node identifier and a selected tracking area identifier.

[0303] 10. The method according to any one of Notes 4 to 8, wherein:

[0304] The first message includes a first container, and the first container includes the first XnAP message transparently transmitted from the source IAB-donor to the target IAB-donor through the core network.

[0305] 11. The method according to Supplement 10, wherein:

[0306] The format of the first container is an octet string, and the first XnAP message is an IAB-related Xn message initiated by the source IAB-donor.

[0307] 12. The method according to Note 11, wherein the Xn message includes at least one of the following:

[0308] IAB TRANSPORT MIGRATION MANAGEMENT REQUEST,

[0309] IAB TRANSPORT MIGRATION MODIFICATION REQUEST,

[0310] IAB RESOURCE COORDINATION REQUEST.

[0311] 13. The method according to any one of Notes 5 to 12, wherein:

[0312] When the AMF receives a confirmation message replied by the target NG-RAN node, the second message is confirmation information that the first XnAP message is successfully forwarded;

[0313] When the AMF does not receive a reply from the target NG-RAN node or receives a failure message from the target NG-RAN node, the second message is confirmation information that the first XnAP message failed to be forwarded.

[0314] 14. The method according to any one of Notes 5 to 13, wherein:

[0315] The second message includes a second container, and the second container includes the second XnAP message transparently transmitted by the target IAB-donor to the source IAB-donor through the core network.

[0316] 15. The method according to Supplement 14, wherein:

[0317] The format of the second container is an octet string, and the second XnAP message is an IAB-related Xn message replied by the target IAB-donor.

[0318] 16. The method according to Note 15, wherein the Xn message includes at least one of the following:

[0319] IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE,

[0320] IAB TRANSPORT MIGRATION MODIFICATION RESPONSE,

[0321] IAB RESOURCE COORDINATION RESPONSE.

[0322] 17. The method according to any one of Notes 8 to 16, wherein the method further comprises:

[0323] The AMF determines the target NG-RAN node according to the identification information, and sends a third message to the target NG-RAN node, where the third message includes the first XnAP information;

[0324] The AMF receives a fourth message from the target NG-RAN node, where the fourth message includes a second XnAP message.

[0325] 18. The method according to Supplement 17, wherein:

[0326] The third message includes a first container, where the first container includes the first XnAP message transparently transmitted from the source IAB-donor to the target IAB-donor through the core network;

[0327] The target NG-RAN node generates the second XnAP message by decoding the content of the first container.

[0328] 19. The method according to Supplement 18, wherein:

[0329] The fourth message includes a second container, where the second container includes the second XnAP message transparently transmitted by the target IAB-donor to the source IAB-donor through the core network.

[0330] 20. The method according to Supplement 19, wherein:

[0331] The format of the second container is an octet string, and the second XnAP message is an IAB-related Xn message replied by the target IAB-donor.

[0332] 21. The method according to Note 20, wherein the Xn message includes at least one of the following:

[0333] IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE,

[0334] IAB TRANSPORT MIGRATION MODIFICATION RESPONSE,

[0335] IAB RESOURCE COORDINATION RESPONSE.

[0336] 22. A message forwarding method, wherein the method comprises:

[0337] The target NG-RAN node and the source NG-RAN node forward the XnAP message via the core network using NGAP signaling.

[0338] 23. The method according to Note 22, wherein:

[0339] The source NG-RAN node is a host CU of an IAB node, and the host CU is an F1 termination host CU or a non-F1 termination host CU.

[0340] 24. The method according to Note 22, wherein:

[0341] There is no Xn interface between the source NG-RAN node and the target NG-RAN node.

[0342] 25. The method according to Note 23, wherein the method is used in the integration and / or migration process of IAB nodes.

[0343] 26. The method according to any one of Notes 22 to 25, further comprising:

[0344] The target NG-RAN node receives a third message sent by the AMF, where the third message includes the first XnAP information;

[0345] The target NG-RAN node sends a fourth message to the AMF, where the fourth message includes a second XnAP message.

[0346] 27. The method according to Supplementary Note 26, wherein:

[0347] The third message includes a first container, where the first container includes the first XnAP message transparently transmitted from the source IAB-donor to the target IAB-donor through the core network;

[0348] The target NG-RAN node generates the second XnAP message by decoding the content of the first container.

[0349] 28. The method according to Supplementary Note 27, wherein:

[0350] The fourth message includes a second container, where the second container includes the second XnAP message transparently transmitted by the target IAB-donor to the source IAB-donor through the core network.

[0351] 29. The method according to Supplementary Note 28, wherein:

[0352] The format of the second container is an octet string, and the second XnAP message is an IAB-related Xn message replied by the target IAB-donor.

[0353] 30. The method according to Supplementary Note 29, wherein the Xn message includes at least one of the following:

[0354] IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE,

[0355] IAB TRANSPORT MIGRATION MODIFICATION RESPONSE,

[0356] IAB RESOURCE COORDINATION RESPONSE.

[0357] 31. A message forwarding method, wherein the method comprises:

[0358] The AMF forwards the XnAP message between the source NG-RAN node and the target NG-RAN node through NGAP signaling.

[0359] 32. The method according to Note 31, wherein:

[0360] The source NG-RAN node is a host CU of an IAB node, and the host CU is an F1 termination host CU or a non-F1 termination host CU.

[0361] 33. The method according to Note 31, wherein:

[0362] There is no Xn interface between the source NG-RAN node and the target NG-RAN node.

[0363] 34. The method according to Note 32, wherein the method is used in the integration and / or migration process of IAB nodes.

[0364] 35. The method according to Supplement 31, wherein the method comprises:

[0365] The AMF receives a first message sent by the source NG-RAN node, where the first message includes a first XnAP message;

[0366] The AMF sends a second message to the source NG-RAN node, where the second message includes a second XnAP message if the first XnAP message is forwarded successfully.

[0367] 36. The method according to Note 35, wherein:

[0368] The first message further includes identification information, where the identification information indicates the target NG-RAN node.

[0369] 37. The method according to Supplement 36, wherein:

[0370] The identification information is a global RAN node identifier and a selected tracking area identifier.

[0371] 38. The method according to any one of Notes 35 to 37, wherein:

[0372] The first message includes a first container, and the first container includes the first XnAP message transparently transmitted from the source IAB-donor to the target IAB-donor through the core network.

[0373] 39. The method according to Supplement 38, wherein:

[0374] The format of the first container is an octet string, and the first XnAP message is an IAB-related Xn message initiated by the source IAB-donor.

[0375] 40. The method according to Supplementary Note 39, wherein the Xn message includes at least one of the following:

[0376] IAB TRANSPORT MIGRATION MANAGEMENT REQUEST,

[0377] IAB TRANSPORT MIGRATION MODIFICATION REQUEST,

[0378] IAB RESOURCE COORDINATION REQUEST.

[0379] 41. The method according to any one of Notes 35 to 40, wherein:

[0380] When the AMF receives a confirmation message replied by the target NG-RAN node, the second message is confirmation information that the first XnAP message is successfully forwarded;

[0381] When the AMF does not receive a reply from the target NG-RAN node or receives a failure message from the target NG-RAN node, the second message is confirmation information that the first XnAP message failed to be forwarded.

[0382] 42. The method according to any one of Notes 35 to 41, wherein:

[0383] The second message includes a second container, and the second container includes the second XnAP message transparently transmitted by the target IAB-donor to the source IAB-donor through the core network.

[0384] 43. The method according to Note 42, wherein:

[0385] The format of the second container is an octet string, and the second XnAP message is an IAB-related Xn message replied by the target IAB-donor.

[0386] 44. The method according to Note 43, wherein the Xn message includes at least one of the following:

[0387] IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE,

[0388] IAB TRANSPORT MIGRATION MODIFICATION RESPONSE,

[0389] IAB RESOURCE COORDINATION RESPONSE.

[0390] 45. The method according to any one of Notes 36 to 44, wherein the method further comprises:

[0391] The AMF determines the target NG-RAN node according to the identification information, and sends a third message to the target NG-RAN node, where the third message includes the first XnAP information;

[0392] The AMF receives a fourth message from the target NG-RAN node, where the fourth message includes a second XnAP message.

[0393] 46. ​​The method according to Note 45, wherein:

[0394] The third message includes a first container, where the first container includes the first XnAP message transparently transmitted from the source IAB-donor to the target IAB-donor through the core network;

[0395] The target NG-RAN node generates the second XnAP message by decoding the content of the first container.

[0396] 47. The method according to Note 46, wherein:

[0397] The fourth message includes a second container, where the second container includes the second XnAP message transparently transmitted by the target IAB-donor to the source IAB-donor through the core network.

[0398] 48. The method according to Note 47, wherein:

[0399] The format of the second container is an octet string, and the second XnAP message is an IAB-related Xn message replied by the target IAB-donor.

[0400] 49. The method according to Supplement 48, wherein the Xn message includes at least one of the following:

[0401] IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE,

[0402] IAB TRANSPORT MIGRATION MODIFICATION RESPONSE,

[0403] IAB RESOURCE COORDINATION RESPONSE.

[0404] 50. A message forwarding method, wherein the method comprises:

[0405] The IAB node receives a fifth message from the first host CU, where the fifth message includes the first XnAP message;

[0406] The IAB node sends a sixth message to the second host CU, where the sixth message includes the first XnAP message.

[0407] 51. The method according to Note 50, wherein the method further comprises:

[0408] The IAB node receives a seventh message from the second host CU, where the seventh message includes a second XnAP message;

[0409] The IAB node sends an eighth message to the first host CU, where the eighth message includes the second XnAP message.

[0410] 52. The method according to Note 50, wherein:

[0411] There is no Xn interface between the first host CU and the second host CU.

[0412] 53. The method according to Note 50, wherein the method is used in the integration and / or migration process of IAB nodes.

[0413] 54. The method according to Note 50, wherein:

[0414] The fifth message is an RRC message, the sixth message is an F1AP message, and the fifth message and the sixth message each include a first container;

[0415] The first container includes the first XnAP message transparently transmitted by the first host CU to the second host CU through the IAB node.

[0416] 55. The method according to Note 50, wherein:

[0417] The fifth message is an F1AP message, the sixth message is an RRC message, and the fifth message and the sixth message each include a first container;

[0418] The first container includes the first XnAP message transparently transmitted by the first host CU to the second host CU through the IAB node.

[0419] 56. The method according to Note 54 or 55, wherein:

[0420] The format of the first container is an octal string, and the first XnAP message is an IAB-related Xn message initiated by the first host CU.

[0421] 57. The method according to Note 56, wherein the Xn message includes at least one of the following:

[0422] IAB TRANSPORT MIGRATION MANAGEMENT REQUEST,

[0423] IAB TRANSPORT MIGRATION MODIFICATION REQUEST,

[0424] IAB RESOURCE COORDINATION REQUEST.

[0425] 58. The method according to Note 51, wherein:

[0426] The seventh message is an F1AP message, the eighth message is an RRC message, and the seventh message and the eighth message each include a second container;

[0427] The second container includes the second XnAP message transparently transmitted by the second host CU to the first host CU through the IAB node.

[0428] 59. The method according to Note 51, wherein:

[0429] The seventh message is an RRC message, the eighth message is an F1AP message, and the seventh message and the eighth message each include a second container;

[0430] The second container includes the second XnAP message transparently transmitted by the second host CU to the first host CU through the IAB node.

[0431] 60. The method according to Note 58 or 59, wherein:

[0432] The format of the second container is an octal string, and the second XnAP message is an IAB-related Xn message replied by the second host CU.

[0433] 61. The method according to note 60, wherein the Xn message includes at least one of the following:

[0434] IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE,

[0435] IAB TRANSPORT MIGRATION MODIFICATION RESPONSE,

[0436] IAB RESOURCE COORDINATION RESPONSE.

[0437] 62. A message forwarding method, wherein the method comprises:

[0438] The first host CU sends a fifth message to the IAB node, where the fifth message includes the first XnAP message; so that the IAB node sends a sixth message to the second host CU, where the sixth message includes the first XnAP message.

[0439] 63. The method according to Note 62, wherein:

[0440] The IAB node further receives a seventh message from the second host CU, wherein the seventh message includes a second XnAP message;

[0441] The method further comprises:

[0442] The first host CU receives an eighth message sent by the IAB node, where the eighth message includes the second XnAP message.

[0443] 64. A message forwarding method, wherein the method comprises:

[0444] The second host CU receives a sixth message sent by the IAB node, where the sixth message includes a first XnAP message. The first XnAP message comes from a fifth message received by the IAB node from the first host CU, where the fifth message includes the first XnAP message.

[0445] 65. The method according to Supplementary Note 64, wherein the method further comprises:

[0446] The second host CU sends a seventh message to the IAB node, where the seventh message includes a second XnAP message; so that the IAB node sends an eighth message to the first host CU, where the eighth message includes the second XnAP message.

[0447] 66. A node device comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the method as described in any one of Notes 1 to 30.

[0448] 67. An AMF entity device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the method as described in any one of Notes 31 to 49.

[0449] 68. An IAB node, comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the method as described in any one of Notes 50 to 61.

[0450] 69. An IAB host node, comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the method as described in any one of Notes 62 to 65.

[0451] 70. A communication system comprising the node device described in Note 66 and the AMF entity device described in Note 67, or comprising the IAB node described in Note 68 and the IAB host node described in Note 69.

Claims

1. A message forwarding device, configured at a source NG-RAN node, wherein: The device comprises: A processing unit, which forwards the XnAP message with the target NG-RAN node via the core network through NGAP signaling.

2. The device according to claim 1, wherein: The source NG-RAN node is a host CU of an IAB node, and the host CU is an F1 termination host CU or a non-F1 termination host CU.

3. The device according to claim 2, wherein: The device is used in the integration and / or migration process of the IAB node.

4. The device according to claim 1, wherein: The processing unit sends a first message to the AMF, where the first message includes a first XnAP message; The processing unit receives a second message from the AMF, where the second message includes a second XnAP message when the first XnAP message is forwarded successfully.

5. The device according to claim 4, wherein: The processing unit starts a first timer when sending the first message, and when the first timer times out, the processing unit considers that the forwarding of the first XnAP message fails; When receiving the second message from the AMF, the processing unit stops the first timer.

6. The device according to claim 4, wherein: The first message also includes identification information, where the identification information indicates the target NG-RAN node.

7. The device according to claim 4, wherein: The first message includes a first container, and the first container includes the first XnAP message transparently transmitted from the source IAB-donor to the target IAB-donor through the core network.

8. The device according to claim 7, wherein: The first XnAP message is an IAB-related Xn message initiated by the source IAB-donor, and includes at least one of the following: IAB TRANSPORT MIGRATION MANAGEMENT REQUEST, IAB TRANSPORT MIGRATION MODIFICATION REQUEST, IAB RESOURCE COORDINATION REQUEST.

9. The device according to claim 4, wherein: The second message includes a second container, and the second container includes the second XnAP message transparently transmitted by the target IAB-donor to the source IAB-donor through the core network.

10. The device according to claim 9, wherein: The second XnAP message is an IAB-related Xn message replied by the target IAB-donor, and includes at least one of the following: IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE, IAB TRANSPORT MIGRATION MODIFICATION RESPONSE, IAB RESOURCE COORDINATION RESPONSE.

11. The device according to claim 6, wherein: The AMF determines the target NG-RAN node according to the identification information, and sends a third message to the target NG-RAN node, where the third message includes the first XnAP information; The AMF receives a fourth message from the target NG-RAN node, wherein the fourth message includes a second XnAP message.

12. The device according to claim 11, wherein The third message includes a first container, wherein the first container includes the first XnAP message transparently transmitted from the source IAB-donor to the target IAB-donor through the core network; The target NG-RAN node generates the second XnAP message by decoding the content of the first container.

13. The device according to claim 12, wherein: The fourth message includes a second container, where the second container includes the second XnAP message transparently transmitted by the target IAB-donor to the source IAB-donor through the core network.

14. A message forwarding device, configured in an IAB node, wherein: The device comprises: A receiving unit, configured to receive a fifth message from the first host CU, wherein the fifth message includes the first XnAP message; A sending unit, which sends a sixth message to the second host CU, wherein the sixth message includes the first XnAP message.

15. The device according to claim 14, wherein: The device also includes: The receiving unit receives a seventh message from the second host CU, wherein the seventh message includes a second XnAP message; The sending unit sends an eighth message to the first host CU, wherein the eighth message includes the second XnAP message.

16. The device according to claim 14, wherein: The fifth message is an RRC message, the sixth message is an F1AP message, and the fifth message and the sixth message respectively include a first container; The first container includes the first XnAP message transparently transmitted by the first host CU to the second host CU through the IAB node.

17. The device according to claim 14, wherein: The fifth message is an F1AP message, the sixth message is an RRC message, and the fifth message and the sixth message respectively include a first container; The first container includes the first XnAP message transparently transmitted by the first host CU to the second host CU through the IAB node.

18. The device according to claim 17, wherein: The first XnAP message is an IAB-related Xn message initiated by the first host CU, and includes at least one of the following: IAB TRANSPORT MIGRATION MANAGEMENT REQUEST, IAB TRANSPORT MIGRATION MODIFICATION REQUEST, IAB RESOURCE COORDINATION REQUEST.

19. The device according to claim 15, wherein: The seventh message is an RRC message, the eighth message is an F1AP message, and the seventh message and the eighth message respectively include a second container; The second container includes the second XnAP message transparently transmitted by the second host CU to the first host CU through the IAB node.

20. The device according to claim 19, wherein The second XnAP message is an IAB-related Xn message replied by the second host CU, and includes at least one of the following: IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE, IAB TRANSPORT MIGRATION MODIFICATION RESPONSE, IAB RESOURCE COORDINATION RESPONSE.

Images