WO2022266870A1 - Sidelink communication method, terminal device, network device and communication system - Google Patents

Abstract

The present application relates to a sidelink communication method, a terminal device, a network device and a communication system. The sidelink communication method comprises: a terminal device sending a first message to a network device, wherein the first message is used for requesting a resource for discovering a message.

Description

Side link communication method, terminal equipment, network equipment and communication system technical field

The present application relates to the communication field, and more specifically, relates to a sidelink communication method, a terminal device, a network device and a communication system.

Background technique

Side Link (SL) transmission technology adopts the technology of direct communication from terminal equipment to terminal equipment, which has higher spectral efficiency and lower transmission delay. The SL transmission process can be roughly divided into the SL discovery process and the SL data communication process. In the SL discovery process, the terminal device will detect the discovery message broadcast by other terminal devices, so as to detect other SL-supporting terminal devices within a short distance. existence, and identify the identity information of other terminal devices. During the SL data communication process, various forms of data exchange such as voice calls or multimedia information sharing can be carried out between terminal devices at close range.

For the sidelink relay, it is possible that the network side configures a resource pool dedicated to data, a resource pool shared by data and discovery messages, and/or a resource pool dedicated to discovery messages for the terminal. If there are two types of resource pools (for example, a resource pool dedicated to data or a resource pool shared by data and discovery messages; or a resource pool dedicated to discovery messages or a resource pool shared by data and discovery messages) are configured for the terminal at the same time, according to Rel-16 If it is a terminal in mode 1, it will follow the allocation instructions from the network side; if it is a terminal in mode 2, it will select a resource pool according to the behavior of the terminal, and for Rel-17 sidelink relay, the sending of data and discovery messages Should be different. For example, for a terminal in mode 2, a resource pool for discovery messages and a resource pool for data can be selected according to specific rules; and for a terminal in mode 1, it can indicate the currently requested resource to the base station.

However, currently, for the Rel-17 sidelink relay, there is no definite solution on how the mode-1 terminal indicates the currently requested resource to the base station.

Contents of the invention

Embodiments of the present application provide a sidelink communication method, a terminal device, a network device, and a communication system.

An embodiment of the present application provides a sidelink communication method, including: a terminal device sends a first message to a network device, where the first message is used to request resources for a discovery message.

An embodiment of the present application provides a sidelink communication method, including: a network device receives a first message from a terminal device, where the first message is used to request resources for a discovery message.

An embodiment of the present application provides a terminal device, including: a transceiver configured to send a first message to a network device, where the first message is used to request a resource for a discovery message.

An embodiment of the present application provides a network device, including: a transceiver configured to receive a first message from a terminal device, where the first message is used to request a resource for a discovery message.

An embodiment of the present application provides a communication device, including: a processor and a memory, the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, so that the communication device executes The sidelink communication method described above.

An embodiment of the present application provides a communication system, including:

at least one of the aforementioned terminal devices; and

At least one of the aforementioned network devices.

An embodiment of the present application provides a chip configured to implement the above sidelink communication method.

Specifically, the chip includes: a processor, configured to call and run a computer program from the memory, so that the device installed with the chip executes the above-mentioned sidelink communication method.

An embodiment of the present application provides a computer-readable storage medium for storing a computer program, and the computer program enables a computer to execute the above sidelink communication method.

An embodiment of the present application provides a computer program product, including computer program instructions, where the computer program instructions cause a computer to execute the foregoing sidelink communication method.

An embodiment of the present application provides a computer program, which, when running on a computer, causes the computer to execute the above sidelink communication method.

Description of drawings

Fig. 1 is a schematic diagram of an application scenario according to an embodiment of the present application.

Figure 2 exemplarily shows the communication of two terminals UE A and UE B via the PC5 interface.

Fig. 3 is a schematic flowchart of a sidelink transmission method according to an embodiment of the present application.

Fig. 4 is a schematic flowchart of a sidelink transmission method according to another embodiment of the present application.

Fig. 5 is a schematic flowchart of a sidelink transmission method according to another embodiment of the present application.

Fig. 6 exemplarily shows a schematic structural diagram of a terminal device according to an embodiment of the present application.

Fig. 7 exemplarily shows a schematic structural diagram of a network device according to an embodiment of the present application.

Fig. 8 exemplarily shows a schematic structural diagram of a communication device according to an embodiment of the present application.

FIG. 9 exemplarily shows a schematic structural diagram of a chip according to an embodiment of the present application.

Fig. 10 exemplarily shows a schematic structural diagram of a communication system according to an embodiment of the present application.

detailed description

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.

The technical solution of the embodiment of the present application can be applied to various communication systems, such as: Global System of Mobile communication (Global System of Mobile communication, GSM) system, code division multiple access (Code Division Multiple Access, CDMA) system, broadband code division multiple access (Wideband Code Division Multiple Access, WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced long term evolution (LTE-A) system , New Radio (NR) system, evolution system of NR system, LTE (LTE-based access to unlicensed spectrum, LTE-U) system on unlicensed spectrum, NR (NR-based access to unlicensed spectrum) on unlicensed spectrum unlicensed spectrum, NR-U) system, non-terrestrial communication network system, Universal Mobile Telecommunications System (Universal Mobile Telecommunication System, UMTS), Wireless Local Area Networks (Wireless Local Area Networks, WLAN), Wireless Fidelity (Wireless Fidelity, WiFi), the 5th generation communication (5th-Generation, 5G) system or other communication systems, etc.

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

Optionally, the communication system in the embodiment of the present application may be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, may also be applied to a dual connectivity (Dual Connectivity, DC) scenario, and may also be applied to an independent (Standalone, SA) deployment Web scene.

Optionally, the communication system in the embodiment of the present application may be applied to an unlicensed spectrum, where the unlicensed spectrum may also be considered as a shared spectrum; or, the communication system in the embodiment of the present application may also be applied to a licensed spectrum, where, Licensed spectrum can also be considered as non-shared spectrum.

The embodiments of the present application describe various embodiments in conjunction with network equipment and terminal equipment, wherein the terminal equipment may also be referred to as user equipment (User Equipment, UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.

The terminal device can be a station (STAION, ST) in the WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital processing (Personal Digital Assistant, PDA) devices, handheld devices with wireless communication functions, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, next-generation communication systems such as terminal devices in NR networks, or future Terminal equipment in the evolved public land mobile network (Public Land Mobile Network, PLMN) network, etc.

In the embodiment of this application, the terminal device can be deployed on land, including indoor or outdoor, handheld, wearable or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air (such as aircraft, balloons and satellites) superior).

In this embodiment of the application, the terminal device may be a mobile phone (Mobile Phone), a tablet computer (Pad), a computer with a wireless transceiver function, a virtual reality (Virtual Reality, VR) terminal device, an augmented reality (Augmented Reality, AR) terminal Equipment, wireless terminal equipment in industrial control, wireless terminal equipment in self driving, wireless terminal equipment in remote medical, wireless terminal equipment in smart grid , wireless terminal equipment in transportation safety, wireless terminal equipment in smart city, or wireless terminal equipment in smart home.

