System and method for data transmission in inactive state

Abstract

Control signaling mechanisms are provided to support transmission of data to or from a user equipment (UE) in an inactive state. In some embodiments, a UE in an inactive state receives a DCI including a cyclic redundancy check (CRC) scrambled by a radio network temporary identifier (RNTI) specific to a group of UEs, the group of UEs including the UE, and a resource allocation for a data transmission to the UE. The data transmission is then received on a physical shared channel. In other embodiments, a UE in an inactive state receives a DCI including a CRC scrambled by a paging RNTI and a resource allocation for a paging message to the UE. A data transmission is received by the UE in the paging message or in a further transmission scheduled by the paging message.

Description

[0001] This application claims priority to U.S. Patent Application No. 16 / 664,302, filed October 25, 2019, entitled “SYSTEMS AND METHODS FOR DATA TRANSMISSION IN AN INACTIVE STATE,” which is incorporated by reference herein. TECHNICAL FIELD

[0002] The present application relates generally to wireless communications, and in particular embodiments, to control signaling in wireless communication networks. BACKGROUND

[0003] In some wireless communication networks, a user equipment (UE) wirelessly communicates with a base station to transmit data to and / or receive data from the base station. The wireless communication from the UE to the base station is referred to as uplink (UL) communication. The wireless communication from the base station to the UE is referred to as downlink (DL) communication. The wireless communication from a first UE to a second UE is referred to as sidelink (SL) communication or device-to-device (D2D) communication.

[0004] In 3GPP new radio (NR), a UE can operate in one of the following three states: radio resource control (RRC) idle state (RRC_IDLE), RRC connected state (RRC_CONNECTED), and RRC inactive state (RRC_INACTIVE). In the RRC_CONNECTED state, the UE is connected to the network through a connection setup procedure. In the RRC_IDLE state, the UE is not connected to the network, but the network knows that the UE exists in the network. The RRC_IDLE state helps to save network resources and UE power (e.g., battery life) when the UE is not communicating with the network. The RRC_INACTIVE state also helps to save network resources and UE power when the UE is not communicating with the network. However, unlike the RRC_IDLE state, when the UE is in the RRC_INACTIVE state, at least some configuration information is stored by both the network and the UE so that the UE can more quickly reconnect to the network.

[0005] Traditionally, data transmission with a UE is limited when the UE is in the RRC_INACTIVE state. SUMMARY

[0006] The RRC_INACTIVE state is one example of an inactive state. Currently, there is no control signaling mechanism to support transmission of data to or from a UE in the RRC_INACTIVE state. Some embodiments of the present application provide a control signaling mechanism to support data transmission in the RRC_INACTIVE state, and more generally, in any inactive state.

[0007] According to an aspect of the present application, a method is provided, comprising: receiving, by a user equipment (UE) in an inactive state, a downlink control information (DCI); and receiving, by the UE in the inactive state, a data transmission on a physical shared channel. The DCI includes a cyclic redundancy check (CRC) scrambled by a radio network temporary identifier (RNTI) that is specific to a group of UEs, the group of UEs including the UE. The DCI also includes a resource assignment for the data transmission to the UE.

[0008] In some embodiments, the DCI further includes a short message.

[0009] In some embodiments, the DCI further includes an indication of a hybrid automatic repeat request (HARQ) process associated with the data transmission.

[0010] In some embodiments, the DCI further includes a measurement request.

[0011] In some embodiments, the RNTI is specific to the inactive state.

[0012] In some embodiments, the RNTI is specific to a UE, optionally based on another UE-specific identifier.

[0013] In some embodiments, the RNTI is a first RNTI, and the method further includes receiving, by the UE in the inactive state, another DCI including another CRC scrambled by a paging RNTI different from the first RNTI. The DCI and the other DCI are size-matched.

[0014] In some embodiments, the physical shared channel is a physical downlink shared channel or a physical sidelink shared channel.

[0015] In some embodiments, the resource allocation comprises at least one of: a frequency domain resource allocation, a time domain resource allocation, a virtual resource block to physical resource block mapping, a modulation and coding scheme, and a transport block scaling factor.

[0016] According to another aspect of the present application, a method is provided, comprising: receiving, by a UE in an inactive state, a DCI; receiving, by the UE in the inactive state, a data transmission on a physical shared channel according to a paging message. The DCI comprises a CRC scrambled by a paging RNTI (P-RNTI), and a resource allocation for transmitting the paging message to the UE.

[0017] In some embodiments, the method further comprises: receiving, by the UE in the inactive state, an indication in the DCI or the paging message that the data transmission is scheduled. Optionally, receiving the data transmission on the physical shared channel comprises: receiving the data transmission in the paging message on a paging physical downlink shared channel.

[0018] In some embodiments, the method further comprises: receiving, by the UE in the inactive state, a resource allocation for the data transmission in the paging message on a paging physical downlink shared channel.

[0019] In some embodiments, the physical shared channel is a physical downlink shared channel or a physical sidelink shared channel.

[0020] In some embodiments, the indication is a single bit of the DCI.

[0021] In some embodiments, the indication is in a short message indication field of the DCI.

[0022] In some embodiments, the indication is in a short message field of the DCI.

[0023] In some embodiments, the paging message comprises an indication of whether the data transmission is greater than a predetermined threshold.

[0024] According to another aspect of the present application, a UE is provided, comprising: a processor configured to configure a UE in an inactive state; a receiver configured to receive a DCI while the UE is in the inactive state, and receive a data transmission on a physical shared channel while the UE is in the inactive state. The DCI comprises a CRC scrambled by a RNTI specific to a group of UEs, the group of UEs comprising the UE. The DCI further comprises a resource allocation for the data transmission.

[0025] According to another aspect of the present application, a UE is provided, comprising: a processor configured to configure the UE in an inactive state; a receiver configured to receive a DCI when the UE is in the inactive state, and receive a data transmission on a physical shared channel according to a paging message when the UE is in the inactive state. The DCI comprises: a CRC scrambled by a P-RNTI, and a resource allocation for transmitting the paging message to the UE.

[0026] In some embodiments, the receiver is further configured to receive an indication of the data transmission being scheduled in the DCI or the paging message when the UE is in the inactive state. Optionally, the physical shared channel is a paging physical downlink shared channel, and the receiver is configured to receive the data transmission in the paging message on the paging physical downlink shared channel.

[0027] In some embodiments, the receiver is further configured to receive a resource allocation for the data transmission in the paging message on a paging physical downlink shared channel when the UE is in the inactive state.

[0028] In some embodiments, the physical shared channel is a physical downlink shared channel or a physical sidelink shared channel. BRIEF DESCRIPTION OF DRAWINGS

[0029] For a more complete understanding of the present embodiments and their advantages, reference is now made to the following description taken in conjunction with the accompanying drawings in which:

[0030] Figure 1 is a schematic diagram of a communication system in which embodiments of the present application can occur;

[0031] Figure 2A and Figure 2B are block diagrams of exemplary user equipment and base stations, respectively, provided in accordance with aspects of the present application;

[0032] Figure 3 is a block diagram of a radio manager for configuring a software configurable air interface, provided in accordance with an aspect of the present application;

[0033] Figures 4 to 6 is a signaling diagram between a base station and a UE in an inactive state, provided in accordance with aspects of the present application;

[0034] Figure 7A shows a first exemplary UE identity, which is a combination of a medium access control (MAC) identity and network resource information;

[0035] Figure 7B shows a second exemplary UE identity, which is a combination of a MAC identity and dormancy cycle group information;

[0036] Figure 8 is a signaling diagram between a base station and a UE in an inactive state provided by other aspects of the present application;

[0037] Figure 9 and Figure 10 is a flowchart of a method provided by aspects of the present application. DETAILED DESCRIPTION

[0038] For the purposes of illustration, specific example embodiments are explained below in detail by making reference to the drawings.

[0039] The embodiments set forth herein represent information sufficient to enable those skilled in the art to practice the claimed subject matter and illustrate the best modes of practicing the claimed subject matter. Upon being presented with the description, drawings, and claims, one of ordinary skill in the art will be able to utilize the disclosure to overcome any number of technical difficulties, and is not limited in implementation to any particular embodiment. It should be understood that the concepts and applications described herein can be employed in various ways, changing one or more conditions or events, without departing from the scope of the present application and the claims appended hereto.

[0040] Furthermore, it should be understood that any modules, components, or devices disclosed herein implementing instructions can include or otherwise have access to one or more non-transitory computer / processor readable storage media storing information, such as computer / processor readable instructions, data structures, program modules, and / or other data. A non-exhaustive list of examples of non-transitory computer / processor readable storage media includes magnetic tapes, magnetic disks, magnetic disks or other magnetic storage devices, compact discs (CD-ROMs), digital video discs (DVDs), Blu-ray discs, or other optical storage devices, volatile and non-volatile memories, random access memories (RAMs), read-only memories (ROMs), electrically erasable programmable read-only memories (EEPROMs), flash memories, or other memory technology, whether volatile or non-volatile, removable or non-removable. Any such non-transitory computer / processor storage media can be part of a device or accessible or connectable thereto. Computer / processor readable / executable instructions implementing the applications or modules described herein can be stored or otherwise held by such non-transitory computer / processor readable storage media. TM

[0041] Figure 1 , Figure 2A ,​Figure 2B and Figure 3 An example of a network and devices that can implement any or all of the aspects of the application is shown.

[0042] Figure 1 An example communication system 100 is shown. Generally, the system 100 is capable of enabling multiple wireless or wireline elements to communicate data and other content. The system 100 can have the goal of providing content (voice, data, video, text) through broadcast, narrowcast, user equipment to user equipment, etc. The system 100 can operate efficiently by sharing resources such as bandwidth.

[0043] In this example, the communication system 100 includes electronic devices (EDs) 110a-110c, radio access networks (RANs) 120a-120b, a core network 130, a public switched telephone network (PSTN) 140, the Internet 150, and other networks 160. While Figure 1 A certain number of these components or elements are shown, but any reasonable number of these components or elements can be included in the system 100.

[0044] The EDs 110a-110c are for operating in, communicating in, or both in the system 100. For example, the EDs 110a-110c are for transmitting, receiving, or both over a wireless communication channel. Each of the EDs 110a-110c represents any suitable end user device for wireless operation and can include (or can be referred to as) a user equipment (UE), a wireless transmit / receive unit (WTRU), a mobile station, a mobile user unit, a cellular phone, a station (STA), a machine type communication (MTC) device, a personal digital assistant (PDA), a smartphone, a notebook, a computer, a tablet, a wireless sensor, or a consumer electronic device.

[0045] In Figure 1In particular embodiments, the RAN 120a-120b includes base stations 170a-170b, respectively. Each base station 170a-170b is configured to wirelessly interface with one or more EDs 110a-110c to enable access to any of the other base stations 170a-170b, the core network 130, the PSTN 140, the Internet 150, and / or the other networks 160. By way of example, the base stations 170a-170b can comprise or be one or more base transceiver stations (BTSs), Node-Bs, evolved Node-Bs (eNode Bs), Home eNode Bs, gNode Bs, transmission and receive points (TRPs), site controllers, access points (APs), or wireless routers, among other possibilities. Alternatively or additionally, any of the EDs 110a-110c can be configured to connect, access, or communicate with any of the other base stations 170a-170b, the Internet 150, the core network 130, the PSTN 140, the other networks 160, or any combination of the above. The wireless system 100 can include a RAN, such as the RAN 120b, in which the corresponding base station 170b accesses the core network 130 through the Internet 150, as shown.

