Communication method, device and storage medium

Abstract

The present application proposes a communication method, device, and storage medium. The method includes: receiving Internet Protocol (IP) data sent by a second communication node; mapping the IP data to an intermediate bearer according to a first preset mapping method, and transmitting the data to a third communication node.

Description

Technical Field

[0001] The present application relates to communications, and in particular to a communications method, device, and storage medium. Background Art

[0002] With the development of wireless multimedia services, the demand for high data rates and user experience is growing, placing higher demands on the system capacity and coverage of traditional cellular networks. To support wider network communications, relay communication technology based on side links (SL) has attracted widespread attention. In 5G New Radio (NR) systems, how to implement relay communication is a pressing issue. Summary of the Invention

[0003] The embodiments of the present application provide a communication method, device, and storage medium, which effectively implement direct link relay communication in a 5G NR system.

[0004] An embodiment of the present application provides a communication method, applied to a first communication node, including:

[0005] receiving Internet Protocol (IP) data sent by the second communication node;

[0006] The IP data is mapped to the intermediate carrier according to a first preset mapping method and transmitted to the third communication node.

[0007] An embodiment of the present application provides a communication method, applied to a first communication node, including:

[0008] receiving downlink data sent by the third communication node;

[0009] Determine the second communication node to which the downlink data belongs according to the IP address in the downlink data;

[0010] The downlink data is mapped into PC5 data according to a second preset mapping method, mapped to a PC5 DRB, and transmitted to the second communication node to which it belongs.

[0011] An embodiment of the present application provides a device, comprising: a memory, and one or more processors;

[0012] The memory is used to store one or more programs;

[0013] When the one or more programs are executed by the one or more processors, the one or more processors implement the method described in any one of the above embodiments.

[0014] An embodiment of the present application provides a storage medium storing a computer program. When the computer program is executed by a processor, the method described in any one of the above embodiments is implemented. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 This is a flow chart of a communication method provided by an embodiment of the present application;

[0016] Figure 2 is a flow chart of another communication method provided by an embodiment of the present application;

[0017] Figure 3 This is a schematic diagram showing a user plane protocol stack provided in an embodiment of the present application;

[0018] Figure 4 This is a schematic diagram of an air interface data forwarding bearer establishment process when a relay UE forwards data for a remote UE, provided in an embodiment of the present application;

[0019] Figure 5 This is a schematic diagram showing another user plane protocol stack provided in an embodiment of the present application;

[0020] Figure 6 This is a schematic diagram of an air interface data forwarding bearer establishment process when another relay UE forwards data for a remote UE provided in an embodiment of the present application;

[0021] Figure 7 This is a schematic diagram showing another user plane protocol stack provided in an embodiment of the present application;

[0022] Figure 8 This is a schematic diagram of an air interface data forwarding bearer establishment process when another relay UE forwards data for a remote UE, provided in an embodiment of the present application;

[0023] Figure 9 This is a structural block diagram of a communication device provided in an embodiment of the present application;

[0024] Figure 10 This is a structural block diagram of another communication device provided in an embodiment of the present application;

[0025] Figure 11 It is a structural diagram of a device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0026] The embodiments of the present application will be described below with reference to the accompanying drawings.

[0027] Application scenarios such as public safety, social networking, short-range data sharing, and local advertising have led to an increasing demand for people to understand and communicate with nearby people or things. Traditional base station-centric cellular networks have obvious limitations in supporting high data rates and proximity services. Against this backdrop of demand, device-to-device (D2D) communication technology has emerged. The application of D2D technology can reduce the burden on cellular networks, reduce battery power consumption of user devices, increase data rates, and improve the robustness of network infrastructure, thus meeting the requirements of the above-mentioned high data rate services and proximity services. D2D technology is also known as Proximity Services (ProSe), unilateral / side link / straight link (SL) communication; the interface between devices is the PC5 interface.

[0028] In order to support a wider range of network communications, SideLink-based relay communication technology has received widespread attention. Based on the communication object, SideLink communication technology can be divided into:

[0029] 1) UE-to-Network Relay: This communication technology supports data relay for UEs in areas where base stations have no coverage or have weak coverage. A UE that needs to communicate with a base station but cannot connect directly to it is called a remote UE, and a UE that provides relay functionality for the remote UE is called a relay UE.

[0030] 2) UE-to-UE relay: This communication technology allows two UEs with communication needs to communicate with each other through the assistance of another supporting UE, even when direct communication is not possible or possible. The UE with communication needs is called the remote UE, and the UE providing the relay function for the remote UE is called the relay UE.

[0031] From the perspective of relay technology implementation, SideLink relay communication technology can be divided into:

[0032] 1) Internet Protocol (IP) layer (Layer-3 based) relay technology, that is, the relay UE completes data forwarding based on the IP information of the data packet (such as IP address and port number). The remote UE does not establish a Radio Resource Control (RRC) connection with the base station (gNB) or the core network.

[0033] 2) Access layer (Layer 2-based) relay technology, that is, the remote UE establishes a connection with the gNB and the core network through the relayUE, and the remote UE forwards the bearer data between the relayUE and the gNB.

[0034] In actual communication, Layer 3-based relay is simple to implement, but its reliability and security are not good enough. Layer 2-based relay is complex to implement, but its support for reliability and security is stronger than Layer 3-based relay, and it can effectively support the mobility and security of remote UEs. Currently, there is no mature relay communication technology in 5G NR systems. In view of this, this application provides a communication method that effectively implements direct link relay communication in 5G NR systems.

[0035] In one embodiment, Figure 1 This is a flow chart of a communication method provided by an embodiment of the present application. Figure 1 As shown, this embodiment is applied to the first communication node and is used for transmission of uplink data. For example, the first communication node may be a relay UE. Figure 1 As shown, this embodiment includes: S110-S120.

[0036] S110. Receive IP data sent by the second communication node.

[0037] S120: Map the IP data to the intermediate bearer according to the first preset mapping method, and transmit the data to the third communication node.

[0038] In an embodiment, during communication between a second communication node and a base station, due to the mobility of the second communication node and the dynamic nature of the network environment, the second communication node experiences deterioration in air interface link quality or relay link quality. In this case, the first communication node can be used as a relay node between the second communication node and a third communication node to forward data transmitted between the second communication node and the third communication node. In one embodiment, after the first communication node receives IP data sent by the second communication node, it can map the IP data to a relay bearer according to a preconfigured first preset mapping method for transmission to the third communication node.

[0039] In one embodiment, the PDU session selected by the first communication node for the IP data includes one of the following:

[0040] Establish an independent Protocol Data Unit (PDU) session for IP data and transmit IP data on the Data Radio Bearer (DRB) corresponding to the PDU session;

[0041] The first communication node's own PDU session is used to transmit IP data.

[0042] In one embodiment, for a case where at least two second communication nodes are connected to the same first communication node, the first preset mapping mode includes one of the following: one-to-one mapping; many-to-one mapping;

[0043] Among them, one-to-one mapping is used to indicate that the IP data of different second communication nodes are sent through different relay air interface DRBs respectively; many-to-one mapping is used to indicate that the IP data of at least two second communication nodes are mapped to the same relay air interface DRB for sending.

[0044] In one embodiment, when a new radio interface direct link interface (NR PC5) is used to connect the first communication node and the second communication node, and the second communication node and the third communication node use an NR air interface, the many-to-one mapping includes one of the following methods:

[0045] Mapping the IP data of the second communication node to the relay air interface DRB according to the air interface QoS rules and DRB configuration of the first communication node;

[0046] Map the IP data to the relay air interface DRB based on the mapping relationship between the PC5 DRB and the air interface DRB configured or pre-configured by the third communication node;

[0047] Map the IP data to the relay air interface DRB based on the mapping relationship between the PC5 QoS flow and the NR air interface QoS flow configured or pre-configured by the third communication node and the configuration of the NR air interface DRB;

[0048] Based on the mapping relationship between the PC5 QoS flow and the air interface DRB configured or pre-configured by the third communication node, the IP data is mapped to the relay air interface DRB.

[0049] In one embodiment, when a new air interface direct link interface NR PC5 is used to connect the first communication node and the second communication node and the second communication node and the third communication node use an NR air interface, before receiving the IP data sent by the second communication node, the method further includes:

[0050] receiving a relay connection request from a second communication node and / or a unicast connection request from PC5;

[0051] An air interface DRB and a downlink PC5 DRB, as well as uplink and downlink data mapping, are established based on the configuration information fed back by the third communication node. In an embodiment, after receiving a relay connection request and / or a PC5 unicast connection request from the second communication node, and before establishing the air interface DRB and the downlink PC5 DRB based on the configuration information fed back by the third communication node, the QoS information in the relay connection request and the PC5 unicast connection request may be sent to the third communication node.

[0052] In one embodiment, when an NR PC5 connection is adopted between the first communication node and the second communication node, and an NR air interface is adopted between the second communication node and the third communication node, in the process of establishing a layer 2 link connection between the first communication node and the second communication node, a third preset mapping method is adopted to map the pre-acquired PC5 QoS information into air interface QoS information.

[0053] In one embodiment, the third preset mapping method includes:

[0054] Map the PQI in the PC5 QoS flow to the same air interface 5QI;

[0055] If the same air interface 5QI does not match the PQI, the 5QI value in the standard 5QI list that is closest to the QoS attribute represented by the PQI is selected;

[0056] The guaranteed flow bit rate (GFBR) value and the maximum flow bit rate (MFBR) value in the air interface QoS flow are set to the GFBR and MFBR values ​​in the PC5 QoS flow.

[0057] In one embodiment, after mapping the pre-acquired PC5 QoS information to air interface QoS information, the method further includes:

[0058] Sending a PDU session establishment request to the third communication node according to the air interface QoS flow, where the PDU session establishment request is used to forward the IP data of the second communication node;

[0059] Alternatively, a PDU session modification request is sent to the third communication node, where the PDU session modification request is used to modify the current PDU session and carries the mapped air interface QoS information.

[0060] In one embodiment, the communication method further includes: receiving a relay air interface DRB or PC5 DRB configured by the third communication node, and a mapping relationship between PC5 data and air interface data.

[0061] In one embodiment, when an NR PC5 connection is adopted between the first communication node and the second communication node, and the second communication node and the third communication node adopt an NR air interface, the mapping relationship between PC5 data and air interface data includes one of the following: mapping of PC5 QoS flow to air interface QoS flow, mapping of PC5 DRB to air interface DRB, mapping of PC5 QoS flow to air interface DRB, and mapping of PC5DRB to air interface QoS flow.

[0062] In one embodiment, when an NR PC5 connection is adopted between the first communication node and the second communication node, and an NR air interface is adopted between the second communication node and the third communication node, a time period during which the third communication node configures a mapping relationship between PC5 data and air interface data for the first communication node includes one of the following:

[0063] After the first communication node sends a PDU session establishment request or a PDU session modification request;

[0064] After the first communication node establishes a PC5 RRC connection with the second communication node, the first communication node reports PC5 DRB information, where the PC5 DRB information includes at least one of the following: a bearer identifier, a Radio Link Control (RLC) mode, a logical channel identifier, a logical channel priority, and RLC-related configuration;

[0065] After the first communication node sends the direct link UE information (SideLink UE information, SUI) to the third communication node.

[0066] In one embodiment, when an NR PC5 connection is adopted between the first communication node and the second communication node, and an NR air interface is adopted between the second communication node and the third communication node, the mapping relationship between the PC5 data and the air interface data includes one of the following:

[0067] NR PC5 QoS flow and NR air interface QoS flow mapping configuration, the mapping configuration including at least one of the following: mapping of PC5 QoS information to air interface QoS information, mapping of QFI to PC5 Flow Identifier (PFI); the mapping of PC5 QoS information to air interface QoS information including at least one of the following: mapping the 5QI in the air interface QoS flow to an identical PC5 PQI; if the identical air interface 5QI does not match the PQI, selecting the 5QI value in the standard 5QI list that is closest to the QoS attribute represented by the PQI; the GFBR and MFBR in the air interface QoS flow are directly set to the GFBR and MFBR in the PC5 QoS information;

[0068] Map the PQI in the PC5 QoS flow to the same air interface 5QI; if the same air interface 5QI does not match the PQI, select the PQI value in the standard PQI list that is closest to the QoS attribute represented by the 5QI; directly set the GFBR and MFBR in the PC5 QoS flow to the GFBR and MFBR in the Uu QoS Info;

[0069] NR PC5 QoS flow and NR air interface DRB mapping configuration, the mapping configuration includes at least one of the following: PC5 PFI and air interface DRB identifier mapping, PC5 PQI and air interface DRB priority mapping, PC5 PQI and air interface logical channel priority mapping;

[0070] NR PC5 DRB to NR air interface DRB mapping configuration, the mapping configuration including at least one of the following: PC5 DRB priority to air interface DRB priority mapping, PC5 DRB identifier to air interface DRB identifier mapping, PC5 logical channel priority to air interface logical channel priority mapping, PC5 logical channel identifier to air interface logical channel identifier mapping;

[0071] NR PC5 DRB to NR Uu QoS flow mapping configuration, the configuration includes at least one of the following: mapping of PC5 DRB identifier to UuQFI, mapping of PC5 DRB to priority and Uu 5QI, mapping of PC5 logical channel priority and Uu 5QI.

