Method and device for determining resources

Abstract

The present application provides a method and device for determining resources, the method comprising: a transmitting end user equipment receives a scheduling request SR configuration information sent by a network device, the SR configuration information corresponds to a signaling radio bearer SL SRB of a side link, the SR configuration information is used to indicate a first SR resource, the transmitting end user equipment is a device in the side link SL; the transmitting end user equipment sends an SR to the network device through the first SR resource. The method can determine the SR configuration information for the transmitting end user equipment in the side link, further determine the SR resource, and request uplink resources or SL resources from the base station through the SR resource, thereby reducing signaling overhead, reducing power consumption of the user equipment, and reducing the delay in obtaining uplink resources.

Description

[0001] This application is a divisional application. The application number of the original application is 202010280182.8, and the original application date is April 10, 2020. The entire contents of the original application are incorporated into this application by reference. Technical Field

[0002] The present application relates to the field of communications, and more specifically, to a method and device for determining resources in the field of communications. Background Art

[0003] In the fifth generation (5G) mobile communication system, for the device-to-device (D2D) direct communication mode or vehicle to everything (V2X) scenario, the transmission user equipment (TX UE) can send data directly to the reception user equipment (RX UE) without the need for transfer through network equipment or cellular network. The direct link between TX UE and RX UE is called the sidelink (SL), and the interface between TX UE and RX UE is called the PC5 interface; the link between UE and network equipment is called the cellular link, and the interface between UE and network equipment is called the Uu interface.

[0004] In D2D communication, when the TX UE has data to send to the RX UE, if there are currently no available SL resources, the TX UE can send a buffer status report (BSR) to the network device, and use the BSR to tell the network device the amount of data to be sent. The network device can decide how many SL resources to allocate to the TX UE based on the amount of data to be sent in the BSR to achieve communication between the TX UE and the RX UE. Specifically, after the TX UE triggers the BSR, if there are currently no available SL resources to send the BSR, the TX UE first sends a scheduling request (SR) to the network device to inform the network device that there is data to be sent. After receiving the SR, the network device can allocate an uplink resource that is at least enough to send the BSR to the TX UE, and the TX UE uses the uplink resource to send the BSR to the network device.

[0005] Among them, when the TX UE sends an SR to the network device, it can be sent through the SR resources. At present, for D2D / V2X communication, the TX UE does not have SR resources configured for the SL signaling radio bearer (SRB), that is, for the transmission of data carried on the SLSRB, it is impossible to request SL resources or UL resources from the network device by sending SR. It can only request uplink resources from the network device by triggering contention-based random access to send BSR, and then request SL resources. However, requesting uplink resources through random access will increase signaling overhead, increase power consumption, and increase communication delay. Summary of the invention

[0006] The present application provides a method and device for determining resources, which can determine SR configuration information for a transmitting user equipment in a side link, further determine SR resources, and request uplink resources or SL resources from a base station through SR resources, thereby reducing signaling overhead, reducing power consumption of user equipment, and reducing the delay in obtaining uplink resources.

[0007] In a first aspect, a method for determining resources is provided, the method comprising: a sending user equipment receives a scheduling request SR configuration information sent by a network device, the SR configuration information corresponds to a signaling radio bearer SL SRB of a side link, the SR configuration information is used to indicate a first SR resource, and the sending user equipment is a device in the side link SL; the sending user equipment sends an SR to the network device through the first SR resource.

[0008] When the sending user equipment has no available uplink resources (uplink) and the sending user equipment has cached messages to be transmitted to other receiving user equipment, a SR resource can be determined for the sending user equipment through the method for determining resources in an embodiment of the present application, and used to send SR to the network device. SR is used to request allocation of uplink resources or sidelink resources for transmitting new data, so that the network device can configure uplink resources for sending BSR for the sending user equipment, and then allocate sidelink (SL) resources to the sending user equipment and UE 30, or the network device can allocate sidelink (SL) resources to the sending user equipment.

[0009] It should be understood that the "message to be transmitted" mentioned in the embodiment of the present application may be one or more of the PC5-RRC messages and PC5-S messages listed above, or in other words, the "message to be transmitted" mentioned in the embodiment of the present application may be a message carried on the SL SRB.

[0010] Exemplarily, the message to be transmitted includes at least one of a PC5 radio resource control PC5-RRC message, a non-security protected PC5 signal PC5-S message, a PC5-S message after PC5-S security establishment, and a security protected PC5-S message.

[0011] It should also be understood that the SR configuration information corresponds to the SL SRB, which may be one SL SRB corresponding to one SR configuration information, or one SL SRB corresponding to multiple SR configuration information, or one SR configuration information corresponding to multiple SL SRBs. The embodiment of the present application is not limited to this.

[0012] Optionally, the SR configuration information (schedulingRequestConfig) may include at least one of: an SR identification ID (schedulingRequestID), a prohibition timer (SR-ProhibitTimer) for SR transmission, a maximum number of SR retransmissions (SR-TransMax), and the like.

[0013] In addition to the SR configuration information (schedulingRequestConfig), the network device may also configure SR resource configuration information (SchedulingRequestResourceConfig) for the transmitting user equipment. The SR resource configuration information may include: SR ID (schedulingRequestID), SR resource ID (schedulingRequestResourceID), SR period and offset within the period (periodicityAndOffset), etc.

[0014] Therefore, when the sending user equipment receives the SR configuration information sent by the network device, it can determine the SRID, which can correspond to the SR resource ID, and then determine an SR resource based on the SR resource ID, such as the "first SR resource" referred to in the embodiment of the present application, that is, the first SR resource is the uplink resource that the sending user equipment finally sends the SR to the network device.

[0015] Through the above technical solution, the base station configures SR configuration information for the UE, and the UE can determine the first SR resource through the SR configuration information, and send SR to the base station through the first SR resource to request uplink resources or SL resources, thereby reducing signaling overhead, reducing UE power consumption and reducing the delay in obtaining uplink resources.

[0016] In combination with the first aspect, in some possible implementations, the SR configuration information is preset SR configuration information, and before the sending user equipment sends the SR to the network device through the first SR resource, the method also includes: the sending user equipment determines that the SR configuration information is preset SR configuration information.

[0017] In a second aspect, a method for determining resources is provided, the method comprising: a sending user device determines a corresponding first SR resource according to preset SR configuration information, the sending user device being a device in a side link SL; the sending user device sends an SR to a network device through the first SR resource.

[0018] Optionally, the preset SR configuration information can be understood as specifying SR configuration information in the protocol, and the base station 10 and the UE 20 can reach a consensus and both know which preset SR configuration information the preset SR configuration information includes. It should be understood that one or more preset SR configuration information is specified in the protocol, and the embodiment of the present application does not limit the number of the preset SR configuration information.

[0019] Optionally, the preset SR configuration information may be included in a dedicated configuration instruction for SCCH of the base station 10. The base station 10 configures the preset SR configuration information to the UE 20 when configuring the SCCH. Then, the first SR resource may be understood as the SR resource determined by the preset SR configuration information.

[0020] Exemplarily, in the dedicated configuration instruction of SCCH, a parameter may be added to indicate the SR configuration information, such as schedulingRequest ID=X, where X may be taken from any one of the set {X, Y, Z, M, N…}. Alternatively, the parameter may indicate multiple ones of the set {X, Y, Z, M, N…}, such as schedulingRequestID=X,Y,Z.

[0021] The above technical solution presets SR configuration information for the network device and the user equipment in the standard. In the specific implementation process, the network device can flexibly decide whether to configure dedicated SR resources for the SL SRB of the user equipment. When it is determined that dedicated SR resources can be configured for the SL SRB of the user equipment, the network device carries the preset SR configuration information when configuring SR resources for the user equipment. The user equipment can send SR to the network device through the preset SR resources to request uplink resources or SL resources, thereby reducing signaling overhead, reducing power consumption of the user equipment, and reducing the delay in obtaining uplink resources.

[0022] In combination with the above-mentioned implementation methods, in some possible implementation methods, the SR configuration information is the SR configuration information of at least one signaling radio bearer SRB between the transmitting user equipment and the network device; and / or the SR configuration information is the SR configuration information of at least one signaling radio bearer DRB between the transmitting user equipment and the network device; and / or the SR configuration information is the SR configuration information of at least one sidelink data radio bearer SL DRB of the transmitting user equipment; and / or the SR configuration information is the SR configuration information of at least one sidelink channel state information CSI report of the transmitting user equipment.

[0023] Through the above technical solution, when SR resources are configured for a user device through a network device, the determined SR configuration information is associated with the existing SR configuration information. The user device can determine the first SR resource through the SR configuration information, and send SR to the network device through the first SR resource to request uplink resources or SL resources, thereby reducing signaling overhead, reducing power consumption of the user device, and reducing the delay in obtaining uplink resources.

[0024] In combination with the above implementation methods, in some possible implementation methods, the sending user equipment caches messages to be transmitted that are sent to at least one receiving user equipment, and each of the messages to be transmitted has the same SR configuration information; or each of the messages to be transmitted has different SR configuration information; or the same type of messages to be transmitted have the same SR configuration information, and different types of messages to be transmitted have different SR configuration information; or at least two messages to be transmitted have the same SR configuration information; or the messages to be transmitted of the same receiving user equipment have the same SR configuration information; or different types of messages to be transmitted of the same receiving user equipment have different SR configuration information; or different types of messages to be transmitted of different receiving user equipment have different SR configuration information; or the same type of messages to be transmitted of different receiving user equipment have the same SR configuration information.

[0025] In summary, the network device configures different SR configuration information for different target user equipments. Under each target UE, the SL SRB carrying the PC5-RRC message and the SL SRB carrying the three types of PC5-S messages may have different SR configuration information.

[0026] In combination with the above implementations, in some possible implementations, the SR configuration information also includes indication information, and the indication information is used to indicate whether the first SR resource is an SR resource for requesting a sidelink, or the indication information is used to indicate whether the SR configuration information can be used for a SL SRB in a sidelink.

[0027] Through the above technical solution, by adding indication information to the SR configuration information determined by the network device, the user equipment can determine whether the first resource can be used as an SR resource for requesting a sidelink according to the indication information. When it can be used as an SR resource for requesting a sidelink, the user equipment can determine the first SR resource through the SR configuration information, and send an SR to the network device through the first SR resource to request an uplink resource or SL resource, thereby reducing signaling overhead, reducing power consumption of the user equipment, and reducing the delay in obtaining uplink resources. When it cannot be used as an SR resource for requesting a sidelink, the user equipment can trigger a random access process to obtain uplink resources.

[0028] In combination with the above implementations, in some possible implementations, the SR configuration information includes one or more SR identification IDs.

[0029] According to a third aspect, a method for determining resources is provided, the method comprising: a network device sends a scheduling request SR configuration information to a transmitting user equipment, the SR configuration information corresponds to a signaling radio bearer SL SRB of a side link, the SR configuration information is used to indicate a first SR resource, and the transmitting user equipment is a device in the side link SL; the network device receives the SR sent by the transmitting user equipment through the first SR resource.

[0030] In combination with the above implementations, in some possible implementations, the SR configuration information is preset SR configuration information.

[0031] In a fourth aspect, a method for determining resources is provided, the method comprising: a network device determines a corresponding first SR resource according to preset SR configuration information; the network device receives an SR sent by a sending user device through the first SR resource, and the sending user device is a device in a side link SL.

[0032] In combination with the above-mentioned implementation methods, in some possible implementation methods, the SR configuration information is the SR configuration information of at least one signaling radio bearer SRB between the transmitting user equipment and the network device; and / or the SR configuration information is the SR configuration information of at least one signaling radio bearer DRB between the transmitting user equipment and the network device; and / or the SR configuration information is the SR configuration information of at least one sidelink data radio bearer SL DRB of the transmitting user equipment; and / or the SR configuration information is the SR configuration information of at least one sidelink channel state information CSI report of the transmitting user equipment.

[0033] In combination with the above implementation methods, in some possible implementation methods, the sending user equipment caches messages to be transmitted that are sent to at least one receiving user equipment, and each of the messages to be transmitted has the same SR configuration information; or each of the messages to be transmitted has different SR configuration information; or the same type of messages to be transmitted have the same SR configuration information, and different types of messages to be transmitted have different SR configuration information; or at least two messages to be transmitted have the same SR configuration information; or the messages to be transmitted of the same receiving user equipment have the same SR configuration information; or different types of messages to be transmitted of the same receiving user equipment have different SR configuration information; or different types of messages to be transmitted of different receiving user equipment have different SR configuration information; or the same type of messages to be transmitted of different receiving user equipment have the same SR configuration information.

[0034] In combination with the above implementations, in some possible implementations, the SR configuration information also includes indication information, and the indication information is used to indicate whether the first SR resource is an SR resource for requesting a sidelink, or the indication information is used to indicate whether the SR configuration information can be used for a SL SRB in a sidelink.

