WO2022236682A1

WO2022236682A1 - Sidelink transmission method, terminal device and network device

Info

Publication number: WO2022236682A1
Application number: PCT/CN2021/093069
Authority: WO
Inventors: 张博源; 卢前溪
Original assignee: Oppo广东移动通信有限公司
Priority date: 2021-05-11
Filing date: 2021-05-11
Publication date: 2022-11-17
Also published as: CN116762365A

Abstract

A sidelink transmission method, a terminal device and a network device. The method comprises: a first terminal determining, according to association information of a first data packet sent by a second terminal, version information of the first data packet or a packet data convergence protocol (PDCP) service data unit (SDU) type in the first data packet; and determining, according to the version information of the first data packet or the PDCP SDU type corresponding to the first data packet, whether to receive the first data packet. Therefore, a sending end indicates the version information of the data packet or the PDCP SDU type in the data packet by means of the association information of the sent data packet, so that a receiving end determines whether to receive the data packet according to the version information of the data packet or the PDCP SDU type corresponding to the data packet, thereby facilitating avoiding resource waste caused by receiving a data packet of an unsupported version.

Description

Method, terminal device and network device for sidewalk transmission

technical field

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.

Background technique

In related technologies, it is considered to introduce Address Resolution Protocol (Address Resolution Protocol, ARP) type packet data convergence protocol (Packet Data Convergence Protocol, PDCP) SDU in version 17 (Rel-17) sideline relay (sidelink relay), and Version 16 (Rel-16) does not need to support ARP-type PDCP SDUs. Therefore, in the scenario where terminals supporting Rel-16/Rel-17 coexist, how to realize the reception of side data packets is an urgent problem to be solved. .

Contents of the invention

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.

According to the first aspect, a method for lateral transmission is provided, 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;

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

In a second aspect, a method for lateral transmission is provided, 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.

In a third aspect, a sidelink transmission method is provided, 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.

In a fourth aspect, a terminal device is provided, configured to execute the method in any one of the above-mentioned first aspect to the second aspect or in each implementation manner thereof.

Specifically, 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.

In a fifth aspect, a network device is provided, configured to execute the method in the above third aspect or various implementation manners thereof.

Specifically, the network device includes a functional module for executing the method in the above third aspect or each implementation manner thereof.

In a sixth aspect, a terminal device is provided, including a processor and a memory. The memory is used to store a computer program, and 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.

In a seventh aspect, a network device is provided, including a processor and a memory. The memory is used to store a computer program, and 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.

In an eighth aspect, there is provided 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.

In a ninth aspect, a computer program product is provided, 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.

In a tenth aspect, a computer program is provided, 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.

In an eleventh aspect, a chip is provided for implementing any one of the first aspect to the third aspect or the method in each implementation manner thereof.

Specifically, 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.

Through the above technical solution, 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.

Description of drawings

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.

Detailed ways

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, but not all of the embodiments. With regard to the embodiments in this application, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the scope of protection of this 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.

Generally speaking, the number of connections supported by traditional communication systems is limited and easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communication, but also support, for example, Device to Device (Device to Device, D2D) communication, Machine to Machine (M2M) communication, Machine Type Communication (MTC), Vehicle to Vehicle (V2V) communication, or Vehicle to everything (V2X) communication, etc. , the embodiments of the present application may also be applied to these communication systems.

Optionally, 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.

Optionally, 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.

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.

In the embodiment of this application, 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).

In this embodiment of the application, 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.

As an example but not a limitation, in this embodiment of the present application, 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.

In the embodiment of the present application, 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.

As an example but not a limitation, in this embodiment of the present application, the network device may have a mobile feature, for example, the network device may be a mobile device. Optionally, the network equipment may be a satellite or a balloon station. For example, 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. Optionally, the network device may also be a base station installed on land, water, and other locations.

In this embodiment of the present application, 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.

It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and/or" in this article is just an association relationship describing associated objects, which means that there can be three relationships, for example, A and/or B can mean: A exists alone, A and B exist simultaneously, and there exists alone B these three situations. In addition, the character "/" in this article generally indicates that the contextual objects are an "or" relationship.

