Cot sharing procedure for unlicensed band communication

Abstract

A computer-readable storage medium stores instructions for configuring a base station for URLLC and for encoding higher-layer signaling for transmission to the UE. The higher-layer signaling includes COT configuration information with multiple COT-shared combinations. Each COT-shared combination specifies a duration and offset. CG UCIs received during the UE's FFP are decoded. The FFP includes the COT and an idle period. The CG UCI includes a COT-shared indication associated with one of the multiple COT-shared combinations. DL transmissions to the UE are performed during the COT. DL transmissions include multiple DL transmission slots corresponding to the duration of the COT-shared combination.

Description

[0001] Priority requirements

[0002] This application claims the priority of the following patent applications:

[0003] U.S. Provisional Patent Application No. 63 / 136,740, filed on January 13, 2021, entitled “UE INITIATING CHANNEL OCCUPANCY TIME (COT) SHARING PROCEDURE FOR ULTRA-RELIABLE AND LOW LATENCY COMMUNICATION (URLLC) OPERATING IN UNLICENSED BAND IN SEMI-STATIC CHANNEL ACCESS MODE”;

[0004] U.S. Provisional Patent Application No. 63 / 216,383, filed on June 29, 2021, entitled "UE INITIATING CHANNEL OCCUPANCY TIME (COT) SHARING PROCEDURE FOR ULTRA-RELIABLE AND LOW LATENCY COMMUNICATION (URLLC) OPERATING IN UNLICENSED BAND IN SEMI-STATIC CHANNEL ACCESS MODE"; and

[0005] U.S. Provisional Patent Application No. 63 / 247,472, filed on September 23, 2021, entitled “UE INITIATING CHANNEL OCCUPANCY TIME (COT) SHARING PROCEDURE FOR ULTRA-RELIABLE AND LOW LATENCY COMMUNICATION (URLLC) OPERATING IN UNLICENSED BAND IN SEMI-STATIC CHANNEL ACCESS MODE”.

[0006] Each of the patent applications listed above is incorporated herein by reference in its entirety. Technical Field

[0007] The various aspects involve wireless communications. Some aspects involve wireless networks, including 3GPP (3rd Generation Partnership Project) networks, 3GPP LTE (Long Term Evolution) networks, 3GPP LTE-A (LTE-Advanced) networks, (MulteFire, LTE-U) and fifth-generation (5G) networks and above (including 5G New Radio (NR) (or 5G-NR) networks, 5G-LTE networks (e.g., 5G NR unlicensed spectrum (NR-U) networks) and other unlicensed networks (including Wi-Fi, CBRS (OnGo), etc.). Other aspects involve techniques for configuring user equipment (UE) to initiate a Channel Occupancy Time (COT) sharing procedure for Ultra Reliable Low Latency Communication (URLLC) operating in unlicensed frequency bands under semi-static channel access mode in 5G-NR (and above) networks. Background Technology

[0008] Mobile communications have evolved significantly from early voice systems to today's highly complex integrated communication platforms. The use of 3GPP LTE systems has increased with the growing number of different types of devices communicating with various network devices. The penetration of mobile devices (User Equipment) in modern society continues to drive demand for a wide variety of connected devices in many diverse environments. Fifth-generation (5G) wireless systems are on the horizon, promising higher speeds, connectivity, and availability. Next-generation 5G networks (or NR networks) are expected to increase throughput, coverage, and robustness, while reducing latency and operational and capital expenditures. 5G-NR networks will continue to evolve based on 3GPP LTE-Advanced with the addition of potential new Radio Access Technologies (RATs) to enrich people's lives through seamless wireless connectivity solutions that deliver fast, rich content, and services. With current cellular network frequencies saturated, higher frequencies (e.g., millimeter wave (mmWave) frequencies) will be beneficial due to their higher bandwidth.

[0009] Potential LTE operations in unlicensed spectrum include (but are not limited to) LTE operations via dual connectivity (DC) or DC-based LAA, and standalone LTE systems in unlicensed spectrum (under which LTE-based technologies operate only in unlicensed spectrum without requiring "anchoring" in licensed spectrum) are referred to as MulteFire. Further enhanced operations of LTE and NR systems in licensed and unlicensed spectrum are anticipated in future releases and 5G (and above) systems. These enhanced operations may include URLLC techniques for UE-initiated COT sharing procedures for operation in unlicensed bands under semi-static channel access mode in 5G-NR (and above) networks. Attached Figure Description

[0010] In accompanying drawings that are not necessarily drawn to scale, similar reference numerals can describe similar parts in different views. Similar numbers with different letter suffixes can represent different instances of similar parts. The accompanying drawings generally illustrate the various aspects discussed in this document by way of example rather than limitation.

[0011] Figure 1A The network architecture is shown based on several aspects.

[0012] Figure 1B and Figure 1C The non-roaming 5G system architecture is shown based on some aspects.

[0013] Figure 2 , Figure 3 and Figure 4 Various systems, devices, and components are shown that can implement aspects of the disclosed embodiments.

[0014] Figure 5 A diagram showing the first operating mode of COT sharing for UE based on some aspects is provided.

[0015] Figure 6 A diagram illustrating a second operating mode for COT sharing for UEs is shown, based on several aspects.

[0016] Figure 7 This is a diagram illustrating UL to DLCOT sharing when the base station is allowed to schedule inter-UE FFP UL transmissions, based on some aspects.

[0017] Figure 8 This is a diagram illustrating UL to DLCOT sharing when the base station is allowed to schedule only other UEs' FFP-based UL transmissions, according to some aspects.

[0018] Figure 9 This is a diagram illustrating the UL to DL COT sharing process according to some aspects.

[0019] Figure 10 A block diagram is shown for communication equipment (e.g., evolved Node B (eNB), next-generation Node B (gNB) (or another RAN node), access point (AP), radio station (STA), mobile station (MS) or user equipment (UE)) based on some aspects. Detailed Implementation

[0020] The following description and figures fully illustrate the aspects to enable those skilled in the art to implement them. Other aspects may be combined with structural variations, logical variations, electrical variations, process variations, and other variations. Parts and features of some aspects may be included or replaced by parts and features of other aspects. The aspects set forth in the claims cover all available equivalents of those claims.

[0021] Figure 1A A network architecture based on several aspects is illustrated. Network 140A is shown as including User Equipment (UE) 101 and UE 102. UE 101 and 102 are shown as smartphones (e.g., handheld touchscreen mobile computing devices that can connect to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as a personal digital assistant (PDA), pager, laptop computer, desktop computer, cordless phone, drone, or any other computing device including wired and / or wireless communication interfaces. UE 101 and 102 may be collectively referred to herein as UE 101, and UE 101 may be used to perform one or more of the techniques disclosed herein.

[0022] Any radio link described herein (e.g., a radio link used in Network 140A or any other network shown) may operate according to any exemplary radio communication technology and / or standard.

[0023] LTE and LTE-Advanced are standards for high-speed data wireless communication for UEs such as mobile phones. In LTE-Advanced and various wireless systems, carrier aggregation is a technique that allows multiple carrier signals operating at different frequencies to carry communication for a single UE, thus increasing the bandwidth available for a single device. In some aspects, carrier aggregation can be used when one or more component carriers operate on unlicensed frequencies.

[0024] The aspects described herein can be used in the context of any spectrum management scheme, including, for example, dedicated licensed spectrum, unlicensed spectrum, and (licensed) shared spectrum (e.g., licensed shared access (LSA) in the 2.3–2.4 GHz, 3.4–3.6 GHz, 3.6–3.8 GHz and other frequencies, and spectrum access systems (SAS) in the 3.55–3.7 GHz and other frequencies).

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

[0026] In some aspects, either UE 101 or 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 utilizing short-lived UE connections. In some aspects, either UE 101 or 102 may include a narrowband (NB) IoT UE (e.g., enhanced NB-IoT (eNB-IoT) UE and further enhanced (FeNB-IoT) UE). The IoT UE may utilize technologies such as machine-to-machine (M2M) or machine-type communication (MTC) to exchange data with an MTC server or device via a Public Land Mobile Network (PLMN), ProSe or Device-to-Device (D2D) communication, sensor network, or IoT network. M2M or MTC data exchange may be machine-initiated data exchange. The IoT network includes interconnected IoT UEs with short-lived connections (which may include uniquely identifiable embedded computing devices within the Internet infrastructure). The IoT UE may execute background applications (e.g., keep-alive messages, state updates, etc.) to facilitate connectivity within the IoT network.

[0027] In some respects, either UE 101 or 102 may include an enhanced MTC (eMTC) UE or a further enhanced MTC (FeMTC) UE.

[0028] UEs 101 and 102 can be configured to connect (e.g., communicate coupled) to a radio access network (RAN) 110. RAN 110 can be, for example, Universal Mobile Telecommunications System (UMTS), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), Next Generation RAN (NG RAN), or some other type of RAN. UEs 101 and 102 utilize connections 103 and 104, respectively, each connection including a physical communication interface or layer (discussed in further detail below); in this example, connections 103 and 104 are shown as air interfaces for implementing communication coupling and can comply with cellular communication protocols such as Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA) network protocols, Push-to-Talk (PTT) protocols, PTT on Cellular (POC) protocols, Universal Mobile Telecommunications System (UMTS) protocols, 3GPP Long Term Evolution (LTE) protocols, 5G protocols, New Radio (NR) protocols, etc.

[0029] In one aspect, UEs 101 and 102 can also directly exchange communication data via ProSe interface 105. ProSe interface 105 may also be referred to as a sidelink interface, which includes one or more logical channels, including but not limited to the Physical Sidelink Control Channel (PSCCH), Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Discovery Channel (PSDCH), and Physical Sidelink Broadcast Channel (PSBCH).

[0030] UE 102 is shown configured to access access point (AP) 106 via connection 107. Connection 107 may include a local wireless connection, such as a connection conforming to any IEEE 802.11 protocol, according to which AP 106 may include Wi-Fi. 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).

[0031] RAN 110 may include one or more access nodes that implement the connection between 103 and 104. These access nodes (ANs) may be referred to as base stations (BS), NodeBs, evolved NodeBs (eNBs), next-generation NodeBs (gNBs), RAN network 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, communication nodes 111 and 112 may be transmit / receive points (TRPs). In the case that communication nodes 111 and 112 are NodeBs (e.g., eNBs or gNBs), one or more TRPs may operate within the communication cell of the NodeB. RAN 110 may include one or more RAN nodes (e.g., macro RAN node 111) for providing macro cells, and one or more RAN nodes (e.g., low-power (LP) RAN node 112 or secondary RAN node 112 based on unlicensed spectrum) for providing femtocells or picocells (e.g., cells with smaller coverage areas, smaller user capacity, or higher bandwidth compared to macro cells).

[0032] Either RAN node 111 or 112 can terminate the air interface protocol and can be the first contact point for UEs 101 and 102. In some aspects, either RAN node 111 or 112 can implement various logical functions for RAN 110, including but not limited to Radio Network Controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management, data packet scheduling, and mobility management. In the example, either node 111 and / or 112 can be a Next Generation Node B (gNB), an Evolved Node B (eNB), or another type of RAN node.

[0033] RAN 110 is shown as being communicatively coupled to core network (CN) 120 via S1 interface 113. In various respects, 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 referenced). Figure 1B-1C (As shown). In this respect, the S1 interface 113 is divided into two parts: the S1-U interface 114, which carries user service data between RAN nodes 111 and 112 and the serving gateway (S-GW) 122; and the S1-Mobility Management Entity (MME) interface 115, which is the signaling interface between RAN nodes 111 and 112 and the MME 121.

[0034] 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 functionally resemble the control plane of a Legacy Service General Packet Radio Service (GPRS) Support Node (SGSN). MME 121 can manage mobility aspects of access, such as gateway selection and tracking area list management. HSS 124 can include a database (including subscription-related information) for network users to support network entities in handling communication sessions. CN 120 can include one or more HSS 124s, depending on the number of mobile subscribers, equipment capacity, network organization, etc. For example, HSS 124 can provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependencies, etc.

[0035] The S-GW 122 can terminate the S1 interface 113 toward RAN 110 and route data packets between RAN 110 and CN 120. Furthermore, the S-GW 122 can serve as a local mobility anchor for handover between RAN nodes and can also provide anchoring for inter-3GPP mobility. Other responsibilities of the S-GW 122 may include lawful interception, charging, and some policy enforcement.

