CN114830803B

CN114830803B - A side link communication method and device

Info

Publication number: CN114830803B
Application number: CN201980103025.5A
Authority: CN
Inventors: 李翔宇; 王君; 徐海博; 戴明增
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2019-12-26
Filing date: 2019-12-26
Publication date: 2025-06-03
Anticipated expiration: 2039-12-26
Also published as: CN114830803A; WO2021128218A1

Abstract

A sidelink communication method and apparatus, wherein the method includes: after a first terminal device determines that a first QoS flow is remapped to a second SLRB, the SDAP entity of the first terminal device may stop sending data packets of the first QoS flow on the first SLRB, and cache the data packets of the first QoS flow in an SDAP buffer within a first preset time after stopping sending data packets of the first QoS flow on the first SLRB, and then send the cached data packets of the first QoS flow on the second SLRB after the first preset time. In this way, the data packets transmitted through the second SLRB can arrive after the data packets transmitted through the first SLRB, thereby effectively ensuring that the SDAP layer on the receiving side can deliver the data packets of the first QoS flow to the upper layer in order.

Description

Side-link communication method and device

Technical Field

The present application relates to the field of wireless communications technologies, and in particular, to a method and an apparatus for side uplink communications.

Background

In a network of vehicles (vehicle to everything, V2X) communication system, a PC5 quality of service flow (PC 5 quality of service flow, PC5 QoS flow) is associated with a PC5 quality of service rule (PC 5 quality of service rule, PC5 QoS rule). The V2X layer of the terminal device may map the side-link packets (V2X packets) issued by the application layer to corresponding PC5 QoS flows according to the configured PC5 QoS rules, and then send the mapped packets to the service data adaptation (SERVICE DATA adaptation protocol, SDAP) layer.

At the SDAP layer, the SDAP entity can map the side-uplink packets in the PC5 QoS flows onto corresponding SLRB according to a mapping relationship between the PC5 QoS flows and the side-uplink radio bearers (side link radio bearer, SLRB) configured by the network device.

In the prior art, when SLRB configuration acquired by the transmitting end changes, the mapping relationship between the PC5 QoS flows and SLRB may also change. If the mapping relationship between a QoS flow and SLRB of a PC5 changes immediately from mapping to the source SLRB to mapping to the destination SLRB, due to some packets in the source SLRB being retransmitted or not being transmitted in time, some packets sent by the source SLRB may reach the receiving end after the packets sent by the destination SLRB, which may cause the SDAP layer of the receiving end to be unable to deliver the packets of the QoS flow in sequence when delivering the packets to the upper layer.

Disclosure of Invention

The embodiment of the application provides a side uplink communication method and a device, which are used for ensuring that data packets of a remapped QoS flow can be submitted in sequence at a receiving side.

In a first aspect, an embodiment of the present application provides a method for side-link communication, where the method may be applied to a first terminal device, where the method includes the terminal device sending data of a first QoS flow on a first side-link radio bearer SLRB, the first terminal device obtaining configuration information of a second SLRB, where the configuration information of the second SLRB indicates that the first QoS flow is remapped to the second SLRB, the service data adaptation layer SDAP entity of the first terminal device stopping sending data packets of the first QoS flow on the first SLRB, and buffering the data packets of the first QoS flow in an SDAP buffer for a first preset time period after stopping sending the data packets of the first QoS flow on the first SLRB, and after the first preset time period passes, the first terminal device sending the data packets of the first QoS flow buffered in the SDAP buffer on the second SLRB.

In the embodiment of the present application, after determining that the first QoS flow needs to be remapped to the second SLRB, the first terminal device may stop submitting the data of the first QoS flow to the first SLRB for transmission, buffer the data packet of the first QoS flow in the SDAP buffer, and send the data packet of the first QoS flow buffered in the SDAP buffer on the second SLRB after a first preset period of time. As can be seen, by setting the first preset duration, the data packet of the first QoS flow that has been previously delivered to the first SLRB for transmission can be completed during the period of time within the first preset duration after the data of the first QoS flow is stopped from being delivered to the first SLRB. After a first preset time period, the buffered data packets of the first QoS flow are submitted to the second SLRB for transmission, so that the data packets transmitted through the second SLRB can arrive after the data packets transmitted through the first SLRB, and therefore the SDAP layer at the receiving side can be effectively ensured to be capable of sequentially submitting the data packets of the first QoS flow to the upper layer.

With reference to the first aspect, in one possible design of the first aspect, the SDAP entity of the first terminal device may immediately stop sending the data packet of the first QoS flow on the first SLRB after the first terminal device obtains the configuration information of the second SLRB. Or the SDAP entity of the first terminal device can stop sending the data packet of the first QoS flow on the first SLRB after the first terminal device obtains the configuration information of the second SLRB for a second preset time period, so that service continuity can be ensured.

With reference to the first aspect, in one possible design of the first aspect, the first terminal device may establish the second SLRB according to the configuration information of the second SLRB, so as to facilitate remapping the first QoS flow onto the second SLRB.

With reference to the first aspect, in one possible design of the first aspect, the first terminal device may release the first SLRB after stopping sending the data packet of the first QoS flow on the first SLRB for a first preset period of time.

In a second aspect, an embodiment of the present application provides a method for side-link communication, where the method may be applied to a second terminal device, where the method includes the second terminal device receiving data of a first quality of service QoS flow on a first side-link radio bearer SLRB, the second terminal device receiving configuration information of a second SLRB from the first terminal device, where the configuration information of the second SLRB indicates that the first QoS flow is remapped to the second SLRB, the second terminal device buffering a data packet received from the second SLRB in a service data adaptation layer SDAP buffer within a third preset time period after receiving the configuration information of the second SLRB, and after the third preset time period, delivering, by an SDAP entity of the second terminal device, the data packet received from the second SLRB buffered in the SDAP buffer to an upper layer for processing.

In the embodiment of the present application, the SDAP entity of the second terminal device may buffer the data packet received from the second SLRB in the SDAP buffer within a third preset duration after determining that the first QoS flow needs to be remapped. And after the third preset time period is over, delivering the cached data packet received from the second SLRB to an upper layer for processing. In this way, the SDAP layer of the second terminal device may further continue to receive the data packet of the first QoS flow from the first SLRB and submit the data packet to the upper layer for processing within a third preset duration after the second terminal device determines that the remapping of the first QoS flow needs to occur. After the third preset time period is over, the SDAP layer of the second terminal device submits the data packet received on the second SLRB to the upper layer, so that the SDAP layer submits the data packet of the first QoS flow received from the first SLRB to the upper layer for processing, and then submits the data packet of the first QoS flow received from the second SLRB, thereby ensuring that the SDAP layer of the second terminal device can submit the data packet of the first QoS flow in sequence.

With reference to the second aspect, in one possible design of the second aspect, the second terminal device may establish the second SLRB according to the second SLRB configuration information, so as to facilitate remapping the first QoS flow onto the second SLRB.

With reference to the second aspect, in one possible design of the second aspect, after a third preset period of time, the second terminal device may release the first SLRB.

In a third aspect, an embodiment of the present application provides a method for side-link communication, where the method is applicable to a first terminal device, where the method includes the first terminal device sending data of a first quality of service QoS flow on a first side-link radio bearer SLRB, the first terminal device obtaining configuration information of a second SLRB, where the configuration information of the second SLRB indicates that the first QoS flow is remapped to the second SLRB, and the first terminal device releasing the first SLRB after a fourth preset time period after obtaining the configuration information of the second SLRB.