[0072] In one embodiment, when a long-term evolution LTE PC5 connection is adopted between the first communication node and the second communication node, and the second communication node and the third communication node adopt an NR air interface, the many-to-one mapping includes one of the following methods:

[0073] Map the IP data of the second communication node to the relay NR air interface DRB according to the air interface uplink QoS rules and DRB configuration of the first communication node;

[0074] Map the IP data to the relay NR air interface DRB based on the mapping relationship between the LTE PC5 logical first arrival and the NR air interface DRB configured or pre-configured by the third communication node;

[0075] Based on the received neighbor service packet priority (ProSe Per Packet Priority, PPPP) of the second communication node PC5 data, the mapping relationship between PPPP and 5QI configured or pre-configured by the third communication node, and the NR air interface DRB configuration, the IP data of the second communication node is mapped to the air interface QoS flow, and then mapped to the relay NR air interface DRB;

[0076] Based on the PPPP value of the received data of the second communication node PC5, and the mapping relationship between the PPPP value configured or pre-configured by the third communication node and the NR air interface DRB, the IP data of the second communication node is mapped to the relay NR air interface DRB.

[0077] In one embodiment, when an LTE PC5 connection is adopted between the first communication node and the second communication node, and an NR air interface is adopted between the second communication node and the third communication node, before receiving Internet Protocol IP data sent by the second communication node, the method further includes:

[0078] receiving a relay connection request from a second communication node and / or a unicast connection request from PC5;

[0079] Sending QoS information in the relay connection established by the relay connection request and the PC5 unicast connection established by the PC5 unicast connection request to the third communication node;

[0080] An air interface DRB is established based on the configuration information fed back by the third communication node, as well as mapping of uplink and downlink data. In an embodiment, after receiving a relay connection request and / or a PC5 unicast connection request from the second communication node, and before establishing an air interface DRB based on the configuration information fed back by the third communication node, QoS information in the relay connection established by the relay connection request and the PC5 unicast connection established by the PC5 unicast connection request may be sent to the third communication node.

[0081] In one embodiment, when an LTE PC5 connection is adopted between the first communication node and the second communication node, and an NR air interface is adopted between the second communication node and the third communication node, in the process of establishing a layer 2 link connection between the first communication node and the second communication node, a fourth preset mapping method is adopted to map the pre-acquired PPPP value into NR air interface QoS information.

[0082] In one embodiment, the fourth preset mapping method includes:

[0083] Based on the PPP-5QI mapping table configured or pre-configured by the third communication node.

[0084] In one embodiment, after mapping the pre-acquired PC5 PPPP value to the NR air interface QoS information, the method further includes:

[0085] Sending a PDU session establishment request to the third communication node according to the air interface QoS information, where the PDU session establishment request is used to forward the IP data of the second communication node;

[0086] Alternatively, a PDU session modification request is sent to the third communication node, where the PDU session modification request is used to modify the current PDU session and carries the air interface QoS information obtained after mapping.

[0087] In one embodiment, the communication method further includes: receiving a relay air interface DRB configured by the third communication node, and a mapping relationship between PC5 data and air interface data.

[0088] In one embodiment, when an LTE PC5 connection is adopted between the first communication node and the second communication node, and the second communication node and the third communication node adopt an NR air interface, the mapping relationship between PC5 data and air interface data includes one of the following: mapping of PC5 logical channel and air interface DRB, mapping of PC5 PPPP data flow and air interface DRB, and mapping of PC5 PPPP data flow and Uu QoS flow.

[0089] In one embodiment, when an LTE PC5 connection is adopted between the first communication node and the second communication node, and an NR air interface is adopted between the second communication node and the third communication node, a time period during which the third communication node configures a mapping relationship between PC5 data and air interface data for the first communication node includes one of the following:

[0090] After the first communication node sends a PDU session establishment request or a PDU session modification request;

[0091] After the first communication node establishes a relay connection with the second communication node, the first communication node reports LTE PC5 logical channel information, where the PC5 logical channel information includes at least one of the following: RLC mode, logical channel identifier, logical channel priority, and RLC-related configuration;

[0092] After the first communication node sends the SUI to the third communication node.

[0093] In one embodiment, when an LTE PC5 connection is adopted between the first communication node and the second communication node, and an NR air interface is adopted between the second communication node and the third communication node, the mapping relationship between the PC5 data and the air interface data includes one of the following:

[0094] Mapping configuration of LTE PC5 logical channels and NR air interface DRBs, the mapping configuration including at least one of the following: mapping of LTE PC5 logical channel identifiers and NR air interface DRB identifiers, mapping of LTE PC5 logical channel priorities and NR air interface DRB priorities, mapping of LTE PC5 logical channel priorities and NR air interface logical channel priorities, and mapping of LTE PC5 logical channel identifiers and NR air interface logical channel identifiers;

[0095] LTE PC5 PPPP flow and NR air interface DRB mapping configuration, the mapping configuration including at least one of the following: LTE PPPP value and air interface DRB priority mapping configuration, LTE PPPP value and air interface logical channel priority mapping;

[0096] Mapping configuration of LTE PC5 PPPP flow and NR air interface QoS flow, wherein the mapping configuration includes at least one of the following: Mapping configuration of LTE PPPP value and NR air interface QoS information

[0097] A mapping configuration of LTE PC5 PPPP value and NR air interface QoS information, the mapping configuration including at least one of the following: a mapping table of LTE PC5 PPPP value and NR air interface 5QI. In one embodiment, when an NR PC5 connection is adopted between the first communication node and the second communication node, and the second communication node and the third communication node adopt an LTE air interface, the many-to-one mapping includes one of the following methods:

[0098] Mapping IP data of at least two second communication nodes to an LTE air interface DRB according to an uplink traffic flow template (TFT) and DRB configuration of the first communication node;

[0099] Map the IP data to the LTE air interface DRB based on the mapping relationship between the NR PC5 DRB or the LTE air interface DRB configured or pre-configured by the third communication node;

[0100] Map the IP data to the LTE air interface DRB based on the mapping relationship between the NR PC5 QoS flow configured or pre-configured by the third communication node and the LTE air interface DRB;

[0101] Based on the mapping relationship between the NR PC5 QoS flow configured or pre-configured by the third communication node and the LTE air interface EPS bearer and the configuration of the LTE air interface DRB, the IP data should be set to the LTE air interface DRB.

[0102] In one embodiment, when an NR PC5 connection is adopted between the first communication node and the second communication node, and the second communication node and the third communication node adopt an LTE air interface, the fifth preset mapping method is adopted to map the pre-acquired NRPC5 QoS information into LTE air interface QoS information.

[0103] In one embodiment, the fifth preset mapping method includes:

[0104] Map the PQI in the NR PC5 QoS flow to the exact same LTE air interface 5QI;

[0105] In the case that the identical LTE air interface 5QI does not match the PQI, the QCI value in the standard LTE QCI list closest to the QoS attribute represented by the PQI is selected;

[0106] Set the GFBR and MFBR values ​​in the air interface QoS flow to the GFBR and MFBR values ​​in the PC5 QoS flow.

[0107] In one embodiment, after mapping the pre-acquired PC5 PPPP value to the NR air interface QoS information, the method further includes:

[0108] Sending a PDU session establishment request to the third communication node according to the air interface QoS information, where the PDU session establishment request is used to forward the IP data of the second communication node;

[0109] Alternatively, a PDU session modification request is sent to the third communication node, where the PDU session modification request is used to modify the current PDU session and carries the air interface QoS information obtained after mapping.

[0110] In one embodiment, the communication method further includes: receiving a relay air interface DRB configured by the third communication node, and a mapping relationship between PC5 data and air interface data.

[0111] In one embodiment, when an NR PC5 connection is adopted between the first communication node and the second communication node, and the second communication node and the third communication node adopt the LTE air interface, the mapping relationship between PC5 data and air interface data includes one of the following: NR PC5 QoS and LTE air interface EPS bearer mapping, NR PC5DRB and LTE air interface DRB mapping, NR PC5 QoS flow and LTE air interface DRB mapping, NR PC5DRB and LTE air interface PES bearer mapping.

[0112] In one embodiment, when an NR PC5 connection is adopted between the first communication node and the second communication node, and the second communication node and the third communication node adopt an LTE air interface, the time period during which the third communication node configures a mapping relationship between PC5 data and air interface data for the first communication node includes one of the following:

[0113] After the first communication node sends a PDU session connection request or a bearer resource modification request;

[0114] After the first communication node establishes a PC5 radio resource control RRC connection with the second communication node, the first communication node reports NR PC5 DRB information, where the NR PC5 DRB information includes at least one of the following: a bearer identifier, an RLC mode, a logical channel identifier, a logical channel priority, and an RLC-related configuration;

[0115] After the first communication node sends the SUI to the third communication node.

[0116] In one embodiment, when an NR PC5 connection is adopted between the first communication node and the second communication node, and the second communication node and the third communication node adopt an LTE air interface, the mapping relationship between PC5 data and air interface data includes one of the following:

[0117] The mapping configuration of the NR PC5 QoS flow to the LTE air interface EPS bearer includes at least one of the following: a mapping between the PC5QFI and the air interface EPS bearer identifier, and a mapping between the NR PC5 QoS Info and the LTE air interface QoS Info; the mapping between the PC5 QoS Info and the air interface QoS Info includes at least one of the following:

[0118] Map the QCI of the air interface QoS flow to the same PC5 PQI;

[0119] In the case where the identical air interface QCI does not match the PQI, selecting the QCI value in the standard QCI list that is closest to the QoS attribute represented by the PQI;

[0120] The GFBR and MFBR in the air interface QoS flow are directly set to the GFBR and MFBR in the PC5 QoS Info.

[0121] Map the PQI in the PC5 QoS flow to the same air interface QCI;

[0122] If the completely identical air interface QCI does not match the PQI, select the PQI value in the standard PQI list that is closest to the QoS attribute represented by the QCI;

[0123] The GFBR and MFBR in the PC5 QoS flow are directly set to the GFBR and MFBR in the Uu QoS Info;

[0124] NR PC5 QoS flow and LTE air interface DRB mapping configuration, the mapping configuration includes at least one of the following: PC5 PFI and air interface DRB identifier mapping, PC5 PQI and air interface DRB priority mapping, PC5 PQI and air interface logical channel priority mapping;

[0125] The mapping configuration of NR PC5 DRB and LTE air interface DRB, the mapping configuration includes at least one of the following: mapping of PC5 DRB priority and air interface DRB priority, mapping of PC5 DRB identifier and air interface DRB identifier, mapping of PC5 logical channel priority and air interface logical channel priority, mapping of NR PC5 logical channel identifier and LTE air interface logical channel identifier.

[0126] The mapping configuration of NR PC5 DRB and LTE air interface EPS bearer includes at least one of the following: mapping of PC5 DRB priority and air interface EPS bearer QCI, mapping of PC5 DRB identifier and air interface EPS bearer identifier, and mapping of PC5 logical channel and air interface EPS bearer QCI.

[0127] In one embodiment, when the air interface link quality or relay link quality of the second communication node fails, the switching method of the second communication node includes one of the following: switching from an air interface connection to a relay connection; switching from a relay connection to an air interface connection; switching from a first first communication node connection to a second first communication node connection.

[0128] In one embodiment, when the switching mode of the second communication node is switching from an air interface connection to a relay connection, uplink data buffered in the second communication node waiting for transmission includes one of the following connection modes:

[0129] Directly switch the unprocessed IP data in the second communication node to the relay link for transmission;

[0130] For the IP data mapped to the air interface QoS flow in the second communication node, based on the mapping configuration of the air interface QoS flow to the PC5 QoS flow configured or pre-configured by the third communication node, the air interface QoS flow is mapped to the PC5 QoS flow, or, based on the mapping configuration of the air interface QoS flow to the PC5 DRB configured or pre-configured by the third communication node, the air interface QoS flow is mapped to the PC5 DRB;

[0131] For the IP data mapped to the air interface DRB in the second communication node, the IP data is decrypted according to the air interface PDCP, and based on the mapping configuration of the air interface DRB to PC5 DRB configured or pre-configured by the third communication node, the air interface DRB is mapped to PC5 DRB.

[0132] In one embodiment, when the switching mode of the second communication node is switching from a relay connection to an air interface connection, uplink data buffered in the second communication node waiting for transmission includes one of the following connection modes:

[0133] Directly switch the unprocessed IP data in the second communication node to the air interface link for transmission;

[0134] For the IP data mapped to the PC5 QoS flow in the second communication node, based on the mapping configuration of the air interface QoS flow to the PC5 QoS flow configured or pre-configured by the third communication node, the PC5 QoS flow is mapped to the air interface QoS flow, or based on the mapping configuration of the PC5 QoS flow to the air interface DRB configured or pre-configured by the third communication node, the PC5 QoS flow is mapped to the air interface DRB;

[0135] For the IP data mapped to the PC5 DRB in the second communication node, the IP data is decrypted according to the PC5 PDCP, and based on the mapping configuration of the PC5 DRB to the air interface DRB configured or pre-configured by the third communication node, the PC5 DRB is mapped to the air interface DRB.

