Random access method, resource configuration method, and apparatus

Abstract

The embodiment of the present application provides a kind of random access method, resource configuration method and device;The random access device includes: third receiving unit, it is used to receive the random access preamble that terminal equipment sends on physical random access channel resource;Wherein, the random access preamble is used to indicate that the terminal equipment has sidelink data transmission, and / or the physical random access channel resource is used to indicate that the terminal equipment has sidelink data transmission;Second sending unit, it is used to send random access response to the terminal equipment. By random access process, it indicates that the terminal equipment has sidelink MAC CE to send to network device, to avoid the problem that network device does not know that the terminal equipment has sidelink MAC CE to send, so that network equipment allocates resource for sidelink, and reduce resource consumption.

Description

TECHNICAL FIELD

[0001] Embodiments of the present application relate to the field of communication technology. BACKGROUND

[0002] The automotive communication service, represented by V2X (Vehicle-to-Everything) service, can include multiple types: V2V (Vehicle-to-Vehicle), V2I (Vehicle-to-Infrastructure) and V2P (Vehicle-to-Pedestrian). The V2X service can be provided through the PC5 interface and / or the Uu interface. For the V2X service transmitted through the PC5 interface, V2X sidelink (SL) communication is provided, which is a communication mode in which terminals can directly communicate with each other through the PC5 interface. In Long Term Evolution (LTE) or New Radio (NR), this communication mode is supported when the terminal is within or outside the coverage of the network.

[0003] There are two resource allocation modes in V2X, mode-1 and mode-2. Mode-1 refers to a resource allocation mode in which a network device schedules sidelink resources, and mode-2 refers to a resource allocation mode in which a terminal device autonomously selects resources.

[0004] It should be noted that the above introduction to the technical background is only to facilitate a clear and complete description of the technical solutions of the present application, and to facilitate the understanding of those skilled in the art. The above technical solutions cannot be considered as known to those skilled in the art merely because they are described in the background section of the present application. SUMMARY

[0005] When the terminal device is in mode-1, if the terminal device has a sidelink media access control control element (SL MAC CE) to be transmitted and currently has no available sidelink resources, the terminal device will trigger a scheduling request (SR). Once an SR is triggered, the SR is in a pending state until it is cancelled, and the terminal device is expected to transmit the SR using the SR configuration corresponding to the SL MAC CE, which includes a set of physical uplink control channel (PUCCH) resources.

[0006] For each pending SR, if there is no valid PUCCH resource configured for the SR by the network device, or the number of SR transmission reaches the maximum value, the random access procedure will be initiated. The inventors find that when the terminal device only has a SL MAC CE to be transmitted, if the SR configuration corresponding to the SL MAC CE has no valid PUCCH resource (including the case that no valid PUCCH resource is configured and the PUCCH resource is released due to the timeAlignmentTimer timeout), the random access procedure will be initiated. However, since the current random access procedure cannot distinguish what kind of data the terminal device has to transmit, the network device does not know whether to allocate uplink resources or sidelink resources, or how many resources to allocate.

[0007] In addition, the inventors find that the random access procedure triggered by the SL MAC CE triggered SR reaching the maximum number of SR transmissions, since the time experienced by reaching the maximum number of SR transmissions is relatively long and the terminal device may move at a relatively fast speed, the information carried on the MAC CE, such as channel state information, may have expired, and the reporting of the information may be of little use to the transmitting terminal device.

[0008] To solve at least one of the above problems, embodiments of the present application provide a random access method and device.

[0009] According to an aspect of embodiments of the present application, a random access device is provided, applied to a network device, and the device comprises:

[0010] A third receiving unit is configured to receive a random access preamble transmitted by a terminal device on a physical random access channel resource; wherein the random access preamble is used to indicate that the terminal device has sidelink data to transmit, and / or the physical random access channel resource is used to indicate that the terminal device has sidelink data to transmit;

[0011] A second sending unit is configured to send a random access response to the terminal device.

[0012] According to another aspect of embodiments of the present application, a random access device is provided, applied to a terminal device, and the device comprises:

[0013] A fourth sending unit is configured to send an uplink message including sidelink related information to the network device on a physical uplink data channel in a random access procedure.

[0014] A fourth receiving unit is configured to receive a contention resolution message sent by the network device.

[0015] According to another aspect of embodiments of the present application, a random access device is provided, applied to a network device, and the device comprises:

[0016] a seventh sending unit, configured to send, to the terminal device, a scheduling request configuration corresponding to the sidelink data, the scheduling request configuration comprising a set of physical uplink control channel (PUCCH) resources on a partial bandwidth (BWP);

[0017] a seventh receiving unit, configured to receive the scheduling request sent by the terminal device using the scheduling request configuration.

[0018] One of the beneficial effects of the embodiments of the present application is that, by indicating to the network device that the terminal device has sidelink MAC CEs to send through the random access procedure, or by always sending an SR but not initiating a random access procedure, the problem that the network device does not know that the terminal device has sidelink MAC CEs to send can be avoided, so that the network device allocates resources for sidelink, and resource consumption is reduced, and in addition, the way of not initiating a random access procedure can reduce the occupation of wireless resources by the random access procedure, and improve the utilization rate of wireless resources.

[0019] One of the beneficial effects of the embodiments of the present application is that, by stopping the sending of the SR or canceling the SR when the sending of the SR exceeds the delay limit required by the MAC CE, the random access procedure can be avoided, the network device can be prevented from requesting sidelink resources for transmitting the expired sidelink MAC CE, resource consumption on the Uu interface and the sidelink is reduced, and the utilization rate of wireless resources is improved.

[0020] Specific embodiments of the application are disclosed in detail in the following description and claims, indicating the ways in which the principles of the application can be employed. It should be understood that the embodiments of the application are not limited in scope to the specific embodiments described herein. Embodiments of the application include many changes, modifications and equivalents within the spirit and scope of the appended claims.

[0021] Features described and / or illustrated with respect to one implementation can be used in the same or similar manner in one or more other implementations, in combination with features of other implementations, or in place of features of other implementations.

[0022] It should be emphasized that the term "comprises / comprising" when used in this specification is taken to mean the presence of stated features, integers, steps or components but not the exclusion of one or more other features, integers, steps, components or groups thereof. BRIEF DESCRIPTION OF DRAWINGS

[0023] Elements and features of one or more embodiments of the application described in the present application and / or one drawing can be combined with elements and features of one or more other embodiments and / or drawings. Furthermore, in the drawings, like reference numerals indicate corresponding parts throughout the several views of the drawings. Like reference numerals can be used to indicate corresponding parts in more than one implementation.

[0024] Figure 1 is a schematic diagram of a communication system according to an embodiment of the application;

[0025] Figure 2 is a schematic diagram of a random access method according to an embodiment of the first aspect of the application;

[0026] Figure 3 is a schematic diagram of a 4-step random access procedure according to an embodiment of the application;

[0027] Figure 4 is a schematic diagram of a 2-step random access procedure according to an embodiment of the application;

[0028] Figure 5 is a schematic diagram of a random access method according to an embodiment of the second aspect of the application;

[0029] Figure 6 is a schematic diagram of a random access apparatus according to an embodiment of the third aspect of the application;

[0030] Figure 7 is a schematic diagram of a random access apparatus according to an embodiment of the fourth aspect of the application;

[0031] Figure 8 is a schematic diagram of a random access method according to an embodiment of the fifth aspect of the application;

[0032] Figure 9 is a schematic diagram of a random access method according to an embodiment of the sixth aspect of the application;

[0033] Figure 10 is a schematic diagram of a random access apparatus according to an embodiment of the seventh aspect of the application;

[0034] Figure 11 is a schematic diagram of a random access apparatus according to an embodiment of the eighth aspect of the application;

[0035] Figure 12 is a schematic diagram of a sidelink transmission method according to an embodiment of the ninth aspect of the application;

[0036] Figure 13 is a schematic diagram of a resource configuration method according to an embodiment of the tenth aspect of the application;

[0037] Figure 14 is a schematic diagram of a random access method according to an embodiment of the eleventh aspect of the application;

[0038] Figure 15 is a schematic diagram of a random access method according to an embodiment of the twelfth aspect of the application;

[0039] Figure 16 is a schematic diagram of a scheduling request transmission method according to an embodiment of the thirteenth aspect of the application;

[0040] Figure 17 is a schematic diagram of an edge link transmission device according to an embodiment of the fourteenth aspect of the present application;

[0041] Figure 18 is a schematic diagram of a resource configuration device according to an embodiment of the fifteenth aspect of the present application;

[0042] Figure 19 is a schematic diagram of a random access device according to an embodiment of the sixteenth aspect of the present application;

[0043] Figure 20 is a schematic diagram of a random access device according to an embodiment of the seventeenth aspect of the present application;

[0044] Figure 21 is a schematic diagram of a scheduling request sending device according to an embodiment of the eighteenth aspect of the present application;

[0045] Figure 22 is a schematic diagram of a terminal device according to an embodiment of the nineteenth aspect of the present application;

[0046] Figure 23 is a schematic diagram of a network device according to an embodiment of the twentieth aspect of the present application. DETAILED DESCRIPTION

[0047] The foregoing and other features of the present application will become apparent to those skilled in the art upon consideration of the following detailed description of the application, especially when taken in conjunction with the accompanying drawings and descriptions thereof. In the description of the application and in the claims, the terms "include" and "comprise" are used synonymously with the term "have" or "contain." The term "coupled" is used synonymously with the term "connected." The term "about" is used to indicate approximations and is meant to encompass variations that would be expected by a person of ordinary skill in the art given the content of this disclosure. The terms "first," "second," and the like, do not denote any order, quantity, or importance, but rather are used to distinguish one element from another. The terms "a" and "an" are defined as one or more unless indicated otherwise by the context. The terms "another" and "one or more" are defined as at least a second or at least one unless indicated otherwise by the context. The terms "including," "comprising," "having" and the like are defined as "including" and "comprising" but not "consisting of."

[0048] In the embodiments of the present application, the terms "first", "second", and the like are used to distinguish different elements from each other, but do not indicate spatial arrangement or time sequence of the elements, and the elements should not be limited by these terms. The term "and / or" includes any one and all combinations of the associated listed terms. The terms "include", "comprise", "have" and the like mean the presence of the stated feature, element, component or assembly, but do not exclude the presence or addition of one or more other features, elements, components or assemblies.

[0049] In the embodiments of the present application, the singular forms "a", "an" and "the" include the plural forms unless the context clearly indicates otherwise. The term "said" should be understood to include both the singular and the plural forms unless the context clearly indicates otherwise. In addition, the term "according to" should be understood to mean "at least partially according to", and the term "based on" should be understood to mean "at least partially based on" unless the context clearly indicates otherwise.

[0050] In the embodiments of the present application, the term "communication network" or "wireless communication network" can refer to a network conforming to any communication standard, such as Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), and the like.

[0051] In addition, the communication between devices in the communication system can be performed according to any phase communication protocol, such as can include but is not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G, and 5G, New Radio (NR), and the like, and / or other currently known or to be developed in the future communication protocols.

[0052] In the embodiments of the present application, the term "network device" refers to, for example, a device in a communication system that accesses a terminal device to a communication network and provides services for the terminal device. The network device can include but is not limited to the following devices: base station (BS), access point (AP), transmission reception point (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), and the like.

[0053] Among them, the base station can include but is not limited to: Node B (NodeB or NB), evolved Node B (eNodeB or eNB), and 5G base station (gNB), and the like, in addition to remote radio head (RRH), remote radio unit (RRU), relay or low power node (such as femto, pico, etc.). In addition, the term "base station" can include some or all functions thereof, and each base station can provide communication coverage for a specific geographic area. The term "cell" can refer to a base station and / or its coverage area, depending on the context in which the term is used.

[0054] In the embodiments of the present application, the term "user equipment" (UE) or "terminal equipment" (TE) refers to, for example, a device that accesses a communication network through a network device and receives network services. The terminal equipment can be fixed or mobile, and can also be referred to as a mobile station (MS), a terminal, a subscriber station (SS), an access terminal (AT), a station, and the like.

[0055] The terminal equipment can include, but is not limited to, the following devices: a cellular phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a machine type communication device, a laptop computer, a cordless phone, a smart phone, a smart watch, a digital camera, and the like.

[0056] For another example, in an Internet of Things (IoT) scenario or the like, the terminal equipment can also be a machine or device that performs monitoring or measurement, and can include, but is not limited to, the following devices: a machine type communication (MTC) terminal, a vehicle-mounted communication terminal, a device-to-device (D2D) terminal, a machine-to-machine (M2M) terminal, and the like.

[0057] In addition, the term "network side" or "network device side" refers to the side of the network, which can be a certain base station, or can include one or more network devices as described above. The term "user side" or "terminal side" or "terminal equipment side" refers to the side of the user or terminal, which can be a certain UE, or can include one or more terminal devices as described above. In this document, "device" can refer to a network device or a terminal device unless otherwise specified.

[0058] The following describes the scenarios of the embodiments of the present application by way of example.

[0059] Figure 1 is a schematic diagram of a communication scenario of the embodiments of the present application, which schematically illustrates the case of taking a terminal equipment and a network device as an example, as shown in Figure 1 The communication system 100 can include a network device 101 and terminal equipments 102 and 103. For simplicity, Figure 1 Only two terminal equipments and one network device are taken as an example for description, but the embodiments of the present application are not limited thereto.

[0060] In the embodiments of the present application, the network device 101 and the terminal devices 102 and 103, or between the terminal devices 102 and 103, can perform existing services or future implementable service transmission. For example, these services can include, but are not limited to, enhanced mobile broadband (eMBB), massive machine type communication (mMTC), high reliability and low latency communication (URLLC), and vehicle-to-everything (V2X) communication, etc. The present application takes the uplink or downlink communication of LTE or NR between the network device 101 and the terminal device 102, and the sidelink communication (SL communication) between the terminal device 102 and the terminal device 103 as an example for illustration. Here, the SL communication is, for example, a V2X service related communication.

[0061] Hereinafter, the terminal device that is a sender of service data is referred to as a sending terminal device, which sends sidelink data to one or more other terminal devices (receiving terminal device or destination terminal device).

[0062] The various embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0063] In the embodiments of the present application, the network device can be indicated that the terminal device has sidelink MAC CE to be sent through the random access process, which will be described in conjunction with the embodiments of the first aspect to the eighth aspect.

[0064] Embodiments of the first aspect

[0065] The embodiments of the present application provide a random access method, which is described from the terminal device side. Figure 2 is a schematic diagram of the random access method of the embodiments of the present application, as shown in Figure 2 The method comprises:

[0066] 201, the terminal device selects a random access preamble;

[0067] 202, the terminal device sends the random access preamble to the network device on a physical random access channel resource; wherein the random access preamble is used to indicate that the terminal device has sidelink data to send, and / or the physical random access channel resource is used to indicate that the terminal device has sidelink data to send.

[0068] According to the embodiments of the present application, the network device can be indicated that the terminal device has sidelink MAC CE to be sent through the random access process, which can avoid the problem that the network device does not know that the terminal device has sidelink MAC CE to be sent, so as to allocate resources for sidelink by the network device, and reduce resource consumption.

[0069] It is worth noting that the above-mentioned Figure 2The embodiments of the present application are only illustrative but not limited thereto. For example, the execution order between various operations can be adjusted as appropriate, and in addition, some operations can be added or some operations can be deleted. Those skilled in the art can make appropriate modifications based on the above description, and the modifications are not limited to the above description of the accompanying drawings. Figure 2