In the embodiment of the present application, after determining that the first QoS flow needs to be remapped to the second SLRB, the first terminal device may not immediately release the first SLRB, and may release the first SLRB after a fourth preset period of time. Therefore, under the condition that the first QoS flow is remapped, the data packet which is submitted to the first SLRB before the remapping and transmitted can be sent to the second terminal equipment, so that the service continuity is ensured.

With reference to the third aspect, in one possible design of the third aspect, the first terminal device may establish the second SLRB according to the configuration information of the second SLRB, so as to facilitate remapping the first QoS flow onto the second SLRB.

With reference to the third aspect, in one possible design of the third aspect, the service data adaptation layer SDAP entity of the first terminal device may send a data packet of the first QoS flow on the second SLRB after a fourth preset duration.

In a fourth aspect, embodiments of the present application provide a communication apparatus having a function of implementing the terminal device in any one of the possible designs of the first aspect or the first aspect, or having a function of implementing the terminal device in any one of the possible designs of the second aspect or the second aspect, or having a function of implementing the terminal device in any one of the possible designs of the third aspect or the third aspect. The device may be a terminal device, for example, a handheld terminal device, a vehicle-mounted terminal device, a vehicle user device, a road side unit, or the like, or may be a device included in a terminal device, for example, a chip, or may be a device including a terminal device. The functions of the terminal device may be implemented by hardware, or may be implemented by executing corresponding software by hardware, where the hardware or software includes one or more modules corresponding to the functions.

In one possible design, the structure of the apparatus includes a processing module and a transceiver module, where the processing module is configured to support the apparatus to perform the function corresponding to the terminal device in the first aspect or any of the designs of the first aspect, or perform the function corresponding to the terminal device in the second aspect or any of the designs of the second aspect, or perform the function corresponding to the terminal device in the third aspect or any of the designs of the third aspect. The transceiver module is configured to support communication between the apparatus and other communication devices, for example, when the apparatus is a terminal device, the apparatus may transmit side uplink information to another terminal device. The communication device may also include a memory module coupled to the processing module that holds the program instructions and data necessary for the device. As an example, the processing module may be a processor, the communication module may be a transceiver, and the storage module may be a memory, where the memory may be integrated with the processor or may be separately provided from the processor, and the present application is not limited thereto.

In another possible design, the device may include a processor and may also include a memory. The processor is coupled to the memory and operable to execute computer program instructions stored in the memory to cause the apparatus to perform the method of the first aspect, or any of the possible designs of the first aspect, or to perform the method of the second aspect, or any of the designs of the third aspect. Optionally, the apparatus further comprises a communication interface, the processor being coupled to the communication interface. The communication interface may be a transceiver or an input/output interface when the apparatus is a terminal device, or an input/output interface of a chip when the apparatus is a chip included in a terminal device. Alternatively, the transceiver may be a transceiver circuit and the input/output interface may be an input/output circuit.

In a fifth aspect, embodiments of the present application provide a chip system comprising a processor coupled to a memory for storing a program or instructions that, when executed by the processor, cause the chip system to implement a method in any one of the possible designs of the first aspect or the first aspect, or to implement a method in any one of the possible designs of the second aspect or the second aspect, or to implement a method in any one of the possible designs of the third aspect or the third aspect.

Optionally, the system on a chip further comprises an interface circuit for interacting code instructions to the processor.

Alternatively, the processor in the chip system may be one or more, and the processor may be implemented by hardware or software. When implemented in hardware, the processor may be a logic circuit, an integrated circuit, or the like. When implemented in software, the processor may be a general purpose processor, implemented by reading software code stored in a memory.

Alternatively, the memory in the system-on-chip may be one or more. The memory may be integral with the processor or separate from the processor, and the application is not limited. The memory may be a non-transitory processor, such as a ROM, which may be integrated on the same chip as the processor, or may be separately provided on different chips, and the type of memory and the manner of providing the memory and the processor are not particularly limited in the present application.

In a sixth aspect, embodiments of the present application provide a computer readable storage medium having stored thereon a computer program or instructions which, when executed, cause a computer to perform the method of the first aspect or any of the possible designs of the first aspect, or the method of the second aspect or any of the possible designs of the second aspect, or the method of the third aspect or any of the possible designs of the third aspect.

In a seventh aspect, embodiments of the present application provide a computer program product which, when read and executed by a computer, causes the computer to perform the method of or the third aspect of any of the possible designs of the first or second aspect.

In an eighth aspect, an embodiment of the present application provides a communication system including a first terminal device and a second terminal device.

Drawings

Fig. 1 is a schematic diagram of a network architecture of a communication system to which an embodiment of the present application is applicable;

Fig. 2 is a schematic diagram of a PC5 QoS model according to an embodiment of the present application;

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

fig. 4 is a schematic diagram of QoS flow remapping according to an embodiment of the present application;

Fig. 5 is a schematic diagram of one possible implementation of stopping delivery of a packet of a first QoS flow to a first SLRB transmission according to an embodiment of the present application;

fig. 6 is a schematic diagram of another possible implementation manner of stopping delivery of a packet of a first QoS flow to a first SLRB transmission according to an embodiment of the present application;

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

FIG. 8 is a schematic diagram of a third preset duration in an embodiment of the present application;

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

FIG. 10 is a schematic diagram of a fourth preset duration in an embodiment of the present application;

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

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

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present application more apparent, the embodiments of the present application will be described in further detail with reference to the accompanying drawings.

The technical scheme of the embodiment of the application can be applied to various communication systems, such as a global system for mobile communication (global system for mobile communications, GSM) system, a code division multiple access (code division multiple access, CDMA) system, a wideband code division multiple access (wideband code division multiple access, WCDMA) system, a general packet radio service (GENERAL PACKET radio service, GPRS), a long term evolution (long term evolution, LTE) system, an LTE frequency division duplex (frequency division duplex, FDD) system, an LTE time division duplex (time division duplex, TDD), a universal mobile communication system (universal mobile telecommunication system, UMTS), a worldwide interoperability for microwave access (worldwide interoperability for microwave access, WIMAX) communication system, a fifth generation (5th generation,5G) system or a New Radio (NR) system, or a future communication system or other similar communication system.

The technical scheme of the embodiment of the application can be applied to the technical fields of unmanned driving (unmanned driving), auxiliary driving (DRIVER ASSISTANCE, ADAS), intelligent driving (INTELLIGENT DRIVING), internet-connected driving (connected driving), intelligent internet-connected driving (INTELLIGENT NETWORK DRIVING), automobile sharing (CAR SHARING), intelligent automobile (smart/INTELLIGENT CAR), digital automobile (DIGITAL CAT), unmanned automobile (unmanned car/DRIVERLESS CAR/pilotless car/automobile), internet of vehicles (Internet of vehicles, ioV), automatic automobile (self-DRIVING CAR, automatic monarch), road cooperation (cooperative vehicle infrastructure, CVIS), intelligent traffic (INTELLIGENT TRANSPORT SYSTEM, ITS), vehicle-mounted communication (vehicular communication) and the like.

In addition, the technical scheme provided by the embodiment of the application can be applied to a cellular link and also can be applied to a link between devices, such as a device-to-device (D2D) link. The D2D link or V2X link may also be referred to as a side link, secondary link, or routine link, etc. In the embodiment of the present application, the above terms refer to links established between devices of the same type, and the meanings of the links are the same. The same type of device may be a link between terminal devices, a link between base stations, a link between relay nodes, or the like, which is not limited in the embodiment of the present application.