[0035] In combination with the above implementation methods, in some possible implementation methods, the message to be transmitted includes at least one of a PC5 wireless resource control PC5-RRC message, a non-security protected PC5 signal PC5-S message, a PC5-S message after PC5-S security establishment, and a security protected PC5-S message.

[0036] In combination with the above implementations, in some possible implementations, the SR configuration information includes one or more SR identification IDs.

[0037] In the fifth aspect, a device for determining resources is provided, which includes: a receiving unit, used to receive scheduling request SR configuration information sent by a network device, the SR configuration information corresponds to a signaling radio bearer SL SRB of a side link, and the SR configuration information is used to indicate a first SR resource; a sending unit, used to send SR to the network device through the first SR resource.

[0038] In combination with the above implementations, in some possible implementations, the SR configuration information is preset SR configuration information, and the device further includes: a processing unit, configured to determine that the SR configuration information is preset SR configuration information.

[0039] In a sixth aspect, a device for determining resources is provided, the device comprising: a processing unit, used to determine a corresponding first SR resource according to preset SR configuration information; and a sending unit, used to send an SR to a network device through the first SR resource.

[0040] In combination with the above implementations, in some possible implementations, the SR configuration information is the SR configuration information of at least one signaling radio bearer SRB between the device and the network device; and / or the SR configuration information is the SR configuration information of at least one signaling radio bearer DRB between the device and the network device; and / or the SR configuration information is the SR configuration information of at least one sidelink data radio bearer SL DRB of the device; and / or the SR configuration information is the SR configuration information of at least one sidelink channel state information CSI report of the device.

[0041] In combination with the above implementation methods, in some possible implementation methods, the device caches messages to be transmitted that are sent to at least one receiving user device, and each of the messages to be transmitted has the same SR configuration information; or each of the messages to be transmitted has different SR configuration information; or the same type of messages to be transmitted have the same SR configuration information, and different types of messages to be transmitted have different SR configuration information; or at least two messages to be transmitted have the same SR configuration information; or the messages to be transmitted of the same receiving user device have the same SR configuration information; or different types of messages to be transmitted of the same receiving user device have different SR configuration information; or different types of messages to be transmitted of different receiving user devices have different SR configuration information; or the same type of messages to be transmitted of different receiving user devices have the same SR configuration information.

[0042] In combination with the above implementations, in some possible implementations, the SR configuration information also includes indication information, and the indication information is used to indicate whether the first SR resource is an SR resource for requesting a sidelink, or the indication information is used to indicate whether the SR configuration information can be used for a SL SRB in a sidelink.

[0043] In combination with the above implementation methods, in some possible implementation methods, the message to be transmitted includes at least one of a PC5 wireless resource control PC5-RRC message, a non-security protected PC5 signal PC5-S message, a PC5-S message after PC5-S security establishment, and a security protected PC5-S message.

[0044] In combination with the above implementations, in some possible implementations, the SR configuration information includes one or more SR identification IDs.

[0045] In the seventh aspect, a device for determining resources is provided, which includes: a sending unit, used to send scheduling request SR configuration information to a sending user equipment, the SR configuration information corresponds to a signaling radio bearer SL SRB of a side link, the SR configuration information is used to indicate a first SR resource, and the sending user equipment is a device in the side link SL; a receiving unit, used to receive the SR sent by the sending user equipment through the first SR resource.

[0046] In combination with the above implementations, in some possible implementations, the SR configuration information is preset SR configuration information.

[0047] In the eighth aspect, a device for determining resources includes: a processing unit, used to determine a corresponding first SR resource according to preset SR configuration information; a receiving unit, used to receive an SR sent by a sending user equipment through the first SR resource, and the sending user equipment is a device in a side link SL.

[0048] In combination with the above-mentioned implementation methods, in some possible implementation methods, the SR configuration information is the SR configuration information of at least one signaling radio bearer SRB between the transmitting user equipment and the network device; and / or the SR configuration information is the SR configuration information of at least one signaling radio bearer DRB between the transmitting user equipment and the network device; and / or the SR configuration information is the SR configuration information of at least one sidelink data radio bearer SL DRB of the transmitting user equipment; and / or the SR configuration information is the SR configuration information of at least one sidelink channel state information CSI report of the transmitting user equipment.

[0049] In combination with the above implementation methods, in some possible implementation methods, the sending user equipment caches messages to be transmitted that are sent to at least one receiving user equipment, and each of the messages to be transmitted has the same SR configuration information; or each of the messages to be transmitted has different SR configuration information; or the same type of messages to be transmitted have the same SR configuration information, and different types of messages to be transmitted have different SR configuration information; or at least two messages to be transmitted have the same SR configuration information; or the messages to be transmitted of the same receiving user equipment have the same SR configuration information; or different types of messages to be transmitted of the same receiving user equipment have different SR configuration information; or different types of messages to be transmitted of different receiving user equipment have different SR configuration information; or the same type of messages to be transmitted of different receiving user equipment have the same SR configuration information.

[0050] In combination with the above implementations, in some possible implementations, the SR configuration information also includes indication information, and the indication information is used to indicate whether the first SR resource is an SR resource for requesting a sidelink, or the indication information is used to indicate whether the SR configuration information can be used for a SL SRB in a sidelink.

[0051] In combination with the above implementation methods, in some possible implementation methods, the message to be transmitted includes at least one of a PC5 wireless resource control PC5-RRC message, a non-security protected PC5 signal PC5-S message, a PC5-S message after PC5-S security establishment, and a security protected PC5-S message.

[0052] In combination with the above implementations, in some possible implementations, the SR configuration information includes one or more SR identification IDs.

[0053] In the ninth aspect, a method for determining resources is provided, which is applied to a system consisting of a sending user equipment, at least one receiving user equipment and a network device, the method comprising: the sending user equipment receives a scheduling request SR configuration information sent by the network device, and the SR configuration information corresponds to a signaling radio bearer SL SRB of a side link; the sending user equipment determines a corresponding first SR resource according to the SR configuration information; the sending user equipment sends an SR to the network device through the first SR resource.

[0054] In combination with the ninth aspect, in some possible implementations, the SR configuration information is preset SR configuration information; or when the SR configuration information is not the preset SR configuration information, the method also includes: the sending user equipment initiating a random access process to the network device.

[0055] In combination with the ninth aspect and the above-mentioned implementation methods, in some possible implementation methods, the SL SRB is associated with the SR configuration information corresponding to at least one signaling radio bearer SRB of the network device; or the SL SRB is associated with the SR configuration information corresponding to at least one data radio bearer DRB of the transmitting user equipment and the network device; or the SL SRB is associated with the SR configuration information corresponding to at least one side link channel state information CSI report of the transmitting user equipment.

[0056] In combination with the ninth aspect and the above-mentioned implementation methods, in some possible implementation methods, when the sending user equipment caches a message to be transmitted to at least one receiving user equipment, the preset SR configuration information is determined based on the message type of the message to be transmitted, and the message to be transmitted is carried in the SL SRB.

[0057] In combination with the ninth aspect and the above-mentioned implementation methods, in some possible implementation methods, the message to be transmitted includes a first message set and a second message set, each message set includes at least one message, and the message types in the first message set and the second message set are different, and the preset SR configuration information includes a first SR configuration information set and a second SR configuration information set, each SR configuration information set includes at least one SR configuration information, wherein each SR configuration information in the first SR configuration information set corresponds to at least one message carried in the first message set, and each SR configuration information in the second SR configuration information set corresponds to at least one message carried in the second message set.

[0058] In combination with the ninth aspect and the above-mentioned implementation methods, in some possible implementation methods, the destination address of each message in the first message set and the second message set is the first receiving user device, or the destination address of each message in the first message set is the first receiving user device, and the destination address of each message in the second message set is the second receiving user device.

[0059] In combination with the ninth aspect and the above-mentioned implementation methods, in some possible implementation methods, the preset SR configuration information is determined according to the destination address corresponding to the message to be transmitted, and the message to be transmitted is carried in the SL SRB.

[0060] In combination with the ninth aspect and the above-mentioned implementation methods, in some possible implementation methods, the message to be transmitted includes a third message set and a fourth message set, each message set includes at least one message, and the destination address of each message in the third message set is a first receiving user device, and the destination address of each message in the fourth message set is a second receiving user device, and the preset SR configuration information includes a third SR configuration information set and a fourth SR configuration information set, each SR configuration information set includes at least one SR configuration information, wherein any one of the SR configuration information in the third SR configuration information set is associated with each message in the third message set, and any one of the SR configuration information sets in the fourth SR configuration information set is associated with each message in the fourth message set.

[0061] In combination with the ninth aspect and the above-mentioned implementation methods, in some possible implementation methods, the SR configuration information also includes indication information for indicating whether the first SR resource can be used to send the SR to the network device.

[0062] In combination with the ninth aspect and the above-mentioned implementation methods, in some possible implementation methods, the message to be transmitted includes at least one of a PC5 wireless resource control PC5-RRC message, a non-security-protected PC5 signal PC5-S message, a PC5-S message after PC5-S security establishment, and a security-protected PC5-S message.

[0063] In combination with the ninth aspect and the above implementations, in some possible implementations, the SR configuration information includes a SR identification ID.

[0064] In the tenth aspect, a method for determining resources is provided, which is applied to a system consisting of a sending user equipment, at least one receiving user equipment and a network device, the method comprising: the network device sends a scheduling request SR configuration information to the sending user equipment, the SR configuration information corresponds to a signaling radio bearer SL SRB of a side link; the network device determines a corresponding first SR resource based on the SR configuration information; the network device receives the SR sent by the sending user equipment through the first SR resource.

[0065] In combination with the tenth aspect, in some possible implementations, the SR configuration information is preset SR configuration information; or when the SR configuration information is not the preset SR configuration information, the method also includes: the network device receives a random access process initiated by the sending user equipment.

[0066] In combination with the tenth aspect and the above-mentioned implementation methods, in some possible implementation methods, the SL SRB is associated with the SR configuration information corresponding to at least one signaling radio bearer SRB of the network device; or the SL SRB is associated with the SR configuration information corresponding to at least one data radio bearer DRB of the transmitting user equipment and the network device; or the SL SRB is associated with the SR configuration information corresponding to at least one side link channel state information CSI report of the transmitting user equipment.

[0067] In combination with the tenth aspect and the above-mentioned implementation methods, in some possible implementation methods, when the sending user equipment caches a message to be transmitted to at least one receiving user equipment, the preset SR configuration information is determined based on the message type of the message to be transmitted, and the message to be transmitted is carried in the SL SRB.

[0068] In combination with the tenth aspect and the above-mentioned implementation methods, in some possible implementation methods, the message to be transmitted includes a first message set and a second message set, each message set includes at least one message, and the message types in the first message set and the second message set are different, and the preset SR configuration information includes a first SR configuration information set and a second SR configuration information set, each SR configuration information set includes at least one SR configuration information, wherein each SR configuration information in the first SR configuration information set corresponds to at least one message carried in the first message set, and each SR configuration information in the second SR configuration information set corresponds to at least one message carried in the second message set.

[0069] In combination with the tenth aspect and the above-mentioned implementation methods, in some possible implementation methods, the destination address of each message in the first message set and the second message set is the first receiving user device, or the destination address of each message in the first message set is the first receiving user device, and the destination address of each message in the second message set is the second receiving user device.

[0070] In combination with the tenth aspect and the above-mentioned implementation methods, in some possible implementation methods, the preset SR configuration information is determined according to the destination address corresponding to the message to be transmitted, and the message to be transmitted is carried in the SL SRB.

[0071] In combination with the tenth aspect and the above-mentioned implementation methods, in some possible implementation methods, the message to be transmitted includes a third message set and a fourth message set, each message set includes at least one message, and the destination address of each message in the third message set is a first receiving user device, and the destination address of each message in the fourth message set is a second receiving user device, and the preset SR configuration information includes a third SR configuration information set and a fourth SR configuration information set, each SR configuration information set includes at least one SR configuration information, wherein any one of the SR configuration information in the third SR configuration information set is associated with each message in the third message set, and any one of the SR configuration information sets in the fourth SR configuration information set is associated with each message in the fourth message set.

[0072] In combination with the tenth aspect and the above-mentioned implementation methods, in some possible implementation methods, the SR configuration information also includes indication information for indicating whether the first SR resource can be used to send the SR to the network device.

[0073] In combination with the tenth aspect and the above-mentioned implementation methods, in some possible implementation methods, the message to be transmitted includes at least one of a PC5 wireless resource control PC5-RRC message, a non-security-protected PC5 signal PC5-S message, a PC5-S message after PC5-S security establishment, and a security-protected PC5-S message.

