Collision handling and HARQ-ACK codebook generation in sidelink carrier aggregation

Abstract

An apparatus and system supporting sidelink carrier aggregation are described. Mechanisms for type 1 and type 2 sidelink hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook generation for carrier aggregation are described. The sidelink carrier index is included in a downlink control information (DCI) format 300 received by the user equipment. The sidelink carrier index indicates a sidelink carrier for resource allocation of a physical sidelink shared channel (PSSCH) and a physical sidelink control channel (PSCCH). And generating a HARQ-ACK (Hybrid Automatic Repeat Request Acknowledgement) for the sidelink serving cell, and concatenating sidelink HARQ-ACK information bits according to an ascending order of the sidelink serving cell index. Collision handling and prioritization between sidelink transmission and reception as well as uplink transmissions during sidelink carrier aggregation are described.

Description

[0001] Priority claim

[0002] This application claims the benefit of priority to U.S. Provisional Patent Application Serial No. 63 / 393,726 filed on July 29, 2022 and U.S. Provisional Patent Application Serial No. 63 / 397,269 filed on August 11, 2022, each of which is incorporated herein by reference in its entirety. Technical Field

[0003] Embodiments relate to communications in 3GPP networks. In particular, some embodiments relate to sidelink communications in next generation networks. Background Art

[0004] As the types of electronic devices using network resources and the amount of data and bandwidth used by various applications (e.g., video streaming) operating on the electronic devices increase, the use and complexity of wireless systems also increase. As expected, the emergence of any new technology has many problems, including the complexity associated with the use of sidelink communications. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] In the accompanying drawings, which are not necessarily drawn to scale, like numbers may describe similar components in different views. Like numbers with different letter suffixes may represent different instances of similar components. The accompanying drawings generally illustrate various embodiments discussed in this document by way of example and not limitation.

[0006] Figure 1A An architecture of a network according to some aspects is shown.

[0007] Figure 1B A non-roaming 5G system architecture is shown according to some aspects.

[0008] Figure 1C A non-roaming 5G system architecture is shown according to some aspects.

[0009] Figure 2 A block diagram of a communication device according to some embodiments is shown.

[0010] Figure 3 Sidelink Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) reporting is shown in accordance with some embodiments.

[0011] Figure 4 Type 1 sidelink HARQ-ACK codebook generation according to some embodiments is shown.

[0012] Figure 5 A Type 1 sidelink HARQ-ACK codebook on a physical uplink control channel (PUCCH) is shown in accordance with some embodiments.

[0013] Figure 6 Prioritization of PUCCH with sidelink HARQ-ACK feedback and Physical Sidelink Feedback Channel (PSFCH) transmissions is shown in accordance with some embodiments.

[0014] Figure 7 Prioritization between Physical Sidelink Shared Channel (PSSCH) / Physical Sidelink Control Channel (PSCCH) transmission and PSFCH reception according to some embodiments is shown.

[0015] Figure 8 Prioritization between PSSCH / PSCCH transmission and PSFCH reception according to some embodiments is shown.

[0016] Fig. 9 Prioritization between uplink (UL) transmissions and sidelink (SL) transmissions in more than one sidelink carrier is shown in accordance with some embodiments.

[0017] Fig.10 Prioritization between UL and SL transmissions in more than one sidelink carrier is shown according to some embodiments.

[0018] Fig.11 Prioritization between UL transmission, SL sending and SL reception according to some embodiments is shown.

[0019] Fig.12 Another prioritization between UL transmission, SL sending and SL receiving according to some embodiments is shown.

[0020] Fig.13 A process for providing sidelink HARQ-ACK information according to some embodiments is shown.

[0021] Fig.14 A process for prioritizing transmissions or receptions, including sidelink transmissions or receptions, is shown in accordance with some embodiments. DETAILED DESCRIPTION

[0022] The following description and accompanying drawings fully illustrate specific embodiments to enable those skilled in the art to implement them. Other embodiments may incorporate structural changes, logical changes, electrical changes, process changes, and other changes. Portions and features of some embodiments may be included in or substituted with portions and features of other embodiments. The embodiments set forth in the claims encompass all available equivalents of those claims.

[0023] Figure 1AThe architecture of a network according to some aspects is shown. The network 140A includes 3GPP LTE / 4G and NG network functions, which can be extended to 6G and later generation functions. Therefore, although 5G is mentioned herein, it should be understood that this will be able to be extended to 6G (and beyond) structures, systems, and functions. The network functions can be implemented as discrete network elements on dedicated hardware, as software instances running on dedicated hardware, and / or as virtualized functions instantiated on an appropriate platform (e.g., dedicated hardware or cloud infrastructure).

[0024] Network 140A is shown to include user equipment (UE) 101 and UE 102. UE 101 and 102 are shown as smart phones (e.g., handheld touch screen mobile computing devices that can connect to one or more cellular networks), but can also include any mobile or non-mobile computing devices, such as portable (laptop) or desktop computers, wireless phones, drones, or any other computing devices that include wired and / or wireless communication interfaces. UE 101 and 102 may be collectively referred to as UE 101 herein, and UE 101 may be used to perform one or more techniques disclosed herein.

[0025] Any radio link described herein (e.g., as used in network 140A or any other illustrated network) may operate in accordance with any exemplary radio communication technology and / or standard. Any spectrum management scheme may be used, including, for example, dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (e.g., licensed shared access (LSA) in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz and other frequencies, and spectrum access system (SAS) in 3.55-3.7 GHz and other frequencies). Different single carrier or orthogonal frequency domain multiplexing (OFDM) modes (CP-OFDM, SC-FDMA, SC-OFDM, filter bank based multi-carrier (FBMC), OFDMA, etc.), in particular 3GPP NR, may be used by assigning OFDM carrier data bit vectors to corresponding symbol resources.

[0026] In some aspects, any one of UE 101 and 102 may include an Internet of Things (IoT) UE or a cellular IoT (CIoT) UE, which may include a network access layer designed for low-power IoT applications that utilize short-term UE connections. In some aspects, any one of UE 101 and 102 may include a narrowband (NB) IoT UE (e.g., such as an enhanced NB-IoT (eNB-IoT) UE and a further enhanced (FeNB-IoT) UE). The IoT UE may exchange data with an MTC server or device via a public land mobile network (PLMN), proximity service (ProSe) or device-to-device (D2D) communication, a sensor network, or an IoT network using technologies such as machine-to-machine (M2M) or machine-type communication (MTC). The M2M or MTC data exchange may be a machine-initiated data exchange. The IoT network includes interconnected IoT UEs (which may include uniquely identifiable embedded computing devices (within the Internet infrastructure)) with short-term connections. The IoT UE may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network. In some aspects, either of UEs 101 and 102 may include an enhanced MTC (eMTC) UE or a further enhanced MTC (FeMTC) UE.

[0027] UEs 101 and 102 may be configured to connect (e.g., be communicatively coupled) to a radio access network (RAN) 110. The RAN 110 may be, for example, an evolved universal mobile telecommunications system (UMTS) terrestrial radio access network (E-UTRAN), a next generation RAN (NGRAN), or some other type of RAN. The RAN 110 may include one or more gNBs, one or more of which may be implemented by multiple units. Note that although gNBs may be referred to herein, the same aspects may apply to other generations of NodeBs, such as the sixth generation NodeB - and may therefore be referred to alternatively as next generation NodeBs (xNBs).

[0028] Each gNB may implement protocol entities in the 3GPP protocol stack, where the layers are considered ordered, from lowest to highest order: physical (PHY), medium access control (MAC), radio link control (RLC), packet data convergence control (PDCP), and radio resource control (RRC) / service data adaptation protocol (SDAP) (for control plane / user plane). The protocol layers in each gNB may be distributed in different units - a central unit (CU), at least one distributed unit (DU), and a remote radio head (RRH). In addition to those functions specifically assigned to the DU, the CU may provide functions such as controlling the transmission of user data, and implementing mobility control, radio access network sharing, positioning, and session management.

[0029] The higher protocol layers (PDCP and RRC for the control plane / PDCP and SDAP for the user plane) may be implemented in the CU, while the RLC and MAC layers may be implemented in the DU. The PHY layer may be divided, wherein the higher PHY layers are also implemented in the DU, while the lower PHY layers are implemented in the RRH. The CU, DU, and RRH may be implemented by different manufacturers, but nonetheless may be connected by appropriate interfaces between them. The CU may be connected to multiple DUs.

[0030] The interfaces within the gNB include E1 and fronthaul (F)F1 interfaces. The E1 interface can be located between the CU control plane (gNB-CU-CP) and the CU user plane (gNB-CU-UP), and can therefore support the exchange of signaling information between the control plane and the user plane through the E1AP service. The E1 interface can separate the radio network layer and the transport network layer, and enable the exchange of UE-associated information and non-UE-associated information. E1AP services can be non-UE-associated services and UE-associated services. Non-UE-associated services are related to the entire E1 interface instance between the gNB-CU-CP and the gNB-CU-UP using a non-UE-associated signaling connection. UE-associated services are related to a single UE and are associated with the UE-associated signaling connection maintained for the UE.

[0031] The F1 interface can be set between the CU and the DU. The CU can control the operation of the DU through the F1 interface. Since the signaling in the gNB is divided into control plane signaling and user plane signaling, the F1 interface can be divided into an F1-C interface for control plane signaling between the gNB-DU and the gNB-CU-CP, and an F1-U interface for user plane signaling between the gNB-DU and the gNB-CU-UP, which support control plane and user plane separation. The F1 interface can separate the radio network layer and the transport network layer, and enable the exchange of UE-associated information and non-UE-associated information. In addition, the F2 interface can be located between the lower and upper parts of the NR PHY layer. The F2 interface can also be separated into F2-C and F2-U interfaces based on the control plane and user plane functions.