Fig. 1 is a schematic diagram of a network architecture of a communication system according to an embodiment of the present application. The communication system comprises a terminal device 110, a terminal device 120 and a network device 130. The network device may communicate with at least one terminal device (e.g., terminal device 110) via an Uplink (UL) and a Downlink (DL), and the communication interface between the network device and the terminal device is a Uu interface. A terminal device may communicate with another terminal device via a Sidelink (SL), where the communication interface between the terminal device and the terminal device is a PC5 interface, and a routine link may also be understood as a direct communication link between the terminal devices.

The sidelink-based communication may use at least one of a physical sidelink shared channel (PHYSICAL SIDELINK SHARED CHANNEL, PSSCH) for carrying sidelink data information, a physical sidelink control channel (PHYSICAL SIDELINK control channel, PSCCH) for carrying sidelink control information (sidelink control information, SCI), and a physical sidelink feedback channel (PHYSICAL SIDELINK feedback channel, PSFCH) for carrying sidelink HARQ feedback information.

The network device in fig. 1 may be an access network device, such as a base station. The access network device may correspond to different devices in different systems, for example, eNB in the fourth generation mobile communication technology (the 4 ^th generation, 4G) system, and may correspond to an access network device in 5G, for example, gNB in the 5G system. The technical scheme provided by the embodiment of the application can also be applied to future mobile communication systems, such as 6G or 7G communication systems, so that the network equipment in the figure 1 can also correspond to access network equipment in the future mobile communication systems.

It should be understood that there may be multiple network devices in the communication system, where each network device may provide services for multiple terminal devices, and the number of network devices and terminal devices in the communication system is not limited in the embodiments of the present application. The network device in fig. 1, and some or all of the plurality of terminal devices may implement the technical solution provided by the embodiments of the present application. In addition, the terminal device in fig. 1 is described by taking an in-vehicle terminal device or a vehicle as an example, and it should be understood that the terminal device in the embodiment of the present application is not limited thereto. The terminal device can also be a mobile phone, a vehicle-mounted device, a vehicle-mounted module, a road side unit, a pedestrian handheld device, and a mass machine type Communication (MASSIVE MACHINE TYPE of Communication, mMTC) terminal device such as an intelligent water meter, an electric meter and the like in the internet of things.

In the following, some terms in the embodiments of the present application are explained for easy understanding by those skilled in the art.

1) A terminal device, which may also be referred to as a User Equipment (UE), a Mobile Station (MS), a Mobile Terminal (MT), etc., is a device that provides voice and/or data connectivity to a user. The terminal device may communicate with the core network via a radio access network (radio access network, RAN) to exchange voice and/or data with the RAN. For example, the terminal device may be a handheld device having a wireless connection function, an in-vehicle device, a vehicle user device, or the like. Currently, examples of some terminal devices are mobile phones, tablet computers, notebook computers, palm computers, mobile internet devices (mobile INTEMET DEVICE, MID), wearable devices, virtual Reality (VR) devices, augmented reality (augmented reality, AR) devices, wireless terminals in industrial control (industrial control), wireless terminals in unmanned (SELF DRIVING), wireless terminals in tele-surgery (remote medical surgery), wireless terminals in smart grid (SMART GRID), wireless terminals in transportation security (transportation safety), wireless terminals in smart city (SMART CITY), wireless terminals in smart home (smart home), etc.

By way of example, and not limitation, in embodiments of the present application, the terminal device may also be a wearable device. The wearable device can also be called as a wearable intelligent device or an intelligent wearable device, and is a generic name for intelligently designing daily wear and developing wearable devices, such as glasses, gloves, watches, clothes, shoes, and the like, by applying wearable technology. The wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also can realize a powerful function through software support, data interaction and cloud interaction. The generalized wearable intelligent device comprises full functions, large size and complete or partial functions which can be realized independently of a smart phone, such as a smart watch, a smart glasses and the like, and is only focused on certain application functions, and needs to be matched with other devices such as the smart phone for use, such as various smart bracelets, smart helmets, smart jewelry and the like for physical sign monitoring.

The terminal device in the embodiment of the application may also be a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit which are built in a vehicle as one or more components or units, and the vehicle may implement the method of the application through the built-in vehicle-mounted module, vehicle-mounted component, vehicle-mounted chip or vehicle-mounted unit.

2) The network device is a device in a network for accessing a terminal device to a wireless network. The network device may be a node in a radio access network, also referred to as a base station, and also referred to as a radio access network (radio access network, RAN) node (or device). The network device may be operable to inter-convert the received air frames with Internet Protocol (IP) packets as a router between the terminal device and the rest of the access network, which may include an IP network. The network device may also coordinate attribute management for the air interface. For example, the network device may include an evolved base station (NodeB or eNB or e-NodeB, evolutional Node B) in a long term evolution (long term evolution, LTE) system or an evolved LTE system (LTE-Advanced, LTE-a), such as a conventional macro base station eNB and a micro base station eNB in a heterogeneous network scenario, or may also include a next generation Node B (next generation Node B, gNB) in a New Radio (NR) system of a fifth generation mobile communication technology (5th generation,5G), or may further include a transmission receiving point (transmission reception point, TRP), a home base station (e.g., home evolved NodeB, or home Node B, HNB), a baseband unit (BBU), a baseband pool BBU pool, or a WiFi Access Point (AP), or may further include a centralized unit (centralized unit, CU) and a Distributed Unit (DU) in a cloud access network (cloud radio access network, cloudRAN) system, and the embodiment of the present application is not limited. As another example, a network device in V2X technology is a Road Side Unit (RSU), which may be a fixed infrastructure entity supporting V2X applications, and may exchange messages with other entities supporting V2X applications.

3) PC5 quality of service flows (PC 5 QoSflow), a PC5 QoS flow is associated with a PC5 quality of service flow identifier (PFI) (PC 5 QoS flow indicator), which is used to uniquely identify a QoS flow under a layer two destination address (destination L2 ID). Also, a PFI may be associated with a set of QoS profiles, which may include parameters such as PC5 interface 5G quality of service identification (PC 5 5G quality of service identifier,PQI), guaranteed traffic bit rate (guaranteed flow bit rate, GFBR), maximum traffic bit rate (maximum flow bit rate, MFBR), etc.

Referring to the QoS model shown in fig. 2, the V2X layer may receive V2X packets from the application layer, map the V2X packets into corresponding PC5 QoS flows according to the set PC5 QoSrules, and then send to the SDAP layer.

4) The service data is adapted to the SDAP, and is used for mapping the data packets in the PC5 QoS stream to the corresponding SLRB according to the mapping relation between the PC5 QoS stream and SLRB.

5) The side-link radio bearer SLRB is a bearer in layer two for transmitting and receiving side-link data, and includes a packet data convergence protocol (PACKET DATA convergence protocol, PDCP) entity, a radio link control (radio link control, RLC) entity, a Logical Channel (LCH), and the like. One SLRB is uniquely associated with a group (source L2 ID, destination L2 ID, cast type), where cast type may be unicast, multicast, or broadcast.