The terms used in the embodiments of the present application are only used to explain specific embodiments of the present application, and are not intended to limit the present application. The terms "first", "second", "third" and "fourth" in the specification and claims of the present application and the drawings are used to distinguish different objects, rather than to describe a specific order . Furthermore, the terms "include" and "have", as well as any variations thereof, are intended to cover a non-exclusive inclusion.

It should be understood that 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. For example, 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.

In the description of the embodiments of the present application, 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.

In this embodiment of the application, "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. For example, pre-defined may refer to defined in the protocol.

In the embodiment of the present application, 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 . Specifically, 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. Optionally, the vehicle-mounted terminal may select transmission resources randomly, or select transmission resources by listening.

In LTE-V2X, broadcast transmission is supported, and in NR-V2X, unicast and multicast transmission are introduced. For 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.

In the sideline transmission, 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.

In some embodiments, 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.

As shown in Figure 6, 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.

As shown in Figure 6, the subheader of a MAC subPDU may include at least one of the following fields:

R: reserved bit;

L: length field, used to indicate the length of MAC SDU or MAC CE, in bytes;

F: used to indicate the length of the L field.

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.

In some scenarios, it is considered to introduce Address Resolution Protocol (Address Resolution Protocol, ARP) type Packet Data Convergence Protocol (PDCP) SDU in version 17 (Rel-17) sideline relay, while version 16 (Rel -16) It is not necessary to support ARP-type PDCP SDUs. Therefore, in a scenario where Rel-16/Rel-17 terminals coexist, if a Rel-17 terminal sends an ARP-type SDU to a Rel-16 terminal data packet, the Rel-16 terminal needs to parse the data packet to the PDCP layer to find that it does not support receiving the data packet, which increases the resource consumption of the terminal. Therefore, how to realize the reception of side data packets to reduce the resource consumption of the terminal It is an urgent problem to be solved.

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:

S310. The second terminal sends the first data packet to the first terminal;

S320. 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;

S330. Determine 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.

Therefore, in this embodiment of the present application, 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.

In this embodiment of the present application, 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.

Optionally, in some embodiments of the present application, the first version may include Rel-17, and the second version may include Rel-16.

In some embodiments, the first version supports ARP type packets, and the second version does not support ARP type packets.

It should be understood that, in some embodiments of the present application, the ARP-type data packet may be replaced by an ARP-type PDCP SDU or an ARP-type MAC PDU.

In this embodiment of the present application, the first data packet includes a MAC PDU.

It can be seen from the encapsulation process of data by the protocol layer that the MAC SDU in the MAC PDU comes from the PDCP SDU of the PDCP layer. Therefore, in the embodiment of the present application, the PDCP SDU type can also be considered as the MAC SDU type.

Optionally, the PDCP SDU type may include an ARP type PDCP SDU and a non-ARP type PDCP SDU.

Optionally, the MAC SDU type may include an ARP type MAC SDU and a non-ARP type MAC SDU.

In some embodiments of the present application, 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 .

For example, 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.

For another example, 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.

In some embodiments of the present application, 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:

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

In some embodiments, sending or receiving the ARP type data packet is a capability that the terminal of the first version must support. In this case, the data packet of the first version must include an ARP type PDCP SDU. In this case, indicating the version information of the first data packet is equivalent to indicating the PDCP SDU type of the first data packet.

In some other embodiments, sending or receiving the ARP type data packet is an optional capability of the terminal of the first version. In this case, the first version of the data packet may include an ARP-type PDCP SDU, or may not include an ARP-type PDCP SDU.

Optionally, in some embodiments, 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.

In some scenarios, such as multicast and broadcast services, 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.

It should be understood that in this embodiment of the present application, 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.

In some embodiments of the present application, the associated information of the first data packet includes sidelink control information (Sidelink Control Information, SCI) for scheduling the first data packet. For example, when scheduling the first data packet, version information of the scheduled first data packet may be indicated at the same time.

In some embodiments, the SCI includes first indication information, and the first indication information is used to indicate version information of the first data packet.