[0136] In one embodiment, when the switching mode of the second communication node is switching from the first first communication node to the second first communication node, uplink data buffered in the second communication node waiting for transmission includes one of the following connection modes:

[0137] forwarding the IP data and PC5 QoS flow data sent by the second communication node to the first first communication node to the second first communication node;

[0138] For the IP data mapped to the PC5 DRB established with the first first communication node, decrypt the IP data according to the PDCP layer established with the second first communication node, and map the IP data to the PC5 DRB with the same logical channel priority established with the second first communication node;

[0139] For the IP data that has been buffered in the first first communication node, the first first communication node continues to complete the uplink transmission.

[0140] In one embodiment, when the air interface link quality or relay link quality of the second communication node fails, the link switching decision includes one of the following:

[0141] configuring a link switching criterion or a measurement configuration through a third communication node;

[0142] The link switching criterion is configured or preconfigured by the third communication node.

[0143] In one embodiment, when the switching mode of the second communication node is switching from an air interface connection to a relay connection, the link switching criterion includes at least one of the following:

[0144] Air interface link quality threshold; service type; PC5 interface link quality threshold;

[0145] Measurement configuration, including air interface measurement configuration and relay measurement configuration.

[0146] In one embodiment, when the switching mode of the second communication node is switching from a relay connection to an air interface connection, the link switching criterion includes at least one of the following:

[0147] Air interface link quality threshold; PC5 interface link quality threshold; first communication node air interface link quality threshold; PC5 interface resource pool CBR threshold; service type / service requirements.

[0148] Figure 2 This is a flow chart of another communication method provided by an embodiment of the present application. This embodiment is applied to the second communication node and is used for transmission of downlink data. Figure 2 As shown, this embodiment includes S201-S203.

[0149] S201, receiving downlink data sent by the third communication node.

[0150] S202: Determine the second communication node to which the downlink data belongs according to the IP address in the downlink data.

[0151] S203: Map the downlink data into PC5 data according to a second preset mapping method, and transmit the data to the second communication node to which it belongs.

[0152] In one embodiment, when an NR PC5 connection is adopted between the first communication node and the second communication node, and the second communication node and the third communication node adopt an NR air interface, the second preset mapping mode includes one of the following:

[0153] Mapping the downlink data to a corresponding PC5 DRB according to the QoS rule derived by the first communication node itself and the PC5 DRB configuration configured by the third communication node;

[0154] In the case of bidirectional PC5 DRB, reverse mapping is performed based on the mapping relationship between uplink PC5 DRB and air interface DRB;

[0155] Based on the mapping relationship between the NR Uu QoS flow and the PC5 QoS flow configured by the third communication node and the PC5 DRB configuration, the air interface QoS flow is mapped to the PC5 QoS flow, and then mapped to the PC5 DRB;

[0156] Map the downlink data to the PC5 DRB based on the mapping relationship between the NR Uu QoS flow and the PC5 DRB configured or pre-configured by the third communication node;

[0157] Based on the mapping relationship between the air interface DRB configured or pre-configured by the third communication node and the PC5 DRB, the downlink data is mapped to the PC5 DRB.

[0158] In one embodiment, when an LTE PC5 connection is adopted between the first communication node and the second communication node, and an NR air interface is adopted between the second communication node and the third communication node, the second preset mapping mode includes one of the following:

[0159] Mapping the IP data of the second communication node to the LTE PC5 logical channel based on the mapping relationship between the NR air interface DRB and the LTE PC5 logical channel configured or pre-configured by the third communication node;

[0160] Mapping the IP data of the second communication node to the LTE PC5 logical channel based on the mapping relationship between the NR air interface DRB configured or pre-configured by the third communication node and the LTE PC5 PPPP value;

[0161] Based on the mapping relationship between the NR air interface QoS flow configured or pre-configured by the third communication node and the LTE PC5PPPP data flow, the IP data of the second communication node should be set to the LTE PC5 logical channel.

[0162] In one embodiment, when an NR PC5 connection is adopted between the first communication node and the second communication node, and the second communication node and the third communication node adopt an LTE air interface, the second preset mapping mode includes one of the following:

[0163] Mapping the downlink data to the corresponding NR PC5 DRB according to the QoS rules derived by the first communication node itself and the PC5 DRB configuration configured by the third communication node;

[0164] Map the IP data to the NR PC5 DRB based on the mapping relationship between the LTE air interface DRB and the NR PC5 DRB configured or pre-configured by the third communication node;

[0165] Map the IP data to the NR PC5 DRB based on the mapping relationship between the LTE air interface DRB and the NR PC5 QoS flow configured or pre-configured by the third communication node;

[0166] Based on the mapping relationship between the LTE air interface EPS bearer and the NR PC5QoS flow configured or pre-configured by the third communication node and the configuration of the LTE air interface DRB, the IP data should be set to the LTE air interface DRB.

[0167] It should be noted here that, in the present application, the uplink transmission, uplink, uplink data, etc. involved between the first communication node refer to the process of sending by the second communication node and receiving by the first communication node; correspondingly, the downlink transmission, downlink, downlink data, etc. involved between the first communication node and the second communication node refer to the process of sending by the first communication node and receiving by the second communication node.

[0168] In one implementation, for a L3 UE-to-Network relay data scenario, NR PC5 is used between a first communication node and a second communication node, and NR air interface (Uu) is used between the first communication node and a third communication node. For example, the first communication node is a relay UE, the second communication node is a remote UE, and the third communication node is a base station.

[0169] For L3 UE-to-Network Relay, no RRC connection is established between the remote UE and the base station. That is, the base station does not identify the remote UE and does not save the remote UE context. The core network does not identify the remote UE and does not establish or maintain a PDU session for the remote UE. The remote UE's IP data packets are sent to the relay UE via a PC5 unicast connection. The relay UE sends the remote UE's IP data packets to the base station via the relay UE's own air interface bearer. The base station then transmits the data to the 5G core network (5GC) via the relay UE's PDU session.

[0170] For L3 UE-to-Network relay, the remote UE does not establish a connection with the base station. Therefore, the relay UE does not need to perform control plane data forwarding. The SideLink control plane protocol stack is used between the relay UE and the remote UE, and the NR air interface protocol stack is used between the relay UE and the base station. Figure 3 This is a schematic diagram showing a user plane protocol stack provided by an embodiment of the present application. Figure 3As shown, the user plane protocol stack is the user plane protocol stack of L3UE-to-Network relay.

[0171] In the case of uplink user plane data routing, steps 1 to 4 are included:

[0172] Step 1: The Remote UE receives the IP data packet from the application layer and transmits the IP data packet to the relay UE through self-derived QoS processing rules and PC5 unicast bearer configuration.

[0173] In order for the relayUE to distinguish whether the data packet received is destined for the relayUE itself or needs to be forwarded, the following methods can be used to determine:

[0174] Method 1: The remote UE and the relay UE establish a PC5 unicast bearer or logical channel through RRC signaling negotiation, and use it specifically to forward the remote UE's data. Optionally, it can be defined by a PC5 DRB identifier or LCID.

[0175] In the second method, the data sent by the Remote UE to the gNB and the data sent to the relay UE use different SRCIDs (source IDs) and DST IDs (destination IDs). The relay UE uses the ID contained in the Media Access Control (MAC) subheader to distinguish whether the data is sent to itself or needs to be relayed.

[0176] Step 2: The relay UE receives the IP data packet sent by the remote UE and parses it. It determines whether the IP data packet needs to be relayed to the gNB based on the ID in the MAC subheader or the negotiated logical channel / bearer. If the data needs to be relayed, the relay UE reads the IP information of the remote UE data packet, uses the Network Address Translation (NAT) function to modify the IP header of the corresponding remote UE data packet, and forwards it.

[0177] Step 3: The Relay UE maps the IP data packet to be forwarded to the relay air interface bearer between the UE and the base station and transmits it to the base station. Exemplarily, one of the following mapping methods is included:

[0178] In mapping mode 1, the relay UE establishes an independent PDU session for the data to be relayed and transmits the remote UE's data on the DRB corresponding to the PDU session.

[0179] In mapping mode 2, the Relay UE uses its own PDU session to transmit the remote UE's data.

[0180] Based on the above two mapping methods, when multiple remote UEs are connected to the same relay UE, the relay UE can choose the following two mapping methods:

[0181] Mapping mode 1: One-to-one mapping, that is, the IP data of different remote UEs are sent through different air interface DRBs;

[0182] Mapping mode 2: many-to-one mapping, that is, IP data packets with similar QoS of multiple remote UEs can be mapped to the same Uu DRB for transmission.

[0183] For many-to-one mapping, one of the following methods is used:

[0184] In method 1, the relay UE does not distinguish the remote UEs from which the IP data packets come, and maps the IP data packets of multiple remote UEs to the Uu DRB according to the Uu QoS rules and DRB configuration of the relay UE;

[0185] Mode 2: The relay UE maps the forwarded IP data to the UuDRB based on the mapping relationship between the PC5 DRB and the Uu DRB configured or pre-configured by the base station (for example, mapping based on the bearer identifier or mapping based on the bearer / logical channel priority);

[0186] Mode 3: The relay UE maps the logical channel or bearer priority of the PC5 DRB to the relay Uu DRB with the same logical channel priority;

[0187] Mode 4: Relay UE maps PC5 QoS flow data packets to Uu QoS flow based on the PQI of the received remote UE PC5 data and the mapping relationship between PQI and 5QI configured or pre-configured by the base station, and further transmits the IP data to the base station through the corresponding relay Uu DRB according to the Uu DRB configuration.

[0188] Step 4: The base station receives the remote UE user plane data forwarded by the relay UE, and further maps the data packet to the NG interface transmission tunnel of the relay UE's PDU session and sends it to the core network element (UPF).

[0189] In the case of downlink user plane data routing, steps 1 to 3 are included:

[0190] In Layer 3-based data communication, the base station and core network process and forward remote UE data as relay UE data. The base station receives downlink data sent by the user plane function (UPF) to the relay UE and maps the relay UE's downlink data to the relay UE's air interface bearer. The relay UE determines the remote UE to which the data packet belongs based on the IP information and NAT in the data packet sent to it. It then forwards the downlink data to the corresponding remote UE using the PC5 DRB.

[0191] Step 1: The relay UE receives the downlink data sent by the base station, reads the IP information in the downlink data, determines which remote UE the data packet belongs to based on the stored NAT information, and then replaces the IP header in the data packet with the IP information of the corresponding remote UE.

[0192] Step 2: The relay UE maps the data packet to the PC5 bearer and sends it to the remote UE. This includes one of the following mapping methods:

[0193] Mapping method 1: The relay UE maps the remote UE's data to the corresponding PC5 DRB according to its own derived QoS rules and the PC5 DRB configuration configured by the base station;

[0194] Mapping method 2: Based on the mapping relationship from 5QI to PQI configured by the base station and the PC5 DRB configuration, the Uu QoS flow is mapped to the PC5 QoS flow and then mapped to the PC5 DRB;

[0195] Mapping mode three: Relay UE maps remote UE data packets to PC5 DRBs based on the mapping relationship between 5QI / QFI and PC5 DRB priorities configured or pre-configured by the base station;

[0196] Mapping mode 4: If the PC5 DRB is a bidirectional bearer, reverse mapping can be performed based on the mapping relationship between the uplink PC5 DRB and the Uu DRB;

[0197] Mapping mode 5: Based on the mapping relationship between the base station configured or pre-configured air interface DRB and PC5 DRB (for example, bearer identifier mapping, or bearer / logical channel priority mapping), the data packet is mapped to the PC5 DRB;

[0198] Mapping mode six: Based on the base station configured or pre-configured Uu DRB bearer priority or logical channel priority, the remote UE data packet is mapped to the PC5 DRB with the same bearer / logical channel priority.

[0199] Step 3: The Remote UE receives downlink data from the PC5 DRB.

[0200] In one implementation, for the L3 UE-to-Network relay data scenario, NR PC5 is used between the first communication node and the second communication node, and NR Uu is used between the first communication node and the third communication node. For example, the first communication node is a relay UE, the second communication node is a remote UE, and the third communication node is a base station. In the embodiment, during the transmission of uplink data and downlink data, the configurations performed by the base station are as follows: Figure 4 steps.

[0201] For Layer-3-based UE-to-network relay, the remote UE does not need to establish an RRC connection with the gNB or a PDU session with the core network. The remote UE first searches for a suitable relay UE to relay and forward its IP data. A remote UE in the RRC connected state then establishes an uplink SL bearer based on the base station's configuration. A remote UE in the RRC idle / inactive state establishes an uplink SL bearer based on the SL bearer configuration in the system message. A UE without coverage establishes an uplink SL bearer based on the SL bearer configuration in the pre-configured information. After receiving the remote UE's relay request and PC5 unicast connection request, the relay UE reports the QoS-related information in the relay request and PC5 unicast connection request to the base station, establishes an air interface DRB and a downlink PC5 DRB based on the configuration information sent by the base station, and forwards the remote UE's data packets based on the mapping relationship configured by the base station.