6) The terms "system" and "network" in embodiments of the application may be used interchangeably. "plurality" means two or more, and "plurality" may also be understood as "at least two" in this embodiment of the present application. "at least one" may be understood as one or more, for example as one, two or more. For example, including at least one means including one, two or more, and not limiting what is included. For example, at least one of A, B and C is included, then A, B, C, A and B, A and C, B and C, or A and B and C may be included. Likewise, the understanding of the description of "at least one" and the like is similar. "and/or" describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate that there are three cases of a alone, a and B together, and B alone. The character "/", unless otherwise specified, generally indicates that the associated object is an "or" relationship.

Unless stated to the contrary, the embodiments of the present application refer to ordinal terms such as "first," "second," etc., for distinguishing between multiple objects, and are not intended to limit the order, timing, priority, or importance of the multiple objects, nor are the descriptions of "first," "second," etc., to limit the objects to be different.

Example 1

Referring to fig. 3, a flow chart of a method for side uplink communication according to an embodiment of the present application is shown, and the method specifically includes the following steps:

in step S301, the first terminal device sends data of the first QoS flow on the first SLRB.

The first terminal device refers to a terminal device at a transmitting side, and the second terminal device refers to a terminal device at a receiving side, i.e. the first terminal device transmits data to the second terminal device through a side uplink communication link. The communication between the first terminal device and the second terminal device based on the sidelink communication link may be unicast, multicast or broadcast, and the present application is not limited thereto.

In the embodiment of the present application, the change of the mapping relationship between the PC5 QoS flows and SLRB may be referred to as that the remapping of the PC5 QoS flows occurs (PC 5 QoS flow remapping). The first QoS flow specifically refers to the PC5 QoS flow where remapping occurs.

As shown in fig. 4, before remapping occurs, the data of the first QoS flow is mapped to a first SLRB transmission, which first SLRB may also be referred to as source SLRB. Optionally, there may also be one or more other QoS flows mapped to the first SLRB transmission with the first QoS flow, such as the second QoS flow shown in fig. 4. After the remapping occurs, the data of the first QoS flow is changed from the original mapping to the first SLRB transmission to the second SLRB transmission, and the second SLRB may also be referred to as the target SLRB. Optionally, there may also be one or more other QoS flows that are mapped with the first QoS flow for transmission on the second SLRB, such as the third QoS flow shown in fig. 4.

It will be understood that the first terminal device described in step S301 sends the data of the first QoS flow on the first SLRB, which means that the first terminal device maps the data of the first QoS flow to the first SLRB for transmission before the remapping of the first QoS flow occurs.

In step S302, the first terminal device obtains configuration information of a second SLRB, where the configuration information of the second SLRB indicates that the first QoS flow is remapped to the second SLRB.

The configuration information of the second SLRB may include information for indicating the QoS flow corresponding to the second SLRB, for example, an identifier of the first QoS flow, where the identifier may be a QFI of the QoS flow, or other identifying information used to uniquely identify one QoS flow in the terminal device. In this manner, the first terminal device may determine that the first QoS flow needs to be remapped to the second SLRB according to the acquired configuration information of the second SLRB.

Optionally, the configuration information of the second SLRB may further include configuration parameters of the second SLRB, for example, configuration parameters of the PDCP entity, RLC entity, LCH, etc. in the second SLRB. In this way, the first terminal device may establish the second SLRB according to the received configuration information of the second SLRB. In one possible design, the first terminal device may establish the second SLRB before sending the buffered data packets of the first QoS flow on the second SLRB as described in step S304. For example, the second SLRB may be established immediately after the configuration information of the second SLRB is acquired, or the second SLRB may be established while the delivery of the data packet of the first QoS flow to the first SLRB is stopped.

In the embodiment of the present application, the first terminal device may acquire the latest SLRB configuration when the radio resource control (radio resource control, RRC) state or coverage (coverage) condition is changed, or when the RRC state or coverage condition is unchanged, but SLRB configuration is changed. The SLRB configuration includes configuration information of each SLRB currently available to the first terminal device, including configuration information of the second SLRB. The latest SLRB configuration may reflect the mapping relationship between the respective PC5 QoS flows and SLRB of the current first terminal device. The first terminal device may determine that the first QoS flow needs to be remapped to the second SLRB based on the resulting SLRB configuration.

It will be appreciated that when the RRC state or coverage of the first terminal device changes, the terminal device needs to acquire the latest SLRB configuration, since the SLRB configuration of the terminal device is typically different in different RRC states or coverage situations. If the SLRB configuration of the first terminal device changes, the mapping relationship between the PC5 QoS flows and SLRB of the first terminal device may also change. By obtaining the latest SLRB configuration, the first terminal device may determine the mapping relationship between each PC5 QoS flow and SLRB of the first terminal device after remapping.

Here, the RRC states may include an RRC CONNECTED state (rrc_connected), an RRC IDLE state (rrc_idle), and an RRC INACTIVE state (rrc_inactive), and the coverage refers to whether the terminal device is within a coverage area of the network device or outside a coverage area of the network device (out-of-coverage, OOC), and only the terminal device within the coverage area of the network device has various RRC states.

Further, the first terminal device may obtain the latest SLRB configuration according to the current RRC state or coverage condition. The first terminal device may receive the latest SLRB configuration from the network device via RRC dedicated signaling if the first terminal device is currently in RRC connected state, may receive the latest SLRB configuration from a system message block (system information block, SIB) broadcasted by the network device if the first terminal device is currently in RRC idle state or RRC inactive state, and may obtain the SLRB configuration of the pre-configuration (pre-configuraed) if the first terminal device is in OOC.

It should be noted that, in the embodiment of the present application, the change of the RRC state or coverage of the first terminal device may include a plurality of situations that the first terminal device transitions from OOC to RRC idle state, the first terminal device transitions from OOC or RRC idle state or RRC inactive state to RRC connected state, the first terminal device transitions from RRC connected state to OOC or RRC idle state or RRC inactive state, and the first terminal device transitions from RRC idle state or RRC inactive state to OOC.

The change in the configuration of SLRB may include various situations, such as the first terminal being in an RRC idle state or an RRC inactive state, the configuration of SLRB in the SIB of the network device or cell to which the first terminal is connected being changed, the first terminal being in an RRC idle state or an RRC inactive state, the configuration of SLRB in the SIB of two cells to which the first terminal is connected before and after cell reselection being different due to the first terminal performing cell reselection, the first terminal being in an RRC connected state, the configuration of SLRB indicated by RRC dedicated signaling by the network device or cell to which the first terminal is connected being changed, and the configuration of SLRB indicated by RRC dedicated signaling by the two cells to which the first terminal is connected before and after cell handover being different due to the first terminal performing cell handover.

In step S303, the SDAP entity of the first terminal device stops sending the data packet of the first QoS flow on the first SLRB, and buffers the data packet of the first QoS flow in the SDAP buffer within a first preset time period after stopping submitting the data packet of the first QoS flow to the first SLRB.

Step S304, after a first preset time period, the first terminal device sends the data packet of the first QoS flow cached in the SDAP buffer area on the second SLRB.

In the embodiment of the present application, after determining that the first QoS flow needs to be remapped to the second SLRB, the first terminal device may stop delivering the data of the first QoS flow to the first SLRB for transmission, and start buffering the data packet of the first QoS flow in the SDAP buffer. By setting the first preset duration, the first terminal device may submit the data packet of the first QoS flow buffered in the SDAP buffer to the second SLRB for transmission after stopping submitting the data packet of the first QoS flow to the first SLRB for transmission for the first preset duration.

