CN111565416B

CN111565416B - Wireless communication method, user equipment, network equipment and communication device

Info

Publication number: CN111565416B
Application number: CN201910112627.9A
Authority: CN
Inventors: 徐海博; 肖潇; 姚楚婷; 彭文杰; 王键; 王君
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2019-02-13
Filing date: 2019-02-13
Publication date: 2021-11-19
Anticipated expiration: 2039-02-13
Also published as: WO2020164533A1; CN111565416A

Abstract

The application provides a wireless communication method, wherein a first User Equipment (UE) sends a first message to a first network device, and the first message comprises first quality of service (QoS) information; the first network device receiving the first message; the first network equipment determines a target identifier mapped by the first QoS information according to the first QoS information and first information of a first UE, wherein the first information comprises a mapping relation between the QoS information of a sidelink service and the target identifier, and the mapping relation at least comprises the mapping relation between the first QoS information and a first sidelink radio bearer (SL RB), or a logical channel of the first SL RB and the first SL RB. Under the condition of enhancing the control of the network equipment to the PC5 port communication, the loss of data packets in the sidelink service is reduced or avoided.

Description

Wireless communication method, user equipment, network equipment and communication device

Technical Field

The present application relates to the field of communications, and in particular, to a method for wireless communications.

Background

In a wireless network, a base station and a terminal may communicate via an uplink (uplink) and a downlink (downlink). The terminal-to-terminal communication may be performed using a sidelink (sidelink).

With the development of technology, for example, in a vehicle-to-outside (V2X) or device-to-device (D2D) information exchange system in a fifth generation mobile communication technology (5G), in order to better guarantee quality of service (QoS) of sidelink services, enhancing the control of the network device over PC5 port communication requires that the network device configure a sidelink radio bearer (SL RB), and the configuration of SL RB of a User Equipment (UE) may change, thereby causing the loss of data packets in the sidelink services.

Disclosure of Invention

Embodiments of the present application provide a wireless communication method, a user equipment, a network device, and a communication apparatus, which can reduce or avoid loss of data packets in a downlink service under the condition of enhancing control of the network device over a PC5 port.

In a first aspect, a method of wireless communication is provided, including: a first User Equipment (UE) sends a first message to a first network device, wherein the first message comprises first quality of service (QoS) information; the first network device receiving the first message; the first network equipment determines a target identifier mapped by the first QoS information according to the first QoS information and first information of a first UE, wherein the first information comprises a mapping relation between the QoS information of a sidelink service and the target identifier, and the mapping relation at least comprises the mapping relation between the first QoS information and a first sidelink radio bearer (SL RB), or a logical channel of the first SL RB and the first SL RB.

The technical scheme solves the problem that the SL RB configured by the network equipment is different from the SL RB configured by the first UE, so that the data packet in the sidelink service is lost. The network equipment determines the target identifier of the first QoS mapping according to the first QoS and the first information of the first UE, so that the loss of data packets in the sidelink service is avoided.

With reference to the first aspect, in a possible implementation manner, the first network device sends a second message to the first UE, where the second message includes first configuration information of the first SL RB, and the first configuration information includes one or more of the following information: a length of a Packet Data Convergence Protocol (PDCP) sequence number of the first SL RB, a length of a Radio Link Control (RLC) sequence number of the first SL RB, configuration information of a PDCP entity of the first SL RB, configuration information of an RLC entity of the first SL RB, and logical channel configuration information of the first SL RB.

With reference to the first aspect, in a possible implementation manner, the first UE receives the second message; and the first UE sends a third message to a second UE, wherein the third message comprises the first configuration information.

With reference to the first aspect, in a possible implementation manner, the method further includes: the second UE receives a third message; the second UE configures the first SL RB according to the first configuration information; and the second UE sends a fourth message to the first UE, wherein the fourth message is used for indicating that the second UE configures the first SL RB according to the first configuration information.

With reference to the first aspect, in a possible implementation manner, the method further includes: stopping transmission of data on the first SL RB after the first UE receives the second message; the first UE receives the fourth message and resumes transmission of data on the first SL RB.

With reference to the first aspect, in a possible implementation manner, the first information is sent to the first network device by the first UE or a core network device.

With reference to the first aspect, in a possible implementation manner, the first message and the second message further include destination information corresponding to the first SL RB.

With reference to the first aspect, in a possible implementation manner, the first SL RB is an established SL RB of the first UE.

With reference to the first aspect, in a possible implementation manner, the first information further includes second configuration information of the first SL RB, where the second configuration information includes one or more of the following information: a length of a Packet Data Convergence Protocol (PDCP) sequence number of the first SL RB, a length of a Radio Link Control (RLC) sequence number of the first SL RB, configuration information of a PDCP entity of the first SL RB, configuration information of an RLC entity of the first SL RB, and logical channel configuration information of the first SL RB.

With reference to the first aspect, in a possible implementation manner, the first information includes mapping relationships between all QoS information and SL RBs preconfigured by the first UE.

In a second aspect, a method of wireless communication is provided, including: the method comprises the steps that a first User Equipment (UE) sends a first message to a first network device, wherein the first message comprises first quality of service (QoS) information and first information, the first information comprises a mapping relation between QoS information of a sidelink service and a target identifier, and the mapping relation at least comprises the mapping relation between the first QoS information and a first sidelink radio bearer (SL RB), or a logical channel of the first SL RB, or the logical channel of the first SL RB and the first SL RB.

With reference to the second aspect, in a possible implementation manner, the method further includes: the first UE receives a second message sent by the first network device, wherein the second message includes first configuration information of the first SL RB, and the first configuration information includes one or more of the following information: a length of a Packet Data Convergence Protocol (PDCP) sequence number of the first SL RB, a length of a Radio Link Control (RLC) sequence number of the first SL RB, configuration information of a PDCP entity of the first SL RB, configuration information of an RLC entity of the first SL RB, and logical channel configuration information of the first SL RB; and the first UE configures the first SL RB according to the first configuration information.

With reference to the second aspect, in a possible implementation manner, the method further includes: and after receiving the second message, the first UE sends a third message to a second UE, wherein the third message comprises the first configuration information.

With reference to the second aspect, in a possible implementation manner, the method further includes: stopping transmission of data on the first SL RB after the first UE receives the second message; and the first UE receives a fourth message sent by the second UE and recovers transmission of data on the first SL RB, wherein the fourth message is used for indicating that the second UE has configured the first SL RB according to the first configuration information.

With reference to the second aspect, in a possible implementation manner, the first message and the second message further include destination information corresponding to the first SL RB.

With reference to the second aspect, in a possible implementation manner, the first SL RB is an established SL RB of the first UE.

With reference to the second aspect, in a possible implementation manner, the first message further includes second configuration information of the first SL RB, where the second configuration information includes one or more of the following information: a length of a Packet Data Convergence Protocol (PDCP) sequence number of the first SL RB, a length of a Radio Link Control (RLC) sequence number of the first SL RB, configuration information of a PDCP entity of the first SL RB, configuration information of an RLC entity of the first SL RB, and logical channel configuration information of the first SL RB.

With reference to the second aspect, in a possible implementation manner, the first information includes mapping relationships between all QoS information and SL RBs preconfigured by the first UE.

In a third aspect, a method of wireless communication is provided, including: the method comprises the steps that first network equipment receives a first message sent by first User Equipment (UE), wherein the first message comprises first quality of service (QoS) information; the first network equipment determines a target identifier mapped by the first QoS information according to the first QoS information and first information of a first UE, wherein the first information comprises a mapping relation between the QoS information of a sidelink service and the target identifier, and the mapping relation at least comprises the mapping relation between the first QoS information and a first sidelink radio bearer (SL RB), or a logical channel of the first SL RB, or the mapping relation between the first SL RB and the logical channel of the first SL RB.

With reference to the third aspect, in a possible implementation manner, the method further includes: the first network device sends a second message to the first UE, the second message including first configuration information of the first SL RB, the first configuration information including one or more of the following information: a length of a Packet Data Convergence Protocol (PDCP) sequence number of the first SL RB, a length of a Radio Link Control (RLC) sequence number of the first SL RB, configuration information of a PDCP entity of the first SL RB, configuration information of an RLC entity of the first SL RB, and logical channel configuration information of the first SL RB.

With reference to the third aspect, in a possible implementation manner, the first message and the second message further include destination information corresponding to the first SL RB.

With reference to the third aspect, in a possible implementation manner, the first information is sent to the first network device by the first UE or a core network device.

With reference to the third aspect, in a possible implementation manner, the first SL RB is an established SL RB of the first UE.

With reference to the third aspect, in a possible implementation manner, the first message further includes second configuration information of the first SL RB, where the second configuration information includes one or more of the following information: a length of a Packet Data Convergence Protocol (PDCP) sequence number of the first SL RB, a length of a Radio Link Control (RLC) sequence number of the first SL RB, configuration information of a PDCP entity of the first SL RB, configuration information of an RLC entity of the first SL RB, and logical channel configuration information of the first SL RB.

In a fourth aspect, a method of wireless communication is provided, comprising: a first User Equipment (UE) receives a first message sent by a network device; the first UE stores a mapping rule for mapping the service quality QoS information of the sidelink service between the first UE and the second UE to a sidelink radio bearer (SL RB), wherein the mapping rule at least comprises a first mapping rule which is mapping the first QoS information to the first SL RB; the first message comprises first indication information indicating that the sidelink radio bearer mapped by the first QoS information is a second SL RB; the first UE sends a second message to the second UE, wherein the second message comprises second indication information, and the second indication information is used for indicating that the first QoS information is not mapped to the first SL RB.

With reference to the fourth aspect, in a possible implementation manner, the method further includes: the first UE receives a third message sent by the second UE, wherein the third message is a response message of the second message; and the first UE sends a control Protocol Data Unit (PDU) corresponding to the first QoS information to the second UE by using the first SL RB, and the control PDU is used for indicating that the transmission of the data corresponding to the first QoS information is finished on the first SL RB.

With reference to the fourth aspect, in a possible implementation manner, the method further includes: after the first UE transmits the control PDU corresponding to the first QoS information to the second UE by using the first SL RB, the method further includes: the first UE stores a second mapping rule of the first QoS information with the second UE, wherein the second mapping rule is that the first QoS information is mapped to the second SL RB; and the first UE sends the PDU and/or the service data unit SDU corresponding to the first QoS information through the second SL RB.

With reference to the fourth aspect, in a possible implementation manner, the second indication information indicates that the sidelink radio bearer mapped by the first QoS information is a second SL RB.

With reference to the fourth aspect, in a possible implementation manner, the first message and/or the second message further include configuration information of the second SL RB.

With reference to the fourth aspect, in a possible implementation manner, the first message and the second message further include destination information corresponding to the second SL RB.

In a fifth aspect, a method of wireless communication is provided, comprising: the second user equipment UE receives a second message sent by the first UE; the second UE stores a mapping rule for mapping the service quality QoS information of the sidelink service between the first UE and the second UE to a sidelink radio bearer (SL RB), wherein the mapping rule at least comprises a first mapping rule which is mapping the first QoS information to the first SL RB; the second message includes second indication information indicating that the first QoS information is not mapped to the first SL RB.

With reference to the fifth aspect, in a possible implementation manner, the method further includes: the second UE sends a third message to the first UE, wherein the third message is a response message of the second message; and the second UE buffers at least one protocol data unit PDU and/or service data unit SDU (service data unit) from the non-first SL RB, which is received and sent by the first UE.

With reference to the fifth aspect, in a possible implementation manner, the method further includes: the second UE receives a control PDU, wherein the control PDU is used for indicating that the data corresponding to the QoS information is transmitted on the first SL RB; and the second UE delivers the at least one buffered PDU and/or SDU to an upper layer of the second UE.

With reference to the fifth aspect, in a possible implementation manner, the second indication information includes a mapping relationship between the QoS information and the second SL RB.

In a sixth aspect, a method of wireless communication is provided, comprising: a first User Equipment (UE) receives a first message sent by a network device, wherein the first UE stores a mapping relation between service quality (QoS) information of side link service of a second UE and a first side link radio bearer (SL RB), and the first message comprises configuration information of the second SL RB mapped by the QoS information; and if the identifier of the first SL RB is different from the identifier of the second SL RB or the identifier of the logical channel of the first SL RB is different from the identifier of the logical channel of the second SL RB, the first UE transmits the data packet corresponding to the QoS information mapped to the first SL RB through the second SL RB.

With reference to the sixth aspect, in a possible implementation manner, if the SL RB identities of the first SL RB and the second SL RB are different and the operating mode of the radio link control RLC of the first SL RB is unacknowledged mode UM, the first UE delivers a first PDCP service data unit SDU corresponding to the QoS information mapped to the packet data convergence protocol PDCP entity of the first SL RB to the PDCP entity of the second SL RB, where the first PDCP SDU includes a PDCP SDU that the PDCP entity of the first SL RB has associated a sequence number but has not been delivered to the RLC entity of the first SL RB; and if the SL RB identifications of the first SL RB and the second SL RB are different and the working mode of the RLC of the first SL RB is an acknowledged mode AM, the first UE delivers a second PDCP SDU corresponding to the QoS information mapped to the PDCP entity of the first SL RB to the PDCP entity of the second SL RB, wherein the second PDCP SDU comprises the PDCP SDU corresponding to the first PDCP protocol data unit PDU which is not acknowledged by the RLC entity of the first SL RB and is successfully received and the PDCP SDU later.

With reference to the sixth aspect, in a possible implementation manner, the method further includes: the first UE releases the PDCP entity of the first SL RB.

With reference to the sixth aspect, in a possible implementation manner, if the logical channel identifier of the first SL RB is different from the logical channel identifier of the second SL RB, the first UE releases the RLC entity of the first SL RB.

With reference to the sixth aspect, in a possible implementation manner, if the logical channel identifier of the first SL RB is the same as the logical channel identifier of the second SL RB, the first UE discards the service data unit SDU and the protocol data unit PDU in the RLC entity of the first SL RB.

With reference to the sixth aspect, in a possible implementation manner, if the SL RB identities of the first SL RB and the second SL RB are the same, but the logical channel identity of the first SL RB is different from the logical channel identity of the second SL RB, and the operating mode of the RLC of the first SL RB is UM, the first UE submits, to the RLC entity of the second SL RB, a first PDCP SDU corresponding to the QoS information mapped to the PDCP entity of the first SL RB, where the first PDCP SDU includes a PDCP SDU that the PDCP entity of the first SL RB has associated a sequence number but has not been submitted to the RLC entity of the first SL RB; if the first SL RB and the second SL RB have the same SL RB identity, but the logical channel identity of the first SL RB is different from the logical channel identity of the second SL RB, and the RLC of the first SL RB has an operating mode of AM, the first UE delivers a second PDCP SDU corresponding to the QoS information mapped onto the PDCP entity of the first SL RB to the RLC entity of the second SL RB, where the second PDCP SDU includes a PDCP SDU corresponding to a first PDCP PDU that the RLC entity of the first SL RB does not confirm successful reception and a subsequent PDCP SDU.