[0070] In some embodiments, when the terminal device is in mode-1, if the terminal device has a sidelink medium access control layer control element (SL MAC CE) to be transmitted and currently has no available sidelink resource, the terminal device will trigger a scheduling request (SR). Once an SR is triggered, the SR is in a pending state until it is cancelled, and the terminal device is expected to transmit the SR using the SR configuration corresponding to the SL MAC CE, which includes a set of physical uplink control channel (PUCCH) resources. For each pending SR, if there is no valid PUCCH resource for the SR configuration or the number of SR transmissions reaches a maximum value, the terminal device will initiate a random access procedure. It should be noted that other scenarios that cause the terminal device to initiate a random access procedure also apply to the embodiments of the present application.

[0071] In some embodiments, the random access procedure is a contention-based random access, and for the contention-based random access procedure, it includes a 4-step random access and a 2-step random access, Figure 3 is a schematic diagram of a four-step random access procedure, Figure 4 is a schematic diagram of a two-step access procedure, as Figure 3 shown, in MSG.1, the terminal device sends a random access preamble, in MSG.2, the network device sends a random access response, in MSG.3, the terminal device sends an uplink message on the allocated uplink resource, and in MSG.4, the network device returns a contention resolution message to the terminal device that successfully accesses. As Figure 4 shown, in MSG.A, the terminal device sends a random access preamble and an uplink data on an uplink resource, and in MSG.B, the network device returns a contention resolution message to the terminal device that successfully accesses, which can also carry downlink data and other information.

[0072] ​In some embodiments, whether the terminal device has sidelink data to transmit or has uplink data to transmit can be distinguished by a random access preamble and / or a physical random access channel resource in MSG.1 or MSG.A in a random access procedure. In the above MSG.1 or MSG.A, the terminal device selects a random access preamble in a random access preamble set and a resource in a physical random access channel (PRACH) resource set to transmit the selected random access preamble. The preamble or preamble index or preamble identity in the random access preamble set and / or the resource in the physical random access channel resource set are used to indicate that the terminal device has sidelink data to transmit.

[0073] In some embodiments, the random access preamble set and / or the physical random access channel resource set are configured by the network device, or are preconfigured, or are a default random access preamble set and / or a default physical random access channel resource set configured to indicate that the terminal device has sidelink data to transmit.

[0074] In some embodiments, in the case that the random access preamble set and / or the physical random access channel resource set are configured by the network device, the method further comprises: the terminal device receives the random access preamble set and / or the physical random access channel resource set configured by the network device. For example, when the terminal device is in a radio resource control (RRC) connected state, the network device can configure the random access preamble set and / or the physical random access channel resource set through an RRC reconfiguration message or an RRC re-establishment message; when the terminal device is in an idle or inactive state, the network device can configure the random access preamble set and / or the physical random access channel resource set through an RRC setup message or an RRC resume message or system information (such as SIB1). Wherein, the network device can configure a cell-specific or user-specific random access preamble set and / or a physical random access channel resource set, or configure a synchronization signal block (SSB) or channel state information reference signal (CSI-RS) specific random access preamble set and / or a physical random access channel resource set, and the like.

[0075] In some embodiments, after receiving the random access preamble sent by the terminal device, the network device can determine whether the terminal device has sidelink data to send according to the random access preamble and / or the physical random access channel resource. For example, when the network device determines that the random access preamble is a preamble in the configured, preconfigured, or default set, and / or determines that the physical random access channel resource is a resource in the configured, preconfigured, or default set, the network device determines that the terminal device has sidelink data to send.

[0076] In some embodiments, to support sidelink transmission of the terminal device and accelerate sidelink resource allocation, the method can further include (optional)

[0077] 203. The terminal device receives a random access response sent by the network device, and the random access response contains a sidelink grant.

[0078] In some embodiments, after receiving the random access preamble sent by the terminal device, the network device returns a random access response to the terminal device. For example, the random access response (RAR) can be carried in MSG.2 in Figure 3 or MSG.B in Figure 4 , and the RAR contains a sidelink grant (SLgrant). The sidelink grant can be sent instead of or together with the uplink grant (ULgrant) in the existing RAR. For example, the sidelink grant can be indicated by a reserved bit. When the bit value is 1, it indicates the sidelink grant; when the bit value is 0, it indicates the uplink grant. Conversely, the present embodiment is not limited in this way.

[0079] In some embodiments, after receiving the random access preamble sent by the terminal device, the network device returns a response message (e.g., MSG.2) to the terminal device. The response message can contain a random access preamble identifier (RAPID). When the terminal device receives the RAPID, if the RAPID is the same as the random access preamble identifier sent by the terminal device in MSG.1 or MSG.A or the RAPID belongs to the random access preamble set, the terminal device considers that the random access response is received successfully, the random access procedure is completed successfully, or the sidelink resource allocation is confirmed.

[0080] In some embodiments, the random access response can not contain other fields in the existing RAR, such as the Timing advance control (TAC) field and / or the Temporary Cell-Radio Network Temporary Identifier (Temporary C-RNTI) field.

[0081] In some embodiments, the sidelink data is a sidelink MAC CE, for example, a channel state information reporting MAC CE, but the embodiments are not limited thereto.

[0082] The above embodiments are only exemplary, and the present application is not limited thereto. For example, one or more of the above embodiments can be combined.

[0083] As can be seen from the above embodiments, by indicating to the network device that the terminal device has sidelink MAC CEs to be sent through the random access process, the problem that the network device does not know that the terminal device has sidelink MAC CEs to be sent can be avoided, so that the network device allocates resources for sidelink, and reduces resource consumption.

[0084] Embodiments of the second aspect

[0085] The present application provides a random access method from the network device side, wherein the same content as the embodiments of the first aspect will not be described again.

[0086] Figure 5 is a schematic diagram of the random access method of the present application, as shown in Figure 5 , the method comprises:

[0087] 501, the network device receives a random access preamble sent by a terminal device on a physical random access channel resource; wherein the random access preamble is used to indicate that the terminal device has sidelink data to send, and / or the physical random access channel resource is used to indicate that the terminal device has sidelink data to send;

[0088] 502, the network device sends a random access response to the terminal device.

[0089] According to the present application, by indicating to the network device that the terminal device has sidelink MAC CEs to be sent through the random access process, the problem that the network device does not know that the terminal device has sidelink MAC CEs to be sent can be avoided, so that the network device allocates resources for sidelink, and reduces resource consumption.

[0090] It is worth noting that the above Figure 5 only exemplary description of the embodiments of the present application, but the present application is not limited thereto. For example, the execution order between each operation can be adjusted appropriately, and in addition, some operations can be added or some operations can be reduced. Those skilled in the art can make appropriate modifications based on the above content, and the present application is not limited to the above Figure 5 .

[0091] In some embodiments, the terminal device selects a random access preamble in a set of random access preambles and a resource in a set of physical random access channel resources to transmit the selected random access preamble. The preamble or preamble index or preamble identity in the set of random access preambles or the resource in the set of physical random access channel resources is used to indicate that the terminal device has sidelink data to transmit.

[0092] In some embodiments, the set of random access preambles and / or the set of physical random access channel resources is configured by the network device, or is preconfigured, or is a default set of random access preambles and / or a default set of physical random access channel resources used to indicate that the terminal device has sidelink data to transmit.

[0093] In some embodiments, upon receiving the random access preamble transmitted by the terminal device, the network device can determine whether the terminal device has sidelink data to transmit according to the random access preamble and / or the physical random access channel resource, e.g., the network device determines that the terminal device has sidelink data to transmit when it determines that the random access preamble is a preamble in the above-mentioned configured, or preconfigured, or default set of random access preambles and / or the physical random access channel resource is a resource in the above-mentioned configured, or preconfigured, or default set of physical random access channel resources.

[0094] In some embodiments, in the case that the set of random access preambles and / or the set of physical random access channel resources is configured by the network device, the method further comprises:

[0095] 500, the network device configures a set of random access preambles and / or a set of physical random access channel resources; and transmits the configured set of random access preambles and / or the set of physical random access channel resources to the terminal device;

[0096] In some embodiments, upon receiving the random access preamble transmitted by the terminal device, the network device returns a random access response to the terminal device, e.g., the random access response (RAR) can be carried by MSG.2 in Figure 3 or MSG.B in Figure 4 .

[0097] To support sidelink transmission of the terminal device and accelerate sidelink resource allocation, the random access response can further include a sidelink grant (SL grant) which can replace the uplink grant (UL grant) in the existing RAR or be sent together with the uplink grant in the existing RAR. For example, the sidelink grant can be indicated by a reserved bit, where a bit value of 1 indicates the sidelink grant and a bit value of 0 indicates the uplink grant, or vice versa. Alternatively, the sidelink grant and the uplink grant can be indicated by the reserved bit, where a bit value of 1 indicates that the sidelink grant and the uplink grant are included in the RAR, and a bit value of 0 indicates that only the uplink grant is included in the RAR, or vice versa. The embodiments are not limited in this regard.

[0098] In some embodiments, the random access response can not include other fields in the existing RAR, such as a time advance control (TAC) field and / or a temporary cell radio network temporary identifier (Temporary C-RNTI) field.

[0099] In some embodiments, after receiving the random access preamble, the network device returns a response message (e.g., MSG.2) which can include a random access preamble identifier (RAPID). If the RAPID received by the terminal device is the same as the random access preamble identifier sent by the terminal device in MSG.1 or MSG.A or the RAPID belongs to the random access preamble set, the terminal device considers that the random access response is successfully received or the random access procedure is successfully completed or the sidelink resource allocation is confirmed.

[0100] In some embodiments, the sidelink data described above is a sidelink MAC CE, such as a channel state information reporting (CSI reporting) MAC CE, but the embodiments are not limited in this regard.

[0101] The above embodiments are only exemplary and the present application is not limited thereto. For example, the above embodiments can be used alone or in combination.

[0102] As can be seen from the above embodiments, the terminal device indicates to the network device that there is sidelink MAC CE to be sent through the random access procedure, which can avoid the problem that the network device does not know that there is sidelink MAC CE to be sent by the terminal device, so as to allocate resources for the sidelink and reduce resource consumption.

[0103] Embodiments of the third aspect

[0104] Embodiments of the present application provide a random access apparatus. The apparatus may, for example, be a terminal device (such as the terminal device described above), or one or more components or elements configured in a terminal device. The same content as the embodiments of the first aspect will not be described again.

[0105] Figure 6 is a schematic diagram of a random access apparatus according to an embodiment of the present application. In some embodiments, as shown in Figure 6 the random access apparatus 600 comprises:

[0106] a selection unit 601 configured to select a random access preamble;

[0107] a first sending unit 602 configured to send the random access preamble to a network device on a physical random access channel resource; wherein the random access preamble is used to indicate that the terminal device has sidelink data to send, and / or the physical random access channel resource is used to indicate that the terminal device has sidelink data to send.

[0108] According to embodiments of the present application, the network device can be indicated that the terminal device has sidelink MAC CE to send through the random access procedure, which can avoid the problem that the network device does not know that the terminal device has sidelink MAC CE to send, so as to allocate resources for sidelink by the network device, and reduce resource consumption.

[0109] In some embodiments, the random access preamble and / or the physical random access channel resource in MSG.1 or MSG.A in the random access procedure can be used to distinguish whether the terminal device has sidelink data to send or has uplink data to send. In MSG.1 or MSG.A as described in the first aspect, the selection unit 601 selects a random access preamble in a random access preamble set and a resource in a physical random access channel resource set to send the selected random access preamble. The preamble or preamble index or preamble identifier in the random access preamble set is used to indicate that the terminal device has sidelink data to send, and / or the resource in the physical random access channel resource set is used to indicate that the terminal device has sidelink data to send.

[0110] In some embodiments, the random access preamble set and / or the physical random access channel resource set is configured by the network device, or is preconfigured, or is a default random access preamble set and / or a default physical random access channel resource set used to indicate that the terminal device has sidelink data to send.

[0111] In some embodiments, in the case that the random access preamble set and / or the physical random access channel resource set is configured by the network device, the apparatus further comprises (optionally) a second receiving unit (not shown) configured to receive the random access preamble set and / or the physical random access channel resource set configured by the network device.

[0112] For example, when the terminal device is in a Radio Resource Control (RRC) connection state, the second receiving unit can receive the random access preamble set and / or the physical random access channel resource set through an RRC reconfiguration message or an RRC re-establishment message; when the terminal device is in an idle or inactive state, the second receiving unit can receive the random access preamble set and / or the physical random access channel resource set through an RRC setup message, an RRC resume message, or system information (e.g., SIB1). The network device can configure the random access preamble set and / or the physical random access channel resource set as cell-specific or user-specific, or it can configure the random access preamble set and / or the physical random access channel resource set as specific to the Synchronization Signal and PBCH block (SSB) or the Channel State Information Reference Signal (CSI-RS), etc.

[0113] In some embodiments, to support sidelink transmission of terminal devices and accelerate sidelink resource allocation, the apparatus may further include: (optional)

[0114] The first receiving unit 603 is used to receive a random access response sent by the network device, the random access response containing a side link grant.

[0115] In some embodiments, after the network device receives the random access preamble sent by the terminal device, it returns a random access response to the terminal device, for example, through... Figure 3 MSG.2 or Figure 4 The MSG.B in the document carries the Random Access Response (RAR), which includes a sidelink grant (SLgrant). This SLgrant can replace the uplink grant (ULgrant) in the existing RAR or be sent together with the uplink grant in the existing RAR. For example, the sidelink grant can be indicated by a reserved bit, where a bit value of 1 indicates a sidelink grant and a bit value of 0 indicates an uplink grant, and vice versa. Alternatively, the reserved bit can indicate whether the RAR includes both sidelink grant and uplink grant, where a bit value of 1 indicates both sidelink grant and uplink grant are included, and a bit value of 0 indicates only uplink grant is included, and vice versa. This embodiment is not intended to limit the scope of the RAR.

[0116] In some embodiments, after the network device receives the random access preamble sent by the terminal device, a response message (e.g., MSG.2) can be returned to the terminal device, which can contain a random access preamble identifier (RAPID). If the RAPID is the same as the random access preamble identifier sent by the terminal device in MSG.1 or MSG.A or the RAPID belongs to the random access preamble set, the terminal device considers that the random access response is received successfully or the random access procedure is completed successfully or the sidelink resource allocation confirmation is received.

[0117] In some embodiments, the random access response can not contain other domains in the existing RAR, such as a time advance control (TAC) domain and / or a temporary cell radio network temporary identifier (Temporary C-RNTI) domain.

[0118] In some embodiments, the sidelink data described above is a sidelink MAC CE, such as a channel state information reporting MAC CE, but the present application is not limited thereto.

[0119] The above embodiments are only exemplary descriptions of the embodiments of the present application, but the present application is not limited thereto, and appropriate modifications can be made on the basis of the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0120] It should be noted that the above only describes the components or modules related to the present application, but the present application is not limited thereto. The random access device 600 can also include other components or modules, and the specific content of these components or modules can be referred to related technologies.

[0121] In addition, for the sake of simplicity, Figure 6 The connection relationship or signal path between the components or modules in the above is only exemplary, but those skilled in the art should understand that various related technologies such as bus connection can be used. The above components or modules can be implemented by hardware facilities such as processors, memories, transmitters, receivers, etc.; the present application is not limited thereto.

[0122] As can be seen from the above embodiments, by indicating to the network device through the random access procedure that the terminal device has sidelink MAC CEs to send, the problem that the network device does not know that the terminal device has sidelink MAC CEs to send can be avoided, so that the network device can allocate resources for sidelink and reduce resource consumption.

[0123] Embodiments of the fourth aspect

[0124] The embodiment of the present application provides a random access device. The device can be a network device (for example, the network device described above), or can be one or more components or assemblies configured in the network device. The same content as the embodiment of the second aspect will not be described herein.

[0125] Figure 7 is a schematic diagram of the random access device of the embodiment of the present application. In some embodiments, as shown in Figure 7 the random access device 700 includes:

[0126] a third receiving unit 701, configured to receive a random access preamble sent by a terminal device on a physical random access channel resource; wherein the random access preamble is used to indicate that the terminal device has sidelink data to send, and / or the physical random access channel resource is used to indicate that the terminal device has sidelink data to send;

[0127] a second sending unit 702, configured to send a random access response to the terminal device.

[0128] According to the embodiment of the present application, the network device is indicated that the terminal device has sidelink MAC CE to send through the random access process, which can avoid the problem that the network device does not know that the terminal device has sidelink MAC CE to send, so as to allocate resources for the sidelink by the network device, and reduce resource consumption.

[0129] In some embodiments, the random access preamble set and / or the physical random access channel resource set is a random access preamble set and / or a physical random access channel resource set configured by the network device, or preconfigured, or default for indicating that the terminal device has sidelink data to send.

[0130] In some embodiments, after receiving the random access preamble sent by the terminal device, the network device can determine whether the terminal device has sidelink data to send according to the random access preamble and / or the physical random access channel resource. For example, when the network device determines that the random access preamble is a preamble in the set configured by the network device, or preconfigured, or default, and / or determines that the physical random access channel resource is a resource in the set configured by the network device, or preconfigured, or default, it is determined that the terminal device has sidelink data to send.

[0131] In some embodiments, in the case that the random access preamble set and / or the physical random access channel resource set is configured by the network device, the device further includes: (optional, not shown)

[0132] a configuration unit, configured to configure the random access preamble set and / or the physical random access channel resource set;

[0133] a third sending unit, configured to send the configured set of random access preambles and / or the set of physical random access channel resources to the terminal device.

[0134] For example, when the terminal device is in a radio resource control (RRC) connected state, the third sending unit can send the set of random access preambles and / or the set of physical random access channel resources through an RRC reconfiguration message or an RRC re-establishment message; when the terminal device is in an idle or inactive state, the third sending unit can send the set of random access preambles and / or the set of physical random access channel resources through an RRC setup message or an RRC resume message or system information (e.g., SIB1). The configuration unit can configure the set of random access preambles and / or the set of physical random access channel resources to be cell-specific or user-specific, or to be specific to a synchronization signal block (SSB) or a channel state information reference signal (CSI-RS), and the like.

[0135] In some embodiments, after the network device receives the random access preamble sent by the terminal device, the second sending unit 702 returns a random access response to the terminal device, which can be carried in MSG.2 in Figure 3 or MSG.B in Figure 4 .

[0136] To support sidelink transmission of the terminal device and speed up sidelink resource allocation, the random access response contains a sidelink grant (SL grant), which can replace the uplink grant (UL grant) in the existing RAR or be sent together with the uplink grant in the existing RAR, for example, the sidelink grant can be indicated by a reserved bit, where a bit value of 1 indicates a sidelink grant and a bit value of 0 indicates an uplink grant, or vice versa, or the sidelink grant and the uplink grant can be indicated by a reserved bit, where a bit value of 1 indicates that the sidelink grant and the uplink grant are included in the RAR, and a bit value of 0 indicates that only the uplink grant is included in the RAR, or vice versa, which is not limited in the present embodiment.

[0137] In some embodiments, the random access response can not contain other domains in the existing RAR, for example, a time advance control (TAC) domain and / or a temporary wireless network temporary identifier (Temporary C-RNTI) domain.

[0138] In some embodiments, after receiving the random access preamble, the second sending unit 702 returns a response message (e.g., MSG.2), which can include a random access preamble identifier (RAPID). If the RAPID is the same as the random access preamble identifier sent by the terminal device in MSG.1 or MSG.A or the RAPID belongs to the random access preamble set, the terminal device considers that the random access response is received successfully or the random access process is completed successfully or the sidelink resource allocation confirmation is received.

[0139] The above embodiments are only exemplary and the present application is not limited thereto. For example, one or more of the above embodiments can be combined.

[0140] It should be noted that the above only illustrates the components or modules related to the present application, but the present application is not limited thereto. The random access apparatus 700 can also include other components or modules, and the specific content of these components or modules can be referred to the related art.

[0141] In addition, for simplicity, Figure 7 The connection relationship or signal path between the components or modules is only exemplary, but those skilled in the art should understand that various related technologies such as bus connection can be used. The above components or modules can be implemented by hardware facilities such as processors, memories, transmitters, receivers, etc., and the present application is not limited thereto.

[0142] As can be seen from the above embodiments, by indicating to the network device through the random access process that the terminal device has sidelink MAC CEs to send, the problem that the network device does not know that the terminal device has sidelink MAC CEs to send can be avoided, so that the network device can allocate resources for sidelink and reduce resource consumption.

[0143] Embodiments of the fifth aspect

[0144] The present application provides a random access method from the terminal device side. Figure 8 is a schematic diagram of the random access method of the present application, as Figure 8 shown, the method comprises:

[0145] 801, in the random access process, the terminal device sends an uplink message to the network device on the physical uplink data channel, and the uplink message includes sidelink related information;

[0146] 802, the terminal device receives the contention resolution message sent by the network device.

[0147] According to the embodiments of the present application, the network device can be indicated that the terminal device has sidelink MAC CEs to be transmitted through the random access procedure, so that the network device can timely allocate resources for the sidelink and reduce resource consumption.

[0148] It should be noted that the above-mentioned Figure 8 The embodiments of the present application are only illustrative, but the present application is not limited thereto. For example, the execution order between the operations can be appropriately adjusted, and in addition, some operations can be added or some operations can be reduced. Those skilled in the art can make appropriate modifications based on the above description, and the present application is not limited to the above-mentioned Figure 8 description.

[0149] In some embodiments, when the terminal device is in mode-1, if the terminal device has sidelink medium access control layer control elements (SL MAC CEs) to be transmitted and currently has no available sidelink resources, the terminal device will trigger a scheduling request (SR). Once an SR is triggered, the SR is in a pending state until it is cancelled, and the terminal device is expected to transmit the SR using the SR configuration corresponding to the SL MAC CE, which includes a set of physical uplink control channel (PUCCH) resources. For each pending SR, if there is no valid PUCCH resource for the SR configuration, or the number of SR transmissions reaches a maximum value, the terminal device will initiate a random access procedure. It should be noted that the scenarios that cause the terminal device to initiate a random access procedure also apply to the embodiments of the present application in other scenarios.

[0150] In some embodiments, the random access procedure is a contention-based random access, and for the contention-based random access procedure, it includes a four-step random access and a two-step random access, Figure 3 is a four-step random access procedure diagram, Figure 4 is a two-step access procedure diagram, as Figure 3 shown, in MSG.1, the terminal device sends a random access preamble, in MSG.2, the network device sends a random access response, in MSG.3, the terminal device sends an uplink message on the allocated uplink resource, and in MSG.4, the network device returns a contention resolution message to the terminal device that successfully accesses. As Figure 4 shown, in MSG.A, the terminal device sends a random access preamble and an uplink data on an uplink resource, and in MSG.B, the network device returns a contention resolution message to the terminal device that successfully accesses, which can also carry downlink data and other information.

[0151] In some embodiments, whether the terminal device has sidelink data to send or uplink data to send can be distinguished by whether there is sidelink related information on the PUSCH in MSG.3 or MSG.A in the random access procedure, i.e., the terminal device sends an uplink message to the network device on the physical uplink data channel (PUSCH), i.e., sends the above-mentioned MSG.3 or MSG.A on the PUSCH, and the MSG.3 or MSG.A includes sidelink related information; the sidelink related information is used to indicate that the terminal device has sidelink data to send. The above-mentioned sidelink data can be a sidelink MAC CE, such as a channel state information reporting MAC CE, but the present embodiment is not limited thereto.

[0152] In some embodiments, the sidelink related information is a sidelink buffer status report, which is used to indicate the logical channel group and / or buffer size corresponding to the sidelink data (e.g., SL MAC CE). In other words, the SL MAC CE can also trigger a sidelink buffer status report, and the SL BSR is used to report the identification (or index) of the logical channel group corresponding to the sidelink MAC CE (e.g., sidelink CSI reporting MAC CE) and / or the corresponding buffer status information, for example, the logical channel group identification corresponding to the sidelink CSI reporting MAC CE is a fixed value, e.g., 8, and the corresponding buffer size is 1. The terminal device carries the SL BSR in MSG.3 or MSG.A of the random access procedure and sends it to the network device. The network device can determine how much sidelink data the terminal device needs to send according to the SL BSR, i.e., can allocate corresponding sidelink resources to the terminal device.

[0153] In some embodiments, the sidelink related information is a logical channel identification (LCID) corresponding to the sidelink data (e.g., SL MAC CE), e.g., taking a value of one of 33-48. The terminal device can include the LCID in the MAC subheader of the uplink MAC sub-protocol data unit (PDU). The terminal device carries the MAC sub-PDU in MSG.3 or MSG.A of the random access procedure and sends it to the network device. The network device can determine that the terminal device has sidelink data to send according to the LCID, i.e., can allocate corresponding sidelink resources to the terminal device.

[0154] In some embodiments, the sidelink-related information is a sidelink RNTI of the terminal device, and the terminal device carries the SL-RNTI through MSG.3 or MSG.A of the random access procedure, for example, a SL-RNTI MAC CE with a predefined LCID can be sent to the network device, and the network device can determine that the terminal device has sidelink data to send according to the SL-RNTI, i.e., can allocate corresponding sidelink resources to the terminal device.

[0155] In some embodiments, the uplink message can also include a C-RNTI of the terminal device for contention resolution of the random access.

[0156] In some embodiments, the terminal device receives the contention resolution message MSG.4 or MSG.B sent by the network device, for example, the network device can scramble the physical downlink control channel of MSG.4 or MSG.B using the C-RNTI, and the terminal device decodes the physical downlink control channel (PDCCH) addressed to its own C-RNTI to indicate that the contention resolution is completed. The network device can allocate sidelink resources (i.e., carry the SL grant) through the PDCCH addressed to the SL-RNTI of the terminal device, and the terminal device sends the sidelink data using the allocated sidelink resources.

[0157] The above embodiments are only exemplary, but the present application is not limited thereto, and can be appropriately modified on the basis of the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined, for example, the first aspect embodiment can be combined with the fifth aspect embodiment, or can be used alone.

[0158] As can be seen from the above embodiments, by indicating to the network device through the random access procedure that the terminal device has sidelink MAC CEs to send, the problem that the network device does not know that the terminal device has sidelink MAC CEs to send can be avoided, so that the network device can timely allocate resources for the sidelink, and resource consumption is reduced.

[0159] Embodiment of the sixth aspect

[0160] The embodiment of the present application provides a random access method, which is described from the network device side. The same content as the embodiment of the fifth aspect will not be described again.

[0161] Figure 9 is a schematic diagram of the random access method of the embodiment of the present application, as Figure 9 shown, the method comprises:

[0162] 901, the network device receives the uplink message sent by the terminal device on the physical uplink data channel, and the uplink message includes sidelink-related information;

[0163] 902, the network device sends a contention resolution message to the terminal device.

[0164] According to the embodiments of the present application, the terminal device indicates to the network device that it has sidelink MAC CEs to send through the random access process, which can avoid the problem that the network device does not know that the terminal device has sidelink MAC CEs to send, so that the network device can timely allocate resources for sidelink, and reduce resource consumption.

[0165] It is worth noting that the above-mentioned Figure 9 The embodiments of the present application are only schematically described, but the present application is not limited thereto. For example, the execution order between the operations can be appropriately adjusted, and in addition, some operations can be added or some operations can be reduced. Those skilled in the art can make appropriate modifications based on the above description, and the present application is not limited to the above-mentioned Figure 9 description.

[0166] In some embodiments, whether the terminal device has sidelink data to send or uplink data to send can be distinguished by whether there is sidelink related information on the physical uplink data channel (PUSCH) in MSG.3 or MSG.A in the random access process, i.e., the network device receives the uplink message sent by the terminal device on the physical uplink data channel (PUSCH), i.e., sends the above-mentioned MSG.3 or MSG.A on the PUSCH, and the MSG.3 or MSG.A includes sidelink related information; the sidelink related information is used to indicate that the terminal device has sidelink data to send. The above-mentioned sidelink data can be sidelink MAC CE, such as channel state information reporting MAC CE, but the present embodiment is not limited thereto.

[0167] In some embodiments, the sidelink related information is a sidelink buffer status report, which is used to indicate the logical channel group and / or buffer size corresponding to the sidelink data (such as SL MAC CE). In other words, the SL MAC CE can also trigger the sidelink buffer status report, and the SL BSR is used to report the identification (or index) of the logical channel group corresponding to the sidelink MAC CE (such as sidelink CSI reporting MAC CE) and the corresponding buffer status information, for example, the logical channel group identification corresponding to the sidelink CSI reporting MAC CE is a fixed value, such as 8, and the corresponding buffer size is 1. The terminal device carries the SL BSR through MSG.3 or MSG.A of the random access process and sends it to the network device, and the network device can determine how much sidelink data the terminal device needs to send according to the SL BSR, i.e., can allocate corresponding sidelink resources to the terminal device.

[0168] In some embodiments, the sidelink related information is a logical channel identifier (LCID) corresponding to the sidelink data (e.g., SL MAC CE), such as a value of one of 33-48. The terminal device can include the LCID in a MAC subheader of an uplink MAC sub-protocol data unit (PDU). The terminal device transmits the MAC sub-PDU to the network device through MSG.3 or MSG.A of the random access procedure, and the network device can determine that the terminal device has sidelink data to be transmitted according to the LCID, i.e., can allocate corresponding sidelink resources to the terminal device.

[0169] In some embodiments, the sidelink related information is a sidelink RNTI of the terminal device. The terminal device transmits the SL-RNTI to the network device through MSG.3 or MSG.A of the random access procedure, such as a SL-RNTI MAC CE with a predefined LCID. The network device can determine that the terminal device has sidelink data to be transmitted according to the SL-RNTI, i.e., can allocate corresponding sidelink resources to the terminal device.

[0170] In some embodiments, the uplink message can further include a C-RNTI of the terminal device, for contention resolution of the random access.

[0171] In some embodiments, the network device transmits a contention resolution message, i.e., MSG.4 or MSG.B, to the terminal device. For example, the network device can scramble the physical downlink control channel of MSG.4 or MSG.B using the C-RNTI, and the terminal device decodes the PDCCH addressed to its own C-RNTI to indicate that the contention resolution is completed. The network device can allocate sidelink resources (i.e., carry the SL grant) through the PDCCH addressed to the SL-RNTI of the terminal device, and the terminal device transmits sidelink data using the allocated sidelink resources.

[0172] The above embodiments are only exemplary, but the present application is not limited thereto, and can be appropriately modified on the basis of the above embodiments. For example, the above embodiments can be used alone or in combination, such as the combination of the second aspect and the sixth aspect, or alone.

[0173] As can be seen from the above embodiments, the terminal device indicates to the network device that it has sidelink MAC CEs to be transmitted through the random access procedure, which can avoid the problem that the network device does not know that the terminal device has sidelink MAC CEs to be transmitted, so that the network device can timely allocate resources for sidelink and reduce resource consumption.

[0174] Embodiments of the seventh aspect

[0175] Embodiments of the present application provide a random access device. The device may, for example, be a terminal device (such as the terminal device described above), or one or more components or assemblies configured in a terminal device. The same content as the embodiments of the fifth aspect will not be described again.

[0176] Figure 10 is a schematic diagram of a random access device according to an embodiment of the present application. In some embodiments, as shown in Figure 10 the random access device 1000 comprises:

[0177] a fourth sending unit 1001 configured to send an uplink message to the network device on a physical uplink data channel in a random access process, the uplink message comprising sidelink-related information;

[0178] a fourth receiving unit 1002 configured to receive a contention resolution message sent by the network device.

[0179] According to embodiments of the present application, the network device is indicated that the terminal device has sidelink MAC CE to send through the random access process, which can avoid the problem that the network device does not know that the terminal device has sidelink MAC CE to send, so as to allocate resources for the sidelink in time and reduce resource consumption.

[0180] In some embodiments, whether the terminal device has sidelink data to send or uplink data to send can be distinguished by whether there is sidelink-related information on the physical uplink data channel (PUSCH) in MSG.3 or MSG.A in the random access process described in the first aspect, i.e., the fourth sending unit 1001 sends an uplink message to the network device on the physical uplink data channel (PUSCH), i.e., sends the above-mentioned MSG.3 or MSG.A on the PUSCH, and the MSG.3 or MSG.A comprises sidelink-related information; the sidelink-related information is used to indicate that the terminal device has sidelink data to send. The above-mentioned sidelink data can be sidelink MAC CE, such as channel state information reporting MAC CE, but the embodiments are not limited thereto.

[0181] In some embodiments, the sidelink related information is a sidelink buffer status report, which is used to indicate the logical channel group and / or buffer size corresponding to the sidelink data (e.g., SL MAC CE). In other words, the SL MAC CE can also trigger a sidelink buffer status report, which is used to report the identification (or index) of the logical channel group and the corresponding buffer status information corresponding to the sidelink MAC CE (e.g., sidelink CSI reporting MAC CE). For example, the sidelink CSI reporting MAC CE corresponds to a fixed value of the logical channel group identification, e.g., 8, and the corresponding buffer size is 1. The terminal device carries the SL BSR in MSG.3 or MSG.A of the random access procedure and sends it to the network device. The network device can determine how much sidelink data the terminal device needs to send according to the SL BSR, i.e., can allocate corresponding sidelink resources to the terminal device.

[0182] In some embodiments, the sidelink related information is the logical channel identification (LCID) corresponding to the sidelink data (e.g., SL MAC CE), e.g., taking a value of one of 33-48. The terminal device can include the LCID in the MAC subheader of the uplink MAC sub-protocol data unit (PDU). The terminal device carries the MAC sub-PDU in MSG.3 or MSG.A of the random access procedure and sends it to the network device. The network device can determine that the terminal device has sidelink data to send according to the LCID, i.e., can allocate corresponding sidelink resources to the terminal device.

[0183] In some embodiments, the sidelink related information is the sidelink RNTI of the terminal device. The terminal device carries the SL-RNTI in MSG.3 or MSG.A of the random access procedure, e.g., can send the SL-RNTI MAC CE with a predefined LCID to the network device. The network device can determine that the terminal device has sidelink data to send according to the SL-RNTI, i.e., can allocate corresponding sidelink resources to the terminal device.

[0184] In some embodiments, the uplink message can also include the C-RNTI of the terminal device, which is used for contention resolution of random access.

[0185] In some embodiments, the fourth receiving unit 1002 receives the contention resolution message MSG.4 or MSG.B sent by the network device. For example, the network device can scramble the physical downlink control channel of MSG.4 or MSG.B using the C-RNTI, and the terminal device decodes the PDCCH addressed by the C-RNTI to indicate that the contention resolution is completed. The network device can allocate sidelink resources (i.e., carry the SL grant) by using the PDCCH addressed by the SL-RNTI of the terminal device, and the terminal device sends the sidelink data using the allocated sidelink resources.

[0186] The above embodiments are only exemplary and the present application is not limited thereto. For example, one or more of the above embodiments can be combined.

[0187] It should be noted that the above only illustrates the components or modules related to the present application, but the present application is not limited thereto. The random access apparatus 1000 can further include other components or modules, and the specific content of these components or modules can be referred to the related art.

[0188] In addition, for simplicity, Figure 10 The connection relationship or signal transmission between the components or modules is only exemplary, but those skilled in the art should understand that various related technologies such as bus connection can be used. The above components or modules can be implemented by hardware facilities such as processors, memories, transmitters, receivers, etc., and the present application is not limited thereto.

[0189] As can be seen from the above embodiments, by indicating to the network device that the terminal device has sidelink MAC CEs to be sent through the random access process, the problem that the network device does not know that the terminal device has sidelink MAC CEs to be sent can be avoided, so that the network device can timely allocate resources for the sidelink, and the resource consumption is reduced.

[0190] Embodiments of the eighth aspect

[0191] The present application provides a random access apparatus. The apparatus can be a network device (such as the network device described above), or can be one or more components or modules configured in the network device. The same content as the embodiments of the sixth aspect will not be described again.

[0192] Figure 11 is a schematic diagram of the random access apparatus of the present application. In some embodiments, as shown in Figure 11 The random access apparatus 1100 includes:

[0193] a fifth receiving unit 1101, configured to receive an uplink message sent by the terminal device on a physical uplink data channel, the uplink message comprising sidelink-related information;

[0194] a fifth sending unit 1102, configured to send a contention resolution message to the terminal device.

[0195] According to the embodiments of the present application, the network device is indicated that the terminal device has sidelink MAC CE to send through the random access process, which can avoid the problem that the network device does not know that the terminal device has sidelink MAC CE to send, so as to allocate resources for sidelink in time and reduce resource consumption.

[0196] In some embodiments, whether the terminal device has sidelink data to send or uplink data to send can be distinguished by whether there is sidelink-related information on the physical uplink data channel (PUSCH) in MSG.3 or MSG.A in the random access process, i.e., the fifth receiving unit 1101 receives the uplink message sent by the terminal device on the physical uplink data channel (PUSCH), i.e., sends the above-mentioned MSG.3 or MSG.A on the PUSCH, and the MSG.3 or MSG.A comprises sidelink-related information; the sidelink-related information is used to indicate that the terminal device has sidelink data to send. The above-mentioned sidelink data can be sidelink MAC CE, such as channel state information reporting MAC CE, but the embodiments are not limited thereto.

[0197] In some embodiments, the sidelink-related information is a sidelink buffer status report, which is used to indicate the logical channel group and / or buffer size corresponding to the sidelink data (such as SL MAC CE). In other words, the SL MAC CE can also trigger the sidelink buffer status report, and the SL BSR is used to report the identification (or index) of the logical channel group corresponding to the sidelink MAC CE (such as sidelink CSI reporting MAC CE) and the corresponding buffer status information, for example, the logical channel group identification corresponding to the sidelink CSI reporting MAC CE is a fixed value, such as 8, and the corresponding buffer size is 1. The terminal device carries the SL BSR through MSG.3 or MSG.A of the random access process and sends it to the network device. The network device can determine how much sidelink data the terminal device needs to send according to the SL BSR, i.e., can allocate corresponding sidelink resources to the terminal device.

[0198] In some embodiments, the sidelink related information is a logical channel identifier (LCID) corresponding to the sidelink data (e.g., SL MAC CE), such as a value of one of 33-48. The terminal device can include the LCID in a MAC subheader of an uplink MAC sub-protocol data unit (PDU). The terminal device transmits the MAC sub-PDU to the network device through MSG.3 or MSG.A of the random access procedure, and the network device can determine that the terminal device has sidelink data to transmit according to the LCID, i.e., can allocate corresponding sidelink resources to the terminal device.

[0199] In some embodiments, the sidelink related information is a sidelink RNTI of the terminal device. The terminal device transmits the SL-RNTI to the network device through MSG.3 or MSG.A of the random access procedure, such as a SL-RNTI MAC CE with a predefined LCID. The network device can determine that the terminal device has sidelink data to transmit according to the SL-RNTI, i.e., can allocate corresponding sidelink resources to the terminal device.

[0200] In some embodiments, the uplink message can further include a C-RNTI of the terminal device, for contention resolution of the random access.

[0201] In some embodiments, the fifth sending unit 1102 sends a contention resolution message, i.e., MSG.4 or MSG.B, to the terminal device. For example, the network device can scramble the physical downlink control channel of MSG.4 or MSG.B using the C-RNTI, and the terminal device decodes the PDCCH addressed to its own C-RNTI to indicate that the contention resolution is completed. The network device can allocate sidelink resources (i.e., carry the SL grant) through the PDCCH addressed to the SL-RNTI of the terminal device, and the terminal device transmits sidelink data using the allocated sidelink resources.

[0202] The above embodiments are only exemplary and the present application is not limited thereto. For example, one or more of the above embodiments can be combined.

[0203] It should be noted that the above only describes the components or modules related to the present application, but the present application is not limited thereto. The random access apparatus 1100 can further include other components or modules, and the specific content of these components or modules can be referred to the related art.

[0204] In addition, for simplicity, Figure 11The connection relationship or signal direction between each component or module is only exemplarily shown, but it should be understood by those skilled in the art that various related technologies such as bus connection can be adopted. The above-mentioned components or modules can be realized by hardware facilities such as processors, memories, transmitters, receivers, etc.; the present application does not limit this.

[0205] As can be seen from the above embodiments, by indicating to the network device through the random access process that the terminal device has sidelink MAC CEs to be sent, the problem that the network device does not know that the terminal device has sidelink MAC CEs to be sent can be avoided, so that the network device can timely allocate resources for the sidelink, and resource consumption is reduced.

[0206] In the embodiments of the present application, for the SR triggered by the SL MAC CE without a valid PUCCH resource or the random access process triggered by reaching the maximum number of SR transmissions, by always initiating the SR but not initiating the random access process, the problem that the network device does not know that the terminal device has sidelink MAC CEs to be sent can be avoided, so that the network device can allocate resources for the sidelink, and resource consumption is reduced. In addition, the way of not initiating the random access process can reduce the occupation of wireless resources by the random access process, and improve the utilization rate of wireless resources. The following will be described in combination with the embodiments of the ninth aspect to the eighteenth aspect.

[0207] Embodiments of the ninth aspect

[0208] The embodiments of the present application provide a sidelink transmission method, which is described from the terminal device side, Figure 12 is a schematic diagram of the sidelink transmission method of the embodiments of the present application, as Figure 12 shown, the method comprises:

[0209] 1201, the terminal device receives the scheduling request configuration corresponding to the sidelink data sent by the network device, the scheduling request configuration comprising a set of PUCCH resources on a partial bandwidth BWP (Bandwidth Part);

[0210] 1202, when the terminal device has sidelink data to be sent and currently has no available sidelink resource, triggering a scheduling request;

[0211] 1203, the terminal device sends the scheduling request using the PUCCH resource corresponding to the scheduling request configuration.

[0212] According to the above embodiments, on the uplink bandwidth part (BWP) configured for the terminal device, the terminal device is configured with PUCCH resources belonging to the SR configuration, thus in the case that the time alignment timer (TimeAlignmentTimer) does not expire, when the SR is triggered, the terminal device has the PUCCH resources corresponding to the SR configuration in the currently activated uplink BWP, thus ensuring that the random access procedure is not initiated due to the lack of valid PUCCH resources for the SR, reducing the occupation of wireless resources by the random access procedure, and improving the utilization rate of wireless resources.

[0213] It is worth noting that the above description of the embodiments of the present application is only illustrative, but the present application is not limited thereto. For example, the execution order between the operations can be appropriately adjusted, and in addition, some operations can be added or some operations can be reduced. Those skilled in the art can make appropriate modifications based on the above description, and the present application is not limited to the above description and the accompanying drawings. Figure 12 The embodiments of the present application are only illustrative, but the present application is not limited thereto. For example, the execution order between the operations can be appropriately adjusted, and in addition, some operations can be added or some operations can be reduced. Those skilled in the art can make appropriate modifications based on the above description, and the present application is not limited to the above description and the accompanying drawings. Figure 12 The embodiments of the present application are only illustrative, but the present application is not limited thereto. For example, the execution order between the operations can be appropriately adjusted, and in addition, some operations can be added or some operations can be reduced. Those skilled in the art can make appropriate modifications based on the above description, and the present application is not limited to the above description and the accompanying drawings.

[0214] In some embodiments, the terminal device has sidelink data to be transmitted, which can be a SL MAC CE, such as a SL CSI reporting MAC CE, and when there is no available sidelink resource at present, the terminal device will trigger a scheduling request (SR) which is in a pending state, i.e., the terminal device is ready but has not yet sent the SR to the network device. The scheduling request is used by the terminal device to apply for resources from the network device for sidelink new data transmission.

[0215] In some embodiments, the terminal device receives a scheduling request configuration corresponding to the sidelink data sent by the network device, and the scheduling request configuration includes a set of PUCCH resources for SR across each BWP in a cell. For example, the network device can send the SR configuration through an RRC reconfiguration message or system information or an RRC resume message or an RRC re-establishment message or an RRC setup message.

[0216] In some embodiments, the BWP includes an initial BWP of the terminal device and / or a BWP configured by the network for the terminal device through an RRC message (such as an RRC reconfiguration message or an RRC setup message, etc.), which is a BWP dedicated to the terminal device.

[0217] In some embodiments, for sidelink data, for example, a sidelink MAC CE, the SR corresponding to the sidelink data, at most one PUCCH resource is configured on each BWP.

[0218] In some embodiments, for sidelink data, the number of scheduling request configurations configured by the network device is one, for example, for a sidelink CSI reporting MAC CE, the network device only configures one scheduling request configuration.

[0219] In some embodiments, the terminal device transmits the SR using the PUCCH resource in the scheduling request configuration corresponding to the sidelink data, that is, after triggering the SR, the SR is transmitted in the configured nearest PUCCH resource.

[0220] The above various embodiments only exemplarily illustrate the embodiments of the present application, but the present application is not limited thereto, and can be appropriately modified on the basis of the above various embodiments. For example, the above various embodiments can be used alone, or one or more of the above various embodiments can be combined.

[0221] From the above embodiments, on the uplink bandwidth BWP configured by the terminal device, the terminal device is configured with the PUCCH resource belonging to the SR configuration, so that in the case that the time advance timer TimeAlignmentTimer does not time out, when the SR is triggered, the terminal device has the PUCCH resource corresponding to the SR configuration in the currently activated uplink BWP, so as to ensure that the random access process is not initiated due to the lack of valid PUCCH resource for the SR, reduce the occupation of wireless resources by the random access process, and improve the utilization rate of wireless resources.

[0222] Embodiments of the tenth aspect

[0223] The embodiments of the present application provide a resource configuration method, which is described from the network device side, wherein the same content as the embodiments of the ninth aspect will not be described again.

[0224] Figure 13 is a schematic diagram of the resource configuration method of the embodiments of the present application, as shown in Figure 13 The method comprises the following steps.

[0225] 1301, the network device sends a scheduling request configuration corresponding to the sidelink data to the terminal device, the scheduling request configuration comprising a set of PUCCH resources on the BWP;

[0226] 1302, the network device receives the scheduling request sent by the terminal device using the PUCCH resource corresponding to the scheduling request configuration.

[0227] According to the above embodiments, on the uplink bandwidth part (BWP) configured for the terminal device, the terminal device is configured with PUCCH resources belonging to the SR configuration, thus in the case that the time alignment timer (TimeAlignmentTimer) does not expire, when the SR is triggered, the terminal device has the PUCCH resources corresponding to the SR configuration in the currently activated uplink BWP, thus ensuring that the random access procedure is not initiated due to the lack of valid PUCCH resources for the SR, reducing the occupation of wireless resources by the random access procedure, and improving the utilization rate of wireless resources.

[0228] It is worth noting that the above embodiments are only illustrative, but the present application is not limited thereto. For example, the execution order between the operations can be appropriately adjusted, and in addition, some operations can be added or some operations can be reduced. Those skilled in the art can make appropriate modifications based on the above description, and the present application is not limited to the above embodiments described in the above Figure 13 The present application is only illustratively described by the above embodiments, but the present application is not limited thereto. For example, the execution order between the operations can be appropriately adjusted, and in addition, some operations can be added or some operations can be reduced. Those skilled in the art can make appropriate modifications based on the above description, and the present application is not limited to the above embodiments described in the above Figure 13 The present application is only illustratively described by the above embodiments, but the present application is not limited thereto. For example, the execution order between the operations can be appropriately adjusted, and in addition, some operations can be added or some operations can be reduced. Those skilled in the art can make appropriate modifications based on the above description, and the present application is not limited to the above embodiments described in the above

[0229] In some embodiments, the terminal device has sidelink data to be transmitted, which can be a SL MAC CE, such as a SL CSI reporting MAC CE. When there is no available sidelink resource at present, the terminal device will trigger a scheduling request (SR), which is in a pending state, i.e., the terminal device is ready but has not yet sent the SR to the network device. The scheduling request is used by the terminal device to apply for resources from the network device for sidelink new data transmission.

[0230] In some embodiments, the network device configures the SR, and the scheduling request configuration includes a set of PUCCH resources for SR across each BWP in a cell. After the configuration is completed, the network device sends the SR configuration to the terminal device. For example, the network device can send the SR configuration through an RRC reconfiguration message or a system information or an RRC resume message or an RRC re-establishment message or an RRC setup message.

[0231] In some embodiments, the BWP includes an initial BWP of the terminal device and / or a BWP configured by the network for the terminal device through an RRC message (such as an RRC reconfiguration message or an RRC setup message, etc.), which is a BWP dedicated to the terminal device.

[0232] In some embodiments, for sidelink data, for example, a sidelink MAC CE, a maximum of one PUCCH resource is configured on each BWP for the SR corresponding to the sidelink data.

[0233] In some embodiments, for sidelink data, the number of scheduling request configurations is one, for example, for a sidelink CSI reporting MAC CE, the network device only configures one scheduling request configuration.

[0234] In some embodiments, the network device receives the SR on the PUCCH resource in the scheduling request configuration corresponding to the sidelink data, and allocates sidelink resources to the terminal device according to the SR.

[0235] The above various embodiments are only exemplarily described, but the present application is not limited thereto, and can be appropriately modified on the basis of the above various embodiments. For example, the above various embodiments can be used alone, or one or more of the above various embodiments can be combined.

[0236] As can be seen from the above embodiments, on the uplink partial bandwidth BWP configured for the terminal device, the terminal device is configured with a PUCCH resource belonging to the SR configuration, so that in the case that the time alignment timer TimeAlignmentTimer does not time out, when the SR is triggered, the terminal device has the PUCCH resource corresponding to the SR configuration in the currently activated uplink BWP, so that it is ensured that the random access process will not be initiated due to the lack of valid PUCCH resource for the SR, the random access process occupies less wireless resources, and the utilization rate of wireless resources is improved.

[0237] Embodiments of the eleventh aspect

[0238] The present application provides a random access method from the terminal device side, Figure 14 is a schematic diagram of the random access method of the present application, as Figure 14 shown, the method comprises:

[0239] 1401, the terminal device sends a scheduling request to the network device;

[0240] 1402, when the number of scheduling requests reaches a predetermined maximum number of transmissions, a random access process is not initiated, wherein the scheduling request is a scheduling request triggered when the terminal device has a sidelink MAC CE to be sent and currently has no available sidelink resource;

[0241] or, when the number of scheduling requests reaches a predetermined maximum number of transmissions, a random access process is initiated, wherein the scheduling request is a scheduling request triggered by a non-sidelink MAC CE.

[0242] According to the above embodiments, the SR triggered by the SL MAC CE does not initiate a random access procedure when the maximum number of SR transmissions is reached, or the SR not triggered by the SL MAC CE initiates a random access procedure when the maximum number of SR transmissions is reached. The maximum number of SR transmissions triggered by the SL MAC CE can avoid the random access procedure from being initiated, and the network device is not clear whether the terminal device is requesting sidelink resources through the random access procedure. The random access procedure cannot be used to request sidelink resources from the network device, so avoiding the initiation of the random access procedure can reduce the occupation of wireless resources by the random access procedure and improve the utilization of wireless resources.

[0243] It is worth noting that the above drawings Figure 14 The embodiments of the present application are only schematically described, but the present application is not limited thereto. For example, the execution order between the operations can be appropriately adjusted, and in addition, some operations can be added or some operations can be reduced. Those skilled in the art can make appropriate modifications based on the above description, and the present application is not limited to the above Figure 14 description.

[0244] In some embodiments, the terminal device has a sidelink MAC CE to be sent, such as a SL CSI reporting MAC CE. When there is no available sidelink resource at present, the terminal device will trigger a scheduling request SR, which is in a pending state, i.e. the terminal device is ready but has not yet sent the SR to the network device. The scheduling request is used by the terminal device to apply for resources from the network device for sidelink new data transmission. Then, when there is a valid PUCCH resource in the SR configuration corresponding to the sidelink MAC CE, the terminal device transmits the SR using the resource in the SR configuration, and sets a prohibit timer sr-ProhibitTimer for monitoring the SR transmitted in the PUCCH. When the timer expires, the terminal device needs to resend the SR until the maximum number of transmissions sr-TransMax is reached. After the maximum number of transmissions is reached, the random access procedure is not initiated. In other words, when the SR is triggered by the sidelink MAC CE, the random access procedure is not initiated after the maximum number of SR transmissions is reached.

[0245] In some embodiments, the terminal device has non-SL MAC CEs to be transmitted, such as uplink data or sidelink logical channel data, triggers an uplink BSR or a sidelink BSR, and when there is no available uplink resource or the available uplink resource cannot meet a certain condition, the terminal device will trigger a scheduling request (SR) in a pending state, that is, the terminal device is ready but has not yet sent the SR to the network device, and the SR is used by the terminal device to apply for resources from the network device for uplink new data transmission. Then, when there is a valid PUCCH resource in the SR configuration, the terminal device transmits the SR using the resource in the SR configuration, sets a prohibit timer sr-ProhibitTimer for monitoring the SR transmitted in the PUCCH, and when the timer expires, the terminal device needs to resend the SR until the maximum number of transmissions sr-TransMax is reached. After the maximum number of transmissions is reached, a random access process can be initiated. In addition, all configured uplink and downlink grants can be cleared, and the RRC can be notified to release the PUCCH and the sounding reference signal (SRS). In other words, when the SR is not triggered by the sidelink MAC CE, after the maximum number of SR transmissions is reached, a random access process can be initiated.

[0246] The above embodiments are only exemplary, and the application is not limited thereto. For example, the above embodiments can be used alone or in combination.

[0247] As can be seen from the above embodiments, the SR triggered by the SL MAC CE does not initiate a random access process when the maximum number of SR transmissions is reached, or the SR triggered by the non-SL MAC CE initiates a random access process when the maximum number of SR transmissions is reached. The random access process can be initiated when the maximum number of SR transmissions triggered by the SL MAC CE is reached, and the network device does not know whether the terminal device is requesting sidelink resources through the random access process. The random access process cannot be used to request sidelink resources from the network device, so avoiding the initiation of the random access process can reduce the occupation of wireless resources by the random access process and improve the utilization of wireless resources.

[0248] Embodiments of the twelfth aspect

[0249] The embodiments of the present application provide a random access method, which is described from the terminal device side, Figure 15 is a schematic diagram of the random access method of the embodiments of the present application, as Figure 15 shown, the method comprises:

[0250] 1501, triggering a scheduling request when the terminal device has sidelink data to be transmitted and currently has no available sidelink resource;

[0251] 1502, initiate a random access procedure in a case that the scheduling request has no valid PUCCH resource configured or the sending of the scheduling request reaches a maximum number of times;

[0252] 1503, stop the random access procedure in a case that a duration of the random access procedure exceeds a maximum latency of the sidelink data.

[0253] According to the above embodiments, for the case that the random access procedure is initiated due to that the SR has no valid PUCCH resource or the sending of the SR reaches a maximum number of times, in a case that a duration of the random access procedure exceeds a maximum latency of the sidelink data, since the sidelink data has expired at this time, it is useless for the peer terminal device, thus the random access procedure is stopped, thereby the random access procedure can occupy wireless resources, and the utilization rate of the wireless resources can be improved.

[0254] It is worth noting that the above drawings Figure 15 The embodiments of the present application are only illustrative, but the present application is not limited thereto. For example, the execution order between the operations can be adjusted as appropriate, and in addition, some operations can be added or some operations can be reduced. Those skilled in the art can make appropriate modifications based on the above description, and the present application is not limited to the above Figure 15 description.

[0255] In some embodiments, the terminal device has sidelink data to be sent, which can be a SL MAC CE, such as a SL CSI reporting MAC CE, or sidelink logical channel data, when there is no available sidelink resource at present, the terminal device will trigger a scheduling request SR, the SR is in a pending state, that is, the terminal device is ready but has not sent the SR to the network device. The scheduling request is used for the terminal device to apply for resources from the network device for sidelink new data transmission.

[0256] In some embodiments, a random access procedure is initiated in a case that the scheduling request has no valid PUCCH resource configured, which can be specifically referred to the embodiments of the first aspect. A duration of the random access procedure is counted, and the random access procedure is stopped in a case that the duration of the random access procedure exceeds a maximum latency of the sidelink data. The maximum latency of the sidelink data can be a value between 4-20 ms.

[0257] In some embodiments, when there is a valid PUCCH resource in the SR configuration, the terminal device uses the resource in the SR configuration to send the SR, sets a prohibit timer sr-ProhibitTimer for monitoring the SR transmitted in the PUCCH, and when the timer expires, the terminal device needs to resend the SR until the maximum number of transmissions sr-TransMax is reached. After reaching the maximum number of transmissions, a random access procedure is initiated. The random access procedure can refer to the embodiments of the first aspect for details. The duration of the random access procedure is counted, and when the duration of the random access procedure exceeds the maximum delay of the sidelink data, the random access procedure is stopped. The maximum delay of the sidelink data can be a value between 4-20 ms.

[0258] The above various embodiments only exemplarily illustrate the embodiments of the present application, but the present application is not limited thereto, and can be appropriately modified on the basis of the above various embodiments. For example, the above various embodiments can be used alone, or one or more of the above various embodiments can be combined.

[0259] As can be seen from the above embodiments, for the case of initiating a random access procedure due to no valid PUCCH resource for SR or SR transmission reaching the maximum number of transmissions, when the duration of the random access procedure exceeds the maximum delay of the sidelink data, since the sidelink data has expired at this time, it is of little use to the peer terminal device, and therefore the random access procedure is stopped. Therefore, the random access procedure can reduce the occupation of wireless resources, and improve the utilization rate of wireless resources.

[0260] Embodiments of the thirteenth aspect

[0261] The embodiments of the present application provide a scheduling request sending method, which is described from the terminal device side, Figure 16 is a schematic diagram of the scheduling request sending method of the embodiments of the present application, as Figure 16 shown, the method comprises:

[0262] 1601, triggering a scheduling request when the terminal device has sidelink data to send and currently has no available sidelink resource;

[0263] 1602, the terminal device sends a scheduling request to a network device;

[0264] 1603, when the sending of the scheduling request exceeds the maximum delay of the sidelink data, stop sending the scheduling request or cancel the scheduling request.

[0265] According to the above embodiments, when the sending of the SR triggered by the sidelink data exceeds the maximum delay of the sidelink data, since the sidelink data has expired at this time and is of little use to the peer terminal device, the sending of the scheduling request is stopped or the scheduling request is cancelled, so that the random access process can be avoided, the SL MAC CE triggered SR can occupy the uplink wireless resource or the base station can allocate sidelink resources for the transmission of the expired sidelink data, the resource consumption on the Uu interface and the sidelink can be reduced, and the utilization rate of the wireless resource can be improved.

[0266] It is worth noting that the above Figure 16 The embodiments of the present application are only illustratively described, but the present application is not limited thereto. For example, the execution order between the operations can be appropriately adjusted, and in addition, some operations can be added or some operations can be reduced. Those skilled in the art can appropriately modify the above embodiments according to the above description, and the present application is not limited to the above Figure 16 description.

[0267] In some embodiments, the terminal device has sidelink data to be sent, which can be a SL MAC CE, such as a SL CSI reporting MAC CE, or sidelink logical channel data. When there is no available sidelink resource at present, the terminal device will trigger a scheduling request SR, which is in a pending state, i.e. the terminal device is ready but has not yet sent the SR to the network device. The scheduling request is used by the terminal device to apply for resources from the network device for sidelink new data transmission.

[0268] In some embodiments, when there is a valid PUCCH resource in the SR configuration, the terminal device sends the SR using the resource in the SR configuration, sets a prohibit timer sr-ProhibitTimer for monitoring the SR transmitted in the PUCCH, and when the timer expires, the terminal device needs to resend the SR. When the sending of the SR (the cumulative time of multiple sending of the SR) exceeds the maximum delay of the sidelink data, the sending of the scheduling request is stopped or the scheduling request is cancelled, so that the random access process is also not initiated. The maximum delay of the sidelink data can be a value between 4-20 ms.

[0269] The above embodiments are only illustratively described, but the present application is not limited thereto, and appropriate modifications can be made on the basis of the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0270] From the above embodiments, when the sending of the SR triggered by the sidelink data exceeds the maximum delay of the sidelink data, since the sidelink data has expired at this time, it is of little use to the peer terminal device, and therefore the sending of the scheduling request is stopped or the scheduling request is cancelled, thereby avoiding initiating the random access process, reducing the occupation of uplink wireless resources by the SR triggered by the SL MAC CE, or reducing the consumption of resources on the Uu interface and the sidelink, and improving the utilization rate of wireless resources.

[0271] Embodiments of the fourteenth aspect

[0272] Embodiments of the present application provide a sidelink transmission device. The device may, for example, be a terminal device (such as the terminal device described above), or may be one or more components or assemblies configured in a terminal device. The same content as the embodiments of the ninth aspect will not be described again.

[0273] Figure 17 is a schematic diagram of a sidelink transmission device according to an embodiment of the present application. In some embodiments, as shown in Figure 17 the sidelink transmission device 1700 comprises:

[0274] a sixth receiving unit 1701 configured to receive a scheduling request configuration corresponding to sidelink data sent by a network device, the scheduling request configuration comprising a set of PUCCH resources on a partial bandwidth BWP;

[0275] a triggering unit 1702 configured to trigger a scheduling request when the terminal device has sidelink data to send and currently has no available sidelink resources;

[0276] a sixth sending unit 1703 configured to send the scheduling request using the PUCCH resource corresponding to the scheduling request configuration.

[0277] According to the above embodiments, on the uplink partial bandwidth BWP configured for the terminal device, the terminal device is configured with PUCCH resources belonging to the SR configuration, and therefore, in the case where the TimeAlignmentTimer has not timed out, when the SR is triggered, the terminal device has the PUCCH resource corresponding to the SR configuration in the currently activated uplink BWP, and therefore, it is ensured that the random access process will not be initiated due to the lack of valid PUCCH resources for the SR, the occupation of wireless resources by the random access process is reduced, and the utilization rate of wireless resources is improved.

[0278] In some embodiments, the terminal device has sidelink data to transmit, which can be a SL MAC CE, e.g., a SL CSI reporting MAC CE, when there is no available sidelink resource at present, the terminal device will trigger a scheduling request (SR), which is in a pending state, i.e., the terminal device is ready but has not yet sent the SR to the network device. The scheduling request is used by the terminal device to apply for resources from the network device for sidelink new data transmission.

[0279] In some embodiments, the sixth receiving unit 1701 receives a scheduling request configuration corresponding to the sidelink data sent by the network device, which includes a set of PUCCH resources for SR across each BWP in a cell. For example, the sixth receiving unit 1701 can receive the SR configuration through an RRC reconfiguration message or system information or an RRC resume message or an RRC re-establishment message or an RRC setup message.

[0280] In some embodiments, the BWP includes an initial BWP of the terminal device and / or a BWP configured by the network for the terminal device through an RRC message (e.g., an RRC reconfiguration message or an RRC setup message, etc.), e.g., a BWP dedicated to the terminal device.

[0281] In some embodiments, for sidelink data, e.g., a sidelink MAC CE, at most one PUCCH resource is configured for the SR corresponding to the sidelink data on each BWP.

[0282] In some embodiments, for sidelink data, the number of scheduling request configurations is one, e.g., for a sidelink CSI reporting MAC CE, the network device only configures one scheduling request configuration.

[0283] In some embodiments, the sixth sending unit 1703 sends the SR using the PUCCH resource in the scheduling request configuration corresponding to the sidelink data, i.e., sends the SR in the configured nearest PUCCH resource after triggering the SR.

[0284] The above various embodiments are only exemplarily described for the embodiments of the present application, but the present application is not limited thereto, and can be appropriately modified on the basis of the above various embodiments. For example, the above various embodiments can be used individually, or one or more of the above various embodiments can be combined.

[0285] It is worth noting that the above only illustrates the components or modules related to the present application, but the present application is not limited thereto. The sidelink transmission apparatus 1700 can also include other components or modules, and the specific content of these components or modules can be referred to in related technologies.

[0286] In addition, for the sake of simplicity, Figure 17 The connection relationship or signal path between the various components or modules is only exemplarily shown, but those skilled in the art should understand that various related technologies such as bus connection can be used. The various components or modules described above can be implemented by hardware facilities such as processors, memories, transmitters, receivers, etc.; the present application is not limited thereto.

[0287] From the above embodiments, on the uplink partial bandwidth BWP configured by the terminal device, the terminal device is configured with PUCCH resources belonging to the SR configuration, so that in the case that the TimeAlignmentTimer does not time out, when the SR is triggered, the terminal device has the PUCCH resource corresponding to the SR configuration in the currently activated uplink BWP, so as to ensure that the random access process is not initiated due to the lack of valid PUCCH resource for the SR, reduce the occupation of wireless resources by the random access process, and improve the utilization rate of wireless resources.

[0288] Embodiments of the fifteenth aspect

[0289] The embodiments of the present application provide a resource configuration apparatus. The apparatus may, for example, be a network device (such as the network device described above), or a certain component or component of the network device, and the same content as the embodiments of the tenth aspect will not be repeated.

[0290] Figure 18 is a schematic diagram of the resource configuration apparatus of the embodiments of the present application. In some embodiments, as Figure 18 shown, the resource configuration apparatus 1800 includes:

[0291] A seventh sending unit 1801 is configured to send a scheduling request configuration corresponding to the sidelink data to a terminal device, the scheduling request configuration including a set of PUCCH resources on a partial bandwidth BWP;

[0292] A seventh receiving unit 1802 is configured to receive the scheduling request sent by the terminal device using the PUCCH resource corresponding to the scheduling request configuration.

[0293] According to the above embodiments, on the uplink bandwidth part (BWP) configured for the terminal device, the terminal device is configured with PUCCH resources belonging to the SR configuration, thus in the case that the time alignment timer (TimeAlignmentTimer) does not expire, when the SR is triggered, the terminal device has the PUCCH resource corresponding to the SR configuration in the currently activated uplink BWP, thus ensuring that the random access procedure is not initiated due to the lack of valid PUCCH resource for the SR, reducing the occupation of wireless resources by the random access procedure, and improving the utilization rate of wireless resources.

[0294] In some embodiments, the terminal device has sidelink data to be transmitted, which can be a SL MAC CE, such as a SL CSI reporting MAC CE. When there is no available sidelink resource at present, the terminal device will trigger a scheduling request (SR), which is in a pending state, i.e., the terminal device is ready but has not yet sent the SR to the network device. The scheduling request is used by the terminal device to apply for resources from the network device for sidelink new data transmission.

[0295] In some embodiments, the network device performs SR configuration, the scheduling request configuration including a set of PUCCH resources for SR across each BWP in a cell, and after completing the configuration, the network device sends the SR configuration to the terminal device. For example, the seventh sending unit 1801 can send the SR configuration through an RRC reconfiguration message or system information or an RRC resume message or an RRC re-establishment message or an RRC setup message.

[0296] In some embodiments, the BWP includes an initial BWP of the terminal device and / or a BWP configured by the network for the terminal device through an RRC message (such as an RRC reconfiguration message or an RRC setup message, etc.), which is a BWP dedicated to the terminal device.

[0297] In some embodiments, for sidelink data, such as a sidelink MAC CE, at most one PUCCH resource is configured for the SR corresponding to the sidelink data on each BWP.

[0298] In some embodiments, for sidelink data, the number of scheduling request configurations is one, for example, for a sidelink CSI reporting MAC CE, the network device only configures one scheduling request configuration.

[0299] In some embodiments, the seventh receiving unit 1802 receives the SR on the PUCCH resource in the scheduling request configuration corresponding to the sidelink data, and allocates sidelink resources to the terminal device according to the SR.

[0300] The above embodiments are only exemplary and the present application is not limited thereto. For example, one or more of the above embodiments can be combined.

[0301] It should be noted that the above only illustrates the components or modules related to the present application, but the present application is not limited thereto. The resource configuration apparatus 1800 can further include other components or modules, and the specific content of these components or modules can be referred to the related art.

[0302] In addition, for the sake of simplicity, Figure 18 The connection relationship or signal path between the components or modules is only exemplary, but those skilled in the art should understand that various related technologies such as bus connection can be used. The above components or modules can be implemented by hardware facilities such as processors, memories, transmitters, receivers, etc., and the present application is not limited thereto.

[0303] As can be seen from the above embodiments, on the uplink bandwidth BWP configured for the terminal device, the terminal device is configured with PUCCH resources belonging to the SR configuration, so that when the SR is triggered without the time alignment timer timeAlignmentTimer expiring, the terminal device has the PUCCH resource corresponding to the SR configuration in the currently activated uplink BWP, thereby ensuring that the random access procedure is not initiated due to the lack of valid PUCCH resource for the SR, reducing the occupation of wireless resources by the random access procedure, and improving the utilization rate of wireless resources.

[0304] Embodiments of the sixteenth aspect

[0305] The present application provides a random access apparatus. The apparatus can be a terminal device (such as the terminal device described above), or a component or component configured in the terminal device. The same content as the eleventh aspect will not be repeated.

[0306] Figure 19 is a schematic diagram of the random access apparatus of the present application. In some embodiments, as Figure 19 shown, the random access apparatus 1900 includes:

[0307] An eighth sending unit 1901 for sending a scheduling request to a network device;

[0308] a first processing unit 1902 configured to not initiate a random access procedure when the number of sent scheduling requests reaches a predetermined maximum number of sending times, wherein the scheduling request is triggered when the terminal device has a sidelink MAC CE to send and no sidelink resource is currently available;

[0309] Alternatively, initiate a random access procedure when the number of sent scheduling requests reaches a predetermined maximum number of sending times, wherein the scheduling request is triggered by a non-sidelink MAC CE.

[0310] According to the above-mentioned embodiments, the random access procedure is not initiated when the number of sent SR triggered by SL MAC CE reaches the maximum number of sending times, or the random access procedure is initiated when the number of sent SR triggered by non-SL MAC CE reaches the maximum number of sending times, which can avoid the random access procedure being initiated due to the number of sent SR triggered by SL MAC CE reaching the maximum number of sending times. Since the network device is not aware of whether the terminal device is requesting sidelink resources through the random access procedure, the random access procedure cannot be used to request sidelink resources from the network device. Therefore, avoiding the initiation of the random access procedure can reduce the occupation of wireless resources by the random access procedure and improve the utilization rate of wireless resources.

[0311] In some embodiments, the terminal device has a sidelink MAC CE to send, for example, a SL CSI reporting MAC CE. When no sidelink resource is currently available, the terminal device will trigger a scheduling request SR, which is in a pending state, i.e., the terminal device is ready but has not yet sent the SR to the network device. The scheduling request is used by the terminal device to apply for resources from the network device for sidelink new data transmission. Then, when there is a valid PUCCH resource in the SR configuration, the eighth sending unit 1901 sends the SR using the resource in the SR configuration, sets a prohibit timer sr-ProhibitTimer for monitoring the SR transmitted in the PUCCH, and when the timer expires, the eighth sending unit 1901 needs to resend the SR until the maximum number of sending times sr-TransMax is reached. After the maximum number of sending times is reached, the first processing unit 1902 does not initiate a random access procedure. In other words, when the SR is triggered by a sidelink MAC CE, the first processing unit 1902 does not initiate a random access procedure after the SR reaches the maximum number of sending times.

[0312] In some embodiments, when the terminal device has non-sidelink data to send, such as uplink data or sidelink logical channel data, an uplink BSR or sidelink BSR is triggered, and there is no available uplink resource at present, the terminal device will trigger a scheduling request SR, which is in a pending state, i.e., the terminal device is ready but has not yet sent the SR to the network device, and the scheduling request is used by the terminal device to apply for resources from the network device for uplink new data transmission. Then, when there is a valid PUCCH resource in the SR configuration, the eighth sending unit 1901 sends the SR using the resource in the SR configuration, sets a prohibit timer sr-ProhibitTimer for monitoring the SR transmitted in the PUCCH, and when the timer expires, the eighth sending unit 1901 needs to resend the SR until the maximum number of transmissions sr-TransMax is reached. After the maximum number of transmissions is reached, the first processing unit 1902 can initiate a random access process. In addition, all configured uplink and downlink grants can be cleared, and the RRC can be notified to release the PUCCH and SRS, etc. In other words, when the SR is not triggered by the sidelink MAC CE, after the maximum number of SR transmissions is reached, the first processing unit 1902 can initiate a random access process.

[0313] The above embodiments are only exemplary and the present application is not limited thereto. The above embodiments can be appropriately modified on the basis of the above embodiments.

[0314] It should be noted that the above only describes the components or modules related to the present application, but the present application is not limited thereto. The random access device 1900 can also include other components or modules, and the specific content of these components or modules can be referred to related technologies.

[0315] In addition, for the sake of simplicity, Figure 19 In addition, for the sake of simplicity,

[0316] It can be known from the above embodiments that, the random access process is not initiated when the SR triggered by the SL MAC CE reaches the maximum number of SR sending times, or the random access process is initiated when the SR triggered by the non-SL MAC CE reaches the maximum number of SR sending times, which can avoid the random access process being initiated due to the SR triggered by the SL MAC CE reaching the maximum number of SR sending times. Since the network device cannot know whether the terminal device is requesting sidelink resources through the random access process, the random access process cannot be used to request sidelink resources from the network device. Therefore, avoiding the initiation of the random access process can reduce the occupation of wireless resources by the random access process and improve the utilization rate of wireless resources.

[0317] Embodiments of the seventeenth aspect

[0318] The embodiments of the present application provide a scheduling request sending apparatus. The apparatus may, for example, be a terminal device (for example, the terminal device described above), or may be one or more components or assemblies configured in the terminal device. The same content as the embodiments of the twelfth aspect will not be described again.

[0319] Figure 20 FIG. 1 is a schematic diagram of a scheduling request sending apparatus according to an embodiment of the present application. In some embodiments, as shown in FIG. 1, the scheduling request sending apparatus 2000 includes: Figure 20

[0320] a triggering unit 2001 configured to trigger a scheduling request when the terminal device has sidelink data to be sent and currently has no available sidelink resources;

[0321] a third processing unit 2002 configured to initiate a random access process when the scheduling request has no valid PUCCH resource or the sending of the scheduling request reaches a maximum number of times;

[0322] a fourth processing unit 2003 configured to stop the random access process when a duration of the random access process exceeds a maximum delay of the sidelink data.

[0323] According to the above embodiments, for the case of initiating a random access process due to the SR having no valid PUCCH resource or the SR sending reaching a maximum number of sending times, the random access process is stopped when the duration of the random access process exceeds the maximum delay of the sidelink data, since the sidelink data has expired at this time and is of little use to the peer terminal device. Therefore, the occupation of wireless resources by the random access process can be reduced, and the utilization rate of wireless resources can be improved.

[0324] ​In some embodiments, the terminal device has sidelink data to transmit, which can be a SL MAC CE, such as a SL CSI reporting MAC CE, or sidelink logical channel data, when there is no available sidelink resource at present, the triggering unit 2001 will trigger a scheduling request SR, which is in a pending state, that is, the terminal device is ready but has not yet sent the SR to the network device. The scheduling request is used by the terminal device to apply for resources from the network device for sidelink new data transmission.

[0325] In some embodiments, the third processing unit 2002 initiates a random access procedure when the scheduling request is not configured with a valid PUCCH resource, which can be specifically referred to the embodiments of the first aspect. The fourth processing unit 2003 counts the duration of the random access procedure, and stops the random access procedure when the duration of the random access procedure exceeds the maximum delay of the sidelink data. The maximum delay of the sidelink data can be a value between 4-20 ms.

[0326] In some embodiments, when there is a valid PUCCH resource in the SR configuration, the terminal device transmits the SR using the resource in the SR configuration, and sets a prohibit timer sr-ProhibitTimer for monitoring the SR transmitted in the PUCCH. When the timer expires, the terminal device needs to resend the SR until the maximum number of transmissions sr-TransMax is reached. After the maximum number of transmissions is reached, the third processing unit 2002 initiates a random access procedure. The random access procedure can be specifically referred to the embodiments of the first aspect. The fourth processing unit 2003 counts the duration of the random access procedure, and stops the random access procedure when the duration of the random access procedure exceeds the maximum delay of the sidelink data. The maximum delay of the sidelink data can be a value between 4-20 ms.

[0327] The above various embodiments are only exemplarily described for the embodiments of the present application, but the present application is not limited thereto, and can be appropriately modified on the basis of the above various embodiments. For example, the above various embodiments can be used alone, or one or more of the above various embodiments can be combined.

[0328] It is worth noting that the above only describes the components or modules related to the present application, but the present application is not limited thereto. The scheduling request sending apparatus 2000 can also include other components or modules, and the specific content of these components or modules can be referred to the related technology.

[0329] In addition, for the sake of simplicity, Figure 20The connection relationship or signal direction between each component or module is only exemplarily shown, but those skilled in the art should understand that various related technologies such as bus connection can be adopted. Each component or module can be implemented by hardware facilities such as a processor, a memory, a transmitter, a receiver, and the like; the implementation of the present application is not limited thereto.

[0330] It can be known from the above embodiments that, in the case of initiating a random access process due to that there is no effective PUCCH resource for SR or the sending of SR reaches the maximum sending times, when the duration of the random access process exceeds the maximum delay of the sidelink data, the sidelink data has expired at this time, and is of little use to the peer terminal device, so the random access process is stopped, thereby the random access process can occupy wireless resources, and the utilization rate of wireless resources can be improved.

[0331] Embodiments of the eighteenth aspect

[0332] The embodiments of the present application provide a random access device. The device can be a terminal device (for example, the terminal device described above), or can be one or more components or assemblies configured in the terminal device. The same content as the embodiments of the thirteenth aspect will not be described again.

[0333] Figure 21 is a schematic diagram of a random access device according to an embodiment of the present application. In some embodiments, as shown in Figure 21 The random access device 2100 includes:

[0334] A triggering unit 2101 configured to trigger a scheduling request when the terminal device has sidelink data to be sent and currently has no available sidelink resource;

[0335] A ninth sending unit 2102 configured to send the scheduling request to a network device;

[0336] A second processing unit 2103 configured to stop sending the scheduling request or cancel the scheduling request when the sending of the scheduling request exceeds the maximum delay of the sidelink data.