As an example but not a limitation, in this embodiment of the present application, the terminal device may also be a wearable device. Wearable devices can also be called wearable smart devices, which is a general term for the application of wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not only a hardware device, but also achieve powerful functions through software support, data interaction, and cloud interaction. Generalized wearable smart devices include full-featured, large-sized, complete or partial functions without relying on smart phones, such as smart watches or smart glasses, etc., and only focus on a certain type of application functions, and need to cooperate with other devices such as smart phones Use, such as various smart bracelets and smart jewelry for physical sign monitoring.

In the embodiment of the present application, the network device may be a device for communicating with the mobile device, and the network device may be an access point (Access Point, AP) in WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA , or a base station (NodeB, NB) in WCDMA, or an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and an NR network The network equipment (gNB) in the network or the network equipment in the future evolved PLMN network or the network equipment in the NTN network, etc.

As an example but not a limitation, in this embodiment of the present application, the network device may have a mobile feature, for example, the network device may be a mobile device. Optionally, the network equipment may be a satellite or a balloon station. For example, the satellite can be a low earth orbit (low earth orbit, LEO) satellite, a medium earth orbit (medium earth orbit, MEO) satellite, a geosynchronous earth orbit (geosynchronous earth orbit, GEO) satellite, a high elliptical orbit (High Elliptical Orbit, HEO) satellite. ) Satellite etc. Optionally, the network device may also be a base station installed on land, water, and other locations.

In this embodiment of the present application, the network device may provide services for a cell, and the terminal device communicates with the network device through the transmission resources (for example, frequency domain resources, or spectrum resources) used by the cell, and the cell may be a network device ( For example, a cell corresponding to a base station), the cell may belong to a macro base station, or may belong to a base station corresponding to a small cell (Small cell), and the small cell here may include: a metro cell (Metro cell), a micro cell (Micro cell), a pico cell ( Pico cell), Femto cell, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

FIG. 1 exemplarily shows a communication system 100 . The communication system includes a network device 110 and two terminal devices 120 . Optionally, the communication system 100 may include multiple network devices 110, and the coverage of each network device 110 may include other numbers of terminal devices 120, which is not limited in this embodiment of the present application.

Optionally, the communication system 100 may also include other network entities such as a mobility management entity (Mobility Management Entity, MME), an access and mobility management function (Access and Mobility Management Function, AMF), etc. Not limited.

Wherein, the network equipment may further include access network equipment and core network equipment. That is, the wireless communication system also includes multiple core networks for communicating with access network devices. The access network device may be a long-term evolution (long-term evolution, LTE) system, a next-generation (mobile communication system) (next radio, NR) system or an authorized auxiliary access long-term evolution (LAA- Evolved base station (evolutional node B, abbreviated as eNB or e-NodeB) macro base station, micro base station (also called "small base station"), pico base station, access point (access point, AP), Transmission point (transmission point, TP) or new generation base station (new generation Node B, gNodeB), etc.

It should be understood that a device with a communication function in the network/system in the embodiment of the present application may be referred to as a communication device. Taking the communication system shown in Figure 1 as an example, the communication equipment may include network equipment and terminal equipment with communication functions. It may include other devices in the communication system, such as network controllers, mobility management entities and other network entities, which are not limited in this embodiment of the present application.

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

It should be understood that the "indication" mentioned in the embodiments of the present application may be a direct indication, may also be an indirect indication, and may also mean that there is an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also indicate that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also indicate that there is an association between A and B relation.

In the description of the embodiments of the present application, the term "corresponding" may indicate that there is a direct or indirect correspondence between the two, or that there is an association between the two, or that it indicates and is indicated, configuration and is configuration etc.

In order to facilitate the understanding of the technical solutions of the embodiments of the present application, the related technologies of the embodiments of the present application are described below. The following related technologies can be combined with the technical solutions of the embodiments of the present application as optional solutions, and all of them belong to the embodiments of the present application. protected range.

In the Rel-13 Long Term Evolution (LTE) period, sidelink discovery is defined as the use of evolved universal terrestrial radio access network (evolved universal terrestrial radio access network, E- UTRA) communicates directly via the PC5 to discover other UEs in its vicinity. Sidelink discovery is supported both when the UE is served by E-UTRA and when the UE is out of E-UTRA coverage. Only UEs that support Proximity based Service (Prose) public safety can perform sidelink discovery when they are out of E-UTRA coverage. For public safety sidelink discovery, an allowed frequency is pre-configured in the UE and used even if the UE is outside the coverage of E-UTRA in that frequency. The pre-configured frequency is the same as that of the public safety carrier.

Upper layers handle notification and authorization of monitoring discovery messages.

The content of the discovery message is transparent to the Access Stratum (AS), and the AS does not distinguish between the sidelink discovery model and the sidelink discovery type. However, higher levels will inform the sidelink discovery broadcast whether it involves public safety or non-public safety discovery. Higher layers also inform whether discovery announcements/monitoring are related to network relay discovery or other public safety findings.

The UE can participate in the Uu interface (the interface between the terminal and the access network is still referred to as the Uu interface in the 5G system, also known as the air interface) according to the configuration of the gNB, and connect with RRC (Radio Resource Control, radio resource control) in the idle state Broadcasting and monitoring of discovery messages in the state. Among them, the UE can broadcast and listen to the discovery message under the half-duplex restriction.

The UE participating in the broadcasting and monitoring of the discovery message can maintain the current UTC (Universal Time Coordinated, Coordinated World Time) time. The UE participating in the broadcast transmits the discovery message, the discovery message may be generated by the Prose (Proximity based Service, proximity service) protocol, while taking into account the UTC time when the discovery message is transmitted. In the listening UE, the Prose protocol (see Figure 2) provides a message, which is verified together with the received UTC time provided by the Prose Function (Prose functional entity).

To perform synchronization, UEs participating in the discovery message broadcast may send a Sidelink Broadcast Control Channel (SBCCH) through resource information based on a synchronization signal provided in a System Information Block (SIB) 19 ) and sync signal to act as a sync source.

There are three range classes. The upper layer authorization provides the applicability level of the UE. The maximum transmission power allowed for each range class is given in SIB19. The UE uses the applicable maximum allowed transmit power corresponding to its authorization range class. This places an upper limit on the transmit power determined based on the open loop power control parameters.

As mentioned above, for the Rel-17 sidelink relay currently, there is no definite solution on how the terminal in mode 1 indicates the currently requested resource to the base station.

This application provides a corresponding solution.

Fig. 3 is a schematic flowchart of a sidelink communication method according to an embodiment of the present application. The method can optionally be applied to terminal devices and network devices in the communication system shown in FIG. 1 , but is not limited thereto. The method includes at least some of the following.

S210. The terminal device sends a first message to the network device, where the first message is used to request resources for discovering messages.

In this embodiment, the currently requested resource is indicated to the network device by sending the first message for requesting resources for the discovery message to the network device.