With reference to the sixth aspect, in a possible implementation manner, the method further includes: and the first UE releases the Radio Link Control (RLC) bearer of the first SL RB.

In a seventh aspect, a method of wireless communication is provided, including: user Equipment (UE) sends a first message to network equipment, wherein the first message comprises service quality (QoS) information of a sidelink service; the UE receives a second message sent by the network equipment, wherein the second message comprises LCG information of a logical channel group corresponding to the QoS information; and the UE attributing the logic channel of the SL RB corresponding to the QoS information to the LCG corresponding to the LCG information.

In an eighth aspect, a method of wireless communication is provided, comprising: the method comprises the steps that network equipment receives a first message sent by User Equipment (UE), wherein the first message comprises service quality (QoS) information of a sidelink service; the network equipment sends a second message to the UE, wherein the second message comprises LCG information of a logical channel group corresponding to the QoS information; the second message is used for instructing the UE to attribute the logic channel of the SL RB corresponding to the QoS information to the LCG corresponding to the LCG information.

In a ninth aspect, there is provided a user equipment comprising: a first sending module, configured to send a first message to a first network device, where the first message includes first quality of service (QoS) information and first information, and the first information includes a mapping relationship between QoS information of a sidelink service and a target identifier, where the mapping relationship at least includes a mapping relationship between the first QoS information and a first sidelink radio bearer (SL RB), or a logical channel of the first SL RB and the first SL RB.

With reference to the ninth aspect, in a possible implementation manner, the method further includes: a first receiving module, configured to receive a second message sent by the first network device, where the second message includes first configuration information of the first SL RB, and the first configuration information includes one or more of the following information: a length of a Packet Data Convergence Protocol (PDCP) sequence number of the first SL RB, a length of a Radio Link Control (RLC) sequence number of the first SL RB, configuration information of a PDCP entity of the first SL RB, configuration information of an RLC entity of the first SL RB, and logical channel configuration information of the first SL RB; a first configuration module, configured to configure the first SL RB according to the first configuration information.

With reference to the ninth aspect, in a possible implementation manner, the method further includes: a second sending module, configured to send, to the second UE, a third message after the user equipment UE receives the second message, where the third message includes the first configuration information.

With reference to the ninth aspect, in a possible implementation manner, the method further includes: a stopping module, configured to stop transmission of data on the first SL RB after the UE receives the second message; a second receiving module, configured to receive a fourth message sent by the second UE, where the fourth message is used to indicate that the second UE has configured the first SL RB according to the first configuration information; a recovery module to recover transmission of data on the first SL RB.

With reference to the ninth aspect, in a possible implementation manner, the first message and the second message further include destination information corresponding to the first SL RB.

With reference to the ninth aspect, in a possible implementation manner, the first SL RB is an established SL RB of the first UE.

With reference to the ninth aspect, in a possible implementation manner, the first message further includes second configuration information of the first SL RB, where the second configuration information includes one or more of the following information: a length of a Packet Data Convergence Protocol (PDCP) sequence number of the first SL RB, a length of a Radio Link Control (RLC) sequence number of the first SL RB, configuration information of a PDCP entity of the first SL RB, configuration information of an RLC entity of the first SL RB, and logical channel configuration information of the first SL RB.

With reference to the ninth aspect, in a possible implementation manner, the first information includes mapping relationships between all QoS information and SL RBs preconfigured by the first UE.

In a tenth aspect, there is provided a network device comprising: a first receiving module, configured to receive a first message sent by a first user equipment UE, where the first message includes first quality of service QoS information; a determining module, configured to determine, according to the first QoS information and first information of a first UE, a target identifier mapped by the first QoS information, where the first information includes a mapping relationship between QoS information of a sidelink service and the target identifier, and the mapping relationship at least includes a mapping relationship between the first QoS information and a first sidelink radio bearer SL RB identifier, or a logical channel identifier of the first SL RB, or a mapping relationship between a first sidelink radio bearer SL RB identifier and a logical channel identifier of the first SL RB.

With reference to the tenth aspect, in a possible implementation manner, the first sending module is configured to send a second message to the first UE, where the second message includes first configuration information of the first SL RB, and the first configuration information includes one or more of the following information: a length of a Packet Data Convergence Protocol (PDCP) sequence number of the first SL RB, a length of a Radio Link Control (RLC) sequence number of the first SL RB, configuration information of a PDCP entity of the first SL RB, configuration information of an RLC entity of the first SL RB, and logical channel configuration information of the first SL RB.

With reference to the tenth aspect, in a possible implementation manner, the first message and the second message further include destination information corresponding to the first SL RB.

With reference to the tenth aspect, in a possible implementation manner, the first information is sent to the first network device by the first UE or a core network device.

With reference to the tenth aspect, in a possible implementation manner, the first SL RB is an established SL RB of the first UE.

With reference to the tenth aspect, in a possible implementation manner, the first message further includes second configuration information of the first SL RB, where the second configuration information includes one or more of the following information: a length of a Packet Data Convergence Protocol (PDCP) sequence number of the first SL RB, a length of a Radio Link Control (RLC) sequence number of the first SL RB, configuration information of a PDCP entity of the first SL RB, configuration information of an RLC entity of the first SL RB, and logical channel configuration information of the first SL RB.

In an eleventh aspect, a user equipment is provided, including: the first receiving module is used for receiving a first message sent by the network equipment; the user equipment stores a mapping rule for mapping the service quality QoS information of the side link service between the user equipment UE and the second UE to a side link radio bearer SL RB, wherein the mapping rule at least comprises a first mapping rule which is that the first QoS information is mapped to the first side link radio bearer SL RB; the first message comprises first indication information indicating that the sidelink radio bearer mapped by the first QoS information is a second SL RB; a first sending module, configured to send a second message to the second UE, where the second message includes second indication information, and the second indication information is used to indicate that the first QoS information is not mapped to the first SL RB.

With reference to the eleventh aspect, in a possible implementation manner, the method further includes: a second sending module, configured to receive a third message sent by the second UE, where the third message is a response message of the second message; a third sending module, configured to send, to the second UE, a control protocol data unit PDU corresponding to the first QoS information by using the first SL RB after the communication module receives a third message, where the control PDU is used to indicate that transmission of data corresponding to the first QoS information is finished on the first SL RB.

With reference to the eleventh aspect, in a possible implementation manner, the method further includes: a second storing module, configured to store a second mapping rule of the first QoS information between the communication module and the second UE after the communication module sends the control PDU corresponding to the first QoS information to the second UE by using the first SL RB, where the second mapping rule is that the first QoS information is mapped to the second SL RB; and a third sending module, configured to send the PDU and/or the service data unit SDU corresponding to the first QoS information through the second SL RB.

With reference to the eleventh aspect, in a possible implementation manner, the second indication information indicates that the sidelink radio bearer mapped by the first QoS information is a second SL RB.

With reference to the eleventh aspect, in a possible implementation manner, the first message and the second message further include configuration information of the second SL RB.

With reference to the eleventh aspect, in a possible implementation manner, the first message and the second message further include destination information corresponding to the second SL RB.

In a twelfth aspect, a user equipment is provided, including: the user equipment stores a mapping rule for mapping the service quality QoS information of the sidelink service between the first UE and the second UE to a sidelink radio bearer SL RB, wherein the mapping rule at least comprises a first mapping rule which is mapping the first QoS information to a first bearer SL RB; a first receiving module, configured to receive a second message sent by the first UE; the second message includes second indication information indicating that the first QoS information is not mapped to the first SL RB.

With reference to the twelfth aspect, in a possible implementation manner, the method further includes: a first sending module, configured to send a third message to the first UE, where the third message is a response message of the second message; a buffering module, configured to buffer the received at least one protocol data unit PDU and/or service data unit SDU from the non-first SL RB, where the PDU is sent by the first UE.

With reference to the twelfth aspect, in a possible implementation manner, the method further includes: a second receiving module, configured to receive a control PDU, where the control PDU is used to indicate that data corresponding to the QoS information ends transmission on the first SL RB; and the submitting module is used for submitting the at least one PDU and/or SDU cached in the caching module to an upper layer of the user equipment.

With reference to the twelfth aspect, in a possible implementation manner, the method further includes: the second indication information includes a mapping relationship of the QoS information and the second SL RB.

In a thirteenth aspect, a user equipment is provided, including: a first sending module, configured to receive a first message sent by a network device, where the user equipment stores a mapping relationship between quality of service (QoS) information of a sidelink service between the User Equipment (UE) and a second UE, and a first sidelink radio bearer (SL RB); the first message includes configuration information of a second SL RB to which the QoS information is mapped; a first transmission module, configured to transmit, via the second SL RB, a packet corresponding to the QoS information mapped to the first SL RB, if the identity of the first SL RB and/or the identity of the logical channel of the first SL RB is different from the identity of the second SL RB and/or the identity of the logical channel of the second SL RB.

With reference to the thirteenth aspect, in a possible implementation manner, the first transmission module is configured to: if the SL RB identities of the first SL RB and the second SL RB are different and the operating mode of the radio link control RLC of the first SL RB is unacknowledged mode UM, the processing module is configured to submit a first PDCP service data unit SDU corresponding to the QoS information on the packet data convergence protocol PDCP entity mapped to the first SL RB to the PDCP entity of the second SL RB, where the first PDCP SDU includes a PDCP SDU which has been associated with a sequence number by the PDCP entity of the first SL RB and has not been submitted to the RLC entity of the first SL RB; if the SL RB identifiers of the first SL RB and the second SL RB are different and the RLC operating mode of the first SL RB is acknowledged mode AM, the processing module is configured to deliver a second PDCP SDU corresponding to the QoS information mapped to the PDCP entity of the first SL RB to the PDCP entity of the second SL RB, where the second PDCP SDU includes a PDCP SDU corresponding to a first PDCP protocol data unit PDU and subsequent PDCP SDUs that are not acknowledged by the RLC entity of the first SL RB and received successfully.

With reference to the thirteenth aspect, in a possible implementation manner, the method further includes: a first release module, configured to release the PDCP entity of the first SL RB.

With reference to the thirteenth aspect, in a possible implementation manner, the method further includes: a second releasing module, configured to release the RLC entity of the first SL RB if the logical channel identifier of the first SL RB is different from the logical channel identifier of the second SL RB.

With reference to the thirteenth aspect, in a possible implementation manner, the method further includes: a discarding module, configured to discard a service data unit SDU and a protocol data unit PDU in the RLC entity of the first SL RB if the logical channel identifier of the first SL RB is the same as the logical channel identifier of the second SL RB.

With reference to the thirteenth aspect, in a possible implementation manner, the first transmission module is configured to: if the first SL RB and the second SL RB have the same SL RB identity, but the first SL RB has a different logical channel identity from the second SL RB, and the RLC of the first SL RB has an operation mode of UM, the processing module is configured to deliver a first PDCP SDU corresponding to the QoS information mapped onto the PDCP entity of the first SL RB to the RLC entity of the second SL RB, wherein the first PDCP SDU includes PDCP SDUs of which the PDCP entity of the first SL RB has been associated with a sequence number but has not been delivered to the RLC entity of the first SL RB; if the first SL RB and the second SL RB have the same SL RB identity, but the logical channel identity of the first SL RB is different from the logical channel identity of the second SL RB, and the RLC of the first SL RB has an operating mode of AM, the processing module is configured to deliver a second PDCP SDU corresponding to the QoS information mapped onto the PDCP entity of the first SL RB to the RLC entity of the second SL RB, where the second PDCP SDU includes a PDCP SDU corresponding to a first PDCP PDU and subsequent PDCP SDUs that the RLC entity of the first SL RB does not confirm successful reception.

With reference to the thirteenth aspect, in a possible implementation manner, the method further includes: and a second releasing module, configured to release the RLC bearer of the first SL RB.

In a fourteenth aspect, a user equipment is provided, which includes: a first sending module, configured to send a first message to a network device, where the first message includes quality of service QoS information of a sidelink service; a first receiving module, configured to receive a second message sent by the network device, where the second message includes a logical channel group LCG information corresponding to the QoS information; and the UE belongs the logic channel of the SL RB corresponding to the QoS information to the LCG corresponding to the LCG information.

In a fifteenth aspect, a user equipment is provided, comprising: a first receiving module, configured to receive a first message sent by a user equipment UE, where the first message includes quality of service QoS information of a sidelink service; a first sending module, configured to send a second message to the UE, where the second message includes the LCG information of the logical channel group corresponding to the QoS information; the second message is used for instructing the UE to attribute the logic channel of the SL RB corresponding to the QoS information to the LCG corresponding to the LCG information.

In a sixteenth aspect, a user equipment is provided, including: a communication interface, configured to send a first message to a first network device, where the first message includes first quality of service QoS information and first information, and the first information includes a mapping relationship between QoS information of a sidelink service and a target identifier, where the mapping relationship at least includes a mapping relationship between the first QoS information and a first sidelink radio bearer SL RB, or a logical channel of the first SL RB and the first SL RB.

With reference to the sixteenth aspect, in a possible implementation manner, the communication interface is further configured to receive a second message sent by the first network device, where the second message includes first configuration information of the first SL RB, and the first configuration information includes one or more of the following information: a length of a Packet Data Convergence Protocol (PDCP) sequence number of the first SL RB, a length of a Radio Link Control (RLC) sequence number of the first SL RB, configuration information of a PDCP entity of the first SL RB, configuration information of an RLC entity of the first SL RB, and logical channel configuration information of the first SL RB; the user equipment further comprises a processor configured to configure the first SL RB according to the first configuration information.

With reference to the sixteenth aspect, in a possible implementation manner, the communication interface is further configured to send, after the user equipment UE receives the second message, a third message to the second UE, where the third message includes the first configuration information.

With reference to the sixteenth aspect, in a possible implementation manner, the processor is further configured to stop transmission of data on the first SL RB after the UE receives the second message; the communication interface is further configured to receive a fourth message sent by the second UE, where the fourth message is used to indicate that the second UE has configured the first SL RB according to the first configuration information; the processor is further configured to resume transmission of data on the first SL RB.

With reference to the sixteenth aspect, in a possible implementation manner, the first message and the second message further include destination information corresponding to the first SL RB.

With reference to the sixteenth aspect, in a possible implementation manner, the first SL RB is an established SL RB of the first UE.