[0074] In combination with the tenth aspect and the above-mentioned implementation manners, in some possible implementation manners, the SR configuration information includes a SR identification ID.

[0075] In an eleventh aspect, a communication device is provided, which has the function of implementing the sending end user equipment in the method design of the first aspect, the second aspect, and the ninth aspect. These functions can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the above functions.

[0076] In a twelfth aspect, a communication device is provided, which has the functions of implementing the network device (e.g., base station) in the method design of the third aspect, the fourth aspect, and the tenth aspect. These functions can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the above functions.

[0077] In a thirteenth aspect, a terminal device is provided, comprising a transceiver and a processor. Optionally, the terminal device further comprises a memory. The processor is used to control the transceiver to send and receive signals, the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that the terminal device executes the method in any possible implementation of the first aspect, the second aspect, and the ninth aspect.

[0078] In a fourteenth aspect, a network device is provided, comprising a transceiver and a processor. Optionally, the network device further comprises a memory. The processor is used to control the transceiver to send and receive signals, the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that the network device executes the method in any possible implementation of the third aspect, the fourth aspect, and the tenth aspect.

[0079] In the fifteenth aspect, a communication system is provided, which includes the sending user equipment of the fifth and sixth aspects and the network equipment of the seventh and eighth aspects; or, the system includes the sending user equipment of the ninth aspect and the network equipment of the tenth aspect; or, the system includes the communication device of the eleventh and twelfth aspects; or, the system includes the terminal equipment of the eleventh aspect and the network equipment of the twelfth aspect.

[0080] In a sixteenth aspect, a communication device is provided, which may be a transmitting end user equipment in the above method design, or a chip set in the transmitting end user equipment. The communication device includes: a processor, coupled with a memory, and can be used to execute instructions in the memory to implement the method executed by the transmitting end user equipment in any possible implementation manner described above. Optionally, the communication device also includes a memory. Optionally, the communication device also includes a communication interface, and the processor is coupled to the communication interface.

[0081] When the communication device is a transmitting end user equipment, the communication interface may be a transceiver, or an input / output interface.

[0082] When the communication device is a chip configured in a transmitting end user equipment, the communication interface may be an input / output interface.

[0083] Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0084] In a seventeenth aspect, a communication device is provided, which may be a network device in the above method design, or a chip set in the network device. The communication device includes: a processor, coupled to a memory, and can be used to execute instructions in the memory to implement the method executed by the network device in any possible implementation manner. Optionally, the communication device also includes a memory. Optionally, the communication device also includes a communication interface, and the processor is coupled to the communication interface.

[0085] When the communication device is a network device, the communication interface may be a transceiver, or an input / output interface.

[0086] When the communication device is a chip configured in a network device, the communication interface may be an input / output interface.

[0087] Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0088] In an eighteenth aspect, a computer program product is provided, the computer program product comprising: a computer program code, when the computer program code is run on a computer, the computer executes the methods in the above aspects.

[0089] In the nineteenth aspect, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores program code, and when the computer program code runs on a computer, the computer executes the methods in the above aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0090] Figure 1is a schematic diagram of a wireless communication system applicable to an embodiment of the present application.

[0091] Figure 2 This is a schematic diagram of the communication process between UE and base station.

[0092] Figure 3 It is a schematic interactive diagram of a method for determining resources provided in an embodiment of the present application.

[0093] Figure 4 This is a schematic interactive diagram of another method for determining resources provided in an embodiment of the present application.

[0094] Figure 5 This is a schematic diagram of an example of a transmission device for determining resources provided in an embodiment of the present application.

[0095] Figure 6 This is a schematic block diagram of another example of a transmission device for determining resources provided in an embodiment of the present application.

[0096] Figure 7 This is a schematic block diagram of another example of a transmission device for determining resources provided in an embodiment of the present application.

[0097] Figure 8 This is a schematic block diagram of another example of a transmission device for determining resources provided in an embodiment of the present application. DETAILED DESCRIPTION

[0098] The technical solution in this application will be described below in conjunction with the accompanying drawings.

[0099] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD) system, fifth generation (5G) mobile communication system or new radio (NR) communication system and future mobile communication systems, etc.

[0100] Figure 1 1 is a schematic diagram of a wireless communication system 100 applicable to an embodiment of the present application. Figure 1 As shown, the wireless communication system 100 may include one or more network devices, for example, Figure 1 The wireless communication system 100 may also include one or more user equipment (UE), for example, Figure 1 The user equipment 20, the user equipment 30, the user equipment 40, etc. are shown.

[0101] It should be understood that Figure 1 This is just a schematic diagram. The communication system may also include other network devices, such as core network devices, wireless relay devices and wireless backhaul devices. Figure 1 The embodiments of the present application do not limit the number of network devices and user equipment included in the mobile communication system.

[0102] In the mobile communication system 100, the user equipment 20, the user equipment 30, and the user equipment 40 in the embodiment of the present application may also be referred to as a terminal, a terminal device, a mobile station (MS), a mobile terminal (MT), etc. The user equipment in the embodiment of the present application may be a mobile phone, a tablet computer (Pad), a computer with a wireless transceiver function, or a wireless terminal used in scenes such as virtual reality (VR), augmented reality (AR), industrial control (industrial control), self driving, remote medical, smart grid, transportation safety, smart city, and smart home. In this application, the aforementioned user equipment and the chip applicable to the aforementioned user equipment are collectively referred to as user equipment. It should be understood that the embodiment of the present application does not limit the specific technology and specific device form adopted by the user equipment.

[0103] The network device 10 in the embodiment of the present application can be a device for communicating with a user device. The network device can be a base station, an evolved node B (eNB), a home base station, an access point (AP) in a wireless fidelity (WIFI) system, a wireless relay node, a wireless backhaul node, a transmission point (TP) or a transmission and reception point (TRP), etc. It can also be a gNB in ​​an NR system, or it can also be a component or a part of a base station, such as a central unit (CU), a distributed unit (DU) or a baseband unit (BBU). It should be understood that in the embodiment of the present application, the specific technology and specific device form adopted by the network device are not limited. In the present application, the network device can refer to the network device itself, or it can be a chip used in the network device to complete the wireless communication processing function.

[0104] It should be understood that in the embodiment of the present application, the user device or network device includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and a memory (also called main memory). The operating system can be any one or more computer operating systems that implement business processing through a process, such as a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system, or a windows operating system. The application layer includes applications such as a browser, an address book, a word processing software, and an instant messaging software. In addition, the embodiment of the present application does not specifically limit the specific structure of the execution subject of the method provided in the embodiment of the present application, as long as it can communicate according to the method provided in the embodiment of the present application by running a program that records the code of the method provided in the embodiment of the present application, for example, the execution subject of the method provided in the embodiment of the present application can be a user device or a network device, or a functional module in a user device or a network device that can call a program and execute a program.

[0105] It should also be understood that the method for determining resources provided in the embodiments of the present application can be applied to the communication process between user equipment and network equipment, such as the uplink communication process between user equipment 20, user equipment 30, user equipment 40 and base station 10; it can also be applied to the communication between user equipment 20, user equipment 30, user equipment 40, such as the side link communication process, in the vehicle to everything (V2X) service, the communication process between user equipment 20 and user equipment 30, etc., and the present application does not limit this.

[0106] In addition, various aspects or features of the present application can be implemented as methods, devices or products using standard programming and / or engineering techniques. The term "product" used in this application covers computer programs that can be accessed from any computer-readable device, carrier or medium. For example, computer-readable storage media may include, but are not limited to: magnetic storage devices (e.g., hard disks, floppy disks or tapes, etc.), optical disks (e.g., compact discs (CDs), digital versatile discs (DVDs), etc.), smart cards and flash memory devices (e.g., erasable programmable read-only memory (EPROM), cards, sticks or key drives, etc.).

[0107] In addition, the various storage media described herein may represent one or more devices and / or other machine-readable storage media for storing information. The term "machine-readable storage medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing and / or carrying instructions and / or data.

[0108] It should be understood that the methods, situations, categories and divisions of the embodiments in the present application are only for the convenience of description and should not constitute special limitations. The features of various methods, categories, situations and embodiments can be combined without contradiction.

[0109] It should also be understood that the "first", "second" and "third" in the embodiments of the present application are only for distinction and should not constitute any limitation to the present application. For example, the "first resource" and "second resource" in the embodiments of the present application refer to resources for transmitting information between a base station and a user equipment.

[0110] It should also be understood that in the various embodiments of the present application, the size of the serial number of each process does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0111] It should also be noted that in the embodiments of the present application, "pre-setting", "pre-definition", etc. can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in a device (for example, including a user device and a network device). The present application does not limit its specific implementation method, such as the preset rules and preset constants in the embodiments of the present application.

[0112] It should also be noted that "and / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. The technical solution provided by the present application will be described in detail below in conjunction with the accompanying drawings.

[0113] In the following embodiments, without loss of generality, a base station is used as a network device, and the communication process of the side link between at least two user devices and the communication process of the uplink between the user device and the base station are taken as examples to specifically introduce the method for determining resources in the present application. The user device can be any user device in a wireless communication system that has a wireless connection relationship with one or more network devices. It can be understood that any user device in the wireless communication system can implement wireless communication based on the same technical solution. This application does not limit this.

[0114] To facilitate understanding of the embodiments of the present application, several concepts involved in the present application are briefly introduced below.

[0115] 1. Uplink channel

[0116] A channel that can be used to carry uplink control information and / or uplink data. For example, the uplink channel may include a physical uplink control channel (PUCCH) and a physical uplink shared channel (PUSCH) defined in the LTE protocol or the NR protocol, as well as other uplink channels with the above functions defined as the network evolves.

[0117] 2. Sidelink share channel (SSCH)

[0118] SSCH can be used to send sidelink data, etc.

[0119] Optionally, in V2X, data transmitted on the SL can be carried on the SL's data radio bearer (DRB), called "SL DRB".

[0120] 3. Sidelink control channel (SCCH)

[0121] The SCCH may be used to carry signaling, such as sidelink control information and / or sidelink feedback control information.

[0122] Optionally, for unicast transmission scenarios, the signaling transmitted on the SCCH may include PC5-radio resource control (PC5-RRC) messages and PC5-signaling (PC5-S) messages. Among them, the signaling transmitted on the SL may be carried on the signaling radio bearer (SRB) of the SL, referred to as "SLSRB".

[0123] For PC5-RRC messages, one SL SRB is introduced for transmitting PC5-RRC messages.

[0124] For PC5-S messages, three SL SRBs are introduced for transmission:

[0125] 1. Unprotected PC5-S message, such as direct communication request message;

[0126] 2. PC5-S message establishing PC5-S security, such as direct security mode command message and direct security mode complete message;

[0127] 3. Protected PC5-S message.

[0128] The method for determining resources is described below with reference to the accompanying drawings. Figure 2 1 is a schematic diagram of a communication process between a UE 20 and a base station 10. In the D2D communication mode, the user equipment may include a TX UE and a RX UE, and the TX UE and the RX UE communicate with each other through a side link SL allocated by the base station, for example Figure 1 Communication between UE 20 and UE 30 in the communication.

[0129] Specifically, when UE 20 needs to send data to UE 30, UE 20 can be used as a TX UE and UE 30 can be used as a RX UE in the process. After receiving the data buffer, UE 20 can send a buffer status report (buffer status reporting, BSR) to base station 10, and tell base station 10 the amount of data to be sent included in its buffer through BSR. Base station 10 can decide how many side link resources (SL grant) to allocate to UE 20 according to the amount of data to be sent in the BSR.

[0130] In this process, when UE 20 triggers a BSR, if there is no available uplink resource (UL grant), the uplink resource is used for UE 20 to send a BSR to base station 10. UE 20 first sends a scheduling request (scheduling request, SR) to base station 10 to inform base station 10 that there is data to be sent. Based on the above process, Figure 2 As shown, the process 200 may include:

[0131] S210 , the UE 20 sends a scheduling request SR to the base station 10 .

[0132] It should be understood that the SR can be used to inform the base station 10 that the UE 20 has data to send to the UE 30. The SR can be a 1-bit indication information and does not carry information about the amount to be sent. After receiving the SR, the base station 10 can know that the UE 20 currently has data to send to the UE 30, and the base station 10 does not know the current amount of data to be sent.

[0133] S220, the base station 10 allocates uplink resources for sending a BSR to the UE 20.

[0134] Specifically, after receiving the SR, the base station 10 allocates an uplink resource at least sufficient to send the BSR to the UE, and the UE 20 can use the uplink resource to send the BSR to the base station 10. It should be understood that the BSR may include information about the amount of data to be sent.

[0135] S230, UE 20 sends a BSR to base station 10 through the uplink resource.

[0136] S240, the base station 10 allocates available sidelink resources (SLgrant) to the UE 20 according to the amount of data to be sent.