[0046] The EDs 110a-110c and the base stations 170a-170b are examples of communication devices that can be used to implement some or all of the functionality and / or embodiments described herein. In particular embodiments, the EDs 110a-110c and the base stations 170a-170b can be configured to communicate using one or more wireless communication technologies, such as, for example, Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA), Wideband CDMA (WCDMA), Long Term Evolution (LTE), Bluetooth, WiFi, or Zigbee, among other possibilities. Figure 1In the illustrated embodiment, base stations 170a form part of RAN 120a, which can include other base stations, one or more base station controllers (BSC), one or more radio network controllers (RNC), relay nodes, elements, and / or devices. Any of base stations 170a, 170b can be a standalone element, as illustrated, or can be distributed among multiple elements in the corresponding RAN, etc. Further, base stations 170b form part of RAN 120b, which can include other base stations, elements, and / or devices. Each base station 170a-170b transmits and / or receives wireless signals within a particular geographic area, sometimes referred to as a "cell" or "coverage area." The cell can be further divided into cell sectors, e.g., base stations 170a-170b can employ multiple transceivers operating on multiple frequencies with various directional or otherwise oriented antenna systems to facilitate communications with EDs 110a-110c. In some embodiments, base stations 170a-170b can be macro cells with a range of about a few meters to about 100s of meters. In some embodiments, base stations 170a-170b can be micro or femto cells with a range of about a few meters to about 100s of meters. In some embodiments, multiple transceivers can be used for each cell, e.g., using multiple-input multiple-output (MIMO) techniques for each cell. The number of RANs 120a-120b illustrated is merely exemplary. Any number of RANs can be considered when designing communication system 100.

[0047] Base stations 170a-170b communicate with one or more of EDs 110a-110c using wireless communication links over one or more air interfaces 190. The air interfaces 190 can utilize any suitable wireless communication techniques. For example, communication system 100 can implement one or more channel access methods including orthogonal or non-orthogonal channel access methods, e.g., code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or single-carrier FDMA (SC-FDMA).

[0048] The base stations 170a-170b can implement a universal mobile telecommunications system (UMTS) universal terrestrial radio access (UTRA) to establish the air interface 190 using wideband CDMA (WCDMA). When doing so, the base stations 170a-170b can implement protocols such as high speed packet access (HSPA), evolved HSPA (HSPA+), optionally including high speed downlink packet access (HSDPA), high speed packet uplink access (HSUPA), or both. Alternatively, the base stations 170a-170b can implement LTE, LTE-A, LTE-B, and / or 5G new radio (NR) using evolved UMTS terrestrial radio access (E-UTRA) to establish the air interface 190. It is contemplated that the communication system 100 can use multiple access technologies including schemes such as those described above. Other wireless technologies can be used to implement the air interface including IEEE 802.11, 802.15, 802.16, CDMA2000, CDMA2000 IX, CDMA2000 EV-DO, IS-2000, IS-95, IS-856, GSM, EDGE, and GERAN. Of course, other multiple access schemes and wireless protocols can be utilized.

[0049] The RANs 120a-120b are in communication with the core network 130 to provide the EDs 110a-110c with access to various services, such as voice, data, and other services. The RANs 120a-120b and / or the core network 130 can be in direct or indirect communication with one or more other RANs (not shown) that can or can not be serviced by the core network 130 and that can or can not utilize the same radio access technology as the RANs 120a, 120b, or both. The core network 130 can also serve as a gateway for the RANs 120a-120b and / or EDs 110a-110c to access other networks (such as PSTN 140, the Internet 150, and the other networks 160).

[0050] The EDs 110a-110c communicate using wireless communication links (e.g., radio frequency (RF), microwave, infrared (IR), and so on) over one or more SL air interfaces 180 with one or more other EDs. The SL air interface 180 can utilize any suitable wireless access technology and can be substantially similar to the air interface 190 by which the EDs 110a-110c communicate with one or more of the base stations 170a-170c, or they can be significantly different. For example, the communication system 100 can implement one or more channel access methods in the SL air interface 180 such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or single-carrier FDMA (SC-FDMA). In some embodiments, the SL air interface 180 can be implemented at least in part over an unlicensed spectrum.

[0051] In this application, SL transmissions between cooperating UEs can be “grant-free” transmissions, or a mode of data transmission that is performed without the need for a transmission grant. Grant-free transmissions are sometimes referred to as “configured grant,” “grant-less,” “grant-free,” or “grant-less” transmissions. For example, grant-free SL transmissions can also be referred to as SL “grant-less transmissions,” “grant-less dynamic grant transmissions,” “grant-less dynamic scheduling transmissions,” or “transmissions using configured grants.”

[0052] Configured grant transmissions generally require that the receiver knows the parameters and resources used by the transmitter for the transmission. However, for SL transmissions, the receiving UE generally does not know the configuration parameters of the transmitting UE, such as which UE is transmitting, the ultimate target of the data (e.g., another UE), the time and frequency domain communication resources used for the transmission, and other control information. However, various approaches incur respective overhead penalties.

[0053] Additionally, some or all of the EDs 110a-110c can include functionality for communicating with different wireless networks over different wireless links using different wireless technologies and / or protocols. In place of (or in addition to) wireless communication, the EDs can communicate with a service provider or switch (not shown) and the Internet 150 over wired communication channels. The PSTN 140 can include a circuit- switched telephone network for providing plain old telephone service (POTS). The Internet 150 can include a network of computers and subnets (intranets) or both, and incorporates protocols such as Internet Protocol (IP), transmission control protocol (TCP), and user datagram protocol (UDP). The EDs 110a-110c can be multi-mode devices capable of operating according to multiple wireless access technologies, and include multiple transceivers needed to support multiple wireless access technologies.

[0054] Figure 2A and Figure 2B An example device that can implement the methods and teachings provided herein is shown. In particular, Figure 2A An example ED 110 is shown, Figure 2B An example base station 170 is shown. These components can be used in the system 100 or any other suitable system.

[0055] As Figure 2A shown, the ED 110 includes at least one processor or processing unit 200. The processing unit 200 implements various processing operations of the ED 110. For example, the processing unit 200 can perform signal coding, bit processing, data processing, power control, input / output processing, or any other functionality enabling the ED 110 to operate in the communication system 100. The processing unit 200 can also be used to implement some or all of the functionality and / or embodiments detailed herein. Each processing unit 200 includes any suitable processing or computing device configured to perform one or more operations. Each processing unit 200 may, for example, include a microprocessor, microcontroller, digital signal processor, field programmable gate array, or application specific integrated circuit.

[0056] The ED 110 also includes at least one transceiver 202. The transceiver 202 is used to modulate data or other content for transmission by at least one antenna or network interface controller (NIC) 204. The transceiver 202 is also used to demodulate data or other content received by the at least one antenna 204. Each transceiver 202 includes any suitable structure for generating signals for wireless or wired transmission, and / or for processing signals received wirelessly or by wire. Each antenna 204 includes any suitable structure for transmitting and / or receiving wireless or wired signals. One or multiple transceivers 202 can be used in the ED 110. One or multiple antennas 204 can be used in the ED 110. Although the transceiver 202 is shown as a single functional unit, it can also be implemented using at least one transmitter and at least one separate receiver.

[0057] The ED 110 also includes one or more input / output devices 206 or interfaces (e.g., wired interfaces to the Internet 150). The input / output devices 206 can interact with users or other devices in the network. Each input / output device 206 includes any suitable structure for providing information to or receiving information from a user, such as a speaker, microphone, keypad, keyboard, display, or touch screen, including network interface communications.

[0058] Furthermore, the ED 110 includes at least one memory 208. The memory 208 stores instructions and data used, generated, or collected by the ED 110. For example, the memory 208 could store software

[0059] As Figure 2BAs shown, the base station 170 includes at least one processing unit 250, at least one transmitter 252, at least one receiver 254, one or more antennas 256, at least one memory 258, and one or more input / output devices or interfaces 266. A transceiver, not shown, can be used instead of the transmitter 252 and receiver 254. A scheduler 253 can be coupled with the processing unit 250. The scheduler 253 can be included within the base station 170 or can operate separately from the base station 170. The processing unit 250 implements various processing operations of the base station 170, such as signal coding, bit

[0060] Each transmitter 252 includes any suitable structure for generating signals for wireless or wired transmission to one or more EDs or other devices. Each receiver 254 includes any suitable structure for processing signals received wirelessly or wired from one or more EDs or other devices. Although at least one transmitter 252 and at least one receiver 254 are shown separately, they can be combined into a transceiver. Each antenna 256 includes any suitable structure for sending and / or receiving wireless or wired signals. Although a common antenna 256 is shown coupled with both the transmitter 252 and the receiver 254, one or more antennas 256 can be coupled with one or more transmitters 252, and one or more separate antennas 256 can be coupled with one or more receivers 254. Each memory 258 includes any suitable volatile and / or non-volatile storage and retrieval devices, such as those described above in connection with the ED 110. The memory 258 stores instructions and data used, generated, or collected by the base station 170. For example, the memory 258 could store software

[0061] Each input / output device 266 can interact with a user or other devices in the network. Each input / output device 266 includes any suitable structure for providing information to or from a user, including network interface communications.

[0062] Further details regarding the UE 110 and the base station 170 are known to those of skill in the art. Accordingly, for the sake of brevity, these details are omitted here.

[0063] Figure 3 A diagram illustrating a radio manager 300 for configuring a software-configurable air interface 190 is shown. For example, the radio manager 300 can be a module that includes a plurality of components or building blocks that define parameters of the air interface 190 and collectively specify how to transmit and / or receive transmissions over the air interface 190. Additionally or alternatively, the radio manager 300 can define parameters of the SL air interface 180 and specify how to transmit and / or receive transmissions over the SL air interface 180.

[0064] The components of the radio manager 300 include at least one of a waveform component 305, a frame structure component 310, a multiple access scheme component 315, a protocol component 320, and a modulation and coding component 325.

[0065] The waveform component 305 can specify the shape and form of the transmitted signal. Waveform options can include orthogonal multiple access waveforms and non-orthogonal multiple access waveforms. Non-limiting examples of such waveform options include single-carrier (SC), ultra wideband (UWB), frequency modulated continuous wave (FMCW), linear frequency modulated (LFM), orthogonal frequency division multiplexing (OFDM), single-carrier frequency division multiple access (SC-FDMA), filtered OFDM (f-OFDM), time windowed OFDM, filter bank multicarrier (FBMC), universal filtered multicarrier (UFMC), generalized frequency division multiplexing (GFDM), wavelet packet modulation (WPM), faster than Nyquist (FTN) waveforms, and peak to average power ratio waveform (PAPR WF). In some embodiments, a combination of waveform options can be employed. LFM-OFDM waveforms are a non-limiting example of such a combination.

