Downlink Control Information (DCI) for Sidelink Grant

Abstract

A service device (e.g., a user equipment (UE), a new radio NR (gNB), or other network entity) as a service provider / consumer can process or generate sidelink communications based on downlink control information (DCI) of one or more sidelink configuration grants that enable resource allocation for sidelink communications. The device can decide whether to activate, release / deactivate, or request retransmission of one or more sidelink configuration grants based on one or more fields of the DCI format 3_0 configuration of the DCI.

Description

Technical Field

[0001] The present disclosure relates to wireless technology, and more specifically, to downlink control information (DCI) for one or more sidelink grants.

Background Art

[0002] Mobile communications in next-generation wireless communication systems, 5G, or new radio (NR) networks provide connectivity and access to information everywhere, as well as data sharing capabilities worldwide. 5G networks and network slicing aim to provide services for very heterogeneous application areas, from high-speed large-capacity (eMBB) to massive machine-type communication (mMTC), ultra-reliable low-latency (URLLC), and other communications, satisfying multi-purpose and sometimes conflicting performance criteria, and are a unified service-based framework. Generally, NR evolves based on the Long-Term Evolution (LTE) advanced technology of the 3rd Generation Partnership Project (3GPP) and uses additional enhanced radio access technology (RAT) to enable seamless and faster wireless connectivity solutions.

[0003] Some services have ultra-low latency, high data capacity, and stringent reliability requirements because network outages or performance issues can cause service disruptions that can lead to physical damage and bodily injury. Types of mobile communications include vehicle communications where vehicles communicate or exchange vehicle-related information. Vehicle communications can include vehicle-to-everything (V2X), which can include vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and vehicle-to-pedestrian (V2P), etc., each of which can include user equipment (UE) or base station equipment such as new radio NodeB (gNB), eNodeB (eNB), or other devices / nodes. For example, V2X nodes can include, when referred to herein, new radio NodeB (gNB), eNodeB (eNB), user equipment (UE), roadside unit (RSU), drone, or other vehicle devices, or network devices. Depending on the situation, vehicle-related information can be targeted at a single vehicle or other entity. In other situations such as emergency warnings, vehicle-related information is targeted at entities of multiple vehicles or other devices. Emergency warnings can include, among other things, collision warnings, loss of control warnings, collision avoidance, pedestrian safety, and other adjustments to ensure a safe and efficient traffic flow in vehicle-to-vehicle communications (e.g., for automobiles, ships, airplanes, drones, etc.).

[0004] Long-Term Evolution (LTE) networks or New Radio (NR) cellular technologies have been developed to support direct communication between devices (e.g., vehicles, drones, wearables, etc.). At present, sidelink communication is available in V2X technology, and multiple reference sources can be used for sidelink synchronization Global Navigation Satellite System (GNSS), eNodeB (eNB), sidelink synchronization signal (SLSS) (the UE derives the timing from either GNSS, eNB, or another user equipment (UE) that derives the timing from GNSS or eNB). To ensure reliability and power efficiency, the sidelink grant for sidelink communicable resources needs to be further configured by an efficient mechanism.

Brief Description of the Drawings

[0005]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

DETAILED DESCRIPTION OF THE INVENTION

[0006] It should be fully understood that the use of personally identifiable information should comply with privacy policies and practices that generally meet or exceed industry or government requirements for maintaining user privacy. In particular, personally identifiable information data should be managed and handled to minimize the risk of unintended or unauthorized access or use, and the nature of the permitted use should be clearly shown to the user.

[0007] Here, the present disclosure will be described with reference to the accompanying drawings, where like reference numerals are used throughout to refer to like elements, and the structures and devices illustrated are not necessarily drawn to scale. As used herein, terms such as "component", "system", "interface", etc. are intended to refer to computer-related entities, hardware, (e.g., running) software, and / or firmware. For example, a component can be a processor (e.g., a microprocessor, a controller, or other processing device), a process running on the processor, a controller, an object, an executable file, a program, a storage device, a computer, a tablet PC, and / or a user device (e.g., a mobile phone, etc.) equipped with a processing device. By way of example, an application running on a server and the server can also be components. One or more components can be present within a process, and the components can be localized on one computer and / or distributed among two or more computers. In this specification, a set of elements or other sets of components can be described, and the term "set" can be interpreted as "one or more".

[0008] Furthermore, these components can be executed from various computer-readable storage media having various data structures stored thereon, such as, for example, modules. The components can communicate via local and / or remote processes, such as in accordance with a signal having one or more data packets (e.g., data from one component acting with another component via a network such as within a local system, a distributed system, and / or the Internet, a local area network, a wide area network, or other similar network through which the signal passes).

[0009] As another example, a component can be a device having a specific function provided by a mechanical part operated by an electrical circuit or an electronic circuit, and the electrical circuit or the electronic circuit can be operated by a software application or a firmware application executed by one or more processors. The one or more processors can be internal or external to the device and can execute at least a part of the software or firmware application. As yet another example, a component can be a device that provides a specific function via an electronic component that does not have a mechanical part, and the electronic component can include therein one or more processors for executing software and / or firmware that at least partially imparts functionality to the electronic component.

[0010] The use of the word "exemplary" is intended to present concepts in a concrete fashion. When used in this application, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or". That is, unless specifically stated otherwise, or clear from the context, "X uses A or B" is intended to mean any of the natural inclusive permutations. That is, "X uses A or B" is satisfied in any of the foregoing instances where X uses A, X uses B, or X uses both A and B. In addition, the articles "a" and "an" as used in this application and the appended claims should generally be construed to mean "one or more" unless specifically designated otherwise, or clear from the context to refer to the singular form. Further, as long as the terms "including", "includes", "having", "has", "with", or variants thereof are used in either the detailed description or the claims, such terms are intended to be inclusive in the same manner as the term "comprising". Further, in situations where one or more numbered items are considered (e.g., "a first X", "a second X", etc.), generally, the one or more numbered items can be distinct or the same, although in some situations the context may indicate whether they are different or the same.

[0011] As used herein, the term "circuit" refers to, is part of, or can include an application specific integrated circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), or associated memory (shared, dedicated, or group) operably coupled to a circuit that executes one or more software or firmware programs, combinational logic circuits, or other suitable hardware components that provide the described functionality. In some embodiments, the circuit may be implemented in one or more software or firmware modules, and the functions associated with the circuit may be implemented by one or more software or firmware modules. In some embodiments, the circuit may include logic that is at least partially operable in hardware.

[0012] Embodiments are described herein with respect to configuring a sidelink grant for resources that enable sidelink communication, particularly by an efficient mechanism that takes into account various requirements for sidelink communication, including ensuring reliability and power efficiency. In particular, mechanisms are described for activating and deactivating a sidelink grant that allocates resources from a network for sidelink communication between devices. Additional aspects relate to retransmission operations such as deriving a hybrid automatic repeat request (HARQ) process identifier (ID) / number involved in retransmitting a sidelink grant. Other embodiments address aligning the size of a DCI format configuration with an existing DCI format to further ensure seamlessness in sidelink communication, thereby further enhancing the reliability and efficiency operational goals.

[0013] In various embodiments, a networked device (e.g., a user equipment, a service consumer device, a network node, a vehicle, or other network component) can store executable instructions that, in response to execution, cause one or more processors on a new radio (NR) network to perform sidelink communication operations. These operations can include receiving downlink control information (DCI) on a physical channel (e.g., a physical downlink control channel (PDCCH), or other physical channel) for a sidelink configuration grant that enables network resources to be allocated for NR sidelink communication. The device can be configured to generate a determination as to whether to activate, release, or retransmit at least one sidelink grant based on one or more fields of a DCI format 3_0 configuration of the DCI.

[0014] A sidelink grant can be, for example, a dynamic grant or a configuration grant. The configuration grant can be a type I (one or 1) configuration grant or a type II (2 or two) configuration grant. The type II configuration grant allocates network communication resources based on a grant via a physical layer trigger (e.g., DCI format 3_0) from the network for the resources. In contrast, the type one configuration grant is distinguished by being based on RRC signaling and is simply referred to herein as a configuration grant. Additional aspects and details of the present disclosure are further described below with reference to the figures.

[0015] FIG. 1 shows an architecture of a system 100 including a core network (CN) 120 according to various embodiments. System 100 is shown to include a user equipment (UE) / vehicle-to-everything (V2X) device 101, a radio access network (R)AN 110 or access node (AN), a 5GC 120, and a data network (DN) 103 that can be, for example, an operator service, an Internet access, or a third-party service.

[0016] A UE (as a V2X, or other network component / device) 101 can include one or more of a vehicle (V2V), vehicle and infrastructure (V2I), vehicle and pedestrian (V2P), or other network device / component(s). In various embodiments, one or more of UE configuration, UE-provided information, network-provided information, and UE coverage can be used to select a V2X radio access technology (RAT) for transmission (e.g., dedicated short range communications (DSRC), long term evolution (LTE), 5G, or other RAT). Since there are multiple technologies available for V2X communication, some network devices (via UE 101) can be equipped with these multiple access technologies for V2X communication and utilize sidelink communication according to these technologies.

[0017] The 5GC 120 can include an Authentication Server Function (AUSF) 112, an Access and Mobility Function (AMF) 121, a Session Management Function (SMF) 124, a Network Exposure Function (NEF) 123, a Policy Control Function (PCF) 126, a Network Function Repository Function (NRF) 125, a Unified Data Management (UDM) 127, an Application Function (AF) 128, a User Plane Function (UPF) 102, and a Network Slice Selection Function (NSSF) 129. Each of these components can be used to process the corresponding 5GC network function (NF) or related performance metrics as a network function associated with any one or more of the embodiments herein.

[0018] UPF102 can function as an anchor point for in-RAT and inter-RAT mobility, an external protocol data unit (PDU) session point interconnected to DN103, and a branching point for supporting multi-home PDU sessions. UPF102 can also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, legally intercept packets (UP collection), execute traffic usage reports, perform QoS (Quality of Service) processing for the user plane (e.g., packet filtering, gating, uplink (UL) / downlink (DL) rate enforcement), verify uplink traffic (e.g., flow mapping from SDF (Service Data Flow) to QoS), perform transport-level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. UPF102 can include an uplink classifier for supporting the routing of traffic flows to the data network. DN103 can represent various network operator services, Internet access, or third-party services. DN103 can include or be similar to an application server. UPF102 can interact with SMF124 via the N4 reference point between SMF124 and UPF102.