[0032] UEs 101 and 102 utilize connections 103 and 104, respectively, each of which includes a physical communication interface or layer (discussed in further detail below); in this example, connections 103 and 104 are shown as air interfaces that implement communication coupling and can comply with cellular communication protocols, such as the Global System for Mobile Communications (GSM) protocol, the Code Division Multiple Access (CDMA) network protocol, the Push-to-Talk (PTT) protocol, the PTT over Cellular (POC) protocol, the Universal Mobile Telecommunications System (UMTS) protocol, the 3GPP Long Term Evolution (LTE) protocol, the 5G protocol, the 6G protocol, etc.

[0033] In an aspect, the UEs 101 and 102 may also exchange communication data directly via the ProSe interface 105. The ProSe interface 105 may alternatively be referred to as a sidelink (SL) interface, which includes one or more logical channels including, but not limited to, a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSSCH), a physical sidelink discovery channel (PSDCH), a physical sidelink broadcast channel (PSBCH), and a physical sidelink feedback channel (PSFCH).

[0034] UE 102 is shown as being configured to access access point (AP) 106 via connection 107. Connection 107 may include a local wireless connection, such as a connection compliant with any IEEE 802.11 protocol, according to which AP 106 may include Wireless Fidelity (WFI). ) router. In this example, AP 106 is shown connected to the Internet, but not to the core network of the wireless system (described in further detail below).

[0035] The RAN 110 may include one or more access nodes that implement connections 103 and 104. These access nodes (ANs) may be referred to as base stations (BS), NodeBs, evolved NodeBs (eNBs), next generation NodeBs (gNBs), RAN nodes, etc., and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). In some aspects, the communication nodes 111 and 112 may be transmit-receive points (TRPs). In the case where the communication nodes 111 and 112 are NodeBs (e.g., eNBs or gNBs), one or more TRPs may function within the communication cell of the NodeB. The RAN 110 may include one or more RAN nodes (e.g., macro RAN nodes 111) for providing macro cells, and one or more RAN nodes (e.g., low power (LP) RAN nodes 112) for providing femto cells or micro cells (e.g., cells with smaller coverage areas, smaller user capacity, or higher bandwidth than macro cells).

[0036] Any of the RAN nodes 111 and 112 may terminate the air interface protocol and may be the first point of contact for the UEs 101 and 102. In some aspects, any of the RAN nodes 111 and 112 may implement various logical functions for the RAN 110, including but not limited to radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management. In an example, any of the nodes 111 and / or 112 may be a gNB, an eNB, or another type of RAN node.

[0037] RAN 110 is shown as being communicatively coupled to a core network (CN) 120 via an S1 interface 113. In various aspects, CN 120 may be an evolved packet core (EPC) network, a next generation packet core (NPC) network, or some other type of CN (e.g., as described with reference to Figure 1B-1C In this regard, the S1 interface 113 is divided into two parts: an S1-U interface 114, which carries traffic data between the RAN nodes 111 and 112 and the serving gateway (S-GW) 122; and an S1-mobility management entity (MME) interface 115, which is a signaling interface between the RAN nodes 111 and 112 and the MME 121.

[0038] In this regard, CN 120 includes MME 121, S-GW 122, Packet Data Network (PDN) Gateway (P-GW) 123 and Home Subscriber Server (HSS) 124. MME 121 can be similar in function to the control plane of the legacy Serving General Packet Radio Service (GPRS) Support Node (SGSN). MME 121 can manage mobility aspects in access, such as gateway selection and tracking area list management. HSS 124 can include a database for network users (including subscription-related information) to support network entities in handling communication sessions. CN 120 can include one or several HSS 124, depending on the number of mobile subscribers, the capacity of the equipment, the organization of the network, etc. For example, HSS 124 can provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependency, etc.

[0039] The S-GW 122 may terminate the S1 interface 113 towards the RAN 110 and route data packets between the RAN 110 and the CN 120. In addition, the S-GW 122 may be a local mobility anchor for handovers between RAN nodes and may also provide an anchor for inter-3GPP mobility. Other responsibilities of the S-GW 122 may include lawful interception, charging, and some policy enforcement.

[0040] The P-GW 123 may terminate the SGi interface toward the PDN. The P-GW 123 may route data packets between the CN 120 and an external network (e.g., a network including an application server 184 (alternatively referred to as an application function (AF))) via an Internet Protocol (IP) interface 125. The P-GW 123 may also deliver data to other external networks 131A (which may include the Internet, an IP Multimedia Subsystem (IPS) network, and other networks). Typically, the application server 184 may be an element that provides an application (e.g., a UMTS packet service (PS) domain, a LTE PS data service, etc.) that uses IP bearer resources with a core network. In this regard, the P-GW 123 is shown as being communicatively coupled to the application server 184 via the IP interface 125. The application server 184 may also be configured to support one or more communication services (e.g., Voice over Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for UEs 101 and 102 via the CN 120.

[0041] The P-GW 123 may also be a node for policy enforcement and charging data collection. The Policy and Charging Rules Function (PCRF) 126 is a policy and charging control element of the CN 120. In a non-roaming scenario, in some aspects, there may be a single PCRF associated with the UE's Internet Protocol Connection Access Network (IP-CAN) session in the Home Public Land Mobile Network (HPLMN). In a roaming scenario where the service is out of local, there may be two PCRFs associated with the UE's IP-CAN session: the Home PCRF (H-PCRF) within the HPLMN and the Visited PCRF (V-PCRF) within the Visited Public Land Mobile Network (VPLMN). The PCRF 126 may be communicatively coupled to the application server 184 via the P-GW 123.

[0042] In some aspects, the communication network 140A can be an IoT network or a 5G or 6G network, including a 5G new air interface network that uses communications in licensed (5GNR) and unlicensed (5G NR-U) spectrum. One of the current implementers of IoT is narrowband IoT (NB-IoT). Operations in unlicensed spectrum can include dual connection (DC) operation and independent LTE systems in unlicensed spectrum (according to which LTE-based technologies operate only in unlicensed spectrum without using an "anchor point" in the licensed spectrum) (referred to as MulteFire). Further enhanced operations of LTE systems in licensed and unlicensed spectrum can be expected in future releases and 5G systems. Such enhanced operations may include techniques for sidelink resource allocation and UE processing behavior for NR sidelink V2X communications.

[0043] The NG system architecture (or 6G system architecture) may include a RAN 110 and a core network (CN) 120. The NG-RAN 110 may include multiple nodes, such as gNBs and NG-eNBs. The CN 120 (e.g., a 5G core network (5GC)) may include an access and mobility function (AMF) and / or a user plane function (UPF). The AMF and UPF may be communicatively coupled to the gNB and NG-eNB via an NG interface. More specifically, in some aspects, the gNB and NG-eNB may be connected to the AMF via an NG-C interface and to the UPF via an NG-U interface. The gNB and NG-eNB may be coupled to each other via an Xn interface.

[0044] In some aspects, the NG system architecture may use reference points between various nodes. In some aspects, each of the gNB and NG-eNB may be implemented as a base station, a mobile edge server, a small cell, a home eNB, etc. In some aspects, the gNB may be a master node (MN) in the 5G architecture, and the NG-eNB may be a secondary node (SN).

[0045] Figure 1B A non-roaming 5G system architecture according to some aspects is shown. Specifically, Figure 1B The 5G system architecture 140B is shown with reference point representation, which can be extended to the 6G system architecture. More specifically, the UE 102 can communicate with the RAN 110 and one or more other CN network entities. The 5G system architecture 140B includes multiple network functions (NFs), such as AMF 132, session management function (SMF) 136, policy control function (PCF) 148, application function (AF) 150, UPF 134, network slice selection function (NSSF) 142, authentication server function (AUSF) 144, and unified data management (UDM) / home subscriber server (HSS) 146.

[0046] UPF 134 may provide a connection to a data network (DN) 152, which may include, for example, operator services, Internet access, or third-party services. AMF 132 may be used to manage access control and mobility, and may also include a network slice selection function. AMF 132 may provide UE-based authentication, authorization, mobility management, etc., and may be independent of access technology. SMF 136 may be configured to establish and manage various sessions according to network policies. Therefore, SMF 136 may be responsible for session management and assigning IP addresses to UEs. SMF 136 may also select and control UPF 134 for data transmission. SMF 136 may be associated with a single session of UE 101 or multiple sessions of UE 101. That is, UE 101 may have multiple 5G sessions. A different SMF may be assigned to each session. Using different SMFs may allow each session to be managed separately. Therefore, the functions of each session may be independent of each other.

[0047] UPF 134 can be deployed in one or more configurations depending on the desired service type and can be connected to the data network. PCF 148 can be configured to provide a policy framework using network slicing, mobility management, and roaming (similar to PCRF in 4G communication systems). UDM can be configured to store subscriber profiles and data (similar to HSS in 4G communication systems).

[0048] AF 150 may provide information about packet flows to PCF 148, which is responsible for policy control, to support the desired QoS. PCF 148 may set mobility and session management policies for UE 101. To this end, PCF 148 may use packet flow information to determine appropriate policies for appropriate operation of AMF 132 and SMF 136. AUSF 144 may store data for UE authentication.

[0049] In some aspects, the 5G system architecture 140B includes an IP multimedia subsystem (IMS) 168B and multiple IP multimedia core network subsystem entities (e.g., call session control functions (CSCFs)). More specifically, the IMS 168B includes a CSCF, which can act as a proxy CSCF (P-CSCF) 162B, a serving CSCF (S-CSCF) 164B, an emergency CSCF (E-CSCF) ( Figure 1B166B. The P-CSCF 162B may be configured as the first contact point for UE 102 within the IM subsystem (IMS) 168B. The S-CSCF 164B may be configured to handle the session state in the network, and the E-CSCF may be configured to handle certain aspects of emergency sessions, such as routing emergency requests to the correct emergency center or PSAP. The I-CSCF 166B may be configured to be used as the contact point for all IMS connections within the operator's network for a subscriber whose destination is the network operator or a roaming subscriber currently located within the service area of ​​the network operator. In some aspects, the I-CSCF 166B may be connected to another IP multimedia network 170B, such as an IMS operated by a different network operator.

[0050] In some aspects, UDM / HSS 146 may be coupled to an application server (AS) 160B, which may include a telephony application server (TAS) or another application server. AS 160B may be coupled to IMS 168B via S-CSCF 164B or I-CSCF 166B.

[0051] Reference point representation indicates that there can be interactions between corresponding NF services. For example, Figure 1B 132), N2 (between RAN 110 and AMF 132), N3 (between RAN 110 and UPF 134), N4 (between SMF 136 and UPF 134), N5 (between PCF 148 and AF 150), N6 (between UPF 134 and DN 152), N7 (between SMF 136 and PCF 148), N8 (between UDM 146 and AMF 132), N9 (between two UPFs 134), N10 (between UDM 146 and SMF 136), N11 (between AMF 132 and SMF 136), N12 (between AUSF 144 and AMF 132), N13 (between AUSF 144 and UDM 148). 146), N14 (between two AMFs 132), N15 (between PCF 148 and AMF 132 in the case of non-roaming scenario, or between PCF 148 and visited network and AMF 132 in the case of roaming scenario), N16 (between two SMFs, not shown), and N22 (between AMF 132 and NSSF 142). Figure 1B Other reference points not shown are indicated.

[0052] Figure 1CA 5G system architecture 140C and a service-based representation are shown. Figure 1B In addition to the network entities shown in , the system architecture 140C may also include a network open function (NEF) 154 and a network repository function (NRF) 156. In some aspects, the 5G system architecture may be service-based, and the interactions between network functions may be represented by corresponding point-to-point reference points Ni, or as service-based interfaces.

[0053] In some aspects, such as Figure 1C As shown, a service-based representation can be used to represent network functions within the control plane that enable other authorized network functions to access its services. In this regard, the 5G system architecture 140C may include the following service-based interfaces: Namf 158H (a service-based interface presented by AMF 132), Nsmf 158I (a service-based interface presented by SMF 136), Nnef 158B (a service-based interface presented by NEF 154), Npcf158D (a service-based interface presented by PCF 148), Nudm 158E (a service-based interface presented by UDM 146), Naf 158F (a service-based interface presented by AF150), Nnrf 158C (a service-based interface presented by NRF 156), Nnssf 158A (a service-based interface presented by NSSF 142), and Nausf 158G (a service-based interface presented by AUSF 144). Figure 1C Other service-based interfaces not shown (e.g., Nudr, N5g-eir, and Nudsf).

[0054] The NR-V2X architecture can support high reliability, low latency sidelink communications with multiple traffic patterns, including periodic and aperiodic communications with random packet arrival times and sizes. The technology disclosed herein can be used to support high reliability in distributed communication systems with dynamic topologies, including sidelink NR V2X communication systems.

[0055] Figure 2 A block diagram of a communication device according to some embodiments is shown. The communication device 200 may be a UE (e.g., a dedicated computer, a personal or laptop computer (PC), a tablet PC, or a smart phone), a dedicated network device (e.g., an eNB), a server running software to configure the server to operate as a network device, a virtual device, or any machine capable of (sequentially or otherwise) executing instructions that specify actions to be taken by the machine. For example, the communication device 200 may be implemented as Figures 1A-1COne or more devices shown in . Note that the communications described herein may be encoded before being transmitted by a transmitting entity (e.g., UE, gNB) so as to be received by a receiving entity (e.g., gNB, UE), and decoded after being received by the receiving entity.

[0056] The examples described herein may include logic or multiple components, modules or mechanisms, or may operate thereon. Modules and components are tangible entities (e.g., hardware) that can perform specified operations, and may be configured or arranged in some manner. In an example, a circuit may be arranged in a specified manner (e.g., internally, or relative to an external entity (e.g., other circuits)) as a module. In an example, all or part of one or more computer systems (e.g., independent, client or server computer systems) or one or more hardware processors may be configured by firmware or software (e.g., instructions, application parts or applications) to operate to perform a module of a specified operation. In an example, the software may reside on a machine-readable medium. In an example, the software causes the hardware to perform a specified operation when executed by the underlying hardware of the module.

[0057] Thus, the term "module" (and "component") is understood to encompass a tangible entity, whether physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., transiently) configured (e.g., programmed) to operate in a specified manner or to perform part or all of any operations described herein. Considering that modules are examples of temporary configurations, each module need not be instantiated at any one time. For example, where a module comprises a general-purpose hardware processor configured using software, the general-purpose hardware processor can be configured into corresponding different modules at different times. Thus, software can configure a hardware processor, for example, to constitute a particular module at one instance in time and to constitute a different module at a different instance in time.