Optionally, 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.

As an example, 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.

In some other embodiments of the present application, the associated information of the first data packet includes a resource pool for transmitting the first data packet.

For example, 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.

Optionally, in some embodiments, the first mapping relationship may be configured by a network device, or predefined, or sent by the second terminal to the first terminal.

It should be understood that this application does not limit the specific manner in which the second terminal sends the first mapping relationship to the first terminal. For example, in unicast communication, 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.

In some embodiments, 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.

As an example, the first version of the network device configuration corresponds to the first resource pool, and 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.

In still some embodiments of the present application, the first terminal may determine the version information of the first data packet according to the information carried in the first data packet.

In some embodiments, 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.

In some embodiments, 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 .

In some embodiments, the first terminal 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.

Therefore, 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.

Optionally, 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.

In some embodiments, the second mapping relationship is configured by a network device, or is sent by the second terminal to the first terminal, or is predefined.

It should be understood that this application does not limit the specific manner in which the second terminal sends the second mapping relationship to the first terminal. For example, in unicast communication, after the second terminal establishes a PC5 RRC connection with the first terminal, the second terminal may send the second mapping relationship to the first terminal.

In some embodiments, 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.

As an example, 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.

In some embodiments, 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.

As an example, 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.

In some embodiments of the present application, the S330 may include:

When the version information of the first data packet is the first version, and the first terminal does not support receiving ARP-type PDCP SDUs, the first terminal discards the first data packet; or

If the version information of the first data packet is the first version, and the first terminal supports receiving ARP-type PDCP SDUs, the first terminal receives the first data packet.

That is to say, 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 ).

In some embodiments, 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 When 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.

In some scenarios, a MAC PDU can include at least one MAC subPDU, and each MAC subPDU can include a MAC SDU. In some embodiments of the present application, 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. Further, 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.

In some embodiments, 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.

As an example, the first data packet includes a first MAC subPDU and a second MAC subPDU, the first MAC subPDU includes a first subheader, and 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, and the reservation information in the second subheader indicates the PDCP SDU type of the MAC SDU in the second MAC subPDU.

For example, if it is determined according to the reservation information in the first subheader that 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, and the first terminal supports the second version of the data packet, but does not support the first version of the data packet, then 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.

In some embodiments, 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.

In some embodiments, 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.

That is, 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.

In some embodiments, the third mapping relationship is configured by a network device, or is sent by the second terminal to the first terminal, or is predefined.

It should be understood that this application does not limit the specific manner in which the second terminal sends the third mapping relationship to the first terminal, for example, in unicast communication, the second terminal and the first terminal After the PC5 RRC connection is established, the second terminal may send the third mapping relationship to the first terminal.

As an example, the first data packet includes a first MAC subPDU and a second MAC subPDU, the first MAC subPDU includes a first subheader, and 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, and the LCID in the second subheader indicates the PDCP SDU type of the MAC SDU in the second MAC subPDU.

For example, if it is determined according to the LCID in the first subheader that the MAC SDU in the first MAC subPDU includes the PDCP SDU data of the first version, it is determined according to the LCID in the second subheader that the MAC SDU in the second MAC subPDU includes the first version The PDCP SDU data of the second version, and the first terminal supports the data packet of the second version, but does not support the data packet of the first version, then 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.

In some embodiments of the present application, 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.

That is, 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.

In some embodiments of the present application, 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.

That is, 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.

To sum up, 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.

It should be understood that 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.

In some embodiments, the second terminal may send the second capability information to the first terminal in unicast communication. Correspondingly, the first terminal may also send the first capability information to the second terminal in unicast communication

In some embodiments, the second terminal may send the second capability information to the multiple terminals in multicast communication, where the multiple terminals include the first terminal. Correspondingly, the first terminal may send the first capability information to the second terminal through a physical sidelink feedback channel (Physical Sidelink Feedback Channel, PSFCH).

In some embodiments, the second terminal may send the second capability information in broadcast communication. Similarly, the first terminal may also send the first capability information through broadcast communication.

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.

