Methods and devices for contention-based data transmission using orthogonal cover codes

Abstract

A user equipment (UE) and a base station (BS) enable a contention-based (CB) data transmissions without using a random preamble and a random access response. The UE receives (704) a CB preconfigured grant configuration and an orthogonal cover code. The UE then transmits (708) a CB transmission including uplink data on a CB physical uplink shared channel occasion and using the orthogonal cover code.

Description

Patent Application Attorney Docket Number 0683-097-WO METHODS AND DEVICES FOR CONTENTION-BASED DATA TRANSMISSION USING ORTHOGONAL COVER CODES FIELD OF THE DISCLOSURE

[0001] This document generally describes methods and devices operating in wireless communication systems such as (but not limited to) the ones described in 5G standard documents, known as 3GPP communication systems. In particular, these methods and devices enhance contention-based data transmissions by using orthogonal cover codes (OCCs) to decrease a collision probability thereby increasing an uplink transmission efficiency. BACKGROUND

[0002] This background section is provided for the purpose of generally presenting the context and the technical problems. Work of the presently named inventors, to the extent it is described in this background section, as well as aspects of the description that do not otherwise qualify as prior art at the time of filing, are neither expressly nor impliedly admitted as prior art.

[0003] The 5G technology builds upon the framework developed for Long Term Evolution (LTE) terrestrial networks (TNs). However, 5G (as well as LTE) systems now extend to communications employing non-terrestrial networks (NTNs) tailored for the Narrowband Internet-of-Thing (NB-IoT) or the enhanced Machine Type Communication (eMTC) scenarios. In an NTN, a radio frequency (RF) transceiver is mounted on a satellite or an uncrewed aircraft system (UAS) (e.g., a drone, a balloon, a plane, etc.). For simplicity, the discussion below refers to all flying apparatuses with an RF transceiver used for intermediating wireless communications as satellites. In addition to satellites, an NTN typically includes a satellite gateway (simply referred to as “sat- gateway” or sometimes as “NTN gateway”) that bridges NTN’s access to a public data network, feeder links between sat-gateways and satellites, service links from the satellite to user equipment (i.e., terminal devices that may be mobile), and inter-satellite links (ISL) between satellites when the satellite is part of a satellite constellation.Patent Application Attorney Docket Number 0683-097-WO

[0004] A satellite can belong to one of several types based on altitude, orbit, beam footprint size, and beam footprint movement. The types include Low-Earth Orbit (LEO) satellite, Medium-Earth Orbit (MEO) satellite, Geostationary Earth Orbit (GEO) satellite, UAS platform (including High Altitude Platform Station (HAPS)), and High Elliptical Orbit (HEO) satellite. The GEO satellites are also known as the Geosynchronous Orbit (GSO) satellites, and LEO / MEO satellites are also known as non-GSO (NGSO) satellites. A GSO satellite communicates with one or more sat- gateways deployed over a satellite targeted coverage area (e.g., a region, country, continent, etc.). A non-GSO satellite at different times communicates with one or several serving sat-gateways. An NTN may be designed to provide service and feeder links continuity between successive serving sat-gateways, with sufficient time overlap to proceed with mobility anchoring and hand-over procedures.

[0005] A satellite may support a transparent payload or a regenerative (with on- board processing) payload, and typically generates several beams for a given service area bounded by its field of view. The footprints of the beams typically have an elliptic shape and depend on the on-board antenna configuration and the satellite’s elevation angle. For a transparent payload, a satellite applies RF filtering and / or frequency conversion and amplification but refrains from changing the waveform signal. For a regenerative payload, a satellite applies RF filtering, frequency conversion and amplification, demodulation and decoding, routing, and / or coding / modulation. The regenerative payload approach is effectively equivalent to the satellite performing most of the functions of a base station (e.g., that is, a 5G Next Generation base station (gNB), or an LTE base station (eNB)).

[0006] The NB-IoTs and the eMTC devices are expected to be particularly suitable for operating in remote areas with limited or no terrestrial connectivity. The NB-IoT devices are used in a variety of industries including, for example: (a) transportation (maritime, road, rail, air) and logistics, (b) solar, oil, and gas harvesting, (c) utilities, (d) farming, (e) environmental monitoring, and (f) mining. These industries deploy satellites to enable connectivity beyond terrestrial coverage. Satellite deployment for NB-IoT or eMTC devices is complementary to terrestrial deployments.Patent Application Attorney Docket Number 0683-097-WO

[0007] Technical features related to NTNs were included in 3GPP Release 17, but since then, they have been optimized in Release 18 and commercial deployments are ongoing. Based on real deployment or deployment plans, 3GPP has identified further aspects of NTNs that need addressed. For example, since in NTN for NB-IoT, the uplink (UL) capacity is tightly coupled with the downlink (DL) control signaling capacity, one objective of the Rel-19 is to improve Early Data Transmission (EDT). An EDT allows a terminal device to transmit data during a Random Access (RA) procedure. The RA procedure conventionally includes four messages: first, the terminal device transmits an RA preamble (msg1) to the network, then the network replies with a random access response (RAR) (msg2), followed by the terminal device transmitting payload data (msg3), and finally, the network releases the connection (msg4). Reducing the UL and DL signaling for completing an EDT in a contention-based data transmission (CBDT) could enhance capacity for data transmission network, reduce latency and improve UE’s battery lifetime.

[0008] Using OCCs favors distinguishing between different CBDTs. In conventional UEs and BSs it remains unclear how to enable an OCC when transmitting a random access (RA) procedure Message 3 without a prior RA msg1 and an RAR.Patent Application Attorney Docket Number 0683-097-WO BRIEF DESCRIPTION OF THE DRAWINGS

[0009] The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate one or more embodiments and, together with the description, explain these embodiments.

[0010] Fig.1 exemplarily illustrates a wireless communication system that includes a UE and at least one base station (BS) configured to perform methods according to various embodiments.

[0011] Fig.2A illustrates a protocol stack usable for communications between the UE in Fig.1 and one or more BSs.

[0012] Fig.2B illustrates another protocol stack usable for communications between the UE of Fig.1 and one or more BSs;

[0013] Fig.3A is a block diagram of an example NTN node with transparent payload embodiment, in which a BS on the ground connects to UE via a satellite and a sat-gateway.

[0014] Fig.3B is a block diagram of an example NTN node with regenerative payload embodiment, in which a base station is mounted on a satellite.

[0015] Fig.4A-4C illustrate scenarios of UEs using contention-based data transmissions and power control according to some embodiments.

[0016] Fig.5 is a frequency-time graph illustrating a CB preconfigured grant configuration for a cell according to a scenario.

[0017] Fig.6 is a frequency-time graph illustrating a CB preconfigured grant configuration for a cell according to another scenario.

[0018] Figs.7, 8A-C, and 9A-C are flowcharts of UE methods related to the orthogonal cover code (OCC) use for CBDTs.

[0019] Figs.10, 11A-D, and 12 are flowcharts of BS methods related to the OCC use for CBDTs.Patent Application Attorney Docket Number 0683-097-WO DETAILED DESCRIPTION

