Lateral link enhancement-resource allocation assistance information

Abstract

The invention relates to sidelink enhancement-resource allocation assistance information. Exchanging resource allocation assistance information between a requester user equipment (UE) and a secondary UE enables the requester to make better resource allocation decisions. The assistance information may include, for example, a blacklist, a whitelist, resource allocation information, a set of candidate resources, and measurement information. The two UEs may have an assistance configuration to assist in the exchange of resource allocation assistance information, which may be obtained from a third device, such as a base station. The configuration may include, for example, information related to when to trigger assistance, an identity of the UE, and a type of assistance information. The requester may modify a candidate set of resources at a medium access control (MAC) layer based on the received assistance information. The requester may use assistance information for the selected destination at the MAC layer to determine a configured sidelink grant for the destination.

Description

[0001] This application is a divisional application of the invention patent application with the application number 202180033460.2, the application date of April 8, 2021, and the title of "Sidelink Enhancement - Resource Allocation Assistance Information".

[0002] Cross - reference to related applications

[0003] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 008,244, filed on April 10, 2020, the content of which is hereby incorporated by reference in its entirety. Background Art

[0004] This disclosure relates to the management of wireless devices in cellular networks, machine - to - machine networks, and other networks such as those described in, for example, the following specifications: 3GPP TS 38.331, NR: Radio Resource Control (RRC) Protocol Specification V15.8.0; 3GPP TS 38.321, NR; Medium Access Control (MAC) Protocol Specification, V15.8.0; R2 - 2001969CR 38.321: Introduction of 5G V2X with NR Sidelink; R2 - 2001966CR 38.331: Introduction of 5G V2X with NR Sidelink; R2 - 2002264CR 38.300: Introduction of 5G V2X with NR Sidelink; and 2GPP TS 38.214NR; Physical Layer Procedures for Data, V15.8.0. Summary of the Invention

[0005] Mode 2 resource allocation is a distributed mechanism that relies on sensing to determine when a UE can transmit on the sidelink. It has many drawbacks, such as low power efficiency, unused sidelink resources, and potential sidelink traffic conflicts (e.g., caused by hidden nodes). Assistance information can be used to address these drawbacks, whereby an assisting UE provides assistance information to a requesting UE, which enables the requesting UE to make better mode 2 resource allocation decisions. Four exemplary types of assistance are proposed: blacklist, whitelist, resource allocation, and candidate resource set.

[0006] The requesting UE and the assisting UE can be configured to exchange assistance information.

[0007] The requesting UE can be configured to trigger a request for assistance. This can include a mechanism for determining which peer UEs to request assistance from and a mechanism for sending an assistance request to the assisting UE.

[0008] The assisting UE may be adapted to manage requests for assistance in a variety of ways. This includes, for example, mechanisms to restrict which UEs are allowed to request assistance, mechanisms to trigger when assistance is generated, mechanisms to generate assistance information, and mechanisms to send an assistance response to the requesting UE.

[0009] The requesting UE may use the assistance information at the PHY layer and / or at the MAC layer (depending on the type of assistance), and use the assistance information when preparing a sidelink grant for a specific destination.

[0010] For example, a UE acting as the requesting UE and using resource allocation pattern 2 may send an indication to the network that the requesting UE is capable of using the assistance information and receiving configuration information related to the assistance information. The requester may then send an assistance information request to the assisting UE, receive the requested assistance information, and use the assistance information at the MAC layer to modify the candidate resource set and generate a grant based on the modified candidate resource set.

[0011] The received assistance configuration may include a list of second UEs, triggers for sending assistance requests, etc., and may be sent from the serving cell or the assisting UE. The assistance information request may include the type of assistance (blacklist, whitelist, resource allocation, candidate resource set, and measurement), the window on which to provide assistance, etc.

[0012] The requesting UE may modify the candidate resource set by eliminating those candidate resources in the blacklist contained in the assistance information or by including those candidate resources in the whitelist contained in the assistance information.

[0013] A UE acting as the assisting UE may send an indication of its ability to the network to indicate that the assisting UE is capable of providing assistance information. The assisting UE may then receive assistance configuration information. For example, the assisting UE may use the configuration information when determining how to process the received assistance information request, generate the assistance information, and send a response to the request.

[0014] The received configuration for the assisting UE may include, for example, a list of allowed requesting UEs, the periodicity of assistance, the type of assistance information, etc. The assisting UE may verify the request based on the identity of the requesting UE, the load on the assisting UE, etc., and may generate assistance information for the response based on a blacklist of time slots, such as those determined based on the assisting UE not being able to receive on the sidelink (due to sidelink DRX, half-duplex operation, transmission on the uplink, etc.).

[0015] At the UE using resource allocation mode 2, the MAC layer may select a destination based on the logical channel with the highest priority and use the auxiliary information for that destination to determine the configured sidelink grant for that destination. The MAC layer may tag the sidelink destination to the configured sidelink grant and may use the configured sidelink grant for the tagged sidelink destination to construct a MAC PDU.

[0016] The purpose of providing this summary of the invention is to introduce selected concepts in a simplified form, which are further described in the following detailed description. This summary of the invention is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. Additionally, the claimed subject matter is not limited to limitations that solve any or all of the disadvantages noted in any part of this disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] A more detailed understanding can be obtained from the following description given by way of example in conjunction with the accompanying drawings.

[0018] Figure 1 Examples of resource allocation for in-coverage UEs and out-of-coverage UEs are shown.

[0019] Figure 2 Examples of resource allocation using auxiliary information are shown.

[0020] Figures 3A to 3E Examples of sidelink deployments are shown.

[0021] Figure 4 Examples of mode 1 / mode 2 sidelink resource allocation are shown.

[0022] Figure 5 Examples of downward selection with assistance are shown.

[0023] Figure 6 Examples of requestor UE / assistant UE interactions are shown.

[0024] Figure 7 Examples of managing whitelist assistance are shown.

[0025] Figure 8 Examples of downward selection with whitelist assistance are shown.

[0026] Figure 9 Examples of downward selection with blacklist assistance are shown.

[0027] Figure 10 Examples of managing resource allocation assistance are shown.

[0028] Figure 11AShows an example of coordination in resource selection and MAC PDU assembly.

[0029] Figure 11B Shows an example of resource sensing and allocation using auxiliary information.

[0030] Figure 12A Shows an exemplary communication system in which the methods and apparatuses described and claimed herein may be embodied.

[0031] Figure 12B Is a block diagram of an exemplary apparatus or device configured for wireless communication.

[0032] Figure 12C Is a system diagram of an exemplary radio access network (RAN) and core network.

[0033] Figure 12D Is another system diagram of an exemplary RAN and core network.

[0034] Figure 12E Is another system diagram of an exemplary RAN and core network.

[0035] Figure 12F Is a block diagram of an exemplary computing system.

[0036] Figure 12G Is a block diagram of another exemplary communication system. Detailed Description

[0037] Table 1 in Appendix 3 of the present disclosure describes some abbreviations used herein.

[0038] Sidelink Resource Allocation

[0039] Sidelink resource allocation refers to the process by which a UE determines the resources for sidelink transmission. 5GNR supports two basic modes of resource allocation. Mode 1 is network-controlled, whereby the base station schedules the sidelink resources that will be used by the UE for sidelink transmission. The UE must be in RRC_CONNECTED and the UE must be within coverage. Mode 2 is UE-autonomous, whereby the base station does not perform scheduling. The sidelink transmission resources are within the sidelink resources configured by the base station / network or pre-configured in the UE. The UE can be in the RRC_CONNECTED, RRC_IDLE, or RRC_INACTIVE state, and the UE can be within coverage or out of coverage. The resources are selected from the TX resource pool. This is in line with the resource allocation modes defined for LTE D2D and LTE V2X.

[0040] Figure 1 Shows an example of resource allocation for a UE within coverage and a UE out of coverage.

[0041] Release 17 Work Item

[0042] Release 17 has started activities to enhance mode 2 resource allocation. One of the objectives is to study the feasibility and benefits of the enhancements in mode 2 in terms of enhancing reliability and reducing latency, taking into account both the packet reception rate (PRR) and the packet reception interval (PIR), and to specify the identified solutions if deemed feasible and beneficial. PRR is a measure of reliability and is calculated by dividing the number of UEs that receive packets in range A by the number of UEs in range A. PIR is a measure of latency and is defined as the time between the consecutive successful receptions of two different packets. UE - to - UE coordination enhancement is considered to be of high priority. In UE - to - UE coordination, a resource set is determined at UE - A. This set is sent to UE - B in mode 2, and UE - B takes this into account in its resource selection for its own transmissions.

[0043] It should be noted that the standardization body does reserve the possibility of making further enhancements to resource allocation.

[0044] The solution should be able to function within coverage, in partial coverage, and outside coverage, and be able to address the problem of consecutive packet loss in all coverage scenarios.

[0045] As Figure 2 shown, the objectives of the enhanced resource allocation are: to reduce the power consumption at UE_B; to make the sidelink communication from UE_B more reliable; and to accommodate the short latency of the sidelink communication from UE_B.

[0046] Example Challenges

[0047] The proposed Release 17 enhancements to the sidelink will allow the deployment as Figures 3A to 3E shown. In Figure 3A , the UE (UE_B) is served by a serving cell and has a Uu connection to the gNB. UE_B can use either mode 1 or mode 2 resource allocation mode and can change dynamically as well as semi - statically from one resource allocation mode to another. Additionally, when in mode 2, UE_B can receive scheduling assistance from one or more assisting UE (UE_A and UE_C). Exemplary internal features of UE_A, UE_B, UE_C, and gNB are shown in Figure 3B , Figure 3C , Figure 3D and Figure 3E respectively.

[0048] The Medium Access Control (MAC) layer is responsible for data transmission on the Sidelink Scheduling Channel (SL-SCH). It has multiple sub-procedures / functions for transmission. Each of these sub-procedures / functions is described in a dedicated section (shown in brackets) of 3GPP TS 38.321, NR; Medium Access Control (MAC) Protocol Specification, V15.8.0. They are: Sidelink grant reception (5.x.1.1); TX resource (re)selection check (5.x.1.2); Sidelink HARQ operation (5.x.1.3); Sidelink multiplexing and assembly (5.x.1.4); Scheduling request (5.x.1.5); Buffer Status Report (BSR) (5.x.1.6); and Channel State Information (CSI) report (5.x.1.7).

[0049] In addition, the MAC layer has multiple sub-procedures / functions for reception: Sidelink control information reception (5.x.2.1); Sidelink HARQ operation (5.x.2.2); Sidelink disassembly and demultiplexing (5.x.2.3).

[0050] The proposed sidelink enhancements will have an impact on the legacy (Release 16) sidelink resource allocation process. Figure 4 The basic process related to UE_B is shown.

[0051] In Figure 4 signaling 1a, the RRC configures the MAC entity for sidelink operation. This includes whether the MAC entity uses resource allocation mode 1 (dynamic grant or configured grant) or resource allocation mode 2 (sense-based or random access-based). Random access-based targets an exceptional resource pool.

[0052] In signaling 1b, the RRC configures the PHY entity for sidelink operation. This includes TX resource pool configuration and mode 1 and mode 2 configurations. For the latter, the RRC may include sense configuration or random access.

[0053] In signaling 2, the PHY notifies the MAC layer when it receives DCI in a PDCCH occasion.

[0054] Sidelink grant reception determines the sidelink grant for UE_B. At the MAC layer, the transmission occasions of these sidelink grants are referred to as PSCCH / PSSCH durations.

[0055] If configured for mode 1 operation, in step 3, the sidelink grant reception determines whether the PDCCH occasion has a sidelink grant. This is determined when the destination of the DCI is the SL-RNTI or the SLCS-RNTI. The former case is for dynamic grants, and the latter case is for the configured grant type 2, i.e., activating, deactivating, or scheduling retransmissions for the configured grant transmissions.

[0056] Steps 4, 5, and 6 are for mode 2 operation.

[0057] If configured for mode 2 operation, in step 4, the transmitting UE needs to continuously evaluate which PSCCH / PSSCH durations are available for single MAC PDU transmissions, for multiple MAC PDU transmissions, and for potential retransmissions of these MAC PDUs. To achieve this, the sidelink grant reception continues to evaluate whether (re)selection of TX resources is necessary. Many triggers can inform the MAC layer that it needs to find new PSCCH / PSSCH durations. For example, if there is a reconfiguration of the Tx resource pool, there is new traffic that has no opportunity to be transmitted on the sidelink, or the PSCCH / PSSCH duration has not been used for an extended period, etc., the trigger can occur.

[0058] In signaling 5, to assist the sidelink grant reception, the MAC layer requests the PHY layer to provide a set of potential resources. These are provided by the PHY layer (either based on sensing or based on a configured exceptional resource pool). This is called the candidate resource set.

[0059] In step 6, the sidelink grant reception randomly selects from the provided set of potential resources in order to satisfy the transmission of one MAC PDU, multiple MAC PDUs, and potential retransmissions of these MAC PDUs. The selected set represents the PSCCH / PSSCH durations for transmission.

[0060] In step 7, within the PSCCH / PSSCH duration, the sidelink grant reception selects the MCS for the sidelink grant, and then sends the sidelink grant, the selected MCS, and the associated HARQ information to the sidelink HARQ entity within that PSSCH duration.

[0061] In step 8, the sidelink HARQ entity obtains the MAC PDU from the multiplexing and assembly process. At this time, logical channel prioritization (LCP) occurs. The sidelink HARQ entity also determines the sidelink control information for the MAC PDU, and then delivers the MAC PDU, the sidelink grant, and the sidelink transmission information to the associated sidelink process.

[0062] In steps 9 and 10, the sidelink procedure informs the PHY to transmit the SCI with an appropriate PSCCH / PSSCH duration and then tells the PHY to generate a transport block transmission. If HARQ is enabled, the sidelink procedure also tells the PHY to monitor the PSFCH.

[0063] Issue 1: Mode 2 Resource Allocation with Assistance

[0064] The first issue is that enhanced resource allocation is an important consideration for the automotive industry. These enhancements should be able to meet the latency and reliability requirements imposed by the usage scenarios and should operate in both in-coverage and out-of-coverage scenarios. UE_A provides resource allocation assistance to UE_B. This assistance can take various forms: sensing assistance, a list of allocated resources, a list of blacklisted resources, etc. Issue 1 needs to address many problems.

[0065] In the following, it is assumed that UE_B is configured for mode 2 resource allocation and has SL data available in one or more logical channels. It can use the assistance information to assist in mode 2 resource allocation.

[0066] Problem 1 - Resource Allocation and MAC PDU

[0067] Here, Problem 1 refers to the lack of coordination between resource selection and MAC PDU assembly. In Release 16 sidelink communication, the sidelink grant reception determines the PSCCH and PSSCH durations for sidelink traffic (step 6 in Figure 4 ). Within these PSCCH / PSSCH durations, the multiplexing / assembly function constructs the MAC PDU for transmission (step 8 in Figure 4 ). The multiplexing and assembly process selects the destination based on the logical channel with the highest priority. The PSCCH / PSSCH durations are determined without knowing the destination of the SL data as the duration is only selected during multiplexing / assembly. However, some of the assistance information in the assistance information can be for a specific destination. For example, a whitelist of time slots for a specific layer 2 destination ID. The sidelink grant reception and the multiplexing / assembly function need to take this into account according to the destination assistance information. If not, the multiplexing / assembly may create a MAC PDU that uses time slots in the whitelist for another destination.

[0068] Problem 2 - Sidelink Grant Reception

[0069] Problem 2 relates to issues related to sidelink grant reception. The assistance information is provided to help UE_B determine the transmission timing. After providing a candidate resource set for sidelink grant reception from the PHY layer, in Figure 4Select these timings in step 6 of the process. In the traditional process, the sidelink grant reception randomly selects a timing from the list provided by the PHY layer. However, in step 6, the sidelink grant reception may want to make a downward selection from the list provided by the PHY layer by using some auxiliary information. See Figure 5 The trigger for this downward selection needs to be defined. Additionally, if UE_B does not have the required auxiliary information, the MAC layer may trigger a request for this information from one or more peer UEs. There is currently no mechanism to request this auxiliary information. Additionally, UE_B may not know which peer UE to request the auxiliary from.

[0070] Problem 3 - Coordination of Assistance Information

[0071] Problem 3 relates to issues related to the coordination of auxiliary information. During the downward selection proposed in step 6 of the sidelink resource allocation process, the sidelink grant reception may use the auxiliary information to make a downward selection from the candidate resource list provided by the PHY layer. Actions associated with the downward selection operation need to be defined. These actions may depend on the type of available auxiliary information.