[0019] The AUSF 122 can store data for the authentication of the UE 101 and process authentication-related functions. The AMF 121 can be involved in registration management (such as registering the UE 101, etc.), connection management, reachability management, mobility management, and legal interception of AMF-related events, as well as access authentication and authorization. The AMF 121 may be the terminating point of the N11 reference point between the AMF 121 and the SMF 124. The AMF 121 can perform the transmission for session management (SM) messages between the UE 101 and the SMF 124 and function as a transparent proxy for routing SM messages. The AMF 121 can also perform the transmission for SMS messages between the UE 101 and the Short Message Service (SMS) function (SMSF). The AMF 121 can function as a Security Anchor Function (SEAF) that may include the interaction between the AUSF 122 and the UE 101 and the reception of an intermediate key established as a result of the authentication process of the UE 101. When Universal Subscriber Identity Module (USIM)-based authentication is used, the AMF 121 may obtain security materials from the AUSF 122. The AMF 121 may also include a Security Context Management (SCM) function that receives a key from the SEAF used to derive an access network-specific key. Further, the AMF 121 may be the terminating point of the RAN CP interface or the RAN connection point interface, can include or be the N2 reference point between the (R)AN 110 and the AMF 121, and the AMF 121 may be the terminating point of the non-access stratum (NAS) layer (N1) signaling and may perform NAS encryption and integrity protection.

[0020] AMF121 can also support NAS signaling using UE101 via the N3 Interworking Function (IWF) interface. The N3 IWF can be used to provide access to untrusted entities. The N3IWF may be the termination point of the N2 interface between the (R)AN110 and the AMF121 in the control plane, or the termination point of the N3 reference point between the (R)AN110 and the UPF102 in the user plane. Thus, the AMF121 can process N2 signaling from the SMF124 and the AMF121 for PDU sessions and QoS, encapsulate / decapsulate packets for IPsec and N3 tunneling, mark N3 user plane packets on the uplink, and enforce QoS corresponding to N3 packet marking considering the QoS requirements associated with such marking received via N2. The N3IWF can also relay uplink and downlink control plane NAS signaling between the UE101 and the AMF121 via the N1 reference point between the UE101 and the AMF121, and relay uplink and downlink user plane packets between the UE101 and the UPF102. The N3IWF also provides a mechanism for establishing an IPsec tunnel with the UE101. The AMF121 can present a Namf service-based interface and may be the termination point of the N14 reference point between two AMF121s and the N17 reference point between the AMF121 and the 5G Equipment Identity Register (EIR).

[0021] UE101 can register with AMF121 to receive network services. Registration Management (RM) is used to register or deregister UE101 with the network (e.g., AMF121) and establish a UE context within the network (e.g., AMF121). UE101 can operate in the RM-REGISTERED state or the RM-DEREGISTERED state. In the RM-DEREGISTERED state, UE101 is not registered with the network, and the UE context in AMF121 does not hold valid location or routing information for UE101, so AMF121 cannot reach UE101. In the RM-REGISTERED state, UE101 is registered with the network, and the UE context in AMF121 can hold valid location or routing information for UE101, so AMF121 can reach UE101. In the RM-REGISTERED state, UE101 can execute mobility registration update procedures, periodic registration update procedures triggered by the expiration of a periodic update timer (e.g., to notify the network that UE101 is still active), and among other things, execute registration update procedures to update UE capability information or renegotiate protocol parameters with the network.

[0022] Connection Management (CM) can be used to establish and release a signaling connection between UE101 and AMF121 via the N1 interface. The signaling connection is used to enable NAS signaling exchange between UE101 and CN120 and includes both a signaling connection between the UE and the access network (AN) (e.g., a Radio Resource Control (RRC) connection for non-3GPP access or a UE-N3IWF connection) and an N2 connection for UE101 between AN110 (e.g., RAN or memory) and AMF121.

[0023] The SMF124 can be involved in and execute session management (SM) (including session establishment, modification, and release, e.g., tunnel maintenance between the UPF and the AN node), UE IP address allocation and management (including optional authorization), selection and control of the UPF function, configuration of traffic steering in the UPF for routing traffic to the appropriate destination, termination of the interface to the policy control function, policy enforcement and partial control of QoS, lawful interception (in the case of SM events and the interface to the LI system), termination of the SM part of the NAS message, notification of downlink data, initiation of AN-specific SM information sent to the AN via the AMF on N2, and determination of the SSC mode of the session. SM refers to the management of the PDU session, and a PDU session or "session" can refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE101 and a data network (DN) 103 identified by a data network name (DNN). The PDU session is established upon request by the UE101 using NAS SM signaling exchanged via the N1 reference point between the UE101 and the SMF124, can be modified upon request by the UE101 and the 5GC120, and can be released upon request by the UE101 and the 5GC120. In response to a request from an application server, the 5GC120 may trigger a specific application in the UE101. In response to the receipt of a trigger message, the UE101 can pass the trigger message (or the relevant part / information of the trigger message) to one or more identified applications within the UE101. The identified application(s) within the UE101 can establish a PDU session to a specific DNN. The SMF124 can check whether the UE101 request complies with the user subscription information associated with the UE101. In this regard, the SMF124 can request to obtain and / or receive an update notification regarding the SMF124-level subscription data from the UDM127.

[0024] NEF123 can provide means for securely disclosing to a third party the services and capabilities provided by 3GPP network functions for third parties, internal disclosure / re - disclosure, application functions (e.g., AF128), edge computing or fog computing systems. In such embodiments, NEF123 can authenticate, authorize, and / or regulate the AF. NEF123 can also convert the information exchanged with AF128 and the information exchanged with internal network functions. For example, NEF123 can convert between an AF service identifier and internal 5GC information. NEF123 can also receive information from other network functions (NFs) based on the disclosed capabilities of other network functions. This information can be stored in NEF123 as structured data or in a data storage NF using a standardized interface. The stored information can then be re - disclosed by NEF123 to other NFs and AFs and / or used for other purposes such as analysis. Further, NEF123 can present a Neff service - based interface.

[0025] NRF125 can support a service discovery function, receive NF discovery requests from NF instances, and provide information on discovered NF instances to NF instances. NRF125 also maintains information on available NF instances and the services they support.

[0026] The UDM 127 can process subscription-related information, support the processing of network entities for communication sessions, and store the subscription data of the UE 101. For example, the subscription data can be communicated between the UDM 127 and the AMF via the N8 reference point between the UDM 127 and the AMF 121. The UDM 127 may include two parts: the Application FE and the Uniform Data Repository (UDR) (the FE and the UDR are not shown in Figure 2). The UDR can store the subscription data and policy data of the UDM 127 and the PCF 126, and / or the structured data for the disclosure and application data of the NEF 123 (including the PFD for application detection and the application request information for multiple UEs 101).

[0027] The NSSF 129 can select a set of network slice instances that provide services to the UE 101. The NSSF 129 can also determine the mapping to the permitted NSSAI and the subscribed single network slice selection assistance information (S-NSSAI) as needed. The NSSF 129 can also determine, based on a suitable configuration, and optionally by querying the NRF 125, the set of AMFs used to provide services to the UE 101, or the list of candidate AMF(s) 121. The selection of the set of network slice instances for the UE 101 may be triggered by the AMF 121 in which the UE 101 is registered by interacting with the NSSF 129, which may result in a change of the AMF 121. The NSSF 129 can interact with the AMF 121 via the N12 reference point between the AMF 121 and the NSSF 129, and communicate with another NSSF 129 in the visited network via the N31 reference point (not shown in Figure 2). In addition, the NSSF 129 can present an Nnssf service-based interface.

[0028] Referring to FIG. 2, illustrated is a block diagram of a system 200 that can be used as a component of a next-generation node B (gNodeB or gNB) or other base station (BS) / transmission and reception point (TRP) in RAN 110, or a 3rd Generation Partnership Project 3GPP network 5G component such as embodiments of this specification. The system 200 includes one or more processors 210 including processing circuitry / components (if any) and associated interfaces (if any) (e.g., a communication interface for communicating with communication circuitry 220, a memory interface for communicating with memory 230), communication circuitry 220 (e.g., including circuitry for wired and / or wireless connections (if any)), and a transmitter circuit and / or a receiver circuit (e.g., associated with one or more transmission chains and / or e.g., associated with one or more reception chains). This transmitter circuit and receiver circuit of transceiver 220 can use common or separate circuit elements, or combinations thereof). Memory 230 can include any of a variety of storage media and can store instructions or data associated with one or more of processors 210 or communication circuitry 220. Similarly, embodiments (e.g., UE embodiments) can include, for example, processors (if any), communication circuitry, and memory within a UE (e.g., a V2X UE, etc.) as processors 210, communication circuitry 220, and memory 230 of gNB 110.

[0029] Embodiments of a base station (BS) (e.g., the system 200 of a gNB) and embodiments of network components (e.g., a user plane function (UPF), etc.) (e.g., the system 200 of a UPF), the processor(s) 210 of the gNB, etc., the communication circuit 220 (etc.), and the memory 230 (etc.) can be within a single device or can be included in different devices such as part of a distributed architecture. In an embodiment, signaling or messaging between different embodiments of the system 200 is generated by the processor(s) 210, transmitted by the communication circuit 220 via an appropriate interface or reference point (e.g., N4, etc.), received by the communication circuit 220, and can be processed by the processor(s) 210.

[0030] UE101 can receive V2X configuration information when the UE is permitted to use V2X services via a 3GPP network. This permission can be performed by a V2X function within the core network (e.g., CN120), and as part of the permission procedure, the V2X function can transmit a list of preferred air interface technologies. Alternatively, or additionally, the V2X configuration can be performed by an application server that is not part of the core network 120. UE101 can use one or more channel quality measurements such as power measurements or other measurements related to sidelink communication.

[0031] The V2X UE can be in a given coverage area within a cell covered by a gNB that supports 5G, LTE, or DSRC Road Side Unit (RSU) functionality. These UEs can notify the gNB / RSU that the V2X communication RAT(s) are supported. Based on that information, the network can select the access technology of the UEs to use. System 200 can include vehicle / traffic participant entity 240. Vehicle / traffic participant entity 240 can include one or more service pedestrian devices (P-UEs) or other UE devices 101, vehicle entity 226 (V-UE), or other network device(s) / component(s). V2X UE 101 can also include one or more antennas for communication, including resources for sidelink communication 214 (e.g., DCI) with the vehicle / traffic participant entity or UE 240.