[0058] The communication device 200 may include a hardware processor (or equivalently, a processing circuit) 202 (e.g., a central processing unit (CPU), a GPU, a hardware processor core, or any combination thereof), a main memory 204, and a static memory 206, some or all of which may communicate with each other via an interconnect (e.g., a bus) 208. The main memory 204 may include any or all removable storage and non-removable storage, volatile memory, or non-volatile memory. The communication device 200 may also include a display unit 210 (e.g., a video display), an alphanumeric input device 212 (e.g., a keyboard), and a user interface (UI) navigation device 214 (e.g., a mouse). In an example, the display unit 210, the input device 212, and the UI navigation device 214 may be a touch screen display. The communication device 200 may also include a storage device (e.g., a drive unit) 216, a signal generating device 218 (e.g., a speaker), a network interface device 220, and one or more sensors (e.g., a global positioning system (GPS) sensor, a compass, an accelerometer, or other sensor). The communication device 200 may also include an output controller, such as a serial connection (e.g., a universal serial bus (USB)), a parallel connection, or other wired or wireless connection (e.g., infrared (IR), near field communication (NFC), etc.)) to communicate with or control one or more peripheral devices (e.g., a printer, a card reader, etc.).

[0059] The storage device 216 may include a non-transitory machine-readable medium 222 (hereinafter referred to as a machine-readable medium) on which is stored one or more sets of data structures or instructions 224 (e.g., software) embodying or utilized by any one or more of the techniques or functionality described herein. The instructions 224 may also reside completely or at least partially within the main memory 204, within the static memory 206, and / or within the hardware processor 202 during execution thereof by the communication device 200. Although the machine-readable medium 222 is illustrated as a single medium, the term "machine-readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database, and / or associated caches and servers) configured to store one or more instructions 224.

[0060] The term "machine-readable medium" may include any medium capable of storing, encoding, or carrying instructions that are executed by the communication device 200 and cause the communication device 200 to perform any one or more of the techniques of the present disclosure, or any medium capable of storing, encoding, or carrying data structures used by or associated with these instructions. Non-limiting examples of machine-readable media may include solid-state memory and optical and magnetic media. Specific examples of machine-readable media may include: non-volatile memory, such as semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; random access memory (RAM); and CD-ROM and DVD-ROM disks.

[0061] The instructions 224 may also be sent or received over a communication network via the network interface device 220 using a transmission medium 226 using any of a variety of wireless local area network (WLAN) transmission protocols (e.g., frame relay, Internet Protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.). Example communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), a mobile phone network (e.g., a cellular network), a plain old telephone (POTS) network, and a wireless data network. Communications over the network may include one or more different protocols, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards (referred to as Wi-Fi), the IEEE 802.16 family of standards (referred to as WiMax), the IEEE 802.15.4 family of standards, the long term evolution (LTE) family of standards, the universal mobile telecommunications system (UMTS) family of standards, a point-to-point (P2P) network, a next generation (NG) / fifth generation (5G) standard, etc. In an example, the network interface device 220 may include one or more physical jacks (eg, Ethernet jacks, coaxial jacks, or telephone jacks) or one or more antennas to connect to the transmission medium 226 .

[0062] Note that the term "circuit" as used herein refers to, is part of, or includes the following hardware components that are configured to provide the described functionality: for example, electronic circuits, logic circuits, processors (shared, dedicated, or group) and / or memories (shared, dedicated, or group), application specific integrated circuits (ASICs), field programmable devices (FPDs) (e.g., field programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high capacity PLDs (HCPLDs), structured ASICs, or programmable SoCs), digital signal processors (DSPs), etc. In some embodiments, the circuit may execute one or more software or firmware programs to provide at least some of the described functionality. The term "circuit" may also refer to a combination of one or more hardware elements and program code (or a combination of circuits and program code used in an electrical or electronic system), where one or more hardware elements are used to perform the functions of the program code. In these embodiments, the combination of hardware elements and program code may be referred to as a specific type of circuit.

[0063] Therefore, the term "processor circuit" or "processor" as used herein refers to, is a part of, or includes a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations, or recording, storing and / or transmitting digital data. The term "processor circuit" or "processor" may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core or multi-core processor, and / or any other device capable of executing or otherwise operating computer-executable instructions (e.g., program code, software modules, and / or functional processes).