[0072] If the auxiliary information has a whitelist of candidate resources from a peer UE, how does the downward selection take this into account. For example, consider the candidate resources provided by the PHY layer of the UE.

[0073] If the auxiliary information has a blacklist of candidate resources from a peer UE, how does the downward selection take this into account. For example, how to avoid the candidate resources in the candidate resources provided by the PHY layer of the UE that are in the blacklist.

[0074] If the auxiliary information has a sidelink grant from a peer UE, how does the downward selection take this into account. For example, consider the candidate resources provided by the PHY layer of the UE.

[0075] If the auxiliary information has a candidate resource set result from a peer UE, how does the downward selection take this into account. For example, consider the sensing performed by the PHY layer of the UE.

[0076] In addition, the UE may have one or more multi-auxiliary information from one or more peer UEs. The sidelink grant reception must determine which auxiliary information to use, how to combine multiple auxiliary information, and how to handle conflicting auxiliary information.

[0077] Problem 4 - Assisting Party UE Functionality 。

[0078] Problem 4 relates to new functions at the assisting UE. The assisting UE may need to provide assistance to one or more other UEs. The MAC layer of these assisting UEs needs to manage requests for assistance and send responses back to the requesting UEs. Five problems need to be solved.

[0079] First, the assisting UE should be able to select the peer UE for which it provides assistance. If not, the assisting UE will have to serve all requests for assistance information. How does the assisting UE know whether to provide assistance information to a peer UE?

[0080] Second, when is a UE triggered to provide assistance information?

[0081] Third, if the assisting UE receives multiple triggers for requests for assistance information, how does it prioritize one trigger over another?

[0082] Fourth, how does the assisting UE send an assistance information response back to the requesting UE?

[0083] Fifth, actions associated with the UE that is triggered to provide assistance information need to be defined. These actions may depend on the type of assistance information requested. If the requested assistance information is a whitelist of candidate resources, the MAC layer may need to consider any configured sidelink grants and sensing information from its PHY layer.

[0084] If the requested assistance information is a blacklist of candidate resources, the MAC layer may need to consider any configured sidelink grants and sensing information from its PHY layer.

[0085] If the requested assistance information is for sidelink grant of the requesting UE, the MAC layer may need to provide a scheduler function.

[0086] If the requested assistance information is a sensing result, the MAC layer may need to coordinate sensing with the PHY layer.

[0087] Types of Assistance Information

[0088] The assisting UE may provide one or more types of assistance information to the requesting UE. Here we describe five exemplary categories / types of assistance. In the following, only these five categories of assistance information are illustrated. However, it should be understood that the solutions in the specific embodiments are applicable to other forms of assistance information. The following are five forms.

[0089] First is whitelist information. The assistance information can be in the form of a whitelist. The whitelist can represent a set of time slots or sub-channels or beams. In one option, the whitelist is a preference or recommendation of time slots / sub-channels / beams that the requesting UE should prefer during its resource allocation process. The requesting UE can continue to select time slots / sub-channels / beams from this whitelist. In another option, the whitelist is a time slot / sub-channel / beam restriction. The requesting UE should perform its resource allocation only from this set. The whitelist information can be provided over an observation window.

[0090] Second is the blacklist information. The auxiliary information can be in the form of a blacklist. The blacklist can represent a set of time slots or sub-channels or beams. The requesting UE should not transmit in the time slots or sub-channels or beams on the blacklist. The blacklist information can be provided over an observation window.

[0091] Third is the resource allocation information. The auxiliary information can be in the form of resource allocation for the requesting UE. The resource allocation information can be provided over an observation window.

[0092] Fourth is the candidate resource set information. The auxiliary information can be in the form of a candidate resource set. For example, the assisting UE can be a dedicated UE that provides candidate resource set information to other UEs without sensing capabilities. Similarly, the assisting UE can provide candidate resource set information to UEs with power limitations and that can only perform partial sensing. These assisting UEs can continuously sense the channel and determine the candidate resource set. The sensing can be performed over the entire channel, over all transmission resource pools, or only over some transmission resource pools. The candidate resource set information can be provided over an observation window, and the resources can be defined at the granularity of sub-channels.

[0093] Fifth is the measurement information. The auxiliary information can be in the form of the measured reference signal received power (RSRP) or signal-to-interference-plus-noise ratio (SINR) in a specific resource. The specific resource can be a resource in the blacklist or whitelist.

[0094] Solution to Issue 1: Mode 2 Resource Allocation with Assistance

[0095] As Figure 6 shown, there are multiple steps involved in the requesting UE using the auxiliary information. In step 1a, the requesting UE is configured with information related to the operation of using the auxiliary information. In step 1b, the assisting UE is configured with information related to the operation of using the auxiliary information. In step 2, the requesting UE monitors conditions to determine when it needs to request assistance from the assisting UE. In step 3, the assisting UE monitors conditions to determine when it needs to send assistance to the requesting UE. In step 4, the requesting UE receives the auxiliary information from the assisting UE.

[0096] Step 5: The requesting UE uses the auxiliary information in its mode 2 resource allocation.

[0097] Steps 1a / 1b: Configuration of Assistance Information

[0098] The procedures in this section address the issues identified in Problem 2 and Problem 4. The requesting UE and the assisting UE need to be configured to allow for resource allocation using the assistance.

[0099] The requesting UE can be configured through pre-configuration, configuration, signaling from the serving cell, signaling from the controlling UE, or system information. The controlling UE is the UE that provides control information to one or more sidelink UEs. It is intended for out-of-coverage scenarios, but can also be used for in-coverage scenarios. The controlling UE can be the assisting UE or another UE. The configuration can also be negotiated between the requesting UE and the assisting UE. This negotiation can occur during the establishment of the PC5-S link, the establishment of the PC5 RRC connection, the UE sidelink capability exchange, the UE sidelink configuration exchange, or a new dedicated RRC exchange between the requesting UE and the assisting UE. The configuration information can include one or more of the following six items.

[0100] The first item is whether the UE is allowed to be the requesting UE. For example, when switching to a new cell, the target gNB may decide that it does not want the UE to exchange assistance information. The UE will be configured not to request assistance information.

[0101] The second item is the list of assisting UEs. This can be a list of layer 2 IDs or application IDs.

[0102] The third item is the trigger for the assistance request. The requesting UE can be configured to request assistance information at a specific period. For example, through the assistancePeridocity parameter. The requesting UE can be configured to request the information based on a request from a higher layer. The requesting UE can be configured to request the information based on some internal trigger from the RRC, MAC layer, or PHY layer.

[0103] The fourth item is the maxCandidateResourceSet, which is the maximum size of the candidate resource set provided by the PHY layer. If the size of the candidate resource set exceeds this maximum value, the requesting UE may find out the assistance information.

[0104] The fifth item is the minCandidateResourceSet, which is the minimum size of the candidate resource set provided by the PHY layer. If the size of the candidate resource set is less than this minimum value, the requesting UE may find out the assistance information.

[0105] The sixth item is the minRequestTime, which is the minimum time interval between the transmissions of assistance requests. This can be used to guarantee a specific prohibited time after the requesting UE sends a request.

[0106] The secondary UE can be configured through (pre)-configuration, through signaling from the serving cell, through signaling from the controlling UE, or through system information. The configuration can also be negotiated between the requesting UE and the secondary UE. This negotiation can occur during the establishment of the PC5-S link, the establishment of the PC5 RRC connection, the UE-side uplink capability exchange, the UE-side uplink configuration exchange, or a new dedicated RRC exchange between the requesting UE and the secondary UE. The configuration information can include one or more of the following eight items.

[0107] The first item is whether the UE is allowed to be a secondary UE. For example, when switching to a new cell, the target gNB may decide that it does not want the UE to exchange assistance information. The UE will be configured not to send assistance information.

[0108] The second item is the list of allowed requestors. This can be a list of layer 2 IDs or application IDs. The secondary UE will only respond to assistance requests or send assistance to the UEs in this list. For each requesting UE, the configuration can include the type of assistance provided for that requestor (e.g., blacklist, whitelist, resource allocation, or candidate resource set).

[0109] The third item is the trigger for the assistance request; the secondary UE can be configured to send assistance information at a specific period. For example, through the assistancePeridocity parameter. The secondary UE can be configured to send this information based on a request from a higher layer. The secondary UE can be configured to send this information based on some internal trigger from the RRC, MAC layer, or PHY layer. For example, based on the measured RSRP, SINR, etc. The secondary UE can be configured to send assistance information when the information changes by more than a (pre)-configured increment or exceeds a (pre)-configured threshold. In such cases, the UE can be configured with this increment or threshold. The secondary UE can be configured to send assistance information semi-persistently. The UE can be configured with the details of this semi-persistence.

[0110] The fourth item is the type of requested assistance information (e.g., whitelist, blacklist, candidate resource set, resource allocation, measurement results for a resource set (such as RSRP or SINR)) and the details of the assistance information. Some details can include the threshold for triggering the monitoring and / or transmission of the assistance information, the timer related to the assistance information. For example, the secondary UE can be configured to provide assistance information for an observation window. For example, for a period of K time slots, where K is configured. In addition, how to provide the assistance information can be provided on a time slot basis or on a channel basis.

[0111] The fifth item is the details related to the assistance information to be provided. For example, the TX resource pool to be monitored.

[0112] The sixth item is any constraint imposed on the sidelink assistance information. For example, the requesting UE may have configured sidelink DRX and the requesting UE will not monitor the sidelink during these DRX time slots. As another example, the requesting UE may not be allowed simultaneous uplink transmission and sidelink transmission. Therefore, the requesting UE may provide an indication of the configured grant for its uplink transmission. As another example, the UE may be configured with measurement gaps to perform inter-frequency measurements. The requesting UE may provide an indication of this measurement gap configuration.

[0113] The seventh item, if the sidelink assistance information is a resource allocation, the configuration may further include scheduling information to assist when the assisting UE provides the resource allocation. This may include the amount of resources requested, the identity of the destination UE that will receive the sidelink transmission of the requesting UE, and any transmission restrictions of the requesting UE (e.g., time slots in which the requesting UE may not transmit).

[0114] The eighth item is a parameter for indicating whether the sidelink assistance information is broadcast for all sidelink UEs or unicast for a specific requesting UE. The assisting UE may also be configured with a broadcast address. It should be noted that this configuration may be used for all sidelink assistance information generated by this assisting UE or for a specific type of sidelink assistance information.

[0115] It should be noted that the UE may need to signal to the network its ability to act as a requesting UE or an assisting UE. It is recommended to add this ability as a new UE ability and provide it to the serving cell in a UE Capability Enquiry exchange, a new RRC message exchange, or a NAS layer message exchange. For example, this could be in a new assisting parameter IE included in the UE Capability Information message.

[0116] Step 2: Monitoring at the Requesting UE

[0117] To use the sidelink assistance information at the requesting UE during the sidelink resource allocation process, multiple sub-problems need to be solved, as identified in Problem 2.

[0118] Initially, the MAC layer may need to determine when to use the sidelink assistance information. Multiple events that trigger the use of the sidelink assistance information may occur at the requesting UE. For example, one or more of the following six triggering items for using the sidelink assistance information may occur:

[0119] First, during the sidelink grant reception process, the candidate resource set may be too large. The requesting UE may be configured with a maxCandidateResourceSet. When the PHY layer returns the candidate resource set ( Figure 4In step 5) therein, the MAC layer can determine whether the quantity is greater than maxCandidateResourceSet. If so, it can trigger the MAC layer to use the auxiliary information to reduce the set.

[0120] Second, during the sidelink grant reception procedure, the candidate resource set may be too small. The requesting UE can be configured with minCandidateResourceSet. When the PHY layer returns the candidate resource set ( Figure 4 in step 5) therein, the MAC layer can determine whether the quantity is less than minCandidateResourceSet. If so, it can trigger the MAC layer to use the auxiliary information to reduce the set.

[0121] Third, during the sidelink grant reception procedure, the PHY layer can return an indication of the threshold for determining the candidate resource set ( Figure 4 in step 5) therein. Alternatively, this can be an indication of the number of times the candidate resource set size is less than 20% of the entire selection window, and the sensing threshold must be increased. If so, it can trigger the MAC layer to use the auxiliary information to reduce the set.

[0122] Fourth, during the sidelink grant reception procedure, the PHY layer can return the candidate resource set ( Figure 4 in step 5) therein and an indication that the set is derived from an abnormal resource pool. If so, it can trigger the MAC layer to use the auxiliary information to reduce the set.

[0123] Fifth, during sidelink grant reception, the MAC layer can always use the auxiliary information for resource allocation mode 2.

[0124] Sixth, during the multiplexing and assembling process, the requesting UE has triggered the use of auxiliary information for a specific destination. This auxiliary information will be used for subsequent determination of sidelink grants.

[0125] Next, the MAC layer may need to determine when to request auxiliary information from the peer UE. Four triggering items can be used.

[0126] First, the MAC layer at the requesting UE can be triggered to use the auxiliary information to reduce the candidate resource set provided by the PHY layer ( Figure 4 in step 5) therein, and the MAC layer can have no auxiliary information. This can trigger the requesting UE to request assistance.

[0127] Second, according to a request from the upper layer: the requesting UE can receive an indication to use the auxiliary information from the upper layer. The upper layer can provide an indication of the type of information to be used and the identities of one or more assisting UE that provide the information.

[0128] Third, when establishing a PC5 RRC connection to a peer UE: the peer UE may provide an indication that it can provide assistance as part of its capability exchange. Alternatively, the peer UE may be in a (pre)-configured list of assisting UEs maintained by the requesting UE.

[0129] Fourth, the currently saved assistance information at the requesting UE may have expired or be about to expire.

[0130] Next, the requesting UE may need to determine which peer UEs to request assistance information from. The requesting UE may have a list of assisting UEs and the assistance information that each of these can provide. This list may be established through (pre)-configuration at the requesting UE. Alternatively, the requesting UE may maintain this list based on a discovery process. Alternatively, the requesting UE may maintain this list based on the capability exchange during the PC5 RRC connection establishment process. This may be done through the new assistantInfo IE in the UECapabilityInformationSidelink message. The assistantInfo IE may include information about the types of assistance that the peer UE can provide. For example: blacklist, whitelist, resource allocation, candidate resource set, and / or measurements. Based on this list, the requesting UE needs to determine which peer UE to request assistance from. The requesting UE may make this determination based on the type of assistance information. For example, the requesting UE may need only the blacklist information for a specific peer UE. In this case, the requesting UE will target only the assistance from that specific peer UE. Another example, if the requesting UE may need candidate resource set information, the requesting UE may target all peer UEs in the list of assisting UEs. If the requesting UE needs to contact a peer UE in the list of assisting UEs that does not have a PC5 RRC connection, the requesting UE may establish a PC5 RRC connection to that peer UE in order to obtain the required assistance.

[0131] For the selected assisting UE, the requesting UE may send a request for assistance information. This request may be sent via one of the following three mechanisms:

[0132] The first is via an RRC message, such as a new RRCAssistantInformationRequest message or as part of a new IE in an RRCReconfigurationSidelink message or a UECapabilityEnquirySidelink message.

[0133] The second is via a MAC CE message, such as an assistance information report request message.

[0134] The third is via a field in the sidelink control information (SCI). For example, the SCI may have an auxiliary information report field. The SCI has two levels. The level 1 SCI uses the SCI format 0-1 for scheduling the PSSCH, and the level 2 SCI uses the SCI format 0-2 for decoding the PSSCH. The auxiliary information report field may be carried at one of these two levels. For example, in the level 2 SCI format 0-2.

[0135] The request may include the following five pieces of information.

[0136] The first is the type of the requested auxiliary information. For example, blacklist, whitelist, resource allocation, candidate resource set, and / or measurements on specific resources such as RSRP or SINR.

[0137] The second is the window on which the auxiliary information is provided. The requesting UE may request the auxiliary information to be provided for a specific number of time slots. For example, the blacklist information may be provided for K consecutive time slots.

[0138] The third is the periodicity of the auxiliary information. The requesting UE may request the auxiliary information to be provided at a specific period. For example, the auxiliary information may be provided every M time slots.

[0139] The fourth is the rules or set of rules, parameters, thresholds, etc. that the assisting party wants the UE to follow and / or execute / react to when sending the auxiliary information.

[0140] The fifth is the guidance to the assisting UE. For example, the requesting UE may tell the assisting UE three things.

[0141] The first is the metric that the requesting UE wants to optimize (such as latency, reliability, both latency and reliability, power saving, or any combination thereof, etc.) and the potential requirements for these metrics.

[0142] The second is the limitation of the requesting UE. For example, the requesting UE may provide its TX resource pool.

