Method for obtaining auxiliary sidelink communication resource allocation and computer readable medium

Abstract

The invention discloses a method for obtaining auxiliary sidelink communication resource allocation and a computer readable medium. The method for obtaining auxiliary sidelink communication resource allocation comprises the following steps: sending a request for auxiliary sidelink communication resource allocation to the second UE; receiving sidelink communication resource allocation information sent by the second UE in response to receiving the request, wherein the sidelink communication resource allocation information comprises available sidelink resource allocation; and selecting a resource for sidelink transmission from available allocated resources indicated by available sidelink resource allocations in the sidelink communication resource allocation information.

Description

[0001] This application is a divisional application of a Chinese patent application with the application number "202080099483.9", the application date of "April 9, 2020", and the title of "Methods and Devices for Resource Allocation and Release in Wireless Sidelink Communication". Technical Field

[0002] The present disclosure generally relates to wireless communication and, more particularly, to sidelink communication resource allocation, configuration, and release. Background Art

[0003] User equipment in a wireless network can communicate data with each other via a direct sidelink communication channel without data relayed by any radio access network node. In some application scenarios of sidelink communication, such as application scenarios involving vehicle wireless network equipment, the communication resource allocation and configuration of one communication terminal may involve another communication terminal in addition to the base station. Providing resource allocation, provisioning, and release mechanisms to achieve low-power and efficient use of sidelink communication resources is crucial. Summary of the Invention

[0004] The present disclosure relates to methods, systems, and devices related to wireless communication and, more particularly, to resource allocation, configuration, and release in sidelink communication between communication terminals.

[0005] In one embodiment, a method for a first user equipment (UE) to release resource allocation assistance in wireless sidelink communication is disclosed. The method may include: determining a release indication that indicates that the first UE no longer needs the second UE to assist in sidelink resource allocation after an association between the first UE and the second UE is established for the second UE to assist the first UE in sidelink resource allocation; and after determining the release indication, transmitting release information to the second UE for indicating to the second UE that the first UE no longer needs the second UE to assist in sidelink resource allocation or that the sidelink resource allocation mode of the first UE has changed.

[0006] In another embodiment, another method for a first UE to release resource allocation assistance in wireless sidelink communication is disclosed. The method may include: determining a release indication that indicates that the first UE no longer assists the second UE in sidelink resource allocation after an association between the first UE and the second UE is established for the first UE to act as an anchor UE to assist the second UE in sidelink resource allocation; and transmitting release information to the second UE for indicating to the second UE that the first UE no longer assists the second UE in sidelink resource allocation.

[0007] In another embodiment, a method for assisting a first UE to obtain a sidelink communication resource allocation from a second UE is disclosed. The method may include: transmitting a request for assisting the sidelink communication resource allocation to the second UE; in response to receiving the request, receiving sidelink communication resource allocation information sent by the second UE; and selecting from the allocated resources indicated by the sidelink communication resource allocation information.

[0008] In another embodiment, a method for assisting a second UE to perform wireless sidelink resource allocation by a first UE is disclosed. The method may include: the first UE transmitting a sidelink message indicating that the first user equipment can assist another user equipment to perform sidelink resource allocation; the first UE receiving a sidelink assistance request message; and the first UE transmitting a response to the received sidelink assistance request message to the second UE to indicate that the first UE can assist the second UE to perform sidelink resource allocation. The sidelink message may include at least one of resource allocation modes for the second UE, which includes at least one of the following: a mode of resource scheduling by the serving cell, a mode of resource allocation by the UE's autonomous selection, a semi-persistent resource allocation / scheduling mode, a dynamic resource allocation / scheduling mode, a multi-shot resource allocation mode, or a single shot resource allocation mode; an indication of the radio access technology (RAT) of the first UE; or a PC5 RAT supported by the first UE.

[0009] In another embodiment, a method for wireless sidelink resource allocation for a first UE is disclosed. The method may include: the first UE receiving a sidelink configuration message indicating multiple sidelink resource allocation modes that can be used by the first UE simultaneously; and the first UE obtaining a sidelink resource allocation via two or more of the multiple sidelink resource allocation modes. The multiple sidelink resource allocation modes may include two or more of a mode of resource allocation by the serving cell, a mode of resource allocation by the UE's autonomous resource selection, or a mode of resource allocation via assistance from a second UE.

[0010] Various devices are also disclosed. Each of these devices includes a processor and a memory, wherein the processor is configured to read computer code from the memory to implement any of the above methods.

[0011] Computer-readable media are also disclosed. Each computer-readable medium includes instructions that, when executed by a computer, cause the computer to perform any of the above methods.

[0012] The above aspects and other aspects and their embodiments are described in more detail in the drawings, the description, and the claims. Description of the Drawings

[0013] Figure 1 FIG. shows an example diagram of a wireless communication network according to various embodiments.

[0014] Figure 2 FIG. shows an example logical flow for an anchor UE to assist another UE in sidelink resource allocation.

[0015] Figure 3 FIG. shows an example logical flow for configuring, restarting, and deactivating a timer that is used in the process of releasing the anchor UE so that it no longer assists the second UE in sidelink resource allocation.

[0016] Figure 4 FIG. shows an example logical flow for the anchor UE to initiate the release of the anchor UE so that it no longer assists the second UE in sidelink resource allocation.

[0017] Figure 5 FIG. shows an example logical flow for the anchor UE to initiate the release of the anchor UE so that it no longer assists the second UE in sidelink resource allocation.

[0018] Figure 6 FIG. shows an example logical flow for a UE to switch its anchor UE to assist in sidelink resource allocation.

[0019] Figure 7 FIG. shows another example logical flow for an anchor UE to assist a second UE in sidelink resource allocation. DETAILED DESCRIPTION

[0020] The techniques and examples of the embodiments and / or examples in the present disclosure can be used to improve the performance in a wireless communication system. The term "exemplary" is used to mean "an example of...", and unless otherwise stated, it does not mean an ideal or preferred example, embodiment, or example. Section headings are used in this disclosure for ease of understanding, rather than limiting the techniques disclosed in the section to the corresponding section. However, note that these embodiments can be embodied in various different forms, and thus, the scope of the present disclosure or the claimed subject matter is intended to be construed as not limited to any of the embodiments set forth below. The various embodiments can be embodied as methods, devices, components, or systems. Thus, the embodiments of the present disclosure can, for example, take the form of hardware, software, firmware, or any combination thereof.

[0021] A vehicle network refers to a network system used for wireless communication and information exchange between vehicles, pedestrians, roadside devices, the Internet, and other data networks according to various communication protocols and data exchange standards. Vehicle network communication helps improve road safety, enhance traffic efficiency, and provide broadband mobile data access and data exchange between nodes in the network. Vehicle network communication can be classified into various types according to different communication endpoints, including but not limited to vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure / vehicle-to-network (V2I / V2N) communication, and vehicle-to-pedestrian (V2P) communication. These types of communication are collectively referred to as vehicle-to-everything (V2X) communication.

[0022] Such a vehicle network may rely heavily on sidelink communication between terminal devices or user equipment (UE) in the network. As used in this disclosure, sidelink communication refers to the direct wireless information exchange between UEs. For example, V2X communication can rely on direct sidelink data exchange from a source UE to a destination UE via the air interface without being forwarded by any radio base station. This communication mode has been studied and implemented in the Third Generation Partnership Project (3GPP). An example V2X subsystem based on sidelink communication technology is shown as Figure 1 part of, and can be referred to as, for example, PC5-based V2X communication or V2X sidelink communication.