In this manner, packets of the first QoS flow that have been previously delivered to the first SLRB for transmission may be allowed to complete during the period of time within the first predetermined duration after delivery of the data of the first QoS flow to the first SLRB is stopped. After a first preset time period, the buffered data packet of the first QoS flow is submitted to the second SLRB for transmission, so that the data packet transmitted through the second SLRB arrives after the data packet transmitted through the first SLRB, thereby effectively ensuring that the SDAP layer in the second terminal device on the receiving side can sequentially submit the data packet of the first QoS flow to the upper layer.

In one possible design, the first preset duration may be set by a timer, for example, after the first terminal device determines that the first QoS flow needs to be remapped to the second SLRB, the first terminal device may stop submitting the data of the first QoS flow to the first SLRB for transmission, and start a timer, where the duration of the timer is the first preset duration. In this way, the first terminal device may buffer the data packet of the first QoS flow during the running process of the timer, and submit the buffered data packet of the first QoS flow to the second SLRB for transmission after the timer expires (i.e. the timer stops running).

It should be noted that, the first terminal device may stop delivering the data packet of the first QoS flow that is subjected to remapping to the first SLRB for transmission, where the first terminal device determines that the first QoS flow needs to be subjected to remapping and then immediately stops delivering the data packet of the first QoS flow to the first SLRB, or may also determine that the first terminal device determines that the first QoS flow needs to be subjected to remapping and then stops delivering the data packet of the first QoS flow to the first SLRB after a second preset duration.

Specifically, as shown in fig. 5, in a first possible implementation manner, at time T1, the first terminal device determines that the first QoS flow needs to be remapped according to the latest SLRB configuration. At this point, the SDAP entity in the first terminal device may immediately cease submitting packets of the first QoS flow to the first SLRB transmissions. And the first terminal equipment caches the data packets of the first QoS flow in the SDAP buffer area within a first preset time period after the time T1. When the first preset duration is over, namely at the time T2, the first terminal device submits the data packet of the first QoS flow to the second SLRB for transmission, so that the sequential delivery of the data packet of the first QoS flow is effectively ensured.

In a second possible implementation, as shown in fig. 6, at time T1, the first terminal device determines that the first QoS flow needs to be remapped according to the latest SLRB configurations. And at a time T3 after the time T1, the SDAP entity in the first terminal equipment stops submitting the data packet of the first QoS flow to the first SLRB for transmission, and the time interval between the time T1 and the time T3 is a second preset duration. And the first terminal equipment caches the data packets of the first QoS flow in the SDAP buffer area within a first preset time period after the time T3. And when the first preset duration is over, namely at the time T2, the first terminal equipment submits the data packet of the first QoS flow to the second SLRB for transmission.

Similarly, the second preset time period may also be set by a timer. For example, the first terminal device may start a timer with a duration of a second preset duration while determining that the first QoS flow needs to be remapped to the second SLRB. Thus, the first terminal device may stop submitting the data of the first QoS flow to the first SLRB for transmission after the timer expires (i.e., the timer stops running).

This second possible implementation may be applicable in situations where the RRC state or coverage of the first terminal device changes. In these scenarios, the configuration of first SLRB may not already exist due to the change in RRC state or coverage conditions, as well as the change in the configuration of SLRB. At this time, if the first SLRB is released immediately, if the data packet of the first QoS flow that has been delivered to the first SLRB before is not yet transmitted, a packet loss occurs.

Therefore, in the embodiment of the present application, when the first terminal device determines that the first SLRB needs to be released according to the latest SLRB configuration, the first terminal device may not immediately release the first SLRB, but after the first QoS flow is remapped, after a second preset period of time, stop submitting the data packet of the first QoS flow to the first SLRB, and then release the first SLRB, so that it can be ensured that the data packet submitted to the first SLRB can be completely transmitted, thereby ensuring service continuity of the terminal device.

Optionally, if the configuration information of the first SLRB does not already exist in the latest SLRB configurations acquired by the first terminal device, the first terminal device may release the first SLRB. In one possible design, the first terminal device may release the first SLRB after stopping submitting the data packet of the first QoS flow to the first SLRB for a first preset time period to ensure service continuity, because during the time period during which the data packet of the first QoS flow is stopped submitting the data packet of the first QoS flow to the first SLRB for the first preset time period, the data packet of the first QoS flow that has been submitted to the first SLRB may not yet be transmitted.

Optionally, after the first terminal device submits all the packets of the first QoS flow buffered in the SDAP buffer to the second SLRB for transmission or after the first terminal device submits the packets of the first QoS flow buffered in the SDAP buffer to the second SLRB for transmission for the first time, the first terminal device may empty the first SLRB buffer. Illustratively, the first SLRB buffer includes a first PDCP buffer, a first RLC buffer, or a first LCH buffer.

The first preset duration and the second preset duration mentioned in the embodiment of the present application may be equal or unequal. The first preset duration and the second preset duration may have a plurality of possible configuration manners, for example, the first preset duration and the second preset duration may be preconfigured or predefined, or may be configured by the network device through RRC dedicated signaling or SIB messages, or may be configured by an upper layer of the terminal device (i.e., configured by, for example, a V2X layer or an application layer located above the SDAP layer inside the first terminal device), or may be implemented based on the terminal device itself. The implementation based on the terminal device may include determining, by the first terminal device, a preset duration according to one or more QoS parameters associated with the first QoS flow, or determining, by the first terminal device, the preset duration according to a buffer status of the first terminal device itself, or determining, by the first terminal device, that the first preset duration is timeout according to a time of endmarker corresponding to the sending of the first QoS flow. Other implementations are also possible based on the terminal device implementation, and the application is not limited.

The first preset duration and the second preset duration may also have a plurality of possible configuration granularities, and the configuration granularities may be per PC5 QoS flows, per SLRB, per SL-LCH, PER SERVICE, per destination L2 ID, PER CAST TYPE, per UE, etc., which is not limited by the present application. For example, the configuration granularity of the first preset duration being the per PC5 QoS flows means that the corresponding first preset duration is independently configured for each PC5 QoS flow, and the first preset durations corresponding to different PC5 QoS flows may be the same or different.

It should be understood that the configuration manner of the first preset duration and the second preset duration may be the same or different, and the present application is not limited. When the configuration mode of the first preset duration and the second preset duration is the same, for example, the first preset duration and the second preset duration are both configured by the network device, the first preset duration and the second preset duration configured by the network device may be sent through the same message or different messages, and the application is not limited. The configuration granularity of the first preset duration and the second preset duration may be the same or different, and the application is not limited as well. Moreover, for the first preset duration or the second preset duration, any of the above configuration modes and configuration granularity may be combined with each other.

Example two

Referring to fig. 7, a flowchart of another method for side-link communication according to an embodiment of the present application is shown, and the method specifically includes steps S701 to S704 as follows:

In step S701, the second terminal device receives data of the first QoS flow on the first SLRB.

The first terminal device refers to a terminal device at a transmitting side, and the second terminal device refers to a terminal device at a receiving side, i.e. the first terminal device transmits data to the second terminal device through a side uplink communication link. The communication between the first terminal device and the second terminal device based on the sidelink communication link is unicast.