[0032] Vehicle communication between V2X UE 101 and any vehicle / pedestrian device entity 240 can utilize cooperative awareness including information from other vehicles, sensors, etc. to process and share information to provide vehicle services such as collision warnings and autonomous driving. V2X UE 101 can be configured to obtain, select, or determine QoS attributes associated with sidelink communication. The communication / communication configuration herein can include transmission resources, frame structure design, transmission power for broadcast (communication), subframe structure, modulation and coding scheme (MCS), number of occupied subchannels / time transmission interval (TTI), resource reservation interval / period, transmission range per transport block (TB), channel busy ratio (CBR), channel occupancy rate (CR), CR limit (CR_limit), associated LTE parameters in 3GPP, 5G, etc. For example, the frame structure can include parameters including sampling rate, frame length, subframe length, subcarrier spacing, and cyclic prefix length, and can be based on the obtained success rate.

[0033] The sensing operation can be a simplified sensing procedure for V2X UE resource selection aimed at reducing complexity and power consumption. In general, the principles of the sensing and resource selection procedures can be used for sidelink communication management. Other embodiments include obtaining resources for sidelink communication from a network (e.g., via downlink control information (DCI) of a physical channel (e.g., physical downlink control channel (PDCCH), etc.)).

[0034] Embodiments herein include various components, configurations, and processes for resource allocation to enable D2D or sidelink communication in one or more UE101, V-UE226, or other networked devices for direct communication between devices. In particular, these mechanisms include obtaining resources for sidelink communication via a network (e.g., from RAN / gNB110 to any of one or more devices 240).

[0035] UE101 or V2X UE226 can be one or more transmitting (Tx) UE240 that can obtain resources for its own transmission or resources from the network. Three different modes can be enabled for the network or gNB110 to provide resources for transmission to TxUE240: A) dynamic grant, B) configured grant type 1, and C) configured grant type 2. There are various differences among these three different resource grants to enable sidelink communication. A dynamic grant involves the network component (e.g., RAN110) providing one resource or separate resources for TxUE240 for, e.g., one transport block (TB), one transmission, or the data of one packet, which can be dynamically modified for subsequent instances of resource allocation.

[0036] The configured grant type 1 or type 2 can include scenarios where the network allocates periodic resources to the TxUE240 in a single-shot signaling. Thus, if the UE101 has some periodic traffic (e.g., traffic that occurs every second), the network can provide one-shot allocations of a one-second period multiple times or for multiple transmissions to device resources (e.g., sidelink transmission resources).

[0037] The configured grant type 1 can include upper layer signaling or high-level signals that may include radio resource control (RRC) signaling and are reduced to physical layer signals. In contrast, the configured grant type 2 can be a combination of upper layer signaling and lower layer signaling. At the upper layer, the network configures the device with the resource periodicity of the configured grant type 2 (e.g., every second or every other period), but does not change the grant and does not give the physical domain of the resources. Specifically, the configured grant type 2 allocates resources depending on the physical layer signaling of the physical channel, similar to the DCI signal of the PDCCH. The network can trigger the configured grant type 2 with DCI and can also release the configured grant type 2 either once or after a certain time.

[0038] The activation / deactivation (release) of the configured grant (configured grant type 2) can be through (via) DCI. However, DCI can also be used to provide and obtain dynamic grants in a direct way, which is similar to the configured grant (configured grant type 2). DCI provides resources, frequency resources, the location of the sidelink grant, or other resources to the topmost layer.

[0039] NR V2X supports dynamic grants, configured grant type 1, and configured grant type 2 for sidelink. For dynamic grants, the DCI can include, for example, a hybrid automatic repeat request (HARQ) process identifier (ID) / number and a new data indicator (NDI) as part of the DCI for the physical channel, as shown in the table of IE field 250. The DCI further indicates time resource allocation and frequency resource allocation according to the signaling format used for sidelink control information (SCI). Additionally, the start subchannel for initial transmission can be signaled within the DCI for sidelink communication.

[0040] An exemplary set of fields of the DCI information element (IE) 250 for configured grants (configured grant type 2) and dynamic grants can be communicated from gNB 110 to Tx-UE 240, for example, based on the technical specifications of 3GPP, TS38.212. The DCI field of the exemplary IE 250 can be based on DCI format 3_0. This DCI format, DCI format 3_0 for NR / 5G, can include one or more of a time gap, a HARQ process ID, a new data indicator (NDI), the lowest index of subchannel allocation to initial transmission, the allocation of frequency (domain) resources (FRA or FDRA) and time resources, the SCI format 0_1 field, the physical sidelink feedback channel (PSFCH) to HARQ feedback timing indicator, the physical uplink control channel (PUCCH) resource indicator, the configuration index or the configured grant index, etc.

[0041] DCI format 3_0 includes the DCI field 250 of gNB 110 for controlling the NR / 5G side link. For 5G Release 16 ultra-reliable low-latency communication (URLLC), the maximum and maximum number of uplink (UL) configured grants (CGs) per bandwidth part (BWP) that are supported can be, for example, 12. Thus, in various embodiments, a configured grant can include a UL configured grant but can also include a downlink (DL) semi-persistent grant. The fields of DCI format 3_0 (e.g., DCI field 250) can be utilized to release multiple configured grants with a single DCI. Further, a single DCI can be utilized to activate a single configured grant as well as to release multiple configured grants. Embodiments configure the release of multiple configured grants, but as discussed herein, it is also contemplated to release a single configured grant as well as to activate multiple configured grants.

[0042] In various other embodiments, the TxUE 101 can be configured to activate and deactivate one or more side link configured grants (e.g., configured grant type 2) for side link communication between devices 240 based on, for example, DCI format 3_0 including the IE field 250. Additional aspects relate to retransmission operations such as deriving a HARQ process ID involved in retransmitting a side link grant based on a dynamic grant, where each side link grant (dynamic grant / configured grant) is configured based on a different radio network temporary identifier (RNTI) and can be distinguished as to the type of grant, dynamic or configured grant, based on a different radio network temporary identifier (RNTI) regardless of whether it is based on a dynamic grant field. In other words, the configured grant continues to be configured based on the configured grant RNTI regardless of whether the transmission of the configured grant is based on a dynamic grant, and the dynamic grant on the dynamic grant RNTI continues to be configured with a different RNTI than the configured grant.

[0043] Other embodiments address, in particular, the calculation of the HARQ process ID for the configured grant for the retransmission operation and the alignment of the size of the DCI format configuration to the existing DCI format. These processes for sidelink communication may be based on DCI format 3_0 having a DCI field 250 for improving the operation objectives in sidelink communication, which generally include a configured grant, also generally referred to herein as a type 2 configured grant, and a dynamic grant, that is, a grant specifically based on DCI or direct control information from the network, including the reliability and efficiency of resource allocation.

[0044] In one embodiment, DCI format 3_0 (e.g., of DCI field 250) can provide a common DCI size for dynamic grants and configured grants. Further, some fields of DCI format 3_0 of DCI field 250 may be applicable only to dynamic grants, while others are applicable to configured grants. For example, the "HARQ process ID" field and the NDI field of the DCI IE of DCI can be used for resources particularly involved in dynamic grants. Other fields (e.g., the configured grant index field) may be applicable to configured grants. In one aspect, the modulation and coding scheme (MCS) and the redundancy version (RV) fields are not configured in DCI format 3_0 for dynamic grants and configured grants.

[0045] In a specific DCI field 250, a truncated table is further shown, including different categories of operations, and columns for activation, deactivation (release), and retransmission of configured grants, as well as applicability to dynamic grants, indicating how each field is applicable to a specific operation. The list of fields is given in the leftmost column, and these different operations are shown from left to right: activation of configured grants, deactivation of configured grants, retransmission of configured grants, and application of dynamic permission. For example, all fields except the index of the configured grant can be used for dynamic grants.

[0046] Specifically, as shown in the second and third columns, the configured grant can be obtained by different types of DCI, one for activation and the other for deactivation, and the fourth column is applicable to the retransmission of the configured grant.

[0047] Field 250 of the table in which the network provides resources for the configured grant. For example, periodicity of 1 second or other time periods. However, if it is not communicated normally, after one transmission opportunity for the configured grant, the retransmission of that TB can be initiated. The retransmission of the configured grant can be configured or generated using dynamic grants depending on the aspect. This resource allocation is the configuration of the dynamic grant but for the retransmission by the configured grant. The difference between the retransmission of the configured grant and the retransmission of the dynamic grant is that in the retransmission of the configured grant, the RNTI for the configured grant is still used. Specifically, two different RNTIs are used, one for the configured grant and one for the dynamic grant, and since they are different from each other, each sidelink grant can be distinguished by a different RNTI (e.g., sidelink (SL)-RNTI or other types). However, the data is for the retransmission of the configured grant, in the form of a dynamic grant but based on the RNTI for the configured grant, and thus is configured for the retransmission of the configured grant.

[0048] In one aspect, for both dynamic grants and retransmission of configured grants, the network indicates to gNB110 or via gNB110 to UE101 which grant is for which purpose via the HARQ process ID, and the last two columns of this row associated with the HARQ process ID field among the fields of Table 250 in the IE of DCI format 3_0 are "yes". However, the HARQ field is not required for activation / release of configured grants, which is indicated by "no" in the second and third columns of Table 250 of the HARQ process ID.

[0049] In another aspect, the SCI format 0_1 field of the frequency resource "allocation" (FRA) field is not used for release, but is used for activation of configured grants, retransmission of configured grants, and dynamic grants. Further, the configured grant index is used for activation of configured grants (indicated by "yes") to determine which configured grant should be activated, and the same applies to release of configured grants. For dynamic grants of retransmission of configured grants, the configured grant index is not used because multiple configured grant indexes can be configured. However, the configured grant index is used when activating a configured grant.

[0050] In one embodiment, a single sidelink configuration grant can be triggered by a single DCI to activate or release only the single sidelink configuration grant. The grant configuration may be indicated via RRC signaling and may also indicate periodicity, while the DCI can be used to activate or release the configuration grant. The gNB 110 communicates the DCI via a physical channel, for example, to activate or release the configuration grant at one or more network devices 240 by means of the configured DCI format 3_0. The activation of the configuration grant can be based on the verification of the DCI format 3_0 being achieved by the "HARQ process ID" field. For example, the UE 101 can process the DCI format 3_0 to determine whether all the HARQ process ID bits have the same state or value. For example, the UE 101 can determine whether the HARQ process ID field is configured with all zeros (0) as a predefined value, for example, and if so, operate to activate the configuration for sidelink communication based on the obtained DCI format 3_0.

