WO2021142801A1 - 一种通信方法及装置 - Google Patents

一种通信方法及装置 Download PDF

Info

Publication number
WO2021142801A1
WO2021142801A1 PCT/CN2020/072857 CN2020072857W WO2021142801A1 WO 2021142801 A1 WO2021142801 A1 WO 2021142801A1 CN 2020072857 W CN2020072857 W CN 2020072857W WO 2021142801 A1 WO2021142801 A1 WO 2021142801A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
routing
terminal device
context
routing node
Prior art date
Application number
PCT/CN2020/072857
Other languages
English (en)
French (fr)
Inventor
朱浩仁
靳维生
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to CN202080093433.XA priority Critical patent/CN115004658B/zh
Priority to PCT/CN2020/072857 priority patent/WO2021142801A1/zh
Publication of WO2021142801A1 publication Critical patent/WO2021142801A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding

Definitions

  • This application relates to the field of communication technology, and in particular to a communication method and device.
  • the integrated access backhaul (IAB) technology and core network architecture are combined to construct communication devices such as terminal devices that require data transmission.
  • Local routing In the process of constructing a local route, the local route node (generally an IAB node) needs to perform address learning to clarify the mapping relationship between the address of the terminal device and the radio bearer and the transmission protocol, so that the subsequent data transmission can be completed.
  • the current local routing node that is, the IAB node, obtains the above-mentioned mapping relationship in two main ways: (1) When each terminal device sends an uplink data stream, the IAB node obtains media access control (MAC) after parsing the data packet. ) Address/Internet Protocol (IP) address, and build a mapping relationship based on data radio bearer (DRB) and radio link control layer protocol (Radio link control, RLC) information; (2) IAB node passes The broadcast method actively learns its MAC address/IP address from the terminal device, and builds a mapping relationship based on the transmitted DRB and RLC information.
  • MAC media access control
  • IP Address/Internet Protocol
  • RLC radio link control layer protocol
  • the local routing node needs to be reselected, and the reselected local routing node needs to re-broadcast to learn the above mapping relationship or wait for the terminal device to send uplink data packets to passively learn the above mapping relationship.
  • the former will cause a lot of signaling overhead.
  • the latter will cause a higher delay.
  • the present application provides a communication method and device, which are used in handover scenarios to reduce signaling overhead and time delay caused by reselecting routing nodes.
  • the present application provides a communication method.
  • the method includes: after determining that the routing node needs to be adjusted, the first node sends context request information to the source routing node, and the context request information is used to request the source routing node The first routing context; the first node receives the first routing context from the source routing node; the first node determines the target routing node, and sends the second routing context to the target routing node, the The second routing context is determined based on the first routing context.
  • the first node when the device is switched, the first node obtains the routing context in the source routing node, processes it and sends it to the reselected routing node, realizing effective sharing of information without the need for reselected routing
  • the node relearns or acquires, which can reduce repeated rule learning calculations and delay overhead.
  • the first node determines that the routing node needs to be adjusted.
  • the specific method may be: after the first node determines that the device needs to be handed over, according to the terminal device grouping information, the packet-bound routing node information or device At least one item in the topology determines that the routing node needs to be adjusted. In this way, the first node can accurately determine that the routing node needs to be adjusted to trigger a subsequent request for the first routing context.
  • the context request information includes the terminal device group identification and/or the identification of the first type of terminal device, and the first type of terminal device is a currently valid terminal device in a device switching scenario or is currently invalid Terminal equipment.
  • the source routing node can accurately determine the first routing context according to the information in the context request information.
  • the first node determines the currently valid terminal device and the currently invalid terminal device according to the device topology structure before the routing node adjustment and the device topology structure after the routing node adjustment. In this way, the first node can accurately learn which terminal devices are not affected in the handover scenario, so as to request to obtain the routing context of these terminal devices.
  • the first routing context includes a first address mapping relationship
  • the first address mapping relationship includes a mapping relationship between an address of a terminal device and a radio bearer identifier.
  • the first address mapping relationship also includes a logical channel identifier.
  • the first node determines the second routing context based on the first routing context.
  • the specific method may be: the first node replaces the radio bearer identifier in the first address mapping relationship To generate a new radio bearer identity to obtain the second routing context, where the new radio bearer identity is allocated by the first node. In this way, the currently required routing context can be generated after the device is switched for data transmission.
  • the first node sends deletion instruction information to the source routing node, and the deletion instruction information includes the terminal device group identifier and/or the identifier of the first type of terminal device.
  • the terminal device is a currently valid terminal device or a currently disabled terminal device in a device switching scenario, and the deletion indication information is used to instruct the source routing node to delete the first routing context; the first node is from the source The routing node receives the deletion confirmation message. In this way, the source routing node can reduce resource occupation.
  • the first node determines that the device switching has been completed. This can ensure that the destination routing node completes the subsequent operations.
  • the first node sends a terminal device grouping attribute to the target routing node, and the terminal device grouping attribute includes a routing indication, and the routing indication is used to instruct the target routing node to perform data exchange.
  • the destination routing node can accurately realize data exchange.
  • the present application provides a communication method, the method includes: a source routing node receives context request information from a first node, the context request information is used to request a first routing context in the source routing node; The source routing node determines the first routing context according to the context request information; the source routing node sends the first routing context to the first node.
  • the first node when the device is switched, the first node can obtain the routing context in the source routing node and send it to the reselected routing node to realize the effective sharing of information without the need for reselection.
  • the routing node to re-learn or obtain, which can reduce the repeated rule learning calculation and delay overhead.
  • the context request information includes the terminal device group identifier and/or the identifier of the first type of terminal device, and the first type of terminal device is a currently valid terminal device in a device switching scenario or is currently invalid
  • the source routing node determines the first routing context according to the context request information, including: the source routing node determines the first type of terminal device according to the group identifier of the terminal device and/or the identifier of the first type of terminal device The first routing context. In this way, the source routing node can accurately determine the first routing context according to the information in the context request information.
  • the first routing context includes a first address mapping relationship
  • the first address mapping relationship includes a mapping relationship between an address of a terminal device and a radio bearer identifier.
  • the first address mapping relationship also includes a logical channel identifier.
  • the source routing node receives deletion indication information from the first node, and the deletion indication information includes a terminal device group identifier and/or an identifier of a first type of terminal device.
  • the terminal device is a currently valid terminal device or a currently disabled terminal device in the device switching scenario, and the deletion indication information is used to instruct the source routing node to delete the first routing context; the source routing node according to the terminal The device group identifier and/or the identifier of the first-type terminal device delete the first routing context; the source routing node sends deletion confirmation information to the first node. In this way, the source routing node can reduce resource occupation.
  • the present application provides a communication method, the method includes: a target routing node receives a second routing context from a first node, the second routing context is determined based on the first routing context; the target The routing node determines the routing rule according to the second routing context.
  • the second routing context includes a second address mapping relationship
  • the second address mapping relationship includes a mapping relationship between an address of a terminal device and a radio bearer identity
  • the second address mapping relationship is Determined based on the first address mapping relationship in the first routing context.
  • the second address mapping relationship further includes a logical channel identifier.
  • the target routing node determines the routing rule according to the second routing node, and the specific method may be: the target routing node determines according to the second address mapping relationship in the second routing context The routing rule; or, the target routing node uses the second address mapping relationship as the routing rule. In this way, the target routing node can accurately determine the routing rule after the device is switched, so as to implement the subsequent routing process.
  • the target routing node receives a terminal device grouping attribute from the first node, the terminal device grouping attribute includes a routing indication, and the routing indication is used to instruct the target routing node to perform data exchange;
  • the target routing node determines the data exchange type according to the grouping attribute of the terminal device. In this way, data can be exchanged accurately according to the type of data exchange.
  • the routing instruction is an L2/L3 layer switching instruction
  • the target routing node determines the data exchange type according to the grouping attributes of the terminal device.
  • the specific method may be: the target routing node according to the L2
  • the /L3 layer exchange indication determines the data exchange type. This can accurately determine the type of data exchange.
  • the present application also provides a first node that has a function of realizing the behavior of the first node in the method example of the first aspect.
  • the function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the structure of the first node includes a processing unit and a communication unit. These units can perform the corresponding functions in the above-mentioned method examples of the first aspect. For details, please refer to the detailed description in the method examples. Go into details.
  • the structure of the first node includes a communication interface, a processor, and optionally a memory, and the communication interface is used to send and receive data, and to communicate with other devices in the communication system.
  • the processor is configured to support the first node to perform the corresponding function in the above-mentioned method in the first aspect.
  • the memory is coupled with the processor, and stores the necessary program instructions and data of the first node.
  • the present application also provides a source routing node, which has the function of realizing the behavior of the source routing node in the method example of the second aspect.
  • the function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the structure of the source routing node includes a processing unit and a communication unit. These units can perform the corresponding functions in the method example of the second aspect. For details, please refer to the detailed description in the method example, which will not be described here. Go into details.
  • the structure of the source routing node includes a communication interface, a processor, and optionally a memory, and the communication interface is used to send and receive data, and to communicate with other devices in the communication system.
  • the processor is configured to support the source routing node to perform the corresponding function in the method of the second aspect described above.
  • the memory is coupled with the processor, and stores the necessary program instructions and data of the source routing node.
  • the present application also provides a target routing node, which has the function of realizing the behavior of the target routing node in the method example of the third aspect.
  • the function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the structure of the target routing node includes a processing unit and a communication unit. These units can perform the corresponding functions in the method example of the third aspect. For details, please refer to the detailed description in the method example, which will not be described here. Go into details.
  • the structure of the target routing node includes a communication interface, a processor, and optionally a memory, and the communication interface is used for sending and receiving data, and for communicating with other devices in the communication system.
  • the processor is configured to support the target routing node to perform the corresponding function in the method of the third aspect described above.
  • the memory is coupled with the processor, and stores the necessary program instructions and data of the target routing node.
  • the present application also provides a communication system including a first node, and the first node can be used to perform the steps performed by the first node in the first aspect and any one of the methods in the first aspect.
  • the communication system may further include a source routing node, and the source routing node may be used to perform the steps performed by the source routing node in the second aspect and any one of the methods of the second aspect.
  • the communication system may further include a target routing node, and the target routing node may be used to execute the steps performed by the target routing node in the third aspect and any method of the third aspect.
  • the communication system may also include other devices that interact with at least one of the first node, the source routing node, or the target routing node in the solution provided in the embodiments of the present application, and so on.
  • the present application also provides a communication system, which includes a source routing node, and the source routing node can be used to perform the steps performed by the source routing node in the second aspect and any one of the methods in the second aspect.
  • the communication system may further include a first node, and the first node may be used to perform the steps performed by the first node in the first aspect and any one of the methods of the first aspect.
  • the communication system may further include a target routing node, and the target routing node may be used to execute the steps performed by the target routing node in the third aspect and any method of the third aspect.
  • the communication system may also include other devices that interact with at least one of the source routing node, the first node, or the target routing node in the solution provided in the embodiments of the present application, and so on.
  • the present application also provides a communication system that includes a target routing node, and the target routing node can be used to execute the steps performed by the target routing node in the third aspect and any of the methods of the third aspect.
  • the communication system may further include a first node, and the first node may be used to perform the steps performed by the first node in the first aspect and any one of the methods of the first aspect.
  • the communication system may further include a source routing node, and the source routing node may be used to perform the steps performed by the source routing node in the second aspect and any one of the methods of the second aspect.
  • the communication system may also include other devices that interact with at least one of the target routing node, the first node, or the source routing node in the solution provided in the embodiments of the present application, and so on.
  • the present application also provides a computer-readable storage medium having computer-executable instructions stored in the computer-readable storage medium, and the computer-executable instructions are used to make the computer executable when called by the computer
  • the computer executes any of the above methods.
  • this application also provides a computer program product containing instructions, which when run on a computer, causes the computer to execute any of the above methods.
  • the present application also provides a chip, which is coupled with a memory, and is configured to read and execute program instructions stored in the memory to implement any of the above methods.
  • Figure 1 is a schematic structural diagram of a communication system provided by this application.
  • Figure 2 is a schematic diagram of a scenario provided by this application.
  • FIG. 3 is a schematic diagram of another scenario provided by this application.
  • FIG. 4 is a flowchart of a communication method provided by this application.
  • FIG. 5 is a flowchart of an example of a communication method provided by this application.
  • FIG. 6 is a flowchart of an example of another communication method provided by this application.
  • FIG. 7 is a schematic structural diagram of a device provided by this application.
  • FIG. 8 is a schematic structural diagram of another device provided by this application.
  • FIG. 9 is a schematic structural diagram of another device provided by this application.
  • FIG. 10 is a structural diagram of a first node provided by this application.
  • FIG. 11 is a structural diagram of a source routing node provided by this application.
  • FIG. 12 is a structural diagram of a target routing node provided by this application.
  • the embodiments of the present application provide a communication method and device, which are used in a handover scenario to reduce signaling overhead and time delay caused by reselecting a routing node.
  • At least one refers to one or more, and “multiple” refers to two or more than two.
  • “And/or” describes the association relationship of the associated object, indicating that there can be three relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, and B exists alone, where A, B can be singular or plural.
  • the character “/” generally indicates that the associated objects before and after are in an “or” relationship.
  • the following at least one (item) or similar expressions refers to any combination of these items, including any combination of a single item (a) or a plurality of items (a).
  • At least one of a, b, or c can mean: a, b, c, a and b, a and c, b and c, or a, b and c, where a, b, c It can be single or multiple.
  • the IAB node is a specific name of a relay node, which does not constitute a limitation to the solution of this application. It can be one of the aforementioned base stations or terminal devices with a forwarding function, or it can be an independent device form.
  • the IAB node of the present application may also be referred to as a relay node (RN), a transmission and reception point (transmission and reception point), a relay transmission and reception point (relaying TRP), and so on.
  • the communication system architecture may include a local network, a core network network, one or more IAB donor nodes (IAB donor), and one or more IABs. Node and one or more terminal devices.
  • FIG. 1 shows a possible example of the architecture of the communication system. It should be understood that the embodiments of the present application are not limited to the communication system shown in FIG. 1.
  • the names of the devices or nodes shown in FIG. 1 are only used as an example for illustration, and are not used as the architecture of the communication system applicable to the method of the present application. Limitations of the equipment included in.
  • the function of each node or device in the communication system is described in detail below:
  • the local network that is, the data network (DN)
  • DN can be an industrial Ethernet data network, or an Internet protocol (IP) data network, and of course, it can also be other networks.
  • IP Internet protocol
  • the core network (core network, CN) is distributed with multiple functional network elements, for example, 5G access and mobility management function (AMF), session management function network elements ( Session management function (SMF), user plane function network elements (user plane function, UPF), etc., will not be listed here.
  • AMF 5G access and mobility management function
  • SMF Session management function
  • UPF user plane function
  • the core network is shown as CN.
  • the IAB host node is responsible for managing all IAB nodes, and can learn the topology structure of the IAB nodes and/or terminal devices.
  • the IAB host node may be composed of a control plane (centralized unit-control plane, CU-CP) in a centralized unit and a user plane (centralized unit-user plane, CU-UP) module in a centralized unit.
  • a control plane centralized unit-control plane, CU-CP
  • CU-UP centralized unit-user plane
  • the IAB node includes a distributed unit (DU) and a mobile terminal (MT) module. Multiple IAB nodes are cascaded using spanning tree (ST) or directed acyclic graph (DAG). When cascading, each IAB node needs to complete the non-access layer (non-access layer). -Access stratum, NAS) authentication, and complete the operation and maintenance management (operation administration and maintenance, OAM) configuration through the session.
  • the IAB node has the capability of CU-UP, that is, it has a packet data protocol (packet data convergence protocol, PDCP) and a service data adaptation protocol (service data adaptation protocol, SDAP) protocol stack; if there is an interface, the IAB node can directly Forward the data to the local Ethernet data network or IP data network.
  • Fig. 1 shows IAB node 1 and IAB node 2.
  • the terminal equipment which may also be referred to as user equipment (UE), mobile station (MS), mobile terminal (MT), etc.
  • UE user equipment
  • MS mobile station
  • MT mobile terminal
  • the terminal device and the access network device communicate with each other using some kind of air interface technology.
  • the terminal device may be: a handheld terminal, a notebook computer, a subscriber unit (SU), a cellular phone (cellular phone), a smart phone (smart phone), a wireless data card, a personal digital assistant (personal digital assistant, PDA) computers, tablet computers, wireless modems, handheld devices, laptop computers, cordless phones or wireless local loops (wireless local loop, WLL), machines Type communication (machine type communication, MTC) terminal or other devices that can access the network.
  • the terminal device in FIG. 1 is shown as a UE, for example, UE1, UE2, and UE3 in FIG. 1 are only examples, and the terminal device is not limited.
  • FIG. 1 the architecture of the communication system shown in FIG. 1 is not limited to include only the nodes or devices shown in the figure, and may also include other devices not shown in the figure. Specifically, this application will not be one by one here. Enumerate.
  • the communication system shown in FIG. 1 does not constitute a limitation of the communication system to which the embodiments of the present application can be applied.
  • the communication system architecture shown in FIG. 1 is a 5G system architecture.
  • the method in the embodiment of the present application is also applicable to various future communication systems, such as 6G or other communication networks.
  • Figure 2 shows a possible scenario.
  • the local route node is IAB node 1. That is, when UE1 communicates with UE2 (also referred to as communication), it only needs to transit through the IAB node 1, and does not need to pass through the IAB host node, CN, and local network.
  • the routing paths of UE1 and UE2 are shown in (a) in Figure 2.
  • IAB host node 1 When UE1 moves and switches to IAB node 2, IAB host node 1 re-selects the local routing node according to the topology information.
  • IAB host node 1 determines that it is a new local routing node, it can be as shown in Figure 2 (b) Show.
  • Figure 3 shows another possible scenario.
  • UE1 and UE3 have already constructed local routes, and the local route node is the IAB host node 1.
  • the routing paths of UE1 and UE3 are shown in (a) in FIG. 3.
  • the topological relationship between the nodes will change, so that the local routing node may also change; for example, if it is because of the difference between IAB host node 1 and IAB node 2.
  • the link condition between the nodes deteriorates, and IAB-node 2 may re-select IAB-node 1 as the parent node.
  • the new local routing node changes to IAB-node 1, as shown in (b) in FIG. 3, for example.
  • the new local routing node either reacquires the mapping relationship related to the routing address by broadcasting, or learns the mapping relationship while waiting for the UE to send uplink data, which will cause a lot of signaling overhead or additional time delay. Based on this, this application proposes a communication method to realize effective sharing of information and reduce repeated rule learning calculations and delay overhead.
  • a communication method provided by an embodiment of the present application is applicable to the communication system shown in FIG. 1.
  • the specific process of the method may include:
  • Step 401 After determining that the routing node needs to be adjusted, the first node sends context request information to the source routing node, where the context request information is used to request the first routing context in the source routing node.
  • the first node may be an IAB host node, and the operation of the first node may be executed by the CU in the first node during the specific implementation of this application.
  • the first node determines that the routing node needs to be adjusted.
  • the specific method may be: after the first node determines that the device needs to be switched, it is based on terminal device grouping information, packet-bound routing node information, or device topology At least one item determines that the routing node needs to be adjusted.
  • the need to switch the device in this application may include the situation where the terminal device needs to switch and the situation where the IAB node needs to switch.
  • the specific method for the first node to determine that the device needs to be switched may be: the first node receives a measurement report from the source IAB node, and the first node determines that the device needs to be switched according to the measurement report and the switching threshold.
  • the source IAB node is the IAB node connected before the terminal device switching in the terminal device switching scenario, or the IAB node or the IAB host node connected before the switching of the IAB node to be switched in the IAB node switching scenario.
  • the operation performed by any IAB node may be performed by the DU or MT in the IAB node.
  • the terminal device grouping information may include a terminal device group (identity, ID), a terminal device group member identification list, and the like.
  • the core network element After receiving the local routing request, the core network element obtains the identities of a group of terminal devices that need local routing, and marks the terminal device group with a unique identifier, that is, the terminal device group identity.
  • the first node may obtain the above-mentioned information from the core network element.
  • the device topology structure is a topology structure in which one or more terminal devices, one or more IAB nodes, and one or more IAB host nodes are distributed.
  • the context request information may include a terminal device group identifier and/or an identifier of a first type of terminal device, where the first type of terminal device is a currently valid terminal device in a device switching scenario or a currently disabled terminal equipment.
  • the terminal device when the terminal device is switched or the IAB node is switched, the device topology will change, and the routing node may need to be adjusted.
  • the address mapping relationship of some terminal devices in the terminal device group will change, and the address mapping relationship of some terminal devices will not change. Therefore, the currently valid terminal device herein refers to a terminal device whose address mapping relationship described above has not changed, and the currently invalid terminal device refers to a terminal device whose address mapping relationship described above has changed.
  • Context instructing the source routing node to send the context of the terminal devices other than these terminal devices in the terminal device group where the terminal device is located, that is, the context of the terminal devices other than these terminal devices in the terminal device group is the first Routing context.
  • the context request information contains the identification of the currently valid terminal device, it indicates that the source routing node can only send the context of the terminal device, that is, the context of the terminal device. Is the first routing context.
  • the first node includes the global device topology and terminal device grouping information.
  • the first node can determine that the topology structure has changed, and the first node determines the routing node After adjustment, the device topology structure before the routing node adjustment and the device topology structure after the routing node adjustment are used to determine which terminal devices are valid and which terminal devices are invalid.
  • the identity of any terminal device can be represented by one of the following: DRB identity, Signaling Radio Bearer (Signaling Radio Bearer, SRB) identity, cell radio network temporary identifier (C-RNTI), etc. Wait.
  • the first routing context includes a first address mapping relationship
  • the first address mapping relationship includes a mapping relationship between an address of a terminal device and a radio bearer identifier.
  • the radio bearer identifier may be a DRB identifier or an SRB identifier or a C-RNTI.
  • the address of the terminal device can be a MAC address or an IP address.
  • the first address mapping relationship included in the first routing context is a mapping relationship used for data transmission of the terminal device before the device is switched.
  • the first routing context is mainly the context of the terminal device whose address mapping relationship is not affected after the device is switched, that is, the context of the currently valid terminal device mentioned above.
  • the first address mapping relationship may also include a logical channel identifier.
  • the logical channel identifier may be an RLC identifier or the like.
  • the first node may send the context request information to the source routing node through F1-application protocol request information (F1-(application protocol, AP) request message).
  • F1-application protocol request information F1-(application protocol, AP) request message
  • Step 402 The source routing node determines the first routing context according to the context request information.
  • the source routing node may determine the first routing context according to the terminal device group identifier and/or the identifier of the first type of terminal device included in the context request information.
  • the local context of the source routing node includes the terminal device group identification and the terminal device identification in the terminal device group, when the first node sends the terminal device group identification and the current invalidity to the source routing node
  • the source routing node excludes the identities of these invalid terminal devices, and the remaining terminal devices are valid terminal devices, so that the context of the currently valid terminal device can be determined, and then the valid terminal device The context of the device is returned to the first node.
  • Step 403 The source routing node sends the first routing context to the first node.
  • the source routing node may send the first routing context to the first node through an F1-AP response message (F1-AP response message).
  • F1-AP response message F1-AP response message
  • the first node after the first node receives the first routing context, the first node sends deletion indication information to the source routing node, and the deletion indication information includes the terminal The device group identifier and/or the identifier of the first type of terminal device, the first type of terminal device is a currently valid terminal device or a currently disabled terminal device in a device switching scenario, and the deletion indication information is used to indicate the source
  • the routing node deletes the first routing context; the source routing node deletes the first routing context according to the terminal device group identifier and/or the identifier of the first type of terminal device contained in the deletion instruction information, and restores to be a routing node The previous transmission path; then the source routing node sends a deletion confirmation message to the first node.
  • the first node may also send the deletion indication information to the source routing node through F1-AP request message; the source routing node may send the deletion indication information to the first node through F1-AP response message Delete confirmation message.
  • Step 404 The first node determines a target routing node.
  • the first node determines that the device switching has been completed before determining the target routing node. It can be understood that it is because the device switch triggers the reselection of the routing node.
  • the specific method for determining the target routing node by the first node may be as follows: the first node selects the target routing node according to the completed device topology and a set strategy.
  • the setting strategy may be to select the smallest common parent node of two terminal devices for communication.
  • the first node associates the terminal device group identifier with the target routing node.
  • Step 405 The first node sends a second routing context to the target routing node, where the second routing context is determined based on the first routing context.
  • the first node determines the second routing context based on the first routing context, it replaces the radio bearer identifier in the first address mapping relationship with a new radio bearer identifier to obtain
  • the new radio bearer identifier is allocated by the first node.
  • the first node includes a global device topology, and a new radio bearer identifier can be assigned to the terminal device after the device topology of the first node changes.
  • the first node may specifically determine the second routing context according to a radio bearer identifier in the first address mapping relationship in the first routing context. For example, if the radio bearer ID of the terminal device changes, the first node needs to replace the old radio bearer ID in the first address mapping relationship with a new radio bearer ID, so as to obtain the second routing context.
  • the first node may determine the new radio bearer ID according to the C-RNTI.
  • Step 406 The target routing node determines a routing rule according to the second routing context.
  • the second routing context includes a second address mapping relationship obtained from the first address mapping relationship, for example, the second address mapping relationship is that the old radio bearer ID in the first address mapping relationship is replaced with a new radio bearer ID obtained.
  • the second mapping relationship may serve as the routing rule, or the routing rule may be determined according to the second mapping relationship.
  • the first node sends a terminal device grouping attribute to the target routing node, and the terminal device grouping attribute includes a routing indication, and the routing indication is used to instruct the target routing node to perform Data exchange; then the target routing node determines the type of data exchange according to the grouping attributes of the terminal device.
  • the routing indication may be an L2/L3 layer switching indication.
  • L2 refers to the MAC layer in the open system interconnect (OSI) seven-layer model
  • L3 layer refers to the IP layer in the OSI seven-layer model, which is used to indicate whether the local exchange is based on the MAC layer or IP Layers are exchanged.
  • the data exchange type is also the business mode of communication within the device group.
  • the core network element after receiving the local routing request, the core network element obtains the packet attributes, such as the service type of the packet, or forwarding instructions (that is, L2/L3 layer switching instructions), etc. according to the local routing request.
  • the packet attributes such as the service type of the packet, or forwarding instructions (that is, L2/L3 layer switching instructions), etc. according to the local routing request.
  • the target routing node determines the data exchange type according to the L2/L3 layer exchange instruction.
  • the group attribute may also include DNN information associated with the device group, and PDU session type information of the device group members.
  • the target node further performs the following processing according to the L2/L3 layer exchange instruction information: ( 1) The L2 layer indicates that the PDCP/SDAP header of the data packet needs to be stripped and forwarded to the industrial Ethernet/IP network according to the switch forwarding method; (2) The L3 layer indicates that the PDCP/SDAP header of the data packet needs to be stripped, If there is a MAC header, the MAC header is stripped and forwarded to the industrial Ethernet/IP network in a router manner.
  • the first node when the device is switched, the first node obtains the routing context in the source routing node, processes it and sends it to the reselected routing node, realizing effective information sharing without the need
  • the re-selected routing node relearns or acquires it, which can reduce repeated rule learning calculations and delay overhead.
  • the following uses specific examples, such as the embodiments shown in FIG. 5 and FIG. 6, to describe in detail the communication method provided in the embodiments of the present application.
  • the host node performs operations through the host node-CU, and the IAB node performs corresponding operations through the DU or MT respectively for illustration.
  • an example of a communication method is shown, and this example can be applied to the UE handover scenario shown in FIG. 2.
  • the host node actively requests the local routing context from the source routing node, and after the UE handover is completed, sends the routing context to the reselected target routing node to reduce the relearning of the target routing node rules. Calculation and delay overhead.
  • the source IAB (node) is the IAB node connected before the UE handover
  • the target IAB (node) is the IAB node connected after the UE handover.
  • the specific process of this example may include the following steps:
  • Step 501 When the UE is moving, it sends a measurement report to the source IAB node (actually, it is the DU sent to the source IAB node, and the source IAB node is shown as the source IAB-DU in FIG. 5).
  • the source IAB node is the IAB node that the UE is connected to before moving.
  • Step 502 The source IAB node sends the measurement report to the host node (actually sent to the CU of the host node, the host node is shown as host node-CU in FIG. 5).
  • the host node is a node that manages the IAB nodes connected before and after the UE handover, that is, the first node involved in the embodiment shown in FIG. 4.
  • Step 503 The host node-CU decides to initiate handover according to the received measurement report and handover threshold, and at the same time according to UE grouping information (UE group identification, UE group member identification list, etc.), group binding information (group-bound routing node Information), the UE/IAB node topology structure judges that the local routing needs to be adjusted.
  • UE grouping information UE group identification, UE group member identification list, etc.
  • group binding information group-bound routing node Information
  • Step 504 The host node-CU sends context request information to the source routing node, where the context request information is used to request the first routing context in the source routing node.
  • the context request information may include a terminal device group identifier and/or an identifier of a first type of terminal device, where the first type of terminal device is a currently valid terminal device in a device switching scenario or a currently disabled terminal equipment.
  • the terminal device when the terminal device is switched, the device topology will change, and the routing node may need to be adjusted.
  • the address mapping relationship of some terminal devices in the terminal device group will change, and the address mapping relationship of some terminal devices will not change. Therefore, the currently valid terminal device herein refers to a terminal device whose address mapping relationship described above has not changed, and the currently invalid terminal device refers to a terminal device whose address mapping relationship described above has changed.
  • Context instructing the source routing node to send the context of the terminal devices other than these terminal devices in the terminal device group where the terminal device is located, that is, the context of the terminal devices other than these terminal devices in the terminal device group is the first Routing context.
  • the context request information contains the identification of the currently valid terminal device, it indicates that the source routing node can only send the context of the terminal device, that is, the context of the terminal device. Is the first routing context.
  • the host node-CU may send an F1-AP request message to the source routing node, and the F1-AP request message includes context request information (may also be referred to as a local routing context request indication).
  • context request information may also be referred to as a local routing context request indication.
  • the local routing context request indication is mainly a request to obtain the mapping relationship learned by the source routing node, that is, the first address mapping included in the first routing context involved in the embodiment shown in FIG. 2 relation.
  • the first address mapping relationship may be UE ⁇ MAC address/IP address ⁇ -DRB-RLC or customer premises equipment (CPE) ⁇ MAC address1/IP address1, MAC address2/IP address2 ,... ⁇ -DRB-RLC.
  • CPE customer premises equipment
  • CPE is a type of UE.
  • Step 505 The source routing node sends an F1-AP response message to the host node-CU, and the F1-AP response message contains the first routing context.
  • Step 506 After receiving the first route up and down, the host node-CU sends deletion indication information to the source routing node through the F1-AP message, which is used to instruct the source routing node to delete the first routing context and restore the previous transmission path.
  • the deletion indication information includes the UE group ID or the UE ID (for example, in this example, the UE ID is the DRB ID of the UE as an example, but it should be understood that this is not a limitation on the UE ID).
  • Step 507 After receiving the deletion instruction information, the source routing node deletes the corresponding local route according to the UE group ID or DRB ID in the deletion instruction information, and restores the previous transmission rule.
  • the source routing node deletes the first routing context.
  • Step 508 After the source routing node is deleted, the deletion confirmation message is sent to the host node-CU through the F1-AP message.
  • Step 509 The host node-CU sends a UE context setup request message (UE context setup request) to the target IAB-DU to create a UE context and set one or more data bearers.
  • UE context setup request UE context setup request
  • the UE context setting request message includes handover preparation information.
  • Step 510 The target IAB-DU sends a UE context setup response message (UE context setup response) to the host node-CU.
  • Step 511 The host node-CU sends a UE context modification request message (UE context modification request) to the source IAB-DU.
  • the UE context modification request message includes the generated radio resource control (radio resource control, RRC) reconfiguration message and instructs to stop data transmission for the UE.
  • RRC radio resource control
  • the source IAB-DU also sends a downlink data delivery status frame (downlink data delivery status) to the host node-CU to notify the host node-CU of information about the downlink data that was not successfully sent to the UE.
  • a downlink data delivery status frame downlink data delivery status
  • Step 512 The source IAB-DU forwards the received RRC reconfiguration (RRC reconfiguration) message to the UE.
  • Step 513 The source IAB-DU sends a UE context modification response message (UE context modification response) to the host node-CU.
  • Step 514 The target IAB-DU performs a random access process.
  • the target IAB-DU sends a downlink data delivery status frame (downlink data delivery status) to the host node-CU.
  • the donor node-CU sends a downlink data packet (which may include a PDCP packet data unit (PDU) that was not successfully sent in the source IAB-DU) to the target IAB-DU.
  • PDU packet data unit
  • Step 515 The UE sends an RRC Reconfiguration Complete (RRC Reconfiguration Complete) message to the target IAB-DU.
  • Step 516 The target IAB-DU sends an uplink RRC message transfer (UL RRC message transfer) message to the donor node-CU to convey the received RRC Reconfiguration Complete message.
  • UL RRC message transfer uplink RRC message transfer
  • the target IAB-DU sends downlink packets (downlink packets) to the UE.
  • the UE sends an uplink data packet to the donor node-CU through the target IAB-DU.
  • Step 517 When the host node-CU has completed the mobility handover of the UE, that is, the UE has been handed over to the target IAB-DU, the host node-CU determines the target routing node at this time.
  • the host node-CU combines the IAB topology information (that is, the device topology structure involved in Figure 4), and selects a strategy (that is, the setting strategy involved in Figure 4) to select the target routing node (such as selecting the smallest common parent node), And associate the UE group identification with the selected routing node.
  • IAB topology information that is, the device topology structure involved in Figure 4
  • a strategy that is, the setting strategy involved in Figure 4
  • Step 518 The host node-CU sends the UE packet attributes (L2/L3 layer exchange indication) and the second routing context to the target routing node.
  • the second routing context is determined by the host node-CU according to the first routing context.
  • the host node-CU regenerates the second routing context according to the new IAB topology relationship and the first routing context.
  • Step 519 The target routing node determines the data exchange type according to the UE packet attribute (L2/L3 layer exchange indication), and then determines the routing rule according to the second routing context.
  • the target routing node constructs a new local route according to the second routing context and the local DRB-RLC channel relationship, that is, determines the routing rule.
  • Step 520 The host node-CU sends a UE context release command (UE context release command) message to the source IAB-DU.
  • UE context release command UE context release command
  • Step 521 The source IAB-DU releases the UE context, and sends a UE context release complete (UE context release complete) message to the host node-CU.
  • UE context release complete UE context release complete
  • the source IAB node and the source routing node are used as two devices for description. It should be understood that, in some scenarios, the source IAB node may be a source routing node, that is, the source IAB node and the source routing node are the same node.
  • the specific implementation method is similar to the above example, which can be referred to each other and will not be described in detail here.
  • an example of another communication method is shown, and this example can be applied to the scenario of IAB node handover shown in FIG. 3.
  • the host node actively requests the local routing context from the source routing node, and after the IAB node is switched, it sends the routing context to the reselected target routing node, so as to reduce the rules of the target routing node.
  • the calculation and delay cost of learning is the migrated IAB node.
  • the migrated IAB node is the IAB node that is switched
  • the source IAB node is the IAB node that the migrated IAB node is connected to before the switch
  • the target IAB node is the IAB node that the migrated IAB node is connected to after the switch.
  • the specific process of this example may include the following steps:
  • Step 601 The migrated IAB node sends a measurement report to the source IAB node (actually, it is the DU sent to the source IAB node, and the source IAB node is shown as the source IAB-DU in FIG. 6).
  • the migrated IAB node sends a measurement report to the source IAB node through the MT, which is exemplarily shown as the migrated IAB-MT in FIG. 6.
  • Step 602 The source IAB node sends the measurement report to the host node (actually sent to the CU of the host node, the host node is shown as host node-CU in FIG. 6).
  • the host node is a node that manages the IAB nodes connected before and after the UE handover, that is, the first node involved in the embodiment shown in FIG. 4.
  • Step 603 The host node-CU decides to initiate handover according to the received measurement report and the handover threshold, and at the same time according to UE grouping information (UE group identifier, UE group member identifier list, etc.), group binding information (group-bound routing node Information), the UE/IAB node topology structure judges that the local routing needs to be adjusted.
  • UE grouping information UE group identifier, UE group member identifier list, etc.
  • group binding information group-bound routing node Information
  • Step 604 The host node-CU sends context request information to the source routing node, where the context request information is used to request the first routing context in the source routing node.
  • the context request information may include a terminal device group identifier and/or an identifier of a first type of terminal device, where the first type of terminal device is a currently valid terminal device in a device switching scenario or a currently disabled terminal equipment.
  • the device topology will change, and the routing node may need to be adjusted.
  • the address mapping relationship of some terminal devices in the terminal device group will change, and the address mapping relationship of some terminal devices will not change. Therefore, the currently valid terminal device herein refers to a terminal device whose address mapping relationship described above has not changed, and the currently invalid terminal device refers to a terminal device whose address mapping relationship described above has changed.
  • Context instructing the source routing node to send the context of the terminal devices other than these terminal devices in the terminal device group where the terminal device is located, that is, the context of the terminal devices other than these terminal devices in the terminal device group is the first Routing context.
  • the context request information contains the identification of the currently valid terminal device, it indicates that the source routing node can only send the context of the terminal device, that is, the context of the terminal device. Is the first routing context.
  • the host node-CU may send an F1-AP request message to the source routing node, and the F1-AP request message includes context request information (may also be referred to as a local routing context request indication).
  • context request information may also be referred to as a local routing context request indication.
  • the local routing context request indication is mainly a request to obtain the mapping relationship learned by the source routing node, that is, the first address mapping included in the first routing context involved in the embodiment shown in FIG. 2 relation.
  • the first address mapping relationship may be UE ⁇ MAC address/IP address ⁇ -DRB-RLC or customer premises equipment (CPE) ⁇ MAC address1/IP address1, MAC address2/IP address2 ,... ⁇ -DRB-RLC.
  • CPE customer premises equipment
  • CPE is a type of UE.
  • Step 605 The source routing node sends an F1-AP response message to the host node-CU, and the F1-AP response message contains the first routing context.
  • Step 606 After receiving the first route up and down, the host node-CU sends deletion indication information to the source routing node through the F1-AP message, which is used to instruct the source routing node to delete the first routing context and restore the previous transmission path.
  • the deletion indication information includes the UE group ID or the UE ID (for example, in this example, the UE ID is the DRB ID of the UE as an example, but it should be understood that this is not a limitation on the UE ID).
  • Step 607 After receiving the deletion instruction information, the source routing node deletes the corresponding local route according to the UE group ID or DRB ID in the deletion instruction information, and restores the previous transmission rule.
  • the source routing node deletes the first routing context.
  • Step 608 After the source routing node is deleted, the deletion confirmation message is sent to the host node-CU through the F1-AP message.
  • Step 609 The host node-CU sends a UE context setup request message (UE context setup request) to the target IAB-DU to create a UE context and set one or more data bearers.
  • UE context setup request UE context setup request
  • the UE context setting request message includes handover preparation information.
  • Step 610 The target IAB-DU sends a UE context setup response message (UE context setup response) to the host node-CU.
  • Step 611 The host node-CU sends a UE context modification request message (UE context modification request) to the source IAB-DU.
  • the UE context modification request message includes the generated radio resource control (radio resource control, RRC) reconfiguration message and instructs to stop data transmission for the UE.
  • RRC radio resource control
  • the source IAB-DU also sends a downlink data delivery status frame (downlink data delivery status) to the host node-CU to notify the host node-CU of information about the downlink data that was not successfully sent to the UE.
  • a downlink data delivery status frame downlink data delivery status
  • Step 612 The source IAB-DU forwards the received RRC reconfiguration (RRC reconfiguration) message to the UE.
  • Step 613 The source IAB-DU sends a UE context modification response message (UE context modification response) to the host node-CU.
  • Step 614 The target IAB-DU performs a random access process.
  • the target IAB-DU sends a downlink data delivery status frame (downlink data delivery status) to the host node-CU.
  • the donor node-CU sends a downlink data packet (which may include a PDCP packet data unit (PDU) that was not successfully sent in the source IAB-DU) to the target IAB-DU.
  • PDU packet data unit
  • Step 615 The UE sends an RRC Reconfiguration Complete (RRC Reconfiguration Complete) message to the target IAB-DU.
  • Step 616 The target IAB-DU sends an uplink RRC message transfer (UL RRC message transfer) message to the donor node-CU to convey the received RRC Reconfiguration Complete message.
  • UL RRC message transfer uplink RRC message transfer
  • the target IAB-DU sends downlink packets (downlink packets) to the UE.
  • the UE sends an uplink data packet to the donor node-CU through the target IAB-DU.
  • Step 617 When the host node-CU has completed the mobility handover of the UE, that is, the UE has been handed over to the target IAB-DU, the host node-CU determines the target routing node at this time.
  • the host node-CU combines the IAB topology information (that is, the device topology structure involved in Figure 4), and selects a strategy (that is, the setting strategy involved in Figure 4) to select the target routing node (such as selecting the smallest common parent node), And associate the UE group identification with the selected routing node.
  • IAB topology information that is, the device topology structure involved in Figure 4
  • a strategy that is, the setting strategy involved in Figure 4
  • Step 618 The host node-CU sends the UE packet attributes (L2/L3 layer exchange indication) and the second routing context to the target routing node.
  • the second routing context is determined by the host node-CU according to the first routing context.
  • the host node-CU regenerates the second routing context according to the new IAB topology relationship and the first routing context.
  • Step 619 The target routing node determines the data exchange type according to the UE packet attribute (L2/L3 layer exchange indication), and then determines the routing rule according to the second routing context.
  • the target routing node constructs a new local route according to the second routing context and the local DRB-RLC channel relationship, that is, determines the routing rule.
  • Step 620 The host node-CU sends a UE context release command (UE context release command) message to the source IAB-DU.
  • UE context release command UE context release command
  • Step 621 The source IAB-DU releases the UE context, and sends a UE context release complete (UE context release complete) message to the host node-CU.
  • UE context release complete UE context release complete
  • the embodiment of the present application also provides a device, which is applied to the first node.
  • the device may specifically be a processor in the first node, or a chip or a chip system, or a functional module.
  • the apparatus 700 may include a processing unit 701 and a communication unit 702.
  • the communication unit 702 is used for the device 700 to receive information (or data) or send information (or data), and the processing unit 701 is used for controlling and managing the actions of the device 700.
  • the processing unit 701 may also be used to indicate the processing procedure involving the first node (for example, the host node) in any of the foregoing embodiments and/or other procedures of the technical solution described in this application.
  • the processing unit 701 may control the steps executed by the communication unit 702.
  • the repetitive parts will not be repeated here.
  • the above-mentioned processing unit 701 may be a processor or a processing circuit, etc.; the communication unit 702 may be a transceiver composed of a transmitter or a transmitting circuit, etc., and a receiver or a receiving circuit.
  • the apparatus 700 when the apparatus 700 is implementing the function of the first node, it may specifically be:
  • the processing unit 701 is configured to determine that the routing node needs to be adjusted; the communication unit 702 is configured to send context request information to the source routing node, where the context request information is used to request the first routing context in the source routing node; The source routing node receives the first routing context; the processing unit 701 is further configured to determine a target routing node; the communication unit 702 is further configured to send a second routing context to the target routing node, and the first routing context The second routing context is determined based on the first routing context.
  • processing unit 701 determines that the routing node needs to be adjusted, it is specifically configured to:
  • the routing node After determining that the device needs to be switched, it is determined that the routing node needs to be adjusted according to at least one of the terminal device grouping information, the packet-bound routing node information, or the device topology structure.
  • the context request information includes a terminal device group identifier and/or an identifier of a first type of terminal device, and the first type of terminal device is a currently valid terminal device in a device switching scenario or It is the terminal device that is currently disabled.
  • the processing unit 701 is further configured to: determine the currently valid terminal device and the currently invalid terminal device according to the device topology structure before the routing node adjustment and the device topology structure after the routing node adjustment .
  • the first routing context includes a first address mapping relationship
  • the first address mapping relationship includes a mapping relationship between an address of a terminal device and a radio bearer identifier.
  • the first address mapping relationship further includes a logical channel identifier.
  • the processing unit 701 determines the second routing context based on the first routing context, it is specifically configured to: replace the radio bearer identifier in the first address mapping relationship with The new radio bearer identifier obtains the second routing context, where the new radio bearer identifier is allocated by the first node.
  • the communication unit 702 is further configured to: send deletion instruction information to the source routing node, where the deletion instruction information includes the terminal device group identifier and/or the first type of terminal device
  • the first type of terminal device is a currently valid terminal device or a currently invalid terminal device in a device switching scenario, and the deletion indication information is used to instruct the source routing node to delete the first routing context;
  • the source routing node receives deletion confirmation information.
  • the processing unit 701 is further configured to: the first node determines that the device switching has been completed.
  • the communication unit 702 is further configured to: send a terminal device grouping attribute to the target routing node, where the terminal device grouping attribute includes a routing indication, and the routing indication is used to indicate the The target routing node performs data exchange.
  • the embodiment of the present application also provides a device, which is applied to a source routing node.
  • the device may specifically be a processor in a source routing node, or a chip or a chip system, or a functional module.
  • the apparatus 800 may include a processing unit 801 and a communication unit 802.
  • the communication unit 802 is used for the device 800 to receive information (or data) or send information (or data), and the processing unit 801 is used for controlling and managing the actions of the device 700.
  • the processing unit 801 may also be used to indicate the processing procedure involving the source routing node in any of the foregoing embodiments and/or other procedures of the technical solution described in this application.
  • the processing unit 801 can control the steps performed by the communication unit 802. For details, refer to the above-mentioned embodiment, and the repetitive parts will not be repeated here.
  • the above-mentioned processing unit 801 may be a processor or a processing circuit, etc.; the communication unit 802 may be a transceiver composed of a transmitter or a transmitting circuit, etc., and a receiver or a receiving circuit.
  • the apparatus 800 when the apparatus 800 is implementing the function of the source routing node, it may specifically be:
  • the communication unit 802 is configured to receive context request information from a first node, where the context request information is used to request the first routing context in the source routing node; the processing unit 801 is configured to determine the The first routing context; the communication unit 802 is further configured to send the first routing context to the first node.
  • the context request information includes a terminal device group identifier and/or an identifier of a first type of terminal device, and the first type of terminal device is a currently valid terminal device in a device switching scenario or Is a terminal device that is currently disabled;
  • the processing unit 801 when determining the first routing context according to the context request information, is specifically configured to: according to the terminal device group identification and/or the identification of the first type of terminal device Determine the first routing context.
  • the first routing context includes a first address mapping relationship
  • the first address mapping relationship includes a mapping relationship between an address of a terminal device and a radio bearer identifier.
  • the first address mapping relationship further includes a logical channel identifier.
  • the communication unit 802 is further configured to: receive deletion instruction information from the first node, where the deletion instruction information includes a terminal device group identifier and/or a terminal device of the first type. ID, the first type of terminal device is a currently valid terminal device or a currently invalid terminal device in a device switching scenario, and the deletion indication information is used to instruct the source routing node to delete the first routing context;
  • the processing unit 801 is further configured to: delete the first routing context according to the terminal device group identification and/or the identification of the first-type terminal device; the communication unit 802 is further configured to: send a deletion confirmation to the first node information.
  • an embodiment of the present application also provides a device, which is applied to a target routing node.
  • the device may specifically be a processor, a chip or a chip system, or a functional module in the target routing node.
  • the device 900 may include a processing unit 901 and a communication unit 902.
  • the communication unit 902 is used for the device 900 to receive information (or data) or send information (or data), and the processing unit 801 is used for controlling and managing the actions of the device 900.
  • the processing unit 901 may also be used to indicate the processing procedure involving the target routing node in any of the foregoing embodiments and/or other procedures of the technical solution described in this application.
  • the processing unit 901 may control the steps performed by the communication unit 902. For details, reference may be made to the foregoing embodiment, and the repetitions are not repeated here.
  • the above-mentioned processing unit 901 may be a processor or a processing circuit, etc.; the communication unit 902 may be a transceiver composed of a transmitter or a transmitting circuit, etc., and a receiver or a receiving circuit.
  • the device 900 when the device 900 is implementing the function of the target routing node, it may specifically be:
  • the communication unit 902 is configured to receive a second routing context from the first node, where the second routing context is determined based on the first routing context; the processing unit 901 is configured to determine a routing rule according to the second routing context.
  • the second routing context includes a second address mapping relationship
  • the second address mapping relationship includes a mapping relationship between an address of a terminal device and a radio bearer identifier, wherein the second address The mapping relationship is determined based on the first address mapping relationship in the first routing context.
  • the second address mapping relationship further includes a logical channel identifier.
  • the processing unit 901 determines the routing rule according to the second routing node, it is specifically configured to: determine the location according to the second address mapping relationship in the second routing context.
  • the routing rule; or, the second address mapping relationship is used as the routing rule.
  • the communication unit 902 is further configured to receive a terminal device grouping attribute from the first node, the terminal device grouping attribute includes a routing indication, and the routing indication is used to indicate the The target routing node performs data exchange; the processing unit 901 is further configured to determine the data exchange type according to the grouping attribute of the terminal device.
  • the routing instruction is an L2/L3 layer exchange instruction
  • the processing unit 901 is specifically configured to: according to the L2/L3 layer exchange type when determining the data exchange type according to the terminal device packet attribute
  • the L3 layer exchange instruction determines the data exchange type.
  • the division of units in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.
  • the functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the above-mentioned integrated unit can be implemented in the form of hardware or software functional unit.
  • the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of the present application essentially or the part that contributes to the existing technology or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , Including several instructions to make a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (processor) execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disks or optical disks and other media that can store program codes. .
  • the embodiment of the present application also provides a first node for implementing the communication method.
  • the first node 1000 may include a communication interface 1001 and a processor 1002.
  • the first node 1000 may further include a memory 1003.
  • the memory 1003 may be arranged inside the first node 1000, or may also be arranged outside the first node 1000.
  • the processor 1002 controls the communication interface 1001 to receive and send data, and is used to implement the method executed by the first node (for example, the host node) in FIGS. 4 to 6.
  • the processor 1002 may be a central processing unit (CPU), a network processor (NP), or a combination of a CPU and an NP.
  • the processor 1002 may further include a hardware chip.
  • the above-mentioned hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof.
  • the above-mentioned PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a general array logic (generic array logic, GAL), or any combination thereof.
  • the communication interface 1001, the processor 1002, and the memory 1003 are connected to each other.
  • the communication interface 1001, the processor 1002, and the memory 1003 are connected to each other through a bus 1004;
  • the bus 1004 may be a Peripheral Component Interconnect (PCI) bus or an extended industry standard Structure (Extended Industry Standard Architecture, EISA) bus, etc.
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • the bus can be divided into an address bus, a data bus, a control bus, and so on. For ease of representation, only one thick line is used to represent in FIG. 10, but it does not mean that there is only one bus or one type of bus.
  • the memory 1003 is used to store programs and the like.
  • the program may include program code, and the program code includes computer operation instructions.
  • the memory 1003 may include RAM, or may also include non-volatile memory, such as one or more disk memories.
  • the processor 1002 executes the application program stored in the memory 1003 to realize the above-mentioned functions, thereby realizing the communication method provided in the embodiment of the present application.
  • the first node when used to implement the communication method shown in FIG. 4, it may specifically include:
  • the processor 1002 is configured to determine that the routing node needs to be adjusted; the communication interface 1001 is configured to send context request information to the source routing node, where the context request information is used to request the first routing context in the source routing node; The source routing node receives the first routing context; the processor 1002 is further configured to determine a target routing node; the communication interface 1001 is further configured to send a second routing context to the target routing node, and the first routing context The second routing context is determined based on the first routing context.
  • the processor 1002 determines that the routing node needs to be adjusted, it is specifically configured to:
  • the routing node After determining that the device needs to be switched, it is determined that the routing node needs to be adjusted according to at least one of the terminal device grouping information, the packet-bound routing node information, or the device topology structure.
  • the context request information includes a terminal device group identifier and/or an identifier of a first type of terminal device, and the first type of terminal device is a currently valid terminal device in a device switching scenario or It is the terminal device that is currently disabled.
  • the processor 1002 is further configured to: determine the currently valid terminal device and the currently invalid terminal device according to the device topology structure before the routing node adjustment and the device topology structure after the routing node adjustment .
  • the first routing context includes a first address mapping relationship
  • the first address mapping relationship includes a mapping relationship between an address of a terminal device and a radio bearer identifier.
  • the first address mapping relationship further includes a logical channel identifier.
  • the processor 1002 determines the second routing context based on the first routing context, it is specifically configured to: replace the radio bearer identifier in the first address mapping relationship with The new radio bearer identifier obtains the second routing context, where the new radio bearer identifier is allocated by the first node.
  • the communication interface 1001 is further configured to: send deletion instruction information to the source routing node, where the deletion instruction information includes the terminal device group identifier and/or the first type of terminal device
  • the first type of terminal device is a currently valid terminal device or a currently invalid terminal device in a device switching scenario, and the deletion indication information is used to instruct the source routing node to delete the first routing context;
  • the source routing node receives deletion confirmation information.
  • the processor 1002 before determining the target routing node, is further configured to: the first node determines that the device switching is completed.
  • the communication interface 1001 is further configured to: send a terminal device grouping attribute to the target routing node, where the terminal device grouping attribute includes a routing indication, and the routing indication is used to indicate the The target routing node performs data exchange.
  • the embodiment of the present application also provides a source routing node for implementing the communication method.
  • the source routing node 1100 may include a communication interface 1101 and a processor 1102.
  • the source routing node 1100 may further include a memory 1103.
  • the memory 1103 may be provided inside the source routing node 1100, and may also be provided outside the source routing node 1100.
  • the processor 1102 controls the communication interface 1101 to receive and send data, and is used to implement the method executed by the source routing node (for example, the host node) in FIG. 4 to FIG. 6.
  • the processor 1102 may be a central processing unit (CPU), a network processor (NP), or a combination of a CPU and an NP.
  • the processor 1102 may further include a hardware chip.
  • the above-mentioned hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof.
  • the above-mentioned PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a general array logic (generic array logic, GAL), or any combination thereof.
  • the communication interface 1101, the processor 1102, and the memory 1103 are connected to each other.
  • the communication interface 1101, the processor 1102, and the memory 1103 are connected to each other through a bus 1104;
  • the bus 1104 may be a Peripheral Component Interconnect (PCI) bus or an extended industry standard Structure (Extended Industry Standard Architecture, EISA) bus, etc.
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • the bus can be divided into an address bus, a data bus, a control bus, and so on. For ease of representation, only one thick line is used to represent in FIG. 11, but it does not mean that there is only one bus or one type of bus.
  • the memory 1103 is used to store programs and the like.
  • the program may include program code, and the program code includes computer operation instructions.
  • the memory 1103 may include RAM, or may also include non-volatile memory, such as one or more disk memories.
  • the processor 1102 executes the application program stored in the memory 1103 to implement the foregoing functions, thereby implementing the communication method provided in the embodiment of the present application.
  • the source routing node when used to implement the communication method shown in FIG. 4, it may specifically include:
  • the communication interface 1101 is configured to receive context request information from a first node, where the context request information is used to request the first routing context in the source routing node; the processor 1102 is configured to determine the context request information according to the context request information The first routing context; the communication interface 1101 is also used to send the first routing context to the first node.
  • the context request information includes a terminal device group identifier and/or an identifier of a first type of terminal device, and the first type of terminal device is a currently valid terminal device in a device switching scenario or Is a terminal device that is currently disabled; the processor 1102, when determining the first routing context according to the context request information, is specifically configured to: according to the terminal device group identification and/or the identification of the first type of terminal device Determine the first routing context.
  • the first routing context includes a first address mapping relationship
  • the first address mapping relationship includes a mapping relationship between an address of a terminal device and a radio bearer identifier.
  • the first address mapping relationship further includes a logical channel identifier.
  • the communication interface 1101 is further configured to: receive deletion instruction information from the first node, where the deletion instruction information includes a terminal device group identifier and/or a terminal device of the first type. ID, the first type of terminal device is a currently valid terminal device or a currently invalid terminal device in a device switching scenario, and the deletion indication information is used to instruct the source routing node to delete the first routing context;
  • the processor 1102 is further configured to: delete the first routing context according to the terminal device group identification and/or the identification of the first-type terminal device; the communication interface 1101 is further configured to: send a deletion confirmation to the first node information.
  • the embodiments of the present application also provide a target routing node for implementing the communication method.
  • the target routing node 1200 may include a communication interface 1201 and a processor 1202.
  • the target routing node 1200 may further include a memory 1203.
  • the memory 1203 may be provided inside the target routing node 1200, and may also be provided outside the target routing node 1200.
  • the processor 1202 controls the communication interface 1201 to receive and send data, and is used to implement the method executed by the target routing node (for example, the host node) in FIGS. 4-6.
  • the processor 1202 may be a central processing unit (CPU), a network processor (NP), or a combination of a CPU and an NP.
  • the processor 1202 may further include a hardware chip.
  • the above-mentioned hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof.
  • the above-mentioned PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a general array logic (generic array logic, GAL), or any combination thereof.
  • the communication interface 1201, the processor 1202, and the memory 1203 are connected to each other.
  • the communication interface 1201, the processor 1202, and the memory 1203 are connected to each other through a bus 1204;
  • the bus 1204 may be a Peripheral Component Interconnect (PCI) bus or an extended industry standard Structure (Extended Industry Standard Architecture, EISA) bus, etc.
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • the bus can be divided into an address bus, a data bus, a control bus, and so on. For ease of presentation, only one thick line is used in FIG. 12 to represent it, but it does not mean that there is only one bus or one type of bus.
  • the memory 1203 is used to store programs and the like.
  • the program may include program code, and the program code includes computer operation instructions.
  • the memory 1203 may include RAM, or may also include non-volatile memory, such as one or more disk memories.
  • the processor 1202 executes the application program stored in the memory 1203 to realize the above-mentioned functions, thereby realizing the communication method provided in the embodiment of the present application.
  • the target routing node when used to implement the communication method shown in FIG. 4, it may specifically include:
  • the communication interface 1201 is configured to receive a second routing context from a first node, where the second routing context is determined based on the first routing context; the processor 1202 is configured to determine a routing rule according to the second routing context.
  • the second routing context includes a second address mapping relationship
  • the second address mapping relationship includes a mapping relationship between an address of a terminal device and a radio bearer identifier, wherein the second address The mapping relationship is determined based on the first address mapping relationship in the first routing context.
  • the second address mapping relationship further includes a logical channel identifier.
  • the processor 1202 determines the routing rule according to the second routing node, it is specifically configured to: determine the location according to the second address mapping relationship in the second routing context.
  • the routing rule; or, the second address mapping relationship is used as the routing rule.
  • the communication interface 1201 is further configured to receive a terminal device grouping attribute from the first node, the terminal device grouping attribute includes a routing indication, and the routing indication is used to indicate the The target routing node performs data exchange; the processor 1202 is further configured to determine the data exchange type according to the grouping attribute of the terminal device.
  • the routing instruction is an L2/L3 layer switching instruction
  • the processor 1202 is specifically configured to: according to the L2/L3 layer exchange type when determining the data exchange type according to the terminal device packet attribute
  • the L3 layer exchange instruction determines the data exchange type.
  • the embodiment of the present application also provides a computer-readable storage medium on which a computer program (or instruction) is stored.
  • a computer program or instruction
  • the computer executes the above method.
  • An operation performed by at least one of the first node, the source routing node, or the target routing node in any possible implementation manner of the embodiment and method embodiment.
  • this application also provides a computer program product, which when invoked and executed by a computer, enables the computer to implement the above method embodiment and any possible implementation of the method embodiment The operation performed by at least one of the first node, the source routing node, or the target routing node in.
  • this application also provides a chip or chip system, which is coupled with a memory, and is used to implement the above method embodiment and any one of the possible implementation manners of the method embodiment. , The operation performed by at least one of the source routing node or the target routing node.
  • the chip system may include the chip and components such as memory and communication interface.
  • this application can be provided as methods, systems, or computer program products. Therefore, this application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, this application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device.
  • the device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.
  • These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment.
  • the instructions provide steps for implementing the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