For example, 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.

For example, in the subsequent lateral transmission, 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.

To sum up, in this embodiment of the present application, when the second terminal sends the first data packet to the first terminal, 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.

The method embodiment of the present application is described in detail above in conjunction with FIG. 8 , and the device embodiment of the present application is described in detail below in conjunction with FIG. 9 to FIG. 13 . It should be understood that the device embodiment and the method embodiment correspond to each other, and similar descriptions can be Refer to the method example.

Fig. 9 shows a schematic block diagram of a terminal device 400 according to an embodiment of the present application. As shown in FIG. 9, 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.

In some embodiments of the present application, the associated information of the first data packet includes at least one of the following:

The sideline control information SCI used to schedule the first data packet, the resource pool used to transmit the first data packet, and the information carried in the first data packet.

In some embodiments of the present application, the SCI includes first indication information, and the first indication information is used to indicate version information of the first data packet.

In some embodiments of the present application, 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.

In some embodiments of the present application, the first mapping relationship is configured by the network device, or is sent by the second terminal to the terminal device, or is predefined.

In some embodiments of the present application, the information carried in the first data packet includes at least one of the following:

The target address information in the medium access control MAC protocol data unit PDU subheader in the first data packet, the version information in the MAC PDU subheader in the first data packet, the Reserved information in the MAC PDU subheader.

In some embodiments of the present application, 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.

In some embodiments of the present application, the second mapping relationship is configured by the network device, or is sent by the second terminal to the terminal device, or is predefined.

In some embodiments of the present application, 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.

In some embodiments of the present application, 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.

In some embodiments of the present application, 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.

In some embodiments of the present application, the processing unit 410 is specifically used to:

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

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.

In some embodiments of the present application, the first version includes version 17, and the second version includes version 16.

The reserved information in the subheader of the MAC sub-PDU in the first data packet, and the logical channel identifier LCID in the subheader of the MAC sub-PDU in the first data packet.

In some embodiments of the present application, 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.

In some embodiments of the present application, 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.

In some embodiments of the present application, 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.

In some embodiments of the present application, the third mapping relationship is configured by the network device, or is sent by the second terminal to the terminal device, or is predefined.

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

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.

In some embodiments of the present application, 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.

In some embodiments of the present application, the first capability information is sent through a physical sidelink feedback channel PSFCH.

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.

In some embodiments of the present application, the version information of the first data packet includes a sending specification of the first data packet.

Optionally, in some embodiments, 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.

It should be understood that the terminal device 400 according to the embodiment of the present application 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.

In some embodiments of the present application, 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.

In some embodiments of the present application, the second mapping relationship is configured by the network device, or is predefined.

In some embodiments of the present application, 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.

In some embodiments of the present application, 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.

In some embodiments of the present application, 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.

In some embodiments of the present application, the third mapping relationship is configured by the network device, or is predefined.

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.

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.

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.

In some embodiments of the present application, the capability information of the first target address is reported to the network device through sidelink user equipment information.

It should be understood that the terminal device 500 according to the embodiment of the present application 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 For the sake of brevity, 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.

Optionally, the terminal device may be the aforementioned first terminal and/or the second terminal.

In some embodiments of the present application, 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.

In some embodiments of the present application, the communication unit 810 is also used to:

receiving the capability information of the first target address reported by the terminal device, where 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.

In some embodiments of the present application, 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.

It should be understood that the network device 800 according to the embodiment of the present application 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.

Optionally, as shown in FIG. 12 , the communication device 600 may further include a memory 620 . Wherein, 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.

Wherein, the memory 620 may be an independent device independent of the processor 610 , or may be integrated in the processor 610 .

Optionally, as shown in FIG. 12, 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.

Wherein, 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.

Optionally, 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. .

Optionally, 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.

Optionally, as shown in FIG. 13 , the chip 700 may further include a memory 720 . Wherein, 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.

Wherein, the memory 720 may be an independent device independent of the processor 710 , or may be integrated in the processor 710 .

Optionally, the chip 700 may also include an input interface 730 . Wherein, 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.

