WO2021128218A1 - Procédé et appareil de communication de liaison latérale - Google Patents

Procédé et appareil de communication de liaison latérale Download PDF

Info

Publication number
WO2021128218A1
WO2021128218A1 PCT/CN2019/128898 CN2019128898W WO2021128218A1 WO 2021128218 A1 WO2021128218 A1 WO 2021128218A1 CN 2019128898 W CN2019128898 W CN 2019128898W WO 2021128218 A1 WO2021128218 A1 WO 2021128218A1
Authority
WO
WIPO (PCT)
Prior art keywords
slrb
terminal device
qos flow
configuration information
data packet
Prior art date
Application number
PCT/CN2019/128898
Other languages
English (en)
Chinese (zh)
Inventor
李翔宇
王君
徐海博
戴明增
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to CN201980103025.5A priority Critical patent/CN114830803A/zh
Priority to PCT/CN2019/128898 priority patent/WO2021128218A1/fr
Publication of WO2021128218A1 publication Critical patent/WO2021128218A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H04W4/46—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P] for vehicle-to-vehicle communication [V2V]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup

Definitions

  • This application relates to the field of wireless communication technology, and in particular to a side link communication method and device.
  • a PC5 quality of service flow (PC5 QoS flow) is associated with a PC5 quality of service rule (PC5 QoS rule).
  • the V2X layer of the terminal device can map the side link data packet (V2X packet) delivered by the application layer to the corresponding PC5 QoS flow according to the configured PC5 QoS rules, and then send it to the service data adaptation protocol , SDAP) layer.
  • the SDAP entity can map the data packets of the side link in the PC5 QoS flow according to the mapping relationship between the PC5 QoS flow configured by the network device and the side link radio bearer (SLRB) To the corresponding SLRB.
  • SLRB side link radio bearer
  • the mapping relationship between the PC5 QoS flow and the SLRB may also change. If the mapping relationship between a certain PC5 QoS flow and SLRB changes, the data of the QoS flow is immediately changed from mapping to the source SLRB to the target SLRB, then some data packets in the source SLRB are re- Some data packets sent through the source SLRB may arrive at the receiving end after the data packets sent through the target SLRB. This will cause the SDAP layer of the receiving end to deliver the data packets of the QoS flow to the upper layer. Circumstances that cannot be submitted in order.
  • the embodiments of the present application provide a side-link communication method and device, which are used to ensure that the data packets of the remapped QoS flow can be delivered in order on the receiving side.
  • an embodiment of the present application provides a side link communication method, which can be applied to a first terminal device, and the method includes: the terminal device sends a first quality of service on the first side link radio bearer SLRB QoS flow data; the first terminal device obtains the configuration information of the second SLRB, 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 at The data packet of the first QoS flow is sent on the first SLRB, and the data packet of the first QoS flow is buffered in the first preset time period after stopping sending the data packet of the first QoS flow on the first SLRB In the SDAP buffer; after the first preset time period, the first terminal device sends the data packet of the first QoS flow buffered in the SDAP buffer on the second SLRB.
  • the first terminal device can stop submitting the data of the first QoS flow to the first SLRB for transmission, and buffer the data packets of the first QoS flow In the SDAP buffer, after the first preset time period has elapsed, the data packet of the first QoS flow buffered in the SDAP buffer is sent on the second SLRB. It can be seen that by setting the first preset duration, the data packets of the first QoS flow that have been previously delivered to the first SLRB can be set to the first preset after the first QoS flow is stopped from being delivered to the first SLRB. The transmission is completed during this period of time.
  • the buffered data packets of the first QoS flow are then 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, thereby effectively Ensure that the SDAP layer on the receiving side can deliver the data packets of the first QoS flow to the upper layer in order.
  • the SDAP entity of the first terminal device may immediately stop sending the first SLRB on the first SLRB after the first terminal device obtains the configuration information of the second SLRB. Data packets of QoS flow.
  • the SDAP entity of the first terminal device may also stop sending the data packet of the first QoS flow on the first SLRB after a second preset period of time after the first terminal device obtains the configuration information of the second SLRB. Can guarantee business continuity.
  • the first terminal device may establish the second SLRB according to the configuration information of the second SLRB, thereby facilitating remapping the first QoS flow onto the second SLRB.
  • the first terminal device may release the first SLRB after a first preset period of time after stopping sending data packets of the first QoS flow on the first SLRB .
  • embodiments of the present application provide a side link communication method, which can be applied to a second terminal device, and the method includes: the second terminal device receives the first side link radio bearer SLRB on the first side link.
  • 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 time period after determining that the first QoS flow needs to be remapped. After the third preset duration is over, the buffered data packet received from the second SLRB is then submitted to the upper layer for processing. In this way, within the third preset time period after the second terminal device determines that the first QoS flow needs to be remapped, the SDAP layer of the second terminal device can continue to receive the data packets of the first QoS flow from the first SLRB and deliver them To the upper management.
  • the SDAP layer of the second terminal device submits the data packet received on the second SLRB to the upper layer after the third preset duration ends, so that the SDAP layer can receive the data of the first QoS flow from the first SLRB After the packet is submitted to the upper layer for processing, the data packet of the first QoS flow received from the second SLRB is then delivered, so as to ensure that the SDAP layer of the second terminal device can deliver the data packets of the first QoS flow in order.
  • the second terminal device may establish a second SLRB according to the second SLRB configuration information, thereby facilitating remapping the first QoS flow onto the second SLRB.
  • the second terminal device may release the first SLRB after the third preset time period has elapsed.
  • embodiments of the present application provide a side link communication method, which can be applied to a first terminal device, and the method includes: the first terminal device sends a first side link radio bearer SLRB on the first side link. Data of the quality of service QoS flow; the first terminal device obtains the configuration information of the second SLRB, and the configuration information of the second SLRB indicates that the first QoS flow is remapped to the second SLRB; the first terminal device is acquiring the configuration of the second SLRB After the fourth preset period of time after the message, the first SLRB is released.
  • the first terminal device may not release the first SLRB immediately, and release the first SLRB again after the fourth preset period of time has elapsed. In this way, in the case of remapping of the first QoS flow, data packets that have been delivered to the first SLRB for transmission before remapping can be sent to the second terminal device, thereby ensuring service continuity.
  • 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.
  • the service data adaptation layer SDAP entity of the first terminal device may send the data of the first QoS flow on the second SLRB after the fourth preset duration package.
  • an embodiment of the present application provides a communication device, which has the function of a terminal device in any possible design of the foregoing first aspect or the first aspect, or has the capability to implement the foregoing second or second aspect
  • the device may be a terminal device, such as a handheld terminal device, a vehicle-mounted terminal device, a vehicle user equipment, a roadside unit, etc., a device included in the terminal device, such as a chip, or a device including a terminal device.
  • the functions of the above-mentioned terminal device may be realized by hardware, or may be realized by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the structure of the device includes a processing module and a transceiver module, wherein the processing module is configured to support the device to perform the first aspect or the corresponding function of the terminal device in any of the first aspects of the design. , Or perform the corresponding function of the terminal device in the above-mentioned second aspect or any design of the second aspect, or perform the corresponding function of the terminal device in the above-mentioned third aspect or any design of the third aspect.
  • the transceiver module is used to support the communication between the device and other communication devices. For example, when the device is a terminal device, it can send side link information to another terminal device.
  • the communication device may also include a storage module, which is coupled with the processing module, which stores program instructions and data necessary for the device.
  • the processing module may be a processor
  • the communication module may be a transceiver
  • the storage module may be a memory.
  • the memory may be integrated with the processor or may be provided separately from the processor, which is not limited in this application.
  • the structure of the device includes a processor and may also include a memory.
  • the processor is coupled with the memory, and can be used to execute the computer program instructions stored in the memory, so that the device executes the above-mentioned first aspect or any one of the possible design methods of the first aspect, or executes the above-mentioned second aspect or the second aspect.
  • the method in any design of the aspect, or the method in the design of any of the above-mentioned third aspect or the third aspect is implemented.
  • the device further includes a communication interface, and the processor is coupled with the communication interface.
  • the communication interface may be a transceiver or an input/output interface; when the device is a chip included in the terminal device, the communication interface may be an input/output interface of the chip.
  • the transceiver may be a transceiver circuit, and the input/output interface may be an input/output circuit.
  • an embodiment of the present application provides a chip system, including: a processor, the processor is coupled with a memory, the memory is used to store a program or an instruction, when the program or an instruction is executed by the processor , Enabling the chip system to implement the method in any possible design of the foregoing first aspect or the first aspect, or implement the method in any possible design of the foregoing second aspect or the second aspect, or implement the foregoing first aspect Any one of the three aspects or the third aspect of the possible design method.
  • the chip system further includes an interface circuit, which is used to exchange code instructions to the processor.
  • processors in the chip system, and the processors may be implemented by hardware or software.
  • the processor may be a logic circuit, an integrated circuit, or the like.
  • the processor may be a general-purpose processor, which is implemented by reading software codes stored in the memory.
  • the memory may be integrated with the processor, or may be provided separately from the processor, which is not limited in this application.
  • the memory may be a non-transitory processor, such as a read-only memory ROM, which may be integrated with the processor on the same chip, or may be set on different chips.
  • the setting method of the processor is not specifically limited.
  • an embodiment of the present application provides a computer-readable storage medium on which a computer program or instruction is stored.
  • the computer executes the first aspect or any one of the first aspect.
  • the method in one possible design, or the method in any one of the possible designs of the above-mentioned second aspect or the second aspect, or the method in any one of the possible designs of the above-mentioned third aspect or the third aspect.
  • the embodiments of the present application provide a computer program product.
  • the computer reads and executes the computer program product, the computer executes the first aspect or any one of the possible design methods in the first aspect, Or implement the method in any possible design of the foregoing second aspect or the second aspect, or implement the method in any possible design of the foregoing third aspect or the third aspect.
  • an embodiment of the present application provides a communication system.
  • the communication system includes a first terminal device and a second terminal device.
  • FIG. 1 is a schematic diagram of a network architecture of a communication system to which an embodiment of this application is applicable;
  • Figure 2 is a schematic diagram of a PC5 QoS model provided by an embodiment of the application.
  • FIG. 3 is a schematic flowchart of a communication method provided by an embodiment of this application.
  • FIG. 4 is a schematic diagram of QoS flow remapping according to an embodiment of the application.
  • FIG. 5 is a schematic diagram of a possible implementation manner of stopping delivery of data packets of the first QoS flow to the first SLRB for transmission according to an embodiment of the application;
  • FIG. 6 is a schematic diagram of another possible implementation manner for stopping delivery of data packets of the first QoS flow to the first SLRB for transmission according to an embodiment of the application;
  • FIG. 7 is a schematic flowchart of another communication method provided by an embodiment of this application.
  • FIG. 8 is a schematic diagram of the third preset duration in an embodiment of this application.
  • FIG. 9 is a schematic flowchart of another communication method provided by an embodiment of this application.
  • FIG. 10 is a schematic diagram of the fourth preset duration in an embodiment of this application.
  • FIG. 11 is a schematic structural diagram of a communication device provided by an embodiment of this application.
  • FIG. 12 is a schematic structural diagram of another communication device provided by an embodiment of this application.
  • GSM global system for mobile communications
  • CDMA code division multiple access
  • WCDMA broadband code division multiple access
  • GPRS general packet radio service
  • LTE long term evolution
  • LTE frequency division duplex FDD
  • TDD LTE Time division duplex
  • UMTS universal mobile telecommunication system
  • WIMAX worldwide interoperability for microwave access
  • 5G fifth generation
  • NR new radio
  • the technical solutions of the embodiments of the present application can be applied to unmanned driving (unmanned driving), driver assistance (ADAS), intelligent driving (intelligent driving), connected driving, and intelligent network driving (Intelligent Network Driving). ), car sharing, smart/intelligent car, digital car, unmanned car/driverless car/pilotless car/automobile, Internet of vehicles (IoV) , Autonomous vehicles (self-driving car, autonomous car), cooperative vehicle infrastructure (CVIS), intelligent transportation (intelligent transport system, ITS), vehicle communication (vehicular communication) and other technical fields.
  • unmanned driving unmanned driving
  • ADAS driver assistance
  • intelligent driving intelligent driving
  • connected driving and intelligent network driving
  • Intelligent Network Driving Intelligent Network Driving
  • the technical solutions provided by the embodiments of the present application can be applied to cellular links, and can also be applied to links between devices, such as device-to-device (D2D) links.
  • D2D link or V2X link can also be called side link, auxiliary link or side link.
  • the aforementioned terms all refer to links established between devices of the same type, and have the same meaning.
  • the so-called devices of the same type can be the link between the terminal device and the terminal device, the link between the base station and the base station, and the link between the relay node and the relay node. This application The embodiment does not limit this.
  • FIG. 1 is a schematic diagram of a network architecture of a communication system to which an embodiment of this application is applicable.
  • the communication system includes a terminal device 110, a terminal device 120, and a network device 130.
  • the network device can communicate with at least one terminal device (such as the terminal device 110) through uplink (UL) and downlink (DL), and the communication interface between the network device and the terminal device is a Uu interface.
  • a terminal device can communicate with another terminal device through a sidelink (SL).
  • the communication interface between the terminal device and the terminal device is the PC5 interface, and the side link can also be understood as a direct connection between the terminal devices. Communication link.
  • Sidelink-based communication can use at least one of the following channels: physical sidelink shared channel (PSSCH), used to carry sidelink data information; physical sidelink control channel ( The physical sidelink control channel (PSCCH) is used to carry sidelink control information (SCI); the physical sidelink feedback channel (PSFCH) is used to carry side-line HARQ feedback information.
  • PSSCH physical sidelink shared channel
  • PSCCH physical sidelink control channel
  • SCI sidelink control information
  • PSFCH physical sidelink feedback channel
  • the network device in FIG. 1 may be an access network device, such as a base station.
  • the access network device in different systems corresponding to different devices for example, in the fourth generation mobile communication technology (the 4 th generation, 4G) system, the eNB may correspond, a corresponding access network device 5G 5G in the system, For example, gNB.
  • the technical solutions provided by the embodiments of the present application can also be applied to future mobile communication systems, such as 6G or 7G communication systems. Therefore, the network equipment in FIG. 1 can also correspond to the access network equipment in the future mobile communication system.
  • each network device may provide services for multiple terminal devices.
  • the embodiment of the present application does not limit the number of network devices and terminal devices in the communication system.
  • the network device in FIG. 1 and each of some or all of the terminal devices among multiple terminal devices can implement the technical solutions provided in the embodiments of the present application.
  • the terminal device in FIG. 1 is described by taking a vehicle-mounted terminal device or a vehicle as an example. It should be understood that the terminal device in the embodiment of the present application is not limited to this.
  • Terminal devices can also be mobile phones, vehicles, vehicle-mounted devices, vehicle-mounted modules, roadside units, pedestrian handheld devices, and massive Machine Type of Communication (mMTC) terminal devices such as smart water meters and electricity meters in the Internet of Things.
  • mMTC massive Machine Type of Communication
  • Terminal equipment which can also be called user equipment (UE), mobile station (MS), mobile terminal (MT), etc.
  • UE user equipment
  • MS mobile station
  • MT mobile terminal
  • the terminal device may communicate with the core network via a radio access network (RAN), and exchange voice and/or data with the RAN.
  • RAN radio access network
  • the terminal device may be a handheld device with a wireless connection function, a vehicle-mounted device, a vehicle user device, and so on.
  • terminal devices are: mobile phones (mobile phones), tablet computers, notebook computers, handheld computers, mobile internet devices (MID), wearable devices, virtual reality (VR) devices, augmented Augmented reality (AR) equipment, wireless terminals in industrial control, wireless terminals in self-driving (self-driving), wireless terminals in remote medical surgery, and smart grid (smart grid)
  • the terminal device may also be a wearable device.
  • Wearable devices can also be called wearable smart devices or smart wearable devices, etc. It is a general term for using wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes Wait.
  • a wearable device is a portable device that is directly worn on the body or integrated into the user's clothes or accessories. Wearable devices are not only a kind of hardware device, but also realize powerful functions through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-sized, complete or partial functions that can be achieved without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, and need to cooperate with other devices such as smart phones.
  • Use such as all kinds of smart bracelets, smart helmets, smart jewelry, etc. for physical sign monitoring.
  • the terminal device in the embodiments of the present application may also be a vehicle-mounted module, vehicle-mounted module, vehicle-mounted component, vehicle-mounted chip, or vehicle-mounted unit that is built into a vehicle as one or more components or units, and the vehicle passes through the built-in vehicle-mounted module, vehicle-mounted Modules, on-board components, on-board chips, or on-board units can implement the method of the present application.
  • Network equipment is the equipment used to connect terminal equipment to the wireless network in the network.
  • the network device may be a node in a radio access network, may also be called a base station, or may be called a radio access network (RAN) node (or device).
  • the network device can be used to convert received air frames and Internet Protocol (IP) packets into each other, and act as a router between the terminal device and the rest of the access network, where the rest of the access network can include an IP network.
  • IP Internet Protocol
  • the network equipment can also coordinate the attribute management of the air interface.
  • the network equipment may include an evolved base station (NodeB or eNB or e-NodeB, evolutional Node B) in a long term evolution (LTE) system or an evolved LTE system (LTE-Advanced, LTE-A), such as
  • LTE long term evolution
  • LTE-A evolved LTE system
  • the traditional macro base station eNB and the micro base station eNB in the heterogeneous network scenario may also include the next generation node B (next generation) in the new radio (NR) system of the fifth generation mobile communication technology (5th generation, 5G).
  • NR new radio
  • node B node B, gNB
  • TRP transmission reception point
  • home base station for example, home evolved NodeB, or home Node B, HNB
  • baseband unit BBU
  • baseband pool BBU pool or WiFi access point (access point, AP), etc.
  • CU centralized unit
  • CU distributed unit
  • CU cloud access network
  • CloudRAN cloud radio access network
  • DU distributed unit
  • a network device in a V2X technology is a roadside unit (RSU).
  • the RSU may be a fixed infrastructure entity that supports V2X applications, and can exchange messages with other entities that support V2X applications.
  • PC5 QoS flow PC5 QoS flow
  • PFI PC5 quality of service flow indicator
  • PFI PC5 QoS flow indicator
  • PFI is used to uniquely identify under a layer 2 destination address (destination L2 ID) A QoS flow.
  • a PFI is also associated with a set of QoS profiles.
  • the QoS profile can include the PC5 interface 5G quality of service identifier (PQI), guaranteed flow bit rate (GFBR), and maximum flow rate. Bit rate (maximum flow bit rate, MFBR) and other parameters.
  • the V2X layer can receive V2X data packets from the application layer, and map the V2X data packets to the corresponding PC5 QoS flow according to the set PC5 QoS rules, and then send it to the SDAP layer.
  • Service data adaptation SDAP is used to map the data packets in the PC5 QoS flow to the corresponding SLRB according to the mapping relationship between the PC5 QoS flow and the SLRB.
  • the side link radio bearer SLRB is the bearer used to send and receive side link data in layer 2, including the packet data convergence protocol (PDCP) entity, radio link control (radio link) control, RLC) entity, logical channel (logical channel, LCH), etc.
  • PDCP packet data convergence protocol
  • RLC radio link control
  • LCH logical channel
  • An SLRB is uniquely associated with a group (source L2 ID, destination L2 ID, cast type), where the cast type can be unicast, multicast, or broadcast.
  • “Multiple” refers to two or more than two. In view of this, “multiple” may also be understood as “at least two” in the embodiments of the present application. "At least one” can be understood as one or more, for example, one, two or more. For example, including at least one means including one, two or more, and it does not limit which ones are included. For example, if 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 are included. In the same way, the understanding of "at least one" and other descriptions is similar.
  • ordinal numbers such as “first” and “second” mentioned in the embodiments of this application are used to distinguish multiple objects, and are not used to limit the order, timing, priority, or importance of multiple objects.
  • the descriptions of “first” and “second” do not limit the objects to be different.
  • FIG. 3 is a schematic flowchart of a side link communication method provided by an embodiment of this application. The method specifically includes the following steps:
  • Step S301 The first terminal device sends the data of the first QoS flow on the first SLRB.
  • the first terminal device refers to the terminal device on the sending side
  • the second terminal device refers to the terminal device on the receiving side, that is, the first terminal device sends data to the second terminal device through the sideline communication link.
  • the communication based on the sideline communication link between the first terminal device and the second terminal device may be unicast, multicast, or broadcast, which is not limited in this application.
  • the change in the mapping relationship between the PC5 QoS flow and the SLRB may be referred to as PC5 QoS flow remapping (PC5 QoS flow remapping).
  • PC5 QoS flow remapping PC5 QoS flow remapping
  • the first QoS flow specifically refers to the PC5 QoS flow where remapping occurs.
  • the data of the first QoS flow is mapped to the first SLRB for transmission, and the first SLRB may also be referred to as the source SLRB.
  • the first SLRB may also be referred to as the source SLRB.
  • 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.
  • the first terminal device sending the data of the first QoS flow on the first SLRB described in step S301 means that before the first QoS flow is remapped, the first terminal device maps the data of the first QoS flow to Transmission on the first SLRB.
  • Step S302 The first terminal device obtains 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 configuration information of the second SLRB may include information used to indicate the QoS flow corresponding to the second SLRB, such as the identification of the first QoS flow.
  • the identification may be the QFI of the QoS flow, or it may be used for unique identification in the terminal device. Other identification information of a QoS flow.
  • 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.
  • the configuration information of the second SLRB may also include configuration parameters of the second SLRB, for example, configuration parameters of the PDCP entity, RLC entity, LCH, etc. in the second SLRB.
  • the first terminal device may establish the second SLRB according to the received configuration information of the second SLRB.
  • 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.
  • the second SLRB may be established immediately after obtaining the configuration information of the second SLRB, or the second SLRB may be established while stopping the delivery of the data packet of the first QoS flow to the first SLRB.
  • the first terminal device may be in a situation where its radio resource control (radio resource control, RRC) state or coverage situation changes, or its RRC state or coverage situation remains unchanged, but the SLRB In the case of configuration changes, obtain the latest SLRB configuration.
  • 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 current mapping relationship between each PC5 QoS flow of the first terminal device and the SLRB.
  • the first terminal device may determine that the first QoS flow needs to be remapped to the second SLRB according to the obtained SLRB configuration.
  • the terminal device needs to obtain the latest SLRB configuration, because in different RRC states or coverage situations, the SLRB configuration of the terminal device is generally different. If the SLRB configuration of the first terminal device changes, the mapping relationship between each PC5 QoS flow of the first terminal device and the SLRB may also change. By obtaining the latest SLRB configuration, the first terminal device can determine the mapping relationship between each PC5 QoS flow of the first terminal device after remapping and the SLRB.
  • the RRC state may include RRC connected state (RRC_CONNECTED), RRC idle state (RRC_IDLE), and RRC inactive state (RRC_INACTIVE).
  • the coverage state refers to whether the terminal device is within the coverage of the network device (in-coverage) or Out-of-coverage (OOC) of the network equipment, only the terminal equipment within the coverage of the network equipment has various RRC states.
  • the first terminal device may obtain the latest SLRB configuration according to the current RRC state or coverage situation. If the first terminal device is currently in the RRC connected state, the first terminal device can receive the latest SLRB configuration from the network device through RRC dedicated signaling; if the first terminal device is currently in the RRC idle state or the RRC inactive state, the first terminal device The latest SLRB configuration can be received from the system information block (SIB) broadcast by the network device; if the first terminal device is in OOC, the first terminal device can obtain the pre-configuraed SLRB configuration.
  • SIB system information block
  • the RRC state or coverage of the first terminal device changes may include the following scenarios: the first terminal device switches from OOC to the RRC idle state, and the first terminal device switches from OOC or The RRC idle state or RRC inactive state transitions to the RRC connected state, the first terminal device transitions from the RRC connected state to the OOC or RRC idle state or the RRC inactive state, and the first terminal device transitions from the RRC idle state or the RRC inactive state to OOC.
  • the RRC state or coverage of the first terminal device remains unchanged, but the SLRB configuration changes may include the following situations: the first terminal device is in the RRC idle state or the RRC inactive state, and the network device accessed by the first terminal device or The SLRB configuration in the SIB of the cell has changed; the first terminal device is in the RRC idle state or the RRC inactive state.
  • the first terminal device Since the first terminal device has performed the cell reselection, the two terminals that the first terminal device accessed before and after the cell reselection The SLRB configuration in the SIB of the cell is different; the first terminal device is in the RRC connected state, and the network device or cell that the first terminal device accesses through the RRC dedicated signaling indicates the SLRB configuration has changed; the first terminal device is in the RRC connected state Since the first terminal device performs the cell handover, the SLRB configurations indicated by the RRC dedicated signaling in the two cells that the first terminal device accesses before and after the cell handover are different.
  • 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 within a first preset time period after it stops delivering the data packet of the first QoS flow to the first SLRB, The data packets of the first QoS flow are buffered in the SDAP buffer.
  • Step S304 After the first preset time period, the first terminal device sends the data packet of the first QoS flow buffered in the SDAP buffer on the second SLRB.
  • the first terminal device after the first terminal device determines that the first QoS flow needs to be remapped to the second SLRB, it can stop submitting the data of the first QoS flow to the first SLRB for transmission, and start sending the data packets of the first QoS flow Cached in SDAP buffer.
  • the first terminal device can stop delivering the data packets of the first QoS flow to the first preset duration after the first SLRB transmission, and then transfer the first QoS flow buffered in the SDAP buffer The data packet is submitted to the second SLRB for transmission.
  • the data packet of the first QoS flow that has been previously delivered to the first SLRB for transmission can be completed within the first preset period of time after the data of the first QoS flow is stopped being delivered to the first SLRB. .
  • the buffered data packets of the first QoS flow are then 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, thereby effectively Ensure that the SDAP layer in the second terminal device on the receiving side can deliver the data packets of the first QoS flow to the upper layer in order.
  • the first preset duration can 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, it can stop delivering the data of the first QoS flow Until the first SLRB is transmitted, a timer is started at the same time, and the duration of the timer is the first preset duration. In this way, the first terminal device can buffer the data packets of the first QoS flow during the operation of the timer, and after the timer expires (that is, the timer stops running), then deliver the buffered data packets of the first QoS flow to Second SLRB transmission.
  • the first terminal device to stop delivering the data packet of the first QoS flow that has undergone remapping to the first SLRB for transmission may be: the first terminal device immediately stops sending the data packet of the first QoS flow to the first SLRB after determining that the first QoS flow needs to be remapped The data packets of the QoS flow are delivered to the first SLRB, or alternatively, the first terminal device determines that the first QoS flow needs to be remapped, and then stops delivering the data packets of the first QoS flow to the second preset period of time.
  • the first SLRB may be: the first terminal device immediately stops sending the data packet of the first QoS flow to the first SLRB after determining that the first QoS flow needs to be remapped The data packets of the QoS flow are delivered to the first SLRB, or alternatively, the first terminal device determines that the first QoS flow needs to be remapped, and then stops delivering the data packets of the first QoS flow to
  • the first terminal device determines that the first QoS flow needs to be remapped according to the latest SLRB configuration.
  • the SDAP entity in the first terminal device can immediately stop submitting the data packet of the first QoS flow to the first SLRB for transmission.
  • the first terminal device buffers the data packet of the first QoS flow in the SDAP buffer.
  • the first terminal device then delivers the data packets of the first QoS flow to the second SLRB for transmission, thereby effectively ensuring that the data packets of the first QoS flow are delivered in order.
  • the first terminal device determines that the first QoS flow needs to be remapped according to the latest SLRB configuration.
  • the SDAP entity in the first terminal device stops delivering the data packet of the first QoS flow to the first SLRB for transmission, and the time interval between time T1 and time T3 is the second preset duration.
  • the first terminal device buffers the data packet of the first QoS flow in the SDAP buffer.
  • the first terminal device submits the data packet of the first QoS flow to the second SLRB for transmission.
  • the second preset duration can also be set by a timer.
  • the first terminal device may start a timer when determining that the first QoS flow needs to be remapped to the second SLRB, and the duration of the timer is the second preset duration. In this way, the first terminal device can stop delivering the data of the first QoS flow to the first SLRB for transmission after the timer expires (that is, the timer stops running).
  • the second possible implementation manner may be applicable to a scenario where the RRC state or coverage situation of the first terminal device changes.
  • the configuration of the SLRB has also changed, and the configuration of the first SLRB may no longer exist.
  • the first SLRB is released immediately, if the data packet of the first QoS flow that has been previously delivered to the first SLRB for transmission has not been transmitted yet, data packet loss will occur.
  • the first terminal device 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 release the first SLRB immediately, but after the first QoS flow is remapped After the second preset time period, stop delivering the data packets of the first QoS flow to the first SLRB, and then release the first SLRB. In this way, it can be ensured that the data packets that have been delivered to the first SLRB can be completely transmitted, thereby ensuring Business continuity of terminal equipment.
  • the first terminal device may release the first SLRB.
  • the first terminal device may release the first SLRB after the first preset period of time after it stops delivering the data packets of the first QoS flow to the first SLRB to ensure service continuity, because During the first preset period of time after stopping the delivery of the data packet of the first QoS flow to the first SLRB, the data packet of the first QoS flow that has been delivered to the first SLRB for transmission may not be completely transmitted.
  • the first terminal device when the first terminal device submits all the data packets of the first QoS flow buffered in the SDAP buffer to the second SLRB for transmission or the first terminal device buffers the data packets of the first QoS flow in the SDAP buffer After submitting to the second SLRB for transmission for the first time, the first terminal device can clear the first SLRB buffer.
  • 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 embodiments of the present application may be equal or unequal.
  • the first preset duration and the second preset duration can have multiple possible configurations.
  • the first preset duration and the second preset duration can be pre-configured or predefined, or the network device can be dedicated through RRC.
  • the signaling or SIB message configuration can also be the upper layer configuration of the terminal device (that is, the configuration of the first terminal device located on the SDAP layer, for example, the V2X layer or the application layer), or it can be implemented based on the terminal device itself.
  • the implementation based on the terminal device may include that the first terminal device determines the preset duration according to one or more QoS parameters associated with the first QoS flow, or the first terminal device determines the preset duration according to its own buffer status, Or the first terminal device determines that the first preset duration expires according to the time when the endmarker corresponding to the first QoS flow is sent.
  • the first terminal device determines the preset duration according to one or more QoS parameters associated with the first QoS flow, or the first terminal device determines the preset duration according to its own buffer status, Or the first terminal device determines that the first preset duration expires according to the time when the endmarker corresponding to the first QoS flow is sent.
  • There may be other implementation manners based on terminal device implementation which is not limited in this application.
  • the first preset duration and the second preset duration can also have multiple possible configuration granularities.
  • the configuration granularity can be per PC5 QoS flow, per SLRB, per SL-LCH, per service, per destination L2 ID, per cast type, per UE, etc., this application is not limited.
  • the configuration granularity of the first preset duration is per PC5 QoS flow means that the corresponding first preset duration is independently configured for each PC5 QoS flow, and the first preset duration corresponding to different PC5 QoS flows can be the same Or not the same.
  • the configuration of the first preset duration and the second preset duration may be the same or different, and this application is not limited.
  • the first preset duration and the second preset duration are configured in the same manner, for example, both the first preset duration and the second preset duration are configured by the network device, then the first preset duration and the second preset duration configured by the network device
  • the set duration can be sent through the same message or through different messages, which is not limited by this application.
  • the configuration granularity of the first preset duration and the second preset duration may be the same or different, which is also not limited in this application.
  • any of the above configuration modes and configuration granularity can be combined with each other.
  • FIG. 7 is a schematic flowchart of another sidelink communication method provided by an embodiment of this application.
  • the method specifically includes the following steps S701 to S704:
  • Step S701 The second terminal device receives the data of the first QoS flow on the first SLRB.
  • the first terminal device refers to the terminal device on the sending side
  • the second terminal device refers to the terminal device on the receiving side, that is, the first terminal device sends data to the second terminal device through the sideline communication link.
  • the communication based on the side-line communication link between the first terminal device and the second terminal device is unicast.
  • the first QoS flow refers to the PC5 QoS flow where remapping occurs.
  • the first QoS flow is changed from the original mapping to the first SLRB to the second SLRB, where the first SLRB is the source SLRB, and the second SLRB is the target SLRB.
  • the reason for the remapping of the first QoS flow may be that the RRC state or coverage of the first terminal device has changed, or it may be that although the RRC state or coverage of the first terminal device remains unchanged, the SLRB configuration of the first terminal device Changes have taken place, please refer to the first embodiment for details, which will not be repeated here.
  • 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.
  • the first terminal device can obtain the latest SLRB configuration. 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 can The configuration information of the second SLRB is sent to the second terminal device 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 used to indicate the QoS flow corresponding to the second SLRB, such as the identification of the first QoS flow.
  • the identification may be the QFI of the QoS flow, or it may be used inside the terminal device to identify a QoS Other identification information of the stream. In this way, the second terminal device may determine that the first QoS flow needs to be remapped to the second SLRB according to the received configuration information of the second SLRB.
  • the configuration information of the second SLRB may also include the configuration parameters of the second SLRB itself, such as the configuration parameters of the PDCP entity, the RLC entity, and the LCH in the second SLRB.
  • the second terminal device may establish the second SLRB according to the received configuration information of the second SLRB.
  • the first terminal device may send a PC5 RRC message to the second terminal device, and the PC5 RRC message carries the configuration information of the second SLRB.
  • the first terminal device may also communicate with the first terminal device.
  • the latest SLRB configuration related to the two terminal devices is carried in the PC5 RRC message and sent to the second terminal device.
  • the first terminal device may also send a PC5 RRC message to the second terminal device, and the PC5 RRC message carries a message for indicating the second SLRB.
  • 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.
  • Step S704 After the third preset time period has elapsed, the SDAP entity of the second terminal device submits the data packet received from the second SLRB buffered in the SDAP buffer to the upper layer for processing.
  • 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 time period after determining that the first QoS flow needs to be remapped. After the third preset time period ends, the buffered data packet received from the second SLRB is then submitted to the upper layer for processing. In this way, within the third preset time period after the second terminal device determines that the first QoS flow needs to be remapped, the SDAP layer of the second terminal device can continue to receive the data packets of the first QoS flow from the first SLRB and deliver them To the upper management.
  • the SDAP layer of the second terminal device submits the data packet received on the second SLRB to the upper layer after the third preset duration ends, so that the SDAP layer can receive the data of the first QoS flow from the first SLRB After the packet is submitted to the upper layer for processing, the data packet of the first QoS flow received from the second SLRB is then delivered, so as to ensure that the SDAP layer of the second terminal device can deliver the data packets of the first QoS flow in order.
  • the second terminal device determines that the first QoS flow needs to be remapped.
  • the SDAP entity in the second terminal device buffers the data packet received from the second SLRB in the SDAP buffer.
  • the second terminal device submits the data packets received from the second SLRB buffered in the SDAP buffer to the upper layer for processing, thereby effectively ensuring that the data packets of the first QoS flow are processed Order submission.
  • the upper layer refers to the upper layer of the SDAP layer in the protocol stack, such as the V2X layer and the application layer.
  • the data packets received from the second SLRB may also include data packets of other QoS flows except the first QoS flow. . If the SDAP layer of the second terminal device cannot distinguish or does not distinguish the data packets of each QoS flow transmitted on the same SLRB, the SDAP layer of the second terminal device can equalize the data packets received from the second SLRB during this period of time. It is cached in the SDAP cache, and after the third preset time period ends, it is then submitted to the upper layer for processing.
  • the second terminal device can identify the received data from the second SLRB according to the identification information
  • the SDAP entity of the second terminal device may also only buffer the received data packets of the first QoS flow.
  • the identification information is the PFI associated with the QoS flow.
  • the second terminal device may release the first SLRB after determining that the first QoS flow needs to be remapped to the second SLRB for a third preset period of time.
  • the second terminal device when the second terminal device delivers all the data packets of the first QoS flow buffered in the SDAP buffer to the upper layer or the first terminal device delivers the data packets of the first QoS flow buffered in the SDAP buffer for the first time After giving to the upper layer, the second terminal device can clear the first SLRB buffer.
  • the first SLRB buffer includes a first PDCP buffer, a first RLC buffer, or a first LCH buffer.
  • the third preset duration can also be set by a timer.
  • the first terminal device may start a timer while determining that the first QoS flow needs to be remapped to the second SLRB, and the duration of the timer is the third preset duration.
  • the first terminal device can buffer the data packet received from the second SLRB in the SDAP buffer during the operation of the timer, and after the timer expires (that is, the timer stops running), it can stop buffering from the second SLRB.
  • the second SLRB receives the data packet, and submits the buffered data packet received from the second SLRB to the upper layer for processing.
  • the configuration method and configuration granularity of the third preset duration may refer to the first preset duration or the second preset duration, and details are not described herein again.
  • the second terminal device determines that the third preset duration expires according to the moment when the endmarker corresponding to the first QoS flow is received.
  • FIG. 9 is a schematic flowchart of another sidelink communication method according to an embodiment of this application.
  • the method specifically includes the following steps S901 to S903:
  • Step S901 The first terminal device sends the data of the first QoS flow on the first SLRB.
  • the first terminal device refers to the terminal device on the sending side
  • the second terminal device refers to the terminal device on the receiving side, that is, the first terminal device sends data to the second terminal device through the sideline communication link.
  • the communication based on the lateral communication link between the first terminal device and the second terminal device may be unicast, multicast, or broadcast, which is not limited in this application.
  • the first QoS flow refers to the PC5 QoS flow where remapping occurs.
  • the first QoS flow is changed from the original mapping to the first SLRB to the second SLRB, where the first SLRB is the source SLRB, and the second SLRB is the target SLRB.
  • the reason for the remapping of the first QoS flow may be that the RRC state or coverage of the first terminal device has changed, or it may be that although the RRC state or coverage of the first terminal device remains unchanged, the SLRB configuration of the first terminal device Changes have taken place, please refer to the first embodiment for details, which will not be repeated here.
  • Step S902 The first terminal device obtains 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 configuration information of the second SLRB also indicates that the first SLRB needs to be released.
  • step S902 please refer to the first embodiment, which will not be repeated here.
  • Step S903 The first terminal device releases the first SLRB after a fourth preset period of time after acquiring the configuration information of the second SLRB.
  • the first terminal device may not release the first SLRB immediately, and release the first SLRB again after the fourth preset period of time has elapsed. In this way, in the case of remapping of the first QoS flow, data packets that have been delivered to the first SLRB for transmission before remapping can be sent to the second terminal device, thereby ensuring service continuity.
  • This method can be applied to a scenario where the RRC status or coverage situation of the first terminal device 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 SLRB configuration obtained by the first terminal device through the SIB message will be invalid, and the first terminal device needs to pass the RRC The signaling obtains the latest SLRB configuration from the network equipment. In this scenario, the first SLRB configured by the network device through the SIB message needs to be released.
  • the first terminal device may determine, according to the acquired latest SLRB configuration, that the first QoS flow needs to be remapped from the first SLRB to the second SLRB, and the first SLRB needs to be released. However, if the first SLRB is released immediately at this time, the data packet of the first QoS flow that has been delivered to the first SLRB for transmission may not be completely transmitted, resulting in data packet loss in the first QoS flow. In this way, after determining 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 period of time, which can effectively ensure the service continuity of the first terminal device and avoid There is a data packet loss situation.
  • the first terminal device determines that the first QoS flow needs to be remapped.
  • the first terminal device can receive the data packet from the first SLRB as usual, and submit it to the upper layer for processing.
  • the first terminal device stops receiving data packets from the first SLRB and releases the first SLRB.
  • the fourth preset duration can also be set by a timer.
  • the first terminal device may start a timer while determining that the first QoS flow is remapped from the first SLRB to the second SLRB, and the duration of the timer is the fourth preset duration. In this way, the first terminal device can release the first SLRB after the timer expires (that is, the timer stops running).
  • the configuration method and configuration granularity of the fourth preset duration may refer to the first preset duration, the second preset duration, or the third preset duration, which will not be repeated here.
  • the various method embodiments provided in this application can be combined with each other.
  • the first or second embodiment can also be combined to further ensure that the data packets of the first QoS flow can be delivered in order on the receiving side.
  • FIG. 11 is a schematic structural diagram of another communication device provided in an embodiment of this application.
  • the communication device 1100 includes a transceiver module 1110 and a processing module 1120.
  • the communication device can be used to implement the functions related to terminal equipment in any of the foregoing method embodiments.
  • the communication device may be a terminal device, such as a handheld terminal device or a vehicle-mounted terminal device; the communication device may also be a chip included in the terminal device, or a device including the terminal device, such as various types of vehicles.
  • the transceiver module 1110 is used to send the data of the first QoS flow on the first SLRB and obtain the configuration information of the second SLRB,
  • 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 stop sending data packets of the first QoS flow on the first SLRB, and send the first QoS flow within a first preset time period after stopping sending the data packets of the first QoS flow on the first SLRB.
  • the data packets of the flow are buffered in the SDAP buffer.
  • the transceiver module 1110 is further configured to send the data packet of the first QoS flow buffered in the SDAP buffer on the second SLRB after the first preset time period has elapsed.
  • the processing module 1120 is specifically configured to immediately stop sending data packets of the first QoS flow on the first SLRB after acquiring the configuration information of the second SLRB; or, after acquiring the second SLRB After a second preset period of time after the configuration information, stop sending the data packet of the first QoS flow on the first SLRB.
  • the processing module 1120 is further configured to establish the second SLRB according to the configuration information of the second SLRB.
  • the processing module 1120 is further configured to release the first SLRB after a first preset period of time after stopping sending the data packet of the first QoS flow on the first SLRB.
  • the transceiver module 1110 is used to receive the data of the first QoS flow on the first SLRB and the second terminal device from the first terminal device.
  • Configuration information of the 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 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 after the third preset time period has elapsed , Submit the data packet received from the second SLRB buffered in the SDAP buffer to the upper layer for processing.
  • the processing module 1120 is further configured to establish the second SLRB according to the configuration information of the second SLRB.
  • the processing module 1120 is further configured to release the first SLRB after the third preset time period has elapsed.
  • the transceiver module 1110 is used to send the data of the first QoS flow on the first SLRB and obtain the configuration information of the second SLRB,
  • 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 period of time after obtaining the configuration information of the second SLRB.
  • the processing module 1120 is further configured to establish the second SLRB according to the configuration information of the second SLRB.
  • 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 operation and/or function of each module in the communication device is to implement the corresponding process of the method shown in FIG. 3 to FIG. 10, and is not repeated here for brevity.
  • FIG. 12 is a schematic diagram of another structure of a communication device provided in an embodiment of the present application.
  • the communication device may specifically be a terminal device. It is easy to understand and easy to illustrate.
  • the terminal device uses a mobile phone as an example.
  • the terminal device includes a processor, and may also include a memory, and of course, it may also include a radio frequency circuit, an antenna, an input and output device, and so on.
  • the processor is mainly used to process the communication protocol and communication data, and to control the terminal device, execute the software program, and process the data of the software program.
  • the memory is mainly used to store software programs and data.
  • the radio frequency circuit is mainly used for the conversion of baseband signals and radio frequency signals and the processing of radio frequency signals.
  • the antenna is mainly used to send and receive radio frequency signals in the form of electromagnetic waves.
  • Input and output devices such as touch screens, display screens, keyboards, etc., are mainly used to receive data input by users and output data to users. It should be noted that some types of terminal devices may not have input and output devices.
  • the processor When data needs to be sent, the processor performs baseband processing on the data to be sent, and then outputs the baseband signal to the radio frequency circuit.
  • the radio frequency circuit performs radio frequency processing on the baseband signal and sends the radio frequency signal to the outside in the form of electromagnetic waves through the antenna.
  • the radio frequency circuit receives the 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.
  • FIG. 12 only one memory and processor are shown in FIG. 12. In an actual terminal 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.
  • the memory may be set independently of the processor, or may be integrated with the processor, which is not limited in the embodiment of the present application.
  • the antenna and radio frequency circuit with the transceiving function can be regarded as the transceiving unit of the terminal device
  • the processor with the processing function can be regarded as the processing unit of the terminal device.
  • the terminal device includes a transceiver unit 1210 and a processing unit 1220.
  • the transceiving unit may also be referred to as a transceiver, a transceiver, a transceiving device, and so on.
  • the processing unit may also be called a processor, a processing board, a processing module, a processing device, and so on.
  • the device for implementing the receiving function in the transceiver unit 1210 can be regarded as the receiving unit, and the device for implementing the sending function in the transceiver unit 1210 as the sending unit, that is, the transceiver unit 1210 includes a receiving unit and a sending unit.
  • the transceiver unit may sometimes be referred to as a transceiver, a transceiver, or a transceiver circuit.
  • the receiving unit may sometimes be called a receiver, a receiver, or a receiving circuit.
  • the transmitting unit may sometimes be called a transmitter, a transmitter, or a transmitting circuit.
  • transceiving unit 1210 is used to perform sending and receiving operations on the terminal device side in the foregoing method embodiment
  • processing unit 1220 is used to perform other operations on the terminal device in the foregoing method embodiment except for the transceiving operation.
  • An embodiment of the present application also provides a chip system, including: a processor, the processor is coupled with a memory, the memory is used to store a program or instruction, when the program or instruction is executed by the processor, the The chip system implements the method in any of the foregoing method embodiments.
  • processors in the chip system there may be one or more processors in the chip system.
  • the processor can be implemented by hardware or software.
  • the processor may be a logic circuit, an integrated circuit, or the like.
  • the processor may be a general-purpose processor, which is implemented by reading software codes stored in the memory.
  • the memory may be integrated with the processor, or may be provided separately from the processor, which is not limited in this application.
  • the memory may be a non-transitory processor, such as a read-only memory ROM, which may be integrated with the processor on the same chip, or may be set on different chips.
  • the setting method of the processor is not specifically limited.
  • the chip system may be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or a system on chip (SoC). It can also be a central processor unit (CPU), a network processor (NP), a digital signal processing circuit (digital signal processor, DSP), or a microcontroller (microcontroller).
  • the controller unit, MCU may also be a programmable controller (programmable logic device, PLD) or other integrated chips.
  • each step in the foregoing method embodiments may be completed by an integrated logic circuit of hardware in a processor or instructions in the form of software.
  • the steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed and completed by a hardware processor, or executed and completed by a combination of hardware and software modules in the processor.
  • the embodiment of the present application also provides a computer-readable storage medium, which stores computer-readable instructions, and when the computer reads and executes the computer-readable instructions, the computer is caused to execute any of the above-mentioned method embodiments In the method.
  • the embodiments of the present application also provide a computer program product.
  • the computer reads and executes the computer program product, the computer is caused to execute the method in any of the foregoing method embodiments.
  • An embodiment of the present application also provides a communication system, which includes a first terminal device and a second terminal device.
  • processors mentioned in the embodiments of this application may be a central processing unit (central processing unit, CPU), or other general-purpose processors, digital signal processors (digital signal processors, DSP), and application-specific integrated circuits ( application specific integrated circuit (ASIC), ready-made programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc.
  • CPU central processing unit
  • DSP digital signal processors
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the memory mentioned in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory can be read-only memory (ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), and electrically available Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be random access memory (RAM), which is used as an external cache.
  • RAM random access memory
  • static random access memory static random access memory
  • dynamic RAM dynamic RAM
  • DRAM dynamic random access memory
  • synchronous dynamic random access memory synchronous DRAM, 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 connection dynamic random access memory serial DRAM, SLDRAM
  • direct rambus RAM direct rambus RAM, DR RAM
  • the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component
  • the memory storage module
  • the size of the sequence numbers of the above-mentioned processes does not mean the order of execution.
  • the execution order of the processes should be determined by their functions and internal logic, and should not be used in the embodiments of the present invention.
  • the implementation process constitutes any limitation.
  • the disclosed system, device, and method can be implemented in other ways.
  • the device embodiments described above are merely illustrative, for example, the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of the present application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Procédé et appareil de communication de liaison latérale. Le procédé comprend les étapes suivantes : après qu'un premier dispositif terminal détermine un remappage d'un premier flux de QoS vers une seconde SLRB, une entité SDAP du premier dispositif terminal cesse d'envoyer un paquet de données du premier flux de QoS sur une première SLRB, et met en cache le paquet de données du premier flux QoS dans une zone tampon SDAP pendant une première durée prédéfinie après l'arrêt de l'envoi du paquet de données du premier flux de QoS sur la première SLRB, et envoie le paquet de données mis en cache du premier flux de QoS sur la seconde SLRB après la première durée prédéfinie. Ainsi, un paquet de données transmis par la seconde SLRB arrive après un paquet de données transmis par la première SLRB, pour assurer efficacement qu'une couche SDAP sur le côté réception peut délivrer les paquets de données du premier flux de QoS à la couche supérieure dans l'ordre.
PCT/CN2019/128898 2019-12-26 2019-12-26 Procédé et appareil de communication de liaison latérale WO2021128218A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201980103025.5A CN114830803A (zh) 2019-12-26 2019-12-26 一种侧行链路通信方法及装置
PCT/CN2019/128898 WO2021128218A1 (fr) 2019-12-26 2019-12-26 Procédé et appareil de communication de liaison latérale

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/128898 WO2021128218A1 (fr) 2019-12-26 2019-12-26 Procédé et appareil de communication de liaison latérale

Publications (1)

Publication Number Publication Date
WO2021128218A1 true WO2021128218A1 (fr) 2021-07-01

Family

ID=76572963

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/128898 WO2021128218A1 (fr) 2019-12-26 2019-12-26 Procédé et appareil de communication de liaison latérale

Country Status (2)

Country Link
CN (1) CN114830803A (fr)
WO (1) WO2021128218A1 (fr)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107079530A (zh) * 2015-01-30 2017-08-18 松下电器（美国）知识产权公司 用于侧行链路逻辑信道的逻辑信道优先级排序过程
CN109952806A (zh) * 2019-02-14 2019-06-28 北京小米移动软件有限公司 Sr配置的确定方法、装置及存储介质
CN110267311A (zh) * 2016-01-27 2019-09-20 华为技术有限公司 通信方法、网络侧设备及终端
WO2019185830A1 (fr) * 2018-03-29 2019-10-03 Fraunhofer-Gesellschaft zur Förderung der angewandten Forschung e.V. Qualité de service améliorée pour v2x
CN110312228A (zh) * 2018-03-27 2019-10-08 现代自动车株式会社 用于在v2x通信系统中利用聚合载波进行通信的方法和装置
WO2019221826A1 (fr) * 2018-05-16 2019-11-21 Qualcomm Incorporated Découpage de ressources en tranches sur une interface de liaison latérale
WO2019240548A1 (fr) * 2018-06-14 2019-12-19 Lg Electronics Inc. Procédé et appareil pour réaliser une communication de liaison latérale par un ue dans un nr v2x

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107079530A (zh) * 2015-01-30 2017-08-18 松下电器（美国）知识产权公司 用于侧行链路逻辑信道的逻辑信道优先级排序过程
CN110267311A (zh) * 2016-01-27 2019-09-20 华为技术有限公司 通信方法、网络侧设备及终端
CN110312228A (zh) * 2018-03-27 2019-10-08 现代自动车株式会社 用于在v2x通信系统中利用聚合载波进行通信的方法和装置
WO2019185830A1 (fr) * 2018-03-29 2019-10-03 Fraunhofer-Gesellschaft zur Förderung der angewandten Forschung e.V. Qualité de service améliorée pour v2x
WO2019221826A1 (fr) * 2018-05-16 2019-11-21 Qualcomm Incorporated Découpage de ressources en tranches sur une interface de liaison latérale
WO2019240548A1 (fr) * 2018-06-14 2019-12-19 Lg Electronics Inc. Procédé et appareil pour réaliser une communication de liaison latérale par un ue dans un nr v2x
CN109952806A (zh) * 2019-02-14 2019-06-28 北京小米移动软件有限公司 Sr配置的确定方法、装置及存储介质

Also Published As

Publication number Publication date
CN114830803A (zh) 2022-07-29

Similar Documents

Publication Publication Date Title
WO2021159906A1 (fr) Procédé et appareil de communication de relais de liaison latérale, dispositif et support
US11405964B2 (en) Radio bearer configuration method, apparatus, and system
WO2018170914A1 (fr) Procédé et appareil de transmission d'un bloc d'informations système
JP7277002B2 (ja) 通信方法及び装置
WO2022110168A1 (fr) Procédé de configuration de communication et appareil de communication
US20230261826A1 (en) Communication method and apparatus
WO2021004191A1 (fr) Procédé et appareil permettant de prendre en charge un réseau sensible au temps
WO2019223639A1 (fr) Procédé et dispositif de communication sans fil
WO2021203998A1 (fr) Procédé et dispositif de communication
CN115699816A (zh) 用于在双连接下进行侧行链路中继通信的方法
WO2021027790A1 (fr) Procédé et appareil de communication de liaison latérale
WO2021237525A1 (fr) Procédé et dispositif de communication sans fil
US20230099586A1 (en) Communication method and related apparatus
WO2022027523A1 (fr) Procédé de configuration d'informations auxiliaires et appareil de communication
WO2021128218A1 (fr) Procédé et appareil de communication de liaison latérale
WO2021213014A1 (fr) Procédé et appareil de communication
WO2020156394A1 (fr) Procédé et appareil de rétroaction
WO2021134763A1 (fr) Procédé, appareil et dispositif de récupération de transmission
WO2021056584A1 (fr) Procédé et appareil de communication
WO2024060200A1 (fr) Procédés et appareils de communication, et dispositif, support d'enregistrement, puce, produit et programme
WO2024065137A1 (fr) Procédé d'acquisition d'informations de configuration, procédé de transfert d'informations de configuration et équipement terminal
WO2023093889A1 (fr) Procédé et appareil de communication par liaison latérale
WO2023169451A1 (fr) Procédé et appareil de communication et support d'informations
WO2022233011A1 (fr) Procédé d'établissement de connexion, et dispositif terminal
WO2022126412A1 (fr) Procédé et appareil de réinitialisation de configuration et dispositif de terminal

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19957602

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19957602

Country of ref document: EP

Kind code of ref document: A1