WO2023092507A1

WO2023092507A1 - Sidelink communication method and apparatus

Info

Publication number: WO2023092507A1
Application number: PCT/CN2021/133730
Authority: WO
Inventors: 张博源; 赵振山; 卢前溪
Original assignee: Oppo广东移动通信有限公司
Priority date: 2021-11-26
Filing date: 2021-11-26
Publication date: 2023-06-01
Also published as: CN117837205A

Abstract

Provided in the embodiments of the present application are a sidelink communication method and apparatus. The method comprises: a first terminal device determining a first BWP among a plurality of BWPs according to first data and/or BWP configuration information; and the first terminal device sending the first data to a second terminal device by means of the first BWP. A plurality of BWPs are configured for a terminal device on a sidelink by means of a network device, such that different service requirements of the terminal device can be effectively met. In addition, BWP configuration information is configured by means of the network device, such that the first terminal device may select, from the plurality of BWPs, one BWP for use according to first data and the BWP configuration information, which need to be transmitted. Therefore, it can be effectively ensured that the plurality of configured BWPs can meet the use of the terminal device for different service requirements.

Description

Side link communication method and device

technical field

The present application relates to communication technologies, and in particular to a side link communication method and device.

Background technique

Sidelink (sidelink, SL) communication is different from the way in which communication data is received or sent by a base station in a traditional cellular system, and devices can communicate directly with each other.

Network devices often need to configure corresponding transmission resources for terminal devices on the side link. Currently, only a single BWP is supported in the system for terminal devices on the side link. However, different terminal devices have different service requirements. For example, some terminal devices have power-saving requirements, and some terminal devices have high service throughput requirements. Therefore, configuring a single BWP cannot meet the requirements of different terminal devices. need.

Contents of the invention

Embodiments of the present application provide a side link communication method and device to meet different requirements of different terminal devices.

In the first aspect, the embodiment of the present application provides a side link communication method, including:

The first terminal device determines the first BWP among the multiple BWPs according to the first data and/or BWP configuration information;

The first terminal device sends the first data to the second terminal device through the first BWP.

In the second aspect, the embodiment of the present application provides a side link communication method, including:

The second terminal device negotiates a first BWP with the first terminal device, where the first BWP is determined by the first terminal device among multiple BWPs according to the first data and/or BWP configuration information;

If the first BWP is successfully negotiated, the second terminal device receives the first data sent by the first terminal device through the first BWP.

In a third aspect, the embodiment of the present application provides a sidelink communication device, including:

A processing module, configured for the first terminal device to determine the first BWP among the multiple BWPs according to the first data and/or BWP configuration information;

A sending module, configured for the first terminal device to send the first data to a second terminal device through the first BWP.

In a fourth aspect, the embodiment of the present application provides a sidelink communication device, including:

A processing module, configured for the second terminal device to negotiate a first BWP with the first terminal device, wherein the first BWP is determined among multiple BWPs by the first terminal device according to the first data and/or BWP configuration information ;

A sending module, configured to, if the negotiation on the first BWP is successful, the second terminal device receives the first data sent by the first terminal device through the first BWP.

In a fifth aspect, the embodiment of the present application provides a terminal device, including: a transceiver, a processor, and a memory;

the memory stores computer-executable instructions;

The processor executes the computer-executable instructions stored in the memory, so that the processor executes the side-link communication method described in the first aspect above.

In a sixth aspect, the embodiment of the present application provides a terminal device, including: a transceiver, a processor, and a memory;

the memory stores computer-executable instructions;

The processor executes the computer-executable instructions stored in the memory, so that the processor executes the side-link communication method as described in the second aspect above.

In the seventh aspect, the embodiment of the present application provides a computer-readable storage medium, where computer-executable instructions are stored in the computer-readable storage medium, and when the computer-executable instructions are executed by a processor, they are used to implement the above first aspect or The side link communication method as described in the second aspect above.

In the eighth aspect, the embodiment of the present application provides a computer program product, including a computer program, characterized in that, when the computer program is executed by a processor, the side link communication method as described in the first aspect above or in the second aspect above is implemented .

Embodiments of the present application provide a side link communication method and apparatus, and the method includes: a first terminal device determines a first BWP among the multiple BWPs according to first data and/or BWP configuration information. The first terminal device sends the first data to the second terminal device through the first BWP. Configure multiple BWPs to the terminal devices on the side link through the network device, so as to effectively meet the different service requirements of the terminal devices. At the same time, configure the BWP configuration information through the network device, so the first terminal device may need to transmit the first data and/or BWP configuration information, and select a BWP to use among multiple BWPs, so as to effectively ensure that the configured multiple BWPs can meet different service requirements of the terminal device.

Description of drawings

FIG. 1 is a schematic diagram of the types of V2X applications provided by the embodiment of the present application;

FIG. 2 is a schematic diagram of a V2X communication scenario provided by an embodiment of the present application;

FIG. 3 is a schematic diagram of another V2X communication scenario provided by the embodiment of the present application;

FIG. 4 is a schematic diagram of implementation of data packet copy transmission provided by the embodiment of the present application;

Figure 5 is a schematic diagram of the BWP provided by the embodiment of the present application;

FIG. 6 is a flow chart of a side link communication method provided by an embodiment of the present application;

FIG. 7 is a first schematic diagram of the implementation of BWP configuration information provided by the embodiment of the present application;

FIG. 8 is a second schematic diagram of the implementation of BWP configuration information provided by the embodiment of the present application;

FIG. 9 is a third schematic diagram of the implementation of BWP configuration information provided by the embodiment of the present application;

FIG. 10 is a schematic diagram 4 of realizing BWP configuration information provided by the embodiment of the present application;

FIG. 11 is a schematic diagram five of the implementation of the BWP configuration information provided by the embodiment of the present application;

FIG. 12 is a signaling interaction diagram of the side link communication method provided by the embodiment of the present application;

FIG. 13 is a first implementation schematic diagram of determining a negotiation result by a second terminal device provided in an embodiment of the present application;

FIG. 14 is a second implementation schematic diagram of determining a negotiation result by a second terminal device provided in an embodiment of the present application;

FIG. 15 is a first structural schematic diagram of a sidelink communication device provided by an embodiment of the present application;

FIG. 16 is a second structural schematic diagram of a sidelink communication device provided by an embodiment of the present application;

FIG. 17 is a first structural schematic diagram of a terminal device provided by an embodiment of the present application;

FIG. 18 is a second schematic structural diagram of a terminal device provided by an embodiment of the present application.

Detailed ways

For ease of understanding, first, the concepts involved in this application will be described.

Terminal device: It is a device with wireless transceiver function. Terminal equipment 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 on aircraft, balloons and satellites, etc.). The terminal device may be a mobile phone, a tablet computer (Pad), a computer with a wireless transceiver function, a virtual reality (virtual reality, referred to as VR) terminal device, an augmented reality (augmented reality, referred to as AR) terminal device, an industrial Wireless terminals in industrial control, vehicle terminal equipment, wireless terminals in self driving, wireless terminal equipment in remote medical, wireless terminal equipment in smart grid, Wireless terminal devices in transportation safety, wireless terminal devices in smart city, wireless terminal devices in smart home, wearable terminal devices, etc. The terminal equipment involved in the embodiments of the present application may also be referred to as terminal, user equipment (UE), access terminal equipment, vehicle-mounted terminal, industrial control terminal, UE unit, UE station, mobile station, mobile station, remote station , remote terminal equipment, mobile equipment, UE terminal equipment, wireless communication equipment, UE agent or UE device, etc. Terminal equipment can also be fixed or mobile.

Network device: It is a device with wireless transceiver function. Including but not limited to: evolved base station (Evolutional Node B, eNB or eNodeB) in long term evolution (long term evolution, LTE), base station (gNodeB or gNB) or transceiver point ( transmission receiving point/transmission reception point, TRP), the base station in the subsequent evolution system, the access node in the wireless fidelity (Wireless Fidelity, WiFi) system, the wireless relay node, the wireless backhaul node, etc. The base station can be: a macro base station, a micro base station, a pico base station, a small station, a relay station, or a balloon station, etc. Multiple base stations may support the aforementioned networks of the same technology, or may support the aforementioned networks of different technologies. A base station may contain one or more co-sited or non-co-sited TRPs. The network device may also be a wireless controller, a centralized unit (centralized unit, CU), and/or a distributed unit (distributed unit, DU) in a cloud radio access network (cloud radio access network, CRAN) scenario. The network device can also be a server, a wearable device, or a vehicle-mounted device, etc. In the following, a network device is used as an example for description. The multiple network devices may be base stations of the same type, or base stations of different types. The base station can communicate with the terminal, and can also communicate with the terminal through a relay station. The terminal can communicate with multiple base stations of different technologies. For example, the terminal can communicate with the base station supporting the LTE network, and can also communicate with the base station supporting the 5G network. It can also support dual connection with the base station of the LTE network and the base station of the 5G network , It can also support dual connection with the base station of the 5G network, etc.

Sideline (sideline, SL): defines a direct communication link between terminal devices as a sideline, which may also be called a direct link. The wireless interface corresponding to the direct link on the terminal device is called a direct communication interface, also called an SL (Sidelink, direct communication) interface. The communication link between the network device and the terminal device is called Uu link (cellular communication link), and the wireless interface corresponding to the cellular communication link on the terminal device is called Uu interface.