[0066] The frame structure component 310 can specify the configuration of a frame or frame group. The frame structure component 310 can indicate one or more of the time, frequency, pilot signature, code, or other parameters of a frame or frame group.

[0067] Non-limiting examples of frame structure options include the number of symbols in a slot, the number of slots in a frame, and the duration of each slot (sometimes referred to as a transmission time interval (TTI) or transmission time unit (TTU)). The frame structure component can also specify whether the slots are configurable multi-level TTIs, fixed TTIs, or configurable single-level TTIs. The frame structure component can also specify coexistence mechanisms for different frame structure configurations.

[0068] For certain waveforms, such as certain OFDM-based waveforms, the frame structure component can also specify one or more associated waveform parameters, such as subcarrier spacing width, symbol duration, cyclic prefix (CP) length, channel bandwidth, guard band / subcarriers, and sample size and frequency.

[0069] In addition, the frame structure component 310 can also specify whether the frame structure is for time division duplex communications or for frequency division duplex communications.

[0070] In addition, the frame structure component 310 can also specify a transmission state and / or direction for each symbol in a frame. For example, each symbol can be independently configured as a downlink symbol, an uplink symbol, or a flexible symbol.

[0071] The specifications of the waveform component and the frame structure component are sometimes collectively referred to as the “numerology.” Thus, the air interface 190 can include a numerology component 330 that defines a plurality of air interface configuration parameters, such as subcarrier spacing, CP length, symbol length, slot length, and symbols per slot.

[0072] These numerologies, also referred to as subcarrier spacing configurations, can be scalable in the sense that the subcarrier spacing of different numerologies are multiples of each other, as are the slot lengths of different numerologies. This scalable design between multiple numerologies provides implementation benefits, such as a scalable total OFDM symbol duration in a time division duplex (TDD) context.

[0073] A frame can be configured using one scalable numerology or a combination of scalable numerologies. For example, a numerology with a 60 kHz subcarrier spacing has a relatively short OFDM symbol duration (as OFDM symbol duration varies inversely with subcarrier spacing), which makes the 60 kHz numerology particularly suitable for ultra-low latency communications, such as vehicle-to-any (V2X) communications. Another example of a numerology with a relatively short OFDM symbol duration suitable for low latency communications is a numerology with a 30 kHz subcarrier spacing. A numerology with a 15 kHz subcarrier spacing can be compatible with LTE. A numerology with a 15 kHz subcarrier spacing can serve as a default numerology for devices initially accessing the network. Such a 15 kHz numerology can also be suitable for wideband services. A numerology with a 7.5 kHz spacing has a relatively long OFDM symbol duration and can be particularly useful for coverage enhancement and broadcast. Additional uses of these numerologies will be apparent or become apparent to those of ordinary skill in the art. Among the four numerologies listed, the numerologies with 30 kHz and 60 kHz subcarrier spacing are more robust to Doppler spreading (fast moving conditions) due to the wider subcarrier spacing. It is also contemplated that different numerologies can use different values for other physical layer parameters, such as the same subcarrier spacing and different cyclic prefix lengths. Furthermore, the subcarrier spacing can depend on the operating frequency band. For example, the subcarrier spacing in millimeter wave frequencies can be higher than the subcarrier spacing in low frequencies.

[0074] It is also contemplated that other subcarrier spacings can be used, such as higher or lower subcarrier spacings. For example, a 2 n Other subcarrier spacings that vary by a factor of two include 120 kHz and 3.75 kHz.

[0075] In other examples, a more limited scalability can be implemented, in which two or more numerologies have a subcarrier spacing that is an integer multiple of the smallest subcarrier spacing, without necessarily being related by a factor of two n Examples include 15 kHz, 30 kHz, 45 kHz, 60 kHz subcarrier spacings.

[0076] In yet other examples, non-scalable subcarrier spacings can be used, which are not all integer multiples of the smallest subcarrier spacing, such as 15 kHz, 20 kHz, 30 kHz, 60 kHz.

[0077] An OFDM-based signal can be used to transmit multiple numerology coexisting signals. More specifically, multiple subband OFDM signals can be generated in parallel, each in a different subband, each with a different subcarrier spacing (more generally, with different numerologies). The multiple subband signals are combined into a single signal for transmission, e.g., for downlink transmission. Alternatively, the multiple subband signals can be transmitted from different transmitters, e.g., for uplink transmission from multiple electronic devices (EDs), which can be user equipment (UEs).

[0078] Using different numerologies can enable the air interface 190 to support coexistence of different sets of use cases with various quality of service (QoS) requirements, e.g., different levels of latency or reliability tolerance, as well as different bandwidth or signaling overhead requirements. In one example, a base station can signal to an ED an index representing a selected numerology or a single parameter (e.g., subcarrier spacing) of a selected numerology. Based on the signaling, the ED can determine the parameters of the selected numerology from other information, e.g., a lookup table of candidate numerologies stored in memory.

[0079] Continuing the discussion of the components of the air interface 190, the multiple access scheme component 315 can specify how access to a channel is granted to one or more EDs. Non-limiting examples of multiple access technology options include techniques that define how EDs share a common physical channel, e.g., time division multiple access (TDMA), frequency division multiple access (FDMA), code division multiple access (CDMA), space division multiple access (SDMA), single carrier frequency division multiple access (SC-FDMA), low density signature multicarrier code division multiple access (LDS-MC-CDMA), non-orthogonal multiple access (NOMA), pattern division multiple access (PDMA), lattice partition multiple access (LPMA), resource spread multiple access (RSMA), and sparse code multiple access (SCMA). Any of these multiple access technology options can be implemented using one or more of the following: scheduled access; unscheduled access, also referred to as grant-free access or configured grant access; non-orthogonal multiple access; orthogonal multiple access, e.g., through dedicated channel resources (i.e., not shared among multiple EDs); contention-based shared channel resources; non-contention-based shared channel resources; and sensing radio-based access.

[0080] The protocol component 320 can specify how transmissions and / or retransmissions are conducted. Non-limiting examples of transmission and / or retransmission mechanism options include those that specify scheduled data pipe sizes and signaling mechanisms for transmissions and / or retransmissions.

[0081] The modulation and coding component 325 can specify how to encode / decode and modulate / demodulate the information being transmitted for transmission / reception purposes. Coding can refer to methods of error detection and forward error correction. Non-limiting examples of coding options include turbo block codes, turbo product codes, fountain codes, low-density parity-check codes, and polar codes. Modulation can simply refer to quadrature amplitude modulation (QAM) specified by a complex constellation system (e.g., including modulation techniques and orders such as 16QAM, 64QAM, etc.), or more specifically, to various types of advanced modulation methods such as hierarchical modulation, multi-dimensional modulation, and low peak-to-average power ratio (PAPR) modulation.

[0082] Because the air interface includes multiple components or building blocks, and each component can have multiple candidate technologies (also referred to herein as air interface capability options), the air interface manager 300 can configure and store a large number of different air interface profiles. Each air interface profile defines a respective set of air interface capability options.

[0083] For example, in each air interface profile defining a respective set of air interface capability options, an air interface capability option is selected for each component building block of the air interface. Each of the different air interface profiles can be used to satisfy a different set of transmission requirements, including transmission content, transmission conditions, and reception conditions.

[0084] According to the transmission requirements of a pair of communication transmitting-receiving devices, one of the different air interface profiles that best satisfies the transmission requirements can be selected from the air interface manager 300 for use in communication between the pair of communication transmitting-receiving devices.

[0085] In other embodiments, the air interface manager 300 can modify or update its components, profiles, or capability options. For example, the air interface manager 300 can replace the waveform and frame structure components 305, 310 with a single parameter configuration component 330. Conversely, the air interface manager 300 can separate the modulation and coding component 325 into a separate coding component and a separate modulation component. Further, the air interface manager 300 is configurable such that new soft air interface configuration components developed in the future should be able to be utilized.

[0086] The air interface manager 300 can also update certain components to modify the capability options of any given component. For example, the air interface manager 300 can update the modulation and coding component 325 to include higher order modulation schemes.

[0087] By updating the stored components, configuration files, and candidate options, the air interface manager 300 can flexibly adjust to better accommodate different wireless traffic types and services. Modifying or updating the components, configuration files, and candidate options can enable the air interface manager 300 to provide suitable air interface profiles for traffic types or services other than those already anticipated for ultra-reliable low latency communications (URLLC), enhanced mobile broadband (eMBB), and massive machine-type communications (mMTC).

[0088] As mentioned above, in 3GPP new radio (NR), a UE can operate in one of the following three states: RRC_IDLE, RRC_CONNECTED, and RRC_INACTIVE.

[0089] The RRC_CONNECTED state is a non-limiting example of a connected or active state. A UE in the RRC_CONNECTED state is connected to a radio access network (RAN) and a core network (CN). For example, a UE can enter the RRC_CONNECTED state from the RRC_IDLE state after a connection setup procedure or from the RRC_INACTIVE state after a connection resume procedure. The RRC_CONNECTED state can be characterized as including the following features:

[0090] • The UE stores access stratum (AS) context;

[0091] • Transmission of unicast data with the UE is supported;

[0092] • At a lower layer, the UE can be configured with a UE-specific discontinuous reception (DRX);

[0093] • For UEs that support carrier aggregation (CA), the use of one or more secondary cells (SCells) is supported, aggregated with a special cell (SpCell) to increase bandwidth;

[0094] • For UEs supporting dual connectivity (DC), support using a secondary cell group (SCG) aggregated with a master cell group (MCG) to increase bandwidth;

[0095] • Support network-controlled mobility within NR networks and to / from E-UTRA networks;

[0096] • If configured, the UE monitors for short messages sent using a paging radio network temporary identifier (P-RNTI) via downlink control information (DCI);

[0097] • The UE monitors a control channel associated with a shared data channel to determine if data is scheduled for the UE;

[0098] • The UE provides channel quality and feedback information to the network;

[0099] • The UE performs neighbor cell measurements and measurement reporting;

[0100] • The UE acquires system information.

[0101] RRC_IDLE state is a non-limiting example of an idle state or a disconnected state. A UE in RRC_IDLE state has no connection to the RAN or the CN, and the UE can need to perform an initial access procedure to establish a connection with the network and transition to RRC_CONNECTED state. RRC_IDLE state can be characterized as including the following features:

[0102] • UE-specific DRX can be configured by upper layers of the network;

[0103] • UE-controlled mobility is based on network configuration;

[0104] • The UE monitors for short messages sent using a P-RNTI via DCI;

[0105] • The UE monitors a paging channel for CN paging using a 5G system architecture evolution temporary mobile station identifier (5G-S-TMSI);

[0106] • The UE performs neighbor cell measurements and cell selection or cell reselection;

[0107] • If configured, the UE acquires system information (SI) and can send an SI request.

[0108] The RRC_INACTIVE state is a non-limiting example of an inactive state. A UE in an inactive state uses less network resources and / or power than a UE in a connected state. This can save battery life of the UE. When the UE transitions to an inactive state, configuration information of the UE is stored by the UE and the network. This enables the UE to return to a connected state relatively quickly and efficiently. For example, the signaling used by the UE to transition from an inactive state to a connected state can be less than the signaling used to transition from an idle state to a connected state.