[0023] The application scenarios of V2X communication are expanding and diversifying. Advanced V2X services and applications include but are not limited to vehicle platooning, extended sensors, semi-autonomous driving, fully autonomous driving, and remote driving. These applications and services require increasingly high network performance, including wider bandwidth, lower latency, and higher reliability. For example, these applications and services may require the basic sidelink communication technology to support communication data packets sized from 50 to 12,000 bytes, a message transmission rate of 2 to 50 messages per second, a maximum end-to-end latency of 3 to 500 milliseconds, a transmission reliability of 90% to 99.999%, a data transmission rate of 0.5 to 1000 Mbps, and a signal range of 50 to 1000 meters, depending on the specific data services required by these applications.

[0024] Although communication can be carried out between the various UEs described above using sidelinks, the various UEs can also be connected to a radio access network and connected to a core network via the access network. The radio access network and the core network can participate in configuring and providing the communication resources required for sending / receiving data and control information for sidelink communication. Example radio access networks can be based on, for example, cellular 4G LTE or 5G NR technology and / or formats. Figure 1FIG. 0 shows an example system diagram of a wireless access communication network 100 including UEs 102, 124, and 126 and a wireless access network node (WANN) 104. Each of UEs 102, 124, and 126 may include, but is not limited to, a mobile phone, a smartphone, a tablet computer, a laptop computer, a vehicle in-vehicle communication device, a roadside communication device, a sensor device, a smart appliance (such as a television, a refrigerator, and an oven), or other devices capable of wireless communication over a network. The UEs may communicate with each other indirectly via the WANN 104 or directly with each other via a sidelink. As Figure 1 shown, each UE (such as UE 102) may include a transceiver circuit 106 coupled to an antenna 108 to enable wireless communication with the WANN 104 or another UE (such as UE 124 or 126). The transceiver circuit 106 may also be coupled to a processor 110, which may also be coupled to a memory 112 or other storage device. The memory 112 may store computer instructions or code therein, which, when read and executed by the processor 110, cause the processor 110 to implement various methods described herein for sidelink resource allocation / configuration / release and data transmission / reception.

[0025] Similarly, the WANN 104 may include a base station or other wireless network access point capable of wirelessly communicating with one or more UEs over a network and communicating with a core network. For example, the WANN 104 may be implemented in the form of a 4G LTE base station, a 5G NR base station, a 5G central unit base station, or a 5G distributed unit base station. Each of these types of WANNs may be configured to perform a corresponding set of wireless network functions. The WANN 104 may include a transceiver circuit 114 coupled to an antenna 116, which may include various forms of antenna towers 118, to enable wireless communication with UEs 102, 124, and 126. The transceiver circuit 114 may be coupled to one or more processors 120, which may also be coupled to a memory 122 or other storage device. The memory 122 may store instructions or code therein, which, when read and executed by the processor 120, cause the processor 120 to implement various functions. For example, these functions may include functions related to sidelink resource allocation, configuration, provisioning, and release described below.

[0026] For simplicity and clarity, only one WAN and three UEs are shown in the wireless communication access network 100. It should be understood that one or more WANNs may exist in a wireless communication network, and each WANN may serve one or more UEs. Although Figure 1The UEs 102, 124, and 126 therein are shown as being served within a serving cell, but they may alternatively be served by different cells and / or not be served by a cell. Although various embodiments of sidelink communication are discussed below in the context of the specific example cellular radio communication access network 100, the basic principles apply to other types of wireless communication networks.

[0027] Figure 1 Sidelink communication between various UEs can support the coexistence of various different communication broadcast types, including unicast, multicast (or groupcast), and broadcast. In conventional techniques, UEs deployed in the access network 100 may be required to perform exhaustive monitoring of a wide range of sidelink radio resources in unicast, multicast, or broadcast mode, resulting in high power consumption. For some low-power UEs, this power consumption may be at an unacceptable high level. To address these issues, a low-power UE can request another UE to act as an anchor UE to assist in allocating sidelink resources for the low-power UE. In this way, the anchor UE, which is less restricted by power consumption, can be responsible for monitoring and sensing the sidelink transmission resource pool to assist in the sidelink resource allocation of the low-power UE. Therefore, the low-power UE can reduce the frequency and number of its sensing and monitoring of the sidelink communication resource pool. The term "anchor UE" is used in this disclosure to indicate the auxiliary role of a UE in resource allocation for other UEs.

[0028] Although the following various embodiments may be beneficial for the resource allocation and release of low-power UEs, the basic principles apply to the sidelink resource allocation and release of any other UEs.

[0029] The various embodiments described below relate to example processes for: (1) a UE establishing an auxiliary relationship with an anchor UE to obtain assistance in sidelink resource allocation, (2) releasing such an auxiliary relationship under various conditions, and (3) the assisted UE selecting the configured sidelink resources allocated from the anchor UE. First Embodiment (Process for Assisting Sidelink Resource Allocation by an Anchor UE)

[0030] As an example, referring to Figure 2 this embodiment describes Figure 1The communication process between UE 102 and UE 124 so that UE 102 acts as an anchor UE to assist in allocating sidelink resources for UE 124. It is assumed that UE 102 is eligible to act as an anchor UE. An example process for establishing UE 102 as eligible to act as an anchor UE is described in the PCT international application No. PCT / CN2020 / 077568 filed with the Chinese Patent Office by the same applicant as the present patent application on March 3, 2020 and entitled "Device and Methods for Allocating Resources for Sidelink Transmission", the entire content of which is incorporated herein by reference.

[0031] As Figure 2 shown, the anchor UE 102 may transmit a sidelink message (202) indicating that UE 102 is acting as an anchor user equipment. The sidelink message may be carried in a sidelink broadcast message, a sidelink multicast message, a sidelink radio resource control (RRC) message, a PC5-MIB message, or a sidelink control information message. Thus, the sidelink message may be transmitted to UE 124 in a broadcast, multicast, or unicast manner.

[0032] In some embodiments, the sidelink message may include, for example, access control information about UE 102. The access control information may include, for example, the channel quality between UE 102 and the cell serving UE 102, the current load rate of UE 102, the number of user equipments for which UE 102 is assisting in allocating sidelink resources, the geographical location identifier of UE 102, and the quality of service supported by UE 102.

[0033] Additionally or alternatively, the sidelink message may include, for example, the resource allocation mode of UE 124. Such a resource allocation mode may include, but is not limited to, a mode of resource allocation by the serving cell, a mode of resource allocation by UE autonomous selection, a semi-persistent resource allocation / scheduling mode, a dynamic resource allocation / scheduling mode, a multiple resource allocation mode; or a single resource allocation mode.

[0034] Additionally or alternatively, the sidelink message may include an indication of the current radio access technology (RAT) of the current Uu interface between UE 102 and its serving cell, including but not limited to E-UTRAN technology, new radio (NR) technology, or dual-link connection technology.

[0035] Alternatively or additionally, the sidelink message may include the PC5 radio access technology supported by UE 102.

[0036] Alternatively or additionally, the sidelink message may include, for example, an indication that UE 102 supports the relay function or the roadside unit function. The sidelink message may also include, for example: a destination identifier indicating that UE 102 is capable of assisting in allocating sidelink resources for sidelink transmissions of UE 124 having such a destination identifier; quality of service information indicating that UE 102 is capable of assisting in allocating sidelink resources for sidelink transmissions of UE 124 having such quality of service information; a transmission type indicating that UE 102 is capable of assisting in allocating sidelink resources for sidelink transmissions of UE 124 of such a transmission type; a serving cell identifier of the cell serving UE 124; the number of allocable resources in the sidelink transmission resource pool; the CBR of the transmission resource pool; and a resource utilization rate indicating the ratio of the allocated resources to the allocable resources in the transmission resource pool.

