WO2025035233A1 - Appareil et procédé de transfert de messages - Google Patents

Appareil et procédé de transfert de messages Download PDF

Info

Publication number
WO2025035233A1
WO2025035233A1 PCT/CN2023/112433 CN2023112433W WO2025035233A1 WO 2025035233 A1 WO2025035233 A1 WO 2025035233A1 CN 2023112433 W CN2023112433 W CN 2023112433W WO 2025035233 A1 WO2025035233 A1 WO 2025035233A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
iab
xnap
donor
host
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2023/112433
Other languages
English (en)
Chinese (zh)
Inventor
易粟
李国荣
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Fujitsu Ltd
Original Assignee
Fujitsu Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Fujitsu Ltd filed Critical Fujitsu Ltd
Priority to PCT/CN2023/112433 priority Critical patent/WO2025035233A1/fr
Publication of WO2025035233A1 publication Critical patent/WO2025035233A1/fr
Anticipated expiration legal-status Critical
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H04W8/14—Mobility data transfer between corresponding nodes

Definitions

  • the present application relates to the field of communications.
  • IAB Integrated access and backhaul
  • NG-RAN next generation radio access network
  • 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.
  • DAG directed acyclic graph
  • the IAB-donor node is responsible for performing centralized resource management, topology management, and routing management in the IAB network topology.
  • the IAB node supports the functions of gNB, which is called IAB-DU (distributed unit), and can serve ordinary UE (user equipment) and IAB child nodes.
  • the IAB node also supports some functions of UE, which can be called IAB-MT (mobile termination).
  • IAB-MT can support functions such as UE physical layer, AS (access stratum), RRC (radio resource control) and NAS (non-access stratum), and can be connected to the IAB parent node.
  • the termination node on the network side is called IAB-donor, which provides network access for IAB-MT or UE through backhaul or access link.
  • IAB-donor is further divided into IAB-donor-CU (central unit) and IAB-donor-DU.
  • IAB-DU and IAB-donor-CU are connected through the F1 interface.
  • gNB and IAB-donor-CU are connected through the Xn interface.
  • IAB introduces the BAP (Backhaul Adaptation Protocol) sublayer.
  • the BAP sublayer is located above the RLC (radio link control) sublayer and below the IP (Internet Protocol) layer. It supports the selection of the destination node and path of the data packet, routing forwarding of the data packet, bearer mapping, flow control feedback, and notification of backhaul link failure.
  • RLC radio link control
  • IP Internet Protocol
  • the IAB node In a multi-hop scenario, in order to realize the relay forwarding of data packets, the IAB node needs to determine the destination node of the data packet, and then determine the next hop node corresponding to the destination node according to the routing table and send the data packet.
  • the IAB-donor-CU configures the IAB node to receive the data from the IAB through F1AP (F1 Application Protocol) signaling.
  • F1AP F1 Application Protocol
  • the IAB node determines the BAP routing identifier corresponding to different types of uplink IP packets initiated from the IAB node based on the routing identifier mapping information, and encapsulates the BAP subheader containing the BAP routing identifier information for these uplink IP packets.
  • the IAB-donor-CU (abbreviated as donor-CU, or CU, or gNB-CU) configures the mapping of different types of downlink data packets to BAP routing identifiers for the IAB-donor-DU through F1AP signaling.
  • the IAB-donor-DU determines the BAP routing identifier corresponding to the received downlink IP packet based on the routing identifier mapping information, and encapsulates the BAP subheader containing the BAP routing identifier information for these downlink IP packets.
  • 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 DESTINATION in the BAP header.
  • Each IAB node and IAB-donor-DU is configured with a BAP address.
  • the integration process of IAB nodes is also called the startup process, which refers to the process in which IAB-MT accesses the network and obtains IAB-related configuration information, and starts some DU functions to provide services for UE.
  • the startup process refers to the process in which IAB-MT accesses the network and obtains IAB-related configuration information, and starts some DU functions to provide services for UE.
  • the MT and/or DU of the IAB node can be migrated, that is, the terminal host of the MT and/or can be changed.
  • the migration process is called MT migration and DU migration respectively.
  • the inventors have found that when the IAB node is in an inter-CU topology scenario, signaling interaction between CUs is necessary.
  • the current signaling interaction between IAB-donor-CU is carried out through the Xn interface between IAB-donor-CU.
  • these signaling interactions cannot be carried out, and the inter-CU IAB topology cannot be supported, thereby affecting the mobility performance of the IAB node.
  • an embodiment of the present application provides a message forwarding method and device.
  • a message forwarding device which is configured in a source NG-RAN node, and the device includes:
  • a sending unit which sends a first XnAP message to a target NG-RAN node, wherein the first XnAP message is forwarded via a core network through NGAP signaling.
  • a message forwarding device which is configured in a target NG-RAN node, and the device includes:
  • a receiving unit which receives a first XnAP message from a source NG-RAN node, wherein the first XnAP message is forwarded via a core network through NGAP signaling.
  • a message forwarding device which is configured in an AMF (Access and Mobility Management Function) entity, and the device includes:
  • a first receiving unit configured to receive a first message sent by a source NG-RAN node, wherein the first message includes a first XnAP message;
  • a first sending unit sends a second message to the source NG-RAN node, and the second message includes a second XnAP message when the first XnAP message is forwarded successfully.
  • a message forwarding device configured in an IAB node in an IAB network, and the device includes:
  • 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.
  • a message forwarding device configured in an IAB host node in an IAB network, and the device includes:
  • a sending unit which sends 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;
  • 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.
  • One of the beneficial effects of the embodiment of the present application is that: according to the embodiment of the present application, the signaling interaction problem between IAB-donors of the IAB node without the Xn interface is solved, thereby supporting the inter-CU integration of the IAB node and the IAB migration. In addition, the embodiment of the present application also solves the signaling interaction problem between general RAN nodes without the Xn interface, thereby supporting information interaction between RAN nodes.
  • FIG1 is a schematic diagram of an example of an IAB network topology
  • FIG2 is a schematic diagram of an example of a topology scenario of IAB-MT migration
  • FIG3 is a schematic diagram of an example of a topology scenario of IAB-DU migration
  • FIG4 is a schematic diagram of a message forwarding method according to an embodiment of the first aspect of the present application.
  • FIG5 is a schematic diagram of the first process
  • FIG6 is a schematic diagram of the second process.
  • FIG. 7 is another schematic diagram of the message forwarding method of the embodiment of the first aspect of the present application.
  • FIG8 is another schematic diagram of the message forwarding method of the embodiment of the first aspect of the present application.
  • FIG9 is a schematic diagram of the NG-based IAB-MT migration process
  • FIG10 is a schematic diagram of an NG-based IAB-DU migration process
  • FIG11 is a schematic diagram of an NG-based IAB integration process
  • FIG. 12 is a schematic diagram of a message forwarding method according to an embodiment of the second aspect of the present application.
  • FIG13 is a schematic diagram of information interaction according to a method according to an embodiment of the present application.
  • FIG14 is a schematic diagram of XnAP message forwarding based on RRC/F1AP
  • FIG15 is a schematic diagram of an example of IAB integration without an Xn interface
  • 16 is another schematic diagram of the message forwarding method of the embodiment of the second aspect of the present application.
  • 17 is another schematic diagram of the message forwarding method of the embodiment of the second aspect of the present application.
  • FIG18 is a schematic diagram of a message forwarding device according to an embodiment of the present application.
  • FIG20 is another schematic diagram of a message forwarding device according to an embodiment of the present application.
  • FIG21 is another schematic diagram of a message forwarding device according to an embodiment of the present application.
  • FIG22 is another schematic diagram of a message forwarding device according to an embodiment of the present application.
  • FIG23 is another schematic diagram of a message forwarding device according to an embodiment of the present application.
  • FIG24 is a schematic diagram of an NG-RAN node according to an embodiment of the present application.
  • FIG. 25 is a schematic diagram of an IAB host node according to an embodiment of the present application.
  • the terms “first”, “second”, etc. are used to distinguish different elements in terms of title, but do not indicate the spatial arrangement or temporal order of these elements, etc., 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.
  • the term “communication network” or “wireless communication network” may refer to any of the following: Networks based on communication standards, such as Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), etc.
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • WCDMA Wideband Code Division Multiple Access
  • HSPA High-Speed Packet Access
  • communication between devices in the communication system may be carried out according to communication protocols of any stage, such as 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 communication protocols currently known or to be developed in the future.
  • 1G generation
  • 2G 2.5G
  • 2.75G 3G
  • 4G 4G
  • 4.5G and future 5G
  • NR New Radio
  • the term "network device” refers to, for example, a device in a communication system that connects a terminal device to a communication network and provides services for the terminal device.
  • the network device may include, but is 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.
  • Base stations may include but are not limited to: Node B (NodeB or NB), evolved Node B (eNodeB or eNB) and 5G base station (gNB), RAN node, IAB-donor, etc., and may also include remote radio heads (RRH, Remote Radio Head), remote radio units (RRU, Remote Radio Unit), relays or low-power nodes (such as femto, pico, etc.).
  • RRH Remote Radio Head
  • RRU Remote Radio Unit
  • relays or low-power nodes such as femto, pico, etc.
  • base station may include some or all of their functions, and each base station may provide communication coverage for a specific geographical 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.
  • the term "user equipment” 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).
  • the terminal equipment may be fixed or mobile, and may also be referred to as a mobile station (MS), a terminal, a user, a subscriber station (SS), an access terminal (AT), a station, and the like.
  • Terminal devices may include, but are not limited to, the following devices: cellular phones, personal digital assistants (PDA), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptop computers, cordless phones, smart phones, smart watches, digital cameras, and IAB-MT, etc.
  • PDA personal digital assistants
  • wireless modems wireless communication devices
  • handheld devices machine-type communication devices
  • machine-type communication devices laptop computers
  • cordless phones smart phones
  • smart watches smart watches
  • digital cameras digital cameras
  • IAB-MT IAB-MT
  • terminal devices can also perform The monitored or measured machines or devices may include, but are not limited to: machine type communication (MTC) terminals, vehicle-mounted communication terminals, device to device (D2D) terminals, machine to machine (M2M) terminals, and the like.
  • MTC machine type communication
  • D2D device to device
  • M2M machine to machine
  • 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.
  • the control plane network elements also include a session management function (SMF), a positioning management function (LMF), etc.
  • SMF session management function
  • LMF positioning management function
  • the embodiment of the present application is not limited to which network element of the core network is used for forwarding, and AMF is used as an example for illustration.
  • the NG-RAN node is connected to the 5GC via the NG interface.
  • the NG-RAN node in the embodiment of the present application can be replaced by any network device, and the Xn interface can be replaced by an interface between any network devices, such as an X2 interface and a network device interface in a future communication protocol.
  • XnAP can be replaced by an interface application protocol between corresponding network devices.
  • the NG interface can be replaced by an interface from any network device to the core network.
  • NGAP can be replaced by an interface application protocol from a corresponding network device to the core network.
  • FIG. 1 is a schematic diagram of an example of an IAB network topology structure, showing a situation where an MT and a DU of an IAB are terminated to different donor-CUs.
  • the inventors have discovered that the mobility of a mobile IAB (mIAB) or a 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.
  • mIAB mobile IAB
  • a 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.
  • the F1-terminating node refers to the donor-CU that terminates the F1 interface of the IAB node, such as donor-CU2 (the F1 of IAB-DU1 in Figure 1 is terminated to donor-CU2).
  • the F1-terminating donor-CU can also be called the donor-CU of the IAB-DU because the IAB-DU is configured by this CU.
  • a non-F1-terminating node refers to a CU with host function that is not terminated by the F1 interface of an IAB node, such as donor-CU1. Because a non-F1-terminating node has an RRC connection with an IAB-MT, a non-F1-terminating node can also be called a host node of an IAB-MT, and a non-F1-terminating host CU can also be called a host CU of an IAB-MT, or an RRC-terminating donor-CU of an IAB node.
  • IAB-MT1 is connected to the parent node IAB node 2, and then connected to donor-DU1 and donor-CU1.
  • IAB-DU1 and donor-CU2 are connected via F1, but the path of this F1 connection is through IAB node 2, donor-DU1 and finally to CU2.
  • the IAB node 1 is the border IAB node.
  • the inventors have found that when the IAB node 1 is in the inter-CU topology scenario shown in FIG1 , signaling interaction between CUs is necessary.
  • the signaling interaction between IAB-donor-CU is performed through the interface Xn between IAB-donor-CU. If there is no Xn interface between IAB-donor-CU, these signaling interactions cannot be performed, and the inter-CU IAB topology cannot be supported, thereby affecting the mobility performance of the IAB node.
  • the IAB node to which the UE is connected can be moved.
  • the MT and DU of the IAB node can be integrated into different donor-CUs, and the IAB node can perform MT migration and DU migration.
  • the present application is not limited to this, and the embodiment of the present application is also applicable to other non-IAB scenarios.
  • Figure 1 can be regarded as an integration scenario in which the MT and DU of the IAB node are connected to different donor-CUs.
  • donor-CU1 is an RRC-terminated donor-CU, referred to as CU1;
  • donor-CU2 is an F1-terminated donor-CU, referred to as CU2.
  • CU1 needs to perform signaling interaction with CU2 to perform IAB related configurations.
  • FIG2 is a schematic diagram of an example of a topology scenario for MT migration.
  • donor-CU1 is the source RRC-terminated donor-CU
  • donor-CU2 is the target RRC-terminated donor-CU
  • 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 in order to modify and release the traffic offloading association between them (that is, the binding relationship of traffic transmission migration).
  • the F1-terminated donor-CU and donor-CU2 also need to perform signaling interaction in order to establish and modify the traffic offloading association between them and/or IAB resource coordination.
  • FIG. 3 is a schematic diagram of an example of a topology scenario for DU migration.
  • donor-CU1 is a source F1-terminated donor-CU
  • donor-CU3 is a target F1-terminated donor-CU
  • donor-CU2 is an RRC-terminated donor-CU, which remain unchanged during the DU migration process.
  • IAB-DU3 (DU3a and DU3b in Figure 3 are 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 in order to modify and release the traffic offloading association between them.
  • Donor-CU3 and donor-CU2 also need to perform signaling interaction in order to establish and modify the traffic offloading association between them and/or IAB resource coordination.
  • Donor-CU1 transfers IAB node 3 to donor-CU3.
  • the served UE switches to donor-CU3.
  • An embodiment of the present application provides a message forwarding method.
  • FIG 4 is a schematic diagram of the message forwarding method of an embodiment of the present application, which is explained from the side of the 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.
  • the F1-terminated donor-CU in the scenario shown in Figure 2 is the target NG-RAN node, and vice versa; or, the source NG-RAN node is, for example, donor-CU 1 or donor-CU 3 in the scenario shown in Figure 3.
  • the donor-CU 2 in the scenario shown in Figure 3 is the target NG-RAN node, and vice versa.
  • the method includes:
  • the source NG-RAN node and the target NG-RAN node forward the XnAP message via the core network through NGAP signaling.
  • the source CU and the target CU can forward the XnAP message that originally needs to be transmitted through the Xn interface through the NGAP (NG Application Protocol) signaling of the NG interface.
  • NGAP NG Application Protocol
  • the above takes the IAB scenario as an example.
  • the embodiment of the present application can also be extended to other scenarios.
  • the source base station and the target base station can communicate through the NGAP of the NG interface.
  • the signaling is forwarded through the core network to the XnAP message that originally needs to be transmitted through the Xn interface.
  • the following only takes the IAB scenario as an example.
  • source and target refer to the source and target that need to exchange information.
  • 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.
  • the source NG-RAN node and the target NG-RAN node forward the XnAP message via the core network through NGAP signaling.
  • 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.
  • 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.
  • 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.
  • a new procedure may be used for forwarding the XnAP message. For example, if it is not a signaling interaction related to UE switching, 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.
  • NGAP NG Application Protocol
  • the first process is for the source NG-RAN node to forward the message (called the first XnAP message) that originally needs to be sent on the Xn interface to the target NG-RAN node through 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
  • the initiator is the source NG-RAN node and the recipient is the target NG-RAN node.
  • the source NG-RAN node sends a first message to the AMF, wherein the first message includes a first XnAP message; the source NG-RAN node receives a second message from the AMF, wherein the second message includes a second XnAP message when the first XnAP message is forwarded successfully.
  • the source NG-RAN node initiates the first process by sending a first message (NGAP message) to the serving AMF.
  • NGAP message a first message
  • a first timer can be started. The function of the first timer is to determine whether to continue waiting for the reply from the AMF. Because the AMF needs to forward the message to the target NG-RAN node, receive the reply from the target NG-RAN, and then reply the 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.
  • the source NG-RAN node When the source NG-RAN node receives the second message from the AMF, the first timer can be stopped. In addition, when the source NG-RAN node considers that the forwarding of the first XnAP message has failed, it can also send a cancel command to the AMF to inform the AMF to cancel the forwarding of the first XnAP message.
  • the first message may also include an identification information, such as an identification of a global RAN node identification plus a selected tracking area identification, for indicating the target NG-RAN node.
  • the first message also includes information that the source NG-RAN node wants to send to the target NG-RAN node, that is, the aforementioned first XnAP message.
  • the above first XnAP message can be placed in an Xn container, such as a first container.
  • the first container as an IE, contains information (first XnAP message) transparently transmitted from the source IAB-donor to the target IAB-donor through 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.
  • the format of the first container is an octal string, which 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.
  • the first container is transparent to the core network.
  • 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 first container may be added by enhancing the above IE.
  • the first message may therefore include the Source to Target Transparent Container IE or the Source NG-RAN Node to Target NG-RAN Node Transparent Container IE.
  • 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 put the second container in the reply (including the information that the target NG-RAN node wants to send to the source NG-RAN node, referred to as the second XnAP message) into the second message and send it to the source NG-RAN node. At this time, 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 from the target NG-RAN node, the second message may be a failure message.
  • the second container may contain information transparently transmitted from the target IAB-donor to the source IAB-donor through the core network, which is called the second XnAP message.
  • the format of the second container may also be an octal string, which contains the IAB-related Xn message replied by the target IAB-donor, that is, the above second XnAP message is the IAB-related Xn message replied by the target IAB-donor, for example: IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE, IAB TRANSPORT MIGRATION MODIFICATION RESPONSE, IAB RESOURCE COORDINATION RESPONSE, and so on.
  • the second process is for the AMF to forward to the target NG-RAN node the information originally required to be sent on the Xn interface (that is, the above-mentioned first Xn message) received from the source NG-RAN node.
  • 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.
  • the AMF determines the target NG-RAN node according to the above identification information, and sends a third message to the target NG-RAN node, the third message including the above 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, indicating the information that the target NG-RAN node wants to send to the source NG-RAN node.
  • the AMF initiates the second process by sending a third message (NGAP message) to the target NG-RAN node.
  • the third message may include the first container received by the AMF from the first process.
  • the first container has been introduced above and is omitted here.
  • 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.
  • second XnAP message a reply Xn message
  • the format of the second container is, for example, an octal 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.
  • IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE IAB TRANSPORT MIGRATION MODIFICATION RESPONSE
  • IAB RESOURCE COORDINATION RESPONSE etc.
  • 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, and the second Xn container is added by enhancing the above IE. 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.
  • 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, and the same contents as the previous embodiment are not repeated. As shown in FIG7 , the method includes:
  • the target NG-RAN node and the source NG-RAN node forward the XnAP message via the core network through NGAP signaling.
  • the target NG-RAN node receives a third message sent by the AMF, wherein the third message includes the aforementioned first XnAP information; the target NG-RAN node sends a fourth message to the AMF, wherein the fourth message includes the aforementioned second XnAP message.
  • the third message may include a first container, which includes the above-mentioned 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 above-mentioned second XnAP message by decoding the content of the first container.
  • the fourth 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.
  • the first XnAP information can be transparently transmitted through the first container; the second XnAP information can be transparently transmitted through the second container, which has been explained in detail above and will not be repeated here.
  • FIG8 is another schematic diagram of the message forwarding method of an embodiment of the present application, which is described from the perspective of AMF, and the same contents as the previous embodiment are not repeated. As shown in FIG8, the method includes:
  • AMF forwards the XnAP message between the source NG-RAN node and the target NG-RAN node via NGAP signaling.
  • the AMF receives a first message sent by a source NG-RAN node, wherein the first message includes a first XnAP message; the AMF sends a second message to the source NG-RAN node, wherein the second message includes a second XnAP message when the first XnAP message is forwarded successfully.
  • the second message 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 confirmation message from the target When the NG-RAN node replies 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.
  • 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, wherein the third message includes the aforementioned first XnAP information; the AMF receives a fourth message from the target NG-RAN node, wherein the fourth message includes the aforementioned second XnAP message.
  • the first XnAP information can be transparently transmitted through the first container; the second XnAP information can be transparently transmitted through the second container, which has been specifically described above and will not be repeated here.
  • 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, in Figure 9, only the process of forwarding XnAP messages based on the NG interface is shown, and other migration-related signaling processes can occur at any step.
  • the first to fourth steps are to 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 process and the second process.
  • the IAB Transport Migration Modification process can realize the modification and release of IAB transport migration.
  • the first step is that IAB-donor CU1 sends a first message to AMF, the first message includes a first container, the base station identifier of IAB-donor CU3, and may also include the UE XnAP ID (Target NG-RAN node UE XnAP ID) of the IAB node in IAB-donor CU3.
  • the second step is that AMF sends a third message to IAB-donor CU3, the third message includes the first container, and may also include the UE XnAP ID of the IAB node in IAB-donor CU3.
  • the first container includes the Xn IAB TRANSPORT MIGRATION MODIFICATION REQUEST message.
  • the third step is that IAB-donor CU3 replies to AMF with a fourth message, the fourth message includes the second container.
  • the second container includes the Xn IAB TRANSPORT MIGRATION MODIFICATION RESPONSE message.
  • the fourth step is that AMF sends a second message to IAB-donor CU1, the second message may include the second container.
  • the second message type or name may be confirmation information/failure information.
  • steps 5 to 8 are similar to steps 1 to 4.
  • the management function of IAB transport migration can be implemented.
  • FIG. 10 is a schematic diagram of a DU migration process based on NG, showing message forwarding based on NG interface
  • FIG10 only the process of forwarding Xn messages based on the NG interface is shown, and other migration-related signaling processes can occur at any step.
  • each step can be performed similarly to the signaling process of the diagram and the aforementioned MT migration.
  • the main difference is that the donor-CU and MT migration represented by IAB-donor CU1, IAB-donor CU, and IAB-donor CU3 in FIG10 are different.
  • the first step to the fourth step are the IAB transmission migration management process from the target F1-terminating donor to the RRC-terminating donor based on NGAP.
  • FIG. 11 is a schematic diagram of an NG-based IAB integration process, illustrating an IAB integration process based on NG interface message forwarding.
  • Steps 6 to 9 are to implement the Xn IAB process between F1-terminating IAB-donor (source NG-RAN node) and RRC-terminating IAB donor (target NG-RAN node) through the first and second NGAP processes when there is no Xn interface between IAB-donor CU1 and IAB-donor CU2, such as the IAB transport migration management process.
  • the signaling interaction problem between general RAN nodes without Xn interface is solved, thereby supporting information interaction between RAN nodes.
  • the problem of integrating MT and DU of mobile IAB nodes into different IAB-donors, as well as MT migration and DU migration problems is solved in the scenario where there is no Xn interface between IAB-donors, thereby supporting the configuration flexibility of IAB nodes, supporting the mobility of IAB nodes in a wide area, and being able to provide high-quality services for UEs served by mobile IAB nodes.
  • An embodiment of the present application provides a message forwarding method, which is applied to an IAB network.
  • FIG12 is a schematic diagram of a message forwarding method according to an embodiment of the present application, which is described from the side of an IAB node in an IAB network.
  • FIG13 is a schematic diagram of information interaction according to a method according to an embodiment of the present application. Referring to FIGS. 12 and 13 , the method includes:
  • the IAB node receives a fifth message from the first host CU, wherein the fifth message includes the first XnAP messages;
  • the IAB node sends a sixth message to the second host CU, where the sixth message includes the first XnAP message.
  • the XnAP message between the first host CU and the second host CU is forwarded through the IAB node, which solves the problem of integrating the MT and DU of the mobile IAB node into different IAB-donors in the scenario where there is no Xn interface between the IAB-donors, as well as the MT migration and DU migration problems, thereby supporting the configuration flexibility of the IAB node, supporting the movement of the IAB node in a wide area, and being able to provide high-quality services for the UE served by the mobile IAB node.
  • 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.
  • 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, and the first container includes the above-mentioned first XnAP message transparently transmitted from the first host CU to the second host CU through the IAB node.
  • the fifth message is an RRC message and the sixth message is an F1AP message.
  • the fifth message is an F1AP message and the sixth message is an RRC message.
  • RRC and F1AP are enhanced to include XnAP messages, and these IAB-related coordination messages are transparently forwarded through the IAB node.
  • Figure 14 is a schematic diagram of XnAP message forwarding based on RRC/F1AP.
  • the RRC layer is enhanced to put the first XnAP message as the first container into the RRC message for transmission; between F1-terminating donor-CU (Donor-CU2) and IAB-DU, F1AP is enhanced to put the first XnAP message as the first container into the F1AP message for transmission.
  • the IAB node 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 when Donor-CU1 is the second host CU, the IAB node may 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.
  • 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.
  • 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 from the second host CU to the first host CU through the IAB node.
  • 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.
  • the enhancement of the RRC layer is, for example, to add information of the first container and the second container in the downlink RRC message (the fifth message or the seventh message), such as the RRCReconfiguration message or the DLInformationTransfer, and the uplink RRC message (the sixth message or the eighth message), such as the ULInformationTransfer, IAB0therInformation.
  • the containers can be defined as new IEs in the above messages.
  • 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.
  • the enhancement of F1AP is, for example, that the F1AP message (sixth message or eighth message) in the direction from gNB-DU to gNB-CU includes information of the first container and the second container; and/or, the F1AP message (fifth message or seventh message) in the direction from gNB-CU to gNB-DU includes information of the first container and the second container.
  • These containers can be defined in the above messages as new IEs.
  • a new F1AP process can be defined to include a newly defined fifth message, sixth message, seventh message, and eighth message. Because the above F1AP message already includes IEs representing the first container and the second container, the messages can be merged in the F1AP process.
  • the F1AP process may only require two messages, such as the fifth message and the eighth message.
  • the first container or the second container is used in the message according to the requirements.
  • 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.
  • the fifth message may be CU-DU RADIO INFORMATION TRANSFER, etc.
  • the eighth message may be DU-CU RADIO INFORMATION TRANSFER, etc.
  • FIG15 is a schematic diagram of an example of IAB integration without an Xn interface, showing the case of IAB integration using RRC and F1AP for Xn message forwarding. As shown in FIG15, steps 6 to 9 are the Xn message forwarding process between two donor-CUs. Similar steps can be used in other IAB migration scenarios.
  • FIG16 is another schematic diagram of the message forwarding method of an embodiment of the present application, which is described from the side of the first host CU in the IAB network, and the same contents as the previous embodiment are not repeated.
  • the method includes:
  • the first host CU 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.
  • the IAB node further receives a seventh message from the second host CU, the seventh message including the second XnAP message; then the first host CU may also receive an eighth message sent by the IAB node, the eighth message including the second XnAP message.
  • FIG17 is another schematic diagram of the message forwarding method of an embodiment of the present application, which is described from the side of the second host CU in the IAB network, and the same contents as the previous embodiment are not repeated.
  • the method includes:
  • the second host CU receives a sixth message sent by the IAB node, wherein the sixth message includes a first XnAP message, wherein the first XnAP message comes from a fifth message received by the IAB node from the first host CU, and the fifth message includes the first XnAP message.
  • the second host CU may further send a seventh message to the IAB node, wherein the seventh message includes the second XnAP message; so that the IAB node sends an eighth message to the first host CU, wherein the eighth message includes the second XnAP message. Containing the second XnAP message.
  • the signaling interaction problem between general RAN nodes without Xn interface is solved, thereby supporting information interaction between RAN nodes.
  • the problem of integrating MT and DU of mobile IAB nodes into different IAB-donors, as well as MT migration and DU migration problems is solved in the scenario where there is no Xn interface between IAB-donors, thereby supporting the configuration flexibility of IAB nodes, supporting the mobility of IAB nodes in a wide area, and being able to provide high-quality services for UEs served by mobile IAB nodes.
  • An embodiment of the present application provides a message forwarding method.
  • FIG18 is a schematic diagram of a message forwarding device 1800 of an embodiment of the present application, which may be, for example, a source NG-RAN node, or one or more components or assemblies configured in the source NG-RAN node. Since the principle of solving the problem by the device is similar to that of the embodiment of the first aspect, the same contents will not be repeated.
  • the device 1800 includes:
  • the processing unit 1801 forwards the XnAP message with the target NG-RAN node via the core network through NGAP signaling.
  • the source NG-RAN node is a host CU of an IAB node
  • the host CU is an F1-terminated host CU or a non-F1-terminated host CU.
  • the apparatus 1800 is used for integration and/or migration process of an IAB node.
  • the processing unit 1801 sends a first message to the AMF, wherein the first message includes a first XnAP message; the processing unit 1801 receives a second message from the AMF, wherein the second message includes a second XnAP message when the first XnAP message is forwarded successfully.
  • 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 fails; when the second message from the AMF is received, the first timer is stopped.
  • the processing unit 1801 may send a Send a cancel command.
  • the first message may further include identification information, where the identification information indicates the target NG-RAN node.
  • the identification information is a global RAN node identifier and a selected tracking area identifier.
  • 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.
  • the format of the first container may be an octal string
  • the first XnAP message is an IAB-related Xn message initiated by the source IAB-donor.
  • the Xn message may include, for example, at least one of the following:
  • the second message 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.
  • 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.
  • the format of the second container may be an octal string
  • 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:
  • the AMF can 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.
  • the third message may include a first container, which includes the above-mentioned first XnAP message transparently transmitted from 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.
  • the fourth 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.
  • the format of the second container may be an octal string
  • the second XnAP message is an IAB-related Xn message replied by the target IAB-donor.
  • the Xn message may include, for example, at least one of the following:
  • FIG19 is another schematic diagram of a message forwarding device 1900 according to an embodiment of the present application.
  • the device may be, for example, a target NG-RAN node, or may be one or more components or assemblies configured in the target NG-RAN node. Since the principle of solving the problem by the device is similar to that of the embodiment of the first aspect, the same contents will not be repeated.
  • the device 1900 includes:
  • the processing unit 1901 forwards the XnAP message with the source NG-RAN node via the core network through NGAP signaling.
  • the source NG-RAN node is a host CU of an IAB node
  • the host CU is an F1-terminated host CU or a non-F1-terminated host CU.
  • the apparatus 1900 is used for integration and/or migration process of an IAB node.
  • the processing unit 1901 receives a third message sent by the AMF, wherein the third message includes the first XnAP information; the processing unit 1901 sends a fourth message to the AMF, wherein the fourth message includes the second XnAP message.
  • the third message may include a first container, which includes the above 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 above second XnAP message by decoding the content of the g5 first container.
  • the fourth 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.
  • the format of the second container may be an octal string
  • 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:
  • FIG. 20 is another schematic diagram of a message forwarding device 2000 according to an embodiment of the present application.
  • the device may be, for example, AMF may also be one or more components or assemblies configured in AMF. Since the principle of solving the problem by the device is similar to that of the embodiment of the first aspect, the same contents will not be repeated.
  • the device 2000 includes:
  • the processing unit 2001 forwards the XnAP message between the source NG-RAN node and the target NG-RAN node through NGAP signaling.
  • the source NG-RAN node is a host CU of an IAB node
  • the host CU is an F1-terminated host CU or a non-F1-terminated host CU.
  • the apparatus 2000 is used for integration and/or migration process of IAB nodes.
  • processing unit 2001 receives a first message sent by a source NG-RAN node, wherein the first message includes a first XnAP message; processing unit 2001 sends a second message to the source NG-RAN node, wherein the second message includes a second XnAP message when the first XnAP message is forwarded successfully.
  • the first message may further include identification information, where the identification information indicates the target NG-RAN node.
  • the identification information is, for example, a global RAN node identifier and a selected tracking area identifier.
  • 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.
  • the format of the first container may be an octal string
  • the above first XnAP message is an IAB-related Xn message initiated by the source IAB-donor.
  • the Xn message may include, for example, at least one of the following:
  • the second message when the processing unit 2001 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 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 second message is confirmation information that the first XnAP message fails to be forwarded.
  • 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.
  • the format of the second container may be an octal string
  • 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:
  • 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, and the third message includes the above-mentioned first XnAP information; the processing unit 2001 receives a fourth message from the target NG-RAN node, and the fourth message includes the above-mentioned second XnAP message.
  • the third message may include a first container, which includes the above-mentioned 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 above-mentioned second XnAP message by decoding the content of the first container.
  • the fourth 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.
  • the format of the second container may be an octal string
  • the second XnAP message is an IAB-related Xn message replied by the target IAB-donor.
  • the Xn message may include, for example, at least one of the following:
  • Fig. 21 is another schematic diagram of a message forwarding device 2100 of an embodiment of the present application, which may be, for example, an IAB node, or one or more components or assemblies configured in the IAB node. Since the principle of solving the problem by the device is similar to that of the embodiment of the second aspect, the same contents will not be repeated.
  • the device 2100 includes:
  • a receiving unit 2101 which receives a fifth message from a first host CU, wherein the fifth message includes a first XnAP message;
  • the sending unit 2102 sends a sixth message to the second host CU, wherein the sixth message includes the first XnAP message.
  • the receiving unit 2101 further receives a seventh message from the second host CU, wherein the seventh message includes a second XnAP message; the sending unit 2102 further sends an eighth message to the first host CU, wherein the eighth message includes the second XnAP message.
  • the apparatus 2100 may be used in an integration and/or migration process of an IAB node.
  • the fifth message is an RRC message
  • the sixth message is an F1AP message
  • the fifth message and the sixth message respectively contain a first container; the first container contains the above-mentioned first XnAP message transparently transmitted from the first host CU to the second host CU through the IAB node.
  • the fifth message is an F1AP message
  • the sixth message is an RRC message
  • the fifth message and the sixth message respectively contain a first container; the first container contains the above-mentioned first XnAP message transparently transmitted from the first host CU to the second host CU through the IAB node.
  • the format of the first container may be an octal string
  • 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:
  • the seventh message is an F1AP message
  • the eighth message is an RRC message
  • the seventh message and the eighth message respectively contain a second container; the second container contains a second XnAP message transparently transmitted from the second host CU to the first host CU through the IAB node.
  • the seventh message is an RRC message
  • the eighth message is an F1AP message
  • the seventh message and the eighth message respectively contain a second container; the second container contains the above-mentioned second XnAP message transparently transmitted from the second host CU to the first host CU through the IAB node.
  • the format of the second container may be an octal string
  • the above second XnAP message is an IAB-related Xn message replied by the second host CU.
  • the Xn message may include, for example, at least one of the following:
  • FIG. 22 is another schematic diagram of a message forwarding device 2200 of an embodiment of the present application, which may be, for example, a first host CU, or may be one or more components or assemblies configured in the first host CU. Since the principle of solving the problem by the device is similar to that of the embodiment of the second aspect, the same contents will not be repeated.
  • the device 2200 includes:
  • 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. 1. XnAP message.
  • the IAB node further receives a seventh message from the second host CU, wherein the seventh message includes a second XnAP message.
  • the apparatus 2200 further includes:
  • the receiving unit 2202 receives an eighth message sent by the IAB node, where the eighth message includes the second XnAP message.
  • FIG. 23 is another schematic diagram of a message forwarding device 2300 of an embodiment of the present application, which may be, for example, a second host CU, or one or more components or assemblies configured in the second host CU. Since the principle of solving the problem by the device is similar to that of the embodiment of the first aspect, the same contents will not be repeated.
  • the device 2300 includes:
  • the receiving unit 2301 receives a sixth message sent by the IAB node, wherein the sixth message includes a first XnAP message, wherein the first XnAP message comes from a fifth message received by the IAB node from a first host CU, and the fifth message includes the first XnAP message.
  • the apparatus 2300 further includes:
  • the sending unit 2401 sends a seventh message to the IAB node, wherein the seventh message includes the second XnAP message; so that the IAB node sends an eighth message to the first host CU, wherein the eighth message includes the second XnAP message.
  • the devices 1800, 1900, 2000, 2100, 2200, 2300 of the embodiments of the present application may also include other components or modules, and the specific contents of these components or modules may refer to the relevant technology.
  • FIG. 18 to FIG. 23 only exemplarily illustrate the connection relationship or signal direction between various components or modules, but it should be clear to those skilled in the art that various related technologies such as bus connection can be used.
  • the above-mentioned various components or modules can be implemented by hardware facilities such as processors, memories, transmitters, and receivers; the implementation of this application is not limited to this.
  • the signaling interaction problem between common RAN nodes without Xn interface is solved, thereby supporting information interaction between RAN nodes.
  • the embodiment of the present application provides a communication system, including a source NG-RAN node and a target NG-RAN second node, wherein the source NG-RAN node and the target NG-RAN node are configured to perform 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 contents thereof are incorporated herein and will not be repeated here.
  • the embodiment of the present application also provides an IAB communication system, including a first host node, a second host node and an IAB node, wherein the first host node, the second host node and the IAB node are configured to execute the method described in the embodiment of the second aspect.
  • the behaviors of the first host node, the second host node and the IAB node have been described in detail in the embodiment of the second aspect, and the contents thereof are incorporated herein and will not be repeated here.
  • 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 described in any one of the first to third aspects.
  • FIG24 is a schematic diagram of an NG-RAN node according to an embodiment of the present application.
  • the NG-RAN node 2400 may include a processor 2401 and a memory 2402; the memory 2402 stores data and programs and is coupled to the processor 2401. It is worth noting that the figure is exemplary; other types of structures may also be used to supplement or replace the structure to implement telecommunication functions or other functions.
  • 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.
  • 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 the above components are similar to those in the prior art and are not described in detail here. It is worth noting that the NG-RAN node 2400 does not necessarily include all the components shown in FIG24 , and the above components are not necessary; in addition, the NG-RAN node 2400 may also include components not shown in FIG24 , and reference may be made to the prior art.
  • An embodiment of the present application further provides an IAB host node, the IAB host node comprising a memory and a processor, the memory storing a computer program, the processor being configured to execute the computer program to implement the method as described in the embodiment of the fourth aspect.
  • FIG25 is a schematic diagram of an IAB host node according to an embodiment of the present application.
  • the 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; in addition, it may store information processing programs, and execute the programs under the control of the CPU 2501 to receive various information sent by the IAB node and send various information to the IAB node.
  • 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.
  • the IAB host node 2500 may further include: a transceiver 2503 and an antenna 2504, etc.; wherein the functions of the above components are similar to those of the prior art and are not described in detail here. It is worth noting that the IAB host node 2500 does not necessarily include all the components shown in FIG25 ; in addition, the IAB host node 2500 may also include components not shown in FIG25 , and reference may be made to the prior art.
  • 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 to execute the method performed by the IAB node in the embodiment of the second aspect.
  • 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 a source NG-RAN node or a target NG-RAN in an embodiment of the first aspect or to execute the method performed by an IAB node in an embodiment of the second aspect.
  • 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.
  • 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.
  • the above devices and methods of the present application can be implemented by hardware, or by hardware combined with software.
  • the present application relates to such a computer-readable program, which, when executed by a logic component, enables the logic component to implement the above-mentioned devices or components, 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.
  • the method/device described in conjunction with the embodiments of the present application may be directly embodied as hardware, a software module executed by a processor, or a combination of the two.
  • one or more of the functional block diagrams shown in the figure and/or one or more combinations of the functional block diagrams may correspond to various software modules of the computer program flow or to various hardware modules.
  • These software modules may correspond to various steps shown in the figure, respectively.
  • These hardware modules may, for example, be implemented using Field Programmable Gate Array (FPGA) implements these software modules by solidifying them.
  • FPGA Field Programmable Gate Array
  • the software module may be located in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, 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 a memory of a mobile terminal or in a memory card that can be inserted into the mobile terminal.
  • the software module may be stored in the MEGA-SIM card or the large-capacity flash memory device.
  • the functional blocks described in the drawings and/or one or more combinations of functional blocks it can be implemented as a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component or any appropriate combination thereof for performing the functions described in the present application.
  • DSP digital signal processor
  • ASIC application-specific integrated circuit
  • FPGA field programmable gate array
  • it can 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.
  • a message forwarding method wherein the method comprises:
  • the source NG-RAN node and the target NG-RAN node forward the XnAP message via the core network through NGAP signaling.
  • 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.
  • 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.
  • 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 the forwarding of the first XnAP message fails;
  • the source NG-RAN node When receiving the second message from the AMF, the source NG-RAN node stops the first timer.
  • the source NG-RAN node When the forwarding of the first XnAP message fails, the source NG-RAN node sends a cancellation command to the AMF.
  • the first message also includes identification information, where the identification information indicates the target NG-RAN node.
  • the identification information is a global RAN node identifier and a selected tracking area identifier.
  • 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.
  • 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.
  • the second message is confirmation information that the first XnAP message is successfully forwarded
  • the second message is confirmation information that the first XnAP message failed to be forwarded.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • a message forwarding method wherein the method comprises:
  • the target NG-RAN node and the source NG-RAN node forward the XnAP message via the core network through NGAP signaling.
  • 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.
  • the target NG-RAN node receives a third message sent by the AMF, where the third message includes the first XnAP information;
  • the target NG-RAN node sends a fourth message to the AMF, wherein the fourth message includes a second XnAP message.
  • 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.
  • 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.
  • 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.
  • a message forwarding method wherein the method comprises:
  • the AMF forwards the XnAP message between the source NG-RAN node and the target NG-RAN node through NGAP signaling.
  • 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.
  • the AMF receives a first message sent by the 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.
  • the first message also includes identification information, where the identification information indicates the target NG-RAN node.
  • the identification information is a global RAN node identifier and a selected tracking area identifier.
  • 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.
  • 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.
  • the second message is confirmation information that the first XnAP message is successfully forwarded
  • the second message is confirmation information that the first XnAP message failed to be forwarded.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • a message forwarding method wherein the method comprises:
  • the IAB node receives a fifth message from the first host CU, wherein the fifth message includes the first XnAP message;
  • the IAB node sends a sixth message to the second host CU, where the sixth message includes the first XnAP message.
  • the IAB node receives a seventh message from the second host CU, where the seventh message includes a second XnAP message;
  • the IAB node sends an eighth message to the first host CU, where the eighth message includes the second XnAP message.
  • the fifth message is an RRC message
  • the sixth message is an F1AP message
  • 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.
  • the fifth message is an F1AP message
  • the sixth message is an RRC message
  • 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.
  • the format of the first container is an octal string
  • the first XnAP message is an IAB-related Xn message initiated by the first host CU.
  • the seventh message is an F1AP message
  • the eighth message is an RRC message
  • 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.
  • the seventh message is an RRC message
  • the eighth message is an F1AP message
  • 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.
  • 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.
  • a message forwarding method wherein the method comprises:
  • the first host CU 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.
  • the IAB node also receives a seventh message from the second host CU, wherein the seventh message includes a second XnAP message;
  • the method further comprises:
  • the first host CU receives an eighth message sent by the IAB node, where the eighth message includes the second XnAP message.
  • a message forwarding method wherein the method comprises:
  • the second host CU receives a sixth message sent by the IAB node, wherein the sixth message includes a first XnAP message, wherein the first XnAP message comes from a fifth message received by the IAB node from the first host CU, and wherein the fifth message includes the first XnAP message.
  • the second host CU sends a seventh message to the IAB node, wherein the seventh message includes a second XnAP message; so that the IAB node sends an eighth message to the first host CU, wherein the eighth message includes the second XnAP message.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Des modes de réalisation de la présente demande concernent un appareil et un procédé de transfert de messages. Le procédé comprend les étapes suivantes : un nœud NG-RAN source et un nœud NG-RAN cible transfèrent un message XnAP par l'intermédiaire d'un réseau central au moyen d'une signalisation NGAP. Selon les modes de réalisation de la présente demande, le problème de manque d'interaction de signalisation par l'intermédiaire d'une interface Xn entre des nœuds RAN universels est résolu, et une interaction d'informations entre des nœuds RAN est prise en charge.
PCT/CN2023/112433 2023-08-11 2023-08-11 Appareil et procédé de transfert de messages Pending WO2025035233A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/112433 WO2025035233A1 (fr) 2023-08-11 2023-08-11 Appareil et procédé de transfert de messages

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/112433 WO2025035233A1 (fr) 2023-08-11 2023-08-11 Appareil et procédé de transfert de messages

Publications (1)

Publication Number Publication Date
WO2025035233A1 true WO2025035233A1 (fr) 2025-02-20

Family

ID=94631928

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/112433 Pending WO2025035233A1 (fr) 2023-08-11 2023-08-11 Appareil et procédé de transfert de messages

Country Status (1)

Country Link
WO (1) WO2025035233A1 (fr)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109699050A (zh) * 2017-10-24 2019-04-30 普天信息技术有限公司 一种非激活态终端恢复连接的方法、基站、设备及系统
US20210051547A1 (en) * 2019-08-16 2021-02-18 Nokia Solutions And Networks Oy Associating iab mt to iab du at handover-target gnb
WO2021031015A1 (fr) * 2019-08-16 2021-02-25 华为技术有限公司 Procédé, dispositif et système de communications
WO2023083228A1 (fr) * 2021-11-10 2023-05-19 中兴通讯股份有限公司 Procédé de transfert de station de base, station de base et support de stockage lisible par ordinateur
CN116458190A (zh) * 2020-10-22 2023-07-18 中兴通讯股份有限公司 用于增强新空口集成接入回程网络的方法和设备
US20230232285A1 (en) * 2020-06-18 2023-07-20 Telefonaktiebolaget Lm Ericsson (Publ) Handling Communication
WO2023135573A1 (fr) * 2022-01-14 2023-07-20 Telefonaktiebolaget Lm Ericsson (Publ) Systèmes et procédés de transfert temporel dans des réseaux non terrestre

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109699050A (zh) * 2017-10-24 2019-04-30 普天信息技术有限公司 一种非激活态终端恢复连接的方法、基站、设备及系统
US20210051547A1 (en) * 2019-08-16 2021-02-18 Nokia Solutions And Networks Oy Associating iab mt to iab du at handover-target gnb
WO2021031015A1 (fr) * 2019-08-16 2021-02-25 华为技术有限公司 Procédé, dispositif et système de communications
US20230232285A1 (en) * 2020-06-18 2023-07-20 Telefonaktiebolaget Lm Ericsson (Publ) Handling Communication
CN116458190A (zh) * 2020-10-22 2023-07-18 中兴通讯股份有限公司 用于增强新空口集成接入回程网络的方法和设备
WO2023083228A1 (fr) * 2021-11-10 2023-05-19 中兴通讯股份有限公司 Procédé de transfert de station de base, station de base et support de stockage lisible par ordinateur
WO2023135573A1 (fr) * 2022-01-14 2023-07-20 Telefonaktiebolaget Lm Ericsson (Publ) Systèmes et procédés de transfert temporel dans des réseaux non terrestre

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ZTE: "Discussion on enhancements to IAB node migration in mobile IAB scenario", 3GPP DRAFT; R3-233172, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. 3GPP RAN 3, no. Incheon, Republic of Korea; 20230522 - 20230526, 12 May 2023 (2023-05-12), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052373081 *

Similar Documents

Publication Publication Date Title
JP7516578B2 (ja) Ｉａｂネットワーク通信方法及び関連デバイス
CN116235543A (zh) 群组切换的方法、装置和系统
CN117796000A (zh) 集成的接入和回传的通信装置以及方法
WO2022236644A1 (fr) Procédé d'envoi et de réception de signal, appareil d'envoi et de réception de signal, et système de communication
WO2022205326A1 (fr) Procédés et systèmes de migration de donneur d'accès et de de liaison terrestre intégré
WO2024031289A1 (fr) Procédé de communication pour nœud de réseau, procédé de communication pour nœud mobile, nœud mobile et dispositif donneur
JP2024516007A (ja) メッセージ送信方法、装置及びシステム
US20240349166A1 (en) Iab-node device, iab-donor device and topology revoking method
WO2022205252A1 (fr) Procédé et appareil d'envoi et de réception de signal et système de communication
CN116349293A (zh) Iab节点的移植方法及装置
WO2023066337A1 (fr) Procédé et appareil de transfert de données
WO2023150975A1 (fr) Dispositif donneur d'iab et procédé de transmission et de retour en arrière de la migration
WO2025035233A1 (fr) Appareil et procédé de transfert de messages
CN116724589A (zh) 群组迁移方法、装置和系统
EP4664961A1 (fr) Procédé et appareil de traitement d'informations
JP7806927B2 (ja) 情報を設定する方法と装置及び通信システム
US20260032520A1 (en) Distributed unit migration method and control apparatus, and communication system
US20240397380A1 (en) Iab-donor device and transport migration management method
WO2025091416A1 (fr) Procédé et appareil de mise à jour de l'état d'autorisation d'un nœud iab mobile
WO2025035240A1 (fr) Procédé d'intégration pour nœud d'accès et de liaison terrestre intégrés, et appareil
WO2023130260A1 (fr) Procédé, appareil et système de configuration de message rrc
WO2024026803A1 (fr) Procédé de configuration de nœud mobile, et dispositif donneur
KR20240129057A (ko) Iab 도너 디바이스 및 전송 마이그레이션 관리 방법
JP2026513309A (ja) 信号の送受信方法と装置及び通信システム
WO2023130232A1 (fr) Dispositif de nœud iab, dispositif donneur iab et procédé de migration de trajet

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23948678

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE