CN116982373A

CN116982373A - Side-link communication method, terminal device, network device and communication system

Info

Publication number: CN116982373A
Application number: CN202180095539.8A
Authority: CN
Inventors: 张博源; 卢前溪
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2021-06-22
Filing date: 2021-06-22
Publication date: 2023-10-31
Also published as: WO2022266870A1

Abstract

The application relates to a side-link communication method, a terminal device, a network device and a communication system, wherein the side-link communication method comprises the following steps: the terminal device sends a first message to the network device, the first message being for requesting resources for discovery messages.

Description

Side-link communication method, terminal device, network device and communication system

Technical Field

The present application relates to the field of communications, and more particularly, to a side-uplink communication method, a terminal device, a network device, and a communication system.

Background

The Side Link (SL) transmission technology adopts the technology of terminal equipment-to-terminal equipment direct communication, and has higher frequency spectrum efficiency and lower transmission delay. The SL transmission process can be roughly classified into an SL discovery process in which a terminal device detects discovery messages broadcast by other terminal devices, thereby detecting the presence of other SL-capable terminal devices in a short range, and recognizing identity information of the other terminal devices, and an SL data communication process. In the SL data communication process, various forms of data exchange such as voice call or multimedia information sharing can be performed between terminal devices at a short distance.

For the side-link, then, it is possible that the network side will configure the terminal with a data-specific resource pool, a data-and discovery message-shared resource pool, and/or a discovery message-specific resource pool. If two types of resource pools (such as a resource pool special for data or a resource pool shared by data and discovery information, or a resource pool shared by the resource pool special for discovery information or the data and the discovery information) are simultaneously configured to the terminal, according to the rule of Rel-16, if the terminal is in a mode one, the allocation instruction of the network side is listened to; if the mode is the mode two terminal, the resource pool is selected according to the terminal implementation behavior, and the data is distinguished from the discovery message transmission for the Rel-17 side uplink relay. For example, for mode two terminals, the resource pool of the discovery message and the resource pool of the data may be selected according to a particular rule; and for mode one terminals it may indicate to the base station the currently requested resources.

However, currently there is no definitive solution for how a mode-one terminal indicates to the base station the currently requested resources for the Rel-17 side uplink.

Disclosure of Invention

The embodiment of the application provides a side uplink communication method, terminal equipment, network equipment and a communication system.

The embodiment of the application provides a side uplink communication method, which comprises the following steps: the terminal device sends a first message to the network device, the first message being for requesting resources for discovery messages.

The embodiment of the application provides a side uplink communication method, which comprises the following steps: the network device receives a first message from the terminal device requesting resources for discovery messages.

The embodiment of the application provides a terminal device, which comprises: and a transceiver configured to send a first message to the network device, the first message requesting resources for the 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, the first message being for requesting resources for a discovery message.

An embodiment of the present application provides a communication apparatus including: the communication device comprises a processor and a memory, wherein the memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory so as to enable the communication device to execute the side uplink communication method.

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

At least one of the above terminal devices; and

at least one of the above network devices.

The embodiment of the application provides a chip for realizing the side uplink communication method.

Specifically, the chip includes: and a processor for calling and running the computer program from the memory, so that the device mounted with the chip executes the side-link communication method described above.

An embodiment of the present application provides a computer-readable storage medium storing a computer program that causes a computer to execute the above-described side-uplink communication method.

An embodiment of the present application provides a computer program product including computer program instructions for causing a computer to perform the above-described sidelink communication method.

The embodiments of the present application provide a computer program which, when run on a computer, causes the computer to perform the above-described side-uplink communication method.

Drawings

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

Fig. 2 exemplarily shows the communication of two terminals UE a and UE B via a PC5 interface.

Fig. 3 is a schematic flow chart of a side-link transmission method according to one embodiment of the application.

Fig. 4 is a schematic flow chart of a side-uplink transmission method according to another embodiment of the present application.

Fig. 5 is a schematic flow chart diagram of a side-link 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 apparatus according to an embodiment of the present application.

Fig. 9 exemplarily shows a schematic structural view 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 accompanying drawings in the embodiments of the present application.

The technical scheme of the embodiment of the application can be applied to various communication systems, such as: global system for mobile communications (Global System of Mobile communication, GSM), code division multiple access (Code Division Multiple Access, CDMA) system, wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) system, general packet Radio service (General Packet Radio Service, GPRS), long term evolution (Long Term Evolution, LTE) system, advanced long term evolution (Advanced long term evolution, LTE-a) system, new Radio (NR) system, evolved system of NR system, LTE-based access to unlicensed spectrum, LTE-U) system on unlicensed spectrum, NR (NR-based access to unlicensed spectrum, NR-U) system on unlicensed spectrum, non-terrestrial communication network system, universal mobile communication system (Universal Mobile Telecommunication System, UMTS), wireless local area network (Wireless Local Area Networks, WLAN), wireless fidelity (Wireless Fidelity, wiFi), fifth Generation communication (5 th-Generation, 5G) system, or other communication system, etc.

Generally, the number of connections supported by the conventional communication system is limited and easy to implement, however, as the communication technology advances, the mobile communication system will support not only conventional communication but also, for example, device-to-Device (D2D) communication, machine-to-machine (Machine to Machine, M2M) communication, machine type communication (Machine Type Communication, MTC), inter-vehicle (Vehicle to Vehicle, V2V) communication, or internet of vehicles (Vehicle to everything, V2X) communication, etc., to which the embodiments of the present application can also be applied.

Optionally, the communication system in the embodiment of the present application may be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, a dual connectivity (Dual Connectivity, DC) scenario, or a Stand Alone (SA) fabric scenario.

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

Embodiments of the present application are described in connection with a network device and a terminal device, where the terminal device may also be referred to as a User Equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a User terminal, a wireless communication device, a User agent, a User Equipment, or the like.

The terminal device may be a Station (ST) in a WLAN, may be a cellular telephone, a cordless telephone, a session initiation protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital assistant (Personal Digital Assistant, PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle device, a wearable device, a terminal device in a next generation communication system such as an NR network, or a terminal device in a future evolved public land mobile network (Public Land Mobile Network, PLMN) network, etc.

In the embodiment of the application, the terminal equipment can be deployed on land, including indoor or outdoor, handheld, wearable or vehicle-mounted; can also be deployed on the water surface (such as ships, etc.); but may also be deployed in the air (e.g., on aircraft, balloon, satellite, etc.).

In the embodiment of the present application, the terminal device may be a Mobile Phone (Mobile Phone), a tablet computer (Pad), a computer with a wireless transceiving function, a Virtual Reality (VR) terminal device, an augmented Reality (Augmented Reality, AR) terminal device, a wireless terminal device in industrial control (industrial control), a wireless terminal device in unmanned driving (self driving), a wireless terminal device in remote medical (remote medical), a wireless terminal device in smart grid (smart grid), a wireless terminal device in transportation security (transportation safety), a wireless terminal device in smart city (smart city), or a wireless terminal device in smart home (smart home), and the like.

By way of example, and not limitation, in embodiments of the present application, the terminal device may also be a wearable device. The wearable device can also be called as a wearable intelligent device, and is a generic name for intelligently designing daily wear by applying wearable technology and developing wearable devices, such as glasses, gloves, watches, clothes, shoes and the like. The wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also can realize a powerful function through software support, data interaction and cloud interaction. The generalized wearable intelligent device includes full functionality, large size, and may not rely on the smart phone to implement complete or partial functionality, such as: smart watches or smart glasses, etc., and focus on only certain types of application functions, and need to be used in combination with other devices, such as smart phones, for example, various smart bracelets, smart jewelry, etc. for physical sign monitoring.

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

By way of example, and not limitation, in embodiments of the present application, a network device may have a mobile nature, e.g., the network device may be a mobile device. Alternatively, the network device may be a satellite, a balloon station. For example, the satellite may be a Low Earth Orbit (LEO) satellite, a medium earth orbit (medium earth orbit, MEO) satellite, a geosynchronous orbit (geostationary earth orbit, GEO) satellite, a high elliptical orbit (High Elliptical Orbit, HEO) satellite, or the like. Alternatively, the network device may be a base station disposed on land, in a water area, or the like.

In the embodiment of the present application, a network device may provide services for a cell, where a terminal device communicates with the network device through a transmission resource (e.g., a frequency domain resource, or a spectrum resource) used by the cell, where the cell may be a cell corresponding to the network device (e.g., a base station), and the cell may belong to a macro base station, or may belong to a base station corresponding to a Small cell (Small cell), where the Small cell may include: urban cells (Metro cells), micro cells (Micro cells), pico cells (Pico cells), femto cells (Femto cells) and the like, and the small cells have the characteristics of small coverage area and low transmitting power and are suitable for providing high-rate data transmission services.

Fig. 1 schematically illustrates a communication system 100. The communication system comprises one network device 110 and two terminal devices 120. Alternatively, the communication system 100 may include a plurality of network devices 110, and the coverage area of each network device 110 may include other numbers of terminal devices 120, which are not limited by the embodiments of the present application.

Optionally, the communication system 100 may further 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), and the present application is not limited thereto.

The network device may further include an access network device and a core network device. I.e. the wireless communication system further comprises a plurality of core networks for communicating with the access network devices. The access network device may be a long-term evolution (LTE) system, a next-generation (NR) system, or an evolved base station (evolutional node B, abbreviated as eNB or e-NodeB) macro base station, a micro base station (also called "small base station"), a pico base station, an Access Point (AP), a transmission point (transmission point, TP), a new generation base station (new generation Node B, gNodeB), or the like in an licensed assisted access long-term evolution (LAA-LTE) system.

It should be understood that a device having a communication function in a network/system according to an embodiment of the present application may be referred to as a communication device. Taking the communication system shown in fig. 1 as an example, the communication device may include a network device and a terminal device with a communication function, where the network device and the terminal device may be specific devices in the embodiments of the present application, and are not described herein again; the communication device may also include other devices in the communication system, such as a network controller, a mobility management entity, 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 used interchangeably herein. The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated 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, an indirect indication, or an indication having an association relationship. For example, a indicates B, which may mean that a indicates B directly, e.g., B may be obtained by a; it may also indicate that a indicates B indirectly, e.g. a indicates C, B may be obtained by C; it may also be indicated that there is an association between a and B.

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

In order to facilitate understanding of the technical solutions of the embodiments of the present application, the following description describes related technologies of the embodiments of the present application, and the following related technologies may be optionally combined with the technical solutions of the embodiments of the present application as alternatives, which all belong to the protection scope of the embodiments of the present application.