[0037] As Figure 2 Further shown in 204 as such, UE 124 may receive a sidelink message indicating that UE 102 is acting as an anchor user equipment. Upon receiving the sidelink message, UE 124 may transmit a request message to UE 102, which requests assistance in allocating sidelink resources for UE 124 (206). The request message may include, for example, an identifier of UE 124, power saving information of UE 124, a sidelink destination index or destination identifier to be used by UE 124 in sidelink transmissions, a sidelink source index or source identifier to be used by UE 124 in sidelink transmissions, sidelink quality of service information to be used by UE 124 in sidelink transmissions, coverage status information indicating whether UE 124 is within or outside the coverage area of any radio access network node, a serving cell identifier of the cell serving UE 124, a list of frequency information to be used by UE 124 in sidelink transmissions, and a sidelink transmission type / broadcast type to be used by UE 124 in sidelink transmissions.

[0038] As Figure 2 Shown in 208 as such, UE 102 may receive the request message from UE 124. In response to the request message, UE 102 may transmit a response message to UE 124 indicating whether to assist in allocating sidelink resources for UE 124 (210).

[0039] As Figure 2 Further shown in 212 as such, UE 124 may receive the response message from UE 102. The response message may indicate that UE 102 will assist in allocating sidelink resources for UE 124. Such a response message may include, for example, the following information to facilitate UE 124 in obtaining sidelink resource allocation via the anchor UE 102:

[0040] · A scheduling request configuration set information, which indicates the resource configuration for the UE 124 to transmit a scheduling request to the UE 102, · A destination identifier list, which indicates that the UE 102 can assist in allocating sidelink resources for the sidelink transmission of a second user equipment having one or more destination identifiers in the destination identifier list,

[0041] · Quality of service information, which indicates that the UE 102 can assist in allocating sidelink resources for the sidelink transmission of the UE 124 having the quality of service information,

[0042] · Transmission type or broadcast type, which indicates that the UE 102 can assist in allocating sidelink resources for the sidelink transmission of the UE

[0043] 124 in this transmission or broadcast type, and

[0044] · A range of HARQ process ID lists, which indicates that the UE 102 can assist in allocating sidelink resources for the sidelink transmission of the UE 124 having a HARQ process ID within the range of the HARQ process ID list.

[0045] Optionally, the response message may further include information about the transmission resource pool of the UE 124, for example.

[0046] Optionally, as Figure 2 shown in 214, in the case where the response message indicates that the UE 102 will assist in allocating sidelink resources for the UE 124, the UE 102 may separately transmit scheduling request configuration information to the UE 124. The UE 124 may use the scheduling request configuration to construct a scheduling request.

[0047] As Figure 2 shown in 216, the UE 124 may receive scheduling request configuration information from the UE 102. Then, when the UE 124 needs to perform a sidelink transmission, the UE 24 may generate a scheduling request for the sidelink transmission based on the received scheduling request configuration information, as shown in 218, and transmit the scheduling request to the UE 102, as shown in 220.

[0048] In response to receiving the scheduling request (as shown in 222), the UE 102 may, for example, allocate sidelink resources in the transmission resource pool for the UE 124 (as shown in 224), and as shown in 226, transmit a resource allocation message including information about the allocated sidelink resources to the UE 124.

[0049] Alternatively, at 214, UE 102 may transmit buffer status report configuration information to UE 124. Then, UE 124 may generate a buffer status report (at 218) based on the buffer status report configuration information and transmit the buffer status report to UE 102 (at 220). In response to receiving the buffer status report, UE 102 may, for example, allocate sidelink resources in the transmission resource pool of UE 124 (224) and transmit a resource allocation message including information on the allocated sidelink resources to UE 124 (226).

[0050] Optionally, before transmitting a request message (206) to UE 102 requesting assistance in allocating sidelink resources for UE 124, if UE 124 is covered by a WANN such as WANN 118, UE 124 may transmit a radio resource control (RRC) message to WANN 118. The RRC message may carry at least one of the following: for example, an identifier of UE 124, an identifier of the cell serving UE 124, power saving information of UE 124, a sidelink destination index or destination identifier to be used by UE 124 in sidelink transmission, sidelink quality of service information to be used by UE 124 in sidelink transmission, a list of frequency information to be used by UE 124 in sidelink transmission, or a sidelink transmission / broadcast type to be used by UE 124 in sidelink transmission.

[0051] Then, UE 124 may receive the RRC message from WAN 118. The RRC message may indicate whether UE 124 is allowed to obtain sidelink resource allocation via UE 102.

[0052] Optionally, the RRC message may include, for example, information about the transmission resource pool, which indicates the scope of the transmission resource pool of UE 124. The RRC message may also include, for example,

[0053] · a transmission type, which indicates that UE 102 is capable of assisting in allocating sidelink resources for sidelink transmission of user equipment in this transmission type;

[0054] · a destination identifier, which indicates that UE 102 is capable of assisting in allocating sidelink resources for sidelink transmission of UE 124 with the destination identifier;

[0055] · sidelink quality of service information, which indicates that UE 102 is capable of assisting in allocating sidelink resources for sidelink transmission of UE 124 with the sidelink quality of service information; and

[0056] · The range of the HARQ process ID list, which indicates that UE 102 can assist in allocating sidelink resources for the sidelink transmissions of UE 124 having HARQ process IDs within the HARQ process ID list range.

[0057] Optionally, before transmitting a response message (210) indicating whether to assist in allocating sidelink resources for UE 124 to UE 124, UE 102 may transmit an RRC message to WANN 118 to request authorization to assist in allocating sidelink resources for UE 124. The RRC message may include, for example, one or more identification information of UE 124; power saving information of UE 124; in sidelink transmissions, the sidelink destination index or destination identification that UE 124 is interested in; sidelink quality of service information to be used by UE 124 in sidelink transmissions; a list of frequency information that UE 124 is interested in during sidelink transmissions; and the sidelink transmission / broadcast type to be used by UE 124 in sidelink transmissions.

[0058] Then, UE 102 may receive an RRC message from WANN 118, which indicates whether to authorize or allow UE 102 to assist in allocating sidelink resources for UE 124. The RRC message may also include, for example, · identification information of the user equipment, which indicates that UE 102 can assist in allocating sidelink resources for the user equipment, · information about the transmission resource pool, which indicates that UE 102 assists in allocating sidelink resources in the transmission resource pool,

[0059] · Scheduling request configuration set information for configuring scheduling request resources for UE 124,

[0060] · The range of the hybrid automatic repeat request (HARQ) process ID list, which indicates that UE 102 can assist in allocating sidelink resources for the sidelink transmissions of UE 124 having HARQ process IDs within the HARQ process ID list range,

[0061] · Destination identification, which indicates that UE 102 can assist in allocating sidelink resources for the sidelink transmissions of UE 124 having the destination identification,

[0062] · Quality of service information, which indicates that UE 102 can assist in allocating sidelink resources for the sidelink transmissions of UE 124 having the quality of service information,

[0063] · Transmission type, which indicates that UE 102 can assist in allocating sidelink resources for the sidelink transmissions of UE 124 in this transmission type, and

[0064] · A list of sidelink radio bearers (SLRBs) or logical channels, which indicates that UE 102 is capable of assisting in the allocation of sidelink resources for the sidelink radio transmission or logical channels of UE 124.