Optionally, the chip 700 may also include an output interface 740 . Wherein, 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.

Optionally, 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. For the sake of brevity, details are not repeated here.

Optionally, 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.

It should be understood that 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 .

Wherein, 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, and the second terminal 920 can be used to realize the corresponding functions realized by the second terminal in the above method, And the network device 930 can be used to realize the corresponding functions realized by the network device in the above method. For the sake of brevity, details are not repeated here.

It should be understood that the processor in the embodiment of the present application may be an integrated circuit chip, which has a signal processing capability. In the implementation process, 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. Various methods, steps, and logic block diagrams disclosed in the embodiments of the present application may be implemented or executed. 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.

It can be understood that 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. Among them, 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. By way of illustration and not limitation, many forms of RAM are available, such as Static Random Access Memory (Static RAM, SRAM), Dynamic Random Access Memory (Dynamic RAM, DRAM), Synchronous Dynamic Random Access Memory (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 (Synchlink DRAM, SLDRAM ) and Direct Memory Bus Random Access Memory (Direct Rambus RAM, DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but not be limited to, these and any other suitable types of memory.

It should be understood that the above-mentioned memory is illustrative but not restrictive. For example, 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.

Optionally, 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. For brevity, here No longer.

Optionally, 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 For the sake of brevity, 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.

Optionally, 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. For the sake of brevity, the Let me repeat.

Optionally, 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 For the sake of brevity, the corresponding process will not be repeated here.

The embodiment of the present application also provides a computer program.

Optionally, the computer program can be applied to the network device in the embodiment of the present application. When the computer program is run on the computer, the computer executes the corresponding process implemented by the network device in each method of the embodiment of the present application. For the sake of brevity , which will not be repeated here.

Optionally, 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. For the sake of brevity, the corresponding process implemented by the second terminal will not be repeated here.

Those skilled in the art can appreciate that the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed by hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present application.

Those skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the above-described system, device and unit can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods may be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented. In another point, 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.

In addition, 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.

If 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. Based on this understanding, 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. .

The above is only a specific implementation of the application, but the scope of protection of the application is not limited thereto. Anyone familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the application. Should be covered within the protection scope of this application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

A method for lateral transmission, characterized in that it comprises:

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;

Determine 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 method according to claim 1, wherein the associated information of the first data packet includes at least one of the following:

The sideline control information SCI used to schedule the first data packet, the resource pool used to transmit the first data packet, and the information carried in the first data packet.
The method according to claim 2, wherein the SCI includes first indication information, and the first indication information is used to indicate version information of the first data packet.
The method according to claim 2 or 3, wherein a first mapping relationship is configured on the first terminal, and the first mapping relationship is used to represent a mapping relationship between a resource pool and version information of a data package.
The method according to any one of claims 2-4, wherein the information carried in the first data packet includes at least one of the following:

The target address information in the medium access control MAC protocol data unit PDU subheader in the first data packet, the version information in the MAC PDU subheader in the first data packet, the Reserved information in the MAC PDU subheader.
The method according to claim 5, wherein a second mapping relationship is configured on the first terminal, 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 method according to claim 6, wherein the second mapping relationship is configured by a network device, or is sent by the second terminal to the first terminal, or is predefined.
The method according to any one of claims 5-7, wherein 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 in A target version corresponding to at least two versions, wherein the at least two versions include a first version and a second version.
The method according to any one of claims 5-8, wherein the value of the reserved information in the MAC PDU subheader of the first data packet is used to indicate the version information of the first data packet A corresponding target version in at least two versions, wherein the at least two versions include a first version and a second version.
The method according to any one of claims 2-9, wherein the version information of the first data packet is the first version or the second version, wherein the first version supports sending or receiving address resolution Protocol ARP type PDCP SDU, the second version does not support sending or receiving ARP type PDCP SDU.
The method according to claim 10, wherein the 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 includes:

When the version information of the first data packet is the first version, and the first terminal does not support receiving ARP-type PDCP SDUs, the first terminal discards the first data packet; or

If the version information of the first data packet is the first version, and the first terminal supports receiving ARP-type PDCP SDUs, the first terminal receives the first data packet.
The method according to any one of claims 8-11, wherein the first version comprises version 17 and the second version comprises version 16.
The method according to claim 1, wherein the associated information of the first data packet includes at least one of the following:

The reserved information in the subheader of the MAC sub-PDU in the first data packet, and the logical channel identifier LCID in the subheader of the MAC sub-PDU in the first data packet.
The method according to claim 13, wherein the associated information of the first data packet is used to determine whether the PDCP SDU type of the MAC sub-PDU in the first data packet is an ARP type.
The method according to claim 14, wherein the 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 of the MAC sub-PDU is ARP type.
The method according to any one of claims 13-15, wherein a third mapping relationship is configured on the first terminal, and the third mapping relationship is used to indicate the LCID corresponding to the PDCP SDU of the ARP type and The LCID corresponding to the non-ARP PDCP SDU.
The method according to claim 16, wherein 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 method according to any one of claims 14-17, wherein, according to the version information of the first data packet or the PDCP SDU type of the first data packet, it is determined whether to perform the first Reception of packets, including:

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, the terminal device receives the first MAC sub-PDU MAC SDUs; or

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 the ARP-type PDCP SDU, the terminal device discards the first MAC sub-PDU MAC SDU in.
The method according to any one of claims 1-18, further comprising:

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 method according to claim 19, wherein the first capability information is sent through a physical sidelink feedback channel (PSFCH).
The method according to any one of claims 1-20, further comprising:

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 method according to any one of claims 1-21, wherein the version information of the first data packet includes a sending specification of the first data packet.
A method for lateral transmission, characterized in that it comprises:

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 version information of the first data packet or the Packet Data Convergence Protocol PDCP in the first data packet Type of service data unit SDU.
The method according to claim 23, wherein the associated information of the first data packet includes at least one of the following:

The sideline control information SCI used to schedule the first data packet, the resource pool used to transmit the first data packet, and the information carried in the first data packet.
The method according to claim 24, wherein the SCI includes first indication information, and the first indication information is used to indicate version information of the first data packet.
The method according to claim 24 or 25, wherein a first mapping relationship is configured on the first terminal, and the first mapping relationship is used to represent a mapping relationship between a resource pool and version information of a data package.
The method according to any one of claims 24-26, wherein the information carried in the first data packet includes at least one of the following:

The target address information in the medium access control MAC protocol data unit PDU subheader in the first data packet, the version information in the MAC PDU subheader in the first data packet, the Reserved information in the MAC PDU subheader.
The method according to claim 27, wherein a second mapping relationship is configured on the second terminal, 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 method according to claim 28, wherein the second mapping relationship is configured by the network device, or is predefined.
The method according to any one of claims 27-29, wherein 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 A corresponding target version in at least two versions, wherein the at least two versions include a first version and a second version.
The method according to any one of claims 27-30, wherein the value of the reserved information in the MAC PDU subheader of the first data packet is used to indicate the version information of the first data packet is a corresponding target version in at least two versions, wherein the at least two versions include a first version and a second version.
The method according to any one of claims 24-31, wherein the version information of the first data packet is the first version or the second version, wherein the first version supports sending or receiving address resolution Protocol ARP type PDCP SDU, the second version does not support sending or receiving ARP type PDCP SDU.
The method of any one of claims 30-32, wherein the first version comprises version 17 and the second version comprises version 16.
The method according to any one of claims 23-33, wherein the version information of the first data packet includes a sending specification of the first data packet.
The method according to claim 23, wherein the associated information of the first data packet includes at least one of the following:

The reserved information in the subheader of the MAC sub-PDU in the first data packet, and the logical channel identifier LCID in the subheader of the MAC sub-PDU in the first data packet.
The method according to claim 35, wherein the association information of the first data packet is used to determine whether the PDCP SDU type of the MAC sub-PDU in the first data packet is an ARP type.
The method according to claim 36, wherein 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 of the MAC sub-PDU is an ARP type .
The method according to any one of claims 35-37, wherein a third mapping relationship is configured on the second terminal, and the third mapping relationship is used to indicate the LCID corresponding to the PDCP SDU of the ARP type and The LCID corresponding to the non-ARP PDCP SDU.
The method according to claim 38, wherein the third mapping relationship is configured by the network device, or is predefined.
The method according to any one of claims 23-39, further comprising:

The second terminal receives the 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 method according to claim 40, wherein the first capability information is sent through a physical sidelink feedback channel PSFCH.
The method according to any one of claims 23-41, further comprising:

The second capability information reported by the second terminal to the first terminal, where the second capability information is used to indicate whether the second terminal supports receiving ARP-type PDCP SDUs.
The method according to any one of claims 23-42, further comprising:

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 needs to support ARP-type PDCP SDUs, and the first target address is the target address of the second terminal.
The method according to claim 43, wherein the capability information of the first target address is reported to the network device through sidelink user equipment information.
A method for lateral transmission, characterized in that it comprises:

The network device sends 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 type of the packet data convergence protocol PDCP service data unit SDU in the sidelink data packet.
The method according to claim 45, wherein 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 method according to claim 45 or 46, further comprising:

The network device receives the capability information of the first target address reported by the terminal 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 The target address is the target address of the terminal device.
The method according to claim 47, wherein the capability information of the first target address is reported to the network device through sidelink user equipment information.
The method according to any one of claims 45-48, wherein the version information of the sidebound data packet is the first version or the second version, wherein the first version supports sending or receiving address resolution Protocol ARP type PDCP SDU, the second version does not support sending or receiving ARP type PDCP SDU.
The method of claim 49, wherein the first version comprises version 17 and the second version comprises version 16.
A terminal device, characterized in that it includes:

A processing unit, 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 according to the version information of the first data packet or the PDCP SDU type of the first data packet, determine whether to receive the first data packet.
A terminal device, characterized in that it includes:

A communication unit, configured to send a first data packet to a first terminal, wherein the associated information of the first data packet is used to determine version information of the first data packet or aggregation of packet data in the first data packet Type of protocol PDCP service data unit SDU.
A network device, characterized in that it includes:

A communication unit, configured to send first information to the terminal device, wherein the first information is used to determine the version information of the sidelink data packet or the type of the packet data convergence protocol PDCP service data unit SDU in the sidelink data packet .
A terminal device, characterized by comprising: 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 of the following claims 1 to 22 one of the methods described.
A terminal device, characterized by comprising: a processor and a memory, the memory is used to store a computer program, the processor is used to invoke and run the computer program stored in the memory, and execute any of the following claims 23 to 44 one of the methods described.
A chip, characterized in that it includes: a processor, used to call and run a computer program from a memory, so that the device installed with the chip executes the method according to any one of claims 1 to 22, or as described in A method as claimed in any one of claims 23 to 44.
A computer-readable storage medium, characterized in that it is used to store a computer program, the computer program causes the computer to perform the method according to any one of claims 1 to 22, or any one of claims 23 to 44 method described in the item.
A computer program product, characterized in that it includes computer program instructions, the computer program instructions cause the computer to perform the method as described in any one of claims 1 to 22, or as described in any one of claims 23 to 44 Methods.
A computer program, characterized in that the computer program causes a computer to execute the method according to any one of claims 1 to 22, or the method according to any one of claims 23 to 44.
A network device, characterized by comprising: a processor and a memory, the memory is used to store a computer program, the processor is used to invoke and run the computer program stored in the memory, and execute any of claims 45 to 50 one of the methods described.
A chip, characterized by comprising: a processor, configured to call and run a computer program from a memory, so that a device installed with the chip executes the method according to any one of claims 45 to 50.
A computer-readable storage medium, characterized by being used for storing a computer program, the computer program causes a computer to execute the method according to any one of claims 45 to 50.
A computer program product, characterized by comprising computer program instructions, the computer program instructions cause a computer to execute the method according to any one of claims 45 to 50.
A computer program, characterized in that the computer program causes a computer to execute the method according to any one of claims 45-50.