WO2022236682A1 - Procédé de transmission de liaison latérale, dispositif terminal et dispositif de réseau - Google Patents

Procédé de transmission de liaison latérale, dispositif terminal et dispositif de réseau Download PDF

Info

Publication number
WO2022236682A1
WO2022236682A1 PCT/CN2021/093069 CN2021093069W WO2022236682A1 WO 2022236682 A1 WO2022236682 A1 WO 2022236682A1 CN 2021093069 W CN2021093069 W CN 2021093069W WO 2022236682 A1 WO2022236682 A1 WO 2022236682A1
Authority
WO
WIPO (PCT)
Prior art keywords
data packet
version
information
terminal
type
Prior art date
Application number
PCT/CN2021/093069
Other languages
English (en)
Chinese (zh)
Inventor
张博源
卢前溪
Original Assignee
Oppo广东移动通信有限公司
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 Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to CN202180090568.5A priority Critical patent/CN116762365A/zh
Priority to PCT/CN2021/093069 priority patent/WO2022236682A1/fr
Publication of WO2022236682A1 publication Critical patent/WO2022236682A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor

Definitions

  • the embodiments of the present application relate to the field of communications, and in particular to a method for lateral transmission, a terminal device, and a network device.
  • the present application provides a method for sideline transmission, a terminal device and a network device.
  • the sending end indicates the version information of the data packet or the PDCP SDU type of the data packet through the associated information of the sent data packet, so that the receiving end
  • the PDCP SDU type corresponding to the information or data packet determines whether to receive the data packet, which is beneficial to avoid the waste of resources caused by receiving the unsupported version of the data packet.
  • a method for lateral transmission including: the first terminal determines the version information of the first data packet or the first data packet according to the associated information of the first data packet sent by the second terminal Packet Data Convergence Protocol PDCP Service Data Unit SDU type;
  • a method for lateral transmission including: the second terminal sends a first data packet to the first terminal, wherein the associated information of the first data packet is used to determine the information of the first data packet The version information or the packet data convergence protocol PDCP service data unit SDU type of the first data packet.
  • a sidelink transmission method including: a network device sends first information to a terminal device, wherein the first information is used to determine version information of a sidelink data packet or the sidelink data packet Packet Data Convergence Protocol PDCP Service Data Unit SDU type.
  • a terminal device configured to execute the method in any one of the above-mentioned first aspect to the second aspect or in each implementation manner thereof.
  • the terminal device includes a functional module configured to execute any one of the above first aspect to the second aspect or the method in each implementation manner thereof.
  • a network device configured to execute the method in the above third aspect or various implementation manners thereof.
  • the network device includes a functional module for executing the method in the above third aspect or each implementation manner thereof.
  • a terminal device including a processor and a memory.
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program stored in the memory, and execute any one of the above-mentioned first to second aspects or the method in each implementation manner.
  • a network device including a processor and a memory.
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program stored in the memory to execute the method in the above third aspect or its various implementations.
  • a computer-readable storage medium for storing a computer program, and the computer program causes a computer to execute any one of the above-mentioned first to third aspects or the method in each implementation manner thereof.
  • a computer program product including computer program instructions, the computer program instructions causing a computer to execute any one of the above first to third aspects or the method in each implementation manner thereof.
  • a computer program which, when running on a computer, causes the computer to execute any one of the above-mentioned first to third aspects or the method in each implementation manner.
  • a chip is provided for implementing any one of the first aspect to the third aspect or the method in each implementation manner thereof.
  • the chip includes: a processor, configured to call and run a computer program from the memory, so that the device installed with the device executes any one of the above-mentioned first to third aspects or any of the implementations thereof. method.
  • the first terminal when the second terminal sends the first data packet to the first terminal, the first terminal can determine whether to receive the first data packet according to the associated information of the first data packet, for example, according to The associated information of the first data packet determines the version information of the first data packet or the PDCP SDU type of the first data packet, and further according to the version information of the first data packet or the PDCP SDU type of the first data packet, Determining whether to receive the first data packet is beneficial to avoid resource waste caused by receiving a data packet of an unsupported version.
  • Fig. 1 is a schematic diagram of a communication system architecture provided by the present application.
  • Fig. 2 is a schematic diagram of another communication system architecture provided by the present application.
  • Fig. 3 is a schematic diagram of unicast sidelink communication provided by the present application.
  • Fig. 4 is a schematic diagram of multicast sideline communication provided by the present application.
  • Fig. 5 is a schematic diagram of broadcast sideline communication provided by the present application.
  • FIG. 6 is a schematic diagram of the format of a MAC PDU according to an embodiment of the present application.
  • FIG. 7 is a schematic diagram of the format of a MAC PDU subheader according to an embodiment of the present application.
  • Fig. 8 is a schematic interactive diagram of a method for lateral transmission according to an embodiment of the present application.
  • Fig. 9 is a schematic block diagram of a terminal device provided according to an embodiment of the present application.
  • Fig. 10 is a schematic block diagram of another terminal device provided according to an embodiment of the present application.
  • Fig. 11 is a schematic block diagram of a network device provided according to an embodiment of the present application.
  • Fig. 12 is a schematic block diagram of a communication device provided according to an embodiment of the present application.
  • Fig. 13 is a schematic block diagram of a chip provided according to an embodiment of the present application.
  • Fig. 14 is a schematic block diagram of a communication system provided according to an embodiment of the present application.
  • the technical solution of the embodiment of the present application can be applied to various communication systems, such as: Global System of Mobile communication (Global System of Mobile communication, GSM) system, code division multiple access (Code Division Multiple Access, CDMA) system, broadband code division multiple access (Wideband Code Division Multiple Access, WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced long term evolution (LTE-A) system , New Radio (NR) system, evolution system of NR system, LTE (LTE-based access to unlicensed spectrum, LTE-U) system on unlicensed spectrum, NR (NR-based access to unlicensed spectrum) on unlicensed spectrum unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunications System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (Wireless Fidelity, WiFi), fifth-generation communication (5th-Generation, 5G) system or other communication systems, etc.
  • GSM Global System of Mobile
  • D2D Device to Device
  • M2M Machine to Machine
  • MTC Machine Type Communication
  • V2V Vehicle to Vehicle
  • V2X Vehicle to everything
  • the communication system in the embodiment of the present application may be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, may also be applied to a dual connectivity (Dual Connectivity, DC) scenario, and may also be applied to an independent (Standalone, SA) deployment Web scene.
  • Carrier Aggregation, CA Carrier Aggregation
  • DC Dual Connectivity
  • SA independent deployment Web scene
  • the communication system in the embodiment of the present application may be applied to an unlicensed spectrum, where the unlicensed spectrum may also be considered as a shared spectrum; or, the communication system in the embodiment of the present application may also be applied to a licensed spectrum, where, Licensed spectrum can also be considered as non-shared spectrum.
  • the embodiments of the present application describe various embodiments in conjunction with network equipment and terminal equipment, wherein the terminal equipment may also be referred to as user equipment (User Equipment, UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.
  • user equipment User Equipment, UE
  • access terminal user unit
  • user station mobile station
  • mobile station mobile station
  • remote station remote terminal
  • mobile device user terminal
  • terminal wireless communication device
  • wireless communication device user agent or user device
  • the terminal device can be a station (STATION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital assistant (Personal Digital Assistant, PDA) devices, handheld devices with wireless communication functions, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, next-generation communication systems such as terminal devices in NR networks, or future Terminal equipment in the evolved public land mobile network (Public Land Mobile Network, PLMN) network, etc.
  • PLMN Public Land Mobile Network
  • the terminal device can be deployed on land, including indoor or outdoor, handheld, wearable or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air (such as aircraft, balloons and satellites) superior).
  • the terminal device may be a mobile phone (Mobile Phone), a tablet computer (Pad), a computer with a wireless transceiver function, a virtual reality (Virtual Reality, VR) terminal device, an augmented reality (Augmented Reality, AR) terminal Equipment, wireless terminal equipment in industrial control, wireless terminal equipment in self driving, wireless terminal equipment in remote medical, wireless terminal equipment in smart grid , wireless terminal equipment in transportation safety, wireless terminal equipment in smart city, or wireless terminal equipment in smart home.
  • a virtual reality (Virtual Reality, VR) terminal device an augmented reality (Augmented Reality, AR) terminal Equipment
  • wireless terminal equipment in industrial control wireless terminal equipment in self driving
  • wireless terminal equipment in remote medical wireless terminal equipment in smart grid
  • wireless terminal equipment in transportation safety wireless terminal equipment in smart city, or wireless terminal equipment in smart home.
  • the terminal device may also be a wearable device.
  • Wearable devices can also be called wearable smart devices, which is a general term for the application of wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not only a hardware device, but also achieve powerful functions through software support, data interaction, and cloud interaction.
  • Generalized wearable smart devices include full-featured, large-sized, complete or partial functions without relying on smart phones, such as smart watches or smart glasses, etc., and only focus on a certain type of application functions, and need to cooperate with other devices such as smart phones Use, such as various smart bracelets and smart jewelry for physical sign monitoring.
  • the network device may be a device for communicating with the mobile device, and the network device may be an access point (Access Point, AP) in WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA , or a base station (NodeB, NB) in WCDMA, or an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and an NR network A network device or a base station (gNB) in a network device or a network device in a future evolved PLMN network or a network device in an NTN network.
  • AP Access Point
  • BTS Base Transceiver Station
  • NodeB, NB base station
  • Evolutional Node B, eNB or eNodeB evolved base station
  • LTE Long Term Evolution
  • eNB evolved base station
  • gNB base station
  • the network device may have a mobile feature, for example, the network device may be a mobile device.
  • the network equipment may be a satellite or a balloon station.
  • the satellite can be a low earth orbit (low earth orbit, LEO) satellite, a medium earth orbit (medium earth orbit, MEO) satellite, a geosynchronous earth orbit (geosynchronous earth orbit, GEO) satellite, a high elliptical orbit (High Elliptical Orbit, HEO) satellite. ) Satellite etc.
  • the network device may also be a base station installed on land, water, and other locations.
  • the network device may provide services for a cell, and the terminal device communicates with the network device through the transmission resources (for example, frequency domain resources, or spectrum resources) used by the cell, and the cell may be a network device ( For example, a cell corresponding to a base station), the cell may belong to a macro base station, or may belong to a base station corresponding to a small cell (Small cell), and the small cell here may include: a metro cell (Metro cell), a micro cell (Micro cell), a pico cell ( Pico cell), Femto cell, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.
  • the transmission resources for example, frequency domain resources, or spectrum resources
  • the cell may be a network device (
  • the cell may belong to a macro base station, or may belong to a base station corresponding to a small cell (Small cell)
  • the small cell here may include: a metro cell (Metro cell), a micro cell (Micro
  • the "indication" mentioned in the embodiments of the present application may be a direct indication, may also be an indirect indication, and may also mean that there is an association relationship.
  • a indicates B which can mean that A directly indicates B, for example, B can be obtained through A; it can also indicate that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also indicate that there is an association between A and B relation.
  • the term "corresponding" may indicate that there is a direct or indirect correspondence between the two, or that there is an association between the two, or that it indicates and is indicated, configuration and is configuration etc.
  • predefined or “preconfigured” can be realized by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in devices (for example, including terminal devices and network devices).
  • the application does not limit its specific implementation.
  • pre-defined may refer to defined in the protocol.
  • the "protocol” may refer to a standard protocol in the communication field, for example, may include the LTE protocol, the NR protocol, and related protocols applied to future communication systems, which is not limited in the present application.
  • Fig. 1 is a schematic diagram of a communication system to which the embodiment of the present application is applicable.
  • the transmission resources of the vehicle-mounted terminals (vehicle-mounted terminal 121 and vehicle-mounted terminal 122 ) are allocated by the base station 110 , and the vehicle-mounted terminals transmit data on the sidelink according to the resources allocated by the base station 110 .
  • the base station 110 may allocate resources for a single transmission to the terminal, or may allocate resources for semi-static transmission to the terminal.
  • Fig. 2 is a schematic diagram of another communication system to which the embodiment of the present application is applicable.
  • the vehicle-mounted terminals (vehicle-mounted terminal 131 and vehicle-mounted terminal 132 ) autonomously select transmission resources on sidelink resources for data transmission.
  • the vehicle-mounted terminal may select transmission resources randomly, or select transmission resources by listening.
  • unicast transmission there is only one terminal at the receiving end, as shown in Figure 3, unicast transmission is performed between UE1 and UE2; for multicast transmission, the receiving end is all terminals in a communication group, or in a certain All terminals within the transmission distance, as shown in Figure 4, UE1, UE2, UE3 and UE4 form a communication group, in which UE1 sends data, and other terminal devices in the group are receiving terminals; for broadcast transmission mode, its receiving An end is any terminal around the transmitting terminal. As shown in FIG. 5 , UE1 is the transmitting terminal, and other terminals around it, UE2-UE6 are all receiving terminals.
  • the transmitting terminal can generate a Media Access Control (Media Access Control, MAC) Protocol Data Unit (Protocol Data Unit, PDU) according to the data to be transmitted, and send the MAC PDU to the receiving terminal.
  • Media Access Control Media Access Control
  • PDU Protocol Data Unit
  • a MAC PDU includes a MAC PDU subheader (subheader), 0 or at least one MAC sub-PDU (subPDU), and possibly padding bits.
  • Figure 6 is an example of a MAC PDU format.
  • a MAC subPDU can include a subheader of a MAC subPDU, and a subheader of a MAC subPDU can correspond to a MAC service data unit (service data unit, SDU) or a MAC control element (MAC Control Element, MAC CE) or Padding bits.
  • SDU service data unit
  • MAC CE MAC Control Element
  • the subheader of a MAC subPDU may include at least one of the following fields:
  • L length field, used to indicate the length of MAC SDU or MAC CE, in bytes
  • LCID Logical Channel ID field.
  • FIG. 7 is a schematic diagram of the format of a subheader of a MAC PDU. Among them, the meaning of each field in the subheader of the MAC PDU is as follows:
  • V version field, which occupies 4 bits and is set to all 0;
  • R reserved (reserved) bit, set to 0;
  • SRC source address field, occupying 16 bits, carrying 16 bits of the most effective source layer 2 (layer2) identification (Identify, ID);
  • DST Destination address field, which occupies 8 bits and carries the most effective 8-bit target layer 2 (layer2) ID.
  • ARP Address Resolution Protocol
  • PDCP Packet Data Convergence Protocol
  • Fig. 3 is a schematic interaction diagram of a method for lateral transmission according to an embodiment of the present application. As shown in Fig. 3 , the method 300 may include at least part of the following:
  • the second terminal sends the first data packet to the first terminal
  • the first terminal determines the version information of the first data packet or the packet data convergence protocol PDCP service data unit SDU type of the first data packet according to the associated information of the first data packet sent by the second terminal;
  • the first terminal when the second terminal sends the first data packet to the first terminal, the first terminal can determine whether to receive the first data packet according to the associated information of the first data packet , for example, determine the version information of the first data packet or the PDCP SDU type of the first data packet according to the associated information of the first data packet, further according to the version information of the first data packet or the first data packet.
  • the PDCP SDU type determines whether to receive the first data packet, which is beneficial to avoid the waste of resources caused by receiving and parsing data of unsupported versions.
  • the version information of the first data package is one of at least two versions.
  • the at least two versions include a first version and a second version.
  • the first version may include Rel-17
  • the second version may include Rel-16.
  • the first version supports ARP type packets
  • the second version does not support ARP type packets
  • the ARP-type data packet may be replaced by an ARP-type PDCP SDU or an ARP-type MAC PDU.
  • the first data packet includes a MAC PDU.
  • the PDCP SDU type can also be considered as the MAC SDU type.
  • the PDCP SDU type may include an ARP type PDCP SDU and a non-ARP type PDCP SDU.
  • the MAC SDU type may include an ARP type MAC SDU and a non-ARP type MAC SDU.
  • the PDCP SDU type of the first data packet may refer to the PDCP SDU type of the data in the first data packet, or the PDCP SDU type of the MAC SDU in the first data packet .
  • the PDCP SDU type of the first data packet may refer to: the first data packet is an ARP type PDCP SDU, or the first data packet is another type of PDCP SDU.
  • the PDCP SDU type of the first data packet may refer to: the first data packet includes an ARP type PDCP SDU, or the first data packet includes other types of PDCP SDUs.
  • the associated information of the first data packet may be used to indicate the version information of the first data packet, or whether the receiving terminal of the first data packet needs to support ARP type data packet, or, whether the first data packet includes an ARP type PDCP SDU.
  • Whether the receiving end terminal of the first data packet needs to support ARP type data packets may refer to:
  • the receiving end terminal of the first data packet needs to support ARP type PDCP SDU, or whether the receiving end terminal of the first data packet needs to have the ability to receive ARP type data packets, or, the first data packet Whether the receiving end of the packet needs to support the first version of the packet.
  • sending or receiving the ARP type data packet is a capability that the terminal of the first version must support.
  • the data packet of the first version must include an ARP type PDCP SDU.
  • indicating the version information of the first data packet is equivalent to indicating the PDCP SDU type of the first data packet.
  • sending or receiving the ARP type data packet is an optional capability of the terminal of the first version.
  • the first version of the data packet may include an ARP-type PDCP SDU, or may not include an ARP-type PDCP SDU.
  • the version information of the first data packet includes a transmission specification (Tx profile) of the first data packet. That is to say, the Tx profile of the first data packet may be indicated through the associated information of the first data packet.
  • Tx profile transmission specification
  • the first terminal and the second terminal have not established a PC5 RRC connection. Therefore, the Tx profile information cannot be directly sent from the sender to the receiver. In this case, the first data
  • the associated information of the package indicates version information such as Tx profile.
  • the associated information of the first data packet may refer to any information associated with the first data packet, for example, the resource information of the first data packet, scheduling information, the The information carried in the first data packet, etc.
  • the associated information of the first data packet includes sidelink control information (Sidelink Control Information, SCI) for scheduling the first data packet.
  • SCI Sidelink Control Information
  • version information of the scheduled first data packet may be indicated at the same time.
  • the SCI includes first indication information, and the first indication information is used to indicate version information of the first data packet.
  • the first indication information is carried in a reserved field in the SCI, or in a reserved bit, or an invalid bit in an existing field in the SCI may be used to indicate the version information of the first data packet, This application is not limited thereto.
  • the first indication information includes at least one bit, and a value of the at least one bit is used to indicate a target version corresponding to the at least two versions of the version information of the first data packet. For example, a value of 0 indicates that the target version is the first version, and a value of 1 indicates that the target version is the second version.
  • the associated information of the first data packet includes a resource pool for transmitting the first data packet.
  • the terminal device is configured with a first mapping relationship
  • the first mapping relationship is the mapping relationship between the resource pool used for data packet transmission and the version information of the data packet, therefore, the receiving end of the data packet can receive the data according to the The resource pool of the package determines the version information corresponding to the data package.
  • the first mapping relationship may be configured by a network device, or predefined, or sent by the second terminal to the first terminal.
  • the second terminal and the first terminal establish After the PC5 RRC connection, the second terminal may send the first mapping relationship to the first terminal.
  • the network device can configure corresponding resource pools for the sidelink services of the first version and the second version, for example, including a sending resource pool and a receiving resource pool, and the resources used by the receiving end to receive data packets pool, and determine the version information corresponding to the data packet.
  • the first version of the network device configuration corresponds to the first resource pool
  • the second version corresponds to the second resource pool. If the first terminal receives the first data packet in the first resource pool, the version of the first data packet can be determined. Information is first edition.
  • the first terminal may determine the version information of the first data packet according to the information carried in the first data packet.
  • the information carried in the first data packet includes information in the MAC PDU subheader of the first data packet.
  • the information in the subheader of the MAC PDU of the first data packet indicates the version information of the first data packet, or whether the receiving end terminal of the first data packet needs to support the PDCP SDU of the ARP type, so that the first data packet
  • the receiving terminal only needs to parse the first data packet to the MAC layer to know whether it supports the version of the first data packet, and then determine whether to receive subsequent data.
  • the information carried in the first data packet includes at least one of the following:
  • Target address information in the MAC PDU subheader header in the first data packet version information in the MAC PDU subheader in the first data packet, reservation information in the MAC PDU subheader in the first data packet .
  • the first terminal is configured with a second mapping relationship
  • the second mapping relationship is used to characterize the mapping relationship between the destination address of the data packet and the version information of the data packet.
  • the first terminal may acquire the destination address information of the first data packet, and further determine the version information of the first data packet according to the destination address information of the first data packet and the second mapping relationship.
  • the first terminal may obtain the first destination address information from the DST field in the MAC PDU subheader of the first data packet, and obtain the second destination address information from the destination address information in the SCI scheduling the first data packet.
  • Destination address information determining the destination address information of the first data packet according to the first destination address information and the second destination address information.
  • the second mapping relationship is configured by a network device, or is sent by the second terminal to the first terminal, or is predefined.
  • this application does not limit the specific manner in which the second terminal sends the second mapping relationship to the first terminal.
  • the second terminal may send the second mapping relationship to the first terminal.
  • the value of the V field in the MAC PDU subheader of the first data packet indicates the target version corresponding to at least two versions of the version information of the first data packet.
  • the value of the V field is all "0", indicating that the first data packet is a second version of the data packet, for example, a Rel-16 type MAC PDU, and there is at least 1 bit in the V field If it is "1", it means that the first data packet is a data packet of the first version, for example, a MAC PDU of Rel-17 type.
  • the value of at least one R field in the MAC PDU subheader of the first data packet indicates a target version corresponding to at least two versions of the version information of the first data packet.
  • the value of the at least one R field is all "0", indicating that the first data packet is a data packet of the second version, for example, a MAC PDU of the Rel-16 type, and there is a The value of the R field is "1", which means that the first data packet is a data packet of the first version, for example, a MAC PDU of Rel-17 type.
  • the S330 may include:
  • the first terminal discards the first data packet;
  • the first terminal receives the first data packet.
  • the first terminal when the version of the first data packet is a version not supported by the first terminal, the first terminal performs overall discard processing on the first data packet (that is, does not receive the MAC PDU subheader data), or, when the version of the first data packet is the version supported by the first terminal, the first terminal performs overall reception processing on the first data packet (that is, receives the data after the MAC PDU subheader ).
  • the first terminal when the first data packet is a data packet of the first version, the first terminal is a terminal of the first version, and the terminal of the first version supports sending or receiving the first
  • the version of the data packet is a necessary capability (that is, the first terminal has the ability to receive the ARP type data packet)
  • the first terminal determines the first data packet according to the version information of the first data packet Whether it is an ARP type data packet, the first data packet is further subjected to overall discarding processing or overall receiving processing.
  • a MAC PDU can include at least one MAC subPDU, and each MAC subPDU can include a MAC SDU.
  • the information in the subheader in the MAC subPDU in the first data packet can also be passed Indicate the PDCP SDU type of the MAC SDU in the MAC subPDU, for example, whether the MAC SDU contains ARP type PDCP SDU data, or whether the MAC SDU is ARP type PDCP SDU data, etc.
  • the first terminal can determine the PDCP SDU type of the MAC SDU in each MAC subPDU according to the information in the subheader of each MAC subPDU in the first data packet (or in other words, whether the MAC SDU includes an ARP type PDCP SDU Data), so as to determine whether to receive the MAC SDU in each MAC subPDU, and can realize the more fine-grained reception control of the first data packet.
  • the PDCP SDU type of the MAC SDU in the MAC subPDU may be indicated through the reserved information in the subheader of the MAC subPDU, for example, whether it is (or contains) ARP type PDCP SDU data.
  • the first data packet includes a first MAC subPDU and a second MAC subPDU
  • the first MAC subPDU includes a first subheader
  • the second MAC subPDU includes a second subheader, which can be passed through the first subheader
  • the reservation information in the first MAC subPDU indicates the PDCP SDU type of the MAC SDU in the first MAC subPDU
  • the reservation information in the second subheader indicates the PDCP SDU type of the MAC SDU in the second MAC subPDU.
  • the MAC SDU in the first MAC subPDU includes PDCP SDU data of the first version
  • it is determined according to the reservation information in the second subheader that the MAC SDU in the second MAC subPDU The MAC SDU includes the second version of the PDCP SDU
  • the first terminal supports the second version of the data packet, but does not support the first version of the data packet
  • the first terminal does not receive the MAC SDU in the first MAC subPDU (for all The first MAC subPDU is discarded), and the MAC SDU in the second MAC subPDU is received.
  • the PDCP SDU type of the MAC SDU in the MAC subPDU may be indicated through the Logic Channel Identification (LCID) in the subheader of the MAC subPDU, for example, whether it is ARP type PDCP SDU data.
  • LCID Logic Channel Identification
  • the first terminal is configured with a third mapping relationship, and the third mapping relationship is used to indicate the LCID corresponding to the ARP type PDCP SDU and the LCID corresponding to the non-ARP type PDCP SDU.
  • corresponding LCIDs can be configured for different types of PDCP SDUs, so that when the second terminal can transmit PDCP SDUs of different versions, different LCID indications can be used in the corresponding MAC subPDUs.
  • the third mapping relationship is configured by a network device, or is sent by the second terminal to the first terminal, or is predefined.
  • the second terminal may send the third mapping relationship to the first terminal.
  • the first data packet includes a first MAC subPDU and a second MAC subPDU
  • the first MAC subPDU includes a first subheader
  • the second MAC subPDU includes a second subheader, which can be passed through the first subheader
  • the LCID in the first MAC subPDU indicates the PDCP SDU type of the MAC SDU in the first MAC subPDU
  • the LCID in the second subheader indicates the PDCP SDU type of the MAC SDU in the second MAC subPDU.
  • the first terminal does not receive the MAC SDU in the first MAC subPDU (that is, for the first MAC subPDU One MAC subPDU is discarded), and the MAC SDU in the second MAC subPDU is received.
  • the method 300 further includes:
  • the first terminal reports first capability information to the second terminal, where the first capability information is used to indicate whether the first terminal supports receiving ARP-type PDCP SDUs.
  • the receiving end of the data packet may report to the sending end of the data packet whether it supports receiving the data packet of the first version, or in other words, whether it has the ability to receive the data packet of the first version.
  • the method 200 further includes:
  • the first terminal receives second capability information reported by the second terminal, where the second capability information is used to indicate whether the second terminal supports receiving ARP-type PDCP SDUs.
  • the sending end of the data packet may report to the receiving end of the data packet whether it supports receiving the data packet of the first version, or in other words, whether it has the ability to receive the data packet of the first version.
  • the sending end and receiving end of the data packet can exchange their ability to receive the first version of the data packet, so that in the subsequent side communication, the sending end of the data packet can send the appropriate version according to the receiving ability of the receiving end data packets, which is beneficial to avoid resource waste caused by unnecessary data packet parsing.
  • this embodiment of the present application does not limit the specific manner in which the first terminal and the second terminal interact with each other to receive capabilities of data packets corresponding to the first version, for example, in unicast communication, multicast communication or broadcast communication interaction, etc.
  • the second terminal may send the second capability information to the first terminal in unicast communication.
  • the first terminal may also send the first capability information to the second terminal in unicast communication
  • the second terminal may send the second capability information to the multiple terminals in multicast communication, where the multiple terminals include the first terminal.
  • the first terminal may send the first capability information to the second terminal through a physical sidelink feedback channel (Physical Sidelink Feedback Channel, PSFCH).
  • PSFCH Physical Sidelink Feedback Channel
  • the second terminal may send the second capability information in broadcast communication.
  • the first terminal may also send the first capability information through broadcast communication.
  • the method 300 further includes:
  • the second terminal sends capability information of the first target address to the network device, where the capability information of the first target address is used to indicate whether the first target address supports ARP-type PDCP SDUs, or, the first target address Whether the address supports version 1 packets.
  • the first target address is the target address of the second terminal.
  • the capability information of the first target address is reported to the network device through sidelink UEInformation. Further, the network device may send the capability information of the first target address to the first terminal.
  • the first terminal may obtain the target address in the first data packet, and further combine the capability information of the first target address to determine whether the target address of the first data packet supports
  • the PDCP SDU of the ARP type further determines whether to receive the first data packet.
  • the first terminal may determine whether to receive the first data packet according to the associated information of the first data packet.
  • a data packet for example, determine the version information of the first data packet according to the associated information of the first data packet, further determine whether to receive the first data packet according to the version information of the first data packet, or determine whether to receive the first data packet according to the
  • the information carried in the first data packet determines the PDCP SDU type of the MAC SDU in each MAC subPDU in the first data packet, further according to the PDCP SDU type of the MAC SDU in the MAC subPDU in the first data packet Determining whether to receive the MAC SDU in each MAC subPDU in the first data packet helps to avoid the problem of waste of resources caused by not supporting receiving the first data packet after parsing the first data packet to the PDCP layer.
  • Fig. 9 shows a schematic block diagram of a terminal device 400 according to an embodiment of the present application.
  • the terminal device 400 includes:
  • the processing unit 410 is configured to determine the version information of the first data packet or the type of the packet data convergence protocol PDCP service data unit SDU in the first data packet according to the associated information of the first data packet sent by the second terminal and determining whether to receive the first data packet according to the version information of the first data packet or the PDCP SDU type of the first data packet.
  • the associated information of the first data packet includes at least one of the following:
  • the SCI includes first indication information, and the first indication information is used to indicate version information of the first data packet.
  • the terminal device is configured with a first mapping relationship, and the first mapping relationship is used to represent the mapping relationship between the resource pool and the version information of the data package.
  • the first mapping relationship is configured by the network device, or is sent by the second terminal to the terminal device, or is predefined.
  • the information carried in the first data packet includes at least one of the following:
  • the terminal device is configured with a second mapping relationship, and the second mapping relationship is used to characterize the mapping relationship between the destination address of the data packet and the version information of the data packet.
  • the second mapping relationship is configured by the network device, or is sent by the second terminal to the terminal device, or is predefined.
  • the value of the version information in the MAC PDU subheader of the first data packet is used to indicate the target version corresponding to the version information of the first data packet in at least two versions, wherein, The at least two versions include a first version and a second version.
  • the value of the reserved information in the MAC PDU subheader of the first data packet is used to indicate the target version corresponding to the version information of the first data packet in at least two versions, where , the at least two versions include a first version and a second version.
  • the version information of the first data packet is the first version or the second version, wherein the first version supports sending or receiving PDCP SDUs of the Address Resolution Protocol ARP type, and the second version Sending or receiving PDCP SDUs of type ARP is not supported.
  • the processing unit 410 is specifically used to:
  • the terminal device When the version information of the first data packet is the first version, and the terminal device does not support receiving ARP-type PDCP SDUs, controlling the communication unit of the terminal device not to receive the first data packet; or
  • the terminal device When the version information of the first data packet is the first version, and the terminal device supports receiving ARP-type PDCP SDUs, controlling the communication unit of the terminal device to receive the first data packet.
  • the first version includes version 17, and the second version includes version 16.
  • the associated information of the first data packet includes at least one of the following:
  • the association information of the first data packet is used to determine whether the PDCP SDU type in the MAC sub-PDU in the first data packet is an ARP type.
  • different values of the reserved information in the subheader of the MAC sub-PDU of the first data packet are used to indicate whether the PDCP SDU type in the MAC sub-PDU is an ARP type.
  • the terminal device is configured with a third mapping relationship, and the third mapping relationship is used to indicate the LCID corresponding to the ARP type PDCP SDU and the LCID corresponding to the non-ARP type PDCP SDU.
  • the third mapping relationship is configured by the network device, or is sent by the second terminal to the terminal device, or is predefined.
  • the processing unit 410 is specifically used to:
  • the terminal device When the first MAC sub-PDU in the first data packet includes an ARP-type PDCP SDU, and the terminal device supports receiving an ARP-type PDCP SDU, control the communication unit of the terminal device to receive the first A MAC SDU in a MAC sub-PDU; or
  • the terminal device When the first MAC sub-PDU in the first data packet includes an ARP-type PDCP SDU, and the terminal device does not support receiving an ARP-type PDCP SDU, control the communication unit of the terminal device not to receive the MAC SDU in the first MAC sub-PDU.
  • the terminal device further includes:
  • a communication unit configured to report first capability information to the second terminal, where the first capability information is used to indicate whether the terminal device supports receiving ARP-type PDCP SDUs.
  • the first capability information is sent through a physical sidelink feedback channel PSFCH.
  • the terminal device further includes:
  • the terminal device receives second capability information reported by the second terminal, where the second capability information is used to indicate whether the second terminal supports receiving ARP-type PDCP SDUs.
  • the version information of the first data packet includes a sending specification of the first data packet.
  • the above-mentioned communication unit may be a communication interface or a transceiver, or an input-output interface of a communication chip or a system-on-chip.
  • the aforementioned processing unit may be one or more processors.
  • terminal device 400 may correspond to the terminal device in the method embodiment of the present application, and the above-mentioned and other operations and/or functions of each unit in the terminal device 400 are for realizing the method shown in FIG. 8 For the sake of brevity, the corresponding process of the first terminal in 300 will not be repeated here.
  • Fig. 10 is a schematic block diagram of a terminal device according to another embodiment of the present application.
  • the terminal equipment 500 of Fig. 10 comprises:
  • a communication unit 510 configured to send a first data packet to a first terminal, where the associated information of the first data packet is used to determine version information of the first data packet or packet data in the first data packet Convergence protocol PDCP service data unit SDU type.
  • the associated information of the first data packet includes at least one of the following:
  • the SCI includes first indication information, and the first indication information is used to indicate version information of the first data packet.
  • the first terminal is configured with a first mapping relationship, and the first mapping relationship is used to represent the mapping relationship between the resource pool and the version information of the data package.
  • the information carried in the first data packet includes at least one of the following:
  • the terminal device is configured with a second mapping relationship, and the second mapping relationship is used to characterize the mapping relationship between the destination address of the data packet and the version information of the data packet.
  • the second mapping relationship is configured by the network device, or is predefined.
  • the value of the version information in the MAC PDU subheader of the first data packet is used to indicate that the version information of the first data packet is the corresponding target version in at least two versions, where , the at least two versions include a first version and a second version.
  • the value of the reserved information in the MAC PDU subheader of the first data packet is used to indicate that the version information of the first data packet is the corresponding target version in at least two versions, wherein, the at least two versions include a first version and a second version.
  • the version information of the first data packet is the first version or the second version, wherein the first version supports sending or receiving PDCP SDUs of the Address Resolution Protocol ARP type, and the second version Sending or receiving PDCP SDUs of type ARP is not supported.
  • the first version includes version 17, and the second version includes version 16.
  • the version information of the first data packet includes a sending specification of the first data packet.
  • the associated information of the first data packet includes at least one of the following:
  • the association information of the first data packet is used to determine whether the PDCP SDU type in the MAC sub-PDU in the first data packet is an ARP type.
  • the value of the reserved information in the subheader of the MAC sub-PDU of the first data packet is used to indicate whether the PDCP SDU type in the MAC sub-PDU is an ARP type.
  • the terminal device is configured with a third mapping relationship, and the third mapping relationship is used to indicate the LCID corresponding to the ARP type PDCP SDU and the LCID corresponding to the non-ARP type PDCP SDU.
  • the third mapping relationship is configured by the network device, or is predefined.
  • the terminal device further includes:
  • a communication unit configured to receive first capability information reported by the first terminal, where the first capability information is used to indicate whether the first terminal supports receiving ARP-type PDCP SDUs.
  • the first capability information is sent through a physical sidelink feedback channel PSFCH.
  • the terminal device further includes:
  • a communication unit configured to report second capability information to the first terminal, where the second capability information is used to indicate whether the terminal device supports receiving ARP-type PDCP SDUs.
  • the terminal device further includes:
  • a communication unit configured to send capability information of a first target address to a network device, where the capability information of the first target address is used to indicate whether the first target address needs to support ARP-type PDCP SDUs, and the first target address is the target address of the terminal device.
  • the capability information of the first target address is reported to the network device through sidelink user equipment information.
  • the above-mentioned communication unit may be a communication interface or a transceiver, or an input-output interface of a communication chip or a system-on-chip.
  • the aforementioned processing unit may be one or more processors.
  • terminal device 500 may correspond to the network device in the method embodiment of the present application, and the above-mentioned and other operations and/or functions of each unit in the terminal device 500 are to realize the method shown in FIG. 8
  • the corresponding process of the second terminal in 300 will not be repeated here.
  • Fig. 11 is a schematic block diagram of a network device according to an embodiment of the present application.
  • the network device 800 of FIG. 11 includes:
  • the communication unit 810 is configured to send the first information to the terminal device, where the first information is used to determine the version information of the sidelink data packet or the packet data convergence protocol PDCP service data unit SDU in the sidelink data packet type.
  • the terminal device may be the aforementioned first terminal and/or the second terminal.
  • the first information includes at least one of the following:
  • the first mapping relationship is used to indicate the mapping relationship between the resource pool and the version information of the data package
  • the second mapping relationship is used to indicate the mapping relationship between the target address of the side data packet and the version information of the side data packet
  • the third mapping relationship is used to indicate the logical channel identifier LCID corresponding to the PDCP SDU of the address resolution protocol ARP type and the LCID corresponding to the PDCP SDU of the non-ARP type.
  • the communication unit 810 is also used to:
  • the capability information of the first target address is used to indicate whether the first target address needs to support an ARP-type PDCP SDU, and the first target address is the The target address of the terminal device mentioned above.
  • the capability information of the first target address is reported to the network device through sidelink user equipment information.
  • the version information of the sidebound data packet is the first version or the second version, wherein the first version supports sending or receiving PDCP SDUs of Address Resolution Protocol ARP type, and the second version Sending or receiving PDCP SDUs of type ARP is not supported.
  • the first version includes version 17, and the second version includes version 16.
  • the version information of the first data packet includes a sending specification of the first data packet.
  • the network device 800 may correspond to the network device in the method embodiment of the present application, and the above-mentioned and other operations and/or functions of each unit in the network device 800 are for realizing the method shown in FIG. 8 For the sake of brevity, the corresponding processes of the network devices in 300 will not be repeated here.
  • Fig. 12 is a schematic structural diagram of a communication device 600 provided by an embodiment of the present application.
  • the communication device 600 shown in FIG. 12 includes a processor 610, and the processor 610 can call and run a computer program from a memory, so as to implement the method in the embodiment of the present application.
  • the communication device 600 may further include a memory 620 .
  • the processor 610 can invoke and run a computer program from the memory 620, so as to implement the method in the embodiment of the present application.
  • the memory 620 may be an independent device independent of the processor 610 , or may be integrated in the processor 610 .
  • the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices, specifically, to send information or data to other devices, or receive other Information or data sent by the device.
  • the transceiver 630 may include a transmitter and a receiver.
  • the transceiver 630 may further include antennas, and the number of antennas may be one or more.
  • the communication device 600 may specifically be the network device of the embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the network device in each method of the embodiment of the present application. For the sake of brevity, details are not repeated here. .
  • the communication device 600 may specifically be the first terminal or the second terminal in the embodiment of the present application, and the communication device 600 may implement the corresponding functions implemented by the first terminal or the second terminal in each method of the embodiment of the present application. For the sake of brevity, the process will not be repeated here.
  • FIG. 13 is a schematic structural diagram of a chip according to an embodiment of the present application.
  • the chip 700 shown in FIG. 13 includes a processor 710, and the processor 710 can call and run a computer program from a memory, so as to implement the method in the embodiment of the present application.
  • the chip 700 may further include a memory 720 .
  • the processor 710 can invoke and run a computer program from the memory 720, so as to implement the method in the embodiment of the present application.
  • the memory 720 may be an independent device independent of the processor 710 , or may be integrated in the processor 710 .
  • the chip 700 may also include an input interface 730 .
  • the processor 710 can control the input interface 730 to communicate with other devices or chips, specifically, can obtain information or data sent by other devices or chips.
  • the chip 700 may also include an output interface 740 .
  • the processor 710 can control the output interface 740 to communicate with other devices or chips, specifically, can output information or data to other devices or chips.
  • the chip can be applied to the network device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the network device in the methods of the embodiment of the present application.
  • the chip can implement the corresponding processes implemented by the network device in the methods of the embodiment of the present application.
  • the chip can be applied to the first terminal or the second terminal in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the first terminal or the second terminal in the methods of the embodiments of the present application, in order to It is concise and will not be repeated here.
  • the chip mentioned in the embodiment of the present application may also be called a system-on-chip, a system-on-chip, a system-on-a-chip, or a system-on-a-chip.
  • Fig. 14 is a schematic block diagram of a communication system 900 provided by an embodiment of the present application. As shown in FIG. 14 , the communication system 900 includes a first terminal 910 , a second terminal 920 and a network device 930 .
  • the first terminal 910 can be used to realize the corresponding functions realized by the first terminal or the second terminal in the above method
  • the second terminal 920 can be used to realize the corresponding functions realized by the second terminal in the above method
  • the network device 930 can be used to realize the corresponding functions realized by the network device in the above method.
  • the processor in the embodiment of the present application may be an integrated circuit chip, which has a signal processing capability.
  • each step of the above-mentioned method embodiments may be completed by an integrated logic circuit of hardware in a processor or instructions in the form of software.
  • the above-mentioned processor can be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other available Program logic devices, discrete gate or transistor logic devices, discrete hardware components.
  • DSP Digital Signal Processor
  • ASIC Application Specific Integrated Circuit
  • FPGA Field Programmable Gate Array
  • a general-purpose processor may be a microprocessor, or the processor may be any conventional processor, or the like.
  • the steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, register.
  • the storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware.
  • the memory in the embodiments of the present application may be a volatile memory or a nonvolatile memory, or may include both volatile and nonvolatile memories.
  • the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electronically programmable Erase Programmable Read-Only Memory (Electrically EPROM, EEPROM) or Flash.
  • the volatile memory can be Random Access Memory (RAM), which acts as external cache memory.
  • RAM Static Random Access Memory
  • SRAM Static Random Access Memory
  • DRAM Dynamic Random Access Memory
  • Synchronous Dynamic Random Access Memory 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 connection dynamic random access memory
  • Synchlink DRAM, SLDRAM Direct Memory Bus Random Access Memory
  • Direct Rambus RAM Direct Rambus RAM
  • the memory in the embodiment of the present application may also be a static random access memory (static RAM, SRAM), a dynamic random access memory (dynamic RAM, DRAM), 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 (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is, the memory in the embodiments of the present application is intended to include, but not be limited to, these and any other suitable types of memory.
  • the embodiment of the present application also provides a computer-readable storage medium for storing computer programs.
  • the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the methods of the embodiments of the present application.
  • the computer program enables the computer to execute the corresponding processes implemented by the network device in the methods of the embodiments of the present application.
  • the computer-readable storage medium can be applied to the first terminal or the second terminal in the embodiments of the present application, and the computer program enables the computer to execute the methods performed by the first terminal or the second terminal in the embodiments of the present application
  • the corresponding process of implementation is not repeated here.
  • the embodiment of the present application also provides a computer program product, including computer program instructions.
  • the computer program product may be applied to the network device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the Let me repeat for the sake of brevity, the Let me repeat.
  • the computer program product can be applied to the first terminal or the second terminal in the embodiments of the present application, and the computer program instructions cause the computer to execute the methods implemented by the first terminal or the second terminal in the embodiments of the present application
  • the computer program instructions cause the computer to execute the methods implemented by the first terminal or the second terminal in the embodiments of the present application
  • the corresponding process will not be repeated here.
  • the embodiment of the present application also provides a computer program.
  • the computer program can be applied to the network device in the embodiment of the present application.
  • the computer program executes the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer program executes the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer program can be applied to the first terminal or the second terminal in the embodiments of the present application, and when the computer program is run on the computer, the computer executes the various methods in the embodiments of the present application performed by the first terminal or the second terminal.
  • the corresponding process implemented by the second terminal will not be repeated here.
  • the disclosed systems, devices and methods may be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units 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 may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit.
  • the functions described above are realized in the form of software function units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of the present application is essentially or the part that contributes to the prior art 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 disc and other media that can store program codes. .

Abstract

La présente invention concerne un procédé de transmission de liaison latérale, un dispositif terminal et un dispositif de réseau. Le procédé comprend : la détermination, par un premier terminal, selon des informations d'association d'un premier paquet de données envoyé par un second terminal, d'informations de version du premier paquet de données ou d'un type d'unité de données de service (SDU) de protocole de convergence de données en paquet (PDCP) dans le premier paquet de données ; et le fait de déterminer, selon les informations de version du premier paquet de données ou le type SDU PDCP correspondant au premier paquet de données, s'il faut recevoir le premier paquet de données. Par conséquent, une extrémité d'envoi indique les informations de version du paquet de données ou le type SDU PDCP dans le paquet de données au moyen des informations d'association du paquet de données envoyé de sorte qu'une extrémité de réception détermine s'il faut recevoir le paquet de données selon les informations de version du paquet de données ou le type SDU PDCP correspondant au paquet de données, ce qui facilite l'évitement de gaspillage de ressources causé par la réception d'un paquet de données d'une version non prise en charge.
PCT/CN2021/093069 2021-05-11 2021-05-11 Procédé de transmission de liaison latérale, dispositif terminal et dispositif de réseau WO2022236682A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202180090568.5A CN116762365A (zh) 2021-05-11 2021-05-11 侧行传输的方法、终端设备和网络设备
PCT/CN2021/093069 WO2022236682A1 (fr) 2021-05-11 2021-05-11 Procédé de transmission de liaison latérale, dispositif terminal et dispositif de réseau

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/093069 WO2022236682A1 (fr) 2021-05-11 2021-05-11 Procédé de transmission de liaison latérale, dispositif terminal et dispositif de réseau

Publications (1)

Publication Number Publication Date
WO2022236682A1 true WO2022236682A1 (fr) 2022-11-17

Family

ID=84029106

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/093069 WO2022236682A1 (fr) 2021-05-11 2021-05-11 Procédé de transmission de liaison latérale, dispositif terminal et dispositif de réseau

Country Status (2)

Country Link
CN (1) CN116762365A (fr)
WO (1) WO2022236682A1 (fr)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140211692A1 (en) * 2013-01-30 2014-07-31 Nvidia Corporation Communication system and method
CN105704641A (zh) * 2014-11-06 2016-06-22 中兴通讯股份有限公司 设备到设备d2d数据传输方法、装置及d2d ue
CN107079338A (zh) * 2014-11-10 2017-08-18 Lg 电子株式会社 在d2d通信系统中指示用于侧链路无线电承载的加密指示的方法及其设备
WO2018195770A1 (fr) * 2017-04-25 2018-11-01 Oppo广东移动通信有限公司 Procédé de transmission de données et dispositif de communication
CN108781383A (zh) * 2016-03-22 2018-11-09 Lg 电子株式会社 发送数据单元的方法和用户设备和接收数据单元的方法和用户设备
WO2019023998A1 (fr) * 2017-08-02 2019-02-07 Oppo广东移动通信有限公司 Procédé de communication dispositif à dispositif, dispositif terminal et dispositif de réseau
CN111835767A (zh) * 2014-10-30 2020-10-27 三星电子株式会社 在用户装备之间执行设备到设备通信的方法

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140211692A1 (en) * 2013-01-30 2014-07-31 Nvidia Corporation Communication system and method
CN111835767A (zh) * 2014-10-30 2020-10-27 三星电子株式会社 在用户装备之间执行设备到设备通信的方法
CN105704641A (zh) * 2014-11-06 2016-06-22 中兴通讯股份有限公司 设备到设备d2d数据传输方法、装置及d2d ue
CN107079338A (zh) * 2014-11-10 2017-08-18 Lg 电子株式会社 在d2d通信系统中指示用于侧链路无线电承载的加密指示的方法及其设备
CN108781383A (zh) * 2016-03-22 2018-11-09 Lg 电子株式会社 发送数据单元的方法和用户设备和接收数据单元的方法和用户设备
WO2018195770A1 (fr) * 2017-04-25 2018-11-01 Oppo广东移动通信有限公司 Procédé de transmission de données et dispositif de communication
WO2019023998A1 (fr) * 2017-08-02 2019-02-07 Oppo广东移动通信有限公司 Procédé de communication dispositif à dispositif, dispositif terminal et dispositif de réseau

Also Published As

Publication number Publication date
CN116762365A (zh) 2023-09-15

Similar Documents

Publication Publication Date Title
WO2022040939A1 (fr) Procédés de communication sans fil et dispositifs de terminal
WO2022236682A1 (fr) Procédé de transmission de liaison latérale, dispositif terminal et dispositif de réseau
WO2022021008A1 (fr) Procédé de détermination de ressources d'autorisation configurée de liaison latérale, et équipement terminal
WO2022021165A1 (fr) Procédé de découverte de relais et terminal
WO2023150998A1 (fr) Procédé de communication sans fil, dispositif terminal et dispositif de réseau
WO2023133685A1 (fr) Procédé de communication sans fil et dispositif terminal
WO2023283777A1 (fr) Procédés de communication sans fil et dispositifs terminaux
WO2023216018A1 (fr) Procédé et dispositif de communication par relais
WO2023000328A1 (fr) Procédé de communication sans fil, dispositif terminal et dispositif de réseau
US20230224763A1 (en) Wireless communication method, terminal device, and network device
WO2022233011A1 (fr) Procédé d'établissement de connexion, et dispositif terminal
WO2023035187A1 (fr) Procédé de communication sans fil, et dispositif
WO2023044735A1 (fr) Procédé de communication sans fil et dispositif terminal
WO2022077214A1 (fr) Procédé de transmission d'avance temporelle ta commune, dispositif terminal et dispositif de réseau
US20240008027A1 (en) Wireless communication method, terminal device and network device
WO2023077439A1 (fr) Procédé de communication sans fil, dispositif terminal et dispositif de réseau
WO2022082434A1 (fr) Procédé de communication entre terminaux, ainsi que dispositif terminal et dispositif de réseau
WO2023065155A1 (fr) Procédé de communication sans fil, dispositif terminal, dispositif de réseau d'accès, et dispositif de réseau central
WO2022174726A1 (fr) Procédé de communication sans fil et dispositif terminal
US20230090887A1 (en) Relay communication method and device
WO2022261975A1 (fr) Procédé de communication sans fil et dispositif terminal
WO2023279258A1 (fr) Procédé de sélection de ressource et dispositif terminal
WO2022133977A1 (fr) Procédé de contrôle de qualité de service (qos), dispositif terminal, et dispositif de réseau
WO2023108638A1 (fr) Procédé de communication sans fil, dispositif terminal, et dispositif de réseau
WO2023184405A1 (fr) Procédé de communication sans fil, dispositif de réseau et dispositif 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: 21941258

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202180090568.5

Country of ref document: CN

NENP Non-entry into the national phase

Ref country code: DE