[0202] Figure 4 This is a schematic diagram of the process of establishing an air interface data forwarding bearer when a relay UE forwards data to a remote UE according to an embodiment of the present application. Figure 4 As shown, the forwarding bearer establishment process in this embodiment includes S210-S2140.

[0203] S210: IP data packet arrives.

[0204] S220: Derives QoS information by itself.

[0205] S230, relay discovery.

[0206] S240: L2 link establishment process.

[0207] S250: PDU session establishment request, or PDU session modification request.

[0208] S260: N2 PDU session establishment request.

[0209] S270, RRC reconfiguration.

[0210] S280, SL RRC reconfiguration.

[0211] S290: Report PC5 bearer information.

[0212] S2100, RRC reconfiguration.

[0213] S2110, DL data.

[0214] S2120: Derives QoS information by itself.

[0215] S2130, SUI: QoS Profile.

[0216] S2140, RRC reconfiguration.

[0217] In an embodiment, the remote UE establishes an L2 link connection with the relay UE through high-layer signaling. The relay UE then maps the PC5 QoS flow (e.g., PQI, MFBR, and GFBR) obtained during the L2 link establishment process to a Uu QoS flow. Exemplarily, the mapping method for mapping the PC5 QoS flow to the Uu QoS flow includes:

[0218] The PQI in the PC5 QoS flow is mapped to an identical Uu 5QI. If no identical Uu 5QI matches the PQI, the 5QI value in the standard 5QI list that is closest to the QoS attribute represented by the PQI is selected. The GFBR and MFBR values ​​in the Uu QoS flow are directly set to the GFBR and MFBR values ​​in the PC5 QoS info.

[0219] The relay UE chooses to send a PDU session establishment request (PDU session establishment request) based on the mapped Uu QoS flow to establish a new PDU session for the remote UE, which is dedicated to forwarding the remote UE's data packets, or send a PDU session modification request (PDU session modification request) to modify the existing PDU session, which contains the mapped Uu QoS flow. The core network configures the corresponding PDU session based on the QoS in the PDU session establishment request or PDU session modification request, and notifies the base station of the configuration result. The base station configures the corresponding relay UE air interface DRB or PC5 DRB used by the relay UE to forward the remote UE's downlink data based on the PDU session configuration result, as well as the mapping relationship between PC5 data and air interface data when the relay UE forwards the remote UE's uplink and downlink data (for example, PC5 QoS flow to Uu QoS flow mapping, PC5 DRB to Uu DRB mapping).

[0220] The base station may configure the mapping relationship between PC5 data and air interface data for the relay UE at the following time points:

[0221] At time point 1, after the Relay UE sends a PDU session establishment request or a PDU session modification request, Figure 4 S250, S260 and S270.

[0222] At time point 2, after the relay UE establishes a PC5 RRC connection with the remote UE, the relay UE reports the PC5 DRB information. The PC5 DRB information includes at least one of the following: bearer identifier, RLC mode, logical channel identifier, logical channel priority, and RLC-related configurations, such as Figure 4 S280, S290 and S2100.

[0223] At time point three, after the Relay UE sends the SUI to the base station, Figure 4 S2110, S2120, S2130 and S2140 in it.

[0224] The base station configures an air interface data forwarding bearer (relay DRB) for the relay UE. The air interface data forwarding bearer configuration includes at least one of the following: data forwarding bearer indication, bearer identifier, RLC mode, logical channel identifier, logical channel group identifier, logical channel priority, priority guaranteed bit rate, bucket size duration, and RLC related configuration.

[0225] The base station configures PC5 DRB for the relay UE. PC5 DRB is the downlink PC5 DRB (sent by the relay UE and received by the remote UE). The configuration information includes the relevant parameters required for SLRB transmission; RLC AM mode or UM mode, and other RLC and logical channel related configuration information.

[0226] In an embodiment, the base station configures a mapping relationship between PC5 data and air interface data when the relay UE forwards uplink and downlink data of the remote UE. The mapping relationship includes one of the following:

[0227] Mapping relationship 1, mapping configuration of NR PC5 QoS flow and NR Uu QoS flow, the configuration includes at least one of the following: mapping of PC5 QoS info and Uu QoS info, mapping of QFI and PFI.

[0228] Mapping relationship 2, mapping configuration of NR PC5 QoS flow and NR Uu DRB, the configuration includes at least one of the following: mapping of PC5 PFI and Uu DRB identification, mapping of PC55QI and Uu DRB priority, mapping of PC55QI and Uu logical channel priority.

[0229] Mapping relationship three, mapping configuration of NR PC5 DRB and NR Uu DRB, the configuration includes at least one of the following: mapping of PC5 DRB priority and Uu DRB priority, mapping of PC5 DRB label and Uu DRB label, mapping of PC5 logical channel priority and Uu logical channel priority.

[0230] The base station sends the above configuration information to the relay UE through an RRC reconfiguration message.

[0231] In one implementation, for a L3 UE-to-Network relay data scenario, LTE PC5 is used between a first communication node and a second communication node, and NR air interface (Uu) is used between the first communication node and a third communication node. For example, the first communication node is a relay UE, the second communication node is a remote UE, and the third communication node is a base station.

[0232] In the embodiment, this embodiment is similar to the above-described embodiment in which NRPC5 is used between the first communication node and the second communication node, and NR air interface is used between the first communication node and the third communication node. The difference is that the remote UE and the relay UE use LTE sidelink connection, and the relay UE and the base station use NR air interface connection.

[0233] Figure 5 This is a schematic diagram showing another user plane protocol stack provided by an embodiment of the present application. Figure 5 As shown, the user plane protocol stack is a user plane protocol stack of L3 UE-to-Network relay.

[0234] In the case of uplink user plane data routing, steps 1 to 4 are included:

[0235] Step 1: The Remote UE receives an IP data packet from the application layer and transmits the IP data packet to the corresponding LTE PC5 logical channel based on the ProSe Per Packet Priority (PPPP) value provided by the upper layer.

[0236] In order for the relay UE to distinguish whether the data packet received is destined for the relay UE itself or needs to be forwarded, the following methods can be used to determine:

[0237] In the first method, the remote UE and the relay UE negotiate through the upper layer which logical channels are dedicated to forwarding the remote UE's data. Optionally, the data can be defined in the form of LCID.

[0238] In the second method, the data sent by the Remote UE to the gNB and the data sent to the relay UE use different SRC and DST IDs. The relay UE uses the ID contained in the MAC subheader to distinguish whether the data is sent to itself or needs to be relayed.

[0239] Step 2: The relay UE receives the IP data packet sent by the remote UE and parses it. It determines whether the IP data packet needs to be relayed to the gNB based on the ID in the MAC subheader or the negotiated logical channel. If the data packet needs to be relayed, the relay UE reads the IP information of the remote UE data packet, uses the NAT function to modify the IP header of the corresponding remote UE data packet, and forwards it.

[0240] Step 3: The Relay UE maps the IP data packet to be forwarded to the relay air interface bearer between the UE and the base station and transmits it to the base station. Exemplarily, one of the following mapping methods is included:

[0241] In mapping mode 1, the relay UE establishes an independent PDU session for the data to be relayed and transmits the remote UE's data on the DRB corresponding to the PDU session.

[0242] In mapping mode 2, the Relay UE uses its own PDU session to transmit the remote UE's data.

[0243] Based on the above two mapping methods, when multiple remote UEs are connected to the same relay UE, the relay UE can choose the following two mapping methods:

[0244] Mapping mode 1: One-to-one mapping, that is, the data of different remote UEs are sent through different Uu DRBs;

[0245] Mapping mode 2: many-to-one mapping, that is, similar PPPP data packets of multiple remote UEs can be mapped to the same UuDRB for transmission.

[0246] For many-to-one mapping, one of the following methods is used:

[0247] In method 1, the relay UE does not distinguish the remote UE from which the IP data packets come. According to the Uu UL QoS rules and DRB configuration of the relay UE, the IP data packets of multiple remote UEs are mapped to the relayNR Uu DRB.

[0248] Method 2: The relay UE maps the forwarded data to the relay NR Uu DRB based on the mapping relationship between the base station configured or pre-configured LTE PC5 logical channel and the NR Uu DRB (for example, the mapping of logical channel priority).

[0249] Method 3: The relay UE maps the logical channel of LTE PC5 to the relayNR Uu DRB with the same logical channel priority.

[0250] Method 4: Relay UE maps LTE PC5 data packets to Uu QoS flow based on the PPPP value of the received remote UE PC5 data and the mapping relationship between the base station configured or pre-configured PPPP value and 5QI, and further transmits the IP data to the base station through the corresponding relayNR Uu DRB according to the Uu DRB configuration.

[0251] Method 5: Realy UE maps the LTE PC5 data packet to the relay NR Uu DRB and transmits it to the base station based on the PPPP value of the received remote UE PC5 data and the mapping relationship between the base station configured or pre-configured PPPP value and the NR Uu DRB.

[0252] Step 4: The base station receives the remote UE user plane data forwarded by the relay UE, and further maps the data packet to the NG interface transmission tunnel of the relay UE's PDU session and sends it to the user plane function (UPF) in the core network element.

[0253] In the case of downlink user plane data routing, steps 1 to 3 are included:

[0254] Step 1: The relay UE receives the downlink data sent by the base station, reads the IP information in the downlink data, determines which remote UE the data packet belongs to based on the stored NAT information, and then replaces the IP header in the data packet with the IP information of the corresponding remote UE.

[0255] Step 2: The relay UE maps the data packet to the PC5 bearer and sends it to the remote UE. This includes one of the following mapping methods:

[0256] Mapping method 1: The Relay UE maps the NR Uu data stream to a PC5 PPPP data stream based on the 5QI to PPPP mapping relationship configured by the base station, and then maps it to the LTE PC5 logical channel;

[0257] Mapping method 2: The relay UE maps the remote UE data packet to the LTE PC5 logical channel based on the mapping relationship between the base station configured or pre-configured 5QI / QFI and the priority of the PC5 logical channel;

[0258] Mapping mode 3: The Relay UE maps the data packet to the LTE PC5 logical channel based on the base station configuration or pre-configured mapping relationship between the NR Uu DRB and the LTE PC5 logical channel (for example, bearer / logical channel priority mapping);

[0259] Mapping method four: Relay UE maps the remote UE data packet to the LTE PC5 logical channel with the same logical channel priority based on the NR Uu DRB bearer priority or logical channel priority configured or pre-configured by the base station.

[0260] Step 3: The Remote UE receives downlink data from the PC5 logical channel.

[0261] In one implementation, for the scenario of L3 UE-to-Network relay data, LTE PC5 is used between the first communication node and the second communication node, and NR Uu is used between the first communication node and the third communication node. For example, the first communication node is a relay UE, the second communication node is a remote UE, and the third communication node is a base station. In the embodiment, during the transmission of uplink data and downlink data, the configurations performed by the base station are as follows: Figure 6 steps.

[0262] Figure 6 1 is a schematic diagram of another embodiment of the present application, when a relay UE forwards data to a remote UE, to establish an air interface data forwarding bearer. Figure 6 As shown, the forwarding bearer establishment process in this embodiment includes S310-S3140.

[0263] S310, relay discovery.

[0264] S320: L2 link establishment process.

[0265] S330: PDU session establishment request, or PDU session modification request.

[0266] S340: N2 PDU session establishment request.

[0267] S350, RRC reconfiguration.

[0268] S360: Derives QoS information by itself.

[0269] S370: Report LTE PC5 receiving logical channel information.

[0270] S380, RRC reconfiguration.

[0271] S390, DL data.

[0272] S3100, SUI: QoS Profile.

[0273] S3110, RRC reconfiguration.

[0274] In the embodiment, the remote UE establishes an L2 link connection with the relay UE through high-layer signaling. Afterwards, the relay UE maps the PPPP to Uu QoS info, and the mapping method is based on the PPPP-5QI mapping table configured or pre-configured by the base station.

[0275] The relay UE chooses to send a PDU session establishment request based on the mapped Uu QoS flow to establish a new PDU session for the remote UE, which is dedicated to forwarding the remote UE's data packets, or send a PDU session modification request to modify the existing PDU session, which contains the mapped Uu QoS flow. The core network configures the corresponding PDU session based on the QoS information in the PDU session establishment request or PDU session modification request, and notifies the base station of the configuration result. The base station configures the corresponding relay UE NR Uu DRB and the mapping relationship between the PC5 data and air interface data of the remote UE downlink data forwarded by the relay UE based on the PDU session configuration result (for example, LTE PC5 PPPP-NR DRB priority mapping, LTE PC5 PPPP-NR 5QI mapping, LTE PC5 PPPP-NR logical channel priority mapping).

[0276] The base station may configure the mapping relationship between PC5 data and air interface data for the relay UE at the following time points:

[0277] At time point 1, after the Relay UE sends a PDU session establishment request or a PDU session modification request, Figure 6 S330, S340 and S350.

[0278] At time point 2, after the relay UE establishes a relay connection with the remote UE, the relay UE reports the LTE PC5 logical channel information. The PC5 logical channel information includes at least one of the following: RLC mode, logical channel identifier, logical channel priority, and RLC related configuration, such as Figure 6 S360, S370 and S380.