[0036] P-GW 123 can terminate the SGi interface toward the PDN. P-GW 123 can route data packets between EPC network 120 and external networks (e.g., networks including application server 184 (alternately referred to as application function (AF)) via Internet Protocol (IP) interface 125. P-GW 123 can also pass data to other external networks 131A (which may include the Internet, IP Multimedia Subsystem (IPS) networks, and other networks). Typically, application server 184 can be an element that provides IP bearer resources for use with the core network (e.g., UMTS Packet Service (PS) domain, LTE PS data service, etc.). In this respect, P-GW 123 is shown communicatively coupled to application server 184 via IP interface 125. Application server 184 can 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 CN 120.

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

[0038] In some aspects, the communication network 140A can be an IoT network or a 5G network, including 5G NR networks using licensed (5G NR) and unlicensed (5G NR-U) spectrum for communication. One current implementer of IoT is narrowband IoT (NB-IoT).

[0039] The NG system architecture may include a RAN 110 and a 5G network core (5GC) 120. The NG-RAN 110 may include multiple nodes, such as gNBs and NG-eNBs. The core network 120 (e.g., a 5G core network or 5GC) may include Access and Mobility Functions (AMF) and / or User Plane Functions (UPF). The AMF and UPF may be communicatively coupled to the gNB and NG-eNB via NG interfaces. More specifically, in some aspects, the gNB and NG-eNB may connect 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.

[0040] In some aspects, the NG system architecture can use reference points between nodes as provided in 3GPP Technical Specification (TS) 23.501 (e.g., V15.4.0, December 2018). In some aspects, each of the gNB and NG-eNB can be implemented as a base station, mobile edge server, small cell, home eNB, RAN network node, etc. In some aspects, the gNB can be the primary node (MN) in a 5G architecture, while the NG-eNB can be a secondary node (SN). In some aspects, the primary / major node can operate in licensed frequency bands, while the secondary node can operate in unlicensed frequency bands.

[0041] Figure 1B The non-roaming 5G system architecture is illustrated based on several aspects. (See reference...) Figure 1BThe 5G system architecture 140B is illustrated with reference points. More specifically, UE 102 can communicate with RAN 110 and one or more other 5G core (5GC) network entities. The 5G system architecture 140B includes multiple network functions (NFs), such as Access and Mobility Management Function (AMF) 132, Location Management Function (LMF) 133, Session Management Function (SMF) 136, Policy Control Function (PCF) 148, Application Function (AF) 150, User Plane Function (UPF) 134, Network Slice Selection Function (NSSF) 142, Authentication Server Function (AUSF) 144, and Unified Data Management (UDM) / Home Subscriber Server (HSS) 146. UPF 134 can provide connectivity to a data network (DN) 152, which may include, for example, operator services, internet access, or third-party services. AMF 132 can be used to manage access control and mobility, and may also include network slice selection functionality. SMF 136 can be configured to establish and manage various sessions according to network policies. UPF 134 can be deployed in one or more configurations depending on the desired service type. 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).

[0042] LMF 133 can be used in conjunction with 5G positioning functionality. In some aspects, LMF 133 receives measurement and assistance information from Next Generation Radio Access Network (NG-RAN) 110 and mobile devices (e.g., UE 101) via the NLs interface through AMF 132 to calculate the location of UE 101. In some aspects, NR Positioning Protocol A (NRPPa) can be used to carry positioning information between NG-RAN and LMF 133 via Next Generation Control Plane Interface (NG-C). In some aspects, LMF 133 uses the LTE Positioning Protocol (LPP) to configure the UE via AMF 132. NG RAN 110 uses the Radio Resource Control (RRC) protocol via the LTE-Uu and NR-Uu interfaces to configure UE 101.

[0043] In some aspects, the 5G system architecture 140B is configured with different reference signals to enable positioning measurements. Example reference signals that can be used for positioning measurements include the Positioning Reference Signal (NR PRS) in the downlink and the Detection Reference Signal (SRS) for positioning in the uplink. The downlink Positioning Reference Signal (PRS) is a reference signal configured to support downlink-based positioning methods.

[0044] 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 Function (CSCF)). More specifically, the IMS 168B includes a CSCF that can act as a proxy CSCF (P-CSCF) 162B, a serving CSCF (S-CSCF) 164B, and an emergency CSCF (E-CSCF). Figure 1B (Not shown in the image) or query the CSCF (I-CSCF) 166B. The P-CSCF 162B can be configured as the first contact point for UE 102 within the IM subsystem (IMS) 168B. The S-CSCF 164B can be configured to handle session states in the network, and the E-CSCF can 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 can be configured as the contact point within the operator's network for all IMS connections to subscribers whose destination is that network operator or roaming subscribers currently located within that network operator's service area. In some aspects, the I-CSCF 166B can connect to another IP multimedia network 170E, such as an IMS operated by a different network operator.

[0045] In some respects, the UDM / HSS 146 can be coupled to an application server 160B, which may include a Telephone Application Server (TAS) or another application server (AS). The AS 160B can be coupled to the IMS 168B via an S-CSCF 164B or an I-CSCF 166B.

[0046] Reference points indicate that interaction is possible between corresponding NF services. For example, Figure 1BThe following reference points are shown: N1 (between UE 102 and AMF 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, not shown), N6 (between UPF 134 and DN 152), N7 (between SMF 136 and PCF 148, not shown), N8 (between UDM 146 and AMF 132, not shown), N9 (between the two UPF 134, not shown), N10 (between UDM 146 and SMF 136, not shown), N11 (between AMF 132 and SMF 136, not shown), N12 (between AUSF 144 and AMF 132, not shown), N13 (between AUSF 144 and AMF 132, not shown). N14 (between PCF 144 and UDM 146, not shown), N14 (between the two AMF 132s, not shown), N15 (between PCF 148 and AMF 132 in non-roaming scenarios, or between PCF 148 and the visited network and AMF 132 in roaming scenarios, not shown), N16 (between the two SMFs, not shown), and N22 (between AMF 132 and NSSF 142, not shown). Alternatively, you can use... Figure 1B Other reference points not shown in the text are indicated.

[0047] Figure 1C The 5G system architecture 140C and its service-based representation are shown. In addition... Figure 1B In addition to the network entities shown, system architecture 140C may also include Network Open Function (NEF) 154 and Network Repository Function (NRF) 156. In some aspects, the 5G system architecture may be service-based, and the interaction between network functions may be represented by corresponding point-to-point reference points Ni, or represented as service-based interfaces.

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

[0049] Figure 2 , Figure 3 and Figure 4 Various systems, devices, and components are illustrated that can implement aspects of the disclosed embodiments in different communication systems, such as 5G-NR (and above) networks. Figure 1A-4 The discussed UE, base station (e.g., gNB) and / or other nodes (e.g., satellite or other NTN nodes) can be configured to perform the disclosed technologies.

[0050] Figure 2 Network 200 according to various embodiments is illustrated. Network 200 can operate in a manner consistent with 3GPP technical specifications for LTE or 5G / NR systems. However, the example embodiments are not limited thereto, and the described embodiments can be applied to other networks (e.g., future 3GPP systems, etc.) that benefit from the principles described herein.

[0051] Network 200 may include UE 202, which may include any mobile or non-mobile computing device designed to communicate with RAN 204 via an over-the-air connection. UE 202 may be, but is not limited to, smartphones, tablets, wearable computing devices, desktop computers, laptops, in-vehicle infotainment systems, in-vehicle entertainment systems, dashboards, head-mounted displays, onboard diagnostic equipment, dashboard mobile devices, mobile data terminals, electronic engine management systems, electronic / engine control units, electronic / engine control modules, embedded systems, sensors, microcontrollers, control modules, engine management systems, networked devices, machine-type communication devices, M2M or D2D devices, IoT devices, etc.

[0052] In some embodiments, network 200 may include a plurality of UEs that are directly coupled to each other via sidelink interfaces. The UEs may be M2M / D2D devices that communicate using physical sidelink channels (e.g., but not limited to PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.).

[0053] In some embodiments, UE 202 may additionally communicate with AP 206 via an over-the-air connection. AP 206 may manage WLAN connections, which may be used to offload some / all network services from RAN 204. The connection between UE 202 and AP 206 may conform to any IEEE 802.11 protocol, wherein AP 206 may be a Wireless Fibre Channel device. Router. In some embodiments, UE 202, RAN 204, and AP 206 may utilize cellular-WLAN aggregation (e.g., LWA / LWIP). Cellular-WLAN aggregation may involve UE 202 being configured by RAN 204 to utilize both cellular radio resources and WLAN resources.

[0054] RAN 204 may include one or more access nodes (e.g., access node (AN) 208). AN 208 may terminate the air interface protocol for UE 202 by providing access layer protocols including RRC, Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), MAC, and L1 protocols. In this way, AN 208 can provide data / voice connectivity between core network (CN) 220 and UE 202. In some embodiments, AN 208 may be implemented in a discrete device or as one or more software entities running on a server computer as part of, for example, a virtual network (which may be referred to as CRAN or a virtual baseband unit pool). AN 208 may be referred to as BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. AN 208 may be a macrocell base station or a low-power base station, where the low-power base station is used to provide femtocells, picocells, or other similar cells with smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.

[0055] In embodiments where RAN 204 includes multiple ANs, they may be coupled to each other via an X2 interface (if RAN 204 is an LTE RAN) or an Xn interface (if RAN 204 is a 5G RAN). The X2 / Xn interfaces (in some embodiments, they may be separated into control / user plane interfaces) allow ANs to pass information related to handover, data / context delivery, mobility, load management, interference coordination, etc.

[0056] Each AN of RAN 204 can manage one or more cells, cell groups, component carriers, etc., to provide an air interface for network access to UE 202. UE 202 can simultaneously connect to multiple cells provided by the same or different ANs of RAN 204. For example, UE 202 and RAN 204 can use carrier aggregation to allow UE 202 to connect to multiple component carriers (each corresponding to a Pcell or Scell). In a dual-connectivity scheme, the first AN can be the primary node providing the MCG, while the second AN can be the secondary node providing the SCG. The first / second AN can be any combination of eNB, gNB, ng-eNB, etc.

[0057] RAN 204 can provide an air interface on either licensed or unlicensed spectrum. For operation in unlicensed spectrum, nodes can use LAA, eLAA, and / or feLAA mechanisms based on CA technology with PCells / Scells. Before accessing unlicensed spectrum, nodes can perform medium / carrier sensing operations based on, for example, a Listen-Before-Speak (LBT) protocol.

[0058] In a V2X scenario, UE 202 or AN 208 can be or may act as a Roadside Unit (RSU), where RSU can refer to any traffic infrastructure entity used for V2X communication. An RSU can be implemented in, or by, a suitable AN or a stationary (or relatively stationary) UE. An RSU implemented in or by the following can be referred to as a "UE-type RSU" for a UE; an "eNB-type RSU" for an eNB; a "gNB-type RSU" for a gNB; and so on. In one example, an RSU is a computing device coupled to radio frequency circuitry located on the roadside that provides connectivity support to passing vehicle UEs. An RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling oncoming vehicle and pedestrian traffic. An RSU can provide extremely low-latency communication required for high-speed events such as collision avoidance, traffic warnings, etc. Additionally or alternatively, an RSU may provide other cellular / WLAN communication services. RSU components can be enclosed in a weatherproof enclosure suitable for outdoor installation and may include a network interface controller for providing wired connectivity (e.g., Ethernet) to traffic signal controllers or backhaul networks.

[0059] In some embodiments, RAN 204 may be an LTE RAN 210 with an eNB (e.g., eNB 212). LTE RAN 210 may provide an LTE air interface with the following characteristics: a subcarrier spacing (SCS) of 15 kHz; CP-OFDM waveforms for downlink (DL) and SC-FDMA waveforms for uplink (UL); turbo codes for data and TBCC for control; etc. The LTE air interface may rely on: CSI-RS for CSI acquisition and beam management; PDSCH / PDCCHDMRS for PDSCH / PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurement, and channel estimation with respect to coherent demodulation / detection at the UE. The LTE air interface may operate in the sub-6 GHz band.

[0060] In some embodiments, RAN 204 may be an NG-RAN 214 with gNBs (e.g., gNB 216) or ng-eNBs (e.g., ng-eNB 218). gNB 216 can connect to a 5G-enabled UE using a 5G NR interface. gNB 216 can connect to the 5G core via an NG interface, which may include an N2 interface or an N3 interface. ng-eNB 218 can also connect to the 5G core via an NG interface, but can connect to the UE via an LTE air interface. gNB 216 and ng-eNB 218 can connect via an Xn interface.