[0137] Specifically, after receiving the BSR, the base station 10 determines the amount of data to be sent from the UE 20 to the UE 30, and decides how many sidelink resources (SL grant) to allocate to the UE 20 according to the amount of data to be sent.

[0138] In S210, the uplink resource for UE 20 to send SR to base station 10 is called "SR resource", and UE 20 can send SR to base station 10 through SR resource. Before this, UE 20 can determine a certain SR resource through SR configuration information. Among them, base station 10 can configure SR configuration information (schedulingRequestConfig) for UE 20, and the SR configuration information can specifically include: SR identification ID (schedulingRequestID), prohibition timer for SR sending (SR-ProhibitTimer), maximum number of SR retransmissions (SR-TransMax), etc.

[0139] In addition, the base station 10 may also configure SR resource configuration information (SchedulingRequestResourceConfig) for the UE 20. The SR resource configuration information may specifically include: SR ID (schedulingRequestID), SR resource ID (schedulingRequestResourceId), SR period and offset within the period (periodicityAndOffset), etc.

[0140] For SL DRB (or logical channel), the corresponding SR ID can be indicated so that the UE can request resources from the network device by sending an SR. Therefore, the UE 20 can determine the SR resource ID through the correspondence between the SR ID and the SR resource ID in the SR resource configuration information, thereby determining the SR resource corresponding to the SR resource ID. Furthermore, the UE 20 can send an SR to the base station 10 through the SR resource corresponding to the SR ID according to other configuration information in the SR configuration corresponding to the SR ID, so as to inform the base station 10 that it has data to send to the UE 30.

[0141] It should be understood that a UE may have multiple SR configurations, corresponding to multiple SR IDs, or multiple SR resource configurations, and one or more logical channels of a UE may correspond to a certain SR configuration or a SR resource configuration. When a logical channel has data cache, triggering a BSR and then triggering an SR, the UE 20 may use the SR resources corresponding to the SR configuration of the logical channel and follow other configuration information in the SR configuration to send an SR to the base station 10.

[0142] In one possible scenario, UE 20 (TX UE) can send SR to base station 10. If base station 10 does not allocate available SR resources to UE 20, UE 20 needs to trigger a random access process to request SR resources when there is no available UL. The method of requesting uplink resources to send BSR to the base station based on contention-based random access will increase signaling overhead and power consumption, and increase latency.

[0143] In addition, in the existing process of configuring SL SRB for UE 20 by base station 10, SR resources and SR resource configuration information are not included, that is, UE 20 cannot determine on which uplink resource to send SR to base station 10, that is, it cannot further request SL grant by sending BSR to base station 10.

[0144] Figure 3 3 is a schematic interactive diagram of a method 300 for determining resources provided in an embodiment of the present application. Each step of the method 300 is described in detail below. It should be understood that the method 300 can be applied to a communication system including a transmitting end user equipment UE 20 (TX UE), at least one receiving end user equipment (RX UE) and a network device (such as a base station 10), for example Figure 1 In the communication system 100 shown, UE 20 may be used as a transmitting user equipment, and UE 30 and UE 40 may be used as receiving user equipment.

[0145] It should also be understood that in the embodiment of the present application, the method 300 is described with the UE 20 and the base station 10 (for example, the primary base station and the secondary base station) as the execution subjects of the method 300. As an example but not a limitation, the execution subject of the method 300 may also be a chip applied to the UE and a chip applied to the base station.

[0146] It should also be understood that the method for determining resources provided in the embodiments of the present application is not limited to any one network connection architecture, for example, Figure 1 Any possible network connection form listed in the present application is not limited to this.

[0147] Optionally, when UE 20 has no available uplink resources (uplink) and UE 20 has cached messages to be transmitted to other UEs (such as UE 30 or UE 40), a SR resource can be determined for UE 20 through the method for determining resources in an embodiment of the present application, for sending SR to the base station 10, so that the base station 10 can configure uplink resources for UE 20 for sending BSR, and then allocate side link (SL) resources to UE 20 and UE 30.

[0148] It should be understood that the "message to be transmitted" mentioned in the embodiment of the present application may be one or more of the PC5-RRC messages and PC5-S messages listed above, or in other words, the "message to be transmitted" mentioned in the embodiment of the present application may be a message carried on the SL SRB.

[0149] The method 300 for determining resources in the embodiment of the present application may include the following steps:

[0150] S310, configuring preset SR configuration information for the base station 10 and the UE 20, where the SR configuration information corresponds to a signaling radio bearer SL SRB of a side link;

[0151] S320, the base station 10 determines the current SR configuration information;

[0152] S330, the base station 10 sends the current SR configuration information to the UE 20;

[0153] S340, UE 20 determines that the current SR configuration information includes preset SR configuration information;

[0154] S350, UE 20 sends an SR to base station 10 on the first SR resource determined by the preset SR configuration information.

[0155] It should be understood that when the sidelink data radio bearer SL DRB has data cached, UE 20 can also send SR to base station 10 to further trigger BSR. Different from determining SR resources for SL DRB in the prior art, in the embodiment of the present application, the SR configuration information is associated with the sidelink signaling radio bearer SL SRB, in other words, SR resources are requested for the message to be transmitted carried on the SL SRB.

[0156] It should also be understood that the SR configuration information corresponds to the SL SRB, which may be one SL SRB corresponding to one SR configuration information, or one SL SRB corresponding to multiple SR configuration information, or one SR configuration information corresponding to multiple SL SRBs. The embodiment of the present application is not limited to this.

[0157] In a possible implementation, the preset SR configuration information can be understood as specifying the SR configuration information in the protocol, and the base station 10 and the UE 20 can reach a consensus and both know which preset SR configuration information the preset SR configuration information includes. It should be understood that one or more preset SR configuration information is specified in the protocol, and the embodiment of the present application does not limit the number of the preset SR configuration information.

[0158] Optionally, the preset SR configuration information may be included in a dedicated configuration instruction for SCCH of the base station 10. The base station 10 configures the preset SR configuration information to the UE 20 when configuring the SCCH. Then, the first SR resource may be understood as the SR resource determined by the preset SR configuration information.

[0159] Exemplarily, in the dedicated configuration instruction of SCCH, a parameter may be added to indicate the SR configuration information, such as schedulingRequest ID=X, where X may be taken from any one of the set {X, Y, Z, M, N…}. Alternatively, the parameter may indicate multiple ones of the set {X, Y, Z, M, N…}, such as schedulingRequestID=X,Y,Z.

[0160] Specifically, as described above, the messages to be transmitted in the buffer on the SCCH may include PC5-RRC messages and three different types of PC5-S messages, and different messages may be carried on different SL SRBs. Therefore, for different message types, there may be the following multiple configurations.

[0161] Method 1

[0162] The SL SRB carrying the PC5-RRC message and the SL SRB carrying the PC5-S message multiplex one SR configuration information, that is, they correspond to one SR configuration ID. In other words, the SL SRB corresponding to the PC5-RRC message and the SL SRB corresponding to the three different types of PC5-S messages are configured with the same preset SR configuration information.

[0163] Exemplarily, the dedicated configuration instructions of the SCCH corresponding to the PC5-RRC message shown in Table 1 below may include packet data convergence protocol (PDCP) configuration information, reordering information, PDCP sequence number, radio link control (RLC) layer configuration information, serial number (SN) field length information, reconfiguration information, logical channel identity (logical channel Identity), media access control (MAC) layer configuration information, priority information, priority bit rate and logical channel group information.

[0164] In the embodiment of the present application, a parameter schedulingRequestID may be added, for example, schedulingRequestID=10. After schedulingRequestID=10 is added to the dedicated configuration instruction of the SCCH corresponding to the PC5-RRC message, as shown in Table 1 below. The parameter information may be specified in the protocol, and the UE 20 and the base station 10 may default to schedulingRequestID=10 corresponding to the PC5-RRC message, and then the UE 20 searches for the SR resource ID according to schedulingRequestID=10, and then sends an SR to the base station 10 on the SR resource determined by the SR resource ID. Accordingly, the base station 10 may receive the SR sent by the UE 20 on the SR resource determined by the SR resource ID.

[0165] Table 1

[0166]

[0167] Alternatively, as shown in Table 2 below, the dedicated configuration instructions of the SCCH corresponding to the PC5-S message, especially for unprotected PC5-S messages, such as Direct Communication Request messages, are added with schedulingRequestID=10 on the basis of the dedicated configuration instructions of the SCCH, as shown in Table 2 below. This parameter information can be specified in the protocol, and the UE 20 and the base station 10 can default to schedulingRequestID=10 corresponding to the PC5-S message, and then the UE 20 searches for the SR resource ID according to schedulingRequestID=10, and then sends the SR to the base station 10 on the SR resource determined by the SR resource ID. Accordingly, the base station 10 can receive the SR sent by the UE 20 on the SR resource determined by the SR resource ID.

[0168] Table 2

[0169]

[0170] Alternatively, for PC5-S message establishing PC5-S security after PC5-S security is established, such as Direct Security Mode Command message and Direct Security Mode Complete message, schedulingRequestID=10 is added in the corresponding SCCH dedicated configuration instruction, as shown in Table 3 below. The parameter information may be specified in the protocol, and UE 20 and base station 10 may default to schedulingRequestID=10 corresponding to the PC5-S message, and then UE 20 searches for the SR resource ID according to schedulingRequestID=10, and then sends SR to base station 10 on the SR resource determined by the SR resource ID. Accordingly, base station 10 may receive SR sent by UE 20 on the SR resource determined by the SR resource ID.

[0171] Table 3

[0172]

[0173] Alternatively, for a PC5-S message with security protection, schedulingRequestID=10 is added to the dedicated configuration instruction of the corresponding SCCH, as shown in Table 4 below. The parameter information may be specified in the protocol, and the UE 20 and the base station 10 may default to schedulingRequestID=10 corresponding to the PC5-S message, and then the UE 20 searches for the SR resource ID according to schedulingRequestID=10, and then sends an SR to the base station 10 on the SR resource determined by the SR resource ID. Accordingly, the base station 10 may receive the SR sent by the UE 20 on the SR resource determined by the SR resource ID.

[0174] Table 4

[0175]

[0176] According to the configuration process of the above method 1, four SL SRBs can reuse one SR configuration information, that is, corresponding to one SR configuration ID, so that four SL SRBs share one SR resource.

[0177] Method 2

[0178] The SL SRB carrying the PC5-RRC message and the SL SRB carrying the three types of PC5-S messages can be configured with different SR configuration information, that is, corresponding to different SR resources. In other words, the SCCH corresponding to the PC5-RRC message and the SCCH corresponding to the three different types of PC5-S messages are configured with different SR configuration IDs.

[0179] Exemplarily, the SR configuration information of the SL SRB carrying the PC5-RRC message is schedulingRequestID=X, and the SR configuration information of the SL SRB carrying the PC5-S signaling is schedulingRequestID=Y.

[0180] Specifically, in the preset SR configuration information {X, Y, Z, M, N…}, select any one schedulingRequestID=X, and configure the SR configuration information of the SL SRB carrying the PC5-RRC message to schedulingRequestID=X, or the parameter may indicate multiple ones in the set {X, Y, Z, M, N…}, for example, schedulingRequestID=X, Y; and select any one schedulingRequestID=Y, and configure the SR configuration information of the SL SRB carrying the three PC5-S messages to schedulingRequestID=Y, or the parameter may indicate multiple ones in the set {X, Y, Z, M, N…}, for example, schedulingRequestID=Z, M. Thus, the SL SRB carrying the PC5-RRC message and the SL SRB carrying the three PC5-S messages correspond to different SR resources.

[0181] According to the configuration process of the above method 2, four SL SRBs can be associated with two different SR configuration information, so that transmission messages with different message types correspond to different SR resources.

[0182] Method 3

[0183] The SL SRB carrying the PC5-RRC message and the SL SRB corresponding to the three PC5-S messages can be configured with different SR configuration information, that is, each message to be transmitted corresponds to different SR resources.

[0184] Exemplarily, the SL SRB corresponding to the PC5-RRC message is associated with schedulingRequestID=X, and the SCCH corresponding to the PC5-S message can be associated with schedulingRequestID=Y or Z or M respectively.

[0185] Specifically, among the preset SR configuration information {X, Y, Z, M, N…}, select any one schedulingRequestID=X, and configure the SR configuration information of the SL SRB carrying the PC5-RRC message to schedulingRequestID=X; select any one schedulingRequestID=Y, and configure the SR configuration information of the SL SRB carrying the unprotected PC5-S message to schedulingRequestID=Y; select any one schedulingRequestID=Z, and configure the SR configuration information of the SL SRB carrying the PC5-S message establishing PC5-S security to schedulingRequestID=Z; select any one schedulingRequestID=M, and configure the SR configuration information of the SL SRB carrying the protected PC5-S message to schedulingRequestID=M. Similar to the first or second method, each preset SR configuration information corresponding to the message to be transmitted may indicate multiple ones of the set {X, Y, Z, M, N…}.