[0143] The third is any constraint imposed on the auxiliary information. For example, the requesting UE may have a configured sidelink DRX and the requesting UE will not monitor the sidelink during these DRX time slots. Another example is that the requesting UE may not be allowed simultaneous uplink transmission and sidelink transmission. Therefore, the requesting UE may provide an indication of the configured grant for its uplink transmission. Another example is that the UE may be configured with measurement gaps to perform inter-frequency measurements. The requesting UE may provide an indication of this measurement gap configuration.

[0144] Step 3: Monitoring at the Assisting UE

[0145] To enable the assisting UE to provide assistance information, multiple sub - problems need to be solved, as identified in Problem 4. In the first sub - problem, the UE may need to determine when to monitor or evaluate the assistance information or send the assistance information to / for the requesting UE. The assisting UE can use one or more of the following seven triggers:

[0146] First, the assisting UE can send the assistance information to the requesting UE periodically or broadcast the information. The periodicity can be based on the configured assistancePeridocity parameter. When the timer expires, the assisting UE can determine the assistance information and send it to the requesting UE or broadcast the information.

[0147] Second, the assisting UE can send the assistance information semi - persistently based on the configured mode.

[0148] Third, the assisting UE can monitor one or more metrics and send the assistance information when the monitored metric changes by more than a configured threshold. For example, the assisting UE can monitor the number of blacklisted time slots since the last sending of the assistance information. If this number is higher than the (pre)configured threshold, it can trigger the assisting UE to send an update to the requesting UE.

[0149] Fourth, the assisting UE can receive a request to send the assistance information from the requesting UE. This request can be made via an RRC message (e.g., RRCReconfigurationSidelink message, RRCReconfigurationCompleteSidelink message, UECapabilityEnquirySidelink message, UECapabilityInformationSidelink message, or a new RRC message), a MAC CE, or an SCI.

[0150] Fifth, the assisting UE can receive a request to send the assistance information from the controlling UE. This request can be made via an RRC message, a MAC CE, or an SCI.

[0151] Sixth, the assisting UE can receive a request to send the assistance information from its serving cellular cell. This request can be made via an RRC message, a MAC CE, or a DCI.

[0152] Seventh, the assisting UE can receive a request to send the assistance information from its upper layer. For example, after establishing a PC5 - S connection, the upper layer can trigger the assisting UE to send the assistance information.

[0153] It should be noted that these trigger mechanisms can be combined. For example, the requesting UE can provide the periodic value via an RRC message and perform periodic transmission of the activated / deactivated assistance information via an SCI message.

[0154] In the second sub - problem, upon receiving a request, the assisting UE may need to determine whether to allow the requesting UE to request assistance. The assisting UE may be configured with an allowedRequester list. This list may be (pre) - configured, configured via signaling with the serving cell, configured via signaling with the controlling UE, configured via system information, or negotiated with peer UEs. Upon receiving a request for assistance information, the assisting UE may first check whether the requesting UE is in the allowedRequester list. If so, the assisting UE proceeds to provide the requested assistance. If not, the assisting UE may ignore the request. Alternatively, it may send a failure indication to the requesting UE so that it knows that the request has failed and no assistance is forthcoming. The request may have an associated priority and type. The assisting UE may use this to determine whether to accept or reject the request. For example, the assisting UE may assist many peer UEs. It may determine that it does not want to handle any further requests and may reject any future requests. Alternatively, upon receiving an incoming request with a high priority, the assisting UE may cancel existing requests with lower priorities.

[0155] In the third sub - problem, when the assisting UE is triggered to provide assistance, the actions taken depend on the type of assistance. Some of these actions are described below for the following five types of assistance information: blacklist, whitelist, resource allocation, and candidate resource list.

[0156] The first is the blacklist. The assisting UE may determine all time slots or sub - channels or beams from which it does not want to receive sidelink transmissions from the requesting UE or from any peer UE. These time slots and sub - channels are determined in the configured resource pool for monitoring and for the configured observation window. The assisting UE may make this decision based on load - balancing reasons. For example, the assisting UE may want to isolate traffic from certain UEs to occur only in certain time slots. Alternatively, the assisting UE may blacklist certain time slots because it will not be able to receive sidelink transmissions in these time slots. For example, the assisting UE may have sidelink DRX configured during these time slots, or the assisting UE may have measurement gaps configured during these time slots, or the assisting UE may have a configured grant for sidelink transmissions scheduled for that time slot (some UEs will have half - duplex limitations and they cannot receive and transmit on the sidelink simultaneously), or the assisting UE may have a configured grant for uplink transmissions scheduled for that time slot (some UEs will not be able to transmit on the uplink and receive on the sidelink simultaneously). Alternatively, the assisting UE may blacklist certain beams. For example, it may know that transmissions in that beam are very poor.

[0157] The second is the whitelist. The assisting UE can determine all time slots or sub-channels or beams on which it prefers to receive sidelink transmissions from the requesting UE or from any peer UE. These time slots / sub-channels / beams are determined in the configured resource pool for monitoring and for the configured observation window. The assisting UE can make this decision based on load balancing reasons. For example, the assisting UE may want to isolate traffic from certain UEs to occur only in certain time slots. Alternatively, the assisting UE can whitelist certain time slots so that it can schedule when it can enter sidelink DRX.

[0158] The third is the candidate resource set. The assisting UE can notify the PHY layer to return the candidate resource set. The assisting UE can provide the following information to the PHY layer to assist sensing: the sensing window size (if not provided, the PHY layer can use the (pre)-configured default size), the TX resource pool on which to determine the candidate resource set. The PHY layer will then return candidate resource set information, where the candidate resources are identified at the sub-channel level.

[0159] The fourth is resource allocation. The assisting UE can determine the resources to be allocated to the requesting UE based on the scheduling information provided by the requesting UE. The assisting UE can consider the amount of resources requested. The assisting UE can consider the time slots or sub-channels on which the requesting UE is not allowed to transmit. For example, during these time slots or sub-channels, the requesting UE may already have an authorization for UL transmission or sidelink transmission. The requesting UE can consider the sub-channels or time slots on which the destination UE for the sidelink transmission may not receive the sidelink transmission. For example, the requesting UE may want to send sidelink traffic to the destination UE (the destination UE can be the assisting UE or another peer UE). The assisting UE can allocate resources such that these resources are transmitted when the destination UE is receiving the sidelink transmission.

[0160] The fifth is the measurement of the selected resources (such as RSRP, SINR). The assisting UE can retrieve the measurement results from the PHY layer or the RRC layer. If these measurements have not been monitored, the assisting UE may have to configure these measurements.

[0161] In the fourth sub-question, the assisting UE must send an assistance information response to the requesting UE. This response can be sent via one of five mechanisms.

[0162] The first is via an RRC message, such as a new RRCAssistantInformationResponse message or as part of a new IE in an RRCReconfigurationSidelink message or a UECapabilityEnquirySidelink message.

[0163] The second is via a MAC CE message. For example, an auxiliary information report response message.

[0164] The third is via a field in the sidelink control information (SCI). For example, the SCI may have an auxiliary information report field.

[0165] The fourth is via the sidelink feedback channel (PSFCH).

[0166] The fifth is via the sidelink shared channel (PSSCH).

[0167] The response may include the requested auxiliary information (e.g., blacklist, whitelist, candidate resource set, resource allocation, measurement). The auxiliary information may also include a validity period. The validity period may include a start time and a duration (e.g., in terms of time slots). If the assisting UE has multiple pending response messages to send, the pending response messages may be prioritized depending on the type of the auxiliary information and / or the configuration of the auxiliary information. The auxiliary information may be sent only to the requesting UE or broadcast to all UEs. This may depend on the type of the auxiliary information. For example, the candidate resource set information may be broadcast to all UEs so that the information can be used during the sidelink authorization reception procedure at these UEs. In the case of multiple requests from multiple requesting UEs, the assisting UE may combine the auxiliary information and transmit the information together to all the requesting UEs instead of transmitting the information separately to each of the individual requesting UEs. That is, the assisting UE may multiplex multiple auxiliary information and transmit it via multicast or broadcast.

[0168] Step 4: Managing Received Assistance Information at the Requesting UE

[0169] The requesting UE may receive auxiliary information from multiple destinations. The information must be managed at the requesting UE. The information may be received via an RRC message, a MAC CE, or an SCI. The requesting UE may store the auxiliary information at the MAC layer. The following types of auxiliary information may be received: blacklist, whitelist, resource allocation, candidate resource set, measurement, etc. Each of these auxiliary information may have a validity period indicating the period during which the information is valid. The period may include a start time and a duration (e.g., based on the number of time slots). Each of these auxiliary information may also have an associated priority. The priority of the auxiliary information may take various forms.

[0170] First, the priority may be (pre)-configured in the standard. For example, the priority of the auxiliary information may always be resource allocation auxiliary information > candidate resource set auxiliary information > blacklist auxiliary information > whitelist auxiliary information.

[0171] Second, the priority may be based on the remaining lifetime of the auxiliary information. For example, if the auxiliary information is about to expire, the auxiliary information may have a higher priority.

[0172] Third, the priority can be based on the freshness of the sidelink assistance information. For example, the most recently received sidelink assistance information can be more accurate than that received many time slots ago.

[0173] Fourth, the priority can be based on the priority provided by the assisting UE.

[0174] When receiving the sidelink assistance information, the requesting UE attempts to combine the information with the sidelink assistance information already stored. For example, it can combine the candidate resource set information from multiple sidelink assistance information. If there is a conflict between the sidelink assistance information, both can be discarded. Alternatively, the one with the lower priority can be discarded.

[0175] Step 5: Using Assistance Information at the Requesting UE

[0176] Assistance Information at the MAC Layer

[0177] To solve Problem 3 related to issues involving sidelink coordination, the sidelink assistance information can be used at the MAC layer to reduce or modify the candidate resource set. The UE has a candidate resource set {Rx,y} for the selection window. The selection window duration is based on the packet delay budget for the sidelink data in the sidelink logical channel. The set {Rx,y} includes those time and frequency resources at time slot y and subchannel x. The number of subchannels in the time and frequency resources is based on the amount of frequency resources selected.

[0178] The set {Rx,y} does not include any time slots that are eliminated because the UE cannot sense the transmission of PSCCH or PSSCH as it is transmitting (either in the sidelink or on the uplink). The candidate resources removed from the selection window as a result of this half-duplex issue are represented as {Hx,y} and are called the half-duplex resource set.

[0179] Whitelist Assistance Information

[0180] The whitelist can include a set of time slots that the assisting UE informs the requesting UE that sidelink transmissions on these time slots are allowed or preferred.

[0181] The whitelist can include a resource (subchannel on a time slot) or a beam set that the assisting UE informs the requesting UE that sidelink transmissions on these resources are allowed or preferred.

[0182] The following sub-steps will be performed as part of Step 5 in Figure 4 These sub-steps are shown in Figure 7 and are described below.

[0183] Step 1: Provide a candidate resource set {Rx,y} and a half-duplex resource set {Hx,y} to the sidelink grant reception procedure.

[0184] Step 2: If the UE is configured to use sidelink assistance information and the information is available, the sidelink grant reception procedure selects the sidelink assistance information to use. This can be based on one or more of the following criteria: the destination of the logical channel with the highest priority selected randomly, the destination of the logical channel with a packet delay budget used to limit the selection window, the priority of the sidelink assistance information, etc.