[0279] At time point three, after the Relay UE sends the SUI to the base station, Figure 6 S390, S3100 and S3110 in it.

[0280] The relay UE configures the LTE PC5 logical channel based on the system broadcast or pre-configured information: data forwarding bearer indication, bearer identifier, RLC mode, logical channel identifier, logical channel group identifier, logical channel priority, priority guaranteed bit rate, bucket size duration, and RLC-related configuration.

[0281] Optionally, the base station configures a mapping relationship between PC5 data and air interface data for forwarding downlink data of the remote UE by the relay UE. The mapping relationship includes one of the following:

[0282] Mapping relationship 1: Mapping of LTE PC5 PPPP and NR Uu 5QI.

[0283] Mapping relationship 2, mapping configuration of LTE PC5 PPPP and NR Uu DRB, the configuration includes at least one of the following: mapping of PC5PPPP and Uu DRB identifier, mapping of PC5 PPPP and Uu DRB priority, mapping of PC5 PPPP and Uu logical channel priority.

[0284] Mapping relationship three, mapping configuration of LTE PC5 logical channel and NR Uu DRB, the configuration includes at least one of the following: mapping of PC5 logical channel priority and Uu logical channel priority, mapping of PC5 logical channel ID and Uu logical channel ID.

[0285] The base station sends the above configuration information to the relay UE via an RRC reconfiguration message.

[0286] In one implementation, for a L3 UE-to-Network relay data scenario, NRPC5 is used between a first communication node and a second communication node, and an LTE air interface (Uu) is used between the first communication node and a third communication node. For example, the first communication node is a relay UE, the second communication node is a remote UE, and the third communication node is a base station.

[0287] Figure 7 This is another schematic diagram showing a user plane protocol stack provided by an embodiment of the present application. Figure 7 As shown, the user plane protocol stack is a user plane protocol stack of L3 UE-to-Network relay.

[0288] In the case of uplink user plane data routing, steps 1 to 4 are included:

[0289] Step 1: The Remote UE receives the IP data packet from the application layer and transmits the IP data packet to the relay UE through self-derived QoS processing rules and PC5 unicast bearer configuration.

[0290] In order for the relayUE to distinguish whether the data packet received is destined for the relayUE itself or needs to be forwarded, the following methods can be used to determine:

[0291] Method 1: Remote UE and relay UE negotiate through RRC signaling to establish an NRPC5 unicast bearer or the data in the logical channel is dedicated to forwarding the remote UE's data. Optionally, it can be defined by NR PC5 DRB identifier or LCID.

[0292] In the second method, the data sent by the Remote UE to the gNB and the data sent to the relay UE use different SRC and DST IDs. The relay UE uses the ID contained in the MAC subheader to distinguish whether the data is sent to itself or needs to be relayed.

[0293] Step 2: The relay UE receives the IP data packet sent by the remote UE and parses it. It determines whether the IP data packet needs to be relayed to the gNB based on the ID in the MAC subheader or the negotiated logical channel or bearer. If the data needs to be relayed, the relay UE reads the IP information of the remote UE data packet, uses the NAT function to modify the IP header of the corresponding remote UE data packet, and forwards it.

[0294] Step 3: The RelayUE maps the data packet to be forwarded to the relay air interface bearer between the UE and the base station and transmits it to the base station. Exemplarily, one of the following mapping methods is included:

[0295] In mapping mode 1, the relay UE establishes an independent PDU session for the data to be relayed and transmits the remote UE's data on the DRB corresponding to the PDU session.

[0296] In mapping mode 2, the RelayUE uses its own PDU session to transmit the remote UE's data.

[0297] Based on the above two mapping methods, if multiple remote UEs are connected to the same relay UE, the relay UE can choose the following two mapping methods:

[0298] Mapping mode 1: One-to-one mapping, that is, the data of different remote UEs are sent through different Uu DRBs;

[0299] Mapping mode 2: many-to-one mapping, that is, data packets with similar QoS of multiple remote UEs can be mapped to the same UuDRB for transmission.

[0300] For many-to-one mapping, one of the following methods is used:

[0301] In method 1, the relay UE does not distinguish the remote UEs from which the IP data packets come. It maps the IP data packets of multiple remote UEs to Uu DRBs according to the uplink TFT and DRB configuration of the relay UE.

[0302] In the second method, the relay UE maps the forwarded data to the LTE Uu DRB based on the mapping relationship between the NR PC5 DRB and the LTE Uu DRB configured or pre-configured by the base station (for example, mapping based on bearer identity or mapping based on bearer / logical channel priority);

[0303] Method 3: The relay UE maps the logical channel or bearer priority of the LTE PC5 DRB to the relayNR Uu DRB with the same logical channel priority;

[0304] Method 4: The Relay UE maps the PC5 QoS flow data packet to the Uu QoS flow based on the PQI of the received remote UE NR PC5 data and the mapping relationship between the base station configuration or pre-configured NR PC5 PQI and LTE Uu QCI, and further transmits the data to the base station through the corresponding relay LTE Uu DRB according to the Uu DRB configuration.

[0305] Step 4: The base station receives the remote UE user plane data forwarded by the relay UE, further maps the data packet to the relay UE's PDU session and forwards it to the PDN gateway (PGW) in the core network element.

[0306] In the case of downlink user plane data routing, steps 1 to 3 are included:

[0307] In Layer 3-based data communication, the base station and core network process and forward remote UE data as relay UE data. The base station receives downlink data sent to the relay UE and maps the downlink relay UE data to the relay UE Uu bearer. The relay UE determines which remote UE the data packet belongs to based on the IP information and NAT of the data packet sent to it. It then forwards the data to the corresponding remote UE using the NR PC5 DRB.

[0308] Step 1: The relay UE receives the downlink data sent by the base station, reads the IP information in the downlink data, determines which remote UE the data packet belongs to based on the stored NAT information, and then replaces the IP header in the data packet with the IP information of the corresponding remote UE.

[0309] Step 2: The relay UE maps the data packet to the NR PC5 bearer and sends it to the remote UE. The mapping method may include one of the following:

[0310] Mapping method 1: The relay UE maps the remote UE's IP data to the corresponding PC5 DRB based on its own derived QoS rules and the PC5 DRB configuration configured by the base station;

[0311] In mapping mode 2, the Relay UE maps the Uu QoS flow to a PC5 QoS flow and then maps it to the PC5 DRB based on the mapping relationship between the LTE Uu QCI and the NR PC5 PQI configured by the base station and the PC5 DRB configuration.

[0312] Mapping mode three: Relay UE maps remote UE data packets to PC5 DRBs based on the mapping relationship between the base station configured or pre-configured LTE Uu QCI / EPS bearer ID and PC5 DRB priority;

[0313] Mapping method 4: If the PC5 DRB is a bidirectional bearer, reverse mapping can be performed based on the mapping relationship between the uplink NR PC5 DRB and the LTE Uu DRB;

[0314] Mapping mode 5: Based on the base station configured or pre-configured mapping relationship between LTE Uu DRB and NR PC5 DRB (for example, bearer identity mapping, or bearer / logical channel priority mapping), the data packet is mapped to the PC5 DRB;

[0315] Mapping mode six: Based on the base station configured or pre-configured Uu DRB bearer priority or logical channel priority, the remote UE data packet is mapped to the PC5 DRB with the same bearer / logical channel priority.

[0316] Step 3: The Remote UE receives downlink data from the NR PC5 DRB.

[0317] In one implementation, for the scenario of L3 UE-to-Network relay data, NR PC5 is used between the first communication node and the second communication node, and LTE Uu is used between the first communication node and the third communication node. For example, the first communication node is a relay UE, the second communication node is a remote UE, and the third communication node is a base station. In the embodiment, during the transmission of uplink data and downlink data, the configurations performed by the base station are as follows: Figure 8 steps.

[0318] Figure 8 This is a schematic diagram of the process of establishing an air interface data forwarding bearer when another relay UE forwards data to a remote UE according to an embodiment of the present application. Figure 8 As shown, the forwarding bearer establishment process in this embodiment includes S410-S4140.

[0319] S410: IP data packet arrives.

[0320] S420: Derives QoS information by itself.

[0321] S430, relay discovery.

[0322] S440: L2 link establishment process.

[0323] S450: PDU session connection request, or bearer resource modification request.

[0324] S460: Establish or modify a PDU session.

[0325] S470, RRC reconfiguration.

[0326] S480, SL RRC reconfiguration.

[0327] S490: Report the bearer information of PC5.

[0328] S4100, RRC reconfiguration.

[0329] S4110, DL data.

[0330] S4120: Derives QoS information by itself.

[0331] S4130, SUI: QoS Profile.

[0332] S4140, RRC reconfiguration.

[0333] In an embodiment, the remote UE establishes an L2 link connection with the relay UE through high-layer signaling. Afterwards, the relay UE maps the NR PC5 QoS info (e.g., PQI, MFBR, GFBR) obtained during the L2 link establishment process to LTE UuQoS info. The mapping method includes:

[0334] Map the PQI in the NR PC5 QoS info to an identical LTE Uu QCI. If no identical Uu QCI matches the PQI, select the QCI value in the standard LTE QCI list that is closest to the QoS attribute represented by the PQI. Set the GFBR and MFBR values ​​in the Uu QoS info directly to the GFBR and MFBR values ​​in the PC5 QoS info.

[0335] Based on the mapped Uu QoS info, the relay UE chooses to send a PDU connectivity request to establish a new PDU session for the remote UE, dedicated to forwarding the remote UE's data packets, or send a bearer resource modification request to modify the existing PDU session. The bearer resource modification request contains the mapped Uu QoS info. The core network configures the corresponding PDU session based on the QoS information in the bearer resource modification request and notifies the base station of the configuration result. The base station configures the corresponding relay UE air interface DRB or PC5 DRB used by the relay UE to forward the remote UE's downlink data based on the PDU session configuration result, as well as the mapping relationship between PC5 data and air interface data when the relay UE forwards the remote UE's uplink and downlink data (for example, mapping of LTE PC5 QoS flow to NR Uu QoS flow, and mapping of LTE PC5 DRB to NRUu DRB).

[0336] The base station may configure the mapping relationship between PC5 data and air interface data for the relay UE at the following time points:

[0337] At time point 1, after the Relay UE sends a PDU connectivity request or a Bearer resource modification request, Figure 8S450, S460 and S470.

[0338] At time point 2, after the relay UE establishes a PC5 RRC connection with the remote UE, the relay UE reports the NR PC5 DRB information. The PC5 DRB information includes at least one of the following: bearer identifier, RLC mode, logical channel identifier, logical channel priority, and RLC related configuration, such as Figure 8 S480, S490 and S4100 in.

[0339] At time point three, after the Relay UE sends the SUI to the base station, Figure 8 S4110, S4120, S4130 and S4140 in.

[0340] The base station configures an air interface data forwarding bearer (relay DRB) for the relay UE. The air interface data forwarding bearer configuration includes at least one of the following: data forwarding bearer indication, bearer identifier, RLC mode, logical channel identifier, logical channel group identifier, logical channel priority, priority guaranteed bit rate, bucket size duration, and RLC related configuration.

[0341] The base station configures PC5 DRB for the relay UE. PC5 DRB is a downlink PC5 DRB (i.e., sent by the relay UE and received by the remote UE). The configuration information includes the relevant parameters required for SLRB transmission; RLC AM mode or UM mode, and other RLC and logical channel related configuration information.

[0342] Optionally, the base station configures a mapping relationship between PC5 data and air interface data when the relay UE forwards uplink and downlink data of the remote UE. The mapping relationship includes one of the following:

[0343] Mapping relationship 1: Mapping configuration between NR PC5 QoS flow and LTE Uu QoS flow, the configuration includes at least one of the following: mapping between PC5 QoS info and Uu QoS info, mapping between PQI and QCI, and mapping between PFI and EPS bearer ID;

[0344] Mapping relationship 2, mapping configuration of NR PC5 QoS flow and LTE Uu DRB, the configuration includes at least one of the following: mapping of PC5 PFI and Uu DRB identification, mapping of PC55QI and Uu DRB priority, mapping of PC55QI and Uu logical channel priority

[0345] Mapping relationship three, mapping configuration of NR PC5 DRB and LTE Uu DRB, the configuration includes at least one of the following: mapping of PC5 DRB priority and Uu DRB priority, mapping of PC5 DRB label and Uu DRB label, mapping of PC5 logical channel priority and Uu logical channel priority.

[0346] The base station sends the above configuration information to the relay UE via an RRC reconfiguration message.

[0347] In one implementation, due to UE mobility and the dynamic nature of the network environment, the UE experiences deterioration in air interface link quality or relay link quality. In this case, the UE can choose to switch from an air interface connection to a relay connection, from a relay connection to an air interface connection, or from one relay UE to another, to maintain UE-to-network data transmission. This embodiment describes how to maintain service continuity during the handover process.

[0348] Exemplarily, the scenario in which the network link switching occurs includes one of the following:

[0349] Scenario 1: Path transition from a direct air link to a PC5 / SL relay link: Remote UE1 is in RRC connected state communicating over a direct Uu link. When the Uu channel quality deteriorates, UE1 locates a relay UE and switches the air interface path (Uu traffic) to be forwarded to the network via the relay UE. The remote UE's base station and the relay UE's base station can be the same or different base stations.