[0051] In another embodiment, for the side link grant release (deactivation) operation, gNB 110 can configure the configured grant with DCI format 3_0, and UE 101 can process the configured grant from DCI format 3_0 based on the verification of DCI format 3_0 being achieved by both fields of "HARQ process ID" and "frequency (domain) resource allocation of the SCI format 0_1 field". UE 101 can be configured to determine whether to release / deactivate the side link grant based on the value of the HARQ process ID. For example, UE 101 can process DCI format 3_0 to determine whether all the HARQ process ID bits have the same state or value. For example, the HARQ process ID can have all zeros (0). The release can be controlled by a combination of the HARQ process ID and the SCI format 0_1 field of the "frequency resource allocation (FRA)" field, so that the HARQ process ID contains bits of a specific value, and the SCI format FRA field also contains bits of a specific value, and the release of the side link grant (e.g., the configured grant) can be initiated by UE 101. The SCI format 0_1 field of the "frequency resource allocation" can have bits in the same state (e.g., all 1s) as a different state from the HARQ process ID, for example. For example, when the HARQ process ID contains bits in the same first state (e.g., all zeros, 0) while the SCI format 0_1 field of the "frequency resource allocation" contains bits in the same second state (e.g., all 1s), the configured grant can be released or deactivated based on DCI format 3_0.

[0052] The SCI format 0_1 field of the "frequency resource allocation" is configured to indicate, for example, the start subchannels of the second and third resources and the number of subchannel sizes. Here, if the maximum number of resources is 2, for example, the SCI format 0_1 field has the SCI format [Number] bits, where N is the total number of subchannels in the resource pool. When the maximum number of resources is 3, the SCI format 0_1 field is [Number] bits, can have. For any integer value N, [Number] None of them is a power of 2. Specifically, this enables the configuration of the frequency resource indication value design to avoid being all 1 while maintaining its intended function. Thus, for example, being all 1 is reserved to indicate the release of the configured grant and can be defined as for the UE101 to process the deactivation of the configured grant.

[0053] In another embodiment, the network can trigger a plurality of sidelink configured grants for the UE101 via the gNB110 using the sidelink grant for sidelink communication in DCI format 3_0. The IE of the DCI can include one or more configured grant configurations, which can be based on the URLLC configuration or other configurations for sidelink communication. For example, a single DCI can be used to activate one configured grant. To activate multiple configured grants, multiple DCIs can be configured, and there are at least two embodiments for this, as further described below. In one, a single DCI or field of DCI format 3_0 can be used to release a single configured grant. Alternatively, or additionally, as a second case, a single DCI can be configured to release multiple configured grants in one shot (or one signaling resource transmission).

[0054] In one embodiment, for example, a single DCI may be configured to activate a single sidelink configuration grant or release one or more sidelink configuration grants. The configured grant index field can be avoided by using other fields of field 250 based on DCI format 3_0. To activate a configuration grant, for example, the HARQ process ID field of field 250 can be used as an indication indicating the grant index information of the sidelink configuration grant to be activated, as a way to indicate the index of the sidelink configuration grant to be activated. Although the size of the HARQ process ID field may not be specifically defined for the bit size, the network via gNB110 can define a variable size as size M. By doing so, the upper limit bit number can be indicated or configured as up to Log2M as the number of bits of the configuration grant. For example, 12, 10, or other numbers can be selected for the configuration of the configuration grant. Therefore, 4 bits can be used as M for the sidelink configuration grant to indicate 10, determined as Log2 of 10, and expressed as Log2M. This is an example, and thus, using this example, the HARQ process ID field can be 4 bits long.

[0055] In one embodiment, up to 16 can be used as M for the configuration grant configuration. Specifically, the HARQ process ID of DCI format 3_0 is configured in this way to indicate the configuration grant, and it can be shown which index of the sidelink configuration grant is activated. If the maximum configurable number of sidelink configuration grants is M, Log2M bits can be used to indicate the sidelink configuration grant index. If Log2M is shorter than the bit length of the HARQ process ID, the least significant (or most significant)

Number

[0056] In another embodiment, for example, as in the second case above, the HARQ process ID field can be used to indicate the simultaneous or parallel release of multiple configured grants. Here, an independent or separate table can be configured such that the HARQ process ID field can be used to indicate an entry in the table. Each table can have at least one entry, and each entry in the table includes a plurality of configured grant indexes. Thus, the HARQ process ID field can be configured to point to a table entry and indicate which entry in the table is being pointed to. If this entry includes a plurality of configured grant indexes, all associated configured grants are released. UE101 can be configured to process the release of multiple configured grants simultaneously using this mechanism (e.g., via one or more processors).

[0057] Thus, gNB110 can provide a release operation for multiple sidelink grants according to the DCI format 3_0 configuration. A separate table from Table 250 can be configured for each entry to indicate one or more sidelink configured grant indexes. If the bit length of the "HARQ process ID" field is represented as X, the table can have a maximum of 2 X entries. Thus, the "HARQ process ID" field can indicate a table entry of the associated sidelink configured grants to be released from activation or use in sidelink communication.

[0058] The methods described within this disclosure are illustrated and described herein as a series of operations or events, but it will be understood that the illustrated order of such operations or events should not be construed in a limiting sense. For example, some operations may occur in a different order than, and / or concurrently with, the operations or events illustrated and / or described herein, and apart from the operations or events illustrated and / or described herein. Additionally, not all of the illustrated operations may be required to implement one or more aspects or embodiments of the description herein. Further, one or more of the operations shown herein may be performed in one or more separate operations and / or stages. For ease of explanation, reference may be made to the above figures. However, the method is not limited to any particular embodiment or example provided within the disclosure and may be applied to any of the systems disclosed herein.

[0059] Referring to FIG. 3, illustrated is an exemplary process flow 300 for processing or configuring DCI format 3_0 for sidelink communication, particularly with respect to a single sidelink grant. At 302, for example, a UE or other networked device (e.g., V2X or network component) can receive DCI as a DCI format 3_0 configuration for processing operations related to a sidelink grant for sidelink communication. As described above, DCI format 3_0 includes fields (e.g., the fields of sample table 250 of FIG. 2) utilized for dynamic grants or configured grants (configured grant type 2).

[0060] At 304, after decoding the DCI, a determination is made as to whether the cyclic redundancy check (CRC) is masked with the SL-RNTI. If the determination 304 ends with an affirmative ("yes"), the process proceeds to 306 to process the dynamic grant. If the determination 304 ends with a negative ("no"), the process proceeds to determination 308 to further determine whether the NDI of the received DCI format 3_0 contains one or more zeros, or other predefined values.

[0061] If the determination 308 is "No", the process proceeds to 310 and processes the dynamic grant for retransmission (reTx) of the HARQ process ID within the DCI. If the determination 308 is "Yes", the process proceeds to an additional determination at 312 to determine whether the HARQ process ID contains bits equal to a pre-defined value or a first same value (e.g., all zeros, etc.). If the determination 312 is "No", the grant is ignored, but if it is "Yes", the process proceeds to 316 and a further additional determination is made to determine whether the frequency (domain) resource allocation (FDRA / FRA) contains bits equal to another pre-defined value or a second different same value (e.g., all ones, etc.).

[0062] If the determination at 316 with the FDRA (e.g., the SCI format 0_1 field including frequency (domain) resource allocation (FRA or FDRA) and time resource allocation) is "Yes", the release of the configured grant is executed at 320 based on the field of the DCI format 3_0 (e.g., 250). If the determination at 316 is "No", the activation of the configured grant is executed based on the field of the IE of the DCI within the physical channel. As a result, the process flow 300 ends by performing operations associated with and enabling the configuration of sidelink communication with a specific sidelink grant (e.g., dynamic grant and configured grant type 2 / II).

[0063] Referring to FIG. 4, illustrated is another exemplary process flow 400 for processing or configuring DCI format 3_0 for sidelink communication, particularly with respect to the configuration of a plurality of sidelink grants. Operations 402-410 of the process flow may be similar to operations 302-310 of the process flow 300 of FIG. 3 above. In particular, process flow 400 can be configured to utilize separate tables for a plurality of configured grant configurations, as discussed in this disclosure with an HARQ process ID field. Separate or distinct tables can be configured, and the HARQ process ID field can be utilized to indicate table entries. This table can have at least one entry, and each entry of the table includes a plurality of configured grant indices. The "HARQ process ID" field can be configured to indicate associated table entries of sidelink configured grants to be released from activation or use in sidelink communication.

[0064] At 402, a UE or other networked device (e.g., V2X or network component) can receive DCI as a DCI format 3_0 configuration for processing operations related to a sidelink grant for sidelink communication. As described above, DCI format 3_0 includes fields (e.g., fields of the sample table 250 of FIG. 2) that can be utilized for one or more dynamic grants or configured grants (configured grant type 2).

[0065] At 404, after decrypting the DCI, a determination is made as to whether the cyclic redundancy check (CRC) is masked with the SL-RNTI. If the determination 304 ends with an affirmative ("yes"), the process proceeds to 406 and processes the dynamic grant by indicating the configuration index (e.g., HARQ process ID field, or another field of DCI format 3_0) without using the configuration index field or using a field different from the configuration index field. If the determination 404 ends with a negative ("no"), the process proceeds to determination 408 to further determine whether the NDI of the received DCI format 3_0 contains one or more zeros, or other predefined values.

[0066] If the determination 408 is "no", the process proceeds to 410 and processes the dynamic grant for retransmission (reTx) of the HARQ process ID in the DCI by indicating the configuration index without using the configuration index field or using a field different from the configuration index field. If the determination 408 is "yes", the process proceeds to an additional determination at 412 to determine whether the frequency (domain) resource allocation (FDRA / FRA) contains bits equal to another predefined value, or a second different same value (e.g., all 1s, etc.). If the FDRA is equal to all 1s, this indicates releasing the configured grant at 420, and the configured grant index can be equal to, or equivalent to, the HARQ process ID field. For activation of the configured grant at 418, the HARQ process ID field determines which configured grant should be activated. The configured grant index is not used through these processes to avoid being used for the configured grant. Specifically, the process flow 400 in FIG. 4 avoids the configured grant index field and uses the FDRA field to distinguish between releasing and activating the configured grant(s).