During the Rel-13 long term evolution (Long Term Evolution, LTE), sidelink discovery is defined as the process by which a UE supporting sidelink discovery uses an evolved universal terrestrial radio access network (evolved universal terrestrial radio access network, E-UTRA) to communicate directly to discover other UEs in its vicinity via PC 5. Side-uplink discovery is supported both when the UE is served by E-UTRA and when the UE is not in E-UTRA coverage. Only UEs supporting proximity services (Proximity based Service, prose) public safety can perform side-uplink discovery when they are out of E-UTRA coverage. For public safety side uplink discovery, an allowed frequency is preconfigured in the UE and used even if the UE is out of coverage of E-UTRA in the frequency. The preconfigured frequency is the same as the frequency of the public safety carrier.

The upper layer processes the notification and monitors the authorization of the discovery message.

The content of the discovery message is transparent to the Access Stratum (AS), where there is no distinction between the sidelink discovery model and the sidelink discovery type. However, the higher layer will inform the side-link discovery broadcast whether it relates to public safety or non-public safety discovery. The higher layers also inform the discovery announcement/monitoring whether or not it relates to network relay discovery or other public safety discovery.

The UE may participate in the broadcasting and listening of discovery messages of the Uu interface (the 5G system still refers to the interface between the terminal and the access network simply as Uu interface, also referred to as air interface) in idle state and RRC (Radio Resource Control ) connected state according to the configuration of the gNB. Wherein the UE may broadcast and listen for discovery messages under half duplex restrictions.

UEs participating in the broadcasting and listening of the discovery message may maintain the current UTC (Universal Time Coordinated, universal coordinated time) time. UEs participating in the broadcast transmit a discovery message, which may be generated by a Prose (Proximity based Service, proximity services) protocol, while taking into account UTC time when the discovery message is transmitted. In the listening UE, the Prose protocol (see fig. 2) provides a message, which is verified together with the received UTC time provided by Prose Function (Prose Function entity).

To perform synchronization, UEs participating in the discovery message broadcast may act as a synchronization source by transmitting a side uplink broadcast control channel (side uplink Broadcast Control Channel, SBCCH) and a synchronization signal based on the resource information of the synchronization signal provided in the system information block (System Information Block, SIB) 19.

There are three range classes. The upper layer authorization provides the UE's coverage class. The maximum allowed transmit power per range class is given in SIB 19. The UE uses the applicable maximum allowed transmit power corresponding to its grant range level. This sets an upper limit on the transmit power determined based on the open loop power control parameters.

As described above, currently, there is no deterministic scheme for how a mode-one terminal indicates the currently requested resources to the base station for the Rel-17 side uplink.

The application provides a corresponding solution.

Fig. 3 is a schematic flow chart diagram of a method of side-uplink communication according to an embodiment of the application. The method may alternatively be applied to a terminal device and a network device 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 a resource for discovery messages.

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

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

buffer status reporting (Buffer Status Report, BSR);

a resource scheduling request (Scheduling Request, SR); and

side uplink terminal information (sidelink information).

The first message of the present application may include at least one of the BSR, the SR, and side uplink terminal information (sidelink information) described above to indicate the currently requested resource to the network device. 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 manners of indicating the currently requested resource to the network device may also be used.

Additionally, the first message may optionally include other content in addition to the content for indicating the currently requested resource to the network device.

Optionally, the resource request includes a request for a resource pool and/or a request for a resource type. That is, the terminal device requests resources from the network device, which may indicate the pool of resources to be requested and/or the type of resources to be requested, so that the network device specifies and configures and/or allocates the resources requested by the terminal device.

Optionally, the resource pool and/or the resource type is indicated explicitly or implicitly by said first message. That is, the manner in which the requested resource is indicated may be explicit or implicit. In summary, in the present application, as long as the network device can determine the resource pool and/or the resource type requested by the terminal device based on the resource request of the terminal device, there is no need to specifically define the indication manner of the resource request.

Regarding the resource pool, in the present application, the network device may configure the terminal device with a resource pool common to the data and the discovery message, a resource pool dedicated to the discovery message, and a resource pool dedicated to the data.

It is simpler if the network device configures its dedicated resource pool for data or discovery messages, and if the network device configures two types of resource pools, namely a common resource pool and a dedicated resource pool, for data or discovery messages, it is necessary to further determine which resource pool to use.

For example, a plurality of available resource pools may be configured for the terminal device, and each of the plurality of available resource pools may be capable of being used to transmit discovery messages. When a terminal device wishes to initiate SL communication, or the terminal device wishes to access the network device through other terminal devices, the terminal device may determine a target resource pool from the plurality of available resource pools to send a discovery message.

In the present application, as long as one target resource pool can be determined from a plurality of available resource pools, there is no limitation on the specific embodiment thereof.

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

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

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

In the present application, when the terminal device needs to request resources, the required resources may be indicated to the network device through the first BSR, specifically, for example, the terminal device may carry a resource pool ID (may carry the resource pool ID through, for example, a resource pool ID field) in the first BSR to explicitly indicate resource pool information of the resources to be requested by the terminal device.

An example manner of indicating the resource pool information of the requested resources for the discovery message through the first BSR is given above, it should be noted that the present application is not limited to this example manner.

According to an 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 a resource type of the requested resource for the discovery message.

That is, in the present application, another BSR may be used to indicate the type of requested resource.