[0350] Scenario 2: Path switch from PC5 / SL relay link to direct Uu link: Remote UE1 communicates with the network through a relay UE. When UE1 enters base station coverage and establishes an RRC connection, services forwarded by the relay UE are switched to direct transmission over the Uu interface. The remote UE's base station and the relay UE's base station can be the same or different.

[0351] Scenario 3: Due to relay reselection, the relay UE to which the remote UE is connected changes, and the services forwarded by the remote UE through relay UE1 are switched to being forwarded through relay UE2. The base station of relay UE1 and the base station of relay UE2 can be the same base station or different base stations.

[0352] There are two ways to make link switching decisions:

[0353] Method 1: The base station configures link switching criteria or measurement configuration. When the remote UE meets the criteria, it notifies the base station or reports the measurement results to the base station according to the measurement reporting configuration. The base station decides and instructs the handover.

[0354] Method 2: The base station configures or pre-configures link switching criteria. When the remote UE meets the criteria, the remote UE performs the switch autonomously. Optionally, the remote UE notifies the base station after the switch. The link switch notification information reported by the remote UE to the base station includes at least one of the following: a switch indication, a switched service type, a switched PDU session ID, a switched DRB, information about the switched QoS flow (such as QFI / 5QI), and a relay UE identifier.

[0355] For scenario 1, the link switching criteria include at least one of the following: a Uu link quality threshold (which includes a hysteresis value; if the remote UE Uu link quality is lower than the threshold, link switching can be performed), a service type (e.g., data of certain service types is transmitted via the PC5 interface), and a PC5 interface link quality threshold (e.g., if the PC5 interface link quality between the remote UE and the relay UE is higher than the threshold, link switching can be performed). The measurement configuration includes a Uu measurement configuration and a relay (PC5 interface between the UE and the relay UE) measurement configuration. For scenario 2, the link switching criteria include at least one of the following: a Uu link quality threshold (known, including a certain hysteresis value; when the remote UE Uu link quality is higher than the threshold, link switching can be performed), a PC5 link quality threshold (e.g., when the PC5 interface link quality between the remote UE and the relay UE is lower than the threshold, link switching can be performed), a relay UE Uu link quality threshold (optionally, the relay UE informs the remote UE of its Uu link quality through a PC5 RRC signaling message, or a Uu link quality level indication (e.g., an above / below threshold indication, a good / medium / poor indication)), a PC5 interface resource pool CBR threshold (e.g., when the PC5 interface resource pool CBR or the average CBR of all resource pools is higher than the threshold, it indicates that the relay link load is gradually increasing and link switching can be performed), and a service type / service requirement (e.g., data of certain service types / service requirements (e.g., data with a delay requirement lower than a certain threshold) is switched to the Uu interface for transmission). It can be seen that the Uu link quality is the measured RSRP / RSRQ of the Uu port, and the PC5 link quality is the measured RSRP / RSRQ / RSSI of the SL discovery channel or communication channel.

[0356] For the UE-to-Network path / link switch scenarios described in the above three scenarios, since the remote UE does not maintain the RRC connection with the gNB during the UE-to-Network relay,

[0357] Scenario 1: When the remote UE switches from air interface data communication to relay data communication, the remote UE needs to establish a new PC5 PDCP / RLC layer for relay data transmission. For uplink data buffered in the remote UE waiting for transmission:

[0358] 1. Unprocessed IP packets in the Remote UE are directly switched to the relay link for transmission.

[0359] 2. For data packets that have been mapped to Uu QoS flow in Remote UE, based on the base station configured or pre-configured mapping configuration of Uu QoS flow to PC5 QoS flow, the Uu QoS flow data is mapped to PC5 QoS flow, or based on the base station configured or pre-configured mapping configuration of Uu QoS flow to PC5 DRB, the Uu QoS flow data is mapped to PC5 DRB.

[0360] 3. For data packets that have been mapped to Uu DRBs in the Remote UE, since the remote UE has established a new PC5 PDCP layer, the data in the Uu DRB needs to be decrypted according to the Uu PDCP, and then the Uu DRB data needs to be mapped to the PC5 DRB according to the base station configured or pre-configured Uu DRB to PC5 DRB mapping configuration.

[0361] For downlink data buffered in the gNB, since the remote UE uses L3 UE-to-Network Relay after handover, the remote UE does not establish an RRC connection with the gNB. Therefore, the downlink data buffered in the gNB cannot be switched to the relay link for transmission. To maintain service continuity, the remote UE must complete downlink data transmission before handover.

[0362] Scenario 2: When the remote UE switches from relay data communication to air interface data communication, the remote UE needs to establish a new Uu PDCP / RLC layer for air interface data transmission. For uplink data buffered in the remote UE waiting for transmission:

[0363] 1. The unprocessed IP data packets in the Remote UE are directly switched to the air interface link for transmission;

[0364] 2. For data packets in the Remote UE that have been mapped to PC5 QoS flow, based on the base station configured or pre-configured Uu QoS flow to PC5 QoS flow mapping configuration, the PC5 QoS flow data is mapped to Uu QoS flow, or based on the base station configured or pre-configured PC5 QoS flow to Uu DRB mapping configuration, the PC5 QoS flow data is mapped to Uu DRB.

[0365] 3. For data packets that have been mapped to PC5 DRBs in the remote UE, since the remote UE has established a new Uu PDCP layer, the data in the PC5 DRB needs to be decrypted according to the PC5 PDCP, and then the PC5 DRB data needs to be mapped to the Uu DRB according to the base station configured or pre-configured PC5 DRB to Uu DRB mapping configuration.

[0366] For the uplink data buffered in the relay UE, the relay UE continues to complete the uplink transmission.

[0367] Because the remote UE uses L3 UE-to-Network Relay before handover, the remote UE does not establish an RRC connection with the gNB. Therefore, the gNB cannot be informed of the remote UE's handover behavior. Therefore, the downlink data buffered in the gNB cannot be handed over to the remote UE's Uu link for transmission and must be discarded. For the same reason, the relay UE cannot transfer the downlink data buffered in the relay UE to the remote UE's air interface for transmission. Therefore, the transmission must be completed before the remote UE performs handover.

[0368] Scenario 3: When the remote UE switches from one relay UE1 to another relay UE2, the remote UE needs to establish a new PC5 PDCP / RLC layer for relay data transmission. For uplink data buffered in the remote UE awaiting transmission, the IP packets and PC5 QoS flow packets sent to relay UE1 are forwarded to relay UE2. For data mapped to the PC5 DRB established with relay UE1, it is first decrypted according to the PDCP layer established with relay UE1, and then mapped to the PC5 DRB with the same logical channel priority established with relay UE2 for transmission.

[0369] For the uplink data buffered in relay UE1, relay UE1 continues to complete the uplink transmission;

[0370] As for the downlink data buffered in relay UE1, since relay UE1 and relay UE2 do not communicate with each other, this part of the data can only be discarded.

[0371] For downlink data buffered in the gNB, since the remote UE uses L3 UE-to-Network Relay before handover, the remote UE does not establish an RRC connection with the gNB. Therefore, the gNB cannot know the handover behavior of the remote UE. Therefore, the downlink data buffered in the gNB cannot be handed over to the remote UE's Uu link for transmission and can only be discarded.

[0372] In one embodiment, Figure 9 This is a structural block diagram of a communication device provided in an embodiment of the present application. This embodiment is applied to a first communication node. Figure 9 As shown, the communication device in this embodiment includes: a first receiving module 510 and a first mapping module 520.

[0373] A first receiving module 510 is configured to receive Internet Protocol IP data sent by the second communication node;

[0374] The first mapping module 520 is configured to map the IP data to the intermediate bearer according to a first preset mapping method, and transmit the IP data to the third communication node.

[0375] The communication device provided in this embodiment is configured to implement Figure 1 The communication method applied to the first communication node in the illustrated embodiment is similar to the implementation principle and technical effect of the communication device provided in this embodiment, and will not be repeated here.

[0376] In one embodiment, the PDU session selected by the first communication node for the IP data includes one of the following:

[0377] Establish an independent protocol data unit (PDU) session for IP data and transmit IP data on the data bearer (DRB) corresponding to the PDU session;

[0378] The first communication node's own PDU session is used to transmit IP data.

[0379] In one embodiment, for a case where at least two second communication nodes are connected to the same first communication node, the first preset mapping mode includes one of the following: one-to-one mapping; many-to-one mapping;

[0380] Among them, one-to-one mapping is used to indicate that the IP data of different second communication nodes are sent through different relay air interface DRBs respectively; many-to-one mapping is used to indicate that the IP data of at least two second communication nodes are mapped to the same relay air interface DRB for sending.

[0381] In one embodiment, when the first communication node and the second communication node are connected using a new air interface direct link interface NRPC5, and the second communication node and the third communication node use an NR air interface, the many-to-one mapping includes one of the following methods:

[0382] Mapping the IP data of the second communication node to the relay air interface DRB according to the air interface QoS rules and DRB configuration of the first communication node;

[0383] Map the IP data to the relay air interface DRB based on the mapping relationship between the PC5 DRB and the air interface DRB configured or pre-configured by the third communication node;

[0384] Map the IP data to the relay air interface DRB based on the mapping relationship between the PC5 QoS flow and the NR air interface QoS flow configured or pre-configured by the third communication node and the configuration of the NR air interface DRB;

[0385] Based on the mapping relationship between the PC5 QoS flow configured or pre-configured by the third communication node and the air interface DRB, the IP data is mapped to the relay air interface DRB. In one embodiment, when the first communication node and the second communication node are connected using a new air interface direct link interface NR PC5, and the second communication node and the third communication node use an NR air interface, before receiving the Internet Protocol IP data sent by the second communication node, the method further includes:

[0386] Receive the relay connection request from the second communication node and the PC5 unicast connection request;

[0387] The air interface DRB and downlink PC5 DRB, as well as the mapping of uplink and downlink data, are established according to the configuration information fed back by the third communication node.

[0388] In one embodiment, when an NR PC5 connection is adopted between the first communication node and the second communication node, and an NR air interface is adopted between the second communication node and the third communication node, in the process of establishing a layer 2 link connection between the first communication node and the second communication node, a third preset mapping method is adopted to map the pre-acquired PC5 QoS information into air interface QoS information.

[0389] In one embodiment, the third preset mapping method includes:

[0390] Map the PQI in the PC5 QoS flow to the same air interface 5QI;

[0391] If the same air interface 5QI does not match the PQI, the 5QI value in the standard 5QI list that is closest to the QoS attribute represented by the PQI is selected;

[0392] The guaranteed flow bit rate (GFBR) and maximum flow bit rate (MFBR) in the air interface QoS flow are set to the GFBR and MFBR values ​​in the PC5 QoS flow.

[0393] In one embodiment, after mapping the pre-acquired PC5 QoS information to air interface QoS information, the method further includes:

[0394] Sending a PDU session establishment request to the third communication node according to the air interface QoS flow, where the PDU session establishment request is used to forward the IP data of the second communication node;

[0395] Alternatively, a PDU session modification request is sent to the third communication node, where the PDU session modification request is used to modify the current PDU session and carries the mapped air interface QoS information.

[0396] In one embodiment, the communication device further includes:

[0397] The second receiving module is configured to receive the relay air interface DRB or PC5 DRB configured by the third communication node, as well as the mapping relationship between PC5 data and air interface data.

[0398] In one embodiment, when an NR PC5 connection is adopted between the first communication node and the second communication node, and the second communication node and the third communication node adopt an NR air interface, the mapping relationship between PC5 data and air interface data includes one of the following: mapping of PC5 QoS flow to air interface QoS flow, mapping of PC5 DRB to air interface DRB, mapping of PC5 QoS flow to air interface DRB, and mapping of PC5DRB to air interface QoS flow.

[0399] In one embodiment, when an NR PC5 connection is adopted between the first communication node and the second communication node, and an NR air interface is adopted between the second communication node and the third communication node, a time period during which the third communication node configures a mapping relationship between PC5 data and air interface data for the first communication node includes one of the following:

[0400] After the first communication node sends a PDU session establishment request or a PDU session modification request;

[0401] After the first communication node establishes a PC5 RRC connection with the second communication node, the first communication node reports PC5 DRB information, where the PC5 DRB information includes at least one of the following: a bearer identifier, an RLC mode, a logical channel identifier, a logical channel priority, and a radio link layer control protocol RLC-related configuration;

[0402] After the first communication node sends the direct link UE information SUI to the third communication node.

[0403] In one embodiment, when an NR PC5 connection is adopted between the first communication node and the second communication node, and an NR air interface is adopted between the second communication node and the third communication node, the mapping relationship between the PC5 data and the air interface data includes one of the following:

[0404] NR PC5 QoS flow and NR air interface QoS flow mapping configuration, the mapping configuration includes at least one of the following: mapping of PC5 QoS information and air interface QoS information, mapping of QFI and PC5 flow identifier PFI;