[0067] Referring to FIG. 5, illustrated is an exemplary process flow 500 for determining a HARQ process ID for a configured grant. Embodiments where UE101, gNB110, or other network components perform processing via one or more processing components may, at 520, include determining a HARQ process ID for a configured grant via one or more processors. In some examples, the HARQ process ID can be calculated when transmission fails for a configured grant transmission / opportunity. The UE101 can then process a report, report it to the network, and request a retransmission via gNB110 by the network, and in response, the network can provide a retransmission grant.

[0068] Retransmission for a configured grant can be triggered with respect to a dynamic grant or by the function of a dynamic grant, and a HARQ process ID within the HARQ process ID field of DCI format 3_0 is also provided. A network component (e.g., gNB120) can indicate to the UE101 that, for example, a sidelink grant is for a configured grant with a transmission block (TB) associated with a HARQ process ID. The HARQ process ID may not be directly known to the network (e.g., gNB110). Since this is a configured grant, multiple transmissions can be associated with a sidelink grant, and thus gNB110 or other network components can calculate the HARQ process ID used by the TxUE (e.g., UE101 / 240).

[0069] In one embodiment, the HARQ process ID can be calculated to retransmit a configured grant based on a first RNTI via a dynamic grant with a different RNTI. The calculation of the HARQ process ID can be based on the periodicity of the configured grant at 520. For example, the periodicity of the configured grant can be in slot units or milliseconds. The calculation of the HARQ process ID at 530 can be further determined depending on whether the periodicity of the configured grant is in slot units or milliseconds.

[0070] In one embodiment, at 530, sidelink transmission can be defined with respect to a slot or in units of slots. For example, the HARQ process ID can be determined according to whether the grant periodicity is related to slots or milliseconds. Different from the uplink configured grant whose periodicity is a symbol, the periodicity of the sidelink configured grant can be at the slot level or at the millisecond level, similar to DL semi-persistent scheduling (SPS). In sidelink communication for a configured grant, since not all slots are available, there is a certain periodicity (e.g., 1 second or other duration), but after a certain period, the slot resources may not be available for UE sidelink transmission. Therefore, when the configured grant is provided in units of slots, the periodicity of the configured grant can be configured in units of logical slots instead of physical slots. A logical slot may mean all the slots available for sidelink transmission to ensure continuous time.

[0071] In another embodiment, when the configured grant periodicity is in milliseconds, the HARQ process ID for the configured grant can be determined / defined using the first logical slot after a certain period. In the case of milliseconds or the absolute value of time (e.g., milliseconds or seconds), the configured grant indicates that this configured grant is per second or some other duration, but after 1 second this resource may not be available for sidelink use and may be available, for example, for downlink transmission or for other resources. Thus, even though the configured grant provides periodicity in milliseconds (s), if the slot is not available for the configured grant, the first available or the first logical slot after the period can be defined for use. For example, after 1 second the resource becomes unavailable, and the first slot after that 1 second is used for the configured grant, which can constitute the handling of error cases. Alternatively, or additionally, sidelink transmission is interrupted over a certain period if the corresponding slot is not available for sidelink transmission. The HARQ process ID can accordingly be skipped.

[0072] In other embodiments, when the network node or gNB 110 allocates a configured grant, it can indicate the number of HARQ process IDs used, but does not necessarily provide the HARQ process ID values. For example, the gNB 110 can provide the UE device 101 with the total number to be used. For example, the network can indicate a number, such as, for example, two HARQ process IDs, or three HARQ process IDs, but does not necessarily indicate the exact numbers of the specific HARQ process IDs. Thus, in one embodiment, this is to accurately indicate which HARQ process IDs are associated with use for sidelink communication at the UE 101 for a certain configured grant. For example, the network can indicate that this configured grant can use, for example, HARQ process ID numbers 3, 4, 5. In this way, a bitmap, dataset, or table can be provided that indicates which HARQ process IDs are associated with the configured grant for use in sidelink communication.

[0073] Alternatively, or in addition, for example, the HARQ process ID, which is, for example, the numbers 3, 4, 5, can indicate a range of values by providing a range to be displayed with a minimum HARQ process ID of 3 and a maximum value of 5. In that way, a range is given here. Thus, rather than defining in various embodiments how many HARQ process IDs can be used for a particular set grant, there are two ways to determine the HARQ process ID instead of providing an exact HARQ process ID number.

[0074] Other embodiments include HARQ process ID calculation based on a grant HARQ ID derived from a direct frame number (DFN). When the HARQ process ID is based on the unit of the slot used for transmission, the grant HARQ ID can be determined according to the following expression, as defined in the Uu link. Grant HARQ ID = [floor(CURRENT_slot / periodicity)] modulo nrofHARQ - Processes. When the HARQ process ID is composed of milliseconds, the grant HARQ ID can be determined according to the following expression. Grant HARQ ID = [floor(CURRENT_slot × 10 / (numberofslotsPerFrame × periodicity))] modulo nrofHARQ - Processes. Here, "CURRENT_slot" may be equal to [DFN * numberofslotsPerFrame + slot number in the frame], or [SFN * numberofslotsPerFrame + slot number in the frame], where DFN is the direct frame number and SFN is the system frame number. The HARQ process ID calculation is applicable to both the sidelink and the Uu link with multiple active configured grants. Here, DFN is the direct frame number used for the sidelink, and SFN is the system frame number used for the main link from eNB 110 to UE 101. In this embodiment, since the sidelink is communication from UE device 101 to another UE device (e.g., 226), the DSN can be used to calculate the grant HARQ ID and further determine or derive the HARQ process ID using the grant HARQ ID.

[0075] The grant HARQ ID indicates which HARQ index is within the sidelink grant. For example, the grant can assign HARQ process IDs from a number between 3 and 5, and this grant HARQ ID can be mapped to the HARQ process ID. For example, a one-to-one mapping can be configured between the grant HARQ ID and the HARQ process ID. If the configured grant has a bitmap of HARQ process IDs, the HARQ process ID can be associated with the i-th bit with a value of 1 in the bitmap, where i is equal to the "grant HARQ ID". If the configured grant has a range of HARQ process IDs, the HARQ process ID can be equal to, for example, the sum of the "minimum HARQ process ID" configured with the "grant HARQ ID".

[0076] In other embodiments, at least one of the DCI format 3_0 size or the DCI format 3_1 size can be aligned with an existing DCI format size (e.g., slot, time, BWP, or other resource parameters). The DCI format 3_1 can be configured for the NR Uu link to control the LTE sidelink. The DCI format 3_0 and the DCI format 3_1 can be configured from the gNB 110 or the 5G network to control the UE device. The DCI format 3_0 is configured to control 5G sidelink communication, and the DCI format 3_1 is configured to control the LTE sidelink. In particular, the DCI format 3_0 and the DCI format 3_1 can be aligned based on the size of the existing DCI format size.

[0077] In one embodiment, the gNB 110 can be configured to match the size of DCI format 3_0 and / or DCI format 3_1 to an existing DCI format size according to a fixed size or a configurable size that can be dynamically configured for different times or different DCI transmissions. For example, DCI format 3_0 or DCI format 3_1 can be matched to a size that follows a fixed match with DCI format 0_0 or 0_1.

[0078] Alternatively, or in addition, one or more of DCI format 3_0 or DCI format 3_1 can be matched to a size that follows a fixed match with DCI format 0_2, which is itself configurable. While DCI format 0_0 can have the same size as DCI format 3_0, the size of DCI format 0_2 is configurable and can be smaller than the size of DCI format 0_0. Thus, the size of DCI format 3_0 can be configured to be the same as that of DCI format 0_2.

[0079] Alternatively, or in addition, the DCI format 3_0 or DCI format 3_1 size can be configured to match configurably to DCI format 0_0, DCI format 0_1, DCI format 0_2, or sequential combinations thereof. Thus, DCI format 3_0 or 3_1 can be defined fixedly or configurably based on another DCI format configuration.

[0080] Alternatively, or in addition, the size alignment of DCI format 3_0 or DCI format 3_1 can be configured based on the maximum number of reserved resources for sidelink transmission. For example, up to three resources can be allocated for sidelink, and the size of DCI format 3_0 or DCI format 3_1 can be different when three resources are reserved for sidelink and when two resources are reserved for sidelink. When the maximum number of reserved resources for sidelink transmission is two, DCI format 3_0 or DCI format 3_1 can be aligned to a smaller DCI format such as DCI format 0_2. When the maximum number of reserved resources for sidelink transmission is three, the DCI format 3_0 or DCI format 3_1 size can be aligned to DCI format 0_0 or 0_1.

[0081] Alternatively, or in addition, the DCI format 3_0 or DCI format 3_1 size can be aligned to an uplink grant starting from zero, but can also be aligned to the grants of downlink formats (e.g., DCI formats 1_0, 1_1, and 1_2) as an extension of the above embodiments and this specification.

[0082] Referring to FIG. 6, illustrated is an exemplary process flow 600 for aligning the size of DCI format 3_0 or format 3_1 to another DCI format for sidelink communication. The process flow 600 can start the alignment and includes aligning the sizes of DCI formats 0_0 and 0_1 to a common search space (CSS) at 610.

[0083] At 620, the process flow includes aligning DCI format 0_0 and 0_1 sizes to the UE-specific search space (USS). In an embodiment at 630, when DCI format 3_0 is monitored, DCI format 3_0 can be aligned to DCI format 0_0 / 0_1 by zero-padding. At 640, when DCI format 3_0 has a larger payload size, zero-padding can be performed on DCI format 0_0 / 0_1. Otherwise, zero-padding can be done on DCI format 3_0. When DCI format 3_1 is monitored but DCI format 3_0 is not monitored, alternatively or additionally, at 650, DCI format 3_1 can be aligned to DCI format 0_0 / 0_1 by zero-padding. At 660, when DCI format 3_1 has a larger payload size, zero-padding can be executed on DCI format 0_0 / 0_1. Otherwise, zero-padding can be performed on DCI format 3_1.

[0084] At 670, the process flow 600 further includes distinguishing DCI format 0_1 and 1_1 from DCI format 0_0 / 1_0. DCI formats 0_2 and 1_2 can be further distinguished from DCI format 0_0 / 1_0.