[0337] According to the above embodiments, when the sending of the SR triggered by the sidelink data exceeds the maximum delay of the sidelink data, the sidelink data has expired at this time, and is of little use to the peer terminal device, so the sending of the scheduling request is stopped or the scheduling request is cancelled, thereby the random access process can be avoided to be initiated, the SL MAC CE triggered SR can occupy uplink wireless resources, or the base station can allocate sidelink resources for the transmission of the expired sidelink data, the resource consumption on the Uu interface and the sidelink can be reduced, and the utilization rate of wireless resources can be improved.

[0338] In some embodiments, the terminal device has sidelink data to be transmitted, which can be a SL MAC CE, such as a SL CSI reporting MAC CE, or sidelink logical channel data, when there is no available sidelink resource at present, the triggering unit 2101 will trigger a scheduling request SR, which is in a pending state, that is, the terminal device is ready but has not yet transmitted the SR to the network device. The scheduling request is used by the terminal device to apply for resources from the network device for sidelink new data transmission.

[0339] In some embodiments, when there is a valid PUCCH resource in the SR configuration, the ninth sending unit 2102 transmits the SR using the resource in the SR configuration, sets a prohibit timer sr-ProhibitTimer for monitoring the SR transmitted in the PUCCH, and when the timer expires, the ninth sending unit 2102 needs to retransmit the SR. When the transmission (cumulative time of multiple transmissions) of the SR exceeds the maximum delay of the sidelink data, the second processing unit 2103 stops transmitting the scheduling request or cancels the scheduling request, so it also does not initiate a random access process. The maximum delay of the sidelink data can be a value between 4-20 ms. The above embodiments only exemplarily illustrate the embodiments of the present application, but the present application is not limited thereto, and appropriate modifications can be made on the basis of the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0340] It is worth noting that the above only illustrates the components or modules related to the present application, but the present application is not limited thereto. The random access apparatus 2100 can also include other components or modules, and the specific content of these components or modules can be referred to related technologies.

[0341] In addition, for the sake of simplicity, Figure 21 The connection relationship or signal path between the components or modules in the above embodiments is only exemplarily illustrated, but those skilled in the art should understand that various related technologies such as bus connection can be used. The above components or modules can be realized by hardware facilities such as processors, memories, transmitters, receivers, etc.; the present application is not limited thereto.

[0342] As can be seen from the above embodiments, when the transmission of the SR triggered by the sidelink data exceeds the maximum delay of the sidelink data, since the sidelink data has expired at this time, it is of little use to the peer terminal device, so the transmission of the scheduling request is stopped or the scheduling request is cancelled, thereby avoiding the initiation of the random access process, reducing the occupation of uplink radio resources by the SL MAC CE triggered SR, or the base station allocating sidelink resources for the transmission of expired sidelink data, reducing resource consumption on the Uu interface and the sidelink, and improving the utilization rate of wireless resources.

[0343] Embodiments of the nineteenth aspect

[0344] Embodiments of the present application also provide a communication system, which can be referred to Figure 1 Embodiments of the first aspect to the eighteenth aspect are the same and will not be repeated.

[0345] Embodiments of the present application also provide a network device, which can be a base station, but the present application is not limited to this, and can also be other network devices.

[0346] Figure 22 is a schematic diagram of the network device of the embodiments of the present application. As shown in Figure 22 The network device 2200 can include a processor 2210 (such as a central processing unit CPU) and a memory 2220; the memory 2220 is coupled to the processor 2210. The memory 2220 can store various data; in addition, it also stores a program 2230 for information processing, and executes the program 2230 under the control of the processor 2210.

[0347] For example, the processor 2210 can be configured to execute the program to implement the random access method as described in the embodiments of the second aspect. For example, the processor 2210 can be configured to control as follows: receiving a random access preamble sent by a terminal device on a physical random access channel resource; wherein the random access preamble is used to indicate that the terminal device has sidelink data to send, and / or the physical random access channel resource is used to indicate that the terminal device has sidelink data to send; sending a random access response to the terminal device.

[0348] For example, the processor 2210 can be configured to execute the program to implement the random access method as described in the embodiments of the sixth aspect. For example, the processor 2210 can be configured to control as follows: receiving an uplink message sent by the terminal device on a physical uplink data channel, the uplink message including sidelink related information; sending a contention resolution message to the terminal device.

[0349] For example, the processor 2210 can be configured to execute the program to implement the resource configuration method as described in the embodiments of the tenth aspect. For example, the processor 2210 can be configured to control as follows: sending a scheduling request configuration corresponding to the sidelink data to the terminal device, the scheduling request configuration including a set of PUCCH resources on a partial bandwidth BWP; receiving the scheduling request sent by the terminal device using the PUCCH resource corresponding to the scheduling request configuration.

[0350] In addition, as Figure 22As shown, network device 2200 may also include: transceiver 2240 and antenna 2250, etc.; the functions of the above components are similar to those in the prior art, and will not be described in detail here. It is worth noting that network device 2200 is not necessarily required to include... Figure 22 All components shown; in addition, network device 2200 may also include Figure 22 For components not shown, please refer to existing technologies.

[0351] This application also provides a terminal device, but the application is not limited thereto and may also include other devices.

[0352] Figure 23 This is a schematic diagram of a terminal device according to an embodiment of this application. Figure 23 As shown, the terminal device 2300 may include a processor 2310 and a memory 2320; the memory 2320 stores data and programs and is coupled to the processor 2310. It is worth noting that this figure is exemplary; other types of structures may be used to supplement or replace this structure to implement telecommunications functions or other functions.

[0353] For example, processor 2310 may be configured to execute a program to implement the random access method as described in the first aspect embodiment. For example, processor 2310 may be configured to perform the following control: selecting a random access preamble; sending the random access preamble to a network device on a physical random access channel resource; wherein the random access preamble is used to indicate that the terminal device has sidelink data transmission, and / or the physical random access channel resource is used to indicate that the terminal device has sidelink data transmission.

[0354] For example, processor 2310 may be configured to execute a program to implement the random access method as described in the embodiments of the fifth aspect. For example, processor 2310 may be configured to perform the following control during the random access process: sending an uplink message to the network device on a physical uplink data channel, the uplink message including sidelink-related information; and receiving a contention resolution message sent by the network device.

[0355] For example, processor 2310 may be configured to execute a program to implement the sidelink transmission method as described in the embodiment of the ninth aspect. For example, processor 2310 may be configured to perform the following control: receive a scheduling request configuration corresponding to sidelink data sent by a network device, the scheduling request configuration including a set of PUCCH resources on a partial bandwidth BWP; trigger the scheduling request when the terminal device has sidelink data to send and there are currently no available sidelink resources; and send the scheduling request using the PUCCH resources corresponding to the scheduling request configuration.

[0356] For example, the processor 2310 can be configured to execute programs to implement the random access method as described in the embodiments of the eleventh aspect. For example, the processor 2310 can be configured to control: sending a scheduling request to a network device; when the number of scheduling request sending reaches a predetermined maximum sending number, not initiating a random access procedure, wherein the scheduling request is a scheduling request triggered when the terminal device has sidelink MAC CE to send and currently has no available sidelink resource; or, when the number of scheduling request sending reaches a predetermined maximum sending number, initiating a random access procedure, wherein the scheduling request is a scheduling request triggered by a non-sidelink MAC CE.

[0357] For example, the processor 2310 can be configured to execute programs to implement the scheduling request sending method as described in the embodiments of the twelfth aspect. For example, the processor 2310 can be configured to control: triggering a scheduling request when the terminal device has sidelink data to send and currently has no available sidelink resource; sending a scheduling request to a network device; when the sending of the scheduling request exceeds the maximum delay of the sidelink data, stopping sending the scheduling request or canceling the scheduling request.

[0358] For example, the processor 2310 can be configured to execute programs to implement the random access method as described in the embodiments of the thirteenth aspect. For example, the processor 2310 can be configured to control: triggering a scheduling request when the terminal device has sidelink data to send and currently has no available sidelink resource; initiating a random access procedure in the case that the scheduling request is not configured with a valid PUCCH resource or the sending of the scheduling request reaches a maximum number; when the duration of the random access procedure exceeds the maximum delay of the sidelink data, the terminal device stops the random access procedure.

[0359] As shown in the Figure 23 The terminal device 2300 can also include: a communication module 2330, an input unit 2340, a display 2350, a power supply 2360. Wherein, the functions of the above components are similar to those in the prior art, and will not be repeated here. It is worth noting that the terminal device 2300 does not necessarily include all the components shown in Figure 23 The above components are not essential; in addition, the terminal device 2300 can also include components not shown in Figure 23 The prior art can be referred to.

[0360] The embodiments of the present application also provide a computer program, wherein when the program is executed in a terminal device, the program causes the terminal device to perform the random access method of the first, fifth, eleventh, and thirteenth aspects.

[0361] The embodiment of the present application further provides a computer program, wherein when the program is executed in the network device, the program enables the network device to perform the random access method in the second and sixth aspects.

[0362] The embodiment of the present application further provides a computer program, wherein when the program is executed in the terminal device, the program enables the terminal device to perform the sidelink transmission method in the ninth aspect.

[0363] The embodiment of the present application further provides a computer program, wherein when the program is executed in the network device, the program enables the network device to perform the resource configuration method in the tenth aspect.

[0364] The embodiment of the present application further provides a computer program, wherein when the program is executed in the terminal device, the program enables the terminal device to perform the scheduling request sending method in the twelfth aspect.

[0365] The embodiment of the present application further provides a storage medium storing a computer program, wherein the computer program enables the terminal device to perform the random access method in the first, fifth, eleventh and thirteenth aspects.

[0366] The embodiment of the present application further provides a storage medium storing a computer program, wherein the computer program enables the terminal device to perform the sidelink transmission method in the ninth aspect.

[0367] The embodiment of the present application further provides a storage medium storing a computer program, wherein the computer program enables the terminal device to perform the scheduling request sending method in the twelfth aspect.

[0368] The embodiment of the present application further provides a storage medium storing a computer program, wherein the computer program enables the network device to perform the random access method in the second and sixth aspects.

[0369] The embodiment of the present application further provides a storage medium storing a computer program, wherein the computer program enables the network device to perform the resource configuration method in the tenth aspect.

[0370] The apparatus and method of the present application can be realized by hardware, or by hardware in combination with software. The present application relates to a computer readable program, which, when executed by a logic component, enables the logic component to realize the apparatus or constituent components described above, or enables the logic component to realize the various methods or steps described above. The present application further relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.

[0371] The method / apparatus described in combination with the embodiments of the present application can be directly embodied as hardware, a software module executed by a processor, or a combination of the two. For example, one or more of the functional blocks shown in the figure and / or a combination of one or more of the functional blocks can correspond to each software module of a computer program flow, and can also correspond to each hardware module. These software modules can correspond to each step shown in the figure, respectively. These hardware modules can be implemented by, for example, fixing the software modules by using a field programmable gate array (FPGA).

[0372] The software module can be located in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a mobile disk, a CD-ROM, or any other form of storage medium known in the art. One storage medium can be coupled to the processor, so that the processor can read information from the storage medium and write information to the storage medium; or the storage medium can be an integral part of the processor. The processor and the storage medium can be located in an ASIC. The software module can be stored in the memory of the mobile terminal, or in a memory card that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a MEGA-SIM card or a large-capacity flash memory device, the software module can be stored in the MEGA-SIM card or the large-capacity flash memory device.

[0373] For one or more of the functional blocks shown in the figure and / or a combination of one or more of the functional blocks, a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or any appropriate combination thereof can be implemented to perform the functions described in the present application. For one or more of the functional blocks described in the figure and / or a combination of one or more of the functional blocks, a combination of computing devices can also be implemented, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.

[0374] The present application has been described above in conjunction with specific embodiments, but it will be clear to those skilled in the art that these descriptions are exemplary and not limiting to the scope of protection of the present application. Those skilled in the art can make various modifications and changes to the present application according to the spirit and principles of the present application, and these modifications and changes are also within the scope of the present application.

[0375] In connection with the embodiments including the above embodiments, the following notes are also disclosed:

[0376] Note 1: A random access method applied to a terminal device side, wherein the method comprises:

[0377] the terminal device selects a random access preamble;

[0378] the terminal device sends the random access preamble to a network device on a physical random access channel resource; wherein the random access preamble is used to indicate that the terminal device has sidelink data to send, and / or the physical random access channel resource is used to indicate that the terminal device has sidelink data to send.

[0379] Paragraph 2, the method according to paragraph 1, wherein the method further comprises:

[0380] the terminal device receives a random access response sent by the network device, wherein the random access response contains a sidelink grant.

[0381] Paragraph 3, the method according to paragraph 2, wherein the sidelink grant is indicated using a reserved field bit in the random access response.

[0382] Paragraph 4, the method according to paragraph 2 or 3, wherein the random access response does not contain a time advance control field and a temporary C-RNTI field.

[0383] Paragraph 5, the method according to any one of paragraphs 1 to 4, wherein the sidelink data is a sidelink MAC CE.

[0384] Paragraph 6, the method according to any one of paragraphs 1 to 5, wherein the method further comprises:

[0385] the terminal device receives the set of random access preambles and / or the set of physical random access channel resources configured by the network device.

[0386] Paragraph 7, the method according to paragraph 6, wherein the set of random access preambles and / or the set of physical random access channel resources are received using a radio resource control (RRC) reconfiguration message or system information or an RRC resume message or an RRC reestablishment message or an RRC setup message.

[0387] Paragraph 8, a random access method applied to a network device side, wherein the method comprises:

[0388] the network device receives a random access preamble sent by a terminal device on a physical random access channel resource; wherein the random access preamble is used to indicate that the terminal device has sidelink data to send, and / or the physical random access channel resource is used to indicate that the terminal device has sidelink data to send;

[0389] the network device sends a random access response to the terminal device.

[0390] Note 9. The method of Note 8, wherein the random access response includes a sidelink grant.

[0391] Note 10. The method of Note 9, wherein the sidelink grant is indicated using a reserved field bit in the random access response.

[0392] Note 11. The method of Note 9 or 10, wherein the random access response does not include a time advance control field and a temporary C-RNTI field.

[0393] Note 12. The method of any one of Notes 8 to 11, wherein the sidelink data is a sidelink MAC CE.

[0394] Note 13. The method of Note 5 or 12, wherein the sidelink MAC CE is a sidelink CSI reporting MAC CE.

[0395] Note 14. The method of any one of Notes 8 to 13, wherein the method further comprises:

[0396] configuring the set of random access preambles and / or the set of physical random access channel resources;

[0397] transmitting the configured set of random access preambles and / or the set of physical random access channel resources to the terminal device.

[0398] Note 15. The method of Note 14, wherein the set of random access preambles and / or the set of physical random access channel resources are transmitted using a radio resource control (RRC) reconfiguration message or system information or an RRC resume message or an RRC reestablishment message.

[0399] Note 16. A random access method applied to a terminal device side, wherein the method comprises:

[0400] in a random access procedure, transmitting an uplink message including sidelink related information to a network device on a physical uplink data channel;

[0401] receiving a contention resolution message transmitted by the network device.

[0402] Note 17. A random access method applied to a network device side, wherein the method comprises:

[0403] receiving an uplink message including sidelink related information transmitted by the terminal device on a physical uplink data channel;

[0404] The network device sends a contention resolution message to the terminal device.

[0405] Paragraph 18, the method according to any one of paragraphs 16 or 17, wherein the sidelink related information is a sidelink buffer status report or a logical channel identifier (LCID) corresponding to the sidelink data or a sidelink SL RNTI of the terminal device.

[0406] Paragraph 19, the method according to any one of paragraphs 15 to 18, wherein the sidelink related information is used to indicate that the terminal device has sidelink data to transmit.

[0407] Paragraph 20, the method according to any one of paragraphs 15 to 19, wherein the uplink message further comprises a C-RNTI of the terminal device.