[0065] In some other embodiments, UE 124 may support multiple modes of sidelink resource allocation. For example, UE 124 may receive a sidelink configuration message that indicates multiple sidelink resource allocation modes that can be used simultaneously by UE 124. Then, UE 124 may determine a set of sidelink resource allocation modes among multiple sidelink resource allocations; and simultaneously use the set of sidelink resource allocation modes to obtain sidelink resource allocations for sidelink communication. The multiple sidelink resource allocation modes may include two or more of a mode of resource allocation by the serving cell, a mode of resource allocation by UE autonomous resource selection, or a mode of resource allocation via assistance from a second UE. Optionally, UE 124 may also receive indication information indicating the simultaneous modes of sidelink resource allocation supported by the PC5 RAT and each PC5 RAT, or receive cross-RAT indication information indicating the simultaneous modes of sidelink resource allocation supported by cross-RAT. Optionally, UE 124 may also receive priority information indicating the relative priorities among the multiple sidelink resource allocation modes.

[0066] Second embodiment (determining candidate anchor UEs and selecting an anchor UE from the candidate anchor UEs)

[0067] As an example, this embodiment describes the manner in which UE 124 selects a specific user equipment (such as UE 102) to assist in the allocation of sidelink resources for UE 124 when multiple user equipments are available as anchor user equipments. Once UE 124 selects a specific UE to act as its anchor user equipment, the example sidelink resource allocation assistance process described in the first embodiment above is applied.

[0068] UE 124 may receive sidelink messages from multiple user equipments (such as UE 102 and 126). The sidelink messages may indicate that the user equipment sending the sidelink message can act as an anchor user equipment, and may include information indicating the qualification for acting as an anchor user equipment. Such sidelink messages may include the above regarding applied to UE 102 or UE 126 Figure 2The various information discussed in 202. Additionally or optionally, such a sidelink message may include an indication of whether the user equipment transmitting the sidelink message is the group header of a sidelink communication group. Then, based on the sidelink message, UE 124 can identify which one of the multiple user equipments is the group header of the sidelink communication group of which UE 124 is a member. If such a user equipment is identified, UE124 can directly select the header user equipment to assist in allocating sidelink resources for UE 124.

[0069] Alternatively or additionally, UE 124 may first select a candidate user equipment that meets a predetermined candidate condition from among the multiple user equipments based on the sidelink message. The predetermined candidate condition may include, for example, at least one of the following items:

[0070] · The load rate of the candidate user equipment is lower than a load rate threshold,

[0071] · The number of user equipments that the candidate user equipment is assisting in allocating sidelink resources to is lower than a number threshold,

[0072] · The channel quality of the candidate user equipment is higher than a channel quality threshold,

[0073] · The quality of service range supported by the candidate user equipment includes the quality of service of the sidelink data that UE 124 is to transmit,

[0074] · The resources available for allocation to the candidate user equipment exceed a resource availability threshold,

[0075] · The resource utilization rate of the resources to be allocated to the candidate user equipment is lower than a resource utilization rate threshold,

[0076] · The CBR of the transmission resource pool of the candidate user equipment is lower than a CBR threshold,

[0077] · The list of sidelink group communication destination identifiers includes the sidelink group communication destination identifier of the sidelink data that UE 124 is to transmit,

[0078] · The candidate user equipment and UE 124 belong to the same sidelink communication group,

[0079] · The geographical distance between the candidate user equipment and UE 124 is less than a geographical distance threshold, or

[0080] · The candidate user equipment and UE 124 are being served in the same cell.

[0081] Then, UE 124 may select one of the candidate user equipments that meet one or more of the above conditions to assist in allocating sidelink resources for UE 124. The selection from the candidate user equipments may be based on the selected candidate user equipment that meets a predetermined selection condition, and the predetermined selection condition may include, for example, one of the following conditions: · The candidate user equipment is the group header of a sidelink communication group.

[0082] · The candidate user equipment has the best channel quality between the candidate user equipment and the cell serving the candidate user equipment or between the candidate user equipment and UE 124.

[0083] · The candidate user equipment and UE 124 belong to the same sidelink communication group.

[0084] · The candidate user equipment and UE 124 are being served in the same cell.

[0085] · The resource allocation mode of the candidate user equipment is the radio access network node scheduling mode.

[0086] · The candidate user equipment has the most resources available for allocation.

[0087] · The candidate user equipment has the lowest resource utilization rate with respect to the resources to be allocated by the candidate user equipment.

[0088] · The transmission resource pool of the candidate user equipment has the lowest channel busy rate.

[0089] · The candidate user equipment supports the roadside unit function, or

[0090] · The candidate user equipment supports the relay function.

[0091] Optionally, before selecting a candidate user equipment that meets the predetermined criteria from multiple user equipments, UE 124 may receive the predetermined criteria from WANN 118. For example, the UE may receive metrics from WANN 118, such as a load rate threshold, a quantity threshold, a channel quality threshold, the quality of service range supported by the user equipment, and a geographical distance threshold. Alternatively, the metrics may be pre-configured in UE 124.

[0092] Third Embodiment (Releasing the Anchor UE from Assisting Sidelink Resource Allocation)

[0093] Figure 1UE 124 may select, for example, UE 102 as the anchor UE and obtain assistance for sidelink resource allocation from UE 102 after various procedures described above in the first and second embodiments. For example, the connection between UE 124 and UE 102 may be implemented as a unicast connection (even though other broadcast-type connections may be feasible). When such a connection is released and thus UE 124 and UE 102 are effectively disconnected, the responsibility of UE 102 as the anchor UE of UE 124 may be released accordingly. In other words, after the connection between UE 124 and UE 102 is released, UE 102 will no longer act as the anchor UE for assisting UE 124 in sidelink resource allocation.

[0094] For example, the connection between UE 124 and the anchor UE 102 may time out (e.g., T400 timeout), or the sidelink RRC reconfiguration may fail, e.g., as indicated by the sidelink radio link control (RLC) entity, the maximum number of retransmissions to a specific destination has been reached. In any of these cases or some other cases, the connection between UE 102 and UE 124 may be considered released. Then UE 102 is no longer considered as the anchor UE for assisting UE 124 in sidelink resource allocation.

[0095] However, in some cases, there may be no data transmission between the anchor UE 102 and UE 124 for a long time. The connection between UE 124 and UE 102 may have been lost during this period (e.g., because the distance between UE 124 and UE 102 has increased too much), yet this disconnection may not be detected because there is no data transmission and thus no detectable T400 timeout and no detectable RRC reconfiguration failure. In this case, even though the connection between UE 102 and UE 124 has been lost, UE 102 may still be considered as the anchor UE of UE 124. Therefore, in order to provide more efficient resource allocation, it may be desirable to have a separate mechanism for releasing UE 102 from acting as the anchor UE of UE 124.

[0096] In some embodiments, a timer may be used to provide a separate mechanism for releasing UE 102 from acting as the anchor UE of UE 124. Such a timer may be referred to as a release timer. The release timer may be based on Figure 3The logical flow 300 is configured, activated (restarted), and deactivated (stopped). For example, as shown at 310, the release timer can be initially configured with predefined time parameters. Such time parameters can be obtained from the serving cell of UE 124 or the anchor UE 102. Alternatively, the initial time parameters can be preconfigured in UE 124 or UE 102. As shown at 320, the release timer can be conditionally restarted (e.g., counting down from an initial value) at various stages. For example, when UE 124 transmits a sidelink scheduling request (SR) or buffer status report (BSR) to UE 102 (e.g., at Figure 2 220 of) or after, the release timer can be restarted. Alternatively, when UE 124 transmits sidelink information or sidelink UE assistance information included in, for example, Figure 2 the sidelink request message 206, the timer can be restarted. As further shown at 330, the activated release timer can be conditionally deactivated (e.g., stop counting down). For example, when UE 124 receives a sidelink resource allocation from the anchor UE 102, the release timer can be deactivated (stopped).

[0097] When the release timer is counting down, it can be monitored. When the timer expires, then UE102 can be triggered to release from being the anchor UE of UE 124. This trigger due to timer expiration can be implemented in parallel with other release mechanisms or triggers. These other release trigger conditions can include, for example, but are not limited to:

[0098] · When UE 124 enters the RRC sidelink connected state,

[0099] · When UE 124 receives configuration information from its serving cell indicating that the first UE will transmit sidelink communications based on network scheduling, the first UE will transmit sidelink communications based on the first UE's autonomous resource selection,

[0100] · When UE 124 receives configuration information from its serving cell indicating that it is no longer allowed to use other UEs to assist in allocating sidelink resources,

[0101] · When UE 102 is no longer eligible to act as an anchor UE to assist other UEs in sidelink resource allocation,

[0102] · When the serving cell of UE 102 indicates to UE 102 that it cannot act as an anchor UE to assist other UEs in sidelink resource allocation.

[0103] When any of the above conditions is triggered or the timer expires, UE 102 can be released to no longer act as the anchor UE for assisting UE 124 in sidelink resource allocation. As described in several examples below, the release process can be initiated by UE 124 or UE 102. Generally, a release message can be sent from one UE to another UE. The release message can also include an indication of the release reason. The reason can include time expiration or any of the above trigger conditions. The other UE receiving the release message can send a response message.

[0104] Once UE 102 is released to no longer act as the anchor UE for UE 124, various options regarding the sidelink resources that have been allocated by UE 102 to UE 124 can be provided. For example, UE 124 may not be allowed to continue using the sidelink resources previously allocated by the released UE 102. As another example, and to facilitate the continuity of sidelink services, UE 124 may be allowed to continue using the sidelink resources previously allocated by UE 102 even if UE 102 has been released from the anchor role. Alternatively, UE 124 may be allowed to use resources from a certain emergency or exceptional sidelink resource pool instead of the sidelink resources previously allocated by the released UE 124. Accordingly, the release message or some other message to UE 124 can include an indicator for indicating whether UE 124 can continue using the sidelink resources previously allocated by the released UE 102.

[0105] In some embodiments, UE 124 can initiate the release of UE 102 to no longer act as the anchor UE for UE 124. Figure 4 An example is shown in the logical flow 400. At 410, UE 124 determines that one or more release conditions have been triggered and an indication that UE 102 does not continue to act as the anchor UE to assist UE 124 in sidelink resource allocation. The release conditions can include at least one of the following:

[0106] · The release timer has expired,

[0107] · UE 124 has entered the RRC sidelink connected state,

[0108] · UE 124 receives configuration information from its serving cell, which indicates that the sidelink resources of UE 124 will be used to transmit sidelink communication based on, for example, network scheduling by its serving cell,

[0109] · UE 124 receives a configuration from its serving cell, which indicates that it will transmit sidelink communication based on the autonomous resource selection of UE 124,

[0110] ·UE 124 receives configuration information from its serving cell, which indicates that it is no longer allowed to use other UEs to assist in allocating sidelink resources, or that its sidelink resource allocation will not be provided by other UEs. · The number of transmissions reaches the maximum retransmission number at UE 124.

[0111] · UE 124 meets at least one of a set of radio communication environment conditions.

[0112] The initial time value of the release timer and the maximum retransmission number can be configured in UE 124 by its serving cell, or can be configured by UE 102. When UE 124 transmits a sidelink scheduling request or a sidelink buffer status report, or when UE 124 transmits sidelink UE information or sidelink UE assistance information, the release timer can be restarted or the retransmission number can be incremented by 1 by UE 124. When UE 124 receives sidelink resource allocation information from UE 102, the release timer can be stopped or the transmission number can be set to zero.

[0113] The above set of radio communication environment conditions can include but are not limited to:

[0114] · UE 124 enters the cellular coverage area (when it was not previously covered by a cell).

[0115] · The channel quality between UE 124 and UE 102 is less than a first channel quality threshold.

[0116] · The distance between UE 124 and UE 102 is greater than a second distance threshold.

[0117] · UE 124 detects that the CBR of the allocable sidelink resource pool is lower than a third CBR threshold.

[0118] · UE 124 leaves the sidelink communication group to which UE 102 belongs.

[0119] · UE 124 identifies another UE that is more suitable to act as an anchor UE to assist UE 124 in sidelink resource allocation (more details are provided below in connection with the fifth embodiment).

[0120] As Figure 4 shown in 420, once at Figure 4If one or more release conditions are triggered in the 410 of [description missing], UE 124 sends a release message to UE 102. The release message is used to indicate to UE 102 that UE 102 is released and no longer responsible for acting as an anchor UE to assist UE 124 in sidelink resource allocation. Depending on the reason for the release (determined by the various triggering conditions above), the release message can alternatively be used to indicate to UE 102 that the sidelink resource allocation mode of UE 124 has changed (e.g., from UE-assisted to allocated by the serving cell).

[0121] The release message can optionally include an indication of the reason for the release. Corresponding to the above release triggering conditions, the reason for the release can include one or more of the following:

[0122] · The release timer expires,

[0123] · A change in the RRC connection state;

[0124] · A change in the sidelink resource allocation mode;

[0125] · A degradation in the first channel quality between the first UE and its serving cell;

[0126] · A degradation in the second channel quality between the first UE and the second UE;

[0127] · Detection of a low channel busy rate (CBR) of the configured sidelink resource pool;

[0128] · Leaving the sidelink communication group including the second UE; or

[0129] The first UE determines to switch to a third UE as the anchor UE to assist the first UE in sidelink resource allocation. Optionally, the release message can include an indicator for indicating whether UE 124 will continue to use the sidelink resources previously allocated by the released anchor UE 102.

[0130] Optionally, the release process 400 can further include Figure 4 step 430, in which the anchor UE 102 receives the release message and transmits a response to UE 124 to confirm the release of UE 102 so that it no longer acts as the anchor UE for assisting UE 124 in sidelink resource allocation.

[0131] In some embodiments, the release process 400 can further include step 402 before step 410, in which the release condition is determined by UE 124. Specifically, in step 402, UE 124 can first obtain the various thresholds for triggering the release as described above, including but not limited to the first channel quality threshold, the second distance threshold, and the third CBR threshold. These thresholds can be obtained by UE 124 from its serving cell. Alternatively, these thresholds can be pre-configured in UE 124.

[0132] In some other example embodiments, the anchor UE 102 instead of the UE 124 may initiate the release of the UE 102 so that it no longer acts as the anchor UE for the UE 124. Figure 5 An example is shown in the logic flow 500. At 510, the UE 102 determines that it is no longer responsible for assisting the UE 124 in performing sidelink allocation. Under various example conditions, the UE 102 may decide to release itself as the anchor UE for the UE 124. For example, the serving cell of the UE 102 may send a configuration message to the UE 102 to indicate to the UE 102 that the UE 124 will obtain sidelink resource allocation by its own resource selection (or the UE will transmit sidelink communication based on autonomous resource selection). For another example, the serving cell of the UE 102 may send a configuration message to the UE 102 to indicate that the UE 102 is no longer allowed to assist other UEs in sidelink resource allocation. For yet another example, the UE 102 may determine that one or more other release trigger conditions are met. These release trigger conditions may include, but are not limited to: · The channel quality between the UE 102 and its serving cell is less than a first channel quality threshold,