[0109] The RRC_INACTIVE state can be considered to be between the RRC_CONNECTED state and the RRC_IDLE state. In the RRC_INACTIVE state, both the UE and the network store at least part of the UE’s AS context, which enables the network to communicate with the UE. As a result, secure and fast signaling can occur between the network and the UE. Furthermore, a UE in the RRC_IDLE state can only support CN paging performed in a tracking area in which the UE is located. In contrast, a UE in the RRC_INACTIVE state can support RAN paging performed in a RAN notification area (RNA) in which the UE is located in addition to CN paging. Since an RNA typically covers a smaller number of cells than a tracking area, RAN paging of a UE in the RRC_INACTIVE state can result in less DL resource consumption and / or overhead. The RRC_INACTIVE state can be characterized as including the following features:

[0110] • UE-specific DRX can be configured by upper layers of the network or by the RRC layer;

[0111] • UE-controlled mobility is based on network configuration;

[0112] • The UE stores an inactive AS context, which can be different from the AS context used in the RRC_CONNECTED state;

[0113] • A RAN-based notification area is configured by the RRC layer;

[0114] • The UE monitors for short messages sent using a P-RNTI via DCI;

[0115] • The UE monitors a paging channel for CN paging using a 5G-S-TMSI and for RAN paging using a Full I-RNTI;

[0116] • UE performs neighbor cell measurements and cell selection or cell reselection;

[0117] • UE performs RAN-based notification area update periodically when moving outside the configured RAN-based notification area;

[0118] • If configured, UE acquires SI and can send SI request.

[0119] RRC_INACTIVE state is implemented in NR, but in general, the inactive state can be implemented in any wireless protocol or wireless technology. Thus, the inactive state is not limited to a specific wireless protocol or radio technology. Similar notes apply to the idle state and the connected state as well.

[0120] A UE can transition from the connected state to the inactive state through a suspend procedure and transition back to the connected state through a resume procedure. The UE can also transition from the inactive state to the idle state through a release procedure. The transition from the connected state to the inactive state is not visible to the CN. Thus, UE-related signaling and data exchange between the RAN and the CN can occur while the UE is in the inactive state. From the CN’s perspective, the UE in the inactive state is handled similarly to the UE in the connected state. For example, from the CN’s perspective, the UE can have two connection management (CM) states. The UE is in either a CM-CONNECTED state or a CM-IDLE state. The UE in the CM-IDLE state in the CN is in the RRC_IDLE state from the RAN’s perspective, while the UE in the CM-CONNECTED state in the CN can be in either the RRC_CONNECTED state or the RRC_INACTIVE state from the RAN’s perspective. The security context of the UE and / or other parts of the UE context are stored by the UE and the network before the UE transitions from the connected state to the inactive state. Thus, the network can quickly and securely send signaling to the UE to transition from the inactive state to the connected state or the idle state.

[0121] The network can use a paging message to facilitate the UE’s transition from the idle state or from the inactive state to the connected state. For example, the paging message can be received over a paging physical DL shared channel (paging PDSCH). The network initiates the paging procedure by sending the paging message at a paging occasion of the UE. The network can address multiple UEs with a single paging message by including multiple UE identities (IDs) in a paging record carried by the paging message. The paging record is a set of UE IDs corresponding to the UEs that the network pages. In 3GPP NR specification # TS 38.331, an example of the paging record is the PagingRecord parameter, and an example of the UE ID is the ue-Identity parameter.

[0122] In some embodiments, UEs in the idle state or inactive state monitor a paging search space of a physical DL control channel (PDCCH) containing a paging DCI. An example of paging DCI in NR is DCI format 1 0 with a cyclic redundancy check (CRC) scrambled or masked with a P-RNTI. UEs in the idle state or inactive state know the P-RNTI, so these UEs are able to descramble or demask the CRC and use the CRC to check whether the decoding of DCI format 1 0 is successful. DCI format 1 0 includes, among other information, scheduling information of a short message and / or a paging message. The scheduling information of a paging message can include a resource allocation with a frequency domain resource allocation, a time domain resource allocation, a virtual resource block (VRB) to physical resource block (PRB) mapping, a modulation and coding scheme (MCS), and / or a transport block (TB) scaling. For example, DCI format 1 0 with CRC scrambled by P-RNTI can include any or all of the following bit fields:

[0123] • Short message indicator - length of 2 bits;

[0124] • Short message - length of 8 bits;

[0125] • Frequency domain resource allocation of paging message - length of bits, where may be equal to the size of control resource set (CORESET) 0 (this bit field is reserved if only a short message is carried);

[0126] • Time domain resource allocation of paging message - length of 4 bits (this bit field is reserved if only a short message is carried);

[0127] • VRB to PRB mapping of paging message - length of 1 bit (this bit field is reserved if only a short message is carried);

[0128] • MCS of paging message - length of 5 bits (this bit field is reserved if only a short message is carried);

[0129] • TB scaling of paging message - length of 2 bits (this bit field is reserved if only a short message is carried);

[0130] • Reserved bits - length of 6 bits.

[0131] In this application, the terms “resource assignment” and “resource allocation” are equivalent and can be used interchangeably.

[0132] In case the paging DCI contains resource allocation of the paging message, the UE receiving the paging DCI continues to receive the scheduled paging message according to the resource allocation. When the UE in RRC_IDLE state receives the paging message, the UE can determine whether any UE ID included in each paging record of the paging message matches a specific ID assigned to the UE by an upper layer of the network. In NR, 5G-S-TMSI is used as the UE ID for paging the UE in RRC_IDLE state. In case the UE ID in the paging record matches the specific ID of the UE, the UE can initiate connection with the network, i.e., transition to RRC_CONNECTED state, by forwarding the specific ID of the UE and an access type (if present) to an upper layer of the UE. The access type of the UE can be included as an accessType parameter in the paging message as specified in 3GPP NR specification # TS 38.331.

[0133] When the UE in RRC_INACTIVE state receives the paging message, the UE can determine whether the UE ID included in each paging record of the paging message matches a FullI-RNTI stored by the UE. The FullI-RNTI is a 40-bit string configured to the UE in the RRC suspend procedure. For example, according to 3GPP NR specification # TS 38.331, the FullI-RNTI can be configured in the SuspendConfig field of the RRCRelease information element (IE) configured to the UE for suspending the RRC connection and transitioning the UE from RRC_CONNECTED state to RRC_INACTIVE state.

[0134] In case the UE ID included in the paging record matches the FullI-RNTI of the UE, the UE can initiate the RRC connection resume procedure. The RRC connection resume procedure can be set to a multimedia priority service (MPS)-priority access depending on an access type configured for the UE.

[0135] If the UE is configured by an upper layer of the network to access identity 1, the RRC connection resume procedure can be set to a multimedia priority service (MPS)-priority access. For example, according to 3GPP NR specification # TS 38.331, the resumeCause field can be set to mps-PriorityAccess.

[0136] If the UE is configured by upper layers of the network to access identity 2, the RRC connection resume procedure can be set to mission critical service (MSC)-priority access. For example, according to 3GPP NR specification #TS 38.331, the resumeCause field can be set to msc-PriorityAccess.

[0137] If the UE is configured by upper layers of the network to any of access identities 11 to 15, the RRC connection resume procedure can be set to high priority access. For example, according to 3GPP NR specification #TS 38.331, the resumeCause field can be set to highPriorityAccess.

[0138] For other access identities, the RRC connection resume procedure can be set to mobile terminated (MT) access. For example, according to 3GPP NR specification #TS 38.331, the resumeCause field can be set to mt-Access.

[0139] In case the UE ID included in the paging record does not match the UE’s Full I-RNTI, but another ID assigned to the UE by the network, the UE can forward the UE’s specific ID and access type (if present) to the UE’s upper layers. After entering RRC_IDLE state, the UE can perform the actions specified in 3GPP NR specification #TS 38.331 with release cause set to “other”. An example of another ID assigned to the UE by upper layers of the network is 5G-S-TMSI.

[0140] In addition to transmissions made as part of the state transition procedure from the inactive state to the connected state, legacy control signaling mechanisms do not support (non-paging) DL data transmission to the UE or data transmission from the UE in the inactive state. According to these legacy control signaling mechanisms, the only DCI format that the UE monitors when the UE is in the inactive state and does not perform a connection resume procedure is the paging DCI. For example, the only DCI format that a UE in RRC_INACTIVE state monitors is DCI format 1_0 with CRC scrambled by P-RNTI. However, legacy paging DCI does not support:

[0141] • non-paging DL data scheduling;

[0142] • notification of non-paging DL data scheduling;

[0143] • SL data scheduling; or

[0144] • UL data scheduling.

[0145] Aspects of the application provide control signaling mechanisms to support transmission of data to or from a UE in an inactive state.

[0146] According to one aspect, unicast or groupcast data transmission to or from a UE in an inactive state is scheduled using DCI and a UE-specific ID, or an ID specific to a group of UEs including at least the UE. This enables direct scheduling of data by DCI. For example, for DL, direct scheduling can be faster and more flexible than paging-based scheduling.

[0147] Figures 4 to 6 Figure 4 is a signaling diagram of signaling between a base station (BS) 404 and a UE 402 in an inactive state, provided by some embodiments. For example, the UE 402 and the BS 404 can be similar to the ED 110 and the base station 170 of Figure 2A and Figure 2B Figures 1 and 2.

[0148] Figure 4 includes DCI 406 transmitted from the BS 404 to the UE 402, a scheduled data transmission 408 transmitted from the BS 404 to the UE 402, optional hybrid automatic repeat request (HARQ) feedback 410 transmitted from the UE 402 to the BS 404, and optional sounding reference signal (SRS) 412 transmitted from the UE 402 to the BS 404.

[0149] The UE 402 is in an inactive state when receiving the DCI 406. The DCI 406 includes a CRC scrambled by an RNTI specific to the UE 402. The RNTI is specific to a particular UE or to a group of UEs, and is used when one or more of the UEs is in an inactive state. The RNTI is referred to herein as an “I-RNTI”. Optionally, the I-RNTI is associated with or specific to the inactive state. If the I-RNTI is specific to the inactive state, the I-RNTI is not used to scramble the CRC of a DCI for a UE or a group of specific UEs in a connected state or an idle state. In some implementations, the UE 402 is in an RRC_INACTIVE state, and the DCI 406 is in DCI format 1_0. The DCI 406 includes a CRC scrambled by an I-RNTI of the UE 402. The I-RNTI is different from a P-RNTI, which is not used to scramble the CRC of a DCI when the UE 402 is in an RRC_CONNECTED or RRC_IDLE state.

[0150] A UE in the inactive state monitors for DCI with CRC scrambled by its own I-RNTI. The UE stores its own I-RNTI, so the UE can descramble the CRC and use the CRC to check whether the decoding of the DCI is successful. In the case that the I-RNTI is specific to a particular UE, any other UE in the same network or service area will have a different I-RNTI. The other UEs can not store the I-RNTI of the particular UE, so the other UEs can not be able to descramble the CRC of the DCI. Even if one of the other UEs knows the I-RNTI of the particular UE, the other UE should ignore the DCI with CRC scrambled by the I-RNTI of the particular UE.