With reference to the sixteenth aspect, in a possible implementation manner, the first message further includes second configuration information of the first SL RB, where the second configuration information includes one or more of the following information: a length of a Packet Data Convergence Protocol (PDCP) sequence number of the first SL RB, a length of a Radio Link Control (RLC) sequence number of the first SL RB, configuration information of a PDCP entity of the first SL RB, configuration information of an RLC entity of the first SL RB, and logical channel configuration information of the first SL RB.

With reference to the sixteenth aspect, in a possible implementation manner, the first information includes mapping relationships between all QoS information and SL RBs preconfigured by the first UE.

In a seventeenth aspect, a network device is provided, including: a communication interface, configured to receive a first message sent by a first user equipment UE, where the first message includes first quality of service QoS information; and a processor, configured to determine a target identifier mapped by the first QoS information according to the first QoS information and first information of a first UE, where the first information includes a mapping relationship between QoS information of a sidelink service and the target identifier, and the mapping relationship at least includes a mapping relationship between the first QoS information and a first sidelink radio bearer SL RB identifier, or a logical channel identifier of the first SL RB, or a mapping relationship between a first sidelink radio bearer SL RB identifier and a logical channel identifier of the first SL RB.

With reference to the seventeenth aspect, in a possible implementation manner, the communication interface is further configured to send a second message to the first UE, where the second message includes first configuration information of the first SL RB, and the first configuration information includes one or more of the following information: a length of a Packet Data Convergence Protocol (PDCP) sequence number of the first SL RB, a length of a Radio Link Control (RLC) sequence number of the first SL RB, configuration information of a PDCP entity of the first SL RB, configuration information of an RLC entity of the first SL RB, and logical channel configuration information of the first SL RB.

With reference to the seventeenth aspect, in a possible implementation manner, the first message and the second message further include destination information corresponding to the first SL RB.

With reference to the seventeenth aspect, in a possible implementation manner, the first information is sent to the first network device by the first UE or a core network device.

With reference to the seventeenth aspect, in a possible implementation manner, the first SL RB is an established SL RB of the first UE.

With reference to the seventeenth aspect, in a possible implementation manner, the first message further includes second configuration information of the first SL RB, where the second configuration information includes one or more of the following information: a length of a Packet Data Convergence Protocol (PDCP) sequence number of the first SL RB, a length of a Radio Link Control (RLC) sequence number of the first SL RB, configuration information of a PDCP entity of the first SL RB, configuration information of an RLC entity of the first SL RB, and logical channel configuration information of the first SL RB.

In an eighteenth aspect, there is provided a user equipment comprising: the communication interface is used for receiving a first message sent by the network equipment; the user equipment stores a mapping rule for mapping the service quality QoS information of the side link service between the user equipment UE and the second UE to a side link radio bearer SL RB, wherein the mapping rule at least comprises a first mapping rule which is that the first QoS information is mapped to the first side link radio bearer SL RB; the first message comprises first indication information indicating that the sidelink radio bearer mapped by the first QoS information is a second SL RB; the communication interface is further configured to send a second message to the second UE, the second message including second indication information indicating that the first QoS information is not mapped to the first SL RB.

With reference to the eighteenth aspect, in a possible implementation manner, the communication interface is further configured to receive a third message sent by the second UE, where the third message is a response message of the second message; the communication interface is further configured to, after the communication module receives a third message, send a control protocol data unit PDU corresponding to the first QoS information to the second UE by using the first SL RB, where the control PDU is used to indicate that transmission of data corresponding to the first QoS information ends on the first SL RB.

With reference to the eighteenth aspect, in one possible implementation, a processor is included; the processor is configured to store a second mapping rule of the first QoS information between the communication module and the second UE after the communication module sends the control PDU corresponding to the first QoS information to the second UE by using the first SL RB, where the second mapping rule is that the first QoS information is mapped to the second SL RB; the communication interface is further configured to send the PDU and/or the service data unit SDU corresponding to the first QoS information through the second SL RB.

With reference to the eighteenth aspect, in a possible implementation manner, the second indication information indicates that the sidelink radio bearer mapped by the first QoS information is a second SL RB.

With reference to the eighteenth aspect, in a possible implementation manner, the first message and the second message further include configuration information of the second SL RB.

With reference to the eighteenth aspect, in a possible implementation manner, the first message and the second message further include destination information corresponding to the second SL RB.

A nineteenth aspect provides a user equipment, where the user equipment stores a mapping rule for mapping quality of service (QoS) information of a sidelink service between a first UE and a second UE to a sidelink radio bearer (SL RB), where the mapping rule at least includes a first mapping rule, and the first mapping rule is mapping of first QoS information to a first bearer (SL RB); the user equipment includes: a communication interface, configured to receive a second message sent by the first UE; the second message includes second indication information indicating that the first QoS information is not mapped to the first SL RB.

With reference to the nineteenth aspect, in a possible implementation manner, the communication interface is further configured to send a third message to the first UE, where the third message is a response message of the second message;

the user equipment comprises a processor for buffering at least one protocol data unit PDU and/or service data unit SDU (service data unit) from the non-first SL RB, which is received and sent by the first UE.

With reference to the nineteenth aspect, in a possible implementation manner, the communication interface is further configured to receive a control PDU, where the control PDU is used to indicate that data corresponding to the QoS information ends being transmitted on the first SL RB; the processor is further configured to deliver the at least one PDU and/or SDU buffered in the buffer module to an upper layer of the ue.

With reference to the nineteenth aspect, in a possible implementation manner, the second indication information includes a mapping relationship between the QoS information and the second SL RB.

In a twentieth aspect, there is provided a user equipment comprising: a communication interface, a processor; the user equipment stores the mapping relation between the service quality QoS information of the side link service between the user equipment UE and the second UE and the first side link radio bearer SL RB; the communication interface is used for receiving a first message sent by a network device, wherein the first message comprises configuration information of a second SL RB mapped by the QoS information; the processor is configured to transmit a packet corresponding to the QoS information mapped to the first SL RB through the second SL RB if the identity of the first SL RB and/or the identity of the logical channel of the first SL RB is different from the identity of the second SL RB and/or the identity of the logical channel of the second SL RB.

With reference to the twentieth aspect, in one possible implementation manner, the processor is configured to: if the SL RB identities of the first SL RB and the second SL RB are different and the operating mode of the radio link control RLC of the first SL RB is unacknowledged mode UM, the processing module is configured to submit a first PDCP service data unit SDU corresponding to the QoS information on the packet data convergence protocol PDCP entity mapped to the first SL RB to the PDCP entity of the second SL RB, where the first PDCP SDU includes a PDCP SDU which has been associated with a sequence number by the PDCP entity of the first SL RB and has not been submitted to the RLC entity of the first SL RB; if the SL RB identifiers of the first SL RB and the second SL RB are different and the RLC operating mode of the first SL RB is acknowledged mode AM, the processing module is configured to deliver a second PDCP SDU corresponding to the QoS information mapped to the PDCP entity of the first SL RB to the PDCP entity of the second SL RB, where the second PDCP SDU includes a PDCP SDU corresponding to a first PDCP protocol data unit PDU and subsequent PDCP SDUs that are not acknowledged by the RLC entity of the first SL RB and received successfully.

With reference to the twentieth aspect, in a possible implementation manner, the processor is further configured to release the PDCP entity of the first SL RB.

With reference to the twentieth aspect, in a possible implementation manner, the processor is further configured to release the RLC entity of the first SL RB if the logical channel identity of the first SL RB is different from the logical channel identity of the second SL RB.

With reference to the twentieth aspect, in a possible implementation manner, the processor is further configured to discard a service data unit SDU and a protocol data unit PDU in the RLC entity of the first SL RB if the logical channel identifier of the first SL RB is the same as the logical channel identifier of the second SL RB.

With reference to the twentieth aspect, in one possible implementation manner, the processor is further configured to: if the first SL RB and the second SL RB have the same SL RB identity, but the first SL RB has a different logical channel identity from the second SL RB, and the RLC of the first SL RB has an operation mode of UM, the processing module is configured to deliver a first PDCP SDU corresponding to the QoS information mapped onto the PDCP entity of the first SL RB to the RLC entity of the second SL RB, wherein the first PDCP SDU includes PDCP SDUs of which the PDCP entity of the first SL RB has been associated with a sequence number but has not been delivered to the RLC entity of the first SL RB; if the first SL RB and the second SL RB have the same SL RB identity, but the logical channel identity of the first SL RB is different from the logical channel identity of the second SL RB, and the RLC of the first SL RB has an operating mode of AM, the processing module is configured to deliver a second PDCP SDU corresponding to the QoS information mapped onto the PDCP entity of the first SL RB to the RLC entity of the second SL RB, where the second PDCP SDU includes a PDCP SDU corresponding to a first PDCP PDU and subsequent PDCP SDUs that the RLC entity of the first SL RB does not confirm successful reception.

With reference to the twentieth aspect, in a possible implementation manner, the processor is further configured to release a radio link control, RLC, bearer of the first SL RB.

In a twenty-first aspect, there is provided a user equipment, comprising: a communication interface, a processor; the communication interface is used for sending a first message to a network device, wherein the first message comprises service quality QoS information of a sidelink service; the communication interface is further configured to receive a second message sent by the network device, where the second message includes the LCG information of the logical channel group corresponding to the QoS information; the processor is configured to attribute the logical channel of the SL RB corresponding to the QoS information to the LCG corresponding to the LCG information.

In a twenty-second aspect, there is provided a network device, comprising: a communication interface, configured to receive a first message sent by a user equipment UE, where the first message includes quality of service QoS information of a sidelink service; the communication interface is further configured to send a second message to the UE, where the second message includes the LCG information of the logical channel group corresponding to the QoS information; the second message is used for instructing the UE to attribute the logic channel of the SL RB corresponding to the QoS information to the LCG corresponding to the LCG information.

A twenty-third aspect provides a computer program storage medium, which is characterized by having program instructions, when the program instructions are directly or indirectly executed, the functions of the method provided in the first to eighth aspects are realized on any one of the following devices: the first user equipment, the second user equipment, the first network equipment, the user equipment.

A twenty-fourth aspect provides a chip system, wherein the chip system comprises at least one processor, and when the program instructions are executed in the at least one processor, the functions of the methods provided in the first to eighth aspects are implemented on any one of the following apparatuses: the first user equipment, the second user equipment, the first network equipment, the user equipment.

Drawings

FIG. 1 is a schematic diagram of one scenario of an inter-device communication scheme.

Fig. 2 is a schematic flow diagram of a method of configuring a sidelink radio bearer by a base station.

Fig. 3 is a schematic flow diagram of a method of configuring a sidelink radio bearer by a UE.

Fig. 4 is a schematic diagram of a SL RB for a UE entering from out-of-coverage into in-coverage for sidelink traffic transmission.

FIG. 5 is a diagram of a SL RB for a UE to transmit sidelink traffic with different QoS information from out-of-coverage to in-coverage.

Fig. 6 is a schematic flow chart of a wireless communication method according to an embodiment of the present application.

Fig. 7 is a schematic flow chart of a wireless communication method according to another embodiment of the present application.

Fig. 8 is a schematic flow chart of a wireless communication method according to another embodiment of the present application.

Fig. 9 is a schematic flow chart of a wireless communication method according to another embodiment of the present application.

FIG. 10 is a schematic diagram of a SL RB variation scenario.

Fig. 11 is a schematic flow chart of a wireless communication method according to another embodiment of the present application.

Fig. 12 is a schematic diagram of another SL RB variation.

Fig. 13 is a schematic flow chart of a wireless communication method according to another embodiment of the present application.

Fig. 14 is a format of a sidelink buffer status report in a long term evolution system.

Fig. 15 is a format of a sidelink buffer status report according to an embodiment of the present application.

Fig. 16 is a side link buffer status report format according to another embodiment of the present application.

Fig. 17 is a side link buffer status report format according to another embodiment of the present application.

Fig. 18 is a schematic flowchart of reporting a sidelink buffer status report according to an embodiment of the present application.

Fig. 19 is a schematic structural diagram of a user equipment provided in an embodiment of the present application.

Fig. 20 is a schematic structural diagram of a network device according to an embodiment of the present application.

Fig. 21 is a schematic structural diagram of a user equipment according to another embodiment of the present application.

Fig. 22 is a schematic structural diagram of a user equipment provided in another embodiment of the present application.

Fig. 23 is a schematic structural diagram of a user equipment provided in another embodiment of the present application.

Fig. 24 is a schematic structural diagram of a user equipment provided in another embodiment of the present application.

Fig. 25 is a schematic structural diagram of a network device according to another embodiment of the present application.

Fig. 26 is a schematic structural diagram of a communication device according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

Fig. 1 is a schematic diagram of a scenario of an inter-device communication scheme. In the scenario shown in fig. 1, there are mainly two air interfaces, namely, a communication interface (Uu port) between a User Equipment (UE) 121 and a network device 110 and a communication interface (PC5 port) between the UE 121 and a UE 122, where the Uu port is used for communication between the user equipment and a base station or a roadside unit, and the PC5 port is used for sidelink communication between the UE and the UE. A link on the Uu port where the UE transmits data to the base station is called an uplink (uplink), and a link on the Uu port where the UE receives data transmitted by the base station is called a downlink (downlink). The communication interface between the UE and the UE is called PC5 port. The link between the UE on the PC5 port and the UE for transmitting data is called Sidelink (Sidelink). The PC5 port is generally used in a scenario where vehicle-to-other devices (V2X), device-to-device (D2D), or the like can perform direct communication between devices. V2X communication can be seen as a special case of D2D communication.

Over the Uu interface, data and Radio Resource Control (RRC) signaling are transmitted between the UE and the base station over radio bearers. Herein, a radio bearer for transmitting data is referred to as a Data Radio Bearer (DRB), and a bearer for transmitting RRC signaling is referred to as a Signaling Radio Bearer (SRB). One radio bearer includes a Packet Data Convergence Protocol (PDCP) entity and a Radio Link Control (RLC) bearer. One RLC bearer includes one RLC entity and a corresponding Logical Channel (LCH). The configuration of the radio bearer is the configuration of the PDCP entity, the RLC entity and the logical channel of the radio bearer. The configuration of a radio bearer requires quality of service (QoS) requirements that can guarantee the traffic transmitted over the radio bearer. At the Uu port, the configuration of radio bearers is configured by the base station for the UE.

On the PC5 port, data and RRC signaling also need to be transmitted between the UE and the UE over the radio bearer. The radio bearer on the PC5 port may be referred to as a sidelink radio bearer (SL RB). In a Long Term Evolution (LTE) V2X system, radio bearers on a PC5 port are respectively established by a sending UE and a receiving UE themselves, and configuration of the radio bearers is predefined by a standard or determined by the sending UE and the receiving UE themselves.

In order to better guarantee the QoS of the V2X service and strengthen the control of the base station on the PC5 port communication, for the UE which is in a coverage area (IC) and is switched to an RRC connection state for carrying out the PC5 port communication in the RRC connection state or according to the configuration requirement of the base station, the base station configures the side link radio bearer according to the QoS information of the side link service sent by the UE.