[0085] At 680, the process flow 600 further includes determining whether further DCI format payload size alignment is performed by re-alignment. If further alignment or re-alignment is desired, the DCI format 0_0 and 0_1 sizes can be re-aligned. When DCI format 3_0 is monitored, similar to the operation(s) at 630, DCI format 3_0 can be further aligned to DCI format 0_0 / 0_1 by zero-padding. When DCI format 3_1 is monitored but DCI format 3_0 is not monitored, similar to the operation(s) at 650, DCI format 3_1 can be further aligned to DCI format 0_0 / 0_1 by zero-padding. The DCI format 0_2 and 1_2 sizes can also be further aligned by re-alignment, similar to the DCI format 0_1 and 1_1 sizes.

[0086] Alternatively, or additionally, as described above, it will be understood that the illustrated order of such operations or events should not be construed in a limiting sense. For example, some operations may occur in a different order than, and / or concurrently with, the operations or events illustrated and / or described herein, separate from the operations or events illustrated and / or described herein. In one example, the re-alignment of DCI format 3_0 / DCI format 3_1 to DCI format 0_0 / 0_1 can be further aligned by zero-padding before or after the DCI format 0_2 and 1_2 sizes are re-aligned.

[0087] Referring to FIG. 7, illustrated is an example of a process flow of a network device or component (e.g., UE101, or other network component) that performs a sidelink grant operation to enable sidelink communication between UE devices.

[0088] At 710, the process flow 700 begins by receiving / processing downlink control information (DCI) for a sidelink configuration grant that enables NR sidelink communication.

[0089] At 720, the process flow 700 further includes determining whether to perform activation of a sidelink configuration grant, release of at least one sidelink configuration grant, or generation of a retransmission of at least one sidelink configuration grant based on one or more fields of the DCI format 3_0 configuration of the DCI.

[0090] In various embodiments herein, the process flow 700 can further include determining whether to generate a retransmission operation, or to generate a further determination as to whether to generate an activation operation or a release operation based on the new data indicator (NDI) field of the DCI format 3_0 configuration.

[0091] In various embodiments herein, the process flow 700 can further include generating an activation operation of a sidelink configuration grant based on the hybrid automatic repeat request (HARQ) process ID field of the DCI format 3_0 configuration.

[0092] In various embodiments herein, the process flow 700 can further include generating a release operation of a sidelink configuration grant based on the sidelink control information (SCI) format 0_1 field and the HARQ process ID field for frequency resource allocation of the DCI format 3_0 configuration.

[0093] In various embodiments of the present specification, the process flow 700 may further include releasing at least one sidelink configuration grant and activating at least one sidelink configuration grant based on one of the HARQ process ID field of the DCI format 3_0 configuration and the frequency (domain) resource allocation field of the sidelink control information (SCI) format 0_1. The HARQ process ID field can be equal to the sidelink configuration grant index, or can indicate an entry in a dataset, bitmap, or table that includes one or more sidelink configuration grant indexes.

[0094] In various embodiments of the present specification, the process flow 700 may further include determining whether to initiate a retransmission operation for retransmission of a sidelink configuration grant based on a field of the DCI format 3_0 configuration applicable to the sidelink dynamic grant. The sidelink configuration grant is based on a different RNTI than the sidelink dynamic grant.

[0095] Referring to FIG. 8, illustrated is a block diagram of a user equipment wireless communication device (UE) or other network device / component (e.g., a component of CN120 or gNB110) configured to perform sidelink communication according to various aspects described herein. The UE device 800 includes one or more processors 810 (e.g., one or more baseband processors) having a processing circuit and associated interface(s), a transceiver circuit 820 including a transmitter circuit and / or a receiver circuit (e.g., associated with one or more transmit chains and / or one or more receive chains, which may use common circuit components, separate circuit components, or combinations thereof), and a memory 830 (which can include any of a variety of storage media and can store instructions and / or data associated with the one or more processors 810 or the transceiver circuit 820).

[0096] In various embodiments (aspects) discussed herein, signals and / or messages can be generated and output for transmission, and / or transmitted messages can be received and processed. Depending on the type of signal or message being generated, outputting for transmission (e.g., by processor(s) 810, etc.) can include one or more of the following. Generation of a set of associated bits encoding the content of the signal or message, encoding (which can include, e.g., addition of a cyclic redundancy check (CRC) and / or encoding via one or more turbo codes, low density parity check (LDPC) codes, tail-biting convolutional codes (TBCC), Polar codes, etc.), scrambling (e.g., based on a scrambling seed), modulation (e.g., via one of binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), or some form of quadrature amplitude modulation (QAM)), and / or resource mapping (e.g., to a set of listed resources, to a set of time and frequency resources permitted for uplink transmission). Depending on the type of received signal or message, processing (e.g., by processor(s) 810) can include one or more of identification of physical resources associated with the signal / message, detection of the signal / message, deinterleaving of resource element groups, demodulation, descrambling, and / or decoding.

[0097] As used herein, the term "processor" can refer to substantially any computing processing unit or device, including, but not limited to, a single-core processor, a single processor with software multithreading capabilities, a multi-core processor, a multi-core processor with software multithreading capabilities, a multi-core processor with hardware multithreading technology, a parallel platform, and a parallel platform with distributed shared memory. Further, a processor can refer to an integrated circuit, an application-specific integrated circuit, a digital signal processor, a field programmable gate array, a programmable logic controller, a complex programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to execute the functions and / or processes described herein. The processor can utilize nanoscale architectures including, but not limited to, molecular dot and quantum dot-based transistors, switches, and gates, to optimize space usage or improve the performance of mobile devices. The processor can also be implemented as a combination of computing processing units.

[0098] Embodiments can include subject matter such as a method, means for performing operations or blocks of a method, a machine (e.g., a processor having a memory, an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), etc.), that causes the operations of the method or the operations of the apparatus or system to be performed by the machine, and at least one machine-readable medium including instructions to perform simultaneous communications using multiple communication techniques according to the embodiments and examples described herein.

[0099] The first embodiment is an apparatus configured to be used in a networked device or user equipment (UE) for new radio (NR) side-link communication. The apparatus comprises a processing circuit configured to process downlink control information (DCI) to enable NR side-link communication based on one or more side-link configuration grants, and to determine whether to configure at least one of an activation operation, a release operation, or a retransmission operation of the one or more side-link configuration grants based on a DCI format 3_0 configuration of the DCI for NR side-link communication and one or more fields of the DCI format 3_0 configuration.

[0100] The second embodiment may include the first embodiment, and the processing circuit is further configured to configure an activation operation of the one or more side-link configuration grants based on a hybrid automatic repeat request (HARQ) process ID field of the DCI format 3_0 configuration.

[0101] The third embodiment may include the first or second embodiment, and the processing circuit is further configured to configure a release operation of the one or more side-link configuration grants based on a first field and a second field of the DCI format 3_0 configuration, the first field including a HARQ process ID field and the second field including a frequency (domain) resource allocation field of a side-link control information (SCI) format 0_1.

[0102] The fourth embodiment can include any one or more of the first to third embodiments. The processing circuit releases one or more sidelink configuration grants in response to a HARQ process ID field of DCI format 3_0 configuration indicating which sidelink configuration grant index should be released, and is further configured to release a plurality of sidelink configuration grants in response to a bitmap, table, or dataset including one or more sidelink configuration grant indexes and a HARQ process ID field including one or more entries of the bitmap, table, or dataset.

[0103] The fifth embodiment can include any one or more of the first to fourth embodiments. The processing circuit is further configured to release one or more sidelink configuration grants in response to a HARQ process ID field of DCI format 3_0 configuration including bits of the same first state and an SCI format 0_1 field for frequency resource allocation of DCI format 3_0 configuration including all bits of the same second state different from the same first state.

[0104] The sixth embodiment can include any one or more of the first to fifth embodiments. The processing circuit is further configured to determine whether to generate a retransmission operation, or to generate a further determination of whether to perform an activation operation or a release operation based on a new data indicator (NDI) field of DCI format 3_0 configuration.

[0105] The seventh embodiment can include any one or more of the first to sixth embodiments. The processing circuit is further configured to generate a retransmission operation of one or more sidelink configuration grants based on that one or more fields are applicable to a sidelink dynamic grant, and the one or more fields include at least one of a HARQ process ID field or a new data indicator (NDI) field of DCI format 3_0 configuration.

[0106] The eighth embodiment can include any one or more of the first to seventh embodiments, and the processing circuit is configured to be based on one or more logical slots and based on the period of the configured grant periodicity in milliseconds to ensure continuous time for NR sidelink communication in response to the periodicity of the configured grant based on the slot, and further configured to determine a HARQ process ID based on the first logical slot after the period of the periodicity of the configured grant for NR sidelink communication in response to the periodicity of the configured grant based on the slot.

[0107] The ninth embodiment can include any one or more of the first to eighth embodiments, and the processing circuit is further configured to determine a plurality of HARQ process IDs associated with one or more sidelink configured grants in DCI format 3_0 configuration based on a bitmap or a HARQ process ID range.

[0108] The tenth embodiment can include any one or more of the first to ninth embodiments, and the processing circuit is further configured to derive a grant HARQ ID based on a current_slot variable derived from a direct frame number (DFN) or a system frame number (SFN), and determine a HARQ process ID from the grant HARQ ID, where the grant HARQ ID and the HARQ process ID include a one-to-one mapping therebetween.

[0109] The 11th embodiment can include any one or more of the 1st to 10th embodiments, and the processing circuit further configures at least one of the DCI format 3_0 size or the DCI format 3_1 size to match a legacy DCI format size based on a fixed size or a configurable size based on the maximum number of reserved resources for DCI format 0_0, DCI format 0_1, DCI format 0_2, DCI format 1_0, DCI format 1_1, DCI format 1_2, or NR sidelink communication. In response to a legacy DCI format size including DCI format 0_0 or DCI format 0_1, the processing circuit is further configured to align at least one of the DCI format 3_0 size or the DCI format 3_1 size by zero-padding.

[0110] The 12th embodiment can be a device configured to be used in a user equipment (UE) or a service consumer device for a new radio (NR) network, the device receiving downlink control information (DCI) about a sidelink configuration grant enabling NR sidelink communication and determining whether to activate a sidelink configuration grant, release at least one sidelink configuration grant, or generate a retransmission for at least one sidelink configuration grant based on one or more fields of the DCI in the DCI format 3_0 configuration, and the device can include one or more processors.

[0111] The 13th embodiment can include the 12th embodiment, and the one or more processors are further configured to activate a sidelink configuration grant in response to the HARQ process ID field of the DCI format 3_0 configuration being configured with all zeros.