Optionally, the first message may include at least one of the following:

Buffer Status Report (Buffer Status Report, BSR);

Resource Scheduling Request (Scheduling Request, SR); and

Sidelink UEInformation.

The first message of the present application may include at least one of the above-mentioned BSR, SR, and sidelink terminal information (sidelinkUEInformation), to indicate the currently requested resource to the network device. Please note that the content included in the first message for indicating the currently requested resource to the network device is not limited to the above example, but other ways may also be used to indicate the currently requested resource to the network device.

In addition, optionally, in addition to the content used to indicate the currently requested resource to the network device, the first message may also include other content.

Optionally, the resource request includes a request for a resource pool and/or a request for a resource type. That is to say, when the terminal device requests resources from the network device, it may indicate the resource pool to be requested and/or the resource type to be requested, so that the network device can specify the resource requested by the terminal device and configure and/or allocate it.

Optionally, the resource pool and/or resource type are indicated explicitly or implicitly through the first message. That is, the manner of indicating the requested resource can be explicit or implicit. In a word, in this application, as long as the network device can determine the resource pool and/or resource type requested by the terminal device based on the resource request of the terminal device, there is no need to specifically limit the indication manner of the resource request.

Regarding resource pools, in this application, the network device may configure a resource pool shared by data and discovery messages, a resource pool dedicated to discovery messages, and a resource pool dedicated to data for the terminal device.

If the network device configures its dedicated resource pool for data or discovery messages, it is relatively simple, and if the network device configures two types of resource pools for data or discovery messages, that is, shared resource pools and dedicated resource pools, you need to further determine Which resource pool to use.

For example, multiple available resource pools may be configured for the terminal device, and all of the multiple available resource pools can be used to send discovery messages. When a terminal device wishes to initiate SL communication, or a terminal device wishes to access a network device through another terminal device, the terminal device may determine a target resource pool from the multiple available resource pools to send a discovery message.

In this application, as long as a target resource pool can be determined from multiple available resource pools, no limitation is imposed on its specific implementation manner.

Optionally, the first message includes a first buffer status reporting BSR, and the first BSR is used to request resources for the discovery message, whereby the terminal device indicates the requested resource for the discovery message through the first BSR. Resource pool information for the resource where the message was discovered.

Optionally, the first BSR includes a resource pool ID, and the resource pool ID is used to indicate the requested resource pool information of the resource used for the discovery message.

Optionally, by carrying the resource pool ID in the first BSR, the terminal device indicates in the first BSR the requested resource pool information of resources used for the discovery message.

In this application, when a terminal device needs to request resources, it can indicate the required resources to the network device through the first BSR. Specifically, for example, the terminal device can carry a resource pool ID in the first BSR (which can be through, for example, resource The pool ID field carries the resource pool ID) to explicitly indicate the resource pool information of the resource to be requested by the terminal device.

An example manner is given above in which the first BSR indicates the resource pool information of the resource used for the discovery message requested. It should be noted that the present application is not limited to this example manner.

According to this embodiment of the present application, optionally, the first message may include a second buffer status report BSR, and the second BSR is used to indicate the resource type of the resource requested for the discovery message.

That is to say, in this application, another BSR can be used to indicate the type of resource requested.

Optionally, through the resource type field carried by the second BSR, the terminal device indicates the requested resource type of the resource used for the discovery message through the second BSR.

Optionally, the first message includes a second buffer status reporting BSR, and the second BSR is used to indicate the resource type of the resource requested for the discovery message.

In this application, when a terminal device needs to request resources, it can indicate to the network device through the second BSR. Specifically, for example, the terminal device can carry a resource type field through the second BSR, and the resource type field can indicate the resource type field of the terminal device. Whether a data sending resource or a discovery message sending resource is being requested.

An example manner is given above in which the second BSR indicates the resource type of the resource used for the discovery message requested. It should be noted that the present application is not limited to this example manner.

According to this embodiment of the present application, optionally, the first message may include a third cache status reporting BSR, and the terminal device may indicate the requested user address through a destination index included in the third BSR. The resource pool information of the resources used in the discovery message.

Optionally, the first message includes a third buffer status reporting BSR, and the third BSR includes a target address index, where the target address index is used to indicate resource pool information of resources requested for the discovery message.

The manner of indicating the resource pool information of the resource to be requested by using the target address index is an implicit indication.

Optionally, the target address index may be obtained by serializing the resource pool ID and the target address ID.

Optionally, the target address index obtained by serializing the resource pool ID and the target address ID may have a specific number of bits. For example, the target address index may have a number of 5 bits. Of course, the number of digits of the target address index can also be other values.

As mentioned above, when the terminal needs to request resources, it can indicate to the network device through the BSR. Specifically, the terminal device may report the target address index obtained by serializing the resource pool ID and the target address ID to implicitly indicate the resource pool information of the resource to be requested.

An example of a serialization rule is given below:

Destination index 1 => {resource pool ID1, destination IDA}

Destination index 2 => {resource pool ID1, destination IDB}

Destination index 3 => {resource pool ID2, destination IDA}

Destination index 4 => {resource pool ID2, destination IDB}

As mentioned above, the target address index 1, that is, Destination index 1, can be serialized by the resource pool ID1, that is, resource pool ID1, and the target address IDA, that is, destination IDA. Similarly, the target address index 2, that is, Destination index 2, can be serialized from the resource pool ID1, that is, resource pool ID1, and the target address IDB, that is, destination IDB. Destination index 3, namely Destination index 3, can be serialized by resource pool ID2, namely resource pool ID2, and destination address IDA, namely destination IDA. Destination index 4, namely Destination index 4, can be serialized by resource pool ID2, namely resource pool ID2, and target address IDB, namely destination IDB.

The above gives an example form for serializing the resource pool ID and target address ID to obtain the target address index. It should be pointed out that this application is not limited to this example form, but other ways can also be used for serialization .

Optionally, the first message may include a fourth buffer status report BSR, and the terminal device indicates the requested resource for the resource discovery message through the logical channel group ID contained in the fourth BSR, that is, LCGID Types of.

Optionally, the first message includes a fourth buffer status report BSR, and the fourth BSR includes a logical channel group ID, ie, LCGID, where the LCGID is used to indicate the resource type of the resource requested for the discovery message .

Optionally, in response to receiving the fourth BSR including the LCGID, the network device determines the resource type of the resource used for the discovery message requested by the terminal device based on the following pre-configured mapping relationship: (SL-SRB (Signalling Radio The mapping relationship between Bearer, signaling bearer)/DRB (Data radio Bearer, data bearer) or data packet priority) and (LCGID or logical channel).

That is to say, the resource type of the requested resource can be indicated through the mapping relationship by only specifying the LCGID when reporting by the terminal device. This is also a way of implicit indication.

More specifically, optionally, based on the pre-configured mapping relationship between (SL-SRB/DRB or data packet priority) and (LCGID or logical channel), the network device determines the terminal device through the LCGID reported by the terminal device The requested resource type.