The first QoS flow refers to the PC5 QoS flow where remapping occurs. The first QoS flow changes from original mapping to first SLRB to second SLRB, first SLRB being source SLRB, second SLRB being target SLRB. The reason why the remapping of the first QoS flow occurs may be that the RRC state or coverage of the first terminal device is changed, or that the configuration of SLRB of the first terminal device is changed although the RRC state or coverage of the first terminal device remains unchanged, which will not be described in detail herein with reference to embodiment one.

In step S702, the second terminal device receives configuration information of the second SLRB from the first terminal device, where the configuration information of the second SLRB indicates that the first QoS flow is remapped to the second SLRB.

In the embodiment of the present application, the first terminal device may obtain the latest SLRB configuration, and according to the latest SLRB configuration, if the first terminal device determines that the first QoS flow needs to be remapped from the first SLRB to the second SLRB, the first terminal device may send the second SLRB configuration information to the second terminal device, so as to notify the second terminal device that the first QoS flow is remapped to the second SLRB.

The configuration information of the second SLRB may include information for indicating the QoS flow corresponding to the second SLRB, for example, the identifier of the first QoS flow, where the identifier may be a QFI of the QoS flow, or other identifying information used to identify one QoS flow inside the terminal device. In this manner, the second terminal device may determine that the first QoS flow needs to be remapped to the second SLRB based on the received configuration information of the second SLRB.

Optionally, the configuration information of the second SLRB may further include configuration parameters of the second SLRB itself, for example, configuration parameters of the PDCP entity, RLC entity, LCH, etc. in the second SLRB. In this way, the second terminal device may establish the second SLRB according to the received configuration information of the second SLRB.

In one possible design, the first terminal device may send a PC5 RRC message to the second terminal device, where the PC5 RRC message carries the configuration information of the second SLRB, and optionally, the first terminal device may also send the latest SLRB configuration related to the second terminal device, all carried in the PC5 RRC message.

In another possible design, if the configuration of the second SLRB already exists in the second terminal device, the first terminal device may also send a PC5 RRC message to the second terminal device, where the PC5 RRC message carries indication information for indicating that the first QoS flow is remapped from the first SLRB to the second SLRB, so that the second terminal device is convenient to learn that the first QoS flow is remapped from the first SLRB to the second SLRB.

In step S703, the second terminal device buffers the data packet received from the second SLRB in the SDAP buffer within a third preset time period after receiving the configuration information of the second SLRB.

And step 704, after a third preset period of time, the SDAP entity of the second terminal device submits the data packet received from the second SLRB and buffered in the SDAP buffer to an upper layer for processing.

As shown in fig. 8, at time T1, the second terminal device determines that the first QoS flow needs to be remapped. And in a third preset time period after the time T1, the SDAP entity in the second terminal device buffers the data packet received from the second SLRB in an SDAP buffer area. And after the third preset time length is over, namely at the time T2, the second terminal equipment delivers the data packet received from the second SLRB and buffered in the SDAP buffer area to the upper layer for processing, so that the sequential delivery of the data packet of the first QoS flow is effectively ensured.

In the embodiment of the present application, the upper layer refers to an upper layer of the SDAP layer in the protocol stack, such as a V2X layer and an application layer.

It should be noted that, in the third preset duration for determining the first QoS flow, the second terminal device may also include packets of other QoS flows except the first QoS flow in the packets received from the second SLRB. If the SDAP layer of the second terminal device cannot distinguish or does not distinguish the data packets of each QoS stream transmitted on the same SLRB, the SDAP layer of the second terminal device can buffer the data packets received from the second SLRB in the SDAP buffer, and deliver the data packets to the upper layer for processing after the third preset time period is over.

Or in a possible design, if each data packet includes identification information for indicating the QoS flow to which the data packet belongs, the second terminal device may identify, according to the identification information, the data packet of the first QoS flow received from the second SLRB, and then the SDAP entity of the second terminal device may also only buffer the received data packet of the first QoS flow. Illustratively, the identification information is a PFI associated with the QoS flow.

Optionally, the second terminal device may release the first SLRB after determining that the first QoS flow needs to be remapped to the third preset duration after the second SLRB.

Optionally, after the second terminal device submits all the data packets of the first QoS flow buffered in the SDAP buffer to the upper layer, or after the first terminal device submits the data packets of the first QoS flow buffered in the SDAP buffer to the upper layer for the first time, the second terminal device may empty the first SLRB buffer. Illustratively, the first SLRB buffer includes a first PDCP buffer, a first RLC buffer, or a first LCH buffer.

It is understood that the third preset time period may also be set by a timer. For example, the first terminal device may start a timer with a duration of a third preset duration while determining that the first QoS flow needs to be remapped to the second SLRB. In this way, the first terminal device may buffer the data packet received from the second SLRB in the SDAP buffer during the running of the timer, and after the timer expires (i.e., the timer stops running), may stop buffering the data packet received from the second SLRB, and deliver the buffered data packet received from the second SLRB to the upper layer.

The configuration manner and the configuration granularity of the third preset duration may refer to the first preset duration or the second preset duration, which are not described herein. Optionally, the second terminal device determines that the third preset duration is timeout according to the time endmarker corresponding to the received first QoS flow.

Example III

Referring to fig. 9, a flowchart of another method for side uplink communication according to an embodiment of the present application specifically includes the following steps S901 to S903:

In step S901, the first terminal device sends data of the first QoS flow on the first SLRB.

In step S902, the first terminal device obtains configuration information of a second SLRB, where the configuration information of the second SLRB indicates that the first QoS flow is remapped to the second SLRB.

Optionally, the configuration information of the second SLRB further indicates that the first SLRB needs to be released.

The specific implementation of step S902 can refer to embodiment one, and will not be described herein.

In step S903, after obtaining the fourth preset duration after the configuration information of the second SLRB, the first terminal device releases the first SLRB.

The method can be applied to the scene that the RRC state or coverage condition of the first terminal equipment changes. For example, if the RRC state of the first terminal device changes from the RRC idle state to the RRC connected state, then the configuration SLRB previously acquired by the first terminal device through SIB messages will fail, and the first terminal device needs to acquire the latest SLRB configuration from the network device through RRC signaling. In this scenario, the first SLRB of the previous network device configuration via SIB messages needs to be released.

The first terminal device may determine that the first QoS flow needs to be remapped from the first SLRB to the second SLRB and that the first SLRB needs to be released based on the latest SLRB configuration acquired. However, if the first SLRB is released immediately at this time, the packet loss may occur in the first QoS flow because the packet submitted to the first QoS flow transmitted by the first SLRB is not yet transmitted. Therefore, after the first terminal device determines that the first QoS flow is remapped from the first SLRB to the second SLRB, the first terminal device releases the first SLRB after the fourth preset time length, so that service continuity of the first terminal device can be effectively ensured, and the situation of data packet loss is avoided.

As shown in fig. 10, at time T1, the first terminal device determines that the first QoS flow needs to be remapped. During a fourth preset time period after the time T1, the first terminal device may receive the data packet from the first SLRB as usual and submit it to the upper layer processing. At the end of the fourth preset time period, i.e. at time T2, the first terminal device stops receiving data packets from the first SLRB and releases the first SLRB.

It is understood that the fourth preset time period may also be set by a timer. For example, the first terminal device may start a timer having a duration of a fourth preset duration while determining that the first QoS flow is remapped from the first SLRB to the second SLRB. In this manner, the first terminal device may release the first SLRB after the timer expires (i.e., the timer stops running).

The configuration manner and the configuration granularity of the fourth preset duration may refer to the first preset duration, the second preset duration or the third preset duration, which are not described herein.