[0061] In some embodiments, the NG interface can be divided into two parts: the NG user plane (NG-U) interface, which carries service data between the nodes of NG-RAN 214 and UPF 248 (e.g., the N3 interface); and the NG control plane (NG-C) interface, which is the signaling interface between the nodes of NG-RAN 214 and AMF 244 (e.g., the N2 interface).

[0062] NG-RAN 214 can provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar codes, repetition codes, simplex codes and Reed-Muller codes for control, and LDPC for data. Similar to the LTE air interface, the 5G-NR air interface can rely on CSI-RS and PDSCH / PDCCH DMRS. The 5G-NR air interface may not use CRS, but can use: PBCH DMRS for PBCH demodulation; PTRS for phase tracking of the PDSCH; and a tracking reference signal for time tracking. The 5G-NR air interface can operate on the FR1 band, which includes the sub-6GHz band, or the FR2 band, which includes the band from 24.25GHz to 52.6GHz. The 5G-NR air interface may include a synchronization signal and a physical broadcast channel (SS / PBCH) block SSB, where the SSB is an area of ​​the downlink resource grid that includes the PSS / SSS / PBCH.

[0063] In some embodiments, the 5G-NR air interface can utilize portion bandwidth (BWP) for various purposes. For example, BWPs can be used for dynamic adaptation of SCS. For instance, UE 202 can be configured with multiple BWPs, each configured with a different SCS. When a BWP is indicated to UE 202 for a change, the transmitted SCS also changes. Another example of a BWP use case relates to power saving. Specifically, multiple BWPs with different amounts of frequency resources (e.g., PRBs) can be configured for UE 202 to support data transmission under different traffic load scenarios. A BWP containing a smaller number of PRBs can be used for data transmission with low traffic loads, while allowing power saving at UE 202 and, in some cases, at gNB 216. A BWP containing a larger number of PRBs can be used for scenarios with high traffic loads.

[0064] RAN 204 is communicatively coupled to CN 220, which includes network elements for providing various functions, to support data and telecommunications services to customers / subscribers (e.g., users of UE 202). Components of CN 220 may be implemented in a single physical node or in separate physical nodes. In some embodiments, NFV may be utilized to virtualize any or all functions provided by the network elements of CN 220 onto physical computing / storage resources such as servers, switches, etc. A logical instantiation of CN 220 may be referred to as a network slice, while a logical instantiation of a portion of CN 220 may be referred to as a network subslice.

[0065] In some embodiments, CN 220 can be connected to an LTE radio network as part of an Enhanced Packet System (EPS) 222 (which may also be referred to as EPC (or Enhanced Packet Core)). EPC 222 may include MME 224, SGW 226, SGSN 228, HSS 230, PGW 232, and PCRF 234, which are coupled to each other via interfaces (or “reference points”), as shown in the figure. The functions of the components of EPC 222 can be briefly described below.

[0066] MME 224 can implement mobility management functions to track the current location of UE 202 to facilitate paging, bearer activation / deactivation, handover, gateway selection, authentication, etc.

[0067] The SGW 226 can terminate the S1 interface toward the RAN and route data packets between the RAN and EPC 222. The SGW 226 can serve as a local mobility anchor for handover between RAN nodes and can also provide anchoring for inter-3GPP mobility. Other responsibilities may include lawful interception, charging, and some policy enforcement.

[0068] SGSN 228 can track the location of UE 202 and perform security functions and access control. Furthermore, SGSN 228 can perform EPC inter-node signaling for mobility between different RAT networks; PDN and S-GW selection specified by MME 224; MME selection for handover; etc. The S3 reference point between MME 224 and SGSN 228 enables the exchange of user and bearer information for 3GPP indirect network access mobility in idle / active states.

[0069] HSS 230 may include a database (including subscription-related information) for network users to support network entities in processing communication sessions. HSS 230 can provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependencies, etc. The S6a reference point between HSS 230 and MME 224 enables the transmission of subscription and authentication data for authenticating / authorizing user access to LTE CN 220.

[0070] PGW 232 may terminate its SGi interface toward a data network (DN) 236, which may include an application / content server 238. PGW 232 may route data packets between the LTE CN 220 and the data network 236. PGW 232 may be coupled to SGW 226 via an S5 reference point to facilitate user plane tunneling and tunnel management. PGW 232 may also include nodes for policy enforcement and charging data collection (e.g., PCEF). Furthermore, the SGi reference point between PGW 232 and the data network 236 may be an external public or private PDN or an internal packet data network (e.g., for IMS service allocation). PGW 232 may be coupled to PCRF 234 via a Gx reference point.

[0071] PCRF 234 is the policy and charging control element of LTE CN 222. PCRF 234 can be communicatively coupled to application / content server 238 to determine appropriate QoS and charging parameters for service flows. PCRF 232 can assign association rules (via Gx reference point) to PCEF using appropriate TFTs and QCIs.

[0072] In some embodiments, CN 220 may be 5GC 240. 5GC 240 may include AUSF 242, AMF 244, SMF 246, UPF 248, NSSF 250, NEF 252, NRF 254, PCF 256, UDM 258, and AF 260, which are coupled to each other via interfaces (or “reference points”), as shown in the figure. The functionality of the components of 5GC 240 can be briefly described below.

[0073] The AUSF 242 can store data for UE 202 authentication and handle authentication-related functions. The AUSF 242 facilitates a common authentication framework for various access types. In addition to communicating with other components of the 5GC 240 via a reference point as shown, the AUSF 242 can also demonstrate an interface based on Nausf services.

[0074] AMF 244 allows other functions of 5GC 240 to communicate with UE 202 and RAN 204 and subscribe to notifications regarding mobility events for UE 202. AMF 244 can handle registration management (e.g., for registering UE 202), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. AMF 244 can provide transport for SM messages between UE 202 and SMF 246 and act as a transparent broker for routing SM messages. AMF 244 can also provide transport for SMS messages between UE 202 and SMSF. AMF 244 can interact with AMF 242 and UE 202 to perform various security anchoring and context management functions. Furthermore, AMF 244 can be the termination point of the RAN CP interface, which may include or be the N2 reference point between RAN 204 and AMF 244; and AMF 244 can be the termination point of NAS (N1) signaling, performing NAS encryption and integrity protection. AMF 244 can also support NAS signaling with UE 202 via the N3IWF interface.

[0075] SMF 246 can be responsible for SM (e.g., session establishment and tunnel management between UPF 248 and AN 208); UE IP address allocation and management (including optional authorization); selection and control of UP functions; configuring service bootstrapping at UPF 248 to route services to the correct destination; terminating the interface for policy control functions; controlling policy enforcement, charging, and QoS as part of the process; lawful interception (for SM events and interfaces to the LI system); terminating the SM portion of NAS messages; downlink data notification; initiating AN-specific SM information sent to AN 208 on N2 via AMF 244; and determining the SSC mode of the session. SM can refer to the management of PDU sessions, while a PDU session or “session” can refer to the PDU connectivity service that provides or enables the exchange of PDUs between UE 202 and data network 236.

[0076] UPF 248 can serve as an anchor point for intra- and inter-RAT mobility, an external PDU session point for interconnecting with data network 236, and a branch point for supporting multi-homed PDU sessions. UPF 248 can also perform packet routing and forwarding, packet inspection, user plane portion enforcement of policy rules, lawful packet interception (UP collection), service usage reporting, QoS processing for user plane (e.g., packet filtering, gating, UL / DL rate enforcement), uplink service verification (e.g., SDF-to-QoS flow mapping), transport-level packet marking in uplink and downlink, and downlink packet buffering and downlink data notification triggering. UPF 248 may include an uplink classifier to support routing service flows to the data network.

[0077] NSSF 250 can select a set of network slice instances to serve UE 202. If needed, NSSF 250 can also determine the allowed NSSAIs and the mapping to subscribed S-NSSAIs. NSSF 250 can also determine the set of AMFs or a list of candidate AMFs to serve UE 202 based on appropriate configuration and, possibly, by querying NRF 254. The selection of a set of network slice instances for UE 202 can be triggered by AMF 244, to which UE 202 is registered, interacting with NSSF 250, which may result in a change of AMF. NSSF 250 can interact with AMF 244 via reference point N22; and can communicate with another NSSF in the visited network via reference point N31 (not shown). Furthermore, NSSF 250 can expose an interface based on NNSSF services.

[0078] NEF 252 can securely expose services and capabilities provided by 3GPP network functions to third parties, internal open / reopened systems, AFs (e.g., AF 260), edge computing, or fog computing systems. In these embodiments, NEF 252 can authenticate, authorize, or restrict AFs. NEF 252 can also translate information exchanged with AF 260 and information exchanged with internal network functions. For example, NEF 252 can translate between AF service identifiers and internal 5GC information. NEF 252 can also receive information from other NFs based on the capabilities of other open NFs. This information can be stored as structured data at NEF 252 or stored at a data storage NF using a standardized interface. The stored information can then be reopened by NEF 252 to other NFs and AFs, or used for other purposes (e.g., analysis). Furthermore, NEF 252 can expose interfaces based on Nnef services.

[0079] NRF 254 supports service discovery, receiving NF discovery requests from NF instances and providing information about discovered NF instances to those instances. NRF 254 also maintains information about available NF instances and the services they support. As used herein, the terms "instantiate," "instantiation," etc., can refer to the creation of an instance, and "instance" can refer to the concrete occurrence of an object (which may occur, for example, during the execution of program code). Furthermore, NRF 254 can demonstrate interfaces based on NRF services.

[0080] PCF 256 can provide policy rules to control plane functions for enforcement and can also support a unified policy framework to govern network behavior. PCF 256 can also implement a front-end to access subscription information related to policy decisions in the UDR of UDM 258. In addition to communicating with functions via reference points as shown, PCF 256 also demonstrates an interface based on Npcf services.

[0081] UDM 258 can process subscription-related information to support network entities in handling communication sessions and can store subscription data for UE 202. For example, subscription data can be passed via the N8 reference point between UDM 258 and AMF 244. UDM 258 can include two parts: an application front-end and a UDR. The UDR can store subscription and policy data for UDM 258 and PCF 256, and / or structured data for open access and application data for NEF 252 (including PFD for application detection and application request information for multiple UE 202). The UDR can expose an interface based on Nudr services to allow UDM 258, PCF 256, and NEF 252 to access a specific set of stored data, as well as read, update (e.g., add, modify), delete, and subscribe to notifications of relevant data changes in the UDR. UDM can include UDM-FE, which is responsible for handling credentials, location management, subscription management, etc. Several different front-ends can serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identity processing, access authorization, registration / mobility management, and subscription management. In addition to communicating with other NFs via reference points as shown, the UDM 258 can also demonstrate interfaces based on Nudm services.

[0082] AF 260 can provide application impact on service routing, provide access to NEF, and interact with the policy framework for policy control.

[0083] In some embodiments, 5GC 240 can implement edge computing by selecting operator / third-party services as geographically proximate points where UE 202 attaches to the network. This reduces latency and load on the network. To provide edge computing implementation, 5GC 240 can select a UPF 248 proximate to UE 202 and perform service routing from UPF 248 to data network 236 via the N6 interface. This can be based on UE subscription data, UE location, and information provided by AF 260. In this way, AF 260 can influence UPF (re)selection and service routing. Based on operator deployment, when AF 260 is considered a trusted entity, the network operator can allow AF 260 to interact directly with the relevant NF. Furthermore, AF 260 can expose interfaces based on Naf services.

[0084] Data network 236 can represent various network operator services, Internet access, or third-party services that can be provided by one or more servers (including, for example, application / content server 238).

[0085] Figure 3 A wireless network 300 according to various embodiments is schematically illustrated. The wireless network 300 may include a UE 302 that wirelessly communicates with an AN 304. The UE 302 and AN 304 may be similar to and substantially interchangeable with components of the same name described elsewhere herein.

[0086] UE 302 can be communicatively coupled to AN 304 via connection 306. Connection 306 is shown as an air interface for communication coupling and can conform to cellular communication protocols (e.g., LTE protocol or 5G NR protocol operating at mmWave or sub-6GHz frequencies).

[0087] UE 302 may include a host platform 308 coupled to a modem platform 310. Host platform 308 may include application processing circuitry 312 coupled to protocol processing circuitry 314 of modem platform 310. Application processing circuitry 312 may run various applications for giving / receiving application data for UE 302. Application processing circuitry 312 may also implement one or more layer operations to send / receive application data to / from a data network. These layer operations may include transport (e.g., UDP) and Internet (e.g., IP) operations.

[0088] Protocol processing circuitry 314 can implement one or more layer operations to facilitate the transmission or reception of data via connection 306. Layer operations implemented by protocol processing circuitry 314 may include, for example, MAC, RLC, PDCP, RRC, and NAS operations.

[0089] The modem platform 310 may also include digital baseband circuitry 316, which can implement one or more layer operations as “lower” layer operations performed by protocol processing circuitry 314 in the network protocol stack. These operations may include, for example, PHY operations, which include one or more of the following: HARQ-ACK function, scrambling / descrambling, encoding / decoding, layer mapping / demapping, modulation symbol mapping, received symbol / bit metric determination, multi-antenna port precoding / decoding (which may include one or more of space-time, space-frequency, or spatial coding), reference signal generation / detection, preamble sequence generation and / or decoding, synchronization sequence generation / detection, blind decoding of control channel signals, and other related functions.

[0090] The modem platform 310 may also include transmitting circuitry 318, receiving circuitry 320, RF circuitry 322, and an RF front-end (RFFE) 324, which may include or be connected to one or more antenna panels 326. In short, transmitting circuitry 318 may include a digital-to-analog converter, mixer, intermediate frequency (IF) component, etc.; receiving circuitry 320 may include an analog-to-digital converter, mixer, IF component, etc.; RF circuitry 322 may include a low-noise amplifier, power amplifier, power point tracking component, etc.; RFFE 324 may include filters (e.g., surface acoustic wave filters), switches, antenna tuners, beamforming components (e.g., phased array antenna components), etc. The selection and arrangement of the components (generally referred to as "transmit / receive components") of transmitting circuitry 318, receiving circuitry 320, RF circuitry 322, RFFE 324, and antenna panels 326 may be specific to implementation details (e.g., whether the communication is TDM or FDM, in mmWave or sub-6GHz frequencies, etc.). In some embodiments, the transmitting / receiving components may be arranged in multiple parallel transmitting / receiving chains, may be located in the same or different chips / modules, etc.

[0091] In some embodiments, the protocol processing circuitry 314 may include one or more instances of control circuitry (not shown) to provide control functions for the transmitting / receiving components.

[0092] UE reception can be established via and through antenna panel 326, RFFE 324, RF circuit 322, receiving circuit 320, digital baseband circuit 316, and protocol processing circuit 314. In some embodiments, antenna panel 326 can receive transmissions from AN 304 through receive beamforming signals received by a plurality of antennas / antenna elements of one or more antenna panels 326.

[0093] UE transmission can be established via and through protocol processing circuitry 314, digital baseband circuitry 316, transmission circuitry 318, RF circuitry 322, RFFE 324, and antenna panel 326. In some embodiments, the transmission components of UE 302 may apply a spatial filter to the data to be transmitted to form a transmission beam emitted by the antenna elements of antenna panel 326.

[0094] Similar to UE 302, AN 304 may include a host platform 328 coupled to a modem platform 330. The host platform 328 may include application processing circuitry 332 coupled to protocol processing circuitry 334 of the modem platform 330. The modem platform may also include digital baseband circuitry 336, transmitting circuitry 338, receiving circuitry 340, RF circuitry 342, RFFE circuitry 344, and antenna panel 346. Components of AN 304 may be similar to and substantially interchangeable with their namesake components in UE 302. In addition to performing data transmission / reception as described above, components of AN 304 may also perform various logical functions, including, for example, RNC functions (e.g., radio bearer management, uplink and downlink dynamic radio resource management, and packet scheduling).

[0095] Figure 4 This is a block diagram illustrating components according to some example embodiments, which are capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any or more methods discussed herein. Specifically, Figure 4 The illustration shows a schematic representation of hardware resource 400, which includes one or more processors (or processor cores) 410, one or more memory / storage devices 420, and one or more communication resources 430, each of which may be communicatively coupled via bus 440 or other interface circuitry. In embodiments utilizing node virtualization (e.g., NFV), a hypervisor 402 may be executed to provide an execution environment for one or more network slices / subslices to utilize hardware resource 400.

[0096] Processor 410 may include, for example, processor 412 and processor 414. Processor 410 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP (e.g., a baseband processor), an ASIC, an FPGA, a radio frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

[0097] Memory / storage device 420 may include main memory, disk storage, or any suitable combination thereof. Memory / storage device 420 may include, but is not limited to, any type of volatile, non-volatile, or semi-volatile memory (e.g., dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state storage, etc.).

[0098] Communication resource 430 may include an interconnect or network interface controller, component, or other suitable device for communicating with one or more peripheral devices 404 or one or more databases 406 or other network elements via network 408. For example, communication resource 430 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, etc. (or low power consumption) ) components, Components and other communication components.

[0099] Instructions 450 may include software, programs, applications, applets, apps, or other executable code for causing at least any processor 410 to perform any one or more of the methods discussed herein. Instructions 450 may reside wholly or partially within at least one of the processor 410 (e.g., within the processor's cache memory), memory / storage device 420, or any suitable combination thereof. Furthermore, any portion of instructions 450 may be transferred from any combination of peripheral device 404 or database 406 to hardware resource 400. Thus, the memory of processor 410, memory / storage device 420, peripheral device 404, and database 406 are examples of computer-readable and machine-readable media.

[0100] For one or more embodiments, at least one of the components outlined in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, and / or methods as outlined in the Examples section below. For example, baseband circuitry associated with one or more of the foregoing figures may be configured to operate according to one or more of the examples set forth below. As another example, circuitry associated with a UE, base station, satellite, network element, etc., as described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples set forth below in the Examples section.

[0101] The term "application" can refer to a complete and deployable package or environment used to implement specific functions in an operating environment. The term "AI / ML application," etc., can refer to an application that includes some artificial intelligence (AI) / machine learning (ML) models and an application-level description. In some embodiments, an AI / ML application can be used to configure or implement one or more of the disclosed aspects.

[0102] The term "machine learning" or "ML" refers to a computer system that uses algorithms and / or statistical models to perform specific tasks without explicit instructions, instead relying on patterns and reasoning. ML algorithms build or estimate mathematical models (called "ML models," etc.) based on sample data (called "training data," "model training information," etc.) to make predictions or decisions without explicit programming to perform these tasks. Typically, an ML algorithm is a computer program that learns from experience with some tasks and some performance metrics, while an ML model can be any object or data structure created after training an ML algorithm with one or more training datasets. After training, an ML model can be used to make predictions on new datasets. Although the term "ML algorithm" refers to a different concept than the term "ML model," these terms discussed herein may be used interchangeably for the purposes of this disclosure.

[0103] The terms "machine learning model," "ML model," etc., can also refer to ML methods and concepts used by ML-assisted solutions. An "ML-assisted solution" is a solution that uses ML algorithms to solve a specific use case during operation. ML models include supervised learning (e.g., linear regression, k-nearest neighbors (KNN), decision tree algorithms, support machine vectors, Bayesian algorithms, ensemble algorithms, etc.), unsupervised learning (e.g., K-means clustering, principal component analysis (PCA), etc.), reinforcement learning (e.g., Q-learning, multi-armed learning, deep RL, etc.), neural networks, etc. Depending on the implementation, a particular ML model may have many sub-models as components, and the ML model may train all sub-models together. Individually trained ML models can also be chained together in an ML pipeline during inference. An "ML pipeline" is a set of functional, feature, or functional entities specific to an ML-assisted solution; an ML pipeline may include one or more data sources such as a data pipeline, a model training pipeline, a model evaluation pipeline, and actors. An "actor" is an entity that hosts the output of the ML model for inference using the ML model. The term "ML training host" refers to an entity that hosts the training of the model (e.g., a network function). The term "ML inference host" refers to the entity (e.g., a network function) that hosts the model during inference mode (which includes both model execution and any online learning, if applicable). The ML host informs participants of the output of the ML algorithm, and participants make decisions about actions ("actions" are performed by participants as a result of the output of the ML-assisted solution). The term "model inference information" refers to the information used as input to the ML model to determine inference; the data used to train the ML model and the data used to determine inference may overlap; however, "training data" and "inference data" refer to different concepts.

[0104] NR's achievable latency and reliability performance are key to supporting use cases with stringent requirements. To expand NR's applicability across various verticals, Rel-16 NR has evolved to support use cases that include: those enabling version 15 improvements (e.g., AR / VR and entertainment industry applications) and new version 16 use cases with higher requirements (e.g., factory automation, transportation, and power distribution).

[0105] However, in some of the scenarios listed above, the limiting factor is spectrum availability. To mitigate this, one of the goals of Rel.17 is to identify potential enhancements to ensure that the features of version 16 are compatible with unlicensed ultra-reliable low-latency communication (URLLC) and industrial Internet of Things (IIoT) operations in controlled environments.

[0106] In some embodiments, aspects of the design that can be enhanced when operating in unlicensed spectrum can be identified. One challenge is ensuring that the system complies with regulatory requirements for the sub-6 GHz band, where a Listen-Before-Speak (LBT) process needs to be performed in some parts of the world to acquire the medium before transmission can occur (e.g., as described in ETSI EN 301 893), while still guaranteeing the reliability and latency requirements identified for the URLLC / IIoT design to meet the aforementioned use cases. Additional design considerations can be made in this regard. In some aspects, when operating URLLC / IIoT in unlicensed spectrum, due to the LBT process and its contingent nature, additional latency and reliability losses may be introduced when LBT fails, depending on medium contention.

[0107] In some aspects, both load-based device (LBE) and frame-based device (FBE) designs can be employed to accommodate different scenarios and LBT process usage. However, for the FBE framework, to illustrate an NR-U design, only the gNB can act as the initiating device, and a given fixed frame period (FFP) can be one of {1ms, 2ms, 2.5ms, 4ms, 5ms, 10ms}, with the start position of the fixed frame period aligned with each even-numbered frame. However, this operating mode can lead to long delays when an LBT failure occurs at the gNB at the start of the FFP, because in this case, all DL and UL transmissions scheduled within that FFP may be delayed until a subsequent FFP where the gNB can successfully perform its LBT process.

[0108] Considering the stringent latency requirements in URLLC / IIoT designs, the operating mode can be modified to remove the single point of failure at the gNB, thus providing devices with more opportunities to transmit and allowing them to operate as initiators and acquire their own Channel Occupancy Time (COT).

[0109] In some aspects, if the UE also operates as the initiating device, a UL to DL COT sharing procedure can be established, and while the UL to DL procedure for LBE can be used as a baseline, the disclosed techniques provide some enhancements to adapt to frame-based frameworks.

[0110] In some embodiments, given that a gNB has complete control over the scheduled resources, and considering that the gNB provides the UE with explicit information about the COT sharing procedure in addition to indicating the channel access type to be used, the UL to DL COT sharing procedure defined in Rel. 16 provides a certain level of transparency to the UE itself for dynamically approved UEs. While a similar concept can be used in Rel. 17 when dynamically approved (DG) UEs share COT in a semi-static channel access mode (aka FBE framework), it is important to enhance the COT sharing procedure for configured approved UEs, as this is not well optimized for ultra-reliable low-latency applications and is not intended for semi-static channel access operation modes. In this context, the disclosed techniques provide details about the UL to DL COT sharing procedure and its associated signaling for configured approved (CG) UEs. The disclosed techniques also identify enhancements to the information that can be carried in the CG uplink control information (CG-UCI).

[0111] COT sharing procedure for semi-static channel access for CG UE

[0112] In Rel.16NR-U, a UE can only operate as an initiating device when it is operating within an LBE framework. Only in this case is a CG UE allowed to share its COT with its associated gNB. However, the COT sharing mechanism differs depending on whether the higher-layer parameter ul-toDL-COT-SharingED-Threshold-r16 is provided to the UE, and two different operating modes (e.g., Mode A and Mode B) can be defined (e.g., as...). Figure 5 and Figure 6 (As shown).

[0113] (A) Pattern A.

[0114] Figure 5 Figure 500 illustrates the first operating mode (Mode A) for COT sharing for UE based on some aspects.

[0115] If the higher-layer parameter ul-toDL-COT-SharingED-Threshold-r16 is provided, the UE is allowed to share its COT with the gNB. In this case, DL transmissions may include transmissions to the UE that initiated the channel occupancy, and may also include non-unicast and / or unicast transmissions, wherein any unicast transmissions include user plane data sent only to the UE that initiated the channel occupancy. In this operating mode, the UE is configured by cg-COT-SharingList-r16, which provides a table configured by higher-layer signaling, wherein each row of the table jointly provides the following information: (a) the channel access priority class used by the UE when acquiring the COT; (b) the time slot in which the DL transmission may begin, identified as x+O, where x is the current time slot and O is the offset indicated by the time slot; and (c) the maximum duration of the DL transmission, indicated by D and provided by the time slot. Figure 5 The description of this operating mode is provided in the document.

[0116] In some respects (for example, as listed in Table 1 below), the cg-COT-SharingList-r16 cell also includes entries indicating that COT sharing will not be permitted.

[0117]

[0118] Table 1

[0119] (B) Pattern B.

[0120] Figure 6 Figure 600 illustrates a second operating mode (Mode B) for COT sharing for UE based on some aspects.

[0121] If the higher-layer parameter ul-toDL-COT-SharingED-Threshold-r16 is not provided, then if the "COT sharing information" (i.e., COT sharing indication) in the CG-UCI indicates "1", then the UE is only allowed to share its COT for DL ​​control transmissions with lengths of 2 / 4 / 8 OFDM symbols for 15 / 30 or 60kHz subcarrier spacing, respectively. In this case, the gNB can share the UE channel occupancy and begin DL transmission of X symbols from the end of the slot where the CG-UCI is detected, where cg-COT-SharingOffset-r16 is provided by higher-layer signaling. Figure 6 The description of this operating mode is provided in the document.

[0122] In some embodiments, when designing a UL to DL procedure for a semi-static channel access mode, although the UL to DL COT sharing procedure defined for LBT can be used as a baseline, the following configuration can be used:

[0123] (a) The higher-level parameter ul-toDL-COT-SharingED-Threshold-r16 can be introduced to address the issue of coexistence with other incumbent technologies, thereby reducing potential interference and congestion. However, it is important to note that URLLC / IIoT only operates in unlicensed frequency bands within a controlled environment (where there is a long-term guarantee against incumbent technologies).

[0124] (b) Regardless of whether Mode A or Mode B is used, the UE indicates an offset value to the gNB, indicating where the gNB can begin transmission. However, this offset indication points to the first symbol of the first time slot in which the gNB is allowed to begin transmission. This has a disadvantage: if the UE does not terminate its UL burst precisely at the time slot level, a gap greater than 16µs will remain between the UL and DL, meaning the gNB will need to perform Cat-2 Listen-Before-Speak (LBT) before transmitting within the UE's COT.

[0125] (c) If mode A is used, this carries information related to the CAPC used by the UE. However, it is important to note that for semi-static channel access mode, the UE can only perform a single LBT when acquiring its FFP, and therefore the concept of CAPC does not have any further meaning.

[0126] (d) If mode A is used, the maximum length of the allowed DL transmission depends on the maximum COT defined by the CAPC used by the UE to obtain that COT. However, as mentioned above, when operating in semi-static channel access mode, the concept of CAPC loses its meaning, and the maximum COT is strictly related to the maximum length of the supported FFP.

[0127] In one embodiment, when the UE is provided with the parameter ChannelAccessMode-r16='semistatic' by System Information Block 1 (SIB1) or with a dedicated configuration by higher-layer RRC signaling, and regardless of whether cg-RetransmissionTimer is configured, one or all of the following can be supported:

[0128] (a) gNB is never allowed to configure the higher-layer parameter ul-toDL-COT-SharingED-Threshold-r16, and the UE does not expect this RRC parameter.

[0129] (b) Regardless of whether it will share its COT, when the UE operates as an initiating device and acquires a new FFP while performing a CCA procedure, it will use the Energy Detection (ED) threshold to determine whether the channel is idle or busy. The ED threshold is calculated based solely on its own transmit power and is detailed in TS 37.213 Sec.4.2.3.

[0130] (c) When performing a CCA procedure, a UE that shares its COT with a gNB will use an Energy Detection (ED) threshold calculated based on one or more of the following conditions to determine whether the channel is idle or busy:

[0131] (c.1) If one or more of the following conditions are met, then based on its own transmission power, and as detailed in TS37.213 Sec.4.2.3:

[0132] (c.1.1) When within a shared COT, the gNB sends unicast user plane data or control to the initiating UE;

[0133] (c.1.2) When within a shared COT, the UL to DL is always greater than 16us, and regardless of what the gNB will be transmitted and who transmits it to, as long as the transmission is dedicated to a UE other than the UE that initiated the FFP, and the UE operates as a DGUE within a u-FFP that the gNB is sharing and / or within a g-FFP that may overlap with the u-FFP that the gNB is sharing;

[0134] (c.1.3) The UE is provided with the UE's FFP parameters;

[0135] (c.1.4) When within a shared COT, the UL to DL is always greater than 16us, regardless of what the gNB will be sent to and who sends it to it;

[0136] (c.2) The gNB is configured with the higher-layer parameter ul-toDL-COT-SharingED-Threshold-r16, and if the above conditions for the UE to calculate the ED threshold based on its transmit power are not met, the UE will calculate the ED threshold based on the gNB's transmit power.

[0137] In one embodiment, when the UE is provided with ChannelAccessMode-r16='semistatic' by SIB1 or with a dedicated configuration by higher-layer RRC signaling, and regardless of whether cg-RetransmissionTimer is configured, the UE is allowed to share its FFP with its associated gNB, and multiple switching points are allowed. In this case, both control and data transmissions can be performed by the gNB, as long as this includes per-switching-point transmissions dedicated to the UE that initiated the FFP. Alternatively, both control and data transmissions can be performed by the gNB, regardless of whether any transmission is intended for the UE that initiated the FFP. Another alternative is that both control and data transmissions can be performed by the gNB, but they must be intended for the UE that initiated the FFP.

[0138] In some embodiments, the gNB is allowed to share the UE's FFP and perform transmissions as long as one or more of the following configurations are met:

[0139] (a) The gNB’s transmissions (either data, control, or both) are dedicated solely to the UE that initiated the FFP that the gNB is sharing;

[0140] (b) The gNB can address other UEs besides the UE that initiated the FFP, provided that one or more of the following conditions are met:

[0141] (b.1) At each switching point there is at least one transmission dedicated to the UE that initiated the FFP;

[0142] (b.2) Only transmissions containing UE-specific control information and / or UE-specific control and data information are allowed to be addressed to UEs other than the UE that initiated the FPP. In one option, the gNB may perform unicast transmissions only to UEs (Rel.17 UEs) that provided the UE's FFP parameters, and these UEs will operate only as DG UEs within either a UE-initiated FFP shared by the gNB or a g-FFP shared by the gNB that overlaps with the initiating UE's FFP. In this particular case, in one option, if the DL transmission is intended for other UEs compared to the UE that initiated the FFP, the bit fields included in the scheduled DCI containing information related to channel access information (i.e., CP extension, channel access type, and COT initiator) must always be present in the unicast DL burst, and the content of the channel access information must explicitly indicate that the gNB is operating as a responding device (using index 3 in Table 2). If the UE intended for this transmission:

[0143] (b.2.1) If the COT or FFP to which the DL transmission has fallen has not yet been obtained, this information will indicate that the gNB is indeed operating as a responding device, but under an FFP initiated by another UE (which is not sharing the u-FFP of the UE to which the DL transmission is intended);

[0144] (b.2.2) If the COT or FFP of the DL transmission has been obtained, the information will instruct the gNB to operate as a responding device, and potentially, the gNB will share the UE's FFP (note that this will be transparent from the UE's perspective since the UE is operating as a DG UE).

[0145]

[0146]

[0147] Table 2 - Channel Access Type, Cyclic Prefix (CP) Extension and COT Initiator Information (if ChannelAccessMode-r16="semistatic" is provided and if the UE's FFP parameters are configured).

[0148] (c) The gNB’s transmission can be dedicated to the UE that initiates the FFP, but it can also be dedicated to any other UE besides the UE that initiates the FFP, provided that these UEs have been provided with the UE’s FFP parameters (Rel.17UE), and for UEs other than the UE that initiates the FFP, they will operate only as DG UEs within the FFP shared by the gNB and initiated by the UE or within the g-FFP shared by the gNB and overlapping with the FFP of the initiating UE (e.g., they will be able to evaluate the COT initiator through the information provided in the Channel Access Field included in the downlink control information).

[0149] In this specific case, in one option, if the DL transmission intent is directed at other UEs compared to the UE initiating the FFP, then the bit fields included in the scheduling DCI containing information related to channel access information (i.e., CP extension, channel access type, and COT initiator) must always be present within that unicast DL burst, and the content of the channel access information must explicitly indicate that the gNB is operating as a responding device (using index 3 in Table 2). If the transmission intent is directed at the UE:

[0150] (c.1) If the COT or FFP to which the DL transmission has fallen has not yet been obtained, this information will indicate that the gNB is indeed operating as a responding device, but under an FFP initiated by another UE (which is not sharing the u-FFP of the UE to which the DL transmission is intended);

[0151] (c.2) If the COT or FFP of the DL transmission has been acquired, this information will instruct the gNB to operate as a responding device, and potentially, the gNB will share the UE's FFP (note that this will be transparent from the UE's perspective since the UE is operating as a DG UE).

[0152] In some embodiments, when the UE is provided with ChannelAccessMode-r16='semistatic' by SIB1 or with a dedicated configuration by higher-layer RRC signaling, and regardless of whether cg-RetransmissionTimer is configured, if a gap of less than 16µs is formed at a given switching point (e.g., UL to DL and / or DL ​​to UL), the device transmitting shortly after the switching point can follow one of the following two options:

[0153] (a) It does not sense the channel before transmission and it follows the Type 2C channel access procedure detailed in TS 37.213; and

[0154] (b) It does not sense the channel before transmission, and the transmission length does not need to be constrained to 584µs.

[0155] In some aspects, when the UE is provided with ChannelAccessMode-r16='semistatic' by SIB1 or with a dedicated configuration by higher-layer RRC signaling, if a gap greater than 16us is formed at a given switching point (e.g., UL to DL and / or DL ​​to UL), a device that transmits shortly after the switching point may only need a slot duration of at least 9us to sense that the channel is idle in order to assess that the channel is idle and may then perform the transmission.

[0156] In one embodiment, when the UE is provided with ChannelAccessMode-r16='semistatic' by SIB1 or with a dedicated configuration by higher-layer RRC signaling, and regardless of whether cg-RetransmissionTimer is configured, the UE is allowed to share its FFP with its associated gNB, and the gNB is allowed to schedule UL transmissions for other UEs besides the UE that initiated the FFP. In one option, when the gNB operates as a responsive device, newly scheduled UL transmissions scheduled by the gNB can occur at any time and even in time-domain resources that overlap with the FFP of the current UE to which the gNB shares its FFP.

[0157] exist Figure 7 The description of this option is provided in the documentation. Figure 7This illustrates a scenario where the gNB can schedule UL transmissions for different UEs (or multiple UEs) even within the FFP of another acquired UE. To enable or disable this behavior, the gNB can provide the UE with individual RRC parameters in an SIB1 or UE-specific RRC message.

[0158] Figure 7 Figure 700 illustrates UL to DLCOT sharing when the base station is allowed to schedule inter-UE FFP UL transmissions, according to some aspects.

[0159] In another option, scheduled UL transmissions for other UEs are not allowed within the FFPs of different UEs, and UL transmissions for other UEs (multiple UEs) can only be scheduled in time-domain resources that do not overlap with the FFP of the currently acquired UE. Figure 8 The description of this option is provided in the documentation. Figure 8 This illustrates a scenario where the gNB is allowed to schedule UL transmissions for another UE (or multiple UEs) only outside of the FFP of the acquired UE.

[0160] Figure 8 Figure 800 illustrates UL to DLCOT sharing when the base station is allowed to schedule only other UEs' FFP-based UL transmissions, according to some aspects.

[0161] In one embodiment, when the UE is provided with ChannelAccessMode-r16='semistatic' by SIB1 or a dedicated configuration by higher-layer RRC signaling, and cg-RetransmissionTimer is configured, the concept / definition of offset already introduced in Rel.16 is modified so that the offset always points from the first symbol after the end of the UL burst to the first symbol that the gNB can use for DL ​​transmission, regardless of whether the symbol is at a slot boundary. In this case, the offset can be defined in terms of symbol / slot granularity or the PUSCH length corresponding to the latest value indicated by the start and length indicator value (SLIV) for a particular UL burst or UL transmission carrying that information. In different options, the offset is defined as the elapsed time from the first symbol of the first slot after the end of the UL burst to the first symbol of the slot that the gNB can use for DL ​​transmission. If a separate RRC parameter in the form of a binary flag exists in SIB1 or the dedicated configuration, the modified behavior can be activated, thus implementing the modified behavior.

