A communication method and communication device
By configuring downlink data mapping for IAB nodes during the handover process between host nodes, the problem of terminal service continuity in the handover scenario between IAB nodes is solved, and reliable data transmission is achieved.
Patent Information
- Application Number
- CN202110091250.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-01-22
- Publication Date
- 2026-11-10
- Estimated Expiration
- 2041-01-22
AI Technical Summary
Existing communication standards do not define a solution to ensure terminal service continuity in scenarios where IAB nodes switch between host nodes.
The centralized unit (CU) of the first host node configures the mapping of downlink data for the terminal and sends the mapping information, including routing mapping and bearer mapping, to the CU of the second host node to ensure that downlink data can be accurately transmitted during the handover process between host nodes.
It ensures the continuity of terminal services during the handover between IAB node host nodes, ensuring that data can be reliably transmitted to the terminal and avoiding service interruption.
Smart Images

Figure CN114828133B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of communication technology, and in particular to a communication method and communication device. Background Technology
[0002] In 3GPP Release 15, the Integrated Access and Backhaul (IAB) node and IAB donor node were introduced. IAB nodes provide radio access services to terminals and connect to the donor node via a radio backhaul link. A donor node can connect to one or more IAB nodes. In a network containing IAB nodes, IAB nodes can perform handover. Current communication standards discussions have proposed scenarios and solutions for intra-donor-CU handover of IAB nodes. However, current communication standards do not define the process for inter-donor-CU handover of IAB nodes; that is, there is currently no solution to ensure terminal service continuity in inter-donor-CU handover scenarios. Summary of the Invention
[0003] This application provides a communication method and a communication device to improve the continuity of terminal services in Inter-donor-CU handover scenarios.
[0004] To achieve the above objectives, the embodiments of this application provide the following technical solutions:
[0005] In a first aspect, a communication method is provided, comprising: a first centralized unit (CU) of a first host node determining a first mapping and sending the first mapping to a second CU of a second host node; and the first CU sending the downlink data to a second DU of the second host node.
[0006] The first mapping includes routing mapping and / or bearer mapping; the routing mapping is a mapping relationship between downlink data and downlink transmission path; the bearer mapping is a mapping relationship between downlink data and downlink transmission bearer; the downlink transmission path includes the transmission path between the first CU and the target node of the downlink data through the second DU; the downlink transmission bearer includes the Radio Link Control (RLC) channel between the second DU and the first node; the first node is the next-hop node of the second DU.
[0007] The communication method provided in this application, in a scenario where IAB nodes are switching between host nodes, involves the first CU of the first host node configuring a first mapping for the downlink data of the terminal and sending this first mapping to the second CU of the second host node. Thus, after receiving downlink data from the first host node, the second host node can perform routing and bearer selection on the downlink data according to the first mapping. In other words, in a scenario where IAB nodes are switching between host nodes, the downlink data can reach the terminal through the second host node, avoiding disruption to the terminal's service continuity.
[0008] In one possible design, the mapping relationship between downlink data and downlink transmission path includes: the destination address of the downlink data, the service attribute information of the downlink data, and the first routing identifier corresponding to the destination address and the service attribute information; the mapping relationship between downlink data and downlink transmission bearer includes: the destination address of the downlink data, the service attribute information of the downlink data, and the information of the first radio link control (RLC) channel corresponding to the destination address and the service attribute information; the downlink data includes the service attribute information.
[0009] Optionally, service attribute information includes differentiated services codepoints (DSCPs) or flow labels. Service attribute information can distinguish different services to ensure quality of service (QoS). In this way, data carrying different service attribute information can be transmitted through different transmission paths.
[0010] In one possible design, before the first CU sends the first mapping to the second CU, the method further includes:
[0011] The first CU receives one or more second route identifiers allocated by the second CU; the first route identifier is different from the one or more second route identifiers. In this way, the first CU can know the route identifier allocated by the second CU. Therefore, when reallocating route identifiers, the first CU can allocate different route identifiers from the second CU to ensure that the route identifiers allocated by the first CU and the second CU are not duplicated, that is, the route identifiers allocated by both can uniquely identify the transmission path.
[0012] In one possible design, before the first CU sends the first mapping to the second CU, the method further includes:
[0013] The first CU receives information about one or more RLC channels between the second DU and the first node, as well as QoS information corresponding to the one or more RLC channels, from the second CU; the one or more RLC channels include the first RLC channel.
[0014] Typically, the first CU only knows the corresponding RLC channel information of the IAB nodes it manages or controls, and does not know the corresponding RLC channel information of the nodes managed by other CUs (e.g.). The second CU needs to send the corresponding RLC channel information of the nodes it manages to the first CU so that the first CU can determine the above bearer mapping based on this information.
[0015] Optionally, the first CU determines the service attribute information of the downlink data.
[0016] Alternatively, the second CU may determine the service attribute information of the downlink data.
[0017] In one possible design of the method for determining the service attribute information of downlink data in the second CU, the method further includes:
[0018] The first CU sends information about the General Packet Radio Service Tunneling Protocol (GTP) tunnel for the downlink data and the QoS information corresponding to the GTP tunnel to the second CU.
[0019] Thus, the second CU determines the service attribute information of the downlink data based on the information received from the first CU.
[0020] In one possible design of the method for determining the service attribute information of downlink data in the second CU, the method further includes:
[0021] The first CU receives information about the GTP tunnel for the downlink data and the corresponding service attribute information from the second CU. Thus, the first CU can receive the service attribute information of the downlink data determined by the second CU, so that the first CU can accordingly include the corresponding service attribute information in the IP header of the downlink data.
[0022] In one possible design, the first host node is the source host node and the second host node is the target host node; or, the first host node is the target host node and the second host node is the source host node.
[0023] In one possible design, the first host node is the primary host node and the second host node is the secondary host node; or, the first host node is the secondary host node and the second host node is the primary host node.
[0024] Secondly, this application provides a communication method, including:
[0025] The second CU of the second host node receives the first mapping from the first centralized unit CU of the first host node; the second DU of the second host node receives downlink data from the first CU.
[0026] The first mapping includes routing mapping and / or bearer mapping; the routing mapping is a mapping relationship between downlink data and downlink transmission path; the bearer mapping is a mapping relationship between downlink data and downlink transmission bearer; the downlink transmission path includes the transmission path between the first CU and the target node of the downlink data through the second DU; the downlink transmission bearer includes the Radio Link Control (RLC) channel between the second DU and the first node; the first node is the next-hop node of the second DU.
[0027] In one possible design, the mapping relationship between downlink data and downlink transmission path includes: the destination address of the downlink data, the service attribute information of the downlink data, the destination address and the first routing identifier corresponding to the service attribute information; the mapping relationship between downlink data and downlink transmission bearer includes: the destination address of the downlink data, the service attribute information of the downlink data, the destination address and the information of the first radio link control (RLC) channel corresponding to the service attribute information; the downlink data includes the service attribute information.
[0028] In one possible design, the downlink data includes the business attribute information.
[0029] In one possible design, the method further includes:
[0030] The second CU sends one or more second route identifiers allocated by the second CU to the first CU; the first route identifier and the one or more second route identifiers are different.
[0031] In one possible design, the method further includes:
[0032] The second CU sends information about one or more RLC channels between the second DU and the first node, as well as the Quality of Service (QoS) information corresponding to the one or more RLC channels, to the first CU; the one or more RLC channels include the first RLC channel.
[0033] Optionally, the second CU determines the service attribute information of the downlink data.
[0034] In one possible design of the method for determining the service attribute information of downlink data in the second CU, the method further includes:
[0035] The second CU receives from the first CU information about the General Packet Radio Service Tunneling Protocol (GTP) tunnel for the downlink data, as well as the QoS information corresponding to the GTP tunnel.
[0036] In one possible design of the method for determining the service attribute information of downlink data in the second CU, the method further includes:
[0037] The second CU sends the GTP tunnel information of the downlink data and the service attribute information corresponding to the GTP tunnel to the first CU.
[0038] In one possible design, the first host node is the source host node and the second host node is the target host node; or, the first host node is the target host node and the second host node is the source host node.
[0039] In one possible design, the first host node is the primary host node and the second host node is the secondary host node; or, the first host node is the secondary host node and the second host node is the primary host node.
[0040] Thirdly, this application provides a communication method, including:
[0041] The second centralized unit (CU) of the second host node determines the first mapping, and the second DU of the second host node receives the downlink data from the first CU of the first host node.
[0042] The first mapping includes routing mapping and / or bearer mapping; the routing mapping is a mapping relationship between downlink data and downlink transmission path; the bearer mapping is a mapping relationship between downlink data and downlink transmission bearer; the downlink transmission path includes the transmission path between the first CU and the target node of the downlink data through the second DU; the downlink transmission bearer includes the RLC channel between the second DU and the first node; the first node is the next-hop node of the second DU.
[0043] In this method, the second host node can determine the first mapping. Therefore, when receiving downlink data, the second host node can perform routing and bearer selection on the received downlink data according to the first mapping. In this way, in the scenario where IAB nodes switch between host nodes, downlink data can reach the terminal through the second host node, thereby improving the service continuity of the terminal.
[0044] In one possible design, the mapping relationship between the downlink data and the downlink transmission path includes: the target address of the downlink data, the service attribute information of the downlink data, the target address and the third routing identifier corresponding to the service attribute information; the mapping relationship between the downlink data and the downlink transmission bearer includes: the target address of the downlink data, the service attribute information of the downlink data, the target address and the information of the second radio link control (RLC) channel corresponding to the service attribute information.
[0045] In one possible design, the method further includes:
[0046] The second CU receives the service attribute information of the downlink data and the quality of service (QoS) information corresponding to the service attribute information from the first CU.
[0047] In one possible design, before the second CU determines the first mapping, the method further includes:
[0048] The second CU receives one or more fourth route identifiers assigned by the first CU. The third route identifier is different from the one or more fourth route identifiers.
[0049] In one possible design, before the second CU determines the first mapping, the method further includes:
[0050] The second CU receives information about one or more RLC channels from the first CU, as well as QoS information corresponding to the one or more RLC channels. The one or more RLC channels include the second RLC channel.
[0051] In one possible design, the method further includes:
[0052] The second CU receives from the first CU information about the General Packet Radio Service Tunneling Protocol (GTP) tunnel for the downlink data, as well as the QoS information corresponding to the GTP tunnel.
[0053] In one possible design, the method further includes:
[0054] The second CU sends the GTP tunnel information of the downlink data and the service attribute information corresponding to the GTP tunnel to the first CU.
[0055] Fourthly, this application provides a communication method in which the first CU of the first host node determines the service attribute information of downlink data. The method includes:
[0056] The first CU of the first host node determines the service attribute information of the downlink data and sends the service attribute information to the second CU of the second host node.
[0057] In one possible design, the method further includes:
[0058] The first CU sends the service attribute information of the downlink data and the corresponding Quality of Service (QoS) information to the second CU.
[0059] In one possible design, the method further includes:
[0060] The first CU sends one or more fourth route identifiers allocated by the first CU to the second CU.
[0061] In one possible design, the method further includes:
[0062] The first CU sends information about one or more RLC channels, as well as QoS information corresponding to the one or more RLC channels, to the second CU.
[0063] Fifthly, this application provides a communication method in which a first CU of a first host node sends some information to a second CU of a second host node, so that the second CU can determine the service attribute information of downlink data based on this information. The method includes:
[0064] The first CU of the first host node determines the information of the General Packet Radio Service Tunneling Protocol (GTP) tunnel for downlink data and the QoS information corresponding to the GTP tunnel.
[0065] The first CU sends the GTP tunnel information and the corresponding QoS information to the second CU of the second host node.
[0066] In one possible design, the method further includes:
[0067] The first CU receives information about the GTP tunnel for the downlink data and the service attribute information corresponding to the GTP tunnel from the second CU.
[0068] In one possible design, the method further includes:
[0069] The first CU sends one or more fourth route identifiers allocated by the first CU to the second CU.
[0070] In one possible design, the method further includes:
[0071] The first CU sends information about one or more RLC channels, as well as QoS information corresponding to the one or more RLC channels, to the second CU.
[0072] Sixthly, this application provides a communication method, comprising:
[0073] The first CU of the first host node determines the service attribute information of the downlink data and the first mapping, and sends the first mapping to the second CU of the second host node; and the first CU sends the downlink data to the second DU of the second host node.
[0074] The first mapping includes routing mapping and / or bearer mapping; the routing mapping is a mapping relationship between downlink data and downlink transmission path; the bearer mapping is a mapping relationship between downlink data and downlink transmission bearer; the downlink transmission path includes the transmission path between the first CU and the target node of the downlink data through the second DU; the downlink transmission bearer includes the Radio Link Control (RLC) channel between the second DU and the first node; the first node is the next-hop node of the second DU.
[0075] In one possible design, the mapping relationship between downlink data and downlink transmission path includes: the destination address of the downlink data, the service attribute information of the downlink data, the destination address and the first routing identifier corresponding to the service attribute information; the mapping relationship between downlink data and downlink transmission bearer includes: the destination address of the downlink data, the service attribute information of the downlink data, the destination address and the information of the first radio link control (RLC) channel corresponding to the service attribute information; the downlink data includes the service attribute information.
[0076] In one possible design, the method further includes:
[0077] The first CU receives one or more second route identifiers assigned by the second CU; the first route identifier is different from the one or more second route identifiers.
[0078] In one possible design, the method further includes:
[0079] The first CU receives information about one or more RLC channels between the second DU and the first node, as well as the Quality of Service (QoS) information corresponding to the one or more RLC channels, from the second CU.
[0080] In one possible design, the first host node is the source host node and the second host node is the target host node; or, the first host node is the target host node and the second host node is the source host node.
[0081] In one possible design, the first host node is the primary host node and the second host node is the secondary host node; or, the first host node is the secondary host node and the second host node is the primary host node.
[0082] Seventhly, this application provides a communication method, comprising:
[0083] The first CU of the first host node determines the service attribute information of the downlink data;
[0084] The second CU of the second host node determines the first mapping;
[0085] The first CU sends the downlink data to the second DU of the second host node.
[0086] The first mapping includes routing mapping and / or bearer mapping; the routing mapping is a mapping relationship between downlink data and downlink transmission path; the bearer mapping is a mapping relationship between downlink data and downlink transmission bearer; the downlink transmission path includes the transmission path between the first CU and the target node of the downlink data through the second DU; the downlink transmission bearer includes the Radio Link Control (RLC) channel between the second DU and the first node; the first node is the next-hop node of the second DU.
[0087] In one possible design, before the second CU determines the first mapping, the method further includes:
[0088] The first CU sends the service attribute information and the corresponding Quality of Service (QoS) information to the second CU.
[0089] In one possible design, the method further includes:
[0090] The first CU sends one or more fourth route identifiers allocated by the first CU to the second CU.
[0091] In one possible design, the method further includes:
[0092] The first CU sends information about one or more RLC channels, as well as QoS information corresponding to the one or more RLC channels, to the second CU.
[0093] Eighthly, this application provides a communication method, comprising:
[0094] The second CU of the second host node determines the service attribute information of the downlink data, as well as the first mapping;
[0095] The first CU of the first host node sends the downlink data to the second DU of the second host node.
[0096] The first mapping includes routing mapping and / or bearer mapping; the routing mapping is a mapping relationship between downlink data and downlink transmission path; the bearer mapping is a mapping relationship between downlink data and downlink transmission bearer; the downlink transmission path includes the transmission path between the first CU and the target node of the downlink data through the second DU; the downlink transmission bearer includes the RLC channel between the second DU and the first node; the first node is the next-hop node of the second DU.
[0097] In one possible design, the first CU sends downlink data GTP tunnel information and the corresponding QoS information of the GTP tunnel to the second CU.
[0098] In one possible design, the first CU receives information about the GTP tunnel for downlink data and the service attribute information corresponding to the GTP tunnel from the second CU.
[0099] Ninthly, this application provides a communication method, comprising:
[0100] The second CU of the second host node determines the service attribute information of the downlink data;
[0101] The first CU of the first host node determines the first mapping and sends the first mapping to the second CU;
[0102] The first CU sends the downlink data to the second DU of the second host node.
[0103] The first mapping includes routing mapping and / or bearer mapping; the routing mapping is a mapping relationship between downlink data and downlink transmission path; the bearer mapping is a mapping relationship between downlink data and downlink transmission bearer; the downlink transmission path includes the transmission path between the first CU and the target node of the downlink data through the second DU; the downlink transmission bearer includes the RLC channel between the second DU and the first node; the first node is the next-hop node of the second DU.
[0104] In one possible design, the first CU sends downlink data GTP tunnel information and the corresponding QoS information of the GTP tunnel to the second CU.
[0105] In one possible design, the first CU receives information about the GTP tunnel for downlink data and the service attribute information corresponding to the GTP tunnel from the second CU.
[0106] Tenthly, this application provides a communication method, comprising:
[0107] The primary network device determines the first indication information and sends the first indication information to the secondary network device.
[0108] The first indication information is used to request / instruct the secondary network device to transmit the first signaling to the first node through the first signaling radio bearer;
[0109] In one possible design, the method further includes: the primary network device receiving second indication information from the secondary network device, the second indication information being used to indicate that the establishment of the first signaling radio bearer failed, or that the first signaling could not be transmitted through the first signaling radio bearer.
[0110] In one possible design, the method further includes:
[0111] The main network device sends a third indication information to the first node. The third indication information is used to indicate the information of the uplink transmission path used to transmit the first signaling. The uplink transmission path includes an MCG path or an SCG path.
[0112] In one possible design, the method further includes:
[0113] The main network device sends a fourth indication message to the first node, the fourth indication message being used to indicate the information carried by the first signaling transmitted on the uplink transmission path.
[0114] In one possible design, the first signaling includes an F1-C message.
[0115] In one possible design, the first signaling radio bearer includes an SRB3 or a split SRB.
[0116] In one possible design, if the first signaling radio bearer is SRB3, the method includes:
[0117] The primary network device sends the first signaling to the secondary network device. The secondary network device encapsulates the first signaling in an RRC message and sends it to the first node via SRB3.
[0118] In one possible design, if the first signaling radio bearer is a split SRB, the method includes:
[0119] The primary network device encapsulates the first signaling in an RRC message and sends the RRC message to the secondary network device. The secondary network device then sends the RRC message to the first node via a split SRB.
[0120] This method enables the transmission of F1-C messages along the SCG path, thereby improving the reliability of F1-C message transmission.
[0121] In its eleventh aspect, this application provides a communication method, comprising:
[0122] The primary network device receives the fifth instruction information from the secondary network device and sends the first signaling to the secondary network device according to the fifth instruction information.
[0123] The fifth indication information is used to instruct the first signaling to transmit the corresponding bearer information on the SCG path.
[0124] In one possible design, before the primary network device receives the fifth indication information from the secondary network device, the method further includes:
[0125] The primary network device sends a sixth instruction message to the secondary network device, the sixth instruction message being used to request the secondary network device to transmit the first signaling.
[0126] In one possible design, the method further includes:
[0127] The main network device sends a third indication information to the first node. The third indication information is used to indicate the information of the uplink transmission path used to transmit the first signaling. The uplink transmission path includes MCG or SCG.
[0128] In one possible design, the method further includes:
[0129] The main network device sends a fourth indication message to the first node, the fourth indication message being used to indicate the information carried by the first signaling transmitted on the uplink transmission path.
[0130] In one possible design, the first signaling includes an F1-C message.
[0131] In one possible design, the first signaling radio bearer includes an SRB3 or a split SRB.
[0132] In one possible design, if the first signaling radio bearer is SRB3, the method includes:
[0133] The primary network device sends the first signaling to the secondary network device. The secondary network device encapsulates the first signaling in an RRC message and sends it to the first node via SRB3.
[0134] In one possible design, if the first signaling radio bearer is a split SRB, the method includes:
[0135] The primary network device encapsulates the first signaling in an RRC message and sends the RRC message to the secondary network device. The secondary network device then sends the RRC message to the first node via a split SRB.
[0136] In a twelfth aspect, this application provides a communication device comprising: a module for executing the aforementioned first aspect and any possible implementation thereof.
[0137] In a thirteenth aspect, this application provides a communication device comprising: a module for executing the aforementioned second aspect and any possible implementation thereof.
[0138] In a fourteenth aspect, this application provides a communication device comprising: a module for executing the aforementioned third aspect and any possible implementation thereof.
[0139] In a fifteenth aspect, this application provides a communication device comprising: a module for executing the aforementioned fourth aspect and any possible implementation thereof.
[0140] In a sixteenth aspect, this application provides a communication device comprising: a module for performing the aforementioned fifth aspect and any possible implementation thereof.
[0141] In a seventeenth aspect, this application provides a communication device comprising: a module for executing the aforementioned sixth aspect and any possible implementation thereof.
[0142] In an eighteenth aspect, this application provides a communication device comprising: a module for performing the aforementioned seventh aspect and any possible implementation thereof.
[0143] In a nineteenth aspect, this application provides a communication device comprising: a module for executing the aforementioned eighth aspect and any possible implementation thereof.
[0144] In a twentieth aspect, this application provides a communication device comprising: a module for executing the aforementioned ninth aspect and any possible implementation thereof.
[0145] In a twentieth aspect, this application provides a communication device comprising: a module for executing the aforementioned tenth aspect and any possible implementation thereof.
[0146] In a twentieth aspect, this application provides a communication device comprising: a module for executing any possible implementation of the aforementioned eleventh aspect.
[0147] In a twenty-third aspect, a network node is provided, comprising: a processor. The processor is connected to a memory for storing computer-executable instructions, and the processor executes the computer-executable instructions stored in the memory to implement any of the methods provided in any of the preceding aspects. The memory and processor may be integrated together or may be separate devices. If the latter, the memory may be located within or outside the network node.
[0148] In one possible implementation, the processor includes logic circuitry and input and / or output interfaces. The output interfaces are used to perform the sending action in the corresponding method, and the input interfaces are used to perform the receiving action in the corresponding method.
[0149] In one possible implementation, the network node further includes a communication interface and a communication bus, with the processor, memory, and communication interface connected via the communication bus. The communication interface is used to perform the sending and receiving actions in the corresponding method. The communication interface can also be called a transceiver. Optionally, the communication interface includes a transmitter and a receiver; in this case, the transmitter is used to perform the sending action in the corresponding method, and the receiver is used to perform the receiving action in the corresponding method.
[0150] In one possible implementation, network nodes exist in the form of chips.
[0151] In a twentieth aspect, a computer-readable storage medium is provided, including instructions that, when executed on a computer, cause the computer to perform any of the methods provided in any of the preceding aspects.
[0152] In a twenty-fifth aspect, a computer program product containing instructions is provided, which, when executed on a computer, cause the computer to perform any of the methods provided in any of the preceding aspects.
[0153] In a twenty-sixth aspect, a system-on-a-chip (SoC) is provided, which is used in a network node. The SoC includes at least one processor, in which program instructions are executed to perform any of the methods provided in any of the preceding aspects.
[0154] In a twentieth aspect, a communication system is provided, comprising one or more network nodes selected from the network nodes provided in the twelfth to twenty-second aspects above.
[0155] It should be noted that any of the possible implementations of any of the above aspects can be combined, provided that the solutions do not contradict each other. Attached Figure Description
[0156] Figure 1 This application provides a schematic diagram of an IAB networking scenario.
[0157] Figure 2 A schematic diagram of the nodes in the transmission path provided in the embodiments of this application;
[0158] Figure 3 , Figure 4 These are schematic diagrams of a protocol stack architecture provided in embodiments of this application;
[0159] Figure 5 A schematic diagram of the RLC channel, RLC bearer, and logical channel provided in the embodiments of this application;
[0160] Figure 6 This is a schematic diagram illustrating the scene switching within the host node.
[0161] Figures 7-1 to 7-3 These are schematic diagrams illustrating the scenarios of host node switching provided in the embodiments of this application;
[0162] Figures 7-4 to 7-6 These are schematic diagrams illustrating dual-connection scenarios provided in the embodiments of this application;
[0163] Figures 8 to 14 A flowchart illustrating the communication method provided in the embodiments of this application;
[0164] Figure 15-1 A flowchart illustrating the communication method provided in the embodiments of this application;
[0165] Figure 15-2 A schematic diagram of the related protocol stack processing for SRB3 transmission provided in the embodiments of this application;
[0166] Figure 15-3 A schematic diagram of the relevant protocol stack processing for split SRB transmission provided in the embodiments of this application;
[0167] Figures 16 to 19 A flowchart illustrating the communication method provided in the embodiments of this application;
[0168] Figures 20 to 22 These are schematic diagrams of the structure of a network node provided in the embodiments of this application. Detailed Implementation
[0169] The technical solutions of the embodiments of this application will be described below with reference to the accompanying drawings. In the description of this application, unless otherwise stated, " / " indicates "or," for example, A / B can mean A or B. "And / or" in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Furthermore, in the description of this application, unless otherwise stated, "multiple" refers to two or more. Additionally, to facilitate a clear description of the technical solutions of the embodiments of this application, the terms "first," "second," etc., are used in the embodiments of this application to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first," "second," etc., do not limit the quantity or execution order, and that "first," "second," etc., do not necessarily imply differences.
[0170] The technical solutions of this application can be applied to various communication systems, such as Orthogonal Frequency-Division Multiple Access (OFDMA), Single Carrier Frequency-Division Multiple Access (SC-FDMA), and other systems. The term "system" can be used interchangeably with "network." OFDMA systems can implement wireless technologies such as Evolved Universal Terrestrial Radio Access (E-UTRA) and Ultramobile Broadband (UMB). E-UTRA is an evolved version of the Universal Mobile Telecommunications System (UMTS). 3GPP uses a new version of E-UTRA in Long Term Evolution (LTE) and various versions based on LTE evolution. The 5th-generation (5G) communication system, employing New Radio (NR), is a next-generation communication system currently under research. Furthermore, the communication system can also be applied to future-oriented communication technologies, all of which are applicable to the technical solutions provided in this application.
[0171] The equipment involved in this application includes terminals and wireless backhaul nodes.
[0172] The terminal in this application embodiment can also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or user device. The terminal can also be a station (ST) in a wireless local area network (WLAN), which can be a cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA) device, handheld device with wireless communication capabilities, computing device, or other processing device connected to a wireless modem, vehicle-mounted device, or wearable device (also referred to as wearable smart device). The terminal can also be a terminal in a next-generation communication system, such as a terminal in 5G or a terminal in a future evolved public land mobile network (PLMN).
[0173] A wireless backhaul node is used to provide wireless backhaul services to nodes (e.g., terminals) that wirelessly access the wireless backhaul node. The wireless backhaul service refers to data and / or signaling backhaul services provided through a wireless backhaul link.
[0174] The system architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. Those skilled in the art will understand that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems. The embodiments of this application use the application of the provided method in an NR system or a 5G network as an example for illustration. However, it should be noted that the method provided in the embodiments of this application can also be applied to other networks, such as an evolved packet system (EPS) network (i.e., the commonly referred to fourth-generation (4G) network). Accordingly, when the method provided in the embodiments of this application is applied to an EPS network, the network node executing the method provided in the embodiments of this application can be replaced with a network node in the EPS network. For example, when the method provided in the embodiments of this application is applied to a 5G network or an NR system, the wireless backhaul node mentioned below can be a wireless backhaul node in the 5G network. For example, a wireless backhaul node in the 5G network can be called an IAB node, or it can have other names; the embodiments of this application do not specifically limit this. When the method provided in the embodiments of this application is applied in an EPS network, the wireless backhaul node mentioned below can be a wireless backhaul node in the EPS network. For example, a wireless backhaul node in the EPS network can be called a relay node (RN).
[0175] With the development of technologies such as virtual reality (VR), augmented reality (AR), and the Internet of Things (IoT), there will be an increasing number of terminals in the future network, and the usage of network data will continue to rise. To accommodate the increasing number of terminals and the rapidly growing network data usage, higher demands are being placed on the capacity of 5G networks. In hotspot areas, the use of high-frequency small cell networks is becoming increasingly popular to meet the ultra-high capacity requirements of 5G. High-frequency carriers have poor propagation characteristics, are severely attenuated by obstructions, and have limited coverage; therefore, a large number of small cells need to be densely deployed in hotspot areas. These small cells can serve as IAB (Information, Access, and Block) nodes.
[0176] To design flexible and convenient access and backhaul solutions, both the access link (AL) and backhaul link (BL) in the IAB scenario can adopt wireless transmission schemes.
[0177] In a network containing IAB nodes (hereinafter referred to as an IAB network), the IAB nodes can provide wireless access services to terminals and connect to the host node (donor node) via a wireless backhaul link to transmit user service data. For example, the host node can be a host base station. In a 5G network, the host node can be simply referred to as an IAB donor or DgNB (i.e., donor gNodeB). The host node can be a complete entity, or it can be a separate entity consisting of a centralized unit (CU) (hereinafter referred to as donor-CU, or simply CU) and a distributed unit (DU) (hereinafter referred to as donor-DU), i.e., the host node consists of donor-CU and donor-DU. In this application, the embodiments and accompanying drawings mainly use the example of a host node consisting of donor-CU and donor-DU to illustrate the method provided in this application.
[0178] The donor-CU can also be a separate form of user plane (UP) (hereinafter referred to as CU-UP) and control plane (CP) (hereinafter referred to as CU-CP), that is, the donor-CU is composed of CU-CP and CU-UP.
[0179] IAB nodes connect to the core network via a wired link through the host node. For example, in a standalone 5G architecture, IAB nodes connect to the 5G network core (5G core, or 5GC) via a wired link through the host node. In a non-standalone 5G architecture, IAB nodes connect to the evolved packet core (EPC) via an evolved NodeB (eNB) on the control plane, and to the EPC via the host node and eNB on the user plane.
[0180] To ensure the reliability of service transmission, the IAB network supports multi-hop IAB nodes and multi-connection IAB node networking. Therefore, multiple transmission paths may exist between the terminal and the host node. On a single path, there is a defined hierarchical relationship between IAB nodes, and between IAB nodes and the host nodes serving them. Each IAB node considers the node providing backhaul services to it as its parent node. Correspondingly, each IAB node can be considered a child node of its parent node.
[0181] For example, see Figure 1In this architecture, IAB node 1's parent node is the host node, which in turn is the parent node of IAB nodes 2 and 3. IAB nodes 2 and 3 are both parent nodes of IAB node 4, and IAB node 5's parent node is IAB node 2. Uplink data packets from the terminal can be transmitted to the host node via one or more IAB nodes, and then sent by the host node to the mobile gateway device (e.g., a user plane function (UPF) element in a 5G network). The path for transmitting uplink data packets is called the uplink transmission path. Downlink data packets are received by the host node from the mobile gateway device and then sent to the terminal via one or more IAB nodes. The path for transmitting downlink data packets is called the downlink transmission path. For example, Figure 1 In the diagram, there are two available paths for data packet transmission between Terminal 1 and the host node: Terminal 1 → IAB Node 4 → IAB Node 3 → IAB Node 1 → Host Node, and Terminal 1 → IAB Node 4 → IAB Node 2 → IAB Node 1 → Host Node. There are three available paths for data packet transmission between Terminal 2 and the host node: Terminal 2 → IAB Node 4 → IAB Node 3 → IAB Node 1 → Host Node, Terminal 2 → IAB Node 4 → IAB Node 2 → IAB Node 1 → Host Node, and Terminal 2 → IAB Node 5 → IAB Node 2 → IAB Node 1 → Host Node.
[0182] Understandably, in an IAB network, a transmission path between a terminal and a host node can contain one or more IAB nodes. Each IAB node needs to maintain a radio backhaul link to its parent node and also maintain radio links with its child nodes. If an IAB node is the node through which a terminal accesses, the link between that IAB node and its child nodes (i.e., the terminal) is a radio access link. If an IAB node is the node that provides backhaul services to other IAB nodes, the link between that IAB node and its child nodes (i.e., the other IAB nodes) is a radio backhaul link. See, for an example... Figure 1 In the path “Terminal 1 → IAB Node 4 → IAB Node 3 → IAB Node 1 → Host Node”, Terminal 1 accesses IAB Node 4 via a wireless access link, IAB Node 4 accesses IAB Node 3 via a wireless backhaul link, IAB Node 3 accesses IAB Node 1 via a wireless backhaul link, and IAB Node 1 accesses the host node via a wireless backhaul link.
[0183] In some other embodiments, for example, the IAB node can be a customer premises equipment (CPE), a residential gateway (RG), or other similar devices. In this case, the method provided in this application embodiment can also be applied to home access scenarios.
[0184] The above IAB networking scenarios are merely examples. In IAB scenarios that combine multi-hop and multi-connection, there are many other possibilities for IAB networking, such as a host node and an IAB node under another host node forming a dual connection to provide terminal services, etc., which will not be listed here.
[0185] To make the embodiments of this application clearer, some contents and concepts related to the embodiments of this application will be uniformly introduced here.
[0186] 1. Links, the previous hop node of a node, the next hop node of a node, the ingress link of a node, and the egress link of a node.
[0187] Link: refers to the path between two adjacent nodes in a path.
[0188] The previous hop node of a node: This refers to the last node in the path containing that node to receive the data packet before that node. The previous hop node of a node can also be called the previous hop node of the data packet. For an example, see still... Figure 1 For downlink transmission, IAB node 3 can be referred to as the previous hop node of IAB node 4. For uplink transmission, IAB node 4 can be referred to as the previous hop node of IAB node 3.
[0189] The next-hop node of a node is the first node in the path that contains the node to receive the data packet after that node. The next-hop node of a node can also be called the next-hop node of the data packet.
[0190] The ingress link of a node refers to the link between the node and its previous hop node; it can also be called the previous hop link of a node.
[0191] The egress link of a node refers to the link between the node and its next-hop node, also known as the next-hop link of a node.
[0192] Ingress Radio Link Control Channel (RLC): This refers to the backhaul radio link control channel between the node and its previous hop node.
[0193] Egress RLC Radio Link Control Channel: This refers to the backhaul radio link control channel between the node and its next-hop node.
[0194] 2. Access to IAB nodes and intermediate IAB nodes
[0195] In this application embodiment, the access IAB node refers to the IAB node that the terminal accesses, and the intermediate IAB node refers to the IAB node that provides wireless backhaul services to other IAB nodes (e.g., access IAB nodes or other intermediate IAB nodes).
[0196] For example, see Figure 1 In the path "Terminal 1 → IAB Node 4 → IAB Node 3 → IAB Node 1 → Host Node", IAB Node 4 is the access IAB node, and IAB Node 3 and IAB Node 1 are intermediate IAB nodes. IAB Node 3 provides backhaul services to IAB Node 4, and IAB Node 1 provides backhaul services to IAB Node 3.
[0197] It's important to note that, from the perspective of the terminal accessing that IAB node, it is an access IAB node. All other IAB nodes on the path between the access IAB node and the host node are intermediate IAB nodes. Therefore, whether an IAB node is a specific access IAB node or an intermediate IAB node is not fixed and needs to be determined based on the specific application scenario. For example, see [link to relevant documentation]. Figure 1 IAB node 4 can be referred to as the access IAB node of UE1, and IAB node 3 can be referred to as the intermediate IAB node.
[0198] 3. Composition of IAB nodes
[0199] An IAB node can have both MT (Mediator) and DU (Dedicated Access Provider) roles. When an IAB node faces its parent node, it can be considered an endpoint. In this case, the IAB node acts as an MT. When an IAB node faces its child node (which may be an endpoint or an endpoint portion of another IAB node), it can be considered a network device. In this case, the IAB node acts as a DU. Therefore, an IAB node can be considered to consist of an MT part and a DU part. An IAB node can establish a backhaul connection with at least one of its parent nodes through its MT part. The DU part of an IAB node can provide access services to endpoints or the MT parts of other IAB nodes.
[0200] For example, see Figure 2The terminal connects to the host node sequentially through IAB Node 2 and IAB Node 1. Both IAB Node 1 and IAB Node 2 include a DU (Dedicated Access Unit) portion and a MT (Maintenance Module) portion. The DU portion of IAB Node 2 provides access services to the terminal. The DU portion of IAB Node 1 provides access services to the MT portion of IAB Node 2. The donor-DU provides access services to the MT portion of IAB Node 1. The donor-DU and donor-CU can be connected via the F1 interface. The donor-CU can be connected to the core network via the NG interface.
[0201] In this embodiment of the application, the MT part of the IAB node can be simply referred to as IAB-MT (or IAB-UE), and the DU part of the IAB node can be simply referred to as IAB-DU.
[0202] 4. Protocol stack architecture of intermediate IAB nodes, access IAB nodes, donor-DU, donor-CU, and terminals.
[0203] Intermediate IAB nodes in the user plane protocol stack (e.g.) Figure 3 (as shown in (a)) and the control plane protocol stack (such as Figure 3 (b) is the same.
[0204] The protocol stacks for the user plane and control plane of IAB nodes are different; please refer to the following for details. Figure 3 (c) and Figure 3 (d) in the middle.
[0205] For example, based on Figure 3 The example shown illustrates the user plane protocol stack architecture for each node. Figure 4 In section (a), the control plane protocol stack architecture of each node can be found in [reference]. Figure 4 (b) in the middle.
[0206] in, Figure 3 , Figure 4The meanings of each protocol layer are as follows: Packet Data Convergence Protocol (PDCP) layer, General Packet Radio Service Tunneling Protocol User Plane (GTP-U) layer, User Datagram Protocol (UDP) layer, Internet Protocol (IP) layer, Layer 2 (L2), Layer 1 (L1), Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, Physical (PHY) layer, Radio Resource Control (RRC) layer, F1 Application Protocol (F1AP) layer, and Stream Control Transmission Protocol (SCTP) layer. Among these, Layer 2 is the data link layer; for example, Layer 2 can be the data link layer in the Open Systems Interconnection (OSI) reference model. The L1 layer can be a physical layer; for example, the L1 layer can be the physical layer in the OSI reference model.
[0207] It should be noted that, Figure 4 The examples used here are those where the host node consists of a donor-DU and a donor-CU. Therefore, Figure 4 The protocol layers of donor-DU and donor-CU are shown in the diagram. If the host node is a fully functional entity, the host node only needs to retain the protocol stack of the external node interface of donor-DU and donor-CU, and there is no need for the protocol layer on the internal interface between donor-DU and donor-CU.
[0208] Additionally, it should be noted that, regardless of whether it's the control plane protocol stack architecture or the user plane protocol stack architecture, when the donor-DU acts as a proxy node for the F1 interface between the donor-CU and the IAB node, the protocol stack architecture of the donor-DU facing the IAB node includes, above the IP layer, UDP and GTP-U layers that are equivalent to the UDP and GTP-U layers in the protocol stack architecture of the DU part of the accessed IAB node (not included in...). Figure 4 (as shown in the image).
[0209] 5. Protocol layer of F1 interface and protocol layer of wireless backhaul interface
[0210] The F1 interface can refer to the logical interface between an IAB node (e.g., IAB-DU) and a host node (e.g., donor-CU). The F1 interface can also have other names and supports both the user plane and control plane. The protocol layer of the F1 interface refers to the communication protocol layer on the F1 interface.
[0211] In other embodiments, the F1 interface may also refer to the wired interface between the donor-CU and the donor-DU.
[0212] For example, the user plane protocol layer of the F1 interface may include one or more of the IP layer, UDP layer, and GTP-U layer. Optionally, the user plane protocol layer of the F1 interface may also include a PDCP layer and / or an IP security (IPsec) layer.
[0213] For example, the control plane protocol layer of the F1 interface may include one or more of the IP layer, F1AP layer, and SCTP layer. Optionally, the control plane protocol layer of the F1 interface may also include one or more of the PDCP layer, IPsec layer, and datagram transport layer security (DTLS) layer.
[0214] A wireless backhaul interface refers to the logical interface between IAB nodes or between an IAB node and a host node (or donor-DU). The protocol layer of a wireless backhaul interface refers to the communication protocol layer on that interface. The protocol layer of a wireless backhaul interface includes one or more of the following layers: Backhaul Adaptation Protocol (BAP) layer, RLC layer, MAC layer, and PHY layer.
[0215] For example, the user plane protocol layer of the F1 interface of the IAB node includes a GTP-U layer, a UDP layer, and an IP layer. See also: Figure 4 In (a) of the example, the GTP-U and UDP layers of the IAB node are equivalent to the donor-CU, and the IP layer is equivalent to the donor-DU. In another scenario, the donor-DU acts as a proxy node for the F1 interface between the donor-CU and the IAB node, with the GTP-U, UDP, and IP layers of the IAB node being equivalent to the protocol layers in the donor-DU, respectively. It should be noted that if security protection for the F1 interface is considered, the user plane protocol layer of the F1 interface can also include an IPsec layer and / or a PDCP layer. In one possible implementation, the IPsec layer or PDCP layer is located above the IP layer and below the GTP-U layer.
[0216] For example, the control plane protocol layer of the F1 interface of the IAB node includes the F1AP layer, SCTP layer, and IP layer. See also: Figure 4 In (b), the F1AP and SCTP layers of the IAB node are equivalent to the donor-CU, and the IP layer is equivalent to the donor-DU. In another scenario, the donor-DU acts as a proxy node for the F1 interface between the donor-CU and the IAB node, and the F1AP, SCTP, and IP layers of the IAB node are equivalent to the donor-DU. It should be noted that if security protection for the F1 interface is considered, the control plane protocol layer of the F1 interface can also include one or more of the IPsec, PDCP, and DTLS layers. In one possible implementation, the IPsec, PDCP, or DTLS layer is located above the IP layer and below the F1AP layer.
[0217] It is understandable that when a security protection protocol layer is introduced into the F1 interface protocol layer, then... Figure 3 , Figure 4 The protocol stack architecture of some nodes may change; please refer to the text for details. This application embodiment... Figure 3 , Figure 4 The protocol stack architecture of each node in the IAB network shown is merely an example. The method provided in this application does not depend on this example, but rather uses this example to make the method provided in this application easier to understand.
[0218] 6. Transmitter protocol stack, receiver protocol stack
[0219] In the embodiments of this application, the sending-side protocol stack of a node refers to the protocol stack of that node facing the next-hop node, and the receiving-side protocol stack of a node refers to the protocol stack of that node facing the previous-hop node.
[0220] For example, in Figure 4In the protocol stack architecture shown, for uplink transmission, the protocol stack facing the terminal in the DU part of the access IAB node (IAB node 2) is the receiving-side protocol stack, and the protocol stack facing the host node or donor-CU is the transmitting-side protocol stack. The protocol stack in the MT part of the access IAB node is the transmitting-side protocol stack. The protocol stack in the DU part of the intermediate IAB node is the receiving-side protocol stack, and the protocol stack in the MT part of the intermediate IAB node is the transmitting-side protocol stack. The protocol stack facing the IAB node in the donor-DU is the receiving-side protocol stack, and the protocol stack facing the donor-CU in the donor-DU is the transmitting-side protocol stack. For downlink transmission, the protocol stack facing the terminal in the DU part of the access IAB node is the transmitting protocol stack, and the protocol stack facing the host node or donor-CU is the receiving protocol stack. The protocol stack in the MT part of the access IAB node is the receiving protocol stack. The protocol stack in the DU part of the intermediate IAB node is the transmitting protocol stack, the protocol stack in the MT part of the intermediate IAB node is the receiving protocol stack, the protocol stack facing the IAB node in the donor-DU is the transmitting protocol stack, and the protocol stack facing the donor-CU in the donor-DU is the receiving protocol stack.
[0221] Hereinafter, the sending-side protocol stack will be referred to as the sending side, and the receiving-side protocol stack will be referred to as the receiving side.
[0222] 7. Upper protocol layer, lower protocol layer
[0223] In this embodiment of the application, the hierarchical relationship of the protocol layers is defined as follows: during the process of a node sending data, the protocol layer that processes the data packet first is above the protocol layer that processes the data packet later, that is, the protocol layer that processes the data packet first can be considered as the upper protocol layer of the protocol layer that processes the data packet later; or, during the process of a node receiving data, the protocol layer that processes the data packet first is below the protocol layer that processes the data packet later, that is, the protocol layer that processes the data packet first can be considered as the lower protocol layer of the protocol layer that processes the data packet later.
[0224] For example, see Figure 3 In the protocol stack of the intermediate IAB node, the BAP layer is the upper protocol layer above the RLC, MAC, and PHY layers, while the RLC, MAC, and PHY layers are the lower protocol layers below the BAP layer. Furthermore, it should be noted that in this embodiment, for a given node, the transmitting-side protocol stack is considered the lower protocol stack of the receiving-side protocol stack. For example, for uplink data packets from the intermediate IAB node, the BAP layer of the MT part (i.e., the transmitting-side protocol stack) is the lower protocol layer of the BAP layer of the DU part (i.e., the receiving-side protocol stack).
[0225] It should be noted that for downlink data packets accessing the IAB node, since the protocol layer of the MT part and the protocol stack facing the host node or donor-CU in the DU part of the access IAB node are both receiver-side protocol stacks, the BAP layer of the MT part is a lower protocol layer than the IP layer of the DU part. For uplink data packets accessing the IAB node, since the protocol layer of the MT part and the protocol stack facing the host node or donor-CU in the DU part of the access IAB node are both sender-side protocol stacks, the BAP layer of the MT part is a lower protocol layer than the IP layer of the DU part.
[0226] 8. RLC channel (RLC CH) and logical channel (LCH)
[0227] An RLC channel refers to the channel between the RLC layer and an upper protocol layer (e.g., the Adapt layer). A logical channel refers to the channel between the RLC layer and a lower protocol layer (e.g., the MAC layer). A logical channel can also be called a MAC logical channel. An RLC bearer refers to both the RLC layer entity and the MAC logical channel.
[0228] Currently, the configuration of a terminal's radio bearer (RB) corresponds to both higher-layer (e.g., PDCP layer) and lower-layer (e.g., RLC layer and MAC layer) configurations. The RLC bearer configuration refers to the lower-layer configuration corresponding to the RB, specifically including the RLC layer entity and the MAC logical channel configuration. In this paper, the RLC bearer of an IAB node on the radio backhaul link includes the RLC layer and the MAC logical channel. The RLC channel on the radio backhaul link can refer to the channel between the RLC layer and the PDCP layer, or it can refer to the channel between the RLC layer and the Adapt layer, depending on the upper protocol layer of the RLC layer. The following explanation uses the RLC channel as an example, referring to the channel between the RLC layer and the Adapt layer. The RLC channels of an IAB node on the radio backhaul link correspond one-to-one with the RLC layer entities, and the RLC channels also correspond one-to-one with the RLC bearers. For details, please refer to [link to relevant documentation]. Figure 5 To understand.
[0229] The terminal's RB can be either a data radio bearer (DRB) or a signaling radio bearer (SRB).
[0230] For ease of description, RLC channels, RLC bearers, and logical channels will be collectively referred to as service differentiation channels in the following text. That is to say, the service differentiation channel in the following text can be replaced by any one of RLC channels, RLC bearers, and logical channels.
[0231] 9. Routing and bearer selection
[0232] In this embodiment of the application, routing is used to select and determine a routing ID for data packets.
[0233] The bearer selection in this application embodiment can also be called QoS selection. Bearer selection is used to select the RLC bearer, RLC channel, or logical channel for transmitting data packets.
[0234] 10. Routing table
[0235] For a given node, its routing table includes one or more route identifiers, and the identifier of the next-hop node corresponding to that route identifier. Different nodes corresponding to the same route identifier have different routing tables. For example, for a transmission path identified by route identifier 1, the three nodes in this transmission path are node 1-node 2-node 3 in sequence. Node 1's routing table includes route identifier 1 and the identifier of node 2, and there is a correspondence between route identifier 1 and the identifier of node 2. Node 2's routing table includes route identifier 1 and the identifier of node 3.
[0236] As one possible implementation, the donor-CU distributes the corresponding routing table to each IAB node it manages / controls. The donor-CU also sends the routing table corresponding to the donor-DU to its fellow donor-DU.
[0237] Current communication standards, such as those mentioned in R16, address scenarios where IAB nodes perform intra-donor-CU handover, such as... Figure 6 As shown, the IAB node switches from the source parent node (donor-DU1) to the target parent node (donor-DU2), where both the source and target parent nodes are connected to the same donor-CU. In this scenario, the IAB node undergoing the switch can be called the switching IAB node. The IAB-MT and IAB-DU of the switching IAB node are managed / controlled only by the same donor-CU. In this scenario, the terminal's service data can remain continuous and uninterrupted during the IAB node switchover. However, the current standard does not address how to prevent terminal data interruption in inter-donor-CU switchover scenarios. Furthermore, unlike the Intra-donor-CU switchover scheme where the MT and DU parts of the switching IAB node are connected to the same host node, in Inter-donor-CU switchover, the MT and DU parts of the IAB node can be connected to different host nodes. Therefore, the existing Intra-donor-CU switchover scheme is not applicable to Inter-donor-CU switchover scenarios.
[0238] To improve the continuity of terminal service data in Inter-donor-CU handover scenarios, this application provides a communication method as shown in the following embodiments. These embodiments are applied to Inter-donor-CU handover scenarios. Figure 7-1 The image shows an example of an Inter-donor-CU handover scenario applicable to the embodiments of this application.
[0239] Taking the IAB2 node handover as an example, IAB2-MT switches from the source parent node IAB1-DU to the target parent node IAB4-DU. IAB1-DU and IAB4-DU are managed / controlled by different donor-CUs. Specifically, IAB1-DU is managed / controlled by donor-CU1, and IAB4-DU is managed / controlled by donor-CU2. Donor-CU1 is referred to as the source donor-CU for this handover, and donor-CU2 is referred to as the target donor-CU for this handover.
[0240] Before IAB2 performs the switchover, the host nodes of each IAB node and the connection relationships between IAB nodes and their host nodes are as follows:
[0241] The host node for nodes IAB1, IAB2, IAB3, and the terminal is donor-CU1; that is, nodes IAB1, IAB2, IAB3, and the terminal are all managed / controlled by donor-CU1. IAB1-MT establishes an RRC connection with donor-CU1, and IAB1-DU establishes an F1 connection with donor-CU1. IAB2-MT establishes an RRC connection with donor-CU1, and IAB2-DU (e.g., ...) establishes an F1 connection with donor-CU1. Figure 7-1 The leftmost IAB-DU establishes an F1 connection with donor-CU1. IAB3-MT establishes an RRC connection with donor-CU1, and the IAB3-DU (e.g., ...) Figure 7-1 The left IAB3-DU establishes an F1 connection with the donor-CU1. The UE establishes an RRC connection with the donor-CU1.
[0242] The IAB4 node is managed / controlled by the donor-CU2, that is: IAB4-MT establishes an RRC connection with the donor-CU2, and IAB4-DU establishes an F1 connection with the donor-CU2.
[0243] Figure 7-1 In this system, black nodes or parts of nodes are managed by donor-CU2, while white nodes or parts of nodes are managed by donor-CU1. (Following...) Figure 7-2 or Figure 7-3 The black and white in the attached diagrams represent the meanings of... Figure 7-1 Similar to the Chinese.
[0244] In some cases, for IAB2, IAB2-MT performs the handover first, or completes the handover first. That is, IAB2-MT switches to donor-CU2 first, while IAB2-DU has not yet switched to donor-CU2 (i.e., IAB2-DU has not yet established an F1 connection with donor-CU2). In this case, after IAB2-MT performs the handover, the host nodes of each IAB node and the connection relationships between them are as follows:
[0245] Nodes IAB1, IAB3, and the terminal are also managed / controlled by donor-CU1, while node IAB4 is managed / controlled by donor-CU2. That is, IAB1-MT maintains an RRC connection with donor-CU1, and IAB1-DU maintains an F1 connection with donor-CU1. IAB3-MT maintains an RRC connection with donor-CU1, and IAB3-DU (such as...) Figure 7-1 The left IAB3-DU maintains an F1 connection with donor-CU1. The terminal maintains an RRC connection with donor-CU1. The IAB4-MT maintains an RRC connection with donor-CU2, and the IAB4-DU maintains an F1 connection with donor-CU2.
[0246] The management / control of the IAB2 node has changed, namely: IAB2-MT establishes an RRC connection with donor-CU2, but IAB2-DU (such as...) Figure 7-1 Of the two IAB2-DUs, the left one maintains an F1 connection with the donor-CU1. In other words, the DU and MT at the same station are connected to different donor-CUs.
[0247] In this application embodiment, for switching IAB nodes, when the IAB-MT of the switching IAB node switches to the target parent node before the IAB-DU, this switching situation is called a top-down switching (or it may have other names). For example, as mentioned above, Figure 7-1 In the switching scenario shown, IAB2-MT switches to the target parent node, i.e., IAB4 node, before IAB2-DU. This switching scenario is a top-down switching.
[0248] In some other cases, see Figure 7-2For the switching node IAB2, the switching can also occur either with IAB2-DU performing the switch before IAB2-MT, or with IAB2-DU completing the switch before IAB2-MT (IAB2-DU switching refers to the switching of IAB2-DU's F1 interface; before the switch, IAB2-DU establishes an F1 connection with donor-CU1, and after the switch, IAB2-DU establishes an F1 connection with donor-CU2). That is, if IAB2-DU, IAB3, and the terminal have already switched to donor-CU2, IAB2-MT has not yet switched to donor-CU2. In this case, after IAB2-DU performs the switch and before IAB2-MT completes the switch, the host nodes of each IAB node and the connection relationships between them are as follows:
[0249] Compared to before the switchover, the host nodes of IAB1 and IAB4 remain unchanged. Specifically, IAB1-MT maintains its RRC connection with donor-CU1, and IAB1-DU maintains its F1 connection with donor-CU1. IAB4-MT maintains its RRC connection with donor-CU2, and IAB4-DU maintains its F1 connection with donor-CU2.
[0250] Compared to before the switchover, the management of terminals, IAB3, and IAB2 has changed after the switchover. Specifically, IAB3-MT establishes an RRC connection with donor-CU2, and IAB3-DU (such as...) Figure 7-2 The black IAB3-DU establishes an F1 connection with donor-CU2. The terminal establishes an RRC connection with donor-CU2. IAB2-MT maintains the RRC connection with donor-CU1, but IAB2-DU (as shown) Figure 7-1 The black IAB2-DU establishes an F1 connection with the donor-CU2.
[0251] In other embodiments, the technical solution of this application can also be applied to dual-connectivity (DC) scenarios. See also Figure 7-4 Taking the IAB2 node as an example again, IAB2-MT operates in dual-connectivity mode, meaning that there are two parent nodes, IAB1-DU and IAB4-DU, existing simultaneously. As one possible implementation, the M-donor acts as the primary base station of IAB2-MT, and the S-donor acts as the secondary base station.
[0252] in, Figure 7-4 In this context, the connection relationships between each IAB node or terminal and the host node are as follows:
[0253] • The IAB1 node is managed / controlled by M-donor-CU1, that is: IAB1-MT establishes an RRC connection with M-donor-CU1, and IAB1-DU establishes an F1 connection with M-donor-CU1;
[0254] • IAB2-MT establishes an RRC connection with M-donor-CU1, and IAB2-DU (such as...) Figure 7-4 The white part in the middle) establishes an F1 connection with M-donor-CU1.
[0255] • The IAB3 node is managed / controlled by M-donor-CU1, that is: IAB3-MT establishes an RRC connection with M-donor-CU1, and IAB3-DU (such as Figure 7-4 The white part on the right side of the middle section establishes an F1 connection with M-donor-CU1;
[0256] • The terminal is managed / controlled by M-donor-CU1, that is: the terminal establishes an RRC connection with M-donor-CU1;
[0257] • The IAB4 node is managed / controlled by S-donor-CU2, that is: IAB4-MT establishes an RRC connection with S-donor-CU2, and IAB4-DU establishes an F1 connection with S-donor-CU2.
[0258] In this embodiment of the application, for switching IAB nodes, when the IAB-DU of the switching IAB node switches to the target parent node before the IAB-MT, this switching situation is called a bottom-up switching (or it may have other names). For example, Figure 7-2 In the switching scenario shown, IAB2-DU switches to the target parent node, i.e., IAB4 node, before IAB2-MT. This switching scenario is a bottom-up switching.
[0259] Figure 7-1 This is merely one example of a communication system applicable to the embodiments of this application. In a specific implementation, the communication system may include more or fewer devices. The topology of the communication system (such as the specific number of connections or hops) may be of other types.
[0260] For example, regarding the link between the IAB2 node and the donor-CU, the IAB2 node can be directly connected to the donor-CU node, meaning there is no IAB1 or IAB4 node, or there are at least two intermediate IAB nodes between the IAB2 node and the donor-CU. That is, in addition to the IAB1 or IAB4 node, there is at least one other IAB node between the IAB2 node and the donor-CU.
[0261] For example, regarding the link between the IAB2 node and the terminal, the terminal can directly connect to the IAB2 node, meaning there is no IAB3 node. Alternatively, there can be at least two intermediate nodes between the terminal and the IAB2 node, meaning there is at least one other IAB node between the terminal and the IAB2 node in addition to the IAB3 node.
[0262] The following describes each embodiment.
[0263] Example 1
[0264] This application provides a communication method, such as... Figure 8 As shown, the method includes:
[0265] S101, The first CU determines the first mapping.
[0266] For ease of description, the “CU of the first host node” mentioned in the embodiments of this application can be referred to as the first CU, the “CU of the second host node” can be referred to as the second CU, the “DU of the first host node” can be referred to as the first DU, and the “DU of the second host node” can be referred to as the second DU.
[0267] In some embodiments of this application, the first host node is the source host node and the second host node is the target host node; or, the first host node is the target host node and the second host node is the source host node.
[0268] The source host node is the host node that manages the IAB node before the switch, and the target host node is the host node that manages the IAB node after the switch.
[0269] In some other embodiments, the first host node is the primary host node and the second host node is the secondary host node; or, the first host node is the secondary host node and the second host node is the primary host node.
[0270] The first mapping includes routing mapping and / or bearer mapping. Routing mapping is the mapping relationship between downlink data and the downlink transmission path. The downlink transmission path includes the transmission path between the first CU and the target node of the downlink data via the second DU. In other words, the downlink transmission path includes the transmission path between the first CU and the target node of the downlink data via the second DU. For example, Figure 7-1 An example of a downlink transmission path is shown.
[0271] Optionally, the mapping relationship between downlink data and downlink transmission paths includes: the destination address of the downlink data, the service attribute information of the downlink data, and the first routing identifier (RoutingID) corresponding to the destination address and service attribute information. The routing identifier can be used to uniquely identify a transmission path. Different transmission paths correspond to different routing identifiers.
[0272] Optionally, downlink data may include business attribute information.
[0273] Optionally, the destination address includes the destination IP address. Optionally, the service attribute information includes a differentiated services code point (DSCP) or a flow label. Service attribute information can distinguish different services to ensure quality of service (QoS). In this way, data carrying different service attribute information can be transmitted through different transmission paths.
[0274] Taking the first host node as the source host node and the second host node as the target host node as an example, in Figure 7-1 In the scenario shown, the first CU is donor-CU1, and the second CU is donor-CU2. Downlink data is sent to the terminal, whose access IAB node is IAB3. Therefore, the destination node for the downlink data is IAB3, and the destination address is the address of IAB3. The downlink transmission path is transmission path 1 between donor-CU1 and IAB3 via donor-DU2. This downlink transmission path 1 corresponds to a route identifier 1. Route mapping is the mapping relationship between downlink data and this route identifier 1. Optionally, this mapping relationship between downlink data and route identifier 1 can refer to the address of IAB3, the service attribute information of the downlink data, the address of IAB3, and the route identifier 1 corresponding to the service attribute information. This means that for downlink data (e.g., downlink data 1) with corresponding service attributes (e.g., DSCP 000111) destined for IAB3, donor-DU2 transmits downlink data 1 through the downlink transmission path (e.g., transmission path 1) corresponding to the route identifier.
[0275] The bearer mapping is the mapping relationship between downlink data and downlink transmission bearers; the downlink transmission bearers include the first RLC channel between the second DU and the first node; the first node is the next-hop node of the second DU. The radio link control RLC channel can also be called the backhaul RLC channel.
[0276] Optionally, the mapping relationship between downlink data and downlink transmission bearer includes: the target address of downlink data, the service attribute information of downlink data, the target address, and the information of the first RLC channel corresponding to the service attribute information.
[0277] Optionally, the RLC channel information includes the identifier of the RLC channel and the node identifiers at both ends of the RLC channel (e.g., the BAP addresses of the nodes). The interpretation of the RLC channel information is applicable to all embodiments of this application.
[0278] See also Figure 7-1 The downlink transmission bearer includes the first RLC channel between donor-DU2 and IAB4-MT. Bearer mapping refers to the mapping relationship between downlink data and this first RLC channel. Optionally, this mapping relationship between downlink data and the first RLC channel can refer to the address of the IAB3 node, the service attribute information of the downlink data, the address of the IAB3 node, and the first RLC channel corresponding to the service attribute information. This means that for downlink data with corresponding service attributes destined for the IAB3 node (e.g., downlink data 1), donor-DU2 will send downlink data 1 to IAB4-MT through the first RLC channel between it and IAB4-MT. In other words, the downlink bearer mapping on donor-DU2 is determined by donor-CU1.
[0279] Still with Figure 7-1 For example, in some embodiments, according to the above scheme, donor-CU1 determines the RLC channel used for transmitting downlink data between donor-DU2 and the IAB4 node, so that after donor-DU2 receives the downlink data from donor-CU1, it maps the downlink data to the corresponding RLC channel and sends it to the IAB4 node. For the IAB4 node, there are two implementation methods for downlink bearer mapping on the IAB4 node:
[0280] As one possible implementation, the donor-CU2 determines the bearer mapping on the IAB4 node. Taking downlink transmission as an example, the donor-CU2 determines the downlink bearer mapping on the IAB4 node, that is, the donor-CU2 determines the mapping relationship between the ingress RLC channel and the egress RLC channel on the IAB4 node, and sends this mapping relationship to the IAB4 node. Here, the ingress RLC channel refers to the RLC channel between the donor-DU2 and the IAB4-MT, and the egress RLC channel refers to the RLC channel between the IAB4-DU and the IAB2-MT. In other words, the donor-CU2 maps downlink data to the ingress RLC channel and sends it to the IAB4-MT. The IAB4-MT extracts the downlink data from the ingress RLC channel and sends it to the IAB4-DU through its internal interface. The IAB4-DU then maps the downlink data to the corresponding egress RLC channel and sends it to the IAB2-MT. In this implementation, the mapping relationship between downlink data and downlink transmission bearer includes information about the ingress RLC channel and the egress RLC channel.
[0281] As another possible implementation, donor-CU1 determines the bearer mapping on the IAB4 node. Taking downlink transmission as an example, donor-CU1 determines the downlink bearer mapping on the IAB4 node, that is, donor-CU1 determines the mapping relationship between the ingress RLC channel and the egress RLC channel on the IAB4 node, and sends the mapping relationship to the IAB4 node through donor-CU2. In this implementation, the mapping relationship between downlink data and downlink transmission bearer includes: information of the ingress RLC channel and information of the egress RLC channel. That is, donor-CU1 sends a first mapping to donor-CU2, and the first mapping also includes: information of the ingress RLC channel and information of the corresponding egress RLC channel. Among them, the RLC channel information includes: the identifier of the RLC channel, and the node identifiers at both ends of the RLC channel (e.g., the BAP address of the node).
[0282] Still with Figure 7-1 For example, in some embodiments, according to the above scheme, after the IAB4 node receives the downlink data from the donor-DU2, it maps the downlink data to the corresponding egress RLC channel and sends it to the IAB2 node. For the IAB2 node, there are two implementation methods for the downlink bearer mapping on the IAB2 node:
[0283] As one possible implementation, the donor-CU1 determines the bearer mapping on the IAB2 node. Taking downlink transmission as an example, the donor-CU1 determines the downlink bearer mapping on the IAB2 node, that is, the donor-CU1 determines the mapping relationship between the ingress RLC channel and the egress RLC channel on the IAB2 node and sends this mapping relationship to the IAB2 node. Here, the ingress RLC channel refers to the RLC channel between IAB4-DU and IAB2-MT, and the egress RLC channel refers to the RLC channel between IAB2-DU and IAB3-MT. In other words, the IAB4-DU maps the downlink data to the ingress RLC channel and sends it to the IAB2-MT. The IAB2-MT extracts the downlink data from the ingress RLC channel and sends it to the IAB2-DU through its internal interface. The IAB2-DU then maps the downlink data to the corresponding egress RLC channel and sends it to the IAB3-MT. In this implementation, the mapping relationship between downlink data and downlink transmission bearers includes information about the ingress RLC channel and the egress RLC channel.
[0284] As another possible implementation, donor-CU2 determines the bearer mapping on the IAB2 node. Taking downlink transmission as an example, donor-CU2 determines the downlink bearer mapping on the IAB2 node, that is, donor-CU2 determines the mapping relationship between the ingress RLC channel and the egress RLC channel on the IAB2 node, and sends the mapping relationship to the IAB2 node through donor-CU1. In this implementation, the mapping relationship between downlink data and downlink transmission bearer includes: information of the ingress RLC channel and information of the egress RLC channel. That is, donor-CU2 sends the mapping relationship to donor-CU1, which includes: information of the ingress RLC channel and information of the corresponding egress RLC channel. Among them, the RLC channel information includes: the identifier of the RLC channel, and the node identifiers at both ends of the RLC channel (e.g., the BAP address of the node).
[0285] S102, the first CU sends the first mapping to the second CU.
[0286] Correspondingly, the second CU receives the first mapping from the first CU.
[0287] Optionally, the first CU sends a route mapping to the second CU, that is, the first CU sends the following three parameters to the second CU: the destination address of the downlink data, the service attribute information of the downlink data, and the first route identifier corresponding to the destination address and the service attribute information. The destination address and service attribute information of the downlink data can be used to determine the corresponding first route identifier.
[0288] Optionally, the first CU sends a bearer mapping to the second CU, that is, the first CU sends the following three parameters to the second CU: the destination address of the downlink data, the service attribute information of the downlink data, and the information of the first RLC channel corresponding to the destination address and the service attribute information. The destination address and service attribute information of the downlink data can be used to determine the information of the corresponding first RLC channel.
[0289] An Xn interface is established between the first CU and the second CU. The first CU transmits an XnAP message to the second CU through this interface. The XnAP message carries the first mapping.
[0290] For example, see still Figure 7-1 The donor-CU1 sends the following parameters to the donor-CU2: the destination address of the downlink data (the address of the IAB3 node), the service attribute information of the downlink data, the destination address, and the first routing identifier corresponding to the service attribute information.
[0291] For example, donor-CU1 sends the following parameters to donor-CU2: the destination address of the downlink data (the address of node IAB3), the service attribute information of the downlink data, and the RLC channel information between donor-DU2 and node IAB4. The destination address and service attribute information are associated with the RLC channel information between donor-DU2 and node IAB4, meaning that donor-DU2 can determine the RLC channel to use for sending downlink data based on these two parameters.
[0292] For example, donor-CU1 sends the following parameters to donor-CU2: information about the ingress RLC channel and information about the egress RLC channel. The ingress and egress RLC channel information are correlated so that donor-CU2 can further transmit the mapping relationship to the IAB4 node. This means that the IAB4 node can determine the egress RLC channel to be used for transmitting downlink data based on the ingress RLC channel information.
[0293] It is understandable that the second CU receiving the first mapping from the first CU means that the routing mapping and / or bearer mapping of the nodes managed by the second CU may change. Therefore, the second CU can send the first mapping to the nodes it manages and controls in order to update the routing mapping and / or bearer mapping of the nodes it manages. For example, still using... Figure 7-1 For example, after receiving the first mapping from donor-CU1, donor-CU2 can send the first mapping to donor-DU2 and IAB4 nodes so that each node can perform routing mapping and / or bearer mapping for downlink data based on the first mapping.
[0294] S103, the first CU sends downlink data to the second DU.
[0295] Correspondingly, the second DU receives downlink data from the first CU.
[0296] Still with Figure 7-1 Let's take an example to illustrate the specific process of the first CU sending downlink data to the second DU. Figure 7-1 In this process, the donor-CU1 encapsulates the downlink data sent to the terminal through the GTP-U layer, UDP layer, and IP layer to generate IP packets. The IP layer encapsulation process includes: tagging the downlink data of the terminal with the corresponding service attribute information (such as DSCP / flow tag), carrying the service attribute information in the IP header field, and adding the destination IP address of the IP packet (i.e., the IP address of IAB3) to the IP header field.
[0297] Before the IAB2 node handover, donor-CU1 sends downlink data to the UE through the source path, which includes donor-DU1, IAB1 node, IAB2 node, and IAB3 node. All nodes and terminals on the source path are managed / controlled by donor-CU1. Therefore, donor-CU1 knows the network topology related to these nodes and thus knows the terminal's access IAB node, i.e., the target node is IAB3 node.
[0298] Once IAB2-MT undergoes a handover, donor-CU1 sends downlink data to the UE via the target path, which includes donor-DU2, IAB4 node, IAB2 node, and IAB3 node. Different nodes on the target path are managed / controlled by different donor-CUs. For example, donor-DU2, IAB2-MT, and IAB4 nodes (including IAB4-MT and IAB4-DU) are managed / controlled by donor-CU2, while IAB2-DU, IAB3 nodes (including IAB3-MT and IAB3-DU), and the terminal are managed / controlled by donor-CU1. For downlink data routing along the target path, before the IAB3 node handover, donor-DU2 needs to pre-assign an IP address to the IAB3 node and then send the newly assigned IP address to the IAB3 node sequentially through donor-CU2 and donor-CU1. If donor-CU1 decides to send downlink data to the UE via the target path, the target IP address added to the IP header field by donor-CU1 is updated to the IP address assigned to the IAB3 node by donor-DU2. Since the IP address assigned to the IAB3 node by donor-DU2 has the same network prefix as the IP address of donor-DU2, donor-CU1 can correctly route the generated IP packets to donor-DU2.
[0299] After receiving the IP packet from donor-CU1, donor-DU2 extracts the target IP address (i.e., the IP address of the IAB3 node) and service attribute information (such as DSCP or flow label) from the IP packet, and performs routing and / or bearer selection on the IP packet according to the first mapping previously received from donor-CU2.
[0300] Specifically, donor-DU2 determines the route identifier for an IP packet based on the route mapping received from donor-CU2, such as the following three parameters: destination IP address, service attribute information, and the route identifier corresponding to the destination IP address and service attribute information, as well as the destination IP address and service attribute information carried in the IP packet. For example, if donor-DU2 receives an IP packet from donor-CU1 with a destination IP address of 192.168.6.2 and service attribute information of DSCP 000111, and the route mapping received by donor-DU2 from donor-CU2 is shown in Table 1 (Table 1 is just an example), then donor-DU2 can find from Table 1 that the route identifier corresponding to this IP packet is 1, and performs route selection for this IP packet according to this route identifier.
[0301] Table 1 Routing Map
[0302]
[0303]
[0304] After determining the route identifier of the downlink IP packet, donor-DU2 then uses the routing table received from donor-CU2 (i.e., the route identifier and the corresponding next-hop node address) to determine which next-hop node the IP packet should be routed to. The next-hop node address can be the BAP address of that next-hop node. For example, if the routing table indicates that the next-hop node address corresponding to route identifier 1 is the BAP address of node IAB4, then donor-DU2 knows that the IP packet received from donor-CU1 should be sent to node IAB4.
[0305] donor-DU2 carries the determined routing identifier in the BAP layer and sends it along with the IP packet to the next-hop node, namely the IAB4 node.
[0306] Similarly, based on the bearer mapping received from donor-CU2, such as the target IP address, service attribute information, and the identifier of the RLC channel corresponding to the target IP address and service attribute information, and based on the IP data packet received from donor-CU1, donor-DU2 can determine which RLC channel the IP data packet needs to be mapped to for transmission. For example, donor-DU2 determines that the IP data packet needs to be mapped to... Figure 5 The RLC channel 1 shown is used to send the IP packet to the next-hop node of donor-DU2 via RLC channel 1.
[0307] Similarly, subsequent nodes of donor-CU2, such as Figure 7-1 As shown, IAB4, IAB2, and IAB3 can perform route selection and bearer selection for downlink data received from the preceding node based on the route mapping, bearer mapping, and routing table received from the corresponding host node. For example, see... Figure 7-6 (b) After receiving the IP packet from the ingress RLC channel, the IAB4 node performs BAP layer processing, extracts the routing identifier, and performs routing and bearer selection on the IP packet according to the first mapping obtained from the donor-CU2 (which can be carried in the F1AP message; optionally, an F1 interface is established between IAB4-DU and donor-CU2 to transmit the F1AP message).
[0308] Routing: The IAB4 node looks up the routing table (obtained from the donor-CU2) based on the routing identifier extracted from the BAP layer. That is, based on the routing identifier and the BAP address of the next-hop node corresponding to the routing identifier, it determines which next-hop node the IP packet should be routed to (e.g., to the IAB2 node).
[0309] Bearer selection: The IAB4 node determines which egress RLC channel the IP packet is mapped to based on the bearer mapping obtained from the donor-CU2, namely the identifier of the ingress RLC channel and the identifier of the egress RLC channel corresponding to the ingress RLC channel.
[0310] Similarly, IAB2 and IAB3 nodes perform routing and bearer selection based on the first mapping obtained from donor-CU1.
[0311] Still with Figure 7-1 For example, it can be seen that in the scenario where the IAB2 node switches between host nodes, the MT and DU of the IAB2 node may be connected to different host nodes. In this case, the downlink data can still reach the terminal through the downlink transmission path of donor-CU1->donor-DU2->IAB4->IAB2->IAB3. Therefore, the continuity of terminal services should be improved as much as possible.
[0312] The communication method provided in this application, in a scenario where IAB nodes are switching between host nodes, involves the first CU of the first host node configuring a routing map and / or bearer map corresponding to the downlink transmission path for the terminal's downlink data, and sending this routing map and / or bearer map to the second CU of the second host node. This allows the second CU to further forward the received routing map and / or bearer map to the second DU of the second host node. Thus, after receiving downlink data from the first CU of the first host node, the second DU of the second host node can send the downlink data according to the routing map and / or bearer map, meaning the downlink data can reach the terminal through the second host node, preventing disruption to the terminal's service continuity.
[0313] Optionally, before the first CU determines the first mapping, see Figure 9 The above method may further include the following step S104:
[0314] S104. The second CU sends one or more second route identifiers allocated by the second CU to the first CU.
[0315] Accordingly, the first CU receives one or more second route identifiers assigned by the second CU.
[0316] The first route identifier and one or more second route identifiers are all different.
[0317] In this embodiment of the application, in order to avoid conflicts between the routing identifier allocated by the first CU and the routing identifier allocated by the second CU, before the first CU determines the first mapping (i.e., the routing mapping), the second CU needs to send one or more routing identifiers (i.e., the second routing identifiers) that it has already allocated to the first CU. For example, the second CU can send all the routing identifiers that it has already allocated to the first CU to ensure that the routing identifiers allocated by the first CU and the routing identifiers allocated by the second CU can uniquely identify the transmission path.
[0318] Optionally, before the first CU determines the first mapping, see Figure 9 The above method may further include step S105:
[0319] S105, the second CU sends information about one or more RLC channels between the second DU and the first node, as well as QoS information corresponding to the one or more RLC channels, to the first CU.
[0320] Accordingly, the first CU receives information about one or more RLC channels between the second DU and the first node, as well as QoS information corresponding to one or more RLC channels, from the second CU.
[0321] One or more RLC channels include the first RLC channel.
[0322] In this embodiment, the RLC channel information between the second DU and the first node is configured by the second DU and sent to the first node via an RRC message from the second CU. The first CU cannot obtain the RLC channel information between the second DU and the first node. In order for the first CU to determine the first mapping (i.e., bearer mapping), the first CU needs to be able to obtain the QoS information corresponding to the RLC channel between the second DU and the first node, so that the first CU can determine which RLC channel between the second DU and the first node the downlink data will be mapped to for transmission.
[0323] For example, still using Figure 7-1 For example, if donor-CU1 determines the downlink bearer mapping on donor-DU2, it means that donor-CU1 needs to determine the target address of the downlink data, the service attribute information of the downlink data, the target address, and the RLC channel (i.e., the RLC channel between donor-DU2 and IAB4-MT) corresponding to the service attribute information.
[0324] However, donor-CU1 only knows the RLC channel information of the IAB nodes it manages or controls (such as the RLC channel information between IAB2-DU and IAB3-MT), and does not know the RLC channel information between donor-DU2 and IAB4-MT managed by donor-CU2. Therefore, in order for donor-CU1 to determine the above bearer mapping, donor-CU2 needs to send the QoS information of the RLC channels established between donor-DU2 and IAB4-MT to donor-CU1. For example, donor-CU2 sends the following parameters to donor-CU1: the identifier of donor-DU2, the identifier of the IAB4 node, the identifiers of the RLC channels established between donor-DU2 and IAB4-MT (such as RLC channels 1 to 3), and the QoS information corresponding to each RLC channel (the QoS information corresponding to each of RLC channels 1 to 3).
[0325] Optionally, the node identifier can be the node's BAP address information or other information. For example, the identifier of the IAB4 node can be the BAP address of the IAB4 node, and the identifier of the donor-DU2 can be the BAP address of the donor-DU2. QoS information includes at least one of the following: QoS flow identifier, 5QI, PDU session identifier, and guaranteed bit rate.
[0326] Thus, after receiving information about one or more RLC channels between the second DU and the first node from the second CU, as well as the QoS information corresponding to the one or more RLC channels, the first CU can determine the RLC channels that the second DU needs to use to send downlink data based on the QoS information corresponding to the one or more RLC channels.
[0327] In some embodiments, the service attribute information of the downlink data is determined by the first CU. That is, before the first CU determines the first mapping, the above method may further include the following step S106:
[0328] S106. The first CU determines the business attribute information.
[0329] by Figure 7-1 To illustrate an exemplary method for the first CU to determine service attributes, donor-CU1 receives downlink data from a terminal from a core network device (e.g., UPF). Donor-CU1 can determine the service attribute information (e.g., DSCP / flow label) of the downlink data based on the QoS information of the terminal's downlink data. After receiving the downlink data from the terminal, donor-CU1 determines the service attribute information of the downlink data based on its QoS information and maps the downlink data to the corresponding GTP tunnel before sending it to the target node (e.g., an IAB3 node). Therefore, donor-CU1 can determine the correspondence between the tunnel information and the service attribute information of the downlink data. The tunnel information can be, for example, but is not limited to, GTP-FTEID. GTP-FTEID includes a tunnel identifier (general packet radio service tunneling protocol tunnel endpoint ID, abbreviated as GTP-TEID) and an IP address. For example, the donor-CU1 determines the correspondence between the tunnel information and service attribute information of the downlink data. This correspondence can be the correspondence between the GTP-FTEID and DSCP / flow label allocated by the donor-CU1 on the F1 interface, or the correspondence between the GTP-FTEID and DSCP / flow label allocated by the IAB3-DU on the F1 interface, or the correspondence between the GTP-FTEID allocated by the donor-CU1 on the F1 interface and the GTP-TEID and DSCP / flow label allocated by the IAB3-DU on the F1 interface. Therefore, in this embodiment, after the first CU receives the downlink data from the terminal from the core network device (e.g., UPF), it determines the service attribute information of the downlink data (step S106), and then determines the first mapping based on the information received from the second CU in steps S104 and S105 (step S101).
[0330] Example 2
[0331] Similar to Embodiment 1, the first mapping is determined by the first CU. The scheme for the first CU to determine the first mapping can be found in steps S101 to S105 of Embodiment 1, and will not be repeated here. Unlike Embodiment 1, where the service attributes of the downlink data are determined by the first CU, in Embodiment 2, the service attribute information of the downlink data is determined by the second CU. Specifically, see [link to Embodiment 2]. Figure 10 The communication method in this second embodiment further includes:
[0332] S201. The first CU sends downlink data to the second CU via GTP tunnel information and the corresponding QoS information of the GTP tunnel.
[0333] Still with Figure 7-1 For example, to assist donor-CU2 in determining the service attribute information of the terminal's downlink data, donor-CU1 needs to send the QoS information corresponding to the GTP tunnel of the terminal's downlink data to donor-CU2. Since donor-CU1 maps the terminal's downlink data to the corresponding GTP tunnel and sends it to the target node of the downlink data, the downlink data can be identified through the information of the GTP tunnel. A description of the GTP tunnel information can be found above and will not be repeated here.
[0334] Thus, donor-CU2 (i.e., the second CU) can determine the service attribute information of the terminal's downlink data based on the information received from donor-CU1.
[0335] S202. The first CU receives information about the GTP tunnel for downlink data from the second CU, as well as the service attribute information corresponding to the GTP tunnel.
[0336] Still with Figure 7-1 For example, in order for donor-CU1 (i.e., the first CU) to determine the first mapping, donor-CU2 (the second CU) needs to send the service attribute information of the terminal downlink data determined by donor-CU2 to donor-CU1. For instance, donor-CU2 sends the GTP tunnel information of the terminal downlink data, along with the corresponding service attribute information, to donor-CU1. This service attribute information can be used by donor-CU1 to determine the first mapping of the terminal downlink data (including routing mapping and / or bearer mapping). It can also be used by donor-CU1 to add service attribute information to IP packets.
[0337] S203, The first CU determines the first mapping.
[0338] Optionally, steps S104 and S105 may be included before step S203. As one possible implementation, the first CU determines the first mapping based on the information received from the second CU in steps S104-S105.
[0339] S204, the first CU sends the first mapping to the second CU.
[0340] Correspondingly, the second CU receives the first mapping from the first CU.
[0341] S205, the first CU sends downlink data to the second DU.
[0342] Correspondingly, the second DU receives downlink data from the first CU.
[0343] For the specific implementation of steps S203-S205, please refer to steps S101-S103 above.
[0344] Example 3
[0345] This application also provides a communication method. Unlike Embodiments 1 and 2, where the first mapping is determined by a first CU, in Embodiment 3 the first mapping is determined by a second CU. For details, see... Figure 11 The method includes:
[0346] S301, The first CU determines the service attribute information of the downlink data.
[0347] S302. The first CU sends downlink data service attribute information and the corresponding QoS information to the second CU.
[0348] Correspondingly, the second CU receives the service attribute information of the downlink data and the QoS information corresponding to the service attribute information from the first CU.
[0349] The service attribute information of the downlink data, and the QoS information corresponding to this service attribute information, can be found in Embodiment 1 and Embodiment 2.
[0350] S303, The first CU sends one or more fourth route identifiers allocated by the first CU to the second CU.
[0351] The second CU receives one or more fourth route identifiers assigned by the first CU.
[0352] The third route identifier is different from one or more fourth route identifiers. This ensures that the route identifier allocated by the second CU for the downlink transmission path of downlink data does not conflict with the route identifier allocated by the first CU.
[0353] S304. The second CU receives information about one or more RLC channels and QoS information corresponding to one or more RLC channels from the first CU.
[0354] Optionally, one or more RLC channels include the second RLC channel described below. Alternatively, the one or more RLC channels are RLC channels managed and controlled by the first CU, and are not managed and controlled by the second CU. For example, see still... Figure 7-1 The one or more RLC channels can be RLC channels between IAB2-DU and IAB3-MT. The RLC channel information received by donor-CU2 from donor-CU1 includes: the identifier of the IAB2 node, the identifier of the IAB3 node, the identifier of the RLC channel established between IAB2-DU and IAB3-MT (such as RLC channel 1 to RLC channel 3), and the QoS information corresponding to each RLC channel (the QoS information corresponding to each of RLC channel 1 to RLC channel 3).
[0355] Optionally, the node identifier can be the node's BAP address information or other information. For example, the identifier of the IAB2 node can be the BAP address of the IAB2 node, and the identifier of the IAB3 node can be the BAP address of the IAB3 node.
[0356] In this embodiment, the order of steps S301 and S302 with steps S303 and S304 is not limited.
[0357] S305, the second CU determines the first mapping.
[0358] The first mapping includes routing mapping and / or bearer mapping; routing mapping is the mapping relationship between downlink data and downlink transmission path; bearer mapping is the mapping relationship between downlink data and downlink transmission bearer; downlink transmission path includes the transmission path between the first CU of the first host node and the target node of the downlink data through the second distributed unit DU of the second host node; downlink transmission bearer includes the radio link control (RLC) channel between the second DU and the first node; the first node is the next-hop node of the second DU.
[0359] Optionally, the mapping relationship between downlink data and downlink transmission path includes: the destination address of downlink data, the service attribute information of downlink data, the third routing identifier corresponding to the destination address and the service attribute information.
[0360] Optionally, the mapping relationship between downlink data and downlink transmission bearer includes: the target address of downlink data, the service attribute information of downlink data, the target address, and the information of the second RLC channel corresponding to the service attribute information.
[0361] Optionally, the second CU determines the first mapping based on the information received from the first CU in steps S302-S304. Specifically, the second CU determines the route mapping based on the service attribute information and the corresponding QoS information, that is, it determines the destination address, the service attribute information, and the route identifier corresponding to the destination address and the service attribute information. It can be understood that this route identifier is different from the route identifier allocated by the first CU. The second CU determines the bearer mapping based on the service attribute information and the corresponding QoS information, that is, it determines the destination address, the service attribute information, and the RLC channel information corresponding to both.
[0362] S306, The first CU sends downlink data to the second DU.
[0363] Correspondingly, the second DU receives downlink data from the first CU.
[0364] After receiving downlink data from the first CU, the second DU performs downlink data routing and bearer selection based on the first mapping received from the second CU.
[0365] Still with Figure 7-1 For example, in some embodiments, according to the above scheme, the donor-CU2 determines the RLC channel used for transmitting downlink data between the donor-DU2 and the IAB4 node, so that after the donor-DU2 receives the downlink data from the donor-CU1, it maps the downlink data to the corresponding RLC channel and sends it to the IAB4 node.
[0366] For the IAB4 node, the downlink data is sent to the IAB2 node according to the mapping relationship between the ingress RLC channel and the egress RLC channel determined by the donor-CU2. The ingress RLC channel refers to the RLC channel between donor-DU2 and IAB4-MT, and the egress RLC channel refers to the RLC channel between IAB4-DU and IAB2-MT.
[0367] For IAB2 nodes, there are two ways to implement downlink bearer mapping on IAB2 nodes:
[0368] As one possible implementation, the donor-CU1 determines the bearer mapping on the IAB2 node. Taking downlink transmission as an example, the donor-CU1 determines the downlink bearer mapping on the IAB2 node, that is, the donor-CU1 determines the mapping relationship between the ingress RLC channel and the egress RLC channel on the IAB2 node and sends this mapping relationship to the IAB2 node. Here, the ingress RLC channel refers to the RLC channel between IAB4-DU and IAB2-MT, and the egress RLC channel refers to the RLC channel between IAB2-DU and IAB3-MT. In other words, the IAB4-DU maps the downlink data to the ingress RLC channel and sends it to the IAB2-MT. The IAB2-MT extracts the downlink data from the ingress RLC channel and sends it to the IAB2-DU through its internal interface. The IAB2-DU then maps the downlink data to the corresponding egress RLC channel and sends it to the IAB3-MT. In this implementation, the mapping relationship between downlink data and downlink transmission bearers includes information about the ingress RLC channel and the egress RLC channel.
[0369] In this implementation, donor-CU1 is unaware of the ingress RLC channel information on the IAB2 node. To enable donor-CU1 to determine the bearer mapping, it needs to receive the ingress RLC channel information from donor-CU2 on the IAB2 node. This RLC channel information includes: the identifier of the IAB4 node, the identifier of the IAB2 node, the identifiers of the RLC channels established between IAB4-DU and IAB2-MT (e.g., RLC channels 1-3), and the QoS information corresponding to each RLC channel (the QoS information for each of RLC channels 1-3).
[0370] Optionally, the node identifier can be the node's BAP address information or other information. For example, the identifier of an IAB4 node can be the BAP address of the IAB4 node, and the identifier of an IAB2 node can be the BAP address of the IAB2 node.
[0371] As another possible implementation, the donor-CU2 determines the bearer mapping on the IAB2 node. Taking downlink transmission as an example, the donor-CU2 determines the downlink bearer mapping on the IAB2 node; that is, the donor-CU2 determines the mapping relationship between the ingress RLC channel and the egress RLC channel on the IAB2 node, and sends the mapping relationship to the IAB2 node through the donor-CU1. In this implementation, the mapping relationship between downlink data and downlink transmission bearer includes: information about the ingress RLC channel and information about the egress RLC channel.
[0372] In this implementation, donor-CU2 is unaware of the egress RLC channel information on the IAB2 node. For donor-CU2 to determine the bearer mapping, it needs to receive the egress RLC channel information from donor-CU1. The RLC channel information can be found in the description of step S304, and will not be repeated here.
[0373] For the IAB3 node, similar to the IAB2 node, the downlink bearer mapping scheme on the IAB3 node is the same as that on the IAB2 node, so it will not be described again here.
[0374] Example 4
[0375] This application also provides a communication method, which, like Embodiment 3, involves the second CU determining the first mapping. However, unlike Embodiment 3, in Embodiment 4, the service attribute information is determined by the second CU. For details, see [link to documentation]. Figure 12 The method also includes:
[0376] S401. The first CU sends downlink data information of the GTP tunnel and the corresponding QoS information of the GTP tunnel to the second CU.
[0377] Correspondingly, the second CU receives downlink data GTP tunnel information and corresponding QoS information from the first CU.
[0378] S402, the second CU determines the service attribute information corresponding to the GTP tunnel for downlink data.
[0379] The second CU determines the service attribute information corresponding to the GTP tunnel of the downlink data based on the GTP tunnel information and the QoS information corresponding to the GTP tunnel.
[0380] S403. Information about the GTP tunnel through which the second CU sends downlink data to the first CU, and the service attribute information corresponding to the GTP tunnel.
[0381] The first CU receives information about the GTP tunnel for downlink data from the second CU, as well as the service attribute information corresponding to the GTP tunnel.
[0382] S404. The first CU sends one or more fourth route identifiers allocated by the first CU to the second CU.
[0383] The second CU receives one or more fourth route identifiers assigned by the first CU. The third route identifier is different from the one or more fourth route identifiers.
[0384] Step S404 can be found in step S303 above.
[0385] S405. The first CU sends information about one or more RLC channels, as well as QoS information corresponding to one or more RLC channels, to the second CU.
[0386] The second CU receives information about one or more RLC channels, as well as QoS information corresponding to one or more RLC channels, from the first CU.
[0387] Step S405 can be found in step S304 above.
[0388] S406, the second CU determines the first mapping.
[0389] The first mapping includes routing mapping and / or bearer mapping; the routing mapping is the mapping relationship between downlink data and the first routing identifier of the downlink transmission path; the bearer mapping is the mapping relationship between the downlink data and the first backhaul radio link control (RLC) channel of the downlink transmission bearer and the downlink data; the downlink transmission path includes the transmission path between the first CU of the first host node and the target node of the downlink data through the second distributed unit (DU) of the second host node; the first RLC channel of the downlink transmission bearer includes the radio link control (RLC) channel between the second DU and the first node; the first node is the next-hop node of the second DU;
[0390] Step S406 can be found in step S305 above.
[0391] S407, the first CU sends downlink data to the second DU.
[0392] Correspondingly, the second DU receives downlink data from the first CU.
[0393] Step S407 can be found in step S306 above.
[0394] The above embodiments all use top-down switching as an example to illustrate the technical solutions of the embodiments of this application. Figure 7-1 Taking the scenario as an example, top-down switching of IAB2 nodes means that IAB2-MT performs the switch before IAB2-DU, or completes the switch first. In this scenario, the first host node is the source host node, and the second host node is the target host node.
[0395] The technical solutions of this application embodiment (such as the technical solutions of embodiments one to four above) are also applicable to bottom-up switching, for example, Figure 7-2 In the bottom-up handover scenario shown, IAB2-DU performs the handover before or completes the handover before IAB2-MT. In this scenario, the first host node is the target host node, and the second host node is the source host node. Figure 7-2For example, after receiving downlink data from the core network equipment, the donor-CU2 can add service attribute information to the downlink data and send the downlink data carrying the service attribute information to the donor-DU1.
[0396] The correspondence between downlink data and business attribute information can be generated by donor-CU2 itself or by donor-CU1, and then sent by donor-CU1 to donor-CU2.
[0397] donor-DU1 receives downlink data from donor-CU2 and performs routing selection on the downlink data according to the routing mapping, and performs bearer selection on the downlink data according to the bearer mapping.
[0398] Specifically, the route mapping required by donor-DU1 can be determined and sent to donor-DU1 by donor-CU1. Alternatively, the route mapping can be determined by donor-CU2, sent to donor-CU1, and then forwarded to donor-DU1 by donor-CU1. Similarly, the bearer mapping can be determined and sent to donor-DU1 by donor-CU1. Alternatively, the bearer mapping can be determined by donor-CU2, sent to donor-CU1, and then forwarded to donor-DU1 by donor-CU1.
[0399] It should be noted that this application embodiment mainly uses the determination of the first mapping of downlink data by the first CU and the second CU as an example to illustrate the solution for how the terminal's downlink data is transmitted normally in a host node handover scenario. The mapping configuration of the terminal's uplink data can refer to the method for configuring the first mapping of downlink data so that the terminal can transmit uplink data. Among them, the mapping configuration of the terminal's uplink data mainly refers to the mapping configuration on the terminal's access IAB node (in this embodiment, the terminal's access IAB node is the IAB3 node). As mentioned above, the routing / bearer mapping on the IAB3 node can be determined by donor-CU1 and sent to the IAB3 node, or it can be determined by donor-CU2 and sent to donor-CU1, and then sent by donor-CU1 to the IAB3 node. The specific solution for how to enable the normal transmission of uplink data will not be described here.
[0400] The solutions in Embodiments 1 to 4 of this application are applicable not only to bottom-up or top-down host node switching scenarios, but also to scenarios such as... Figure 7-4 The dual-connection scenario is shown.
[0401] Example 5
[0402] This application also provides a communication method that is applied in a dual-connection scenario.
[0403] At the RAN3#110 meeting, the standard mentioned that R17 eIAB needs to support the separation of CP-UP transmission in dual-connectivity scenarios. That is, it should support the transmission of F1-C messages and F1-U data using different paths. Specifically, F1-C messages are transmitted through a single-hop air interface, while F1-U data can be transmitted through a multi-hop air interface.
[0404] like Figure 7-5 and Figure 7-6 Two scenarios are illustrated for F1-C messages and F1-U data transmission. In the dual-connectivity scenario, the transmission path between the IAB node and the master base station can be called the master cell group (MCG) path (or other names), and the path between the IAB node and the secondary base station can be called the secondary cell group (SCG) path.
[0405] like Figure 7-5 As shown in (a), in Scenario 1, on the SCG path, there can be one or more other IAB nodes between the secondary base station S-donor and IAB2, i.e., there are multi-hop nodes. This SCG path can be used to transmit F1-U data. On the MCG path, there are no other IAB nodes between the primary base station M-gNB and IAB2, and this MCG path can be used to transmit F1-C messages. Figure 7-6 As shown in (a), in Scenario 2, one or more other IAB nodes can exist between M-donor and IAB-node2 on the MCG path. The diagram illustrates this using the presence of one other IAB node as an example. This MCG path can be used to transmit F1-U data. Figure 7-5 The SCG path of the single-hop air interface shown in (a) can be used to transmit F1-C messages.
[0406] In Scenario 1 or Scenario 2, the S-donor can be a separate CU-DU architecture or a single entity. IAB1 and IAB2 can be MT-DU architectures. Figure 7-5 (b) and Figure 7-6 (b) is drawn with the donor as the DU-CU architecture and the IAB as the MT-CU architecture as an example.
[0407] It can be seen that F1-C messages can be transmitted via a single-hop MCG path or SCG path, while F1-U data can be transmitted via a single-hop or multi-hop SCG path or MCG path.
[0408] This embodiment mainly addresses the aforementioned dual-connectivity scenario; see [link / reference] Figure 13The method includes the following steps:
[0409] S501, The main network device determines the first instruction information.
[0410] The first instruction information is used to request / instruct the secondary network device to transmit first signaling to the first node via a first signaling radio bearer (SRB). The first signaling radio bearer is a signaling radio bearer on the SCG path. Optionally, the first signaling radio bearer includes SRB3 or split SRB. Optionally, the first signaling includes an F1-C message. For example, the F1-C message includes an F1AP message, or the F1-C message includes SCTP / IPsec related signaling.
[0411] In other words, in this method, the primary network device determines whether the secondary network device needs to establish a first signaling radio bearer to transmit the first signaling, and requests or instructs the secondary network device to establish a first signaling radio bearer to transmit the first signaling.
[0412] by Figure 7-6 Taking scenario 2 of (b) as an example, the primary network device is M-donor, the secondary network device is S-gNB, and the first node is IAB2. M-donor sends the first indication information to S-gNB in order to request / instruct S-gNB to transmit F1-C messages to IAB2 through, for example, SRB3 (or split SRB).
[0413] S502, The primary network device sends the first instruction information to the secondary network device.
[0414] As one possible implementation, after the secondary network device receives the first indication information from the primary network device, if the conditions for establishing the first SRB are met, then refer to... Figure 14 The auxiliary network device can also perform step S503, establish SRB3, and use SRB3 to transmit the first signaling, such as the F1-C message.
[0415] Optionally, the secondary network device sends an indication message to the primary network device to indicate that the first signaling radio bearer has been established.
[0416] Alternatively, as another possible implementation, if the secondary network device does not meet the conditions for establishing the first SRB, such as being unable to establish SRB3 or lacking sufficient resources, then see [the relevant documentation]. Figure 15-1 The secondary network device can also perform the following step S504:
[0417] S504, the secondary network device sends a second instruction message to the primary network device.
[0418] The primary network device receives the second instruction information from the secondary network device.
[0419] The second indication information is used to indicate that the establishment of the first signaling radio bearer failed, or that the first signaling cannot be transmitted via the first signaling radio bearer. Optionally, the second indication information carries a reason value for the failure to establish the first signaling radio bearer.
[0420] In this way, the primary network device can clearly know the establishment status of the first signaling radio bearer based on the second instruction information received from the secondary network device, so as to determine the method of transmitting the first signaling.
[0421] The following, in conjunction with the accompanying diagram, illustrates the specific implementation method of the F1-C message via the SCG path.
[0422] Method 1: Transmit F1-C messages via SRB3 on SCG.
[0423] Combination Figure 15-2 In this method, the M-donor-CU generates an F1-C message, i.e., an F1AP message (including UE-associated F1AP messages and non-UE associated F1AP messages), and encapsulates the generated F1-C message in an XnAP message. This XnAP message is then sent to the S-gNB via the Xn interface between the M-donor-CU and the S-gNB. The S-gNB extracts the F1-C message from the received XnAP message, encapsulates it in an NR RRC message on the Uu interface, and then maps it to SRB3 before sending it to IAB-MT2. IAB-MT2 extracts the F1-C message from the RRC message and sends it to IAB-DU2 for parsing via its internal interface.
[0424] Alternatively, the M-donor-CU generates an F1-C message, processes it through the SCTP layer, encapsulates the generated F1-C message in an IP packet, and then carries this IP packet in an XnAP message, sending the XnAP message to the S-gNB via the Xn interface. The SgNB extracts the IP packet from the received XnAP message, encapsulates it in an NR RRC message on the Uu interface, maps the RRC message to SRB3, and sends the RRC message to IAB-MT2 via SRB3. IAB-MT2 extracts the IP packet from the RRC message and sends it to IAB-DU2 via its internal interface for parsing.
[0425] Method 2: Transmit F1-C messages via the split SRB on the SCG.
[0426] Combination Figure 15-3In this method, the M-donor-CU encapsulates the generated F1-C message within an NR RRC message, then encapsulates the RRC message within an XnAP message, and sends the XnAP message to the S-gNB via the Xn interface. The S-gNB extracts the RRC message from the received XnAP message, maps it to a split SRB (e.g., split SRB1 or split SRB2), and sends the RRC message to IAB-MT2 via the split SRB. IAB-MT2 extracts the F1-C message from the RRC message and sends it to IAB-DU2 via its internal interface for parsing.
[0427] Alternatively, the M-donor-CU generates an F1-C message, processes it through the SCTP and IP layers, encapsulates it in an NR RRC message, then processes the RRC message through the PDCP layer to obtain a PDCP PDU. This PDCP PDU is then encapsulated in an XnAP message and sent to the S-gNB via the Xn interface. The S-gNB extracts the PDCP PDU from the received XnAP message and maps it to a split SRB for transmission to IAB-MT2. IAB-MT2 extracts the IP packet from the received content and sends it to IAB-DU2 via its internal interface for parsing.
[0428] Example 6
[0429] This application also provides a communication method applicable to a dual-connectivity scenario. Unlike Embodiment 5, where the primary network device determines the signaling radio bearer (SRB3 or split SRB) used for the first signaling transmission on the SCG path, in Embodiment 6, the secondary network device determines the signaling radio bearer used for the first signaling transmission on the SCG path. See also... Figure 16 The method includes:
[0430] S601, the auxiliary network device sends the fifth instruction information to the main network device.
[0431] Correspondingly, the primary network device receives the fifth instruction information from the secondary network device.
[0432] The fifth indication information is used to instruct the first signaling to be transmitted on the SCG path along the corresponding first signaling radio bearer, that is, to instruct the first signaling to be transmitted via the first signaling radio bearer. Optionally, the first signaling includes an F1-C message. For example, the F1-C message includes an F1AP message, or the F1-C message includes SCTP / IPsec related signaling.
[0433] Optionally, the first signaling radio bearer includes SRB3 or split SRB.
[0434] In some embodiments, if the secondary network device determines that the first signaling needs to be transmitted through the SCG path, it sends a fifth indication message to the primary network device to instruct the first signaling to be transmitted on the SCG path along the corresponding first signaling radio bearer.
[0435] In other embodiments, the primary network device may trigger the secondary network device to send a fifth indication message. As one possible implementation, before step S601, the primary network device may execute step S602, sending a sixth indication message to the secondary network device. The sixth indication message is used to request the secondary network device to transmit the first signaling. In response to the sixth indication message, the secondary network device determines whether to transmit the first signaling through the SCG path; if so, it sends the fifth indication message to the primary network device.
[0436] S603. The primary network device sends the first signaling to the secondary network device according to the fifth instruction information.
[0437] When secondary network devices use different first signaling radio bearers to transmit first signaling, the primary network device can process the first signaling differently. The two processing methods are described below:
[0438] In the first processing method, if the first signaling radio bearer indicated by the fifth indication information is SRB3, the primary network device sends the first signaling to the secondary network device. This is equivalent to the primary network device directly transmitting the first signaling. Subsequently, the secondary network device encapsulates the first signaling in an RRC message and sends the RRC message to the first node via SRB3. For the specific process, refer to Method 1 in step S504 of Embodiment 5, which will not be repeated here.
[0439] In the second processing method, if the first signaling radio bearer indicated by the fifth indication information is a split SRB, the primary network device first encapsulates the first signaling in an RRC message and sends the RRC message to the secondary network device. Subsequently, the secondary network device sends an RRC message to the first node through the split SRB. The specific process is described in step S504 of Embodiment 5, which will not be repeated here.
[0440] Example 7
[0441] This application also provides a communication method for a network device to indicate an uplink transmission path (SCG path or MCG path) for transmitting first signaling to a first node. See [link to relevant documentation]. Figure 17 The methods include:
[0442] S701, Network devices determine third instruction information.
[0443] The third indication information is used to indicate the information of the uplink transmission path used to transmit the first signaling, and the uplink transmission path includes the MCG path or the SCG path.
[0444] Optionally, the third indication information can be an enumeration type, meaning it includes the identifier of the MCG path or the identifier of the SCG path. Alternatively, the third indication information can include the identifier of the cell group. Or, it can include a preset identifier. For example, 1 bit can be set to indicate the MCG path or the SCG path, 0 to indicate the MCG path, and 1 to indicate the SCG path.
[0445] The network device can be a primary network device or a secondary network device. That is, the primary or secondary network device can determine whether the uplink transmission path of the first signaling is the SCG path or the MCG path.
[0446] S702, The network device sends a third instruction message to the first node.
[0447] If the network device is the master network device, the master network device directly sends the third indication information to the first node to indicate whether the uplink transmission path used by the first node to transmit the first signaling is the SCG path or the MCG path.
[0448] Alternatively, if the network device is a secondary network device, it sends a third instruction message to the first node through the primary network device.
[0449] Still with Figure 7-6 Taking scenario 2 (b) as an example, the primary network device is M-donor, the secondary network device is S-gNB, and the first node is IAB2. If M-donor determines the third indication information (i.e., determines the uplink transmission path for transmitting the first signaling (e.g., the F1-C message)), it directly sends the third indication information to IAB2. For example, M-donor carries the third indication information through an RRC message and sends the RRC message to IAB2-MT. In this way, IAB2 can know that the F1-C message needs to be transmitted to M-donor through, for example, the SCG path via S-gNB. Alternatively, if S-gNB determines the third indication information, it sends the third indication information to IAB2 through M-donor. For example, S-gNB carries the third indication information through an RRC message and sends the RRC message to M-donor, which then further sends the RRC message to IAB2-MT.
[0450] Optionally, the network device may also perform step S703, sending a fourth instruction message to the first node.
[0451] The fourth indication information is used to indicate the information of the radio bearer used to transmit the first signaling on the uplink transmission path. Optionally, if the uplink transmission path is an MCG path, the corresponding signaling radio bearer can be SRB1 or SRB2. If the uplink transmission path is an SCG path, the corresponding signaling radio bearer can be SRB3 or split SRB.
[0452] Alternatively, the fourth indication information is used to indicate information about the logical channel on the uplink transmission path used for transmitting the first signaling.
[0453] In this way, the first node can learn the first signaling radio bearer (such as SRB3 of the SCG path) used to transmit the first signaling (such as the F1-C message).
[0454] Example 8
[0455] This application also provides a communication method in which a network device indicates an uplink transmission path for transmitting first data to a first node. See [link to relevant documentation]. Figure 18 The methods include:
[0456] S801, Network device determines the seventh instruction information.
[0457] The seventh indication information is used to indicate the uplink transmission path used to transmit the first data. The uplink transmission path includes an MCG path or an SCG path. Optionally, the first data can be F1-U data. For example, F1-U data refers to the data transmitted in the GTP tunnel established between the donor-CU and the DU of the access IAB node, where the access IAB node is the IAB node accessed by the terminal. For example, still using... Figure 7-1 For example, the data transmitted in the GTP tunnel between donor-CU1 and IAB3-DU can be called F1-U data.
[0458] Optionally, the seventh indication information can be an enumeration type, meaning it includes the identifier of the MCG path or the identifier of the SCG path. Alternatively, the seventh indication information can include the identifier of the cell group. Or, it can include a preset identifier. For example, 1 bit can be set to indicate the MCG path or the SCG path, 0 to indicate the MCG path, and 1 to indicate the SCG path.
[0459] Network devices can be primary or secondary network devices. That is, the primary or secondary network device can determine whether the uplink transmission path of the first data is the SCG path or the MCG path.
[0460] S802, The network device sends the seventh instruction information to the first node.
[0461] If the network device is the master network device, it directly sends a seventh indication message to the first node to indicate whether the uplink transmission path used by the first node to transmit the first data is an SCG path or an MCG path. Optionally, the seventh indication message is carried in the RRC message generated by the master network device.
[0462] Alternatively, if the network device is a secondary network device, it sends a seventh indication message to the first node through the primary network device. This seventh indication message is carried in the RRC message generated by the secondary network device. In this way, the secondary network device can send only one seventh indication message to the first node, and the first node can transmit all F1-U data along the UL path indicated by the seventh indication message.
[0463] In other embodiments, if the network device is a secondary network device, it can also send a GTP-TEID to the first node through the primary network device. The GTP-TEID and the seventh indication information have a corresponding relationship. Optionally, the seventh indication information and the GTP-TEID are carried in the F1AP message generated by the secondary network device. In this way, the secondary network device can configure the transmission of UL F1-U data of the first node perGTP-U. That is, the secondary network device indicates the UL transmission path for each type of F1-U data. This indication method is more flexible, allowing different types of F1-U data to be transmitted on different UL transmission paths, which is beneficial for load balancing.
[0464] Optionally, the network device may also perform step S803, sending the eighth instruction information to the first node.
[0465] The eighth indication information is used to indicate the information of the data radio bearer used to transmit the first data on the uplink transmission path.
[0466] Alternatively, the eighth indication information is used to indicate information about the logical channel on the uplink transmission path used for transmitting the first data.
[0467] Optionally, the eighth indication information can be carried in the RRC message generated by the network device, and the network device can send the RRC message to the first node.
[0468] Alternatively, the eighth indication information can be carried in the F1AP message generated by the network device, and the network device can send the RRC message to the first node.
[0469] In this way, the first node can learn about the first data radio bearer used to transmit the first data (such as an F1-U message).
[0470] The solutions in this application are mainly illustrated using a dual-connection scenario with separate CP / UP transmission as an example. It is understood that the solutions in this application are also applicable to other dual-connection scenarios, such as scenarios where CP / UP is not separated.
[0471] The above embodiments five to eight can be applied to, for example, Figure 7-5 or Figure 7-6 The example shown is a dual-connection scenario or another similar scenario.
[0472] Example 9
[0473] This application also provides a communication method for obtaining the network topology of a required network in a scenario where host nodes are switched. This method is applicable to scenarios where host nodes are switched, or such as... Figure 7-4 The illustrated dual-connectivity scenario (or other dual-connectivity scenario). See also... Figure 19 The method includes:
[0474] S901, the second CU sends the first network topology information to the first CU.
[0475] Correspondingly, the first CU receives the first network topology information from the second CU.
[0476] The first network topology information is used to characterize the nodes in the network and the connections between them. Optionally, the second CU sends the topology information of the nodes it manages. See, for an example... Figure 7-1 donor-CU2 can send the topology information corresponding to donor-DU2 and IAB4 to donor-CU1.
[0477] The first CU can be the CU of the source host node, and the second CU can be the CU of the target host node. Alternatively, the first CU can be the CU of the target host node, and the second CU can be the CU of the source host node.
[0478] In other embodiments, the first CU may also send topology information of the nodes it manages to the second CU. See still. Figure 7-1 Taking the first CU as donor-CU1 and the second CU as donor-CU2 as an example, donor-CU1 can send topology information of donor-DU1, IAB1, IAB2 and IAB3 to donor-CU2.
[0479] S902, the first CU determines the routing table or bearer mapping based on the first topology information.
[0480] S903, the first CU sends the routing table or bearer mapping to the second CU.
[0481] Taking the determination of the routing table as an example, the method in this embodiment means that the first CU can determine the routing table of each node on the target path. See also Figure 7-1 The target path includes: the first CU, the second DU, node IAB4, node IAB2, and node IAB3. The first CU sends the determined routing table to the second CU, which then forwards it to the corresponding nodes. The routing table includes a route identifier and the identifier of the next-hop node corresponding to that route identifier. For example, see [link to example]. Figure 7-1 The donor-CU1 determines the routing table on the donor-DU2, for example, the correspondence between route identifier 1 and the identifier of node IAB4. The donor-CU1 sends this correspondence to the donor-CU2, which then sends it to the donor-DU2 so that the donor-DU2 can perform routing based on this correspondence.
[0482] Example 9 is applicable to the above. Figure 7-1 , Figure 7-2 In scenarios involving switching between host nodes, and applicable to Figure 7-4 In dual-connection scenarios, etc.
[0483] The foregoing primarily describes the solutions of the embodiments of this application from a methodological perspective. It is understood that, in order to achieve the aforementioned functions, network nodes include corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0484] This application embodiment can divide network nodes into functional units according to the above method example. For example, each function can be divided into a separate functional unit, or two or more functions can be integrated into one processing unit 1701. The integrated unit can be implemented in hardware or as a software functional unit. It should be noted that the unit division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.
[0485] This application also provides a network node (denoted as network node 170), such as Figure 20 As shown, network node 170 includes a processing unit 1701 and a transceiver unit 1702.
[0486] Taking network node 170 as the first host node as an example, here is one possible implementation:
[0487] Processing unit 1701 is configured to determine a first mapping, the first mapping including a routing mapping and / or a bearer mapping; the routing mapping is a mapping relationship between downlink data and a downlink transmission path; the bearer mapping is a mapping relationship between downlink data and a downlink transmission bearer; the downlink transmission path includes a transmission path between the first CU and the second DU through the second host node and the target node of the downlink data; the downlink transmission bearer includes a Radio Link Control (RLC) channel between the second DU and the first node; the first node is the next-hop node of the second DU;
[0488] The transceiver unit 1702 is used to send a first mapping to the second CU of the second host node and to send downlink data to the second DU.
[0489] Optionally, the transceiver unit 1702 is further configured to receive one or more second route identifiers allocated by the second CU from the second CU; the first route identifier and the one or more second route identifiers are different.
[0490] Optionally, the transceiver unit 1702 is further configured to receive information about one or more RLC channels between the second DU and the first node, as well as QoS information corresponding to the one or more RLC channels, from the second CU; the one or more RLC channels include the first RLC channel.
[0491] Optionally, the transceiver unit 1702 is also used to send information about the General Packet Radio Service Tunneling Protocol (GTP) tunnel for downlink data and the QoS information corresponding to the GTP tunnel to the second CU.
[0492] Optionally, the transceiver unit 1702 is also used to receive information about the GTP tunnel for downlink data and the service attribute information corresponding to the GTP tunnel from the second CU.
[0493] Taking network node 170 as the second host node as an example, here is one possible implementation:
[0494] Processing unit 1701 is configured to determine a first mapping, the first mapping including a routing mapping and / or a bearer mapping; the routing mapping is a mapping relationship between downlink data and a downlink transmission path; the bearer mapping is a mapping relationship between downlink data and a downlink transmission bearer; the downlink transmission path includes a transmission path between the first CU and the second DU of the second host node and the target node of the downlink data; the downlink transmission bearer includes an RLC channel between the second DU and the first node; the first node is the next-hop node of the second DU;
[0495] The transceiver unit 1702 is used to receive downlink data from the first CU.
[0496] Optionally, the transceiver unit 1702 is further configured to receive service attribute information of downlink data and QoS information corresponding to the service attribute information from the first CU.
[0497] Optionally, the transceiver unit 1702 is further configured to receive one or more fourth routing identifiers allocated by the first CU from the first CU. The third routing identifier and the one or more fourth routing identifiers are different.
[0498] Optionally, the transceiver unit 1702 is further configured to receive information of one or more RLC channels and QoS information corresponding to one or more RLC channels from the first CU.
[0499] Optionally, the transceiver unit 1702 is further configured to receive information about the General Packet Radio Service Tunneling Protocol (GTP) tunnel for downlink data and the corresponding QoS information from the first CU.
[0500] Optionally, the transceiver unit 1702 is also used to send downlink data GTP tunnel information and GTP tunnel corresponding service attribute information to the first CU.
[0501] For a detailed explanation of the mapping relationship between downlink data and downlink transmission path, and between downlink data and downlink transmission bearer, please refer to the method implementation examples.
[0502] Optionally, the first host node is the source host node and the second host node is the target host node; or, the first host node is the target host node and the second host node is the source host node.
[0503] Optionally, the first host node is the primary host node and the second host node is the secondary host node; or, the first host node is the secondary host node and the second host node is the primary host node.
[0504] Optionally, network node 170 may also include storage module 1703 for storing data required by network node 170.
[0505] All relevant content of each step involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and will not be repeated here.
[0506] The aforementioned network node 170 can be a device, or a chip or other component within the device.
[0507] Figure 20 The unit in the text can also be called a module; for example, processing unit 1701 can be called a processing module. Additionally, in... Figure 20In the embodiments shown, the names of the units may not be the same as those shown in the figures, depending on the way the modules are divided.
[0508] Figure 20 If the various units in the process are implemented as software functional modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods of the various embodiments of this application. Storage media for storing computer software products include: USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, optical disks, and other media capable of storing program code.
[0509] This application also provides a hardware structure diagram of a network node (denoted as network node 200), see [link to diagram]. Figure 21 or Figure 22 The network node 200 includes a processor 2001, and optionally, a memory 2002 connected to the processor 2001.
[0510] Processor 2001 can be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of the program according to the present application. Processor 2001 may also include multiple CPUs, and processor 2001 can be a single-core processor or a multi-core processor. Here, processor can refer to one or more devices, circuits, or processing cores used to process data (e.g., computer program instructions).
[0511] The memory 2002 can be a ROM or other type of static storage device capable of storing static information and instructions, RAM or other type of dynamic storage device capable of storing information and instructions, or it can be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer. This application embodiment does not impose any limitations on this. The memory 2002 can exist independently or be integrated with the processor 2001. The memory 2002 may contain computer program code. The processor 2001 is used to execute the computer program code stored in the memory 2002, thereby implementing the method provided in this application embodiment.
[0512] In the first possible implementation, see Figure 21 The network node 200 also includes a transceiver 2003. The processor 2001, memory 2002, and transceiver 2003 are connected via a bus. The transceiver 2003 is used to communicate with other communication devices or other protocol layers in the network node. Optionally, the transceiver 2003 may include a transmitter and a receiver. The device in the transceiver 2003 used to implement the receiving function (e.g., receiving data packets submitted by an upper protocol layer) can be considered a receiver, and the receiver is used to perform the receiving steps in the embodiments of this application. The device in the transceiver 2003 used to implement the sending function (e.g., submitting data packets to other protocol layers) can be considered a transmitter, and the transmitter is used to perform the sending or submitting steps in the embodiments of this application.
[0513] Based on the first possible implementation method Figure 21 The schematic diagram shown illustrates the structure of the network node involved in the above embodiments. The processor 2001 is used to control and manage the actions of the network node; for example, the processor 2001 is used to support the network node in executing the above method embodiments (e.g.,...). Figures 8 to 14 The processor 2001 can communicate with other communication devices or other protocol layers in the network node via the transceiver 2003. The memory 2002 is used to store the terminal's program code and data.
[0514] In a second possible implementation, the processor 2001 includes logic circuitry and input and / or output interfaces. The output interfaces are used to perform sending or submitting actions in the corresponding method, and the input interfaces are used to perform receiving actions in the corresponding method.
[0515] Based on the second possible implementation, see Figure 22 , Figure 22 The schematic diagram shown illustrates the structure of the network node involved in the above embodiments. The processor 2001 is used to control and manage the actions of the network node; for example, the processor 2001 is used to support the network node in performing... Figures 8 to 14 The processor 2001 can perform actions by network nodes in the steps described in the embodiments of this application, and / or in other processes. The processor 2001 can communicate with other communication devices or other protocol layers in the network node via input and / or output interfaces. The memory 2002 is used to store the terminal's program code and data.
[0516] In one possible implementation, the "module" or unit in network node 170 may refer to a specific ASIC, circuitry, a processor and memory executing one or more software or firmware programs, integrated logic circuitry, and / or other devices that can provide the aforementioned functions. In a simple embodiment, those skilled in the art will recognize that network node 170 may employ... Figure 21 or Figure 22 As shown in the figure.
[0517] for example, Figure 21 or Figure 22 The processor 2001 shown can cause network nodes to execute the communication method in the above method embodiment by calling computer execution instructions stored in memory 2002.
[0518] Specifically, Figure 20 The functions / implementation process of the transceiver unit 1702 and the processing unit 1701 can be obtained through Figure 21 or Figure 22 The processor 2001 shown calls computer execution instructions stored in memory 2002 to implement this. Alternatively, Figure 20 The function / implementation process of the processing unit 1701 can be achieved through... Figure 21 or Figure 22 The processor 2001 shown calls computer execution instructions stored in memory 2002 to implement this. Figure 20 The function / implementation process of the transceiver unit 1702 in the middle can be obtained through Figure 21 The transceiver 2003 shown is used to implement this.
[0519] This application also provides a computer-readable storage medium including instructions that, when run on a computer, cause the computer to perform any of the methods described above.
[0520] This application also provides a computer program product containing instructions that, when run on a computer, cause the computer to perform any of the methods described above.
[0521] This application also provides a system chip used in a network node. The system chip includes at least one processor, in which program instructions are executed to perform any of the methods provided in the above embodiments.
[0522] This application also provides a communication system, including one or more network nodes from the network nodes provided in the above embodiments.
[0523] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software programs, implementation can be, in whole or in part, in the form of a computer program product. This computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device containing one or more servers, data centers, etc., that can be integrated with the medium. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state disks (SSDs)).
[0524] Although this application has been described herein in conjunction with various embodiments, those skilled in the art, by reviewing the accompanying drawings, the disclosure, and the appended claims, will understand and implement other variations of the disclosed embodiments in carrying out the claimed application. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude multiple instances. A single processor or other unit can implement several functions listed in the claims. While different dependent claims may recite certain measures, this does not mean that these measures cannot be combined to produce good results.
[0525] Although this application has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made thereto without departing from the spirit and scope of this application. Accordingly, this specification and drawings are merely exemplary illustrations of this application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Clearly, those skilled in the art can make various alterations and modifications to this application without departing from the spirit and scope of this application. Thus, if such modifications and modifications of this application fall within the scope of the claims of this application and their equivalents, this application is also intended to include such modifications and modifications.
Claims
1. A communication method, characterized in that, include: The first centralized unit (CU) of the first host node determines a first mapping, which includes a routing mapping and / or a bearer mapping. The routing mapping is a mapping relationship between downlink data and a downlink transmission path. The bearer mapping is a mapping relationship between the downlink data and a downlink transmission bearer. The downlink transmission path includes a transmission path between the first CU and the target node of the downlink data through the second distributed unit (DU) of the second host node. The downlink transmission bearer includes a radio link control (RLC) channel between the second DU and the first node. The first node is the next-hop node of the second DU; The first CU sends the first mapping to the second CU of the second host node; The first CU sends the downlink data to the second DU; The mapping relationship between downlink data and downlink transmission path includes: the target address of the downlink data, the service attribute information of the downlink data, and the first routing identifier corresponding to the target address and the service attribute information; The mapping relationship between the downlink data and the downlink transmission bearer includes: the target address of the downlink data, the service attribute information of the downlink data, and the information of the first radio link control (RLC) channel corresponding to the target address and the service attribute information; The downlink data includes the business attribute information; Before the first CU sends the first mapping to the second CU, the method further includes: The first CU receives one or more second route identifiers allocated by the second CU; the first route identifier is different from the one or more second route identifiers. The first CU receives information about one or more RLC channels between the second DU and the first node, as well as QoS information corresponding to the one or more RLC channels, from the second CU; the one or more RLC channels include the first RLC channel.
2. The communication method according to claim 1, characterized in that, The method further includes: The first CU sends information about the General Packet Radio Service Tunneling Protocol (GTP) tunnel for the downlink data and the QoS information corresponding to the GTP tunnel to the second CU.
3. The communication method according to claim 2, characterized in that, The method further includes: The first CU receives information about the GTP tunnel for the downlink data and the service attribute information corresponding to the GTP tunnel from the second CU.
4. The communication method according to any one of claims 1-3, characterized in that, The first host node is the source host node, and the second host node is the target host node; or, the first host node is the target host node, and the second host node is the source host node.
5. The communication method according to any one of claims 1-3, characterized in that, The first host node is the primary host node, and the second host node is the secondary host node; or, the first host node is the secondary host node, and the second host node is the primary host node.
6. A communication method, characterized in that, include: The second centralized unit (CU) of the second host node determines a first mapping, which includes a routing mapping and / or a bearer mapping. The routing mapping is a mapping relationship between downlink data and a downlink transmission path. The bearer mapping is a mapping relationship between the downlink data and a downlink transmission bearer. The downlink transmission path includes a transmission path between the first CU of the first host node and the target node of the downlink data through the second distributed unit (DU) of the second host node. The downlink transmission bearer includes an RLC channel between the second DU and the first node. The first node is the next-hop node of the second DU; The second DU receives the downlink data from the first CU; The mapping relationship between the downlink data and the downlink transmission path includes: the target address of the downlink data, the service attribute information of the downlink data, the target address, and the third routing identifier corresponding to the service attribute information; The mapping relationship between the downlink data and the downlink transmission bearer includes: the target address of the downlink data, the service attribute information of the downlink data, the target address, and the information of the second radio link control (RLC) channel corresponding to the service attribute information; The downlink data includes the business attribute information; Before the second CU determines the first mapping, the method further includes: The second CU receives one or more fourth route identifiers allocated by the first CU; the third route identifier is different from the one or more fourth route identifiers. The second CU receives information about one or more RLC channels from the first CU, as well as QoS information corresponding to the one or more RLC channels; the one or more RLC channels include the second RLC channel.
7. The communication method according to claim 6, characterized in that, The method further includes: The second CU receives the service attribute information of the downlink data and the quality of service (QoS) information corresponding to the service attribute information from the first CU.
8. The communication method according to claim 6 or 7, characterized in that, The method further includes: The second CU receives from the first CU information about the General Packet Radio Service Tunneling Protocol (GTP) tunnel for the downlink data, as well as the QoS information corresponding to the GTP tunnel.
9. The communication method according to claim 8, characterized in that, The method further includes: The second CU sends the GTP tunnel information of the downlink data and the service attribute information corresponding to the GTP tunnel to the first CU.
10. A communication device, characterized in that, include: processor; The processor is connected to a memory for storing computer execution instructions. The processor executes the computer execution instructions stored in the memory to enable the device to implement the method as described in any one of claims 1-5; or to implement the method as described in any one of claims 6-9.
11. A computer-readable storage medium, characterized in that, Includes instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1-5; or to implement the method as described in any one of claims 6-9.
12. A chip, characterized in that, The chip is used in network nodes, and the chip includes: At least one processor, wherein the program instructions involved are executed in the at least one processor to perform the method as claimed in any one of claims 1-5; or to implement the method as claimed in any one of claims 6-9.
13. A communication system, characterized in that, include: A host node for performing the communication method as described in any one of claims 1-5, and a host node for performing the communication method as described in any one of claims 6-9.