Regarding the mapping relationship between (SL-SRB/DRB or data packet priority) and (LCGID or logical channel), for example, it may include the mapping relationship between SL-SRB/DRB and LCGID, SL-SRB/DRB and logical channel Mapping relationship between channels, mapping relationship between data packet priority and LCGID, mapping relationship between data packet priority and logical channel.

Optionally, the terminal device may request resources for the discovery message from the network device through the resource scheduling request SR included in the first message. That is to say, the requested resource can also be indicated by SR.

Optionally, the first message includes a resource scheduling request SR, where the SR is used to request resources to be used for the discovery message.

Optionally, the resource scheduling request SR is sent on a resource corresponding to a scheduling request ID configured by the network device for the terminal device and dedicated to the terminal device requesting to send a discovery message, that is, SchedulingRequestID. In other words, the network device configures the resource corresponding to the scheduling request ID for the terminal device, so that the scheduling request ID is sent on the corresponding resource.

That is to say, the network device configures the terminal device with a schedulingrequestID dedicated to requesting to send the discovery message, so that when the terminal device requests a transmission resource dedicated to the discovery message, the resource scheduling can be sent on the transmission resource corresponding to the schedulingrequestID Request an SR.

Optionally, through the sidelink UEInformation included in the first message, the terminal device may request resources for the discovery message from the network device.

Optionally, the sidelink UEInformation indicates a target address ID corresponding to the requested resource and a requested resource type corresponding to the target address ID.

Optionally, the first message includes sidelink terminal information, and the sidelink terminal information is used to request resources for discovery messages

When the terminal device reports the sidelinkUEInformation, corresponding to different target address IDs, the terminal device indicates the resource type to be requested, specifically, the resource type is a discovery message sending resource or a data sending resource. That is to say, for the sidelink UEInformation here, in addition to indicating the target address ID, it also needs to indicate the requested resource type corresponding to the target address ID. There may be one or more target address IDs indicated therein, and this application does not impose any limitation on this.

A specific example form will be given as follows:

An example form is given above, and it should be pointed out that the present application is not limited to this example form, but other forms may also be used.

As shown in FIG. 4, the sidelink communication method according to the embodiment of the present application may further include the following step S201:

S220. In response to receiving the first message, the network device allocates the requested resource for the terminal device.

In this step, the network device allocates the requested resource to the network device according to the received first message, specifically, according to the indication of the requested resource in the received first message.

Optionally, corresponding resources are allocated to the network device according to the indication of the requested resource type and/or resource pool information in the first message.

In this application, the way network equipment allocates resources for terminal equipment can be dynamic, for example, according to each request; it can also be semi-static, for example, sideline license-free transmission resources are allocated according to the request, so that no The transmission resources are re-requested. Therefore, such an allocation method can reduce the delay of side transmission and improve the response speed.

Optionally, in response to receiving the first message, the network device configures, for the terminal device, a sidelink authorization-free transmission resource CG for discovering messages and/or data.

Examples are given below:

Optionally, the network device may indicate whether the sideline license-free transmission resource CG is available for sending the discovery message by setting at least one of the following:

Boolean type indication; and

A field for indicating a CG type, wherein the CG type indicates whether the corresponding CG is used to send a discovery message or to send data.

The example form of indicating whether the sideline license-free transmission resource CG can be used to send the discovery message is given above. It should be noted that the present application is not limited to the above example form.

Optionally, as shown in FIG. 5, the sidelink communication method according to the embodiment of the present application may further include the following step S231:

S231. In response to sending a discovery message, the terminal device selects a CG that can be used to send the discovery message from the lateral license-free transmission resources CG configured by the network device.

That is to say, the CG that can be used to send the discovery message can be selected according to the type of the CG.

Therefore, through the foregoing exemplary embodiments of the present application, the resources requested by the terminal device can be clearly indicated, and the network device can accurately allocate corresponding resources to the terminal device based on the request of the terminal device.

Fig. 6 shows a schematic block diagram of a terminal device according to an embodiment of the present application.

As shown in FIG. 6 , a terminal device 400 according to the embodiment of the present application may include, for example, a transceiver 410 .

Wherein, the above-mentioned transceiver 410 may be configured to send a first message to a network device, where the first message is used to request resources for a discovery message.

Optionally, the first message includes at least one of the following:

The cache status is reported to the BSR;

Resource Scheduling Request SR; and

Sidelink UEInformation sidelink UEInformation.

Optionally, the request includes a request for a resource pool and/or a request for a resource type.

Optionally, the resource pool and/or resource type are indicated explicitly or implicitly through the first message.

Optionally, the first message includes a first buffer status report BSR, and the terminal device indicates the requested resource pool information of resources used for the discovery message through the first BSR.

Optionally, by carrying the resource pool ID in the first BSR, the terminal device indicates in the first BSR the requested resource pool information of resources used for the discovery message.

Optionally, the first message includes a second buffer status report BSR, and the terminal device indicates the requested resource type of the resource used for the discovery message through the second BSR.

Optionally, through the resource type field carried by the second BSR, the terminal device indicates the requested resource type of the resource used for the discovery message through the second BSR.

Optionally, the first message includes a third buffer status report BSR, and the terminal device indicates the requested resource pool information of resources used for the discovery message through the target address index included in the third BSR.

Optionally, the target address index is obtained by serializing the resource pool ID and the target address ID.

Optionally, the target address index obtained by serializing the resource pool ID and the target address ID has a specific number of bits.

Optionally, the first message includes a fourth buffer status report BSR, and the terminal device indicates the requested resource type of the resource used for the discovery message through the logical channel group ID contained in the fourth BSR, that is, LCGID .

Optionally, in response to receiving the fourth BSR containing the LCGID, the network device determines the resource type of the resource used for the discovery message requested by the terminal device based on the following pre-configured mapping relationship: (SL-SRB/DRB or The mapping relationship between data packet priority) and (LCGID or logical channel).

Optionally, through the resource scheduling request SR included in the first message, the terminal device requests the network device for resources used for the discovery message.

Optionally, the resource scheduling request SR is sent on a resource corresponding to a scheduling request ID configured by the network device for the terminal device and dedicated to the terminal device requesting to send a discovery message, that is, SchedulingRequestID.

Optionally, through the sidelink UEInformation included in the first message, the terminal device requests resources for the discovery message from the network device.

Optionally, the sidelink UEInformation indicates a target address ID corresponding to the requested resource and a requested resource type corresponding to the target address ID.

Optionally, in response to receiving the first message, the network device allocates the requested resource to the terminal device.

Optionally, in response to receiving the first message, the network device configures, for the terminal device, a sidelink authorization-free transmission resource CG for discovering messages and/or data.

Optionally, the network device indicates whether the sideline authorization-free transmission resource CG can be used to send the discovery message by setting at least one of the following:

Boolean type indication; and

A field for indicating a CG type, wherein the CG type indicates whether the corresponding CG is used to send a discovery message or to send data.

Optionally, the terminal device may also include:

The processor 420 is configured to, in response to sending a discovery message, select a CG that can be used to send the discovery message from the sideward license-free transmission resources CG configured by the network device.

Optionally, the transceiver 410 is configured to send a first message to the network device, where the first message is used to request resources for the discovery message.

Optionally, the first message includes at least one of the following:

The cache status is reported to the BSR;

Resource Scheduling Request SR; and

Sidelink terminal information.

Optionally, the resource pool and/or resource type are indicated explicitly or implicitly through the first message.

Optionally, the first message includes a first buffer status report BSR, and the first BSR is used to indicate resource pool information of resources requested for the discovery message.

Optionally, the first BSR includes a resource pool ID, where the resource pool ID is used to indicate the requested resource pool information of the resource used for the discovery message.

Optionally, the first message includes a second buffer status reporting BSR, and the second BSR is used to indicate the resource type of the resource requested for the discovery message.

Optionally, the second BSR includes a resource type field, and the resource type field is used to indicate the requested resource type of the resource used for the discovery message.

Optionally, the first message includes a third buffer status reporting BSR, and the third BSR includes a target address index, where the target address index is used to indicate resource pool information of resources requested for the discovery message.

Optionally, the target address index is obtained by serializing the resource pool ID and the target address ID.

Optionally, the target address index obtained by serializing the resource pool ID and the target address ID has a specific number of bits.

Optionally, the first message includes a fourth buffer status report BSR, and the fourth BSR includes a logical channel group ID, ie, LCGID, where the LCGID is used to indicate the resource type of the resource requested for the discovery message .

Optionally, in response to receiving the fourth BSR including the LCGID, the network device determines the resource type of the resource used for the discovery message requested by the terminal device based on at least one of the following pre-configured mapping relationships:

Sidelink signaling bearer/data bearer, that is, the mapping relationship between SL-SRB/DRB and logical channel group ID, that is, LCGID;

The mapping relationship between SL-SRB/DRB and logical channels;

The mapping relationship between packet priority and LCGID; and

Mapping relationship between data packet priority and logical channel.

Optionally, the first message includes a resource scheduling request SR, where the SR is used to request resources for the discovery message.

Optionally, the SR is sent on a resource corresponding to a scheduling request ID configured by the network device for the terminal device and dedicated to the terminal device requesting to send a discovery message, that is, SchedulingRequestID.

Optionally, the first message includes sidelink terminal information, and the sidelink terminal information is used to request resources for the discovery message.

Optionally, the sidelink terminal information indicates a target address ID corresponding to the requested resource and a requested resource type corresponding to the target address ID.

Optionally, in response to receiving the first message, the network device allocates the requested resource to the terminal device.

Optionally, in response to receiving the first message, the network device configures, for the terminal device, a sidelink authorization-free transmission resource CG for discovering messages and/or data.

Optionally, the network device indicates whether the sideline authorization-free transmission resource CG can be used to send the discovery message by setting at least one of the following:

Boolean type indication; and

A field for indicating a CG type, wherein the CG type indicates whether the corresponding CG is used to send a discovery message or to send data.

Optionally, the terminal device also includes:

The processor 420 is configured to, in response to sending a discovery message, select a CG that can be used to send the discovery message from the sideward license-free transmission resources CG configured by the network device.

Optionally, the above-mentioned processor 420 may also be configured to perform processing operations performed by the terminal device in the above-mentioned information indication method, such as determining, obtaining, reading, saving and other operations, but is not limited thereto.

In addition, the terminal device may further include a memory and the like.

For the sake of brevity, details of its operation will not be repeated here.

Fig. 7 shows a schematic block diagram of a network device according to an embodiment of the present application.

As shown in FIG. 7 , a network device 600 according to the embodiment of the present application may include, for example: a transceiver 610 .

Wherein, the above-mentioned transceiver 610 may be configured to receive a first message from a terminal device, where the first message is used to request resources for a discovery message.

Optionally, the network device 600 may also include:

The processor 620 is configured to, in response to receiving the fourth BSR containing the LCGID, determine the resource type of the resource used for the discovery message requested by the terminal device based on the following pre-configured mapping relationship: (SL-SRB/DRB or data packet priority) and (LCGID or logical channel) mapping relationship.

Optionally, the processor 620 may be further configured to allocate the requested resource to the terminal device in response to receiving the first message.

Optionally, the processor 620 may be further configured to, in response to receiving the first message, configure a sidelink license-free transmission resource CG for the terminal device to discover messages and/or data.

Optionally, the processor may indicate whether the sideline license-free transmission resource CG is available for sending the discovery message by setting at least one of the following:

Boolean type indication; and

A field for indicating a CG type, wherein the CG type indicates whether the corresponding CG is used to send a discovery message or to send data.

Optionally, the transceiver 610 may be configured to receive a first message from the terminal device, the first message is used to request resources for the discovery message

Optionally, the first message includes at least one of the following:

The cache status is reported to the BSR;

Resource Scheduling Request SR; and

Sidelink terminal information.

Optionally, the request includes a request for a resource pool and/or a request for a resource type.

Optionally, the resource pool and/or resource type are indicated explicitly or implicitly through the first message.

Optionally, the first message includes a first buffer status report BSR, and the first BSR is used to indicate resource pool information of resources requested for the discovery message.

Optionally, the first BSR includes a resource pool ID, where the resource pool ID is used to indicate the requested resource pool information of the resource used for the discovery message.

Optionally, the first message includes a second buffer status reporting BSR, and the second BSR is used to indicate the resource type of the resource requested for the discovery message.

Optionally, the second BSR includes a resource type field, and the resource type field is used to indicate the requested resource type of the resource used for the discovery message.

Optionally, the first message includes a third cache status reporting BSR, and the third BSR includes a target address index, where the target address index is used to indicate resource pool information of resources requested for the discovery message.

Optionally, the target address index is obtained by serializing the resource pool ID and the target address ID.

Optionally, the target address index obtained by serializing the resource pool ID and the target address ID has a specific number of bits.

Optionally, the first message includes a fourth buffer status report BSR, and the fourth BSR includes a logical channel group ID, ie, LCGID, where the LCGID is used to indicate the resource type of the resource requested for the discovery message .

Optionally, the processor 620 is configured to, in response to receiving the fourth BSR including the LCGID, determine the resource type of the resource used for the discovery message requested by the terminal device based on at least one of the following pre-configured mapping relationships :

Sidelink signaling bearer/data bearer, that is, the mapping relationship between SL-SRB/DRB and logical channel group ID, that is, LCGID;

The mapping relationship between SL-SRB/DRB and logical channels;

The mapping relationship between packet priority and LCGID; and

Mapping relationship between data packet priority and logical channel.

Optionally, the first message includes a resource scheduling request SR, where the SR is used to request resources for the discovery message.

Optionally, the SR is sent on a resource corresponding to a scheduling request ID configured by the network device for the terminal device and dedicated to the terminal device requesting to send a discovery message, that is, SchedulingRequestID.