[0020] Methods and devices described in this section embody techniques related to the use of orthogonal cover codes (OCCs) in contention-based data transmissions (CBDTs). In order to enhance capacity for data transmission, a CBDT reduces the UL and DL signaling for completing an EDT by, for example: transmitting msg3 of a four-step RA procedure without msg1 and / or msg2 (RAR), and / or efficient delivery (reduced overhead of msg4 (e.g., RRCEarlyDataComplete). Difference between CBDTs and a two-step RACH is summarized in the following table: Contention-based PUSCH Two-step RACH t i idrawings. The same reference numbers in different drawings identify the same or similar elements. The detailed descriptions do not preclude other embodiments within the scopePatent Application Attorney Docket Number 0683-097-WO of the appended claims. The embodiments are not limited to the described configurations but may be extended to other arrangements.

[0022] Fig.1 illustrates a wireless communication system 100 that includes a UE 102, base stations 104 and 106, and a core network (CN) 110. The base stations 104 and 106 can operate in a RAN 105 connected to the CN 110 and other base station components, such as satellites, as will be described with reference to Figs.3A and 3B below. The CN 110 can be implemented as an evolved packet core (EPC) 111 or a fifth generation (5G) core (5GC) 160, for example. The CN 110 can also be implemented as a sixth generation (6G) core and future evolutions.

[0023] The base station 104 covers a cell 124, and the base station 106 covers a cell 126. The cells 124 and 126 can partially overlap, so that the UE 102 can select, reselect, or hand over from one of the cells 124 and 126 to the other. For the purpose of illustration and not of limitation, the footprint of cell 124 is elliptical, which shape is typical for NTN beams, which the footprint of cell 126 is hexagonal, which is a shape often associated with TN beams. If the base station 104 is a gNB, the cell 124 is an NR cell. If the base station 104 is an ng-eNB or eNB, the cell 124 is an evolved universal terrestrial radio access (E-UTRA) cell. Similarly, if the base station 106 is a gNB, the cell 126 is an NR cell, and if the base station 106 is an ng-eNB or eNB, the cell 126 is an E-UTRA cell. The cells 124 and 126 can be in the same Radio Access Network Notification Areas (RNA) or different RNAs. In general, the RAN 105 can include any number of terrestrial and non-terrestrial base stations, and each of the base stations can cover one, two, three, or any other suitable number of cells. The UE 102 can support at least a 5G NR (or simply, “NR”) or E-UTRA air interface to communicate with the base stations 104 and 106. Each of the base stations 104, 106 connect to the CN 110 via an interface (e.g., S1 or NG interface). The base stations 104 and 106 also can be interconnected via an interface (e.g., X2 or Xn interface) for interconnecting NG RAN nodes.

[0024] Among other components, the EPC 111 includes a Mobility Management Entity (MME) 112, a Serving Gateway (SGW) 114, and a Packet Data Network Gateway (PGW) 116. The MME 112 is configured to manage authentication, registration, paging, and other related functions. The SGW 114 is configured to transfer user-plane packets related to audio calls, video calls, Internet traffic, etc. The PGW 116 provides connectivityPatent Application Attorney Docket Number 0683-097-WO from UEs to one or more external packet data networks (e.g., an Internet network and / or an Internet Protocol (IP) Multimedia Subsystem (IMS) network). The 5GC 160 includes an Access and Mobility Management Function (AMF) 162, a Session Management Function (SMF) 164, and a User Plane Function (UPF) 166. The AMF 162 is configured to manage authentication, registration, paging, and other related functions. The SMF 164 is configured to manage PDU sessions. The UPF 166 is configured to transfer user-plane packets related to audio calls, video calls, Internet traffic, etc.

[0025] As discussed in detail below, the UE 102 and / or the RAN 105 may utilize the techniques of this disclosure when the radio connection between the UE 102 and the RAN 105 is suspended, e.g., when the UE 102 operates in an inactive or idle state of the protocol for controlling radio resources between the UE 102 and the RAN 105. For clarity, the examples below refer to the RRC_INACTIVE or RRC_IDLE state of the RRC protocol.

[0026] The base station 104 is equipped with processing hardware 130 that includes one or more general-purpose processors (e.g., central processing units (CPUs)) and a non-transitory computer-readable medium storing instructions that the one or more general-purpose processors execute. Additionally or alternatively, the processing hardware 130 can include special-purpose processing units. The processing hardware 130 illustrated in Fig.1 includes a processor 132 to process data that the base station 104 transmits in the DL direction, or process data received by the base station 104 in the UL direction. The processing hardware 130 also includes a transmitter 134 configured to transmit data in the DL direction, and a receiver 136 configured to receive data in the UL direction. The transmitter and the receiver may be or not separate hardware entities and may be called collectively transceiver. The processing hardware 130 further includes a memory 138, that is, a non-transitory computer-readable medium. The base station 106 includes generally similar components, that is, the processing hardware 140’s components 142, 144, 146, and 148 are substantively similar to the components 130, 132, 134, 136, and 138 respectively.

[0027] The UE 102 is equipped with processing hardware 150 that includes one or more general-purpose and / or special-purpose processors (e.g., CPUs) and a non- transitory computer-readable memory storing machine-readable instructions executable on the one or more processors, and / or special-purpose processing units. The processingPatent Application Attorney Docket Number 0683-097-WO hardware 150 includes a processor 152 to process data that the UE 102 transmits in the UL direction, or to process data received by UE 102 in the DL direction. The processing hardware 150 also includes a transmitter 154 configured to transmit data in the DL direction and a receiver 156 configured to receive data in the UL direction. The transmitter and the receiver may be or not separate hardware entities and may be called collectively transceiver. The processing hardware further includes a memory 158, that is, a non- transitory computer-readable medium.

[0028] Fig.2A exemplarily illustrates a protocol stack 200A usable for communications between the UE 102 and an eNB / ng-eNB or a gNB (e.g., the base station 104 as marked therein but may be base station 106 as well). In the protocol stack 200A, a physical (PHY) layer 202 provides transport channels to a medium access control (MAC) sublayer 204, which in turn provides logical channels to a radio link control (RLC) sublayer 206. The RLC sublayer 206 in turn provides RLC channels to a packet data convergence protocol (PDCP) sublayer 208. The PDCP sublayer 208 in turn can provide data transfer services to a radio resource control (RRC) sublayer 210, an IP layer and / or a Service Data Adaptation Protocol (SDAP) sublayer (not shown in Fig.2). The PDCP sublayer 208 receives packets (e.g., from the RRC sublayer 210, the SDAP sublayer, or the IP layer, layered directly or indirectly over the PDCP layer 208) referred to as service data units (SDUs), and output packets (e.g., to the RLC layer 206) referred to as protocol data units (PDUs). Except where the difference between SDUs and PDUs is relevant, this disclosure for simplicity refers to both SDUs and PDUs as “packets”. The PHY layer 202, the MAC sublayer 204, the RLC sublayer 206, the PDCP sublayer 208, and the RRC sublayer 210 may be EUTRA layers / sublayers or NR layers / sublayers.

[0029] The RRC sublayer 210 provides data transfer services to a Non-Access- Stratum (NAS) layer 212. The NAS layer 212 includes a mobility management (MM) sublayer and / or a session management (SM) sublayer. The MM sublayer may be an EPS MM (EMM) sublayer or a 5G MM (5GMM) sublayer. The SM sublayer may be an EPS SM (ESM) sublayer or a 5G SM (5GSM) sublayer. When the base station (gNB or eNB 104 / 106) receives UL NAS PDUs from the UE 102, the base station forwards the UL NAS PDUs to the CN 110 without processing the UL NAS PDUs. When the basePatent Application Attorney Docket Number 0683-097-WO station receives DL NAS PDUs from the CN 110, the base station forwards the DL NAS PDUs to the UE 102 without processing the DL NAS PDUs. That is, the BS is transparent to the NAS layer 212.

[0030] On a control plane, the PDCP sublayer 208 provides signaling radio bearers (SRBs) to the RRC sublayer 210 to exchange RRC messages or NAS messages (e.g., MM messages and / or SM messages). On a user plane, the PDCP sublayer 208 provides Data Radio Bearers (DRBs) to support user plane data exchange. User plane data exchanged on the PDCP sublayer 208 is made of SDAP PDUs, IP packets or Ethernet packets.

[0031] Fig.2B illustrates a protocol stack 200B similar to the protocol stack 200A, except that unlike in Fig.2A, the BS (gNB / eNB) 104 is not transparent to NAS layer 212. As illustrated in Fig.2B, the NAS layer includes a first part 212A between the UE 102 and the base station 104, and a second part 212B between the base station 104 and the CN 110. Therefore, when the base station 104 receives a UL NAS PDU from the UE 102, the base station processes the UL NAS PDU and transmits a DL NAS PDU to the UE 102 in response. However, when the base station 104 receives DL NAS PDUs from the CN 110, the base station 104 may forward the DL NAS PDUs to the UE 102 without processing the DL NAS PDUs. In other words, the base station may be equipped with a portion of functions of the NAS layer 212 in Fig.2A.

[0032] Fig.3A illustrates a transparent payload NTN deployment 300A, in which a satellite gateway 302 and a “transparent” satellite 304 intermediate communications between the base station 104 and the UE 102. As already mentioned, the “transparent” satellite 304 operates as an analogue RF repeater, performing (if needed) an RF filtering in both the uplink and downlink directions but not modifying the transmitted signals. Thus, the satellite 304 repeats the signal received on the feeder link from the NTN gateway on the service link between the satellite and the UE in the downlink direction and vice versa in the uplink direction. The Satellite Radio Interface (SRI) on the feeder link is the Uu, and the NTN gateway 302 supports all necessary functions to forward the signal of the Uu interface. The NTN gateway 302 may be collocated with the base station 104 or may be connected to the base station 104 via a wired link. A base station may be connected toPatent Application Attorney Docket Number 0683-097-WO more than one NTN gateway. Different transparent satellites may be connected to the same base station on the ground, via the same NTN gateway, or via different NTN gateways. The BS 104 communicates with the CN 110 via an S1 or NG interface, and the CN 110 is typically connected to a data network 307.

[0033] Fig.3B illustrates a regenerative payload NTN deployment 300B, in which the base station 104 is on the satellite 304. The satellite 304 is able to perform an RF filtering, an RF amplification, and a frequency conversion in both the uplink and / or downlink directions. As a result, the base station 104 communicates with the UE 102 via the satellite 304 and an Uu radio interface in the downlink direction and vice versa in the uplink direction. The base station 104 communicates with the CN 110 via a feeder link (between the NTN gateway 302 and the satellite 304) and a link between the NTN gateway 302 and the CN 110. The NTN gateway 302 may be collocated with the CN 110 or may be connected to the CN 110 via a wired or a wireless link.

[0034] In the following scenarios, the BS 104 operating in the system of FIG.1 communicates with the UE 102 and the CN 110 via the satellite 304 as shown in FIGs.3A and 3B. The BS 104 may be located either on the ground, as in FIG.3A or mounted on the satellite 304, as in FIG.3B. The events in FIGs.4A-13B that are similar are labeled with similar reference numbers (e.g., event 404 of FIGs.4A-4C is similar to event 504 of FIGs. 5A-5C, 6, 7A-7C, and 8 and event 904 of FIGs.9A-9C), with differences discussed below where appropriate. With the exception of the differences shown in the figures and discussed below, any of the alternative embodiments discussed with respect to a particular event (e.g., for messaging and processing) may apply to events labeled with similar reference numbers in other figures. Note that the descriptions below, although discussed in the context of an NTN network, equally apply to communication between a UE and a BS in a terrestrial network.

[0035] FIG.4A illustrates a scenario 400A, in which the BS 104 transmits (e.g., broadcasts) 404 a random access channel (RACH) configuration and a contention-based preconfigured grant configuration to the UE 102 via a cell (e.g., cell 124) and satellite 304. In the following, all the communications between the UE 102 and the BS 104 occur via the cell and the satellite 304. In some embodiments, the BS 104 transmits (e.g., broadcasts) the RACH configuration and the CB preconfigured grant configuration using a systemPatent Application Attorney Docket Number 0683-097-WO information block (SIB). The SIB may be an SIB1 or another SIB. The BS 104 may transmit (e.g., broadcasts) 404 the RACH configuration and the CB preconfigured grant configuration using a first SIB and a second SIB to the UE 102, respectively. The first SIB may be an SIB1, and the second SIB may be an SIB other than the SIB1 (e.g., an SIB19, a SIB31, an SIB 32, or an SIB33).

[0036] In some embodiments, the RACH configuration includes configuration parameters for UEs to perform a random access procedure with the BS 104 via the satellite 304. In one embodiment, the RACH configuration includes configuration parameters for a four-step random access procedure. In another embodiment, the RACH configuration includes configuration parameters for a two-step random access procedure. For example, the configuration parameters include preamble information, power ramping parameters, random access control information, and / or physical RACH (PRACH) configuration. The preamble information configures a number of random access preambles. The power ramping parameters configure power ramping for transmitting a preamble, the random access control information configures a maximum number of preamble transmissions, a random access response window size, and / or a contention resolution timer value. The PRACH configuration configures a root sequence index and PRACH configuration information.

[0037] The CB preconfigured grant configuration configures UL time and frequency resources on the cell that UEs (e.g., the UE 102) may use to transmit data (e.g., control- plane data and / or user-plane data) without receiving a dynamic UL grant on a physical DL control channel (PDCCH) or in a random access response (RAR). In some embodiments, the UL time and frequency resources include one or more physical UL shared channel (PUSCH) occasions in the time domain and frequency domain. The UL time and frequency resources are shared among UEs. Based on the CB preconfigured grant configuration, the BS 104 attempts to receive or receives one or more UL transmissions on the UL time and frequency resources from one or more UEs. In some embodiments, the CB preconfigured grant configuration does not configure a random access preamble.

[0038] Various possible parts of the CB preconfigured grant configuration (i.e., UL time resources, UL frequency resources, power related parameters, redundancy version for repetitions, orthogonal cover code) are now discussed in more detail.Patent Application Attorney Docket Number 0683-097-WO

[0039] The UL frequency resources (i.e., frequencies allowed for UE UL transmission) may be specified in one or more frequency domain configurations. In some embodiments, the CB preconfigured grant configuration includes at least one of the following configurations and parameters: a frequency domain resource allocation configuration, a subcarrier configuration, a PO number, a frequency start configuration, a PRB-per-PO number, and a guard band configuration.

[0040] The frequency domain resource allocation configuration configures the UL frequency resources (e.g., CB PUSCH occasion(s) in the frequency domain). To simplify the following description, “PUSCH occasion” is understood to mean “CB PUSCH occasion”.

[0041] The subcarrier configuration configures one or more subcarriers for the UL frequency resource. In some embodiments, the subcarrier configuration is a subcarrier index.

[0042] The PO number indicates a number of PUSCH occasions in the frequency domain in a time instance. The PO number is a positive integer. For example, the PO number may be 1, 2, 4, 8 or 16.

[0043] The frequency start configuration indicates a starting physical resource block (PRB) of a PUSCH occasion. For example, the frequency start configuration is an offset with respect to PRB 0.

[0044] The PRB-per-PO number indicates the number of PRBs per PUSCH occasion.

[0045] A guard band configuration configures a guard band (e.g., in units of PRBs) between PUSCH occasions in the frequency domain.

[0046] The UL time resources (i.e., times allowed for UE UL transmission) may be specified in one or more time domain configurations. In some embodiments, the CB preconfigured grant configuration includes at least one of the following: a PUSCH offset or periodicity and a time domain allocation configuration.

[0047] The offset or the periodicity configures the PUSCH occasions in the time domain. The periodicity configures a periodicity for each of the PUSCH occasions in the time domain. The offset indicates a starting slot or subframe for each of the PUSCH occasions.Patent Application Attorney Docket Number 0683-097-WO

[0048] The time domain allocation configuration configures symbols used for a UL transmission or multiple UL transmissions (e.g., repetitions). In one embodiment, the symbols are in a slot or a subframe. In another embodiment, the symbols are in multiple slots or subframes. In some embodiments, the time domain allocation configuration configures a start symbol, a start slot and / or a start subframe, and / or one or more lengths indicating the number of symbols, the number of slots, and / or the number of subframes.

[0049] In some embodiments, the CB preconfigured grant configuration includes at least one the following configurations and parameters: a scrambling configuration, a repetition number, a redundancy version (RV) configuration, a modulation and coding scheme (MCS) configuration, a waveform configuration, a configuration parameter, one or more hybrid automatic repeat request (HARQ) process IDs (i.e., numbers) or a HARQ ID offset for a UL transmission or multiple UL transmissions (e.g., repetitions), a HARQ configuration, a frequency-hopping configuration, and a demodulation reference signal (DMRS) configuration.

[0050] The scrambling configuration configures data scrambling in a UL transmission or multiple UL transmissions (e.g., repetitions). For example, the scrambling configuration includes or is an identifier used to initialize data scrambling for a UL transmission or multiple UL transmissions (e.g., repetitions). If the CB preconfigured grant configuration does not include the scrambling configuration, the UE 102 applies a physical cell ID of the cell 124 to initialize data scrambling for a UL transmission or multiple UL transmissions (e.g., repetitions).

[0051] The repetition number indicates the number of multiple UL transmissions (e.g., repetitions).

[0052] The redundancy version (RV) configuration indicates each of multiple UL transmissions (e.g., repetitions) of a UL packet data unit (PDU) or transport block.

[0053] The MCS configuration configures an MCS for a UL transmission or multiple UL transmissions (e.g., repetitions). For example, the MCS configuration includes an MCS index indicating an MCS. In some embodiments, the MCS configuration configures DFT-s- OFDM (i.e., Discrete Fourier Transform-Spread Orthogonal Frequency Division Multiplexing) or CP-OFDM (i.e., Cyclic Prefix Orthogonal Frequency Division Multiplexing) for the UL transmission or multiple UL transmissions. In some embodiments, the MCSPatent Application Attorney Docket Number 0683-097-WO configuration includes multiple MCSs. For example, the MCS configuration includes multiple MCS indexes indicating respective MCSs. The UE 102 may select a MCS from the configured MCSs, based on one or more parameters and / or one or more condition(s) against the parameter(s). In some embodiments, the parameter(s) include a volume of data to be transmitted and / or DL signal strength of the cell 124. For example, the MCS configuration configures a first MCS and a second MCS. If the parameter is below a first threshold, the UE 102 selects the first MCS. Otherwise (i.e., if the parameter is above the first threshold), UE 102 selects the second MCS. If the parameter is equal to the first threshold, the UE 102 may select the first MCS or the second MCS. In another example, the MCS configuration configures a first MCS, a second MCS, and a third MCS. If the parameter is below a first threshold, the UE 102 selects the first MCS. Otherwise, if the parameter is above the first threshold and below a second threshold, the UE 102 selects the second MCS. If the parameter is above the second threshold, UE 102 selects the third MCS. If the parameter is equal to the first threshold, the UE 102 might select the first MCS or the second MCS. If the parameter is equal to the second threshold, the UE 102 might select the second MCS or the third MCS. The first threshold and the second threshold for the different parameters are different.

[0054] The waveform configuration configures DFT-s-OFDM or CP-OFDM for a UL transmission or multiple UL transmissions (e.g., repetitions). In some embodiments, the CB preconfigured grant configuration includes multiple waveform configurations corresponding to or associated with different MCSs in the MCS configuration.

[0055] The configuration parameter configures one or more PUSCH formats or types. The BS 104 attempts to decode or decodes a UL transmission with the one or more PUSCH formats or types.

[0056] The CB preconfigured grant configuration may include one or more HARQ process IDs (i.e., numbers) or a HARQ ID offset for a UL transmission or multiple UL transmissions (e.g., repetitions). Alternatively, the CB preconfigured grant configuration does not include or configure the number of HARQ processes for a UL transmission or multiple UL transmissions (e.g., repetitions). In some embodiments, the CB preconfigured grant configuration does not configure a HARQ process ID (i.e., a number) or a HARQ ID offset for a UL transmission or multiple UL transmissions (e.g., repetitions).Patent Application Attorney Docket Number 0683-097-WO

[0057] The HARQ configuration configures whether HARQ is enabled or disabled for a UL transmission or multiple UL transmissions (e.g., repetitions).

[0058] The CB preconfigured grant configuration may include a frequency-hopping configuration for a UL transmission or multiple UL transmissions (e.g., repetitions). Alternatively, the CB preconfigured grant configuration does not configure frequency hopping for the UL transmission or multiple UL transmissions.

[0059] The CB preconfigured grant configuration may also include a DMRS configuration for UL transmission or multiple UL transmissions (e.g., repetitions).

[0060] The power related resources (i.e., transmission power, ramping power, etc. allowed for UE UL transmission) may be specified via power control parameters. In some embodiments, the CB preconfigured grant configuration includes one or more power control parameters for a UL transmission or multiple UL transmissions (e.g., repetitions). The UE may receive separately at least one of the power control parameters. The UE 102 determines a transmission power for the UL transmission(s) 408-1, …, 408-M based on the power control parameters, and applies the transmission power to the UL transmission(s) 408-1, …, 408-M or each of the UL transmission(s) 408-1, …, 408-M. In some embodiments, the UE 102 uses the transmission power to transmit each of the UL transmission(s) 408-1, …, 408-M. In some embodiments, the power control configuration parameters include a received target power (value) and / or a scaling factor (e.g., an alpha value). The scaling factor applies to a DL pathloss estimated by the UE 102. In some embodiments, the UE 102 uses formula (1) with the received target power and the alpha value to determine a transmission power: Transmission power = Received target power + scaling factor × DL pathloss. (1)

[0061] In other embodiments, the UE 102 uses another formula with the received target power, the alpha value, and one or more additional adjustment values to determine a transmission power for the UL transmission(s) 408-1, …, 408-M. In some embodiments, the UE 102 uses the transmission power to transmit each of the UL transmission(s) 408-1, …, 408-M. For example, the additional adjustment value(s) includes a first additional adjustment value and a second adjustment value. The first additional adjustment value may be determined based on the number of PRBs for a UL transmission or each of UL transmissions. The second additional adjustment value may be determined based on thePatent Application Attorney Docket Number 0683-097-WO MCS for the UL transmission or each of UL transmissions. The transmitted power is then calculated using formula (2): Transmission power = Received target power + scaling factor × DL pathloss + the first adjustment value + the second adjustment value. (2)

[0062] In some embodiments, the first adjustment value is given by 10 log10(2µ× number of PRBs), where µ may be 0, 1, 2, 34, 5, or 6 corresponding to subcarrier spacing: 15 KHz, 30 KHz, 60 KHz, 120 KHz, 240 KHz, 480 KHz, and 960 KHz, respectively. The UE 102 determines the number in accordance with the subcarrier spacing that the UE 102 uses to communicate with the BS 104 and determines the first adjustment value for the UL transmission(s) 408-1, …, 408-M, based on the determined number. Alternatively, the first adjustment value may be 0 (i.e., it is omitted). In some embodiments, the CB preconfigured grant configuration indicates which first adjustment value = 10 log10 (2µ× number of PRBs) is applied. If the CB preconfigured grant configuration does not indicate the first adjustment value, the UE 102 considers that the first adjustment value = 0 (i.e., it is omitted). In some embodiments, the second adjustment value = 10log10(2BPRE⋅KS−1), where KS= a predetermined value (e.g., 1.25) and BPRE (Bits Per Resource Element) is the number of bits per resource element related to the MCS. Alternatively, the second adjustment value = 0 (i.e., it is omitted). In some embodiments, the CB preconfigured grant configuration indicates which second adjustment value = 10log10(2BPRE⋅KS−1) is applied. If the CB preconfigured grant configuration does not indicate the first adjustment value, the UE 102 considers that the second adjustment value = 0 (i.e., it is omitted).

[0063] In some other embodiments, the UE 102 compares the transmission power calculated above with a UE configured maximum output power (e.g., PCMAX). If the calculated transmission power is larger than the UE configured maximum output power, the UE 102 uses the UE configured maximum output power to transmit (each of) the UL transmission(s) 408-1, …, 408-M. In some embodiments, the UE 102 determines the UE configured maximum output power based on a power class that represents the maximum transmission power supported by the UE 102. In some embodiments, the UE 102 obtains a pathtloss (value) as follows:Patent Application Attorney Docket Number 0683-097-WO Pathloss = signaled reference signal power value – measured reference signal power value. (3)

[0064] The UE 102 receives the signaled reference signal power value from the BS 104 in a SIB broadcast by the BS 104. For example, the SIB is an SIB1, an SIB19, or an SIB31. The UE 102 measures a reference signal to obtain the measured reference signal power value. For example, the reference signal is a cell-specific reference signal (CRS). In another example, the reference signal is a synchronization signal (SS) / physical broadcast channel (PBCH) block.

[0065] In some embodiments, the UE 102 uses power control parameters in the CB preconfigured grant configuration and the RACH configuration to determine a transmission power for the UL transmission(s) 408-1, …, 408-M or each of the UL transmission(s) 408- 1, …, 408-M. In some embodiments, the UE 102 uses the transmission power to transmit each of the UL transmission(s) 408-1, …, 408-M. In some embodiments, the CB preconfigured grant configuration includes a received target power value and does not include a scaling factor. If the RACH configuration includes a scaling factor (e.g., an alpha value), the UE 102 uses the scaling factor from the RACH configuration and the received target power from the CB preconfigured grant configuration to determine a transmission power with the formula above (i.e., (1) or (2)). In one embodiment, if the RACH configuration does not include a scaling factor, the UE 102 uses a default scaling factor value and the received target power to determine a transmission power with the formula above (i.e., (1) or (2)). In some embodiments, the default scaling factor value is 1 (i.e., no scaling). In other embodiments, the default scaling factor value is larger than 1. In yet other embodiments, the default scaling factor value is smaller than 1.

[0066] In other embodiments, the CB preconfigured grant configuration does not include a received target power and includes a scaling factor. If the RACH configuration includes a received target power, the UE 102 uses the scaling factor (either from the CB preconfigured grant configuration or the RACH configuration) and the received target power with the formula (1) or (2) to determine the transmission power for the UL transmission(s) 408-1, …, 408-M. In some embodiments, the UE 102 uses the transmission power to transmit each of the UL transmission(s) 408-1, …, 408-M.Patent Application Attorney Docket Number 0683-097-WO

[0067] In some alternative embodiments, the CB preconfigured grant configuration does not include power control configuration parameters. In such cases, the UE 102 may use power control configuration parameters from the RACH configuration to determine a transmission power for the UL transmission(s) 408-1, …, 408-M. For example, the RACH configuration includes a preamble received target power value, a power offset value, and / or a scaling factor (e.g., an alpha value). In one embodiment, the preamble received target power value is an msgA preamble received target power. The power offset value may indicate a power offset between a preamble transmission and an Msg3 transmission or a power offset between a preamble transmission and an MsgA transmission. The scaling factor may be an alpha value for an Msg3 transmission or an alpha value for an MsgA transmission. The UE 102 may then determine a transmission power for the UL transmission(s) 408-1, …, 408-M as follows: Transmission power = preamble received target power + power offset + scaling factor × DL pathloss. (4)

[0068] After receiving the RACH configuration and the CB preconfigured grant configuration, the UE 102 initiates a communication session with the BS 104. The UE 102 may operate in an idle state, an inactive state or a connected state to initiate the communication session. The UE 102 may determine to use the CB preconfigured grant configuration for the communication session instead of the RACH configuration. The communication session may be a mobile originated session or a mobile terminated session (i.e., the UE 102 receives a paging from the BS 104 and initiates the communication session in response to the paging). In response to initiating the data communication session, UE 102 generates 406 a first UL PDU based on the CB preconfigured grant configuration. In some embodiments, the first UL PDU is a first UL MAC PDU. In some embodiments, UE 102 includes a first UL radio resource control (RRC) message in the first UL MAC PDU. In some embodiments, the UE 102 includes a UL common control channel (CCCH) message (e.g., UL-CCCH-Message) in the first UL MAC PDU, where the UL CCCH message includes the first UL RRC message. In some embodiments, the first UL RRC message is an RRC connection request message or an RRC setup request message. In other embodiments, the first UL RRC message is an RRC connection resume request message or an RRC resume request message. In yetPatent Application Attorney Docket Number 0683-097-WO other embodiments, the first UL RRC message is an RRC early data request message. In yet another embodiment, the first UL RRC message is an RRC connection reestablishment request message or an RRC reestablishment request message. In some embodiments, the UE 102 includes a user plane (UP) data packet or a non-access stratum (NAS) PDU in the first UL PDU or the first UL RRC message.

[0069] In some embodiments, the UE 102 may include a UE identity / identifier (ID) of the UE 102 in the first UL PDU or the first UL RRC message (e.g., the RRC connection resume request message, the RRC resume request message, the RRC connection reestablishment request message, or the RRC reestablishment request message). In some embodiments, the UE ID is a RAN ID. For example, the RAN ID is a first cell radio network temporary identifier (C-RNTI). In some embodiments, the UE 102 receives the first C-RNTI from the BS 104 and stores the first C-RNTI before initiating the communication session. In another example, the RAN ID is an inactive radio network temporary identifier (I-RNTI). In other embodiments, the UE ID is a NAS ID. For example, the NAS ID is an S-Temporary Mobile Subscription Identifier, a 5G S-Temporary Mobile Subscription Identifier, or a 6G S-Temporary Mobile Subscription Identifier.

[0070] The UE 102 then transmits 408 the first UL PDU to the BS 104, based on the CB preconfigured grant configuration. In some embodiments, the UE 102 transmits 408 the first UL PDU in one or more UL transmissions 408-1, …, 408-M to the BS 104, where M is an integer larger than zero. M may be one of 1, 2, 4, 8, 16, 32, 64, and / or 128. In some embodiments, the CB preconfigured grant configuration configures UL transmission resources for the UL transmission(s) on symbols within a slot or subframe. In such cases, the UE 102 transmits the UL transmission(s) on the symbols within the slot or subframe. In other embodiments, the CB preconfigured grant configuration configures UL transmission resources for the UL transmission(s) on symbols in multiple slots or subframes. In such cases, the UE 102 transmits the UL transmission(s) on the symbols in the multiple slots or subframes. If M is larger than one, the UL transmissions 408-2, …, 408-M are repetitions. In some embodiments, each of the UL transmission(s) is a HARQ transmission or a PUSCH transmission. In some embodiments, the UE 102 encodes the first UL PDU (i.e., a transport block including the first UL PDU) and a cyclic redundancy check (CRC) of the first UL PDU into an encoded block and transmits the encoded blockPatent Application Attorney Docket Number 0683-097-WO or a portion thereof in each of the UL transmission(s). In some embodiments, the CB preconfigured grant configuration includes a repetition number (i.e., M) as described above and the UE 102 determines M in accordance with the repetition number. In some embodiments, if the CB preconfigured grant configuration does not include the repetition number, the UE 102 transmits 408 only one UL transmission (i.e., the UL transmission 408-1) to the BS 104. In some embodiments, UE 102 does not transmit a random access preamble to transmit the first UL PDU.

[0071] The redundancy version for repetitions (i.e., how many times a transmission is repeated when the previous transmission is not detected by the BS) may be specified in one or more configurations of redundancy version for repetitions. In some embodiments, the BS 104 configures the same RV (e.g., RV 0) for each of the UL transmissions (i.e., repetitions) in the CB preconfigured grant configuration as described above, and the UE 102 transmits the first UL PDU (e.g., the same portion of the encoded block) in each of the UL transmissions using the same RV. For example, the CB preconfigured grant configuration includes a field / IE configuring the RV (e.g., RV 0) applied to the UL transmissions (i.e., repetitions). In such cases, the BS 104 decodes each UL transmission using the same RV.

[0072] In other embodiments, the BS 104 configures different RVs for the UL transmissions in the CB preconfigured grant configuration as described above, and the UE 102 transmits the different RVs of the first UL PDU in the UL transmissions. In such cases, the BS 104 receives each of the UL transmissions and decodes each UL transmission using the corresponding RV. For example, the different RVs of the first UL PDU may be different portions of the encoded block. In one embodiment, some of the portions may partially overlap. In another embodiment, the portions do not overlap. In some embodiments, the BS 104 may configure different RVs for the UL transmissions 408-1, …, 408-M as shown in Table 1. For example, the CB preconfigured grant configuration includes an RV configuration (e.g., the third row, the fourth row, the fifth row or the sixth row in Table 1). The UE 102 and the BS 104 apply the RV sequence to the UL transmissions.Patent Application Attorney Docket Number 0683-097-WO Table 1 RV to be applied to nthtransmission, where 1 ≤ n ≤ M [007g y p or more OCC configurations. The OOC is primarily used in conjunction with various Multiple Access schemes in 5G to provide better separation of user’s data and reduce interference. In some embodiments, the CB preconfigured grant configuration includes an OCC. The UE 102 applies the OCC to the UL transmission(s) 408-1, …, 408-M. For example, the UE 102 applies the OCC to the encoded block or the portion of the encoded block and then transmits the encoded block or the portion of the encoded block. In other embodiments, the CB preconfigured grant configuration includes a set of OCCs. In one embodiment, the UE 102 selects (e.g., randomly) an OCC 1 from the set and applies the OCC 1 to the UL transmission(s) 408-1, …, 408-M. For example, the UE 102 applies the OCC 1 to the encoded block or the portion of the encoded block and then transmits the encoded block or the portion of the encoded block. In some scenarios, another UE, called “additional UE” in this document (not illustrated in FIG.1) may select an OCC 2 from the set of OOCs. This additional UE applies the OCC 2 to UL transmission(s) and transmits the UL transmission(s) in the same PUSCH occasion(s) as the UL transmission(s) 408-1, …, 408- M of UE 102. In such cases, the UL transmission(s) of the additional UE and the UL transmission(s) 408-1, …, 408-M of UE 102 are overlapped. Because different OCCs are applied to the UL transmission(s) of the additional UE and the UL transmission(s) 408-1, …, 408-M of the UE 102, the interferences among the other UL transmission(s) and the UL transmission(s) 408-1, …, 408-M are minimized or eliminated. As a result, the BS 104 successfully receives and decodes the UL transmission(s) of the additional UE and the ULPatent Application Attorney Docket Number 0683-097-WO transmission(s) 408-1, …, 408-M of UE 102, using the OCC 2 and OCC 1, respectively. In some embodiments, OCCs in the set of OOCs have the same length. In other embodiments, at least two OCCs in the set of OOCs have different lengths. In some embodiments, the OCCs correspond to or are associated with different MCSs in the MCS configuration. In other embodiments, the CB preconfigured grant configuration does not configure an OCC. Thus, the UE 102 do not use an OCC to transmit the UL transmission(s) and the BS 104 does not use an OCC to receive the UL transmission(s).

[0074] As previously discussed, the CB preconfigured grant configuration includes one or more power control configuration parameters configuring a transmission power. The UE 102 determines the transmission power for the UL transmission(s) 408-1, …, 408- M in accordance with the power control configuration parameter(s) introduced above.

[0075] For example, the BS 104 determines to transmit a first DL PDU to the UE 102 after (e.g., in response to) receiving the first UL PDU. To transmit the first DL PDU, the BS 104 may transmit 410 a downlink control information (DCI) and a CRC of the DCI on a PDCCH to the UE 102. The BS 104 scrambles the CRC with a CB radio network temporary identifier (CB-RNTI). In some embodiments, the BS 104 scrambles the DCI with the CB-RNTI. The DCI includes a DL assignment to schedule one or more DL transmissions of the first DL PDU to the UE 102 as described below. In some embodiments, the first DL PDU does not include or is not a random access response. In other embodiments, the first DL PDU includes or is a random access response. In some embodiments, the BS 104 transmits 412 the first DL PDU to the UE 102, based on a DL assignment.

[0076] The UE 102 may apply scrambling to (each of) the UL transmission(s) 408-1, …, 408-M. The UE 102 generates a scrambling sequence using a scrambling sequence generator and applies the scrambling sequence to bits transmitted in (each of) the UL transmission(s) 408-1, …, 408-M. The UE 102 initializes the scrambling sequence generator with an initial scrambling sequence. In some implementations, the UE 102 generates (e.g., compute or calculate) the initial scrambling sequence c_init using a radio network temporary identifier (RNTI), a power of 2, and / or a scrambling identity. In some implementations, the CB preconfigured grant configuration configures the scrambling identity. In other implementations, the scrambling identity is a physicalPatent Application Attorney Docket Number 0683-097-WO cell identity of the cell. In some implementations, the scrambling sequence generator is defined in a 3GPP specification (e.g., 3GPP specification 36.211 or 38.211). In some implementations, the RNTI is a CB-RNTI as described below. In other implementations, the RNTI is fixed value (e.g., 0).

[0077] After transmitting the first UL PDU as described above, the UE 102 may monitor a PDCCH using the CB-RNTI. While monitoring PDCCH with the CB-RNTI, the UE 102 receives 410 the DCI and the CRC of the DCI on the PDCCH from the BS 104. The UE 102 determines that the CRC is scrambled with the CB-RNTI based on the CB- RNTI and the DCI. The UE 102 receives 412 the first DL PDU from the BS 104 in accordance with the DL assignment, e.g., in response to determining the CRC is scrambled with the CB-RNTI.

[0078] In some embodiments, the BS 104 transmits 412 the first DL PDU in one or more DL transmissions 412-1, …, 412-N to the UE 102, where N is an integer larger than zero. N may be one of 1, 2, 4, 8, 16, 32, 64, and / or 128. In some embodiments, the DL assignment configures DL time and frequency resources for the DL transmission(s). The BS 104 transmits the DL transmission(s) on the DL time and frequency resources to the UE 102, and the UE 102 receives the DL transmission(s) on the DL time and frequency resources. The DL time resources may include symbols within one or more slots or subframes. In some embodiments, the DL transmissions 412-2, …, 412-N are repetitions. In some embodiments, each of the DL transmission(s) is a HARQ transmission or a physical DL shared channel (PDSCH) transmission. In some embodiments, the BS 104 encodes the first DL PDU (i.e., a transport block including the first DL PDU) and a CRC of the first DL PDU into an encoded block and transmits the encoded block or a portion thereof in each of the DL transmission(s). In some embodiments, the DL assignment includes a repetition number (i.e., N). In such cases, the BS 104 transmits 412 the N DL transmission(s) in accordance with the repetition number and the UE 102 may receive or attempt to receive 412 the N DL transmission(s) in accordance with the repetition number. If the DL assignment does not include a repetition number, the BS 104 may transmit the first DL PDU in only one DL transmission (i.e., 412-1). If the DL assignment does not include a repetition number, the UE 102 may receive or attempt to only receive the DLPatent Application Attorney Docket Number 0683-097-WO transmission 412-1 in accordance with the DL assignment. In some embodiments, the UE 102 discards the CB-RNTI in response to receiving the first DL PDU.

[0079] In some embodiments, the BS 104 configures the same RV (e.g., RV 0) for each of the DL transmission(s) in the DL assignment and / or the CB preconfigured grant configuration, and the BS 104 transmits the first DL PDU (e.g., the same portion of the encoded block) in each of the DL transmission(s) using the same RV. For example, the DL assignment or the CB preconfigured grant configuration includes a field / IE configuring a RV (e.g., RV 0) applied to the DL transmissions (i.e., repetitions). In such cases, the UE 102 receives and decodes each DL transmission using the same RV.

[0080] In other embodiments, the BS 104 configures the different RVs for the DL transmissions in the DL assignment and transmits the different RVs of the first DL PDU in the DL transmissions. In such cases, the UE 102 receives each of the DL transmissions and decodes each DL transmission using the corresponding RV. For example, the different RVs of the first DL PDU may be different portions of the encoded block. In one embodiment, some of the portions partially overlap. In another embodiment, the portions do not overlap. In some embodiment, the BS 104 may configure different RVs for the DL transmissions 412-1, …, 412-N in the CB preconfigured grant configuration or the DL assignment. For example, the CB preconfigured grant configuration or the DL assignment indicates an RV configuration (e.g., the third row, the fourth row, the fifth row or the sixth row in Table 2). The UE 102 and the BS 104 apply the RV configuration to the DL transmissions 412-1, …, 412-N based on the indication and / or the Table 2. In other embodiments, the DL assignment indicates a (single) RV. The UE 102 and the BS 104 apply RVs to the DL transmissions 412-1, …, 412-N based on the indicated RV and Table 2.Patent Application Attorney Docket Number 0683-097-WO Table 2 RV indicated in RV to be applied to nthtransmission, where 1 ≤ n ≤ M the DL, TI based on one or more parameters and one multiplier applied to at least one parameter. In some embodiments, the parameters include a slot number, a subframe number, a symbol number, a system frame number (SFN), a hyper SFN, a resource block number, a carrier identifier, and / or a contention resolution window size associated with when a UL transmission 408-K is transmitted, where 1 ≤ K ≤ M. In one example, K = 1. In another example, K = M. The parameter(s) additionally include a fixed number (e.g., 1, 2, …). In some embodiments the parameter(s) additionally include a parameter related to the OCC. In some embodiments, the slot number identifies a slot where the UL transmission 408-K is transmitted, where 1 ≤ K ≤ M. If the UL transmission 408-K is transmitted on symbols on two slots (i.e., a first slot and a second slot), the slot may be the first slot or the second slot. In some embodiments, the subframe number identifies a subframe where the UL transmission 408-K is transmitted. In some embodiments, the SFN identifies a frame including the slot or the subframe. In some embodiments, the hyper SFN identifies a hyper frame including the slot or the subframe. In some embodiments, the symbol number identifies a symbol in the slot or the subframe. For example, the symbol is the first symbol of the slot or the subframe. In another example, the symbol is the first symbol of symbols where the UL transmission 408-K is transmitted. In some embodiments, the resource block number identifies a resource block of resource blocks where the UL transmission 408-K is transmitted. For example, the resource block number is the lowest resource blockPatent Application Attorney Docket Number 0683-097-WO number. In another example, the resource block number is the highest resource block number. In some embodiments, the carrier identifier identifies a carrier where the UL transmission 408-K is transmitted. In the case where OCC(s) is / are configured as described above, the parameter(s) include an OCC identifier (ID) identifying an OCC selected by the UE, applied to the CB PUSCH transmission, or configured for the CB PUSCH occasion.

[0082] In some embodiments, the CB-RNTI is associated with the CB PUSCH occasion in which the CB PUSCH transmission (e.g., the CB PUSCH transmission 408-1) is transmitted. In some embodiments, the CB-RNTI is associated with the last CB PUSCH occasion in which the last CB PUSCH transmission (e.g., the CB PUSCH transmission 408-M) is transmitted in the case of repetitions. In other embodiments, the CB-RNTI is associated with the first CB PUSCH occasion in which the first CB PUSCH transmission (e.g., the CB PUSCH transmission 408-1) is transmitted in the case of repetitions. Generally, the value space of CB-RNTI(s) is different from the value space of RA-RNTI(s). In some embodiments, the CB PUSCH occasion(s) configured in the CB preconfigured grant configuration do not overlap with PRACH occasion(s) in the RACH configuration. Thus, the BS 104 ensures the value space of CB-RNTI(s) is different from the value space of RA-RNTI(s).

[0083] In some embodiments, a CB-RNTI is determined as follows: CB-RNTI = 1 + s_id + 14 × t_id + 14 × 80 × f_id + 14 × 80 × 8 × ul_carrier_id. (5)

[0084] In formula (5), s_id is an index of the first OFDM symbol of a CB PUSCH occasion (0 ≤ s_id < 14) and t_id is an index of the first slot of a CB PUSCH occasion in a system frame. For example, 0 ≤ t_id < 80. If the cell is operated with μ = 0, 1, 2 or 3, t_id is determined based on μ. If the cell is operated with μ = 5 or 6, t_id is an index of the 120 kHz slot in a system frame that contains the CB PUSCH occasion. Further, f_id is an index of a CB PUSCH occasion in the frequency domain, where 0 ≤ f_id < 8 (8 being the maximum number of CB PUSCH occasions that can be configured in the frequency domain). If only a single CB PUSCH occasion is configured for the cell in the frequency domain, the term “14 × 80 × f_id” is omitted. Also in formula (5), ul_carrier_id indicates aPatent Application Attorney Docket Number 0683-097-WO UL carrier used for a CB PUSCH transmission. In some embodiments, a value range of the ul_carrier_id depends on the maximum number of UL carriers that can be configured for the cell. For example, UL carriers 1, …, C are configured for the cell, where C is a positive integer. ul_carrier_id values 0, …, C-1 indicate UL carriers 1, …, C, respectively. If only a single UL carrier is configured for the cell, the term “14 × 80 × 8 × ul_carrier_id” is omitted.

[0085] When OCC(s) is / are configured as described above, the CB-RNTI may further be determined based on an OCC ID (occ_id) identifying an OCC. In this case, occ_id is considered in the formula for determining the CB-RNTI. Formulta 6 below exemplifies considering the occ_id in determining a CB-RNTI: CB-RNTI = 1 + s_id + 14 × t_id + 14 × 80 × f_id + 14 × 80 × 8 × ul_carrier_id + 14 × 80 × 8 × 2 × occ_id (6)

[0086] In formula (6), occ_id is an index of an OCC for a CB PUSCH transmission. For example, 0 ≤ occ_id < 2. In another example, 0 ≤ occ_id < 4. In yet another example, 0 ≤ occ_id < 16. In one embodiment, a value range of the occ_id depends on a maximum number of OCCs that can be configured for CB PUSCH occasion(s) or CB PUSCH transmission. The UE 102 determines the occ_id by identifying the OCC (e.g., a first OCC) that the UE 102 applies to the CB PUSCH transmission (e.g., the CB PUSCH transmission 408).

[0087] If the base station 104 receives CB PUSCH transmissions simultaneously from the UE 102 and an additional UE (not shown in Fig.4A) on the same CB PUSCH occasion with the first OCC and a second OCC respectively, the base station 104 uses a first CB-RNTI and a second CB-RNTI to send DCI 1 and DCI 2 to the UE 102 and the additional UE respectively, similar to event 410. In some embodiments, the base station 104 determines the first CB-RNTI and the second CB-RNTI based on the first OCC and the second OCC respectively. For example, a first occ_id and a second occ_id identify the first OCC and the second OCC, respectively. The base station 104 determines the first CB-RNTI and the second CB-RNTI based on the first occ_id and the second occ_id, respectively, as described above. In some embodiments, the base station 104 transmits the DCI 1 and the DCI 2 on the same PDCCH. In other embodiments, base station 104Patent Application Attorney Docket Number 0683-097-WO transmits the DCI 1 and the DCI 2 on different PDCCHs. The UE 102 determines a first CB-RNTI (same as the first CB-RNTI used by the base station 104) and the additional UE determines a second CB-RNTI (same as the second CB-RNTI used by the base station 104), as described above. Thus, UE 102 receives the DCI 1 using the first CB-RNTI and the additional UE receives the DCI 2 using the second CB-RNTI. In some embodiments, the DCI 1 and DCI 2 are DL assignments. For example, the CB PUSCH occasion is the CB PUSCH occasion where the UE 102 transmits the CB PUSCH transmission 408. The DCI 1 is the DL assignment 410. The DCI 2 is a DL assignment scheduling one or more DL transmissions of a DL PDU for the additional UE, similar to event 410. The DL PDU for the additional UE includes contention resolution for the additional UE. The DL transmission(s) for the additional UE is different from the DL transmission(s) 412.

[0088] In other embodiments, the CB-RNTI is determined as: CB-RNTI=1+t_id + 10*f_id + 60*(SFN_id mod (Wmax / 10)). (7)

[0089] In formula (7), t_id is an index of the first subframe of the CB PUSCH occasion (0≤ t_id <10), and f_id is an index of the CB PUSCH occasion in the frequency domain (0 ≤ f_id < 6, 6 being the maximum number of CB PUSCH occasions that can be configured in the frequency domain). If only a single CB PUSCH occasion is configured for the cell in the frequency domain, the term “10 × f_id” is omitted. Also in formula (7), System Frame Number identifier (SFN_id) is an index of a radio frame of the CB PUSCH occasion, and Wmax is 400, and is a maximum possible contention resolution window size in subframes.

[0090] When OCC(s) is / are configured as described above, the CB-RNTI may further be determined based on an OCC ID (occ_id) identifying an OCC. In this case, occ_id is considered in the formula for determining the CB-RNTI as exemplified below (with occ_id as described above): CB-RNTI = CB-RNTI=1+t_id + 10*f_id + 60*(SFN_id mod (Wmax / 10)) + 60 × 40 × occ_id. (8)

[0091] In yet other embodiments, the CB-RNTI is determined as: CB-RNTI=1 + floor(SFN_id / 4) + 256×carrier_id. (9)Patent Application Attorney Docket Number 0683-097-WO

[0092] In formula (9) SFN_id is an index of a radio frame of the CB PUSCH occasion, and “floor” is a function that returns a minimum value of its variable. Further, carrier_id is an index of a UL carrier associated with the CB PUSCH transmission. In some embodiments, a value range of the carrier_id depends on the maximum number of UL carriers that can be configured for the cell. If only a single UL carrier is configured for the cell, the term “256×carrier_id” is omitted.

[0093] When OCC(s) is / are configured as described above, the CB-RNTI may be further determined based on an OCC ID (occ_id) identifying an OCC. In this case, occ_id is considered in the formula for determining the CB-RNTI as exemplified below (with occ_id is as described above): CB-RNTI=1 + floor(SFN_id / 4) + 256×carrier_id + 256 × the maximum number of carriers × occ_id. (10)

[0094] In yet other embodiments, the CB-RNT is determined as: CB-RNTI = 1 + floor(SFN_id / 4) + 256×(H-SFN mod 2). (11)

[0095] In formula (11), SFN_id is an index of a radio frame of the CB PUSCH occasion. In the case of repetitions across multiple radio frames, the radio frame is the first radio frame of the multiple radio frames. Further, H-SFN is an index of a hyper frame of the CB PUSCH occasion. In the case of repetitions across multiple hyper frames, the radio frame is the first hyper frame of the multiple radio frames.

[0096] When OCC(s) is / are configured as described above, the CB-RNTI may be determined further based on an OCC ID (occ_id) identifying an OCC. In this case, occ_id is considered in the formula for determining the CB-RNTI as exemplified below (with the occ_id is as described above): CB-RNTI = 1 + floor(SFN_id / 4) + 256×(H-SFN mod 2) + 256×2×occ_id. (12)

[0097] In some alternative embodiments, the BS 104 transmits 412 the DL transmission(s) to the UE 102 without transmitting the DL assignment. In some embodiments, the BS 104 transmits 412 the DL transmission(s) on DL transmission resources that the UE 102 has known. In some embodiments, the DL transmission resources are configured in the CB preconfigured grant configuration. In other embodiments, the DL transmission resources are configured in a preconfigured DLPatent Application Attorney Docket Number 0683-097-WO assignment configuration that the BS 104 transmits to the UE 102, before event 406. In one embodiment, the BS 104 broadcasts the preconfigured DL assignment configuration in an SIB via the satellite 304 and / or the cell 124. In another embodiment, the BS 104 transmits a dedicated message including the preconfigured DL assignment configuration to the UE 102, before event 406.

[0098] In some embodiments, the first DL PDU is a first DL MAC PDU. In some embodiments, the BS 104 includes a first DL RRC message in the first DL MAC PDU. In some embodiments, the BS 104 includes a DL CCCH message (e.g., DL-CCCH- Message) in the first DL MAC PDU, where the DL CCCH message includes the first DL RRC message. In some embodiments, the first DL RRC message is an RRC connection setup message or an RRC setup message. In other embodiments, the first DL RRC message is an RRC connection resume message or an RRC resume message. In yet other embodiments, the first DL RRC message is an RRC early data complete message. In yet other embodiments, the first DL RRC message is an RRC connection reestablishment message or an RRC reestablishment message. In yet other embodiments, the first DL RRC message is an RRC connection release message or an RRC release message. In some embodiments, the BS 104 includes a UP data packet or an NAS PDU in the first DL PDU or the first DL RRC message. In other embodiments, the second DL PDU does not include a PDU. In some embodiments, the UE 102 transitions to the connected state from the idle or inactive state in response to receiving the first DL RRC message (e.g., the RRC connection setup message, the RRC setup message, the RRC connection resume message or the RRC resume message).

[0099] Because the periodic UL transmission resources are shared among UEs, other UE(s) may transmit UL transmission(s) on the same CB PUSCH occasion(s) as the UE 102. Therefore, the UL transmission(s) 408-1, …, 408-M are CB data transmission(s). In such cases, the BS 104 needs to resolve a potential contention between the UE 102 and other UE(s). After receiving the first UL PDU, the BS 104 generates contention resolution information for the UE 102 and includes the contention resolution information in the first DL PDU. In some embodiments, the base station 104 identifies the UE 102 based on the UE ID thereof included in the first UL PDU. When the UE 102 receives the contention resolution information and verifies the contention resolution informationPatent Application Attorney Docket Number 0683-097-WO addressed to the UE 102, the UE 102 determines that a contention resolution for transmission of the first UL PDU is successful (i.e., the UE 102 transmits the first UL PDU successfully). In some embodiments, the contention resolution information includes a portion of the first UL PDU (e.g., the first L bits of the first UL PDU). In other embodiments, the contention resolution information includes a portion of the UL CCCH message (e.g., the first L bits of the UL CCCH message). In one embodiment, L is 48. In another embodiment, L is larger than 48 and / or smaller than 73. In yet other embodiments, the contention resolution information includes the UE ID. In some embodiments, the contention resolution information is a MAC control element and the base station 104 includes, in the first DL PDU, a MAC subheader to indicate the contention resolution information.

[0100] In some embodiments, the BS 104 may include a second C-RNTI for the UE 102 in the first DL PDU. In some embodiments, the UE 102 and the BS 104 use the second C-RNTI for subsequent communications (i.e., events 414, 416, 418 and / or 420). Thus, the BS 104 may transmit 414 a DCI and a CRC of the DCI on a PDCCH to the UE 102. The BS 104 scrambles the CRC with the second C-RNTI. In some embodiments, the BS 104 scrambles the DCI with the second C-RNTI. The DCI includes a UL grant (i.e., a dynamic grant) to schedule one or more UL transmissions 416-1, …, 416-X, where X is an integer larger than zero. In the subsequent communication, the UE 102 monitors a PDCCH using the second C-RNTI. The UE 102 transmits 416 UL transmission(s) 416-1, …, 416-X of a second UL PDU in accordance with the UL grant. X may be one of 1, 2, 4, 8, 16, 32, 64, and / or 128. In some embodiments, the UL transmissions 416-2, …, 416-X are repetitions. In some embodiments, each of the UL transmission(s) is a HARQ transmission or a non-CB PUSCH transmission. In some embodiments, the UE 102 encodes the second UL PDU (i.e., a transport block including the second UL PDU) and a CRC of the first UL PDU into an encoded block and transmits the encoded block or a portion thereof in each of the UL transmission(s). In some embodiments, the UL grant includes a repetition number (i.e., X) and the UE 102 determines X in accordance with the included number. In some embodiments, if the UL grant does not include the repetition number, the UE 102 transmits 416 only one UL transmission (e.g., the UL transmission 416-1) to the BS 104.Patent Application Attorney Docket Number 0683-097-WO

[0101] In some embodiments, the BS 104 configures the same RV (e.g., RV 0) for each of the UL transmissions (i.e., repetitions) in the UL grant, and the UE 102 transmits the second UL PDU (e.g., the same portion of the encoded block) in each of the UL transmissions 416-1, …, 416-X using the same RV. For example, the UL grant includes a field / IE configuring an RV (e.g., RV 0) applied to the UL transmissions (i.e., repetitions). In such cases, the BS 104 receives and decodes each UL transmission using the same RV.

[0102] In other embodiments, the BS 104 configures different RVs for the UL transmissions in the UL grant, and the UE 102 transmits the different RVs of the second UL PDU in the UL transmissions 416-1, …, 416-X. In such cases, the BS 104 receives each of the UL transmissions and decodes each UL transmission using the corresponding RV. For example, the different RVs of the second UL PDU may be different portions of the encoded block. In one embodiment, some of the portions partially overlap. In another embodiment, the portions do not overlap. In some embodiments, the UL grant indicates an RV. The UE 102 and the BS 104 apply RVs to the UL transmissions 416-1, …, 416-X based on the indicated RV and Table 3. Table 3 RV indicated in RV to be applied to nthtransmission, where 1 ≤ n ≤ M

[0103] In the subsequent communication, the BS 104 may transmit 418 a DCI and a CRC of the DCI on a PDCCH to the UE 102. The BS 104 scrambles the CRC with the second C-RNTI. In some embodiments, the BS 104 scrambles the DCI with the second C-RNTI. The DCI includes a DL assignment to schedule one or more DL transmissions 420-1, …, 420-Y of a second DL PDU, where Y is an integer larger than zero. The BS 104 transmits the DL transmission(s) 420-1, …, 420-Y in accordance withPatent Application Attorney Docket Number 0683-097-WO the DL assignment. The UE 102 receives 420 the DL transmission(s) 420-1, …, 420-Y in accordance with the DL assignment. Y may be one of 1, 2, 4, 8, 16, 32, 64, and / or 128.

[0104] In some embodiments, the DL assignment configures DL time and frequency resources for the DL transmission(s) 420-1, …, 420-Y. The BS 104 transmits the DL transmission(s) 420-1, …, 420-Y on the DL time and frequency resources to the UE 102, and the UE 102 receives the DL transmission(s) 420-1, …, 420-Y on the DL time and frequency resources. The DL time resources include symbols within one or more slots or subframes. In some embodiments, the DL transmissions 420-2, …, 420-Y are repetitions. In some embodiments, each of the DL transmission(s) is a HARQ transmission or a PDSCH transmission. In some embodiments, the BS 104 encodes the second DL PDU (i.e., a transport block including the second DL PDU) and a CRC of the second DL PDU into an encoded block and transmits the encoded block or a portion thereof in each of the DL transmission(s). In some embodiments, the DL assignment includes a repetition number (i.e., Y). In such cases, the BS 104 transmits 420 the Y DL transmission(s) in accordance with the repetition number and the UE 102 may receive or attempt to receive 420 the Y DL transmission(s) in accordance with the repetition number. If the DL assignment does not include the repetition number, the BS 104 may transmit the second DL PDU in only one DL transmission (i.e., 420-1). If the DL assignment does not include a repetition number, the UE 102 may receive or attempt to only receive the DL transmission 420-1 in accordance with the DL assignment.

[0105] In some embodiments, the BS 104 configures the same RV (e.g., RV 0) for each of the DL transmission(s) in the DL assignment, and the BS 104 transmits the second DL PDU (e.g., the same portion of the encoded block) in each of the DL transmission(s) using the same RV. For example, the DL assignment includes a field / IE configuring a RV (e.g., RV 0) applied to the DL transmissions (i.e., repetitions). In such cases, the UE 102 receives and decodes each DL transmission using the same RV.

[0106] In other embodiments, the BS 104 configures the different RVs for the DL transmissions in the DL assignment and transmits the different RVs of the second DL PDU in the DL transmissions. In such cases, the UE 102 receives each of the DL transmissions and decodes each DL transmission using the corresponding RV. ForPatent Application Attorney Docket Number 0683-097-WO example, the different RVs of the second DL PDU may be different portions of the encoded block. In one embodiment, some of the portions partially overlap. In another embodiment, the portions do not overlap. In some embodiment, the BS 104 may configure different RVs for the DL transmissions 420-1, …, 420-Y in the DL assignment. For example, the DL assignment indicates an RV configuration (e.g., the third row, the fourth row, the fifth row or the sixth row in Table 1). The UE 102 and the BS 104 apply the RV configuration to the DL transmissions 420-1, …, 420-Y based on the indication and / or the Table 1. In other embodiments, the DL assignment indicates a (single) RV. The UE 102 and the BS 104 apply RVs to the DL transmissions 420-1, …, 420-Y based on the indicated RV and Table 2. In some embodiments, events 418 and 420 may occur before or during or after events 414 and 416.

[0107] In some embodiments, the second UL PDU is a second UL MAC PDU. In some embodiments, the UE 102 includes a second UL RRC message in the second UL MAC PDU. In some embodiments, the UE 102 includes a UL dedicated control channel (DCCH) message (e.g., UL-DCCH-Message) in the first UL MAC PDU where the UL DCCH message includes the second UL RRC message. In some embodiments, the second UL RRC message is an RRC connection setup complete message or an RRC setup complete message. In other embodiments, the second UL RRC message is an RRC connection resume complete message or an RRC resume complete message. In yet other embodiments, the second UL RRC message is an RRC connection reestablishment complete message or an RRC reestablishment complete message. In some embodiments, the UE 102 includes a UP data packet or an NAS PDU in the second UL PDU or the second UL RRC message. In some embodiments, the UE 102 may transmit one or more additional UL PDUs to the BS 104, similar to transmitting the second UL MAC PDU.

[0108] In some embodiments, the second DL PDU is a second DL MAC PDU. In some embodiments, the BS 104 includes a second DL RRC message in the second DL MAC PDU. In some embodiments, the BS 104 includes a DL DCCH message (e.g., DL- DCCH-Message) in the second DL MAC PDU, where the DL DCCH message includes the second DL RRC message. In some embodiments, the second DL RRC message is an RRC connection release message or an RRC release message to end or stop thePatent Application Attorney Docket Number 0683-097-WO data communication session or transition the UE 102 to the idle or inactive state. In some embodiments, the BS 104 includes a UP data packet or an NAS PDU in the second DL PDU or the second DL RRC message. The BS 104 may transmit one or more additional DL PDUs to the UE 102, similar to transmitting the second DL PDU. In such cases, after transmitting the second DL PDU and / or the additional DL PDU(s), the BS 104 may transmit a third DL PDU including an RRC connection release message or an RRC release message to the UE 102 to end or stop the data communication session or transition the UE 102 to the idle or inactive state. In some embodiments, the UE 102 ends or stops the data communication session or transitions to the idle or inactive state from the connected state, in response to receiving the second DL RRC message, the RRC connection release message or the RRC release message.

[0109] In other embodiments, after (e.g., in response to) receiving the first DL PDU or the first DL RRC message (e.g., the RRC early data complete message, the RRC connection release message, or the RRC release message), the UE 102 ends or stops the communication session with the BS 104 (i.e., there is no subsequent communication between the UE 102 and the BS 104). In such cases, the UE 102 may remain in the idle or inactive state.

[0110] After ending or stopping the communication session (e.g., a first communication session) with the BS 104, the UE 102 might initiate a second communication session with the BS 104 and performs communication with the BS 104, similar to events 406, 408, 410, 412, 414, 416, 418, and 420.

[0111] Contention resolution information for different UE may be multiplexed in an DL PDU. In some alternative embodiments, OCC(s) are not used for calculating the CB-RNTI in the case where OCC(s) is / are configured as described above. If the base station 104 receives CB PUSCH transmissions simultaneously from the UE 102 and the additional UE on the same CB PUSCH occasion with the first OCC and the second OCC respectively, the base station 104 uses a CB-RNTI (i.e., the same CB-RNTI) to send a DCI on a PDCCH to both the UE 102 and the additional UE. The UE 102 and the additional UE determine the same CB-RNTI (same as the CB-RNTI used by the base station 104) as described above. Thus, UE 102 and the additional UE receive the same DCI on the PDCCH using the same CB-RNTI. In some embodiments, the DCI is aPatent Application Attorney Docket Number 0683-097-WO DL assignment similar to event 410. For example, the CB PUSCH occasion is the CB PUSCH occasion where the UE 102 transmits the CB PUSCH transmission 408 and the DCI is the DL assignment 410. The base station 104 includes contention resolution information (i.e., first contention resolution information) for the UE 102 and second contention resolution information for the additional UE in the DL PDU 412. The UE 102 and the additional UE receive the DL PDU 412 in accordance with the DCI 410. The UE 102 and the additional UE retrieve the first contention resolution information and the second contention resolution information respectively from the DL PDU 412. In some embodiments, the base station 104 includes the first contention resolution information and the second contention resolution information in a MAC control element. In the DL PDU 412A, the base station 104 may include a MAC subheader indicating the MAC control element. The MAC subheader may include a logical channel ID. In the MAC control element or the MAC subheader, the base station 104 includes a first ID and a second ID indicating the first contention resolution information and the second contention resolution respectively. The UE 102 uses the first ID to identify the first contention resolution information in the DL PDU 412 and ignores or discards the second contention resolution information therein. Similarly, the additional UE uses the second ID to identify the second contention resolution information in the DL PDU 412 and ignores or discards the first contention resolution information therein. In one embodiment, the first ID and the second ID are associated with the first OCC and the second OCC, respectively. For example, the first ID and the second ID are a first occ_id and a second occ_id identifying the first OCC and the second OCC, respectively. In another example, the first ID and the second ID are derived based on the first OCC and the second OCC, respectively. For example, the first ID and the second ID are (the first occ_id – 1) and (the second occ_id – 1), respectively. In other embodiments, the base station 104 includes, in the DL PDU 412, a first MAC subheader and a second MAC subheader for the first contention resolution information and the second contention resolution information, respectively. In some embodiments, the base station 104 may include the first ID and the second ID in the first MAC subheader and the second MAC subheader respectively.Patent Application Attorney Docket Number 0683-097-WO

[0112] Next, the handling of the UL transmission timing for the UL transmission(s) 408 is discussed. In some embodiments, the UE 102 determines a timing adjustment (TA, e.g., TTA) and applies the TA to transmit the UL transmission(s) 1, …, M. In some embodiments, the UL transmission(s) starts TA time unit(s) (e.g., second(s)) before the start of a corresponding downlink radio frame at the UE. In some embodiments, the UE 102 determines a value of TA as a predetermined value or a default value. The predetermined value may be zero. For example, the value is 624TSor larger than 624TS(TSbeing a basic time unit). In some other embodiments, the UE 102 determines the TA using a formula as below. ^^TA ൌ ൫^^TA ^ ^^TA,offset ^ ^^common UETA,adj^^^TA,adj൯. (13)

[0113] In some embodiments, TSin the formula (13) is a time unit for LTE (e.g., as defined in 3GPP TS 36.211). In other embodiments, TSin the formula (13) is a time unit for NR (e.g., TSas defined in 3GPP TS 38.211). Further, NTAis a timing offset between uplink and downlink radio frames at the UE 102, and NTA,offsetis a fixed timing advance offset. In some embodiments, NTA,offset= 0. In other embodiments, NTA,offset= 624. In some embodiments, the UE 102 applies the NTA= 0 for frame structure type 1. In other embodiments, the UE 102 applies the NTA= 624 for frame structure type 2. In some embodiments, if the UE 102 receives common TA parameters from the BS 104 (e.g., as described below), the UE 102 derives the ^^commonTA,adjfrom the common TA parameters and an epoch time. Otherwise (i.e., if102 does not receive the common TA parameters), the UE 102 applies the ^^commoncommonTA,adj ൌ 0 or the ^^TA,adjis omitted in the formula (13). In some embodiments, thecommonthe ^^TA,adjfrom the common TA parameters and an one-way propagation delaywhich can be obtained as: ^^^^^^^^^^ୡ୭୫୫୭୬^^^^ ൌ^ ଶ ^^^commonTA ^ ^^commonDriftTA ൈ ൫^^ െ ^^^୮୭ୡ୦൯ ^ ^^commonDriftVariationTAൈ ൫^^ െ ^^ଶ ^୮୭ୡ୦൯^. (14)

[0114] In formula ,DriftVariatiTA, ,onare given by the common TA parameters (e.g., a network-controlled common TA value, a drift rate of the common TA, and a drift rate variation of the common TA respectively), and ^^^^^^^isPatent Application Attorney Docket Number 0683-097-WO an epoch time (e.g., epochTime). ^^^^^^^^^^ୡ୭୫୫୭୬^^^^ provides a distance at time ^^ between the satellite 304 and an uplink time synchronization reference point divided by the speed of light. The uplink time synchronization reference point is the point where DL and UL are frame aligned with an offset given by ^^^^,୭^^^^^.

[0115] In some embodiments, the UE 102 determines (e.g., computes) the ^^UETA,adj, based on a UE position (e.g., Global navigation satellite system (GNSS) position) of the UE 102 and ephemeris information for the satellite 304. In some embodiments, UE 102 determines these quantities to pre-compensate a two-way transmission delay on a service link between the UE 102 and the satellite 304. If the UE 102 does not receive ephemeris information for the satellite 304, the UE 102 applies ^^UETA,adj ൌ 0 or the ^^UETA,adjis omitted in the formula.

[0116] In some embodiments, the BS 104 broadcasts the ephemeris information and the common TA parameters, for example, in one or more SIBs (e.g., SIB19 or SIB31) for the satellite 304. UE 102 receives or acquires the ephemeris information and the common TA parameters before transmitting the first UL PDU. In some embodiments, the common TA parameters include a network-controlled common TA (i.e., value), a drift rate of the common TA, and / or a drift rate variation of the common TA. In some embodiments, the UE 102 is GNSS-capable and acquires a valid GNSS position as the UE position before transmitting the first UL PDU. Before performing transmission of the first UL PDU, the UE 102 determines a TA (e.g., TTA) based on the common TA parameters, the GNSS position, and satellite position and satellite velocity of the satellite 304 through the ephemeris information, as described above. The UE 102 applies the TA (e.g., TTA) to transmit the UL transmission(s) 408-1, …, 408-M.

[0117] In some embodiments, the BS 104 includes a TA command in the first DL PDU to adjust UL transmission timing for UL transmissions from the UE 102. In some embodiments, the TA command is a MAC control element. In some embodiments, the BS 104 determines (e.g., calculates, derives, computes, or estimates) an index value (TA) to adjust UL transmission timing, based on the UL transmission(s) 408-1, …, 408-M and includes the index value in the TA command. Upon receiving the TA command, the UE 102 adjusts UL transmission timing for subsequent UL transmissions (e.g., the ULPatent Application Attorney Docket Number 0683-097-WO transmission(s) 416-1, …, 416-X) based the index value. In some embodiments, UE 102 determines a new NTAbased on the index value and adjusts the UL transmission timing with the new NTA. In some embodiments, the UE 102 determines or updates the TA using the new NTAand the formula (13) to adjust the UL transmission timing.

[0118] In some embodiment, the BS 104 generates the TA command in a first format with a long index value instead of a second format with a short index value. In some embodiments, the first format is a P-bit TA command format, and the second format is a Q-bit TA command, where P > Q. In other words, the P-bit TA command format includes a P-bit index value (TA) and the Q-bit TA command format includes a Q- bit index value (TA). In one embodiment, P is an integer larger than 10 and Q is an integer smaller than 8. For example, P is 11 and Q is 6. In another example, P is 12 and Q is 6. In some embodiments, the UE 102 determines a new NTA= the index value ×16. In other embodiments, the UE 102 determines a new NTA= the index value ×16 × 64 / 2u, where µ is number which may be one of 0, 1, 2, 34, 5, and 6 corresponding to subcarrier spacing 15 KHz, 30 KHz, 60 KHz, 120 KHz, 240 KHz, 480 KHz, and 960 KHz, respectively.

[0119] In other embodiments, the BS 104 generates the TA command in the second format. Upon receiving the TA command with the second format, the UE 102 determines a new NTAbased on an old NTA. The old NTAis the previous NTAused by the UE 102 to determine the UL transmission timing. For example, the old NTA= 0 or 624, which is used to determine the TA for the UL transmissions(s) 408-1, …, 408-M. In some embodiments, the UE 102 determines a new NTA= an old NTA+ (the index value −31) × 16. In other embodiments, the UE 102 determines a new NTA= an old NTA+ (the index value −31) × 16 × 64 / 2u, where µ is a number as discussed above.

[0120] After transmitting the TA command (i.e., a first TA command), the BS 104 continuously measures UL transmissions (e.g., the UL transmission(s) 416-1, ..., 416-X) from the UE 102 to determine whether to adjust UL transmission timing for the UE 102. In some embodiments, the BS 104 determines to adjust UL transmission timing for the UE 102. The BS 104 transmits a second TA command to the UE 102, similar to transmitting the first TA command as described above. In some embodiments, the first TA command is the first format and the second TA command is the second format. InPatent Application Attorney Docket Number 0683-097-WO other embodiments, the first TA command and the second TA command are in the first format. In yet other embodiments, the first TA command and the second TA command are in the second format. Upon receiving the second TA command with the second format, UE 102 determines a new NTAand a new TA as described above.

[0121] In some embodiments, the UE computes the frequency Doppler shift between the UE 102 and the satellite 304 and pre-compensates for the frequency Doppler shift in the UL transmissions, by considering the position of the UE 102 and the ephemeris information for the satellite 304.

[0122] In some embodiments, the UE 102 continuously updates the TA and frequency Doppler shift pre-compensation. If the UE 102 does not have a valid GNSS position and / or valid ephemeris information for the satellite 304, the UE 102 does not communicate with the BS 104 until the UE 102 reacquires a valid GNSS position and / or ephemeris information.

[0123] FIG.4B illustrates a scenario 400B similar to the scenario 400A. Events 411 and 413 are similar to events 410 and 412. The differences between FIG.4B and FIG.4A are described below. In the scenario 400B, the UE 102 stores 405 a dedicate RNTI, before initiating a communication session with the BS 104 to transmit the first UL PDU, as described for FIG.4A. The BS 104 determines to transmit a first DL PDU to the UE 102 after (e.g., in response to) receiving the first UL PDU. To transmit the first DL PDU, the BS 104 may transmit 411 a downlink control information (DCI) and a CRC of the DCI on a PDCCH to the UE 102. In some embodiments, the BS 104 scrambles the CRC with the dedicated RNTI instead of the CB-RNTI in FIG.4A. In some embodiments, the BS 104 scrambles the DCI with the dedicated RNTI instead of the CB-RNTI described for FIG.4A. The DCI includes a DL assignment to schedule one or more DL transmissions of the first DL PDU to the UE 102 as described for event 412. In some embodiments, the BS 104 transmits 413 the first DL PDU to the UE 102, based on the DL assignment.

[0124] After transmitting the first UL PDU as described above, the UE 102 may monitor a PDCCH using the dedicated RNTI. While monitoring PDCCH with the dedicated RNTI, the UE 102 receives 411 the DCI and the CRC of the DCI on the PDCCH from the BS 104. UE 102 determines that the CRC is scrambled with thePatent Application Attorney Docket Number 0683-097-WO dedicated RNTI based on the dedicated RNTI and the DCI. The UE 102 receives 413 the first DL PDU from the BS 104 in accordance with the DL assignment, e.g., in response to determining the CRC is scrambled with the dedicated RNTI. The dedicated RNTI is an RNTI that the BS 104 uniquely assign for the UE 102. Thus, the BS 104 does not include contention resolution information in the first DL PDU. UE 102 determines the first PDU is transmitted successfully in response to receiving the CRC scrambled with the dedicated RNTI.

[0125] In some embodiments, the dedicated RNTI is the first C-RNTI described in FIG.4A. In other embodiments, the dedicated RNTI is not a C-RNTI. In some embodiments, the BS 104 includes the second C-RNTI in the first DL PDU as described for FIG.4A. In such cases, events 414, 416, 418, and 420 in FIG.4B are the same as events 414, 416, 418, and 420 in FIG.4A. In other embodiments, the BS 104 does not include a C-RNTI (e.g., the second C-RNTI) in the first DL PDU. In such cases, the BS 104 scrambles the CRC 414 and the CRC 418 with the first C-RNTI. UE 102 receives 414 the DCI and the CRC and receives 418 the DCI and the CRC, using the first C- RNTI. The descriptions for events 414, 416, 418, and 420 in FIG.4A can apply to FIG. 4B, where the second C-RNTI is replaced with the first C-RNTI.

[0126] FIG.4C illustrates a scenario 400C similar to the scenarios 400A and 400B. Events 411 and 413 are similar to events 410 and 412, respectively. The differences between FIG.4C and FIGs.4A and 4B are described below. In the scenario 400C, the BS 104 transmits 409 a DCI and a CRC of the DCI on a PDCCH to the UE 102 to resolve contention with other UE(s). The BS 104 includes the contention resolution information for the UE 102 in the DCI and scrambles the CRC with the CB- RNTI instead of the first DL PDU. In some embodiments, the DCI neither includes a DL assignment nor a UL grant. In other embodiments, the DCI transmitted at 409 and the DCI transmitted at 410 may be combined as a single DCI which includes the contention resolution information and the DL assignment scheduling DL transmission(s) 413-1, …, 413-M. In such cases, events 409 and 410 are combined as a single event.

[0127] Fig.5 is a frequency-time graph illustrating a CB preconfigured grant configuration for a cell. In this CB preconfigured grant configuration, a base station (e.g., the base station 104) configures a CB PUSCH occasion 1, 550, that occurs periodicallyPatent Application Attorney Docket Number 0683-097-WO with a periodicity T. In CB preconfigured grant configuration, the base station specifies (i.e., indicates or includes) a time location of the CB PSUCH occasion 1 in the time domain. The time location may be defined using a starting time point (e.g., a starting slot or subframe) and / or the number of (consecutive) time units (e.g., slots or subframes). The CB preconfigured grant configuration may include an offset defining the starting point relative to the start of the period. In some embodiments, the CB PUSCH occasion 1 includes P (consecutive) slots or subframes, where P is an integer larger than zero (e.g., P is one of 1, 2, …, 16, or P is an even number). In one embodiment, the CB preconfigured grant configuration specifies the number P or the number (P – 1).

[0128] Further, the base station also configures the frequency location of the CB PSUCH occasion 1, 550, in the frequency domain. The frequency location may be specified using a starting subcarrier or PRB and / or a bandwidth (e.g., one or more subcarriers or PRBs). In some embodiments, the bandwidth consists of S subcarriers, where S is an integer larger than zero (e.g., S is one of 1, 2, …, 12). The CB preconfigured grant configuration then specifies the number S or the number (S – 1). In other embodiments, the CB PUSCH occasion 1 includes U PRBs, where U is an integer larger than zero (e.g., U is one of 1, 2, …, 300). The CB preconfigured grant configuration then specifies the number U or the number (U – 1).

[0129] The base station 104 may configure one or more additional CB PUSCH occasions in the CB preconfigured grant configuration. None of the CB PUSCH occasion 1 and the additional CB PUSCH occasion(s) overlap with one another in frequency and time. The additional CB PUSCH occasion(s) may include the same slots or subframes as the CB PUSCH occasion 1. For example, as illustrated in Fig.5, a CB PUSCH occasion 2552 has the same time parameters (i.e., location within the period and periodicity) as CB PUSCH occasion 1. Thus, the CB PUSCH occasion 2 includes P (consecutive) slots or subframes.

[0130] The base station also specifies a frequency location of each of the additional CB PUSCH occasion(s) in the frequency domain. As in the case of the CB PUSCH occasion 1, this frequency location may include a starting subcarrier or PRB and / or a bandwidth (e.g., one or more subcarriers or PRBs). In some embodiments, the CB preconfigured grant configuration also specifies a guard band between twoPatent Application Attorney Docket Number 0683-097-WO consecutive CB PUSCH occasions (e.g., guard band 551 between the CB PUSCH occasion 1 and the CB PUSCH occasion 2). The bandwidth of the guard band may be one or more subcarriers or PRBs. The guard bands between pairs of consecutive CB PUSCH occasions may be the same or different.

[0131] In some embodiments, the additional CB PUSCH occasion(s) have the same bandwidth (e.g., the same number of subcarriers or PRBs) as the CB PUSCH occasion 1. In other embodiments, the CB preconfigured grant configuration specifies a total number of CB PUSCH occasions (i.e., the CB PUSCH occasion 1 and the additional CB PUSCH occasion(s)) in the frequency domain in each period. In yet other embodiments, the CB preconfigured grant configuration specifies a total number of the additional CB PUSCH occasion(s) in the frequency domain in each period. In some embodiments, the CB preconfigured grant configuration indicates a starting subcarrier or PRB for CB PUSCH occasion 1 and the number S or U. The base station and UE(s) determine a frequency location for each of the additional CB PUSCH occasion(s) based on the starting subcarrier or PRB, the number S or U, the total number of the (additional) CB PUSCH occasion(s), and / or the guard band(s).

[0132] Some or all of the additional CB PUSCH occasion(s) may include different number(s) of subcarriers or PRBs from the CB PUSCH occasion 1. In such cases, the CB preconfigured grant configuration specifies the number of subcarriers or PRBs for the CB PUSCH occasion(s) with different number(s) of subcarriers or PRBs. For example, the CB preconfigured grant configuration specifies the number of subcarriers or PRBs for the CB PUSCH occasion 2 in the same manner as described above for the CB PUSCH occasion 1. The base station and UE(s) determine a frequency location for each of the additional CB PUSCH occasion(s) based on the starting subcarrier or PRB, the number of subcarriers or PRBs for the each of the additional CB PUSCH occasion(s), and / or the guard band.

[0133] In some embodiments, the base station configures a first UE to transmit a non-CB PUSCH transmission on a non-CB PUSCH occasion 554, where the first UE is UL synchronized with the base station. The bandwidth of the non-CB PUSCH occasion 554 may be wider than, narrower than, or equal to the bandwidth of the CB PUSCH occasions 1 (labeled 550) and 2 (labeled 552). For example, the base station transmitsPatent Application Attorney Docket Number 0683-097-WO a DCI including a UL grant to the first UE, configuring the first UE to transmit the non- CB PUSCH transmission on a non-CB PUSCH occasion 554. The first UE transmits the non-CB PUSCH transmission on the non-CB PUSCH occasion in accordance with the DCI. In another example, the base station transmits an RRC message (e.g., an RRC reconfiguration message) to the first UE, including a configured grant configuration configuring the first UE to transmit the non-CB PUSCH transmission on the non-CB PUSCH occasion 554. The first UE transmits the non-CB PUSCH transmission on the non-CB PUSCH occasion in accordance with the configured grant configuration. The base station may also configure a guard time 556 between the CB PUSCH occasion(s) 1 and / or 2 and the non-CB PUSCH occasion 554. A second UE (other than the first UE) may transmit a CB PUSCH transmission on the CB PUSCH occasion 1 (550). Because the second UE is not UL synchronized with the base station on the cell, when the CB PUSCH transmission arrives at the base station, a portion of the CB PUSCH transmission may overlap the guard time. Because the non-CB PUSCH transmission does not overlap with guard time, the CB PUSCH transmission does not interfere with the non-CB PUSCH transmission. That is, by configuring the guard time, the base station ensures that a non-CB PUSCH transmission does not overlap with a CB PUSCH transmission. In some embodiments, a non-CB PUSCH transmission (e.g., the non-CB PUSCH transmission 554) following a CB PUSCH occasion (e.g., the CB PUSCH occasion 550) is shorter than the CB PUSCH occasion in the time domain. In other embodiments, the base station refrains from configuring a short non-CB PUSCH occasion / transmission (i.e., non-CB PUSCH occasion 554) shorter than a normal non- CB PUSCH occasion / transmission (e.g., non-CB PUSCH occasion 558). In such cases, the time period from the end of CB PUSCH occasion 550 to the end of the period T may be considered a guard time.

[0134] In some embodiments, the base station configures a third UE to transmit a non-CB PUSCH transmission on the non-CB PUSCH occasion 558. The non-CB PUSCH occasion / transmission 558 may include P slots. The non-CB PUSCH occasion / transmission 558 may last longer than the non-CB PUSCH transmission 554 and / or than the CB PUSCH occasion. The third UE and the first UE may the same UEPatent Application Attorney Docket Number 0683-097-WO or different UEs. Above-described features related to the non-CB PUSCH occasion 554 are pertinent for the non-CB PUSCH occasion 558.

[0135] In some embodiments, the CB preconfigured grant configuration includes an association configuration configuring an association between a Synchronization Signal / physical broadcast channel (PBCH) block (SSB) and a CB PUSCH occasion. The association configuration may configure multiple SSBs to be associated with a particular CB PUSCH occasion. For example, the association configuration associates SSBs 0…V with the CB PUSCH occasion 1, where V is an integer larger than zero. If the CB PUSCH occasion 2 is configured, the association configuration may associate the SSBs V+1, …, V+W with the CB PUSCH occasion 2, where W is an integer larger than zero. The association configuration may specify a one-to-one association between a particular SSB and a particular CB PUSCH occasion. In other words, the association configuration configures each of SSBs to be associated with a corresponding CB PUSCH occasion. For example, the association configuration configures SSB 0 to be associated with the CB PUSCH occasion 1 (550) and SSB 1 to be associated with the CB PUSCH occasion 2 (552). The association configuration may configure SSB 2 to be associated with the CB PUSCH occasion 1 (560) in the next period and SSB 3 to be associated with the CB PUSCH occasion 2 (562) in the next period. Alternatively, the association configuration configures SSB 0 to be associated with the CB PUSCH occasion 1560 and SSB 1 to be associated with the CB PUSCH occasion 2562. In yet other embodiments, the association configuration configures an SSB to be associated with multiple CB PUSCH occasions. For example, the association configuration configures SSB 0 to be associated with the CB PUSCH occasion 1 and the CB PUSCH occasion 2.

[0136] The base station transmits (e.g., broadcasts) the SSBs described above via the cell. The UE (e.g., the UE 102) may select a CB PUSCH occasion based on an associated SSB received by the UE and transmit a CB PUSCH transmission on the selected CB PUSCH occasion (e.g., event(s) 408-1, …, 408-M). In some embodiments, if a signal strength or quality of an SSB received by the UE is above a threshold, the UE selects a CB PUSCH occasion associated with the SSB. Otherwise (i.e., the signal strength or quality is below the threshold), the UE does not select the CB PUSCHPatent Application Attorney Docket Number 0683-097-WO occasion associated to the SSB. In some embodiments, the UE does not select a CB PUSCH occasion if the UE does not receive a SSB associated with the CB PUSCH occasion.

[0137] In some embodiments, the CB preconfigured grant configuration configures transport block sizes for the CB PUSCH occasions (e.g., the CB PUSCH occasion 1 and the additional CB PUSCH occasion(s)) in the frequency domain and / or in the time domain. For example, the CB preconfigured grant configuration specifies different numbers of subcarriers or PRBs and / or different modulation and coding schemes (MCSs) for the CB PUSCH occasions, which causes different transport block sizes. The UE may select a CB PUSCH occasion with a transport block size that can accommodate a volume of UL data to be transmitted by the UE. For example, the CB preconfigured grant configuration configures a transport block size 1 and a transport bock size 2 for the CB PUSCH occasion 1 and the CB PUSCH occasion 2, respectively. When the transport block size 1 is larger than the transport block size 2, if the UE has a UL data packet to transmit and the transport block size 2 can accommodate a size of the UL data packet but the transport block size 1 cannot, the UE selects the CB PUSCH occasion 2 to transmit the UL data packet. In another example, the CB preconfigured grant configuration configures a transport block size 1 and a transport bock size 2 for the CB PUSCH occasion 552 and the CB PUSCH occasion 562, respectively. When the transport block size 1 is larger than the transport block size 2, if the UE has a UL data packet to transmit and the transport block size 2 can accommodate a size of the UL data packet but the transport block size 1 cannot, the UE selects the CB PUSCH occasion 562 to transmit the UL data packet. The UE may select a CB PUSCH occasion based on a received SSB and a size of UL data to be transmitted as described above.

[0138] In some embodiments, the one or more CB PUSCH occasion(s) in each period are at different time locations within the period. In other embodiments, all the CB PUSCH occasion(s) are at the same time location in all periods.

[0139] Fig.6 is another frequency-time graph illustrating a CB preconfigured grant configuration for a cell, similar to Fig.5. The CB PUSCH occasion 1 labeled 650 and the CB PUSCH occasion 2 labeled 652 in Fig.6 last less than the CB PUSCHPatent Application Attorney Docket Number 0683-097-WO occasion 1 (550) and the CB PUSCH occasion 2 (552) in Fig.5. The duration of the CB PUSCH occasions in Fig.5 is one or multiple slots. The duration of the CB PUSCH occasions in Fig.6 may be shorter than a slot or not a multiple of slot duration. The base station configures a guard time 656 complementary to the shorter CB-PUSCH occasion duration and a non-CB PUSCH transmission 654 longer than the non-CB PUSCH occasion 554. In the scenario illustrated in Fig.6, the non-CB PUSCH transmission 654 lasts substantially the same as the non-CB PUSCH occasion 558 but has a different bandwidth. The non-CB PUSCH occasion / transmission 654 is longer than the CB PUSCH occasion (s) 650 and / or 652 in the time domain. Unless otherwise configured, the CB PUSCH occasions 660 and 662 as well as the guard time 666 repeat the frequency-time pattern described for the CB PUSCH occasions 650 and 652 with guard time 656.

[0140] Figs.7, 8A-C, and 9A-C are flowcharts of UE methods (i.e., methods performed by a UE, such as, the UE 102) related to the use of OCCs for CBDTs. Figs.10, 11A-D, and 12 are flowcharts of BS methods (i.e., methods performed by a BS such as BS 104 or a unit of a distributed BS) related to the power control for CBDTs. One or more of the features specified in the above descriptions of Figs.4A-4C, 5, and 6 may apply to these UE and BS methods. Each of these methods may be implemented using processing hardware (including a processor, a transceiver and a computer readable recording media) as illustrated for UE 102 and BS 104 in Fig.1.

[0141] Referring first to Fig.7, a method 700 is performed by a UE and includes determining an orthogonal cover code (OCC) for a CB PUSCH transmission and transmitting the CB PUSCH transmission with the OCC. The method 700 starts with the UE receiving 704, from a RAN (e.g., a BS such as 104), a contention-based preconfigured grant (CBPG) configuration and one or multiple OCC configurations that configure a CB PUSCH occasion and OCCs respectively. In some embodiments, the CBPG configuration includes the OCC configuration(s). The method 700 further includes initiating 707 transmission of UL data and selecting 722 an OCC from the multiple OCCs. The method 700 continues with the UE generating 724 a CB PUSCH transmission including the UL data, based on the CBPG configuration. The UE then applies the selected OCC to the CB PUSCH transmission. In some embodiments of applying the selected OCC, the UEPatent Application Attorney Docket Number 0683-097-WO applies the selected OCC to bits to obtain an encoded bit or symbol stream and transmits the encoded bit or symbol stream in the CB PUSCH transmission. The method 700 then includes transmitting 708 the CB PUSCH transmission using the selected OCC to the RAN on the CB PUSCH occasion, based on the CBPG configuration.

[0142] Fig.8A is a flow diagram of a method 800A similar to the method 700, except that the method 800A includes optional steps 809, 810A, and 812A. After performing the steps of method 700, the method 800A includes determining 809 a CB- RNTI, based on the CB PUSCH occasion and optionally the selected OCC, receiving 810A, from the RAN, a DL assignment and a CRC scrambled with the CB-RNTI on a PDCCH, and receiving 812A, from the RAN, a DL PDU including contention resolution information.

[0143] In some embodiments, the UE determines whether the contention resolution information is for the UE. If the UE determines that the contention resolution information is indeed for the UE, the UE determines that the contention resolution has been successful. If the determines that the contention resolution information is not for the UE, the UE discards or ignores the contention resolution information. If the contention resolution information is not for the UE and the DL PDU does not include other contention resolution information, the UE may determine that contention resolution has failed. If the contention resolution information is not for the UE and the DL PDU includes another contention resolution information and the other contention resolution information is for the UE, the UE determines that contention resolution is successful.

[0144] Fig.8B is a flow diagram of a method 800B similar to the method 800A, except that the method 800B includes optional steps 810B and 812B instead of steps 810A and 812A. After performing the steps of method 700 and determining 809 a CB- RNTI, based on the CB PUSCH occasion and / or the selected OCC, the method 800B includes receiving 810B, from the RAN, a DL assignment and a CRC scrambled with a dedicated RNTI (not the CB-RNTI as in step 810A) on the PDCCH. The method 800B further includes receiving 812B a DL PDU from the RAN (here the DL PDU does not include contention resolution as in 812A).

[0145] Fig.8C is a flow diagram of a method 800C similar to the method 800A, except that the method 800C includes optional steps 811 instead of steps 810A and 812A.Patent Application Attorney Docket Number 0683-097-WO After performing the steps of the method 700 and determining 809 the CB-RNTI, the method 800C includes receiving, from the RAN, contention resolution information and a CRC scrambled with the CB-RNTI on a PDCCH. In some embodiments, the UE receives a DCI including the contention resolution on the PDCCH and the CRC is a CRC of the DCI.

[0146] In some embodiments, the UE determines whether the contention resolution information is for the UE. If the UE determines that the contention resolution information is for the UE, the UE determines contention resolution has been successful. If the determines that the contention resolution information is not for the UE, the UE discards or ignores the contention resolution information. If the contention resolution information is not for the UE and the DCI does not include other contention resolution information, the UE may determine that contention resolution has failed. If the contention resolution information is not for the UE and the DCI includes other contention resolution information and the other contention resolution information is for the UE, the UE determines that contention resolution has been successful.

[0147] Referring next to Fig.9A, a method 900A is performed by a UE and includes determining whether to apply an OCC to a CB PUSCH transmission. The method 900A begins with the UE receiving 704 a CBPG configuration from a RAN followed by initiating 707 transmission of UL data. After generating 724 a CB PUSCH transmission including the UL data based on the CBPG configuration, the method 900A includes determining 926 whether the CBPG configuration includes an OCC configuration. If the CBPG configuration includes an OCC configuration (e.g., “Yes” branch of 926), the method continues with applying 928 an OCC to the CB PUSCH transmission in accordance with the OCC configuration and transmitting 708 the CB PUSCH transmission to the RAN on the CB PUSCH occasion based on the CBPG configuration as previously described. Otherwise (i.e., if the CBPG configuration does not include an OCC configuration, “No” branch of the 926), the method skips step 928 and continues with step 708. In other words, if the CBPG configuration does not include an OCC configuration, the UE does not apply an OCC to the CB PUSCH transmission.

[0148] Fig.9B is a flow diagram of a method 900B similar to the method 900A, except that the method 900B includes step 904 instead of step 704, and steps 930, 932,Patent Application Attorney Docket Number 0683-097-WO and 724 without step 928 as described below. The method 900B begins with the UE receiving 904 the CBPG configuration and a RACH configuration from the RAN. The method 900B continues with steps 707 and 926. If the CBPG configuration includes an OCC configuration (e.g., “Yes” branch of 726), the method 900B continues with the UE performing 930 a random access procedure with the RAN based on the RACH configuration. The UE performs the random access procedure because the UE does not support the OCC configuration. The method further includes transmitting 932 the UL data in the random access procedure. If the random access procedure is a four-step random access procedure, the UE transmits the UL data in a Message 3 of the four-step random access procedure. If the random access procedure is a two-step random access procedure, the UE transmits the UL data in a Message A of the two-step random access procedure. Otherwise, if the CBPG configuration does not include an OCC configuration (i.e., “No” branch of the 926), the method 900B continues with the previously described steps 724 and 708.

[0149] Fig.9C is a flow diagram of a method 900C similar to the methods 700A and 700B, except that the method 900C includes step 934 instead of 926. After steps 904 and 707 described above, the method 900C includes the UE determining 934 whether the UE supports the CBPG configuration. If the UE does not support the CBPG configuration (i.e., “No” branch of 934), the steps 930 and 932 as in the method 900B. Otherwise (i.e., if the UE supports the CBPG configuration, “Yes” branch of 934), the method 900C continues with steps 724 and 708. Examples and embodiments described for Figs.7A-C and 8 may apply to the methods 900A-C illustrated in Figs.9A-9C.

[0150] Thus, according to an embodiment, a wireless communication method (e.g., 700) performed by a UE (e.g., 102) includes (i) receiving (e.g., 704) a CBPG configuration of a cell and a OCC and (ii) transmitting (e.g., 708) a CB transmission including UL data, on a CB PUSCH occasion, based on the CBPG configuration, using the OCC. The UE may transmit the CB transmission without a random access preamble. This method may further include selecting the OCC from a plurality of OCCs provided via the CBPG configuration. Alternatively or additionally, the method may also include (a) receiving a DL assignment and a CRC scrambled with an RNTI, and (b) receiving a DL transmission responding to the CB transmission, according to the DL assignment, wherein the DLPatent Application Attorney Docket Number 0683-097-WO transmission does not include a random access response. In one embodiment, the RNTI is a CB-RNTI determined based on the CB PUSCH occasion and the OCC. In another embodiment, the RNTI is a dedicated RNTI, the method, in this case further including receiving the dedicated RNTI. Alternatively or additionally, the method may also include (c) determining a CB-radio network temporary identifier, CB-RNTI, based on the CB PUSCH occasion and optionally the OCC, and (d) receiving contention resolution information and a cyclic redundancy check, CRC, scrambled with the CB-RNTI on a PDCCH. The method may also include receiving a RACH configuration, and when the CBPG configuration does not include an OCC configuration, performing an RA procedure based on the RACH configuration to transmit the UL data.

[0151] Referring next to Fig.10, a method 1000 is performed by a base station (BS) to enable OCCs for CB PUSCH transmissions on a CB PUSCH occasion. The method 1000 begins with the BS transmitting 1004 a CBPG configuration and one or more multiple OCC configurations via a cell. Here, the CBPG configuration configures a CB PUSCH occasion, and the OCC configuration(s) configures OCCs 1, …, Z for the CB PUSCH occasion with Z>1 being an integer. The method 1000 then includes monitoring 1007 the CB PUSCH occasion for CB PUSCH transmissions on via the cell, based on the CB pre- configured grant configuration and the OCCs 1, …, Z. Further, the method 1000 includes the BS receiving 1008 CB PUSCH transmission(s) 1, …, J on the CB PUSCH occasion via the cell, based on the CBPG configuration and the OCC(s) 1, …, J. Here, J is an integer and 1 ≤ J ≤ Z. The method 1000 then includes the BS transmitting 1011 DL transmission 1, …, J via the cell in response to the CB PUSCH transmission(s) 1, …, J respectively (e.g., events 410A, 410B, 411, 412A and / or 412B). In some embodiments, the CB PUSCH transmission(s) 1, …, J include UL PDU(s) 1, …, J respectively.

[0152] Fig.11A is a flow diagram of a method 1100A similar to the method 1000, except that the method 1100A includes optional steps 1109A, 1110A, and 1112A. The method 1100A begins with performing steps 1004, 1007, 1008 and 1011 as in the method 1000. The method 1100A then includes determining 1109A CB-RNTI 1, …, J based on the CB PUSCH transmission(s) 1, …, J and the CB PUSCH occasion and optionally the OCC(s) 1, …, J, respectively. In some embodiments, the BS determines the CB-RNTI 1, …, J as described for Fig.4A. The method 1100A then includes the BS transmitting, viaPatent Application Attorney Docket Number 0683-097-WO the cell, 1110A DL assignment(s) 1, …, J and CRC 1, …, J scrambled with the CB-RNTI 1, …, J on PDCCH(s) respectively. Further, the method 1100B includes the BS transmitting 1112A, via the cell, DL PDU(s) 1, …, J including contention resolution information 1, …, J, respectively. In some embodiments, the BS transmits the DL PDU(s) 1, …, J or the contention resolution 1, …, J in response to the CB PUSCH transmission(s) 1, …, J or the UL PDU(s) 1, …, J, respectively. In some embodiments, the BS transmits the contention resolution 1, …, J to resolve contention for the CB PUSCH transmission(s) 1, …, J or the UL PDU(s) 1, …, J, respectively.

[0153] Fig.11B is a flow diagram of a method 1100B similar to the method 1100A, except that the method 1100B includes optional steps 1109B, 1110B, and 1112B instead of steps 1109A, 1110A, and 1112A of the method 1100A. After performing steps 1004, 1007, 1008, and 1011 as in the method 1000, the BS identifies 1109b dedicated RNTI 1, …, J based on the CB PUSCH transmission(s) 1, …, J respectively. In some embodiments, the BS identifies the dedicated RNTI 1, …, J as described for Fig.4B. At block 1110B, the BS transmits DL assignment(s) 1, …, J and CRC 1, …, J scrambled with the dedicated-RNTI 1, …, J on PDCCH(s) via the cell respectively. At block 1112B, the BS transmits, via the cell, DL PDU(s) 1, …, J, respectively.

[0154] Fig.11C is a flow diagram of a method 1100C similar to the method 1100A, except that the method 1100C includes step 1111 instead of steps 1110A and 1112A. Thus, the method 1100C includes the BS transmitting 1111, via the cell, contention resolution information 1, …, J and CRC 1, …, J scrambled with the CB-RNTI 1, …, J on PDCCH(s), respectively.

[0155] Fig.11D is a flow diagram of a method 1100D similar to the method 1000, except that the method 1100D includes optional steps 1109D, 1110D, and 1112D. After performing steps 1004, 1007, 1008, and 1011, the method 1100D may continue with the BS determining 1109D a single CB-RNTI based on the CB PUSCH occasion. The BS may determine the CB-RNTI as described for Fig.4A. The method 1100D then includes the BS transmitting 1110D a DL assignment and a CRC scrambled with the CB-RNTI on a PDCCH, via the cell, and then transmitting 1112D, via the cell, a DL PDU including contention resolution information 1, …, J.Patent Application Attorney Docket Number 0683-097-WO

[0156] Referring next to Fig.12, a method 1200 is performed by a BS to enable OCCs for CB PUSCH transmissions on a CB PUSCH occasion. The method 1200 begins with the BS transmitting 1204, via a cell, a CBPG configuration configuring a CB PUSCH occasion. The method 1200 then includes the BS determining 1240 whether the BS configures OCCs for the CB PUSCH occasion. If indeed the BS configures OCCs for the CB PUSCH occasion (i.e., “Yes” branch of block 1240), the method continues with monitoring 1207 the CB PUSCH occasion for CB PUSCH transmissions via the cell based on the CBPG configuration and the OCCs. Otherwise (if the BS does not configure OCCs for the CB PUSCH occasion, “No” branch of 1240), the method 1200 continues with the BS monitoring 1242 the CB PUSCH occasion for CB PUSCH transmissions via the cell, based on the CBPG configuration. Features described relative to the method 1000 in Fig. 10 apply for the method 1200 in Fig.12.

[0157] Thus, according to an embodiment, a wireless communication method (e.g., 1000) performed by a RAN node (e.g., 104) includes (i) transmitting in a cell, a CBPG configuration and an OCC and (ii) receiving a CB transmission including UL data without an RA preamble on a CB PUSCH occasion and using the OCC, based on the CBPB configuration. The OCC may be one of multiple OCCs provided for the CB PUSCH occasion in the CBPG configuration. The method may further include transmitting a DL assignment and a CRC scrambled with a RNTI transmitting a DL transmission in response to the CB transmission, the DL transmission not including a random access response. Additionally, the method may further include transmitting a DL assignment and a CRC scrambled with an RNTI, the transmitting of the DL transmission being performed according to the DL assignment. The RNTI may be a CB-RNTI determined based on the CB transmission, the CB PUSCH occasion and optionally the OCC. Alternatively, the RNTI is a dedicated RNTI identified based on the CB transmission. The DL transmission may include contention resolution information.

[0158] The description for any one of the above figures can apply to another of the above figures. Examples, embodiments, and methods described above may be combined, if there is no conflict. An event or block or step described above may be optional or omitted. For example, an event or block with dashed lines in the figures can be optional. In some embodiments, the term “message” is used and can be replaced byPatent Application Attorney Docket Number 0683-097-WO “information element (IE)”, and vice versa. In some embodiments, “IE” is used and can be replaced by “field”, and vice versa. In some embodiments, “configuration” can be replaced by “configurations” or “configuration parameters”, and vice versa. In some embodiments, the “longer timer value” and the “normal timer value” can be replaced by a first timer value and a second timer value respectively. In some embodiments, the “normal timer value” can be replaced by a “legacy timer value”. In some embodiments, the “function” can be replaced by a “feature”. The descriptions above may apply to communications without involving a satellite (i.e., 6G communications in a terrestrial network). In some embodiments, the “PUSCH” can be replaced by a “Narrowband PUSCH (NPUSCH)”. In some embodiments, the “PDCCH” can be replaced by “Machine Type Communication PDCCH (MPDCCH)” or “Narrowband PDCCH (NPDCCH)”. In some embodiments, the “orthogonal cover code” or “OCC” can be replaced by an “orthogonal code”.

[0159] A user equipment in which the techniques of this disclosure may be performed (e.g., the UE 102) can be any suitable device capable of wireless communications such as a smartphone, a tablet computer, a laptop computer, a mobile gaming console, a point-of-sale (POS) terminal, a health monitoring device, a drone, a camera, a media-streaming dongle or another personal media device, a wearable device such as a smartwatch, a wireless hotspot, a femtocell, or a broadband router. Further, the user device in some cases may be embedded in an electronic system such as the head unit of a vehicle or an advanced driver assistance system (ADAS). Still further, the user device can operate as an internet-of-things (IoT) device or a mobile- internet device (MID). Depending on the type, the user device can include one or more general-purpose processors, a computer-readable memory, a user interface, one or more network interfaces, one or more sensors, etc.

[0160] Certain embodiments are described as including logic or a number of components or modules. Modules may be software modules (e.g., code, or machine- readable instructions stored on non-transitory machine-readable medium) or hardware modules. A hardware module is a tangible unit capable of performing certain operations and may be configured or arranged in a certain manner. A hardware module may include dedicated circuitry or logic that is permanently configured (e.g., as a special-Patent Application Attorney Docket Number 0683-097-WO purpose processor, such as a field programmable gate array (FPGA) or an application- specific integrated circuit (ASIC), a digital signal processor (DSP), etc.) to perform certain operations. A hardware module may also include programmable logic or circuitry (e.g., as encompassed within a general-purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations. The decision to implement a hardware module in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software) may be driven by cost and time considerations.

[0161] When implemented in software, the techniques can be provided as part of the operating system, a library used by multiple applications, a particular software application, etc. The software can be executed by one or more general-purpose processors or one or more special-purpose processors.

[0162] Numerical adjectives “first”, “second”, and “third” do not imply any order (are not ordinals) but are markers to distinguish separate instances of similar elements. References to the singular (e.g., “a” or “an”, “the”) should include the plural unless clearly indicated otherwise.

[0163] As used herein, a phrase referring to “at least one of” or “one or more of” a list of items refers to any combination of those items, including single members. For example, “at least one of: a, b, or c” is intended to cover the possibilities of: a only, b only, c only, a combination of a and b, a combination of a and c, a combination of b and c, and a combination of a and b and c.

[0164] Although the features and elements of the present embodiments are described in the embodiments in particular combinations, each feature or element can be used alone without the other features and elements of the embodiments or in various combinations with or without other features and elements disclosed herein. The methods or flowcharts may be implemented in a computer program, software or firmware tangibly embodied in a computer-readable storage medium for execution by a specifically programmed computer or processor.

Claims

Patent Application Attorney Docket Number 0683-097-WO What is claimed is:

1. A wireless communication method (700) performed by a user equipment, UE, (102), the method comprising: receiving (904), from a radio access network, RAN, a contention-based preconfigured grant, CBPG, configuration and a random access channel, RACH, configuration; and when the UE supports the CBPG configuration (934), transmitting (708) a CB physical uplink shared channel, PUSCH, transmission including UL data according to the CBPG configuration, otherwise transmitting (932) the UL data in a random access procedure based on the RACH configuration.

2. The wireless communication method of claim 1, further comprising: receiving a timing advance command in response to the transmitting of the CB PUSCH transmission.

3. The wireless communication method of claims 1 or 2, further comprising: receiving an orthogonal cover code, OCC, wherein the UE uses the OCC for the CB PUSCH transmission.

4. The wireless communication method of claim 3, further comprising: selecting the OCC from a plurality of OCCs provided via the CBPG configuration.

5. The wireless communication method of any of claims 1 to 4, further comprising: receiving a downlink, DL, assignment and a cyclic redundancy check, CRC, scrambled with a radio network temporary identifier, RNTI; and receiving a DL transmission responding to the CB PUSCH transmission, according to the DL assignment, wherein the DL transmission does not include a random access response.Patent Application Attorney Docket Number 0683-097-WO 6. The wireless communication method of claim 5, wherein the RNTI is a CB- RNTI determined based on a CB PUSCH occasion used for the CB PUSCH transmission and optionally the OCC.

7. The wireless communication method of claim 5, wherein the RNTI is a dedicated RNTI, the method further comprising: receiving the dedicated RNTI.

8. The wireless communication method of any of claims 1 to 4, further comprising: determining a CB-radio network temporary identifier, CB-RNTI, based on a CB PUSCH occasion used for the CB PUSCH transmission and optionally the OCC; and receiving contention resolution information and a cyclic redundancy check, CRC, scrambled with the CB-RNTI on a physical downlink control channel, PDCCH.

9. A wireless communication method (1000) performed by a radio access network, RAN, node (104), the method comprising: transmitting (1004) in a cell, a contention-based preconfigured grant, CBPG, configuration; and in response to the transmitting, receiving (1008), from a user equipment, UE, (102), a contention-based, CB, transmission according to the CBPG configuration and including uplink, UL, data or a message of a random access procedure including the UL data.

10. The wireless communication method of claim 9, wherein the receiving includes receiving the CB transmission on a CB physical uplink shared channel, PUSCH, occasion, and the CB transmission uses an orthogonal cover code, OCC, included in the CBPG configuration.Patent Application Attorney Docket Number 0683-097-WO 11. The wireless communication method of claim 10, wherein the OCC is one of a plurality of OCCs provided for the CB PUSCH occasion in the CBPG configuration.

12. The wireless communication method of claim 9 or 10, the method further comprising: transmitting a downlink, DL, transmission in response to the CB transmission, the DL transmission including a timing advance command.

13. The wireless communication method of claim 12, further comprising: transmitting a DL assignment and a cyclic redundancy check, CRC, scrambled with a radio network temporary identifier, RNTI, wherein the transmitting of the DL transmission is performed according to the DL assignment.

14. The wireless communication method of claim 13, wherein the RNTI is a CB-RNTI determined based on the CB transmission, the CB PUSCH occasion, and, optionally also based on the OCC.

15. A wireless communication device (104, 102) comprising a transceiver (134, 136, 154, 156), a processor (132, 152) and computer-readable storage media (138, 158) storing executable instructions for the processor to perform any of the methods recited in claims 1-14, using the transceiver.

Images