Optionally, the terminal device may indicate, through the second BSR, a resource type of the requested resource for the discovery message through a resource type field carried by the second BSR.

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

In the present application, when the terminal device needs to request the resource, the indication may be performed to the network device through the second BSR, specifically, for example, the terminal device may carry a resource type field through the second BSR, where the resource type field may indicate whether the terminal device needs to request the data transmission resource or the discovery message transmission resource.

An example manner of indicating the resource type of the requested resource for the discovery message through the second BSR is given above, it should be noted that the present application is not limited to this example manner.

According to an embodiment of the present application, optionally, the first message may include a third buffer status reporting BSR, and the terminal device may indicate the resource pool information of the requested resource for discovery message through a target address index (destination index) included in the third BSR.

Optionally, the first message includes a third buffer status reporting BSR, and the third BSR includes a target address index for indicating resource pool information of the requested resources for discovery messages.

The manner in which the resource pool information of the resource to be requested is indicated by the target address index belongs to an implicit indication.

Alternatively, the destination address index may be obtained by serializing the resource pool ID with the destination address ID.

Alternatively, the destination address index obtained by serializing the resource pool ID with the destination address ID may have a specific number of bits. For example, the target address index may have a number of bits of 5 bits. Of course, the number of bits of the target address index may be other values.

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

An example manner of serialization rules 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 described above, the destination address index 1, destination index 1, can be serialized from the resource pool ID1, i.e., resource pool ID1, and the destination address IDA, i.e., destination IDA. Similarly, the destination address index 2, destination index, may be serialized from the resource pool ID1, and the destination address IDB, destination IDB. The destination address index 3, destination index 3, may be serialized from the resource pool ID2, and the destination address IDA, destination IDA. The destination address index 4, destination index, may be serialized from the resource pool ID2, and the destination address IDB, destination IDB.

The above has given an example form for serializing a resource pool ID with a destination address ID to obtain a destination address index, it should be noted that the application is not limited to this example form, but can also be used for serialization in other ways.

Optionally, the first message may include a fourth buffer status reporting BSR, and the terminal device indicates a resource type of the requested resource for the discovery message through a logical channel group ID, i.e., LCGID, included in the fourth BSR.

Optionally, the first message includes a fourth buffer status reporting BSR, and the fourth BSR includes a logical channel group ID, LCGID, for indicating a resource type of the requested resource for the discovery message.

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

That is, the resource type of the requested resource can be indicated by the mapping relationship by indicating only the LCGID at the time of reporting by the terminal device. This is also an implicit indication.

More specifically, optionally, the network device may determine the resource type requested by the terminal device through the LCGID reported by the terminal device based on a mapping relationship between a preconfigured (SL-SRB/DRB or packet priority) and (LCGID or logical channel).

The mapping relation between (SL-SRB/DRB or packet priority) and (LCGID or logical channel) may include, for example, mapping relation between SL-SRB/DRB and LCGID, mapping relation between SL-SRB/DRB and logical channel, mapping relation between packet priority and LCGID, and mapping relation between packet priority and logical channel.

Alternatively, the terminal device may request the network device for resources for the discovery message through a resource scheduling request SR included in the first message. That is, the requested resources may also be indicated by the SR.

Optionally, the first message includes a resource scheduling request SR, the SR being for requesting 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 request by the terminal device to send a discovery message, i.e. a scheduling request ID. In other words, the network device configures the resource corresponding to the scheduling request ID for the terminal device such that the scheduling request ID is transmitted on the resource corresponding thereto.

That is, the network device configures the terminal device with a schedulingrequestID dedicated to requesting transmission of the discovery message, so that when the terminal device requests a transmission resource dedicated to the discovery message, the resource scheduling request SR can be transmitted on the transmission resource corresponding to the schedulingrequestID.

Alternatively, the terminal device may request the network device for resources for the discovery message through sidelink terminal information including the first message.

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

Optionally, the first message includes side-link terminal information for requesting resources for discovery messages

When the terminal equipment reports the desiring UEinformation, the terminal equipment indicates the resource type required by the terminal equipment corresponding to different target address IDs, and specifically, the resource type is a discovery message sending resource or a data sending resource. That is, for the side-link terminal information sidelink information here, in addition to the destination address ID being indicated therein, the requested resource type corresponding to the destination address ID is indicated therein. Wherein the indicated destination address ID may be one or more, to which the present application is not limited in any way.

A specific example form will be given below:

the above has been given an example form, it is to be noted that the application is not limited to this example form, but that other forms may also be used.

As shown in fig. 4, the side-uplink communication method according to the embodiment of the present application may further include the following step S201:

S220, the network equipment allocates the requested resources for the terminal equipment in response to receiving the first message.

In this step, the network device allocates the requested resources to the network device in accordance with the received first message, in particular in accordance with an indication of the requested resources in the received first message.

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

In the present application, the manner in which the network device allocates resources to the terminal device may be dynamic, for example, allocated per request; the allocation method can also be semi-static, for example, the side line unlicensed transmission resources are allocated according to the request, so that the transmission resources do not need to be re-requested, and therefore, the allocation method can reduce the time delay of the side line transmission and improve the response speed.

Optionally, in response to receiving the first message, the network device configures the terminal device with a sidelink unlicensed transmission resource CG for discovery messages and/or data.

Examples are given below:

optionally, the network device may indicate whether the sidelink unlicensed transmission resource CG is available for sending discovery messages by setting at least one of:

A boolean type indication; and

and a field for indicating a CG type, wherein the CG type indicates whether the corresponding CG is for transmitting a discovery message or for transmitting data.

The above has given an example form indicating whether a sidelink unlicensed transmission resource CG is available for transmitting discovery messages, it is noted that the application is not limited to the above-described example form.

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

s231, in response to the discovery message to be sent, 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.

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

Thus, through the above-described respective exemplary embodiments of the present application, the resources requested by the terminal device can be clearly indicated, and the network device can accurately allocate the 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 application.

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

Wherein the transceiver 410 may be configured to send a first message to the network device, the first message being for requesting resources for the discovery message.

Optionally, the first message includes at least one of:

reporting the buffer status to a BSR;

a resource scheduling request SR; and

side-link terminal information sidelink 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 the resource type is indicated explicitly or implicitly by said first message.

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

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

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

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

Optionally, the destination address index is obtained by serializing the resource pool ID with the destination address ID.

Alternatively, the destination address index obtained by serializing the resource pool ID with the destination address ID has a specific number of bits.

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

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

Optionally, the terminal device requests the network device for resources for the discovery message by means of a resource scheduling request SR comprised by said first 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 for the terminal device to request to send a discovery message, i.e. a scheduling request ID.

Optionally, the terminal device requests the network device for resources for discovery messages through sidelink terminal information including the first message.

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

Optionally, the network device indicates whether the sidelink unlicensed transmission resource CG is available for sending discovery messages by setting at least one of:

a boolean type indication; and

Optionally, the terminal device may further include:

a processor 420 is configured to select, in response to a discovery message to be sent, 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 transceiver 410 is configured to send a first message to the network device, the first message being for requesting resources for the discovery message.

Optionally, the first message includes at least one of:

reporting the buffer status to a BSR;

a resource scheduling request SR; and

side uplink terminal information.

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

Optionally, the first BSR includes a resource pool ID for indicating resource pool information of the requested resource for the discovery message.

Optionally, the second BSR includes a resource type field for indicating a resource type of the requested resource for the discovery message.

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

a mapping relationship between a side-link signaling bearer/data bearer, i.e., SL-SRB/DRB, and a logical channel group ID, i.e., LCGID;

Mapping relation between SL-SRB/DRB and logic channel;

mapping relation between data packet priority and LCGID; and

mapping relation between data packet priority and logical channel.

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

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

Optionally, the first message includes side-uplink terminal information for requesting resources for discovery messages.

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

a boolean type indication; and

Optionally, the terminal device further includes:

Optionally, the processor 420 may be further configured to perform processing operations performed by the terminal device in the information indication method, for example, but not limited to, determining, obtaining, reading, storing, and the like.

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

For brevity, details of the operation thereof are not described herein.

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

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

Wherein the transceiver 610 may be configured to receive a first message from a terminal device, the first message being used to request resources for discovery messages.

Optionally, the network device 600 may further include:

a processor 620 configured to determine a resource type of the resource requested by the terminal device for the discovery message based on a preconfigured mapping relation in response to receiving the fourth BSR containing the LCGID: mapping relationship between (SL-SRB/DRB or packet priority) and (LCGID or logical channel).

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

Optionally, the processor 620 may be further configured to configure the terminal device with a side-by unlicensed transmission resource CG for discovery messages and/or data in response to receiving the first message.

Optionally, the processor may indicate whether the sidelink unlicensed transmission resource CG is available for sending discovery messages by setting at least one of:

a boolean type indication; and

Alternatively, the transceiver 610 may be configured to receive a first message from the terminal device requesting resources for discovery messages

Optionally, the first message includes at least one of:

reporting the buffer status to a BSR;

a resource scheduling request SR; and

side uplink terminal information.

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

mapping relation between SL-SRB/DRB and logic channel;

mapping relation between data packet priority and LCGID; and

mapping relation between data packet priority and logical channel.

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

Optionally, the processor is further configured for configuring the terminal device with a side-by unlicensed transmission resource CG for discovery messages and/or data in response to receiving the first message.

Optionally, the processor indicates whether the sidelink unlicensed transmission resource CG is available for sending discovery messages by setting at least one of:

a boolean type indication; and

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

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

In addition, the network device may also include a memory or the like.

For brevity, details of the operation thereof are not described herein.

Fig. 8 is a schematic structural diagram of a communication device 1900 according to an embodiment of the present application. The communications device 1900 shown in fig. 8 includes a processor 1910, and the processor 1910 may call and run a computer program from memory to implement the methods in embodiments of the present application.

Optionally, as shown in fig. 8, the communications device 1900 may also include a memory 1920. Wherein the processor 1910 may call and run computer programs from the memory 1920 to implement the methods in embodiments of the present application.

Wherein the memory 1920 may be a separate device from the processor 1910 or may be integrated within 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, and in particular, may transmit information or data to other devices, or receive information or data transmitted by other devices.

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

Optionally, the communication device 1900 may be a terminal device according to an embodiment of the present application, and the communication device 1900 may implement corresponding processes implemented by the terminal device in each method according to the embodiment of the present application, which are not described herein for brevity.

Optionally, the communication device 1900 may be a network device according to an embodiment of the present application, and the communication device 1900 may implement corresponding flows implemented by the network device in each method according to the embodiment of the present application, which are not described herein for brevity.