[0151] In some embodiments, the I-RNTI is configured for the UE during a connection setup procedure or when the UE is in a connected state. For example, the I-RNTI can be configured as part of the RRC connection setup. Alternatively, the I-RNTI can be configured in pdcch-ServingCellConfig or PDCCH-Config in DL bandwidth part (BWP) configuration in NR. In some other embodiments, the I-RNTI is configured for the UE during a connection suspend procedure. After the I-RNTI is configured, the UE stores the I-RNTI for use in the inactive state.

[0152] In some embodiments, the I-RNTI is based on another identity specific to the UE. The network can use the other identity to determine and configure the I-RNTI, or the UE can determine the I-RNTI itself according to the other identity and a predetermined rule. Denote the size of the I-RNTI (i.e., the number of bits) as m, non-limiting examples of the I-RNTI based on the other identity include:

[0153] • The m bits are from the 40-bit FullI-RNTI configured to the UE in the RRC suspend procedure (e.g., in SuspendConfig in RRCRelease IE), or a function thereof. The m bits can be the m most significant bits (MSBs) or the m least significant bits (LSBs), or m bits based on a predefined or preconfigured selection pattern.

[0154] • The m bits are from the 24-bit ShortI-RNTI configured to the UE in the RRC suspend procedure (e.g., in SuspendConfig in RRCRelease IE), or a function thereof. The m bits can be the m MSBs or the m LSBs, or m bits based on a predefined or preconfigured selection pattern.

[0155] • The m bits are from or are a function of the 48-bit next generation 5G system architecture evolution temporary mobile station identifier (NG-5G-S-TMSI). The m bits can be the m MSBs or the m LSBs, or m bits based on a predefined or preconfigured selection pattern.

[0156] • The m bits are based on the UE's MAC identifier, or a combination of the UE's MAC identifier and network resource identifier, dormancy cycle group information, or paging cycle group.

[0157] In some embodiments, the I-RNTI is 16 bits in size, i.e., m = 16. In some embodiments, the I-RNTI is equal in size to the number of CRC bits of the DCI. For example, both the I-RNTI and the CRC are 16 bits in size. In some embodiments, to increase the number of UEs that can be addressed by the I-RNTI, and thus the number of UEs that the DCI can reach when the UE is in the inactive state, a number of bits larger than the size of the CRC can be used for the I-RNTI. In one particular embodiment, a portion of the I-RNTI bits are used to scramble the CRC of the DCI by the BS (and to unscramble the CRC by the UE), and the remaining I-RNTI bits are included as a bit field in the DCI content. For example, a 24-bit Short I-RNTI configured to the UE during the RRC suspend procedure can be used as the I-RNTI, where 16 bits are used to scramble the CRC of the DCI and 8 remaining bits are included as a bit field in the DCI content.

[0158] Figure 7A A first example UE identifier is shown, which is a combination of a MAC identifier and network resource information. The first example UE identifier can be used to identify the UE when the UE is in the inactive state. Figure 7A An example network resource diagram is shown, highlighting four network resources, which are identified by their time resource identifier and frequency resource identifier. For example, network resource 705 is identified by its frequency resource identifier Fl and time resource identifier Tl, and network resource 707 is identified by its frequency resource identifier F2 and time resource identifier Tl.

[0159] The first example UE identifier can be represented as a combination of the UE's MAC identifier and network resource identifier. As Figure 7AAs shown, the UE identity of the first UE assigned network resources 705 is (MAC IDK, F1, T1) 710, and the UE identity of the second UE assigned network resources 707 is (MAC IDK, F2, T1) 712, where MAC IDK is the MAC identity assigned to the first and second UEs for use in the inactive state. The combination of the MAC identity and the network resource identity supports different UEs reusing the MAC identity.

[0160] Figure 7B A second example UE identity is shown, which is a combination of a MAC identity and a sleep cycle group information. The second example UE identity can be used to identify a UE when the UE is in the inactive state. Figure 7B A first trajectory 720 and a second trajectory 722 are shown, showing the paging cycle groups of a UE, where a high cycle indicates when the UE can monitor the paging channel in a particular paging cycle group.

[0161] The second example UE identity can be represented as a combination of a UE’s MAC identity and its sleep cycle group information. As Figure 7B As shown, the UE identity of the first UE of the first paging cycle group is (MAC IDK, Cycle Group 1) 725, and the UE identity of the second UE of the second paging cycle group is (MAC IDK, Cycle Group 2) 727, where MAC IDK is the MAC identity assigned to the first and second UEs when the first and second UEs are in the active state.

[0162] Referring again to the DCI 406 of Figure 4 The DCI 406 can be or include a notification of data scheduling. The resource allocation can be referred to as “bit field group #1.” Because the DCI 406 includes a CRC scrambled by the I-RNTI for the UE 402, the resource allocation is specific to the UE 402. The resource allocation includes bit fields to enable direct scheduling of data in the inactive state. This enables the UE 402 to have relatively fast and dynamic data scheduling. For example, only one transmission (the DCI 406) is needed to notify the UE 402 of the scheduled data transmission 408. The UE 402 does not need to read a paging message or any other additional messages to learn of the scheduled data transmission 408.

[0163] According to the resource allocation, the UE 406 can receive the scheduled data transmission 408 on a physical shared channel. One example of a physical shared channel is a PDSCH. The UE 402 is in the inactive state when receiving the data transmission 408.

[0164] The data transmission 408 is shown as a unicast transmission. In some embodiments, the data transmission 408 is replaced with a groupcast data transmission, in which case the I-RNTI is configured to or specific to a group of UEs including the UE 402. Each UE in the group of UEs is able to descramble the CRC, obtain the content of the received DCI, and receive the scheduled data transmission. For example, the group of UEs includes part but not all of the UEs in the network or coverage area that are in the inactive state. Other UEs not in the group of UEs can not be able to descramble the CRC and obtain the content of the received DCI.

[0165] Although shown as a DL transmission, the data transmission 406 can be replaced with a UL transmission or a SL transmission. A UL transmission can be sent by the UE 402 to the BS 404 on a physical UL shared channel (PUSCH), and a SL transmission can be sent or received by the UE on a physical SL shared channel (PSSCH). To schedule a SL transmission, sidelink control information (SCI) can be sent in a physical sidelink control channel (PSCCH), in which case the I-RNTI of the receiving UE can be used by the sending UE to scramble the CRC of the SCI. Alternatively, to schedule a SL transmission, a part of the bits of the I-RNTI of the receiving UE can be used by the sending UE to scramble the CRC of the SCI, and the remaining bits of the I-RNTI can be included as a bit field in the content of the SCI.

[0166] In some implementations, resource allocation in DCI 406 includes frequency domain resource allocation. Frequency domain resource allocation can instruct UE 402 to monitor RBs used for data transmission 408. The RB indicated by the frequency domain resource allocation can be a virtual RB (VRB), in which case the UE uses VRB-to-PRB mapping to obtain the PRB scheduled for data transmission 408. Non-interleaved and interleaved VRB-to-PRB mapping schemes can be supported, or only non-interleaved VRB-to-PRB mapping schemes can be supported. In embodiments supporting both non-interleaved and interleaved mapping schemes, the mapping scheme is configured to the UE by a higher layer when the UE is in connected state. In this case, if no mapping scheme is indicated, the UE can adopt non-interleaved mapping. In non-interleaved VRB-to-PRB mapping, VRB n is mapped to PRB n, where n is an integer. In interleaved VRB-to-PRB mapping, RBs (VRBs and PRBs) are divided into multiple RB bundles (VRB bundles and PRB bundles, respectively). An RB bundle consists of multiple consecutive RBs. The RB bundle size can be pre-specified or configured by a higher layer. VRB bundle j is mapped to PRB bundle f(j), where f(j) is a predefined interleaving function and j is an integer. In one example, for DL ​​data scheduling in the inactive state, frequency domain resource allocation is based on type 1 resource indicator values ​​(RIVs) with a length of... Bit. The value can be selected in various ways, including but not limited to:

[0167] · It is the size of CORESET 0;

[0168] · This is the initial DL BWP size configured for UE 402 when UE 402 is in connected state;

[0169] · This is the size of the active DL BWP for UE 402, where the UE receives the RRCLease message in connected state to suspend the RRC connection;

[0170] · This is the size of the configuration or pre-configuration used for DL ​​data transmission in the inactive state (e.g., the size of the DL BWP configured for UE402 for DL ​​communication in the inactive state).

[0171] In one example, to perform UL data scheduling in the inactive state, frequency domain resource allocation is based on type 1 resource indicator values ​​(RIVs), with a length of [missing information]. bits. The value of can be selected in various different ways, including but not limited to:

[0172] · is the size of the initial UL BWP configured to the UE 402 when the UE 402 is in the connected state;

[0173] · is the size of the active UL BWP of the UE 402, which is active when the UE receives an RRCRelease message in the connected state to suspend the RRC connection;

[0174] · is the size of the configured or preconfigured for UL data transmission in the inactive state (e.g., the size of the UL BWP configured to the UE 402 for UL communication in the inactive state).

[0175] In one example, for SL data scheduling in the inactive state, the frequency domain resource allocation is a resource allocation based on a type 1 resource indicator value (RIV) with a length of bits. The value of can be selected in various different ways, including but not limited to:

[0176] · is the size of the active SL BWP of the UE 402, which is active when the UE receives an RRCRelease message in the connected state to suspend the RRC connection;

[0177] · is the size of the configured or preconfigured for SL data transmission in the inactive state (e.g., the size of the SL BWP configured to the UE 402 for SL communication in the inactive state).

[0178] In some implementations, the resource allocation in the DCI 406 includes a time domain resource allocation. The time domain resource allocation can indicate the slots and / or subframes that the UE 402 should monitor for the data transmission 408. In one example, the time domain resource allocation includes 4 bits indicating a row index in a resource allocation table.

[0179] In some implementations, the resource allocation in the DCI 406 includes a VRB to PRB mapping, MCS, and / or TB scaling field. For example, the resource allocation can include any or all of the following bit fields:

[0180] • VRB to PRB mapping - 1 bit in length, indicating the VRB to PRB mapping scheme (interleaved or non-interleaved) used for the scheduled data transmission;