The QoS information may be a specific set of QoS parameters or an index to the set of QoS parameters. The QoS parameters in the QoS parameter set include, but are not limited to, guaranteed transmission rate, maximum transmission rate, latency requirement, reliability requirement, priority, communication distance. The index of the QoS parameter set may include 5QI (5G QoS identification), VQI (V2X QoS identification), qfi (QoS Flow identification), and the like.

Network device 110 may be used to access a UE to a Radio Access Network (RAN). Thus, the network device may sometimes also be referred to as an access network device, an access network node, or a base station. It will be appreciated that in systems employing different radio access technologies, the names of devices that function as base stations may differ. For convenience of description, apparatuses providing a UE with a wireless communication access function are collectively referred to as a network device in the embodiments of the present application. The network device 110 may be, for example, an evolved Node B (eNB) in Long Term Evolution (LTE), or a next generation Base station (gNB) in 5G. The network device 110 may be a macro base station or a micro base station. The network device 110 may also be a road side device or a certain terminal having a wireless access function, and in this embodiment, devices capable of implementing the functions related to the network device side in this embodiment are collectively referred to as a network device.

The user equipment may also be referred to as a terminal. User equipment may communicate with one or more Core Networks (CNs) via a base station. User equipment may also sometimes be called an access terminal, subscriber unit, subscriber station, mobile, remote station, remote terminal, mobile device, user terminal, wireless network device, user agent, or user equipment. The user equipment may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication capability, a computing device or other device connected to a wireless modem, a vehicle-mounted device, a wearable device or internet of things, a terminal device in a vehicle network, a user equipment in any form in a future network, and the like.

Fig. 2 is a schematic flow diagram of a method of configuring a sidelink radio bearer by a base station. The sidelink service may be a service that does not need to be relayed through a base station or a network when the sender sends the sidelink service to the receiver in a communication mode of D2D. The V2X service is taken as an example for explanation.

The UE1 is in IC and the Radio Resource Control (RRC) state is RRC connected.

At step S201, V2X traffic arrives at UE 1. The UE1 needs to initiate PC5 port based communication with the UE 2.

In step S202, the UE1, the upper layer notifies the Access Stratum (AS) of the PC5QoS information of the V2X service. The UE may obtain QoS information for the V2X service.

In step S203, the UE1 transmits PC5QoS information of the V2X traffic to the base station.

In step S204, the base station transmits configuration information of the SL RB to the UE 1. The base station may obtain the QoS information of the sidelink service, generate configuration information of the SL RB between the UE1 and the UE2 according to the QoS information reported by the UE1, and send the configuration information to the UE 1. .

In step S205, the UE1 and the UE2 establish the SL RB. The UE1 establishes the SL RB according to the configuration information of the SL RB transmitted by the base station.

At step S206, the UE1 and the UE2 perform data transmission on the SL RB.

Fig. 3 is a schematic flow diagram of a method of configuring a sidelink radio bearer by a UE. The UE1 is out of coverage (OOC). The V2X service is taken as an example for explanation.

In step S301, the UE1 stores a mapping relationship between preconfigured QoS information and SL RB configuration.

At step S302, V2X traffic arrives at UE 1. The UE1 needs to initiate communications over the PC5 port.

In step S303, the UE1, the upper layer notifies the Access Stratum (AS) of the PC5QoS information of the V2X service.

In step S304, the UE1 determines the configuration information of the SL RB to be established according to the mapping relationship between the preconfigured QoS information and the SL RB configuration information, and the QoS information of the V2X service.

In step S305, the UE1 and the UE2 establish the SL RB. The UE1 establishes the SL RB with UE2 according to the configuration information.

At step S306, the UE1 and the UE2 perform data transmission on the SL RB.

In the above-described prior art, the configuration of the SL RB of a UE that is performing communication based on port PC5 may be changed, and the change of some configurations of the SL RB may result in the loss of a packet that has not been transmitted. The case of packet loss will be described with reference to fig. 4 and 5.

Fig. 4 is a schematic diagram of a case where the UE1 changes from outside the coverage to the SL RB for the inside-coverage downlink traffic transmission. The UE1 and the UE2 are in communication over the PC5 port. UE1 is out of coverage and a SL RB is established between UE1 and UE2 for transporting current sidelink traffic, e.g., V2X traffic. And the configuration of the SL RB is as follows: the PDCP entity configures a first parameter set; RLC load-bearing configuration first parameter set; the SL RB Identity (ID) is 1 and the logical channel identity is 1. During the communication process, the UE1 moves to the coverage area and shifts to the RRC connection state for communication based on the PC5 port according to the configuration requirement of the base station. According to the traditional manner of configuring sidelink radio bearers by the base station, the UE1 reports the QoS information of the V2X service to the base station, and the base station configures a corresponding SL RB for the UE. Assume that the configuration of the SL RB configured by the base station for the UE1 to carry the V2X service is: the PDCP entity configures a second parameter set; the RLC load-bearing configures a second parameter set; SL RB is identified as 2 and logical channel is identified as 2.

When the UE1 receives the SL RB configuration sent by the base station, there may be data packets that have not been transmitted by the sidelink service in the buffer of the PDCP entity and the buffer of the RLC entity of the SL RB 1.

Illustratively, these packets may include one or more of the following packets: (1) the PDCP has associated a Sequence Number (SN), but has not yet been delivered to a PDCP Protocol Data Unit (PDU) of the RLC layer; (2) PDCP PDUs that have been delivered to the RLC layer but have not yet begun transmission by the RLC layer; (3) the PDCP has been delivered to the RLC layer, and the RLC layer has transmitted but has not transmitted a successful PDCP PDU (corresponding to an Acknowledged Mode (AM) case for the RLC). It should be noted that the present embodiment does not limit the specific type of the data packet.

For the above mentioned packets, there are two possible problems: (1) when a base station configures UE (user equipment) to transmit data by adopting a resource allocation mode based on base station scheduling, the UE cannot report the cache data volume in the SL RB1 to the base station because the base station does not configure a logical channel group to which a logical channel of the SL RB1 belongs; causing the base station to be unable to schedule the transmission of such data; this may result in the UE2 not receiving the data, resulting in data loss; (2) secondly, when the base station configures the UE to transmit data by using a resource allocation method based on autonomously selected resources, if the UE1 transmits both the remaining buffered data in the SL RB1 and the data in the SL RB2, the UE2 may receive packets of the V2X service and deliver the packets out of order, thereby causing data loss.

Fig. 5 is a diagram illustrating a case where the SL RB part for transmitting the sidelink traffic with different QoS information is changed. The UE1 is in coverage and establishes a sidelink data radio bearer (SL DRB) for transporting the current V2X traffic. The sidelink traffic with different QoS information, for example, QoS flows of QFI 1 and QFI 2, or V2X data of VQI 1 and VQI 2, are mapped to the SL RB. The configuration of the SL RB is as follows: the PDCP entity configures a first parameter set; RLC load-bearing configuration first parameter set; the SL RB is identified as 1 and the logical channel is identified as 1.

At some point, the base station reconfigures the mapping of the QoS information to the SL RB. For example, when the UE is handed over, the target base station and the source base station adopt different configuration strategies. In the new configuration, QoS flow of QFI ═ 1 or V2X packet of VQI ═ 1 still maps to SL RB1, but QoS flow of QFI ═ 2 or V2X packet of VQI ═ 2 maps to a new SL RB. The configuration of the new SL RB is as follows: the PDCP entity configures a second parameter set; the RLC load-bearing configures a second parameter set; SL RB is identified as 2 and logical channel is identified as 2.

When the UE1 receives the configuration of the remapping from the base station to the SL RB2, which is QFI/VQI ═ 2, there may be data packets that have not been transmitted by the sidelink service in the buffer of the PDCP entity and the buffer of the RLC entity of the SL RB 1. If UE1 transmits both the remaining buffered data in SL RB1 and the data in SL RB2, it may cause out-of-order delivery of the QFI/VQI ═ 1 packets received by UE2, and thus data loss.

To solve the above problem, the present application provides a method of wireless communication. By the method, the data packet loss of the UE in the communication process based on the PC5 port can be avoided or reduced under the condition that the base station strengthens the communication control of the PC5 port.

In step S601, the first user equipment UE sends a first message to the first network equipment, where the first message includes first quality of service QoS information.

In step S602, the first network device determines, according to the first QoS information and the first information of the first UE, a target identifier to which the first QoS information is mapped.

The first information may include a mapping relationship between QoS information of a sidelink service and a target identifier, where the mapping relationship at least includes a mapping relationship between first quality of service QoS information and a first SL RB, or a logical channel of the first SL RB and the first SL RB.

The target identity may be used to identify the SL RB, or a logical channel of the SL RB and the SL RB.

The "mapping relation" may be "mapping rule", "correspondence" or the like. "mapped" may refer to "corresponding" or "relative".

Optionally, the first information may be sent to the first network device by the first UE or the core network.

As a possible implementation, the first information may be sent by the first UE to the first network device. The first message may include the first information, or the first information may be sent to the first network device via other messages.

The first SL RB may be established by the first UE according to the first QoS information and a mapping relationship of the preconfigured QoS information with the SL RB. The first information may include a mapping relationship of the first QoS information to a first sidelink radio bearer SL RB, or a logical channel of the first SL RB and the first SL RB; further, the first information may include mapping relationships of other QoS information preconfigured by the first UE with SL RBs, for example, the first information may include mapping relationships of all QoS information preconfigured by the first UE with SL RBs. The first SL RB may be an established or an non-established SL RB.

The mapping relationship of the first QoS information and the first SL RB may be self-determined by the first UE, for example, in a case where the first UE does not pre-configure the mapping relationship of the first QoS information and the SL RB. The first UE is preconfigured with the mapping relationship between the first QoS information and the SL RB, or may re-determine the mapping relationship in a self-determined manner according to the situation. For example, when the sidelink service arrives at the first UE, the first UE randomly determines or determines the SL RB mapped by the QoS information of the sidelink service according to a preset manner. The mapping relationship of the first QoS information to the first SL RB may also be determined by the first network device or other network devices. The first SL RB may be an established SL RB. A first SL RB is established and the first UE may determine a mapping relationship of the first QoS information and the first SL RB. The first information may include a mapping relationship of the first QoS information with the first SL RB, or the logical channel of the first SL RB, or the first SL RB and the logical channel of the first SL RB; further, the first information may include mapping relationship between QoS information of traffic transmitted on all SL RBs that the first UE has established and the SL RBs.

The first UE may send first indication information to the first network device, indicating that the first SL RB is an established SL RB. The first message may include first indication information. The first indication information may also be carried in other messages sent to the first network device.

As another possible implementation, the first information may be sent by the core network device to the first network device. The first UE may determine the first SL RB according to the first QoS information and a mapping relationship of the preconfigured QoS information and the SL RB. The first information may include a mapping relationship of the first QoS information with an identity of the first SL RB, or an identity of a logical channel of the first SL RB, or an identity of the first SL RB and an identity of a logical channel of the first SL RB; further, the first information may include mapping relationships of other QoS information preconfigured by the first UE with SL RBs, for example, the first information may include mapping relationships of all QoS information preconfigured by the first UE with SL RBs. The mapping relation between all the QoS information and the SL RB pre-configured by the first UE comprises the mapping relation between the first quality of service QoS information and the first side link radio bearer SL RB, or the logical channel of the first SL RB and the first SL RB. The core network device may be an access and mobility management function (AMF) device. The first SL RB may be a SL RB established or not established by the first UE.

Optionally, the first message may include second configuration information of the first SL RB, the second configuration information including one or more of the following information: length of a packet data convergence protocol PDCP sequence number of the first SL RB, length of a radio link control RLC sequence number of the first SL RB, configuration information of a PDCP entity of the first SL RB, configuration information of an RLC entity of the first SL RB, and logical channel configuration information of the first SL RB.

Optionally, the first message may include destination information corresponding to the first SL RB. When the sidelink service is sent from the first UE to the second UE through the first SL RB, a Layer 2Source ID (Layer 2Source ID) of the second UE or an index corresponding to the Layer two Source ID may be used as the destination information of the first SL RB.

The first message may include source information corresponding to the first SL RB. When the sidelink service is sent from the first UE to the second UE through the first SL RB, a Layer 2Source ID (Layer 2Source ID) of the first UE or an index corresponding to the Layer two Source ID may be used as Source-to-destination information of the first SL RB.

The first network device may send a second message to the first UE. The second message may include first configuration information of the first SL RB, the first configuration information including one or more of the following information: a length of a Packet Data Convergence Protocol (PDCP) sequence number of the first SL RB, a length of a Radio Link Control (RLC) sequence number of the first SL RB, configuration information of a PDCP entity of the first SL RB, configuration information of an RLC entity of the first SL RB, and logical channel configuration information of the first SL RB.

The first configuration information of the first SL RB in the second message may be configuration information that is changed from the second configuration information in the first message. The first network device may perform incremental configuration based on the second configuration information in the first message.

The second message may include a destination identification of the first QoS information map. The target identity of the first QoS information map may be an identity of the first SL RB, an identity of a logical channel of the first SL RB, or an identity of the first SL RB and an identity of a logical channel of the first SL RB. The target identity may indicate a SL RB to which the first configuration information corresponds.

The second message may include the first QoS information. The first QoS information may indicate that sidelink traffic corresponding to the first QoS information is transmitted on the first SL RB.

As a possible implementation manner, if the first message includes the identifier of the first SL RB, or the identifier of the logical channel of the first SL RB, or the identifier of the first SL RB and the identifier of the logical channel of the first SL RB corresponding to the first QoS information, the first configuration information sent by the base station to the first UE may include the identifier of the first SL RB, but does not include the identifier of the logical channel of the first SL RB, nor includes the QoS information of the sidelink service mapped to the first SL RB. The base station may not change the identity of the first SL RB that the UE has configured, the identity of the logical channel of the first SL RB, and the sidelink traffic corresponding to the QoS information mapped to the first SL RB.

The first configuration information sent by the first network device to the first UE may not include the length of the PDCP SN of the first SL RB, and the first network device may not change the length of the PDCP SN of the first SL RB that the UE has configured.

The first configuration information sent by the first network device to the first UE may not include the length of the RLC SN of the first SL RB, and then the first network device may not change the length of the RLC SN of the first SL RB that the UE has configured.

The first UE may configure the first SL RB according to the first configuration information. The first UE may determine configuration parameters of the first SL RB according to the first configuration information. The first UE may configure the PDCP entity, the RLC entity, and the logical channel of the first SL RB.