[0186] According to the configuration process of the third method above, four SL SRBs may be associated with four different SR configuration information, so that each message to be transmitted corresponds to a different SR resource.

[0187] It should be understood that in the three methods of configuring SR resources introduced above, the SR configuration information of the four SL SRBs is predefined in the standard, that is, the base station 10 does not need to configure the parameters of the SL SRB for the UE 20 through system information or dedicated RRC signaling.

[0188] It should be understood that in the above-described method 300 for determining resources, S320-S340 are optional steps. For example, the method 300 may include the processes of S310 and S350, or the method 300 may include the processes of S310, S320, S330, S340 and S350.

[0189] Optionally, in the method 300 , SR configuration information is preset in the standard, and the UE 30 may directly send an SR to the base station 10 through the first SR resource determined by the preset SR configuration information.

[0190] Alternatively, after the SR configuration information is preset in the standard in method 300, the base station 10 may also send the current SR configuration information to the UE 20, and the UE 20 determines whether the current SR configuration information includes the preset SR configuration information, or the UE 20 determines whether the current SR configuration information is the preset SR configuration information. When the current SR configuration information includes the preset SR configuration information, or when the current SR configuration information is the preset SR configuration information, the UE 30 may directly send the SR to the base station 10 through the first SR resource determined by the preset SR configuration information. That is, all the processes of S310, S320, S330, S340 and S350 of method 300 are executed. In this process, if the base station 10 determines that a dedicated SR resource can be configured for the SL SRB of the UE 20 at present, then in SchedulingRequestConfig, the corresponding SR configuration ID (e.g., SchedulingRequestID=10) is configured, and the UE 20 may send the SR through the SR resource configured by the base station 10.

[0191] Alternatively, when UE 20 determines that the current SR configuration information does not include the preset SR configuration information, or when UE 20 determines that the current SR configuration information is not the preset SR configuration information, UE 20 initiates a random access process to base station 10. In this process, if base station 10 determines that dedicated SR resources are not currently configured for SL SRB of UE 20, then in SchedulingRequestConfig, the current SR configuration information is configured as any SR configuration information other than the preset SR configuration information, for example, SchedulingRequestID=1. UE 20 determines that the SR configuration information is not the preset SR configuration information in the standard according to SchedulingRequestID=1, and SR cannot be sent through the SR resource corresponding to SchedulingRequestID=10. UE 20 can send a random access request to base station 10 to obtain uplink resources.

[0192] Optionally, the SR configuration information (schedulingRequestConfig) may include at least one of: an SR identification ID (schedulingRequestID), a prohibition timer (SR-ProhibitTimer) for SR transmission, a maximum number of SR retransmissions (SR-TransMax), and the like.

[0193] In addition to the SR configuration information (schedulingRequestConfig), the base station 10 may also configure SR resource configuration information (SchedulingRequestResourceConfig) for the UE 20. The SR resource configuration information may include: SR ID (schedulingRequestID), SR resource ID (schedulingRequestResourceID), SR period and offset within the period (periodicityAndOffset), etc.

[0194] Therefore, after UE 20 receives the SR configuration information sent by the base station 10, it can determine the SR ID, which can correspond to the SR resource ID, and then determine an SR resource based on the SR resource ID, such as the "first SR resource" referred to in the embodiment of the present application, that is, the first SR resource is the uplink resource that UE 20 ultimately sends SR to the base station 10.

[0195] Different from the above-mentioned way in which the preset SR configuration information is included in the dedicated configuration instruction of the base station 10 for SCCH, optionally, it can also be stipulated that one or more sidelink radio bearer configuration identifiers (SLRB-Uu-ConfigIndex) correspond to the signaling radio bearer SL SRB of the sidelink, or, one or more sidelink radio bearer configurations correspond to the signaling radio bearer SL SRB of the sidelink, or, one or more sidelink data radio bearer configuration identifiers correspond to the signaling radio bearer SL SRB of the sidelink, or, one or more sidelink data radio bearer configurations correspond to the signaling radio bearer SLSRB of the sidelink.

[0196] Exemplarily, SLRB-Uu-ConfigIndex=X is specified, where X can be taken from any one of the set {X, Y, Z, M, N…}, or SLRB-Uu-ConfigIndex=X, Y, Z is specified, where X, Y, Z can be taken from any one of the set {X, Y, Z, M, N…}. For example, SLRB-Uu-ConfigIndex=X is specified. In the sidelink bearer configuration signaling (SL-RLC-BearerConfig), if SLRB-Uu-ConfigIndex=X is configured, it means that the configured sidelink bearer configuration corresponds to SL SRB. Among them, the sidelink bearer configuration signaling includes SR configuration information, for example, the sidelink bearer configuration signaling includes the sidelink logical channel configuration (sl-MAC-LogicalChannelConfig / SL-LogicalChannelConfig) configuration, and the sidelink logical channel configuration includes the SR ID. Therefore, UE 20 can determine the SR configuration corresponding to the SL SRB, that is, the SR resource, through the specified SLRB-Uu-ConfigIndex=X, the SLRB-Uu-ConfigIndex=X included in the sidelink bearer configuration signaling, and the SR configuration information included in the sidelink bearer configuration signaling. Specifically, there are multiple configuration methods for the sidelink radio bearer configuration identifier and the SL SRB, and there are multiple configuration methods for different message types, as described in the above-mentioned method one, method two, and method three, which will not be repeated here.

[0197] Optionally, in the method 300 , SR configuration information is preset in the standard, and the UE 30 may directly send an SR to the base station 10 through the first SR resource determined by the preset SR configuration information.

[0198] Alternatively, after the SR configuration information is preset in the standard in method 300, the base station 10 may also send the current SR configuration information to the UE 20, and the UE 20 determines whether the current SR configuration information includes the preset SR configuration information, or the UE 20 determines whether the current SR configuration information is the preset SR configuration information. When the current SR configuration information includes the preset SR configuration information, or when the current SR configuration information is the preset SR configuration information, the UE 30 may directly send the SR to the base station 10 through the first SR resource determined by the preset SR configuration information. That is, all the processes of S310, S320, S330, S340 and S350 of method 300 are executed. In this process, if the base station 10 determines that a dedicated SR resource can be configured for the SL SRB of the UE 20 at present, then in the SL-RLC-BearerConfig, the corresponding SR configuration ID (for example, SLRB-Uu-ConfigIndex=10) is configured, and the UE 20 may send the SR through the SR resource configured by the base station 10.

[0199] Alternatively, when UE 20 determines that the current SR configuration information does not include the preset SR configuration information, or when UE 20 determines that the current SR configuration information is not the preset SR configuration information, UE 20 initiates a random access process to base station 10. In this process, if base station 10 determines that dedicated SR resources are not currently configured for SL SRB of UE 20, then in SL-RLC-BearerConfig, the current SR configuration information is configured as any SR configuration information other than the preset SR configuration information, for example, SLRB-Uu-ConfigIndex=1. UE 20 determines that the SR configuration information is not the preset SR configuration information in the standard according to SLRB-Uu-ConfigIndex=1, and SR cannot be sent through the SR resource corresponding to SLRB-Uu-ConfigIndex=10. UE 20 can send a random access request to base station 10 to obtain uplink resources.

[0200] Optionally, the SR configuration information (schedulingRequestConfig) may include at least one of: an SR identification ID (schedulingRequestID), a prohibition timer (SR-ProhibitTimer) for SR transmission, a maximum number of SR retransmissions (SR-TransMax), and the like.

[0201] In addition to the SR configuration information (schedulingRequestConfig), the base station 10 may also configure SR resource configuration information (SchedulingRequestResourceConfig) for the UE 20. The SR resource configuration information may include: SR ID (schedulingRequestID), SR resource ID (schedulingRequestResourceID), SR period and offset within the period (periodicityAndOffset), etc.

[0202] It should be noted that the current SR configuration information sent by the base station 10 to the UE 20 does not include the configuration information in the preset SR configuration information; or, the current SR configuration information sent by the base station 10 to the UE 20 may include the configuration information in the preset SR configuration information. If included, the current SR configuration information sent by the base station 10 may be subject to the configuration information, or the configuration information in the preset SR configuration information may be subject to the configuration information.

[0203] Therefore, after UE 20 receives the SR configuration information sent by the base station 10, it can determine the SR ID, which can correspond to the SR resource ID, and then determine an SR resource based on the SR resource ID, such as the "first SR resource" referred to in the embodiment of the present application, that is, the first SR resource is the uplink resource that UE 20 ultimately sends SR to the base station 10.

[0204] The above technical solution presets SR configuration information for the base station and UE in the standard. In the specific implementation process, the base station can flexibly decide whether to configure dedicated SR resources for the SL SRB of the UE. When it is determined that dedicated SR resources can be configured for the SL SRB of the UE, the base station carries the preset SR configuration information when configuring SR resources for the UE. The UE can send SR to the base station through the preset SR resources to request uplink resources or SL resources, thereby reducing signaling overhead, reducing UE power consumption, and reducing the delay in obtaining uplink resources.

[0205] In another possible implementation, the protocol does not specify preset SR configuration information for the base station 10 and the UE 20, and the base station 10 may configure the SR configuration information for the UE 20 according to different methods.

[0206] Figure 4 4 is a schematic interactive diagram of another example of a method 400 for determining resources provided in an embodiment of the present application. Each step of the method 400 is described in detail below.

[0207] It should be understood that the method 400 can be applied to a communication system including a transmitting end user equipment UE 20 (TX UE), at least one receiving end user equipment (RX UE) and a network device (such as a base station 10), for example Figure 1 In the communication system 100 shown, UE 20 may be used as a transmitting user equipment, and UE 30 and UE 40 may be used as receiving user equipment.

[0208] It should also be understood that in the embodiment of the present application, the method 400 is described with the UE 20 and the base station 10 (e.g., the primary base station and the secondary base station) as the execution subjects of the method 400. As an example but not a limitation, the execution subject of the method 400 may also be a chip applied to the UE and a chip applied to the base station.

[0209] It should also be understood that the method for determining resources provided in the embodiments of the present application is not limited to any one network connection architecture, for example, Figure 1 Any possible network connection form listed in the present application is not limited to this.

[0210] Optionally, when UE 20 has no available uplink resources (uplink) and UE 20 has cached messages to be transmitted to other UEs (such as UE 30 or UE 40), a SR resource can be determined for UE 20 through the method for determining resources in an embodiment of the present application, for sending SR to the base station 10, so that the base station 10 can configure uplink resources for UE 20 for sending BSR, and then allocate side link (SL) resources to UE 20 and UE 30.

[0211] It should be understood that the "message to be transmitted" mentioned in the embodiment of the present application may be one or more of the PC5-RRC messages and PC5-S messages listed above, or in other words, the "message to be transmitted" mentioned in the embodiment of the present application may be a message carried on the SL SRB.

[0212] The method 400 for determining resources in the embodiment of the present application may include the following steps:

[0213] S410, the base station 10 determines scheduling request SR configuration information, where the SR configuration information corresponds to a signaling radio bearer SL SRB of a side link.

[0214] S420 , the base station 10 sends the SR configuration information to the UE 20 , and correspondingly, the UE 20 receives the SR configuration information sent by the base station 10 .

[0215] S430: UE 20 determines the corresponding first SR resource according to the SR configuration information.

[0216] S440, UE 20 sends an SR to base station 10 through the first SR resource. Correspondingly, base station 10 receives the SR sent by UE 20 through the first SR resource.

[0217] Optionally, in method 400, the SR configuration information is configured by base station 10 for UE 20, and can be used for scheduling data between base station 10 and UE 20, and can also be used for scheduling data between UE 20 and other UEs (UE 30 or UE 40).

[0218] In one possible implementation, during the process of determining the SR configuration information, the base station 10 can determine the same SR configuration information for each message to be transmitted; or can determine the same SR configuration information for the same type of messages to be transmitted, and determine different SR configuration information for different types of messages to be transmitted; or can determine different SR configuration information for each message to be transmitted; or can determine the same SR configuration information for at least two messages to be transmitted.

[0219] Exemplarily, the base station 10 may determine the SR configuration information for the UE 20 in the following manner.

[0220] Method 4

[0221] The base station 10 can determine the same SR configuration information for each message to be transmitted. In other words, all SL SRBs corresponding to each message to be transmitted share one SR configuration information, that is, the SL SRB carrying the PC5-RRC message and the SL SRB carrying the three PC5-S messages are configured with the same SR configuration ID.

[0222] For example, the SR configuration information schedulingRequestID=X corresponding to the SL SRB carrying the PC5-RRC message and the SL SRB carrying the PC5-S message.

[0223] Method 5