[0133] · The current load rate of the UE 102 is higher than a second load rate threshold;

[0134] · The UE 102 detects that the CBR of the allocable sidelink resource pool is higher than a third CBR threshold;

[0135] · The channel quality between the UE 102 and the UE 124 is less than a fourth channel quality threshold,

[0136] · The distance between the UE 102 and the UE 124 is greater than a fifth distance threshold,

[0137] · The UE 102 leaves the sidelink communication group to which the UE 124 belongs,

[0138] · The UE 102 is no longer the head UE of the sidelink communication group to which the UE 124 belongs.

[0139] As Figure 5 shown, the release process 500 further includes step 520, where the anchor UE 102 sends a release message to the UE 124. The release message can be used to indicate to the UE 124 that the UE 102 no longer acts as an anchor UE to assist the UE 124 in performing sidelink resource allocation. Corresponding to the trigger condition that causes the release, the release message may include one of multiple reasons for the release. The reasons may include, but are not limited to:

[0140] · Channel quality degradation,

[0141] · Change in RRC connection state,

[0142] · Change in resource acquisition mode,

[0143] · UE 102 leaves the sidelink communication group,

[0144] · UE 102 no longer acts as the head UE of the sidelink communication group,

[0145] · High current load rate,

[0146] · High CBR,

[0147] · Large distance between UE 102 and UE 124,

[0148] The above channel degradation reasons may include channel quality degradation between UE 102 and its serving cell or channel quality degradation between UE 102 and UE 124.

[0149] As Figure 5 Further shown in, the release process 500 may further include step 530, where UE 124 receives a release message from UE 102 and in response confirms to release UE 102 no longer acting as the anchor UE assisting UE 124 for sidelink resource allocation.

[0150] Optionally, the release message transmitted by UE 102 may include an indicator for indicating to UE 124 whether UE 124 can continue to use the sidelink resources previously allocated by the released anchor UE 102.

[0151] In some embodiments, the release process 500 may further include step 502 before step 510, where the release condition is determined by UE 102. Specifically, in step 502, UE 124 may first obtain the various thresholds for triggering release as described above, including but not limited to the first channel quality threshold, the second load rate threshold, the third CBR threshold, the fourth channel quality threshold, and the fifth distance threshold. These thresholds may be obtained by UE 102 from its serving cell. Alternatively, these thresholds may be pre-configured in UE102.

[0152] Fourth Embodiment (Selecting the Head UE as the Anchor UE)

[0153] In some embodiments, UE 102 and UE 124 may belong to the same sidelink multicast group. UE 102 may be specifically configured as the head UE of the multicast group. When UE 102 needs assistance in sidelink allocation, it may select the head UE as the anchor UE. For example, UE 124 may first identify the head UE in the group via signaling exchange with its serving cell and / or other UEs in the sidelink multicast group. Then, it may request and establish the head UE 102 to act as the anchor UE to assist it in sidelink resource allocation. When either UE 102 or UE 124 (as the head UE and the anchor UE) leaves the sidelink multicast group, at the initiation of UE 124 or at the initiation of UE 102, UE 124 may be released to no longer act as the anchor UE of UE 102, as described in the third embodiment above.

[0154] Fifth Embodiment (Switching to Anchor UE)

[0155] For UE 124 that is currently assisted by the anchor UE 102 in sidelink resource allocation and when UE 102 has not been released from acting as the anchor UE, one or more other UEs may have become more eligible to act as the anchor UE of UE 102. The anchor UE of UE 124 may be switched to one of the more eligible UEs. In some embodiments, UE 124 may send a scheduling request to the more eligible UE to request it to be used as the anchor UE. After the more eligible UE accepts and confirms, the original assistance relationship between UE 102 and UE 124 may be released, and the more eligible UE will replace UE 102 as the anchor UE to assist UE 102 in sidelink resource allocation.

[0156] In some embodiments, to avoid frequent switching of the anchor UE and the resulting reduction in system efficiency, it may be required that the candidate anchor UE to which UE 124 is to switch is more eligible to be the anchor UE than UE 102, with at least a threshold improvement in at least some aspects, such as the channel quality with its serving cell, the channel quality with UE 124, the load rate, the distance to UE 124, etc., as described in more detail below.

[0157] Figure 6Shows an example logical flow 600 for switching the anchor UE. In step 610, the UE assisted in the sidelink resource allocation, i.e., UE 124, selects a UE other than UE 102 as its anchor UE. In step 520, the assisted UE may initiate a release process to release UE 102 by sending a release message to UE 102 so that it no longer acts as the anchor UE for assisting UE 124 in sidelink resource allocation. The release message is used to indicate to UE 102 that it is no longer responsible for acting as the anchor UE for assisting UE 124 in sidelink resource allocation. The example content of the release message and the subsequent release process may follow the description in the above third embodiment. Specifically, the release message may include an indicator for indicating whether the sidelink resources previously allocated by UE 102 will continue to be used for the sidelink communication of UE 124.

[0158] As Figure 6 Further shown in 620, the current anchor UE 102 is released from its anchor role for UE 124. In 630, an assistance relationship can be established between the newly selected UE and UE 124, and the newly selected UE can then act as the anchor UE for UE 124. The process for establishing the newly selected UE as the anchor UE may follow the processes described in the above respective embodiments. Step 630 may alternatively be performed before step 620.

[0159] The criteria for UE 124 when selecting a new anchor UE or determining that the newly selected UE is more qualified than UE 102 by at least some thresholds may include at least one of the following:

[0160] · The difference between the load rate of UE 102 and the load rate of the new UE is greater than the first load rate difference threshold.

[0161] · The difference between the CBR of the configured resource pool of UE 102 and the CBR of the configured resource pool of the new UE is greater than the second CBR difference threshold.

[0162] · The difference between the channel quality between the new UE and UE 124 and the channel quality between UE 102 and UE 124 is greater than the third channel quality difference threshold.

[0163] · The difference between the channel quality between the new UE and its serving cell and the channel quality between UE 102 and UE 102's serving cell is greater than the fourth channel quality difference threshold.

[0164] · The difference between the distance between UE 102 and UE 124 and the distance between the new UE and UE 124 is greater than the fifth distance difference threshold.

[0165] Optionally, as Figure 6As shown in 602, the above various difference thresholds can be obtained by the UE 124 from its serving cell, or can be pre-configured in the UE 124.

[0166] Sixth Embodiment (Sidelink Resource Allocation by Anchor UE When Assisting More Than One UE)

[0167] In some embodiments, one UE can act as an anchor UE for multiple other UEs. For example, Figure 1 the UE 102 can assist the UE 124 and the UE 126 in sidelink resource allocation. In some cases, the UE 102 can allocate sidelink resources to the UE 124 and the UE 126 in total. Then, the UE 124 and the UE 126 can select from the allocated sidelink resources for sidelink transmission. For example, the UE 124 and the UE 126 can be allowed to randomly select from the allocated resources. In this way, resource selection conflicts may occur between the UE 124 and the UE 126. To avoid resource selection conflicts, the UE 124 and the UE 126 can perform resource sensing before making any selection.