The first UE may send a third message to the second UE. The first configuration information may include information related to reception, information related to transmission, and information related to both transmission and reception. The configuration information of the reception parameters of the first SL RB may include reception-related information in the first configuration information, and information on both transmission and reception. The third message may be transmitted when the reception parameters of the first SL RB need to be reconfigured, or may be transmitted without determining whether reconfiguration is needed. The reconfiguration required for the reception parameters of the first SL RB may be that the information related to reception and/or the information related to both transmission and reception in the first configuration information is different from the configured information of the first SL RB, or that the information related to reception and/or the information related to both transmission and reception is included in the first configuration information. The third message may include a portion of the configuration information in the first configuration information, e.g., the third message may include information related to reception and information related to both transmission and reception in the first configuration information. The third message may include all of the configuration information in the first configuration information.

The second UE may receive the third message. The second UE may configure the first SL RB according to the configuration information in the third message.

The second UE may send a fourth message to the first UE. The fourth message may be sent after the second UE configures the first SL RB according to the configuration information in the third message. The fourth message may be for indicating that the second UE has configured the first SL RB according to the first configuration information.

The first UE may stop transmission of data on the first SL RB after receiving the second message. The first UE may also stop transmission of data on the first SL RB after sending the third message.

The first UE may resume transmission of data on the first SL RB after a predetermined time. The first UE may also resume transmission of data on the first SL RB after receiving the fourth message. The first UE may receive the fourth message, applying the first configuration information, i.e., applying the configuration parameters of the first SL RB. The first UE may resume transmission of data on the first SL RB after applying the first configuration information.

Fig. 7 is a schematic flow chart of a wireless communication method according to another embodiment of the present application. The first UE and the second UE may be vehicles in the intelligent transportation system, where the first UE travels into a coverage area of the first network device and a sidelink service needs to be transmitted between the two vehicles. The first network device may be a wireless access capable device.

In step S701, the first UE sends a first message to the first network device, where the first message includes the first QoS information and the first information.

The first network device receives the first message, and can determine the target identifier mapped by the first QoS information according to the first QoS information and the first information. The first information comprises a mapping relation between QoS information of a sidelink service and a target identifier, and the mapping relation at least comprises a mapping relation between first quality of service QoS information and a first SL RB, or a logical channel of the first SL RB and the first SL RB. The target identity may be used to identify the first SL RB, or a logical channel of the first SL RB and the first SL RB.

In one possible implementation, the first SL RB is established or not established, and step S701 may be performed. In another possible implementation, if the first SL RB is established, step S701 is performed; the message sent by the first UE to the first network device may include the first QoS information but not the first information if the first SL RB is not established. For the case where the first SL RB is not established, the first UE may perform the method of the first UE in fig. 7, or the method of the UE1 in fig. 2.

The mapping relationship of the QoS information and the SL RB may be pre-configured in the first UE. The first SL RB may be non-established, or the first SL RB may be established by the first UE according to the first QoS information and a mapping relationship with the SL RB, which is pre-configured. The first information may include a mapping relationship of the first QoS information to a first sidelink radio bearer SL RB, or a logical channel of the first SL RB and the first SL RB; further, the first information may include mapping relationships of other QoS information preconfigured by the first UE with SL RBs, for example, the first information may include mapping relationships of all QoS information preconfigured by the first UE with SL RBs.

The mapping relationship of the first QoS information and the first SL RB may be self-determined by the first UE, for example, in a case where the first UE does not pre-configure the mapping relationship of the first QoS information and the SL RB. The first UE is preconfigured with the mapping relationship between the first QoS information and the SL RB, or may re-determine the mapping relationship in a self-determined manner according to the situation. For example, when the sidelink service arrives at the first UE, the first UE randomly determines or determines the SL RB mapped by the QoS information of the sidelink service according to a preset manner. The first SL RB may be an established SL RB. A first SL RB is established and the first UE may determine a mapping relationship of the first QoS information and the first SL RB. The first information may include a mapping relationship of the first QoS information with the first SL RB, or the logical channel of the first SL RB, or the first SL RB and the logical channel of the first SL RB; further, the first information may include mapping relationship between QoS information of traffic transmitted on all SL RBs that the first UE has established and the SL RBs.

The mapping relationship of the first QoS information to the first SL RB may also be determined by the first network device or other network devices. The first SL RB may be an established SL RB. A first SL RB is established and the first UE may determine a mapping relationship of the first QoS information and the first SL RB. The first information may include a mapping relationship of the first QoS information with the first SL RB, or the logical channel of the first SL RB, or the first SL RB and the logical channel of the first SL RB; further, the first information may include mapping relationship between QoS information of traffic transmitted on all SL RBs that the first UE has established and the SL RBs.

The first UE enters IC and may send a first message to the first network device. The first UE may send a first message to the first network device while the first UE is in IC and sidelink traffic arrives. The first UE is in IC and may send a first message to the first network device during transmission of sidelink traffic.

Optionally, the first UE may send first indication information to the first network device, where the first indication information is used to indicate that the first SL RB is an established SL RB. The first message may include first indication information. The first indication information may also be carried in other messages sent to the first network device. Alternatively, the first UE may indicate that the first SL RB is not an established SL RB by not transmitting the first indication information or transmitting the second indication message to the first network device. The first message may include a first indication message, and the first indication information may also be carried in other messages to be sent to the first network device.

The first message may include second configuration information of the first SL RB, the second configuration information including one or more of the following information: a length of a PDCP sequence number of the first SL RB, a length of an RLC sequence number of the first SL RB, configuration information of a PDCP entity of the first SL RB, configuration information of an RLC entity of the first SL RB, and logical channel configuration information of the first SL RB.

Optionally, the first message may include destination information corresponding to the first SL RB. The sidelink service is sent from the first UE to the second UE through the first SL RB, and the destination information of the first SL RB may be a layer 2source ID (layer 2source ID) of the second UE or an index corresponding to the layer two source ID.

Optionally, the first message may include source information corresponding to the first SL RB. When the sidelink service is sent from the first UE to the second UE through the first SL RB, the layer 2source ID of the first UE or an index corresponding to the layer 2source ID may be used as the source-to-destination information of the first SL RB.

Optionally, for a case that the first UE needs to transmit multiple sidelink services, the first message may include multiple pieces of QoS information, the first message may include a mapping relationship between each of the multiple pieces of QoS information and the SL RB, and the first message may further include configuration information of the SL RB corresponding to each of the multiple pieces of QoS information.

It should be noted that steps S702 to S703 are optional steps. In some embodiments, in the case that the first SL RB needs to be reconfigured, steps S702-S703 are performed; in a case where the first SL RB does not need to be reconfigured, for example, the first network device does not configure the first SL RB or the configuration information configuring the first SL RB is not changed, the steps S702 to S703 may not be performed, that is, the first SL RB may not be reconfigured.

In step S702, the first network device sends a second message to the first UE. The second message may include first configuration information of the first SL RB. The first configuration information may include one or more of the following information: a length of a Packet Data Convergence Protocol (PDCP) sequence number of the first SL RB, a length of a Radio Link Control (RLC) sequence number of the first SL RB, configuration information of a PDCP entity of the first SL RB, configuration information of an RLC entity of the first SL RB, and logical channel configuration information of the first SL RB.

The first configuration information of the first SL RB in the second message may be all information for configuring the first SL RB by the first network device, or may be configuration information that is changed from the second configuration information in the first message.

Optionally, the second message may include a destination identification of the first QoS information map. The target identity of the first QoS information map may be an identity of the first SL RB, an identity of a logical channel of the first SL RB, or an identity of the first SL RB and an identity of a logical channel of the first SL RB. The target identity may indicate a SL RB to which the first configuration information corresponds. The target identifier in the second message may indicate that the first configuration information is for configuring the first SL RB.

Optionally, the second message may include the first QoS information. The first QoS information in the second message may indicate that the first SL RB is used to transmit sidelink traffic corresponding to the first QoS information.

Optionally, the second message may include destination information corresponding to the first SL RB. Optionally, the second message may include source information corresponding to the first SL RB.

As a possible implementation manner, if the first information includes a mapping relationship between the first QoS information and an identifier of the first SL RB, or an identifier of a logical channel of the first SL RB, or an identifier of the first SL RB and an identifier of a logical channel of the first SL RB, the first configuration information sent by the base station to the first UE may include the identifier of the first SL RB, but does not include the identifier of the logical channel of the first SL RB, nor includes the QoS information of the sidelink service mapped to the first SL RB. In this implementation, the base station may not change the identity of the first SL RB that the UE has configured, the identity of the logical channel of the first SL RB, and the sidelink traffic corresponding to the QoS information mapped to the first SL RB.

Optionally, if the first configuration information does not include the length of the PDCP SN of the first SL RB, the first network device may not change the length of the PDCP SN of the first SL RB that the UE has configured.

Optionally, if the length of the RLC SN of the first SL RB is not included in the first configuration information, the first network device may not change the length of the RLC SN of the first SL RB that the UE has configured.

Optionally, for a case that the first message may include a plurality of QoS information, the second message may further include configuration information of a SL RB corresponding to each of the plurality of QoS information, or the configuration information of the SL RB corresponding to each of the plurality of QoS information is sent to the first UE in a plurality of messages.

In step S703, the first UE configures the first SL RB according to the first configuration information.

It should be noted that steps S704-S705 are optional steps. In some embodiments, when the receiving parameters of the first SL RB need to be reconfigured, steps S704-S705 are performed; in a case where the receiving parameters of the first SL RB do not need to be reconfigured, for example, the first network device does not configure the receiving parameters of the first SL RB or the configuration information configuring the receiving parameters of the first SL RB is not changed, the steps S704 to S705 may not be performed, that is, the receiving parameters of the first SL RB may not be reconfigured.

In step S704, the first UE transmits a third message to the second UE. The third message includes configuration information of the reception parameters that the first SL RB needs to be reconfigured. Optionally, the third message may include the first configuration information.

In step S705, the second UE configures the first SL RB according to the configuration information of the reception parameter.

The second UE may reconfigure the corresponding parameters of the first SL RB after receiving the third message.

After step S705, the second UE may transmit a fourth message to the first UE. The fourth message may be sent after the second UE configures the first SL RB according to the configuration information in the third message. The fourth message may be for indicating that the second UE has configured the first SL RB according to the first configuration information.

Fig. 8 is a schematic flow chart of a communication method according to another embodiment of the present application.

In step S801, the core network device sends a first message to the first network device. The first message includes first information.

The first UE is pre-configured with first information. The first information comprises a mapping relation between QoS information of a sidelink service and a target identifier, and the mapping relation at least comprises a mapping relation between first quality of service QoS information and a first SL RB, or a logical channel of the first SL RB and the first SL RB.

Optionally, the first information may include mapping relationship of SL RB and other QoS information preconfigured by the first UE. For example, the first information may include a mapping relationship of all QoS information preconfigured by the first UE with the SL RB.

The core network device may be a device having access and mobility management function (AMF).

In step S802, the first UE sends a second message to the first network device, where the second message includes the first QoS information.

The first UE may determine a first SL RB according to the first QoS information and a mapping relationship of the preconfigured QoS information and the SL RB. The first SL RB may be a SL RB established or not established by the first UE. The first information may include a mapping relationship of the first QoS information with an identity of the first SL RB, or an identity of a logical channel of the first SL RB, or an identity of the first SL RB and an identity of a logical channel of the first SL RB.

The first network device receives the second message, and can determine the target identifier mapped by the first QoS information according to the first QoS information and the first information. The first information comprises a mapping relation between QoS information of a sidelink service and a target identifier, and the mapping relation at least comprises a mapping relation between first quality of service QoS information and a first SL RB, or a logical channel of the first SL RB and the first SL RB. The target identity may be used to identify the first SL RB, or a logical channel of the first SL RB and the first SL RB.

Alternatively, the second message may be a sildelinkueinformation message.

The second message may include a plurality of QoS information for a case where the first UE needs to transmit a plurality of sidelink traffic.

Optionally, the first UE may send first indication information to the first network device, where the first indication information is used to indicate that the first SL RB is an established SL RB. The first message may include first indication information. The first indication information may also be carried in other messages sent to the first network device. Alternatively, the first UE may indicate that the first SL RB is not an established SL RB by not transmitting the first indication information or transmitting the second indication message to the first network device. The first message may include a second indication message, and the second indication message may also be carried in other messages to be sent to the first network device.

Optionally, the second message may include destination information of the sidelink traffic of the first QoS information. The sidelink service is sent from the first UE to the second UE through the first SL RB, and the destination information of the first SL RB may be a layer two source identifier of the second UE or an index corresponding to the layer two source identifier.

It should be noted that steps S803 to S804 are optional steps. In some embodiments, in the case that the first SL RB needs to be reconfigured, steps S803-S804 are performed; in a case where the first SL RB does not need to be reconfigured, for example, the first network device does not configure the first SL RB or the configuration information configuring the first SL RB is not changed, the steps S803 to S804 may not be performed, that is, the first SL RB may not be reconfigured.

In step S803, the first network device sends a third message to the first UE. The third message may include first configuration information of the first SL RB. The first configuration information may include one or more of the following information: a length of a Packet Data Convergence Protocol (PDCP) sequence number of the first SL RB, a length of a Radio Link Control (RLC) sequence number of the first SL RB, configuration information of a PDCP entity of the first SL RB, configuration information of an RLC entity of the first SL RB, and logical channel configuration information of the first SL RB.

Optionally, the first message may include second configuration information of the first SL RB, the second configuration information including one or more of the following information: length of a packet data convergence protocol PDCP sequence number of the first SL RB, length of a radio link control RLC sequence number of the first SL RB, configuration information of a PDCP entity of the first SL RB, configuration information of an RLC entity of the first SL RB, and logical channel configuration information of the first SL RB. Optionally, the first message may include configuration information in part or all of the SL RBs in a mapping relationship preconfigured by the first UE, for example, one or more of the following information of part or all of the SL RBs: length of PDCP sequence number, length of RLC sequence number, configuration information of PDCP entity, configuration information of RLC load, and logical channel configuration information.

The first configuration information of the first SL RB in the third message may be all information for configuring the first SL RB by the first network device, or may be configuration information that is changed from the second configuration information in the first message.

Optionally, the third message may include a target identification of the first QoS information map. The target identity of the first QoS information map may be an identity of the first SL RB, an identity of a logical channel of the first SL RB, or an identity of the first SL RB and an identity of a logical channel of the first SL RB. The target identity may indicate a SL RB to which the first configuration information corresponds. The target identifier in the third message may indicate that the first configuration information is for configuring the first SL RB.

The length of the PDCP SN of the first SL RB may not be included in the first configuration information, and the first network device may not change the length of the PDCP SN of the first SL RB that the UE has configured.

The length of the RLC SN of the first SL RB may not be included in the first configuration information, and the first network device may not change the length of the RLC SN of the first SL RB that the UE has configured.