[0185] Step 3a: If the sidelink assistance information is a whitelist of time slots, the sidelink grant reception procedure removes any candidate resources in the time slots in one of the time slots not in the whitelist of time slots ( Figure 8 resources marked as "a" in). The sidelink grant reception procedure may also include in the candidate resource list any resources in the half-duplex source set {Hx,y} that fall within the whitelist of time slots and that the UE has no intention of using for any transmission (no sidelink configured grant for transmission) ( Figure 8 sources marked as "b" in). The sidelink grant reception procedure then has a modified candidate resource set {R'x,y}.

[0186] Step 3b: If the sidelink assistance information is a whitelist of resources, the sidelink grant reception procedure removes any candidate resources not in the whitelist of resources. The sidelink grant reception procedure may also include in the candidate resource list any resources in the half-duplex source set {Hx,y} that fall within the whitelist of resources and that the UE has no intention of using for any transmission (no sidelink configured grant for transmission). The sidelink grant reception procedure then has a modified candidate resource set {R'x,y}.

[0187] Step 4: The sidelink grant reception procedure determines whether the number of transmission opportunities in the modified candidate resource set {R'x,y} is sufficient to satisfy the number of transmissions and optionally the number of selected HARQ retransmissions. If so, proceed to Step 5. If not, the sidelink grant reception procedure may return to Step 2 and select another sidelink assistance information to use. Alternatively, the sidelink grant reception procedure may return to the candidate resource set {Rx,y}.

[0188] Step 5: Randomly select a time resource and a frequency resource for one transmission opportunity from the modified candidate resource set {R'x,y}.

[0189] Step 6: Continue with the Release 16 procedure of the sidelink grant reception procedure.

[0190] Blacklist Assistance Information

[0191] The blacklist may include a set of time slots, and the assisting UE notifies the requesting UE that sidelink transmissions on these time slots should not be allowed.

[0192] The blacklist may include a set of resources (sub-channels on a time slot), and the assisting UE notifies the requesting UE that sidelink transmissions on these resources should not be allowed.

[0193] The following sub-steps will be performed as Figure 4 part of step 5 in Figure 7 The flowchart is similar to the flowchart shown in

[0194] Step 1: Provide the candidate resource set {Rx,y} and the half-duplex resource set {Hx,y} to the sidelink authorization reception process.

[0195] Step 2: The sidelink authorization reception process selects the assisting information to be used. This can be based on one or more of the following criteria: the destination of the logical channel with the highest priority randomly selected, the destination of the logical channel with the packet delay budget used to limit the selection window, the priority of the assisting information, etc.

[0196] Step 3a: If the assisting information is a blacklist of time slots, the sidelink authorization reception process removes any candidate resources in the time slots in the blacklist time slots ( Figure 9 the resources marked as "a" in

[0197] from the candidate resource list. The sidelink authorization reception process then has a modified candidate resource set {R'x,y}.

[0198] Step 3b: If the assisting information is a blacklist of resources, the sidelink authorization reception process removes any candidate resources in the resource blacklist from the candidate resource list. The sidelink authorization reception process then has a modified candidate resource set {R'x,y}.

[0199] Step 4: The sidelink authorization reception process determines whether the number of transmission opportunities in the modified candidate resource set {R'x,y} is sufficient to satisfy the transmission and optionally the number of selected HARQ retransmissions. If so, proceed to step 5. If not, the sidelink authorization reception process may return to step 2 and select another assisting information to use. Alternatively, the sidelink authorization reception process may return to the candidate resource set {Rx,y}.

[0199] Step 5: Randomly select the time resource and frequency resource for one transmission opportunity from the modified candidate resource set {R'x,y}.

[0200] Step 6: Continue the version 16 process of the sidelink authorization reception process.

[0201] Resource Allocation Assistance Information

[0202] Resource allocation from the assisting UE may include one or more resources that the requesting UE can use for transmission. This set can be used for transmission and any potential retransmissions.

[0203] The following sub-steps will be performed as part of step 5 in Figure 4 These sub-steps are shown in Figure 10 and described below.

[0204] Step 1: Provide the sidelink authorization reception procedure with a candidate resource set {Rx,y} and a half-duplex resource set {Hx,y}.

[0205] Step 2: The sidelink authorization reception procedure selects the assisting information to be used. This can be based on one or more of the following criteria: the destination of the logical channel with the highest priority selected randomly, the destination of the logical channel with a packet delay budget used to limit the selection window, the priority of the assisting information, etc.

[0206] Step 3a: If the assisting information is a resource allocation, the sidelink authorization reception procedure may check whether the resources in the resource allocation are part of the candidate resource set. If so, proceed to step 4. If not, proceed to step 5.

[0207] Step 4: Use the time resources and frequency resources from the resource allocation for the initial transmission. If there are additional resources in the resource allocation, use these additional resources for the selected number of HARQ retransmissions. If there are not enough additional resources in the resource allocation, randomly select the time resources and frequency resources for the additional transmission opportunities from the candidate resource set {Rx,y}. Continue at step 6.

[0208] Step 5: One or more of the resources in the resource allocation may not be part of the candidate resource set. Four options are provided.

[0209] The first is to ignore the resource allocation and randomly select the time resources and frequency resources for the transmission opportunities (initial transmission and retransmissions) from the candidate resource set {Rx,y}.

[0210] The second is to use the resources in the resource allocation that are part of the candidate resource set and ignore those resources in the resource allocation that are not part of the candidate resource set. For the transmission opportunities where there are no resources in the resource allocation, the sidelink authorization reception procedure may rely on randomly selecting the time resources and frequency resources from the candidate resource set. It should be noted that this is Figure 10 the option shown.

[0211] The third is to ignore the candidate resource set and rely on the resources from the resource allocation.

[0212] The fourth is to return to step 2 and select another piece of auxiliary information to use.

[0213] Step 6 continues with the version 16 process of the sidelink authorization reception procedure.

[0214] Candidate Resource Set Assistance Information

[0215] The assisting UE can be a special UE with sensing capabilities and no power consumption issues. For example, this can be a roadside unit (RSU) that provides a candidate resource set to nearby UEs. These nearby UEs do not need to perform their own sensing and can thus save power.

[0216] The candidate resource set auxiliary information can be in the form of a set {Ux,y} provided on subchannels (x) of a selection window and over multiple time slots (y). This set includes all subchannels within the selection window where sidelink transmissions are expected. Alternatively, this set includes all subchannels within the selection window where sidelink transmissions are not expected.

[0217] The following sub-steps will replace Figure 4 step 5 in and are performed. Assume that {Ux,y} includes all subchannels within the selection window where sidelink transmissions are expected.

[0218] Step 1: The sidelink authorization reception procedure uses the auxiliary information to determine all subchannels {Ux,y} in the selection window that are not used for sidelink transmissions. The remaining subchannels in the resource window are part of the candidate resource set.

[0219] Step 2: The sidelink authorization reception then proceeds on this candidate resource set to determine a set of contiguous subchannels that can accommodate the amount of selected frequency resources (subchannels) for this sidelink procedure. This amount was selected in the previous step as part of the R16 sidelink authorization reception procedure. This set of contiguous subchannels becomes the candidate resource set.

[0220] Step 3: Randomly select time resources and frequency resources from the candidate resource set for one transmission occasion.

[0221] Step 4: Continue with the version 16 process of the sidelink authorization reception procedure.

[0222] It should be noted that the candidate resource set auxiliary information can also be used together with other auxiliary information (blacklist, whitelist, resource allocation). In this case, the candidate resource set is not determined based on the interaction with the PHY layer as Figure 4 described in step 5 of. Instead, the candidate resource set is determined from the above steps.

[0223] It should also be noted that the candidate resource set auxiliary information can also be used by the UE that uses its own sensing to determine the candidate resource set. In this case, the UE will have two candidate resource sets, namely set 1 provided by the assisting UE and set 2 locally measured by the requesting UE. In the case of a mismatch between these two sets, the sidelink authorization reception process must determine how to handle the resources with the mismatch. There may be the following five options. The first is not to consider the resources as valid resources for the transmission occasion. The second is to consider the resources as valid resources for the transmission occasion. The third is to always follow the rules of set 1. The fourth is to always follow the rules of set 2. The fifth is to use the rules of set 2 if the auxiliary information is received less than K time slots ago.

[0224] Assistance Information at the PHY Layer

[0225] For the auxiliary information at the PHY layer, the auxiliary information is used at the PHY layer. As Figure 4 part of step 5 in, the MAC layer retrieves the candidate resource list from the PHY layer. The MAC layer provides the number of subchannels required for the authorization it attempts to determine, as well as the packet delay budget of the available sidelink data. Additionally, it is recommended that the MAC also provide auxiliary information (such as blacklist, whitelist, resource allocation, or measurement) to the PHY layer. The PHY layer can use this information to reduce sensing. For example, if the PHY layer knows that certain time slots have been blacklisted by the assisting UE, the PHY layer can avoid sensing on these time slots. Similarly, if the PHY layer knows that certain time slots / subchannels are preferred by the assisting UE, the PHY layer can target these time slots / subchannels for sensing. Similarly, if the PHY layer knows the resource allocation provided by the assisting UE, the PHY layer can perform sensing only on these target resources.

[0226] Solving Problem 1 - Lack of Coordination between Resource Selection and MAC PDU Assembly at the Requesting UE 。

[0227] Problem 1 arises for two reasons. First, the UE may have sidelink traffic in its logical channels for one or more different destinations (identified by the layer 2 ID). This is different from the Uu link where all uplink traffic targets the serving cell. Therefore, the sidelink resource allocation process has an additional step of selecting the destination. Then, the MAC PDU is constructed for this destination by selecting data from the logical channel with traffic to this single destination.

[0228] Second, the resource allocation for Release 16 sidelink allows the UE to determine the authorization for sidelink transmission and then construct the MAC PDU to be transmitted on this authorization based on the priority of the data in the logical channel. The destination of the traffic is not considered.

[0229] Problems will arise when determining the authorization based on the sidelink assistance information for a specific destination. The authorization is then intended for that specific destination, but the constructed MAC PDU may not be targeted at that destination (since it is selected based on the logical channel priority). This problem is illustrated in Figure 11.

[0230] Two solutions are proposed to solve this problem. Solution 1 relies on determining the authorization based on the destination of the MAC PDU that will satisfy the authorization. Solution 2 relies on a more reactive approach, where the authorization information includes the destination for which the authorization is allocated. Then, when the UE constructs the MAC PDU, the UE will use this information.

[0231] Solution 1: Determine the Grant for the Selected Destination

[0232] In the first solution, during the sidelink authorization reception procedure, the sidelink authorization reception can determine the destination of the logical channel with the highest priority. The UE can then evaluate whether the sidelink assistance information is for a specific destination. If so, the sidelink authorization for that destination will be determined. The destination information can be included as part of the authorization information passed to the HARQ entity. If the sidelink assistance information is not for a specific destination, the sidelink authorization will be determined independently of the destination (as in the R16 sidelink authorization reception procedure). In this case, the sidelink authorization reception procedure needs to indicate that the authorization is not bound to a specific destination. The destination can be omitted from the determined authorization, or the destination can be set to a special reserved address (e.g., FFF or the broadcast address). Alternatively, the authorization can carry a special indication flag.

[0233] When constructing the MAC PDU, the multiplexing and assembly entity will use this indication to perform destination selection for the sidelink authorization before MAC PDU assembly.

[0234] It should be noted that the concept of binding the authorization to a specific destination can be extended to sidelink dynamic authorization and sidelink configured authorization types 1 and 2. In this case, the gNB can provide the target destination in the DCI authorization signaling. The sidelink authorization reception procedure can then bind the dynamic authorization, the configured authorization type 1, or the configured authorization type 2 to the provided destination, and include the destination as part of the authorization information passed to the HARQ entity. If the gNB does not provide the target destination in the DCI authorization signaling, the sidelink authorization reception procedure can use one of the mechanisms already described to indicate that the authorization information is not bound to a destination. When constructing the MAC PDU, the multiplexing and assembly entity will use this indication to perform destination selection for the sidelink authorization before MAC PDU assembly.

[0235] The procedures for determining sidelink authorization (sidelink authorization reception) and MAC PDU assembly (multiplexing and assembly) are shown in Appendix 1 of this disclosure. New functions are shown underlined, while removed old functions are shown struck through.

[0236] Solution 2: Construct the PDU for the Destination Linked to the Grant

[0237] A second solution is to build the PDU for the destination linked to the authorization. In this solution, the destination is not selected before determining the sidelink authorization. However, if the sidelink authorization reception uses destination-specific auxiliary information when determining the sidelink authorization, it links that destination to the configured sidelink authorization. At MAC PDU assembly, the UE can use this linked destination to build the MAC PDU. However, this has the drawback that the MAC PDU may not contain sidelink data from the logical channel with the highest priority. Alternatively, multiplexing and assembly can build the MAC PDU as in the legacy R16 procedure. It will select the destination based on priority and then select the logical channel from which the MAC PDU will be built. If the destination selected by the multiplexing and assembly procedure matches the destination of the sidelink authorization, the MAC PDU can be built as in the legacy R16 system. If the destination selected by the multiplexing and assembly procedure does not match the destination of the sidelink authorization, the UE can ignore the selected destination and use the destination linked to the authorization. In this case, the multiplexing and assembly procedure can trigger the sidelink authorization reception procedure to use the auxiliary information for the selected destination. Thus, for subsequent authorization determination, the sidelink authorization is determined based on the auxiliary information for the destination of the logical channel with the highest priority.

[0238] Alternatively, the UE can use the selected destination, build the MAC PDU for the selected destination, but use a reduced MCS for this PDU. This is to compensate for the fact that the sidelink authorization is determined based on auxiliary information for different destinations.

[0239] The procedures for determining sidelink authorization (sidelink authorization reception) and MAC PDU assembly (multiplexing and assembly) are shown in Appendix 2 of this disclosure. New functions are shown underlined, while removed old functions are shown struck through.

[0240] Using Assistance Information for Resource Sensing and Selection

[0241] As Figure 11BAs shown in the example of , the transmitting UE can receive different types of auxiliary information from the RSU, group leader or nearby leader, scheduling UE, receiving UE (e.g., Rx UE i and Rx UE j), and other nearby UEs, such as a sensing list, candidate resource list, scheduling with reserved resources, HARQ feedback, RSRP, CSI, and / or measurement reports of CBR, etc., where nearby is based on the communication range of different services or QoS requirements for which UEs can communicate with each other on the sidelink.

[0242] The sensing list may contain five items of information. The first item is the sidelink bandwidth part (SL BWP) ID. The second item is the resource pool ID. The third item is the region ID.

[0243] The fourth item is a list of resources reserved and / or available in time (e.g., time slot), in frequency (e.g., PRB or subchannel), and in space (e.g., beam index or ID / transmit and receive point (TRP) index or ID / sidelink reference signal resource pool index, sidelink demodulation reference signal (SL DMRS) port, sidelink QCL quasi-co-location (SL QCL), or sidelink transmission configuration indication (SL TCI), etc.); and

[0244] The fifth item is the associated sidelink measurement, such as sidelink RSSI (sidelink received signal strength indicator) / sidelink RSRP (sidelink reference signal received power) / sidelink RSRQ (sidelink reference signal received quality) / sidelink CSI (sidelink channel state information) / sidelink CBR (sidelink channel busy ratio) measurement, etc.

[0245] The candidate resource list may contain the following information items: sidelink bandwidth part ID; resource pool ID; region ID; a list of candidate resources in time (e.g., time slot), in frequency (e.g., PRB or subchannel), and in space (e.g., beam index or ID / TRP index or ID / sidelink reference signal resource pool index, SL DMRS port, SL QCL, or SL TCI, etc.); and the associated sidelink measurement, such as SL RSSI, SL RSRP, SL RSRQ, SL CSI, SL CBR, etc.

[0246] The configured or scheduled resources may contain the following information items: sidelink bandwidth part ID; resource pool ID; region ID; and resources in time (e.g., time slot), in frequency (e.g., PRB or subchannel), and in space (e.g., beam index or ID / TRP index or ID / sidelink reference signal resource pool index, SL DMRS port, SL QCL, or SL TCI, etc.).

[0247] The HARQ or measurement may include the following information items: sidelink bandwidth part ID; resource pool ID; region ID or location; sidelink ACK / NACK feedback; and sidelink measurements such as SL RSSI, SL RSRP, SL RSRQ, SL CSI, SLCBR, etc.

[0248] The auxiliary information may be transmitted on the sidelink (e.g., PC5 interface) via at least one of the following four message transmission or signaling mechanisms.

[0249] The first is the sidelink system information carried on the NR PSBCH (New Radio Physical Sidelink Broadcast Channel), such as the sidelink master information block (SL MIB), e.g., those for the sensing list; or the sidelink system information carried on the NR PSSCH (New Radio Physical Sidelink Shared Channel), such as the sidelink system information block (SL SIB) broadcast via the common search space or multicast via the group search space or unicast via the UE search space, which may be performed periodically or aperiodically according to, for example, the request or demand of the UE for the sensing list.

[0250] The second is the sidelink RRC message carried on the NR PSSCH, which may be broadcast via the common search space or multicast via the group search space or unicast via the UE search space. The broadcast may be periodic or aperiodic, or according to the request or demand of the UE, such as for measurements of the sensing list, candidate resource list, configured resources, SL RSSI, SL RSRP, SLRSRQ, SL CSI, or SL CBR, etc.

[0251] The third is the MAC CE carried on the NR PSSCH, which may be broadcast via the common search space or multicast via the group search space or unicast via the UE search space. The broadcast may be periodic or aperiodic, or according to the request or demand of the UE, such as for activating / deactivating the sensing list, activating / deactivating the semi-persistent candidate resource list, activating / deactivating the semi-persistent scheduling resources, SL RSSI, SL RSRP, SL RSRQ, SL CSI, or SL CBR measurements, etc.

[0252] The fourth is the sidelink physical layer (PHY) signaling carried on the NR PSCCH (New Radio Physical Sidelink Control Channel) and / or PSSCH, which may be broadcast via the common search space or multicast via the group search space or unicast via the UE search space. The broadcast may be periodic or aperiodic (e.g., triggered by the UE), or according to the request or demand of the UE, such as for one or more of the following purposes.

[0253] The first purpose is the update of the sensing list of SL BWP ID, resource pool ID or region ID, such as a bitmap with time slots, where the time slots indicate the available resources corresponding in time to the associated subchannels and space (e.g., beam index or ID / TRP index or ID / sidelink reference signal resource pool index, SL DMRS port, SL QCL or SL TCI, etc.); or the index points of a resource sensing table with time, frequency and space (e.g., beam index or ID / TRP index or ID / sidelink reference signal resource pool index, SL DMRS port, SL QCL or SL TCI, etc.).

[0254] The second purpose is the update of the candidate resource list of SL BWP ID, resource pool ID or region ID, such as a bitmap with time slots, where the time slots indicate the candidate resources corresponding in time to the associated subchannels and space (e.g., beam index or ID / TRP index or ID / sidelink reference signal resource pool index, SL DMRS port, SL QCL or SL TCI, etc.); or the index points of a candidate resource table with time, frequency and space (e.g., beam index or ID / TRP index or ID / sidelink reference signal resource pool index, SL DMRS port, SL QCL or SL TCI, etc.).

[0255] The third purpose is the dynamic scheduling resources of SL BWP ID, resource pool ID or region ID indicated by NR PSCCH in the common search space or group search space or UE search space, such as a bitmap with time slots, where the time slots indicate the scheduling resources corresponding in time to the associated subchannels and space (e.g., beam index or ID / TRP index or ID / sidelink reference signal resource pool index, SL DMRS port, SL QCL or SL TCI, etc.); or the index points of a resource table with time, frequency and space (e.g., with start time and time length) (e.g., beam index or ID / TRP index or ID / sidelink reference signal resource pool index, SL DMRS port, SL QCL or SL TCI, etc.).

[0256] The fourth purpose is the SL RSSI, SL RSRP, SL RSRQ, SL CSI or SL CBR measurements carried on NR PSSCH or NR PSFCH (Physical Sidelink Feedback Channel).

[0257] For resource sensing and selection for PSSCH / PSCCH transmission, the higher layer may provide the following seven parameters to the physical layer (e.g., PHY). The first is the sidelink BWP, the second is the resource pool, and the third is the auxiliary information configuration for each resource pool of the sidelink BWP. The fourth is the L1 priority prio for each resource pool of the sidelink BWPTX , and the fifth is the remaining packet delay budget for each resource pool of the sidelink BWP.

[0258] The sixth is the number of subchannels for PSSCH / PSCCH transmission in each resource pool of the sidelink BWP, and the seventh is the resource reservation interval P in milliseconds for each resource pool of the sidelink BWP subCH . rsvp_TX .

[0259] For example, the resource reservation interval is optional.

[0260] If the resource reservation interval P rsvp_TX is provided, it will be converted from milliseconds to logical slot units, resulting in P′ rsvp\_TX . The symbol denotes the set of time slots of the sidelink resource pool that can belong to the sidelink BWP.

[0261] The following steps are used for resource sensing and selection using the auxiliary information:

[0262] In the first step, the candidate single-slot resources R for transmission in the resource pool with the SL BWP x,y are initially defined according to each higher-layer configuration, and it can be initiated using auxiliary information such as a sensing list and / or a candidate resource list.

[0263] In the second step, the sensing window is defined according to the higher-layer configuration. The transmitting UE can use the auxiliary information in these time slots to perform the following steps.

[0264] In the third step, the internal threshold parameter Th(p i ) is set from the higher layer.

[0265] In the fourth step, the set S A is initialized to the set of all candidate single-slot resources for the resource pool with the SL BWP.

[0266] In the fifth step, if in addition to the existing Release 16 exclusion conditions, the UE also meets the following conditions, it shall exclude any candidate single-slot resource R A from the set S x,y : For any periodicity indicated in the auxiliary information, such as reserved or configured resources, or such resources where the SL measurement value is higher than the configured threshold Th(Assit i ) or the number of NACKs Th(NACK) or the number of missed HARQ feedbacks Th(MissHARQ).

[0267] In the sixth step, if the UE meets the following conditions in addition to the existing version 16 exclusion conditions, it shall exclude any candidate single-slot resource R from the set S A : For any auxiliary information dynamically indicated using SCI, such as reserved or configured resources, or such resources where the SL measurement value is higher than the configured threshold Th(Assit x,y ) or the number of NACKs Th(NACK) or the number of missing HARQ feedbacks Th(MissHARQ). i

[0268] In the seventh step, if the number of remaining candidate single-slot resources in the set S A is less than 0.2·M total , then for each priority value Th(p i ), Th(p i ) is increased by 3 dB, and the process continues with step 4.

[0269] The UE shall report to the higher layer the set S of the resource pool for the SL BWP A .

[0270] Example Environment

[0271] The 3rd Generation Partnership Project (3GPP) has developed technical standards for cellular telecommunications network technologies, including radio access, core transport networks, and service capabilities, including research on codecs, security, and quality of service. The most recent radio access technology (RAT) standards include WCDMA (commonly known as 3G), LTE (commonly known as 4G), and LTE Advanced standards. 3GPP has started working on the standardization of the next-generation cellular technology called New Radio (NR) (also known as "5G"). It is expected that the development of the 3GPP NR standard will include the definition of the next-generation radio access technology (new RAT), which is expected to include new flexible radio access below 6 GHz and new ultra-mobile broadband radio access above 6 GHz. This flexible radio access is expected to include new non-backward-compatible radio access in new spectra below 6 GHz and is expected to include different operating modes that can be multiplexed together in the same spectrum to address a wide range of 3GPP NR use cases with different requirements. The ultra-mobile broadband is expected to include centimeter-wave and millimeter-wave spectra, which will provide opportunities for ultra-mobile broadband access for, e.g., indoor applications and hotspots. Specifically, the ultra-mobile broadband is expected to share a common design framework with the flexible radio access below 6 GHz while having centimeter-wave and millimeter-wave specific design optimizations.

[0272] ​3GPP has identified a variety of use cases that NR is expected to support, resulting in a wide variety of user experience requirements for data rate, latency, and mobility. The use cases include the following general categories: enhanced mobile broadband (e.g., broadband access in dense areas, indoor ultra-high broadband access, broadband access in congested areas, 50+ Mbps everywhere, ultra-low-cost broadband access, mobile broadband in vehicles); critical communications; massive machine type communications; network operations (e.g., network slicing, routing, handover and interworking, energy saving); and enhanced vehicle-to-everything (eV2X) communications, which may include any one of vehicle-to-vehicle communication (V2V), vehicle-to-infrastructure communication (V2I), vehicle-to-network communication (V2N), vehicle-to-pedestrian communication (V2P), and vehicle communication with other entities. Specific services and applications in these categories include, for example: surveillance and sensor networks, device remote control, two-way remote control, personal cloud computing, video streaming, cloud-based wireless office, first responder connectivity, automotive eCall, disaster alerts, real-time gaming, multi-person video calls, autonomous driving, augmented reality, tactile Internet, and virtual reality, etc. All of these use cases and other use cases are considered herein.

[0273] Figure 12A An embodiment of an exemplary communication system 100 is shown in which the methods and apparatuses described and claimed herein may be embodied in particular. As shown, the exemplary communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, 102e, 102f, and / or 102g (which may generally or collectively be referred to as WTRU 102), radio access networks (RANs) 103 / 104 / 105 / 103b / 104b / 105b, core networks 106 / 107 / 109, public switched telephone network (PSTN) 108, Internet 110, other networks 112, and a V2X server (or ProSe function and server) 113, but it should be understood that the disclosed embodiments of the present invention contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d, 102e, 102f, 102g may be any type of device or apparatus configured to operate and / or communicate in a wireless environment. Although each of the WTRUs 102a, 102b, 102c, 102d, 102e, 102f, 102g is in Figures 12A to 12Eis depicted as a handheld wireless communication device, but it should be understood that in the case of the diverse use cases envisioned for 5G wireless communication, each WTRU may include or may be embodied as any type of device or equipment configured to transmit and / or receive wireless signals, including by way of example only, user equipment (UE), mobile station, fixed or mobile subscriber unit, pager, cellular phone, personal digital assistant (PDA), smart phone, laptop computer, tablet computer, netbook, notebook computer, personal computer, wireless sensor, consumer electronic device, wearable device (such as a smart watch or smart clothing), medical device or e-health device, robot, industrial equipment, drone, vehicle (such as a car, truck, train or airplane, etc.).

[0274] The communication system 100 may also include base stations 114a and 114b. Base station 114a may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c to facilitate access to one or more communication networks, such as core networks 106 / 107 / 109, the Internet 110, and / or other networks 112. Base station 114b may be any type of device configured to wired and / or wirelessly interface with at least one of the RRHs (remote radio heads) 118a, 118b, TRPs (transmit and receive points) 119a, 119b, and / or RSUs (road side units) 120a and 120b to facilitate access to one or more communication networks, such as core networks 106 / 107 / 109, the Internet 110, other networks 112, and / or the V2X server (or ProSe function and server) 113. The RRHs 118a, 118b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102c to facilitate access to one or more communication networks, such as core networks 106 / 107 / 109, the Internet 110, and / or other networks 112. The TRPs 119a, 119b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102d to facilitate access to one or more communication networks, such as core networks 106 / 107 / 109, the Internet 110, and / or other networks 112. The RSUs 120a and 120b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102e or 102f to facilitate access to one or more communication networks, such as core networks 106 / 107 / 109, the Internet 110, other networks 112, and / or the V2X server (or ProSe function and server) 113. By way of example, the base stations 114a, 114b may be transceiver base stations (BTSs), Node Bs, evolved Node Bs, Home Node Bs, Home evolved Node Bs, site controllers, access points (APs), wireless routers, and so on. Although the base stations 114a, 114b are each depicted as a single element, it should be understood that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

[0275] Base station 114a may be part of RAN 103 / 104 / 105, which may also include other base stations and / or network elements (not shown), such as base station controllers (BSCs), radio network controllers (RNCs), relay nodes, etc. Base station 114b may be part of RAN 103b / 104b / 105b, which may also include other base stations and / or network elements (not shown), such as base station controllers (BSCs), radio network controllers (RNCs), relay nodes, etc. Base station 114a may be configured to transmit and / or receive wireless signals within a specific geographic area, which may be referred to as a cell (not shown). Base station 114b may be configured to transmit and / or receive wired signals and / or wireless signals within a specific geographic area, which may be referred to as a cell (not shown). A cell may be further divided into cell sectors. For example, the cell associated with base station 114a may be divided into three sectors. Thus, in one embodiment, base station 114a may include three transceivers, for example, one transceiver for each sector of the cell. In one embodiment, base station 114a may employ multiple-input multiple-output (MIMO) technology and thus may utilize multiple transceivers for each sector of the cell.

[0276] Base station 114a may communicate with one or more of WTRUs 102a, 102b, 102c via air interfaces 115 / 116 / 117, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.). Any suitable radio access technology (RAT) may be used to establish air interfaces 115 / 116 / 117.

[0277] Base station 114b may communicate with one or more of RRHs 118a, 118b, TRPs 119a, 119b, and / or RSUs 120a and 120b via wired or air interfaces 115b / 116b / 117b, which may be any suitable wired communication link (e.g., cable, fiber optic, etc.) or wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.). Any suitable radio access technology (RAT) may be used to establish air interfaces 115b / 116b / 117b.

[0278] RRH 118a, 118b, TRP 119a, 119b, and / or RSU 120a, 120b may communicate with one or more of WTRU 102c, 102d, 102e, 102f via air interface 115c / 116c / 117c, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.). Any suitable radio access technology (RAT) may be used to establish air interface 115c / 116c / 117c.

[0279] WTRU 102a, 102b, 102c, 102d, 102e, 102f, and / or 102g may communicate with each other via air interface 115d / 116d / 117d (not shown in the figures), which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.). Any suitable radio access technology (RAT) may be used to establish air interface 115d / 116d / 117d.

[0280] More specifically, as noted above, communication system 100 may be a multi-access system and may employ one or more channel access schemes such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, base station 114a in RAN 103 / 104 / 105 and WTRU 102a, 102b, 102c or RRH 118a, 118b, TRP 119a, 119b, and RSU 120a, 120b and WTRU 102c, 102d, 102e, 102f in RAN 103b / 104b / 105b may implement radio technologies such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may use Wideband CDMA (WCDMA) to establish air interfaces 115 / 116 / 117 or 115c / 116c / 117c, respectively. WCDMA may include communication protocols such as High Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High Speed Downlink Packet Access (HSDPA) and / or High Speed Uplink Packet Access (HSUPA).

[0281] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c in the RANs 103b / 104b / 105b or the RRHs 118a, 118b, the TRPs 119a, 119b and / or the RSUs 120a, 120b, and the WTRUs 102c, 102d may implement radio technologies such as evolved UMTS terrestrial radio access (E-UTRA), which may use Long Term Evolution (LTE) and / or LTE-Advanced (LTE-A) to establish the air interfaces 115 / 116 / 117 or 115c / 116c / 117c, respectively. In the future, the air interfaces 115 / 116 / 117 may implement 3GPP NR technologies. LTE and LTE-A technologies include LTE D2D and V2X technologies and interfaces (such as sidelink communication, etc.). 3GPP NR technologies include NR V2X technologies and interfaces (such as sidelink communication, etc.).

[0282] In one embodiment, the base station 114a in the RANs 103 / 104 / 105 and the WTRUs 102a, 102b, 102c in the RANs 103b / 104b / 105b or the RRHs 118a, 118b, the TRPs 119a, 119b and / or the RSUs 120a, 120b, and the WTRUs 102c, 102d, 102e, 102f may implement radio technologies such as IEEE 802.16 (e.g., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rates for GSM Evolution (EDGE), GSM EDGE (GERAN), etc.

[0283] Figure 12AThe base station 114c therein can be, for example, a wireless router, a home Node B, a home evolved Node B, or an access point, and can utilize any suitable RAT to facilitate wireless connectivity in a local area such as a business premise, a home, a vehicle, a campus, etc. In one embodiment, the base station 114c and the WTRU 102e can implement a radio technology (such as IEEE 802.11) to establish a wireless local area network (WLAN). In one embodiment, the base station 114c and the WTRU 102d can implement a radio technology (such as IEEE 802.15) to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114c and the WTRU 102e can utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.) to establish a pico cell or a femto cell. As Figure 12A shown, the base station 114b can have a direct connection to the Internet 110. Thus, the base station 114c may not need to access the Internet 110 via the core network 106 / 107 / 109.

[0284] The RAN 103 / 104 / 105 and / or the RAN 103b / 104b / 105b can communicate with the core network 106 / 107 / 109, which can be any type of network configured to provide voice, data, applications, and / or Internet protocol voice (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. For example, the core network 106 / 107 / 109 can provide call control, billing services, location-based mobile services, prepaid calls, Internet connectivity, video distribution, etc., and / or perform advanced security functions such as user authentication.

[0285] Although not shown in Figure 12A it should be understood that the RAN 103 / 104 / 105 and / or the RAN 103b / 104b / 105b and / or the core network 106 / 107 / 109 can communicate directly or indirectly with other RANs that employ the same RAT or a different RAT as the RAN 103 / 104 / 105 and / or the RAN 103b / 104b / 105b. For example, in addition to being connected to the RAN 103 / 104 / 105 and / or the RAN 103b / 104b / 105b that may be utilizing E-UTRA radio technology, the core network 106 / 107 / 109 can also communicate with another RAN (not shown) that employs GSM radio technology.

[0286] The core networks 106 / 107 / 109 may also act as gateways for the WTRUs 102a, 102b, 102c, 102d, 102e to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may include a circuit-switched telephone network that provides plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols such as the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and the Internet Protocol (IP) in the TCP / IP Internet protocol suite. The network 112 may include a wired or wireless communication network owned and / or operated by another service provider. For example, the network 112 may include another core network connected to one or more RANs, which may employ the same or a different radio access technology (RAT) as the RANs 103 / 104 / 105 and / or the RANs 103b / 104b / 105b.

[0287] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication system 100 may include multi-mode capabilities. For example, the WTRUs 102a, 102b, 102c, 102d, and 102e may include multiple transceivers for communicating with different wireless networks over different wireless links. For example, Figure 12A the illustrated WTRU 102e may be configured to communicate with a base station 114a that may employ a cellular-based radio technology and with a base station 114c that may employ an IEEE 802 radio technology.

[0288] Figure 12B is a block diagram of an exemplary apparatus or device (such as, for example, a WTRU 102) configured for wireless communication according to an embodiment shown herein. As Figure 12B shown, the exemplary WTRU 102 may include a processor 118, a transceiver 120, transmit / receive elements 122, a speaker / microphone 124, a keypad 126, a display / touchpad / indicator 128, a non-removable memory 130, a removable memory 132, a power supply 134, a Global Positioning System (GPS) chipset 136, and other peripheral devices 138. It should be understood that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with the embodiments. Additionally, the embodiments contemplate that the base stations 114a and 114b and / or the nodes that the base stations 114a and 114b may represent (such as, but not limited to, a transceiver station (BTS), a Node B, a site controller, an access point (AP), a home Node B, an evolved home Node B (eNodeB), a home evolved Node B (HeNB), a home evolved Node B gateway, and a proxy node, etc.) may include Figure 12B some or all of the elements depicted in and as described herein.

[0289] The processor 118 can be a general-purpose processor, a dedicated processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 118 can perform signal encoding, data processing, power control, input / output processing, and / or any other functions that enable the WTRU 102 to operate in a wireless environment. The processor 118 can be coupled to a transceiver 120, which can be coupled to a transmit / receive element 122. Although Figure 12B the processor 118 and the transceiver 120 are depicted as separate components, it should be understood that the processor 118 and the transceiver 120 can be integrated together in an electronic package or chip.

[0290] The transmit / receive element 122 can be configured to transmit signals to or receive signals from a base station (e.g., base station 114a) via an air interface 115 / 116 / 117. For example, in one embodiment, the transmit / receive element 122 can be an antenna configured to transmit and / or receive RF signals. In one embodiment, the transmit / receive element 122 can be a transmitter / detector configured to transmit and / or receive, for example, IR, UV, or visible light signals. In yet another embodiment, the transmit / receive element 122 can be configured to transmit and receive both RF signals and optical signals. It should be understood that the transmit / receive element 122 can be configured to transmit and / or receive any combination of wireless signals.

[0291] In addition, although the transmit / receive element 122 is depicted as a single element in Figure 12B the WTRU 102 can include any number of transmit / receive elements 122. More specifically, the WTRU 102 can employ MIMO technology. Thus, in one embodiment, the WTRU 102 can include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals via an air interface 115 / 116 / 117.

[0292] The transceiver 120 can be configured to modulate the signals to be transmitted by the transmit / receive element 122 and demodulate the signals received by the transmit / receive element 122. As noted above, the WTRU 102 can have multi-mode capabilities. For example, thus, the transceiver 120 can include multiple transceivers in order to enable the WTRU 102 to communicate via multiple RATs (such as UTRA and IEEE 802.11).

[0293] The processor 118 of the WTRU 102 can be coupled to a speaker / microphone 124, a keypad 126, and / or a display / touchpad / indicator 128 (e.g., a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit), and can receive user input data from the foregoing components. The processor 118 can also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad / indicator 128. In addition, the processor 118 can access information from any type of suitable memory (such as non-removable memory 130 and / or removable memory 132), and store data in any type of suitable memory. The non-removable memory 130 can include random access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 can include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, etc. In one embodiment, the processor 118 can access information from a memory that is not physically located on the WTRU 102 (such as on a server or a home computer (not shown)), and store data in that memory.

[0294] The processor 118 can receive power from a power source 134, and can be configured to distribute and / or control power to other components in the WTRU 102. The power source 134 can be any suitable device for powering the WTRU 102. For example, the power source 134 can include one or more dry cell batteries, a solar cell, a fuel cell, etc.

[0295] The processor 118 can also be coupled to a GPS chipset 136, which can be configured to provide location information (e.g., longitude and latitude) about the current location of the WTRU 102. In addition to or instead of information from the GPS chipset 136, the WTRU 102 can receive location information from a base station (e.g., base stations 114a, 114b) via an air interface 115 / 116 / 117 and / or determine its location based on the timing of signals received from two or more nearby base stations. It should be understood that the WTRU 102 can obtain location information by any suitable location determination method while remaining consistent with the embodiments.

[0296] The processor 118 may also be coupled to other peripheral devices 138, which may include one or more software modules and / or hardware modules that provide additional features, functionality, and / or wired or wireless connectivity. For example, the peripheral device 138 may include various sensors, such as an accelerometer, a biometric (e.g., fingerprint) sensor, an electronic compass, a satellite transceiver, a digital camera (for photos or videos), a universal serial bus (USB) port or other interconnect interface, a vibration device, a television transceiver, a hands-free headset, modules, a frequency modulation (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, and the like.

[0297] The WTRU 102 may be embodied in other devices or equipment, such as sensors, consumer electronic devices, wearable devices (such as smart watches or smart clothing), medical or e-health devices, robots, industrial equipment, drones, vehicles (such as cars, trucks, trains, or airplanes). The WTRU 102 may be connected to other components, modules, or systems of such devices or equipment via one or more interconnect interfaces, such as an interconnect interface that may include one of the peripheral devices 138.

[0298] Figure 12C is a system diagram of the RAN 103 and the core network 106 according to one embodiment. As described above, the RAN 103 may employ UTRA radio technology to communicate with the WTRU 102a, 102b, and 102c via the air interface 115. The RAN 103 may also communicate with the core network 106. As Figure 12C shown, the RAN 103 may include Node Bs 140a, 140b, 140c, each of which may include one or more transceivers for communicating with the WTRU 102a, 102b, 102c via the air interface 115. The Node Bs 140a, 140b, 140c may each be associated with a specific cell (not shown) within the RAN 103. The RAN 103 may also include RNCs 142a, 142b. It should be understood that the RAN 103 may include any number of Node Bs and RNCs while remaining consistent with the embodiment.

[0299] As Figure 12CAs shown, Node Bs 140a, 140b can communicate with RNC 142a. In addition, Node B 140c can communicate with RNC 142b. Node Bs 140a, 140b, 140c can communicate with the corresponding RNCs 142a, 142b via the Iub interface. RNCs 142a, 142b can communicate with each other via the Iur interface. Each of RNCs 142a, 142b can be configured to control the corresponding Node Bs 140a, 140b, 140c to which it is connected. In addition, each of RNCs 142a, 142b can be configured to perform or support other functions, such as outer loop power control, load control, admission control, packet scheduling, handover control, macro diversity, security functions, data encryption, etc.

[0300] Figure 12C The core network 106 shown in [Figure] can include a media gateway (MGW) 144, a mobile switching center (MSC) 146, a serving GPRS support node (SGSN) 148, and / or a gateway GPRS support node (GGSN) 150. Although each of the foregoing elements is depicted as part of the core network 106, it should be understood that any of these elements can be owned and / or operated by an entity other than the core network operator.

[0301] The RNC 142a in the RAN 103 can be connected to the MSC 146 in the core network 106 via the IuCS interface. The MSC 146 can be connected to the MGW 144. The MSC 146 and the MGW 144 can provide the WTRUs 102a, 102b, 102c with access to a circuit-switched network (such as the PSTN 108) to facilitate communication between the WTRUs 102a, 102b, 102c and traditional landline communication devices.

[0302] The RNC 142a in the RAN 103 can also be connected to the SGSN 148 in the core network 106 via the IuPS interface. The SGSN 148 can be connected to the GGSN 150. The SGSN 148 and the GGSN 150 can provide the WTRUs 102a, 102b, 102c with access to a packet-switched network (such as the Internet 110) to facilitate communication between the WTRUs 102a, 102b, 102c and IP-enabled devices.

[0303] As described above, the core network 106 can also be connected to a network 112, which can include other wired or wireless networks owned and / or operated by other service providers.

[0304] Figure 12DSystem diagram of RAN 104 and core network 107 according to one embodiment. As described above, RAN 104 can communicate with WTRUs 102a, 102b, and 102c via air interface 116 using E-UTRA radio technology. RAN 104 can also communicate with core network 107.

[0305] RAN 104 can include evolved Node Bs 160a, 160b, 160c, but it should be understood that RAN 104 can include any number of evolved Node Bs while remaining consistent with the embodiment. Each of the evolved Node Bs 160a, 160b, 160c can include one or more transceivers to communicate with WTRUs 102a, 102b, 102c via air interface 116. In one embodiment, the evolved Node Bs 160a, 160b, 160c can implement MIMO technology. Thus, the evolved Node B 160a, for example, can use multiple antennas to transmit wireless signals to WTRU 102a and receive wireless signals from that WTRU.

[0306] Each of the evolved Node Bs 160a, 160b, and 160c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, user scheduling in the uplink and / or downlink, etc. As Figure 12D shown, the evolved Node Bs 160a, 160b, 160c can communicate with each other via the X2 interface.

[0307] Figure 12D The core network 107 shown can include a Mobility Management Entity (MME) 162, a Serving Gateway 164, and a Packet Data Network (PDN) Gateway 166. Although each of the foregoing elements is depicted as part of the core network 107, it should be understood that any of these elements can be owned and / or operated by an entity other than the core network operator.

[0308] The MME 162 can be connected to each of the evolved Node Bs 160a, 160b, 160c in RAN 104 via the S1 interface and can act as a control node. For example, the MME 162 can be responsible for authenticating users of WTRUs 102a, 102b, 102c, bearer activation / deactivation, selecting a specific Serving Gateway during the initial attachment of WTRUs 102a, 102b, 102c, etc. The MME 162 can also provide control plane functions for handover between RAN 104 and other RANs (not shown) using other radio technologies such as GSM or WCDMA.

[0309] The serving gateway 164 may be connected to each of the evolved Node Bs 160a, 160b, and 160c in the RAN 104 via the S1 interface. The serving gateway 164 may generally route and forward user data packets to / from the WTRUs 102a, 102b, 102c. The serving gateway 164 may also perform other functions, such as anchoring the user plane during handovers between evolved Node Bs, triggering paging when downlink data is available for the WTRUs 102a, 102b, 102c, managing and storing the context of the WTRUs 102a, 102b, 102c, etc.

[0310] The serving gateway 164 may also be connected to a PDN gateway 166, which may provide the WTRUs 102a, 102b, 102c with access to a packet switched network (such as the Internet 110) to facilitate communication between the WTRUs 102a, 102b, 102c and IP-enabled devices.

[0311] The core network 107 may facilitate communication with other networks. For example, the core network 107 may provide the WTRUs 102a, 102b, 102c with access to a circuit switched network (such as the PSTN 108) to facilitate communication between the WTRUs 102a, 102b, 102c and traditional landline communication devices. For example, the core network 107 may include an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between the core network 107 and the PSTN 108 or may communicate with such an IP gateway. Additionally, the core network 107 may provide the WTRUs 102a, 102b, 102c with access to a network 112, which may include other wired or wireless networks owned and / or operated by other service providers.

[0312] Figure 12E is a system diagram of the RAN 105 and the core network 109 according to one embodiment. The RAN 105 may be an access service network (ASN) that communicates with the WTRUs 102a, 102b, and 102c via an air interface 117 using IEEE 802.16 radio technology. As will be further discussed below, the communication links between the different functional entities of the WTRUs 102a, 102b, 102c, the RAN 105, and the core network 109 may be defined as reference points.

[0313] As Figure 12EAs shown, the RAN 105 may include base stations 180a, 180b, 180c and an ASN gateway 182. However, it should be understood that the RAN 105 may include any number of base stations and ASN gateways while remaining consistent with the embodiments. The base stations 180a, 180b, 180c may each be associated with a specific cell in the RAN 105 and may include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c via an air interface 117. In one embodiment, the base stations 180a, 180b, 180c may implement MIMO technology. Thus, the base station 180a, for example, may use multiple antennas to transmit wireless signals to the WTRU 102a and receive wireless signals from the WTRU. The base stations 180a, 180b, 180c may also provide mobility management functions such as handover triggering, tunnel establishment, radio resource management, traffic classification, quality of service (QoS) policy enforcement, and so on. The ASN gateway 182 may act as a traffic aggregation point and may be responsible for paging, caching of subscriber profiles, routing to the core network 109, and so on.

[0314] The air interface 117 between the WTRUs 102a, 102b, 102c and the RAN 105 may be defined as the R1 reference point that implements the IEEE802.16 standard. In addition, each of the WTRUs 102a, 102b, and 102c may establish a logical interface (not shown) with the core network 109. The logical interface between the WTRUs 102a, 102b, 102c and the core network 109 may be defined as the R2 reference point, which may be used for authentication, authorization, IP host configuration management, and / or mobility management.

[0315] The communication link between each of the base stations 180a, 180b, and 180c may be defined as the R8 reference point, which includes a protocol for facilitating WTRU handover and the transfer of data between the base stations. The communication link between the base stations 180a, 180b, 180c and the ASN gateway 182 may be defined as the R6 reference point. The R6 reference point may include a protocol for facilitating mobility management based on mobility events associated with each of the WTRUs 102a, 102b, 102c.

[0316] As Figure 12EAs shown, the RAN 105 can be connected to the core network 109. The communication link between the RAN 105 and the core network 109 can be defined as the R3 reference point, which includes, for example, protocols for facilitating data transfer and mobility management capabilities. The core network 109 can include a Mobile IP Home Agent (MIP-HA) 184, an Authentication, Authorization, Accounting (AAA) server 186, and a gateway 188. Although each of the foregoing elements is depicted as part of the core network 109, it should be understood that any of these elements can be owned and / or operated by an entity other than the core network operator.

[0317] The MIP-HA can be responsible for IP address management and can enable the WTRUs 102a, 102b, and 102c to roam between different ASNs and / or different core networks. The MIP-HA 184 can provide the WTRUs 102a, 102b, 102c with access to a packet-switched network, such as the Internet 110, to facilitate communication between the WTRUs 102a, 102b, 102c and IP-enabled devices. The AAA server 186 can be responsible for user authentication and supporting user services. The gateway 188 can facilitate interworking with other networks. For example, the gateway 188 can provide the WTRUs 102a, 102b, 102c with access to a circuit-switched network, such as the PSTN 108, to facilitate communication between the WTRUs 102a, 102b, 102c and traditional landline communication devices. In addition, the gateway 188 can provide the WTRUs 102a, 102b, 102c with access to the network 112, which can include other wired or wireless networks owned and / or operated by other service providers.

[0318] Although Figure 12E not shown, it should be understood that the RAN 105 can be connected to other ASNs, and the core network 109 can be connected to other core networks. The communication link between the RAN 105 and other ASNs can be defined as the R4 reference point, which can include protocols for coordinating the mobility of the WTRUs 102a, 102b, 102c between the RAN 105 and other ASNs. The communication link between the core network 109 and other core networks can be defined as the R5 reference point, which can include protocols for facilitating interworking between the home core network and the visited core network.

[0319] As described herein and in Figure 12A 、 Figure 12C 、 Figure 12D and Figure 12EThe core network entities shown are identified by the names given to these entities in certain existing 3GPP specifications, but it should be understood that in the future these entities and functions may be identified by other names, and certain entities or functions may be combined in future 3GPP - published specifications (including future 3GPP NR specifications). Thus, the Figures 12A - 12E specific network entities and functions described and shown are provided by way of example only, and it should be understood that the subject matter disclosed and claimed herein may be embodied or implemented in any similar communication system, whether currently defined or defined in the future.

[0320] Figure 12F is a block diagram of an example computing system 90 in which one or more devices of the communication network shown in Figure 12A , Figure 12C , Figure 12D and Figure 12E may be embodied, such as certain nodes or functional entities in RAN 103 / 104 / 105, core network 106 / 107 / 109, PSTN 108, Internet 110, or other network 112. The computing system 90 may include a computer or a server and may be mainly controlled by computer - readable instructions, which may be in the form of software, regardless of where or by what means such software is stored or accessed. Such computer - readable instructions may be executed within a processor 91 to cause the computing system 90 to operate. The processor 91 may be a general - purpose processor, a special - purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application - specific integrated circuit (ASIC), a field - programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 91 may perform signal encoding, data processing, power control, input / output processing, and / or any other functionality that enables the computing system 90 to operate in a communication network. The coprocessor 81 is an optional processor different from the main processor 91, which may perform additional functions or assist the processor 91. The processor 91 and / or the coprocessor 81 may receive, generate, and process data related to the methods and apparatuses disclosed herein.

[0321] In operation, the processor 91 fetches instructions, decodes the instructions, and executes the instructions, and transfers information to and from other resources via the main data transfer path (system bus 80) of the computing system. This system bus connects the components in the computing system 90 and defines the medium for data exchange. The system bus 80 generally includes data lines for sending data, address lines for sending addresses, and control lines for sending interrupts and for operating the system bus. An example of such a system bus 80 is a PCI (Peripheral Component Interconnect) bus.

[0322] The memories coupled to the system bus 80 include a random access memory (RAM) 82 and a read-only memory (ROM) 93. Such memories include circuitry that permits information to be stored and retrieved. The ROM 93 typically contains stored data that cannot be easily modified. The data stored in the RAM 82 can be read or changed by the processor 91 or other hardware devices. Access to the RAM 82 and / or ROM 93 can be controlled by a memory controller 92. The memory controller 92 can provide an address translation function that converts virtual addresses into physical addresses as instructions are executed. The memory controller 92 can also provide a memory protection function that isolates processes within the system and isolates system processes from user processes. Thus, a program running in the first mode can only access the memory mapped through its own process virtual address space. It cannot access the memory within the virtual address space of another process unless memory sharing between processes has been set up.

[0323] In addition, the computing system 90 can include a peripheral device controller 83 responsible for passing instructions from the processor 91 to peripheral devices such as a printer 94, a keyboard 84, a mouse 95, and a disk drive 85.

[0324] A display 86 controlled by a display controller 96 is used to display visual output generated by the computing system 90. Such visual output can include text, graphics, animated graphics, and video. The visual output can be provided in the form of a graphical user interface (GUI). The display 86 can be implemented using a CRT-based video display, an LCD-based flat panel display, a gas plasma-based flat panel display, or a touchpad. The display controller 96 includes the electronic components needed to generate the video signal sent to the display 86.

[0325] Additionally, the computing system 90 can include communication circuitry such as a network adapter 97, which can be used to connect the computing system 90 to an external communication network such as Figures 12A to 12E the RAN 103 / 104 / 105, core network 106 / 107 / 109, PSTN 108, Internet 110, or other network 112, to enable the computing system 90 to communicate with other nodes or functional entities of these networks. The communication circuitry, either alone or in combination with the processor 91, can be used to perform the transmit and receive steps of certain apparatuses, nodes, or functional entities described herein.

[0326] Figure 12GAn embodiment of an exemplary communication system 111 is shown, in which the methods and apparatuses described herein and claimed may be embodied. As shown, the exemplary communication system 111 may include wireless transmit / receive units (WTRUs) A, B, C, D, E, F, a base station, a V2X server, and RSUs A and B, but it should be understood that the disclosed embodiments of the present invention contemplate any number of WTRUs, base stations, networks, and / or network elements. One or several or all of the WTRUs A, B, C, D, E may be outside the range of the network (e.g., outside the cell coverage boundary as shown by the dashed line in the figure). WTRUs A, B, C form a V2X group, where WTRU A is the group leader and WTRUs B and C are group members. WTRUs A, B, C, D, E, F may communicate via the Uu interface or the sidelink (PC5) interface.

[0327] It should be understood that any one or all of the apparatuses, systems, methods, and processes described herein can be embodied in the form of computer-executable instructions (e.g., program code) stored on a computer-readable storage medium, which, when executed by a processor (such as processor 118 or 91), causes the processor to execute and / or implement the systems, methods, and processes described herein. Specifically, any one of the steps, operations, or functions described herein can be implemented in the form of such computer-executable instructions executed on a processor of a device or computing system configured for wireless and / or wired network communication. The computer-readable storage medium includes volatile and non-volatile, removable and non-removable media implemented in any non-transitory (e.g., tangible or physical) method or technology for storing information, but such computer-readable storage medium does not include signals. The computer-readable storage medium includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disc (DVD) or other optical disc storage devices, magnetic cassette, tape, disk storage device or other magnetic storage devices, or any other tangible or physical medium that can be used to store the required information and can be accessed by a computing system.

[0328] Appendix 1

[0329] ---------------Modified Section 5.x.1.1 SL Authorization Reception and SCI Transmission

[0330] Sidelink authorization is received dynamically on the PDCCH, configured semi-persistently by RRC, or autonomously selected by the MAC entity. The MAC entity shall have sidelink authorization on the active SL BWP to determine a set of PSCCH durations in which SCI transmissions occur and a set of PSSCH durations in which SL-SCH transmissions associated with the SCI occur.

[0331] If the MAC entity has been configured by RRC to use the SL-RNTI or SLCS-RNTI as indicated in 3GPP TS 38.331, NR: Radio Resource Control (RRC) Protocol Specification, V15.8.0, or TS 36.331 for transmission, then for each PDCCH occasion and for each grant received for that PDCCH occasion, the MAC entity shall:

[0332] 1> If a sidelink grant has been received on the PDCCH for the SL-RNTI of the MAC entity:

[0333] 2> If the NDI received on the PDCCH has not toggled compared to the value in the previously received HARQ information for the HARQ process ID:

[0334] 3> Use the received sidelink grant to determine the PSCCH duration and PSSCH duration for one or more retransmissions of a single MAC PDU for the corresponding sidelink process in accordance with clause 8.1.2 of TS 38.214;

[0335] 2> Otherwise:

[0336] 3> Use the received sidelink grant to determine the PSCCH duration and PSSCH duration for the initial transmission and for retransmissions (if available) of a single MAC PDU in accordance with clause 8.1.2 of TS 38.214;

[0337] 2> Treat the received sidelink grant as the configured sidelink grant; If the received sidelink grant has a target destination, link that destination to the configured sidelink grant.

[0338] 2> If the configured sidelink grant is available for retransmission of a MAC PDU that has been positively acknowledged as specified in clause 5.x.1.3.3:

[0339] 3> Clear from the configured sidelink grant the PSCCH duration and PSSCH duration corresponding to the retransmission of the MAC PDU;

[0340] 1> Otherwise, if a sidelink grant has been received on the PDCCH for the SLCS-RNTI of the MAC entity:

[0341] 2> If the PDCCH content indicates retransmission of the configured sidelink grant for activation:

[0342] 3>Use the received sidelink grant to determine the PSCCH duration and PSSCH duration for one or more retransmissions of a single MAC PDU according to clause 8.1.2 of TS 38.214;

[0343] 2>Otherwise, if the PDCCH content indicates deactivation of the configured grant type 2 for the configured sidelink grant:

[0344] 3>Clear the configured sidelink grant, if available;

[0345] 3>Trigger the configured sidelink grant confirmation for the configured sidelink grant;

[0346] 2>Otherwise, if the PDCCH content indicates activation of the configured grant type 2 for the configured sidelink grant:

[0347] 3>Trigger the configured sidelink grant confirmation for the configured sidelink grant;

[0348] 3>Store the configured sidelink grant; If the configured sidelink grant has a target destination, then link that destination to the configured sidelink grant.

[0349] 3>Initialize or re-initialize the configured sidelink grant to determine the set of PSCCH durations and the set of PSSCH durations for the transmission of multiple MAC PDUs according to clause 8.1.2 of TS

[0350] 38.214.

[0351] For each sidelink procedure, if the MAC entity has been RRC-configured to use a resource pool in a carrier as indicated in TS 38.331 or TS 36.331 for transmission based on sensing or random selection, the MAC entity shall:

[0352] Note: If the MAC entity has been RRC-configured to neither use the SL-RNTI nor the SLCS-RNTI for transmission, but has been RRC-configured to use a resource pool in a carrier as indicated in TS 38.331 for transmission, the MAC entity may create a configured sidelink grant on the resource pool only after releasing other configured sidelink grants (if any).

[0353] 1>If the MAC entity has selected to create a configured sidelink grant corresponding to the transmission of multiple MAC PDUs and SL data is available in the logical channel:

[0354] 2>Perform the TX resource (re-)selection check as specified in clause 5.x.1.2;

[0355] Note: The MAC entity continuously performs TX resource (re)-selection checks until the corresponding resource pool is released by RRC or the MAC entity cancels the selection of the configured sidelink authorization that creates the transmission corresponding to multiple MAC PDUs.

[0356] 2> If TX resource

[0357] (re)-selection is triggered as a result of the TX resource (re)-selection check:

[0358] 3> Select one value from the permitted values configured by RRC in sl-ResourceReservePeriodList, and set the resource reservation interval with the selected value;

[0359] 3> Randomly select an integer value in the range [5, 15] with equal probability for a resource reservation interval greater than or equal to 100 ms, and set SL_RESOURCE_RESELECTION_COUNTER to the selected value;

[0360] 3> Select the number of HARQ retransmissions from the permitted number configured by RRC in sl-MaxTxTransNumPSSCH included in sl-PSSCH-TxConfigList, and if configured by the upper layer, for the highest priority of the logical channels permitted on the carrier, overlap in sl-MaxTxTransNumPSSCH indicated in sl-CBR-PSSCH-TxConfigList

[0361] and if CBR measurement results are available, CBR is measured by the lower layer according to TS38.2xx[xx], or if CBR measurement results are not available, the corresponding sl-defaultTxConfigIndex

[0362] is configured by RRC;

[0363]

[0364] 3> Select the amount of frequency resources within the range configured by RRC between sl-MinSubChannelNumPSSCH and sl-MaxSubchannelNumPSSCH included in sl-PSSCH-TxConfigList, and if configured by RRC,

[0365] for the highest priority of the logical channels permitted on the carrier, overlap in sl-

[0366]

[0367] and if CBR measurement results are available, CBR is measured by the lower layer according to TS38.2xx[xx], or if CBR measurement results are not available, the corresponding sl-defaultTxConfigIndex ​​

[0368] Between MinSubChannelNumPSSCH and MaxSubchannelNumPSSCH indicated in the CBR-PSSCH-TxConfigList, and if CBR measurement results are available, according to TS 38.2xx[xx], CBR is measured by the lower layer, or corresponding to the case where CBR measurement results are not available

[0369] The sl-defaultTxConfigIndex is configured by RRC;

[0370] 3> Select, in the logical channels and MAC CE (if any) that satisfy all of the following conditions, the destination that includes the logical channel or MAC CE associated with one of unicast, multicast, and broadcast and that has the highest priority:

[0371] 4> SBj > 0, in the presence of any logical channel with SBj > 0.

[0372] 3> If the grant authorizes the use of destination - specific types of assistance information:

[0373] 4> According to the amount of selected frequency resources and the remaining

[0374] PDB of the SL data available in the logical channels allowed on the carrier, use the assistance information to reduce the resource set indicated by the physical layer according to clause 8.1.4 of TS 38.214, and the reduction of the resource set 3> Based on the selected amount of frequency resources and the remaining PDB of the SL data available in the allowed logical channels on the carrier and the reduction of the resource set , randomly select time resources and frequency resources for one

[0375] transmission occasion from the resources indicated by the physical layer according to clause 8.1.4 of TS 38.214;

[0376] 3> Use the randomly selected resources to select periodic

[0377] resource sets separated by resource reservation intervals for the transmission of PSCCH and PSSCH corresponding to the number of transmission occasions of the MAC PDU determined in TS 38.214

[0378] ;

[0379] 3> If one or more HARQ retransmissions are selected:

[0380] 4> If there are remaining available resources in the resources indicated by the physical layer according to clause 8.1.4 of TS 38.214 for more transmission occasions:

[0381] 5> Based on the selected amount of frequency resources, the selected number of HARQ retransmissions, and the remaining PDB of the SL data available in the allowed logical channels on the carrier 3> If the selected destination is unicast, link that destination to the configured sidelink grant. , randomly select time resources and frequency resources for one or more transmission occasions from the available resources;

[0382] 5>Use randomly selected resources to select a set of periodic resources separated by a resource reservation interval for the transmission of PSCCH and PSSCH corresponding to the number of retransmission opportunities of the MAC PDU determined in TS 38.214;

[0383] 5>[Consider the first set of transmission opportunities as new transmission opportunities and consider the other set of transmission opportunities as retransmission opportunities;]

[0384] 5>Consider the set of new transmission opportunities and retransmission opportunities as the selected sidelink grant.

[0385] 3>Otherwise:

[0386] 4>Consider the set as the selected sidelink grant;

[0387] 3>Use the selected sidelink grant to determine the set of PSCCH durations and the set of PSSCH durations according to TS38.214;

[0388] 3>Consider the selected sidelink grant as the configured sidelink grant.

[0389] 3> If the grant is linked to a destination:

[0390] 2>Otherwise, if SL_RESOURCE_RESELECTION_COUNTER = 0 and when SL_RESOURCE_RESELECTION_COUNTER is equal to 1, the MAC entity randomly selects with equal probability a value less than or equal to the probability value configured by the upper layer in sl - ProbResourceKeep in the interval [0,1]:

[0391] the upper layer in sl - ProbResourceKeep:

[0392] 3>Clear the configured sidelink grant, if available;

[0393] ​

[0394] 4> Select a destination that includes the logical channel or MAC CE with the highest priority and is associated with one of unicast, multicast, and broadcast in the logical channels and MAC CE (if any) that meet all of the following conditions:

[0395] 5> SBj > 0, in the case where there is any logical channel with SBj > 0.

[0396] 3>Randomly select an integer value in the interval [5,15] with equal probability for a resource reservation interval greater than or equal to 100 ms, and set SL_RESOURCE_RESELECTION_COUNTER to the selected value;

[0397] 3> using the previously selected sidelink grant for the number of transmissions of the MAC PDU determined with the resource reservation interval in TS 38.214 to determine the PSCCH duration set and the PSSCH duration set according to TS 38.214;

[0398] 3> Treat the selected sidelink grant as the configured sidelink grant.

[0399] 3> If the selected destination is unicast, link the destination to the configured sidelink grant.

[0400] 1> If the MAC entity has chosen to create a configured sidelink grant corresponding to the transmission of a single MAC PDU and if SL data is available in the logical channel or SL-CSI reporting is triggered:

[0401] 2> Perform TX resource (re)selection checks as specified in clause 5.x.1.2;

[0402] 2> If TX resource (re)selection is triggered as a result of the TX resource (re)selection check:

[0403] 3> from the sl-PSSCH-TxConfigList included in the RRC

[0404] The number of HARQ retransmissions is selected from the allowed number configured in MaxTxTransNumPSSCH and, if configured by RRC, for the highest priority logical channel allowed on the carrier, overlapped in sl-MaxTxTransNumPSSCH indicated in sl-CBR-PSSCH-TxConfigList and the CBR is measured by lower layers according to TS 38.2xx[xx] if the CBR measurement result is available, or the corresponding sl-defaultTxConfigIndex is configured by RRC if the CBR measurement result is not available;

[0405] 3> In the sl-PSSCH-TxConfigList included by RRC

[0406] The amount of subchannel resources is selected within the configured range between MinSubChannelNumPSSCH and sl-MaxSubChannelNumPSSCH, and if configured by RRC, for the highest priority logical channel allowed on the carrier, overlapped in sl-

[0407] sl-indicated in CBR-PSSCH-TxConfigList

[0408] Between MinSubChannelNumPSSCH and sl-MaxSubChannelNumPSSCH, and if CBR measurement results are available, according to TS 38.2xx[xx], CBR is measured by the lower layer, or if CBR measurement results are not available, the corresponding sl-defaultTxConfigIndex is configured by RRC;

[0409] 3> Select a destination that includes the logical channel or MAC CE with the highest priority and is associated with one of unicast, multicast, and broadcast in the logical channels and MAC CE (if any) that meet all of the following conditions:

[0410] 4> SBj > 0, in the case where there is any logical channel with SBj > 0.

[0411] 3> If authorized to use destination-specific type of auxiliary information:

[0412] 4> According to the selected amount of frequency resources and the remaining SL data available in the logical channels allowed on the carrier PDB, use the auxiliary information to reduce the resource set indicated by the physical layer according to Clause 8.1.4 of TS 38.214,

[0413] 3>Based on the amount of selected frequency resources and the remaining PDB of SL data available in the allowed logical channels on the carrier and the reduction of the resource set , randomly select time resources and frequency resources for one transmission occasion from the resources indicated by the physical layer according to clause 8.1.4 of TS 38.214;

[0414] 3>If one or more HARQ retransmissions are selected:

[0415] 4>If there are remaining available resources in the resources indicated by the physical layer according to clause 8.1.4 of TS 38.214 for more transmission occasions:

[0416] 5>Based on the amount of selected frequency resources, the selected number of HARQ retransmissions, and the remaining PDB of SL data available in the allowed logical channels on the carrier and the reduction of the resource set , randomly select time resources and frequency resources for one or more transmission occasions from the available resources;

[0417] 5>[Regard the transmission occasion that arrives first in time as a new transmission occasion and the transmission occasion that arrives later in time as a retransmission occasion];

[0418] 5>Regard both of these transmission occasions as the selected sidelink grant;

[0419] 3>Otherwise:

[0420] 4>Regard this set as the selected sidelink grant;

[0421] 3>Use the selected sidelink grant to determine the PSCCH duration and PSSCH duration according to TS 38.214;

[0422] 3> Consider the selected sidelink grant as the configured sidelink grant.

[0423] 3> If the selected destination is unicast, link the destination to the configured sidelink grant.

[0424] 1> If the configured sidelink grant is available for retransmission of a MAC PDU that has been positively acknowledged as specified in clause 5.x.1.3.3:

[0425] 2> Clear the PSCCH duration and PSSCH duration corresponding to the retransmission of the MAC PDU from the configured sidelink grant;

[0426] For each PSSCH duration, the MAC entity shall:

[0427] 1> For each configured sidelink grant that occurs during this PSSCH duration:

[0428] 2> If the MAC entity has been configured by RRC to use SL-RNTI or SLCS-RNTI for transmission:

[0429] 3> Select the MCS in the configured case within the range configured by RRC between sl-MinMCS-

[0430] PSSCH and sl-MaxMCS-PSSCH;

[0431] 2> Otherwise:

[0432] 3> Select the MCS in the configured case within the range configured by RRC between sl-MinMCS-

[0433] PSSCH and sl-MaxMCS-PSSCH, and if configured by RRC, for the highest priority of the sidelink logical channel in the MAC PDU, overlap between sl-

[0434] CBR-PSSCH-TxConfigList indicates sl-MinMCS-PSSCH and sl-

[0435] MaxMCS-PSSCH, and if CBR measurement results are available then according to TS 38.2xx[xx], CBR is measured by RRC, or if CBR measurement results are not available then the corresponding sl-defaultTxConfigIndex is configured by RRC;

[0436] Note: If the MCS or the corresponding range is not configured by the upper layer, the MCS selection depends on the UE implementation.

[0437] 2> Deliver the sidelink grant, Destination linked to the sidelink grant (if any) , the selected MCS, and the associated HARQ information to the sidelink HARQ entity within the PSSCH duration.

[0438] ---------------- Modified Section 5.x.1.4.1.2 Selection of Logical Channels

[0439] For each SCI corresponding to a new transmission, the MAC entity shall:

[0440] 1> If the authorization has a linked destination:

[0441] 2> Use it as the selected destination;

[0442] 1> Otherwise:

[0443] 2> Select the destination associated with one of unicast, multicast, and broadcast that includes the logical channel or MAC CE with the highest priority among the logical channels and MAC CEs (for the SL grant associated with the SCI, if any) that satisfy all of the following conditions:

[0444] 3> SL data is available for transmission; and

[0445] 3> SBj > 0, in the case where there is any logical channel with SBj > 0; and

[0446] 3> In the case where the SL grant is the configured grant type 1, sl-

[0447] configuredSLGrantType1Allowed (if configured) is set to true.

[0448] Note: If multiple destinations have logical channels with the same highest priority that satisfy all of the above conditions or if multiple destinations include MAC CEs with the highest priority, which destination to select among them depends on the UE implementation.

[0449] 1> Select a logical channel among the logical channels belonging to the selected destination that satisfies all of the following conditions:

[0450] 2> SL data is available for transmission; and

[0451] 2> In the case where the SL grant is the configured grant type 1, sl-

[0452] configuredSLGrantType1Allowed (if configured) is set to true; and

[0453] 2> A logical channel is equivalently configured to the logical channel with the highest priority in sl-HARQ-FeedbackEnabled.

[0454] Appendix 2

[0455] --------------- Modified Section 5.x.1.1 SL Grant Reception and SCI Transmission

[0456] The sidelink grant is received dynamically on the PDCCH, configured semi-persistently by RRC, or autonomously selected by the MAC entity. The MAC entity shall have a sidelink grant on the active SL BWP to determine a set of PSCCH durations in which SCI transmissions occur and a set of PSSCH durations in which SL-SCH transmissions associated with the SCI occur.

[0457] If the MAC entity has been configured by RRC to transmit using an SL-RNTI or SLCS-RNTI as indicated in TS 38.331 or TS 36.331, for each PDCCH occasion and for each grant received for that PDCCH occasion, the MAC entity shall:

[0458] 1> If a sidelink grant has been received on the PDCCH for the SL-RNTI of the MAC entity:

[0459] 2> If the NDI received on the PDCCH has not toggled compared to the value in the previously received HARQ information for the HARQ process ID:

[0460] 3> Use the received sidelink grant to determine the PSCCH durations and PSSCH durations for one or more retransmissions of a single MAC PDU for the corresponding sidelink process according to Clause 8.1.2 of TS 38.214;

[0461] 2> Otherwise:

[0462] 3> Use the received sidelink grant to determine the PSCCH durations and PSSCH durations for the initial transmission and retransmissions (if available) of a single MAC PDU according to Clause 8.1.2 of TS 38.214;

[0463] 2> Consider the received sidelink grant as the configured sidelink grant;

[0464] 2> If the configured sidelink grant is available for retransmissions of MAC PDUs that have been positively acknowledged as specified in Clause 5.x.1.3.3:

[0465] 3> Clear the PSCCH duration and PSSCH duration corresponding to the retransmission of the MAC PDU from the configured sidelink grant;

[0466] 1> Otherwise, if a sidelink grant has been received on the PDCCH with the SLCS-RNTI for the MAC entity:

[0467] 2> If the PDCCH content indicates a retransmission of the configured sidelink grant for activation:

[0468] 3> Use the received sidelink grant to determine the PSCCH duration and PSSCH duration for one or more retransmissions of a single MAC PDU according to clause 8.1.2 of TS 38.214;

[0469] 2> Otherwise, if the PDCCH content indicates the configured grant type 2 deactivation of the configured sidelink grant:

[0470] 3> Clear the configured sidelink grant, if available;

[0471] 3> Trigger the configured sidelink grant confirmation for the configured sidelink grant;

[0472] 2> Otherwise, if the PDCCH content indicates the configured grant type 2 activation of the configured sidelink grant:

[0473] 3> Trigger the configured sidelink grant confirmation for the configured sidelink grant;

[0474] 3> Store the configured sidelink grant;

[0475] 3> Initialize or re-initialize the configured sidelink grant to determine the set of PSCCH durations and the set of PSSCH durations for the transmission of multiple MAC PDUs according to

[0476] 38.214, clause 8.1.2.

[0477] If the MAC entity has been RRC-configured to use a resource pool in a carrier as indicated in TS 38.331 or TS 36.331 for transmission based on sensing or random selection, for each sidelink procedure, the MAC entity shall:

[0478] Note: If the MAC entity has been configured by RRC to use neither the SL-RNTI nor the SLCS-RNTI for transmission, but instead has been configured by RRC to use the resource pool in the carrier as indicated in TS 38.331, the MAC entity may create the configured sidelink grant on the resource pool only after releasing any other configured sidelink grants (if any).

[0479] 1> If the MAC entity has selected to create the configured sidelink grant corresponding to the transmission of multiple MAC PDUs and SL data is available on the logical channel:

[0480] 2> Perform the TX resource (re)selection check as specified in Clause 5.x.1.2;

[0481] Note: The MAC entity continuously performs the TX resource (re)selection check until the corresponding resource pool is released by RRC or the MAC entity deselects to create the configured sidelink grant corresponding to the transmission of multiple MAC PDUs.

[0482] 2> If TX resource

[0483] (re)selection is triggered as a result of the TX resource (re)selection check:

[0484] 3> Select one value from the allowed values configured by RRC in sl-ResourceReservePeriodList and set the resource reservation interval with the selected value;

[0485] 3> Randomly select an integer value in the range [5,15] with equal probability for resource reservation intervals greater than or equal to 100 ms and set the SL_RESOURCE_RESELECTION_COUNTER to the selected value;

[0486] 3> Select the number of HARQ retransmissions from the allowed number configured by RRC in sl-MaxTxTransNumPSSCH included in sl-PSSCH-TxConfigList, and if configured by the upper layer, for the highest priority of the logical channels allowed on the carrier, overlap in sl-CBR-PSSCH-TxConfigList

[0487]

[0488] ​in the sl-MaxTxTransNumPSSCH indicated, and if the CBR measurement result is available, according to TS38.2xx[xx], the CBR is measured by the lower layer, or if the CBR measurement result is not available, the corresponding sl-defaultTxConfigIndex is configured by RRC;

[0489] 3> within the range configured between the sl-MinSubChannelNumPSSCH and sl-MaxSubchannelNumPSSCH included by RRC in the sl-PSSCH-TxConfigList, select the amount of frequency resources, and if configured by RRC, for the highest priority of the logical channels allowed on the carrier, overlapping within the sl-

[0490] between the MinSubChannelNumPSSCH and MaxSubchannelNumPSSCH indicated in the CBR-PSSCH-TxConfigList, and if the CBR measurement result is available, according to TS 38.2xx[xx], the CBR is measured by the lower layer, or if the CBR measurement result is not available, the corresponding

[0491] sl-defaultTxConfigIndex is configured by RRC;

[0492] of sl-defaultTxConfigIndex is configured by RRC;

[0493] 3> If authorized to use destination-specific type of auxiliary information:

[0494] 4> According to the selected amount of frequency resources and the remaining SL data available in the logical channels allowed on the carrier PDB, use the auxiliary information to reduce the resource set indicated by the physical layer according to Clause 8.1.4 of TS 38.214, 3> According to the selected amount of frequency resources and the remaining PDB of the SL data available in the logical channels allowed on the carrier and the reduction of the resource set , randomly select the time resources and frequency resources for one transmission occasion from the resources indicated by the physical layer according to Clause 8.1.4 of TS 38.214;

[0495] 3> Use the randomly selected resources to select the periodic

[0496] resource sets separated by resource reservation intervals for the transmission of PSCCH and PSSCH corresponding to the number of transmission occasions of the MAC PDU determined in TS 38.214; 3> If one or more HARQ retransmissions are selected:

[0497] 4> If there are available resources remaining in the resources indicated by the physical layer for more transmission occasions according to Clause 8.1.4 of TS 38.214:

[0498] 5>Based on the selected amount of frequency resources, the selected number of HARQ retransmissions, and the remaining PDB of the available SL data in the logical channels allowed on the carrier and the reduction of the resource set , randomly select time resources and frequency resources from the available resources for one or more transmission occasions;

[0499] 5>Use the randomly selected resources to select a set of periodic resources separated by resource reservation intervals for the transmission of PSCCH and PSSCH corresponding to the number of retransmission occasions of the MAC PDU determined in TS 38.214;

[0500] 5>[Regard the first set of transmission occasions as new transmission occasions and regard the other set of transmission occasions as retransmission occasions;]

[0501] 5>Regard the set of new transmission occasions and retransmission occasions as the selected sidelink grant.

[0502] 3>Otherwise:

[0503] 4>Regard the set as the selected sidelink grant;

[0504] 3>According to TS 38.214, use the selected sidelink grant to determine the set of PSCCH durations and the set of PSSCH durations;

[0505] 3>Regard the selected sidelink grant as the configured sidelink grant.

[0506] 3> If the selected destination is unicast, link the destination to the configured sidelink grant.

[0507] 2>Otherwise, if SL_RESOURCE_RESELECTION_COUNTER = 0 and when SL_RESOURCE_RESELECTION_COUNTER equals 1, the MAC entity randomly selects with equal probability a value less than or equal to the probability value configured by the upper layer in sl-ProbResourceKeep in the interval [0,1]:

[0508] The upper layer configures in sl-ProbResourceKeep:

[0509] 3>Clear the configured sidelink grant, if available;

[0510] 3> If authorized to link to a destination:

[0511] 4> Select a destination that includes the logical channel or MAC CE with the highest priority and is associated with one of unicast, multicast, and broadcast in the logical channels and MAC CE (if any) that meet all of the following conditions:

[0512] 5> SBj > 0, in the case where there is any logical channel with SBj > 0.

[0513] 3> For resource reservation intervals greater than or equal to 100ms, randomly select an integer value in the interval [5,15] with equal probability and set SL_RESOURCE_RESELECTION_COUNTER to the selected value;

[0514] 3> using the previously selected sidelink grant for the number of transmissions of the MAC PDU determined with the resource reservation interval in TS 38.214 to determine the PSCCH duration set and the PSSCH duration set according to TS 38.214;

[0515] 3> Treat the selected sidelink grant as the configured sidelink grant.

[0516] 3> If the selected destination is unicast, link the destination to the configured sidelink grant.

[0517] 1> If the MAC entity has chosen to create a configured sidelink grant corresponding to the transmission of a single MAC PDU and if SL data is available in the logical channel or SL-CSI reporting is triggered:

[0518] 2> Perform TX resource (re)selection checks as specified in clause 5.x.1.2;

[0519] 2> If TX resource (re)selection is triggered as a result of the TX resource (re)selection check:

[0520] 3> from the sl-PSSCH-TxConfigList included in the RRC

[0521] The number of HARQ retransmissions is selected from the allowed number configured in MaxTxTransNumPSSCH and, if configured by RRC, for the highest priority logical channel allowed on the carrier, overlapped in sl-MaxTxTransNumPSSCH indicated in sl-CBR-PSSCH-TxConfigList and the CBR is measured by lower layers according to TS 38.2xx[xx] if the CBR measurement result is available, or the corresponding sl-defaultTxConfigIndex is configured by RRC if the CBR measurement result is not available;

[0522] 3> In the sl-PSSCH-TxConfigList included by RRC

[0523] The amount of subchannel resources is selected within the configured range between MinSubChannelNumPSSCH and sl-MaxSubChannelNumPSSCH, and if configured by RRC, for the highest priority logical channel allowed on the carrier, overlapped in sl-

[0524] The sl- indicated in the CBR-PSSCH-TxConfigList

[0525] Between MinSubChannelNumPSSCH and sl-MaxSubChannelNumPSSCH, and if the CBR measurement result is available, according to TS 38.2xx[xx], the CBR is measured by the lower layer, or if the CBR measurement result is not available, the corresponding sl-defaultTxConfigIndex is configured by RRC;

[0526] 3> If authorized to use destination-specific type of auxiliary information:

[0527] 4> According to the selected amount of frequency resources and the remaining SL data available in the logical channels allowed on the carrier PDB, use the auxiliary information to reduce the resource set indicated by the physical layer according to Clause 8.1.4 of TS 38.214,

[0528] 3> Based on the selected amount of frequency resources and the remaining PDB of the SL data available in the allowed logical channels on the carrier and the reduction of the resource set , randomly select the time resources and frequency resources for one transmission occasion from the resources indicated by the physical layer according to Clause 8.1.4 of TS 38.214;

[0529] 3> If one or more HARQ retransmissions are selected:

[0530] 4> If there are remaining available resources in the resources indicated by the physical layer according to Clause 8.1.4 of TS 38.214 for more transmission occasions:

[0531] 5> Based on the selected amount of frequency resources, the selected number of HARQ retransmissions, and the remaining PDB of the SL data available in the allowed logical channels on the carrier and the reduction of the resource set , randomly select the time resources and frequency resources for one or more transmission occasions from the available resources;

[0532] 5> [Regard the transmission occasion that arrives first in time as a new transmission occasion and the transmission occasion that arrives later in time as a retransmission occasion];

[0533] 5> Regard both of these transmission occasions as the selected sidelink grant;

[0534] 3> Otherwise:

[0535] 4> Regard this set as the selected sidelink grant;

[0536] 3> Use the selected sidelink grant to determine the PSCCH duration and the PSSCH duration according to TS 38.214;

[0537] 3>Consider the selected sidelink grant as the configured sidelink grant.

[0538] 3> If the selected destination is unicast, link the destination to the configured sidelink grant.

[0539] 1>If the configured sidelink grant is available for retransmission of a MAC PDU that has been positively acknowledged as specified in clause 5.x.1.3.3:

[0540] 2>Clear the PSCCH duration and PSSCH duration corresponding to the retransmission of the MAC PDU from the configured sidelink grant;

[0541] For each PSSCH duration, the MAC entity shall:

[0542] 1>For each configured sidelink grant that occurs during this PSSCH duration:

[0543] 2>If the MAC entity has been configured by RRC to transmit using SL-RNTI or SLCS-RNTI:

[0544] 3>Select the MCS in the configured case within the range configured by RRC between sl-MinMCS-

[0545] PSSCH and sl-MaxMCS-PSSCH;

[0546] 2>Otherwise:

[0547] 3>Select the MCS in the configured case within the range configured by RRC between sl-MinMCS-

[0548] PSSCH and sl-MaxMCS-PSSCH, and if configured by RRC, for the highest priority of the sidelink logical channel in the MAC PDU, overlap between sl-

[0549] CBR-PSSCH-TxConfigList indicates sl-MinMCS-PSSCH and sl-

[0550] MaxMCS-PSSCH, and if CBR measurement results are available, according to TS 38.2xx[xx], CBR is measured by RRC, or if CBR measurement results are not available, the corresponding sl-defaultTxConfigIndex is configured by RRC;

[0551] Note: If the MCS or the corresponding range is not configured by the upper layer, the MCS selection depends on the UE implementation.

[0552] 2> Deliver the sidelink grant, Destination linked to the sidelink grant (if any) the selected MCS, and the associated HARQ information to the sidelink HARQ entity within the PSSCH duration.

[0553] ---------------- Modified Section 5.x.1.4.1.2 Selection of Logical Channels

[0554] For each SCI corresponding to a new transmission, the MAC entity shall:

[0555] 1> Select, among the logical channels and MAC CEs (for the SL grant associated with the SCI, if any), the destination associated with one of unicast, multicast, and broadcast that includes the logical channel or MAC CE with the highest priority:

[0556] 2> SL data is available for transmission; and

[0557] 2> SBj > 0, in the case where there is any logical channel with SBj > 0; and

[0558] 2> In the case where the SL grant is the configured grant type 1, sl-

[0559] configuredSLGrantType1Allowed (if configured) is set to true.

[0560] Note: If multiple destinations have logical channels with the same highest priority that meet all the above conditions or if multiple destinations include MAC CEs with the highest priority, which destination to select among them depends on the UE implementation.

[0561] 1> If the authorization has a linked destination and the linked destination matches the selected destination:

[0562] 2> Use the linked destination as the selected destination;

[0563] 1> Otherwise:

[0564] 2> Trigger the sidelink grant reception to use the auxiliary information for the selected destination;

[0565] 2> Use the link destination as the selected destination;

[0566] 1> Select, among the logical channels belonging to the selected destination, the logical channel that meets all the following conditions:

[0567] 2> SL data is available for transmission; and

[0568] 2> When the authorization type 1 configured in the SL authorization, sl-configuredSLGrantType1Allowed (if configured) is set to true; and

[0569] 2> A logical channel is set equivalently to the logical channel with the highest priority in sl-HARQ-FeedbackEnabled.

[0570] Appendix 3

[0571] Table 1 - Abbreviations

[0572]

[0573]

Claims

1. A first wireless transmit / receive unit (WTRU) comprising a processor and a memory, the memory including computer-executable instructions that, when executed by the processor, cause the first WTRU to: Send a request for a preferred resource set for sidelink transmission, where the preferred resource set includes one or more resources preferably used for transmission from the first WTRU; Receive the preferred resource set; Determine a second candidate resource set from a first candidate resource set sensed from the first WTRU based on the preferred resource set; and In the case where the transmission resources available in the second candidate resource set are insufficient for sidelink transmission, use the transmission resources determined based on the first candidate resource set to transmit the sidelink transmission.

2. The first WTRU according to claim 1, wherein the request for the preferred resource set is sent to a second WTRU, and wherein the preferred resource set is received from the second WTRU.

3. The first WTRU according to claim 1, wherein the first candidate resource set is provided by the physical layer.

4. The first WTRU according to claim 1, wherein the second candidate resource set is determined based on a selection of resources that are both in the preferred resource set and in the first candidate resource set.

5. A method implemented by a first wireless transmit / receive unit (WTRU), the method comprising: Sending a request for a preferred resource set for sidelink transmission, where the preferred resource set includes one or more resources preferably used for transmission from the first WTRU; Receiving the preferred resource set; Determining a second candidate resource set from a first candidate resource set sensed from the first WTRU based on the preferred resource set; And In the case where the transmission resources available in the second candidate resource set are insufficient for sidelink transmission, using the transmission resources determined based on the first candidate resource set to transmit the sidelink transmission.

6. The method according to claim 5, wherein the request for the preferred resource set is sent to a second WTRU, and wherein the preferred resource set is received from the second WTRU.

7. The method according to claim 5, wherein the first candidate resource set is provided by the physical layer.

8. The method according to claim 5, wherein the second candidate resource set is determined based on a selection of resources that are both in the preferred resource set and in the first candidate resource set.

Images