Fig. 9 is a schematic structural diagram of a chip 2000 according to an embodiment of the present application. The chip 2000 illustrated in fig. 9 includes a processor 2010, and the processor 2010 may call and execute a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, as shown in fig. 9, chip 2000 may also include memory 2020. Wherein the processor 2010 may invoke and run a computer program from the memory 2020 to implement the method in embodiments of the present application.

Wherein the memory 2020 may be a separate device from the processor 2010 or may be integrated in the processor 2010.

Optionally, the chip 2000 may also include an input interface 2030. Processor 2010 may control input interface 2030 to communicate with other devices or chips, and in particular, may obtain information or data sent by the other devices or chips.

Optionally, the chip 2000 may also include an output interface 2040. Processor 2010 may control the output interface 2040 to communicate with other devices or chips, and in particular, may output information or data to the other devices or chips.

Optionally, the chip may be applied to a terminal device in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the terminal device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the chip may be applied to the network device in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.

It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, or the like.

Fig. 10 is a schematic block diagram of a communication system 1000 in accordance with 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.

The terminal device 1010 may be used to implement the corresponding function implemented by the terminal device in the method, or may be the terminal device 400 or the communication device 1900 as a terminal device. Wherein the network device 1080 may be configured to implement the corresponding functions implemented by the network device in the above-described method, or may be the network device 600 described above or the communication device 1900 as a network device. For brevity, the description is omitted here.

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

The memory mentioned above may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. The volatile memory may be random access memory (random access memory, RAM).

It should be understood that the above memory is illustrative but not restrictive, and for example, the memory in the embodiments of the present application may be Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), direct RAM (DR RAM), and the like. That is, the memory in embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, 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 loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present application, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line (Digital Subscriber Line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., a floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid State Disk (SSD)), or the like.

It should be understood that, in various embodiments of the present application, the sequence numbers of the foregoing processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic thereof, and should not constitute any limitation on the implementation process of the embodiments of the present application. It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily appreciate variations or alternatives within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

A method of side-link communication, comprising:

the terminal device sends a first message to the network device, the first message being used to request resources of the discovery message.
The method of claim 1, wherein the first message comprises at least one of:

Reporting the buffer status to a BSR;

a resource scheduling request SR; and

side uplink terminal information.
The method according to claim 1 or 2, wherein the request comprises a request for a resource pool and/or a request for a resource type.
A method according to any of claims 1-3, wherein a resource pool and/or a resource type is indicated explicitly or implicitly by the first message.
The method of any of claims 1-4, wherein the first message includes a first buffer status reporting, BSR, and the first BSR is to indicate resource pool information for the requested resources for discovery messages.
The method of claim 5, wherein the first BSR includes a resource pool ID, and wherein the resource pool ID is used to indicate resource pool information for the requested resources for discovery messages.
The method of any of claims 1-6, wherein the first message includes a second buffer status reporting BSR, and the second BSR is to indicate a resource type of the requested resource for discovery messages.
The method of claim 7, wherein the second BSR includes a resource type field indicating a resource type of the requested resource for the discovery message.
The method of any of claims 1-8, wherein the first message comprises a third buffer status reporting BSR, and the third BSR comprises a target address index to indicate resource pool information for the requested resources for discovery messages.
The method of claim 9, wherein the destination address index is obtained by serializing a resource pool ID with a destination address ID.
The method of claim 10, wherein the destination address index obtained by serializing the resource pool ID with the destination address ID has a specific number of bits.
The method of any of claims 1-11, wherein the first message comprises a fourth buffer status reporting, BSR, and the fourth BSR comprises a logical channel group, i.e., LCGID, indicating a resource type of the requested resource for discovery messages.
The method of claim 12, wherein, in response to receiving the fourth BSR including the LCGID, the network device determines a resource type of the resources requested by the terminal device for the discovery message based on at least one of the pre-configured mappings:

A mapping relationship between a side-link signaling bearer/data bearer, i.e., SL-SRB/DRB, and a logical channel group ID, i.e., LCGID;

mapping relation between SL-SRB/DRB and logic channel;

mapping relation between data packet priority and LCGID; and

mapping relation between data packet priority and logical channel.
The method of any of claims 1-4, wherein the first message comprises a resource scheduling request, SR, requesting resources for discovery messages.
The method of claim 14, wherein the SR is transmitted on a resource corresponding to a scheduling request ID configured by the network device for the terminal device, that is, a SchedulingRequestID, dedicated to the terminal device requesting transmission of a discovery message.
The method of any of claims 1-4, wherein the first message includes side-uplink terminal information for requesting resources for discovery messages.
The method of claim 16, wherein the side-uplink 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 of any of claims 1-17, wherein the network device allocates the requested resources to the terminal device in response to receiving the first message.
The method according to any of claims 1-18, wherein in response to receiving the first message, the network device configures the terminal device with side-tracking unlicensed transmission resources, CG, for discovery messages and/or data.
The method of claim 19, wherein the network device indicates whether a sidelink unlicensed transmission resource CG is available for transmitting discovery messages by setting at least one of:

a boolean type indication; and

and a field for indicating a CG type, wherein the CG type indicates whether the corresponding CG is for transmitting a discovery message or for transmitting data.
The method of claim 20, further comprising:

in response to a discovery message to be sent, the terminal device selects a CG that can be used for sending the discovery message from the lateral unlicensed transmission resources CG configured by the network device.
A method of side-link communication, comprising:

the network device receives a first message from the terminal device, the first message being for requesting resources of a discovery message.
The method of claim 22, wherein the first message comprises at least one of:

reporting the buffer status to a BSR;

a resource scheduling request SR; and

side uplink terminal information.
The method according to claim 22 or 23, wherein the request comprises a request for a resource pool and/or a request for a resource type.
The method according to any of claims 22-24, wherein a resource pool and/or a resource type is indicated explicitly or implicitly by the first message.
The method of any of claims 22-25, wherein the first message includes a first buffer status reporting, BSR, and the first BSR is to indicate resource pool information for the requested resources for discovery messages.
The method of claim 26, wherein the first BSR includes a resource pool ID, the first BSR to indicate resource pool information for the requested resources for discovery messages.
The method of any of claims 22-27, wherein the first message includes a second buffer status reporting, BSR, and the second BSR is to indicate a resource type of the requested resource for discovery messages.
The method of claim 28, wherein the second BSR includes a resource type field indicating a resource type of the requested resource for the discovery message.
The method of any of claims 22-29, wherein the first message comprises a third buffer status reporting BSR, and the third BSR comprises a target address index to indicate resource pool information for the requested resources for discovery messages.
The method of claim 30, wherein the destination address index is obtained by serializing a resource pool ID with a destination address ID.
The method of claim 31, wherein the destination address index obtained by serializing the resource pool ID with the destination address ID has a specific number of bits.
The method of any of claims 22-32, wherein the first message comprises a fourth buffer status reporting, BSR, and the fourth BSR comprises a logical channel group, i.e., LCGID, indicating a resource type of the requested resource for discovery messages.
The method of claim 33, further comprising:

In response to receiving the fourth BSR including the LCGID, the network device determines a resource type of the resource requested by the terminal device for the discovery message based on at least one of the pre-configured mappings:

a mapping relationship between a side-link signaling bearer/data bearer, i.e., SL-SRB/DRB, and a logical channel group ID, i.e., LCGID;

mapping relation between SL-SRB/DRB and logic channel;

mapping relation between data packet priority and LCGID; and

mapping relation between data packet priority and logical channel.
The method of any of claims 22-25, wherein the first message comprises a resource scheduling request, SR, requesting resources for discovery messages.
The method of claim 35, wherein the SR is transmitted on a resource corresponding to a scheduling request ID configured by the network device for the terminal device, that is, a SchedulingRequestID, dedicated to the terminal device requesting transmission of a discovery message.
The method of any of claims 22-25, wherein the first message includes side-uplink terminal information for requesting resources for discovery messages.
The method of claim 37, wherein the side-uplink 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 of any of claims 22-38, further comprising:

in response to receiving the first message, the network device allocates the requested resources for the terminal device.
The method of any of claims 22-38, further comprising:

in response to receiving the first message, the network device configures the terminal device with a sidelink unlicensed transmission resource CG for discovery messages and/or data.
The method of claim 40, wherein the network device indicates whether a sidelink unlicensed transmission resource CG is available for transmitting discovery messages by setting at least one of:

a boolean type indication; and

and a field for indicating a CG type, wherein the CG type indicates whether the corresponding CG is for transmitting a discovery message or for transmitting data.
The method of claim 41, wherein in response to a discovery message being sent, 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.
A terminal device, comprising:

and a transceiver configured to send a first message to the network device, the first message requesting resources for the discovery message.
The apparatus of claim 43, wherein the first message comprises at least one of:

reporting the buffer status to a BSR;

a resource scheduling request SR; and

side uplink terminal information.
The device of claim 43 or 44, wherein the request comprises a request for a resource pool and/or a request for a resource type.
The device of any of claims 43-45, wherein a resource pool and/or a resource type is indicated explicitly or implicitly by the first message.
The apparatus of any of claims 43-46, wherein the first message comprises a first buffer status reporting BSR, and the first BSR is to indicate resource pool information for requested resources for discovery messages.
The apparatus of claim 47, wherein the first BSR includes a resource pool ID that indicates resource pool information for the requested resources for discovery messages.
The apparatus of any of claims 43-48, wherein the first message comprises a second buffer status reporting BSR, and the second BSR is to indicate a resource type of the requested resource for the discovery message.
The apparatus of claim 49, wherein the second BSR includes a resource type field indicating a resource type of the requested resource for the discovery message.
The apparatus of any of claims 43-50, wherein the first message comprises a third buffer status reporting BSR, and the third BSR comprises a target address index to indicate resource pool information for the requested resources for discovery messages.
The apparatus of claim 51, wherein the destination address index is obtained by serializing a resource pool ID with a destination address ID.
The apparatus of claim 52, wherein the destination address index obtained by serializing the resource pool ID with the destination address ID has a specific number of bits.
The apparatus of any of claims 43-53, wherein the first message comprises a fourth buffer status reporting BSR, and the fourth BSR contains a logical channel group ID, LCGID, indicating a resource type of resources requested for discovery messages.
The device of claim 54, wherein, in response to receiving the fourth BSR including the LCGID, the network device determines a resource type of resources requested by the terminal device for discovery messages based on at least one of pre-configured mappings:

A mapping relationship between a side-link signaling bearer/data bearer, i.e., SL-SRB/DRB, and a logical channel group ID, i.e., LCGID;

mapping relation between SL-SRB/DRB and logic channel;