In step S804, the first UE configures the first SL RB according to the first configuration information.

It should be noted that steps S805 to S806 are optional steps. In some embodiments, steps S805-S806 are performed in the case that the reception parameters of the first SL RB need to be reconfigured; in the case that the receiving parameters of the first SL RB do not need to be reconfigured, for example, the first network device does not configure the receiving parameters of the first SL RB or the configuration information configuring the receiving parameters of the first SL RB is not changed, the steps S805 to S806 may not be performed, that is, the second UE may not reconfigure the first SL RB.

In step S805, the first UE transmits a fourth message to the second UE. The fourth message includes configuration information of the reception parameters that the first SL RB needs to be reconfigured.

Optionally, the fourth message may include the first configuration information.

In step S806, the second UE configures the first SL RB according to the configuration information of the reception parameter. The second UE may reconfigure the corresponding parameters of the first SL RB after receiving the fourth message.

After step S806, the second UE may transmit a fifth message to the first UE. The fifth message may be sent after the second UE configures the first SL RB according to the configuration information in the fourth message. The fifth message may be used to indicate that the second UE has configured the first SL RB according to the reception parameters in the third message.

The first UE may stop transmission of data on the first SL RB after receiving the third message. The first UE may also stop transmission of data on the first SL RB after sending the fourth message.

The first UE may resume transmission of data on the first SL RB after a predetermined time. The first UE may also resume transmission of data on the first SL RB after receiving the fifth message. The first UE may receive the fifth message, applying the first configuration information, i.e., applying the configuration parameters of the first SL RB. The first UE may resume transmission of data on the first SL RB after applying the first configuration information.

Fig. 9 is a schematic flow chart of a communication method according to another embodiment of the present application.

In step S901, a first user equipment UE receives a first message sent by a network device.

The first UE stores a mapping rule for mapping QoS information of a sidelink service between the first UE and the second UE to a SL RB, wherein the mapping rule at least comprises a first mapping rule, and the first mapping rule is that the first QoS information is mapped to the first SL RB.

The first SL RB may be established. The embodiment of the present application does not specifically limit the manner of establishing the first SL RB. The first SL RB may be established by the first UE according to the preconfigured QoS information and the mapping rule of the SL RB, may be established by the UE itself when receiving the QoS information, or may be established according to configuration information sent by the network device or other network devices.

The first message includes first indication information indicating that the sidelink radio bearer mapped by the first QoS information is a second SL RB.

The first message may include first QoS information indicating sidelink traffic mapped to the second SL RB.

The first message may also include QoS information for other sidelink traffic and mapping rules for SL RBs.

The mapping rule may be determined by the first UE, may be preconfigured information of the UE, or may be determined by the network device or other network devices. The "mapping rule" may be "mapping relation", "correspondence relation", or the like. "mapped" may refer to "corresponding" or "relative".

The first message may include configuration information of the second SL RB. The configuration information may include one or more of the following: a length of a PDCP sequence number of the second SL RB, a length of an RLC sequence number of the second SL RB, configuration information of a PDCP entity of the second SL RB, configuration information of an RLC entity of the second SL RB, logical channel configuration information of the second SL RB, an identification of the second SL RB, and an identification of a logical channel of the second SL RB.

Prior to step S901, the first UE may send a fourth message to the network device. The fourth message includes the first QoS information.

The fourth message may also include the first information. The first information may include a mapping relationship of QoS information of the sidelink service and the target identifier, the mapping relationship including at least a mapping relationship of the first quality of service QoS information and the first SL RB, or a logical channel of the first SL RB and the first SL RB.

The fourth message may further include configuration information of the first SL RB. The configuration information of the first SL RB may include one or more of the following information: length of a packet data convergence protocol PDCP sequence number of the first SL RB, length of a radio link control RLC sequence number of the first SL RB, configuration information of a PDCP entity of the first SL RB, configuration information of an RLC entity of the first SL RB, and logical channel configuration information of the first SL RB.

In step S902, the first UE transmits a second message to the second UE. The second message includes second indication information. The second indication information indicates that the first QoS information is not mapped to the first SL RB.

The second SL RB may be an established SL RB of the first UE and the second UE, for example, an established SL RB of the first UE and the second UE for a sidelink service of other QoS information. The second SL RB may also be a SL RB that has not been established.

Optionally, the second indication information may indicate that the sidelink radio bearer mapped by the first QoS information is a second SL RB. The second message may further include configuration information of the second SL RB. The configuration information may include one or more of the following: a length of a PDCP sequence number of the second SL RB, a length of an RLC sequence number of the second SL RB, configuration information of a PDCP entity of the second SL RB, configuration information of an RLC entity of the second SL RB, logical channel configuration information of the second SL RB, an identification of the second SL RB, and an identification of a logical channel of the second SL RB.

Optionally, the first UE may generate a control protocol data unit PDU corresponding to the first QoS information, where the control PDU is used to indicate that data corresponding to the first QoS information is completely transmitted on the first SL RB. The control PDU may include the first QoS information.

Optionally, the first UE may send a control protocol data unit PDU corresponding to the first QoS information to the second UE by using the first SL RB. The first UE may submit the control PDU to an underlying transport. The first UE may transmit the control PDU after transmitting the second message and after a certain time has elapsed, and may also transmit the control PDU after receiving the third message transmitted by the second UE. The third message may be a response message to the second message. For example, the second message may be a sidelink radio resource control, RRC, reconfiguration message and the third message may be a sidelink radio resource control, RRC, reconfiguration complete message.

The third message may be for indicating that the second UE has completed configuring the second SL RB if the second message includes second indication information that may indicate that the sidelink radio bearer mapped by the first QoS information is the second SL RB.

After the first UE sends the control PDU corresponding to the first QoS information to the second UE by using the first SL RB, the first UE may store a second mapping rule of the first QoS information with the second UE, where the second mapping rule is that the first QoS information is mapped to the second SL RB. And the first UE sends the PDU and/or Service Data Unit (SDU) corresponding to the first QoS information through the second SL RB. The SDU and PDU may be an SDU and PDU of a Service Data Adaptation Protocol (SDAP) layer, or the SDU and PDU may be an SDU and PDU of a PDCP layer.

And the second UE receives a second message sent by the first UE. The second UE stores a mapping rule for mapping the QoS information of the sidelink service between the first UE and the second UE to the SL RB, wherein the mapping rule at least comprises a first mapping rule, and the first mapping rule is that the first QoS information is mapped to the first SL RB. The second message includes second indication information indicating that the first QoS information is not mapped to the first SL RB.

Optionally, the second UE may send a third message to the first UE, where the third message is a response message of the second message.

The second UE may buffer the received at least one PDU and/or SDU from the first UE that is not the first SL RB after receiving the second message. And if the second message comprises second indication information and the second indication information indicates that the sidelink radio bearer mapped by the first QoS information is a second SL RB, the second UE buffers at least one received PDU and/or SDU (service data Unit) sent by the first UE from the second SL RB after receiving the second message. The SDU and PDU may be an SDU and PDU of a Service Data Adaptation Protocol (SDAP) layer, or the SDU and PDU may be an SDU and PDU of a PDCP layer.

The second UE may receive a control PDU sent by the first UE, where the control PDU is used to indicate that data corresponding to the first QoS information ends being transmitted on the first SL RB.

The second UE may deliver the buffered at least one PDU and/or SDU to an upper layer of the second UE upon receiving the control PDU. The second UE may deliver the buffered at least one PDU and/or SDU to an upper layer in the buffered order. The SDU and PDU may be an SDU and PDU of a Service Data Adaptation Protocol (SDAP) layer, and accordingly, an upper layer of the second UE is an upper layer of the SDAP layer; or the SDU and PDU may be SDU and PDU of the PDCP layer, and correspondingly, the upper layer of the second UE is the upper layer of the PDCP layer, i.e., the SDAP layer.

Fig. 10 is a schematic diagram of a SL RB change situation provided in an embodiment of the present application.

The first UE receives a first message sent by network equipment. The first message includes mapping rules for mapping QoS information of sidelink traffic of the first UE to SL RBs, where the mapping rules include at least a second mapping rule, and the second mapping rule is for mapping the first QoS information to the second SL RB.

Optionally, the first message includes configuration information of a second SL RB configured by the network device for a sidelink service of the first QoS information that the first UE needs to transmit. The first message may also include first QoS information. The first QoS information in the first message may be used to indicate sidelink traffic mapped to the second SL RB. For the first QoS information, a first mapping rule of the first QoS information and the SL RB previously saved by the first UE is: the first SL RB to which the first QoS information is mapped. The second SL RB and the first SL RB are different SL RBs, that is, the mapping relationship of the first QoS information and the SL RBs is changed.

The mapping rule in the first message may also include a mapping rule of other QoS information with SL RB.

The first UE may send a fourth message to the network device before accepting the first message. The fourth message includes the first QoS information.

The fourth message may further include configuration information of the first SL RB. The configuration information of the first SL RB in the fourth message may include one or more of the following information: length of a packet data convergence protocol PDCP sequence number of the first SL RB, length of a radio link control RLC sequence number of the first SL RB, configuration information of a PDCP entity of the first SL RB, configuration information of an RLC entity of the first SL RB, and logical channel configuration information of the first SL RB.

The first UE may send a second message to the second UE. Indicating in a second message that the QoS information has changed mapping relation with SL RBs. Optionally, the second message may be a sidelink radio resource control RRC reconfiguration message.

As a possible implementation manner, the second message includes the first QoS information and a new mapping rule of the SL RB, and the new mapping rule maps the first QoS information to the second SL RB. The sidelink traffic of the first QoS information is mapped to the second SL RB. The second message may further include configuration information of the second SL RB. The configuration information of the second SL RB in the second message may include one or more of the following information: a length of a PDCP sequence number of the second SL RB, a length of an RLC sequence number of the second SL RB, configuration information of a PDCP entity of the second SL RB, configuration information of an RLC entity of the second SL RB, logical channel configuration information of the second SL RB, an identification of the second SL RB, and an identification of a logical channel of the second SL RB.

The second message may also include the first QoS information.

The second SL RB may be an established SL RB for the first UE and the second UE, for example, the established SL RB for the sidelink traffic of other QoS information for the first UE and the second UE; the second SL RB may also be a SL RB that has not been established.

As another possible implementation manner, the second message includes indication information indicating that the first QoS information is remapped with the SL RB, that is, the mapping rule of the first QoS information and the SL RB is changed. The second SL RB may be an established SL RB of the first UE and the second UE, for example, an established SL RB of the first UE and the second UE for a sidelink service of other QoS information.

The first UE may receive a third message sent by the second UE. Optionally, the third message may be a sidelink radio resource control RRC reconfiguration complete message. If the second message includes the mapping relationship between the first QoS information and the second SL RB, the third message is used to notify the first UE to: the second UE has configured the second SL RB according to the configuration information of the second SL RB in the second message, and has completed remapping of the first QoS information to the second SL RB. If the second message includes an indication message for a change in the mapping rule of the first QoS and SL RB, the third message is for informing the first UE: the second UE has received the indication message.

After receiving the first message, for example, after sending the second message or after receiving the third message, the first UE's RRC layer may notify the SDAP layer of the new mapping relationship between the QoS information and the second SL RB. The SDAP layer of the first UE may perform the following operations: generating a control PDU corresponding to the QoS information, where the control PDU is used to indicate that data corresponding to the QoS information is transmitted over the first SL RB, and the control PDU may be, for example, an end marker (end marker) control PDU, and the control PDU may include the QoS information; mapping the end mark control PDU to a first SL RB according to the stored mapping relation from the QoS information to the SL RB; submitting the control PDU to a bottom layer for transmission; saving a new mapping relation between the QoS information and the SL RB, namely the mapping relation between the QoS information and the second SL RB; and when the SDAP layer of the first UE receives the SDAP SDU from the upper layer, the SDAP maps the SDAP SDU to the second SL RB for transmission according to the stored mapping relation between the QoS information and the SL RB.

After the second UE receives the second message sent by the first UE, the RRC layer of the second UE may perform the following operations: informing the SDAP layer of the new mapping relation between the QoS information and the SL RB (corresponding to the first indication mode of the first UE), or informing the SDAP layer of the change of the mapping relation between the QoS information and the SL RB (corresponding to the second indication mode of the first UE) by the RRC layer of the second UE; and generating a third message and sending the third message to the first UE. After receiving the above-mentioned notification from the RRC layer, the SDAP layer of the second UE may perform the following operations: after receiving SDAP SDU submitted by a PDCP layer which is not the first SL RB, caching the SDAP SDU according to a receiving sequence; and after receiving an end mark control PDU corresponding to the QoS information sent by the first UE, sequentially submitting the cached SDAP SDUs to an upper layer.

Optionally, if the second message includes the first QoS information mapped to the second SL RB, after receiving the SDAP SDU delivered from the PDCP layer of the second SL RB, the SDAP layer of the second UE may buffer the SDAP SDU in the receiving order; and after receiving an end mark control PDU corresponding to the QoS information sent by the first UE, sequentially submitting the cached SDAP SDUs to an upper layer.

Fig. 11 is a schematic flow chart of a communication method provided in an embodiment of the present application.

In step S1101, the first UE receives a first message sent by the network device.

The first UE stores the mapping relation between the QoS information of the side-link service of the second UE and the first SL RB. The first message includes configuration information of a second SL RB to which the QoS information is mapped.

In step S1102, if the identity of the first SL RB is different from the identity of the second SL RB or the identity of the logical channel of the first SL RB is different from the identity of the logical channel of the second SL RB, the first UE transmits a packet corresponding to the QoS information mapped onto the first SL RB through the second SL RB.

As an implementation manner, if the SL RB identities of the first SL RB and the second SL RB are different, the first UE delivers the PDCP SDU corresponding to the QoS information mapped to the PDCP entity of the first SL RB to the PDCP entity of the second SL RB.

If the work mode of the radio link control RLC of the first SL RB is UM, the PDCP SDU corresponding to the QoS information comprises the PDCP SDU which is associated with the sequence number of the PDCP entity of the first SL RB and is not delivered to the RLC entity of the first SL RB.

And if the working mode of the Radio Link Control (RLC) of the first SL RB is AM, the PDCP SDUs corresponding to the QoS information comprise the PDCP SDU corresponding to the first PDCP Protocol Data Unit (PDU) which is not confirmed to be successfully received by the RLC entity of the first SL RB and the PDCP SDUs after the PDCP SDU.

As another implementation, if the SL RB identities of the first SL RB and the second SL RB are the same, the first UE delivers the PDCP SDU corresponding to the QoS information mapped to the PDCP entity of the first SL RB to the RLC entity of the second SL RB.