[0162] In one embodiment, when the UE is provided with ChannelAccessMode-r16='semistatic' by SIB1 or with a dedicated configuration by higher-layer RRC signaling, and a cg-RetransmissionTimer is configured, the CG-UCI carries COT sharing information. This COT sharing information can be used by the UE to notify the gNB of unused resources it can use within the u-FFP. In this case, the UE carries... The bit is part of the COT shared information field in cg-UCI, where C is the number of combinations configured by the RRC parameter cg-COT-SharingList-r16, which provides a table in which each row of the table indicates the following information:

[0163] (a) The channel access priority class used by the UE when acquiring COT;

[0164] (b) The time slot in which DL transmission can begin is identified as x+O, where x is the current time slot and O is the offset indicated by the time slot; and

[0165] (c) The maximum duration of the DL transmission, which is indicated by D and provided again in time slots.

[0166] In this case, given that the UE is operating in a semi-static channel access mode (where the concept of Channel Access Priority Class (CAPC) no longer applies), one or more of the following options can be used:

[0167] (a) It is expected that the UE will not provide any relevant CAPC information to the gNB;

[0168] (b) It is expected that the gNB will ignore the CAPC information provided by the UE;

[0169] (c) It is always expected that the UE will select an entry from the table corresponding to a specific CAPC information (e.g., CAPC = 1); and

[0170] (d) When gNB is configured with cg-COT-SharingList-r16, this is expected to generate a table in which all rows indicate a specific CAPC value (e.g., CAPC=1).

[0171] In some embodiments, a new optional higher-layer parameter is introduced specifically for use when a semi-static channel access mode is employed and a cg-RetransmissionTimer is configured. This parameter provides a table configured by higher layers, where each row provides joint information about the offset and duration of a specific DL transmission allowed within the acquired UE's FFP, shared with the gNB. When the CG-UCI is carried in the PUSCH, the UE is allowed to select and indicate a specific row in the table to indicate to the gNB whether a UE-initiated COT sharing is permitted and the specific resources available to the gNB. Therefore, the CG-UCI can carry information from... The COT shared information consists of bits, where C is the number of configured combinations. When no table is provided, the application version 16 behavior applies.

[0172] In one example, the high-level parameters can take the form listed in Table 3 below.

[0173]

[0174] Table 3

[0175] In one example, Y (maximum allowed duration) and Z (maximum allowed offset) are equal, and given that the duration and offset are provided per time slot, assuming the UE's maximum FFP is 10 milliseconds and it supports 15 / 30 and 60kHz subcarrier spacing, then Y = Z = 39. In this case, W (maximum size of list cg-COT-SharingList-r17) is equal to 781. This results in the maximum value of C carried by CG-UCI being 10 bits.

[0176] In some embodiments, Y and Z are equal, and given the duration and offset provided per symbol, assuming the UE's maximum FFP is equal to 10ms and it supports 15 / 30 and 60kHz subcarrier spacing, then Y = Z = 546. In this case, W equals 156521. This results in the maximum value of C carried by CG-UCI being 18 bits.

[0177] In some respects, Y and Z are equal, and the duration and offset are provided by the minimum possible PUSCH length, which can be equal to 2 symbols, or the PUSCH length indicated by SLIV. Assuming the maximum FFP of the UE is equal to 10ms and supports 15 / 30 and 60kHz subcarrier spacing, then Y = Z = 273. In this case, W equals 78121. This will result in the maximum value of C carried by CG-UCI = 17 bits.

[0178] In some embodiments, Y and Z are equal, and given the duration and offset provided in half-slots, assuming the UE's maximum FFP is equal to 10ms and supports 15 / 30 and 60kHz subcarrier spacing, then Y = Z = 78. In this case, W equals 3161. This results in the maximum value of C carried by CG-UCI being 12 bits.

[0179] In some respects, Y and Z are different. Given the above options, Y = 39 or 78 or 273 or 546, and Z = 39 or 78 or 273 or 546.

[0180] In one embodiment, when the UE is provided with ChannelAccessMode-r16='semistatic' by SIB1 or with a dedicated configuration by higher-layer RRC signaling, and a cg-RetransmissionTimer is configured, UL or DL ​​transmissions occurring within the UE's FFP cannot extend beyond the length of the FFP, and cannot overlap or extend into the idle period of a subsequent UE's FFP. Even if the UE can indicate in the COT sharing information carried in CG-UCI that DL can extend beyond the current UE's FFP, the gNB is not allowed to transmit within the idle period of a subsequent UE's FFP, and those resources should be considered invalid. In other words, when a UE initiates an FFP and shares it with the gNB, neither the gNB nor the UE should transmit any transmissions for at least T in a consecutive set of symbols before the start of the next UE's FFP. z =max(0.05T) x The duration of ,100us), where T_x is the length of the UE's FFP.

[0181] In some aspects, for the gNB to schedule inter-FFP UL transfers for other UEs within a shared UE's FFP, the gNB is required to have additional information, specifically knowing all time-domain resources that the UE intends to share with the gNB or that they will remain unused. Based on legacy design, the UE can indicate the shared resources to the gNB, but this can only be provided individually per switching point. In some aspects, the gNB cannot be informed in advance of the number of allowed switching points and the resources it can potentially use for each of them. This means that the gNB will not be allowed to schedule any UL transfers for any other UE within the FFP of a particular UE in another switching point because it does not know whether other resources will be allowed in individual instances of the UE's FFP. For this reason, some additional configuration can be performed.

[0182] In one embodiment, for the case where a semi-static channel access mode is used and a cg-RetransmissionTimer is configured, a new optional higher-layer parameter is introduced (e.g., as listed in Table 4 below). This parameter provides a table configured by higher-layer signaling, where each row of the table provides joint information shared with the gNB regarding the offset and duration of a specific DL transmission allowed within the UE's FFP, as well as the number of switching points. When the CG-UCI is carried in the PUSCH, the UE is allowed to select and indicate a specific row of the table to indicate to the gNB whether the UE-initiated COT sharing is permitted and the specific resources that the gNB can use. Therefore, the CG-UCI can carry information from the higher-layer signaling. The COT shared information consists of bits, where C is the number of configured combinations. In one option, while the number of swap points is a scalar, the duration and offset are vectors, where each element indicating the duration and offset is related to each swap point. If no optional table is provided, Rel.16 behavior applies.

[0183]

[0184] Table 4

[0185] In some respects, Y = Z, and given the duration and offset provided by the time slot, the maximum value of the UE's FFP is equal to 10ms, and it supports 15 / 30 and 60kHz subcarrier spacing, then Y = Z = 39.

[0186] In some embodiments, Y = Z, and given the duration and offset provided by symbol, the maximum value of the UE's FFP is equal to 10ms, and 15 / 30 and 60kHz subcarrier spacing is supported, then Y = Z = 546.

[0187] In some respects, Y = Z, and the duration and offset are provided by the minimum possible PUSCH length, which can be equal to 2 symbols or the PUSCH length indicated by SLIV. The maximum value of the UE's FFP is equal to 10ms, and it supports 15 / 30 and 60kHz subcarrier spacing, then Y = Z = 273.

[0188] In some embodiments, Y = Z, and given the duration and offset provided in half-slots, the maximum value of the UE's FFP is equal to 10ms, and 15 / 30 and 60kHz subcarrier spacing is supported, then Y = Z = 78.

[0189] In some respects, Y and Z are different. Given the above options, Y = 39 or 78 or 273 or 546, and Z = 39 or 78 or 273 or 546.

[0190] In some embodiments, optional higher-layer parameters are introduced specifically for use when a semi-static channel access mode is used and a cg-RetransmissionTimer is configured. These parameters provide a table configured by higher layers, where each row provides joint information shared with the gNB regarding the offset and duration of a specific DL transmission allowed within the acquired UE's FFP. When the CG-UCI is carried in the PUSCH, the UE is allowed to select and indicate a specific row in the table to indicate to the gNB whether a COT sharing initiated by the UE is permitted and the specific resources that the gNB can use. Therefore, the CG-UCI can carry information from... The COT shared information consists of bits, where C is the number of configured combinations. Furthermore, the number of allowed switching points within the UE's FFP is either configured separately by RRC or dynamically signaled directly within the CG-UCI, which will include a dedicated field. If no optional table is provided, Rel.16 behavior applies.

[0191] In one option, the offset and duration values ​​are scalar values, and this will only apply to the first swap point, with the offset and duration values ​​for each subsequent swap point provided before each of them.

[0192] In some respects, the values ​​of offset and duration are scalar values, and these values ​​will be the same and apply to all switching points, meaning that each part of the FFP of an unused UE will have the same length, and the first timeslot of each part that can be shared will be equally spaced by the same amount of resources provided by the offset.

[0193] In some embodiments, the values ​​of offset and duration are vectors, where each element indicating duration and offset is associated with each swap point.

[0194] In some aspects, the values ​​of offset and duration are scalars, and the indication of the number of exchange points M is provided via RRC. In this case, the UE will carry... Bits are used for COT sharing, where each The bit will jointly indicate the offset and duration of a specific portion of the UE's FFP that can be shared with the gNB and utilized by other UEs scheduled by that gNB.

[0195] In one embodiment, when cg-RetransmissionTimer is not configured and cg-UCI is not piggybacked during PUSCH transmission, one of the following procedures can be used:

[0196] (a) In some embodiments, the gNB decides to schedule CG resources, and for any resources not scheduled for CG transmission within the UE's FFP, the gNB decides to transmit in those resources as a response device utilizing the UE's COT.

[0197] (b) In some respects, the decision regarding whether to share the UE's COT and the initiation of time-domain resources available for use by the gNB within the UE's FFP is left to the UE, as the gNB operates as a responsive device. With this indication, the UE may provide the gNB only with information regarding the first timeslot / symbol / or CG PUSCH transmission available for DL ​​transmission, but the gNB decides whether to use any of these resources and any subsequent time-domain resources until subsequent CG allocation resources within the specific UE's FFP, and as long as these time-domain resources are within the UE's FFP. Figure 9 The document provides a high-level explanation of this concept.

[0198] Figure 9 Figure 900 illustrates the UL to DL COT sharing process according to some aspects.

[0199] The gNB can provide an indication of which time-domain resources within the UE's FFP it can use, through a combination of a sharing indication (which informs the gNB of the UE's intention to share its COT) and an offset 'X' (which indicates how many symbols / slots / or CG PUSCH transmissions have been transmitted since the UE indicated its intention to share its COT before the gNB can begin performing DL transmissions). The offset 'X' can be a fixed value indicated within the specification (which can depend on the subcarrier spacing), or it can be configured by RRC or equivalent to the minimum gNB processing time required to decode CG PUSCH transmissions.

[0200] In some respects, sharing instructions can be performed implicitly or explicitly using one or more of the following options:

[0201] (a) An indication of the UE's intention to share its COT can be implicitly indicated by the Cyclic Redundancy Check (CRC) of the TB or CB / CBG, which is scrambled with a codeword representing the sharing indication. In this case, when the gNB detects the CRC scrambled with the codeword representing the sharing indication, the gNB will know that the UE intends to share its COT, and the gNB can use subsequent time-domain resources after an 'X' time interval from the end of the PUSCH carrying the current TB or CB / CBG for DL ​​transmission.

[0202] As an example, the codewords for sharing instructions can be generated as follows:

[0203] (a.1) Shared indicator = '0', indicating no intention to share COT. In this case, the codeword can be all zeros; and

[0204] (a.2) Sharing indication = '1', which indicates the intention of COT sharing. In this case, the codeword can be all 1s.

[0205] (b) The indication of the UE's intention to share its COT can be accomplished using a dedicated payload in the encoded CB. The encoded CB payload contains a predefined bit sequence signature that the gNB will interpret as a sharing indication. In this case, when the gNB decodes a CB containing the predefined bit sequence signature representing the sharing indication, the gNB will know that the UE intends to share its COT, and the gNB can use the subsequent time-domain resources after a time amount of 'X' from the end of the PUSCH carrying the current CB for DL transmission. Note that the position of the dedicated payload can be predefined in the specification (e.g., at the beginning of the CB or CBG, or included in the MAC-CE). In the case where the sharing indication is carried by the MAC CE, a logical channel ID (LCID) can be used to distinguish this information from a regular MAC-CE. In one embodiment, one of the reserved LCID values is used to distinguish the UCI carrying the sharing indication from a regular MAC-CE.