[0112] The 14th embodiment can include any one or more of the 12th to 13th embodiments, and one or more processors are further configured to release a sidelink configuration grant in response to that all HARQ process ID fields in the DCI format 3_0 configuration are composed of zeros and all SCI format 0_1 fields for frequency resource allocation in the DCI format 3_0 configuration are composed of ones.

[0113] The 15th embodiment can include any one or more of the 12th to 14th embodiments, and one or more processors are further configured to determine a HARQ process ID based on whether the periodicity of the configuration grant is based on either a slot or a millisecond.

[0114] The 16th embodiment can include any one or more of the 12th to 15th embodiments, and one or more processors are further configured to derive one or more HARQ process IDs associated with a sidelink configuration grant in the DCI format 3_0 configuration based on a bitmap or a HARQ process ID range.

[0115] The 17th embodiment is a computer-readable storage device storing executable instructions, where the executable instructions, in response to execution, cause one or more processors of a user equipment (UE) on a new radio (NR) network to perform operations, and the operations include receiving downlink control information (DCI) for a sidelink configuration grant that enables NR sidelink communication, and determining whether to activate a sidelink configuration grant, release at least one sidelink configuration grant, or generate a retransmission of at least one sidelink configuration grant based on one or more fields in the DCI format 3_0 configuration of the DCI, and can be a computer-readable storage device.

[0116] The 18th embodiment may include the 17th embodiment, and the operations include determining whether to generate a retransmission operation, or to generate a further determination of which of the activation operation and the release operation to generate, based on the new data indicator (NDI) field of the DCI format 3_0 configuration, and generating an activation operation of the sidelink configuration grant based on the hybrid automatic repeat request (HARQ) process ID field of the DCI format 3_0 configuration, and further generating a release operation of the sidelink configuration grant based on the sidelink control information (SCI) format 0_1 field and the HARQ process ID field for the frequency resource allocation of the DCI format 3_0 configuration.

[0117] The 19th embodiment includes any one or more of the 17th to 18th embodiments, and the operations further include releasing at least one or more sidelink configuration grants and activating at least one or more sidelink configuration grants based on the HARQ process ID field of the DCI format 3_0 configuration and the frequency (domain) resource allocation field of the sidelink control information (SCI) format 0_1, where the HARQ process ID field indicates an entry of a dataset, bitmap, or table equal to the sidelink configuration grant index or including one or more sidelink configuration grant indexes.

[0118] The 20th embodiment includes any one or more of the 17th to 19th embodiments, and the operations further include determining whether to start a retransmission operation for retransmission of the sidelink configuration grant based on the fields of the DCI format 3_0 configuration applicable to the sidelink dynamic grant, where the sidelink configuration grant is based on a different RNTI from the sidelink dynamic grant.

[0119] As a further example, 1. The following describes some details of some of the remaining identified tasks, including DCI content, DCI format size alignment, sidelink HARQ feedback reports to the gNB, multiplexing of multiple sidelink HARQs, and HARQ process ID determination for configured grants.

[0120] 2. DCI Content: DCI format 3_0 is defined for the gNB that schedules NR sidelink transmissions. The fields of DCI format 3_0 include a time gap, HARQ process ID, NDI, minimum subchannel index for initial transmission, frequency and time resource allocation SCI format 0_1 fields, PSFCH-to-HARQ feedback timing indicator, and configuration index. The bit sizes of the time gap, HARQ process ID, and configuration index fields are not specified. The time gap field provides an index to a slot offset table given by a higher layer parameter. This slot offset table can have a maximum of 8 entries, and thus 3 bits are used for this field. Similar to NR Uu, up to 16 sidelink HARQ processes can be supported, and 4 bits are used for the HARQ process ID field. In LTE V2X, up to 8 sidelink SPS configurations are supported. In NR V2X, up to 8 configured grants are supported. Thus, one embodiment is to use 3 bits for the configuration index field.

[0121] Proposal 1: In DCI format 3_0, the field for the HARQ process ID has 4 bits, the field for the time gap has 3 bits, and the field for the configuration index has 3 bits. DCI format 3_0 is used to activate or release a type 2 sidelink configuration grant. Similar to the NR type 2 uplink configuration grant, the activation or release of the type 2 sidelink configuration grant can be verified by a special field in DCI format 3_0. For example, the HARQ process ID field in DCI format 3_0 can be all 0s to activate or release a type 2 sidelink configuration grant. Furthermore, it is assumed that the valid SCI format 0_1 field for frequency resource allocation cannot be all 1s. Therefore, the distinction between the activation and release of the type 2 sidelink configuration grant is achieved by checking whether the SCI format 0_1 field for frequency resource allocation is all 1s. If this field is all 1s, DCI format 3_0 is considered to release the type 2 sidelink configuration grant. Otherwise, DCI format 3_0 is considered to activate the type 2 sidelink configuration grant.

[0122] Proposal 2: To verify the activation of the type 2 sidelink configuration grant in DCI format 3_0, the HARQ process ID is all 0s, and the SCI format 0_1 field for frequency resource allocation is not all 1s. To verify the release of the type 2 sidelink configuration grant in DCI format 3_0, the HARQ process ID is not all 0s, and the SCI format 0_1 field for frequency resource allocation is all 1s.

[0123] 2.2 DCI Format Size Alignment: The size of DCI format 3_0 is aligned with the size of one of the existing NR DCI formats. There is no limitation on which existing NR DCI format to align DCI format 3_0 with. It is beneficial to align DCI format 3_0 with an existing DCI format having a similar payload size. In the known content of DCI format 3_0, DCI format 3_0 has a payload size similar to that of DCI format 0_0. The alignment of the payload size between DCI format 3_0 and DCI format 0_0 can be achieved by zero-padding.

[0124] Proposal 3: NR DCI format 3_0 can align its payload size with NR DCI format 0_0 via zero-padding.

[0125] 2.5 HARQ Process ID Determination for Configured Grants: In NR Uu, an uplink configured grant can have multiple HARQ processes, and the number of HARQ processes is part of the configuration of the uplink configured grant. This same scheme should be extended to sidelink configured grants, i.e., multiple HARQ processes are assigned to sidelink configured grants. This increases the throughput of sidelink transmissions. Sidelink dynamic grants are used to provide resources for retransmission of configured grants. Since the HARQ process ID is included in this dynamic grant, the gNB needs to calculate the HARQ process ID for the dynamic grant for retransmission. Similar to Uu, the HARQ process ID for sidelink is obtained based on the sidelink slot index of the initial sidelink transmission, the periodicity of the configured grant, and the number of HARQ processes in the sidelink configured grant. Since multiple configured grant configurations are supported for sidelink, an accurate HARQ process ID should be assigned to each configured grant to avoid ambiguity of the HARQ process ID. Therefore, the sidelink configured grant configuration includes the associated HARQ process ID.

[0126] Proposal 11: The HARQ process ID of the configured grant is determined by the physical resources of the first sidelink transmission. The sidelink configured grant configuration includes its associated HARQ process ID.

[0127] Conclusion Proposal: Proposal 1: In DCI format 3_0, the field of the HARQ process ID has 4 bits, the field of the time gap has 3 bits, and the field of the configuration index has 3 bits. Proposal 2: To verify the activation of the type 2 sidelink configured grant in DCI format 3_0, the HARQ process ID is all 0, and the SCI format 0_1 field of the frequency resource allocation is not all 1. To verify the release of the type 2 sidelink configured grant in DCI format 3_0, the HARQ process ID is all 0, and the SCI format 3_0 field of the frequency resource allocation is all 1. Proposal 3: The payload size of NR DCI format 3_0 should be aligned with NR DCI format 0_0 via zero-padding. Proposal 11: The HARQ process ID of the configured grant is determined by the physical resources of the first sidelink transmission. The sidelink configured grant configuration includes its associated HARQ process ID.

[0128] Furthermore, the various aspects or features described herein can be implemented as a method, apparatus, or article of manufacture using standard programming and / or engineering techniques. As used herein, the term "article of manufacture" is intended to encompass any computer program accessible from any computer-readable device, carrier, or medium. For example, computer-readable media can include, but are not limited to, magnetic storage devices (e.g., hard disks, floppy disks, magnetic strips, etc.), optical disks (e.g., compact disks (CDs), digital versatile disks (DVDs), etc.), smart cards, and flash memory devices (e.g., EPROMs, cards, sticks, key drives, etc.). Additionally, the various storage media described herein can represent one or more devices and / or other machine-readable media for storing information. The term "machine-readable media" can include, but is not limited to, a wireless channel and various other media that can store, contain, and / or transport instructions and / or data. Further, a computer program product can include a computer-readable medium having one or more instructions or codes operable to cause a computer to perform the functions described herein.

[0129] A communication medium includes computer-readable instructions, data structures, program modules, or other structured or unstructured data in a modulated data signal, such as a carrier wave or other transport mechanism, and includes any information delivery or transport medium. A "modulated data signal" or signals refers to a signal having one or more characteristics set or changed to encode information in one or more signals. By way of example and not limitation, communication media includes wired media such as a wired network or direct wired connection, as well as wireless media such as acoustic, RF, infrared, and other wireless media.

[0130] An exemplary memory medium can be coupled to a processor such that the processor can read information from, and write information to, the memory medium. Alternatively, the memory medium can be integral with the processor. Further, in some aspects, the processor and the memory medium can be present in an ASIC. Additionally, the ASIC can be present in a user terminal. Alternatively, the processor and the memory medium can be present as separate components within the user terminal. Additionally, in some aspects, the processes and / or operations of a method or algorithm can exist as one or any combination or code and / or instructions on a machine-readable medium and / or a computer-readable medium, which can be incorporated in a computer program product.

[0131] In this regard, although the disclosed subject matter has been described in connection with various embodiments and corresponding figures, other similar embodiments can be used where applicable, or modifications and additions can be made to the described embodiments without departing therefrom for performing the same, similar, alternative, or alternative functions of the disclosed subject matter. Accordingly, the disclosed subject matter should not be limited to any single embodiment described herein, but rather should be construed in breadth and scope in accordance with the following appended claims.