Optionally, the first message includes sidelink terminal information, and the sidelink terminal information is used to request resources for the discovery message.

Optionally, the sidelink terminal information indicates a target address ID corresponding to the requested resource and a requested resource type corresponding to the target address ID.

Optionally, the processor is further configured to allocate the requested resource to the terminal device in response to receiving the first message.

Optionally, the processor is further configured to, in response to receiving the first message, configure a sidelink license-free transmission resource CG for discovery messages and/or data for the terminal device.

Optionally, the processor indicates whether the sideline license-free transmission resource CG can be used to send the discovery message by setting at least one of the following:

Boolean type indication; and

A field for indicating a CG type, wherein the CG type indicates whether the corresponding CG is used to send a discovery message or to send data.

Optionally, in response to sending a discovery message, the terminal device selects a CG that can be used to send the discovery message from the lateral unlicensed transmission resources CG configured by the network device.

Optionally, the processor 620 may be configured to perform processing operations performed by the network device in the above information indication method, such as determining, obtaining, reading, saving and other operations, but is not limited thereto.

In addition, the network device may further include a memory and the like.

For the sake of brevity, details of its operation will not be repeated here.

Fig. 8 is a schematic structural diagram of a communication device 1900 according to an embodiment of the present application. The communication device 1900 shown in FIG. 8 includes a processor 1910, and the processor 1910 can invoke and run a computer program from a memory, so as to implement the method in the embodiment of the present application.

Optionally, as shown in FIG. 8 , the communication device 1900 may further include a memory 1920 . Wherein, the processor 1910 can invoke and run a computer program from the memory 1920, so as to implement the method in the embodiment of the present application.

Wherein, the memory 1920 may be an independent device independent of the processor 1910 , or may be integrated in the processor 1910 .

Optionally, as shown in FIG. 8, the communication device 1900 may further include a transceiver 1930, and the processor 1910 may control the transceiver 1930 to communicate with other devices, specifically, to send information or data to other devices, or receive other Information or data sent by the device.

Wherein, the transceiver 1930 may include a transmitter and a receiver. The transceiver 1930 may further include antennas, and the number of antennas may be one or more.

Optionally, the communication device 1900 may be the terminal device of the embodiment of the present application, and the communication device 1900 may implement the corresponding processes implemented by the terminal device in the methods of the embodiment of the present application. For the sake of brevity, details are not repeated here.

Optionally, the communication device 1900 may be the network device of the embodiment of the present application, and the communication device 1900 may implement the corresponding process implemented by the network device in each method of the embodiment of the present application. For the sake of brevity, details are not repeated here.

FIG. 9 is a schematic structural diagram of a chip 2000 according to an embodiment of the present application. The chip 2000 shown in FIG. 9 includes a processor 2010, and the processor 2010 can call and run a computer program from a memory, so as to implement the method in the embodiment of the present application.

Optionally, as shown in FIG. 9 , the chip 2000 may further include a memory 2020 . Wherein, the processor 2010 can invoke and run a computer program from the memory 2020, so as to implement the method in the embodiment of the present application.

Wherein, the memory 2020 may be a separate device independent of the processor 2010 , or may be integrated in the processor 2010 .

Optionally, the chip 2000 may also include an input interface 2030 . Wherein, the processor 2010 can control the input interface 2030 to communicate with other devices or chips, specifically, can obtain information or data sent by other devices or chips.

Optionally, the chip 2000 may also include an output interface 2040 . Wherein, the processor 2010 can control the output interface 2040 to communicate with other devices or chips, specifically, can output information or data to other devices or chips.

Optionally, the chip can be applied to the terminal device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the terminal device in the methods of the embodiments of the present application. For the sake of brevity, details are not repeated here.

Optionally, the chip can be applied to the network device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the network device in the methods of the embodiment of the present application. For the sake of brevity, details are not repeated here.

It should be understood that the chip mentioned in the embodiment of the present application may also be called a system-on-chip, a system-on-chip, a system-on-a-chip, or a system-on-a-chip.

Fig. 10 is a schematic block diagram of a communication system 1000 according to an embodiment of the present application. As shown in FIG. 10 , the communication system 1000 may include a terminal device 1010, a network device 1080, and the like.

Wherein, the above-mentioned terminal device 1010 may be used to realize corresponding functions realized by the terminal device in the above-mentioned method, or may be the above-mentioned terminal device 400 or the communication device 1900 as a terminal device. Wherein, the network device 1080 may be used to implement the corresponding functions implemented by the network device in the foregoing method, or may be the foregoing network device 600 or the communication device 1900 as a network device. For the sake of brevity, details are not repeated here.

The processor mentioned above can be a general-purpose processor, a digital signal processor (DSP), an off-the-shelf programmable gate array (FPGA), an application specific integrated circuit (ASIC) or Other programmable logic devices, transistor logic devices, discrete hardware components, etc. Wherein, the general-purpose processor mentioned above may be a microprocessor or any conventional processor or the like.