[0181] • MCS - 5 bits indicating a row index in a MCS table (e.g., Table 5.1.3.1-1 of 3GPP NR Specification # TS 38.214); and

[0182] • TB scaling - 2 bits indicating a row index in a pre-defined TB scaling table.

[0183] An example of the TB scaling table is provided in Table 1 below.

[0184] Table 1: TB scaling table according to one embodiment

[0185]

[0186]

[0187] In some implementations, the DCI 406 includes a messaging bit field, which can be referred to as “bit field group #2.” The messaging bit field includes a short message indicator that indicates whether the DCI 406 includes a short message for the UE 402. In one example, the short message indicator is 1 bit indicating a row index in a short message indicator table. Table 2 provided below is an example of a short message indicator table.

[0188] Table 2: Short message indicator table according to one embodiment

[0189] Bit field Short message indicator 0 Only scheduling information for unicast / groupcast data transmission is present in the DCI 1 Scheduling information for both unicast / groupcast data transmission and short message is present in the DCI

[0190] If the short message indicator indicates that a short message is included in the DCI 406, the UE 402 will proceed to read the short message. In one example, the short message bit field of the DCI 406 includes 8 bits to indicate a row index in a short message table. The rows of the short message table can include possible short messages for the UE 402. One example of a short message table is Table 6.5-1 of 3GPP NR Specification # TS 38.331, shown in Table 3 below.

[0191] Table 3: Table 6.5-1 of 3GPP NR Specification # TS 38.331

[0192]

[0193] Alternatively, if the short message indicator indicates that no short message is included in the DCI 406, the bits of the short message bit field are reserved.

[0194] In some implementations, the DCI 406 includes an indication of a HARQ process associated with the data transmission 408. This indication can be provided by a HARQ-related bit field referred to as “Bit Field Group #3.” In one example, the indication of the HARQ process can include any or all of the following:

[0195] • New data indicator - 1 bit indicating whether the failed transmission is a first transmission or a retransmission;

[0196] • Redundancy version - 2 bits indicating a row index in a table of redundancy versions (e.g., Table 7.3.1.1.1-2 of 3GPP NR Specification # TS 38.212);

[0197] • HARQ process number - 4 bits in length;

[0198] • Transmit power control (TPC) command for scheduled PUCCH - 2 bits indicating a row index in a TPC command table;

[0199] • PUCCH resource indicator - 3 bits in length;

[0200] • PDSCH-to-HARQ feedback timing indicator - 3 bits indicating a row index in a table mapping PDSCH-to-HARQ feedback timing indicator values to a number of time units.

[0201] Using the indication of the HARQ process associated with the data transmission 408, the UE 402 can transmit the HARQ feedback 410 to the BS 404. For example, if the UE 402 fails to successfully receive and decode the data transmission 408, the UE 402 can transmit a negative acknowledgement according to the HARQ process associated with the data transmission 408.

[0202] The HARQ process can not be configured for every data transmission from the BS 404 to the UE 402, so the DCI 406 can not include the indication of the HARQ process in all implementations.

[0203] In some implementations, the DCI 406 includes one or more measurement requests or triggers in measurement-related bit fields. The measurement-related bit fields can be referred to as “Bit Field Group #4.” Non-limiting examples of these measurement requests include:

[0204] • Sounding reference signal (SRS) request - 2 bits representing a row in an SRS request table;

[0205] • Channel State Information (CSI) Request - length up to 6 bits (e.g., the number of bits can be configured by higher layers of the network); and

[0206] • Position Information Request - 1 bit indicating a row in the Position Information Table.

[0207] An example of the Position Information Table is provided in Table 4 below.

[0208] Table 4: Position Information Table According to One Embodiment

[0209] Bit Location information type 0 Mobility tracking information, e.g. GPS information 1 Location prediction information

[0210] The measurement request is used by the BS 404 and / or network to obtain measurement related information. Examples of measurement related information include uplink SRS, measurement results from downlink pilots and / or data, uplink data, mobility tracking information such as GPS information, and position prediction information. The measurement related information can be used to determine the position of the UE 402 and / or the channel quality of the UE, and data can be sent to the UE accordingly. In some implementations, the measurement request can request measurement related information periodically.

[0211] It should be appreciated that the BS 404 can not need to receive any measurement related information. For example, if the wireless device does not move, it can be sufficient to rely on previous measurement related information. Also, if data can be sent with a predefined MCS, the measurement related information can not be needed. Thus, the DCI 406 can not include a measurement request.

[0212] As shown in FIG. 4, optional SRS 412 is transmitted from the UE 402 to the BS 404. The SRS 412 can be transmitted in response to an SRS request included in the DCI 406. Figure 4

[0213] Figure 5 and Figure 6 Other examples of signaling between the UE 402 and the BS 404 are shown. Similar to Figure 4 , Figure 5 includes the DCI 406 transmitted from the BS 404 to the UE 402, the data transmission 408 transmitted from the BS 404 to the UE 402, and optional HARQ feedback 410 transmitted from the UE 402 to the BS 404. In addition, Figure 5 includes optional transmission of position information 412 from the UE 402 to the BS 404. The position information can include GPS or position prediction information, and can be transmitted in response to a position information request in the DCI 406, for example.

[0214] Figure 6 ​It also includes DCI 406 transmitted from BS 404 to UE 402, data transmission 408 transmitted from BS 404 to UE 402, and optional HARQ feedback 410 transmitted from UE 402 to BS 404. Figure 6 It also includes an optional DL reference signal (RS) 416 transmitted from BS 404 to UE 402, and an optional CSI 418 transmitted from UE 402 to BS 404. UE 402 determines CSI 418 based on the measurement results of the DL RS. For example, DL RS 416 can be received in response to a CSI request in DCI 406, and CSI 418 can be generated and transmitted.

[0215] Figures 4 to 6 The transmission order shown is provided as an example and should not be considered as limiting in any way. Other transmission orders have also been considered. For example, UE 402 may send SRS 412 before BS 404 sends data transmission 408.

[0216] Generally, a DCI including a CRC scrambled by I-RNTI can be formatted in various different ways. In some embodiments, the format of a DCI with a CRC scrambled by I-RNTI includes only resource allocation and excludes short messages, HARQ process indications, or measurement requests. For example, this DCI may only include bit field group #1 as defined above.

[0217] In some embodiments, the format of a DCI with a CRC scrambled by I-RNTI includes resource allocation and short messages, but excludes indications or measurement requests from the HARQ process. For example, this DCI may only include bit field group #1 and bit field group #2 as defined above.

[0218] In some embodiments, the format of a DCI with a CRC scrambled by I-RNTI includes indications of resource allocation and HARQ processes, but excludes short messages or measurement requests. For example, this DCI may only include bit field group #1 and bit field group #3 as defined above.

[0219] In some embodiments, the format of a DCI with a CRC scrambled by I-RNTI includes resource allocation, HARQ process indication, and measurement request, but excludes short messages. For example, this DCI may only include bit field group #1, bit field group #3, and bit field group #4 as defined above.

[0220] Other formats of DCI with CRC scrambled by I-RNTI were also considered.

[0221] Although not in Figures 4 to 6DCI 406, but the UE 402 can also receive other DCIs in addition to the DCI 406. The other DCIs can be received before or after the DCI 406. Generally, the UE 402 can monitor a paging search space and perform blind decodes on the paging PDCCH. In each blind decode, the UE 402 attempts to descramble the CRC of the DCI in the paging PDCCH using the P-RNTI and the I-RNTI. If neither the P-RNTI nor the I-RNTI passes the CRC check, the UE 402 continues with the next blind decode attempt in the same paging search space. The UE 402 continues to attempt until a CRC check passes after descrambling by the I-RNTI or the P-RNTI in a blind decode attempt. At this point, the UE 402 proceeds to read the DCI content and follow the corresponding DCI command(s). In some implementations, the UE 402 can temporarily stop blind decoding the paging search space to perform actions according to the corresponding DCI command(s).

[0222] In some implementations, the DCI 406 matches the size of other DCIs that the UE 402 can receive. For example, the DCI 406 can match the size of a paging DCI. As mentioned above, one example of a paging DCI is a DCI format 1 0 with a CRC scrambled by the P-RNTI. When the DCI 406 matches the size of the paging DCI, the DCI 460 and the paging DCI will have the same number of bits after the size matching. One possible benefit of the size matching is to avoid the increased complexity of blind decoding the PDCCH. In some embodiments, to match the size of a first DCI (referred to as “DCI X”) to the size of a second DCI (referred to as “DCI Y”), a first size of the DCI Y is determined according to the DCI format of the DCI Y and other possible size matching of the DCI Y, the matching of the size of the DCI X to the size of the DCI Y is performed as follows:

[0223] • If the number of information bits in the DCI X is less than the payload size of the DCI Y before padding, a number of zero padding bits are generated for the DCI X until the payload size is equal to the payload size of the DCI Y.

[0224] • If the number of information bits in the DCI X is greater than the payload size of the DCI Y before truncation, the bit width of the frequency domain resource allocation field in the DCI X is reduced by truncating a number of most significant bits such that the size of the DCI X is equal to the size of the DCI Y.

[0225] In some implementations, the DCI 406 matches the size of other DCIs that the UE 402 can receive. For example, the DCI 406 can match the size of a paging DCI. As mentioned above, one example of a paging DCI is a DCI format 1 0 with a CRC scrambled by the P-RNTI. When the DCI 406 matches the size of the paging DCI, the DCI 460 and the paging DCI will have the same number of bits after the size matching. One possible benefit of the size matching is to avoid the increased complexity of blind decoding the PDCCH. In some embodiments, to match the size of a first DCI (referred to as “DCI X”) to the size of a second DCI (referred to as “DCI Y”), a first size of the DCI Y is determined according to the DCI format of the DCI Y and other possible size matching of the DCI Y, the matching of the size of the DCI X to the size of the DCI Y is performed as follows: Figure 4In one particular example of DCI 406, DCI X discussed above is DCI 406, and DCI Y discussed above is a paging DCI (not shown). In another example for size matching DCI 406, DCI X is DCI 406, and DCI Y is DCI 1 0 (not shown) that is monitored in the common search space.

[0226] In some embodiments, DCI 406 can be monitored in the same search space as the paging DCI (i.e., in the paging search space). For example, the UE monitors DCI 406 and / or receives data scheduled by DCI 406 following a paging occasion. A possible benefit of doing so is to limit blind decoding attempts by the UE when the UE is in the inactive state, and to achieve further power saving compared to embodiments in which DCI 406 and the paging DCI are monitored in different search spaces or the UE monitors DCI 406 for a duration outside of its paging occasion.

[0227] In some implementations, resource block (RB) scaling can be applied to enable scheduling of a BWP size that is larger than the BWP size used to determine the frequency domain resource allocation of the DCI. For example, when the parameter used to determine the frequency domain resource allocation of the DCI, and is smaller than the size of the inactive DL BWP, RB scaling can be applied. As an example of the RB scaling mechanism, consider the size of the inactive DL BWP denoted by The RIV indicated by the frequency domain resource allocation in the DCI corresponds to the starting RB, and the length of the contiguously allocated RBs The RIV is defined as follows:

[0228] If then

[0229]

[0230] else

[0231]

[0232] Here, L' RBs = L RBs / K, RB' start = RB start / K and If then K is equal to the largest power of 2 that satisfies ; otherwise, K = 1.

[0233] According to one aspect of the application, unicast or groupcast data transmission to or from a UE in inactive state is scheduled by paging using an indication in the paging DCI. The UE can be informed of the data transmission using the indication in the paging DCI. The data transmission can then be received in the paging message or in a further transmission scheduled by the paging message. A possible benefit of using the paging DCI to provide the indication that data transmission is scheduled is that the indication information conveyed by the paging DCI is not intelligible to legacy UEs (i.e., UEs that do not support unicast or groupcast data transmission by paging). Thus, a legacy UE can not attempt to receive the paging message after successfully decoding the paging DCI, and thus power and battery life can be conserved.

[0234] Using the paging DCI to provide the indication that data transmission is scheduled is one example of indirect scheduling. Since a UE in inactive state can have already received and decoded the paging DCI, implementing the indication that data transmission is scheduled using the paging DCI can not increase PDCCH decoding performance or complexity.

[0235] Figure 8 Figure 8 is a signaling diagram of signaling between a BS 804 and a UE 802 in inactive state according to some embodiments. For example, the UE 802 and BS 804 can be similar to the ED 110 and base station 170 of Figures 1 and 2. Figure 2A and Figure 2B of Figures 1 and 2.

[0236] Figure 8 Figure 8 includes a paging DCI 806 transmitted from the BS 804 to the UE 802, a paging message 808 transmitted from the BS 804 to the UE 802 in a paging PDSCH, and an optional PDSCH transmission 810 from the BS 804 to the UE 802. The UE 802 can receive the paging DCI 806, the paging message 808, and the optional PDSCH transmission 810 while in inactive state.

[0237] The paging DCI 806 includes a CRC scrambled by a P-RNTI, and an indication that unicast or groupcast data transmission is scheduled. The data transmission is scheduled on the DL to the UE 802. UEs in idle or inactive state store the P-RNTI, so the UE 802 is able to descramble the CRC to determine whether decoding the paging DCI 806 was successful.

[0238] Any of the various bit fields of the paging DCI 806 can be used to provide the indication that data transmission is scheduled. In some implementations, these bit fields are reinterpretations of bit fields previously or traditionally reserved in paging DCIs. For example, the bit fields of DCI format 1 0 with CRC scrambled by P-RNTI can be reinterpreted to provide the indication that data transmission is scheduled.

[0239] In some embodiments, the short message indicator bit field of the paging DCI is used to indicate data scheduling. Traditionally, for DCI format 1 0 with CRC scrambled by P-RNTI, the bit combination "00" in the short message indicator bit field is reserved. In some embodiments, this bit combination is reinterpreted as an indicator for data scheduling. An example of a short message indicator table specifying bit combination "00" for DL data scheduling is provided below. In this example, a UE that supports unicast or groupcast DL data transmission over paging determines that the scheduled paging message corresponds to unicast or groupcast DL data transmission upon reading the short message indicator bit field of "00." However, a UE that does not support unicast or groupcast DL data transmission over paging can ignore the paging DCI upon reading the short message indicator bit field of "00," thereby conserving power and battery life by avoiding decoding the scheduled paging message.

[0240] Table 5: Example of short message indicator table according to one embodiment

[0241] Bit field Short message indicator 00 Scheduling unicast / groupcast DL data 01 Only scheduling information for paging is present in the DCI 10 Only short message is present in the DCI 11 Scheduling information for both paging and short message is present in the DCI

[0242] In some embodiments, the short message bit field of the paging DCI is used to indicate data scheduling. For example, the short message indicator bit field can indicate to the UE that a short message is present, and the short message can be used to indicate DL data scheduling. For a short message indicator bit field with 2 bits, any of the bit combinations "10" and "11" can be used to indicate that a short message is included in the paging DCI. The short message bit field can include a single bit indicating whether data transmission is scheduled to the UE. Taking the short message table shown in Table 3 as an example, any or all of bits 3-8 can be used to indicate that data transmission is scheduled. This can be considered a reinterpretation of the previously or traditionally reserved short message bit field.

[0243] In some embodiments, a bit field other than the short message indicator bit field and the short message bit field of the paging DCI is used to indicate data scheduling. For example, one of the reserved bits in DCI format 1 0 with CRC scrambled by P-RNTI can be used to indicate that data transmission is scheduled. This can be considered a reinterpretation of the previously or traditionally reserved DCI bit field.

[0244] It is noted that the paging DCI 806 can not indicate which UE data transmission is scheduled for. For example, when the UE 802 receives the paging DCI 806 and determines that data transmission is scheduled, the UE can not know at this time that the data transmission is for the UE. Similar notes apply to other UEs that monitor the paging search space and receive the paging DCI 806. An indication that data transmission is scheduled for the UE 802 can be provided in the paging message 808.

[0245] The paging DCI 806 includes a resource allocation of the paging message 808. Examples of resource allocations of paging messages included in DCI format 1 0 with CRC scrambled by P-RNTI are provided above.

[0246] The UE 402, upon receiving the paging message 808, reads the paging record in the paging message. If the UE ID that has been assigned to the UE 402 is listed in the paging record, the UE can determine that a data transmission is scheduled for the UE. Another UE that receives the paging message 808 but does not find its UE ID in the paging record will determine that no data transmission is scheduled for the other UE.

[0247] In some implementations, the data transmission is included in the paging message 808, and thus the UE 802 receives the data transmission in the paging message. In these implementations, the PDSCH transmission 810 is not needed to perform the data transmission, and the PDSCH transmission 810 can be omitted.

[0248] In other implementations, the paging message 808 includes a resource allocation for the data transmission. The resource allocation corresponds to the PDSCH transmission 810 that includes the data transmission. The UE 802 receives the resource allocation in the paging message 808 and receives the data transmission in the PDSCH transmission 810. Receiving the PDSCH transmission 810 can or can not require the UE 802 to transition from the inactive state to the connected state.

[0249] In some implementations, the paging message 808 includes an indication of whether the data transmission is greater than a predetermined threshold. The indication can be a single bit of the paging message 808, and in particular implementations, a single bit in each paging record included in the paging message 808. If the data transmission is less than the threshold, the data transmission can be considered a small data transmission. If the data transmission is greater than the threshold, the data transmission can be considered a large data transmission. The indication of whether the data transmission is greater than the predetermined threshold can affect the behavior of the UE 802 in decoding the paging message 808.

[0250] Small data transmissions can be included in the paging message 808. Thus, when the UE 802 learns that the data transmission is small, the UE can proceed to decode the paging message 808 to receive the data transmission. Alternatively, when the data transmission is a large data transmission, the data transmission can not fit within the paging message 808. Thus, the paging message 808 can include a resource allocation of the PDSCH transmission 810. When the UE 802 learns that the data transmission is large, the UE can proceed to decode the paging message 808 to receive the resource allocation of the PDSCH transmission 810, and subsequently decode the PDSCH transmission 810 according to the received resource allocation.

[0251] The paging message 808, and in particular implementations, each paging record included in the paging message 808, can include an indication of whether the paging message 808 includes a resource allocation for a data transmission or the data transmission itself. This indication can be provided regardless of whether the data transmission is small or large. Thus, when the UE 802 learns that the paging message 808 includes a data transmission, the UE can proceed to decode the paging message 808 to receive the data transmission. Or, when the UE 802 learns that the paging message 808 includes a resource allocation for a data transmission, the UE can proceed to decode the paging message 808 to receive the resource allocation for the PDSCH transmission 810, and subsequently, decode the PDSCH transmission 810 according to the received resource allocation.

[0252] In some embodiments, the PDSCH transmission 810 can also be a PUSCH transmission or a PSSCH transmission. For example, the paging message 808 can include a resource allocation for a data transmission from the UE 802 on the UL. Or, the paging DCI 806 can be a paging SL control information (SCI), and the paging message 808 can include a resource allocation for a data transmission to or from the UE 802 on the SL.

[0253] According to one aspect of the present application, unicast or groupcast data transmission to or from a UE in the inactive state is scheduled by paging without any indication of the unicast or groupcast data transmission in the paging DCI. One possible benefit of this aspect of the present application is to enable the network to page some UEs by normal or legacy paging using the paging message, and inform other UEs of the unicast or groupcast data transmission. The normal or legacy paging can also be referred to as a conventional paging.

[0254] In some embodiments, a single bit in each paging record indicates whether the UE whose identity is transmitted in the corresponding paging record is paged by normal or conventional paging, or scheduled for unicast or groupcast data transmission.

[0255] In some embodiments, for each UE indicated in the paging message as having scheduled unicast or groupcast data transmission, the data transmission is included in the corresponding paging record.

[0256] In some embodiments, for each UE indicated in the paging message as having scheduled unicast or groupcast data transmission, resource allocation information for the data transmission can be included in the corresponding paging record. Upon reading the corresponding paging record, the UE can proceed to receive the DL data (or transmit UL data) scheduled by the corresponding resource allocation.

[0257] In some embodiments, data transmission and resource allocation for data transmission are not included in the paging record. A UE indicated in the paging message as having a scheduled unicast or groupcast data transmission can continue to monitor and receive PDCCH. The PDCCH can include a DCI (e.g., a DCI according to any of the embodiments described above) with a CRC scrambled by an I-RNTI. The UE can then descramble the CRC and decode the DCI and receive the DL data (or transmit the UL data) scheduled by the DCI. In some embodiments, the PDCCH including the DCI with the CRC scrambled by the I-RNTI can be monitored and received in a paging search space set. In some other embodiments, the PDCCH including the DCI with the CRC scrambled by the I-RNTI can be monitored and received in a search space set referred to as a “non-active unicast / groupcast search space set” (which is different from the paging search space set). In one particular example, only when the UE receives an indication of a unicast or groupcast data transmission in a paging message as described above, the UE can monitor the “non-active unicast / groupcast search space set” in the non-active state.

[0258] Reference is now made to Figure 9 and Figure 10 Further examples of control signaling to support transmission of data to or from a UE in a non-active state are discussed.

[0259] Figure 9 A flowchart of an example method 900 is shown. Step 902 includes a UE in a non-active state receiving a DCI. For example, the DCI can be a DCI format 1 0. The DCI includes a CRC scrambled by an RNTI specific to the UE or a group of UEs, where the group of UEs includes the UE. As described above, this type of RNTI is also referred to herein as an I-RNTI. Optionally, the RNTI is specific to the non-active state. The UE knows the RNTI and can use the RNTI to descramble the CRC. The descrambled CRC can then be used to check whether decoding the DCI is successful.

[0260] In some embodiments, the RNTI is specific to the UE. For example, the group of UEs can include only the UE. Optionally, the RNTI is based on another identity specific to the UE. For example, the RNTI can be based on a Full I-RNTI, a Short I-RNTI, a NG-5G-S-TMSI, a MAC ID, or a combination of a MAC ID and a network resource identity, dormancy cycle group information, or a paging cycle group of the UE.

[0261] The DCI also includes a resource allocation for a data transmission to the UE. In some implementations, the resource allocation includes at least one of: a frequency domain resource allocation, a time domain resource allocation, a virtual resource block to physical resource block mapping, a modulation and coding scheme, and a transport block scaling factor. Examples of resource allocation bit fields are provided elsewhere herein.

[0262] In some embodiments, the DCI also includes a short message, an indication of a HARQ process associated with the data transmission, and / or a measurement request. Examples of short messages, indications of HARQ processes, and measurement requests are provided elsewhere herein.

[0263] Step 904 includes the UE in the inactive state receiving a data transmission on a physical shared channel. The resource allocation for the data transmission in the DCI is used to receive the data transmission. The data transmission can be a DL transmission or a SL transmission, and the physical shared channel can be a PDSCH or a PSSCH.

[0264] Optional step 906 includes the UE in the inactive state receiving another DCI. In step 906, the RNTI used to scramble the CRC of the DCI received in step 902 is considered a first RNTI. The other DCI includes another CRC scrambled by a P-RNTI different from the first RNTI. The UE knows the P-RNTI and can use the P-RNTI to descramble the other CRC. The descrambled other CRC can then be used to check whether decoding the other DCI is successful. For example, the DCI received in step 902 matches the size of the other DCI received in step 906, which can reduce the complexity of blind decoding.

[0265] It is noted that the DCI received in step 902 and the other DCI received in step 906 can be received at different times. For example, the DCI received in step 902 and the other DCI received in step 906 can be received at different PDCCH monitoring occasions or different paging occasions. Moreover, Figure 9 The order of steps 902, 906 shown is provided by way of example. In some cases, step 906 can be performed before step 902.

[0266] Figure 10 A flowchart of another example method 1000 is shown. Step 1002 includes a UE in an inactive state receiving a DCI. For example, the DCI can be a DCI format 1 0. The DCI includes a CRC scrambled by a P-RNTI and a resource allocation for transmitting a paging message to the UE. The UE knows the P-RNTI and can use the P-RNTI to descramble the CRC. The descrambled CRC can then be used to check whether decoding the DCI is successful.

[0267] In some embodiments, step 1002 includes the UE in the inactive state receiving an indication in a DCI that a data transmission is scheduled. In some embodiments, the indication is in a short message indicator field of the DCI or the indication is in a short message field of the DCI. The indication can be a single bit of the DCI.

[0268] The indication that a data transmission is scheduled can not always be received in the DCI. In some embodiments, the UE receives the indication in a paging message.

[0269] Optional step 1004 includes the UE in the inactive state receiving a resource allocation for the data transmission in a paging message on a paging physical downlink shared channel. In step 1004, the UE receives the paging message, where the paging message carries the resource allocation for the data transmission. The resource allocation for the paging message carried in the DCI is used to receive the paging message.

[0270] Step 1006 includes the UE in the inactive state receiving the data transmission on a physical shared channel according to the paging message. When optional step 1004 is performed, the physical shared channel can be a PDSCH or a PSSCH. In this case, receiving the data transmission according to the paging message includes (i) receiving the resource allocation for the data transmission in the paging message and (ii) receiving the data transmission using the resource allocation.

[0271] When step 1004 is not performed, step 1006 includes receiving the data transmission in the paging message on a paging PDSCH. The data transmission is included in the paging message and does not require a separate transmission. In this case, receiving the data transmission according to the paging message includes obtaining the data transmission from the paging message.

[0272] In some embodiments, the paging message includes an indication of whether the data transmission is greater than a predetermined threshold. If the data transmission is less than the predetermined threshold, the data transmission is carried by the paging message and step 1004 is omitted. If the data transmission is greater than the predetermined threshold, the paging message is used to carry the resource allocation for the data transmission in step 1004. The data transmission is then received in a subsequent transmission in step 1006.

[0273] Method 900 and / or method 1000 can be performed by a UE having a processor and a receiver. For example, UE 110 can perform method 900 and / or method 1000. The processor can configure the UE to be in an inactive state, including an RRC INACTIVE state. For example, configuring the UE to be in the inactive state can include performing a suspend procedure to transition from a connected state to the inactive state. The receiver of the UE can be used to receive the DCI, the paging message, and / or other DL or SL transmissions. In some embodiments, the UE also has a transmitter for transmitting data in the inactive state.

[0274] It should be understood that one or more steps of the example methods provided herein can be performed by corresponding units or modules. For example, data can be transmitted by a transmitting unit or a transmitting module. Data can be received by a receiving unit or a receiving module. Data can be processed by a processing unit or a processing module. The corresponding units / modules can be hardware-only implementations, software-only implementations, or combination thereof. For example, one or more of the units / modules described above can be an integrated circuit, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC). It should be understood that if these modules are software, they can be retrieved all or in part, individually or collectively, by a processor as needed for processing, and in one or more instances as needed, and these modules can themselves include instructions for further deployment and instantiation.

[0275] Although combinations of features are recited in the examples, it should be understood that not all combinations are required to achieve the advantages of the application according to the examples. In other words, not all features of one example need to be included in a system or method according to an example design. In addition, selected features of one example embodiment can be combined with selected features of another example embodiment.

[0276] While the present application has been described with reference to illustrative examples, this description is not intended to be limiting. Various modifications and combinations of the illustrative examples and other embodiments of the application will be apparent to those of ordinary skill in the art from the disclosure herein. Accordingly, the appended claims are intended to encompass any such modifications or embodiments.

Claims

1. A method of data transmission, characterized by, Comprising: A user equipment, UE, in an inactive state receives a downlink control information, DCI, comprising: A cyclic redundancy check, CRC, scrambled by a radio network temporary identifier, RNTI, specific to a group of UEs, the group of UEs comprising the UE, and A resource allocation for a data transmission to the UE; The UE in the inactive state receives the data transmission on a physical shared channel.

2. The method of claim 1, wherein, The DCI further comprises a short message.

3. The method according to claim 1 or 2, characterized in that, The DCI further comprises an indication of a hybrid automatic repeat request, HARQ, process associated with the data transmission.

4. The method according to any one of claims 1 to 3, characterized in that, The DCI further comprises a measurement request.

5. The method according to any one of claims 1 to 4, characterized in that, The RNTI is a first RNTI, the method further comprising: The UE in the inactive state receives another DCI, the other DCI comprising another CRC scrambled by a paging RNTI different from the first RNTI, wherein the DCI is size matched to the other DCI.

6. The method according to any one of claims 1 to 5, characterized in that, The RNTI is specific to the inactive state.

7. The method according to any one of claims 1 to 6, characterized in that, The RNTI is specific to the UE.

8. The method of claim 7, wherein, The RNTI is based on another identifier specific to the UE.

9. The method according to any one of claims 1 to 8, characterized in that, The physical shared channel is a physical downlink shared channel or a physical sidelink shared channel.

10. The method according to any one of claims 1 to 9, characterized in that, The resource allocation comprises at least one of: a frequency domain resource allocation, a time domain resource allocation, a virtual resource block to physical resource block mapping, a modulation and coding scheme, and a transport block scaling factor.

11. A method of data transmission, characterized by, Comprising: A user equipment, UE, in an inactive state receives a downlink control information, DCI, comprising: A cyclic redundancy check, CRC, scrambled by a paging radio network temporary identifier, P-RNTI, and A resource allocation for a paging message to the UE; The UE in the inactive state receives a data transmission on a physical shared channel according to the paging message.

12. The method of claim 11, wherein, The method further comprises: The UE in the inactive state receives an indication in the DCI or the paging message that the data transmission is scheduled.

13. The method of claim 12, wherein, Receiving the data transmission on a physical shared channel comprises receiving the data transmission in the paging message on a paging physical downlink shared channel.

14. The method of claim 11, wherein, The method further comprises: The UE in the inactive state receives a resource allocation for the data transmission in the paging message on a paging physical downlink shared channel.

15. The method of claim 14, wherein, The physical shared channel is a physical downlink shared channel or a physical sidelink shared channel.

16. The method of claim 12, wherein, The indication is a single bit of the DCI.

17. The method of claim 12, wherein, The indication is in a short message indication field of the DCI.

18. The method of claim 12, wherein, The indication is in a short message field of the DCI.

19. The method according to any one of claims 11 to 18, characterized in that, The paging message comprises an indication of whether the data transmission is greater than a predetermined threshold.

20. A user equipment (UE), comprising: Comprising: A processor; A non-transitory computer readable storage medium storing programming for execution by the processor, the programming comprising instructions to perform the method according to any one of claims 1 to 10.

21. A user equipment (UE), comprising: Comprising: A processor; A non-transitory computer readable storage medium storing programming for execution by the processor, the programming comprising instructions to perform the method according to any one of claims 11 to 19.

22. A method of data transmission, characterized by Comprising: A base station transmits downlink control information (DCI) to a user equipment (UE) in an inactive state, the DCI comprising: a cyclic redundancy check (CRC) scrambled by a radio network temporary identifier (RNTI) specific to a group of UEs, the group of UEs including the UE, and a resource allocation for data transmission to the UE; The base station transmits the data transmission to the UE in the inactive state on a physical shared channel.

23. The method of claim 22, wherein, The DCI further comprises a short message.

24. The method of claim 22 or 23, wherein, The DCI further comprises an indication of a hybrid automatic repeat request (HARQ) process associated with the data transmission.

25. The method of any one of claims 22-24, wherein, The DCI further comprises a measurement request.

26. The method of any one of claims 22-25, wherein, The RNTI is a first RNTI, the method further comprising: The UE in the inactive state receives another DCI, the other DCI comprising another CRC scrambled by a paging RNTI different from the first RNTI, wherein the DCI is size-matched to the other DCI.

27. The method of any one of claims 22-26, wherein, The RNTI is specific to the inactive state.

28. The method of any one of claims 22-27, wherein, The RNTI is specific to the UE.

29. The method of claim 28, wherein, The RNTI is based on another identifier specific to the UE.

30. The method of any one of claims 22-29, wherein, The physical shared channel is a physical downlink shared channel or a physical sidelink shared channel.

31. The method of any one of claims 22-30, wherein, The resource allocation comprises at least one of: a frequency domain resource allocation, a time domain resource allocation, a virtual resource block to physical resource block mapping, a modulation and coding scheme, and a transport block scaling factor.

32. A method of data transmission, characterized by, Comprising: A base station transmits downlink control information (DCI) to a user equipment (UE) in an inactive state, the DCI comprising: a cyclic redundancy check (CRC) scrambled by a paging radio network temporary identifier (P-RNTI), and a resource allocation for transmitting a paging message to the UE; The base station transmits a data transmission to the UE in the inactive state on a physical shared channel according to the paging message.

33. The method of claim 32, wherein, Further comprising: The base station transmits, to the UE in the inactive state, an indication that the data transmission is scheduled in the DCI or the paging message.

34. The method of claim 33, wherein, Transmitting the data transmission on the physical shared channel comprises transmitting the data transmission in the paging message on a paging physical downlink shared channel.

35. The method of claim 32, wherein, Further comprising: The base station transmits, to the UE in the inactive state, a resource allocation for the data transmission in the paging message on a paging physical downlink shared channel.

36. The method of claim 35, wherein, The physical shared channel is a physical downlink shared channel or a physical sidelink shared channel.

37. The method of claim 33, wherein, The indication is a single bit of the DCI.

38. The method of claim 33, wherein, The indication is in a short message indication field of the DCI.

39. The method of claim 33, wherein, The indication is in a short message field of the DCI.

40. The method of any one of claims 32-39, wherein, The paging message comprises an indication of whether the data transmission is greater than a predetermined threshold.

41. A base station, comprising: Comprising: A processor; A non-transitory computer readable storage medium storing a program for execution by the processor, the program comprising instructions for performing the method of any one of claims 22 to 31.

42. A base station, comprising: Comprising: A processor; A non-transitory computer readable storage medium storing a program for execution by the processor, the program comprising instructions for performing the method of any one of claims 32 to 40.

43. A non-transitory computer-readable storage medium, comprising: storing a program for execution by the processor, the program including instructions for performing the method according to any one of claims 1 to 19 and 22 to 40.

Images