[0405] The mapping of the PC5 QoS information to the air interface QoS information includes at least one of the following: mapping the 5QI in the air interface QoS flow to an identical PC5 PQI; if the identical air interface 5QI does not match the PQI, selecting the 5QI value in the standard 5QI list that is closest to the QoS attribute represented by the PQI; directly setting the GFBR and MFBR in the air interface QoS flow to the GFBR and MFBR in the PC5 QoS information;

[0406] Map the PQI in the PC5 QoS flow to the same air interface 5QI; if the same air interface 5QI does not match the PQI, select the PQI value in the standard PQI list that is closest to the QoS attribute represented by the 5QI; directly set the GFBR and MFBR in the PC5 QoS flow to the GFBR and MFBR in the Uu QoS Info;

[0407] NR PC5 QoS flow and NR air interface DRB mapping configuration, the mapping configuration includes at least one of the following: PC5 PFI and air interface DRB identifier mapping, PC5 PQI and air interface DRB priority mapping, PC5 PQI and air interface logical channel priority mapping;

[0408] NR PC5 DRB to NR air interface DRB mapping configuration, the mapping configuration including at least one of the following: PC5 DRB priority to air interface DRB priority mapping, PC5 DRB identifier to air interface DRB identifier mapping, PC5 logical channel priority to air interface logical channel priority mapping, PC5 logical channel identifier to air interface logical channel identifier mapping;

[0409] NR PC5 DRB to NR Uu QoS flow mapping configuration, the configuration includes at least one of the following: mapping of PC5 DRB identifier to UuQFI, mapping of PC5 DRB to priority and Uu 5QI, mapping of PC5 logical channel priority and Uu 5QI.

[0410] In one embodiment, when a long-term evolution LTE PC5 connection is adopted between the first communication node and the second communication node, and the second communication node and the third communication node adopt an NR air interface, the many-to-one mapping includes one of the following methods:

[0411] Map the IP data of the second communication node to the relay NR air interface DRB according to the air interface uplink QoS rules and DRB configuration of the first communication node;

[0412] Map the IP data to the relay NR air interface DRB based on the mapping relationship between the LTE PC5 logical channel and the NR air interface DRB configured or pre-configured by the third communication node;

[0413] Based on the neighbor service packet priority PPPP of the received data of the second communication node PC5, the mapping relationship between PPPP and 5QI configured or pre-configured by the third communication node, and the NR air interface DRB configuration, the IP data of the second communication node is mapped to the air interface QoS flow, and then mapped to the relay NR air interface DRB;

[0414] Based on the PPPP value of the received data of the second communication node PC5, and the mapping relationship between the PPPP value configured or pre-configured by the third communication node and the NR air interface DRB, the IP data of the second communication node is mapped to the relay NR air interface DRB.

[0415] In one embodiment, when an LTE PC5 connection is adopted between the first communication node and the second communication node, and an NR air interface is adopted between the second communication node and the third communication node, before receiving Internet Protocol IP data sent by the second communication node, the method further includes:

[0416] Receive the relay connection request from the second communication node and the PC5 unicast connection request;

[0417] An air interface DRB and uplink and downlink data mapping are established based on the configuration information fed back by the third communication node. In one embodiment, when an LTE PC5 connection is used between the first communication node and the second communication node, and an NR air interface is used between the second communication node and the third communication node, during the process of establishing a layer 2 link connection between the first communication node and the second communication node, a fourth preset mapping method is used to map the pre-acquired PPPP value to NR air interface QoS information.

[0418] In one embodiment, the fourth preset mapping method includes:

[0419] Based on the PPP-5QI mapping table configured or pre-configured by the third communication node.

[0420] In one embodiment, after mapping the pre-acquired PC5 PPPP value to the NR air interface QoS information, the method further includes:

[0421] Sending a PDU session establishment request to the third communication node according to the air interface QoS information, where the PDU session establishment request is used to forward the IP data of the second communication node;

[0422] Alternatively, a PDU session modification request is sent to the third communication node, where the PDU session modification request is used to modify the current PDU session and carries the air interface QoS information obtained after mapping.

[0423] In one embodiment, the communication method further includes: receiving a relay air interface DRB configured by the third communication node, and a mapping relationship between PC5 data and air interface data.

[0424] In one embodiment, when an LTE PC5 connection is adopted between the first communication node and the second communication node, and the second communication node and the third communication node adopt an NR air interface, the mapping relationship between PC5 data and air interface data includes one of the following: mapping of PC5 logical channel and air interface DRB, mapping of PC5 PPPP data flow and air interface DRB, and mapping of PC5 PPPP data flow and Uu QoS flow.

[0425] In one embodiment, when an LTE PC5 connection is adopted between the first communication node and the second communication node, and an NR air interface is adopted between the second communication node and the third communication node, a time period during which the third communication node configures a mapping relationship between PC5 data and air interface data for the first communication node includes one of the following:

[0426] After the first communication node sends a PDU session establishment request or a PDU session modification request;

[0427] After the first communication node establishes a relay connection with the second communication node, the first communication node reports LTE PC5 logical channel information, where the PC5 logical channel information includes at least one of the following: RLC mode, logical channel identifier, logical channel priority, and RLC-related configuration;

[0428] After the first communication node sends the SUI to the third communication node.

[0429] In one embodiment, when an LTE PC5 connection is adopted between the first communication node and the second communication node, and an NR air interface is adopted between the second communication node and the third communication node, the mapping relationship between the PC5 data and the air interface data includes one of the following:

[0430] Mapping configuration of LTE PC5 logical channels and NR air interface DRBs, the mapping configuration including at least one of the following: mapping of LTE PC5 logical channel identifiers and NR air interface DRB identifiers, mapping of LTE PC5 logical channel priorities and NR air interface DRB priorities, mapping of LTE PC5 logical channel priorities and NR air interface logical channel priorities, and mapping of LTE PC5 logical channel identifiers and NR air interface logical channel identifiers;

[0431] LTE PC5 PPPP flow and NR air interface DRB mapping configuration, the mapping configuration including at least one of the following: LTE PPPP value and air interface DRB priority mapping configuration, LTE PPPP value and air interface logical channel priority mapping;

[0432] Mapping configuration of LTE PC5 PPPP flow and NR air interface QoS flow, wherein the mapping configuration includes at least one of the following: Mapping configuration of LTE PPPP value and NR air interface QoS information

[0433] A mapping configuration of LTE PC5 PPPP values ​​and NR air interface QoS information, the mapping configuration comprising at least one of the following: a mapping table of LTE PC5 PPPP values ​​and NR air interface 5QI.

[0434] In one embodiment, when an NR PC5 connection is adopted between the first communication node and the second communication node, and the second communication node and the third communication node adopt an LTE air interface, the many-to-one mapping includes one of the following methods:

[0435] Mapping the IP data of at least two second communication nodes to the LTE air interface DRB according to the uplink traffic flow template TFT and DRB configuration of the first communication node;

[0436] Map the IP data to the LTE air interface DRB based on the mapping relationship between the NR PC5 DRB or the LTE air interface DRB configured or pre-configured by the third communication node;

[0437] Map the IP data to the LTE air interface DRB based on the mapping relationship between the NR PC5 QoS flow configured or pre-configured by the third communication node and the LTE air interface DRB;

[0438] Based on the mapping relationship between the NR PC5 QoS flow configured or pre-configured by the third communication node and the LTE air interface EPS bearer and the configuration of the LTE air interface DRB, the IP data should be set to the LTE air interface DRB.

[0439] In one embodiment, when an NR PC5 connection is adopted between the first communication node and the second communication node, and the second communication node and the third communication node adopt an LTE air interface, the fifth preset mapping method is adopted to map the pre-acquired NRPC5 QoS information into LTE air interface QoS information.

[0440] In one embodiment, the fifth preset mapping method includes:

[0441] Map the PQI in the NR PC5 QoS flow to the exact same LTE air interface 5QI;

[0442] In the case that the identical LTE air interface 5QI does not match the PQI, the QCI value in the standard LTE QCI list closest to the QoS attribute represented by the PQI is selected;

[0443] Set the GFBR and MFBR values ​​in the air interface QoS flow to the GFBR and MFBR values ​​in the PC5 QoS flow.

[0444] In one embodiment, after mapping the pre-acquired PC5 PPPP value to the NR air interface QoS information, the method further includes:

[0445] Sending a PDU session establishment request to the third communication node according to the air interface QoS information, where the PDU session establishment request is used to forward the IP data of the second communication node;

[0446] Alternatively, a PDU session modification request is sent to the third communication node, where the PDU session modification request is used to modify the current PDU session and carries the air interface QoS information obtained after mapping.

[0447] In one embodiment, the communication device further includes: a third receiving module, configured to receive the relay air interface DRB configured by the third communication node, and a mapping relationship between PC5 data and air interface data.

[0448] In one embodiment, when an NR PC5 connection is adopted between the first communication node and the second communication node, and the second communication node and the third communication node adopt the LTE air interface, the mapping relationship between PC5 data and air interface data includes one of the following: NR PC5 QoS and LTE air interface EPS bearer mapping, NR PC5DRB and LTE air interface DRB mapping, NR PC5 QoS flow and LTE air interface DRB mapping, NR PC5DRB and LTE air interface PES bearer mapping.

[0449] In one embodiment, when an NR PC5 connection is adopted between the first communication node and the second communication node, and the second communication node and the third communication node adopt an LTE air interface, the time period during which the third communication node configures a mapping relationship between PC5 data and air interface data for the first communication node includes one of the following:

[0450] After the first communication node sends a PDU session connection request or a bearer resource modification request;

[0451] After the first communication node establishes a PC5 radio resource control RRC connection with the second communication node, the first communication node reports NR PC5 DRB information, where the NR PC5 DRB information includes at least one of the following: a bearer identifier, an RLC mode, a logical channel identifier, a logical channel priority, and an RLC-related configuration;

[0452] After the first communication node sends the SUI to the third communication node.

[0453] In one embodiment, when an NR PC5 connection is adopted between the first communication node and the second communication node, and the second communication node and the third communication node adopt an LTE air interface, the mapping relationship between PC5 data and air interface data includes one of the following:

[0454] The mapping configuration between NR PC5 QoS flows and LTE air interface EPS bearers includes at least one of the following: mapping between PC5QFI and air interface EPS bearer identifier, and mapping between NR PC5 QoS Info and LTE air interface QoS Info.

[0455] The mapping of the PC5 QoS Info to the air interface QoS Info includes at least one of the following: mapping the QCI of the air interface QoS flow to the identical PC5 PQI; selecting the QCI value closest to the QoS attribute represented by the PQI in the standard QCI list when the identical air interface QCI does not match the PQI; directly setting the GFBR and MFBR in the air interface QoS flow to the GFBR and MFBR in the PC5 QoSInfo;

[0456] Map the PQI in the PC5 QoS flow to the same air interface QCI; if the same air interface QCI does not match the PQI, select the PQI value in the standard PQI list that is closest to the QoS attribute represented by the QCI; directly set the GFBR and MFBR in the PC5 QoS flow to the GFBR and MFBR in the Uu QoS Info;

[0457] NR PC5 QoS flow and LTE air interface DRB mapping configuration, the mapping configuration includes at least one of the following: PC5 PFI and air interface DRB identifier mapping, PC5 PQI and air interface DRB priority mapping, PC5 PQI and air interface logical channel priority mapping;

[0458] NR PC5 DRB and LTE air interface DRB mapping configuration, the mapping configuration including at least one of the following: PC5 DRB priority and air interface DRB priority mapping, PC5 DRB identifier and air interface DRB identifier mapping, PC5 logical channel priority and air interface logical channel priority mapping, NR PC5 logical channel identifier and LTE air interface logical channel identifier mapping;

[0459] The mapping configuration of NR PC5 DRB and LTE air interface EPS bearer includes at least one of the following: mapping of PC5 DRB priority and air interface EPS bearer QCI, mapping of PC5 DRB identifier and air interface EPS bearer identifier, and mapping of PC5 logical channel and air interface EPS bearer QCI.

[0460] In one embodiment, when the air interface link quality or relay link quality of the second communication node fails, the switching method of the second communication node includes one of the following: switching from an air interface connection to a relay connection; switching from a relay connection to an air interface connection; switching from a first first communication node connection to a second first communication node connection.

[0461] In one embodiment, when the switching mode of the second communication node is switching from an air interface connection to a relay connection, uplink data buffered in the second communication node waiting for transmission includes one of the following connection modes:

[0462] Directly switch the unprocessed IP data in the second communication node to the relay link for transmission;

[0463] For the IP data mapped to the air interface QoS flow in the second communication node, based on the mapping configuration of the air interface QoS flow to the PC5 QoS flow configured or pre-configured by the third communication node, the air interface QoS flow is mapped to the PC5 QoS flow, or, based on the mapping configuration of the air interface QoS flow to the PC5 DRB configured or pre-configured by the third communication node, the air interface QoS flow is mapped to the PC5 DRB;

[0464] For the IP data mapped to the air interface DRB in the second communication node, the IP data is decrypted according to the air interface PDCP, and based on the mapping configuration of the air interface DRB to PC5 DRB configured or pre-configured by the third communication node, the air interface DRB is mapped to PC5 DRB.