[0224] The base station 10 can determine the same SR configuration information for the same type of messages to be transmitted, and determine different SR configuration information for different types of messages to be transmitted. In other words, all SL SRBs corresponding to each message to be transmitted of the same type share one SR configuration information, and all SL SRBs corresponding to different types of messages to be transmitted correspond to different SR configuration information.

[0225] For example, the SR configuration information schedulingRequestID=X corresponding to the SL SRB carrying the PC5-RRC message, and the SR configuration information schedulingRequestID=Y corresponding to the SL SRB carrying the PC5-S message.

[0226] Method 6

[0227] The base station 10 may determine different SR configuration information for each message to be transmitted.

[0228] For example, the SR configuration information schedulingRequestID=X corresponding to the SL SRB carrying the PC5-RRC message, and the SR configuration information schedulingRequestID=Y, schedulingRequestID=Z or schedulingRequestID=W corresponding to the SL SRB carrying the three types of PC5-S messages.

[0229] Method 7

[0230] The base station 10 may correspond the same SR configuration information to at least two of the messages to be transmitted.

[0231] For example, the SR configuration information schedulingRequestID=X corresponding to the SL SRB carrying the PC5-RRC message, the SR configuration information schedulingRequestID=Y corresponding to the SL SRB carrying two types of PC5-S messages, and the SR configuration information schedulingRequestID=Z corresponding to the SL SRB carrying one type of PC5-S message.

[0232] In another possible implementation, in the process of determining the SR configuration information, the base station 10 may consider not only the message type of the message to be transmitted cached by the UE 20, but also different RXUEs that are connected to the UE 20 via a side link, so as to more flexibly determine the SR configuration information for the UE 20.

[0233] For example, Figure 1 As shown, for UE 20, UE 30 and UE 40 may communicate with it, and both UE 30 and UE 40 may serve as RX UE. Then, the signaling to be sent by UE 20 may include different signalings with destination addresses being UE 30 and UE 40.

[0234] Specifically, when the RX UE includes different target UEs, the first SR resource for sending the SR may be determined for the UE 20 in the following manner: The RX UE may be referred to as a "target UE" or a "target UE".

[0235] Method 8

[0236] The base station 10 determines all target UEs of UE 20, and determines to share a common SR configuration information for all SL SRBs of all target UEs. In other words, the same SR configuration information is determined for all SL SRBs of all target UEs cached by UE 20, such as the SL SRB carrying the PC5-RRC message and the SL SRB carrying the PC5-S message.

[0237] Exemplarily, the base station 10 determines that all SL SRBs of the UE 30 and the UE 40 have the same SR configuration information.

[0238] It should be understood that after the base station 10 establishes a connection with UE 20, UE 30 and UE 40, the unique identity of UE 20, UE 30 and UE 40 can be obtained, and then when allocating SR resources to UE 20, according to the identity of UE 30 and UE 40, it is determined that the SL SRB between UE 20 and UE 30, and the SL SRB between UE 20 and UE 40 have the same SR configuration information schedulingRequestID=X.

[0239] It should also be understood that method eight does not take into account the identity of the target UE and makes all SL SRBs of all target UEs have the same SR configuration information.

[0240] Method Nine

[0241] The base station 10 determines all target UEs of the UE 20, and determines different SR configuration information in combination with the types of messages to be transmitted by all target UEs.

[0242] Exemplarily, all the messages to be transmitted of the target UE are divided into two types: PC5-RRC messages and PC5-S messages. Determine the SR configuration information schedulingRequestID=X of all SL SRBs carrying PC5-RRC messages; determine the SR configuration information schedulingRequestID=Y source of the SL SRBs carrying PC5-S messages.

[0243] It should be understood that method nine does not consider the identity of the target UE, but only considers the message type of the message to be transmitted carried on the SL SRB, determines the same SR configuration information for the SL SRB carrying PC5-RRC messages of all target UEs, and determines another SR configuration information for the SL SRB carrying PC5-S messages of all target UEs.

[0244] Method 10

[0245] The base station 10 determines all target UEs of the UE 20, and determines different SR configuration information for different target UEs according to the identity identifier (ID) of the target UE. Under each target UE, all SL SRBs are configured to have the same SR configuration information.

[0246] Exemplarily, configure the SR configuration information schedulingRequestID=X of the SL SRB carrying PC5-RRC message and the SL SRB carrying PC5-S message under UE 30; configure the SR configuration information schedulingRequestID=Y source of the SL SRB carrying PC5-RRC message and the SL SRB carrying PC5-S message under UE 40.

[0247] It should be understood that method 10 only considers the identity of the target UE, and all messages to be transmitted under each target UE have the same SR configuration information.

[0248] Method 11

[0249] The base station 10 determines all target UEs of the UE 20, and associates different SR configuration information with different target UEs and different message types in combination with the message type carried on the SL SRB and the identity of the target UE.

[0250] Exemplarily, the SR configuration information schedulingRequestID=X of the SL SRB that carries the PC5-RRC message under UE 30 is configured, the SR configuration information schedulingRequestID=Y of the SL SRB that carries the PC5-S message under UE 30 is configured, the SR configuration information schedulingRequestID=M of the SL SRB that carries the PC5-RRC message under UE 40 is configured, and the SR configuration information schedulingRequestID=N of the SL SRB that carries the PC5-S message under UE 40 is configured.

[0251] It should be understood that method eleven takes into account the identity of the target UE and the message type carried on the SL SRB, determines different SR configuration information for different target UEs, and under each target UE, the SL SRB carrying the PC5-RRC message and the SL SRB carrying the PC5-RRC message can be associated with different SR configuration information.

[0252] Method 12

[0253] On the basis of method 11, method 12 combines the message type carried on the SL SRB and the identity of the target UE to determine different SR configuration information for different target UEs and different message types.

[0254] Exemplarily, the SR configuration information schedulingRequestID=X of the SL SRB carrying the PC5-RRC message under UE 30 is configured, the SR configuration information of the SL SRB carrying three PC5-S messages under UE 30 is configured as schedulingRequestID=Y, M, N respectively, the SR configuration information of the SL SRB carrying the PC5-RRC message under UE 40 is configured as schedulingRequestID=W, and the SR configuration information of the SL SRB carrying three PC5-S messages under UE 40 is configured as schedulingRequestID=Z, L, H respectively.

[0255] It should be understood that method twelve takes into account both the identity of the target UE and the message type carried on the SL SRB, configures different SR configuration information for different target UEs, and under each target UE, the SL SRB carrying the PC5-RRC message and the SL SRB carrying the PC5-RRC message have different SR configuration information respectively.

[0256] Exemplarily, in the implementation process of the fourth to the twelve methods introduced above, SR configuration information can be added in SL-ConfigDedicatedNR or SL-ScheduledConfig or MAC-MainConfigSL to indicate SR configuration information specifically for SL SRB.

[0257] To summarize, the base station configures different SR configuration information for different target UEs. Under each target UE, the SL SRB carrying the PC5-RRC message and the SL SRB carrying the three types of PC5-S messages may have different SR configuration information.

[0258] If the base station 10 determines that dedicated SR configuration information can be configured for the SL SRB of the UE 20, the SR configuration information specifically for the SLSRB is configured in SL-ConfigDedicatedNR or SL-ScheduledConfig or MAC-MainConfigSL, and the UE 20 can send an SR by determining the SR resources corresponding to the SR configuration information.

[0259] If the base station 10 does not currently configure dedicated SR configuration information for the SL SRB of UE 20, then the SR configuration information specifically for the SL SRB is not configured in SL-ConfigDedicatedNR or SL-ScheduledConfig or MAC-MainConfigSL, which means that after the SL SRB of UE 20 triggers SR, it is necessary to obtain uplink resources by initiating a random access process.

[0260] Through the above technical solution, the base station configures SR configuration information for the UE, and the UE can determine the first SR resource through the SR configuration information, and send SR to the base station through the first SR resource to request uplink resources or SL resources, thereby reducing signaling overhead, reducing UE power consumption and reducing the delay in obtaining uplink resources.

[0261] In another possible implementation, in S310, in the process of determining the SR configuration information, the base station 10 may configure dedicated SR resources for the SL SRB between the UE 20 and the target UE, or configure dedicated SR resources for different target UEs of the UE 20, and may also configure dedicated SR resources for the SL SRB by associating with existing SR configuration information. In other words, when the base station 10 determines the SR configuration information for the UE 20, the SR configuration information is associated with the SR configuration information that has been configured during the communication between the base station 10 and / or the UE 20.

[0262] For example, Figure 1 As shown, for the communication link that has been established between UE 20 and base station 10, the communication link can be UL, including a data radio bearer (DRB) for transmitting data and a signaling radio bearer (SRB) for transmitting signaling, and the DRB and SRB respectively correspond to SR configuration information.

[0263] Exemplarily, the base station 10 may determine the SR configuration information for the UE 20 in the following manner.

[0264] Method Thirteen

[0265] The standard defines that the SR configuration information of the SL SRB reuses the SR configuration information of an SRB between the base station 10 and the UE 20. For example, the SR configuration information of SRB1 between the base station 10 and the UE 20 is reused, or the SR configuration information of SRB2 between the base station 10 and the UE 20 is reused. Then, after the data of the SL SRB reaches the triggering SR, the UE 20 can send the SR through the SR resource corresponding to any one of the configuration information in SRB1 or SRB2.

[0266] It should be understood that if the SR configuration information schedulingRequestID=X of the SRB of the Uu interface between the base station 10 and the UE 20, then after the data of the SL SRB of the UE 20 reaches the triggering SR, the SR can be sent through the SR resources corresponding to the SR configuration information schedulingRequestID=X. If the base station 10 does not configure the SR configuration information for the SRB of the Uu interface, then after the data of the SL SRB of the UE 20 reaches the triggering SR, the UE 20 triggers a random access process to obtain uplink resources.

[0267] Method 14

[0268] The standard defines that the SR configuration information of SL SRB reuses the SR configuration information of at least two SRBs (e.g., SRB1 and SRB2) between the base station 10 and the UE 20. Then, after the data of the SL SRB reaches the triggering SR, the UE 20 can send the SR through the SR resource corresponding to any one of the configuration information of SRB1 and SRB2.

[0269] Method 15

[0270] The base station 10 determines that the SR configuration information of the SL SRB multiplexes the SR configuration information of any DRB between the base station 10 and the UE 20 .

[0271] If the SR configuration information schedulingRequestID=Y of any DRB of the Uu interface between the base station 10 and the UE 20, then after the data of the SL SRB of the UE 20 reaches the triggering SR, the SR can be sent through the SR resources corresponding to the SR configuration information schedulingRequestID=Y of any DRB.

[0272] Method 16

[0273] The base station 10 determines that the SR configuration information of the SL SRB multiplexes the SR configuration information of any DRB between UE 20 and UE 30 (or UE 40 ), that is, the base station 10 determines that the SR configuration information of the SL SRB multiplexes the SR configuration information of any SL DRB of UE 20 .

[0274] If the SR configuration information schedulingRequestID=Y of any DRB of the PC5 interface between UE 20 and UE 30 (or UE 40), then after the data of the SL SRB of UE 20 reaches the triggering SR, the SR can be sent through the SR resources corresponding to the SR configuration information schedulingRequestID=Y of any DRB.

[0275] Method 17

[0276] The SR configuration information of the SL SRB is defined in the standard to multiplex the channel state information (CSI) report of the sidelink SL and report the same SR configuration information. The SL CSI report can be transmitted via a media access control (MAC) control element (CE).

[0277] If the base station 10 configures SR configuration information for the SL CSI report, then after the UE 20 has data of the SL SRB reaching the triggering SR, it can send the SR through the SR resources corresponding to the SR configuration information.

[0278] If the base station 10 does not configure SR configuration information for the SL CSI report, then after the data of the SL SRB of the UE 20 reaches the triggering SR, the UE 20 triggers a random access process to acquire uplink resources.

[0279] It should be noted that any one or more of the methods 13 to 17 can also be combined. For example, the combination of method 15 and method 16 indicates that the base station 10 determines the SR configuration information of the SL SRB, reuses the SR configuration information of any one of the DRBs between the base station 10 and the UE 20, and the DRB of the side link of the UE 20.

[0280] Through the above technical solution, when the base station configures SR resources for the UE, the determined SR configuration information is associated with the existing SR configuration information. The UE can determine the first SR resource through the SR configuration information, and send SR to the base station through the first SR resource to request uplink resources or SL resources, thereby reducing signaling overhead, reducing UE power consumption and reducing the delay in obtaining uplink resources.

[0281] In another possible implementation, the SR configuration information also includes indication information, where the indication information is used to indicate whether the first SR resource is an SR resource for requesting a sidelink, or the indication information is used to indicate whether the configured SR configuration information can be used for an SL SRB in an associated sidelink.