Side link (sideline, SL) communication: refers to communication between terminal devices. A link between terminal devices is called a secondary link. Wherein, the side link may also be called a device-to-device (device-to-device, D2D) link, a side link, a side link, etc., which is not limited in this application.

The technical solution of the embodiment of the present application can be applied to various communication systems, for example: long term evolution (long term evolution, LTE) system, LTE frequency division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex) , TDD), the fifth generation (5th generation, 5G) communication system, the future communication system (such as the sixth generation (6th generation, 6G) communication system), or a system where multiple communication systems are integrated, etc., the embodiments of the present application do not Do limited. Among them, 5G can also be called new radio (new radio, NR).

The technical solution provided by the embodiment of the present application can be applied to various communication scenarios, for example, it can be applied to one or more of the following communication scenarios: eMBB communication, URLLC, machine type communication (machine type communication, MTC), mMTC, device Device-to-device (D2D) communication, vehicle to everything (V2X) communication, vehicle to vehicle (V2V) communication, vehicle to Internet (vehicle to network, V2N), vehicle to Infrastructure (vehicle to infrastructure, V2I), vehicle to pedestrian (vehicle to pedestrian, V2P), and internet of things (IoT), etc. Optionally, mMTC may include one or more of the following communications: communications in industrial wireless sensor or network (IWSN), communications in video surveillance (video surveillance) scenarios, and communications in wearable devices wait.

On the basis of the relevant concepts introduced above, in order to make the description of the following embodiments clear and concise, a brief introduction of the relevant technologies is given first.

LTE may be configured to support Device to Device (D2D) communication, Vehicle to Vehicle (V2V) communication and/or Vehicle to Everything (V2V) using Proximity based Service (ProSe). X, V2X) communication.

Among them, vehicle to everything (Vehicle to X, V2X) communication is a key technical direction of the protocol version 16 (Release 16, R16), and NR V2X, as an enhancement of Long Term Evolution (LTE) V2X, is an enabling vehicle The key technical means of networking.

For example, V2X can be introduced in conjunction with FIG. 1 , which is a schematic diagram of types of V2X applications provided by the embodiment of the present application.

Referring to Figure 1, it can be determined that the V2X application of V2X in this application can include the following four different types:

Vehicle to Vehicle (V2V), Vehicle to Infrastructure (V2I), Vehicle to Network (V2N), Vehicle to Pedestrian (V2P).

That is, V2X communication may include vehicles configured to communicate with Vehicle-to-Infrastructure/Network (V2I/N) (e.g., Vehicle-to-Pedestrian (V2P), Pedestrian-to-Vehicle (P2V), Road Side Unit (RSU) ) interface connected devices. In these cases, the vehicle can perform message transmission using resources assigned by the network (e.g. eNB or RSU) or pre-configured for V2X use.

In V2X communication, side link communication is performed between V2X devices through a side link (side link), where the side link may also be referred to as a side link, a secondary link, a side link, and a side link.

On the basis of the content introduced in Figure 1 above, it can be understood that, unlike the traditional cellular system in which communication data is received or sent through the base station, in V2X communication, the vehicle networking system adopts a terminal-to-terminal direct communication method. Therefore, it has higher spectral efficiency and lower transmission delay.

Furthermore, for V2X communication, two transmission modes are defined in 3GPP: mode 1 and mode 2. The following two transmission modes are introduced in combination with FIG. 2 and FIG. 3 respectively, and FIG. A schematic diagram of a V2X communication scenario, and FIG. 3 is a schematic diagram of another V2X communication scenario provided by an embodiment of the present application.

Referring to FIG. 2 , a network device 201 , a terminal device 202 and a terminal device 203 are included in FIG. 2 . Wherein, the link between the terminal device 202 and the terminal device 203 is a side link, and the side link has been described in detail in the foregoing embodiments, and will not be repeated here.

Wherein, the link between the terminal device 202 and the network device 201, and the link between the terminal device 203 and the network device 201 is a Uu air interface link, wherein the Uu air interface can be understood as a universal interface between the UE and the network (universal UE to network interface), Uu air interface communication refers to the communication between terminal equipment and network equipment.

The situation shown in FIG. 2 is the mode 1 described above. Specifically, the transmission resource of the terminal device in mode 1 is allocated by the network device. For example, the network device can use the downlink (Downlink, DL) shown in FIG. 2 as End devices allocate resources. Afterwards, the terminal device sends data on the side link according to the resources allocated by the network device; the network device can allocate resources for a single transmission to the terminal device, or allocate resources for semi-static transmission to the terminal device.

And the mode 2 introduced above can also be understood in conjunction with FIG. 3 , as shown in FIG. 3 , which includes a network device 301 , a terminal device 302 and a terminal device 303 . Its implementation is similar to that described above in FIG. 2 , and will not be repeated here.

The situation shown in FIG. 3 is the mode 2 introduced above. Specifically, in the mode 2, the terminal device can select a resource from the resource pool for data transmission.

On the basis of the content introduced above, the D2D research process is described below. In 3GPP, D2D is divided into different stages for research.

1. ProSe: D2D communication in Rel-12/13 is researched on the ProSe scenario, which is mainly aimed at public security services.

In ProSe, by configuring the position of the resource pool in the time domain, for example, the resource pool is discontinuous in the time domain, so that the UE can discontinuously send/receive data on the side link, thereby achieving the effect of power saving.

2. Vehicle-to-vehicle (V2X): In Rel-14/15, the vehicle-to-vehicle system was studied for the vehicle-to-vehicle communication scenario, which is mainly for relatively high-speed moving vehicle-to-vehicle and vehicle-to-human communication services;

In V2X, because the vehicle system has continuous power supply, power efficiency is not the main issue, but the delay of data transmission is the main issue, so the system design requires the terminal equipment to perform continuous transmission and reception.

3. Wearable devices (FeD2D): In Rel-14, this scenario studies the scenario where wearable devices access the network through mobile phones, and it is mainly oriented to scenarios with low mobile speed and low power access.

In FeD2D, the 3GPP conclusion in the pre-research stage is that the base station can configure the Discontinuous Reception (DRX) parameters of the remote (remote) terminal through a relay (relay) terminal, but since this subject has not further entered the standardization stage, The exact details of how the DRX configuration is done are inconclusive.

4. Multi-carrier: In Rel-15LTE V2X, a multi-carrier mechanism is introduced. Specifically, the multi-carrier mechanism is reflected in that the UE can support data packet segmentation and use multiple carriers to transmit data packets to improve the data transmission rate; and multi-carrier The mechanism supports data packet duplication, duplicating the same data packet twice and sending them on two carriers to improve transmission reliability; it also supports multi-carrier reception enhancement at the receiving end.

Specifically, for data packet replication: V2X side chain communication supports side chain packet replication, and is executed at the Packet Data Convergence Protocol (PDCP) layer of the UE. For sidelink packet replication for transmission, the PDCP PDU (Protocol Data Unit, Protocol Data Unit) is replicated at the PDCP entity.

For example, it can be understood with reference to FIG. 4 , which is a schematic diagram of implementation of data packet copy transmission provided by the embodiment of the present application. As shown in Figure 4, duplicate PDCP PDUs of the same PDCP entity are submitted to two different Radio Link Control (Radio Link Control, RLC) entities, such as RLC1 and RLC2 shown in Figure 4, and for the duplicate PDCP PDUs respectively Associated to two different sidechain logical channels. Among them, the duplicated duplicated PDCP PDUs of the same PDCP entity are only allowed to be transmitted on different side chain carriers.

In a possible implementation, the UE may activate or deactivate sidechain packet replication based on (pre)configuration.

Also, the ProSe Per-Packet Reliability (PPPR) value that supports sidechain packet replication can be (pre)configured via PPPR thresholds. Wherein, for UE autonomous resource selection and scheduled resource allocation, the UE shall perform side chain packet replication for data configured with PPPR values until the packet replication configuration is canceled for these data configured with PPPR values. For scheduled resource allocation, the UE can report the amount of data associated with one or more PPPR values and the destination to which the data belongs through a sidechain buffer status report (Buffer Status Report, BSR). Wherein the mapping of the PPPR value to the logical channel group can be configured by the eNB, and the PPPR value is reflected by the associated logical channel group ID included in the side chain BSR. A list of one or more PPPR values may be reported by a Radio Resource Control (RRC) connected UE in Sidechain UE Information.

The above content introduces the D2D/V2X of LTE. The following describes NR V2X.

On the basis of LTE V2X, NR V2X is not limited to broadcast scenarios, but has been further expanded to unicast and multicast scenarios, and the application of V2X is studied in these scenarios.

Similar to LTE V2X, NR V2X will also define the above mode-1/2 two resource authorization modes; further, the terminal device may be in a mixed mode, that is to say, it can use mode-1 for resource acquisition, At the same time, mode-2 can be used to obtain resources. The resource acquisition is indicated by means of a sidelink grant, that is, the sidelink grant indicates the time-frequency positions of corresponding PSCCH and PSSCH resources.

And, unlike LTE V2X, in addition to HARQ retransmission initiated by UE without feedback, NR V2X also introduces feedback-based HARQ retransmission, which is not limited to unicast communication, but also includes multicast communication;