[0132] Specifically, with respect to the various functions performed by the above-described components (such as assemblies, devices, circuits, systems, etc.), the terms used to describe such components (including references to "means") are intended to correspond to any component or structure (e.g., functionally equivalent) that performs the specific function of the described component, even if not structurally equivalent to the disclosed structure that performs the function in the exemplary implementations of the present disclosure shown herein. Further, although a particular feature may be disclosed with respect to only one of several implementations, such feature can be combined with one or more other features of one or more other implementations as may be desirable and advantageous for any given or particular application. Appendices 1. The following describes some details of several of the remaining specified tasks, including DCI content, DCI format size alignment, sidelink HARQ feedback reports to the gNB, multiplexing of multiple sidelink HARQs, and HARQ process ID determination for configured grants. 2. DCI Content: DCI format 3_0 is defined for gNB scheduling of NR sidelink transmissions. The fields of DCI format 3_0 include a time gap, HARQ process ID, NDI, minimum subchannel index for initial transmission, frequency and time resource allocation SCI format 0_1 fields, PSFCH-to-HARQ feedback timing indicator, and configuration index. The bit sizes of the time gap, HARQ process ID, and configuration index fields are not specified. The time gap field provides an index to a slot offset table given by a higher layer parameter. This slot offset table can have up to 8 entries, and thus 3 bits are used for this field. Similar to NR Uu, up to 16 sidelink HARQ processes can be supported, and 4 bits are used for the HARQ process ID field. In LTE V2X, up to 8 sidelink SPS configurations are supported. In NR V2X, up to 8 configured grants are supported. Thus, one embodiment is to use 3 bits for the configuration index field. Proposal 1: In DCI format 3_0, the field for the HARQ process ID has 4 bits, the field for the time gap has 3 bits, and the field for the configuration index has 3 bits. DCI format 3_0 is used to activate or release a type 2 sidelink configuration grant. Similar to the NR type 2 uplink configuration grant, the activation or release of the type 2 sidelink configuration grant can be verified by a special field in DCI format 3_0. For example, the HARQ process ID field in DCI format 3_0 can be all 0s to activate or release the type 2 sidelink configuration grant. Furthermore, it is assumed that the valid SCI format 0_1 field for frequency resource allocation cannot be all 1s. Therefore, the distinction between the activation and release of the type 2 sidelink configuration grant is achieved by checking whether the SCI format 0_1 field for frequency resource allocation is all 1s. If this field is all 1s, DCI format 3_0 is considered to release the type 2 sidelink configuration grant. Otherwise, DCI format 3_0 is considered to activate the type 2 sidelink configuration grant. Proposal 2: To verify the activation of the type 2 sidelink configuration grant in DCI format 3_0, the HARQ process ID is all 0s and the SCI format 0_1 field for frequency resource allocation is not all 1s. To verify the release of the type 2 sidelink configuration grant in DCI format 3_0, the HARQ process ID is all 0s and the SCI format 0_1 field for frequency resource allocation is all 1s. 2.2 DCI Format Size Alignment: The size of DCI Format 3_0 is aligned with the size of one of the existing NR DCI formats. There is no limitation on which existing NR DCI format DCI Format 3_0 is aligned with. It is beneficial to align DCI Format 3_0 with an existing DCI format having a similar payload size. In the known content of DCI Format 3_0, DCI Format 3_0 has a payload size similar to that of DCI Format 0_0. The alignment of the payload size between DCI Format 3_0 and DCI Format 0_0 can be achieved by zero-padding. Proposal 3: NR DCI Format 3_0 can align its payload size with NR DCI Format 0_0 via zero-padding. 2.5 HARQ Process ID Determination for Set-up Grants: In NR Uu, an uplink set-up grant may have multiple HARQ processes, and the number of HARQ processes is part of the configuration of the uplink set-up grant. This same scheme should be extended to sidelink set-up grants, i.e., multiple HARQ processes are assigned to sidelink set-up grants. This increases the throughput of sidelink transmissions. The sidelink dynamic grant is used to provide resources for retransmissions of set-up grants. Since the HARQ process ID is included in this dynamic grant, the gNB needs to calculate the HARQ process ID for the dynamic grant for retransmissions. Similar to Uu, the HARQ process ID for sidelink is obtained based on the sidelink slot index of the initial sidelink transmission, the periodicity of the set-up grant, and the number of HARQ processes in the sidelink set-up grant. Since multiple set-up grant configurations are supported for sidelink, an accurate HARQ process ID should be assigned to each set-up grant to avoid ambiguity of the HARQ process ID. Therefore, the sidelink set-up grant configuration includes the associated HARQ process ID. Proposal 11: The HARQ process ID of the configured grant is determined by the physical resources of the first sidelink transmission. The sidelink configured grant configuration includes its associated HARQ process ID. Conclusion Proposals: Proposal 1: In DCI format 3_0, the field for the HARQ process ID has 4 bits, the field for the time gap has 3 bits, and the field for the configuration index has 3 bits. Proposal 2: To verify the activation of the type 2 sidelink configured grant in DCI format 3_0, the HARQ process ID is all 0s, and the SCI format 0_1 field of the frequency resource allocation is not all 1s. To verify the release of the type 2 sidelink configured grant in DCI format 3_0, the HARQ process ID is all 0s, and the SCI format 3_0 field of the frequency resource allocation is all 1s. Proposal 3: The payload size of NR DCI format 3_0 should be aligned with NR DCI format 0_0 via zero-padding. Proposal 11: The HARQ process ID of the configured grant is determined by the physical resources of the first sidelink transmission. The sidelink configured grant configuration includes its associated HARQ process ID.

Claims

1. configured to be used in a networked device or user equipment (UE) for new radio (NR) sidelink communication, a processing circuit, processing downlink control information (DCI) including DCI format 3_0 for processing operations related to one or more sidelink configuration grants for the NR sidelink communication, determining to release the one or more sidelink configuration grants based on one or more fields of the DCI for the NR sidelink communication, the one or more fields including a hybrid automatic repeat request (HARQ) process ID field indicating a table entry, the table entry including one or more configuration grant indexes respectively corresponding to the one or more sidelink configuration grants, a processing circuit configured as such, An apparatus comprising.

2. The apparatus according to claim 1, wherein the processing circuit is further configured to configure an activation operation of the one or more sidelink configuration grants based on a HARQ process ID field of another DCI.

3. The apparatus according to claim 1, wherein the one or more fields include a frequency domain resource allocation (FDRA) field of sidelink control information (SCI) format 0_1.

4. The apparatus according to claim 1, wherein the processing circuit is further configured to determine to release the one or more sidelink configuration grants in response to a frequency domain resource allocation (FDRA) field of SCI format 0_1 in which all bits are in the same state.

5. The apparatus according to claim 4, wherein the processing circuit is further configured to determine to release the one or more sidelink configuration grants based on a new data indicator (NDI) field of the DCI.

6. The apparatus according to claim 1, wherein the processing circuit is further configured to determine a HARQ process ID based on one or more logical slots in response to the periodicity of the configuration grant based on a slot, or based on the first logical slot after a period of the periodicity of the configuration grant for the NR sidelink communication in response to the periodicity of the configuration grant based on milliseconds.

7. The apparatus according to claim 1, wherein the processing circuit is further configured to determine a plurality of HARQ process IDs associated with the one or more sidelink configuration grants based on a bitmap or a HARQ process ID range.

8. The apparatus according to claim 1, wherein the processing circuit is further configured to derive a grant HARQ ID based on a current_slot variable derived from a direct frame number (DFN) or a system frame number (SFN), and to determine a HARQ process ID from the grant HARQ ID, wherein the grant HARQ ID and the HARQ process ID include a one-to-one mapping therebetween.

9. The processing circuit is further configured to align at least one of a DCI format 3_0 size or a DCI format 3_1 size to a legacy DCI format size based on a fixed size or a configurable size based on a maximum number of reserved resources for DCI format 0_0, DCI format 0_1, DCI format 0_2, DCI format 1_0, DCI format 1_1, DCI format 1_2, or the NR sidelink communication, and in response to the legacy DCI format size including DCI format 0_0 or DCI format 0_1, the processing circuit is further configured to align the at least one of the DCI format 3_0 size or the DCI format 3_1 size by zero-padding. The apparatus according to claim 1.

10. An apparatus configured to be used in a user equipment (UE) or a service consumer device for a new radio (NR) network, receiving downlink control information (DCI) for processing operations related to one or more sidelink configuration grants for NR sidelink communication, One or more processors configured to determine to release the one or more sidelink configured grants based on one or more fields of the DCI DCI format 3_0 configuration, wherein the one or more fields include a hybrid automatic repeat request (HARQ) process ID field indicating a table entry, and the table entry includes one or more configured grant indexes respectively corresponding to the one or more sidelink configured grants, the apparatus comprising one or more processors.

11. The apparatus according to claim 10, wherein the one or more processors are further configured to activate the sidelink configured grant in response to all HARQ process ID fields of another DCI format 3_0 configuration being configured with zeros.

12. The apparatus according to claim 10, wherein the one or more processors are further configured to release the one or more sidelink configured grants in response to all SCI format 0_1 fields for a frequency domain resource allocation (FDRA) field of the DCI format 3_0 configuration being configured with ones.

13. The apparatus according to claim 10, wherein the one or more processors are further configured to determine a HARQ process ID based on whether the periodicity of the configured grant is based on a slot or a millisecond.

14. The apparatus according to claim 10, wherein the one or more processors are further configured to derive one or more HARQ process IDs associated with one of the one or more sidelink configured grants based on a bitmap or a HARQ process ID range.

15. A computer-readable storage device storing executable instructions, the executable instructions causing, in response to execution, one or more processors of a user equipment (UE) on a new radio (NR) network to perform operations, the operations including processing downlink control information (DCI) for one or more sidelink configured grants for NR sidelink communication, and Determining to release the one or more sidelink configured grants based on one or more fields of the DCI format 3_0 configuration of the DCI, wherein the one or more fields include a hybrid automatic repeat request (HARQ) process ID field indicating a table entry, and the table entry includes one or more configured grant indexes respectively corresponding to the one or more sidelink configured grants, and a computer-readable storage device including the same.

16. The operation is Determining whether to generate a retransmission, activation operation, or release operation based on a new data indicator (NDI) field of the DCI format 3_0 configuration, Generating the activation operation of the sidelink configured grant based on a HARQ process ID field of the DCI format 3_0 configuration, or Generating the release operation of the sidelink configured grant based on a sidelink control information (SCI) format 0_1 field for frequency resource allocation of the DCI format 3_0 configuration and the HARQ process ID field, The computer-readable storage device according to claim 15, further including the same.

17. The operation is Further including determining whether to start a retransmission operation for retransmission of the sidelink configured grant based on a field of the DCI format 3_0 configuration applicable to the sidelink dynamic grant, wherein the sidelink configured grant is based on a different RNTI from the sidelink dynamic grant, and the computer-readable storage device according to claim 15.

Images