[0206] (c) The indication of the UE's intention to share its COT can be implicitly indicated by not transmitting the DMRS symbols for a specific CG PUSCH transmission. Assuming that N single-symbol or double-symbol DMRSs are associated with the PUSCH transmission, when the nth single-symbol or double-symbol DMRS is not transmitted, the PUSCH after the nth single-symbol or double-symbol DMRS is interpreted as a PUSCH carrying the sharing indication, where 0 < n ≤ N - 1. In this case, when the gNB does not detect the DMRS, the gNB will know that the UE intends to share its COT, and the gNB can use the subsequent time-domain resources after a time amount of 'X' from the end of the current PUSCH for DL transmission.

[0207] (d) The indication of the UE's intention to share its COT can be indicated by a specific DMRS associated with the PUSCH transmission. For example, two sets of DMRS resources are formed: the first set can be associated with the PUSCH transmission, while the second set can be used for the sharing indication. When the gNB detects the DMRS in the second set of DMRS resources, the gNB will know that the UE intends to share its COT, and the gNB can use the subsequent time-domain resources after a time amount of 'X' from the end of the current PUSCH for DL transmission. In some aspects, the first and second DMRS resources can be configured by dedicated RRC signaling or DCI or a combination thereof. The frequency shift or time-domain cyclic shift of Y can be configured by RRC signaling, and the frequency shift or time-domain cyclic shift of Y can be applied by the UE to the DMRS carrying the indication that the UE shares its COT.

[0208] In some respects, the embodiments listed above are not mutually exclusive, and one, a portion or more thereof may be applied together.

[0209] Enhancements to CG-UCI content

[0210] In some embodiments, regardless of whether cg-RetransmissionTimer is configured, if CG-UCI is carried and DFI-DCI is used (i.e., the retransmission procedure employed is the Reel.16 NR-U retransmission procedure, where the UE can perform retransmission autonomously, and it can occur not only through scheduled transmissions but also within configured approved resources of the same or different CG configurations), then the CG-UCI content may differ from the CG-UCI content used in NR-U, and in addition to the fields carried in Reel.16 (i.e., HARQ process number, RV, and NDI), it may also carry one or more of the following information:

[0211] (a) Can carry information for COT sharing Bits, which are used as described in the previous embodiments of this disclosure;

[0212] (b) A one-bit field indicating whether the UE is transmitting within the UE's FFP or the gNB's FFP, which can be used by the gNB to resolve ambiguity if the UE is permitted to transmit within a valid gNB's FFP, wherein a valid FFP is an FFP in which the initiating device has been able to successfully obtain its CCA procedure.

[0213] (c) Indicate to the gNB the new field of the FFP parameters that the UE is following, in case the UE may be configured with multiple FFP configurations (i.e., offset and FFP length), and the UE can decide which FFP configuration to use.

[0214] (d) A new field indicating the priority of PUSCH transmissions carrying the cg-UCI: When PUSCH transmissions of different priorities have overlapping time-domain resources, this field can be used by the gNB to resolve ambiguities between the UE and the gNB, and can be left to the UE's implementation and selection to determine which PUSCH should be sent.

[0215] In one embodiment, when cg-RetransmissionTimer is not configured, CG-UCI is carried, and DFI-DCI is not used (i.e., the retransmission procedure employed is the Rel.16URLLC retransmission procedure, where retransmissions can be scheduled only by UL approval), the CG-UCI content may differ from the CG-UCI content used in NR-U, and may carry one or more of the following information:

[0216] (a) Can carry information for COT sharing Bits, which are used as described in the previous embodiments of this disclosure;

[0217] (b) A one-bit field indicating whether the UE is transmitting within the UE's FFP or the gNB's FFP, which can be used by the gNB to resolve ambiguity if the UE is permitted to transmit within a valid gNB's FFP, wherein a valid FFP is an FFP in which the initiating device has been able to successfully obtain its CCA procedure.

[0218] (c) Indicate to the gNB the new field of the FFP parameters that the UE is following, in case the UE may be configured with multiple FFP configurations (i.e., offset and FFP length), and the UE can decide which FFP configuration to use.

[0219] (d) A new field indicating the priority of PUSCH transmissions carrying the cg-UCI: When PUSCH transmissions of different priorities have overlapping time-domain resources, this field can be used by the gNB to resolve ambiguities between the UE and the gNB, and can be left to the UE's implementation and selection to determine which PUSCH should be sent.

[0220] (e)HARQ process ID.

[0221] (f) Redundant version (RV).

[0222] In some respects, the embodiments listed above are not mutually exclusive, and one or more of them can be applied together.

[0223] Figure 10 A block diagram is shown of a communication device (e.g., an evolved Node B (eNB), a next-generation Node B (gNB) (or another RAN node), an access point (AP), a radio station (STA), a mobile station (MS), or a user equipment (UE)) that is implemented according to some aspects and used to perform one or more technologies disclosed herein. In an alternative aspect, the communication device 1000 may operate as a standalone device or may be connected (e.g., networked) to other communication devices.

[0224] A circuit (e.g., a processing circuit) is a collection of circuits implemented in a tangible entity of a device 1000 that includes hardware (e.g., simple circuits, gates, logic, etc.). Circuit membership can be flexible over time. A circuit includes members that, when operated, can perform a specified operation individually or in combination. In the example, the hardware of the circuit may be designed immutably to perform a specific operation (e.g., hardwiring). In the example, the hardware of the circuit may include variably connected physical components (e.g., execution units, transistors, simple circuits, etc.) that include machine-readable media that are physically modified (e.g., immutable magnetic, electrical, or movable placement of a large number of particles, etc.) to encode instructions for a specific operation.

[0225] When physical components are connected, the underlying electrical properties of the hardware structure change (e.g., from an insulator to a conductor, and vice versa). Instructions enable embedded hardware (e.g., an execution unit or loading mechanism) to create members of a circuit within the hardware via variable connections to perform a portion of a specific operation when in operation. Thus, in the example, a machine-readable medium element is part of the circuit, or another component communicatively coupled to the circuit when the device is in operation. In the example, any physical component can be used in more than one member of more than one circuit. For example, under operation, an execution unit may be used in a first circuit of a first circuit system at one point in time, and reused at different times by a second circuit in the first circuit system or by a third circuit in the second circuit system. Additional examples of these components of device 1000 are as follows.

[0226] In some respects, device 1000 may operate as a standalone device or may be connected (e.g., networked) to other devices. In a networked deployment, communication device 1000 may operate as a server communication device, a client communication device, or both in a server-client network environment. In the example, communication device 1000 may act as a peer-to-peer communication device in a point-to-point (P2P) (or other distributed) network environment. Communication device 1000 may be a UE, eNB, PC, tablet PC, STB, PDA, mobile phone, smartphone, network appliance, network router, switch, or bridge, or any communication device capable of executing instructions specifying the actions to be taken by the communication device (sequentially or otherwise). Furthermore, although only a single communication device is shown, the term "communication device" should also be understood to include any collection of communication devices (e.g., cloud computing, Software as a Service (SaaS), and other computer cluster configurations) that individually or jointly execute a set (or more) of instructions to perform any one or more methods discussed herein.

[0227] As described herein, examples may include logic or multiple components, modules, or mechanisms, or on which operations can be performed. A module is a tangible entity (e.g., hardware) capable of performing a specified operation and may be configured or arranged in some way. In the examples, circuitry may be arranged as a module in a specified manner (e.g., internally or relative to an external entity (e.g., other circuitry)). In the examples, all or part of one or more computer systems (e.g., a standalone computer system, a client computer system, or a server computer system) or one or more hardware processors may be configured by firmware or software (e.g., instructions, application portions, or applications) to operate to perform the specified operation. In the examples, software may reside on a communication device-readable medium. In the examples, the software causes the hardware to perform the specified operation when executed by the underlying hardware of the module.

[0228] Therefore, the term "module" is understood to encompass tangible entities, whether physically constructed, concretely configured (e.g., hardwired), or temporarily (e.g., transiently) configured (e.g., programmed) to operate in a specified manner or perform any of the operations described herein, in whole or in part. Consider the example of temporarily configured modules, where each module does not need to be instantiated at any given time. For example, in the case where modules include a general-purpose hardware processor configured using software, the general-purpose hardware processor can be configured as distinct modules at different times. The software can accordingly configure the hardware processor, for example, to constitute a particular module at one time instance and different modules at different time instances.

[0229] The communication device (e.g., UE) 1000 may include a hardware processor 1002 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 1004, a static memory 1006, and a storage device 1007 (e.g., a hard disk drive, a tape drive, flash memory, or other block or storage device), some or all of which may communicate with each other via an interconnect link (e.g., a bus) 1008.

[0230] The communication device 1000 may also include a display device 1010, an alphanumeric input device 1012 (e.g., a keyboard), and a user interface (UI) navigation device 1014 (e.g., a mouse). In the example, the display device 1010, input device 1012, and UI navigation device 1014 may be a touchscreen display. The communication device 1000 may additionally include a signal generation device 1018 (e.g., a speaker), a network interface device 1020, and one or more sensors 1021 (e.g., a Global Positioning System (GPS) sensor, a compass, an accelerometer, or another sensor). The communication device 1000 may include an output controller 1028 (e.g., a serial (e.g., Universal Serial Bus (USB)) connection, a parallel connection, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection) to communicate with or control one or more peripheral devices (e.g., a printer, a card reader, etc.).

[0231] Storage device 1007 may include a communication device-readable medium 1022 storing a set of or more sets of data structures or instructions 1024 (e.g., software) embodying or utilized by any one or more technologies or functions described herein. In some aspects, registers of processor 1002, main memory 1004, static memory 1006, and / or storage device 1007 may ( wholly or at least partially) be or include device-readable medium 1022 storing a set of or more sets of data structures or instructions 1024 embodying or utilized by any one or more technologies or functions described herein. In the example, one or any combination of hardware processor 1002, main memory 1004, static memory 1006, or mass storage 1016 may constitute device-readable medium 1022.

[0232] As used herein, the term "device-readable medium" is interchangeable with "computer-readable medium" or "machine-readable medium." While the communication device-readable medium 1022 is shown as a single medium, the term "communication device-readable medium" can 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 1024. The term "communication device-readable medium" includes the terms "machine-readable medium" or "computer-readable medium" and can include any medium capable of storing, encoding, or carrying instructions (e.g., instructions 1024) for execution by the communication device 1000 and causing the communication device 1000 to perform any one or more technologies of this disclosure, or any medium capable of storing, encoding, or carrying data structures used by or associated with those instructions. Non-limiting examples of communication device-readable media may include solid-state memory as well as optical and magnetic media. Specific examples of communication device readable media may include non-volatile memory (e.g., semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM)) and flash memory devices); magnetic disks (e.g., internal hard disks and removable disks); magneto-optical disks; random access memory (RAM); and CD-ROM and DVD-ROM disks. In some examples, the communication device readable medium may include non-transient communication device readable medium. In some examples, the communication device readable medium may include communication device readable medium that does not transmit signals transiently.

[0233] Instruction 1024 may further utilize any of a variety of transmission protocols to send or receive data over the communication network 1026 via the transmission medium through the network interface device 1020. In examples, the network interface device 1020 may include one or more physical jacks (e.g., Ethernet jack, coaxial jack, or telephone jack) or one or more antennas to connect to the communication network 1026. In examples, the network interface device 1020 may include multiple antennas to perform wireless communication using at least one of single-input multiple-output (SIMO), MIMO, or multiple-input single-output (MISO) technologies. In some examples, the network interface device 1020 may use multi-user MIMO technology for wireless communication.

[0234] The term "transmission medium" should be understood to include any intangible medium capable of storing, encoding, or carrying instructions for execution by the communication device 1000, and includes digital or analog communication signals or another intangible medium to facilitate communication of such software. In this context, the transmission medium is a device-readable medium.

[0235] The terms “machine-readable medium,” “computer-readable medium,” and “device-readable medium” refer to the same thing and may be used interchangeably in this disclosure. These terms are defined to include both machine storage media and transmission media. Therefore, these terms include both storage devices / media and carrier / modulated data signals.

[0236] The implementation of the described subject may include one or more features, individually or in combination, as shown by way of example.