After the first UE delivers the PDCP SDU corresponding to the QoS information mapped to the PDCP entity of the first SL RB to the PDCP entity of the second SL RB, the first UE may release the PDCP entity of the first SL RB.

As one implementation, the first UE may release the RLC entity of the first SL RB if the logical channel identity of the first SL RB is different from the logical channel identity of the second SL RB.

As another implementation, if the logical channel identity of the first SL RB is the same as the logical channel identity of the second SL RB, the first UE may discard SDUs and PDUs in the RLC entity of the first SL RB.

Fig. 12 is a schematic diagram of a SL RB change of the sidelink service mapping in the embodiment of the present application.

In the case of fig. 12(a), the SL RB ID and the logical channel ID of the SL RB to which the QoS information is mapped are both changed.

After the first UE receives the first message transmitted by the network device at step S1101, the first UE may reset a Medium Access Control (MAC).

After receiving the first message, further, the first UE may release the RLC bearer of the original first SL RB (i.e., SL RB1 in fig. 12 (a)) to which the QoS information is mapped; further, the first UE establishes an RLC bearer of a new second SL RB to which the QoS information is mapped; further, the first UE establishes a PDCP entity of the new second SL RB to which the QoS information is mapped.

After receiving the first message, if the SL RB mapped by the QoS information is RLC UM, the PDCP entity of the first SL RB mapped by the QoS information in the first UE may submit the PDCP SDUs that have been associated with the SN number but have not been submitted to the original RLC bearer to the PDCP entity of the new second SL RB (i.e., SL RB2 in fig. 12 (a)) in the order of the associated SN number. If the SL RB mapped by the QoS information is RLC AM, the PDCP entity of the first SL RB mapped by the QoS information in the first UE may submit the PDCP SDU corresponding to the first PDCP PDU and the subsequent PDCP SDUs, which the original RLC entity does not acknowledge to successfully receive, to the PDCP entity of the second SL RB in the order of associated SNs. After handing the PDCP SDU to the PDCP entity of the second SL RB, the first UE may release the PDCP entity of the first SL RB.

After receiving the first message, the first UE may further send a second message to the second UE. The second message indicates the mapping relationship of the QoS information and the second SL RB. Optionally, the first UE sends the second message after releasing the PDCP entity of the first SL RB.

In the case of fig. 12(b), the SL RB ID of the SL RB mapped by the QoS information is not changed, but the logical channel ID of the SL RB mapped by the QoS information is changed.

After the first UE receives the first message transmitted by the network device in step S1101, the first UE may reset the MAC.

After receiving the first message, the first UE may release the original RLC bearer of the original first SL RB (i.e., SL RB1 in fig. 12 (a)) to which the QoS information is mapped; further, the first UE may establish a new RLC bearer of the first SL RB to which the QoS information is mapped.

After receiving the first message, further, if the SL RB mapped by the QoS information is RLC UM, the PDCP entity of the first SL RB mapped by the QoS information of the first UE may submit the PDCP SDUs that have been associated with the SN numbers but have not been submitted to the original RLC bearer to the RLC entity of the new RLC bearer in the order of the associated SN numbers. If the SL RB mapped by the QoS information is RLC AM, the PDCP entity of the original SL RB mapped by the QoS information of the first UE may submit the PDCP SDU corresponding to the first PDCP PDU and the subsequent PDCP SDU, which are not confirmed to be successfully received by the RLC entity carried by the original RLC, to the RLC entity carried by the new RLC in the order of associated SNs.

After receiving the first message, further, the first UE may send a second message to the second UE. The second message indicates the mapping relationship of the QoS information and the second SL RB.

In the case of fig. 12(c), the SL RB ID of the SL RB mapped by the QoS information is changed, but the logical channel ID of the SL RB mapped by the QoS information is not changed.

After receiving the first message, the RLC entity of the first SL RB to which the QoS information of the first UE is mapped may discard all RLC PDUs and RLC SDUs; further, the first UE establishes a PDCP entity of the second SL RB to which the QoS information is mapped.

After receiving the first message, further, if the SL RB mapped by the QoS information is RLC UM, the PDCP entity of the original first SL RB mapped by the QoS information of the first UE may deliver the PDCP SDUs that have been associated with SN numbers but have not been delivered to the RLC entity to the PDCP entity of the second SL RB in the order of the associated SN numbers. If the SL RB mapped by the QoS information is RLC AM, the PDCP entity of the first SL RB mapped by the QoS information of the first UE may deliver the PDCP SDU corresponding to the first PDCP PDU and the subsequent PDCP SDUs that the RLC entity does not acknowledge successful reception to the PDCP entity of the second SL RB in the order of associated SNs. After handing the PDCP SDU to the PDCP entity of the second SL RB, the first UE may release the PDCP entity of the first SL RB.

After receiving the first message, further, the first UE may send a second message to the second UE. The second message indicates the mapping relationship of the QoS information and the second SL RB. Optionally, the first UE sends the second message after releasing the PDCP entity of the first SL RB.

In the three cases of fig. 12, the second UE may reset the MAC after receiving the second message.

After receiving the second message, further, the second UE may release the RLC bearer of the first SL RB.

After receiving the second message, further, if the SL RB mapped by the QoS information is RLC UM, the PDCP entity of the original first SL RB mapped by the QoS information of the second UE may deliver the PDCP SDU, which has been received, to the upper layer. If the SL RB mapped by the QoS information is RLC AM, the PDCP entity of the first SL RB mapped by the QoS information of the second UE can discard the PDCP SDU which is already received. After delivering the PDCP SDU to the upper layer or discarding, the second UE may release the PDCP entity of the original SL RB.

Fig. 13 is a schematic flow chart of a communication method provided in an embodiment of the present application.

In step 1301, the UE sends a first message to the network device.

The first message may include quality of service, QoS, information for sidelink traffic. The time for sending the first information to the network device may be that the first UE initiates a sidelink service, that the first UE enters a coverage, or that the first information is sent at a fixed time, which is not limited in this embodiment of the present application.

In step 1302, the network device sends a second message to the UE, where the second message includes Logical Channel Group (LCG) information corresponding to the QoS information. The LCG information may be an LCG ID.

In step 1303, the UE establishes a SL RB corresponding to the QoS information, and assigns a logical channel of the SL RB corresponding to the QoS information to an LCG corresponding to the LCG information.

The UE may report a sidelink buffer status report (SL BSR) of the SL RB corresponding to the QoS information to the base station through the LCG.

Fig. 14 is a format of SL BSR in LTE. In the communication based on the PC5 port, when the base station configures the UE to adopt the resource allocation method based on scheduling, the UE needs to report the SL BSR to the base station. When the number of destination indexes included is an even number, the format is as shown in fig. 14 (a); when the number of destination indexes included is an odd number, the format is as shown in fig. 14 (b). The format of the SL BSR may generate a large signaling overhead.

In the SL BSR format, if the UE needs to report buffer sizes (buffer sizes) of N LCGs for one destination index, the same destination index needs to appear N times. The application aims to solve the problem of how to design a SL BSR format with low signaling overhead. The content and format contained in the SL BSR is designed with at least one of the following options.

As a possible implementation manner, the SL BSR of the first option includes a first bitmap field, one or more second bitmap fields, and a buffer size (buffer size).

The length of the first bitmap field is the maximum number of sidelink destinations N, i.e. the first bitmap contains N bits. Each bit Di (i ═ 1, 1, 2, … N) is used to indicate whether the second bitmap field corresponding to destination index (destination index) ═ i and the buffer size are present. For example, Di ═ 1 indicates that the second bitmap field and the buffer size corresponding to the destination index ═ i are contained in the SL BSR, and Di ═ 0 indicates that the second bitmap field and the buffer size corresponding to the destination index ═ i are not contained in the SL BSR. The UE reports the destination identity to be communicated to the base station in an RRC message. The sequence of the destination identifiers in the message is the destination index corresponding to the destination identifier.

The length of the second bitmap field is the maximum number M of logical channel groups, i.e. the second bitmap contains M bits. When the reported SL BSR is a non-truncated SL BSR, each bit LCGj (j ═ 0, 1, 2, … M-1) is used to indicate whether the buffer size of LCG ID ═ j appears or is reported; when the reported SL BSR is a truncated SL BSR, each bit LCGj (j ═ 0, 1, 2, … M-1) is used to indicate whether there is data in the logical channel group with LCG ID ═ j. For example, when the reported SL BSR is a non-truncated SL BSR, LCGj ═ 1 indicates that the buffer size of LCG ID ═ j is reported, and LCGj ═ 1 indicates that the buffer size of LCG ID ═ j is not reported. When the reported SL BSR is a truncated SL BSR, LCGj ═ 1 indicates that there is data in the logical channel group with LCG ID ═ j, and LCGj ═ 0 indicates that there is no data in the logical channel group with LCG ID ═ j.

The buffer size is a total data amount of all logical channels in the corresponding logical channel group of the corresponding destination.

Fig. 15 shows a format of a SL BSR according to an embodiment of the present application. Fig. 15 shows an example of a format of an SL BSR, where N is 32, M is 8, the length of the buffer size field is 8 bits, and the length of the LCG ID field is 3 bits.

As another possible implementation, the SL BSR of the second option includes a destination index field, a bitmap field, and a buffer size.

The destination index field is used to indicate the destination to which the following bitmap field corresponds. The UE reports the destination identity to be communicated to the base station in an RRC message. The sequence of the destination identifiers in the message is the destination index corresponding to the destination identifier.

The length of the bitmap field is the maximum number M of logical channel groups, i.e. the second bitmap contains M bits. When the reported SL BSR is a non-truncated SL BSR, each bit LCGj (j ═ 0, 1, 2, … M-1) is used to indicate whether the buffer size of LCG ID ═ j appears or is reported; when the reported SL BSR is a truncated SL BSR, each bit LCGj (j ═ 0, 1, 2, … M-1) is used to indicate whether there is data in the logical channel group with LCG ID ═ j. For example, when the reported SL BSR is a non-truncated SL BSR, LCGj ═ 1 indicates that the buffer size of LCG ID ═ j is reported, and LCGj ═ 1 indicates that the buffer size of LCG ID ═ j is not reported. When the reported SL BSR is a truncated SL BSR, LCGj ═ 1 indicates that there is data in the logical channel group with LCG ID ═ j, and LCGj ═ 0 indicates that there is no data in the logical channel group with LCG ID ═ j.

The total data amount of all logical channels in the corresponding logical channel group of the corresponding destination is buffered.

Fig. 16 shows another format of the SL BSR according to the embodiment of the present application. Fig. 16 shows an example of a format of the SL BSR, where the destination index field is 5 bits long, M is 8 bits long, the buffer size field is 8 bits long, and the LCG ID field is 3 bits long.

As another possible implementation manner, the SL BSR of the second option includes a destination index field, a logical channel group identity (LCG ID) field,

The destination index is used to indicate the destination to which the following bitmap field corresponds. The UE reports the destination identity to be communicated to the base station in an RRC message. The sequence of the destination identifiers in the message is the destination index corresponding to the destination identifier.

The LCG ID is used for indicating a logic channel group corresponding to the buffer data volume reported later.

The total data of all logical channels in the corresponding logical channel group of the corresponding destination is buffered.

Extended indicator bit (bit) E: indicating whether the following fields are LCG ID and buffer size fields or destination index fields. For example, if the next field is the LCG ID and buffer size, E is 1, and if the next field is the destination index field, E is 0.

Fig. 17 shows another format of the SL BSR according to the embodiment of the present application. Fig. 17 gives an example of a format of the SL BSR, taking as an example that the destination index field is 5 bits in length, the buffer size field is 8 bits in length, and the LCG ID field is 3 bits in length.

Fig. 18 is a schematic flowchart of reporting a sidelink buffer status report according to an embodiment of the present disclosure.

In step S1801, the first user equipment sends a SL BSR to the first network equipment.

Optionally, the SL BSR has the fields described above.

Optionally, before step S1801, the first user equipment generates a SL BSR.

Optionally, the first network device receives and processes the SL BSR.

Method embodiments of the present application are described above in conjunction with fig. 1-18, and apparatus embodiments of the present application are described below in conjunction with fig. 19-26. It is to be understood that the description of the method embodiments corresponds to the description of the apparatus embodiments, and therefore reference may be made to the preceding method embodiments for parts not described in detail.

Fig. 19 is a schematic structural diagram of a user equipment provided in an embodiment of the present application. The user equipment UE 1900 may be used to implement the steps performed by the first UE in the description of fig. 7 above.

The UE 1900 includes a first transmit module 1910. The first sending module 1910 is configured to send a first message to a first network device, where the first message includes first quality of service, QoS, information and first information. The first information comprises the mapping relation between the QoS information of the sidelink service and the target identification. The mapping relationship at least comprises a mapping relationship between first quality of service (QoS) information and a first sidelink radio bearer (SL RB), or a logical channel of the first SL RB and the first SL RB.

Optionally, the UE 1900 may further include a first receiving module, configured to receive a second message sent by the first network device, where the second message includes first configuration information of the first SL RB, and the first configuration information includes one or more of the following information: length of a packet data convergence protocol PDCP sequence number of the first SL RB, length of a radio link control RLC sequence number of the first SL RB, configuration information of a PDCP entity of the first SL RB, configuration information of an RLC entity of the first SL RB, and logical channel configuration information of the first SL RB.

Optionally, the UE 1900 may further include a first configuration module, configured to configure the first SL RB according to the first configuration information.

Optionally, the UE 1900 may further include a second sending module, configured to send a third message to the second UE after receiving the second message. The third message includes the first configuration information.

Optionally, the UE 1900 may further include a stopping module configured to stop transmission of data on the first SL RB after the UE receives the second message.

Optionally, the UE 1900 may further include a second receiving module, configured to receive a fourth message sent by the second UE, where the fourth message is used to indicate that the second UE has configured the first SL RB according to the first configuration information.

Optionally, the UE 1900 may further include a recovery module for recovering transmission of data on the first SL RB. The recovery module may recover transmission of data on the first SL RB after the UE receives the fourth message sent by the second UE.

Optionally, the first message and the second message further include destination information corresponding to the first SL RB.

Optionally, the first SL RB is an established SL RB of the first UE.

Optionally, the first message further includes second configuration information of the first SL RB, where the second configuration information includes one or more of the following information: a length of a Packet Data Convergence Protocol (PDCP) sequence number of the first SL RB, a length of a Radio Link Control (RLC) sequence number of the first SL RB, configuration information of a PDCP entity of the first SL RB, configuration information of an RLC entity of the first SL RB, and logical channel configuration information of the first SL RB.

Optionally, the first information includes mapping relationships between all QoS information preconfigured by the first UE and SL RBs.

Fig. 20 is a schematic structural diagram of a network device according to an embodiment of the present application. The user equipment UE 2000 may be configured to implement the steps performed by the network device in the description of fig. 6-8 above. The UE 2000 includes a first receiving module 2010, a determining module 2020.