It should be noted that the method embodiments provided by the present application may be combined with each other. For example, on the basis of the method provided in the third embodiment, the first embodiment or the second embodiment may be further combined, so as to further ensure that the data packets of the first QoS flow can be sequentially delivered at the receiving side.

Referring to fig. 11, a schematic structural diagram of another communication device according to an embodiment of the present application is provided, where the communication device 1100 includes a transceiver module 1110 and a processing module 1120. The communication device may be used to implement the functionality relating to the terminal device in any of the method embodiments described above. The communication means may be, for example, a terminal device, such as a hand-held terminal device or a vehicle-mounted terminal device, a chip included in the terminal device, or a device including the terminal device, such as various types of vehicles, etc.

When the communication apparatus is used as a first terminal device and performs the method embodiment shown in fig. 3, the transceiver module 1110 is configured to send data of the first QoS flow on the first SLRB and obtain configuration information of the second SLRB, where the configuration information of the second SLRB indicates that the first QoS flow is remapped to the second SLRB. A processing module 1120 is configured to stop sending the data packet of the first QoS flow on the first SLRB, and buffer the data packet of the first QoS flow in the SDAP buffer for a first preset duration after stopping sending the data packet of the first QoS flow on the first SLRB. The transceiver module 1110 is further configured to send, after a first preset period of time has elapsed, a data packet of the first QoS flow buffered in the SDAP buffer on the second SLRB.

In one possible design, the processing module 1120 is specifically configured to stop sending the data packet of the first QoS flow on the first SLRB immediately after the configuration information of the second SLRB is acquired, or stop sending the data packet of the first QoS flow on the first SLRB after a second preset period of time after the configuration information of the second SLRB is acquired.

In one possible design, the processing module 1120 is further configured to establish the second SLRB according to the configuration information of the second SLRB.

In one possible design, the processing module 1120 is further configured to release the first SLRB after stopping sending the data packet of the first QoS flow on the first SLRB for a first preset period of time.

When the communication apparatus is implemented as a second terminal device, performing the method embodiment shown in fig. 7, the transceiver module 1110 is configured to receive data of the first QoS flow on the first SLRB and to receive configuration information of the second SLRB from the first terminal device, the configuration information of the second SLRB indicating that the first QoS flow is remapped to the second SLRB. The processing module 1120 is configured to buffer the data packet received from the second SLRB in the SDAP buffer within a third preset time period after receiving the configuration information of the second SLRB, and deliver the data packet received from the second SLRB buffered in the SDAP buffer to an upper layer for processing after the third preset time period.

In one possible design, the processing module 1120 is further configured to release the first SLRB after a third preset period of time has elapsed.

When the communication apparatus is used as a first terminal device and performs the method embodiment shown in fig. 9, the transceiver module 1110 is configured to send data of the first QoS flow on the first SLRB and obtain configuration information of the second SLRB, where the configuration information of the second SLRB indicates that the first QoS flow is remapped to the second SLRB. The processing module 1120 is configured to release the first SLRB after a fourth preset duration after the configuration information of the second SLRB is acquired.

In one possible design, the processing module 1120 is further configured to send the data packet of the first QoS flow on the second SLRB after the fourth preset duration.

The processing module 1120 involved in the communication device may be implemented by a processor or processor-related circuit components and the transceiver module 1110 may be implemented by a transceiver or transceiver-related circuit components. The operations and/or functions of the respective modules in the communication device are not described herein for brevity in order to implement the respective flows of the methods shown in fig. 3 to 10.

Fig. 12 is a schematic diagram of another structure of a communication device according to an embodiment of the application. The communication device may specifically be a terminal device. For easy understanding and ease of illustration, in fig. 12, the terminal device is exemplified by a mobile phone. As shown in fig. 12, the terminal device includes a processor, a memory, a radio frequency circuit, an antenna, an input/output device, and the like. The processor is mainly used for processing communication protocols and communication data, controlling the terminal equipment, executing software programs, processing data of the software programs and the like. The memory is mainly used for storing software programs and data. The radio frequency circuit is mainly used for converting a baseband signal and a radio frequency signal and processing the radio frequency signal. The antenna is mainly used for receiving and transmitting radio frequency signals in the form of electromagnetic waves. Input and output devices, such as touch screens, display screens, keyboards, etc., are mainly used for receiving data input by a user and outputting data to the user. It should be noted that some kinds of terminal apparatuses may not have an input/output device.

When data need to be sent, the processor carries out baseband processing on the data to be sent and then outputs a baseband signal to the radio frequency circuit, and the radio frequency circuit carries out radio frequency processing on the baseband signal and then sends the radio frequency signal outwards in the form of electromagnetic waves through the antenna. When data is sent to the terminal equipment, the radio frequency circuit receives a radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor, and the processor converts the baseband signal into data and processes the data. For ease of illustration, only one memory and processor is shown in fig. 12. In an actual end device product, there may be one or more processors and one or more memories. The memory may also be referred to as a storage medium or storage device, etc. The memory may be provided separately from the processor or may be integrated with the processor, as the embodiments of the application are not limited in this respect.

In the embodiment of the application, the antenna and the radio frequency circuit with the receiving and transmitting functions can be regarded as a receiving and transmitting unit of the terminal equipment, and the processor with the processing function can be regarded as a processing unit of the terminal equipment. As shown in fig. 12, the terminal device includes a transceiving unit 1210 and a processing unit 1220. The transceiver unit may also be referred to as a transceiver, transceiver device, etc. The processing unit may also be called a processor, a processing board, a processing module, a processing device, etc. Alternatively, the device for implementing the receiving function in the transceiver unit 1210 may be regarded as a receiving unit, and the device for implementing the transmitting function in the transceiver unit 1210 may be regarded as a transmitting unit, that is, the transceiver unit 1210 includes a receiving unit and a transmitting unit. The transceiver unit may also be referred to as a transceiver, transceiver circuitry, or the like. The receiving unit may also be referred to as a receiver, or receiving circuit, among others. The transmitting unit may also sometimes be referred to as a transmitter, or a transmitting circuit, etc. It should be understood that, the transceiver unit 1210 is configured to perform the transmitting operation and the receiving operation on the terminal device side in the above-described method embodiment, and the processing unit 1220 is configured to perform other operations on the terminal device other than the transmitting operation in the above-described method embodiment.

The embodiment of the application also provides a chip system, which comprises a processor, wherein the processor is coupled with a memory, and the memory is used for storing a program or instructions, and when the program or instructions are executed by the processor, the chip system realizes the method in any method embodiment.

Alternatively, the processor in the system-on-chip may be one or more. The processor may be implemented in hardware or in software. When implemented in hardware, the processor may be a logic circuit, an integrated circuit, or the like. When implemented in software, the processor may be a general purpose processor, implemented by reading software code stored in a memory.

The chip system may be a field programmable gate array (field programmable GATE ARRAY, FPGA), an Application Specific Integrated Chip (ASIC), a system on chip (SoC), a central processing unit (central processor unit, CPU), a network processor (network processor, NP), a digital signal processing circuit (DIGITAL SIGNAL processor, DSP), a microcontroller (micro controller unit, MCU), a programmable controller (programmable logic device, PLD) or other integrated chip, for example.

It should be understood that the steps in the above-described method embodiments may be accomplished by integrated logic circuitry in hardware in a processor or instructions in the form of software. The steps of the method disclosed in connection with the embodiments of the present application may be embodied directly in a hardware processor for execution, or in a combination of hardware and software modules in the processor for execution.