[0282] Optionally, when determining the SR configuration information, the base station 10 may add an indication field in the SR configuration information to indicate whether the configured SR configuration information between the base station 10 and / or the UE 20 can be used to determine the SR configuration information of the SL SRB in the current sidelink. Exemplarily, a field is added to the SR configuration information to indicate whether the SR configuration information can be used for the SL SRB.

[0283] Alternatively, two fields are added to the SR configuration information, one of which is used to indicate whether the SR configuration information can be used for the SR configuration information of the SL SRB carrying PC5-RRC, and the other is used to indicate whether the SR configuration information can be used for the SR configuration information of the SL SRB carrying PC5-S.

[0284] Alternatively, four fields may be added to the SR configuration information, one of which is used to indicate whether the SR configuration information can be used for the SR configuration information of the SL SRB carrying PC5-RRC, and the other three fields are used to indicate whether the SR configuration information can be used for the SR configuration information of three types of SL SRBs carrying PC5-S.

[0285] It should be understood that if the base station 10 determines dedicated SR configuration information for the SL SRB of the UE 20, the indication information is carried in the SchedulingRequestToAddMod (Uu parameter). Otherwise, if the base station 10 does not determine dedicated SR configuration information for the SL SRB of the UE 20, the indication information is not carried in the SchedulingRequestToAddMod (Uu parameter).

[0286] Correspondingly, UE 20 can determine whether to send an SR or trigger a random access process to acquire uplink resources according to whether SchedulingRequestToAddMod includes the indication information.

[0287] Through the above technical solution, by adding indication information to the SR configuration information determined by the base station, the UE can determine whether the first resource can be used as an SR resource for requesting a sidelink according to the indication information. When it can be used as an SR resource for requesting a sidelink, the UE can determine the first SR resource through the SR configuration information, and send an SR to the base station through the first SR resource to request an uplink resource or SL resource, thereby reducing signaling overhead, reducing UE power consumption, and reducing the delay in obtaining uplink resources. When it cannot be used as an SR resource for requesting a sidelink, the UE can trigger a random access process to obtain uplink resources.

[0288] Several possible embodiments are listed below.

[0289] Embodiment 1:

[0290] The Sidelink Control Channel (SCCH) is used to transmit PC5-RRC messages and PC5-S messages. In the dedicated configuration of SCCH, a parameter is added to indicate the SR configuration ID, such as schedulingRequestID=X. The ID indicating the SR configuration may be one or more, such as schedulingRequestID=X,Y,Z….

[0291] The specific configuration granularity includes:

[0292] (1) All SL SRBs share one SR configuration ID, that is, the SCCH corresponding to the PC5-RRC message and the SCCH corresponding to the three PC5-S messages are configured with the same SR configuration ID;

[0293] (2) The SCCH corresponding to the PC5-RRC message and the SCCH corresponding to the PC5-S signaling can be configured with different SR configuration IDs, for example: the SCCH associated with the PC5-RRC message is schedulingRequestID=X, and the SCCH associated with the PC5-S message is schedulingRequestID=Y;

[0294] (3) The SCCH corresponding to the PC5-RRC message and the SCCH corresponding to the three types of PC5-S signaling can be configured with different SR configuration IDs. For example, the SCCH corresponding to the PC5-RRC message is associated with schedulingRequestID=X, and the SCCH corresponding to the PC5-S message can be associated with schedulingRequestID=Y or Z or W respectively.

[0295] If the base station is willing to configure a dedicated SR for the UE's SL SRB, the corresponding SR configuration ID (SchedulingRequestId) is configured in SchedulingRequestConfig (Uu parameter); if the base station is unwilling to configure a dedicated SR for the UE's SL SRB, the corresponding SR configuration ID (SchedulingRequestId) is not configured in SchedulingRequestConfig (Uu parameter).

[0296] Accordingly, the UE may determine whether to send an SR or trigger a random access procedure to acquire uplink resources according to whether SchedulingRequestConfig includes the configuration of SchedulingRequestId=X.

[0297] Embodiment 2:

[0298] In SL-ConfigDedicatedNR or SL-ScheduledConfig, the SR configuration ID specifically for SL SRB is included.

[0299] The specific configuration granularity includes:

[0300] (1) All SL SRBs under all target UEs (RX UEs for the TX UE) share one SR configuration ID, that is, the SCCH corresponding to the PC5-RRC message under all target UEs and the SCCH corresponding to the three types of PC5-S messages are associated with the same SR configuration ID.

[0301] (2) The SCCH corresponding to the PC5-RRC message under all target UEs and the SCCH corresponding to the PC5-S signaling under all target UEs can be configured with different SR configuration IDs, for example: the SCCH associated schedulingRequestID corresponding to the PC5-RRC message under all target UEs is schedulingRequestID=X, and the SCCH associated schedulingRequestID corresponding to the PC5-S message under all target UEs is schedulingRequestID=Y.

[0302] (3) Different SR configuration IDs are configured for different target UEs. Under each target UE, all SL SRBs share one SR configuration ID. For example, the SCCH corresponding to the PC5-RRC message under each target UE and the SCCH corresponding to the three types of PC5-S messages can be associated with one SR configuration ID.

[0303] (4) Different SR configuration IDs are configured for different target UEs. Under each target UE, the SCCH corresponding to the PC5-RRC message and the SCCH corresponding to the PC5-S signaling can be configured with different SR configuration IDs.

[0304] (5) Different SR configuration IDs are configured for different target UEs. Under each target UE, the SCCH corresponding to the PC5-RRC message and the SCCH corresponding to the three types of PC5-S signaling can be configured with different SR configuration IDs.

[0305] If the base station is willing to configure a dedicated SR for the UE's SL SRB, the SR configuration ID specifically for the SL SRB is included in the SL-ConfigDedicatedNR or SL-ScheduledConfig; if the base station is unwilling to configure a dedicated SR for the UE's SL SRB, the SR configuration ID specifically for the SL SRB is not included in the SL-ConfigDedicatedNR or SL-ScheduledConfig, which means that after the SL SRB triggers the SR, it is necessary to obtain uplink resources through a random access process.

[0306] Embodiment three:

[0307] The standard defines: SL SRB uses the same SR configuration ID as Uu SRB1.

[0308] If the base station configures an SR configuration ID for Uu's SRB1, then after the UE's SL SRB data reaches the trigger SR, it can send an SR through the SR resources corresponding to the SR configuration ID; if the base station does not configure an SR configuration ID for Uu's SRB1, then after the UE's SL SRB data reaches the trigger SR, the UE triggers a random access process to obtain uplink resources.

[0309] As an optional extension scheme, SL SRB adopts the same SR configuration ID as Uu SRB1 or SRB2. If the base station configures the SR configuration ID for Uu's SRB1 or SRB2, then after the UE triggers SR due to the data of SL SRB, it can send SR through the SR resources corresponding to any SR configuration ID in SRB1 and SRB2.

[0310] As another optional extension scheme, SL SRB adopts the same SR configuration ID as Uu SRB1 or SRB2 or DRB. If the base station configures the SR configuration ID for Uu's SRB1 or SRB2 or DRB, then after the UE triggers SR due to the data of SL SRB, it can send SR through the SR resources corresponding to any SR configuration ID in SRB1, SRB2 and DRB.

[0311] Alternatively, the standard defines that: SL SRB uses the same SR configuration ID as the SL Channel State Information (CSI) report. The SL CSI report is transmitted via the Media Access Control (MACCE) Control Element (CE).

[0312] If the base station configures the SR configuration ID for the SL CSI report, then after the data of the SL SRB reaches the triggering SR, the UE can send the SR through the SR resources corresponding to the SR configuration ID; if the base station does not configure the SR configuration ID for the SL CSI report, then after the data of the SL SRB reaches the triggering SR, the UE triggers the random access process to obtain uplink resources.

[0313] Embodiment 4:

[0314] An indication field is added to indicate whether the SR configuration of the Uu can be used for the SL SRB. For example, a field is added to the SR configuration to indicate whether the SR configuration can be used for the SL SRB.

[0315] As an optional extension scheme, there may be two fields, respectively indicating whether the corresponding SR configuration is available for the SL SRB carrying PC5-RRC and the SL SRB carrying PC5-S.

[0316] As another optional extension scheme, there may be four fields, respectively indicating whether the corresponding SR configuration can be used for the SL SRB carrying PC5-RRC and the three types of SL SRB carrying PC5-S.

[0317] If the base station is willing to configure a dedicated SR configuration for the UE's SL SRB, the indication is carried in SchedulingRequestToAddMod (Uu parameter); otherwise, the indication is not carried.

[0318] Accordingly, the UE may determine whether to send an SR or trigger a random access procedure to acquire uplink resources according to whether SchedulingRequestToAddMod includes the indication.

[0319] Through the above embodiments, the base station can flexibly decide whether to configure dedicated SR resources for the SL SRB of the UE. When the base station configures dedicated SR resources for the SL SRB of the UE, the UE can request uplink resources or SL resources from the base station by sending SR, thereby reducing signaling overhead, reducing UE power consumption and reducing the delay in obtaining uplink resources.

[0320] Combination of the above Figures 1 to 4 The method for determining resources in the embodiment of the present application is described in detail. Figures 5 to 8 The device for determining resources in an embodiment of the present application is described in detail.

[0321] Figure 5A schematic block diagram of an apparatus 600 for determining resources according to an embodiment of the present application is shown. The apparatus 500 may correspond to the transmitting end user equipment UE 20 (RX UE) described in the above method 300 or method 400, or may be a chip or component applied to UE 20. In addition, each module or unit in the apparatus 500 is respectively used to execute each action or processing process performed by UE 20 in the above method 300 or method 400, such as Figure 5 As shown, the communication device 500 may include: a receiving unit 510 , a processing unit 520 and a sending unit 530 .

[0322] The receiving unit 510 is used to receive scheduling request SR configuration information sent by a network device, where the SR configuration information corresponds to a signaling radio bearer SL SRB of a side link, and the SR configuration information is used to indicate a first SR resource.

[0323] The processing unit 520 is configured to determine a corresponding first SR resource according to the SR configuration information.

[0324] The sending unit 530 is configured to send the SR to the network device through the first SR resource.

[0325] Specifically, the receiving unit 510 is used to execute the processes S310, S330 in method 300 and S420 in method 400, the processing unit 520 is used to execute the processes S340 in method 300 and S430 in method 400, and the sending unit 530 is used to execute the processes S350 in method 300 and S440 in method 400. The specific processes of each unit executing the above-mentioned corresponding steps have been described in detail in methods 300 and method 400, and for the sake of brevity, they are not repeated here.

[0326] Figure 6 A schematic block diagram of an apparatus 600 for determining resources according to an embodiment of the present application is shown. The apparatus 600 may correspond to (for example, may be applied to or may be) the base station 10 described in the above method 400, and each module or unit in the apparatus 600 is used to execute each action or processing performed by the base station in the above method 300 or method 400, such as Figure 6 As shown, the communication device 600 may include: a sending unit 610 and a receiving unit 620.

[0327] The sending unit 610 is used to send scheduling request SR configuration information to a sending user equipment, where the SR configuration information corresponds to a signaling radio bearer SL SRB of a side link, and the SR configuration information is used to indicate a first SR resource. The sending user equipment is a device in the side link SL.

[0328] The receiving unit 620 is configured to receive the SR sent by the transmitting user equipment through the first SR resource.

[0329] Optionally, the device 600 includes a processing unit 630, configured to determine a corresponding first SR resource according to preset SR configuration information.

[0330] Specifically, the sending unit 610 is used to execute S310, S330 in method 300 and S420 in method 400, and the receiving unit 620 is used to execute the processes of S350 in method 300 and S440 in method 400. The specific processes of each unit executing the above-mentioned corresponding steps have been described in detail in method 300 and method 400, and will not be repeated here for the sake of brevity.

[0331] Figure 7 700 is a schematic diagram of the structure of the user equipment 700 provided in the embodiment of the present application, for example, the transmitting end user equipment in the embodiment of the present application. Figure 7 As shown, the user equipment 700 includes a processor 710 and a transceiver 720. Optionally, the user equipment 700 also includes a memory 730. The processor 710, the transceiver 720 and the memory 730 communicate with each other through an internal connection path to transmit control and / or data signals, and the memory 730 is used to store a computer program, and the processor 710 is used to call and run the computer program from the memory 730 to control the transceiver 720 to send and receive signals.

[0332] The processor 710 and the memory 730 can be combined into a processing device, and the processor 710 is used to execute the program code stored in the memory 730 to implement the functions of the transmitting end user equipment in the above method embodiment. In specific implementation, the memory 730 can also be integrated into the processor 710, or independent of the processor 710. The transceiver 720 can be implemented in the form of a transceiver circuit.