[0168] In some other embodiments, the UE 102 can act as an anchor UE for the UE 124 and the UE 126, and can allocate separate resources to the UE 124 and the UE 26. In this way, the UE 124 and the UE 126 can each select from the allocated resources (e.g., randomly select) without performing sensing to avoid resource selection conflicts. However, since the UE 102 may not know the resource requirements of the UE 124 and the UE 126, this separate allocation of sidelink resources for the UE 124 and the UE 126 may sometimes be over-allocated or under-allocated, resulting in a reduction in the utilization efficiency of sidelink resources.

[0169] In some other embodiments described in more detail below, the UE 102 can allocate resources to a specific assisted UE, such as the UE 124. The allocation can include a sharing indicator to indicate to the UE 124 whether the resources included in the allocation are shared with any other UE. Then, the UE 124 can determine whether to perform resource sensing before selecting resources from the allocation. For example, if the sharing indicator indicates that the allocated resources are shared with other UEs, the UE 124 may need to perform sensing before selecting resources from the allocation to avoid resource selection conflicts with other UEs. However, if the sharing indicator indicates that the resource allocation is not shared with other UEs, the UE 124 can perform random resource selection from the allocation without performing sensing.

[0170] This implementation provides flexibility in using the anchor UE 102 to assist in resource allocation for multiple UEs. For example, UE 102 can use a hybrid type of resource allocation. Specifically, UE 102 can allocate separate non-shared resources to some UEs (e.g., if UE 102 can estimate or has other means to know the approximate resource requirements of these UEs), while allocating shared resources to some other UEs. UE 102 only needs to provide allocation information to each assisted UE, and the allocation information has an indicator indicating whether the allocated resources of a specific UE are shared with any other UE. This indication can be provided at the granularity of the allocation level or the resource level. For example, UE 102 can include a single indicator applicable to the entire resource allocation of a specific assisted UE. Alternatively, UE 102 can include multiple indicators in the allocation for a specific assisted UE to indicate whether different parts of the resources in the allocation are shared with other UEs.

[0171] Figure 7 An example logical flow 700 for the anchor UE 102 to allocate sidelink resources to the assisted UE 102 while also assisting other UEs in sidelink resource allocation is shown. In step 701, UE 124 sends a resource allocation request message to the anchor UE 102. The allocation request message can be transmitted via the PC5 RRC interface or the PC5 MAC CE interface or the sidelink control information interface. The allocation request message can include at least one of the following:

[0172] · Resource allocation assistance information of UE 124,

[0173] · Sidelink information of UE 124,

[0174] · BSR of UE 124,

[0175] · Resource allocation request of UE 124.

[0176] The resource allocation assistance information can include at least one of the following:

[0177] · Traffic periodicity,

[0178] · Timing offset,

[0179] · Message size,

[0180] · Sidelink destination index,

[0181] · Sidelink quality of service (QoS) flow identifier.

[0182] The sidelink information can include at least one of the following:

[0183] · List of information on frequency points of interest,

[0184] · Destination identifier,

[0185] · Transmission broadcast type,

[0186] · Sidelink QoS information list, including at least one of QoS flow identifier or QoS profile index.

[0187] As Figure 7 shown, in step 704, UE 102 receives an allocation request message and generates resource allocation information. In step 706, UE 102 sends the resource allocation information to UE 124. In step 708, UE 124 receives the resource allocation information. The resource allocation information may include at least one of the following:

[0188] · Usable / available sidelink resource allocation,

[0189] · Unusable / unavailable sidelink resource allocation,

[0190] · Sharing indicator,

[0191] · Mode for the first UE to select the allocated resources.

[0192] Including the above sharing indicator to indicate whether the available sidelink resources allocated by UE 102 are shared with at least one other UE. If the available resources are shared, UE 124 needs to perform sensing before selecting sidelink resources from the available sidelink resources to reduce conflicts with other UEs assisted by UE 102. If the available resources are indicated as not shared, UE124 can randomly select from the available resources without performing sensing. Accordingly, the mode for selection included in the above resource allocation information may include one of a sensing mode or a random selection mode.

[0193] As Figure 7 shown in 710, UE 124 can then determine whether sensing is required based on the sharing indicator and / or selection mode in the resource allocation information received from UE 102. At step 712, UE 124 performs selection of resources for sidelink transmission, for example, randomly or after sensing.

[0194] Optionally, before step 702, UE 124 can first detect whether the CBR of the sidelink resource pool is lower than the CBR threshold. UE 124 can obtain such a CBR threshold from its serving cell or from UE 102, or such a CBR threshold can be pre-configured in UE 124.

[0195] In some other embodiments, Figure 7The process 700 can be further enhanced to include resource allocation restrictions imposed by the serving cell. Thus, some additional resource allocation information from UE 124 may be required. Such additional resource information may include, but is not limited to, the BSR of UE 124, or other resource allocation assistance information of UE 124 as described above. For example, UE 124 may send its sidelink BSR to the anchor UE 102 for further restricting sidelink resource allocation. If the current BSR is the same as the original BSR, UE 124 may need to send the priority information of the logical channel or logical channel group to the anchor UE 102, or the anchor UE 102 may directly configure the logical channel or logical channel group for UE 124. For example, the anchor UE 102 may configure the mapping between the logical channel group and the QoS level. As another example, UE 124 may configure the logical channel or logical channel group and convey the priority information of such logical channel or logical channel group to the anchor UE 102.

[0196] The logical flow of this implementation is similar to Figure 7 the logical flow 700, with some additional steps before step 702. For example, before step 702, the assisted UE 124 may first receive the configuration of the logical channel or logical channel group from the anchor UE 102. This configuration indicates the QoS information corresponding to each logical channel or logical channel group. Alternatively, UE 124 may first convey the logical channel or logical channel group information to UE 124. This information indicates the QoS information corresponding to each of the logical channels or logical channel groups. The QoS information may include, but is not limited to, for example, one or more of priority information, resource type (GBR, delay-critical GBR, or non-GBR), QoS flow identifier (QFI), QoS control information (QCI), packet delay information, or reliability information.

[0197] Seventh Embodiment (Simplified Buffer Status Report)

[0198] In some alternative implementations of the sixth embodiment, the BSR information can be simplified. For example, the anchor UE 102 may only need to report the buffer size for each packet priority (PPPP) or the buffer size for each QoS list for assisting UE 124 in sidelink resource allocation. Additionally, if the anchor UE 102 needs to assist in allocating all sidelink traffic resources for the assisted UE 124, it may also need information such as the service destination index. The above QoS list and service destination index may need to be provided to the anchor UE 102 before sidelink resource allocation.

[0199] Therefore, in Figure 7In step 702 of the logical flow 700, the allocation request message sent from UE 124 may include one or more priority information and a buffer size corresponding to the one or more priority information. Additionally or alternatively, the allocation request message may include one or more QoS information and a buffer size corresponding to the one or more QoS information. Optionally, the allocation request message may further include a service destination index. Accordingly, before Figure 7 step 702 of the logical flow 700, the assisted UE 124 may send a list of QoS profiles of the sidelink QoS flow to the anchor UE 102. The above QoS information may include one or more QoS indices for identifying a specific QoS profile in the QoS profile list. An example list of QoS profiles is shown in List 1 below and is explained in Table 1 below.

[0200] List 1

[0201]

[0202]

[0203] Table 1

[0204]

[0205]

[0206] Eighth Embodiment (Scheduling Request)