[0237] Example 1 is an apparatus for configuring a user equipment (UE) to operate in a semi-static channel access mode in a fifth-generation new radio (5G NR) network. The apparatus includes: processing circuitry, wherein, for configuring the UE to use ultra-reliable low-latency communication (URLLC) in unlicensed spectrum of the 5G NR network, the processing circuitry is configured to: decode higher-layer signaling received from a base station, the higher-layer signaling including COT configuration information having multiple shared combinations of Channel Occupancy Time (COT), each COT shared combination specifying a duration and offset; acquire a fixed frame period (FFP) based on the successful completion of a Listen-After-Speak (LBT) procedure performed by the UE as the initiating device, the FFP including a COT and an idle period; and encode configured approval (CG) uplink control information (UCI) for transmission to the base station, the CG... The UCI includes a COT sharing indication associated with one of the plurality of COT sharing combinations; decoding of DL information received during downlink (DL) transmissions at the base station during the COT, the DL transmissions including a plurality of DL transmission slots corresponding to the duration of the COT sharing combination; and a memory coupled to the processing circuitry and configured to store the COT configuration information.

[0238] In Example 2, the subject matter as described in Example 1 includes the following subject matter, wherein the DL transmission is received at a DL transmission slot that is spaced apart from the end of the CG UCI transmission by a plurality of slots, the plurality of slots corresponding to the offset of the COT shared combination.

[0239] In Example 3, the subject matter as described in Examples 1-2 includes the following subject matter, wherein, in order to perform the LBT process, the processing circuitry is configured to: perform energy detection of the unlicensed spectrum based on an energy detection threshold.

[0240] In Example 4, the topic as described in Example 3 includes the following topic, wherein the energy detection threshold is based on the maximum transmit power of the UE.

[0241] In Example 5, the subject matter as described in Examples 1-4 includes the following subject matter, wherein the DL information includes one or both of DL data and DL control information dedicated to the UE.

[0242] In Example 6, the subject matter as described in Examples 1-5 includes the following subject matter, wherein the processing circuitry is configured to: complete the reception of the DL transmission before the end of the FFP.

[0243] In Example 7, the subject matter as described in Examples 1-6 includes: a transceiver circuit coupled to the processing circuit; and one or more antennas coupled to the transceiver circuit.

[0244] Example 8 is a computer-readable storage medium storing instructions for execution by one or more processors of a base station, the instructions being configured to: configure the base station for ultra-reliable low-latency communication (URLLC) in unlicensed spectrum of a fifth-generation new radio (5G NR) network, and to cause the base station to perform operations including: encoding higher-layer signaling for transmission to a user equipment (UE), the higher-layer signaling including COT configuration information having multiple shared combinations of channel occupancy time (COT), each COT shared combination specifying a duration and offset; decoding configured approval (CG) uplink control information (UCI), the CG UCI being received during a fixed frame period (FFP) of the UE, the FFP being acquired based on the successful completion of a listen-before-tell (LBT) procedure performed by the UE as the initiating device, the FFP including COT and idle period, the CG... The UCI includes a COT sharing indication associated with one of the plurality of COT sharing combinations; and downlink (DL) information encoded for use in DL transmission to the UE during the COT, the DL transmission including a plurality of DL transmission slots corresponding to the duration of the COT sharing combination.

[0245] In Example 9, the subject matter as described in Example 8 includes the following subject matter, wherein the DL transmission is started at a DL transmission slot that is spaced apart from the end of the transmission of the CG UCI by a plurality of slots, the plurality of slots corresponding to the offset of the COT shared combination.

[0246] In Example 10, the subject matter as described in Examples 8-9 includes the following subject matter, wherein the DL information includes one or both of DL data and DL control information dedicated to the UE.

[0247] In Example 11, the subject matter as described in Examples 8-10 includes, further, the operation of completing the DL transfer before the end of the FFP.

[0248] In Example 12, the subject matter as described in Examples 8-11 includes, further, suppressing listening to the downlink channel during the COT before the DL transmission.

[0249] In Example 13, the subject matter as described in Example 12 includes, further, the operation of: suppressing the constraint of the duration of the DL transmission to 584 µs.

[0250] In Example 14, the subject matter as described in Examples 12-13 includes, further, scheduling at least a second UE uplink (UL) transmission during the COT.

[0251] Example 15 is a computer-readable storage medium storing instructions for execution by one or more processors of a user equipment (UE), the instructions being configured to: configure the UE for ultra-reliable low-latency communication (URLLC) in semi-static channel access mode in unlicensed spectrum of a fifth-generation new radio (5G NR) network, and to cause the UE to perform operations including: decoding higher-layer signaling received from a base station, the higher-layer signaling including COT configuration information having multiple shared combinations of channel occupancy time (COT), each COT shared combination specifying a duration and offset; acquiring a fixed frame period (FFP) based on the successful completion of a listen-before-speak (LBT) procedure performed by the UE as the initiating device, the FFP including a COT and an idle period; and encoding configured approval (CG) uplink control information (UCI) for transmission to the base station, the CG... UCI includes a COT sharing indication associated with one of the plurality of COT sharing combinations; and decoding of DL information received during downlink (DL) transmissions at the base station during the COT, the DL transmissions including a plurality of DL transmission slots corresponding to the duration of the COT sharing combination.

[0252] In Example 16, the subject matter as described in Example 15 includes the following subject matter, wherein the DL transmission is received at a DL transmission slot that is spaced apart from the end of the CG UCI transmission by a plurality of slots, the plurality of slots corresponding to the offset of the COT shared combination.

[0253] In Example 17, the subject matter as described in Examples 15-16 includes the following subject matter, wherein, in order to perform the LBT process, the operation further includes: performing energy detection of the unlicensed spectrum based on an energy detection threshold.

[0254] In Example 18, the topic described in Example 17 includes the following topic, wherein the energy detection threshold is based on the maximum transmit power of the UE.

[0255] In Example 19, the subject matter as described in Examples 15-18 includes the following subject matter, wherein the DL information includes one or both of DL data and DL control information dedicated to the UE.

[0256] In Example 20, the subject matter as described in Examples 15-19 includes, further, the operation of receiving the DL transmission before the end of the FFP.

[0257] Example 21 is at least one machine-readable medium including instructions that, when executed by processing circuitry, cause the processing circuitry to perform an operation to implement any one of Examples 1-20.

[0258] Example 22 is an apparatus that includes components for implementing any one of Examples 1-20.

[0259] Example 23 is a system for implementing any one of Examples 1-20.

[0260] Example 24 is a method for implementing any one of Examples 1-20.

[0261] While one aspect has been described with reference to specific exemplary aspects, it will be apparent that various modifications and changes can be made to these aspects without departing from the broader scope of this disclosure. Therefore, the specification and drawings are to be considered illustrative rather than restrictive. Consequently, this detailed description should not be construed in a restrictive sense, and the scope of each aspect is defined only by the appended claims together with the full scope of their equivalents.

Claims

1. An apparatus for a user equipment (UE) configured to operate in a fifth-generation new radio (5G NR) network, the apparatus comprising: The processing circuit, wherein, in order to configure the UE to access the channel during semi-static channel occupancy in the 5G NR network, the processing circuit is configured to: The system information received from the base station is decoded, and the system information configures the channel access mode of the UE to semi-static channel occupancy; The Radio Resource Control (RRC) signaling is decoded, the RRC signaling including a configured approval configuration associated with uplink transmissions performed by the UE during semi-static channel occupancy, the RRC signaling including Channel Occupancy Time (COT) sharing information, and the COT sharing information including at least slot identification information, wherein the slot identification information includes an offset indicated by a slot; The RRC signaling includes an entry indicating that COT sharing is unavailable and other entries, each providing a channel occupancy sharing information; The configured approved uplink control information (CG-UCI) is encoded for transmission to the base station, the CG-UCI including COT sharing information for the UE's COT, including the time slot identification information; and The downlink (DL) transmission received from the base station is decoded. The received DL transmission begins in the time slot associated with the time slot identification information within the COT, wherein the time slot in which the DL transmission begins is identified as x+0, where x is the current time slot and 0 is the offset indicated by the time slot identification information. and The memory is coupled to the processing circuitry and configured to store the system information and the RRC signaling.

2. The apparatus of claim 1, wherein, The RRC signaling that includes the COT sharing information is the CG-COT-Sharing-r16 cell.

3. The apparatus of claim 1, wherein, The COT sharing information transmitted in the CG-UCI includes duration information D, which indicates the duration of DL transmission in the time slot.

4. The apparatus of claim 1, wherein, The DL transmissions received from the base station during the UE's COT include user plane data or control information associated only with the UE.

5. The apparatus of claim 1, wherein, The processing circuit is used for: A fixed frame period (FFP) is obtained based on the successful completion of the Listen-Before-Speak (LBT) procedure performed by the UE as the initiating device. The FFP includes the COT and the idle period.

6. The apparatus of claim 5, wherein, In order to perform the LBT process, the processing circuit is used to: Energy detection of the unlicensed spectrum is performed based on the energy detection threshold.

7. The apparatus of claim 6, wherein, The energy detection threshold is based on the UE's maximum transmit power.

8. The apparatus of claim 1, further comprising: A transceiver circuit coupled to the processing circuit; and One or more antennas coupled to the transceiver circuit.

9. A computer-readable storage medium storing instructions, the instructions being executed by one or more processors of a base station, the instructions configuring the base station to perform channel access during semi-static channel occupancy in a fifth-generation new radio (5GNR) network, and causing the base station to perform the following operations: System information is encoded for transmission to a user equipment (UE), the system information configuring the UE's channel access mode to semi-static channel occupancy; Radio Resource Control (RRC) signaling is encoded for transmission to the UE, the RRC signaling including a configured approval configuration associated with uplink transmissions performed by the UE during semi-static channel occupancy, the RRC signaling including Channel Occupancy Time (COT) sharing information, and the COT sharing information including at least slot identification information, wherein the slot identification information includes an offset indicated by a slot; The RRC signaling includes an entry indicating that COT sharing is unavailable and other entries, each providing a channel occupancy sharing information; The configured approved uplink control information (CG-UCI) received from the UE is decoded, the CG-UCI including COT sharing information for the UE's COT, including the time slot identification information; and Data for downlink (DL) transmission to the UE is encoded, the DL transmission starting in a time slot within the COT associated with the time slot identification information, wherein the time slot in which the DL transmission begins is identified as x+O, where x is the current time slot and O is the offset indicated by the time slot identification information.

10. The computer-readable storage medium of claim 9, wherein, The RRC signaling that includes the COT sharing information is the CG-COT-Sharing-r16 cell.

11. A computer-readable storage medium storing instructions, the instructions being executed by one or more processors of a user equipment (UE), the instructions configuring the UE to access a channel in a fifth-generation new radio (5GNR) network during semi-static channel occupancy, and causing the UE to perform the following operations: The system information received from the base station is decoded, and the system information configures the channel access mode of the UE to semi-static channel occupancy; The Radio Resource Control (RRC) signaling is decoded, the RRC signaling including a configured approval configuration associated with uplink transmissions performed by the UE during semi-static channel occupancy, the RRC signaling including Channel Occupancy Time (COT) sharing information, and the COT sharing information including at least slot identification information, wherein the slot identification information includes an offset indicated by a slot; The RRC signaling includes an entry indicating that COT sharing is unavailable and other entries, each providing a channel occupancy sharing information; The configured approved uplink control information (CG-UCI) is encoded for transmission to the base station, the CG-UCI including COT sharing information for the UE's COT, including the time slot identification information; and The downlink (DL) transmission received from the base station is decoded. The received DL transmission begins in a time slot within the COT associated with the time slot identification information, wherein the time slot in which the DL transmission begins is identified as x+0, where x is the current time slot and 0 is the offset indicated by the time slot identification information.

12. The computer-readable storage medium of claim 11, wherein, The RRC signaling that includes the COT sharing information is the CG-COT-Sharing-r16 cell.

13. The computer-readable storage medium of claim 11, wherein, The COT sharing information transmitted in the CG-UCI includes duration information D, which indicates the duration of DL transmission in the time slot.

14. The computer-readable storage medium of claim 11, wherein, The DL transmissions received from the base station during the UE's COT include user plane data or control information associated only with the UE.

15. The computer-readable storage medium of claim 11, wherein the operation further comprises: A fixed frame period (FFP) is obtained based on the successful completion of the Listen-Before-Speak (LBT) procedure performed by the UE as the initiating device. The FFP includes the COT and the idle period.

16. The computer-readable storage medium of claim 15, wherein, In order to perform the LBT process, the operation further includes: Energy detection of the unlicensed spectrum is performed based on the energy detection threshold.

17. The computer-readable storage medium of claim 16, wherein, The energy detection threshold is based on the UE's maximum transmit power.

Images