[0333] The transmitting user equipment may further include an antenna 740 for transmitting the uplink data or uplink control signaling output by the transceiver 720 via a wireless signal, or for receiving the downlink data or downlink control signaling and transmitting it to the transceiver 720 for further processing.

[0334] It should be understood that the device 700 may correspond to the transmitting end user equipment in the method 300 and the method 400 according to the embodiment of the present application, and the device 700 may also be a chip or component applied to the user equipment. In addition, each module in the device 700 implements the corresponding process in the method 300 and the method 400. Specifically, the memory 730 is used to store program code, so that when the processor 710 executes the program code, the processor 710 is controlled to execute the process of S340 in the method 300 and S430 in the method 400, and the transceiver 720 is used to execute the process of S350 in the method 300 and S440 in the method 400. The specific process of each unit executing the above corresponding steps has been described in detail in the method 300 and the method 400, and for the sake of brevity, it is not repeated here.

[0335] Figure 8 800 is a schematic diagram of the structure of the network device 800 provided in the embodiment of the present application. Figure 8 As shown, the network device 800 (e.g., a base station) includes a processor 810 and a transceiver 820. Optionally, the network device 800 also includes a memory 830. The processor 810, the transceiver 820, and the memory 830 communicate with each other through an internal connection path to transmit control and / or data signals. The memory 830 is used to store a computer program, and the processor 810 is used to call and run the computer program from the memory 830 to control the transceiver 820 to send and receive signals.

[0336] The processor 810 and the memory 830 can be combined into a processing device, and the processor 810 is used to execute the program code stored in the memory 830 to implement the functions of the base station in the above method embodiment. In specific implementation, the memory 830 can also be integrated in the processor 810, or independent of the processor 810. The transceiver 820 can be implemented in the form of a transceiver circuit.

[0337] The above network device may further include an antenna 840 for transmitting downlink data or downlink control signaling output by the transceiver 820 via wireless signals, or receiving uplink data or uplink control signaling and transmitting them to the transceiver 820 for further processing.

[0338] It should be understood that the device 800 may correspond to the base station in the method 400 according to the embodiment of the present application, and the device 800 may also be a chip or component applied to the base station. Figure 4The corresponding process in method 400, specifically, the memory 830 is used to store program code, so that when the processor 810 executes the program code, the processor 810 is controlled to execute S320 in method 300 and S410 in method 400, the transceiver 820 is used to execute S310, S330 in method 300 and S420 in method 400, or to execute S350 in method 300 and S440 in method 400. The specific process of each unit executing the above corresponding steps has been described in detail in method 300 and method 400, and will not be repeated here for the sake of brevity.

[0339] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0340] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0341] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic, and the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined. Another point is that the mutual coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units.

[0342] In addition, each functional unit in each embodiment of the present application may be integrated into one physical entity, each unit may correspond to one physical entity separately, or two or more units may be integrated into one physical entity.

[0343] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage media include: various media that can store program codes, such as USB flash drives, mobile hard disks, read-only memories (ROM), random access memories (RAM), magnetic disks or optical disks.

[0344] In this paper, we discussed one issue on the SR configuration for SLSRB.

[0345] For the RRC connected UE,if the UE is configured to use SL Mode 1forresource allocation,the gNB can decide whether to configure dedicated SRconfiguration / resources for the UE.If SR is triggered and the UE hasdedicated SR configuration / resources,the UE use such dedicated configuration / resources to send the scheduling request.Otherwise,the UE needs to trigger the random access procedure.

[0346] For the SL DRB,it can be configured by the gNB via the dedicatedsignalling if the UE is in RRCConnected.In the logical channel configurationof the SL DRB,one parameter is the SR configuration as shownbelow.So via thissignalling,the gNB can configure dedicated SR configuration / resource for theUE per SLDRB if it decides to do so.

[0347]

[0348] Observation 1:for SL DRB,gNB can configure SR configuration / resourceassociate with it via thelogical channel configuration of the SL DRB.

[0349] In addition to SL DRB,four SL SRBs,which are used for transmit PC5-Smessage and PC5-RRC messageare also defined in NR SL.However,the SL SRBrelated configurations,including PDCP,RLC configurationand logical channelconfigurations are specified in 9.1.1 of 38.331[1],which means that nodedicated signallingis defined to reconfigure the SL SRB configurations.So,for the SL SRB,there is no way for the gNB toconfigure dedicated SRconfiguration / resource for the UE with SL Mode 1.In other words,in case theSR istriggered by SL SRB,the UE can only trigger random access procedure inorder to request SL grant.

[0350] Observation 2:There is no signalling supporting to configurededicated SR configuration / resourcewhich is associated with the SL SRB.

[0351] According to the above observations,the current signalling designseems not reasonable.In ourunderstanding,the signalling that could enable thegNB to configure dedicated SR configuration / resource forthe UE’s SL SRBshould be supported in the specification,instead of only relying on therandom access torequest SL grant for SL SRB transmission.

[0352] Proposal 1:The signalling that could enable the gNB to configurededicated SRconfiguration / resource associated with the UE’s SL SRB should bespecified.

[0353] For the signalling design,there could be some options:

[0354] Option 1:Include SR configuration ID(s)which is associated to theSL SRB in the SL-ScheduledConfig.

[0355] -The SR configuration ID could be common for all the destination andfor all the four SLSRBs.Or the SR configuration ID could be per destinationbut common for all the four SL SRBs.

[0356] Option 2:In the specified SCCH configuration,add one new parameter,i.e.,SR configurationID.If the gNB decides to configure the SR configuration / resource for the SCCH,the gNB can add suchSR configuration ID in theSchedulingRequestToAddMod.If there is no such SR configuration ID in theSchedulingRequestToAddMod,the UE needs to trigger random access procedure incase the SR is triggered by SL SRB.

[0357] -This option has no any impact on the ASN.1.

[0358] Option 3:The SL SRB can use any SR configuration ID that isconfigured for the UE.As forwhich SR configuration to use can be up to UEimplementation.With this option,it seems only a Note isneeded in thespecification.However,gNB has no way to decide whether to configure the SLSRB to useSR or random access for requesting SL grant if go for this option.

[0359] From our perspective,we don't have strong preference,and RAN2 iskindly request to discuss which option to be adopted.

[0360] Proposal 2:RAN2 to discuss which of above three options to be adopted in order to enable the SL SRB can be associated with SR configuration / resource.

[0361] In this paper, we discuss one issue on the SR configuration for SLSRB, and have the following proposals:

[0362] Proposal 1:The signaling that could enable the gNB to configurededicated SR configuration / resource associated with the UE's SL SRB should bespecified.

[0363] Proposal 2:RAN2 to discuss which of above three options to be adopted in order to enable the SL SRB can be associated with SR configuration / resource.

[0364] In this article, we discussed an issue regarding SL SRB SR configuration.

[0365] For UEs in RRC connected state, if the UE is configured to use SL mode 1 for resource allocation, the gNB can decide whether to configure a dedicated SR configuration / resource for the UE. If SR is triggered and the UE has a dedicated SR configuration / resource, the UE uses this dedicated configuration / resource to send a scheduling request. Otherwise, the UE needs to trigger a random access procedure.

[0366] For SL DRB, if the UE is in RRC connected state, the gNB can configure it through dedicated signaling. In the logical channel configuration of SLDRB, one parameter is SR configuration, as shown below. Therefore, through this signaling, if the gNB decides to do so, it can configure dedicated SR configuration / resources for the UE's SL DRB.

[0367]

[0368] Observation 1: For SL DRB, the gNB can configure the SR configuration / resources of the SL DRB through the logical channel configuration of the SL DRB.

[0369] In addition to SL DRBs, four SLSRBs for sending PC5-S messages and PC5-RRC messages are defined in NR SL. However, the configurations related to SL SRBs, including PDCP, RLC configuration, and logical channel configuration, are specified in 9.1.1 of 38.331 [1], which means that no dedicated signaling is defined to reconfigure the SL SRB configuration. Therefore, for SL SRBs, the gNB cannot configure dedicated SR configuration / resources for UEs in SL mode 1. In other words, if the SR is triggered by the SL SRB, the UE can only trigger the random access procedure to request SL authorization.

[0370] Observation 2: There is no signaling in the prior art that can support the configuration of dedicated SR configuration / resources associated with SL SRBs.

[0371] Based on the above observations, the current signaling design seems unreasonable. In our understanding, the standard should support signaling for gNB to configure dedicated SR configuration / resources for UE's SL SRBs, rather than relying solely on random access to request SL grant for SL SRB transmission.

[0372] Solution 1: Support signaling to enable the gNB to configure dedicated SR configuration / resources associated with the UE’s SL SRBs.

[0373] For signaling design, there are the following options:

[0374] Option 1: Add the SR configuration ID associated to the SL SRB in the SL-ScheduledConfig field.

[0375] The SR Configuration ID is common to all targets and all four SL SRBs. Alternatively, the SR Configuration ID can be specific to each target but the same for all four SL SRBs.

[0376] Option 2: In the specified SCCH configuration, add a new parameter such as SR configuration ID. If the gNB decides to configure SR configuration / resources for SCCH, the gNB can add such SR configuration ID in SchedulingRequestToAddMod. If no such SR configuration ID is present in SchedulingRequestToAddMod, the UE needs to trigger the random access procedure in case the SR is triggered by SL SRB.

[0377] This option has no effect on ASN.1.

[0378] Option 3: SL SRBs can use any SR configuration ID configured for the UE. It is up to the UE implementation to decide which SR configuration to use. With this option, it appears that only one note is required in the specification. However, if this option is selected, the gNB cannot choose whether to configure the SL SRB to use SR or to request SL grant using random access.

[0379] From our perspective, we do not have a strong preference and would like RAN2 to discuss which option to adopt.

[0380] Solution 2: Adopt at least one of the above three options to associate the SL SRB with the SR configuration / resource.

[0381] In this article, we discuss an issue regarding SR configuration for SL SRB and make the following recommendations:

[0382] Solution 1: Signaling shall be supported to enable the gNB to configure dedicated SR configuration / resources associated with the UE’s SL SRBs.

[0383] Solution 2: Adopt at least one of the above three options to associate the SL SRB with the SR configuration / resource.

Claims

1. A method for determining resources, applied to a communication device, characterized in that: The method comprises: Receiving first scheduling request SR configuration information; If the first SR configuration information includes preset SR configuration information, wherein the preset SR configuration information is the SR configuration information specified in the protocol, and the SR configuration information specified in the protocol is used to configure the sidelink signaling radio bearer SLSRB, then SR is sent on the first SR resource, and the first SR resource is determined based on the preset SR configuration information.

2. The method according to claim 1, characterized in that: The method further comprises: If the first SR configuration information does not include the preset SR configuration information, a random access process is initiated.

3. The method according to claim 1 or 2, characterized in that: The preset SR configuration information includes a preset SR identification ID.

4. The method according to claim 1 or 2, characterized in that: The first SR configuration information includes an SRID.

5. The method according to claim 1 or 2, characterized in that: The communication device buffers a message to be transmitted to at least one receiving user equipment, wherein: Each of the messages to be transmitted has the same preset SR configuration information.

6. The method according to claim 5, characterized in that The message to be transmitted includes at least one of a PC5 radio resource control PC5-RRC message, a non-security protected PC5 signal PC5-S message, a PC5-S message after PC5-S security establishment, and a security protected PC5-S message.

7. A method for determining resources, applied to a network communication device, characterized in that: The method comprises: Sending first scheduling request SR configuration information, where the first SR configuration information includes preset SR configuration information, where the preset SR configuration information is SR configuration information specified in the protocol, and the SR configuration information specified in the protocol is used to configure a sidelink signaling radio bearer SL SRB; An SR is received on a first SR resource, wherein the first SR resource is determined based on the preset SR configuration information.

8. The method according to claim 7, characterized in that The preset SR configuration information includes a preset SR identification ID.

9. The method according to claim 7 or 8, characterized in that: The first SR configuration information includes an SRID.

10. The method according to claim 7 or 8, characterized in that: The first SR configuration information is SR configuration information of at least one signaling radio bearer SRB between the communication device and the network communication device.

11. A communication device, characterized in that: include: A module or unit for implementing the method according to any one of claims 1 to 6.

12. The communication device according to claim 11, characterized in that: The communication device includes a user equipment or a chip in the user equipment.

13. The communication device according to claim 12, characterized in that: The user equipment is a sending end user equipment.

14. A network communication device, characterized in that: include: A module or unit for implementing the method according to any one of claims 7 to 10.

15. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed, the method according to any one of claims 1 to 6 is implemented, or the method according to any one of claims 7 to 10 is implemented.

16. A computer program product, characterized in that When the computer program product is executed, the method according to any one of claims 1 to 6 is implemented, or the method according to any one of claims 7 to 10 is implemented.

Images