Relay communication method, apparatus and system
By receiving instructions and configuration information from network nodes in wireless communication, the terminal retains the original path when switching to a new cell, solving the problems of large delay and signaling overhead in the multi-path relay solution, improving communication performance and security .
Patent Information
- Application Number
- PCT/CN2024/096679
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-06-12
- Filing Date
- 2024-05-31
- Publication Date
- 2024-12-19
AI Technical Summary
In wireless communication, in multi-path relay scheme, when adding direct connection paths between terminals and RAN nodes, how to reduce delay and signaling overhead is an urgent problem.
By receiving messages from network nodes, the terminal retains the original path when switching to a new cell, avoiding disconnection and re-establishing the path, thereby reducing delay and signaling overhead. The method includes receiving indication information and configuration information for indicating a reserved path and keeping the key consistent when the path is updated to ensure communication security.
It effectively reduces the delay and signaling overhead during path update, improves communication performance, and ensures communication security and reliability.
Smart Images

Figure CN2024096679_19122024_PF_FP_ABST
Abstract
Description
Relay communication method, device and system Technical Field
[0001] The embodiments of the present application relate to the field of communication technology, and in particular to a relay communication method, device, and system. Background Art
[0002] In wireless communication technology, in order to improve the communication performance of terminals, the industry has proposed a multi-link relay solution. Multi-link relay can also be called multi-path relay. In a communication scenario of a multi-path relay solution, a first terminal (e.g., remote user equipment (remote UE)) communicates with a radio access network (RAN) node through a direct link and one or more indirect links. On the direct link, the remote UE and the RAN node communicate through an air interface (e.g., a Uu interface). On the indirect link, the remote UE communicates with the RAN node through a second terminal (e.g., a relay UE), wherein the remote UE and the relay UE can communicate through a sidelink interface (e.g., a PC5 interface) or through a non-3rd Generation Partnership Project (3GPP) link. The remote UE can improve the throughput and reliability of data transmission and reception by sending and receiving the same or different data simultaneously on multiple links.
[0003] When a first terminal communicates with a first RAN node (e.g., a source RAN node) via a first path (e.g., a first indirect path), if a direct path is to be added between the first terminal and a second RAN node (e.g., a target RAN node), how to reduce latency and signaling overhead becomes an urgent issue.
[0004] Summary of the Invention
[0005] The embodiments of the present application provide a relay communication method, a communication device, and a communication system to reduce delay and signaling overhead.
[0006] In a first aspect, an embodiment of the present application provides a communication method, which can be executed by a first terminal, or by a component of the first terminal (such as a processor, a chip, or a chip system, etc.), or by a logic module or software that can implement all or part of the terminal functions. The method includes: receiving a first message from a first network node, and the first terminal communicates with the first network node through a second terminal on a first path; the first message includes first indication information and / or first configuration information of the first path, and the first indication information is used to indicate that the first path is retained; the first message includes information for indicating the first cell of the second network node; establishing a third path and retaining the first path, and the third path is a direct connection path between the first terminal and the second network node.
[0007] Through this method, the first terminal retains the first path when switching to the first cell, avoiding the high delay and high signaling overhead caused by disconnecting the first path when the first terminal updates the path and then re-establishing the first path, thereby improving communication performance.
[0008] In one possible manner, determining to retain the first path based on the first indication information and / or the first configuration information. The first terminal determines to retain the first path based on information in the first message, and can instruct the first terminal to retain the first path while instructing the first terminal to access the first cell, thereby reducing latency.
[0009] In one possible embodiment, the first configuration information includes first key indication information, where the first key indication information is used to indicate a second key, where the second key is a key used by the first terminal to communicate with the first network node after receiving the first message. The first configuration information indicates that the key used by the first terminal to communicate with the first network node has been updated to ensure communication security.
[0010] In one possible embodiment, the first key indication information includes indication information for indicating that the second key is the same as the first key; wherein the first key is a key used by the first terminal to communicate with the first network node before receiving the first message. The first configuration information indicates that the key used by the first terminal to communicate with the first network node remains unchanged, thereby ensuring communication security.
[0011] In one possible embodiment, the first configuration information further includes identification information of the second terminal, configurations of one or more protocol layers corresponding to the first terminal, and one or more information indicating a path corresponding to the first configuration. The first configuration information configures the configuration of the first terminal in cross-node multipathing, enabling the first terminal to implement cross-node multipathing.
[0012] In one possible embodiment, the method further includes: sending a first measurement result to the first network node, the first measurement result including communication quality between the first terminal and the second terminal. The first terminal reports the measurement result to the first network node, indicating the communication quality, to assist the network node in making a better decision.
[0013] In one possible manner, the configuration of the first path is updated or determined according to the first configuration information.
[0014] In a second aspect, an embodiment of the present application provides a communication method, which can be performed by a first network node, or by a component of the first network node (such as a processor, a chip, or a chip system), or can be implemented by a logic module or software that can implement all or part of the network device functions, including:
[0015] A first message is sent, and the first network node communicates with the first terminal through the second terminal on the first path; the first message includes first indication information and / or first configuration information, the first indication information is used to indicate that the first path is retained, and the first configuration information includes information for configuring the first path; the first message includes information for indicating the first cell of the second network node; and communication is performed with the first terminal on the first path.
[0016] Through this method, the first network node sends information instructing to retain the first path to the first terminal, so that the first terminal can retain the first path when the path is updated, reducing delay and signaling overhead.
[0017] In a possible manner, the first configuration information includes first key indication information, where the first key indication information is used to indicate a second key, and the second key is a key used by the first terminal to communicate with the first network node after receiving the first message.
[0018] In one possible manner, the first key indication information includes indication information for indicating that the second key is the same as the first key; wherein the first key is a key used by the first terminal to communicate with the first network node before receiving the first message.
[0019] In one possible manner, the first configuration information further includes one or more of identification information of the second terminal, configurations of one or more protocol layers corresponding to the first terminal, and information indicating a path corresponding to the first configuration.
[0020] In one possible embodiment, the method also includes: sending a request message, the request message including identification information of the first cell and one or more of the following messages: first bearer information used by the second network node after receiving the request message, the first bearer information including data radio bearer identification information; information for requesting to retain the first path; or information for indicating adding a third path, the third path being a direct connection path between the first terminal and the second network node.
[0021] In one possible manner, the method further includes: receiving a first request response message, where the first request response message includes the first configuration information.
[0022] In one possible manner, the first request response message further includes one or more of the following information: information indicating a first key derivation parameter, or information indicating to the first terminal to retain the first path; wherein the first key derivation parameter is used to derive the second key.
[0023] In a possible manner, the method further includes: receiving a second message, where the second message is used to request adding an indirect path, and the second message includes identification information of the second terminal.
[0024] In a possible manner, the second message further includes one or more of the following information: information used to indicate the second key to the first network node, or seventh bearer information to be used by the first network node, where the seventh bearer information includes bearer identification information.
[0025] In one possible manner, the method further includes: sending a third message, the third message including the second configuration information, the second configuration information including second key indication information, the second key indication information being used to indicate the second key. Optionally, the third message is sent in response to the second message.
[0026] In a possible manner, the method further includes: sending second configuration information, where the second configuration information includes second key indication information, and the second key indication information is used to indicate the second key.
[0027] In a possible manner, the second key indication information includes indication information for indicating that the second key is the same as the first key, or the second key indication information is used to indicate that the key between the first terminal and the first network node is updated to the second key.
[0028] In a possible manner, sending the second configuration information includes: sending the second configuration information through a request message.
[0029] In one possible manner, the first request response message further includes one or more of the following information:
[0030] Information for indicating the second key to the first network node, or information for indicating to the first network node that the first path is retained.
[0031] In a possible manner, the method further includes: receiving a second request response message, where the second request response message includes information indicating a refusal to retain the first path.
[0032] In a possible manner, the request message further includes auxiliary information, where the auxiliary information includes information used by the second access network node to determine the first configuration information.
[0033] In one possible manner, the method further includes: receiving a first measurement result, where the first measurement result includes communication quality between the first terminal and the second terminal.
[0034] In one possible manner, the method further includes: sending a second measurement result, where the second measurement result includes communication quality between the first terminal and the second terminal.
[0035] In a third aspect, an embodiment of the present application provides a communication method, which can be executed by a second network node, or by a component of the second network node (such as a processor, a chip, or a chip system, etc.), or by a logic module or software that can implement all or part of the network device functions, including: receiving a request message, the request message is used to request the establishment of a third path, the third path is a direct path between the first terminal and the second network node, and the first terminal communicates with the first network node through the second terminal on the first path; sending a request response message, the request response message includes a first request response message and / or a second request response message, wherein the first request response message includes first configuration information, the first configuration information includes information for configuring the first path; the second request response message includes information for indicating a refusal to retain the first path.
[0036] Through this method, the second network node sends configuration information of the first path to the first network node, so that the first terminal can retain the first path when the path is updated, reducing latency and signaling overhead, or the second network node sends indication information of refusing to establish cross-node multipath to the first network node.
[0037] In a possible manner, the first configuration information includes first key indication information, where the first key indication information is used to indicate a second key, and the second key is a key used by the first terminal to communicate with the first network node after receiving the first message.
[0038] In one possible manner, the first key indication information includes indication information for indicating that the second key is the same as the first key; wherein the first key is a key used by the first terminal to communicate with the first network node before receiving the first message.
[0039] In one possible manner, the first configuration information further includes one or more of identification information of the second terminal, configurations of one or more protocol layers corresponding to the first terminal, and information indicating a first path corresponding to the first configuration.
[0040] In one possible embodiment, the request message includes identification information of the first cell and one or more of the following messages: first bearer information used by the second network node, the first bearer information including data radio bearer identification information; information for requesting to retain the first path; or information for indicating adding a third path, the third path being a direct connection path between the first terminal and the second network node.
[0041] In one possible manner, the first request response message further includes one or more of the following information: information indicating a first key derivation parameter, or information indicating to the first terminal to retain the first path; wherein the first key derivation parameter is used to derive the second key.
[0042] In a possible manner, the method further includes: sending a second message, where the second message is used to request adding an indirect path, and the second message includes identification information of the second terminal.
[0043] In a possible manner, the second message further includes one or more of the following information: information used to indicate the second key to the first network node, or seventh bearer information used by the first network node, where the seventh bearer information includes bearer identification information.
[0044] In a possible manner, the method further includes: receiving a third message, the third message including second configuration information, the second configuration information including second key indication information, and the second key indication information is used to indicate the second key.
[0045] In a possible manner, the method further includes: receiving second configuration information, where the second configuration information includes second key indication information, and the second key indication information is used to indicate the second key.
[0046] In a possible manner, the second key indication information includes indication information for indicating that the second key is the same as the first key, or the second key indication information is used to indicate that the key between the first terminal and the first network node is updated to the second key.
[0047] In a possible manner, receiving the second configuration information includes: receiving the second configuration information through a request message.
[0048] In one possible manner, the first request response message further includes one or more of the following information:
[0049] Information for indicating the second key to the first network node, or information for indicating to the first network node that the first path is retained.
[0050] In a possible manner, the request message further includes auxiliary information, where the auxiliary information includes information used by the second network node to determine the first configuration information.
[0051] In one possible manner, the method further includes: determining the first configuration information according to the second configuration information.
[0052] Optionally, the second request response message includes information indicating the reason for rejection.
[0053] In one possible manner, the method further includes: receiving a second measurement result, where the second measurement result includes communication quality between the first terminal and the second terminal.
[0054] In a fourth aspect, an embodiment of the present application provides a communication method, which can be executed by a first terminal, or by a component of the first terminal (such as a processor, a chip, or a chip system, etc.), or by a logic module or software that can realize all or part of the terminal functions. The method includes: communicating with the first terminal through the second terminal on a first path, the key between the first terminal and the first network node is a fourth key, and the identifier used by the first terminal on the first path includes a first local identifier; receiving a fourth message, the fourth message includes the second local identifier of the first terminal and a fifth key derivation parameter, the fifth key derivation parameter is used to derive a fifth key, and the fifth key is the key between the first terminal and the first network node; receiving a third processing data packet and / or a fourth processing data packet, the third processing data packet includes the first local identifier and third data, and the fourth processing data packet includes the second local identifier and fourth data; determining that the third data is encrypted using the fourth key based on the first local identifier, and / or determining that the fourth data is encrypted using the fifth key based on the second local identifier.
[0055] Optionally, receiving the fourth message includes receiving a fourth message from the first network node.
[0056] Through this method, it is possible to determine whether the data packet is encrypted with a new key or the original key through the local identifier carried by the data packet, thereby avoiding the problem of packet errors caused by key confusion. The first terminal can continue to transmit data encrypted with the original key, thus avoiding packet loss.
[0057] In one possible manner, a first data packet and / or a second data packet is sent, where the first data packet includes a first local identifier and first data, and the second data packet includes a second local identifier and second data; the first data is encrypted using a fourth key, and the second data is encrypted using a fifth key.
[0058] In a fifth aspect, an embodiment of the present application provides a communication method, which can be executed by a first network node, or by a component of the first network node (such as a processor, a chip, or a chip system, etc.), or by a logic module or software that can realize all or part of the network device functions, including: communicating with the first terminal through the second terminal on a first path, the key between the first terminal and the first access network node is a fourth key, and the identifier used by the first terminal on the first path includes a first local identifier; sending a fourth message, the fourth message includes the second local identifier of the first terminal and a fifth key derivation parameter, the fifth key derivation parameter is used to derive a fifth key, and the fifth key is the key between the first terminal and the first access network node; receiving a first processing data packet and / or a second processing data packet, the first processing data packet includes a first local identifier and first data, and the second processing data packet includes a second local identifier and second data; determining that the first data is encrypted using the fourth key based on the first local identifier, and / or determining that the second data is encrypted using the fifth key based on the second local identifier.
[0059] Optionally, sending the fourth message includes sending the fourth message to the first terminal.
[0060] Through this method, the first network node can determine whether the data packet is encrypted with a new key or the original key through the local identifier carried by the data packet, thereby avoiding the problem of packet errors caused by key confusion. The first terminal can continue to transmit data encrypted with the original key, thus avoiding packet loss.
[0061] In one possible embodiment, the method further includes: sending a third data packet and / or a fourth data packet, the third data packet including the first local identifier and third data, the third data being encrypted using a fourth key; the fourth data packet including the second local identifier and fourth data, the fourth data being encrypted using a fifth key.
[0062] In one possible manner, the method further includes: sending a fifth message, wherein the fifth message includes the second local identifier. Optionally, the fifth message is sent to the second terminal.
[0063] In a sixth aspect, an embodiment of the present application provides a device that can implement the method in the first aspect, the fourth aspect, any possible implementation of the first aspect, or any possible implementation of the fourth aspect. The device includes corresponding units or modules for executing the above-mentioned method. The units or modules included in the device can be implemented by software and / or hardware. The device can be, for example, a terminal, or a chip, chip system, or processor that supports the terminal to implement the above-mentioned method, or a logic module or software that can implement all or part of the terminal functions.
[0064] In a seventh aspect, an embodiment of the present application provides a device that can implement the method in the second aspect, the third aspect, the fifth aspect, any possible implementation of the second aspect, any possible implementation of the third aspect, or any possible implementation of the fifth aspect. The device includes corresponding units or modules for executing the above-mentioned method. The units or modules included in the device can be implemented by software and / or hardware. The device can be, for example, a network device, or a chip, a chip system, or a processor that supports the network device to implement the above-mentioned method, or a logic module or software that can implement all or part of the functions of the network device.
[0065] In an eighth aspect, an embodiment of the present application provides a device comprising: a processor coupled to a memory, the memory being used to store instructions, and when the instructions are executed by the processor, the device implements the method in the above-mentioned first aspect, fourth aspect, any possible implementation of the first aspect, or any possible implementation of the fourth aspect.
[0066] In the ninth aspect, an embodiment of the present application provides a device, comprising: a processor, the processor being coupled to a memory, the memory being used to store instructions, and when the instructions are executed by the processor, the device implements the method of the above-mentioned second aspect, third aspect, fifth aspect, any possible implementation of the second aspect, any possible implementation of the third aspect, or any possible implementation of the fifth aspect.
[0067] In the tenth aspect, an embodiment of the present application provides a computer-readable storage medium having instructions stored thereon, which, when executed, enables the computer to execute the method in the above-mentioned first aspect, fourth aspect, any possible implementation of the first aspect, or any possible implementation of the fourth aspect.
[0068] In the eleventh aspect, an embodiment of the present application provides a computer-readable storage medium having instructions stored thereon, which, when executed, causes the computer to execute the method of the above-mentioned second aspect, third aspect, fifth aspect, any possible implementation of the second aspect, any possible implementation of the third aspect, or any possible implementation of the fifth aspect.
[0069] In the twelfth aspect, an embodiment of the present application provides a computer program product, which includes computer program code. When the computer program code runs on a computer, it enables the computer to execute the method of the above-mentioned first aspect, fourth aspect, any possible implementation of the first aspect, or any possible implementation of the fourth aspect.
[0070] In the thirteenth aspect, an embodiment of the present application provides a computer program product, which includes computer program code. When the computer program code runs on a computer, it enables the computer to execute the method of the above-mentioned second aspect, third aspect, fifth aspect, any possible implementation of the second aspect, any possible implementation of the third aspect, or any possible implementation of the fifth aspect.
[0071] In the fourteenth aspect, an embodiment of the present application provides a chip, comprising: a processor, the processor being coupled to a memory, the memory being used to store instructions, and when the instructions are executed by the processor, the chip implements the method of the above-mentioned first aspect, second aspect, third aspect, any possible implementation of the first aspect, or any possible implementation of the second aspect, or any possible implementation of the third aspect.
[0072] In the fifteenth aspect, an embodiment of the present application provides a communication system, including: the device of the sixth aspect and the device of the seventh aspect.
[0073] In the sixteenth aspect, an embodiment of the present application provides a communication system, including: the device of the eighth aspect and the device of the ninth aspect.
[0074] It can be understood that the technical effects brought about by any possible implementation of the sixth to sixteenth aspects can be referred to the technical effects brought about by the data transmission method described in any possible design of any of the above aspects, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS
[0075] FIG1 is a schematic diagram of a network architecture applicable to an embodiment of the present application;
[0076] FIG2 is a schematic diagram of another network architecture provided in an embodiment of the present application;
[0077] FIG3 is a schematic diagram of a switching method provided in an embodiment of the present application;
[0078] FIG4 is a schematic diagram of a relay communication method provided in an embodiment of the present application;
[0079] FIG5 is a schematic diagram of a relay communication method provided in an embodiment of the present application;
[0080] FIG6 is a schematic diagram of a relay communication method provided in an embodiment of the present application;
[0081] FIG7 is a schematic diagram of a relay communication method provided in an embodiment of the present application;
[0082] FIG8 is a schematic diagram of a relay communication method provided in an embodiment of the present application;
[0083] FIG9 is a schematic diagram of a relay communication method provided in an embodiment of the present application;
[0084] FIG10 is a schematic structural diagram of a terminal provided in an embodiment of the present application;
[0085] FIG11 is a schematic diagram of a device provided in an embodiment of the present application;
[0086] FIG12 is a schematic diagram of another device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0087] First, to facilitate understanding of the embodiments of the present application, some terms involved in the embodiments of the present application are described:
[0088] Direct path: Also known as a direct link, communication between a first terminal (e.g., a Remote UE) and a RAN node via a direct path can be understood as communication between the remote UE and the RAN node via an air interface (e.g., a Uu interface), or as a radio resource control (RRC) connection established between the remote UE and the RAN node.
[0089] Indirect path: Also known as an indirect link. Communication between a remote UE and a RAN node via an indirect path can be understood as the remote UE communicating with the RAN node via a first terminal (eg, a relay UE).
[0090] Multi-path (also known as multi-link) communication between the remote UE and the RAN node via multi-path can be understood as the simultaneous existence of a direct path and at least one indirect path between the remote UE and the RAN node.
[0091] A remote UE is generally a terminal that supports access to a RAN node through a relay service. When uplink services are available, the corresponding uplink data can be sent to the RAN node through the relay UE or direct path. Alternatively, part of the uplink data can be sent to the RAN node through the relay UE, and part of the data can be transmitted to the RAN node through the Uu interface between the remote UE and the RAN node.
[0092] Relay UE is generally a terminal that supports providing relay services, helping RAN nodes forward downlink data to remote UEs, and helping remote UEs send uplink data to RAN nodes.
[0093] Figure 1 is a schematic diagram illustrating a possible, non-limiting system. As shown in Figure 1 , communication system 1000 includes a RAN 100 and a core network (CN) 200. RAN 100 includes at least two network nodes (e.g., 110a and 110b in Figure 1 ), a first terminal 120a (hereinafter described as a remote UE), and a second terminal 120b (hereinafter described as a relay UE). RAN 100 may also include other network nodes, such as wireless relay devices and / or wireless backhaul devices (not shown in Figure 1 ). The network nodes are described as access network nodes.
[0094] The following description uses 110a as a source RAN node (an example of a first access network node), 110b as a target RAN node (an example of a second access network node), first terminal 120a as a remote UE, and second terminal 120b as a relay UE as an example. The relay UE can communicate with the source RAN node via a communication interface (e.g., a Uu port), and the remote UE can communicate with the relay UE via a communication interface (e.g., a PC5 port). It will be appreciated that the aforementioned communication interfaces are merely examples and are not limiting in the present embodiment. For example, the interface between the remote UE and the relay UE is not limited to a PC5 port, but may also be other communication interfaces for connecting two terminals, such as a wireless fidelity (WiFi) port, a wired interface, or a non-standardized interface. The RAN node is connected to the core network 200 via wireless or wired means. The core network device in the core network 200 and the RAN node in the RAN 100 can be different physical devices, or they can be the same physical device that integrates core network logical functions and radio access network logical functions.
[0095] It is easy to understand that there may be multiple indirect connection paths between the remote UE and the source RAN node. For example, the remote UE may also communicate with the source RAN node through 120c.
[0096] Optionally, while an indirect path exists between the remote UE and the source RAN node, the remote UE can also communicate with the source RAN node via a direct path, as shown by the dashed line in Figure 1. That is, in this embodiment of the present application, the remote UE and the source RAN node can communicate via an indirect path or a multi-path. The target RAN node in Figure 1 can be the target access network device of the remote UE.
[0097] The RAN 100 may be a cellular system related to the Third Generation Partnership Project (3GPP), such as a 4G or 5G mobile communication system, or a future-oriented evolutionary system (such as a 6G mobile communication system). The RAN 100 may also be an open access network (O-RAN or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (WiFi) system. The RAN 100 may also be a communication system that integrates two or more of the above systems.
[0098] RAN nodes, sometimes also referred to as network equipment, access network equipment, RAN entities, network nodes, or access nodes, constitute part of a communication system and are used to help terminals achieve wireless access. The multiple RAN nodes in the communication system 1000 can be nodes of the same type or different types. RAN nodes 110 and terminals are sometimes referred to as communication devices. For example, network elements 110a and 110b in Figure 1 can be understood as communication devices with base station functions, and network elements 120a-120c can be understood as communication devices with terminal functions.
[0099] In one possible scenario, a RAN node may be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next-generation NodeB (gNB), a next-generation base station in a sixth-generation (6G) mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system. A RAN node may be a macro base station, a micro base station, or an indoor station, a relay node or a donor node, or a wireless controller in a CRAN scenario. Optionally, a RAN node may also be a server, a wearable device, a vehicle, or an onboard device. For example, the access network device in vehicle-to-everything (V2X) technology may be a roadside unit (RSU).
[0100] In another possible scenario, multiple RAN nodes collaborate to assist the terminal in achieving wireless access, and different RAN nodes respectively implement part of the functions of the base station. For example, the RAN node can be a centralized unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). The CU and DU can be set separately, or they can be included in the same network element, such as a baseband unit (BBU). The RU can be included in a radio frequency device or radio frequency unit, such as a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH).
[0101] In different systems, CU (or CU-CP and CU-UP), DU or RU may also have different names, but those skilled in the art can understand their meanings. For example, in the ORAN system, CU may also be called O-CU (Open CU), DU may also be called O-DU, CU-CP may also be called O-CU-CP, CU-UP may also be called O-CU-UP, and RU may also be called O-RU. For the convenience of description, this application uses CU, CU-CP, CU-UP, DU and RU as examples for description. Any unit of CU (or CU-CP, CU-UP), DU and RU in this application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.
[0102] A terminal may also be referred to as a terminal device, user equipment (UE), mobile station, mobile terminal, etc. Terminals can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wearable, smart transportation, smart city, etc. A terminal can be a mobile phone, tablet computer, computer with wireless transceiver function, wearable device, vehicle, drone, helicopter, airplane, ship, robot, robotic arm, smart home device, etc. The embodiments of the present application do not limit the device form of the terminal.
[0103] In the embodiments of the present application, the communication device used to implement the functions of a RAN node or terminal may be a RAN node or terminal, or may be a device capable of supporting the RAN node or terminal in implementing the functions, such as a chip or processor, which may be installed in the RAN node or terminal. In the technical solutions provided in the embodiments of the present application, the technical solutions provided in the embodiments of the present application are described by taking the device used to implement the functions of a RAN node or terminal as an example, that is, a RAN node or terminal.
[0104] Figure 2 shows another communication network architecture in the communication system provided by the present application. In the architecture shown in Figure 2, the control plane (CP) and user plane (UP) of the CU can be separated and divided into different entities for implementation, namely the control plane CU entity (CU-CP entity) and the user plane CU entity (CU-UP entity). In this network architecture, the signaling generated by the CU can be sent to the UE through the DU, or the signaling generated by the UE can be sent to the CU through the DU. The DU can directly encapsulate the signaling through the protocol layer and pass it to the UE or CU without parsing it. In this network architecture, the CU is divided into a network device on the RAN side. In addition, the CU can also be divided into a network device on the CN side. This application does not limit this.
[0105] The method provided by the embodiment of the present application is described in detail below with reference to the accompanying drawings. It should be noted that the message names between the network elements or the names of the parameters in the messages in the following embodiments of the present application are only examples, and other names may also be used in the specific implementation, and the embodiments of the present application do not specifically limit this.
[0106] In a mobile communication system, in one possible handover process, the mobility management of a connected UE is controlled by a RAN node. Specifically, the RAN node sends a handover message to instruct the UE which cell to handover to and how to perform the handover. For example, as shown in Figure 3, after receiving the handover message, the UE accesses the target cell based on the content contained in the handover message.
[0107] Step 1: The source RAN node sends an RRC reconfiguration message to the connected UE, which contains parameters such as measurement object, report configuration, and measurement identifier.
[0108] Step 2: After measuring a series of cells according to the RRC reconfiguration message, the UE generates reports to report various events to the currently connected source RAN node, such as the signal strength of the current serving cell is lower than the threshold and the target cell signal is higher than the threshold.
[0109] Step 3: After receiving the report from the UE, the source RAN node will decide whether the UE should be handed over. If the UE is to be handed over, the source RAN node will send a handover request message to the target RAN node.
[0110] Step 4: The target RAN node decides whether to allow the UE to access based on its own connection count and other conditions. If allowed, it sends a handover confirmation message to the source RAN node.
[0111] Step 5: After receiving the handover confirmation message from the target RAN node, the source RAN node sends an RRC reconfiguration message (also called a handover command) to the UE.
[0112] Step 6: The UE initiates random access to the target RAN node according to the handover command. The UE will disconnect from the source RAN node, and there will be a brief interruption in the UE's data transmission and reception before successfully accessing the target RAN node.
[0113] Step 7: The UE sends an RRC reconfiguration complete message to the target RAN node.
[0114] Step 8: The target RAN node sends a context release message to the source RAN node, so that the source RAN node releases the context of the UE.
[0115] According to the method shown in Figure 3, when a remote UE communicates with a source RAN node via an indirect path, if a direct path is to be added between the remote UE and the target RAN node, the remote UE must first be handed over to the target RAN node. During this process, the remote UE releases the original indirect path, and the target RAN node then adds the indirect path between the remote UE and the source RAN node. This entire process results in high latency and signaling overhead.
[0116] Therefore, when the remote UE (an example of the first terminal) communicates with the source RAN node (an example of the first access network node) through a non-direct path (an example of the first path), how to add a direct path (an example of the second path) between the remote UE and the target RAN node or how to switch the direct path (an example of the third path) between the remote UE and the source RAN node to the target RAN node and retain the non-direct path between the remote UE and the source RAN node to reduce latency and signaling overhead is an urgent problem that needs to be solved.
[0117] FIG4 shows a relay communication method 400 provided by an embodiment of the present application, which is used to reduce delay and signaling overhead. The method 400 may include the following steps.
[0118] S401: A first terminal receives a first message from a first access network node. Accordingly, the first access network node sends the first message to the first terminal.
[0119] It should be understood that in various embodiments of the present application, the network node may be a centralized unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU), etc.
[0120] When the first access network node is a CU or an O-CU, the implementation of the first terminal receiving the first message from the first access network node can be that the CU or O-CU sends the first message to the first terminal through one or more network elements (for example, DU and / or RU).
[0121] For example, before S401: a first path exists between the first terminal and the first access network node, and the first path is an indirect path, which can also be referred to as communication between the first terminal and the first access network node via an indirect path. Exemplarily, the first terminal communicates with the first access network node via a second terminal on the first path. There can be one or more second terminals. Optionally, a second path exists between the first terminal and the first access network node, and the second path is a direct path. When the first path and the second path exist, this can also be referred to as communication between the first terminal and the first access network node via multiple paths. That is, before S401, the first terminal can communicate with the first access network node via an indirect path or multiple paths. S401 can be understood as indicating that, when the first terminal and the first access network node communicate via an indirect path or multiple paths, if a direct path is to be added between the first terminal and the second access network node, or the direct path between the first terminal and the first access network node is to be switched to the second access network node, the first terminal can perform a path update operation based on a first message sent by the first access network node.
[0122] For example, the first message includes first indication information and / or first configuration information, the first indication information is used to indicate that the first path is retained, and the first configuration information includes the configuration of the first path. The configuration of the first path can also be referred to as information or parameters used to configure the first path.
[0123] For example, the first message includes information for indicating the first cell, where the first cell is the cell corresponding to the second access network node. Exemplarily, the first cell is the target cell of the first terminal, and may also be referred to as the target access cell. The information of the first cell may be identification information of the first cell. For example, the first message may be understood as a message instructing the first terminal to perform a path update. The first message may be carried in messages such as a radio resource control (RRC) message, a media access control (MAC) control element (CE) or downlink control information (DCI). Exemplarily, the first message is an RRC reconfiguration message.
[0124] It is easy to understand that in the embodiments of the present application, the path update includes adding a third path, or switching the second path to the third path, which can also be called switching, switching to the first cell or switching to the target cell. Optionally, when the path update determines to retain the first path, the path update can be called establishing multiple paths across access network nodes, or establishing multiple paths, which is not limited in this application. The second path is a direct connection path between the first terminal and the first access network node, and the third path is a direct connection path between the first terminal and the second access network node. It is easy to understand that retention can be called maintaining or not disconnecting.
[0125] In one possible implementation, the first indication information may be a display indicating that the first indirect path (an example of the first path) is retained. For example, the first indication information uses a bit indication. Exemplarily, when the bit value is 1, it indicates that the first indirect path is retained. This application does not limit other methods for implementing the indication.
[0126] In another possible implementation, the first indication information may be an implicit indication of retaining the first path. For example, the first indication information indicates the identifier of the relay UE (an example of the second terminal) in the first path. The relay UE identifier enables the remote UE to determine that the relay UE is still selected as the relay device, that is, to retain the first path. For another example, the first indication information indicates the configuration information corresponding to the first path. In other words, the first indication information may also be the first configuration information, that is, in a possible implementation, the first configuration information indicates the configuration of the first path and also implicitly indicates retaining the first path.
[0127] In one possible implementation, the first configuration information includes first key indication information, where the first key indication information is used to indicate a second key, where the second key is the key used by the first terminal for communication with the first access network node after receiving the first message. In another possible implementation, the first key indication information includes indication information indicating that the second key is the same as the first key; wherein the first key is the key used by the first terminal for communication with the first access network node before receiving the first message. In other words, the first key indication information indicates that the key remains unchanged. In another possible implementation, the first key indication information indicates that the key has changed.
[0128] Optionally, the first configuration information also includes one or more of identification information of the second terminal, serving cell information of the second terminal, configurations of one or more protocol layers, and information indicating a path corresponding to the first configuration. The one or more protocol layers corresponding to the first terminal include a physical layer, a MAC layer, an RLC layer, a packet data convergence protocol (PDCP) layer, and an SRAP layer.
[0129] In a possible implementation manner, the first terminal determines to retain the first path according to the first indication information and / or the first configuration information.
[0130] Optionally, retaining the first path further includes determining a configuration corresponding to the first path according to the first configuration information.
[0131] The method further includes: optional step S402: the first terminal performs path update.
[0132] For example, the first terminal performing path updating includes reserving the first path.
[0133] Optionally, the first terminal performing path updating further includes establishing a third path, or switching to the first cell. Optionally, when a second path exists between the first terminal and the first access network node before step S401, the first terminal performing path updating further includes disconnecting the second path.
[0134] The content of the path update performed by the first terminal can refer to the relevant introduction of S506, and will not be repeated in this embodiment of the application.
[0135] By using this method, when performing path updating, the first access network node instructs the first terminal to retain the non-direct path between the first terminal and the first access network node, thereby reducing delay and signaling overhead.
[0136] 5 to 8 respectively provide detailed examples of communication methods based on the solution of Figure 4. It is easy to understand that the steps or contents of Figures 4 to 8 can refer to each other, be combined or separated.
[0137] Next, please refer to FIG5 , which shows a flow chart of a communication method 500 provided in an embodiment of the present application. The method 500 includes:
[0138] Optional step S501: a first terminal sends a first measurement result to a first access network node. Correspondingly, the first access network node receives the first measurement result from the first terminal.
[0139] For example, before S501, the first terminal may communicate with the first access network node via an indirect path or multiple paths. For related content, please refer to the introduction of the indirect path or multiple paths communication between the first terminal and the first access network node in S401, which will not be repeated here.
[0140] Exemplarily, the first measurement result includes: the communication quality between the first terminal and the second terminal. Exemplarily, the first terminal communicates with the first access network node through the second terminal on a non-direct path, and there may be one or more second terminals. The communication quality between the first terminal and the second terminal may be included in a manner that includes a second terminal identifier and a corresponding signal quality. Optionally, the first measurement result also includes the signal quality of the first cell. For example, the signal quality is a reference signal power, a reference signal quality, or other information that can be used to indicate signal quality. Optionally, when the first condition is met, the first terminal determines to send the first measurement result to the first access network node, and the first condition includes one or more of the following: the signal quality of the first cell is higher than a first threshold, the communication quality between the first terminal and the second terminal is higher than a second threshold, or configuration information for periodically reporting the first measurement result is received.
[0141] Optional step S502: Determining whether to perform a path update. It will be readily appreciated that in embodiments of the present application, determining whether to perform a path update can be done in a variety of ways, such as determining whether to perform a path update based on the first measurement result. Optionally, determining whether to perform a path update also includes determining whether to retain the first path. For details regarding path updates, please refer to the description of path updates in S402 and will not be repeated here.
[0142] In a possible implementation manner, the first access network node determines whether to perform a path update.
[0143] For example, the method further includes: the first access network node determining, based on the first measurement result, to perform a path update. Exemplarily, when the signal quality of the first cell in the first measurement result is higher than a specific threshold, the first access network node determines to perform a path update. It will be readily understood that the multiple thresholds in the embodiments of the present application, such as the first threshold, the second threshold, and the specific threshold, may also be referred to as preset thresholds or threshold values. The specific threshold may be predefined by a protocol, determined by an access network node, or determined by a terminal. The multiple thresholds described in the embodiments of the present application may be the same or different.
[0144] Optionally, the first access network node determining whether to perform a path update further includes: the first access network node determining whether to retain the first path. For example, the first access network node determines to retain the first path based on the communication quality between the first terminal and the second terminal. It will be readily understood that when there are multiple second terminals, the first access network node may determine to retain one or more of the multiple first paths. Of course, the first access network node may also use other methods to determine whether to retain the first path, which are not limited in the embodiments of the present application.
[0145] It is easy to understand that when the first access network node determines to perform a path update, where the path update includes retaining the first path, it can also be referred to as the first access network node determining to establish multiple paths across access network nodes.
[0146] Optionally, the method also includes determining the first entity, or determining the establishment method of the first entity corresponding to the first session. It is easy to understand that in the embodiment of the present application, there may be multiple possible ways to determine the establishment method of the first entity corresponding to the first session. The first session may include a protocol data unit (PDU) session, and the first session may include one or more. The first entity may be a service data adaptation protocol (SDAP) entity. For example, the first entity is the entity corresponding to the PDU session. Exemplarily, the function of the first entity includes the mapping between QoS flow and radio bearer. The establishment method of the first entity may include the location where the first entity is established, for example, on which access network node the first entity is established. For example, the establishment method of the first entity may include establishing on the first access network node and / or the second access network node. It is easy to understand that when the first entity is established on the first access network node and the second access network node, the first session may also be referred to as a separated first session. Optionally, the access network node where the first entity is located will establish a second entity corresponding to the first entity, for example, the second entity is a packet data convergence protocol (PDCP) entity. For ease of description, the PDCP bearer located at the first access network node may be referred to as a bearer terminated at the first access network node, and the PDCP bearer located at the second access network node may be referred to as a bearer terminated at the second access network node.
[0147] Optionally, the method also includes determining a first mapping relationship and / or a bearer type. It is easy to understand that there are multiple possible ways to determine the first mapping relationship and / or the bearer type in an embodiment of the present application. Among them, the first mapping relationship includes a mapping relationship between a quality of service (Qos) flow and a bearer. For example, the first mapping relationship is a first mapping relationship corresponding to a first access network node and / or a second access network node. The bearer type may include one or more of a master cell group (MCG) bearer, a first type bearer secondary path bearer, or a split bearer. The first type bearer may be a wireless bearer only on a non-directly connected path of a secondary access network node. Exemplarily, in an embodiment of the present application, the secondary access network node may be the first access network node in cross-node multi-path communication. The bearer type may be a bearer type corresponding to the first access network node and / or the second access network node.
[0148] In one possible implementation, the first access network node determines the first entity. Optionally, when the first access network node determines to establish an inter-node multipath, the method further includes the first access network node determining the first entity. Optionally, the method further includes the first access network node determining the first mapping relationship and / or bearer type.
[0149] Optional step S503: Send a request message.
[0150] For example, the first access network node sends a request message. The request message may also be called a path update request message or a handover request message.
[0151] In a possible manner, the first access network node sends a request message to the second access network node, and correspondingly, the second access network node receives the request message from the first access network node.
[0152] For example, the request message includes information of the first cell. For example, the indication information of the first cell is identification information of the first cell.
[0153] Optionally, the request message also includes one or more of the following information: first bearer information used by the second access network node, the first bearer information including data radio bearer identification information, information for requesting to retain the first path; or information for indicating the addition of a third path. The first bearer information may be a list of DRB identifiers (identities, IDs) that can be used by the second access network node. The information for indicating the addition of a third path may also be referred to as information for indicating the establishment of a cross-node path. It is easy to understand that the first bearer information used by the second access network node may refer to the first bearer that the second access network node can use, or may be referred to as the first bearer information used by the second access network node after receiving the request message.
[0154] Optionally, the request message further includes a second measurement result, wherein the second measurement result includes the communication quality between the first terminal and the second terminal. For details about the communication quality between the first terminal and the second terminal, refer to the description of the communication quality between the first terminal and the second terminal in S501.
[0155] Optionally, the request message also includes one or more of the following information: source configuration information or source QoS information. The source configuration information is used to configure parameters for the first path before the first message. For ease of description, the source configuration information is referred to as configuration #1 (config#1). Exemplarily, the source QoS information is included in the PDU session resources to be setup list.
[0156] Optionally, the method further includes the first access network node sending the first information. For example, the first access network node sends the first information after determining the first entity.
[0157] In a possible implementation manner, the first access network node sends the first information to the second access network node, and correspondingly, the second access network node receives the first information from the first access network node.
[0158] Optionally, the first information includes one or more of the following information: information for requesting resources of the second access network node corresponding to the second bearer; information for indicating the third bearer transmitted on the second access network node, or information for indicating the resources of the first access network node allocated for the fourth bearer.
[0159] The information used to request the resources of the second access network node corresponding to the second bearer may also be referred to as information used to request adding resources of the second access network node for the second bearer, the second bearer being a bearer terminated at the first access network node, and exemplarily, the second bearer being a DRB. Exemplarily, the information used to request the resources of the second access network node corresponding to the second bearer includes one or more of the following information: DRB ID, DRB QoS, uplink (UL) PDCP tunnel information (TNL info) of the associated first access network node, QoS flow ID of the QoS flow mapped to the DRB, and QoS parameters.
[0160] The information used to indicate the third bearer transmitted on the second access network node may also be referred to as information used to indicate which bearers are transmitted on the second access network node. Exemplarily, the third bearer is a DRB. Exemplarily, the information used to indicate the third bearer transmitted on the second access network node includes one or more of the following information: a DRB ID, a DRB QoS, and a QoS flow ID of a QoS flow mapped to the DRB.
[0161] Wherein, the fourth bearer is a bearer that terminates at the second access network node. Exemplarily, the fourth bearer is a DRB. Exemplarily, the information used to indicate the first access network node resources allocated for the fourth bearer includes one or more of the following information: DRB ID, associated first access network node downlink (DL) tunnel information (e.g., secondaryPath TNL info), and QoS flow ID of the QoS flow mapped to the DRB. Wherein, the first access network node DL tunnel information may indicate that the first interface (e.g., Xn port) of the DRB transmits the first access network node GTP-U tunnel endpoint on its lower layer (e.g., RLC layer and layers below it) secondary path (secondaryPath) resource, and the tunnel information is used for the delivery of downlink PDU. The first interface may be a network interface between the first access network node and the second access network node. GTP-U may be used to provide one or more tunnels for each packet data protocol (PDP) context for transmitting user data.
[0162] It is easy to understand that the embodiment of the present application does not limit the timing and content of sending the first information, nor the message carrying the first information. There are many possible ways to send the first information, for example:
[0163] In a possible manner, when the first network node determines that the second entity is established on the first network node, the first information includes information for requesting resources of the second access network node corresponding to the second bearer.
[0164] In one possible approach, when the first network node determines that the second entity is established on the second network node, the first information includes information indicating a third bearer transmitted on the second access network node. Optionally, if a secondary path bearer exists, the first information also includes information indicating resources of the first access network node allocated for the fourth bearer.
[0165] In one possible approach, when the first network node determines that the second entity is established between the first network node and the second network node, the first information includes information indicating a third bearer transmitted on the second access network node. Optionally, if a secondary path bearer exists, the first information also includes information indicating resources of the first access network node allocated for the fourth bearer. Optionally, if an MCG bearer exists, the first information also includes information requesting resources of the second access network node corresponding to the second bearer.
[0166] Optionally, the first information may be carried in a request message, that is, the request message includes the first information. Of course, the first information may also be sent via other messages, which is not limited in the embodiment of the present application.
[0167] Optionally, the second access network node determines air interface resources and / or transport network resources. For example, upon receiving information requesting resources of the second access network node corresponding to the second bearer and / or information indicating resources of the first access network node allocated for the fourth bearer, the second access network node determines the air interface resources and / or transport network resources. Optionally, the second access network node stores source QoS information, for example, the source QoS information is QoS information in a PDU session resources to be setup list.
[0168] Optionally, the method further includes sending second configuration information.
[0169] In one possible implementation, the first access network node sends second configuration information to the second access network node, and the second access network node receives the second configuration information from the first access network node. The second configuration information may be information determined by the first access network node for the first terminal and used after the first message to configure the first path.
[0170] Optionally, the second configuration information may be carried in the request message, that is, the request message includes the second configuration information. Of course, the second configuration information may also be sent via other messages, which is not limited in the embodiment of the present application.
[0171] Optionally, the second configuration information includes second key indication information, where the second key indication information is used to indicate a second key. The second key is a key used by the first terminal to communicate with the first access network node after receiving the first message.
[0172] In one possible approach, config#1 includes a first parameter, which is used to configure the bearer to use a master key or a secondary key. For ease of description, the following uses the example where the first parameter is keyToUse.
[0173] For example, the value of keyToUse in config#1 is master key, which indicates the first key of the first access network node, which can also be called the original key (for the convenience of description below, the original key is recorded as KgNB#1). After establishing multi-path, the master key indicates the third key, which is the key for the first terminal to communicate with the second access network node (for the convenience of description below, the original third key is recorded as KgNB#2). Therefore, the keyToUse parameter on the first path needs to be reconfigured.
[0174] In one possible implementation, the key between the first access network node and the first terminal remains unchanged. There are multiple possible implementations to ensure that the key between the first access network node and the first terminal remains unchanged:
[0175] Method 1: The second key indication information is used to indicate that the key remains unchanged, and there is no restriction on the value of the keyToUse parameter. The value of the keyToUse parameter in config#2 can be a master key or a secondary key, and the second key indication information is used to indicate the original key KgNB#1. That is, the second key indication information is used to indicate that the key between the first access network node and the first terminal remains unchanged, and it can also be called the second key indication information including indication information for indicating that the second key is the same as the first key; wherein the first key is the key used by the first terminal to communicate with the first access network node before receiving the first message, and can also be called the original key.
[0176] Method 2: Use a predefined method. For example, in the scenario where an indirect path or single-site multi-path is switched to an inter-site multi-path, regardless of the value of the keyToUse parameter, the original key KgNB#1 is indicated.
[0177] In another possible implementation, the key between the first access network node and the first terminal is updated, that is, the first key is updated to the second key (hereinafter, for the convenience of description, the second key is recorded as s-Ksn). For example, the second key indication information is used to indicate the second key. Exemplarily, the second key indication information can be keyToUse in config#2, and the value of keyToUse is secondary key. That is, the second key indication information includes information for indicating the second key, that is, the second key indication information can indicate a key change, that is, updating the first key to the second key.
[0178] Optional step S504: Send a request response message.
[0179] For example, the second access network node sends a first request response message.
[0180] In a possible implementation, the second access network node sends a first request response message to the first access network node, and correspondingly, the first access network node receives the first request response message from the second access network node.
[0181] Optionally, the first request response message includes first configuration information. The first configuration information is used to configure the first path after sending the first message. It can be understood that the first configuration information is allocated or determined by the second access network node.
[0182] Optionally, the first configuration information is determined based on the second configuration information. It can be understood that the first configuration information is determined with reference to the second configuration information.
[0183] Optionally, the first configuration information includes first key indication information, where the first key indication information is used to indicate the second key. In one possible implementation, the first key indication information includes indication information indicating that the second key is the same as the first key. For details about the first configuration information, refer to the introduction to the first configuration information in S401 and will not be repeated in this embodiment of the present application.
[0184] Optionally, the first request response message also includes one or more of the following information: information used to indicate a first key derivation parameter, or information used to indicate to the first terminal to retain the first path; wherein, the first key derivation parameter is used to derive the second key, for example, the first key derivation parameter is used by the first terminal to derive the second key.
[0185] Optionally, the first request response message further includes one or more of the following information: information used to indicate the second key to the first access network node, or information used to indicate to the first access network node to retain the first path.
[0186] The information used to indicate the second key to the first access network node may be the second key.
[0187] It is easy to understand that when there are at least two first paths between the first terminal and the first access network node, that is, when the first terminal communicates with the first access network node through one or more second terminals, the instruction to retain the first path in the embodiments of the present application may refer to retaining some or all of the at least two first paths. Optionally, the instruction to retain some or all of the first paths may be indicated by an identifier indicating the second terminal.
[0188] The first access network node may instruct to retain part or all of the at least two first paths. Optionally, the information instructing to retain the first path may further include identifiers of one or more second terminals.
[0189] Optionally, the first request response message also includes information for establishing a third path, for example, the information for establishing the third path includes one or more of the following information: MCG configuration carried in the message, including bearer configuration, random access configuration, or parameters for determining the key between the first terminal and the second access network node.
[0190] In one possible manner, the first configuration information includes one or more of the identification information of the second terminal, the configuration of one or more protocol layers corresponding to the first terminal, and information indicating the first path corresponding to the first configuration. The configuration of the one or more protocol layers corresponding to the first terminal includes: a configuration associated with the PDCP layer (e.g., radiobearerconfig), a configuration associated with the SRAP layer (e.g., sl-L2RemoteUE-Config), and configurations associated with the RLC, MAC layer, and physical layer (e.g., sl-ConfigDedicatedNR). The information indicating the first path corresponding to the first configuration can be understood as indicating one or more first paths corresponding to the first configuration information, that is, indicating which first path or paths the first configuration information corresponds to, and the information indicating the first path corresponding to the first configuration is secondaryPathConfig as an example for introduction.
[0191] It is easy to understand that the first request response message may include multiple information, and the embodiment of the present application does not limit the manner in which the multiple information is carried. For example, the first request response message includes a first container, the first container includes a complete RRC message, and the RRC message includes the first configuration information.
[0192] In one possible transmission method, the first request response message container includes a first field, which may be a field of secondaryPathConfig and is used to configure the first path. The first field includes a complete RRC message. In this method, the request message sent by the first access network node may include a second container, which includes a complete RRC message carrying the second configuration information. The second access network node places the RRC message carried in the second container into the first field as the first container.
[0193] In one possible transmission mode, the first field includes identification information of the second terminal. Optionally, the second access network node determines the configuration of one or more protocol layers corresponding to the first terminal. For example, the configuration of one or more protocol layers corresponding to the first terminal is determined based on the second configuration information. In this mode, the first configuration information includes radiobearerconfig, sl-L2RemoteUE-Config, sl-ConfigDedicatedNR, and secondaryPathConfig.
[0194] In a possible second transmission mode, the first field includes identification information of the second terminal and sl-ConfigDedicatedNR. Optionally, the second access network node determines the configuration corresponding to secondaryPathConfig and sl-L2RemoteUE-Config based on the second configuration information. In this mode, the first configuration information includes radiobearerconfig and sl-ConfigDedicatedNR.
[0195] In a third possible transmission mode, the first field includes the identification information of the second terminal, sl-L2RemoteUE-Config, and sl-ConfigDedicatedNR. Optionally, the second access network node determines the configuration corresponding to secondaryPathConfig based on the second configuration information. In this mode, the first configuration information includes radiobearerconfig and sl-secondaryPathConfig.
[0196] Optionally, for the above-mentioned possible transmission mode 2 or possible transmission mode 3, the first configuration also includes indication information, and the indication information is used to instruct the first terminal to update the sl-ConfigDedicatedNR and sl-L2RemoteUE-Config in the source configuration information according to the sl-ConfigDedicatedNR and sl-L2RemoteUE-Config in the secondaryPathConfig.
[0197] Optionally, when the request message includes information for requesting resources of the second access network node corresponding to the second bearer, the first request response message also includes identification information of the second bearer and downlink tunnel information corresponding to the second bearer (for example, second access network node DL MCG TNL info). For example, the downlink tunnel information corresponding to the second bearer includes a GTP-U tunnel endpoint of the second access network node indicating the Xn transmission of the DRB on its lower layer (RLC layer and below) MCG resources. The tunnel information is used for the delivery of downlink PDUs.
[0198] Optionally, when the request message includes information indicating the first access network node resources allocated for the fourth bearer, the first request response message also includes identification information of the fourth bearer and uplink tunnel information corresponding to the fourth bearer (e.g., second access network node UL PDCP TNL info). For example, the uplink tunnel information corresponding to the fourth bearer includes a GTP-U tunnel endpoint of the second access network node indicating the Xn transmission of the DRB on its PDCP layer. The tunnel information is used for the delivery of the uplink PDU.
[0199] Step S505: Send the first message.
[0200] For example, the first access network node sends a first message.
[0201] In a possible implementation manner, the first access network node sends a first message to the first terminal, and accordingly, the first terminal receives the first message from the first access network node.
[0202] For the content of the first message, please refer to the relevant description of the first message in S401.
[0203] In a possible implementation, the first message is carried in the first request response message. For example, the first message is an RRC message carried in the first container.
[0204] Optionally, the first access network node determines a second key. In one possible implementation, the second key is the same as the first key. In another possible implementation, the second key received from the first request response message is used as the key with the first terminal after sending the first message.
[0205] Optional step S506: The first terminal performs path update.
[0206] For example, the first terminal performing path updating includes reserving the first path.
[0207] In a possible implementation manner, the first terminal determines to retain the first path according to the first indication information.
[0208] In another possible manner, the first terminal determines to retain the first path according to the first configuration information.
[0209] Optionally, the first terminal performing path updating includes updating configuration information between the first terminal and the first access network node.
[0210] In one possible manner, when the first configuration information includes radiobearerconfig, sl-L2RemoteUE-Config, sl-ConfigDedicatedNR and secondaryPathConfig, the first terminal updates corresponding PDCP, SRAP and PC5RLC channel configurations according to the first configuration information.
[0211] In another possible manner, when the first configuration information includes sl-ConfigDedicatedNR and sl-L2RemoteUE-Config, the first terminal updates sl-ConfigDedicatedNR and sl-L2RemoteUE-Config according to the first configuration information.
[0212] Optionally, the first terminal performing path update includes determining a key between the first terminal and the first access network node.
[0213] In one possible approach, the key between the first terminal and the first access network node remains unchanged. For example, based on the first key indication information, the first terminal determines that the key for communication with the first access network node is the first key, i.e., the original key KgNB#1, indicating that the second key is the same as the first key. For another example, if the first terminal determines that the current scenario is transitioning from a non-direct connection or single-node multipath to establishing an inter-node multipath, the first terminal determines that the key for communication with the first access network node is the first key.
[0214] In one possible approach, a key between a first terminal and a first access network node is updated. For example, the first terminal derives a second key based on a first key derivation parameter. Optionally, upon receiving a keyToUse parameter in the first configuration information, the first terminal determines, based on the secondary key indicated by the keyToUse parameter, that the key for communication with the first access network node is the second key, i.e., the new key s-Ksn.
[0215] Optionally, the first terminal performing path updating includes: sending a reconfiguration completion message.
[0216] For example, the first terminal sends a reconfiguration completion message to the second access network node. Correspondingly, the second access network node receives the reconfiguration completion message from the first terminal. The reconfiguration completion message is used to indicate that the configuration is completed.
[0217] Optionally, the method further includes: sending a setup completion message.
[0218] For example, the second access network node sends a setup completion message to the first network node. Correspondingly, the first access network node receives the setup completion message from the second network node. The setup completion message is used to indicate that the establishment of the cross-node multipath is complete.
[0219] Through this method, the first terminal retains the first path when switching to the first cell, avoiding the high delay and high signaling overhead caused by disconnecting the first path when the first terminal updates the path and then re-establishing the first path, thereby improving communication performance.
[0220] Next, please refer to Figure 6, which shows a flow diagram of a communication method 600 provided in an embodiment of the present application. Method 600 includes: Optional step S601: A first terminal sends a first measurement result to a first access network node. In response, a second access network node receives the first measurement result from the first terminal. S601 can refer to the description of the first measurement result in method S501 and is not repeated here.
[0221] For example, before S601, the first terminal may communicate with the first access network node via an indirect path or multipath. For related content, please refer to the introduction of the indirect path or multipath communication between the first terminal and the first access network node in S401, which will not be repeated here.
[0222] Optional step S602: Determine whether to perform a route update. It will be readily appreciated that in embodiments of the present application, there are multiple possible ways to determine whether to perform a route update, such as determining whether to perform a route update based on the first measurement result. For details regarding route updates, please refer to the introduction to route updates in S402 and will not be repeated here.
[0223] In a possible implementation manner, determining whether to perform a path update includes: the first access network node determining whether to switch to the first cell.
[0224] For example, the method further includes: the first access network node determining whether to switch to the first cell based on the first measurement result. Exemplarily, when the signal quality of the first cell in the first measurement result is higher than a specific threshold, the first access network node determines to switch to the first cell. It will be readily understood that the specific threshold in the embodiments of the present application may also be referred to as a specific threshold or a threshold value. The specific threshold may be predefined by a protocol, determined by an access network node, or determined by a terminal. The multiple thresholds described in the embodiments of the present application may be the same or different.
[0225] Optional step S603: Send a request message.
[0226] For example, the first access network node sends a request message.
[0227] In a possible manner, the first access network node sends a request message to the second access network node, and correspondingly, the second access network node receives the request message from the first access network node.
[0228] Optionally, the request message includes one or more of the following information: the second measurement result, information about the first bearer used by the second access network node, the first bearer information including data radio bearer identification information, or information for requesting to retain the first path. For the second measurement result, the first bearer information, and the information for requesting to retain the first path, refer to the relevant description in S503.
[0229] Optionally, the request message also includes one or more of the following information: source configuration information or source QoS information. The source configuration information is used to configure parameters for the first path before the first message. For ease of description, the source configuration information is referred to as configuration #1 (config#1). Exemplarily, the source QoS information is included in the PDU session resources to be setup list.
[0230] Optional step S604: The second access network node determines whether to perform a path update, where whether to perform a path update includes whether to allow the first terminal to access the first cell. Optionally, whether to perform a path update also includes determining whether to retain the first path.
[0231] For example, when the signal quality between the first terminal and the second terminal is higher than a specific threshold, the second access network node determines to retain the first path.
[0232] Optionally, the method further includes determining a first entity.
[0233] For example, the second access network node determines the first entity.
[0234] Optionally, the method further includes determining a first mapping relationship and / or a bearer type.
[0235] For example, the second access network node determines the first mapping relationship and / or bearer type.
[0236] The method for determining the first entity and / or the method for determining the first mapping relationship and / or the bearer type can refer to the relevant description of S502. The difference is that in S502, the first access network node is used as an example for determination, while in S604, the second access network node is used for determination.
[0237] Optional step S605: Send a request response message.
[0238] For example, the second access network node sends a request response message.
[0239] In a possible manner, the second access network node sends a first request response message to the first access network node, and correspondingly, the first access network node receives the first request response message from the second access network node.
[0240] Optionally, the first request response message includes first configuration information. The first configuration information is used to configure the first path after sending the first message. It can be understood that the first configuration information is allocated or determined by the second access network node.
[0241] Exemplarily, the first configuration information is determined according to the source configuration.
[0242] Optionally, the first configuration information includes first key indication information, where the first key indication information is used to indicate the second key. In one possible implementation, the first key indication information includes indication information indicating that the second key is the same as the first key. For details about the first configuration information, refer to the introduction to the first configuration information in S401 and will not be repeated in this embodiment of the present application.
[0243] Optionally, the first request response message also includes one or more of the following information: information used to indicate a first key derivation parameter, or information used to indicate to the first terminal to retain the first path; wherein, the first key derivation parameter is used to derive the second key, for example, the first key derivation parameter is used by the first terminal to derive the second key.
[0244] Optionally, the first request response message further includes one or more of the following information: information used to indicate the second key to the first access network node, or information used to indicate to the first access network node to retain the first path.
[0245] The information used to indicate the second key to the first access network node may be the second key.
[0246] Optionally, the first request response message also includes information for establishing a third path, for example, the information for establishing the third path includes one or more of the following information: MCG configuration carried in the message, including bearer configuration, random access configuration, or parameters for determining the key between the first terminal and the second access network node.
[0247] For one or more types of information included in the first request response message, reference may be made to the relevant description of the corresponding information in the first request response message in S504, and no further details will be given.
[0248] Optionally, the method also includes the second network node sending second information to the first network node, the second information including one or more of the following information: information indicating the fifth bearer transmitted on the first access network node, resource information of the second access network node allocated for the second bearer; or resource information of the first access network node for requesting the fourth bearer.
[0249] Exemplarily, the fifth bearer is a DRB. Exemplarily, the fifth bearer information indicating transmission at the first access network node includes one or more of the following information: a DRB ID, a DRB QoS, and a QoS flow ID of a QoS flow mapped to the DRB.
[0250] For example, the second bearer is a bearer terminated at the first access network node, and the second bearer may be a DRB. Exemplarily, the resource information of the second access network node allocated for the second bearer includes one or more of the following information: a DRB ID, corresponding uplink PDCP tunnel information of the second access network node (e.g., UL PDCP TNL info), and a QoS flow ID of a QoS flow mapped to the DRB.
[0251] The fourth bearer is a bearer terminated at the second access network node. Exemplarily, the fourth bearer is a DRB. Exemplarily, the resource information of the first access network node for requesting the fourth bearer includes one or more of the following information: a DRB ID, a DRB QoS, uplink PDCP tunnel information of the corresponding second access network node (e.g., UL PDCP TNL info), a QoS flow ID of a QoS flow mapped to the DRB, and QoS parameters.
[0252] It is easy to understand that the embodiments of the present application do not limit the timing and content of sending the second information, nor the message carrying the second information. There are many possible ways to send the second information, for example:
[0253] In one possible manner, when the second network node determines that the second entity is established at the first network node, the second information includes fifth bearer information indicating transmission at the first access network node and resource information of the second access network node indicating allocation of the second bearer.
[0254] In a possible manner, when the second network node determines that the second entity is established on the second network node, the second information includes resource information of the first access network node used to request the fourth bearer.
[0255] In one possible manner, when the second network node determines that the second entity is established on the first network node and the second network node, the second information includes information indicating a fifth bearer transmitted on the first access network node, resource information of the second access network node indicating allocation of the second bearer, and resource information of the first access network node for requesting a fourth bearer.
[0256] Optionally, the second information may be carried in the request message, that is, the request message includes the second information. Of course, the second information may also be sent via other messages, which is not limited in the embodiment of the present application.
[0257] Optionally, when the second information includes resource information of the first access network node for requesting the fourth bearer, the method further includes the second access network node receiving downlink secondary path tunnel information (eg, DL secondaryPath TNL info) from the first access network node.
[0258] Optionally, when the second information includes resource information indicating the second access network node allocated for the second bearer, the method further includes the second access network node receiving first access network node uplink PDCP tunnel information (eg, UL PDCP TNL info) from the first access network node.
[0259] Optional step S606: Send a first message.
[0260] For example, the first access network node sends a first message.
[0261] In a possible implementation manner, the first access network node sends a first message to the first terminal, and accordingly, the first terminal receives the first message from the first access network node.
[0262] For the content of the first message, please refer to the relevant description of the first message in S401.
[0263] In a possible implementation, the first message is carried in the first request response message. For example, the first message is an RRC message carried in the first container.
[0264] Optionally, the first access network node determines a second key. In one possible implementation, the second key is the same as the first key. In another possible implementation, the second key received from the first request response message is used as the key with the first terminal after sending the first message.
[0265] Optional step S607: The first terminal performs path update.
[0266] For the first terminal to update the path, reference may be made to the relevant description of S506 , which will not be repeated here.
[0267] This method allows a first terminal to establish a cross-node multipath from an indirect path or multipath, allowing the first and second access network nodes to complete the cross-node multipath configuration during the path update process. The first terminal can retain the indirect path with the source base station, simplifying the process and reducing signaling overhead. Optionally, the second access network node can decide to establish the cross-node multipath, making the access network node's decision more flexible.
[0268] It is easy to understand that in step S604, the second access network node may refuse to retain the first path, or may refuse to establish a cross-node multipath. For example, refusing to retain the first path includes accepting handover to the first cell and refusing to retain the first path. As shown in Figure 7, a flow diagram of a communication method 700 provided in an embodiment of the present application is provided. Method 700 includes:
[0269] Optional step S701: a first terminal sends a first measurement result to a first access network node, and correspondingly, a second access network node receives the first measurement result from the first terminal.
[0270] Optional step S702: Determine whether to perform path update.
[0271] Optional step S703: Send a request message.
[0272] The contents of S701-S703 can refer to the relevant description of S601-S603 and will not be repeated here.
[0273] Optional step S704: The second access network node determines whether to perform a path update, where whether to perform a path update includes whether to allow the first terminal to access the first cell. Optionally, whether to perform a path update also includes determining whether to retain the first path.
[0274] In one possible manner, the second access network node determines that the first terminal is allowed to access the first cell, which may also be referred to as the second access network node determining that handover to the first cell is allowed.
[0275] In one possible approach, the second access network node determines not to retain the first path, or not to establish an inter-node multipath. For example, when the signal quality between the first terminal and the second terminal is lower than a specific threshold, the second access network node determines to retain the first path.
[0276] Optional step S705: Send a request response message.
[0277] For example, the second access network node sends a request response message.
[0278] In one possible manner, the second access network node sends a second request response message to the first access network node, and correspondingly, the first access network node receives the second request response message from the second access network node.
[0279] Optionally, the second request response message includes indication information for indicating rejection of retaining the first path. The indication information for indicating rejection of retaining the first path may include reason information for indicating rejection of retaining the first path.
[0280] Optionally, the second request response message also includes information for establishing a third path, for example, the information for establishing the third path includes one or more of the following information: MCG configuration carried in the message, including bearer configuration, random access configuration, or parameters for determining the key between the first terminal and the second access network node.
[0281] For one or more types of information included in the second request response message, reference may be made to the relevant description of the corresponding information in the first request response message in S504, and details will not be repeated here.
[0282] Optional step S706: Send a first message.
[0283] For example, the first access network node sends a first message.
[0284] In a possible implementation manner, the first access network node sends a first message to the first terminal, and accordingly, the first terminal receives the first message from the first access network node.
[0285] For example, the first message is a message carried in the second request response message.
[0286] Optional step S707: The first terminal performs path update.
[0287] For example, the first terminal establishes a third path and disconnects from the first access network node according to the first message.
[0288] With this method, the second access network node can refuse to retain the first path, or refuse to establish an inter-node multi-path. For example, it can accept a handover to the first cell and refuse to retain the first path. The decision to establish an inter-node multi-path by the second access network node makes the decision more flexible.
[0289] Next, please refer to FIG8 , which shows a flow chart of a communication method 800 provided in an embodiment of the present application. The method 800 includes:
[0290] Optional step S801: A first terminal sends a first measurement result to a first access network node, and correspondingly, a second access network node receives the first measurement result from the first terminal. For S801, reference may be made to the description of the first measurement result in method S501, and details are omitted.
[0291] For example, before S801, the first terminal may communicate with the first access network node via an indirect path or multipath. For related content, please refer to the introduction of the indirect path or multipath communication between the first terminal and the first access network node in S401, which will not be repeated here.
[0292] Optional step S802: Determine whether to perform a route update. It will be readily appreciated that in embodiments of the present application, there are multiple possible ways to determine whether to perform a route update, such as determining whether to perform a route update based on the first measurement result. For details regarding route updates, please refer to the introduction to route updates in S402 and will not be repeated here.
[0293] In a possible implementation manner, determining whether to perform a path update includes: the first access network node determining whether to switch to the first cell.
[0294] For steps S801-S802, reference may be made to the relevant descriptions of steps S601-S602.
[0295] Optional step S803: Send a request message.
[0296] For example, the first access network node sends a request message.
[0297] In a possible manner, the first access network node sends a request message to the second access network node, and correspondingly, the second access network node receives the request message from the first access network node.
[0298] Optionally, the request message includes one or more of the following information: the second measurement result, the first bearer information used by the second access network node, the first bearer information including data radio bearer identification information, information for requesting to retain the first path, or auxiliary information.
[0299] Among them, the second measurement result, the first bearer information, and the information for requesting to retain the first path can refer to the relevant description in S503. Exemplarily, the auxiliary information includes information used by the second access network node to determine the first configuration information. For example, the auxiliary information includes the configuration information expected by the first access network node, and the expected configuration information may include a QoS flow ID, indicating which QoS flows are expected to be transmitted at the first access network node, and indication information, which is used to indicate whether the second access network node is expected to add first access network node resources for the bearer terminated at the second access network node. Exemplarily, the indication information includes auxiliary path tunnel information.
[0300] Optionally, the request message also includes one or more of the following information: source configuration information or source QoS information. The source configuration information is used to configure parameters for the first path before the first message. For ease of description, the source configuration information is referred to as configuration #1 (config#1). Exemplarily, the source QoS information is included in the PDU session resources to be setup list.
[0301] Optional step S804: The second access network node determines whether to perform a path update, where whether to perform a path update includes whether to allow the first terminal to access the first cell. Optionally, whether to perform a path update also includes determining whether to retain the first path.
[0302] For example, when the signal quality between the first terminal and the second terminal is higher than a specific threshold, the second access network node determines to retain the first path.
[0303] Optionally, the method further includes determining a first entity.
[0304] For example, the second access network node determines the first entity.
[0305] Optionally, the method further includes determining a first mapping relationship and / or a bearer type.
[0306] For example, the second access network node determines the first mapping relationship and / or bearer type.
[0307] The method for determining the first entity and / or the method for determining the first mapping relationship and / or the bearer type can refer to the relevant description of S502. The difference is that in S502, the first access network node is used as an example for determination, while in S804, the second access network node is used for determination.
[0308] In a possible implementation, if the request message carries auxiliary information, the second access network node may generate a configuration based on the auxiliary information. Of course, the auxiliary information may also be ignored, which is not limited in the embodiment of the present application.
[0309] Optional step S805: Send a second message.
[0310] For example, the second access network node sends the second message.
[0311] In a possible implementation manner, the second access network node sends a second message to the first access network node, and correspondingly, the first access network node receives the second message from the second access network node.
[0312] For example, the second message is used to request adding an indirect path, and the second message includes identification information of the second terminal.
[0313] Optionally, the second message further includes one or more of the following information: information for indicating the second key to the first access network node, or seventh bearer information used by the first access network node, the seventh bearer information including bearer identification information. The seventh bearer information used by the first access network node may be seventh bearer information that the first access network node can use after receiving the second message. Exemplarily, the seventh bearer information includes a DRB ID list.
[0314] In one possible embodiment, the method further includes the second network node sending third information to the first network node, where the third information includes one or more of the following information: information for requesting resource information of the first access network node for the fourth bearer; information corresponding to the first QoS transmitted at the first access network node; or information corresponding to the second QoS transmitted at the second access network node. The fourth bearer is a bearer terminated at the second access network node. The information corresponding to the first QoS may include a QoS flow ID, and optionally, the information corresponding to the first QoS also includes QoS parameters. The information corresponding to the second QoS may include a QoS flow ID, and optionally, the information corresponding to the second QoS also includes QoS parameters.
[0315] It is easy to understand that the embodiments of the present application do not limit the timing and content of sending the third information, nor the message carrying the third information. There are many possible ways to send the third information, for example:
[0316] In a possible manner, when the second network node determines that the second entity is established in the first network node, the third information includes information corresponding to the first QoS transmitted in the first access network node.
[0317] In a possible manner, when the second network node determines that the second entity is established on the second network node, the third information includes information for requesting resource information of the first access network node for the fourth bearer.
[0318] In one possible manner, when the second network node determines that the second entity is established at the first network node and the second network node, the third information includes information for requesting resource information of the first access network node for the fourth bearer and information corresponding to the second QoS transmitted at the second access network node.
[0319] Optionally, the third information may be carried in the second message, that is, the second message includes the third information. Of course, the third information may also be sent through other messages, which is not limited in the embodiment of the present application.
[0320] Optional step S806: Receive a third message.
[0321] For example, the first access network node receives the third message.
[0322] In a possible implementation manner, the first access network node sends a third message to the second access network node, and correspondingly, the second access network node receives the third message from the first access network node.
[0323] For example, the third message includes the second configuration information. Exemplarily, the second configuration information includes second key indication information, and the second key indication information is used to indicate the second key. For the content of the second configuration information, please refer to the relevant introduction in S503 and will not be repeated here.
[0324] Optionally, when the third information includes information for requesting resource information of the first access network node for the fourth bearer, the method further includes the second access network node receiving resource information of the first access network node allocated for the fourth bearer from the first access network node, the resource information including the DRB ID, the corresponding first access network node downlink secondary path tunnel information (e.g., DL secondaryPath TNL info), and the QoS flow ID of the QoS flow mapped to the DRB. Optionally, the second access network node receiving the resource information of the first access network node allocated for the fourth bearer may be received through a third message, that is, the resource information of the first access network node allocated for the fourth bearer may be carried in the third message.
[0325] Optionally, when the third information includes information corresponding to a first QoS transmitted at the first access network node and / or information corresponding to a second QoS transmitted at the second access network node, the method further includes the second access network node receiving resource information of the first access network node allocated for the fourth bearer and / or resource information of the second access network node allocated for the second bearer from the first access network node. The resource information of the second access network node allocated for the second bearer includes DRB ID, DRB QoS, corresponding uplink PDCP tunnel information of the first access network node (e.g., UL PDCP TNL info), and QoS flow ID of the QoS flow mapped to the DRB, and QoS parameters. Optionally, the second access network node receives the resource information of the first access network node allocated for the fourth bearer and / or the resource information of the second access network node allocated for the second bearer through a third message, that is, the resource information of the first access network node allocated for the fourth bearer and / or the resource information of the second access network node allocated for the second bearer can be carried in the third message.
[0326] Optionally, when the third message includes resource information of the second access network node used to allocate the second bearer, the method further includes the second access network node receiving second access network node downlink master cell group tunnel information (e.g., DL MCG TNL info) from the first access network node.
[0327] Optional step S807: Send a request response message.
[0328] For example, the second access network node sends a request response message.
[0329] In a possible manner, the second access network node sends a first request response message to the first access network node, and correspondingly, the first access network node receives the first request response message from the second access network node.
[0330] Optionally, the first request response message includes first configuration information. The first configuration information is used to configure the first path after sending the first message. It can be understood that the first configuration information is allocated or determined by the second access network node.
[0331] Exemplarily, the first configuration information is determined according to the second configuration information.
[0332] Optionally, the first request response message also includes information for establishing a third path, for example, the information for establishing the third path includes one or more of the following information: MCG configuration carried in the message, including bearer configuration, random access configuration, or parameters for determining the key between the first terminal and the second access network node.
[0333] In one possible manner, the first configuration information includes one or more of identification information of the second terminal, configurations of one or more protocol layers corresponding to the first terminal, and information indicating a first path corresponding to the first configuration. The configurations of the one or more protocol layers corresponding to the first terminal include: configurations associated with the PDCP layer (e.g., radiobearerconfig), configurations associated with the SRAP layer (e.g., sl-L2RemoteUE-Config), and configurations associated with the RLC, MAC, and physical layers (e.g., sl-ConfigDedicatedNR).
[0334] It is easy to understand that the first request response message may include multiple information, and the embodiment of the present application does not limit the manner in which the multiple information is carried. For example, the first request response message includes a first container, the first container includes a complete RRC message, and the RRC message includes the first configuration information.
[0335] For the one or more pieces of information included in the first request response message and the manner in which the information in the first request response message is carried, reference may be made to the description of the corresponding information and the manner in which the information is carried in the first request response message in S504 and will not be repeated here.
[0336] Step S808: Send the first message.
[0337] For example, the first access network node sends a first message.
[0338] In a possible implementation manner, the first access network node sends a first message to the first terminal, and accordingly, the first terminal receives the first message from the first access network node.
[0339] For the content of the first message, please refer to the relevant description of the first message in S401.
[0340] In a possible implementation, the first message is carried in the first request response message. For example, the first message is an RRC message carried in the first container.
[0341] Optional step S809: The first terminal performs path update.
[0342] For example, the first terminal performing path updating includes reserving the first path.
[0343] For the contents of steps S808-S809, please refer to the relevant descriptions of steps S505-S506.
[0344] This method allows a first terminal to retain the indirect path with the source base station when establishing a cross-node multipath from an indirect path or multipath, simplifying the process and reducing signaling overhead. Optionally, a second access network node can decide to establish a cross-node multipath, making the decision more flexible.
[0345] It is easy to understand that when the first terminal communicates with the first access network node through a non-direct path or multi-path, if the key between the first terminal and the first access network node is updated, for example, the first key is updated to the second key, when the configuration corresponding to the QoS flow / DRB transmitted on the non-direct path is retained, in this case, the first terminal may cache the uplink / downlink data packet encrypted with the first key. If the transmission continues, the first terminal or the first access network node will use the second key to decrypt it, resulting in an error packet problem; if the data packet is discarded directly, since there may be other third terminals connected to the first access network node through the second terminal, discarding the data packet will cause the uplink data of the third terminal to be lost.
[0346] This embodiment of the present application provides a relay communication method 900, including:
[0347] Optional step S901: A first path exists between a first terminal and a first access network node, the first path being an indirect path. The key between the first terminal and the first access network node is a fourth key, and the identifier used by the first terminal on the first path includes a first local identifier. Exemplarily, the first terminal communicates with the first access network node via a second terminal on the first path. There may be one or more second terminals. Optionally, a second path exists between the first terminal and the first access network node, the second path being a direct path.
[0348] For example, the local ID is local ID.
[0349] S902: The first terminal receives a fourth message.
[0350] For example, a first terminal receives a fourth message from a first access network node. The fourth message includes the first terminal's second local identifier and a fifth key derivation parameter, where the fifth key derivation parameter is used to derive a fifth key. The second local identifier is different from the first local identifier. The fifth key is the key between the first terminal and the first access network node. This indicates that the key between the first terminal and the first access network node has been updated from the fourth key to the fifth key. For ease of description, the fourth key is referred to as the old key, and the fifth key is referred to as the new key.
[0351] Optional step S903: The second terminal receives a fifth message from the first access network node, where the fifth message includes the second local identifier of the first terminal.
[0352] Optionally, the first terminal and / or the first access network node determines the key corresponding to the data packet according to the local identifier included in the data packet.
[0353] Optional step S904: The first terminal sends a data packet to the first access network node. Optionally, the first terminal sends the data packet to the first access network node via a second terminal. In other words, the second terminal may forward the data packet to the first access network node on behalf of the first terminal. Optionally, the second terminal may process the data packet before forwarding it.
[0354] For example, the data packet includes a first data packet and / or a second data packet.
[0355] In one possible implementation, a first terminal sends a first data packet to a first access network node. The first data packet includes a first local identifier and first data, and the first data is encrypted using a fourth key. It will be readily understood that the first data packet may be sent by the first terminal to the first access network node before the first terminal receives the fourth message. That is, the first data packet may include data that was sent by the first terminal and cached at the second terminal, encrypted using an old key. The second terminal may forward the first data packet to the first access network node after the first terminal receives the fourth message.
[0356] In another possible implementation, the first terminal sends a second data packet to the first access network node, where the second data packet includes a second local identifier and second data, and the second data is encrypted using a fifth key.
[0357] The embodiments of the present application do not limit the time or order of sending or receiving data packets.
[0358] Accordingly, the first access network node receives the data packet from the first terminal. Optionally, the first access network node receives the data packet from the first terminal via the second terminal. It can be understood that the second terminal processes the data packet from the first terminal and then forwards it to the first access network node.
[0359] In one possible implementation, a first access network node receives a first processed data packet, where the first processed data packet includes a first local identifier and first data. It can be understood that the first processed data packet is a data packet obtained after processing the first data packet. Optionally, the first processed data packet may be the same as the first data packet.
[0360] In one possible implementation, the first access network node receives a second processed data packet, where the second processed data packet includes a second local identifier and second data. It can be understood that the second processed data packet is a data packet obtained after processing the second data packet. Optionally, the second processed data packet may be the same as the second data packet.
[0361] In a possible implementation, the first access network node determines, based on the first local identifier included in the first processed data packet, that the first data is encrypted using the fifth key.
[0362] In a possible implementation, the first access network node determines, based on the second local identifier included in the second processed data packet, that the second data packet is encrypted using the fifth key.
[0363] It can be understood that the first access network node determines whether the data packet is encrypted using the new key or the old key according to the local identifier, which can also be called determining the encryption method of the data packet.
[0364] Optionally, after the first access network node determines the encryption method of the data packet, the first access network node has multiple possible methods for processing the data packet.
[0365] For example, when the first access network node determines that the first data is encrypted using the fourth key and / or that the second data is encrypted using the fifth key, in one possible approach, the first access network node decrypts the first data using the fourth key and / or decrypts the second data using the fifth key. In another possible approach, the first access network node discards the first data and / or decrypts the second data using the fifth key. This allows the first access network node to flexibly process received data.
[0366] Optional step S905: The first access network node sends a data packet to the first terminal. Optionally, the first access network node sends the data packet through the second terminal.
[0367] For example, the data packet includes the third data packet and / or the fourth data packet.
[0368] In one possible implementation, the first access network node sends a third data packet to the first terminal. The third data packet includes the first local identifier and third data, and the third data is encrypted using a fourth key. It will be readily understood that the third data packet may be sent to the first terminal before the fourth message is sent to the first terminal. That is, the third data packet may include data encrypted using an old key and cached at the second terminal after being sent by the first access network node. The second terminal may forward the third data packet to the first terminal after the first access network node sends the fourth message to the first terminal.
[0369] For example, it can be understood that after the key of the first access network node is updated from the fourth key to the fifth key, the first access network node uses the fourth key and / or the fifth key to decrypt when receiving data from the first terminal. The fifth key is used when sending data to the first terminal. Correspondingly, after the key of the first terminal is updated from the fourth key to the fifth key, the first terminal uses the fourth key and / or the fifth key to decrypt when receiving data from the first terminal. The fifth key is used when sending data to the first access network node. In this way, the second terminal may cache uplink / downlink data packets encrypted with the fourth key, so that the first access network node can correctly decrypt the data packets and avoid the problem of wrong packets. In a possible implementation method, the first access network node sends a fourth data packet to the first terminal, the fourth data packet includes a second local identifier and fourth data, and the fourth data packet is encrypted using the fifth key.
[0370] Accordingly, the first terminal receives the data packet from the first access network node. Optionally, the first terminal receives the data packet from the first terminal via the second terminal. It can be understood that the second terminal processes the data packet from the first access network node and then forwards it to the first terminal.
[0371] In one possible implementation, the first terminal receives a third processed data packet, which includes the first local identifier and the third data. It can be understood that the third processed data packet is a data packet obtained after processing the third data packet. Optionally, the third processed data packet may be the same as the third data packet.
[0372] In one possible implementation, the first terminal receives a fourth processed data packet, which includes the first local identifier and fourth data. It can be understood that the fourth processed data packet is a data packet obtained after processing the fourth data packet. Optionally, the fourth processed data packet can also be the same as the fourth data packet. It is easy to understand that the processed data packet can be processed by the second terminal.
[0373] In a possible implementation, the first terminal determines, based on the first local identifier included in the third processed data packet, that the third data is encrypted using the fourth key.
[0374] In a possible implementation, the first terminal determines, based on the second local identifier included in the fourth processed data packet, that the fourth data is encrypted using the fifth key.
[0375] Optionally, after the first terminal determines the encryption method of the data packet, the first terminal has multiple possible methods for processing the data packet.
[0376] For example, when the first terminal determines that the third data is encrypted using the fourth key and / or that the fourth data is encrypted using the fifth key, in one possible approach, the first terminal decrypts the third data using the fourth key and / or decrypts the fourth data using the fifth key. In another possible approach, the first terminal discards the third data and / or decrypts the fourth data using the fifth key. In this manner, the first terminal can flexibly process received data.
[0377] Optionally, if the first access network node does not receive a data packet carrying the first local identifier within the first time period, the first access network node may allocate the first local identifier to other terminals; otherwise, the first local identifier cannot be allocated to other terminals.
[0378] Through this method, the first terminal and / or the first access network node can determine whether the data packet is encrypted with a new key or the original key through the local identifier carried by the data packet, thereby avoiding the problem of packet errors caused by key confusion. The first terminal can continue to transmit data encrypted with the original key, thus avoiding packet loss.
[0379] Corresponding to the method provided in the above method embodiment, the present application embodiment also provides a corresponding device, including a module for executing the corresponding module of the above embodiment. The module can be software, hardware, or a combination of software and hardware.
[0380] Figure 10 provides a schematic structural diagram of a terminal. The terminal can be applied to the scenario shown in Figure 1. The terminal or the components in the terminal can execute the methods shown in Figures 4 to 9 and various possible implementation methods. For ease of explanation, Figure 10 only shows the main components of the terminal. As shown in Figure 10, the terminal 1000 includes a processor, a memory, a control circuit, an antenna, and input and output devices. The processor is mainly used to process communication protocols and communication data, as well as to control the entire terminal, execute software programs, and process data of software programs. The memory is mainly used to store software programs and data. The radio frequency circuit is mainly used to convert baseband signals into radio frequency signals and process radio frequency signals. The antenna is mainly used to transmit and receive radio frequency signals in the form of electromagnetic waves. Input and output devices, such as touch screens, display screens, keyboards, etc., are mainly used to receive data input by users and output data to users.
[0381] When the terminal is powered on, the processor reads the software program from the storage unit, parses and executes the instructions of the software program, and processes the data of the software program. When data needs to be sent wirelessly, the processor performs baseband processing on the data to be sent and outputs the baseband signal to the RF circuit. The RF circuit processes the baseband signal to obtain an RF signal and transmits the RF signal to the outside in the form of electromagnetic waves via the antenna. When data is sent to the terminal, the RF circuit receives the RF signal via the antenna, which is further converted into a baseband signal and output to the processor. The processor converts the baseband signal into data and processes the data.
[0382] For ease of explanation, FIG10 shows only one memory and processor. In an actual terminal, there may be multiple processors and memories. The memory may also be referred to as a storage medium or storage device, etc., which is not limited in the present embodiment.
[0383] As an optional implementation, the processor may include a baseband processor and a central processing unit (CPU). The baseband processor is primarily responsible for processing communication protocols and communication data, while the CPU is primarily responsible for controlling the entire terminal device, executing software programs, and processing software program data. The processor in Figure 10 integrates the functions of both the baseband processor and the CPU. Those skilled in the art will appreciate that the baseband processor and the CPU may also be independent processors interconnected via a bus or other technology. Those skilled in the art will appreciate that a terminal may include multiple baseband processors to accommodate different network standards, multiple CPUs to enhance processing capabilities, and various components of the terminal may be connected via various buses. The baseband processor may also be referred to as a baseband processing circuit or a baseband processing chip. The CPU may also be referred to as a central processing circuit or a central processing chip. The functionality for processing communication protocols and communication data may be built into the processor or stored as a software program in a storage unit, with the processor executing the software program to implement the baseband processing functionality.
[0384] In one example, the antenna and control circuitry with transceiver functions can be considered the transceiver unit 1011 of terminal 1000, and the processor with processing functions can be considered the processing unit 1012 of terminal 1000. As shown in Figure 10, terminal 1000 includes a transceiver unit 1011 and a processing unit 1012. The transceiver unit may also be referred to as a transceiver, transceiver, or transceiver device. Optionally, the device in transceiver unit 1011 that implements the receiving function may be considered the receiving unit, and the device in transceiver unit 1011 that implements the transmitting function may be considered the transmitting unit, i.e., transceiver unit 1011 includes a receiving unit and a transmitting unit. For example, the receiving unit may also be referred to as a receiver, a receiver, a receiving circuit, etc., and the transmitting unit may be referred to as a transmitter, a transmitter, or a transmitting circuit, etc. Optionally, the receiving unit and the transmitting unit may be a single integrated unit or multiple independent units. The receiving unit and the transmitting unit may be located in a single geographic location or dispersed across multiple geographic locations.
[0385] As shown in FIG11 , another embodiment of the present application provides an apparatus 1100. The apparatus may be a terminal or a component of a terminal (e.g., an integrated circuit, a chip, etc.). Alternatively, the apparatus may be a network device (an example of a network node), a component of a network device (e.g., an integrated circuit, a chip, etc.), or a logic module or software that can implement all or part of the functions of the network device. The apparatus may also be another communication module. For example, the apparatus 1100 may implement the functions of the network device in the method shown in FIG2 , FIG4 , FIG6 , or FIG7 , or the apparatus 1100 may implement the functions of the first terminal or the second terminal in the method shown in FIG2 , FIG4 , FIG6 , or FIG7 . The apparatus 1100 may include: an interface module 1101 (or referred to as an interface unit) and a processing module 1102 (or referred to as a processing unit), and may also include a storage module 1103 (or referred to as a storage unit).
[0386] In one possible design, one or more modules in FIG11 may be implemented by one or more processors, or by one or more processors and memories, or by one or more processors and transceivers, or by one or more processors, memories, and transceivers, which are not limited in this embodiment of the present application. The processors, memories, and transceivers may be provided separately or integrated.
[0387] The device has the function of implementing the terminal described in the embodiment of the present application. For example, the device includes a module or unit or means corresponding to the steps involved in the terminal described in the embodiment of the present application. The function or unit or means can be implemented by software, or by hardware, or by hardware executing the corresponding software implementation, or by a combination of software and hardware. For details, please refer to the corresponding description in the aforementioned corresponding method embodiment. Alternatively, the device has the function of implementing the wireless access network device described in the embodiment of the present application. For example, the device includes a module or unit or means corresponding to the steps involved in the wireless access network device described in the embodiment of the present application. The function or unit or means can be implemented by software, or by hardware, or by hardware executing the corresponding software implementation, or by a combination of software and hardware. For details, please refer to the corresponding description in the aforementioned corresponding method embodiment.
[0388] In one possible design, apparatus 1100 includes a processing module 1102 and an interface module 1101. Apparatus 1100 may be, for example, a terminal, or a component of a terminal (e.g., a processor, a chip, or a chip system), or a logic module or software capable of implementing all or part of the terminal's functions.
[0389] In another possible design, the apparatus 1100 includes an interface module 1101 and a processing module 1102. The interface module 1101 is configured to receive a first message from a first network node, and the processing module 1102 is configured to communicate with the first network node via a second terminal on a first path; the first message includes first indication information and / or first configuration information of the first path, the first indication information being used to indicate retention of the first path; the first message includes information indicating a first cell of the second network node; the processing module 1102 is further configured to establish a third path and retain the first path, the third path being a direct connection path between the first terminal and the second network node.
[0390] In one possible design, apparatus 1100 includes a processing module 1102 and an interface module 1101. Apparatus 1100 may be a network node, a component of a network node (e.g., an integrated circuit, a chip, etc.), or a logic module or software capable of implementing all or part of the network device functions.
[0391] In one possible design, apparatus 1100 includes an interface module 1101 and a processing module 1102. Interface module 1101 is configured to send a first message, and processing module 1102 is configured to communicate with a first terminal via a second terminal on a first path; the first message includes first indication information and / or first configuration information, the first indication information is used to indicate retention of the first path, and the first configuration information includes information for configuring the first path; the first message includes information for indicating a first cell of a second network node; and processing module 1102 is further configured to communicate with the first terminal on the first path.
[0392] In one possible design, apparatus 1100 includes an interface module 1101 and a processing module 1102. Interface module 1101 is configured to receive a request message, the request message being used to request establishment of a third path, where the third path is a direct path between a first terminal and a second network node, and the first terminal communicates with the first network node through the second terminal on the first path; interface module 1101 is further configured to send a request response message, the request response message including a first request response message and / or a second request response message, wherein the first request response message includes first configuration information, the first configuration information including information for configuring the first path; and the second request response message including information for indicating a refusal to retain the first path.
[0393] It is understandable that the beneficial effects corresponding to the above-mentioned device 1100 and various possible implementations can be referred to the description in the aforementioned method embodiment or invention content, and will not be repeated here.
[0394] Optionally, the apparatus 1100 may further include a storage module 1103 for storing data or instructions (also referred to as code or program). The other modules may interact or couple with the storage module to implement the corresponding methods or functions. For example, the processing module 1102 may read the data or instructions in the storage module 1103 to enable the apparatus 1100 to implement the method in the above embodiment.
[0395] In one example, the module in the above-mentioned device can be one or more integrated circuits configured to implement the above method, such as: one or more application specific integrated circuits (ASICs), or one or more digital singnal processors (DSPs), or one or more field programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms. For another example, when the module in the device can be implemented in the form of a processing element scheduler, the processing element can be a general-purpose processor, such as a central processing unit (CPU) or other processor that can call a program. For another example, these units can be integrated together and implemented in the form of a system-on-a-chip (SOC).
[0396] Referring to Figure 12, a schematic diagram of a device provided in an embodiment of the present application can be used to implement the above method and various possible implementation methods. As shown in Figure 12, the device includes: a processor 1210 and an interface 1230, and the processor 1210 is coupled to the interface 1230. The interface 1230 is used to communicate with other modules or devices. The interface 1230 can be a transceiver or an input and output interface. The interface 1230 can be, for example, an interface circuit. Optionally, the device also includes a memory 1220 for storing instructions executed by the processor 1210 or storing input data required for the processor 1210 to run instructions or storing data generated after the processor 1210 runs instructions.
[0397] The above method and various possible implementations can be implemented by the processor 1210 calling a program or instruction stored in the memory 1220. The memory 1220 can be inside the device or outside the device, which is not limited in this application.
[0398] Optionally, the functions / implementation processes of the interface module 1101 and the processing module 1102 in FIG11 may be implemented by the processor 1210 in the apparatus shown in FIG12 . Alternatively, the functions / implementation processes of the processing module 1102 in FIG11 may be implemented by the processor 1210 in the apparatus shown in FIG12 , and the functions / implementation processes of the interface module 1101 in FIG11 may be implemented by the interface 1230 in the apparatus shown in FIG12 . Exemplarily, the functions / implementation processes of the interface module 1101 may be implemented by the processor calling program instructions in the memory to drive the interface 1230.
[0399] When the above-mentioned device is a chip applied to a terminal, the chip of the terminal implements the functions of the terminal in the above-mentioned method embodiment. The chip receives information from other modules in the terminal (such as a radio frequency module or antenna), and the information is from other terminals or wireless access network devices; or the chip sends information to other modules in the terminal (such as a radio frequency module or antenna), and the information is sent by the terminal to other terminals or wireless access network devices.
[0400] When the above-mentioned apparatus is a chip applied to a network device (e.g., a wireless access network device), the chip implements the functions of the wireless access network device in the above-mentioned method embodiments. The chip receives information from other modules (e.g., a radio frequency module or antenna) in the wireless access network device, where the information originates from other wireless access network devices or terminals; or the chip sends information to other modules (e.g., a radio frequency module or antenna) in the wireless access network device, where the information originates from the wireless access network device and is intended for other wireless access network devices or terminals.
[0401] Those skilled in the art will understand that the various numerical numbers such as the first and second involved in this application are only for the convenience of description and are not used to limit the scope of the embodiments of the present application, and also indicate the order of precedence. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the objects associated before and after are in an "or" relationship. "At least one" refers to one or more. At least two refers to two or more. "At least one", "any one" or similar expressions refer to any combination of these items, including any combination of single items (individuals) or plural items (individuals). For example, at least one item (individual, kind) of a, b, or c can represent: a, b, c, ab, ac, bc or abc, where a, b, c can be single or multiple. "Multiple" refers to two or more, and other quantifiers are similar.
[0402] In this application, "sending information" can be understood as one device sending information to another device, or as one logic module within a device sending information to another logic module. For example, "a network node sending information" can be understood as the network node sending information to another device (such as a terminal), or as logic module 1 within the network node sending information to logic module 2 within the network node.
[0403] In this application, "receiving information" can be understood as one device receiving information from another device, or as a logic module within a device receiving information from another logic module. For example, "a network node receiving information" can be understood as the network node receiving information from another device (such as a terminal), or as logic module 1 within the network node receiving information from logic module 2 within the network node.
[0404] In this application, "sending information to... (e.g., a terminal)" or the related illustrations in the accompanying drawings can be understood as the destination end of the information being the terminal. This can include sending information to the terminal directly or indirectly. "Receiving information from... (e.g., a terminal)" or "receiving information from... (e.g., a terminal)" or "receiving information sent by (e.g., a terminal)", or the related illustrations in the accompanying drawings can be understood as the source end of the information being the terminal, which can include receiving information from the terminal directly or indirectly. The information may be processed as necessary between the source end and the destination end of the information transmission, such as format changes, etc., but the destination end can understand the valid information from the source end. Similar expressions in this application can be understood similarly and will not be repeated here.
[0405] It should be understood that in various embodiments of the present application, the size of the sequence number of each process does not mean the order of execution, and the order of execution of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application. In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. 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 computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).
[0406] The steps of the method described in the embodiments of the present application can be directly embedded in hardware, a software unit executed by a processor, or a combination of the two. The software unit can be stored in a random access memory (RAM), a flash memory, a read-only memory (ROM), a register, a hard disk, a removable disk, or other storage media in any form in the art. Exemplarily, the storage medium can be connected to the processor so that the processor can read information from the storage medium and can write information to the storage medium. Alternatively, the storage medium can also be integrated into the processor. The processor and the storage medium can be arranged in an ASIC.
[0407] The present application also provides a computer-readable storage medium having a computer program stored thereon, which implements the functions of any of the above method embodiments when executed by a computer.
[0408] The present application also provides a computer program product, which implements the functions of any of the above method embodiments when executed by a computer.
[0409] The same or similar parts between the various embodiments in this application can refer to each other. In the various embodiments in this application, and the various implementation methods / implementation methods / implementation methods in each embodiment, if there is no special explanation and logical conflict, the terms and / or descriptions between different embodiments and the various implementation methods / implementation methods / implementation methods in each embodiment are consistent and can be referenced to each other. The technical features in different embodiments and the various implementation methods / implementation methods / implementation methods in each embodiment can be combined to form new embodiments, implementation methods, implementation methods, or implementation methods according to their inherent logical relationships. The above-described implementation methods of this application do not constitute a limitation on the scope of protection of this application.
[0410] The above is only a specific implementation method of the present application, but the scope of protection of the present application is not limited thereto. Any technician familiar with this technical field can easily think of changes or replacements within the technical scope disclosed in this application, which should be covered by the scope of protection of the present application.
Claims
1. A communication method, applied to a first terminal, characterized in that: include: receiving a first message from a first network node, the first terminal communicating with the first network node through a second terminal on a first path; The first message includes first indication information and / or first configuration information of the first path, where the first indication information is used to indicate that the first path is retained; the first message includes information for indicating a first cell of the second network node; A third path is established and the first path is reserved, wherein the third path is a direct connection path between the first terminal and the second network node.
2. The method according to claim 1, characterized in that: The retaining the first path comprises: Determine to retain the first path according to the first indication information and / or the first configuration information.
3. The method according to claim 1 or 2, characterized in that: The first configuration information includes first key indication information, where the first key indication information is used to indicate a second key, where the second key is a key used by the first terminal to communicate with the first network node after receiving the first message.
4. The method according to claim 3, characterized in that The first key indication information includes indication information used to indicate that the second key is the same as the first key; wherein the first key is a key used by the first terminal to communicate with the first network node before receiving the first message.
5. The method according to any one of claims 1 to 4, characterized in that: The first configuration information also includes one or more of identification information of the second terminal, configuration of one or more protocol layers corresponding to the first terminal, and information indicating a path corresponding to the first configuration.
6. The method according to any one of claims 1 to 5, characterized in that: The method further comprises: A first measurement result is sent to the first network node, where the first measurement result includes communication quality between the first terminal and the second terminal.
7. A communication method, applied to a first network node, characterized in that: include: sending a first message, where the first network node communicates with the first terminal through the second terminal on a first path; the first message includes first indication information and / or first configuration information, the first indication information is used to indicate that the first path is retained, and the first configuration information includes information used to configure the first path; the first message includes information used to indicate a first cell of the second network node; Communicate with the first terminal on the first path.
8. The method according to claim 7, characterized in that The first configuration information includes first key indication information, where the first key indication information is used to indicate a second key, where the second key is a key used by the first terminal to communicate with the first network node after receiving the first message.
9. The method according to claim 8, characterized in that The first key indication information includes indication information used to indicate that the second key is the same as the first key; wherein the first key is a key used by the first terminal to communicate with the first network node before receiving the first message.
10. The method according to any one of claims 7 to 9, characterized in that: The first configuration information also includes one or more of identification information of the second terminal, configuration of one or more protocol layers corresponding to the first terminal, and information indicating a path corresponding to the first configuration.
11. The method according to any one of claims 7 to 10, characterized in that: The method further comprises: Send a request message, where the request message includes identification information of the first cell and one or more of the following messages: first bearer information used by the second network node after receiving the request message, the first bearer information comprising data radio bearer identification information; Information for requesting to retain the first path; or Information used to indicate adding a third path, where the third path is a direct connection path between the first terminal and the second network node.
12. The method according to any one of claims 7 to 11, characterized in that The method further comprises: A first request response message is received, where the first request response message includes the first configuration information.
13. The method according to claim 12, characterized in that The first request response message further includes one or more of the following information: information used to indicate a first key derivation parameter, or information used to indicate to the first terminal that the first path is retained; The first key derivation parameter is used to derive the second key.
14. The method according to any one of claims 7 to 13, characterized in that The method further comprises: A second message is received, where the second message is used to request adding an indirect path, and the second message includes identification information of the second terminal.
15. The method according to claim 14, characterized in that The second message further includes one or more of the following information: Information used to indicate the second key to the first network node, or seventh bearer information to be used by the first network node, wherein the seventh bearer information includes bearer identification information.
16. The method according to claim 14 or 15, characterized in that The method further comprises: In response to the second message, a third message is sent, the third message includes second configuration information, the second configuration information includes second key indication information, and the second key indication information is used to indicate the second key.
17. The method according to any one of claims 7 to 13, characterized in that The method further comprises: Second configuration information is sent, where the second configuration information includes second key indication information, where the second key indication information is used to indicate the second key.
18. The method according to claim 16 or 17, characterized in that The second key indication information includes indication information used to indicate that the second key is the same as the first key, or the second key indication information is used to indicate that the key between the first terminal and the first network node is updated to the second key.
19. The method according to claim 17, characterized in that The sending the second configuration information includes: sending the second configuration information through the request message.
20. The method according to claim 13, characterized in that The first request response message also includes one or more of the following information: Information for indicating the second key to the first network node, or information for indicating to the first network node to retain the first path.
21. The method according to any one of claims 7 to 11, characterized in that The method further comprises: A second request response message is received, wherein the second request response message includes information indicating a refusal to retain the first path.
22. A communication method, applied to a second network node, characterized in that: include: receiving a request message, where the request message is used to request to establish a third path, where the third path is a direct path between the first terminal and the second network node, and the first terminal communicates with the first network node through the second terminal on the first path; sending a request response message, wherein the request response message includes a first request response message and / or a second request response message, The first request response message includes first configuration information, and the first configuration information includes information for configuring the first path; the second request response message includes information for indicating a refusal to retain the first path.
23. The method according to claim 22, characterized in that The first configuration information includes first key indication information, where the first key indication information is used to indicate a second key, where the second key is a key used by the first terminal to communicate with the first network node after receiving the first message.
24. The method according to claim 23, characterized in that The first key indication information includes indication information used to indicate that the second key is the same as the first key; wherein the first key is a key used by the first terminal to communicate with the first network node before receiving the first message.
25. The method according to any one of claims 22 to 24, characterized in that The first configuration information also includes one or more of identification information of the second terminal, configuration of one or more protocol layers corresponding to the first terminal, and information indicating the first path corresponding to the first configuration.
26. The method according to any one of claims 22 to 25, characterized in that The request message includes identification information of the first cell and one or more of the following messages: first bearer information used by the second network node, the first bearer information comprising data radio bearer identification information; Information for requesting to retain the first path; or Information used to indicate adding a third path, where the third path is a direct connection path between the first terminal and the second network node.
27. The method according to any one of claims 22 to 26, characterized in that The first request response message further includes one or more of the following information: information used to indicate a first key derivation parameter, or information used to indicate to the first terminal that the first path is retained; The first key derivation parameter is used to derive the second key.
28. The method according to any one of claims 22 to 27, characterized in that The method further comprises: A second message is sent, where the second message is used to request adding an indirect path, and the second message includes identification information of the second terminal.
29. The method according to claim 28, characterized in that The second message further includes one or more of the following information: Information used to indicate the second key to the first network node, or seventh bearer information used by the first network node, wherein the seventh bearer information includes bearer identification information.
30. The method according to claim 28 or 29, characterized in that The method further comprises: A third message is received, where the third message includes second configuration information, where the second configuration information includes second key indication information, and where the second key indication information is used to indicate the second key.
31. The method according to any one of claims 22 to 28, characterized in that The method further comprises: Second configuration information is received, where the second configuration information includes second key indication information, where the second key indication information is used to indicate the second key.
32. The method according to claim 30 or 31, characterized in that: The second key indication information includes indication information used to indicate that the second key is the same as the first key, or the second key indication information is used to indicate that the key between the first terminal and the first network node is updated to the second key.
33. The method according to claim 31, characterized in that The receiving the second configuration information includes: receiving the second configuration information through the request message.
34. The method according to any one of claims 22 to 33, characterized in that The first request response message also includes one or more of the following information: Information for indicating the second key to the first network node, or information for indicating to the first network node to retain the first path.
35. The method according to claim 22, characterized in that The request message further includes auxiliary information, where the auxiliary information includes information used by the second network node to determine the first configuration information.
36. The method according to any one of claims 30 to 35, characterized in that The method further comprises: The first configuration information is determined according to the second configuration information.
37. A communication device, characterized in that: include: A processor, wherein the processor is coupled to a memory, wherein the memory is used to store programs or instructions, and when the programs or instructions are executed by the processor, the device executes the method according to any one of claims 1 to 6.
38. A communication device, characterized in that: include: A processor, the processor is coupled to a memory, the memory is used to store programs or instructions, when the program or instructions are executed by the processor, the device performs any one of claims 7 to 22, or any one of claims 23 to 35.
39. A communication device, characterized in that: The apparatus comprises means for executing the method of any one of claims 1 to 6.
40. A communication device, characterized in that: The apparatus comprises means for performing the method of any one of claims 7 to 22, or any one of claims 23 to 35.
41. A computer-readable storage medium having instructions stored thereon, characterized in that: When the instructions are executed, the computer is caused to perform the method according to any one of claims 1 to 6, or any one of claims 7 to 22, or any one of claims 23 to 35.
42. A computer program product, characterized in that The method comprises a computer program code, which, when executed, implements the method according to any one of claims 1 to 6, or any one of claims 7 to 22, or any one of claims 23 to 35.
43. A chip, characterized in that: The chip includes a processor, which is coupled to a memory, and the memory is used to store instructions. When the instructions are executed by the processor, the chip implements the method as described in any one of claims 1 to 6, or any one of claims 7 to 22, or any one of claims 23 to 35.
44. A communication system, characterized in that: The communication system comprises the communication device according to claim 37 and / or claim 38.
Citation Information
Patent Citations
Processing method and device and computer readable storage medium
CN116112991A
Communication method and device
CN116980928A
Mobility handling between uu path and PC5 relay path
US20230180076A1