The first receiving module 2010 is configured to receive a first message sent by a first user equipment UE, where the first message includes first quality of service QoS information.

The determining module is used for determining the target identifier mapped by the first QoS information according to the first QoS information and the first information of the first UE. The first information comprises a mapping relation between QoS information of side link service and a target identifier, and the mapping relation at least comprises a mapping relation between first quality of service QoS information and a first side link radio bearer SL RB identifier, or a logical channel identifier of a first SL RB, or a mapping relation between the first side link radio bearer SL RB identifier and the logical channel identifier of the first SL RB.

Optionally, the network device 2000 may further include a first sending module, configured to send a second message to the first UE, where the second message includes first configuration information of the first SL RB, and the first configuration information includes one or more of the following information: length of a packet data convergence protocol PDCP sequence number of the first SL RB, length of a radio link control RLC sequence number of the first SL RB, configuration information of a PDCP entity of the first SL RB, configuration information of an RLC entity of the first SL RB, and logical channel configuration information of the first SL RB.

Optionally, the first message and/or the second message further include destination information corresponding to the first SL RB.

Optionally, the first information is sent to the first network device by the first UE or the core network device.

Optionally, the first SL RB is an established SL RB of the first UE.

Optionally, the first message further includes second configuration information of the first SL RB. The second configuration information may include one or more of the following information: a length of a Packet Data Convergence Protocol (PDCP) sequence number of the first SL RB, a length of a Radio Link Control (RLC) sequence number of the first SL RB, configuration information of a PDCP entity of the first SL RB, configuration information of an RLC entity of the first SL RB, and logical channel configuration information of the first SL RB.

Fig. 21 is a schematic structural diagram of a user equipment provided in an embodiment of the present application. The UE 2100 may be used to implement the steps performed by the first UE in the description of fig. 9-10 above. The UE 2100 includes a first receiving module 2110 and a first transmitting module 2120.

The user equipment stores a mapping rule for mapping the service quality QoS information of the side link service between the user equipment UE and the second UE to the side link radio bearer SL RB, wherein the mapping rule at least comprises a first mapping rule, and the first mapping rule is that the first QoS information is mapped to the first side link radio bearer SL RB.

A first receiving module 2120, where the communication module is configured to receive a first message sent by a network device; the first message comprises first indication information indicating that the sidelink radio bearer mapped by the first QoS information is a second SL RB;

a first sending module 2130, configured to send a second message to the second UE, where the second message includes second indication information, and the second indication information is used to indicate that the first QoS information is not mapped to the first SL RB.

Optionally, the UE 2100 may further include a second sending module, configured to receive a third message sent by the second UE, where the third message is a response message of the second message.

Optionally, the UE 2100 may further include a third sending module, configured to send, to the second UE, a control protocol data unit PDU corresponding to the first QoS information by using the first SL RB after the communication module receives a third message, where the control PDU is used to indicate that transmission of data corresponding to the first QoS information ends on the first SL RB.

Optionally, the UE 2100 may further include a second storing module, configured to store a second mapping rule of the first QoS information between the second UE and the communication module after the communication module sends the control PDU corresponding to the first QoS information to the second UE by using the first SL RB, where the second mapping rule is that the first QoS information is mapped to the second SL RB.

Optionally, the UE 2100 may further include a third sending module, configured to send the PDU and/or the service data unit SDU corresponding to the first QoS information through the second SL RB.

Optionally, the second indication information indicates that the sidelink radio bearer mapped by the first QoS information is a second SL RB.

Optionally, the first message and the second message further include configuration information of the second SL RB.

Optionally, the first message and the second message further include destination information corresponding to the second SL RB.

Fig. 22 is a schematic structural diagram of a user equipment provided in an embodiment of the present application. The user equipment UE 2200 may be configured to implement the steps performed by the second UE in the description of fig. 9-10 above. The UE 2200 includes a first saving module 2210, a first receiving module 2220.

The first saving module 2210 is configured to save a mapping rule that QoS information of a sidelink service between the first UE and the second UE is mapped to a sidelink radio bearer SL RB, where the mapping rule at least includes a first mapping rule, and the first mapping rule is that the first QoS information is mapped to the first sidelink radio bearer SL RB;

a first receiving module 2220 is configured to receive a second message sent by the first UE; the second message includes second indication information indicating that the first QoS information is not mapped to the first SL RB.

Optionally, the UE 2200 may further include a first sending module, configured to send a third message to the first UE, where the third message is a response message of the second message.

Optionally, the UE 2200 may further include a buffering module configured to buffer the received at least one protocol data unit PDU and/or service data unit SDU from the non-first SL RB sent by the first UE.

Optionally, the UE 2200 may further include a second receiving module for receiving the control PDU. The control PDU is used for indicating the end of the data transmission corresponding to the QoS information on the first SL RB.

Optionally, the UE 2200 may further include a delivering module further configured to deliver the at least one PDU and/or SDU buffered in the buffering module to an upper layer of the UE.

Optionally, the second indication information includes a mapping relationship of the QoS information and the second SL RB.

Fig. 23 is a schematic structural diagram of a user equipment provided in an embodiment of the present application. User equipment UE 2300 may be used to implement the steps performed by the first UE in the description of fig. 11-12 above. The UE 2300 includes a first transmitting module 2310, a transmitting module 2320.

The user equipment stores the mapping relation between the service quality QoS information of the side link service between the user equipment UE and the second UE and the first side link radio bearer SL RB;

a first sending module 2310, configured to receive a first message sent by a network device, where the first message includes configuration information of a second SL RB mapped by the QoS information;

a first transmission module 2320, if the identity of the first SL RB and/or the identity of the logical channel of the first SL RB is different from the identity of the second SL RB and/or the identity of the logical channel of the second SL RB, the transmission module is configured to transmit a packet corresponding to the QoS information mapped onto the first SL RB through the second SL RB.

Optionally, the first transmission module is configured to: if the SL RB identities of the first SL RB and the second SL RB are different and the operating mode of the radio link control RLC of the first SL RB is unacknowledged mode UM, the processing module is configured to submit a first PDCP service data unit SDU corresponding to the QoS information on the packet data convergence protocol PDCP entity mapped to the first SL RB to the PDCP entity of the second SL RB, where the first PDCP SDU includes a PDCP SDU which has been associated with a sequence number by the PDCP entity of the first SL RB and has not been submitted to the RLC entity of the first SL RB; if the SL RB identifiers of the first SL RB and the second SL RB are different and the RLC operating mode of the first SL RB is acknowledged mode AM, the processing module is configured to deliver a second PDCP SDU corresponding to the QoS information mapped to the PDCP entity of the first SL RB to the PDCP entity of the second SL RB, where the second PDCP SDU includes a PDCP SDU corresponding to a first PDCP protocol data unit PDU and subsequent PDCP SDUs that are not acknowledged by the RLC entity of the first SL RB and received successfully.

Optionally, the UE 2300 may further include a first releasing module configured to release the PDCP entity of the first SL RB.

Optionally, the UE 2300 may further include a second releasing module configured to release the RLC entity of the first SL RB if the logical channel identity of the first SL RB is different from the logical channel identity of the second SL RB.

Optionally, the UE 2300 may further include a discarding module for discarding the service data unit SDU and the protocol data unit PDU in the RLC entity of the first SL RB if the logical channel identity of the first SL RB is the same as the logical channel identity of the second SL RB.

Optionally, the UE 2300 may further include a second releasing module configured to release the radio link control RLC bearer of the first SL RB.

Fig. 24 is a schematic structural diagram of a user equipment provided in an embodiment of the present application. User equipment UE 2400 may be used to implement the steps performed by the UE in the description of fig. 13 above. The UE 2400 includes a first transmitting module 2410, a first receiving module 2420, and a homing module 2430.

A first sending module 2410, configured to send a first message to a network device, where the first message includes quality of service QoS information of a sidelink service;

a first receiving module 2420, configured to receive a second message sent by the network device, where the second message includes the LCG information of the logical channel group corresponding to the QoS information;

a attributing module 2430, where the UE attributing the logical channel of the SL RB corresponding to the QoS information to the LCG corresponding to the LCG information.

Fig. 25 is a schematic structural diagram of a network device according to an embodiment of the present application. Network device 2500 may be used to implement the steps performed by the network device in the description of fig. 13 above. The network device 2500 includes a first receiving module 2510, a first transmitting module 2520.

A first receiving module 2510, configured to receive a first message sent by a user equipment UE, where the first message includes quality of service QoS information of a sidelink service;

a first sending module 2520, configured to send a second message to the UE, where the second message includes a logical channel group LCG information corresponding to the QoS information; the second message is used for instructing the UE to attribute the logic channel of the SL RB corresponding to the QoS information to the LCG corresponding to the LCG information.

Fig. 26 is a schematic structural diagram of a communication device according to an embodiment of the present application. The communication device 2600 shown in fig. 26 may correspond to a user equipment or a network equipment as described previously. The communication device 2100 may comprise: at least one processor 2610 and a communication interface 2620, the communication interface 2620 being operable to enable the communication device 2600 to interact with other communication devices in information, the program instructions when executed in the at least one processor 2610 causing the communication device 2600 to perform the various steps or methods or operations or functions previously performed by any one of the following: user equipment, network equipment.

An embodiment of the present application further provides a communication system, which includes the foregoing network device and one or more user devices.

Embodiments of the present application further provide a computer program storage medium, which is characterized in that the computer program storage medium has program instructions, and when the program instructions are directly or indirectly executed, the functions of the method in the foregoing are implemented on any one of the following devices: network equipment and user equipment.

An embodiment of the present application further provides a chip system, where the chip system includes at least one processor, and when the program instructions are executed in the at least one processor, the functions of the method in the foregoing are implemented on any one of the following apparatuses: network equipment and user equipment.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the embodiments of the present application, "at least one" means one or more, "a plurality" means two or more. "and/or" describes the association relationship of the associated objects, and means that there may be three relationships, for example, a and/or B, and may mean that a exists alone, a and B exist simultaneously, and B exists alone. Wherein A and B can be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one of the following" and similar expressions refer to any combination of these items, including any combination of singular or plural items. For example, at least one of a, b, and c may represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein a, b, c may be single or multiple. It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method of wireless communication, comprising:

the first UE sends a first message to a first network device, wherein the first message comprises first QoS information and first information, the first information comprises a mapping relation between QoS information of a sidelink service and a target identifier, and the mapping relation at least comprises the mapping relation between the first QoS information and a first SL RB, or a logical channel of the first SL RB and the first SL RB.

2. The method of claim 1, further comprising,

the first UE receives a second message sent by the first network device, wherein the second message includes first configuration information of the first SL RB, and the first configuration information includes one or more of the following information: a length of a Packet Data Convergence Protocol (PDCP) sequence number of the first SL RB, a length of a Radio Link Control (RLC) sequence number of the first SL RB, configuration information of a PDCP entity of the first SL RB, configuration information of an RLC entity of the first SL RB, and logical channel configuration information of the first SL RB;

and the first UE configures the first SL RB according to the first configuration information.

3. The method of claim 2, further comprising:

and after receiving the second message, the first UE sends a third message to a second UE, wherein the third message comprises the first configuration information.

4. The method of claim 3, further comprising:

stopping transmission of data on the first SL RB after the first UE receives the second message;

and the first UE receives a fourth message sent by the second UE and recovers transmission of data on the first SL RB, wherein the fourth message is used for indicating that the second UE has configured the first SL RB according to the first configuration information.

5. The method of any of claims 2-4, wherein the first and second messages further comprise destination information corresponding to the first SL RB.

6. The method of any of claims 1-4, wherein the first SL RB is an SL RB that the first UE has established.

7. The method of any of claims 1-4, wherein the first message further comprises second configuration information for the first SL RB, wherein the second configuration information comprises one or more of the following information: a length of a Packet Data Convergence Protocol (PDCP) sequence number of the first SL RB, a length of a Radio Link Control (RLC) sequence number of the first SL RB, configuration information of a PDCP entity of the first SL RB, configuration information of an RLC entity of the first SL RB, and logical channel configuration information of the first SL RB.

8. The method of any of claims 1-4, wherein the first information comprises a mapping relationship of all QoS information pre-configured by the first UE to SL RBs.

9. A method of wireless communication, comprising:

the method comprises the steps that first network equipment receives a first message sent by first UE, wherein the first message comprises first QoS information;

the first network equipment determines a target identifier mapped by the first QoS information according to the first QoS information and first information of a first UE, wherein the first information comprises a mapping relation between the QoS information of a sidelink service and the target identifier, and the mapping relation at least comprises the mapping relation between the first QoS information and a first SL RB, or a logical channel of the first SL RB and the first SL RB.

10. The method of claim 9, further comprising:

the first network device sends a second message to the first UE, the second message including first configuration information of the first SL RB, the first configuration information including one or more of the following information: a length of a Packet Data Convergence Protocol (PDCP) sequence number of the first SL RB, a length of a Radio Link Control (RLC) sequence number of the first SL RB, configuration information of a PDCP entity of the first SL RB, configuration information of an RLC entity of the first SL RB, and logical channel configuration information of the first SL RB.

11. The method of claim 9 or 10, wherein the first message and the second message further comprise destination information corresponding to the first SL RB.

12. The method according to claim 9 or 10, wherein the first information is sent to the first network device by the first UE or a core network device.

13. The method of claim 9 or 10, wherein the first SL RB is an SL RB that has been established by the first UE.

14. The method of claim 9 or 10, wherein the first message further comprises second configuration information of the first SL RB, and wherein the second configuration information comprises one or more of the following information: a length of a Packet Data Convergence Protocol (PDCP) sequence number of the first SL RB, a length of a Radio Link Control (RLC) sequence number of the first SL RB, configuration information of a PDCP entity of the first SL RB, configuration information of an RLC entity of the first SL RB, and logical channel configuration information of the first SL RB.

15. A user equipment comprising means for performing the method of any of claims 1 to 8.

16. A network device comprising means for performing the method of any of claims 9 to 14.

17. A communication apparatus, characterized in that the communication apparatus comprises: at least one processor and a communication interface for the communication device to interact with other communication devices, the program instructions, when executed in the at least one processor, causing the communication device to implement the functionality of the method of any one of claims 1 to 14 on any one of: the first user equipment and the first network equipment.

18. A computer program storage medium having program instructions which, when executed directly or indirectly, cause functions in a method as claimed in any one of claims 1 to 14 to be carried out on any one of: the first user equipment and the first network equipment.

19. A chip system, characterized in that the chip system comprises at least one processor, which when program instructions are executed in the at least one processor causes the functions in the method according to any of claims 1 to 14 to be implemented on any of the following means: the first user equipment and the first network equipment.