mapping relation between data packet priority and LCGID; and

mapping relation between data packet priority and logical channel.
The apparatus of any of claims 43-46, wherein the first message comprises a resource scheduling request, SR, requesting resources for discovery messages.
An apparatus as defined in claim 56, wherein the SR is transmitted on a resource corresponding to a scheduling request ID, i.e., a schedulingRequestID, configured by the network device for the terminal device and dedicated to the terminal device requesting to transmit a discovery message.
The apparatus of any of claims 43-46, wherein the first message comprises side-uplink terminal information 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.
The device of any of claims 43-59, wherein the network device allocates the requested resources to the terminal device in response to receiving the first message.
The device of any of claims 43-60, wherein in response to receiving the first message, the network device configures the terminal device with side-by unlicensed transmission resources CG for discovery messages and/or data.
The device of claim 61, wherein the network device indicates whether a sidelink unlicensed transmission resource CG is available for transmitting discovery messages by setting at least one of:

a boolean type indication; and

and a field for indicating a CG type, wherein the CG type indicates whether the corresponding CG is for transmitting a discovery message or for transmitting data.
The apparatus of claim 62, further comprising:

a processor configured to select, in response to a discovery message to be sent, a CG that is available for sending the discovery message from the lateral unlicensed transmission resources CG configured by the network device.
A network device, comprising:

a transceiver configured to receive a first message from a terminal device, the first message being for requesting resources for a discovery message.
The device of claim 64, wherein the first message comprises at least one of:

reporting the buffer status to a BSR;

a resource scheduling request SR; and

side uplink terminal information.
The device of claim 64 or 65, wherein the request comprises a request for a resource pool and/or a request for a resource type.
The device of any of claims 64-66, wherein a resource pool and/or a resource type is indicated explicitly or implicitly by the first message.
The apparatus of any of claims 64-67, wherein the first message comprises a first buffer status reporting BSR, and the first BSR is to indicate resource pool information for requested resources for discovery messages.
The apparatus of claim 68, wherein the first BSR includes a resource pool ID that indicates resource pool information for the requested resources for discovery messages.
The apparatus of any of claims 64-69, wherein the first message comprises a second buffer status reporting BSR, and the second BSR is to indicate a resource type of the requested resource for discovery messages.
The apparatus of claim 70, wherein the second BSR includes a resource type field indicating a resource type of the requested resource for the discovery message.
The device of any of claims 64-71, wherein the first message comprises a third buffer status reporting BSR, and the third BSR comprises a target address index to indicate resource pool information for the requested resources for discovery messages.
The apparatus of claim 72, wherein the destination address index is obtained by serializing a resource pool ID with a destination address ID.
The apparatus of claim 73, wherein the destination address index obtained by serializing the resource pool ID with the destination address ID has a specific number of bits.
The apparatus of any of claims 64-74, wherein the first message comprises a fourth buffer status reporting BSR, and the fourth BSR comprises a logical channel group ID, LCGID, indicating a resource type of resources requested for discovery messages.
The apparatus of claim 75, further comprising:

A processor configured to determine a resource type of a resource requested by the terminal device for the discovery message based on at least one of the pre-configured mappings in response to receiving a fourth BSR comprising an LCGID:

a mapping relationship between a side-link signaling bearer/data bearer, i.e., SL-SRB/DRB, and a logical channel group ID, i.e., LCGID;

mapping relation between SL-SRB/DRB and logic channel;

mapping relation between data packet priority and LCGID; and

mapping relation between data packet priority and logical channel.
The apparatus of any of claims 64-67, wherein the first message comprises a resource scheduling request, SR, requesting resources for discovery messages.
The apparatus of claim 77, wherein the SR is transmitted on a resource corresponding to a scheduling request ID configured by the network device for the terminal device that is dedicated to the terminal device requesting transmission of discovery messages, i.e., a SchedulingRequestID.
The apparatus of any of claims 64-67, wherein the first message comprises side-uplink terminal information to request resources for discovery messages.
The device 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.
The apparatus of any one of claims 64-80, further comprising:

a processor configured to allocate the requested resources for the terminal device in response to receiving the first message.
The apparatus of any one of claims 64-80, further comprising:

a processor configured to configure the terminal device with a sidelink unlicensed transmission resource CG for discovery messages and/or data in response to receiving the first message.
The device of claim 82, wherein the processor indicates whether a sidelink unlicensed transmission resource CG is available for transmitting discovery messages by setting at least one of:

a boolean type indication; and

and a field for indicating a CG type, wherein the CG type indicates whether the corresponding CG is for transmitting a discovery message or for transmitting data.
The device of claim 83, wherein, in response to a discovery message being sent, the terminal device selects a CG that is available for sending the discovery message from the lateral unlicensed transmission resources CG configured by the network device.
A communication device, comprising: a processor and a memory for storing a computer program, the processor for invoking and running the computer program stored in the memory to cause the communication device to perform the method of any of claims 1-42.
A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of any of claims 1-42.
A computer readable storage medium storing a computer program which, when executed by a device, causes the device to perform the method of any one of claims 1-42.
A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 1-42.
A computer program enabling a computer to carry out the method of any one of claims 1-42.
A communication system, comprising:

at least one terminal device configured for performing the side-uplink communication method of any of claims 1-21; and

At least one network device configured for performing the sidelink communication method of any of claims 22-42.