Same as LTE V2X, in NR V2X, because the vehicle system has continuous power supply, power efficiency is not the main issue, but the delay of data transmission is the main issue, so the system design requires terminal equipment to perform continuous transmission and reception.

gNB works in dynamic or semi-static channel access mode. In both channel access modes, the gNB and UE can apply listen before talk (LBT) before performing transmissions on cells configured with shared spectrum channel access. When applying LBT, the transmitter listens/senses the channel to determine whether the channel is free or busy, and only performs transmission when the channel is sensed to be free.

Wherein, the UE can detect an uplink LBT failure, and the detection is based on each bandwidth part (BWP) and based on all uplink transmissions within the BWP.

The following is a brief introduction to BWP. In 5G NR, both the system bandwidth and the terminal bandwidth may reach hundreds of MHz or even several GHz to support high-speed mobile data transmission, but this is not always required in actual data transmission. Large bandwidth, for example, in a working scenario that only needs to support low data rate transmission (such as WeChat chat), the terminal device only needs to use a small working bandwidth, for example, a bandwidth of 10MHz is sufficient.

In order to flexibly support different bandwidth requirements in the above-mentioned different scenarios, 5G introduces the concept of BWP. Wherein, the bandwidth part may be a part of the system bandwidth (cell carrier bandwidth). For example, the system bandwidth is 100 MHz, and the terminal equipment may use a bandwidth less than 100 MHz. For example, the bandwidth part of 20 MHz or 50 MHz may be used for data transmission within the system bandwidth. The bandwidth part can also be called "carrier bandwidth part", also can be called "operating bandwidth (operating bandwidth), or transmission bandwidth, and the name and abbreviation of the bandwidth part are not particularly limited in the embodiment of the present application.

In a possible implementation, the network device can enable the terminal device to switch between multiple BWPs according to the service requirements of the terminal device. ; When the terminal device transmits at a relatively small service data rate, it can use a BWP with a relatively small bandwidth.

A possible implementation manner of the BWP is introduced below with reference to FIG. 5 , which is a schematic diagram of the BWP provided in the embodiment of the present application.

As shown in Figure 5, there are currently multiple moments:

Assuming that at the first moment t1, the traffic volume of the terminal device is relatively large, the network device can configure a large bandwidth (BWP1) for the terminal device, and it can be assumed that the frequency range of BWP1 is 15KHz to 40MKz;

Assuming that at the second time t2, the traffic volume of the terminal equipment is small, the network equipment can configure a small bandwidth (BWP2) for the terminal equipment. It can be assumed that the frequency range of BWP2 is 15KHz ~ 10MKz, as long as BWP2 can meet the basic requirements of the terminal equipment. communication needs;

Assuming that at the third moment t3, the network device finds that there is a wide range of frequency selective fading in the bandwidth where BWP1 is located, or that the resources in the frequency range where BWP1 is located are relatively scarce, at this time the network device can configure a new bandwidth (BWP3) for the terminal device, It can be assumed that the frequency range of BWP3 is 60KHz～20MKz.

Those skilled in the art can understand that the above-mentioned introduction to BWP in conjunction with FIG. There is no particular limitation on this.

Based on the above introduction, it can be determined that the UE can detect an uplink LBT failure based on each BWP and based on all uplink transmissions in each BWP.

In a possible implementation, when a consistent uplink LBT failure is detected on a secondary cell (Secondary Cell, SCell), the UE transmits the LBT failure via MAC CE on a serving cell different from the SCell where the failure is detected The fault is reported to the corresponding gNB, where the master node (MN) is used for the master cell group (Master Cell group, MCG), and the secondary node (Secondary node, SN) is used for the secondary cell group (Secondary Cell group, SCG)) . If there are no resources available for transmitting a Media Access Control Control Element (MAC CE), the UE may transmit a Scheduling Request (SR).

In another possible implementation, when a consistent uplink LBT failure is detected on the SpCell, the UE switches to another uplink configured with random access channel (Random Access Channel, RACH) resources on the cell Link (Uplink, UL) BWP, initiates RACH, and reports failure through MAC CE. When multiple UL BWPs are available for exchange, it is up to the UE implementation to choose which one. Among them, SpCell (special Cell) includes primary cell (Primary Cell, PCell) and primary secondary cell (Primary Secondary Cell, PSCell)

In another possible implementation, for PSCell, if a consistent uplink LBT failure is detected on all UL BWPs configured with RACH resources, the UE declares SCG radio link failure (radio link failure, RLF), And report failure to MN through SCG FailureInformation (configuration failure).

In another possible implementation, for PCell, if an uplink LBT failure is detected on all UL BWPs with configured RACH resources, the UE declares RLF.

On the basis of the content introduced above, the implementation of the BWP configuration of the opposite link in the related art will be described below.

In NR V2X and Rel-17 sidelink enh, only a single BWP is supported in the system for the terminal device of the direct link. However, because different terminals have different service requirements, for example, some terminal devices have power-saving requirements, and some terminal devices have high service throughput requirements. Therefore, currently configuring a single BWP cannot meet the different requirements of different terminals.

Aiming at the problems in the prior art, this application proposes the following technical idea: the network device configures multiple BWPs for the terminal equipment of the side link, so as to effectively meet the needs of different terminal equipment, and this application aims to solve the problem of direct link How to select one or more configured BWPs for the terminal device of the direct link in communication.

On the basis of the content introduced above, the side link communication method provided by the present application will be described below in conjunction with specific embodiments. First, description will be made with reference to FIG. 6 , which is a flowchart of a side link communication method provided by an embodiment of the present application.

As shown in Figure 6, the method includes:

S601. The first terminal device determines a first BWP among multiple BWPs according to the first data and/or BWP configuration information.

In this embodiment, the communication scenario may be, for example, that the first terminal device sends service data to the second terminal device. In a possible implementation, the first data in this embodiment may be currently required by the first terminal device The data corresponding to the sent business.

And, the first terminal device in this embodiment may also determine BWP configuration information, where the BWP configuration information may include information corresponding to multiple BWPs, and the multiple BWPs may be configured by the network device for the terminal device, for example. , and the information corresponding to each BWP therein may also be configured for each BWP by the network device.

In a possible implementation manner, the BWP configuration information may include at least one of the following first information, for example:

The priority corresponding to each BWP in multiple BWPs; at least one target address corresponding to each BWP in multiple BWPs; at least one quality of service (Quality of Service, QoS) flow identifier corresponding to each BWP in multiple BWPs; At least one geographical area identifier corresponding to each BWP in the BWP.

Wherein, the target address may include at least one of the following information, for example: the group identifier of the target device, the identifier of the target device, and the service type; wherein, the target device may be the device corresponding to the service that the current terminal device needs to send, That is to say, the current terminal device is to send service data to the target device. The group ID of the target device can be understood as the group ID of the target device in a multicast scenario. And the service type therein can be, for example, making a phone call, sending a short message, etc., and this embodiment does not limit the specific realization of the specific service type. In a possible implementation, the specific data format of the target address can be, for example, n-bit data, and the n bits can indicate, for example, the group ID of the target device, the ID of the target device, and the service type described above. at least one of the