[0465] In one embodiment, when the switching mode of the second communication node is switching from a relay connection to an air interface connection, uplink data buffered in the second communication node waiting for transmission includes one of the following connection modes:

[0466] Directly switch the unprocessed IP data in the second communication node to the air interface link for transmission;

[0467] For the IP data mapped to the PC5 QoS flow in the second communication node, based on the mapping configuration of the air interface QoS flow to the PC5 QoS flow configured or pre-configured by the third communication node, the PC5 QoS flow is mapped to the air interface QoS flow, or based on the mapping configuration of the PC5 QoS flow to the air interface DRB configured or pre-configured by the third communication node, the PC5 QoS flow is mapped to the air interface DRB;

[0468] For the IP data mapped to the PC5 DRB in the second communication node, the IP data is decrypted according to the PC5 PDCP, and based on the mapping configuration of the PC5 DRB to the air interface DRB configured or pre-configured by the third communication node, the PC5 DRB is mapped to the air interface DRB.

[0469] In one embodiment, when the switching mode of the second communication node is switching from the first first communication node to the second first communication node, uplink data buffered in the second communication node waiting for transmission includes one of the following connection modes:

[0470] forwarding the IP data and PC5 QoS flow data sent by the second communication node to the first first communication node to the second first communication node;

[0471] For the IP data mapped to the PC5 DRB established with the first first communication node, decrypt the IP data according to the PDCP layer established with the second first communication node, and map the IP data to the PC5 DRB with the same logical channel priority established with the second first communication node;

[0472] For the IP data that has been buffered in the first first communication node, the first first communication node continues to complete the uplink transmission.

[0473] In one embodiment, when the air interface link quality or relay link quality of the second communication node fails, the link switching decision includes one of the following:

[0474] configuring a link switching criterion or a measurement configuration through a third communication node;

[0475] The link switching criterion is configured or preconfigured by the third communication node.

[0476] In one embodiment, when the switching mode of the second communication node is switching from an air interface connection to a relay connection, the link switching criterion includes at least one of the following:

[0477] Air interface link quality threshold; service type; PC5 interface link quality threshold;

[0478] Measurement configuration, including air interface measurement configuration and relay measurement configuration.

[0479] In one embodiment, when the switching mode of the second communication node is switching from a relay connection to an air interface connection, the link switching criterion includes at least one of the following:

[0480] Air interface link quality threshold; PC5 interface link quality threshold; first communication node air interface link quality threshold; PC5 interface resource pool CBR threshold; service type / service requirements.

[0481] Figure 10 This is a structural block diagram of another communication device provided in an embodiment of the present application. Figure 10 As shown, the communication device in this embodiment includes: a fourth receiving module 610, a determining module 620, and a second mapping module 630;

[0482] A third receiving module 610 is configured to receive downlink data sent by a third communication node;

[0483] A determination module 620 is configured to determine the second communication node to which the downlink data belongs based on the IP address in the downlink data;

[0484] The second transmission module 630 is configured to map the downlink data into PC5 data according to a second preset mapping method, and transmit the data to the second communication node to which it belongs.

[0485] The communication device provided in this embodiment is configured to implement Figure 2 The communication method applied to the first communication node in the illustrated embodiment is similar to the implementation principle and technical effect of the communication device provided in this embodiment, and will not be repeated here.

[0486] In one embodiment, when an NR PC5 connection is adopted between the first communication node and the second communication node, and the second communication node and the third communication node adopt an NR air interface, the second preset mapping mode includes one of the following:

[0487] Mapping the downlink data to a corresponding PC5 DRB according to the QoS rule derived by the first communication node itself and the PC5 DRB configuration configured by the third communication node;

[0488] In the case of bidirectional PC5 DRB, reverse mapping is performed based on the mapping relationship between uplink PC5 DRB and air interface DRB;

[0489] Based on the mapping relationship between the NR Uu QoS flow and the PC5 QoS flow configured by the third communication node and the PC5 DRB configuration, the air interface QoS flow is mapped to the PC5 QoS flow, and then mapped to the PC5 DRB;

[0490] Map the downlink data to the PC5 DRB based on the mapping relationship between the NR Uu QoS flow and the PC5 DRB configured or pre-configured by the third communication node;

[0491] Based on the mapping relationship between the air interface DRB configured or pre-configured by the third communication node and the PC5 DRB, the downlink data is mapped to the PC5 DRB.

[0492] In one embodiment, when an LTE PC5 connection is adopted between the first communication node and the second communication node, and an NR air interface is adopted between the second communication node and the third communication node, the second preset mapping mode includes one of the following:

[0493] Mapping the IP data of the second communication node to the LTE PC5 logical channel based on the mapping relationship between the NR air interface DRB and the LTE PC5 logical channel configured or pre-configured by the third communication node;

[0494] Mapping the IP data of the second communication node to the LTE PC5 logical channel based on the mapping relationship between the NR air interface DRB configured or pre-configured by the third communication node and the LTE PC5 PPPP value;

[0495] Based on the mapping relationship between the NR air interface QoS flow configured or pre-configured by the third communication node and the LTE PC5PPPP data flow, the IP data of the second communication node should be set to the LTE PC5 logical channel.

[0496] In one embodiment, when an NR PC5 connection is adopted between the first communication node and the second communication node, and the second communication node and the third communication node adopt an LTE air interface, the second preset mapping mode includes one of the following:

[0497] Mapping the downlink data to the corresponding NR PC5 DRB according to the QoS rules derived by the first communication node itself and the PC5 DRB configuration configured by the third communication node;

[0498] Map the IP data to the NR PC5 DRB based on the mapping relationship between the LTE air interface DRB and the NR PC5 DRB configured or pre-configured by the third communication node;

[0499] Map the IP data to the NR PC5 DRB based on the mapping relationship between the LTE air interface DRB and the NR PC5 QoS flow configured or pre-configured by the third communication node;

[0500] Based on the mapping relationship between the LTE air interface EPS bearer and the NR PC5QoS flow configured or pre-configured by the third communication node and the configuration of the LTE air interface DRB, the IP data should be set to the LTE air interface DRB.

[0501] Figure 11 This is a schematic diagram of the structure of a device provided in an embodiment of the present application. Figure 11 As shown, the device provided by this application includes: a processor 710, a memory 720 and a communication module 730. The number of processors 710 in the device can be one or more. Figure 11 In the example, a processor 710 is used. The number of memories 720 in the device can be one or more. Figure 11 In the example, a memory 720 is used. The processor 710, memory 720 and communication module 730 of the device can be connected via a bus or other means. Figure 11 In the embodiment, the device is a first communication node.

[0502] The memory 720, as a computer-readable storage medium, can be configured to store software programs, computer executable programs, and modules, such as program instructions / modules corresponding to the device of any embodiment of the present application (for example, the first receiving module and mapping module in the communication device). The memory 720 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of the device, etc. In addition, the memory 720 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some instances, the memory 720 may further include a memory remotely located relative to the processor 710, and these remote memories may be connected to the device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0503] The communication module 730 is configured to establish a communication connection between the first communication node and the second communication node to perform data communication and signal communication.

[0504] The device provided above can be configured to execute the communication method applied to the first communication node provided in any of the above embodiments, and have corresponding functions and effects.

[0505] An embodiment of the present application also provides a storage medium containing computer-executable instructions. When the computer-executable instructions are executed by a computer processor, they are used to execute a communication method applied to a first communication node. The method includes: receiving Internet Protocol IP data sent by a second communication node; mapping the IP data to an intermediate carrier according to a first preset mapping method, and transmitting it to a third communication node.

[0506] An embodiment of the present application also provides a storage medium containing computer-executable instructions, which, when executed by a computer processor, are used to execute a communication method applied to a first communication node. The method includes: determining the second communication node to which it belongs based on the IP address in the downlink data; mapping the downlink data into PC5 data according to a second preset mapping method, and transmitting it to the second communication node to which it belongs.

[0507] It will be appreciated by those skilled in the art that the term user equipment encompasses any suitable type of wireless user equipment, such as a mobile phone, a portable data processing device, a portable web browser or a car-mounted mobile station.

[0508] In general, various embodiments of the present application may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device, although the present application is not limited thereto.

[0509] Embodiments of the present application may be implemented by executing computer program instructions by a data processor of a mobile device, for example, in a processor entity, or by hardware, or by a combination of software and hardware. The computer program instructions may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages.

[0510] The block diagram of any logic flow in the drawings of the present application may represent program steps, or may represent interconnected logic circuits, modules and functions, or may represent a combination of program steps and logic circuits, modules and functions. The computer program may be stored on a memory. The memory may be of any type suitable for the local technical environment and may be implemented using any suitable data storage technology, such as, but not limited to, read-only memory (ROM), random access memory (RAM), optical storage devices and systems (digital versatile discs (DVD) or compact disks (CD)), etc. Computer-readable media may include non-transient storage media. The data processor may be of any type suitable for the local technical environment, such as, but not limited to, a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), and a processor based on a multi-core processor architecture.

Claims

1. A communication method, characterized in that: include: The first communication node receives Internet Protocol IP data sent by the second communication node; wherein NR PC5 is used between the first communication node and the second communication node, and NR air interface Uu is used between the first communication node and the third communication node; The first communication node maps the IP data to the relay bearer according to a first preset mapping mode; wherein the first preset mapping mode includes: many-to-one mapping; the many-to-one mapping is used to indicate that the IP data is mapped to the same relay air interface DRB for transmission; The first communication node transmits the IP data to the third communication node through the corresponding relay Uu DRB according to the Uu DRB configuration.

2. The method according to claim 1, characterized in that Mapping the IP data to the intermediate carrier includes: The first communication node maps the IP data to a relay Uu DRB based on a Uu QoS rule.

3. The method according to claim 2, characterized in that The Uu QoS rules include: The second communication node receives the 5QI on the PQI of the IP data on the PC5 interface, and receives the mapping relationship configuration of the PQI and 5QI from the third communication node, mapping the PC5 QoS flow data packet to the Uu QoS flow.

4. The method according to claim 1, wherein include: The first communication node establishes an independent protocol data unit (PDU) session for the IP data, and transmits the IP data on a data bearer (DRB) corresponding to the PDU session.

5. The method according to claim 1, wherein The first preset mapping method further includes: one-to-one mapping; The one-to-one mapping is used to indicate that IP data is sent through different relay air interface DRBs.

6. A device, characterized in that include: memory, and one or more processors; The memory is used to store one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors are caused to implement: Receiving Internet Protocol IP data sent by the second communication node; wherein NR PC5 is used between the first communication node and the second communication node, and NR air interface Uu is used between the first communication node and the third communication node; Mapping the IP data to the relay bearer according to a first preset mapping mode; wherein the first preset mapping mode includes: many-to-one mapping; the many-to-one mapping is used to indicate that the IP data is mapped to the same relay air interface DRB for transmission; According to the Uu DRB configuration, the IP data is transmitted to the third communication node through the corresponding relay Uu DRB.

7. The device according to claim 6, characterized in that The one or more processors further implement mapping the IP data to a relay Uu DRB based on a UuQoS rule.

8. The device according to claim 7, characterized in that The Uu QoS rules include: The second communication node receives the 5QI on the PQI of the IP data on the PC5 interface, and receives the mapping relationship configuration of the PQI and 5QI from the third communication node, mapping the PC5 QoS flow data packet to the Uu QoS flow.

9. The device according to claim 6, characterized in that The one or more processors further implement: An independent protocol data unit (PDU) session is established for the IP data, and the IP data is transmitted on a data bearer (DRB) corresponding to the PDU session.

10. The device according to claim 6, characterized in that The first preset mapping method further includes: one-to-one mapping; The one-to-one mapping is used to indicate that IP data is sent through different relay air interface DRBs.

11. A storage medium, characterized in that: The storage medium stores a computer program, which, when executed by a processor, implements: Receiving Internet Protocol IP data sent by the second communication node; wherein NR PC5 is used between the first communication node and the second communication node, and NR air interface Uu is used between the first communication node and the third communication node; Mapping the IP data to the relay bearer according to a first preset mapping mode; wherein the first preset mapping mode includes: many-to-one mapping; the many-to-one mapping is used to indicate that the IP data is mapped to the same relay air interface DRB for transmission; According to the Uu DRB configuration, the IP data is transmitted to the third communication node through the corresponding relay Uu DRB.

12. The storage medium according to claim 11, wherein When the computer program is executed by a processor, the one or more processors are caused to further implement: mapping the IP data to a relay Uu DRB based on a Uu QoS rule.

13. The storage medium according to claim 12, wherein: The Uu QoS rules include: The second communication node receives the 5QI on the PQI of the IP data on the PC5 interface, and receives the mapping relationship configuration of the PQI and 5QI from the third communication node, mapping the PC5 QoS flow data packet to the Uu QoS flow.

14. The storage medium according to claim 11, wherein: When the computer program is executed by a processor, the one or more processors are caused to further implement: An independent protocol data unit (PDU) session is established for the IP data, and the IP data is transmitted on a data bearer (DRB) corresponding to the PDU session.

15. The storage medium according to claim 11, wherein The first preset mapping method further includes: one-to-one mapping; The one-to-one mapping is used to indicate that IP data is sent through different relay air interface DRBs.

Images