[0408] Paragraph 21, the method according to any one of paragraphs 15 to 20, wherein the sidelink data is a sidelink MAC CE.

[0409] Paragraph 22, the method according to paragraph 21, wherein the sidelink MAC CE is a sidelink CSI reporting MAC CE.

[0410] Paragraph 23, the method according to paragraph 18, wherein the sidelink buffer status report indicates a logical channel group and / or a buffer size corresponding to the sidelink MAC CE.

[0411] Paragraph 24, a sidelink transmission method applied to a terminal device side, the method comprising:

[0412] The terminal device receives a scheduling request configuration corresponding to sidelink data sent by a network device, the scheduling request configuration comprising a set of PUCCH resources on a partial bandwidth BWP;

[0413] When the terminal device has sidelink data to transmit and currently has no available sidelink resources, triggering a scheduling request;

[0414] The terminal device transmits the scheduling request using the PUCCH resource corresponding to the scheduling request configuration.

[0415] Paragraph 25, a resource configuration method applied to a network device side, the method comprising:

[0416] The network device sends a scheduling request configuration corresponding to the sidelink data to a terminal device, the scheduling request configuration comprising a set of PUCCH resources on a partial bandwidth BWP;

[0417] The network device receives the scheduling request sent by the terminal device using the scheduling request configuration.

[0418] Comment 26. The method of any one of Comments 24 or 25, wherein the number of the scheduling request configurations is one.

[0419] Comment 27. The method of any one of Comments 24 to 26, wherein the scheduling request configuration comprises a set of PUCCH resources on each BWP.

[0420] Comment 28. The method of any one of Comments 24 to 27, wherein at most one PUCCH resource is configured on each BWP in one scheduling request configuration.

[0421] Comment 29. The method of any one of Comments 24 to 28, wherein the scheduling request configuration is sent using a radio resource control (RRC) reconfiguration message or system information or an RRC resume message or an RRC reestablishment message or an RRC setup message.

[0422] Comment 30. The method of any one of Comments 24 to 29, wherein the sidelink data is a sidelink MAC CE.

[0423] Comment 31. The method of Comment 30, wherein the sidelink MAC CE is a sidelink CSI reporting MAC CE.

[0424] Comment 32. A random access method applied to a terminal device side, wherein the method comprises:

[0425] the terminal device sends a scheduling request to a network device;

[0426] when the number of the scheduling request sending reaches a predetermined maximum sending number, the terminal device does not initiate a random access procedure, wherein the scheduling request is a scheduling request triggered when the terminal device has a sidelink MAC CE to send and currently has no available sidelink resource;

[0427] or,

[0428] when the number of the scheduling request sending reaches a predetermined maximum sending number, the terminal device initiates a random access procedure, wherein the scheduling request is a scheduling request triggered by a non-sidelink MAC CE.

[0429] Comment 33. The method of Comment 32, wherein the sidelink MAC CE is a sidelink CSI reporting MAC CE.

[0430] Comment 34. A scheduling request sending method applied to a terminal device side, wherein the method comprises:

[0431] trigger a scheduling request when the terminal device has sidelink data to transmit and no sidelink resource is currently available;

[0432] send, by the terminal device, a scheduling request to a network device;

[0433] stop sending the scheduling request or cancel the scheduling request when the sending of the scheduling request exceeds a maximum latency of the sidelink data.

[0434] Appendix 35, a random access method applied to a terminal device side, wherein the method comprises:

[0435] trigger a scheduling request when the terminal device has sidelink data to transmit and no sidelink resource is currently available;

[0436] initiate a random access procedure when the scheduling request does not have a valid PUCCH resource configured or the sending of the scheduling request reaches a maximum number of times;

[0437] stop the random access procedure when the duration of the random access procedure exceeds a maximum latency of the sidelink data.

[0438] Appendix 36, the method according to any one of appendices 34 to 35, wherein the sidelink data is a sidelink MAC CE or a sidelink logical channel data.

[0439] Appendix 37, the method according to appendix 36, wherein the sidelink MAC CE is a sidelink CSI reporting MAC CE.

[0440] Appendix 38, a random access device applied to a terminal device, wherein the device comprises:

[0441] a selection unit for selecting a random access preamble;

[0442] a first sending unit for sending the random access preamble to a network device on a physical random access channel resource; wherein the random access preamble is used to indicate that the terminal device has sidelink data to transmit, and / or the physical random access channel resource is used to indicate that the terminal device has sidelink data to transmit.

[0443] Appendix 39, the device according to appendix 38, wherein the device further comprises:

[0444] a first receiving unit for receiving a random access response sent by the network device, wherein the random access response contains a sidelink grant.

[0445] Note 40. The apparatus of any one of Note 39, wherein the sidelink grant is indicated using reserved bits in the random access response.

[0446] Note 41. The apparatus of any one of Note 39 or 40, wherein the random access response does not contain a time advance control field and a temporary C-RNTI field.

[0447] Note 42. The apparatus of any one of Note 39 to 41, wherein the sidelink data is a sidelink MAC CE.

[0448] Note 43. The apparatus of any one of Note 39 to 42, wherein the apparatus further comprises:

[0449] a second receiving unit, configured to receive the set of random access preambles and / or the set of physical random access channel resources configured by the network device.

[0450] Note 44. The apparatus of Note 43, wherein the second receiving unit receives the set of random access preambles and / or the set of physical random access channel resources using a radio resource control (RRC) reconfiguration message or system information or an RRC resume message or an RRC reestablishment message or an RRC setup message.

[0451] Note 45. An apparatus for random access, applied to a network device, wherein the apparatus comprises:

[0452] a third receiving unit, configured to receive a random access preamble sent by a terminal device on a physical random access channel resource; wherein the random access preamble is used to indicate that the terminal device has sidelink data to send, and / or the physical random access channel resource is used to indicate that the terminal device has sidelink data to send;

[0453] a second sending unit, configured to send a random access response to the terminal device.

[0454] Note 46. The apparatus of Note 45, wherein the random access response contains a sidelink grant.

[0455] Note 47. The apparatus of Note 46, wherein the sidelink grant is indicated using reserved bits in the random access response.

[0456] Note 48. The apparatus of any one of Note 46 or 47, wherein the random access response does not contain a time advance control field and a temporary C-RNTI field.

[0457] Note 49. The apparatus of any one of Note 45 to 48, wherein the sidelink data is a sidelink MAC CE.

[0458] Note 50, the apparatus according to Note 49, wherein the sidelink MAC CE is a sidelink CSI reporting MAC CE.

[0459] Note 51, the apparatus according to any one of Notes 45 to 50, wherein the apparatus further comprises:

[0460] a configuration unit, configured to configure the set of random access preambles and / or the set of physical random access channel resources;

[0461] a third sending unit, configured to send the configured set of random access preambles and / or the set of physical random access channel resources to the terminal device.

[0462] Note 52, the apparatus according to Note 51, wherein the third sending unit sends the set of random access preambles and / or the set of physical random access channel resources using a radio resource control (RRC) reconfiguration message or system information or an RRC resume message or an RRC reestablishment message or an RRC setup message.

[0463] Note 53, a random access apparatus applied to a terminal device, wherein the apparatus comprises:

[0464] a fourth sending unit, configured to send an uplink message including sidelink related information to a network device on a physical uplink data channel in a random access procedure;

[0465] a fourth receiving unit, configured to receive a contention resolution message sent by the network device.

[0466] Note 54, a random access apparatus applied to a network device, wherein the apparatus comprises:

[0467] a fifth receiving unit, configured to receive an uplink message including sidelink related information sent by the terminal device on a physical uplink data channel;

[0468] a fifth sending unit, configured to send a contention resolution message to the terminal device.

[0469] Note 55, the apparatus according to Note 53 or 54, wherein the sidelink related information is a sidelink buffer status report or a logical channel identifier (LCID) corresponding to sidelink data or a sidelink (SL) RNTI of the terminal device.

[0470] Note 56, the apparatus according to any one of Notes 53 to 55, wherein the sidelink related information is used to indicate that the terminal device has sidelink data to send.

[0471] Clause 57. The apparatus of any of clauses 53 to 56, wherein the uplink message further comprises a C-RNTI of the terminal device.

[0472] Clause 58. The apparatus of any of clauses 53 to 57, wherein the sidelink data is a sidelink MAC CE.

[0473] Clause 59. The apparatus of clause 58, wherein the sidelink MAC CE is a sidelink CSI reporting MAC CE.

[0474] Clause 60. The apparatus of clause 55, wherein the sidelink buffer status report indicates a logical channel group and / or a buffer size corresponding to the sidelink MAC CE.

[0475] Clause 61. A sidelink transmission apparatus, applied to a terminal device, the apparatus comprising:

[0476] a sixth receiving unit, configured to receive a scheduling request configuration corresponding to sidelink data sent by a network device, the scheduling request configuration comprising a set of PUCCH resources on a partial bandwidth BWP;

[0477] a triggering unit, configured to trigger a scheduling request when the terminal device has sidelink data to send and no sidelink resource is currently available;

[0478] a sixth sending unit, configured to send the scheduling request using a PUCCH resource corresponding to the scheduling request configuration.

[0479] Clause 62. A resource configuration apparatus, applied to a network device, the apparatus comprising:

[0480] a seventh sending unit, configured to send a scheduling request configuration corresponding to the sidelink data to a terminal device, the scheduling request configuration comprising a set of PUCCH resources on a partial bandwidth BWP;

[0481] a seventh receiving unit, configured to receive the scheduling request sent by the terminal device using a PUCCH resource corresponding to the scheduling request configuration.

[0482] Clause 63. The apparatus of clause 61 or 62, wherein the number of scheduling request configurations is one.

[0483] Clause 64. The apparatus of any of clauses 61 to 63, wherein the scheduling request configuration comprises a set of PUCCH resources on each BWP.

[0484] In any one of the apparatuses of the clauses 61-64, at most one PUCCH resource is configured on each BWP in one scheduling request configuration.

[0485] In any one of the apparatuses of the clauses 61-65, the seventh sending unit sends the scheduling request configuration using a radio resource control (RRC) reconfiguration message, system information, an RRC resume message, an RRC reestablishment message, or an RRC setup message.

[0486] In any one of the apparatuses of the clauses 61-66, the sidelink data is a sidelink MAC CE.

[0487] In the apparatus of the clause 67, the sidelink MAC CE is a sidelink CSI reporting MAC CE.

[0488] Clause 69. An apparatus for random access, applied to a terminal device, wherein the apparatus comprises:

[0489] an eighth sending unit configured to send a scheduling request to a network device;

[0490] a first processing unit configured to, when a number of sent scheduling requests reaches a predetermined maximum number of sending times, not initiate a random access procedure, wherein the scheduling request is a scheduling request triggered when the terminal device has a sidelink MAC CE to send and currently has no available sidelink resource;

[0491] or,

[0492] when the number of sent scheduling requests reaches the predetermined maximum number of sending times, initiate a random access procedure, wherein the scheduling request is a scheduling request triggered by a non-sidelink MAC CE.

[0493] Clause 70. The apparatus of the clause 69, wherein the sidelink MAC CE is a CSI reporting MAC CE.

[0494] Clause 71. An apparatus for sending a scheduling request, applied to a terminal device, wherein the apparatus comprises:

[0495] a triggering unit configured to trigger a scheduling request when the terminal device has sidelink data to send and currently has no available sidelink resource;

[0496] a ninth sending unit configured to send a scheduling request to a network device;

[0497] a second processing unit, configured to stop sending the scheduling request or cancel the scheduling request when the sending of the scheduling request exceeds the maximum latency of the sidelink data.

[0498] Paragraph 72, a random access apparatus applied to a terminal device, wherein the apparatus comprises:

[0499] a triggering unit, configured to trigger a scheduling request when the terminal device has sidelink data to send and no sidelink resource is currently available;

[0500] a third processing unit, configured to initiate a random access procedure when the scheduling request does not have a valid PUCCH resource configured or the sending of the scheduling request reaches a maximum number of times;

[0501] a fourth processing unit, configured to stop the random access procedure when the duration of the random access procedure exceeds the maximum latency of the sidelink data.

[0502] Paragraph 73, the apparatus according to any one of paragraphs 71-72, wherein the sidelink data is a sidelink MAC CE or a sidelink logical channel data.

[0503] Paragraph 74, the apparatus according to paragraph 73, wherein the sidelink MAC CE is a sidelink CSI reporting MAC CE.

[0504] Paragraph 75, a terminal device comprising a memory and a processor, the memory storing a computer program, and the processor being configured to execute the computer program to implement the method according to any one of paragraphs 1-7, 16, 18-24, 26-37.

[0505] Paragraph 76, a network device comprising a memory and a processor, the memory storing a computer program, and the processor being configured to execute the computer program to implement the method according to any one of paragraphs 8-15, 17-23, 25-31.

[0506] Paragraph 77, a communication system comprising the terminal device according to paragraph 75.

[0507] Paragraph 78, a communication system comprising the network device according to paragraph 76.

Claims

1. A scheduling request sending device, applied to a terminal device side, wherein, The device includes: A memory and a processor coupled to the memory; the processor is used for: A scheduling request is triggered when the terminal device has sidelink channel state information reporting (CSI reporting) to send and there are currently no available sidelink resources; Send a scheduling request to the network device; When the side link CSI reporting expires, the scheduling request is cancelled. Wherein, if the maximum delay of the side link CSI reporting is exceeded, the side link CSI reporting expires. When the scheduling request (SR) configuration has valid Physical Uplink Control Channel (PUCCH) resources, the processor also uses the PUCCH resources in the SR configuration to send the scheduling request. The processor also includes a disable timer, which monitors the SRs transmitted in the PUCCH resource. When the disable timer expires, the processor retransmits the SR. The processor also receives the SR configuration corresponding to the CSIreporting of the side link, which is sent by the network device via an RRC reconfiguration message. For the SR corresponding to the aforementioned side link CSIreporting, configure at most one PUCCH resource per bandwidth part (BWP).

2. The apparatus according to claim 1, wherein, The maximum latency of the side link data is exceeded when the sending of the scheduling request exceeds the maximum latency of the side link data.

3. The apparatus according to claim 1, wherein when the scheduling request is triggered, the scheduling request is a pending scheduling request.

4. The apparatus according to claim 1, wherein, The maximum latency of the side link data is 4 to 20 milliseconds.

5. A scheduling request receiving device, applied to the network device side, wherein, The device includes: A memory and a processor coupled to the memory; the processor is used for: After a scheduling request is triggered when the terminal device has a sidelink channel state information reporting (CSI) report to send but there are currently no available sidelink resources, the scheduling request sent by the terminal device is received. When the side link CSI reporting expires, the scheduling request will not be received. Wherein, if the maximum delay of the side link CSI reporting is exceeded, the side link CSI reporting expires. When the scheduling request (SR) configuration has valid Physical Uplink Control Channel (PUCCH) resources, the processor also uses the PUCCH resources in the SR configuration to receive the scheduling request. The processor also includes a disable timer, which monitors the SRs transmitted in the PUCCH resource. When the disable timer expires, the processor resumes receiving the SRs. The processor also sends the SR configuration corresponding to the CSIreporting of the side link, which is sent by the network device via an RRC reconfiguration message. For the SR corresponding to the aforementioned side link CSIreporting, configure at most one PUCCH resource per bandwidth part (BWP).

6. The apparatus according to claim 5, wherein, The maximum latency of the side link data is exceeded when the sending of the scheduling request exceeds the maximum latency of the side link data.

7. The apparatus according to claim 5, wherein when the scheduling request is triggered, the scheduling request is a pending scheduling request.

8. The apparatus according to claim 5, wherein, The maximum latency of the side link data is 4 to 20 milliseconds.

Images