[0064] Any radio link described herein may operate in accordance with any one or more of the following radio communication technologies and / or standards, including but not limited to: Global System for Mobile Communications (GSM) radio communication technology, General Packet Radio Service (GPRS) radio communication technology, Enhanced Data Rates for GSM Evolution (EDGE) radio communication technology, and / or Third Generation Partnership Project (3GPP) radio communication technology, such as Universal Mobile Telecommunications System (UMTS), Freedom of Multimedia Access (FOMA), 3GPP Long Term Evolution (LTE), 3GPP Long Term Evolution Advanced (LTE-A), and / or 3rd Generation Partnership Project (3GPP) radio communication technology. Advanced), Code Division Multiple Access 2000 (CDMA2000), Cellular Digital Packet Data (CDPD), Mobitex, Third Generation (3G), Circuit Switched Data (CSD), High Speed ​​Circuit Switched Data (HSCSD), Universal Mobile Telecommunications System (Third Generation) (UMTS (3G)), Wideband Code Division Multiple Access (Universal Mobile Telecommunications System) (W-CDMA (UMTS)), High Speed ​​Packet Access (HSPA), High Speed ​​Downlink Packet Access (HSDPA), High Speed ​​Uplink Packet Access (HSUPA), High Speed ​​Packet Access Plus (HSPA+), Universal Mobile Telecommunications System - Time Division Duplex (UMTS-TDD), Time Division - Code Division Multiple Access (TD-CDMA), Time Division - Synchronous Code Division Multiple Access (TD-CDMA), 3rd Generation Partnership Project Release 8 (Pre-4th Generation) (3GPP Rel.8 (Pre-4G)), 3GPP Rel.9 (3rd Generation Partnership Project Release 9), 3GPP Rel.10 (3rd Generation Partnership Project Release 10), 3GPP Rel.11 (3rd Generation Partnership Project Release 11), 3GPP Rel.12 (3rd Generation Partnership Project Release 12), 3GPP Rel.13 (3rd Generation Partnership Project Release 13), 3GPP Rel.14 (3rd Generation Partnership Project Release 14), 3GPP Rel.15 (3rd Generation Partnership Project Release 15), 3GPP Rel.16 (3rd Generation Partnership Project Release 16), 3GPP Rel.17 (3rd Generation Partnership Project Release 17) and subsequent versions (for example, Rel.18, Rel.19, etc.), 3GPP 5G, 5G, 5G New Radio (5G NR), 3GPP 5G New Radio, 3GPP LTE Extra, LTE-Advanced Pro, LTE License Assisted Access (LAA), MuLTEfire, UMTS Terrestrial Radio Access (UTRA), Evolved UMTS Terrestrial Radio Access (E-UTRA), Advanced Long Term Evolution (Fourth Generation) (LTE Advanced (4G)), cdmaOne (2G), Code Division Multiple Access 2000 (Third Generation) (CDMA2000 (3G)), Evolution Data Optimized or Evolution Data Only (EV-DO), Advanced Mobile Phone System (First Generation) (AMPS (1G)), Total Access Communication System / Extended Total Access Communication System (TACS / ETACS), Digital AMPS (Second Generation) (D-AMPS (2G)), Push to Talk (PTT), Mobile Telephone System (MTS), Improved Mobile Telephone System (IMTS), Advanced Mobile Phone System (AMTS), OLT (Norwegian Offentlig Landmobil Telefoni (public land mobile), MTD (Swedish acronym Mobiltelefonisystem D, or Mobile Phone System D), Public Automatic Land Mobile (Autotel / PALM), ARP (Finnish Autoradiopuhelin, "car radio telephone"), NMT (Nordic mobile), High Capacity Version (Hicap) of NTT (Nippon Telegraph and Telephone), Cellular Digital Packet Data (CDPD), Mobitex, DataTAC, Integrated Digital Enhanced Network (iDEN), Personal Digital Cellular (PDC), Circuit Switched Data (CSD), Personal Handyphone System (PHS), Broadband Integrated Digital Enhanced Network (WiDEN), iBurst, Unlicensed Mobile Access (UMA) (also known as the 3GPP Universal Access Network or GAN standard), Zigbee, Bluetooth, Wireless Gigabit Alliance (WiGig) standard, Generic mmWave standard (wireless systems operating at 10-300 GHz and above, such as WiGig, IEEE 802.11ad, IEEE 802.11ay, etc.), technologies operating in frequency bands above 300 GHz and THz (based on 3GPP / LTE or IEEE 802.11p or IEEE 802.11bd and others), vehicle-to-vehicle (V2V) and vehicle-to-X (V2X) and vehicle-to-infrastructure (V2I) and infrastructure-to-vehicle (I2V) communication technologies, 3GPP cellular V2X, DSRC (dedicated short range communication) communication systems (e.g., intelligent transportation systems and others (typically operating at or above 5850 MHz to 5925 MHz (typically up to 5935 MHz as recommended by the changes in CEPT Report 71)), European ITS-G5 systems (i.e., based on IEEE European flavors of DSRC of 802.11p, including ITS-G5A (i.e., ITS-G5 operation in the European ITS band dedicated to ITS for safety-related applications in the frequency range of 5,875 GHz to 5,905 GHz), ITS-G5B (i.e., operation in the European ITS band dedicated to ITS non-safety applications in the frequency range of 5,855 GHz to 5,875 GHz), ITS-G5C (i.e., operation for ITS applications in the frequency range of 5,470 GHz to 5,725 GHz), Japanese DSRC in the 700 MHz band (715 MHz to 725 MHz inclusive), IEEE 802.11bd-based systems, etc. .

[0065] The aspects described herein may be used in the context of any spectrum management scheme, including dedicated licensed spectrum, unlicensed spectrum, license-exempt spectrum, (licensed) shared spectrum (e.g., LSA = Licensed Shared Access in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz and further frequencies and SAS = Spectrum Access System / CBRS = Citizens Broadband Radio System in 3.55-3.7 GHz and further frequencies). Applicable frequency bands include IMT (International Mobile Telecommunications) spectrum as well as other types of spectrum / frequency bands, such as bands with national allocations (including 450-470 MHz, 902-928 MHz (Note: for example allocated in the United States (FCC Part 15)), 863-868.6 MHz (Note: for example allocated in the European Union (ETSI EN 300 220)), 915.9-929.7MHz (Note: for example, allocated in Japan), 917-923.5MHz (Note: for example, allocated in South Korea), 755-779MHz and 779-787MHz (Note: for example, allocated in China), 790-960MHz, 1710-2025MHz, 2110-2200MHz, 2300-2400MHz, 2.4-2.4835GHz (Note: it is an ISM band with global availability and is used by the Wi-Fi technology family (11b / g / n / ax) and also used by Bluetooth), 2500-2690MHz, 698-790MHz, 610-790MHz, 3400-3600MHz, 3400-3800MHz, 3800-4200MHz, 3.55-3.7GHz (Note: for example, allocated in the United States for Citizens Broadband Radio Service), 5.15-5.25GHz and 5.25-5.35GHz and 5.47-5.725GHz and 5.725-5.85GHz bands (Note: for example, allocated in the United States (FCC part 15), consisting of four U-NII bands with a total of 500MHz spectrum), 5.725-5.875GHz (Note: allocated in the European Union (ETSI EN 301 893)), 5.47-5.65GHz (Note: allocated in South Korea), 5925-7125MHz and 5925-6425MHz bands (Note: under consideration in the United States and the European Union, respectively. The next generation of Wi-Fi systems is expected to include the 6GHz spectrum as an operating band, but note that as of December 2017, Wi-Fi systems are not allowed in this band.Regulations are expected to be completed in the 2019-2020 time frame), IMT-advanced spectrum, IMT-2020 spectrum (expected to include 3600-3800MHz, 3800-4200MHz, 3.5GHz band, 700MHz band, bands in the 24.25-86GHz range, etc.), spectrum available under the FCC's "Spectrum Frontier" 5G initiative (including 27.5-28.35GHz, 29.1-29.25GHz, 31-31.3GHz, 37-38.6GHz, 38.6-40GHz, 42-42.5GHz, 57-64GHz, 71-76GHz, 8 1-86 GHz and 92-94 GHz, etc.), 5.9 GHz (usually 5.85-5.925 GHz) and 63-64 GHz ITS (Intelligent Transportation System) bands, bands currently allocated to WiGig (for example, WiGig Band 1 (57.24-59.40 GHz), WiGig Band 2 (59.40-61.56 GHz), WiGig Band 3 (61.56-63.72 GHz) and WiGig Band 4 (63.72-65.88 GHz)), 57-64 / 66 GHz (Note: This band is almost globally designated for Multi-Gigabit Wireless System (MGWS) / WiGig). A total of 14 GHz spectrum is allocated in the United States (FCC part 15), and a total of 9 GHz spectrum is allocated in the European Union (ETSI EN 302 567 and ETSI EN 301 217-2 (for fixed P2P)), 70.2 GHz-71 GHz band, any band between 65.88 GHz and 71 GHz, bands currently allocated for automotive radar applications (e.g., 76-81 GHz), and future bands (including 94-300 GHz and above). In addition, the solution can be used in an auxiliary manner on bands such as TV white space bands (typically below 790 MHz), where the 400 MHz and 700 MHz bands are particularly promising candidate bands. In addition to cellular applications, specific applications for vertical markets can also be addressed, such as PMSE (Programming and Special Events), medical, health, surgery, automotive, low latency, drones, etc.

[0066] The aspects described herein may also enable hierarchical application of the scheme, for example, by introducing hierarchical prioritization for use for different types of users (e.g., low / medium / high priority, etc.) based on prioritized access to the spectrum, for example, the highest priority is given to primary users, followed by secondary users, then tertiary users, etc.

[0067] The aspects described herein may also be applied to different single carrier or OFDM styles (CP-OFDM, SC-FDMA, SC-OFDM, filter bank based multi-carrier (FBMC), OFDMA, etc.), in particular to 3GPP NR (New Radio) by assigning OFDM carrier data bit vectors to corresponding symbol resources.

[0068] As mentioned above, mobile communications have evolved significantly from early voice systems to modern, highly complex, integrated communications platforms used in current generation networks. The next generation of wireless communications systems, 5G or New Radio (NR), is expected to enable an increased number and type of users and applications to access information and share data anywhere, anytime. NR is intended to be a unified network / system designed to meet widely varying and sometimes conflicting performance dimensions and services. This diverse, multi-dimensional demand is driven by different services and applications.

[0069] Sidelink communication was introduced in Rel-16 of the 3GPP specification. One of the goals of sidelink communication is advanced vehicle-to-everything (V2X) applications. Power saving solutions introduced in Rel-17, including partial listening and discontinuous reception (DRX) and inter-UE coordination, improve power consumption and reliability of sidelink transmission for terminals with limited battery.

[0070] Although NR sidelink was initially developed for V2X applications, there is growing interest in extending the application of NR sidelink to commercial use cases. Specifically, for commercial sidelink applications, an increase in sidelink data rate is desired. This increase can be achieved with support for sidelink carrier aggregation.

[0071] In Rel-16, two modes of resource allocation are defined for sidelink communications used in V2X applications: 1) Mode 1, where the gNB allocates resources for sidelink communications; 2) Mode 2, where the UE autonomously selects resources for sidelink communications based on a listening and resource selection process. For Mode 1 resource allocation, the UE can send sidelink HARQ-ACK reports on both PUCCH and PUSCH. In addition, both Type 1 and Type 2 sidelink HARQ-ACK codebooks are supported in Rel-16.

[0072] Figure 3 Sidelink hybrid automatic repeat request acknowledgement (HARQ-ACK) reporting according to some embodiments is shown. Specifically, Figure 3 An example of sidelink HARQ-ACK reporting on PUCCH for Mode 1 resource allocation is shown. Figure 3In the 3_0 format, the Tx UE sends PSCCH and PSSCH in the resources allocated from the gNB via the downlink control format (DCI) format 3_0 carried by the PDCCH. In addition, the Rx UE sends the sidelink HARQ-ACK feedback in the PSFCH to the Tx UE. Subsequently, the Tx UE sends the sidelink HARQ-ACK report in the PUCCH resources indicated in the DCI format 3_0. Multiple sidelink HARQ-ACK information bits on the PUCCH can be aggregated using type 1 and type 2 sidelink HARQ-ACK codebooks.

[0073] In Rel-16 and Rel-17, only a single carrier is considered for sidelink communications. When sidelink carrier aggregation (CA) is supported, multiple sets of design considerations can be taken for sidelink HARQ-ACK codebook generation. This article describes the mechanisms for both type 1 sidelink HARQ-ACK codebook generation for CA and type 2 sidelink HARQ-ACK codebook generation for CA. Note that in the following embodiments, the term "sidelink carrier" can be interchanged with "sidelink cell" and "sidelink serving cell".

[0074] In one embodiment, a sidelink carrier index may be included in DCI format 3_0 to indicate a sidelink carrier for resource allocation for PSCCH and PSSCH. The size of the field associated with the sidelink carrier index may be determined as in, is the number of sidelink carriers configured by higher layers.

[0075] Embodiments related to type 1 sidelink HARQ-ACK codebook generation for CA are provided as follows:

[0076] In one embodiment, for type 1 sidelink HARQ-ACK codebook generation for CA, sidelink HARQ-ACK bits are generated per sidelink carrier and then concatenated in ascending (or descending) order of the sidelink serving cell index.

[0077] The text in clause 16.5.1 in TS 38.213 regarding type 1 HARQ-ACK codebook generation may be updated as follows:

[0078] UE uses the following pseudo code to ACK The total number of HARQ-ACK information bits, determined HARQ-ACK information bits

[0079] Collection M A,c The cardinality defines a pair of corresponding HARQ-ACK information bits for the sidelink serving cell c. The total number of opportunities for candidate PSSCH transmissions that should be PSFCH reception opportunities is M c

[0080] Set c=0 - Sidelink serving cell index: lower index corresponds to lower RRC index of the corresponding cell

[0081] Set j = 0 - HARQ-ACK information bit index

[0082] Will Set to the number of sidelink serving cells configured by higher layers for the UE

[0083] If O ACK ≤11, the UE uses the HARQ-ACK information bit n used to obtain the transmit power for PUCCH as described in clause 7.2.1. HARQ-ACK The number is determined as in, yes For sidelink serving cell c , the number of HARQ-ACK information bits determined for the corresponding PSSCH sending of the corresponding PSFCH reception opportunity in the PSFCH reception opportunity m.

[0084] Figure 4 Type 1 sidelink HARQ-ACK codebook generation according to some embodiments is shown. Figure 4 In the example shown, the SL HARQ-ACK for the sidelink serving cell is first generated according to the existing specification defined in clause 16.5.1 of TS38.213. Further, the SL HARQ-ACK information bits are concatenated in ascending order of the sidelink serving cell index.

[0085] Figure 5 A type 1 sidelink HARQ-ACK codebook on PUCCH according to some embodiments is shown. Figure 5 In the example shown, four PSCCH / PSSCH transmissions are allocated by DCI format 3_0 carried by PDCCH, respectively. In addition, four sidelink HARQ-ACK information bits are generated and carried by PUCCH indicated by corresponding fields in DCI format 3_0.

[0086] Type 2 sidelink HARQ-ACK codebook generation for CA

[0087] Embodiments related to type 2 sidelink HARQ-ACK codebook generation for CA are provided as follows:

[0088] In one embodiment, a field of the total sidelink assignment index (T-SAI) may be included in DCI format 3_0 to indicate the total number of sidelink HARQ-ACK feedback information bits for CA. Specifically, the two bit fields defined in Table 16.5.2.1-1 may be used for the T-SAI field as follows:

[0089] Table 16.5.2.1-1: Counter SAI in DCI format 3_0 and total SAI Value

[0090]

[0091] Embodiments related to type 2 sidelink HARQ-ACK codebook generation for CA are provided as follows:

[0092] In another embodiment, the set of PDCCH monitoring opportunities of DCI format 3_0 for scheduling PSSCH transmission with associated PSFCH reception opportunities is defined as the union of the PDCCH monitoring opportunities in the active downlink (DL) part bandwidth (BWP) of the configured serving cell in ascending order of the start time of the associated search space set. The cardinality of the PDCCH monitoring opportunity set defines the total number M of PDCCH monitoring opportunities.

[0093] The value of the Counter SAI field in DCI format 3_0 other than DCI format 3_0 for SL configuration approval type 2 activation represents the cumulative number of {sidelink carrier, PDCCH monitoring opportunity} pairs, where PSSCH transmissions with associated PSFCH receptions are scheduled first in ascending order of sidelink carrier index and then in ascending order of PDCCH monitoring opportunity index m, up to the current PDCCH monitoring opportunity, where 0 ≤ m <M。

[0094] The value of Total SAI in DCI format 3_0 except DCI format 3_0 for SL configuration approval type 2 activation (when present) represents the total number of {sidelink carrier, PDCCH monitoring opportunity} pairs for which PSSCH transmissions with associated PSFCH receptions are scheduled until the current PDCCH monitoring opportunity and updated from PDCCH monitoring opportunity to PDCCH monitoring opportunity.

[0095] In another embodiment, for type 2 HARQ-ACK codebook generation on PUCCH, the T-SAI and sidelink carrier index are included in the pseudo code.

[0096] Specifically, the text in clause 16.5.2 in TS 38.213 for type 2 HARQ-ACK codebook generation may be updated as follows:

[0097] According to Table 16.5.2.1-1, Indicates the value of the counter SAI in the DCI format 3_0 in the PDCCH monitoring occasion m.

[0098] According to Table 16.5.2.1-1, Indicates the total SAI in DCI format 3_0 in PDCCH monitoring opportunity m value.

[0099] If the UE sends HARQ-ACK information in the PUCCH in time slot n, the UE receives the following pseudo code: ACK The total number of HARQ-ACK information bits is determined

[0100]

[0101] Set m=0 - PDCCH with DCI format 3_0 monitoring occasion index: lower index corresponds to earlier PDCCH with DCI format 3_0 monitoring occasion

[0102] Set j = 0

[0103] Setting V temp =0

[0104] Setting V temp,2 =0

[0105] set up

[0106] Will Set to the number of sidelink serving cells configured by higher layers for the UE

[0107] Set M to the number of PDCCH monitoring opportunities,

[0108] whilem <M

[0109] Set c=0 - Sidelink serving cell index: lower index corresponds to lower RRC index of the corresponding cell

[0110]

[0111]

[0112] In another embodiment, for power control of the PUCCH carrying sidelink HARQ-ACK information bits, the number of sidelink carriers will be included in determining the number of HARQ-ACK information bits.

[0113] The text in clause 9.1.3.1 in TS 38.213 regarding type 2 HARQ-ACK codebook generation may be updated as follows:

[0114] If O ACK ≤11, the UE determines the number of HARQ-ACK information bits used to obtain the transmit power for PUCCH as described in clause 7.2.1.

[0115]

[0116] in

[0117] - The value of the Counter SAI field in the last DCI format 3_0 other than the DCI format 3_0 approved for activating SL configuration, which schedules PSSCH transmission associated with the PSFCH reception opportunity detected by the UE within M PDCCH monitoring opportunities

[0118] - If the UE does not detect any DCI format 3_0 scheduling PSSCH transmission associated with a PSFCH reception opportunity in any of the M PDCCH monitoring occasions, other than the DCI format 3_0 approved by the activated SL configuration

[0119] - U SAI , c It is the DCI format 3_0 other than the DCI format approved by the activation SL configuration, which is detected by the scheduling UE within M PDCCH monitoring opportunities. For sidelink carrier c If the UE does not detect any DCI format 3_0 that schedules PSSCH transmission with associated PSFCH reception opportunities in any M PDCCH monitoring opportunities, except for the DCI format 3_0 approved by the activated SL configuration, U SAI =0

[0120] - Except for the DCI format 3_0 approved by the activation SL configuration, the scheduling has the UE in For sidechain Carrier c The number of DCI formats 3_0 transmitted by the PSSCH associated with the PSFCH reception opportunity detected in the PDCCH monitoring opportunity m

[0121] - N CG , c Is the UE in the corresponding For sidelink carrier c The number of SL configurations approved for sending the corresponding HARQ-ACK information in the same PUCCH as the PSSCH dynamically scheduled to send the HARQ-ACK information of the associated PSFCH reception opportunity within the M PDCCH monitoring opportunities

[0122] - is the number of sidelink carriers .

[0123] In some aspects, if SL configuration approval is supported in only one sidelink carrier, the above formula may be updated as follows:

[0124]

[0125] Prioritization

[0126] In Rel-16, the UE is expected to transmit and receive PSFCH carrying HARQ-ACK feedback in the same symbol. In this case, depending on the priority value of PSFCH determined based on the priority of the associated PSSCH transmission, the UE may choose to transmit or receive PSFCH due to the half-duplex constraint.

[0127] Similarly, when the PUCCH carrying the sidelink HARQ-ACK information bits overlaps with the sidelink transmission including PSSCH and PSFCH transmissions, if the priority value of the PUCCH is less than the priority value of the sidelink transmission, the UE can determine that the PUCCH has a higher priority than the SL transmission. In this case, if the UE is not able to perform sidelink and uplink transmissions simultaneously in the same carrier or two corresponding carriers, the UE can only send the PUCCH and cancel the sidelink transmission. Otherwise, if the sidelink transmission has a higher priority than the PUCCH, the UE can only send the sidelink channel and cancel the PUCCH.

[0128] Figure 6 Prioritization of PUCCH and Physical Sidelink Feedback Channel (PSFCH) transmissions with sidelink HARQ-ACK feedback is shown in accordance with some embodiments. Figure 6 In the example shown, respectively, the PUCCH with sidelink HARQ-ACK feedback has a priority value of 3, while the PSFCH transmission has a priority value of 2. In this case, the UE determines that the PSFCH transmission has a higher priority than the PUCCH transmission. If the UE is not able to communicate on both carriers for uplink transmission and sidelink transmission, the UE only sends the PSFCH and cancels the PUCCH transmission.

[0129] In Rel-16 and Rel-17, only single carrier operation is considered for sidelink communications. For sidelink CA, when sidelink transmission and reception overlap in time on different corresponding carriers, if the UE is not able to transmit and receive simultaneously on the sidelink carrier, priority sorting rules can be defined to allow the UE to send or receive the sidelink physical channel / signal only on a single sidelink carrier. Similarly, in the case where sidelink transmission and / or reception on more than one sidelink carrier overlaps with uplink transmission on an uplink carrier, priority sorting rules can be defined. This article discloses conflict handling for sidelink transmission and reception in CA scenarios.

[0130] Conflict handling for side link transmission and reception in CA scenarios

[0131] In one embodiment, for SL communication and S-SS / PBCH transmission of different sidelink carriers of sidelink CA, the UE is expected to be (pre) configured with the same set of time slots. In addition, for PSFCH transmission in different sidelink carriers, the UE is expected to be (pre) configured with the same periodicity. In this case, the same PSFCH transmission opportunity in time can be configured for different carriers.

[0132] In one embodiment, when the UE is about to simultaneously send a first group of sidelink physical channels / signals in a first group of sidelink carriers and receive a second group of sidelink physical channels / signals in a second group of sidelink carriers (i.e., the first and second groups of sidelink physical channels / signals overlap in time): the UE first determines the priority value of the sidelink transmission as the minimum priority value among the sidelink transmissions in the first group of sidelink physical channels / signals, and the UE determines the priority value of the sidelink reception as the minimum priority value among the sidelink receptions in the second group of sidelink physical channels / signals.

[0133] If the determined sidelink transmission priority value of the first group of sidelink physical channels / signals is less than the determined sidelink reception priority value of the second group of sidelink physical channels / signals, the first group of sidelink physical channels / signals has a higher priority than the second group of sidelink physical channels / signals; otherwise, the second group of sidelink physical channels / signals has a higher priority than the first group of sidelink physical channels / signals.

[0134] In addition, if the UE is not capable of simultaneously transmitting and receiving sidelink physical channels / signals in two or more corresponding carriers, the UE transmits only or receives only the sidelink physical channels / signals based on which channel / signal has a higher priority.

[0135] The first and second groups of sidelink physical channels / signals may include one or more of the following: sidelink synchronization signal (S-SS) and physical sidelink broadcast channel (PSBCH), PSSCH and PSCCH, PSFCH or sidelink-positioning reference signal (SL-PRS).

[0136] In some aspects, the first set of sidelink physical channels / signals may include only sidelink physical channels on the first sidelink carrier; and the second set of sidelink physical channels / signals may include only sidelink physical channels on the second sidelink carrier.

[0137] In one example, when PSSCH / PSCCH transmissions in a first group of side link carriers overlap in time with PSFCH receptions for a second group of side link carriers, and if the minimum priority value among the PSSCH / PSCCH transmissions is less than the minimum priority value among the PSFCH receptions, the PSSCH / PSCCH transmissions in the first group of side link carriers have a higher priority than the PSFCH receptions in the second group of side link carriers; otherwise, the PSFCH receptions in the second group of side link carriers have a higher priority than the PSSCH / PSCCH transmissions in the first group of side link carriers.

[0138] Figure 7 1 shows the prioritization between PSSCH / PSCCH transmission and PSFCH reception according to some embodiments. Figure 7 In the example shown, PSSCH / PSCCH transmission has a priority value of 3, and PSFCH reception in sidelink carriers 2 and 3 has priority values ​​2 and 4, respectively. Based on the above rules, PSFCH reception has a priority value of 2 and has a higher priority than PSSCH / PSCCH transmission. If the UE is not capable of performing sidelink transmission and reception on more than two sidelink carriers simultaneously, the UE cancels PSSCH / PSCCH transmission in sidelink carrier 1 and receives PSFCH in sidelink carriers 2 and 3, respectively.

[0139] In another example, when S-SS / PSBCH reception for a first side link carrier overlaps in time with PSFCH or PSSCH / PSCCH transmission for a second side link carrier, if the priority value of S-SS / PSBCH is less than the priority value of PSFCH or PSSCH / PSCCH transmission, S-SS / PSBCH reception has a higher priority than PSFCH or PSSCH / PSCCH transmission; otherwise, PSFCH or PSSCH / PSCCH transmission has a higher priority than S-SS / PSBCH reception.

[0140] Figure 8 1 shows the prioritization between PSSCH / PSCCH transmission and PSFCH reception according to some embodiments. Figure 8 In the example shown, PSSCH / PSCCH transmission has a lower priority value than S-SS / PSBCH reception. Based on the above priority sorting rules, PSSCH / PSCCH transmission has a higher priority than S-SS / PSBCH reception. If the UE is not capable of performing sidelink transmission and reception on more than two sidelink carriers simultaneously, the UE cancels S-SS / PSBCH reception in sidelink carrier 2 and only transmits PSSCH / PSCCH in sidelink carrier 1.

[0141] In another embodiment, when the UE is about to send an uplink channel / signal in an uplink carrier and simultaneously send a first sidelink physical channel / signal in a first sidelink carrier and a second sidelink physical channel / signal in a second sidelink carrier, the UE first determines the priority of the sidelink transmissions in the first and second carriers, which is the minimum priority value among the SL transmissions. In addition, the UE determines the priority of UL transmission and SL transmission according to the priority sorting for sidelink and uplink transmission / reception determined in clause 16.2.4.3.1 in TS 38.213.

[0142] If the UE is not able to transmit physical channels / signals in the sidelink and uplink simultaneously in more than one carrier, the UE sends the uplink channel / signal only in the uplink carrier if the uplink transmission has a higher priority than the sidelink transmission; otherwise, if the determined SL transmission has a higher priority than the uplink transmission, the UE sends the sidelink transmission in the first and second sidelink carriers, respectively, and discards / cancels the uplink transmission.

[0143] Fig. 9 Prioritization between UL transmissions and SL transmissions in more than one sidelink carrier is shown according to some embodiments. Fig. 9 In the example shown, PUCCH with sidelink HARQ-ACK feedback has a priority value of 3, PSSCH / PSCCH transmission has a priority value of 4, and PSFCH transmission has a priority value of 2, respectively. Based on the above rules, the UE first determines that SL transmission has a priority value of 2. In addition, the UE determines that SL transmission has a higher priority than UL transmission. If the UE is not capable of uplink and sidelink transmission at the same time, the UE sends PSSCH / PSCCH and PSFCH only in the two corresponding sidelink carriers and cancels the uplink transmission in the uplink carrier.

[0144] In another embodiment, when the UE is about to transmit an uplink channel / signal in an uplink carrier and simultaneously receive a first sidelink physical channel / signal in a first sidelink carrier and a second sidelink physical channel / signal in a second sidelink carrier, the UE first determines the priority of the sidelink transmission in the first and second carriers as the minimum priority value among the SL receptions. In addition, the UE determines the priority of UL transmission and SL reception according to the priority sorting for sidelink and uplink transmission / reception determined in clause 16.2.4.3.1 in TS38.213.

[0145] If the UE is not able to simultaneously transmit on the uplink and receive on the sidelink in more than one carrier, the UE transmits the uplink channel / signal only in the uplink carrier if the uplink transmission has a higher priority than the sidelink reception; otherwise, if the determined SL transmission has a higher priority than the uplink transmission, the UE receives on the sidelink in the first and second sidelink carriers, respectively, and discards / cancels the uplink transmission.

[0146] Fig.10 Prioritization between UL transmissions and SL transmissions in more than one sidelink carrier is shown according to some embodiments. Fig.10 In the example shown, PUCCH with sidelink HARQ-ACK feedback has a priority value of 1, PSFCH reception in SL carrier 1 has a priority value of 4, and PSFCH reception in SL carrier 2 has a priority value of 3, respectively. Based on the above rules, the UE first determines that PSFCH reception has a priority value of 2. In addition, the UE determines that UL transmission has a higher priority than SL reception. If the UE is not capable of simultaneously transmitting and receiving on the uplink and sidelink carriers, respectively, the UE only transmits PUCCH with sidelink HARQ-ACK feedback and cancels PSFCH reception in the two corresponding sidelink carriers.

[0147] In another embodiment, when the UE is about to simultaneously send an uplink channel / signal in an uplink carrier, send a first sidelink physical channel / signal set in a first group of sidelink carriers, and receive a second sidelink physical channel / signal in a second group of sidelink carriers: the UE first determines the priority value of the sidelink transmission as the minimum priority value among the sidelink transmissions in the first group of sidelink physical channels / signals, and the UE determines the priority value of the sidelink reception as the minimum priority value among the sidelink receptions in the second group of sidelink physical channels / signals.

[0148] The UE first performs priority sorting between sidelink transmission and reception in the first group and the second group of sidelink carriers based on the determined priority value for sidelink transmission and reception, wherein the priority sorting rule can be determined as described above (i.e., a smaller priority value has a higher priority). In addition, the UE performs priority sorting between sidelink transmission or reception with a higher priority and uplink transmission based on the existing priority sorting rule defined in clause 16.2.4.3 in TS38.213.

[0149] In one option, if the priority value of the uplink transmission is less than the determined priority value of the sidelink transmission and reception, and if the UE is not capable of performing uplink transmission and sidelink transmission or reception simultaneously, the UE transmits the uplink channel / signal only on the uplink carrier and cancels the sidelink transmission / reception in the first and second groups of sidelink carriers.

[0150] Fig.11 The prioritization between UL transmission, SL transmission and SL reception according to some embodiments is shown. Fig.11 In the example shown, PUCCH with sidelink HARQ-ACK feedback has a priority value of 1, PSFCH transmission in SL carrier 1 has a priority value of 4, and PSFCH reception in SL carrier 2 has a priority value of 3, respectively. Based on the above rules, PUCCH transmission has the highest priority. If the UE is not capable of uplink transmission and sidelink transmission or reception at the same time, the UE only transmits PUCCH and cancels PSFCH transmission in SL carrier 1 and PSFCH reception in SL carrier 2.

[0151] In another option, if the determined priority value of the sidelink transmission is less than the priority value of the uplink transmission and the determined priority value of the sidelink reception, and if the UE is not capable of performing uplink transmission and sidelink transmission or reception simultaneously, the UE transmits the sidelink physical channel / signal only in the first group of sidelink carriers and cancels the uplink transmission and the sidelink reception in the second group of sidelink carriers.

[0152] In another option, if the determined priority value of the sidelink reception is less than the priority value of the uplink transmission and the determined priority value of the sidelink transmission, and if the UE is not capable of performing uplink transmission and sidelink transmission or reception simultaneously, the UE receives the sidelink physical channels / signals only in the second group of sidelink carriers and cancels the uplink transmission and the sidelink transmission in the first group of sidelink carriers.

[0153] In another option, if the priority value of uplink transmission or sidelink transmission is less than the priority value of sidelink reception, if the UE is not capable of simultaneously performing uplink transmission and sidelink reception on two or more carriers, and if the UE is capable of simultaneously performing uplink transmission and sidelink transmission on two or more carriers, the UE sends an uplink channel / signal on the uplink carrier and sends a sidelink channel / signal in a first group of sidelink carriers, and cancels the sidelink reception in a second group of sidelink carriers.

[0154] Fig.12 Another prioritization between UL transmission, SL transmission and SL reception according to some embodiments is shown. Fig.12In the example shown, PUCCH with sidelink HARQ-ACK feedback has a priority value of 1, PSFCH transmission in SL carrier 1 has a priority value of 4, and PSFCH reception in SL carrier 2 has a priority value of 3, respectively. Based on the above rules, PUCCH transmission has a higher priority than PSFCH reception. If the UE is not capable of simultaneously performing uplink transmission and sidelink reception on two or more carriers, and the UE is capable of simultaneously performing uplink transmission and sidelink transmission on two or more carriers, the UE transmits PUCCH and PSFCH in SL carrier 1 and cancels PSFCH reception in SL carrier 2.

[0155] In another embodiment, when the priority value of the sidelink transmission in the determined first group of sidelink carriers is the same as the priority value of the sidelink reception in the determined second group of sidelink carriers, in one option, the sidelink transmission has a higher priority than the sidelink reception. In this case, if the UE is not able to simultaneously transmit and receive the sidelink physical channel / signal in two or more corresponding carriers, the UE transmits the sidelink physical channel / signal and cancels the sidelink reception.

[0156] In another option, sidelink reception has a higher priority than sidelink transmission. In this case, if the UE is not able to simultaneously transmit and receive the sidelink physical channel / signal in two or more corresponding carriers, the UE receives the sidelink physical channel / signal and cancels the sidelink transmission.

[0157] In another option, whether the sidelink transmission or reception has a higher priority can be configured by a higher layer (pre-). In this case, if the UE is not able to simultaneously transmit and receive the sidelink physical channel / signal in two or more corresponding carriers, the UE will transmit or receive the sidelink physical channel / signal according to the configuration.

[0158] In another embodiment, if the UE is capable of transmitting on more than one sidelink carrier simultaneously, and the UE is to transmit on more than one sidelink carrier, wherein the transmissions on more than one sidelink carrier overlap for a time period, then if the total UE transmit power for that time period would exceed P CMAX : If the SL transmission on the second sidelink carrier has a higher priority than the first sidelink carrier, the UE reduces the power used for SL transmission before the SL transmission on the first sidelink carrier so that the total UE transmit power does not exceed P CMAX ; and if the SL transmission on the first side link carrier has a higher priority than the second side link carrier, the UE reduces the power used for SL transmission before the SL transmission on the second side link carrier so that the total UE transmit power does not exceed P CMAX .

[0159] In another embodiment, if the UE is capable of transmitting on an uplink carrier and more than one sidelink carrier simultaneously, and the UE is to transmit on an uplink carrier and more than one sidelink carrier, wherein the transmissions on the uplink carrier and more than one sidelink carrier overlap for a time period, if the total transmit power of the UE for the time period exceeds P CMAX , the UE allocates power to the UL transmission and the sidelink transmission in descending order based on their priority values. Specifically, the transmission with the smallest priority value has the highest priority, followed by the transmission with the second smallest priority value, and so on.

[0160] In some embodiments, the electronic device, network, system, chip or component of the above figures or a portion or implementation thereof may be configured to perform one or more processes, techniques or methods described herein or a portion thereof. Fig.13 One such process that may be performed by a UE or a portion thereof is depicted in FIG. Fig.13 A process for providing sidelink HARQ-ACK information according to some embodiments is shown. For example, process 1300 may include: generating sidelink HARQ-ACK information for sidelink communication with carrier aggregation at operation 1302. At operation 1304, process 1300 may also include: sending the generated sidelink HARQ-ACK information on the PUCCH.

[0161] Fig.14 A process for prioritizing transmissions or receptions, including sidelink transmissions or receptions, is shown in accordance with some embodiments. Fig.14 The process 1400 may include or relate to a method performed by a UE, one or more elements of a UE, and / or one or more electronic devices that include and / or implement one or more elements of a UE. The process 1400 may include: at operation 1402, identifying that a sidelink transmission or reception will at least partially overlap in time with another transmission or reception; at operation 1404, identifying a priority of the sidelink transmission or reception and a priority of the other transmission or reception; and at operation 1406, giving priority to the sidelink transmission or reception or the other transmission or reception based on the priority of the sidelink transmission or reception and the priority of the other transmission or reception.

[0162] Example

[0163] Although the embodiments have been described with reference to specific example embodiments, it is apparent that various modifications and changes may be made to these embodiments without departing from the broader scope of the present disclosure. Therefore, the description and the drawings are considered to be illustrative rather than restrictive. The drawings constituting a part of the description show specific embodiments in which the subject matter can be practiced by way of illustration and not limitation. The illustrated embodiments are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other embodiments may be utilized and derived therefrom so that structural and logical substitutions and changes may be made without departing from the scope of the present disclosure. Therefore, this detailed description should not be understood as limiting, and the scope of the various embodiments is limited only by the appended claims together with the full scope of equivalents to which these claims are assigned.

[0164] Subject matter may be referred to herein individually and / or collectively by the term "embodiment", which is merely for convenience and is not intended to actively limit the scope of the present application to any single inventive concept (if more than one is actually disclosed). Therefore, although specific embodiments have been shown and described herein, it should be understood that any arrangement that is considered to achieve the same purpose can replace the specific embodiments shown. The present disclosure is intended to cover any and all adaptations or variations of the various embodiments. After reading the above description, combinations of the above embodiments and other embodiments not specifically described herein will be apparent to those skilled in the art.

[0165] In this document, as is common in patent documents, the term "one" or "an" is used to indicate one or more than one, independent of any other instance or usage of "at least one" or "one or more". In this document, the term "or" is used to refer to a non-exclusive "or", such that "A or B" includes "A but not B", "B but not A", and "A and B", unless otherwise indicated. In this document, the terms "including" and "wherein" are used as the plain English equivalents of the corresponding terms "comprising" and "wherein". In addition, in the following claims, the terms "including" and "comprising" are open-ended, that is, systems, UEs, articles, compositions, formations, or processes that include elements other than the elements listed after such terms in the claims are still considered to fall within the scope of the claim. In addition, in the following claims, the terms "first", "second", and "third", etc. are used only as labels and are not intended to impose numerical requirements on their objects. As indicated herein, although the term "one" is used herein, one or more associated elements may be used in different embodiments. For example, the term "a processor" configured to perform a particular operation includes both a single processor configured to perform all operations and multiple processors individually configured to perform some or all operations (possibly overlapping), such that a combination of processors performs all operations. In addition, the term "comprising" may be interpreted as "including at least" the elements that follow.

[0166] The disclosed abstract is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. Furthermore, in the foregoing detailed description, it can be seen that various features are grouped together in a single embodiment for the purpose of simplifying the disclosure. This disclosure method should not be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. On the contrary, as reflected in the following claims, the inventive subject matter lies in less than all the features of a single disclosed embodiment. Therefore, the following claims are hereby incorporated into the detailed description, with each claim representing a separate embodiment on its own.

Claims

1. An apparatus for a user equipment (UE), the apparatus comprising: Memory; and a processing circuit, configured to configure the UE to: generating type 1 or type 2 sidelink hybrid automatic repeat request-acknowledgement (HARQ-ACK) information bits for sidelink carrier aggregation; and sending the type 1 or type 2 sidelink HARQ-ACK information bits on a physical uplink control channel (PUCCH) to a fifth generation Node B (gNB) using sidelink carrier aggregation; and The memory is configured to store the type 1 or type 2 side link HARQ-ACK information bits.

2. The device according to claim 1, wherein: The processing circuit is further configured to: Downlink control information (DCI) having a DCI format 3_0 is received from the gNB, the DCI including a sidelink carrier index indicating a sidelink carrier for resource allocation of a physical sidelink control channel (PSCCH) and a physical sidelink shared channel (PSSCH).

3. The device according to claim 1, wherein: The processing circuit is further configured to: For type 1 sidelink HARQ-ACK codebook generation for sidelink carrier aggregation, sidelink HARQ-ACK bits are generated per sidelink carrier and concatenated in ascending order of sidelink serving cell index.

4. The device of claim 1, wherein: The processing circuit is further configured to: receive downlink control information (DCI) having DCI format 3_0 from the gNB, and The DCI format 3_0 has a total sidelink assignment index (T-SAI) field, which indicates the total number of sidelink HARQ-ACK feedback information bits for sidelink carrier aggregation used for type 2 HARQ-ACK codebook generation.

5. The device of claim 1, wherein: The processing circuit is further configured to: receive downlink control information (DCI) having DCI format 3_0 from the gNB, and The physical downlink control channel (PDCCH) monitoring opportunity set for the DCI format 3_0 for scheduling physical sidelink shared channel (PSSCH) transmissions with associated physical sidelink feedback channel (PSFCH) reception opportunities is defined as the union of the PDCCH monitoring opportunities in the active downlink (DL) part bandwidth (BWP) of the configured service cell in ascending order of the start time of the associated search space set.

6. The device of claim 1, wherein: The processing circuit is further configured to: receive downlink control information (DCI) having DCI format 3_0 from the gNB, and The value of the counter Sidelink Assignment Index (SAI) field in the DCI format 3_0 other than the DCI format 3_0 for sidelink (SL) configuration approval type 2 activation represents the cumulative number of {sidelink carrier, physical downlink control channel (PDCCH) monitoring opportunity} pairs, where physical sidelink shared channel (PSSCH) transmissions with associated physical sidelink feedback channel (PSFCH) reception are first scheduled in ascending order of sidelink carrier index and then in ascending order of PDCCH monitoring opportunity index until the current PDCCH monitoring opportunity.

7. The device of claim 1, wherein: The processing circuit is further configured to: receive downlink control information (DCI) having DCI format 3_0 from the gNB, and The value of the total sidelink assignment index (SAI) in the DCI format 3_0 other than the DCI format 3_0 for sidelink (SL) configuration approval type 2 activation, when present, represents the total number of {sidelink carrier, physical downlink control channel (PDCCH) monitoring occasions} pairs, where physical sidelink shared channel (PSSCH) transmissions with associated physical sidelink feedback channel (PSFCH) receptions are scheduled until the current PDCCH monitoring occasion and updated between PDCCH monitoring occasions.

8. The device of claim 1, wherein: The processing circuit is further configured to: Type 2 HARQ-ACK codebook generation on the PUCCH is performed using a total sidelink assignment index (T-SAI) and a sidelink carrier index in a pseudocode.

9. The device of claim 1, wherein: The processing circuit is further configured to: For power control of the PUCCH carrying sidelink HARQ-ACK information bits, the number of the sidelink HARQ-ACK information bits is determined based on the number of sidelink carriers.

10. The device of claim 1, wherein: The processing circuit is further configured to: configuring or indicating a priority value for a sidelink physical channel or signal; and For sidelink carrier aggregation, it is determined whether the sidelink physical channel or signal has a higher priority than another sidelink physical channel or signal or an uplink transmission.

11. The device of claim 10, wherein: The sidelink physical channel or signal is selected from the group of sidelink physical channels and signals including: sidelink synchronization signal (S-SS) and physical sidelink broadcast channel (PSBCH), physical sidelink shared channel (PSSCH) and physical sidelink control channel (PSCCH), physical sidelink feedback channel (PSFCH) and sidelink positioning reference signal (SL PRS).

12. The device of claim 1, wherein: The processing circuit is further configured to: for sidelink carrier aggregation, determining that a first set of sidelink physical channels or signals to be transmitted in a first set of sidelink carriers and a second set of sidelink physical channels or signals to be received in a second set of sidelink carriers overlap in time; setting a priority value for sidelink transmissions to a minimum priority value among the sidelink transmissions in the first set of sidelink physical channels or signals, and setting a priority value for sidelink receptions to a minimum priority value among the sidelink receptions in the second set of sidelink physical channels or signals; as well as The minimum priority value between the priority value sent by the side link and the priority value received by the side link is determined as the highest priority.

13. The device of claim 1, wherein: The processing circuit is further configured to: determining that an uplink channel or signal is to be transmitted in the uplink carrier, and that a first sidelink physical channel or signal in the first sidelink carrier and a second sidelink physical channel or signal in the second sidelink carrier are to be simultaneously transmitted or received; determining a priority of sidelink transmissions in the first sidelink carrier and the second sidelink carrier, the priority being a minimum priority value among the sidelink transmissions in the first sidelink carrier and the second sidelink carrier; as well as The sidelink transmission having the minimum priority value is selected for transmission or reception.

14. The device of claim 1, wherein: The processing circuit is further configured to: prioritizing the sidelink transmissions and receptions based on priority values ​​for the sidelink transmissions and receptions in the first set of sidelink carriers and the second set of sidelink carriers, wherein a smaller priority value has a higher priority; and In response to determining that the priority value of sidelink transmissions in the first set of sidelink carriers is the same as the priority value of sidelink receptions in the second set of sidelink carriers, prioritizing the sidelink transmissions over the sidelink receptions.

15. The device of claim 1, wherein: The processing circuit is further configured to: for a UE having the capability to transmit simultaneously on more than one sidelink carrier: determining that transmissions on the more than one sidelink carriers will overlap over a period of time; determining that a total UE transmit power over the time period is about to exceed a maximum UE transmit power; as well as In response to determining that the total UE transmit power over the time period is about to exceed the maximum UE transmit power, reducing the power used for sidelink transmission on one of the more than one sidelink carriers, the sidelink transmission on the one of the more than one sidelink carriers having a lower priority than the sidelink transmission on another of the more than one sidelink carriers, and the power of the sidelink transmission on the one of the more than one sidelink carriers is reduced to reduce the total UE transmit power to at most the maximum UE transmit power.

16. The device of claim 1, wherein: The processing circuit is further configured to: for a UE having the capability of transmitting simultaneously on an uplink carrier and more than one sidelink carrier: determining that uplink transmissions on the uplink carrier and sidelink transmissions on the more than one sidelink carriers are to overlap for a period of time; determining that a total UE transmit power over the time period is about to exceed a maximum UE transmit power; as well as In response to determining that the total UE transmit power over the time period will exceed the maximum UE transmit power, power is allocated to the uplink transmission and the sidelink transmission in descending order based on the priority values ​​of the uplink transmission and the sidelink transmission.

17. An apparatus for a fifth generation Node B (gNB), the apparatus comprising: Memory; and a processing circuit, configured to configure the gNB to: sending downlink control information (DCI) having a DCI format 3_0 to a user equipment (UE), the DCI format 3_0 having a total sidelink assignment index field indicating a total number of sidelink hybrid automatic repeat request-acknowledgement (HARQ-ACK) feedback information bits for sidelink carrier aggregation; as well as receiving, from the UE, type 1 or type 2 sidelink HARQ-ACK information bits on a physical uplink control channel (PUCCH) that has used sidelink carrier aggregation; and Wherein, the memory is configured to: store the DCI.

18. The device of claim 17, wherein: The DCI includes a sidelink carrier index indicating a sidelink carrier used for resource allocation of a physical sidelink control channel (PSCCH) and a physical sidelink shared channel (PSSCH).

19. A non-transitory computer-readable storage medium storing instructions, the instructions being for execution by one or more processors of a user equipment (UE), the one or more processors being for, when the instructions are executed, configuring the UE to: generating type 1 or type 2 sidelink hybrid automatic repeat request-acknowledgement (HARQ-ACK) information bits for sidelink carrier aggregation; and Using sidelink carrier aggregation, type 1 or type 2 sidelink HARQ-ACK information bits are sent to the fifth generation Node B (gNB) on the physical uplink control channel (PUCCH).

20. The medium of claim 19, wherein: When the instructions are executed, the one or more processors are further configured to cause the UE to: determining that an uplink channel or signal is to be transmitted in the uplink carrier, and that a first sidelink physical channel or signal in the first sidelink carrier and a second sidelink physical channel or signal in the second sidelink carrier are to be simultaneously transmitted or received; determining a priority of sidelink transmissions in the first sidelink carrier and the second sidelink carrier, the priority being a minimum priority value among the sidelink transmissions in the first sidelink carrier and the second sidelink carrier; as well as The sidelink transmission having the minimum priority value is selected for transmission or reception.

Images