And, the QoS flow identifier introduced above is used to indicate the QoS flow. For example, the QoS flow identifier can be any of the following: QoS flow identifier (QoS flow identifier), default priority (default priority), logical channel ( logical channel (LCH) priority. Wherein, the default priority is a parameter of the QoS flow, so the corresponding QoS flow can be indicated according to the default priority. And there is a corresponding correspondence between the LCH priority and the QoS flow, so the corresponding QoS flow can also be indicated according to the LCH priority. In the actual implementation process, the specific implementation of the QoS flow identifier can be selected according to actual requirements, and this embodiment does not limit this, as long as the QoS flow identifier can uniquely identify each QoS flow.

The terminal device currently needs to determine the BWP used for the first data transmission among multiple BWPs. In a possible implementation, the first terminal device can select from multiple BWPs according to the first data and/or BWP configuration information. A first BWP matching the current first data, where the first BWP is a BWP used for data transmission.

S602. The first terminal device sends the first data to the second terminal device through the first BWP.

After the first BWP is determined, the first terminal device may send the first data corresponding to the service to be sent currently to the second device through the first BWP.

Therefore, the second terminal device can receive the first data sent by the first terminal device through the first BWP. In addition, the second terminal device can also send data to the first terminal device through the first BWP. Correspondingly, the first terminal device Therefore, the device can receive the data sent by the second terminal device through the first BWP. That is to say, the first terminal device and the second terminal device can perform data transmission on the determined first BWP.

The side link communication method provided by the embodiment of the present application includes: the first terminal device determines the first BWP among the multiple BWPs according to the first data and/or BWP configuration information. The first terminal device sends the first data to the second terminal device through the first BWP. Configure multiple BWPs to the terminal devices on the side link through the network device, so as to effectively meet the different service requirements of the terminal devices. At the same time, configure the BWP configuration information through the network device, so the first terminal device may need to transmit the first data As well as the BWP configuration information, one BWP is selected for use among multiple BWPs, thereby effectively ensuring that the configured multiple BWPs can meet different service requirements of the terminal device.

On the basis of the above-mentioned embodiments, it can be determined that the first terminal device needs to determine the first BWP among multiple BWPs according to the first data and/or BWP configuration information, and the above-mentioned introductions to the possible implementation of BWP configuration information The manner in which the first terminal device selects the first BWP in this application is further introduced below with reference to FIG. 7 to FIG. 11 . Figure 7 is a schematic diagram of the implementation of the BWP configuration information provided by the embodiment of the present application. Figure 8 is a schematic diagram of the implementation of the BWP configuration information provided by the embodiment of the present application. , FIG. 10 is a schematic diagram 4 for realizing BWP configuration information provided by the embodiment of the present application, and FIG. 11 is a schematic diagram 5 for realizing the BWP configuration information provided in the embodiment of the present application.

In a possible implementation manner, only the priority corresponding to each BWP may be included in the BWP configuration information, which can be understood with reference to FIG. 7 , for example.

As shown in Figure 7, the BWP configuration information includes BWP1, BWP2, BWP3, and BWP4, where the priority of BWP1 is priority 1, the priority of BWP2 is priority 3, the priority of BWP3 is priority 4, and the priority of BWP4 The priority is priority 2, and assume that the current priority order is priority 1>priority 2>priority 3>priority 4. Then it can be determined that the priority of BWP1 is the highest, and the priority of BWP3 is the lowest.

In this case, the first BWP may be a BWP with the highest priority among at least one second BWP, and the second BWP is a BWP in an available state among the multiple BWPs.

Specifically, the first terminal device may determine a second BWP in an available state among multiple BWPs, and then select a BWP with the highest priority among the second BWPs to obtain the first BWP. It can also be understood that the first terminal device preferentially selects the BWP with the highest priority, and when the BWP with the highest priority is unavailable, the terminal device selects the BWP with the second highest priority, and so on.

For example, it can be understood in conjunction with Figure 7. Assuming that among the current four BWPs, BWP1 is unavailable, and BWP2, BWP3, and BWP4 are all available, then the current BWP2, BWP3, and BWP4 are the second BWP introduced above. The BWP with the highest priority among the second BWPs is determined as the first BWP. In the example in FIG. 7 , the highest priority among the available BWPs is BWP4, so BWP4 may be determined as the first BWP.

In the actual implementation process, the specific indication form of the priority can be selected and set according to actual requirements, which is not limited in this embodiment, as long as the indication of the priority can specifically distinguish the priorities of different BWPs.

In another possible implementation manner, the BWP configuration information may only include at least one target address corresponding to each BWP, which can be understood with reference to FIG. 8 , for example.

As shown in Figure 8, the BWP configuration information includes BWP1 and BWP2, wherein the target address corresponding to each BWP may exist in the form of a target address list, for example, referring to Figure 8, the target address corresponding to BWP1 includes target address 1, target Address 2 , target address 3 , target address 4 , and target addresses corresponding to BWP2 include target address 5 , target address 6 , target address 7 , and target address 8 .

In the actual implementation process, the specific implementation of at least one target address corresponding to each BWP can be selected and set according to actual needs, wherein, for example, the target addresses corresponding to different BWPs may not overlap, or may also overlap. This is not limited.

In this case, there is a target address corresponding to the first data in at least one target address corresponding to the first BWP.

In a possible implementation manner, the current first data may be sent by the first terminal device to the second terminal device, so the target address corresponding to the first data may include at least one of the following, for example: the second terminal The device identifier, the group identifier of the second terminal device, and the service type corresponding to the first data.

Specifically, when determining the first BWP at present, the target address corresponding to the first data is found among the target addresses corresponding to which BWP, and the BWP is determined as the first BWP. It can also be understood that when the first terminal device currently sends the first data to the target address, it can use the BWP corresponding to the current target address to send.

For example, it can be understood in conjunction with FIG. 8 , assuming that the target address corresponding to the current first data is target address 4, it can be determined that in the BWP configuration information shown in FIG. 8 , the target address list of BWP1 includes target address 4, then it can be Determine BWP1 as the first BWP.

It can be understood that the situation shown in FIG. 8 above is a situation where the target addresses corresponding to the various BWPs do not overlap. In this case, there is only one BWP corresponding to a specific target address. In other possible implementations, when the target addresses corresponding to each BWP overlap, then it is possible that a specific target address corresponds to multiple BWPs. In this case, for example, each BWP can be configured with its own corresponding After that, among multiple BWPs corresponding to a specific target address, select the BWP with the highest priority to determine the first BWP.

In another possible implementation manner, the BWP configuration information may only include at least one QoS flow identifier corresponding to each BWP in the multiple BWPs, which can be understood with reference to FIG. 9 , for example.

As shown in Figure 9, the BWP configuration information includes BWP1 and BWP2, where the QoS flow identifiers corresponding to each BWP may exist in the form of a QoS flow identifier list, for example, referring to Figure 9, the QoS flow identifiers corresponding to BWP1 include QoS flow ID 1, QoS flow ID 2, QoS flow ID 3, QoS flow ID 4, and QoS flow IDs corresponding to BWP2 include QoS flow ID 5, QoS flow ID 6, QoS flow ID 7, and QoS flow ID 8.

In the actual implementation process, the specific implementation of at least one QoS flow identifier corresponding to each BWP can be selected and set according to actual needs, wherein the QoS flow identifiers corresponding to different BWPs may, for example, not overlap, or may overlap, this implementation Examples are not limited to this.

In this case, the QoS flow identifier corresponding to the first data exists in at least one QoS flow identifier corresponding to the first BWP.

Specifically, when determining the first BWP at present, it is to check which QoS flow identifier corresponding to the BWP has the QoS flow identifier corresponding to the first data, and then determine the BWP as the first BWP. It can also be understood that when the first terminal device currently sends a specific QoS flow corresponding to a certain service, the first terminal device can use the corresponding BWP to send.

For example, it can be understood in conjunction with FIG. 9, assuming that the QoS flow identifier corresponding to the current first data is QoS flow identifier 7, it can be determined that in the BWP configuration information shown in FIG. 9, the QoS flow identifier list of BWP2 includes the QoS flow identifier 7, BWP2 may be determined as the first BWP.

It can be understood that the situation shown in FIG. 9 above is a situation where the QoS flow identifiers corresponding to each BWP do not overlap. In this case, there is only one BWP corresponding to a specific QoS flow identifier. In other possible implementations, when the QoS flow identifiers corresponding to each BWP overlap, then there may be a situation where a specific QoS flow identifier corresponds to multiple BWPs. In this case, for example, you can configure for each BWP After that, among the multiple BWPs corresponding to the specific QoS flow identifier, select the BWP with the highest priority to determine the first BWP.

In another possible implementation manner, the BWP configuration information may only include at least one geographical area identifier corresponding to each BWP among the multiple BWPs, which can be understood with reference to FIG. 10 , for example.

As shown in Figure 10, the BWP configuration information includes BWP1 and BWP2, where the geographic area identifiers corresponding to each BWP may exist in the form of a list of geographic area identifiers, for example, referring to Figure 10, the geographic area identifiers corresponding to BWP1 include geographic area 1. Geographical area 2, geographical area 3, and geographical area identifiers corresponding to BWP2 include geographical area 4, geographical area 5, geographical area 6, and geographical area 7.

In the actual implementation process, the specific implementation of at least one geographic area identifier corresponding to each BWP can be selected and set according to actual needs, wherein the geographic area identifiers corresponding to different BWPs may not overlap, or may overlap, for example, this implementation Examples are not limited to this.

In this case, the at least one geographic area identifier corresponding to the first BWP includes the geographic area identifier of the geographic area where the first terminal device is located.

Specifically, when determining the first BWP, the BWP is determined as the first BWP based on the identification of the geographical area where the first terminal device is currently located in the geographical area identification corresponding to which BWP. It can also be understood that when the first terminal device moves to a certain geographic location area, the terminal device can use the corresponding BWP to send services.

For example, it can be understood in conjunction with FIG. 10 , assuming that the geographic area identifier corresponding to the current first data is geographic area 6, it can be determined that in the BWP configuration information shown in FIG. 10 , the geographic area list of BWP2 includes geographic area 6, then BWP2 may be determined as the first BWP.

It can be understood that the above situation shown in FIG. 9 is a situation in which the geographical area identifiers corresponding to each BWP do not overlap, and in this case there is only one BWP corresponding to a specific geographical area identifier. In other possible implementations, when the geographical area identifiers corresponding to each BWP overlap, then there may be a situation where a specific geographical area identifier corresponds to multiple BWPs. In this case, for example, you can configure for each BWP After each corresponding priority, among the multiple BWPs corresponding to the specific geographical area identifier, select the BWP with the highest priority to determine the first BWP.

What is described above with reference to FIG. 7-FIG. 10 is an implementation manner in which only a single first information is included in the BWP configuration information. In another possible implementation, the BWP configuration information in this application may also include at least two types of the first information introduced above, where the at least two types of first information correspond to different priorities, and the The priority is the priority for each first information.

In this case, for example, the BWP to be selected can be determined according to each first information, wherein the implementation of determining the BWP to be selected according to each first information is the same as the implementation of determining the first BWP introduced in Figures 7-9 above. Similarly, after each corresponding candidate BWP is determined according to each piece of first information.

For example, it may be determined whether the candidate BWPs determined according to each of the at least two kinds of first information are the same.

If it is determined that the candidate BWPs determined according to each piece of first information are the same, it can be determined that the only candidate BWP is currently determined, and thus the candidate BWP can be determined as the first BWP.

If it is determined that the candidate BWPs determined according to each piece of first information are different, it is currently necessary to determine which candidate BWP is to be determined as the first BWP. Because in this embodiment, a corresponding priority is set for each first information, the candidate BWP determined by the first information with the highest priority may be determined as the first BWP.

For example, the current implementation can be understood in conjunction with Figure 11. Referring to Figure 11, it is assumed that the current BWP configuration information includes the four types of first information introduced above. The introduction is similar and will not be repeated here.

In an example, it is assumed that the target address corresponding to the current first data is the target address 5, and the QoS flow identifier corresponding to the current first data is assumed to be the QoS flow identifier 5, and it is assumed that the current geographic area where the current terminal device is located is the geographic area 5. In the current situation, in the example of FIG. 11 , BWP2 will be selected when the candidate BWP is selected according to the priority, BWP2 will be selected when the candidate BWP is selected according to the target address, and BWP2 will be selected when the candidate BWP is selected according to the QoS flow identifier, And BWP2 will be selected when the candidate BWP is selected according to the geographical area, so in the current example, it can be determined that the candidate BWPs determined according to each first information are all the same, all of which are BWP2, so it can be determined that the first BWP is BWP2.

In another example, it is assumed that the target address corresponding to the current first data is target address 1, and the QoS flow identifier corresponding to the current first data is assumed to be QoS flow identifier 5, and it is also assumed that the current geographical area where the current terminal device is located is geographic area 3. In the current situation, in the example of FIG. 11 , BWP2 will be selected when the candidate BWP is selected according to the priority, BWP1 will be selected when the candidate BWP is selected according to the target address, and BWP2 will be selected when the candidate BWP is selected according to the QoS flow identifier. And when selecting the BWP to be selected according to the geographical area, BWP1 will be selected, so in the current example, it can be determined that the BWPs to be selected according to each first information are different, so the first information with the highest priority can be determined The obtained candidate BWP is determined as the first BWP.

In the example in FIG. 11, it is assumed that the priorities of each first information are as shown in FIG. The priority of the QoS flow identification information is priority 3, the priority of the geographical area information of the BWP is priority 4, and it is assumed that the current priority order is priority 1>priority 2>priority 3>priority 4. Then it can be determined that the priority information of the BWP is the highest, and the priority of the geographical area information of the BWP is the lowest.

Therefore, currently, the candidate BWP determined according to the priority information of the BWP may be determined as the first BWP, that is, it is determined that the first BWP is BWP2.

The above describes the possible implementation of determining the first BWP according to the first data and/or BWP configuration information. Further, after the first terminal device in this embodiment determines the first BWP, it also needs to report to the second BWP through the first BWP. The second terminal device sends the first data.

In a possible implementation manner, when sending the first data through the first BWP, the first terminal device needs to negotiate with the second terminal device on the first BWP, and after the first BWP negotiation is successful, the first Only the terminal device can send the first data to the second terminal device through the first BWP.

The negotiation here is mainly to determine whether the second terminal device determines whether the current first BWP can be used to transmit the first data. The specific realization of the first BWP negotiation between the first terminal device and the second terminal device is as follows in conjunction with Fig. 12 to Fig. 14 Make an introduction.

Figure 12 is a signaling interaction diagram of the side link communication method provided by the embodiment of the present application, Figure 13 is a schematic diagram of the first implementation of the second terminal device determining the negotiation result provided by the embodiment of the present application, and Figure 14 is provided by the embodiment of the present application The second implementation schematic diagram of determining the negotiation result by the second terminal device.

As shown in Figure 12, the negotiation process between the first terminal device and the second terminal device includes:

S1201. The first terminal device sends a first message to the second terminal device, where the first message is used to indicate the first BWP.

After the first terminal device determines the first BWP, the first terminal device may send a first message to the second terminal device, where the first message is used to indicate the first BWP. In a possible implementation manner, in For example, the first message may include BWP-related configuration information such as the bandwidth, time domain position, frequency domain position, and frequency point of the first BWP. This embodiment does not limit the specific implementation of the first message, as long as the first message can It only needs to be used to indicate the first BWP, and the first message may include any configuration information of the first BWP.

S1202. The second terminal device receives the first message sent by the first terminal device.

Afterwards, the second terminal device may receive the first message sent by the first terminal device, so as to determine which BWP the first BWP currently selected by the first terminal device is.

S1203. The second terminal device determines the negotiation result of the first BWP.

After receiving the first message, the second terminal device may determine a negotiation result of the first BWP according to the indicated first BWP, where the negotiation result is used to indicate whether the current first BWP is acceptable.

In a possible implementation manner of determining the negotiation result, referring to FIG. 13 , if the second terminal device is located in the service area (also referred to as the coverage area) 1301 of the network device, the second terminal device may send a verification message to the network device request, wherein the verification request is used to request the network device to determine whether the first BWP is available, for example, the above-mentioned first message may be included in the verification request, that is, the relevant configuration information of the first BWP is sent to the network device, and then the network device Determine whether the current first BWP is acceptable, so as to send the negotiation result to the second terminal device. Therefore, when the second terminal device determines the negotiation result of the first BWP, it receives the negotiation result determined by the network device. The negotiation result may indicate that the first BWP is available, or the negotiation result may also indicate that the first BWP is unavailable.

And when the second terminal device is in the service area of the network device, if the second terminal device is in the connected state, the above process can be directly executed; if the second terminal device is not in the connected state, then the second terminal device still It is necessary to trigger the second terminal device to enter the connected state. The connected state in this embodiment may specifically be the RRC connected state.

And in another possible implementation manner of determining the negotiation result, referring to FIG. 14, if the second terminal device is not located in the service area (also called coverage) 1401 of the network device, the second terminal device can determine by itself The result of the negotiation of the first BWP.

In a possible implementation, the second terminal device includes second BWP configuration information, where the second BWP configuration information is similar to the BWP configuration information introduced above, except that the above BWP configuration information is When the network device is configured to the terminal device, the current second BWP configuration information is pre-configured in the second terminal device, which can be understood as being pre-configured when the second terminal device leaves the factory. And the multiple BWPs corresponding to the current second BWP configuration information may be the same as or different from the multiple BWPs configured by the above-mentioned network device. This embodiment does not limit this, and it can be selected and limited according to actual needs .

Then the second terminal device can determine the second BWP among the multiple BWPs according to the first message and the second BWP configuration information. For example, the first message in this embodiment may also include at least one of the following: the identifier of the first terminal device, the service type of the first data, the QoS corresponding to the first data, and the geographical area where the first terminal device is located logo.

Wherein, the second BWP configuration information is similar to the BWP configuration information introduced above, and may include at least one of the following: a priority corresponding to each BWP in multiple BWPs; at least one target address corresponding to each BWP in multiple BWPs; At least one QoS flow identifier corresponding to each BWP in a BWP; at least one geographic area identifier corresponding to each BWP in a plurality of BWPs.

Then, when the second terminal device determines the second BWP according to the first message and the second BWP configuration information, its implementation is similar to the above-mentioned implementation of the first terminal device determining the first BWP.

Wherein, the implementation of determining the second BWP may include at least one of the following: determining the second BWP according to the priority corresponding to the BWP, determining the target address according to the identity of the first terminal device and the service type of the first data, and then determining the target address according to the priority of the target The address determines the second BWP, and the QoS corresponding to the first data determines the second BWP, and determines the second BWP according to the geographical area identifier where the first terminal device is located. Currently, various possible implementations of determining the second BWP are the same as the above introduction The implementation manner of determining the first BWP is similar and will not be repeated here.

After the second terminal device determines the second BWP according to the preconfigured second BWP configuration information, for example, it can determine whether the first BWP and the second BWP are the same, if they are the same, it can determine that the negotiation result indicates that the first BWP is available, if they are not the same , it may be determined that the negotiation result indicates that the first BWP is unavailable.

S1204. When the negotiation result indicates that the first BWP is available, the second terminal device determines that the response message is a confirmation message, and the confirmation message is used to indicate that the negotiation of the first BWP is successful.

In a possible implementation manner, when the negotiation result indicates that the first BWP is available, the second terminal device may determine that the response message is an acknowledgment message, where the acknowledgment message is used to indicate that the negotiation on the first BWP is successful. The confirmation message may be, for example, configuration completion (RRCReconfigurationSidelinkComplete).

In another possible implementation manner, when the negotiation result indicates that the first BWP is unavailable, the second terminal device may determine that the message is a failure message, where the failure message is used to indicate that the negotiation on the first BWP fails. The failure message may be, for example, configuration failure (RRCReconfigurationSidelinkFailure).

S1205. The second terminal device sends a response message to the first terminal device.

When confirming the response message, the second terminal device may send the above-mentioned determined response message to the first terminal device, so as to inform the first terminal device whether the current negotiation of the first BWP is successful.

S1206. The first terminal device receives a response message corresponding to the first message sent by the second terminal device.

S1207. When the response message is a confirmation message, the first terminal device determines that the negotiation on the first BWP is successful.

Afterwards, the first terminal device can receive the response message sent by the second terminal device. When the response message is a confirmation message, the first terminal device can confirm that the negotiation on the first BWP is successful, and then send a message to the second terminal device through the first BWP. The terminal device has sent the first data.

Or, if the response message is a failure message, the first terminal device may confirm that the negotiation on the first BWP fails, and the first terminal device may, for example, feed back the failure message to the network device, and the network device performs subsequent processing.

Through the negotiation process described above, it can be ensured that the first BWP determined by the first terminal device is also acceptable to the second terminal device, thereby ensuring correct transmission of subsequent first data.

The foregoing embodiment introduces the implementation process of negotiating the first BWP between the first terminal device and the second terminal device. In a possible implementation, the network device, for example, can configure a default (default) BWP for the terminal device, which is used to send a physical sidelink broadcast channel (Physical Sidelink Broadcast Channel, PSBCH) and a unicast link establishment process. .

Therefore, the negotiation process between the first terminal device and the second terminal device described above can be carried out on the default BWP. When the second terminal device accepts the first BWP determined by the first terminal device, it can be determined that the first terminal device and the second terminal device After the second terminal device successfully negotiates the first BWP, the first terminal device and the second terminal device need to switch to the negotiated first BWP to work.

Then, before the first terminal device sends the first data to the second terminal device through the first BWP, the first terminal device and the second terminal device may first switch to the first BWP. There can be different ways to implement the switching timing

In a possible implementation manner, the first terminal device may switch to the first BWP after receiving the confirmation message. Similar to the second terminal device, for example, it may switch to the second BWP after it is determined that the negotiation of the first BWP is successful.

In order to ensure that both the first terminal device and the second terminal device can switch, for example, the first terminal device may switch to the first BWP within a preset time period after receiving the confirmation message.

In another possible implementation manner, after determining that the first BWP negotiation is successful, the first terminal device may also send handover instruction information to the second terminal device, where the handover instruction information may include the identifier of the first BWP, the handover instruction information Used to indicate switching to the first BWP. Then, for example, after the second terminal device receives the switching instruction information, the first terminal device and the second terminal device switch to the first BWP.

The handover instruction information therein can be, for example, MAC CE, and the handover instruction information can also include time information, for example, where the time information is used to indicate that the first BWP is used within the duration corresponding to the time information, and the time information can be as follows At least one of: timer, start time and end time, start time and duration, duration.

When the duration of using the first BWP by the first terminal device and the second terminal device exceeds the duration corresponding to the time information, the first terminal device and the second terminal device need to renegotiate the BWP on the default BWP, for example. And in a possible implementation manner, for example, one or more BWP ID fields may be included in the handover indication information MAC CE.

The switching process described above can ensure that the first terminal device and the second terminal device can be switched to work on the negotiated first BWP, thereby effectively ensuring the validity of the determined first BWP.

To sum up, in the side link communication method provided by the embodiment of the present application, multiple BWPs are configured for the terminal device through the network device, so as to effectively meet different service requirements of the terminal device. And the first terminal device can determine the first BWP among multiple BWPs, and then negotiate with the second terminal device on the first BWP. After the negotiation is successful, the first terminal device and the second terminal device switch to the first BWP Carry out data transmission, so as to ensure that the terminal device can reasonably select one or more BWPs among multiple BWPs, and then carry out corresponding services with the peer terminal device according to actual needs, further ensuring the availability of multiple configured BWPs .

FIG. 15 is a first structural schematic diagram of a sidelink communication device provided by an embodiment of the present application. Referring to FIG. 15, the side link communication device 150 may include a receiving module 1501 and a sending module 1502, wherein,

A processing module 1501, configured for the first terminal device to determine a first BWP among multiple BWPs according to the first data and/or BWP configuration information;

A sending module 1502, configured for the first terminal device to send the first data to a second terminal device through the first BWP.

In a possible implementation manner, the BWP configuration information includes at least one of the following first information:

The priority corresponding to each BWP in the plurality of BWPs;

At least one target address corresponding to each BWP in the plurality of BWPs;

At least one quality of service QoS flow identifier corresponding to each BWP in the plurality of BWPs;

At least one geographical area identifier corresponding to each BWP in the multiple BWPs.

In a possible implementation manner, the BWP configuration information includes a priority corresponding to each BWP in the multiple BWPs;

The first BWP is a BWP with the highest priority among at least one second BWP, and the second BWP is a BWP in an available state among the multiple BWPs.

In a possible implementation manner, the BWP configuration information includes at least one target address corresponding to each BWP in the multiple BWPs;

A target address corresponding to the first data exists in at least one target address corresponding to the first BWP.

In a possible implementation manner, the BWP configuration information includes at least one QoS flow identifier corresponding to each BWP in the multiple BWPs;

The QoS flow identifier corresponding to the first data exists in at least one QoS flow identifier corresponding to the first BWP.

In a possible implementation manner, the BWP configuration information includes at least one geographical area identifier corresponding to each BWP in the multiple BWPs;

The at least one geographic area identifier corresponding to the first BWP includes the geographic area identifier of the geographic area where the first terminal device is located.

In a possible implementation manner, the BWP configuration information includes at least two kinds of the first information, and at least two kinds of the first information correspond to different priorities;

If the candidate BWP determined according to each first information in at least two kinds of the first information is the same, the first BWP is the candidate BWP;

If the candidate BWP determined according to each of the at least two kinds of first information is different, the first BWP is: determined according to the first information with the highest priority among the at least two kinds of first information The obtained candidate BWP.

In a possible implementation manner, the sending module 1502 is specifically configured to:

The first terminal device negotiates the first BWP with the second terminal device;

After successfully negotiating the first BWP, the first terminal device sends the first data to the second terminal device through the first BWP.

The first terminal device sends a first message to the second terminal device, where the first message includes the identifier of the first BWP;

receiving, by the first terminal device, a response message corresponding to the first message sent by the second terminal device;

When the response message is an acknowledgment message, it is determined that the negotiation on the first BWP is successful.

In a possible implementation manner, the response message is determined according to a negotiation result, and when the negotiation result indicates that the first BWP is available, the response message is a confirmation message;

If the second terminal device is located within the service area of the network device, the negotiation result is determined by the network device; or,

If the second terminal device is not located in the service area of the network device, the negotiation result is determined by the second terminal device.

In a possible implementation manner, the first message further includes at least one of the following information:

The identifier of the first terminal device, the service type of the first data, the QoS corresponding to the first data, and the identifier of the geographical area where the first terminal device is located.

In a possible implementation manner, the processing module 1501 is further configured to:

Before the first terminal device sends the first data to the second terminal device through the first BWP, the first terminal device switches to the first BWP.

In a possible implementation manner, the processing module 1501 is specifically configured to:

Within a preset time period after receiving the confirmation message, the first terminal device switches to the first BWP.

The first terminal device sends handover instruction information to the second terminal device, and switches to the first BWP, the handover instruction information includes an identifier of the first BWP, and the handover instruction information is used to indicate Switch to the first BWP.

In a possible implementation manner, the handover instruction information further includes time information, and the time information is used to indicate that the first BWP is used within a duration corresponding to the time information.

In a possible implementation manner, the time information is any of the following:

timer;

start time and end time;

start time and duration;

Duration.

In a possible implementation manner, the handover instruction information is MAC CE.

The side link communication device provided in the embodiment of the present application can implement the technical solution shown in the above method embodiment, and its implementation principles and beneficial effects are similar, and details are not repeated here.

FIG. 16 is a second structural schematic diagram of a sidelink communication device provided by an embodiment of the present application. Referring to FIG. 16, the side link communication device 160 may include a processing module 1601 and a sending module 1602, wherein,

The processing module 1601 is configured to negotiate a first BWP between the second terminal device and the first terminal device, where the first BWP is the first BWP that the first terminal device uses in the multiple BWPs according to the first data and/or BWP configuration information. identified in

The sending module 1602 is configured to, if the negotiation on the first BWP is successful, the second terminal device receives the first data sent by the first terminal device through the first BWP.

In a possible implementation manner, the processing module 1601 is specifically configured to:

receiving, by the second terminal device, a first message sent by the first terminal device, where the first message includes the identifier of the first BWP;

The second terminal device generates a response message corresponding to the first message, and sends the response message to the first terminal device.

An identifier of the first terminal device, a service type of the first data, a QoS corresponding to the first data, and an identifier of a geographical area where the first terminal device is located.

The second terminal device determines the negotiation result of the first BWP;

When the negotiation result indicates that the first BWP is available, the second terminal device determines that the response message is an acknowledgment message, and the acknowledgment message is used to indicate that the negotiation on the first BWP is successful.

In a possible implementation manner, the second terminal device is located in a service area of the network device; the processing module 1601 is specifically configured to:

The second terminal device sends a verification request to the network device, where the verification request includes the first message;

The second terminal device receives the negotiation result sent by the network device.

In a possible implementation manner, if the second terminal device is not in the connected state, the processing module 1601 is further configured to:

Triggering the second terminal device to enter a connection state before the second terminal device sends a verification request to the network device.

In a possible implementation manner, the second terminal device is not located in the service area of the network device; the processing module 1601 is specifically configured to:

The second terminal device determines a second BWP among the multiple BWPs according to the first message and second BWP configuration information;

If the second BWP and the first BWP are the same BWP, determine that the first BWP is available as a result of the negotiation of the first BWP.

In a possible implementation manner, the second BWP configuration information includes at least one of the following:

The priority corresponding to each BWP in the plurality of BWPs;

At least one target address corresponding to each BWP in the plurality of BWPs;

At least one QoS flow identifier corresponding to each BWP in the multiple BWPs;

In a possible implementation manner, the processing module 1601 is further configured to:

Before the second terminal device receives the first data sent by the first terminal device through the first BWP, the second terminal device switches to the first BWP.

After successfully negotiating the first BWP, the second terminal device switches to the first BWP.

receiving, by the second terminal device, handover instruction information sent by the first terminal device;

The second terminal device switches to the first BWP according to the switching instruction information.

timer;

start time and end time;

start time and duration;

Duration.

FIG. 17 is a first schematic structural diagram of a terminal device provided by an embodiment of the present application. Referring to FIG. 17 , a terminal device 170 may include: a transceiver 21 , a memory 22 , and a processor 23 . The transceiver 21 may include: a transmitter and/or a receiver. The transmitter may also be referred to as a transmitter, a transmitter, a sending port, or a sending interface, and the like, and the receiver may also be called a receiver, a receiver, a receiving port, or a receiving interface, or similar descriptions. Exemplarily, the transceiver 21 , the memory 22 , and the processor 23 are connected to each other through a bus 24 .

The memory 22 is used to store program instructions;

The processor 23 is configured to execute the program instructions stored in the memory, so as to enable the terminal device 120 to execute any one of the above-mentioned side link communication methods.

Wherein, the receiver of the transceiver 21 can be used to perform the receiving function of the terminal device in the above-mentioned side link communication method.

FIG. 18 is a second schematic structural diagram of a terminal device provided by an embodiment of the present application. Referring to FIG. 18 , the terminal device 180 may include: a transceiver 31 , a memory 32 , and a processor 33 . The transceiver 31 may include: a transmitter and/or a receiver. The transmitter may also be called a transmitter, a transmitter, a sending port, or a sending interface, and similar descriptions, and the receiver may also be called a receiver, a receiver, a receiving port, or a receiving interface, or similar descriptions. Exemplarily, the transceiver 31 , the memory 32 , and the processor 33 are connected to each other through a bus 34 .

The memory 32 is used to store program instructions;

The processor 33 is configured to execute the program instructions stored in the memory, so as to enable the terminal device 180 to execute any one of the above-mentioned side link communication methods.

Wherein, the receiver of the transceiver 31 can be used to perform the receiving function of the terminal device in the above communication method.

An embodiment of the present application provides a computer-readable storage medium, where computer-executable instructions are stored in the computer-readable storage medium, and when the computer-executable instructions are executed by a processor, they are used to implement the foregoing side link communication method.

An embodiment of the present application may further provide a computer program product, where the computer program product may be executed by a processor, and when the computer program product is executed, any one of the above-mentioned side link communication methods performed by the terminal device may be implemented.

The communication device, computer-readable storage medium, and computer program product in the embodiments of the present application can execute the side-link communication method executed by the above-mentioned terminal device. For the specific implementation process and beneficial effects, refer to the above, and details will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, device and method can 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 shown 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. The above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.

Those of ordinary skill in the art can understand that all or part of the steps for implementing the above method embodiments can be completed by program instructions and related hardware. The aforementioned computer program can be stored in a computer-readable storage medium. When the computer program is executed by the processor, it implements the steps of the above-mentioned method embodiments; and the aforementioned storage medium includes: ROM, RAM, magnetic disk or optical disk and other various media that can store program codes.

Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, rather than limiting them; although the application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: It is still possible to modify the technical solutions described in the foregoing embodiments, or perform equivalent replacements for some or all of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the technical solutions of the various embodiments of the present application. scope.

Claims

A side link communication method, characterized in that, comprising:

The first terminal device determines the first BWP among the multiple BWPs according to the first data and/or bandwidth part BWP configuration information;

The first terminal device sends the first data to the second terminal device through the first BWP.
The method according to claim 1, wherein the BWP configuration information includes at least one of the following first information:

The priority corresponding to each BWP in the plurality of BWPs;

At least one target address corresponding to each BWP in the plurality of BWPs;

At least one quality of service QoS flow identifier corresponding to each BWP in the plurality of BWPs;

At least one geographical area identifier corresponding to each BWP in the multiple BWPs.
The method according to claim 2, wherein the BWP configuration information includes the priority corresponding to each BWP in the plurality of BWPs;

The first BWP is a BWP with the highest priority among at least one second BWP, and the second BWP is a BWP in an available state among the multiple BWPs.
The method according to claim 2, wherein the BWP configuration information includes at least one target address corresponding to each BWP in the plurality of BWPs;

A target address corresponding to the first data exists in at least one target address corresponding to the first BWP.
The method according to claim 2, wherein the BWP configuration information includes at least one QoS flow identifier corresponding to each BWP in the plurality of BWPs;

The QoS flow identifier corresponding to the first data exists in at least one QoS flow identifier corresponding to the first BWP.
The method according to claim 2, wherein the BWP configuration information includes at least one geographical area identifier corresponding to each BWP in the plurality of BWPs;

The at least one geographic area identifier corresponding to the first BWP includes the geographic area identifier of the geographic area where the first terminal device is located.
The method according to any one of claims 2-6, wherein the BWP configuration information includes at least two kinds of the first information, and at least two kinds of the first information correspond to different priorities;

If the candidate BWP determined according to each first information in at least two kinds of the first information is the same, the first BWP is the candidate BWP;

If the candidate BWP determined according to each of the at least two kinds of first information is different, the first BWP is: determined according to the first information with the highest priority among the at least two kinds of first information The obtained candidate BWP.
The method according to any one of claims 1-7, wherein the first terminal device sends the first data to the second terminal device through the first BWP, comprising:

The first terminal device negotiates the first BWP with the second terminal device;

After successfully negotiating the first BWP, the first terminal device sends the first data to the second terminal device through the first BWP.
The method according to claim 8, wherein the negotiating the first BWP between the first terminal device and the second terminal device comprises:

The first terminal device sends a first message to the second terminal device, where the first message is used to indicate the first BWP;

receiving, by the first terminal device, a response message corresponding to the first message sent by the second terminal device;

When the response message is an acknowledgment message, it is determined that the negotiation on the first BWP is successful.
The method according to claim 9, wherein the response message is determined according to a negotiation result, and when the negotiation result indicates that the first BWP is available, the response message is a confirmation message;

If the second terminal device is located within the service area of the network device, the negotiation result is determined by the network device; or,

If the second terminal device is not located in the service area of the network device, the negotiation result is determined by the second terminal device.
The method according to claim 9 or 10, wherein the first message further includes at least one of the following information:

The identifier of the first terminal device, the service type of the first data, the QoS corresponding to the first data, and the identifier of the geographical area where the first terminal device is located.
The method according to any one of claims 9-11, wherein before the first terminal device sends the first data to the second terminal device through the first BWP, further comprising:

The first terminal device switches to the first BWP.
The method according to claim 12, wherein switching the first terminal device to the first BWP comprises:

Within a preset time period after receiving the confirmation message, the first terminal device switches to the first BWP.
The method according to claim 12, wherein switching the first terminal device to the first BWP comprises:

The first terminal device sends handover instruction information to the second terminal device, and switches to the first BWP, the handover instruction information includes an identifier of the first BWP, and the handover instruction information is used to indicate Switch to the first BWP.
The method according to claim 14, wherein the handover instruction information further includes time information, and the time information is used to indicate that the first BWP is used within a duration corresponding to the time information.
The method according to claim 15, wherein the time information is any of the following:

timer;

start time and end time;

start time and duration;

Duration.
The method according to any one of claims 14-16, wherein the handover indication information is a transmission medium access control layer control element (MAC CE).
A side link communication method, characterized in that, comprising:

The second terminal device negotiates a first BWP with the first terminal device, where the first BWP is determined by the first terminal device among multiple BWPs according to the first data and/or BWP configuration information;

If the first BWP is successfully negotiated, the second terminal device receives the first data sent by the first terminal device through the first BWP.
The method according to claim 18, wherein the second terminal device negotiates the first BWP with the first terminal device, comprising:

receiving, by the second terminal device, a first message sent by the first terminal device, where the first message is used to indicate the first BWP;

The second terminal device generates a response message corresponding to the first message, and sends the response message to the first terminal device.
The method according to claim 19, wherein the first message further includes at least one of the following information:

The identifier of the first terminal device, the service type of the first data, the QoS corresponding to the first data, and the identifier of the geographical area where the first terminal device is located.
The method according to claim 19 or 20, wherein the second terminal device generates a response message corresponding to the first message, comprising:

The second terminal device determines the negotiation result of the first BWP;

When the negotiation result indicates that the first BWP is available, the second terminal device determines that the response message is an acknowledgment message, and the acknowledgment message is used to indicate that the negotiation on the first BWP is successful.
The method according to claim 21, wherein the second terminal device is located in the service area of the network device; determining the negotiation result of the first BWP by the second terminal device includes:

The second terminal device sends a verification request to the network device, where the verification request includes the first message;

The second terminal device receives the negotiation result sent by the network device.
The method according to claim 22, wherein if the second terminal device is not in a connected state, before the second terminal device sends a verification request to the network device, the method further comprises:

triggering the second terminal device to enter a connection state.
The method according to claim 21, wherein the second terminal device is not located in the service area of the network device; determining the negotiation result of the first BWP by the second terminal device includes:

The second terminal device determines a second BWP among the multiple BWPs according to the first message and second BWP configuration information;

If the second BWP and the first BWP are the same BWP, determine that the first BWP is available as a result of the negotiation of the first BWP.
The method according to claim 24, wherein the second BWP configuration information includes at least one of the following:

The priority corresponding to each BWP in the plurality of BWPs;

At least one target address corresponding to each BWP in the plurality of BWPs;

At least one QoS flow identifier corresponding to each BWP in the multiple BWPs;

At least one geographical area identifier corresponding to each BWP in the multiple BWPs.
The method according to any one of claims 18-25, wherein before the second terminal device receives the first data sent by the first terminal device through the first BWP, further comprising:

The second terminal device switches to the first BWP.
The method according to claim 26, wherein switching the second terminal device to the first BWP comprises:

After successfully negotiating the first BWP, the second terminal device switches to the first BWP.
The method according to claim 26, wherein switching the second terminal device to the first BWP comprises:

receiving, by the second terminal device, handover instruction information sent by the first terminal device;

The second terminal device switches to the first BWP according to the switching instruction information.
The method according to claim 28, wherein the handover instruction information further includes time information, and the time information is used to indicate that the first BWP is used within a duration corresponding to the time information.
The method according to claim 29, wherein the time information is any of the following:

timer;

start time and end time;

start time and duration;

Duration.
The method according to any one of claims 28-30, wherein the handover indication information is MAC CE.
A side link communication device, characterized in that it comprises:

A processing module, configured for the first terminal device to determine the first BWP among the multiple BWPs according to the first data and/or BWP configuration information;

A sending module, configured for the first terminal device to send the first data to a second terminal device through the first BWP.
The device according to claim 32, wherein the BWP configuration information includes at least one of the following first information:

The priority corresponding to each BWP in the plurality of BWPs;

At least one target address corresponding to each BWP in the plurality of BWPs;

At least one quality of service QoS flow identifier corresponding to each BWP in the plurality of BWPs;

At least one geographical area identifier corresponding to each BWP in the multiple BWPs.
The device according to claim 33, wherein the BWP configuration information includes the priority corresponding to each BWP in the multiple BWPs;

The first BWP is a BWP with the highest priority among at least one second BWP, and the second BWP is a BWP in an available state among the multiple BWPs.
The device according to claim 33, wherein the BWP configuration information includes at least one target address corresponding to each BWP in the multiple BWPs;

A target address corresponding to the first data exists in at least one target address corresponding to the first BWP.
The device according to claim 33, wherein the BWP configuration information includes at least one QoS flow identifier corresponding to each BWP in the multiple BWPs;

The QoS flow identifier corresponding to the first data exists in at least one QoS flow identifier corresponding to the first BWP.
The device according to claim 33, wherein the BWP configuration information includes at least one geographical area identifier corresponding to each BWP in the multiple BWPs;

The at least one geographic area identifier corresponding to the first BWP includes the geographic area identifier of the geographic area where the first terminal device is located.
The device according to any one of claims 33-37, wherein the BWP configuration information includes at least two kinds of the first information, and at least two kinds of the first information correspond to different priorities;

If the candidate BWP determined according to each first information in at least two kinds of the first information is the same, the first BWP is the candidate BWP;

If the candidate BWP determined according to the first information in at least two kinds of first information is different, the first BWP is: determined according to the first information with the highest priority among the at least two kinds of first information The obtained candidate BWP.
The device according to any one of claims 32-38, wherein the sending module is specifically used for:

The first terminal device negotiates the first BWP with the second terminal device;

After successfully negotiating the first BWP, the first terminal device sends the first data to the second terminal device through the first BWP.
The device according to claim 39, wherein the sending module is specifically used for:

The first terminal device sends a first message to the second terminal device, where the first message is used to indicate the first BWP;

receiving, by the first terminal device, a response message corresponding to the first message sent by the second terminal device;

When the response message is an acknowledgment message, it is determined that the negotiation on the first BWP is successful.
The device according to claim 40, wherein the response message is determined according to a negotiation result, and when the negotiation result indicates that the first BWP is available, the response message is a confirmation message;

If the second terminal device is located within the service area of the network device, the negotiation result is determined by the network device; or,

If the second terminal device is not located in the service area of the network device, the negotiation result is determined by the second terminal device.
The device according to claim 40 or 41, wherein the first message further includes at least one of the following information:

The identifier of the first terminal device, the service type of the first data, the QoS corresponding to the first data, and the identifier of the geographical area where the first terminal device is located.
The device according to any one of claims 40-42, wherein the processing module is further configured to:

Before the first terminal device sends the first data to the second terminal device through the first BWP, the first terminal device switches to the first BWP.
The device according to claim 43, wherein the processing module is specifically used for:

Within a preset time period after receiving the confirmation message, the first terminal device switches to the first BWP.
The device according to claim 43, wherein the processing module is specifically used for:

The first terminal device sends handover instruction information to the second terminal device, and switches to the first BWP, the handover instruction information includes an identifier of the first BWP, and the handover instruction information is used to indicate Switch to the first BWP.
The device according to claim 45, wherein the handover instruction information further includes time information, and the time information is used to indicate that the first BWP is used within the duration corresponding to the time information.
The device according to claim 46, wherein the time information is any of the following:

timer;

start time and end time;

start time and duration;

Duration.
The device according to any one of claims 45-47, wherein the handover indication information is MAC CE.
A side link communication device, characterized in that it comprises:

A processing module, configured for the second terminal device to negotiate a first BWP with the first terminal device, wherein the first BWP is determined among multiple BWPs by the first terminal device according to the first data and/or BWP configuration information ;

A sending module, configured to, if the negotiation on the first BWP is successful, the second terminal device receives the first data sent by the first terminal device through the first BWP.
The device according to claim 49, wherein the processing module is specifically used for:

receiving, by the second terminal device, a first message sent by the first terminal device, where the first message is used to indicate the first BWP;

The second terminal device generates a response message corresponding to the first message, and sends the response message to the first terminal device.
The device according to claim 50, wherein the first message further includes at least one of the following information:

The identifier of the first terminal device, the service type of the first data, the QoS corresponding to the first data, and the identifier of the geographical area where the first terminal device is located.
The device according to claim 50 or 51, wherein the processing module is specifically used for:

The second terminal device determines the negotiation result of the first BWP;

When the negotiation result indicates that the first BWP is available, the second terminal device determines that the response message is an acknowledgment message, and the acknowledgment message is used to indicate that the negotiation on the first BWP is successful.
The device according to claim 52, wherein the second terminal device is located in the service area of the network device; the processing module is specifically used for:

The second terminal device sends a verification request to the network device, where the verification request includes the first message;

The second terminal device receives the negotiation result sent by the network device.
The device according to claim 53, wherein if the second terminal device is not in a connected state, the processing module is further configured to:

Triggering the second terminal device to enter a connection state before the second terminal device sends a verification request to the network device.
The device according to claim 52, wherein the second terminal device is not located in the service area of the network device; the processing module is specifically used for:

The second terminal device determines a second BWP among the multiple BWPs according to the first message and second BWP configuration information;

If the second BWP and the first BWP are the same BWP, determine that the first BWP is available as a result of the negotiation of the first BWP.
The device according to claim 55, wherein the second BWP configuration information includes at least one of the following:

The priority corresponding to each BWP in the plurality of BWPs;

At least one target address corresponding to each BWP in the plurality of BWPs;

At least one QoS flow identifier corresponding to each BWP in the multiple BWPs;

At least one geographical area identifier corresponding to each BWP in the multiple BWPs.
The device according to any one of claims 49-56, wherein the processing module is further configured to:

Before the second terminal device receives the first data sent by the first terminal device through the first BWP, the second terminal device switches to the first BWP.
The device according to claim 57, wherein the processing module is specifically used for:

After successfully negotiating the first BWP, the second terminal device switches to the first BWP.
The device according to claim 57, wherein the processing module is specifically used for:

receiving, by the second terminal device, handover instruction information sent by the first terminal device;

The second terminal device switches to the first BWP according to the switching instruction information.
The device according to claim 59, wherein the handover instruction information further includes time information, and the time information is used to indicate that the first BWP is used within the duration corresponding to the time information.
The device according to claim 60, wherein the time information is any of the following:

timer;

start time and end time;

start time and duration;

Duration.
The device according to any one of claims 59-61, wherein the handover instruction information is MAC CE.
A terminal device, characterized in that it includes: a transceiver, a processor, and a memory;

the memory stores computer-executable instructions;

The processor executes the computer-executed instructions stored in the memory, so that the processor executes the side-link communication method according to any one of claims 1 to 17.
A terminal device, characterized in that it includes: a transceiver, a processor, and a memory;

the memory stores computer-executable instructions;

The processor executes the computer-executed instructions stored in the memory, so that the processor executes the side-link communication method according to any one of claims 18 to 31.
A computer-readable storage medium, characterized in that computer-executable instructions are stored in the computer-readable storage medium, and when the computer-readable instructions are executed by a processor, they are used to implement claims 1 to 17 or 18 to 31 The side link communication method described in any one.
A computer program product, comprising a computer program, wherein, when the computer program is executed by a processor, the side link communication method according to any one of claims 1 to 17 or 18 to 31 is implemented.