[0207] In some other alternative embodiments of the above sixth embodiment, the BSR may not be included in the allocation request message in step 702. The allocation request may be made only via a scheduling request (SR). Different scheduling request configurations may correspond to different size levels of resource allocation. The anchor UE 102 may transmit one or more SR configuration information to the assisted UE 124. The one or more SR configuration information may be used by the assisted UE 124 to request sidelink resource allocation.

[0208] The anchor UE 102 may request SR configuration information from its serving cell. For example, the serving cell may be configured with a scheduling request list. The anchor UE 102 may determine the SR configuration information for a specific assisted UE (such as UE 124).

[0209] Therefore, in these embodiments, Figure 7 the resource allocation request message in step 702 may include one or more SRs, each SR corresponding to different priority information. Each SR carries separate buffer size information.

[0210] Accordingly, before such a modification step 702, the assisted UE 124 may first receive SR configuration information, including an SR configuration list. The assisted UE 124 may select SR configuration information from the SR configuration list for configuring the assisted UE 124.

[0211] Throughout the specification and claims, except for the explicitly stated meanings, terms may have subtle meanings suggested or implied in the context. Similarly, as used herein, the phrase "in one embodiment / implementation" does not necessarily refer to the same embodiment, and the phrase "in another embodiment / implementation" as used herein does not necessarily refer to different embodiments. For example, it is intended that the claimed subject matter includes all or part of the combination of the exemplary embodiments.

[0212] Generally speaking, terms can be understood at least in part from their usage in the context. For example, as used herein, terms such as "and", "or", "and / or" can include various meanings, which can at least in part depend on the context in which these terms are used. Typically, if "or" is used to relate a list such as A, B, or C, it is intended to mean A, B, and C used in the inclusive sense here, and A, B, or C used in the exclusive sense here. Additionally, as used herein, the term "one or more" can, at least in part, depend on the context, be used to describe any feature, structure, or property in the singular sense, or can be used to describe a combination of features, structures, or properties in the plural sense. Similarly, terms such as "a", "an", or "the" can be understood to convey the usage of the singular or the plural at least in part depending on the context. Additionally, the term "based on" can be understood not necessarily to convey an exclusive set of factors, but can similarly, at least in part, depend on the context and allow the existence of additional factors that are not necessarily explicitly described.

[0213] Throughout the specification, references to features, advantages, or similar language do not imply that all features and advantages that can be achieved by the solution should or are included in any single embodiment. Instead, language referring to features and advantages is understood to mean that the specific features, advantages, or characteristics described in connection with an embodiment are included in at least one embodiment of the solution. Thus, throughout the specification, the discussion of features and advantages and similar language can, but does not necessarily, refer to the same embodiment.

[0214] In addition, the described features, advantages, and characteristics of the present solution can be combined in any suitable manner in one or more embodiments. Those of ordinary skill in the relevant art will recognize that, based on the description herein, the present solution can be practiced without one or more specific features or advantages of a particular embodiment. In other cases, additional features and advantages may be recognized in certain embodiments that may not exist in all embodiments of the present solution.

Claims

1. A method for a first user equipment (UE) to obtain an auxiliary sidelink communication resource allocation from a second UE, comprising: Send a request for sidelink communication resource allocation to the second UE; Receive sidelink communication resource allocation information sent by the second UE in response to receiving the request, the sidelink communication resource allocation information including available sidelink resource allocations; and Select resources for sidelink transmission from the available allocated resources indicated by the available sidelink resource allocations in the sidelink communication resource allocation information.

2. The method according to claim 1, wherein, The sidelink communication resource allocation information further includes at least one of the following: A sharing indicator for indicating whether the sidelink resources allocated by the second UE are shared with at least one other UE; Unavailable sidelink resource allocations; A mode for the first UE to select from the allocated resources.

3. The method according to claim 2, wherein, The method further includes: When the sharing indicator indicates that the allocated resources are shared with the at least one other UE, perform sidelink resource sensing to select from the allocated resources; and When the sharing indicator indicates that the allocated resources are not shared with the at least one other UE, randomly select resources for sidelink transmission from the allocated resources.

4. The method according to claim 2, wherein, The mode for the first UE to select from the allocated resources includes one of a sensing mode and a random selection mode.

5. The method according to claim 1, wherein, Selecting from the allocated resources indicated by the sidelink communication resource allocation information includes: Performing resource sensing before making any selection from the allocated resources.

6. The method according to claim 1, wherein, The request for sidelink communication resource allocation assistance includes at least one of the following: Resource allocation assistance information of the first UE; Sidelink information of the first UE; The buffer status report of the first UE; or A sidelink resource configuration request.

7. The method according to claim 6, wherein, The resource allocation assistance information of the first UE includes at least one of the following: Traffic periodicity; Timing offset; Message size; Sidelink destination index; Sidelink quality of service (QoS) flow identifier.

8. The method according to claim 6, wherein, The sidelink information of the first UE includes at least one of the following: A list of information on frequency points of interest; Destination identifier; Transmission broadcast type; A list of sidelink QoS information, including at least one of a QoS flow identifier and a QoS profile index.

9. The method according to claim 1, wherein, The request for sidelink communication resource allocation assistance is sent by the first UE to the second UE via the PC5 interface or the sidelink control information interface.

10. The method according to claim 1, further comprising:Before sending the request for sidelink communication resource allocation assistance to the second UE, determine that the channel busy rate of the configured sidelink resource pool is not lower than the CBR threshold.

11. The method according to claim 10, wherein, The CBR threshold is obtained from the serving cell of the first UE or from the second UE, or is pre-configured.

12. The method according to claim 1, further comprising: Before sending the request for sidelink communication resource allocation assistance to the second UE: The first UE receives from the second UE logical channel or logical channel group configuration information for indicating the mapping between QoS information and each logical channel or each logical channel group; Or The first UE sends to the second UE logical channel or logical channel group configuration information for indicating the mapping between QoS information and each logical channel or each logical channel group.

13. The method according to claim 12, wherein, The QoS information includes at least one of the following: priority information; a resource type including GBR, delay-critical GBR, or non-GBR; packet delay information; packet error rate; reliability information.

14. The method according to claim 1, wherein, The request for the sidelink communication resource allocation includes at least one of the following: one or more priority information and one or more buffer size information corresponding to the one or more priority information; or one or more QoS information and one or more buffer size information corresponding to the one or more QoS information.

15. The method according to claim 14, wherein, The request for the sidelink communication resource allocation further includes a service destination index.

16. The method according to claim 14, further comprising: Before sending the request for the sidelink communication resource allocation to the second UE, the first UE sends a list of QoS profiles of the sidelink QoS flow to the second UE.

17. The method according to claim 16, wherein, Each of the one or more QoS information includes a QoS index in the list of QoS profiles.

18. The method according to claim 1, wherein, The request for the sidelink communication resource allocation includes one or more scheduling requests corresponding to different priority information.

19. The method according to claim 18, further comprising: Before sending the request for the sidelink communication resource allocation, the first UE receives one or more scheduling request configurations from the second UE, where the one or more scheduling request configurations correspond to different priorities.

20. A method for a first user equipment UE to assist a second UE in wireless sidelink resource allocation, comprising: The first UE sends a sidelink message indicating that the first user equipment is capable of assisting another user equipment in sidelink resource allocation; The first UE receives a sidelink assistance request message; and In response to the sidelink assistance request message, the first UE sends sidelink communication resource allocation information to the second UE, and the sidelink communication resource allocation information includes available sidelink resource allocations.

21. A computer-readable medium comprising instructions that, when executed by a processor, cause the processor to execute the method according to any one of claims 1 to 20.

Images