The aforementioned memories may be volatile memories or nonvolatile memories, or may include both volatile and nonvolatile memories. Among them, the non-volatile memory can be read-only memory (read-only memory, ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically programmable Erases programmable read-only memory (electrically EPROM, EEPROM) or flash memory. The volatile memory may be random access memory (RAM).

It should be understood that the above-mentioned memory is illustrative but not restrictive. For example, the memory in the embodiment of the present application may also be a static random access memory (static RAM, SRAM), a dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is, the memory in the embodiments of the present application is intended to include, but not be limited to, these and any other suitable types of memory.

In the above embodiments, all or part of them may be implemented by software, hardware, firmware or any combination thereof. When implemented using software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present application will be generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transferred from a website, computer, server, or data center by wire (such as coaxial cable, optical fiber, digital subscriber line (Digital Subscriber Line, DSL)) or wireless (such as infrared, wireless, microwave, etc.) to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, a data center, etc. integrated with one or more available media. The available medium may be a magnetic medium (such as a floppy disk, a hard disk, or a magnetic tape), an optical medium (such as a DVD), or a semiconductor medium (such as a solid state disk (Solid State Disk, SSD)), etc.

It should be understood that, in various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the order of execution, and the execution order of the processes should be determined by their functions and internal logic, and should not be used in the embodiments of the present application. The implementation process constitutes any limitation. Those skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the above-described system, device and unit can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

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

Claims (90)

A sidelink communication method comprising: The terminal device sends a first message to the network device, where the first message is used to request resources for discovery messages. The method according to claim 1, wherein the first message includes at least one of the following: The cache status is reported to the BSR; Resource Scheduling Request SR; and Sidelink terminal information. The method according to claim 1 or 2, wherein the request includes a request for a resource pool and/or a request for a resource type. The method according to any one of claims 1-3, wherein resource pools and/or resource types are indicated explicitly or implicitly through the first message. The method according to any one of claims 1-4, wherein the first message includes a first buffer status report BSR, and the first BSR is used to indicate the requested resources for the discovery message Resource pool information. The method according to claim 5, wherein the first BSR includes a resource pool ID, and the resource pool ID is used to indicate resource pool information of resources requested for the discovery message. The method according to any one of claims 1-6, wherein the first message includes a second buffer status report BSR, and the second BSR is used to indicate the requested resources for the discovery message Resource Type. The method according to claim 7, wherein the second BSR includes a resource type field, and the resource type field is used to indicate a resource type of the requested resource for the discovery message. The method according to any one of claims 1-8, wherein the first message includes a third buffer status report BSR, and the third BSR includes a target address index, and the target address index is used to indicate Resource pool information for the resource requested for the discovery message. The method according to claim 9, wherein the target address index is obtained by serializing the resource pool ID and the target address ID. The method according to claim 10, wherein the target address index obtained by serializing the resource pool ID and the target address ID has a specific number of bits. The method according to any one of claims 1-11, wherein the first message includes a fourth buffer status report BSR, and the fourth BSR includes a logical channel group ID, ie, LCGID, and the LCGID uses The resource type used to indicate the resource requested for the discovery message. The method according to claim 12, wherein, in response to receiving the fourth BSR including the LCGID, the network device determines the resources requested by the terminal device for the discovery message based on at least one of the following pre-configured mapping relationships A resource type of: Sidelink signaling bearer/data bearer, that is, the mapping relationship between SL-SRB/DRB and logical channel group ID, that is, LCGID; The mapping relationship between SL-SRB/DRB and logical channels; The mapping relationship between packet priority and LCGID; and Mapping relationship between data packet priority and logical channel. The method according to any one of claims 1-4, wherein the first message includes a resource scheduling request SR, and the SR is used to request resources for discovery messages. The method according to claim 14, wherein the SR is sent on a resource corresponding to a Scheduling Request ID configured by the network device for the terminal device and dedicated to the terminal device requesting to send a discovery message, that is, SchedulingRequestID . The method according to any one of claims 1-4, wherein the first message includes sidelink terminal information for requesting resources for discovery messages. The method of claim 16, wherein the sidelink terminal information indicates a target address ID corresponding to the requested resource and a requested resource type corresponding to the target address ID. The method according to any of claims 1-17, wherein, in response to receiving the first message, the network device allocates the requested resource to the terminal device. A method according to any one of claims 1-18, wherein, in response to receiving the first message, the network device configures the terminal device for side-bound license-free transmission of discovery messages and/or data Resource CG. The method according to claim 19, wherein the network device indicates whether the sideline authorization-free transmission resource CG can be used to send the discovery message by setting at least one of the following: Boolean type indication; and A field for indicating a CG type, wherein the CG type indicates whether the corresponding CG is used to send a discovery message or to send data. The method of claim 20, further comprising: In response to sending a discovery message, the terminal device selects a CG that can be used to send the discovery message from the lateral license-free transmission resources CG configured by the network device. A sidelink communication method comprising: The network device receives a first message from the terminal device, where the first message is used to request resources for discovery messages. The method of claim 22, wherein the first message includes at least one of the following: The cache status is reported to the BSR; Resource Scheduling Request SR; and Sidelink terminal information. The method according to claim 22 or 23, wherein the request includes a request for a resource pool and/or a request for a resource type. The method according to any of claims 22-24, wherein resource pools and/or resource types are indicated explicitly or implicitly through the first message. The method according to any one of claims 22-25, wherein the first message includes a first buffer status report BSR, and the first BSR is used to indicate the requested resources for the discovery message Resource pool information. The method according to claim 26, wherein the first BSR includes a resource pool ID, and the first BSR is used to indicate resource pool information of resources used for the discovery message requested. The method according to any one of claims 22-27, wherein the first message includes a second buffer status report BSR, and the second BSR is used to indicate the requested resources for the discovery message Resource Type. The method of claim 28, wherein the second BSR includes a resource type field for indicating a resource type of resources requested for discovery messages. The method according to any one of claims 22-29, wherein the first message includes a third buffer status report BSR, and the third BSR includes a target address index, and the target address index is used to indicate Resource pool information for the resource requested for the discovery message. The method according to claim 30, wherein the target address index is obtained by serializing the resource pool ID and the target address ID. The method according to claim 31, wherein the target address index obtained by serializing the resource pool ID and the target address ID has a specific number of bits. The method according to any one of claims 22-32, wherein the first message includes a fourth buffer status report BSR, and the fourth BSR includes a logical channel group ID, ie, LCGID, and the LCGID uses The resource type used to indicate the resource requested for the discovery message. The method of claim 33, further comprising: In response to receiving the fourth BSR including the LCGID, the network device determines, based on at least one of the following pre-configured mapping relationships, the resource type of the resource used for the discovery message requested by the terminal device: Sidelink signaling bearer/data bearer, that is, the mapping relationship between SL-SRB/DRB and logical channel group ID, that is, LCGID; The mapping relationship between SL-SRB/DRB and logical channels; The mapping relationship between packet priority and LCGID; and Mapping relationship between data packet priority and logical channel. The method according to any one of claims 22-25, wherein the first message includes a resource scheduling request, SR, for requesting resources for discovery messages. The method according to claim 35, wherein the SR is sent on a resource corresponding to a Scheduling Request ID configured by the network device for the terminal device and dedicated to the terminal device requesting to send a discovery message, that is, SchedulingRequestID . The method according to any one of claims 22-25, wherein the first message includes sidelink terminal information for requesting resources for discovery messages. The method of claim 37, wherein the sidelink terminal information indicates a target address ID corresponding to the requested resource and a requested resource type corresponding to the target address ID. The method according to any one of claims 22-38, further comprising: In response to receiving the first message, the network device allocates the requested resource to the terminal device. The method according to any one of claims 22-38, further comprising: In response to receiving the first message, the network device configures the terminal device with a sidelink license-free transmission resource CG for discovery messages and/or data. The method according to claim 40, wherein the network device indicates whether the sideline authorization-free transmission resource CG can be used to send the discovery message by setting at least one of the following: Boolean type indication; and A field for indicating a CG type, wherein the CG type indicates whether the corresponding CG is used to send a discovery message or to send data. The method according to claim 41, wherein, in response to sending a discovery message, the terminal device selects a CG that can be used to send the discovery message from the lateral license-free transmission resources CG configured by the network device . A terminal device, comprising: A transceiver configured to send a first message to a network device, where the first message is used to request resources for a discovery message. The device according to claim 43, wherein the first message includes at least one of: The cache status is reported to the BSR; Resource Scheduling Request SR; and Sidelink terminal information. The apparatus according to claim 43 or 44, wherein the request comprises a request for a resource pool and/or a request for a resource type. The apparatus according to any of claims 43-45, wherein resource pools and/or resource types are indicated explicitly or implicitly through the first message. The device according to any one of claims 43-46, wherein the first message includes a first buffer status report BSR, and the first BSR is used to indicate the requested resources for the discovery message Resource pool information. The device according to claim 47, wherein the first BSR includes a resource pool ID, and the resource pool ID is used to indicate resource pool information of resources requested for the discovery message. The device according to any one of claims 43-48, wherein the first message includes a second buffer status report BSR, and the second BSR is used to indicate the requested resources for the discovery message Resource Type. The apparatus of claim 49, wherein the second BSR includes a resource type field for indicating a resource type of resources requested for discovery messages. The device according to any one of claims 43-50, wherein the first message includes a third buffer status report BSR, and the third BSR includes a target address index, and the target address index is used to indicate Resource pool information for the resource requested for the discovery message. The device according to claim 51, wherein the target address index is obtained by serializing the resource pool ID and the target address ID. The apparatus according to claim 52, wherein the target address index obtained by serializing the resource pool ID and the target address ID has a specific number of bits. The device according to any one of claims 43-53, wherein the first message includes a fourth buffer status report BSR, and the fourth BSR includes a logical channel group ID, namely LCGID, and the LCGID uses The resource type used to indicate the resource requested for the discovery message. The device according to claim 54, wherein, in response to receiving the fourth BSR including the LCGID, the network device determines the resources requested by the terminal device for the discovery message based on at least one of the following pre-configured mapping relationships A resource type of: Sidelink signaling bearer/data bearer, that is, the mapping relationship between SL-SRB/DRB and logical channel group ID, that is, LCGID; The mapping relationship between SL-SRB/DRB and logical channels; The mapping relationship between packet priority and LCGID; and Mapping relationship between data packet priority and logical channel. The apparatus according to any of claims 43-46, wherein the first message includes a resource scheduling request, SR, for requesting resources for discovery messages. The device according to claim 56, wherein the SR is sent on a resource corresponding to a scheduling request ID configured by the network device for the terminal device and dedicated to the terminal device requesting to send a discovery message, that is, SchedulingRequestID . The apparatus according to any of claims 43-46, wherein the first message includes sidelink terminal information for requesting resources for discovery messages. The apparatus of claim 58, wherein the sidelink terminal information indicates a target address ID corresponding to the requested resource and a requested resource type corresponding to the target address ID. Apparatus according to any of claims 43-59, wherein, in response to receiving the first message, the network device allocates the requested resource to the terminal device. Apparatus according to any one of claims 43-60, wherein, in response to receiving the first message, the network device configures the terminal device for side-bound license-free transmission of discovery messages and/or data Resource CG. The device according to claim 61, wherein the network device indicates whether the sideline authorization-free transmission resource CG can be used to send the discovery message by setting at least one of the following: Boolean type indication; and A field for indicating a CG type, wherein the CG type indicates whether the corresponding CG is used to send a discovery message or to send data. The apparatus of claim 62, further comprising: A processor configured to select a CG that can be used to send the discovery message from the lateral license-free transmission resources CG configured by the network device in response to the discovery message being sent. A network device comprising: A transceiver configured to receive a first message from a terminal device, where the first message is used to request resources for a discovery message. The device of claim 64, wherein the first message includes at least one of: The cache status is reported to the BSR; Resource Scheduling Request SR; and Sidelink terminal information. The apparatus according to claim 64 or 65, wherein the request comprises a request for a resource pool and/or a request for a resource type. The apparatus according to any of claims 64-66, wherein resource pools and/or resource types are indicated explicitly or implicitly through the first message. The device according to any one of claims 64-67, wherein the first message includes a first buffer status report BSR, and the first BSR is used to indicate the resources requested for the discovery message Resource pool information. The apparatus according to claim 68, wherein the first BSR includes a resource pool ID for indicating resource pool information of resources requested for discovery messages. The device according to any one of claims 64-69, wherein the first message includes a second buffer status report BSR, and the second BSR is used to indicate the requested resources for the discovery message Resource Type. The apparatus of claim 70, wherein the second BSR includes a resource type field for indicating a resource type of resources requested for discovery messages. The device according to any one of claims 64-71, wherein the first message includes a third buffer status report BSR, and the third BSR includes a target address index, and the target address index is used to indicate Resource pool information for the resource requested for the discovery message. The device according to claim 72, wherein the target address index is obtained by serializing the resource pool ID and the target address ID. The apparatus according to claim 73, wherein the target address index obtained by serializing the resource pool ID and the target address ID has a specific number of bits. The device according to any one of claims 64-74, wherein the first message includes a fourth buffer status report BSR, and the fourth BSR includes a logical channel group ID, ie, LCGID, and the LCGID uses Used to indicate the resource type of the resource requested for the discovery message. The apparatus of claim 75, further comprising: A processor configured to determine a resource type of a resource requested by the terminal device for a discovery message based on at least one of the following pre-configured mapping relationships in response to receiving the fourth BSR including the LCGID: Sidelink signaling bearer/data bearer, that is, the mapping relationship between SL-SRB/DRB and logical channel group ID, that is, LCGID; The mapping relationship between SL-SRB/DRB and logical channels; The mapping relationship between packet priority and LCGID; and Mapping relationship between data packet priority and logical channel. The apparatus according to any of claims 64-67, wherein the first message comprises a resource scheduling request, SR, for requesting resources for discovery messages. The device according to claim 77, wherein the SR is sent on the resource corresponding to the scheduling request ID configured by the network device for the terminal device and dedicated to the terminal device requesting to send a discovery message, that is, SchedulingRequestID . The apparatus according to any of claims 64-67, wherein the first message includes sidelink terminal information for requesting resources for discovery messages. The apparatus of claim 79, wherein the sidelink terminal information indicates a target address ID corresponding to the requested resource and a requested resource type corresponding to the target address ID. Apparatus according to any one of claims 64-80, further comprising: A processor configured to allocate the requested resource to the terminal device in response to receiving the first message. Apparatus according to any one of claims 64-80, further comprising: A processor configured to, in response to receiving the first message, configure a lateral license-free transmission resource CG for discovery messages and/or data for the terminal device. The device according to claim 82, wherein the processor indicates whether the sideline license-free transmission resource CG is available for sending the discovery message by setting at least one of the following: Boolean type indication; and A field for indicating a CG type, wherein the CG type indicates whether the corresponding CG is used to send a discovery message or to send data. The device according to claim 83, wherein, in response to sending a discovery message, the terminal device selects a CG that can be used to send the discovery message from the lateral license-free transmission resources CG configured by the network device . A communication device, comprising: a processor and a memory, the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, so that the communication device performs as claimed in claim 1- The method described in any one of 42. A chip, comprising: a processor, configured to invoke and run a computer program from a memory, so that a device installed with the chip executes the method according to any one of claims 1-42. A computer-readable storage medium for storing a computer program, which causes the device to execute the method according to any one of claims 1-42 when the computer program is run by a device. A computer program product comprising computer program instructions for causing a computer to perform the method according to any one of claims 1-42. A computer program that causes a computer to perform the method according to any one of claims 1-42. A communication system comprising: at least one terminal device configured to perform the sidelink communication method according to any one of claims 1-21; and At least one network device configured to perform the sidelink communication method according to any one of claims 22-42.

Images