Landscapes

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

Abstract

一种通信方法及装置，用以实现在切换场景中，以减少因重新选择路由节点导致的信令开销以及时延。该方法包括：第一节点确定路由节点需要调整后，向源路由节点发送上下文请求信息，上下文请求信息用于请求源路由节点中的第一路由上下文；第一节点从源路由节点接收第一路由上下文；第一节点确定目标路由节点，并向目标路由节点发送第二路由上下文，第二路由上下文是基于第一路由上下文确定的。这样，在切换场景中，在设备切换时，第一节点获取到源路由节点中的路由上下文后处理并发送给重选的路由节点，实现信息的有效共享，而不需要重选的路由节点去重新学习或获取，从而可以减少重复的规则学习计算和时延开销。

Description

一种通信方法及装置 技术领域
本申请涉及通信技术领域，尤其涉及一种通信方法及装置。
背景技术
目前，为了满足工业制造等场景中超低时延的需求，结合了接入回传一体化技术(integrated access backhaul，IAB)和核心网架构，对需要进行数据传输的终端设备等通信设备之间构建本地路由。在构建本地路由的过程中，本地路由节点(一般是IAB节点)需要进行地址学习，以明确终端设备的地址和无线承载与传输协议之间的映射关系，以使后续完成数据传输。
具体的，当前本地路由节点即IAB节点获取上述映射关系的方式主要有两种：(1)每个终端设备发送上行数据流时，IAB节点解析数据包后获得媒体介入控制(medium access control，MAC)地址/互联网协议(internet protocol，IP)地址，并根据数据无线承载(data radio bearer，DRB)与无线链路控制层协议(radio link control，RLC)信息构建映射关系；(2)IAB节点通过广播的方式主动向终端设备学习其MAC地址/IP地址，并根据传输的DRB与RLC信息构建映射关系。
但是，在切换场景中，需要重新选择本地路由节点，重新选择的本地路由节点需要重新广播学习上述映射关系或者等待终端设备发送上行数据包被动学习上述映射关系，前者会造成大量的信令开销，后者会造成较高的时延。
发明内容
本申请提供一种通信方法及装置，用以实现在切换场景中，以减少因重新选择路由节点导致的信令开销以及时延。
第一方面，本申请提供了一种通信方法，该方法包括：第一节点确定路由节点需要调整后，向源路由节点发送上下文请求信息，所述上下文请求信息用于请求所述源路由节点中的第一路由上下文；所述第一节点从所述源路由节点接收所述第一路由上下文；所述第一节点确定目标路由节点，并向所述目标路由节点发送第二路由上下文，所述第二路由上下文是基于所述第一路由上下文确定的。
通过上述方法，在切换场景中，在设备切换时，第一节点获取到源路由节点中的路由上下文后处理并发送给重选的路由节点，实现信息的有效共享，而不需要重选的路由节点去重新学习或获取，从而可以减少重复的规则学习计算和时延开销。
在一个可能的设计中，所述第一节点确定路由节点需要调整，具体方法可以为：所述第一节点确定设备需要切换后，根据终端设备分组信息、分组绑定的路由节点的信息或设备拓扑结构中的至少一项判定路由节点需要调整。这样所述第一节点可以准确地确定路由节点需要调整，以触发后续请求第一路由上下文。
在一个可能的设计中，所述上下文请求信息中包含终端设备分组标识和/或第一类终端设备的标识，所述第一类终端设备为设备切换场景中当前有效的终端设备或者为当前失效的终端设备。这样可以使所述源路由节点根据所述上下文请求信息中的信息准确地确定所 述第一路由上下文。
在一个可能的设计中，所述第一节点根据路由节点调整前的设备拓扑结构和路由节点调整后的设备拓扑结构，确定当前有效的终端设备和当前无效的终端设备。这样所述第一节点可以准确地获知哪些终端设备在切换场景中没有受影响，以便请求获取这些终端设备的路由上下文。
在一个可能的设计中，所述第一路由上下文包含第一地址映射关系，所述第一地址映射关系包含终端设备的地址和无线承载标识的映射关系。
在一个可能的设计中，所述第一地址映射关系中还包含逻辑信道标识。
在一个可能的设计中，所述第一节点基于所述第一路由上下文确定所述第二路由上下文，具体方法可以为：所述第一节点将所述第一地址映射关系中无线承载标识替换成新的无线承载标识，得到所述第二路由上下文，其中新的无线承载标识是所述第一节点分配的。这样可以在设备切换后生成当前所需的路由上下文以便实现数据传输。
在一个可能的设计中，所述第一节点向所述源路由节点发送删除指示信息，所述删除指示信息中包含终端设备分组标识和/或第一类终端设备的标识，所述第一类终端设备为设备切换场景中当前有效的终端设备或者为当前失效的终端设备，所述删除指示信息用于指示所述源路由节点删除所述第一路由上下文；所述第一节点从所述源路由节点接收删除确认信息。这样可以使源路由节点减少资源占用。
在一个可能的设计中，在所述第一节点确定目标路由节点之前，所述第一节点确定设备切换已完成。这样可以保证由目的路由节点完成后续操作。
在一个可能的设计中，所述第一节点向所述目标路由节点发送终端设备分组属性，所述终端设备分组属性包括路由指示，所述路由指示用于指示所述目标路由节点进行数据交换。这样可以使目的路由节点准确实现数据交换。
第二方面，本申请提供了一种通信方法，该方法包括：源路由节点从第一节点接收上下文请求信息，所述上下文请求信息用于请求所述源路由节点中的第一路由上下文；所述源路由节点根据所述上下文请求信息确定所述第一路由上下文；所述源路由节点向所述第一节点发送所述第一路由上下文。
通过上述方法，在切换场景中，在设备切换时，可以使第一节点获取到源路由节点中的路由上下文后处理并发送给重选的路由节点，实现信息的有效共享，而不需要重选的路由节点去重新学习或获取，从而可以减少重复的规则学习计算和时延开销。
在一个可能的设计中，所述上下文请求信息中包含终端设备分组标识和/或第一类终端设备的标识，所述第一类终端设备为设备切换场景中当前有效的终端设备或者为当前失效的终端设备；所述源路由节点根据所述上下文请求信息确定所述第一路由上下文，包括：所述源路由节点根据所述终端设备分组标识和/或第一类终端设备的标识确定所述第一路由上下文。这样可以使所述源路由节点根据所述上下文请求信息中的信息准确地确定所述第一路由上下文。
在一个可能的设计中，所述第一路由上下文包含第一地址映射关系，所述第一地址映射关系包含终端设备的地址和无线承载标识的映射关系。
在一个可能的设计中，所述第一地址映射关系中还包含逻辑信道标识。
在一个可能的设计中，所述源路由节点从所述第一节点接收删除指示信息，所述删除指示信息中包含终端设备分组标识和/或第一类终端设备的标识，所述第一类终端设备为设 备切换场景中当前有效的终端设备或者为当前失效的终端设备，所述删除指示信息用于指示所述源路由节点删除所述第一路由上下文；所述源路由节点根据所述终端设备分组标识和/或第一类终端设备的标识删除所述第一路由上下文；所述源路由节点向所述第一节点发送删除确认信息。这样可以使源路由节点减少资源占用。
第三方面，本申请提供了一种通信方法，该方法包括：目标路由节点从第一节点接收第二路由上下文，所述第二路由上下文是基于所述第一路由上下文确定的；所述目标路由节点根据所述第二路由上下文确定路由规则。
通过上述方法，在切换场景中，在设备切换时，可以实现信息的有效共享，而不需要重选的路由节点去重新学习或获取，从而可以减少重复的规则学习计算和时延开销。
在一个可能的设计中，所述第二路由上下文包含第二地址映射关系，所述第二地址映射关系包含终端设备的地址和无线承载标识的映射关系，其中，所述第二地址映射关系是基于所述第一路由上下文中的第一地址映射关系确定的。
在一个可能的设计中，所述第二地址映射关系中还包含逻辑信道标识。
在一个可能的设计中，所述目标路由节点根据所述第二路由节点确定路由规则，具体方法可以为：所述目标路由节点根据所述第二路由上下文中的所述第二地址映射关系确定所述路由规则；或者，所述目标路由节点将所述第二地址映射关系作为所述路由规则。这样所述目标路由节点可以准确地确定设备切换后的路由规则，以实现后续路由过程。
在一个可能的设计中，所述目标路由节点从所述第一节点接收终端设备分组属性，所述终端设备分组属性包括路由指示，所述路由指示用于指示所述目标路由节点进行数据交换；所述目标路由节点根据所述终端设备分组属性确定数据交换类型。这样可以根据数据交换类型准确地进行数据交换。
在一个可能的设计中，所述路由指示为L2/L3层交换指示，所述目标路由节点根据所述终端设备分组属性确定数据交换类型，具体方法可以为：所述目标路由节点根据所述L2/L3层交换指示确定所述数据交换类型。这样可以准确地确定数据交换类型。
第四方面，本申请还提供了一种第一节点，该第一节点具有实现上述第一方面方法实例中第一节点行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，所述第一节点的结构中包括处理单元和通信单元，这些单元可以执行上述第一方面方法示例中的相应功能，具体参见方法示例中的详细描述，此处不做赘述。
在一个可能的设计中，所述第一节点的结构中包括通信接口和处理器，可选的还包括存储器，所述通信接口用于收发数据，以及用于与通信系统中的其他设备进行通信交互，所述处理器被配置为支持所述第一节点执行上述第一方面方法中相应的功能。所述存储器与所述处理器耦合，其保存所述第一节点必要的程序指令和数据。
第五方面，本申请还提供了一种源路由节点，该源路由节点具有实现上述第二方面方法实例中源路由节点行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，所述源路由节点的结构中包括处理单元和通信单元，这些单元可以执行上述第二方面方法示例中的相应功能，具体参见方法示例中的详细描述，此处不做赘述。
在一个可能的设计中，所述源路由节点的结构中包括通信接口和处理器，可选的还包括存储器，所述通信接口用于收发数据，以及用于与通信系统中的其他设备进行通信交互，所述处理器被配置为支持所述源路由节点执行上述第二方面方法中相应的功能。所述存储器与所述处理器耦合，其保存所述源路由节点必要的程序指令和数据。
第六方面，本申请还提供了一种目标路由节点，该目标路由节点具有实现上述第三方面方法实例中目标路由节点行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，所述目标路由节点的结构中包括处理单元和通信单元，这些单元可以执行上述第三方面方法示例中的相应功能，具体参见方法示例中的详细描述，此处不做赘述。
在一个可能的设计中，所述目标路由节点的结构中包括通信接口和处理器，可选的还包括存储器，所述通信接口用于收发数据，以及用于与通信系统中的其他设备进行通信交互，所述处理器被配置为支持所述目标路由节点执行上述第三方面方法中相应的功能。所述存储器与所述处理器耦合，其保存所述目标路由节点必要的程序指令和数据。
第七方面，本申请还提供了一种通信系统，该通信系统包括第一节点，所述第一节点可用于执行上述第一方面及第一方面的任一方法中第一节点执行的步骤。在一个可能的设计中，所述通信系统还可以包括源路由节点，所述源路由节点可用于执行上述第二方面及第二方面的任一方法中源路由节点执行的步骤。在一个可能的设计中，所述通信系统还可以包括目标路由节点，所述目标路由节点可用于执行上述第三方面及第三方面的任一方法中目标路由节点执行的步骤。在一个可能的设计中，该通信系统还可以包括本申请实施例提供的方案中与第一节点、源路由节点或目标路由节点中的至少一个进行交互的其他设备等等。
第八方面，本申请还提供了一种通信系统，该通信系统包括源路由节点，所述源路由节点可用于执行上述第二方面及第二方面的任一方法中源路由节点执行的步骤。在一个可能的设计中，所述通信系统还可以包括第一节点，所述第一节点可用于执行上述第一方面及第一方面的任一方法中第一节点执行的步骤。在一个可能的设计中，所述通信系统还可以包括目标路由节点，所述目标路由节点可用于执行上述第三方面及第三方面的任一方法中目标路由节点执行的步骤。在一个可能的设计中，该通信系统还可以包括本申请实施例提供的方案中与源路由节点、第一节点或目标路由节点中的至少一个进行交互的其他设备等等。
第九方面，本申请还提供了一种通信系统，该通信系统包括目标路由节点，所述目标路由节点可用于执行上述第三方面及第三方面的任一方法中目标路由节点执行的步骤。在一个可能的设计中，所述通信系统还可以包括第一节点，所述第一节点可用于执行上述第一方面及第一方面的任一方法中第一节点执行的步骤。在一个可能的设计中，所述通信系统还可以包括源路由节点，所述源路由节点可用于执行上述第二方面及第二方面的任一方法中源路由节点执行的步骤。在一个可能的设计中，该通信系统还可以包括本申请实施例提供的方案中与目标路由节点、第一节点或源路由节点中的至少一个进行交互的其他设备等等。
第十方面，本申请还提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机可执行指令，所述计算机可执行指令在被所述计算机调用时用于使所述计算机 执行上述任一种方法。
第十一方面，本申请还提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述任一种方法。
第十二方面，本申请还提供了一种芯片，所述芯片与存储器耦合，用于读取并执行所述存储器中存储的程序指令，以实现上述任一种方法。
附图说明
图1为本申请提供的一种通信系统的结构示意图；
图2为本申请提供的一种场景的示意图；
图3为本申请提供的另一种场景的示意图；
图4为本申请提供的一种通信方法的流程图；
图5为本申请提供的一种通信方法的示例的流程图；
图6为本申请提供的另一种通信方法的示例的流程图；
图7为本申请提供的一种装置的结构示意图；
图8为本申请提供的另一种装置的结构示意图；
图9为本申请提供的另一种装置的结构示意图；
图10为本申请提供的一种第一节点的结构图；
图11为本申请提供的一种源路由节点的结构图；
图12为本申请提供的一种目标路由节点的结构图。
具体实施方式
下面将结合附图，对本申请实施例进行详细描述。
本申请实施例提供一种通信方法及装置，用以实现在切换场景中，以减少因重新选择路由节点导致的信令开销以及时延。
在本申请的描述中，“第一”、“第二”等词汇，仅用于区分描述的目的，而不能理解为指示或暗示相对重要性，也不能理解为指示或暗示顺序。
应理解，本申请实施例中“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A、B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。“以下至少一(项)个”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a、b或c中的至少一项(个)，可以表示：a，b，c，a和b，a和c，b和c，或a、b和c，其中a、b、c可以是单个，也可以是多个。
IAB节点是中继节点的特定的名称，不对本申请的方案构成限定，可以是一种具有转发功能的上述基站或者终端设备中的一种，也可以是一种独立的设备形态。例如，本申请的IAB节点也可以被称为中继节点(relay node,RN)、传输接收点(transmission and reception point)、中继发送接收点(relaying TRP)等。
为了更加清晰地描述本申请实施例的技术方案，下面结合附图，对本申请实施例提供的通信方法及装置进行详细说明。
本申请提供的通信方法适用的一种可能的通信系统的架构，所述通信系统的架构中可以包括本地网络、核心网网络、一个或多个IAB宿主节点(IAB donor)、一个或多个IAB节点和一个或多个终端设备。其中，图1示出了所述通信系统的架构的一种可能的示例。应理解，本申请实施例并不限于图1所示通信系统，图1中所示的设备或节点的名称在这里仅作为一种示例说明，并不作为对本申请的方法适用的通信系统的架构中包括的设备的限定。下面对所述通信系统中的各个节点或设备的功能进行详细描述：
所述本地网络，也即数据网络(data network，DN)，可以是工业以太数据网络，还可以是互联网协议(internet protocol，IP)数据网络，当然还可以是其他网络，本申请此处不再一一列举。
所述核心网网络(core network，CN)中分布了多个功能网元，例如，5G中的接入和移动性管理功能网元(access and mobility management function，AMF)、会话管理功能网元(session management function，SMF)、用户面功能网元(user plane function，UPF)等等，此处不再一一列举。例如，在图1中，所述核心网网络以CN示出。
所述IAB宿主节点，负责管理所有的IAB节点，可以学习到IAB节点和/或终端设备的拓扑结构。所述IAB宿主节点可以由集中式单元中的控制面(centralized unit-control plane，CU-CP)和集中式单元中的用户面(centralized unit-user plane，CU-UP)模块组成。示例性的，图1中示出了IAB宿主节点1、IAB宿主节点2。
所述IAB节点，包含分布单元(distributed unit,DU)和移动终端(mobile termination,MT)模块。多个IAB节点之间采用生成树(spanning tree，ST)或者有向无环图(directed acyclic graph,DAG)的方式进行级联，在级联时每个IAB节点需要完成非接入层(non-access stratum，NAS)鉴权，以及通过会话完成操作维护管理(operation administration and maintenance，OAM)配置。所述IAB节点具备CU-UP的能力，即具备分组数据协议(packet data convergence protocol，PDCP)和服务数据适配协议(service data adaptation protocol，SDAP)的协议栈；如果存在接口，IAB节点可以直接转发数据到本地以太网数据网络或者IP数据网络。示例性的，图1中示出了IAB节点1、IAB节点2。
所述终端设备，又可以称为用户设备(user equipment，UE)、移动台(mobile station，MS)、移动终端(mobile terminal，MT)等，是一种向用户提供语音和/或数据连通性的设备，所述终端设备与接入网设备之间采用某种空口技术相互通信。目前，所述终端设备可以是：手持终端、笔记本电脑、用户单元(subscriber unit，SU)、蜂窝电话(cellular phone)、智能电话(smart phone)、无线数据卡、个人数字助理(personal digital assistant，PDA)电脑、平板型电脑、无线调制解调器(modem)、手持设备(handheld)、膝上型电脑(laptop computer)、无绳电话(cordless phone)或者无线本地环路(wireless local loop，WLL)台、机器类型通信(machine type communication，MTC)终端或是其他可以接入网络的设备。其中，图1中所述终端设备以UE示出，例如图1中的UE1、UE2、UE3，仅作为示例，并不对终端设备进行限定。
需要说明的是，图1所示的通信系统的架构中不限于仅包含图中所示的节点或设备，还可以包含其它未在图中表示的设备，具体本申请在此处不再一一列举。
需要说明的是，本申请实施例并不限定各个节点或设备的分布形式，图1所示的分布形式只是示例性的，本申请不作限定。
应理解，本申请中所有节点或设备的名称仅仅作为示例，在未来通信中还可以称为其 它名称，或者在未来通信中本申请涉及的节点或设备还可以通过其它具有相同功能的实体或者设备等来替代，本申请对此均不作限定。这里做统一说明，后续不再赘述。
需要说明的是，图1所示的通信系统并不构成本申请实施例能够适用的通信系统的限定。图1所示的通信系统架构为5G系统架构，可选的，本申请实施例的方法还适用于未来的各种通信系统，例如6G或者其他通信网络等。
基于上述通信系统的架构，示例性的介绍以下两种可能的切换场景：
例如图2示出了一个可能的场景。在该场景中，假设UE1和UE2建立了本地路由，本地路由节点为IAB节点1。即UE1与UE2通讯(也称通信)时仅需要经过IAB节点1中转，不需要再途径IAB宿主节点、CN以及本地网络。例如，UE1和UE2的路由途径如图2中的(a)所示。当UE1移动后切换到IAB节点2下时，IAB宿主节点1重新根据拓扑信息重新选择本地路由节点，当IAB宿主节点1确定本身为新的本地路由节点时，可以如图2中(b)所示。
例如图3示出了另一个可能的场景。在该场景中，UE1和UE3已经构建了本地路由，本地路由节点为IAB宿主节点1。例如，UE1和UE3的路由途径如图3中的(a)所示。当拓扑结构中的节点因为负载或者链路状况，需要进行调整时，节点之间的拓扑关系会发生改变，这样本地路由节点也可能发生改变；例如，若因为IAB宿主节点1和IAB节点2之间的链路状况变差，IAB-节点2可能重新选择IAB-节点1为父节点，此时新的本地路由节点变化为IAB-节点1，例如图3中的(b)所示。
在上述两种场景中，在本地路由节点变化之后，均需要重新构建本地路由规则。按照现有方法，新的本地路由节点要么通过广播的方式重新获取路由地址相关的映射关系，要么等待UE发送上行数据时学习上述映射关系，这样会造成大量的信令开销或者额外的时延。基于此，本申请提出了一种通信方法，来实现信息的有效共享，减少重复的规则学习计算和时延开销。
本申请实施例提供的一种通信方法，适用于如图1所示的通信系统。参阅图4所示，该方法的具体流程可以包括：
步骤401：第一节点确定路由节点需要调整后，向源路由节点发送上下文请求信息，所述上下文请求信息用于请求所述源路由节点中的第一路由上下文。
具体的，所述第一节点可以为IAB宿主节点，在本申请具体实施时所述第一节点的操作可以是所述第一节点中的CU执行的。
示例性的，所述第一节点确定路由节点需要调整，具体方法可以为：所述第一节点确定设备需要切换后，根据终端设备分组信息、分组绑定的路由节点的信息或设备拓扑结构中的至少一项判定路由节点需要调整。
其中，在本申请中设备需要切换可以包括终端设备需要切换的情况和IAB节点需要切换的情况。具体的，所述第一节点确定设备需要切换具体方法可以为：所述第一节点从源IAB节点接收测量报告，所述第一节点根据所述测量报告和切换阈值确定设备需要切换。其中，所述源IAB节点是终端设备切换场景中终端设备切换之前连接的IAB节点，或者是IAB节点切换场景中将要切换的IAB节点在切换之前连接的IAB节点或IAB宿主节点。需要说明的是，在本申请中，任一个IAB节点执行的操作可以是通过该IAB节点中的DU或者MT来执行的。
在一种可选的实施方式中，所述终端设备分组信息可以包括终端设备分组标识(group (identity，ID))、终端设备分组成员标识列表等等。
具体的，核心网网元在接收到本地路由请求后，获取需要本地路由的一组终端设备的标识，并用唯一标识标记终端设备分组，即为所述终端设备分组标识。所述第一节点可以从所述核心网网元获取上述信息。
在一种具体的实施方式中，所述设备拓扑结构为一个或多个终端设备、一个或多个IAB节点以及一个或多个IAB宿主节点分布的拓扑结构。
示例性的，所述上下文请求信息中可以包含终端设备分组标识和/或第一类终端设备的标识，所述第一类终端设备为设备切换场景中当前有效的终端设备或者为当前失效的终端设备。其中，当终端设备发生切换或者IAB节点发生切换时，设备拓扑结构会发生改变，路由节点可能需要调整。此时，终端设备分组中的部分终端设备的地址映射关系会发生变化，部分终端设备的地址映射关系没有发生变化。因此，这里所述当前有效的终端设备是指上述描述的地址映射关系没有发生变化的终端设备，所述当前失效的终端设备是指上述描述的地址映射关系发生了变化的终端设备。
在一种可能的情况中，当所述上下文请求信息中包含的是当前失效的终端设备的标识时，则指示所述源路由节点忽略该终端设备的上下文，也即不需要获取该终端设备的上下文，指示所述源路由节点发送该终端设备所在的终端设备分组中除这些终端设备以外的终端设备的上下文，也即终端设备分组中除这些终端设备以外的终端设备的上下文为所述第一路由上下文。
在另一种可能的情况中，当所述上下文请求信息中包含的是当前有效的终端设备的标识，则指示所述源路由节点可以仅发送该终端设备的上下文，也即该终端设备的上下文是所述第一路由上下文。
具体的，所述第一节点包含全局的设备拓扑结构，以及终端设备分组信息，当终端设备或者IAB节点切换时，所述第一节点能够确定拓扑结构发生变化，所述第一节点确定路由节点调整后，对于路由节点调整前的设备拓扑结构和路由节点调整后的设备拓扑结构来确定哪些终端设备有效，以及哪些终端设备无效。
可选的，任一个终端设备的标识可以通过以下其中一种表示：DRB标识，信号无线承载(Signaling Radio Bearer，SRB)标识，小区无线网络临时标识(cell radio network temporary identifier，C-RNTI)等等。
在一种具体的实施方式中，所述第一路由上下文包含第一地址映射关系，所述第一地址映射关系包含终端设备的地址和无线承载标识的映射关系。其中，无线承载标识可以是DRB标识或者SRB标识或者C-RNTI。终端设备的地址可以是MAC地址或者IP地址。具体的，所述第一路由上下文中包含的第一地址映射关系是在设备切换前用于终端设备的数据传输的映射关系。所述第一路由上下文主要是在设备切换后，地址映射关系没有受影响的终端设备的上下文，也即上述涉及的当前有效的终端设备的上下文。
进一步地，所述第一地址映射关系中还可以包含逻辑信道标识。其中，所述逻辑信道标识可以为RLC标识等。
在本申请中，所述第一节点可以通过F1-应用协议请求信息(F1-(application protocol，AP)request message)向所述源路由节点发送所述上下文请求信息。
步骤402：所述源路由节点根据所述上下文请求信息确定所述第一路由上下文。
具体的，所述源路由节点可以根据所述上下文请求信息中包含的终端设备分组标识和 /或第一类终端设备的标识确定所述第一路由上下文。
示例性的，所述源路由节点本地上下文中包含了终端设备分组标识，以及终端设备分组内终端设备的标识，当所述第一节点向所述源路由节点发送了终端设备分组标识和当前无效的终端设备的标识时，所述源路由节点排除这些无效的终端设备的标识，剩下的终端设备则为有效的终端设备，进而可以确定当前有效的终端设备的上下文，然后可以把有效的终端设备的上下文返回给所述第一节点。
步骤403：所述源路由节点向所述第一节点发送所述第一路由上下文。
具体的，所述源路由节点可以通过F1-AP响应消息(F1-AP response message)向所述第一节点发送所述第一路由上下文。
在一种可选的实施方式中，在所述第一节点收到所述第一路由上下文后，所述第一节点向所述源路由节点发送删除指示信息，所述删除指示信息中包含终端设备分组标识和/或第一类终端设备的标识，所述第一类终端设备为设备切换场景中当前有效的终端设备或者为当前失效的终端设备，所述删除指示信息用于指示所述源路由节点删除所述第一路由上下文；所述源路由节点根据所述删除指示信息中包含的终端设备分组标识和/或第一类终端设备的标识删除所述第一路由上下文，恢复作为路由节点之前的传输路径；然后所述源路由节点向所述第一节点发送删除确认信息。
具体的，所述第一节点同样可以通过F1-AP request message向所述源路由节点发送所述删除指示信息；所述源路由节点可以通过F1-AP response message向所述第一节点发送所述删除确认信息。
步骤404：所述第一节点确定目标路由节点。
具体的，所述第一节点在确定所述目标路由节点之前，确定设备切换已完成。可以理解为是因为设备切换触发了路由节点的重新选择。
示例性的，所述第一节点确定所述目标路由节点，具体方法可以为：所述第一节点根据切换完成的设备拓扑结构、设定策略选择所述目标路由节点。例如，所述设定策略可以是选择通信的两个终端设备的最小公共父节点。
之后，所述第一节点将终端设备分组标识和所述目标路由节点进行关联。
步骤405：所述第一节点向所述目标路由节点发送第二路由上下文，所述第二路由上下文是基于所述第一路由上下文确定的。
一种可能的实现方式中，所述第一节点基于所述第一路由上下文确定所述第二路由上下文时，将所述第一地址映射关系中无线承载标识替换成新的无线承载标识，得到所述第二路由上下文，其中新的无线承载标识是所述第一节点分配的。具体的，所述第一节点包含全局的设备拓扑，在所述第一节点设备拓扑发生变化后可以为终端设备分配新的无线承载标识。
示例性的，所述第一节点具体可以是根据所述第一路由上下文中第一地址映射关系中无线承载标识确定所述第二路由上下文。例如，如果终端设备的无线承载ID发生改变，所述第一节点需要将第一地址映射关系中的旧无线承载ID替换成新无线承载ID，从而得到所述第二路由上下文。
具体的，当终端设备的标识为C-RNTI时，所述第一节点可以根据所述C-RNTI确定所述新无线承载ID。
步骤406：所述目标路由节点根据所述第二路由上下文确定路由规则。
其中，所述第二路由上下文中包含由第一地址映射关系得到的第二地址映射关系，例如，第二地址映射关系为所述第一地址映射关系中的旧无线承载ID替换成新无线承载ID得到的。所述第二映射关系可以作为所述路由规则，或者可以根据所述第二映射关系确定所述路由规则。
在一种可选的实施方式中，所述第一节点向所述目标路由节点发送终端设备分组属性，所述终端设备分组属性包括路由指示，所述路由指示用于指示所述目标路由节点进行数据交换；然后所述目标路由节点根据所述终端设备分组属性确定数据交换类型。
其中，所述路由指示可以是L2/L3层交换指示。这里L2指的是开放式系统互联(open system interconnect，OSI)七层模型中MAC层，L3层指的是OSI七层模型中的IP层，用于指示本地交换是基于MAC层进行交换还是IP层进行交换。所述数据交换类型也即设备组内通信的业务模式。
其中，核心网网元在接收到本地路由请求后，根据本地路由请求中获取所述分组属性，例如分组的服务类型，或者转发指示(也即L2/L3层交换指示)等。
具体的，所述目标路由节点根据所述L2/L3层交换指示确定所述数据交换类型。
示例性的，所述分组属性中还可以包含设备分组关联的DNN信息，设备分组成员的PDU会话类型信息。
例如，在一个具体的场景中，例如IAB节点直接到工业以太网/IP网络的场景下，如果本地路由规则需要直接进行转发，则目标节点进一步根据L2/L3层交换指示信息进行如下处理：(1)L2层指示，需要剥离数据包的PDCP/SDAP报文头，按照交换机转发方式转发到工业以太网/IP网络；(2)L3层指示，需要剥离数据包的PDCP/SDAP报文头，如果存在MAC头，则剥离MAC头后按照路由器方式转发到工业以太网/IP网络。
采用本申请提供的通信方法，在切换场景中，在设备切换时，第一节点获取到源路由节点中的路由上下文后处理并发送给重选的路由节点，实现信息的有效共享，而不需要重选的路由节点去重新学习或获取，从而可以减少重复的规则学习计算和时延开销。
基于上述实施例，下面以具体的示例，如图5和图6所示的实施例，对本申请实施例提供的通信方法进行详细说明。在以下的示例中，以终端设备为UE为例，宿主节点通过宿主节点-CU执行操作，IAB节点通过DU或者MT分别执行相应操作来进行说明。
如图5所示，示出了一种通信方法的示例，在该示例可以应用于图2中所示的UE切换的场景。在该示例中，当UE发生切换时，宿主节点主动向源路由节点请求本地路由上下文，并在UE切换完成后，向重新选择的目标路由节点发送路由上下文，以减少目标路由节点规则重新学习的计算和时延开销。其中该示例中源IAB(节点)是UE切换前连接的IAB节点，目标IAB(节点)是UE切换后连接的IAB节点。具体的，该示例的具体流程可以包括以下步骤：
步骤501：UE移动时发送测量报告给源IAB节点(实际是发送给源IAB节点的DU，在图5中源IAB节点这里以源IAB-DU示出)。
所述源IAB节点为所述UE在移动前连接的IAB节点。
步骤502：源IAB节点将所述测量报告发送给宿主节点(实际是发送给宿主节点的CU，在图5中宿主节点以宿主节点-CU示出)。
其中，所述宿主节点是管理所述UE切换前后连接的IAB节点的节点，也即图4所示的实施例中涉及的第一节点。
步骤503：宿主节点-CU根据接收的所述测量报告以及切换阈值决定发起切换，同时根据UE分组信息(UE分组标识，UE分组成员标识列表等)、分组绑定信息(分组绑定的路由节点的信息)、UE/IAB节点拓扑结构判断本地路由需要调整。
步骤504：宿主节点-CU向源路由节点发送上下文请求信息，所述上下文请求信息用于请求所述源路由节点中的第一路由上下文。
具体的，所述上下文请求信息可以包括可以包含终端设备分组标识和/或第一类终端设备的标识，所述第一类终端设备为设备切换场景中当前有效的终端设备或者为当前失效的终端设备。其中，当终端设备发生切换时，设备拓扑结构会发生改变，路由节点可能需要调整。此时，终端设备分组中的部分终端设备的地址映射关系会发生变化，部分终端设备的地址映射关系没有发生变化。因此，这里所述当前有效的终端设备是指上述描述的地址映射关系没有发生变化的终端设备，所述当前失效的终端设备是指上述描述的地址映射关系发生了变化的终端设备。
在一种可能的情况中，当所述上下文请求信息中包含的是当前失效的终端设备的标识时，则指示所述源路由节点忽略该终端设备的上下文，也即不需要获取该终端设备的上下文，指示所述源路由节点发送该终端设备所在的终端设备分组中除这些终端设备以外的终端设备的上下文，也即终端设备分组中除这些终端设备以外的终端设备的上下文为所述第一路由上下文。
在另一种可能的情况中，当所述上下文请求信息中包含的是当前有效的终端设备的标识，则指示所述源路由节点可以仅发送该终端设备的上下文，也即该终端设备的上下文是所述第一路由上下文。
具体的，所述宿主节点-CU可以向所述源路由节点发送F1-AP请求消息，F1-AP请求消息中包含上下文请求信息(也可以称为本地路由上下文请求指示)。
示例性的，所述本地路由上下文请求指示，主要是请求获取源路由节点学习到的映射关系，也即图2所示的实施例中涉及的所述第一路由上下文中包含的第一地址映射关系。例如，所述第一地址映射关系可以为UE{MAC地址/IP地址}-DRB-RLC或者用户固定设备(customer premises equipment，CPE){MAC地址1/IP地址1，MAC地址2/IP地址2，…}-DRB-RLC。其中，CPE是UE的一种。
步骤505：源路由节点向宿主节点-CU发送F1-AP响应消息，F1-AP响应消息中包含第一路由上下文。
步骤506：宿主节点-CU在收到第一路由上下后，通过F1-AP消息向源路由节点发送删除指示信息，用于指示源路由节点删除第一路由上下文，恢复之前的传输路径。
所述删除指示信息中包含UE分组ID或者UE ID(例如，在该示例中UE ID是UE的DRB ID为例说明，但是应理解，这不作为对UE ID的限定)。
步骤507：源路由节点接收到删除指示信息后，根据删除指示信息中的UE分组ID或者DRB ID，删除相应的本地路由，并恢复之前的传输规则。这里也即所述源路由节点删除所述第一路由上下文。
步骤508：源路由节点删除完成后，通过F1-AP消息发送删除确认信息给宿主节点-CU。
步骤509：宿主节点-CU向目标IAB-DU发送UE上下文设置请求消息(UE context setup request)，以创建UE上下文并设置一个或多个数据承载。
其中，UE上下文设置请求消息中包括切换准备信息。
步骤510：目标IAB-DU向宿主节点-CU发送UE上下文设置响应消息(UE context setup response)。
步骤511：宿主节点-CU向源IAB-DU发送UE上下文修改请求消息(UE context modification request)。所述UE上下文修改请求消息中包括生成的无线资源控制重配置((radio resource control，RRC)reconfiguration)消息，并指示停止针对UE的数据传输。
示例性的，源IAB-DU还向宿主节点-CU发送下行链路数据传递状态帧(downlink data delivery status)，以通知宿主节点-CU有关未成功发送给UE的下行链路数据的信息。
步骤512：源IAB-DU将收到的RRC重配置(RRC reconfiguration)消息转发给UE。
步骤513：源IAB-DU向宿主节点-CU发送UE上下文修改响应消息(UE context modification response)。
步骤514：目标IAB-DU执行随机访问过程。
同时，目标IAB-DU向宿主节点-CU发送下行数据传送状态帧(downlink data delivery status)。宿主节点-CU向目标IAB-DU发送下行链路数据包(可能包括未在源IAB-DU中成功发送的PDCP分组数据单元(packet data unit，PDU)。
步骤515：UE向目标IAB-DU发送RRC重配置完成(RRC ReconfigurationComplete)消息。
步骤516：目标IAB-DU向宿主节点-CU发送上行RRC消息转移(UL RRC message transfer)消息，以传达接收到的RRC ReconfigurationComplete消息。
示例性的，目标IAB-DU向UE发送下行分组数据(downlink packets)。此外，UE通过目标IAB-DU向宿主节点-CU发送上行链路数据包。
步骤517：当宿主节点-CU已经完成UE的移动性切换，即UE已经切换到目标IAB-DU下，此时宿主节点-CU确定目标路由节点。
具体的，宿主节点-CU结合IAB拓扑信息(也即图4涉及的设备拓扑结构)，选择策略(也即图4所涉及的设定策略)选择目标路由节点(比如选择最小公共父节点)，并关联UE分组标识和选定的路由节点。
步骤518：宿主节点-CU发送向目标路由节点发送UE分组属性(L2/L3层交换指示)以及第二路由上下文。
其中第二路由上下文是宿主节点-CU根据第一路由上下文确定的，示例性的，所述宿主节点-CU根据新的IAB拓扑关系、第一路由上下文重新生成第二路由上下文。
步骤519：目标路由节点根据UE分组属性(L2/L3层交换指示)确定数据交换类型，然后根据第二路由上下文确定路由规则。
具体的，所述目标路由节点根据第二路由上下文以及本地的DRB-RLC信道关系构建新的本地路由，也即确定路由规则。
步骤520：宿主节点-CU向源IAB-DU发送UE上下文释放命令(UE context release command)消息。
步骤521：源IAB-DU释放UE上下文，并向宿主节点-CU发送UE上下文释放完成(UE context release complete)消息。
需要说明的是，在该示例中，以源IAB节点和源路由节点为两个设备进行说明的。应理解，在一些场景中，源IAB节点可以是源路由节点，也即源IAB节点和源路由节点为同一个节点，具体实现方法与上述示例类似，可以相互参见，此处不再详细说明。
如图6所示，示出了另一种通信方法的示例，在该示例可以应用于图3中所示的IAB节点切换的场景。在该示例中，当IAB节点发生切换时，宿主节点主动向源路由节点请求本地路由上下文，并在IAB节点切换完成后，向重新选择的目标路由节点发送路由上下文，以减少目标路由节点规则重新学习的计算和时延开销。在该示例中，迁移的IAB节点即发生切换的IAB节点，源IAB节点为迁移的IAB节点切换前连接的IAB节点，目标IAB节点为迁移的IAB节点切换后连接的IAB节点。具体的，该示例的具体流程可以包括以下步骤：
步骤601：迁移的IAB节点发送测量报告给源IAB节点(实际是发送给源IAB节点的DU，在图6中源IAB节点这里以源IAB-DU示出)。
具体的，迁移的IAB节点通过MT发送测量报告给源IAB节点，示例性的，在图6中以迁移的IAB-MT示出。
步骤602源IAB节点将所述测量报告发送给宿主节点(实际是发送给宿主节点的CU，在图6中宿主节点以宿主节点-CU示出)。
其中，所述宿主节点是管理所述UE切换前后连接的IAB节点的节点，也即图4所示的实施例中涉及的第一节点。
步骤603：宿主节点-CU根据接收的所述测量报告以及切换阈值决定发起切换，同时根据UE分组信息(UE分组标识，UE分组成员标识列表等)、分组绑定信息(分组绑定的路由节点的信息)、UE/IAB节点拓扑结构判断本地路由需要调整。
步骤604：宿主节点-CU向源路由节点发送上下文请求信息，所述上下文请求信息用于请求所述源路由节点中的第一路由上下文。
具体的，所述上下文请求信息可以包括可以包含终端设备分组标识和/或第一类终端设备的标识，所述第一类终端设备为设备切换场景中当前有效的终端设备或者为当前失效的终端设备。其中，当IAB节点发生切换时，设备拓扑结构会发生改变，路由节点可能需要调整。此时，终端设备分组中的部分终端设备的地址映射关系会发生变化，部分终端设备的地址映射关系没有发生变化。因此，这里所述当前有效的终端设备是指上述描述的地址映射关系没有发生变化的终端设备，所述当前失效的终端设备是指上述描述的地址映射关系发生了变化的终端设备。
在一种可能的情况中，当所述上下文请求信息中包含的是当前失效的终端设备的标识时，则指示所述源路由节点忽略该终端设备的上下文，也即不需要获取该终端设备的上下文，指示所述源路由节点发送该终端设备所在的终端设备分组中除这些终端设备以外的终端设备的上下文，也即终端设备分组中除这些终端设备以外的终端设备的上下文为所述第一路由上下文。
在另一种可能的情况中，当所述上下文请求信息中包含的是当前有效的终端设备的标识，则指示所述源路由节点可以仅发送该终端设备的上下文，也即该终端设备的上下文是所述第一路由上下文。
具体的，所述宿主节点-CU可以向所述源路由节点发送F1-AP请求消息，F1-AP请求消息中包含上下文请求信息(也可以称为本地路由上下文请求指示)。
示例性的，所述本地路由上下文请求指示，主要是请求获取源路由节点学习到的映射关系，也即图2所示的实施例中涉及的所述第一路由上下文中包含的第一地址映射关系。例如，所述第一地址映射关系可以为UE{MAC地址/IP地址}-DRB-RLC或者用户固定设备 (customer premises equipment，CPE){MAC地址1/IP地址1，MAC地址2/IP地址2，…}-DRB-RLC。其中，CPE是UE的一种。
步骤605：源路由节点向宿主节点-CU发送F1-AP响应消息，F1-AP响应消息中包含第一路由上下文。
步骤606：宿主节点-CU在收到第一路由上下后，通过F1-AP消息向源路由节点发送删除指示信息，用于指示源路由节点删除第一路由上下文，恢复之前的传输路径。
所述删除指示信息中包含UE分组ID或者UE ID(例如，在该示例中UE ID是UE的DRB ID为例说明，但是应理解，这不作为对UE ID的限定)。
步骤607：源路由节点接收到删除指示信息后，根据删除指示信息中的UE分组ID或者DRB ID，删除相应的本地路由，并恢复之前的传输规则。这里也即所述源路由节点删除所述第一路由上下文。
步骤608：源路由节点删除完成后，通过F1-AP消息发送删除确认信息给宿主节点-CU。
步骤609：宿主节点-CU向目标IAB-DU发送UE上下文设置请求消息(UE context setup request)，以创建UE上下文并设置一个或多个数据承载。
其中，UE上下文设置请求消息中包括切换准备信息。
步骤610：目标IAB-DU向宿主节点-CU发送UE上下文设置响应消息(UE context setup response)。
步骤611：宿主节点-CU向源IAB-DU发送UE上下文修改请求消息(UE context modification request)。所述UE上下文修改请求消息中包括生成的无线资源控制重配置((radio resource control，RRC)reconfiguration)消息，并指示停止针对UE的数据传输。
示例性的，源IAB-DU还向宿主节点-CU发送下行链路数据传递状态帧(downlink data delivery status)，以通知宿主节点-CU有关未成功发送给UE的下行链路数据的信息。
步骤612：源IAB-DU将收到的RRC重配置(RRC reconfiguration)消息转发给UE。
步骤613：源IAB-DU向宿主节点-CU发送UE上下文修改响应消息(UE context modification response)。
步骤614：目标IAB-DU执行随机访问过程。
同时，目标IAB-DU向宿主节点-CU发送下行数据传送状态帧(downlink data delivery status)。宿主节点-CU向目标IAB-DU发送下行链路数据包(可能包括未在源IAB-DU中成功发送的PDCP分组数据单元(packet data unit，PDU)。
步骤615：UE向目标IAB-DU发送RRC重配置完成(RRC ReconfigurationComplete)消息。
步骤616：目标IAB-DU向宿主节点-CU发送上行RRC消息转移(UL RRC message transfer)消息，以传达接收到的RRC ReconfigurationComplete消息。
示例性的，目标IAB-DU向UE发送下行分组数据(downlink packets)。此外，UE通过目标IAB-DU向宿主节点-CU发送上行链路数据包。
步骤617：当宿主节点-CU已经完成UE的移动性切换，即UE已经切换到目标IAB-DU下，此时宿主节点-CU确定目标路由节点。
具体的，宿主节点-CU结合IAB拓扑信息(也即图4涉及的设备拓扑结构)，选择策略(也即图4所涉及的设定策略)选择目标路由节点(比如选择最小公共父节点)，并关联UE分组标识和选定的路由节点。
步骤618：宿主节点-CU发送向目标路由节点发送UE分组属性(L2/L3层交换指示)以及第二路由上下文。
其中第二路由上下文是宿主节点-CU根据第一路由上下文确定的，示例性的，所述宿主节点-CU根据新的IAB拓扑关系、第一路由上下文重新生成第二路由上下文。
步骤619：目标路由节点根据UE分组属性(L2/L3层交换指示)确定数据交换类型，然后根据第二路由上下文确定路由规则。
具体的，所述目标路由节点根据第二路由上下文以及本地的DRB-RLC信道关系构建新的本地路由，也即确定路由规则。
步骤620：宿主节点-CU向源IAB-DU发送UE上下文释放命令(UE context release command)消息。
步骤621：源IAB-DU释放UE上下文，并向宿主节点-CU发送UE上下文释放完成(UE context release complete)消息。
基于与方法实施例同样的发明构思，本申请实施例还提供了一种装置，该装置应用于第一节点。该装置具体可以是第一节点中的处理器，或者芯片或者芯片系统，或者是一个功能模块等。参阅图7所示，该装置700可以包括处理单元701和通信单元702。所述通信单元702用于所述装置700接收信息(或数据)或发送信息(或数据)，所述处理单元701用于对所述装置700的动作进行控制管理。所述处理单元701还可以用于指示上述任意实施例中涉及第一节点(例如宿主节点)的处理过程和/或本申请所描述的技术方案的其他过程。具体的，所述处理单元701可以控制所述通信单元702执行的步骤，具体可以参见上述实施例，重复之处此处不再赘述。
在硬件实现上，上述处理单元701可以为处理器或者处理电路等；通信单元702可以为发送器或者发送电路等以及接收器或者接收电路等构成的收发器。
在一种实现方式中，当所述装置700在实现所述第一节点的功能时，具体可以为：
处理单元701，用于确定路由节点需要调整；通信单元702，用于向源路由节点发送上下文请求信息，所述上下文请求信息用于请求所述源路由节点中的第一路由上下文；以及从所述源路由节点接收所述第一路由上下文；所述处理单元701，还用于确定目标路由节点；所述通信单元702，还用于向所述目标路由节点发送第二路由上下文，所述第二路由上下文是基于所述第一路由上下文确定的。
在一种可选的实施方式中，所述处理单元701在确定路由节点需要调整时，具体用于：
确定设备需要切换后，根据终端设备分组信息、分组绑定的路由节点的信息或设备拓扑结构中的至少一项判定路由节点需要调整。
在一种可选的实施方式中，所述上下文请求信息中包含终端设备分组标识和/或第一类终端设备的标识，所述第一类终端设备为设备切换场景中当前有效的终端设备或者为当前失效的终端设备。
在一种可选的实施方式中，所述处理单元701还用于：根据路由节点调整前的设备拓扑结构和路由节点调整后的设备拓扑结构，确定当前有效的终端设备和当前无效的终端设备。
在一种可选的实施方式中，所述第一路由上下文包含第一地址映射关系，所述第一地址映射关系包含终端设备的地址和无线承载标识的映射关系。
在一种可选的实施方式中，所述第一地址映射关系中还包含逻辑信道标识。
在一种可选的实施方式中，所述处理单元701在基于所述第一路由上下文确定所述第二路由上下文时，具体用于：将所述第一地址映射关系中无线承载标识替换成新的无线承载标识，得到所述第二路由上下文，其中新的无线承载标识是所述第一节点分配的。
在一种可选的实施方式中，所述通信单元702，还用于：向所述源路由节点发送删除指示信息，所述删除指示信息中包含终端设备分组标识和/或第一类终端设备的标识，所述第一类终端设备为设备切换场景中当前有效的终端设备或者为当前失效的终端设备，所述删除指示信息用于指示所述源路由节点删除所述第一路由上下文；从所述源路由节点接收删除确认信息。
在一种可选的实施方式中，所述处理单元701在确定目标路由节点之前，还用于：所述第一节点确定设备切换已完成。
在一种可选的实施方式中，所述通信单元702还用于：向所述目标路由节点发送终端设备分组属性，所述终端设备分组属性包括路由指示，所述路由指示用于指示所述目标路由节点进行数据交换。
基于与方法实施例同样的发明构思，本申请实施例还提供了一种装置，该装置应用于源路由节点。该装置具体可以是源路由节点中的处理器，或者芯片或者芯片系统，或者是一个功能模块等。参阅图8所示，该装置800可以包括处理单元801和通信单元802。所述通信单元802用于所述装置800接收信息(或数据)或发送信息(或数据)，所述处理单元801用于对所述装置700的动作进行控制管理。所述处理单元801还可以用于指示上述任意实施例中涉及源路由节点的处理过程和/或本申请所描述的技术方案的其他过程。具体的，所述处理单元801可以控制所述通信单元802执行的步骤，具体可以参见上述实施例，重复之处此处不再赘述。
在硬件实现上，上述处理单元801可以为处理器或者处理电路等；通信单元802可以为发送器或者发送电路等以及接收器或者接收电路等构成的收发器。
在一种实现方式中，当所述装置800在实现所述源路由节点的功能时，具体可以为：
通信单元802，用于从第一节点接收上下文请求信息，所述上下文请求信息用于请求所述源路由节点中的第一路由上下文；处理单元801，用于根据所述上下文请求信息确定所述第一路由上下文；所述通信单元802，还用于向所述第一节点发送所述第一路由上下文。
在一种可选的实施方式中，所述上下文请求信息中包含终端设备分组标识和/或第一类终端设备的标识，所述第一类终端设备为设备切换场景中当前有效的终端设备或者为当前失效的终端设备；所述处理单元801，在根据所述上下文请求信息确定所述第一路由上下文时，具体用于：根据所述终端设备分组标识和/或第一类终端设备的标识确定所述第一路由上下文。
在一种可选的实施方式中，所述第一路由上下文包含第一地址映射关系，所述第一地址映射关系包含终端设备的地址和无线承载标识的映射关系。
在一种可选的实施方式中，所述第一地址映射关系中还包含逻辑信道标识。
在一种可选的实施方式中，所述通信单元802还用于：从所述第一节点接收删除指示信息，所述删除指示信息中包含终端设备分组标识和/或第一类终端设备的标识，所述第一类终端设备为设备切换场景中当前有效的终端设备或者为当前失效的终端设备，所述删除指示信息用于指示所述源路由节点删除所述第一路由上下文；所述处理单元801还用于： 根据所述终端设备分组标识和/或第一类终端设备的标识删除所述第一路由上下文；所述通信单元802还用于：向所述第一节点发送删除确认信息。
基于与方法实施例同样的发明构思，本申请实施例还提供了一种装置，该装置应用于目标路由节点。该装置具体可以是目标路由节点中的处理器，或者芯片或者芯片系统，或者是一个功能模块等。参阅图9所示，该装置900可以包括处理单元901和通信单元902。所述通信单元902用于所述装置900接收信息(或数据)或发送信息(或数据)，所述处理单元801用于对所述装置900的动作进行控制管理。所述处理单元901还可以用于指示上述任意实施例中涉及目标路由节点的处理过程和/或本申请所描述的技术方案的其他过程。具体的，所述处理单元901可以控制所述通信单元902执行的步骤，具体可以参见上述实施例，重复之处此处不再赘述。
在硬件实现上，上述处理单元901可以为处理器或者处理电路等；通信单元902可以为发送器或者发送电路等以及接收器或者接收电路等构成的收发器。
在一种实现方式中，当所述装置900在实现所述目标路由节点的功能时，具体可以为：
通信单元902，用于从第一节点接收第二路由上下文，所述第二路由上下文是基于所述第一路由上下文确定的；处理单元901，用于根据所述第二路由上下文确定路由规则。
在一种可选的实施方式中，所述第二路由上下文包含第二地址映射关系，所述第二地址映射关系包含终端设备的地址和无线承载标识的映射关系，其中，所述第二地址映射关系是基于所述第一路由上下文中的第一地址映射关系确定的。
在一种可选的实施方式中，所述第二地址映射关系中还包含逻辑信道标识。
在一种可选的实施方式中，所述处理单元901在根据所述第二路由节点确定路由规则时，具体用于：根据所述第二路由上下文中的所述第二地址映射关系确定所述路由规则；或者，将所述第二地址映射关系作为所述路由规则。
在一种可选的实施方式中，所述通信单元902，还用于从所述第一节点接收终端设备分组属性，所述终端设备分组属性包括路由指示，所述路由指示用于指示所述目标路由节点进行数据交换；所述处理单元901，还用于根据所述终端设备分组属性确定数据交换类型。
在一种可选的实施方式中，所述路由指示为L2/L3层交换指示，所述处理单元901在根据所述终端设备分组属性确定数据交换类型时，具体用于：根据所述L2/L3层交换指示确定所述数据交换类型。
需要说明的是，本申请实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。在本申请的实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或 者光盘等各种可以存储程序代码的介质。
基于以上实施例，本申请实施例还提供一种第一节点，用于实现通信方法。参阅图10所示，所述第一节点1000中可以包括通信接口1001和处理器1002。可选的，所述第一节点1000中还可以包括存储器1003。其中，所述存储器1003可以设置于所述第一节点1000内部，还可以设置于所述第一节点1000外部。其中，所述处理器1002控制所述通信接口1001接收和发送数据，并用于实现图4～图6中所述第一节点(例如宿主节点)所执行的方法。
具体的，所述处理器1002可以是中央处理器(central processing unit，CPU)，网络处理器(network processor，NP)或者CPU和NP的组合。所述处理器1002还可以进一步包括硬件芯片。上述硬件芯片可以是专用集成电路(application-specific integrated circuit，ASIC)，可编程逻辑器件(programmable logic device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(complex programmable logic device，CPLD)，现场可编程逻辑门阵列(field-programmable gate array，FPGA)，通用阵列逻辑(generic array logic，GAL)或其任意组合。
其中，所述通信接口1001、所述处理器1002和所述存储器1003之间相互连接。可选的，所述通信接口1001、所述处理器1002和所述存储器1003通过总线1004相互连接；所述总线1004可以是外设部件互连标准(Peripheral Component Interconnect，PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，EISA)总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图10中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
在一种可选的实施方式中，所述存储器1003，用于存放程序等。具体地，程序可以包括程序代码，该程序代码包括计算机操作指令。所述存储器1003可能包括RAM，也可能还包括非易失性存储器(non-volatile memory)，例如一个或多个磁盘存储器。所述处理器1002执行所述存储器1003所存放的应用程序，实现上述功能，从而实现本申请实施例提供的通信方法。
在一个实施例中，所述第一节点用于实现图4所示的通信方法时，具体可以包括：
处理器1002，用于确定路由节点需要调整；通信接口1001，用于向源路由节点发送上下文请求信息，所述上下文请求信息用于请求所述源路由节点中的第一路由上下文；以及从所述源路由节点接收所述第一路由上下文；所述处理器1002，还用于确定目标路由节点；所述通信接口1001，还用于向所述目标路由节点发送第二路由上下文，所述第二路由上下文是基于所述第一路由上下文确定的。
在一种可选的实施方式中，所述处理器1002在确定路由节点需要调整时，具体用于：
确定设备需要切换后，根据终端设备分组信息、分组绑定的路由节点的信息或设备拓扑结构中的至少一项判定路由节点需要调整。
在一种可选的实施方式中，所述上下文请求信息中包含终端设备分组标识和/或第一类终端设备的标识，所述第一类终端设备为设备切换场景中当前有效的终端设备或者为当前失效的终端设备。
在一种可选的实施方式中，所述处理器1002还用于：根据路由节点调整前的设备拓扑结构和路由节点调整后的设备拓扑结构，确定当前有效的终端设备和当前无效的终端设备。
在一种可选的实施方式中，所述第一路由上下文包含第一地址映射关系，所述第一地址映射关系包含终端设备的地址和无线承载标识的映射关系。
在一种可选的实施方式中，所述第一地址映射关系中还包含逻辑信道标识。
在一种可选的实施方式中，所述处理器1002在基于所述第一路由上下文确定所述第二路由上下文时，具体用于：将所述第一地址映射关系中无线承载标识替换成新的无线承载标识，得到所述第二路由上下文，其中新的无线承载标识是所述第一节点分配的。
在一种可选的实施方式中，所述通信接口1001，还用于：向所述源路由节点发送删除指示信息，所述删除指示信息中包含终端设备分组标识和/或第一类终端设备的标识，所述第一类终端设备为设备切换场景中当前有效的终端设备或者为当前失效的终端设备，所述删除指示信息用于指示所述源路由节点删除所述第一路由上下文；从所述源路由节点接收删除确认信息。
在一种可选的实施方式中，所述处理器1002在确定目标路由节点之前，还用于：所述第一节点确定设备切换已完成。
在一种可选的实施方式中，所述通信接口1001还用于：向所述目标路由节点发送终端设备分组属性，所述终端设备分组属性包括路由指示，所述路由指示用于指示所述目标路由节点进行数据交换。
基于以上实施例，本申请实施例还提供一种源路由节点，用于实现通信方法。参阅图11所示，所述源路由节点1100中可以包括通信接口1101和处理器1102。可选的，所述源路由节点1100中还可以包括存储器1103。其中，所述存储器1103可以设置于所述源路由节点1100内部，还可以设置于所述源路由节点1100外部。其中，所述处理器1102控制所述通信接口1101接收和发送数据，并用于实现图4～图6中所述源路由节点(例如宿主节点)所执行的方法。
具体的，所述处理器1102可以是中央处理器(central processing unit，CPU)，网络处理器(network processor，NP)或者CPU和NP的组合。所述处理器1102还可以进一步包括硬件芯片。上述硬件芯片可以是专用集成电路(application-specific integrated circuit，ASIC)，可编程逻辑器件(programmable logic device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(complex programmable logic device，CPLD)，现场可编程逻辑门阵列(field-programmable gate array，FPGA)，通用阵列逻辑(generic array logic，GAL)或其任意组合。
其中，所述通信接口1101、所述处理器1102和所述存储器1103之间相互连接。可选的，所述通信接口1101、所述处理器1102和所述存储器1103通过总线1104相互连接；所述总线1104可以是外设部件互连标准(Peripheral Component Interconnect，PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，EISA)总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图11中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
在一种可选的实施方式中，所述存储器1103，用于存放程序等。具体地，程序可以包括程序代码，该程序代码包括计算机操作指令。所述存储器1103可能包括RAM，也可能还包括非易失性存储器(non-volatile memory)，例如一个或多个磁盘存储器。所述处理器1102执行所述存储器1103所存放的应用程序，实现上述功能，从而实现本申请实施例提供的通信方法。
在一个实施例中，所述源路由节点用于实现图4所示的通信方法时，具体可以包括：
通信接口1101，用于从第一节点接收上下文请求信息，所述上下文请求信息用于请求所述源路由节点中的第一路由上下文；处理器1102，用于根据所述上下文请求信息确定所述第一路由上下文；所述通信接口1101，还用于向所述第一节点发送所述第一路由上下文。
在一种可选的实施方式中，所述上下文请求信息中包含终端设备分组标识和/或第一类终端设备的标识，所述第一类终端设备为设备切换场景中当前有效的终端设备或者为当前失效的终端设备；所述处理器1102，在根据所述上下文请求信息确定所述第一路由上下文时，具体用于：根据所述终端设备分组标识和/或第一类终端设备的标识确定所述第一路由上下文。
在一种可选的实施方式中，所述第一路由上下文包含第一地址映射关系，所述第一地址映射关系包含终端设备的地址和无线承载标识的映射关系。
在一种可选的实施方式中，所述第一地址映射关系中还包含逻辑信道标识。
在一种可选的实施方式中，所述通信接口1101还用于：从所述第一节点接收删除指示信息，所述删除指示信息中包含终端设备分组标识和/或第一类终端设备的标识，所述第一类终端设备为设备切换场景中当前有效的终端设备或者为当前失效的终端设备，所述删除指示信息用于指示所述源路由节点删除所述第一路由上下文；所述处理器1102还用于：根据所述终端设备分组标识和/或第一类终端设备的标识删除所述第一路由上下文；所述通信接口1101还用于：向所述第一节点发送删除确认信息。
基于以上实施例，本申请实施例还提供一种目标路由节点，用于实现通信方法。参阅图12所示，所述目标路由节点1200中可以包括通信接口1201和处理器1202。可选的，所述目标路由节点1200中还可以包括存储器1203。其中，所述存储器1203可以设置于所述目标路由节点1200内部，还可以设置于所述目标路由节点1200外部。其中，所述处理器1202控制所述通信接口1201接收和发送数据，并用于实现图4～图6中所述目标路由节点(例如宿主节点)所执行的方法。
具体的，所述处理器1202可以是中央处理器(central processing unit，CPU)，网络处理器(network processor，NP)或者CPU和NP的组合。所述处理器1202还可以进一步包括硬件芯片。上述硬件芯片可以是专用集成电路(application-specific integrated circuit，ASIC)，可编程逻辑器件(programmable logic device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(complex programmable logic device，CPLD)，现场可编程逻辑门阵列(field-programmable gate array，FPGA)，通用阵列逻辑(generic array logic，GAL)或其任意组合。
其中，所述通信接口1201、所述处理器1202和所述存储器1203之间相互连接。可选的，所述通信接口1201、所述处理器1202和所述存储器1203通过总线1204相互连接；所述总线1204可以是外设部件互连标准(Peripheral Component Interconnect，PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，EISA)总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图12中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
在一种可选的实施方式中，所述存储器1203，用于存放程序等。具体地，程序可以包括程序代码，该程序代码包括计算机操作指令。所述存储器1203可能包括RAM，也可能还包括非易失性存储器(non-volatile memory)，例如一个或多个磁盘存储器。所述处理器 1202执行所述存储器1203所存放的应用程序，实现上述功能，从而实现本申请实施例提供的通信方法。
在一个实施例中，所述目标路由节点用于实现图4所示的通信方法时，具体可以包括：
通信接口1201，用于从第一节点接收第二路由上下文，所述第二路由上下文是基于所述第一路由上下文确定的；处理器1202，用于根据所述第二路由上下文确定路由规则。
在一种可选的实施方式中，所述第二路由上下文包含第二地址映射关系，所述第二地址映射关系包含终端设备的地址和无线承载标识的映射关系，其中，所述第二地址映射关系是基于所述第一路由上下文中的第一地址映射关系确定的。
在一种可选的实施方式中，所述第二地址映射关系中还包含逻辑信道标识。
在一种可选的实施方式中，所述处理器1202在根据所述第二路由节点确定路由规则时，具体用于：根据所述第二路由上下文中的所述第二地址映射关系确定所述路由规则；或者，将所述第二地址映射关系作为所述路由规则。
在一种可选的实施方式中，所述通信接口1201，还用于从所述第一节点接收终端设备分组属性，所述终端设备分组属性包括路由指示，所述路由指示用于指示所述目标路由节点进行数据交换；所述处理器1202，还用于根据所述终端设备分组属性确定数据交换类型。
在一种可选的实施方式中，所述路由指示为L2/L3层交换指示，所述处理器1202在根据所述终端设备分组属性确定数据交换类型时，具体用于：根据所述L2/L3层交换指示确定所述数据交换类型。
基于与上述方法实施例相同构思，本申请实施例中还提供一种计算机可读存储介质，其上存储有计算机程序(或称指令)，该程序被处理器执行时，使该计算机执行上述方法实施例、方法实施例的任意一种可能的实现方式中由第一节点、源路由节点或目标路由节点中至少一项执行的操作。
基于与上述方法实施例相同构思，本申请还提供一种计算机程序产品，该计算机程序产品在被计算机调用执行时，可以使得计算机实现上述方法实施例、方法实施例的任意一种可能的实现方式中由第一节点、源路由节点或目标路由节点中至少一项执行的操作。
基于与上述方法实施例相同构思，本申请还提供一种芯片或芯片系统，该芯片与存储器耦合，用于实现上述方法实施例、方法实施例的任意一种可能的实现方式中由第一节点、源路由节点或目标路由节点中至少一项执行的操作。该芯片系统可包括该芯片，以及包括存储器、通信接口等组件。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的保护范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (49)

  1. 一种通信方法，其特征在于，包括：
    第一节点确定路由节点需要调整后，向源路由节点发送上下文请求信息，所述上下文请求信息用于请求所述源路由节点中的第一路由上下文；
    所述第一节点从所述源路由节点接收所述第一路由上下文；
    所述第一节点确定目标路由节点，并向所述目标路由节点发送第二路由上下文，所述第二路由上下文是基于所述第一路由上下文确定的。
  2. 如权利要求1所述的方法，其特征在于，所述第一节点确定路由节点需要调整，包括：
    所述第一节点确定设备需要切换后，根据终端设备分组信息、分组绑定的路由节点的信息或设备拓扑结构中的至少一项判定路由节点需要调整。
  3. 如权利要求1或2所述的方法，其特征在于，所述上下文请求信息中包含终端设备分组标识和/或第一类终端设备的标识，所述第一类终端设备为设备切换场景中当前有效的终端设备或者为当前失效的终端设备。
  4. 如权利要求3所述的方法，其特征在于，所述方法还包括：
    所述第一节点根据路由节点调整前的设备拓扑结构和路由节点调整后的设备拓扑结构，确定当前有效的终端设备和当前无效的终端设备。
  5. 如权利要求1-4任一项所述的方法，其特征在于，所述第一路由上下文包含第一地址映射关系，所述第一地址映射关系包含终端设备的地址和无线承载标识的映射关系。
  6. 如权利要求5所述的方法，其特征在于，所述第一地址映射关系中还包含逻辑信道标识。
  7. 如权利要求5或6所述的方法，其特征在于，所述第一节点基于所述第一路由上下文确定所述第二路由上下文，包括：
    所述第一节点将所述第一地址映射关系中无线承载标识替换成新的无线承载标识，得到所述第二路由上下文，其中新的无线承载标识是所述第一节点分配的。
  8. 如权利要求1-7任一项所述的方法，其特征在于，所述方法还包括：
    所述第一节点向所述源路由节点发送删除指示信息，所述删除指示信息中包含终端设备分组标识和/或第一类终端设备的标识，所述第一类终端设备为设备切换场景中当前有效的终端设备或者为当前失效的终端设备，所述删除指示信息用于指示所述源路由节点删除所述第一路由上下文；
    所述第一节点从所述源路由节点接收删除确认信息。
  9. 如权利要求1-8任一项所述的方法，其特征在于，在所述第一节点确定目标路由节点之前，所述方法还包括：
    所述第一节点确定设备切换已完成。
  10. 如权利要求1-9任一项所述的方法，其特征在于，所述方法还包括：
    所述第一节点向所述目标路由节点发送终端设备分组属性，所述终端设备分组属性包括路由指示，所述路由指示用于指示所述目标路由节点进行数据交换。
  11. 一种通信方法，其特征在于，包括：
    源路由节点从第一节点接收上下文请求信息，所述上下文请求信息用于请求所述源路 由节点中的第一路由上下文；
    所述源路由节点根据所述上下文请求信息确定所述第一路由上下文；
    所述源路由节点向所述第一节点发送所述第一路由上下文。
  12. 如权利要求11所述的方法，其特征在于，所述上下文请求信息中包含终端设备分组标识和/或第一类终端设备的标识，所述第一类终端设备为设备切换场景中当前有效的终端设备或者为当前失效的终端设备；
    所述源路由节点根据所述上下文请求信息确定所述第一路由上下文，包括：
    所述源路由节点根据所述终端设备分组标识和/或第一类终端设备的标识确定所述第一路由上下文。
  13. 如权利要求11或12所述的方法，其特征在于，所述第一路由上下文包含第一地址映射关系，所述第一地址映射关系包含终端设备的地址和无线承载标识的映射关系。
  14. 如权利要求13所述的方法，其特征在于，所述第一地址映射关系中还包含逻辑信道标识。
  15. 如权利要求11-14任一项所述的方法，其特征在于，所述方法还包括：
    所述源路由节点从所述第一节点接收删除指示信息，所述删除指示信息中包含终端设备分组标识和/或第一类终端设备的标识，所述第一类终端设备为设备切换场景中当前有效的终端设备或者为当前失效的终端设备，所述删除指示信息用于指示所述源路由节点删除所述第一路由上下文；
    所述源路由节点根据所述终端设备分组标识和/或第一类终端设备的标识删除所述第一路由上下文；
    所述源路由节点向所述第一节点发送删除确认信息。
  16. 一种通信方法，其特征在于，包括：
    目标路由节点从第一节点接收第二路由上下文，所述第二路由上下文是基于所述第一路由上下文确定的；
    所述目标路由节点根据所述第二路由上下文确定路由规则。
  17. 如权利要求16所述的方法，其特征在于，所述第二路由上下文包含第二地址映射关系，所述第二地址映射关系包含终端设备的地址和无线承载标识的映射关系，其中，所述第二地址映射关系是基于所述第一路由上下文中的第一地址映射关系确定的。
  18. 如权利要求17所述的方法，其特征在于，所述第二地址映射关系中还包含逻辑信道标识。
  19. 如权利要求17或18所述的方法，其特征在于，所述目标路由节点根据所述第二路由节点确定路由规则，包括：
    所述目标路由节点根据所述第二路由上下文中的所述第二地址映射关系确定所述路由规则；或者
    所述目标路由节点将所述第二地址映射关系作为所述路由规则。
  20. 如权利要求16-19任一项所述的方法，其特征在于，所述方法还包括：
    所述目标路由节点从所述第一节点接收终端设备分组属性，所述终端设备分组属性包括路由指示，所述路由指示用于指示所述目标路由节点进行数据交换；
    所述目标路由节点根据所述终端设备分组属性确定数据交换类型。
  21. 如权利要求20所述的方法，其特征在于，所述路由指示为L2/L3层交换指示， 所述目标路由节点根据所述终端设备分组属性确定数据交换类型，包括：
    所述目标路由节点根据所述L2/L3层交换指示确定所述数据交换类型。
  22. 一种第一节点，其特征在于，包括：
    处理单元，用于确定路由节点需要调整；
    通信单元，用于向源路由节点发送上下文请求信息，所述上下文请求信息用于请求所述源路由节点中的第一路由上下文；以及从所述源路由节点接收所述第一路由上下文；
    所述处理单元，还用于确定目标路由节点；
    所述通信单元，还用于向所述目标路由节点发送第二路由上下文，所述第二路由上下文是基于所述第一路由上下文确定的。
  23. 如权利要求22所述的第一节点，其特征在于，所述处理单元在确定路由节点需要调整时，具体用于：
    确定设备需要切换后，根据终端设备分组信息、分组绑定的路由节点的信息或设备拓扑结构中的至少一项判定路由节点需要调整。
  24. 如权利要求22或23所述的第一节点，其特征在于，所述上下文请求信息中包含终端设备分组标识和/或第一类终端设备的标识，所述第一类终端设备为设备切换场景中当前有效的终端设备或者为当前失效的终端设备。
  25. 如权利要求24所述的第一节点，其特征在于，所述处理单元还用于：
    根据路由节点调整前的设备拓扑结构和路由节点调整后的设备拓扑结构，确定当前有效的终端设备和当前无效的终端设备。
  26. 如权利要求22-25任一项所述的第一节点，其特征在于，所述第一路由上下文包含第一地址映射关系，所述第一地址映射关系包含终端设备的地址和无线承载标识的映射关系。
  27. 如权利要求26所述的第一节点，其特征在于，所述第一地址映射关系中还包含逻辑信道标识。
  28. 如权利要求26或27所述的第一节点，其特征在于，所述处理单元在基于所述第一路由上下文确定所述第二路由上下文时，具体用于：
    将所述第一地址映射关系中无线承载标识替换成新的无线承载标识，得到所述第二路由上下文，其中新的无线承载标识是所述第一节点分配的。
  29. 如权利要求22-28任一项所述的第一节点，其特征在于，所述通信单元，还用于：
    向所述源路由节点发送删除指示信息，所述删除指示信息中包含终端设备分组标识和/或第一类终端设备的标识，所述第一类终端设备为设备切换场景中当前有效的终端设备或者为当前失效的终端设备，所述删除指示信息用于指示所述源路由节点删除所述第一路由上下文；
    从所述源路由节点接收删除确认信息。
  30. 如权利要求22-29任一项所述的第一节点，其特征在于，所述处理单元在确定目标路由节点之前，还用于：
    所述第一节点确定设备切换已完成。
  31. 如权利要求22-30任一项所述的第一节点，其特征在于，所述通信单元还用于：
    向所述目标路由节点发送终端设备分组属性，所述终端设备分组属性包括路由指示，所述路由指示用于指示所述目标路由节点进行数据交换。
  32. 一种源路由节点，其特征在于，包括：
    通信单元，用于从第一节点接收上下文请求信息，所述上下文请求信息用于请求所述源路由节点中的第一路由上下文；
    处理单元，用于根据所述上下文请求信息确定所述第一路由上下文；
    所述通信单元，还用于向所述第一节点发送所述第一路由上下文。
  33. 如权利要求32所述的源路由节点，其特征在于，所述上下文请求信息中包含终端设备分组标识和/或第一类终端设备的标识，所述第一类终端设备为设备切换场景中当前有效的终端设备或者为当前失效的终端设备；
    所述处理单元，在根据所述上下文请求信息确定所述第一路由上下文时，具体用于：
    根据所述终端设备分组标识和/或第一类终端设备的标识确定所述第一路由上下文。
  34. 如权利要求32或33所述的源路由节点，其特征在于，所述第一路由上下文包含第一地址映射关系，所述第一地址映射关系包含终端设备的地址和无线承载标识的映射关系。
  35. 如权利要求34所述的源路由节点，其特征在于，所述第一地址映射关系中还包含逻辑信道标识。
  36. 如权利要求32-35任一项所述的源路由节点，其特征在于，
    所述通信单元还用于：从所述第一节点接收删除指示信息，所述删除指示信息中包含终端设备分组标识和/或第一类终端设备的标识，所述第一类终端设备为设备切换场景中当前有效的终端设备或者为当前失效的终端设备，所述删除指示信息用于指示所述源路由节点删除所述第一路由上下文；
    所述处理单元还用于：根据所述终端设备分组标识和/或第一类终端设备的标识删除所述第一路由上下文；
    所述通信单元还用于：向所述第一节点发送删除确认信息。
  37. 一种目标路由节点，其特征在于，包括：
    通信单元，用于从第一节点接收第二路由上下文，所述第二路由上下文是基于所述第一路由上下文确定的；
    处理单元，用于根据所述第二路由上下文确定路由规则。
  38. 如权利要求37所述的目标路由节点，其特征在于，所述第二路由上下文包含第二地址映射关系，所述第二地址映射关系包含终端设备的地址和无线承载标识的映射关系，其中，所述第二地址映射关系是基于所述第一路由上下文中的第一地址映射关系确定的。
  39. 如权利要求38所述的目标路由节点，其特征在于，所述第二地址映射关系中还包含逻辑信道标识。
  40. 如权利要求38或39所述的目标路由节点，其特征在于，所述处理单元在根据所述第二路由节点确定路由规则时，具体用于：
    根据所述第二路由上下文中的所述第二地址映射关系确定所述路由规则；或者
    将所述第二地址映射关系作为所述路由规则。
  41. 如权利要求37-40任一项所述的目标路由节点，其特征在于，
    所述通信单元，还用于从所述第一节点接收终端设备分组属性，所述终端设备分组属性包括路由指示，所述路由指示用于指示所述目标路由节点进行数据交换；
    所述处理单元，还用于根据所述终端设备分组属性确定数据交换类型。
  42. 如权利要求41所述的目标路由节点，其特征在于，所述路由指示为L2/L3层交换指示，所述处理单元在根据所述终端设备分组属性确定数据交换类型时，具体用于：
    根据所述L2/L3层交换指示确定所述数据交换类型。
  43. 一种第一节点，其特征在于，包括：
    通信接口，用于收发数据；
    处理器，用于使得所述第一节点执行如权利要求1-10中任一项所述的方法。
  44. 一种源路由节点，其特征在于，包括：
    通信接口，用于收发数据；
    处理器，用于使得所述源路由节点执行如权利要求11-15中任一项所述的方法。
  45. 一种目标路由节点，其特征在于，包括：
    通信接口，用于收发数据；
    处理器，用于使得所述目标路由节点执行如权利要求16-21中任一项所述的方法。
  46. 一种通信系统，其特征在于，包括权利要求22-31、43中任一项所述的第一节点、权利要求32-36、44任一项所述的源路由节点和权利要求37-42、45中任一项所述的目标路由节点。
  47. 一种计算机可读存储介质，其特征在于，包括指令，当所述指令在计算机上运行时，使得计算机执行权利要求1至21中任一项所述的方法。
  48. 一种包含指令的计算机程序产品，其特征在于，当所述计算机程序产品在计算机上运行时，使得计算机执行权利要求1至21中任一项所述的方法。
  49. 一种芯片，其特征在于，所述芯片与存储器耦合，所述芯片用于执行如权利要求1至21中任一项所述的方法。
PCT/CN2020/072857 2020-01-17 2020-01-17 一种通信方法及装置 WO2021142801A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202080093433.XA CN115004658B (zh) 2020-01-17 2020-01-17 一种通信方法及装置
PCT/CN2020/072857 WO2021142801A1 (zh) 2020-01-17 2020-01-17 一种通信方法及装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/072857 WO2021142801A1 (zh) 2020-01-17 2020-01-17 一种通信方法及装置

Publications (1)

Publication Number Publication Date
WO2021142801A1 true WO2021142801A1 (zh) 2021-07-22

Family

ID=76863309

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/072857 WO2021142801A1 (zh) 2020-01-17 2020-01-17 一种通信方法及装置

Country Status (2)

Country Link
CN (1) CN115004658B (zh)
WO (1) WO2021142801A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024074000A1 (en) * 2023-02-16 2024-04-11 Lenovo (Beijing) Limited Method and apparatus for communicating in iab network

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103518402A (zh) * 2012-11-26 2014-01-15 华为技术有限公司 信令处理方法、设备和系统
WO2014092613A1 (en) * 2012-12-10 2014-06-19 Telefonaktiebolaget L M Ericsson (Publ) Methods and apparatus for routing communications using slotted resources of radio access mesh networks
CN107040462A (zh) * 2015-09-29 2017-08-11 丛林网络公司 路由方法和中间路由器
CN110581778A (zh) * 2019-08-13 2019-12-17 中兴通讯股份有限公司 一种路由方法、bsr的生成方法、装置和存储介质

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107770825B (zh) * 2016-08-19 2021-03-16 中兴通讯股份有限公司 一种基于用户文本信息的路径切换方法及装置
CN108632927B (zh) * 2017-03-24 2021-08-13 华为技术有限公司 移动网络切换方法和通信装置
CN108811153A (zh) * 2017-05-05 2018-11-13 华为技术有限公司 通信方法、集中式单元、分布式单元、基站及终端设备
US10708968B2 (en) * 2017-08-25 2020-07-07 Kt Corporation Method of controlling mobility of UE and apparatus therefor
CN110636561B (zh) * 2018-06-21 2022-11-08 中兴通讯股份有限公司 信息传输方法及装置、存储介质、电子装置
CN112470542B (zh) * 2018-07-05 2023-02-28 联想(北京)有限公司 用于回程链路切换的方法及设备
GB2583521B (en) * 2019-05-02 2022-01-12 Samsung Electronics Co Ltd Relay network routing

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103518402A (zh) * 2012-11-26 2014-01-15 华为技术有限公司 信令处理方法、设备和系统
WO2014092613A1 (en) * 2012-12-10 2014-06-19 Telefonaktiebolaget L M Ericsson (Publ) Methods and apparatus for routing communications using slotted resources of radio access mesh networks
CN107040462A (zh) * 2015-09-29 2017-08-11 丛林网络公司 路由方法和中间路由器
CN110581778A (zh) * 2019-08-13 2019-12-17 中兴通讯股份有限公司 一种路由方法、bsr的生成方法、装置和存储介质

Also Published As

Publication number Publication date
CN115004658A (zh) 2022-09-02
CN115004658B (zh) 2024-04-12

Similar Documents

Publication Publication Date Title
RU2713442C1 (ru) Система и способ переключения сот
CN110351024B (zh) 数据传输方法和装置
JP7303833B2 (ja) 情報伝送方法及び装置
JP7135100B2 (ja) パケット伝送方法、装置、およびシステム
JP2024020336A (ja) データ伝送方法、通信デバイス、及び通信システム
WO2022082679A1 (zh) 一种通信方法及相关设备
WO2023011245A1 (zh) 通信方法和通信装置
US20220225443A1 (en) Data transmission method and apparatus
WO2022041249A1 (zh) 一种节点的切换方法以及相关设备
CN111148158B (zh) 一种通信方法及装置
US20230247521A1 (en) Lossless data transmission communication method, apparatus, and system
WO2022078112A1 (zh) 连接建立方法、装置、设备及存储介质
WO2019076182A1 (zh) 连接处理方法和设备
CN110351890A (zh) 集中式单元-分布式单元架构下的通信方法、通信设备
WO2021142801A1 (zh) 一种通信方法及装置
US20230362779A1 (en) Communication method and related device
CN115918244A (zh) 第一节点、第二节点和由其执行的用于处理多跳网络中的分组重复的方法
CN116491214A (zh) 一种释放f1连接的方法、装置及系统
WO2024060239A1 (zh) 通信方法、装置、设备、存储介质及程序产品
WO2023150974A1 (zh) Iab宿主设备以及传输迁移管理方法
WO2023150976A1 (zh) Iab宿主设备以及传输迁移管理方法
WO2022183453A1 (zh) 一种通信方法、装置及芯片
TWI827186B (zh) 路由方法和通信裝置
WO2023150975A1 (zh) Iab宿主设备以及传输迁移回退方法
WO2023130989A1 (zh) 一种通信方法及装置

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: 20913627

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20913627

Country of ref document: EP

Kind code of ref document: A1