Embodiments of the present application also provide a computer-readable storage medium having stored therein computer-readable instructions which, when read and executed by a computer, cause the computer to perform the method of any of the method embodiments described above.

Embodiments of the present application also provide a computer program product which, when read and executed by a computer, causes the computer to perform the method of any of the method embodiments described above.

The embodiment of the application also provides a communication system which comprises the first terminal equipment and the second terminal equipment.

It should be appreciated that the processor referred to in the embodiments of the present application may be a central processing unit (central processing unit, CPU), but may also be other general purpose processors, digital signal processors (DIGITAL SIGNAL processors, DSPs), application Specific Integrated Circuits (ASICs), off-the-shelf programmable gate arrays (field programmable GATE ARRAY, FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

It should also be understood that the memory referred to in embodiments of the present application may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an erasable programmable ROM (erasable PROM), an electrically erasable programmable EPROM (EEPROM), or a flash memory. The volatile memory may be random access memory (random access memory, RAM) which acts as external cache memory. By way of example, and not limitation, many forms of RAM are available, such as static random access memory (STATIC RAM, SRAM), dynamic random access memory (DYNAMIC RAM, DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate synchronous dynamic random access memory (double DATA RATE SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (ENHANCED SDRAM, ESDRAM), synchronous link dynamic random access memory (SYNCHLINK DRAM, SLDRAM), and direct memory bus random access memory (direct rambus RAM, DR RAM).

It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, the memory (storage module) is integrated into the processor.

It should be noted that the memory described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

It should be understood that, in various embodiments of the present application, the sequence numbers of the foregoing processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic thereof, and should not constitute any limitation on the implementation process of the embodiments of the present application.

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 solution. 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.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown 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 may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in 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 this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. The storage medium includes a U disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, an optical disk, or other various media capable of storing program codes.

The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within 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 side-link communication, the method comprising:

the first terminal device transmits data of a first quality of service QoS flow on a first side uplink radio bearer SLRB;

the first terminal device obtains configuration information of a second SLRB, wherein the configuration information of the second SLRB indicates that the first QoS flow is remapped to the second SLRB;

The service data adaptation layer (SDAP) entity of the first terminal device stops sending the data packet of the first QoS flow on the first SLRB, and caches the data packet of the first QoS flow in an SDAP buffer area within a first preset duration after stopping sending the data packet of the first QoS flow on the first SLRB;

after the first preset duration, the first terminal device sends the data packet of the first QoS flow cached in the SDAP buffer on the second SLRB.

2. The method of claim 1, wherein the service data adaptation layer, SDAP, entity of the first terminal device stops sending packets of the first QoS flow on the first SLRB, comprising:

After the first terminal device obtains the configuration information of the second SLRB, the SDAP entity of the first terminal device immediately stops sending the data packet of the first QoS flow on the first SLRB, or

After the first terminal device obtains the second preset duration after the configuration information of the second SLRB, the SDAP entity of the first terminal device stops sending the data packet of the first QoS flow on the first SLRB.

3. The method according to claim 1 or 2, characterized in that the method further comprises:

the first terminal device establishes the second SLRB according to the configuration information of the second SLRB.

4. The method according to claim 1 or 2, characterized in that the method further comprises:

The first terminal device releases the first SLRB after stopping sending the data packet of the first QoS flow on the first SLRB for the first preset duration.

5. A method of side-link communication, the method comprising:

The second terminal device receives data of the first quality of service QoS flow on the first side uplink radio bearer SLRB;

The second terminal device receives configuration information of a second SLRB from the first terminal device, the configuration information of the second SLRB indicating that the first QoS flow is remapped to the second SLRB;

The second terminal device caches the data packet received from the second SLRB in a service data adaptation layer (SDAP) buffer area within a third preset time period after receiving the configuration information of the second SLRB, and delivers the data packet of the first QoS flow received from the first SLRB to an upper layer for processing;

And after the third preset duration, the SDAP entity of the second terminal equipment submits the data packet received from the second SLRB and buffered in the SDAP buffer to an upper layer for processing.

6. The method of claim 5, wherein the method further comprises:

the second terminal device establishes the second SLRB according to the configuration information of the second SLRB.

7. The method according to claim 5 or 6, characterized in that the method further comprises:

and after the third preset time period, the second terminal device releases the first SLRB.

8. A communication device, the device comprising:

a transceiver module for transmitting data of a first quality of service, qoS, flow on a first side uplink radio bearer SLRB;

The transceiver module is further configured to obtain configuration information of a second SLRB, where the configuration information of the second SLRB indicates that the first QoS flow is remapped to the second SLRB;

a processing module, configured to stop sending the data packet of the first QoS flow on the first SLRB, and buffer the data packet of the first QoS flow in an SDAP buffer within a first preset duration after stopping sending the data packet of the first QoS flow on the first SLRB;

The transceiver module is further configured to send, after the first preset duration, the data packet of the first QoS flow buffered in the SDAP buffer on the second SLRB.

9. The apparatus of claim 8, wherein the processing module is specifically configured to:

immediately after the configuration information of the second SLRB is obtained, the transmission of the data packet of the first QoS flow on the first SLRB is stopped, or

And stopping sending the data packet of the first QoS flow on the first SLRB after a second preset time period after the configuration information of the second SLRB is acquired.

10. The apparatus of claim 8 or 9, wherein the processing module is further configured to:

and establishing the second SLRB according to the configuration information of the second SLRB.

11. The apparatus of claim 8 or 9, wherein the processing module is further configured to:

And releasing the first SLRB after stopping the transmission of the data packet of the first QoS flow on the first SLRB for the first preset period of time.

12. A communication device, the device comprising:

a transceiver module for receiving data of a first quality of service, qoS, flow over a first side uplink radio bearer SLRB;

the transceiver module is further configured to receive configuration information of a second SLRB from a first terminal device, where the configuration information of the second SLRB indicates that the first QoS flow is remapped to the second SLRB;

A processing module, configured to buffer, in a third preset duration after receiving the configuration information of the second SLRB, a data packet received from the second SLRB in a service data adaptation layer SDAP buffer, and deliver, to an upper layer, a data packet of the first QoS flow received from the first SLRB;

and the processing module is further configured to deliver, after the third preset duration passes, the data packet received from the second SLRB and buffered in the SDAP buffer to an upper layer for processing.

13. The apparatus of claim 12, wherein the processing module is further configured to:

14. The apparatus of claim 12 or 13, wherein the processing module is further configured to:

and after the third preset time period passes, releasing the first SLRB.

15. A communication apparatus, the apparatus comprising at least one processor coupled with at least one memory:

the at least one processor configured to execute a computer program or instructions stored in the at least one memory to cause the apparatus to perform the method of any one of claims 1 to 4 or to cause the apparatus to perform the method of any one of claims 5 to 7.

16. A readable storage medium storing instructions which, when executed, cause the method of any one of claims 1 to 4 to be implemented or cause the method of any one of claims 5 to 7 to be implemented.

17. A communication device comprising a processor and an interface circuit;

The interface circuit is used for receiving code instructions and transmitting the code instructions to the processor;

The processor being configured to execute the code instructions to perform the method of any one of claims 1 to 4, or

The processor being configured to execute the code instructions to perform the method of any one of claims 5 to 7.