Improvements for mobile originated data

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) can transmit an uplink message including user data and an identifier associated with a contention resolution for the UE. The UE can receive a downlink control information (DCI) message in response to the uplink message. In some examples, at least a portion of the DCI message can be scrambled according to a radio network temporary identifier (RNTI) associated with the UE. For example, the RNTI can be a first RNTI based on the identifier included in the uplink message, which can indicate that the DCI message is associated with contention resolution. In some cases, the RNTI can be a subset of the identifier, and a remaining subset of the identifier can be included in a payload of the DCI message. In some other examples, the RNTI can be a second RNTI associated with a non-contention resolution procedure.

Description

Cross-references to related applications

[0001] This patent application claims priority to U.S. Patent Application No. 18 / 887,552, filed September 17, 2024, entitled “IMPROVEMENTS FOR MOBILE ORIGINATED DATA”, and U.S. Provisional Patent Application No. 63 / 605,216, filed December 1, 2023, entitled “IMPROVEMENTS FOR MOBILE ORIGINATED DATA”, each of which has been assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0002] The following content relates to wireless communications, including improvements for mobile-initiated data. Background Technology

[0003] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, and broadcasting. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication for communication devices, which may be referred to as User Equipment (UE). Summary of the Invention

[0004] The described technology relates to improved methods, systems, devices, and apparatuses supporting improvements for mobile-initiated data. For example, the described technology allows a UE to transmit user data while operating in idle mode. In some examples, the UE may transmit an uplink message including user data and an identifier associated with contention resolution and the UE. A network entity may transmit a downlink control information (DCI) message in response to the uplink message. In some examples, at least a portion of the DCI message may be scrambled according to a Radio Network Temporary Identifier (RNTI) associated with the UE. For example, a first RNTI may be a UE-specific RNTI based on an identifier included in the uplink message, indicating that the DCI message is associated with contention resolution. In some cases, the RNTI may be a subset of the identifiers, and the remaining subset of the identifiers may be included in the payload of the DCI message. In some other examples, the RNTI may be a second RNTI associated with a purpose other than contention resolution, such as a static RNTI. The UE may monitor the DCI and attempt to decode it according to the UE-specific RNTI and the second RNTI, and successful decoding may indicate the purpose of the DCI message to the UE. By sending DCI messages in response to uplink messages, network entities can experience reduced transmission overhead compared to other technologies, such as sending downlink data messages in response.

[0005] A method for wireless communication by a UE is described. The method may include: transmitting an uplink message containing user data at the UE based on an idle mode of the UE, the uplink message including a first identifier associated with the UE via a set of bits; and receiving a downlink control information message in response to the uplink message, at least a portion of the downlink control information message being scrambled according to an RNTI, wherein the RNTI is one of a set of multiple RNTIs, the set of multiple RNTIs including a first RNTI associated with contention resolution and the first identifier.

[0006] A UE for wireless communication is described. The UE may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories. The one or more processors are capable of operating individually or jointly to execute the code to cause the UE to: transmit an uplink message containing user data at the UE based on an idle mode of the UE, the uplink message including a first identifier associated with the UE via a set of bits; and receive a downlink control information message in response to the uplink message, at least a portion of the downlink control information message being scrambled according to an RNTI, wherein the RNTI is one of a set of multiple RNTIs, the set of multiple RNTIs including a first RNTI associated with contention resolution and the first identifier.

[0007] Another UE for wireless communication is described. The UE may include: components for transmitting an uplink message containing user data at the UE based on an idle mode of the UE, the uplink message including a first identifier associated with the UE via a set of bits; and components for receiving a downlink control information message in response to the uplink message, at least a portion of the downlink control information message being scrambled according to an RNTI, wherein the RNTI is one of a set of multiple RNTIs, the set of multiple RNTIs including a first RNTI associated with contention resolution and the first identifier.

[0008] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: transmit an uplink message containing user data at the UE based on an idle mode of the UE, the uplink message including a first identifier associated with the UE via a set of bits; and receive a downlink control information message in response to the uplink message, at least a portion of the downlink control information message being scrambled according to an RNTI, wherein the RNTI is one of a set of RNTIs, the set of RNTIs including a first RNTI associated with contention resolution and the first identifier.

[0009] The methods described herein, examples of UEs and non-transitory computer-readable media may also include operations, features, components or instructions for decoding downlink control information messages based on RNTIs, wherein the RNTI may be a first RNTI and the first RNTI includes a first subset of the bit set of a first identifier.

[0010] In the methods described herein, and in some examples of UEs and non-transitory computer-readable media, the payload of a downlink control information message includes a second subset of the set of bits associated with a first identifier.

[0011] The methods described herein, UEs, and some examples of non-transitory computer-readable media may also include: operations, features, components, or instructions for resolving competition between the UE and at least a second UE, which may be based on the payload of a first RNTI and a downlink control information message.

[0012] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, uplink messages may be contention-based shared pre-configured uplink resource (PUR) request messages or early data transmission (EDT) request messages, and downlink control information messages may be used at least in part for contention resolution.

[0013] The methods described herein, examples of UEs and non-transitory computer-readable media may also include operations, features, components or instructions for decoding downlink control information messages based on RNTIs, wherein the RNTI may be a second RNTI, different from a first RNTI, in a set of multiple RNTIs.

[0014] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, the second RNTI can be a static RNTI.

[0015] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, downlink control information messages schedule uplink data transmission, downlink data messages, instruct the UE to perform random access procedures for transmitting user data, or combinations thereof.

[0016] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, uplink data transmissions may be scheduled for the UE to retransmit user data, downlink data messages may instruct the UE to switch to connected mode operation, or both.

[0017] The methods described herein, examples of UEs and nontransitory computer-readable media may also include operations, features, components or instructions for decoding downlink control information messages by: evaluating a first scrambling hypothesis associated with a first identifier in the search space, and evaluating a second scrambling hypothesis associated with a second RNTI in the search space.

[0018] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, when the uplink message is a contention-based shared PUR request message, the second RNTI may be based on the time and frequency resources associated with the uplink message, the multiplexing signature associated with the UE, the demodulation reference signal sequence, or a combination thereof.

[0019] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, when the uplink message is an EDT request message, the second RNTI may be a temporary cell radio network temporary identifier associated with the UE.

[0020] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, the size of the downlink control information message may differ from the size of the second downlink control information message, wherein the downlink control information message is associated with a first downlink control information format, which differs from the second downlink control information format associated with the second downlink control information message. In some cases, at least a portion of the second downlink control information message may be scrambled by an RNTI having the same value as the RNTI.

[0021] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the scrambling process associated with the decoded bits of the downlink control information message may differ from the scrambling process of the second downlink control information message, and at least a portion of the second downlink control information message may be scrambled by an RNTI having the same value as the RNTI.

[0022] In some examples of the methods described herein, UEs, and nontransitory computer-readable media, downlink control information messages include flags indicating whether the downlink control information message is associated with a contention resolution process.

[0023] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the downlink control information message includes one or more additional flags indicating whether the downlink control information message may be scheduling uplink data messages, whether the downlink control information message may be scheduling downlink data messages, or both.

[0024] The methods described herein, examples of UEs, and non-transitory computer-readable media may also include operations, features, components, or instructions for performing the following: avoiding monitoring of additional downlink transmissions when operating in idle mode after receiving a downlink control information message; and monitoring additional downlink transmissions based on a second uplink message indicating the transmission of second user data.

[0025] The methods described herein, examples of UEs, and non-transitory computer-readable media may also include operations, features, components, or instructions for performing the following: monitoring additional downlink transmissions during a first time period after receiving a downlink control information message, and entering a sleep period after the first time period.

[0026] The methods described herein, examples of UEs, and non-transitory computer-readable media may also include operations, features, components, or instructions for receiving system information block messages indicating downlink control configurations that indicate at least one of the following: the timing of the start of a search space associated with a downlink control information message, the start offset of a search space associated with a downlink control information message, or the number of repetitions associated with a downlink control information message.

[0027] The methods described herein, examples of UEs, and nontransitory computer-readable media may also include operations, features, components, or instructions for receiving system information block messages instructing uplink control configurations that instruct the UE to send acknowledgment messages in response to downlink control information messages or downlink data messages scheduled by downlink control information messages.

[0028] The methods described herein, examples of UEs, and non-transitory computer-readable media may also include operations, features, components, or instructions for receiving system information block messages that indicate the configuration of downlink data messages associated with data messages, wherein the downlink control information message schedules the data message.

[0029] The methods described herein, examples of UEs and non-transitory computer-readable media may also include operations, features, components or instructions for determining the number of repetitions for transmitting uplink messages based on downlink signal strength, transmit power limits associated with the UE, or both.

[0030] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, determining the number of repetitions based on downlink signal strength may include operations, features, components, or instructions for determining the number of repetitions for sending uplink messages based on downlink signal strength that satisfies one or more signal strength thresholds.

[0031] The methods described herein, examples of UEs, and non-transitory computer-readable media may also include operations, features, components, or instructions for selecting one or more resources from a set of resources associated with an uplink message for sending an uplink message based on determining the number of repetitions used to send the uplink message.

[0032] The methods described herein, examples of UEs, and non-transitory computer-readable media may also include operations, features, components, or instructions for receiving system information block messages that indicate a configuration associated with a downlink control information message, wherein the configuration may be active for a first narrowband IoT carrier associated with the UE.

[0033] The methods described herein, examples of UEs, and nontransitory computer-readable media may also include operations, features, components, or instructions for receiving a group common downlink control information message that includes an indication of a backoff period, wherein the uplink message may be sent via a timing selected from a set of timings according to the backoff period.

[0034] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, the indication of a backoff period includes an indication of a time period or an indication of the number of transmission opportunities.

[0035] The methods described herein, examples of UEs and non-transitory computer-readable media may also include operations, features, components, or instructions for receiving configurations that indicate a limit on transport block size and for selecting a transport block size from a set of candidate transport block sizes for sending uplink messages based on that limit.

[0036] A method for wireless communication by a network entity is described. The method may include: receiving an uplink message containing user data at the UE based on an idle mode of the UE, the uplink message including a first identifier associated with the UE via a set of bits; and transmitting a downlink control information message in response to the uplink message, at least a portion of the downlink control information message being scrambled according to an RNTI, wherein the RNTI is one of a set of multiple RNTIs, the set of multiple RNTIs including a first RNTI associated with contention resolution and the first identifier.

[0037] A network entity for wireless communication is described. The network entity may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors are capable of operating individually or jointly to execute the code to enable the network entity to: receive an uplink message containing user data at the UE based on an idle mode of the UE, the uplink message including a first identifier associated with the UE via a set of bits; and transmit a downlink control information message in response to the uplink message, at least a portion of the downlink control information message being scrambled according to an RNTI, wherein the RNTI is one of a set of multiple RNTIs, the set of multiple RNTIs including a first RNTI associated with contention resolution and the first identifier.

[0038] Another network entity for wireless communication is described. This network entity may include: components for receiving an uplink message containing user data at the UE based on an idle mode of the UE, the uplink message including a first identifier associated with the UE via a bit set; and components for transmitting a downlink control information message in response to the uplink message, at least a portion of the downlink control information message being scrambled according to an RNTI, wherein the RNTI is one of a set of multiple RNTIs, the set of multiple RNTIs including a first RNTI associated with contention resolution and the first identifier.

[0039] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: receive an uplink message containing user data at the UE based on an idle mode of the UE, the uplink message including a first identifier associated with the UE via a set of bits; and transmit a downlink control information message in response to the uplink message, at least a portion of the downlink control information message being scrambled according to an RNTI, wherein the RNTI is one of a set of multiple RNTIs, the set of multiple RNTIs including a first RNTI associated with contention resolution and the first identifier.

[0040] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the RNTI may be a first RNTI, and the first RNTI includes a first subset of the bit set of the first identifier.

[0041] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the payload of a downlink control information message includes a second subset of the set of bits associated with a first identifier.

[0042] Examples of the methods, network entities, and non-transitory computer-readable media described herein may also include: operations, features, components, or instructions for resolving competition between the UE and at least a second UE, which may be based on the payload of a first RNTI and a downlink control information message.

[0043] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, uplink messages may be contention-based shared PUR request messages or EDT request messages, and downlink control information messages may be used at least in part for contention resolution.

[0044] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, an RNTI may be a second RNTI, distinct from a first RNTI, within a set of multiple RNTIs.

[0045] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the second RNTI can be a static RNTI.

[0046] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, downlink control information messages schedule uplink data transmission, downlink data messages, instruct the UE to perform a random access procedure for transmitting user data, or a combination thereof.

[0047] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, uplink data transmission may be scheduled for the UE to retransmit user data, downlink data messages may instruct the UE to switch to connected mode operation, or both.

[0048] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, when the uplink message is a contention-based shared PUR request message, the second RNTI may be based on time and frequency resources associated with the uplink message, multiplexing signature associated with the UE, demodulation reference signal sequence, or a combination thereof.

[0049] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, when the uplink message is an EDT request message, the second RNTI may be a temporary cell radio network temporary identifier associated with the UE.

[0050] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the size of the downlink control information message may differ from the size of the second downlink control information message, wherein the downlink control information message is associated with a first downlink control information format, which differs from the second downlink control information format associated with the second downlink control information message. In some cases, at least a portion of the second downlink control information message may be scrambled by an RNTI having the same value as the RNTI.

[0051] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the scrambling process associated with the decoded bits of the downlink control information message may differ from the scrambling process of the second downlink control information message, and at least a portion of the second downlink control information message may be scrambled by an RNTI having the same value as the RNTI.

[0052] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, downlink control information messages include flags indicating whether the downlink control information message is associated with a contention resolution process.

[0053] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the downlink control information message includes one or more additional flags indicating whether the downlink control information message may be scheduling uplink data messages, whether the downlink control information message may be scheduling downlink data messages, or both.

[0054] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for sending system information block messages indicating downlink control configurations that indicate at least one of the following: the timing of the start of a search space associated with a downlink control information message, the start offset of a search space associated with a downlink control information message, or the number of repetitions associated with a downlink control information message.

[0055] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for sending system information block messages instructing uplink control configurations that instruct a UE to send an acknowledgment message in response to a downlink control information message or a downlink data message scheduled by a downlink control information message.

[0056] The methods, network entities, and some examples of nontransitory computer-readable media described herein may also include operations, features, components, or instructions for sending system information block messages that indicate the configuration of downlink data messages associated with data messages, wherein the downlink control information messages schedule the data messages.

[0057] Some examples of the methods, network entities, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending system information block messages that indicate a configuration associated with a downlink control information message, wherein the configuration may be active for a first narrowband IoT carrier associated with the UE.

[0058] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for sending group common downlink control information messages indicating a backoff period, wherein the uplink message may be sent via a timing selected from a set of timings according to the backoff period.

[0059] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the indication of a backoff period includes an indication of a time period or an indication of the number of times a transmission occurs.

[0060] The methods, network entities, and some examples of nontransitory computer-readable media described herein may also include operations, features, components, or instructions for sending configurations that indicate a limit on transport block size, wherein uplink messages may be sent using transport block sizes from a set of candidate transport block sizes in accordance with the limit on transport block size. Attached Figure Description

[0061] Figure 1Examples of improved wireless communication systems for mobile-initiated data, according to one or more aspects of this disclosure, are shown.

[0062] Figure 2 Examples of improved wireless communication systems for mobile-initiated data, according to one or more aspects of this disclosure, are shown.

[0063] Figure 3 An example of an improved process flow for mobile-initiated data is shown, supporting one or more aspects of this disclosure.

[0064] Figure 4 and Figure 5 A block diagram of a device supporting improvements for mobile-initiated data according to one or more aspects of this disclosure is shown.

[0065] Figure 6 A block diagram is shown that supports an improved communication manager for mobile-initiated data according to one or more aspects of this disclosure.

[0066] Figure 7 A diagram is shown illustrating a system including a device that supports improvements for mobile-initiated data, according to one or more aspects of this disclosure.

[0067] Figure 8 and Figure 9 A block diagram of a device supporting improvements for mobile-initiated data according to one or more aspects of this disclosure is shown.

[0068] Figure 10 A block diagram is shown that supports an improved communication manager for mobile-initiated data according to one or more aspects of this disclosure.

[0069] Figure 11 A diagram is shown illustrating a system including a device that supports improvements for mobile-initiated data, according to one or more aspects of this disclosure.

[0070] Figures 12 to 15 A flowchart illustrating an improved method for supporting mobile-initiated data according to one or more aspects of this disclosure is shown. Detailed Implementation

[0071] In some systems, a UE can initiate uplink transmission while operating in idle mode. In some cases, the UE can use EDT (Early Data Transmission) technology, and the UE can include user data in its Early Data Transmission Request (EDT) to a network entity. By including user data in the EDT, the UE can reduce the total number of messages sent to initiate uplink transmission compared to initiating a Random Access Channel (RACH) procedure. In some examples, the network entity can send an acknowledgment message in response. However, the network entity may be managing communication with multiple UEs, and sending acknowledgment messages can incur significant overhead. In some examples, to reduce this overhead, the UE can use PUR (Programming Uplink Request) technology to initiate uplink transmission, where the UE can transmit uplink data in idle mode via uplink resources configured for the UE when it was previously in connected mode. However, if the UE did not previously have uplink resources configured, this may prevent the UE from transmitting uplink data. Therefore, additional technologies may be needed to enable the UE to transmit data in idle mode.

[0072] Based on the examples described herein, a UE may use a contention-based shared PUR procedure (e.g., an EDT procedure without RACH) to transmit user data while in idle mode. In some examples, one or more UEs may be configured with a resource pool for transmitting uplink user data (e.g., mobile-initiated data) on a contention-based basis. Since these resources may be shared among multiple UEs, conflicts may occur, and network entities may perform contention resolution to resolve these conflicts. In some examples, contention resolution may be performed by network entities using DCI messages, which significantly reduces overhead compared to using downlink shared channel messages. In some examples, since the payload of the DCI message may be limited, a portion of the contention resolution identifier (CR ID) may be indicated via scrambling of the DCI message (e.g., cyclic redundancy check (CRC) scrambling). For example, a subset of bits in the CR ID (e.g., least significant bit, most significant bit) may be used as an RNTI (e.g., a UE-specific RNTI) to scramble the DCI message, and the remaining subset of bits in the CR ID may be included in the payload of the DCI message. In some cases, such as if the DCI message in response to uplink user data is intended for purposes other than contention resolution, a different second RNTI (e.g., a static RNTI, a non-UE-specific RNTI) can be used to scramble the DCI message. Therefore, network entities can send DCI messages in response to uplink user data, which reduces the network entity's transmission overhead and saves downlink resources.

[0073] The aspects of this disclosure are first described in the context of a wireless communication system. These aspects are further described in the context of a process flow. Reference is made to apparatus diagrams, system diagrams, and flowcharts relating to improvements for mobile-initiated data.

[0074] Figure 1 Examples of an improved wireless communication system 100 supporting mobile-initiated data according to one or more aspects of this disclosure are shown. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0075] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, etc. In some examples, network entity 105 and UE 115 may wirelessly communicate via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish one or more communication links 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0076] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Some example UE 115s are illustrated herein. The UE 115 described herein can be able to support various types of devices (such as, e.g., ...). Figure 1 It communicates with other UEs (115 or network entity 105) as shown.

[0077] As described herein, a node in the wireless communication system 100 (which may be referred to as a network node or wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, apparatus, device, computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be UE 115. As another example, a node may be network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc., may include disclosures of UE 115, network entity 105, device, equipment, computing system, etc., as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.

[0078] In some examples, network entity 105 may communicate with core network 130, communicate with each other, or both. For example, network entity 105 may communicate with core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entities 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entities 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. The backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof, or may include one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 may communicate with the core network 130 via communication link 155.

[0079] One or more network entities in network entity 105 described herein may include or be referred to as base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, node B, eNodeB (eNB), next-generation node B or gigabit node B (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home node B, home evolution node B, or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture that may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as base station 140).

[0080] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC, a non-real-time RIC), a service management and orchestration (SMO) 180 system, or any combination thereof. 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 in a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0081] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 can connect to one or more DU 165 or RU 170, and one or more DU 165 or RU 170 can host lower protocol layers, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Medium Access Control (MAC) layer) functionality and signaling, and each can be at least partially controlled by CU 160. Additionally or alternatively, a protocol stack functional split can be employed between DU 165 and RU 170, such that DU 165 can support one or more layers of the protocol stack, and RU 170 can support one or more different layers of the protocol stack. DU 165 can support one or more different cells (e.g., via one or more RU 170). In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by different of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by the corresponding network entities 105 communicating via such communication links.

[0082] In a wireless communication system (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB node 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DU 165s or one or more RU 170s may be partially controlled by one or more CU 160s associated with donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 of IAB node 104. (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0083] When applying the techniques described herein to a decomposed RAN architecture, one or more components of the decomposed RAN architecture can be configured to support improvements for mobile-initiated data as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

[0084] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or any other suitable term, wherein "device" may also be referred to as a cell, station, terminal, or client, etc. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0085] The UE 115 described herein can communicate with various types of devices, such as other UEs 115 that sometimes act as relays, network entities 105, and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

[0086] UE 115 and network entity 105 can wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources having a defined physical layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating carrier operation, user data, or other signaling. Wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN’s network entity 105 (e.g., base station 140, CU160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities 105).

[0087] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0088] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, of which It can represent the supported subcarrier spacing, and This can represent the supported Discrete Fourier Transform (DFT) size. The time interval of the communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0089] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may be further divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

[0090] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0091] Depending on the technology, carriers can be used to multiplex physical channels for communication. One or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used, for example, to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel can be defined by a set of symbol periods and can extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates can refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include: a shared search space set configured to transmit control information to multiple UEs 115, and a UE-specific search space set used to transmit control information to a specific UE 115.

[0092] Network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used (e.g., using a carrier) to communicate with network entity 105 and may be associated with an identifier used to distinguish adjacent cells (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID), or other identifier). In some examples, a cell may also refer to a coverage area 110 or a portion of coverage area 110 (e.g., a sector) in which a logical communication entity operates. Depending on various factors such as the capabilities of network entity 105, the range of such cells may be from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be a building, a subset of buildings, or external space between or overlapping coverage areas 110, or may include buildings, subsets of buildings, or external space between or overlapping coverage areas.

[0093] In some examples, a carrier can support multiple cells and can be configured with different cells based on different protocol types that provide access for different types of devices (e.g., MTC, Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB)).

[0094] In some examples, network entity 105 (e.g., base station 140, RU 170) may be mobile, and thus provide communication coverage to mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 use the same or different radio access technologies to provide coverage for various coverage areas 110.

[0095] Some UE 115 devices (such as MTC or IoT devices) can be low-cost or low-complexity devices and can provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that allow devices to communicate with each other or with network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices with integrated sensors or meters to measure or acquire information and relay such information to a central server or application that uses the information or presents it to people interacting with the application. Some UE 115 devices may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geographic event monitoring, queue management and tracking, remote security sensing, physical access control, and transaction-based commercial toll collection.

[0096] Some UE 115s can be configured to operate in reduced-power modes, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not involve concurrent transmission and reception). In some examples, half-duplex communication can be performed at reduced peak rates. Other power-saving techniques for UE 115s include entering a power-saving deep sleep mode when not engaged in active communication, operating with limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UE 115s can be configured to operate using a narrowband protocol type associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a carrier's guard band, or outside a carrier.

[0097] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communication may include private or group communication and may be supported by one or more services, such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritizing services, and such services may be used for public safety or general business applications. The terms “ultra-reliable,” “low-latency,” and “ultra-reliable low-latency” are used interchangeably herein.

[0098] In some examples, UE 115 may be configured to support direct communication with other UE 115s via device-to-device (D2D) communication link 135 (e.g., according to peer-to-peer (P2P), D2D, or sidelink protocols). In some examples, one or more UE 115s performing D2D communication in a group may be within the coverage area 110 of network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured (e.g., scheduled by network entity 105). In some examples, one or more UE 115s in this group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some examples, the group of UE 115s communicating via D2D communication may support a one-to-many (1:M) system, where each UE 115 transmits to each of the other UE 115s in the group. In some examples, network entity 105 may facilitate the scheduling of resources used for D2D communication. In other examples, D2D communication may be performed between UEs 115 without involving network entity 105.

[0099] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 can be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), access and mobility management function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function (UPF)) for routing packets or interconnecting to external networks. The control plane entity manages non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with core network 130. User IP packets can be transferred through user plane entities, which provide IP address allocation and other functions. User plane entities can connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0100] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the area from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) band or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer wavelengths in the lower frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than 100 km).

[0101] Wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may use unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ Licensed Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology. When operating with unlicensed RF spectrum, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed bands may be combined with component carriers operating with licensed bands based on carrier aggregation configurations (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0102] Network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some examples, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0103] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a specific orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

[0104] UE 115 and network entity 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correctly receiving data via communication links (e.g., communication link 125, D2D communication link 135). HARQ can include a combination of error detection (e.g., using CRC), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device can support same-slot HARQ feedback, in which case the device can provide HARQ feedback in a specific time slot for data received via a previous symbol in that time slot. In some other examples, the device can provide HARQ feedback in subsequent time slots or according to a different time interval.

[0105] In some examples, for UE 115 to perform mobile-initiated data transmission, UE 115 can use EDT or PUR techniques to reduce latency and overhead (e.g., compared to using RACH). For example, EDT can reduce the number of steps (e.g., transmissions) that UE 115 performs (e.g., performed by UE 115 and network entity 105) to transmit uplink user data from idle mode (e.g., from five steps to three steps). Similarly, by allowing UE 115 to transmit uplink data from idle mode in resources previously configured for UE 115, PUR can further reduce the number of steps performed (e.g., to one step). In some examples, EDT allows contention-based transmission, where UE 115 can compete for resources with other UE 115; while PUR allows contention-free transmission because UE 115 can transmit on resources dedicated to it, which may have been previously configured for UE 115 when it was in connected mode.

[0106] In some cases, because contention-free PUR technology may involve resources configured for UE 115 while UE 115 is in connected mode, contention-free PUR technology may not allow UE 115 to send mobile initiation data if UE 115 has not previously been configured with resources (e.g., if UE 115 recently joined the network). However, EDT technology may incur significant overhead at network entity 105. For example, network entity 105 may be managing communications for multiple UE 115. Network entity 105 may be configured to send an acknowledgment message (e.g., per UE Msg4 ACK) in response to mobile initiation data received from the respective UE 115 (e.g., via Msg3), and this acknowledgment message may include downlink data messages (e.g., Physical Downlink Shared Channel (PDSCH) messages) and downlink control messages (e.g., Physical Downlink Control Channel (PDCCH) messages). Network entity 105 may be managing communications with various UEs 115, so acknowledgment messages can be overhead-intensive in terms of downlink resource availability and utilization, especially in NB-IoT scenarios where bandwidth may be scarce. Therefore, different technologies may be needed for sending mobile-initiated data.

[0107] As described in the examples herein, UE 115 can use a contention-based shared PUR procedure (e.g., a RACH-free EDT procedure) to transmit mobile-initiated data (e.g., user data) while in idle mode. The contention-based shared PUR procedure allows UE 115 to transmit uplink data via pre-configured resources. However, compared to contention-free PUR techniques, these resources can be shared among multiple UE 115s and are not necessarily dedicated to a specific UE 115. For example, one or more UE 115s can be configured (e.g., via a system information block in broadcast signaling) to have a resource pool for transmitting uplink user data (e.g., mobile-initiated data) on a contention-based basis. This resource pool can be configured for one or more UE 115s without these UE 115s previously operating in connected mode, thus providing flexibility for transmitting uplink resources.

[0108] Because resources used for contention-based shared PUR procedures may be shared among multiple UEs 115, conflicts may occur, and network entity 105 may perform contention resolution to resolve these conflicts. In some examples, contention resolution may be performed by the network entity using DCI messages, which significantly reduces overhead compared to using downlink shared channel (e.g., PDSCH) messages. However, the payload of a DCI message may be limited compared to the payload of a downlink shared channel message, and the payload of a DCI message may not be large enough to include the entire identifier (e.g., CR ID) associated with contention resolution. In some examples, a portion of the identifier may be indicated via scrambling of the DCI message (e.g., CRC scrambling). For example, a subset of the identifier's bits (e.g., least significant bits) may be used as an RNTI to scramble the DCI message, and the remaining subset of the identifier's bits may be included in the payload of the DCI message.

[0109] In some cases, if a DCI message responding to uplink user data is intended for purposes other than contention resolution, a different second RNTI can be used to scramble the DCI message. For example, the DCI message can be used to initiate a retransmission of the corresponding uplink transmission by UE 115 to switch UE 115 from using one access technology to another (e.g., from contention-based shared PUR or EDT to using RACH), or to instruct UE 115 to switch to connected mode. Therefore, UE 115 can monitor the DCI message based on scrambling assumptions based on the first and second RNTIs, and UE 115 can determine the purpose of the DCI message based on which scrambling assumption succeeds. Thus, network entity 105 and UE 115 can operate using contention-based shared PUR technology, thereby reducing overhead at network entity 105.

[0110] Figure 2 An example of an improved wireless communication system 200 supporting mobile-initiated data according to one or more aspects of this disclosure is shown. The wireless communication system 200 illustrates communication between UE 115-a, UE 115-b and network entity 105-a, which may be as referenced herein. Figure 1 Examples of the corresponding devices described.

[0111] UE 115-a and UE 115-b may transmit user data 220 (e.g., mobile-initiated data) via uplink message 205 using contention-based shared PUR technology or RACH-free EDT technology, which may support user data 220 transmission based on (e.g., when UE 115-a is operating in) an idle mode. In some examples, such as for contention-based PUR, resource pools may be defined (e.g., by network entity 105-a) that include resources for uplink transmission of user data 220 by one or more UE 115s (such as UE 115-a and UE 115-b). For example, network entity 105-a may be associated with multiple resource pools, and each resource pool may potentially use multiplexing techniques such as non-orthogonal multiple access (NOMA) and orthogonal coverage code (OCC) to define resources for one or more UE 115s. In some examples, each resource pool may be associated with a corresponding demodulation reference signal (DMRS) pool, and each DMRS in the pool may correspond to a corresponding resource in the resource pool to enable UE 115 to transmit uplink message 205 via that resource. In some examples, UE 115-a, UE 115-b, or both may receive an indication of the configured resource pool via a System Information Block (SIB) sent by network entity 105-a.

[0112] In some examples, network entity 105-a may send a message in response to uplink message 205. For example, uplink message 205 may be a request message (e.g., an EDT request message), and network entity 105-a may be configured to send a response to such a request message. Additionally or alternatively, if the reuse capacity of a resource in the resource pool is exceeded (e.g., if too many UEs 115 send uplink messages 205 via that resource), network entity 105-a may detect a failure because it may be unable to decode multiple uplink messages 205. Therefore, network entity 105-a may send a message to perform a contention resolution procedure. In some examples, sending a PDSCH message may be more downlink resource intensive than a PDCCH message (e.g., a factor of 5). Therefore, it may be desirable to send a response (e.g., for performing contention resolution) via a DCI message (e.g., a PDCCH message) to reduce downlink overhead at network entity 105-a.

[0113] According to the examples described herein, network entity 105-a may perform contention resolution via DCI messages (e.g., PDCCH messages using a Layer 1-based mechanism). In some examples, in response to an uplink message 205-a sent by UE 115-a, network entity 105-a may encode an identifier 210 (e.g., CR ID) associated with contention resolution within the DCI message 215 for contention resolution. In some examples, the identifier may be a high-level network identifier previously configured for UE 115-a, and UE 115-a may include the identifier 210 in the uplink message 205 (e.g., via the payload of the uplink message 205). However, in some cases, the identifier 210 (e.g., it may be 48 bits) may be too large to be encoded within the payload of the DCI message 215 (e.g., in some implementations, it may be 25 bits to reduce overhead).

[0114] In some examples, to encode identifier 210 within DCI message 215, network entity 105-a may embed a portion of identifier 210 within scrambling (e.g., CRC scrambling) for DCI message 215. For example, a first subset of bits of identifier 210 (e.g., the 16 least significant bits of identifier 210) may form a first RNTI (e.g., a UE-specific RNTI). Network entity 105-a may use the first RNTI to scramble DCI message 215 (e.g., CRC scrambling of DCI message 215). Network entity 105-a may include the remaining second subset of bits of identifier 210 within the payload of DCI message 215. Therefore, UE 115-a may at least monitor DCI message 215 scrambled using the first RNTI. Thus, UE 115-a may receive DCI message 215 indicating identifier 210, which may indicate that DCI message 215 is associated with contention resolution. Network entity 105-a may similarly respond to uplink message 205-b by sending DCI message 215 scrambled according to RNTI associated with UE 115-b.

[0115] In some examples, network entity 105-a may send DCI message 215 for different purposes in response to uplink message 205-a from UE 115-a. For example, network entity 105-a may instruct UE 115-a to perform retransmission of user data 220 (e.g., HARQ retransmission) via DCI message 215. In some cases, DCI message 215 may schedule or instruct uplink permission for retransmission (e.g., Physical Uplink Shared Channel (PUSCH) permission). Additionally or alternatively, DCI message 215 may instruct UE 115-a to change the access technology used to transmit user data 220. For example, DCI message 215 may instruct UE 115-a to switch from using a contention-based shared PUR (e.g., or no RACH EDT or another technology) to using a different access technology, such as a RACH procedure (e.g., a 4-step RACH procedure). Additionally or alternatively, DCI message 215 may instruct UE 115-a to transition from idle mode to connected mode. In some cases, DCI message 215 may schedule downlink grant (e.g., PDSCH) that may indicate Radio Resource Control (RRC) configuration (e.g., similar to an RRC configuration indicated via Msg4).

[0116] However, in some cases, if DCI message 215 is used for one of these purposes, the identifier 210 associated with contention resolution may not be used for DCI message 215. For example, if uplink message 205 fails to be decoded by network entity 105-a, network entity 105-a may send DCI message 215. However, for example, network entity 105-a may not have already obtained the identifier 210 from uplink message 205. Therefore, a second RNTI may be used to facilitate the sending of DCI message 215 for non-contention resolution purposes.

[0117] For example, network entity 105-a may scramble DCI message 215 using a first RNTI or a second RNTI based on the purpose of DCI message 215 (e.g., scrambling the CRC of DCI message 215). For example, for contention resolution, the first RNTI, which is a subset of identifier 210, may be used to scramble DCI message 215. For other purposes, such as scheduling the retransmission of user data 220, instructing UE 115-a to change its access technology, causing UE 115-a to switch (e.g., switch) to a connection mode, or for other purposes, the second RNTI may be used to scramble DCI message 215.

[0118] In some examples, the second RNTI may be based on the access technology being used by UE 115-a. For example, for a contention-based shared PUR, the second RNTI may be based on time resources, frequency resources, or both configured for transmitting uplink message 205. Additionally or alternatively, the second RNTI may be based on the multiplexing signature used (such as OCC for shared resources) or on the DMRS sequence associated with the resource. Thus, the second RNTI may be independent of identifier 210. In some examples, such as for EDT technologies (e.g., RACH-free EDT technology), the second RNTI may be a temporary cell RNTI (TC-RNTI) associated with UE 115-a, which may have been previously configured for UE 115-a (e.g., by network entity 105-a) and may be known to both UE 115-a and network entity 105-a.

[0119] Since DCI message 215 can be scrambled by either the first RNTI or the second RNTI, and it is expected that DCI message 215 scrambled by either RNTI will arrive in the same search space without PDCCH candidate splitting for each RNTI, UE 115-a can use two different scrambling assumptions to monitor DCI message 215. For example, UE 115-a can attempt to decode DCI message 215 by evaluating a first scrambling assumption associated with the first RNTI. Additionally or alternatively, UE 115-a can attempt to decode DCI message 215 by evaluating a second scrambling assumption associated with the second RNTI. In some examples, UE 115-a can attempt to decode DCI message 215 using one of the scrambling assumptions, and if decoding fails, UE 115-a can attempt to decode DCI message 215 using another of the scrambling assumptions. In some cases, if UE 115-a fails to decode DCI message 215, DCI message 215 may be intended for use with a different UE 115 (e.g., UE 115-b).

[0120] UE 115-a may determine the purpose of DCI message 215 based on which scrambling assumption is successfully performed. For example, if UE 115-a successfully decodes DCI message 215 using a first RNTI, UE 115-a may determine that DCI message 215 is intended for contention resolution. Alternatively, if UE 115-a successfully decodes DCI message 215 using a second RNTI, UE 115-a may determine that DCI message 215 is intended for a purpose different from contention resolution, such as the purpose described herein. In some examples, DCI message 215 may include flags indicating whether DCI message 215 is associated with contention resolution or with other purposes. Additionally or alternatively, DCI message 215 may include one or more flags indicating the purpose of DCI message 215 (e.g., between scheduling the retransmission of user data 220, scheduling PDSCH to transition UE 115-a to connected mode, transitioning UE 115-a to another access technology, contention resolution, or other purposes).

[0121] In some examples, masking DCI message 215 from connected mode UE 115 (e.g., legacy connected mode UE 115) may be beneficial because the behavior indicated by DCI message 215 can be specific to idle mode UE 115-a. For example, the first or second RNTI used to scramble DCI message 215 may match (e.g., have the same value) RNTIs associated with different UE 115s (e.g., legacy UE 115, connected mode UE 115), such as cell RNTIs (C-RNTIs). Therefore, it would be beneficial if different UE 115s could not decode DCI message 215. In some examples, in order to mask DCI message 215 from connected mode UE 115 (e.g., legacy UE 115), DCI message 215 may have a different size relative to other DCI messages with different DCI formats (e.g., legacy DCI messages, connected mode DCI messages). Alternatively or additionally, the decoding bits (e.g., CRC bits) of DCI message 215 may be scrambled using a different scrambling technique than that used in DCI messages sent to connected mode UE 115 (e.g., using a DCI format different from the DCI format of DCI message 215). Therefore, connected mode UE 115 (e.g., conventional connected mode UE 115) may not need to decode DCI message 215, thereby avoiding potential decoding confusion for connected mode UE 115.

[0122] In some examples, after receiving DCI message 215 (e.g., a Layer 1 response message) from network entity 105-a, UE 115-a may be configured to stop monitoring for further downlink messages (e.g., in idle mode) until UE 115-a has more user data 220 to transmit. Alternatively, UE 115-a may be configured to monitor downlink transmission for a certain amount of time after receiving DCI message 215. For example, UE 115-a may be configured with a certain amount of time (e.g., in seconds, symbols, or transmission timing) after which, if no additional downlink messages are received, UE 115-a may initiate a sleep process.

[0123] In some cases, UE 115-a may receive an SIB indicating the PDCCH configuration associated with DCI message 215. For example, network entity 105-a may send a message including an information element (e.g., the contention-PUR-PDCCH-Config-r19 information element) that includes one or more fields indicating the search space configuration (e.g., starting slot or subframe, starting offset), the limit (e.g., maximum) number of PDCCH repetitions (e.g., for DCI message 215), and other parameters (e.g., those defined in the information element PUR-MPDCCH-Config-r16 for contention-free PURs).

[0124] In some examples, UE 115-a may also receive an SIB (e.g., or the same SIB) indicating the Physical Uplink Control Channel (PUCCH) configuration. In some examples, the PUCCH configuration configures UE 115-a to send acknowledgment messages (e.g., ACK or NACK) for DCI message 215 or for PDSCH scheduled by DCI message 215. In some cases (e.g., in NB-IoT), the PDCCH-related configuration, the PUCCH-related configuration, or both may differ depending on the carrier. For example, the configuration may differ depending on whether UE 115-a operates on an anchor carrier (e.g., an anchor NB-IoT carrier) or a non-anchor carrier (e.g., a non-anchor NB-IoT carrier). In some examples, the configuration may be active for one or more carriers (such as NB-IoT carriers), while another configuration may be active for other carriers (e.g., other NB-IoT carriers).

[0125] Additionally or alternatively, UE 115-a may receive an SIB (e.g., the same SIB or a different SIB) indicating the PDSCH configuration. The PDSCH configuration may configure one or more parameters for UE 115-a to receive downlink data messages (e.g., PDSCH messages), which may be scheduled by DCI message 215. In some examples, the PDSCH configuration may indicate a limit (e.g., maximum) number of repetitions associated with the downlink data message, whether frequency hopping is enabled for the downlink data message, or other parameters.

[0126] In some examples, such as for contention-based shared PURs, different coverage levels may exist for resources configured via SIBs. Each coverage level may be associated with a different number of repetitions transmitted via that resource. In some cases, UE 115-a may determine the coverage level to use (e.g., the number of repetitions) based on downlink signal strength. For example, UE 115-a may be configured with one or more reference signal received power (RSRP) thresholds (e.g., signal strength thresholds) for selecting the coverage level (e.g., the number of repetitions), and these RSRP thresholds may have different values ​​than RSRP thresholds not associated with contention-based shared PURs (e.g., RSRP thresholds for physical RACH procedures). Therefore, UE 115-a may determine which coverage level to use based on whether the measured RSRP meets one or more RSRP thresholds (e.g., at, above, below, or between one or more RSRP thresholds). Additionally or alternatively, UE 115-a may determine the coverage level to use based on the power level of UE 115-a. For example, UE 115-a may determine the coverage level based on the UE 115-a's limited (e.g., maximum) transmit power, where the lower limit transmit power may be associated with a lower number of repetitions and the upper limit transmit power may be associated with a higher number of repetitions.

[0127] In some examples, such as for a contention-based shared PUR, network entity 105-a may send a group common DCI message, which may be associated with a different RNTI, a different search space, or both, relative to DCI message 215. The group common DCI message may indicate a backoff indication for congestion control, and UEs 115-a and UE 115-b may monitor the group common DCI message to obtain the backoff indication (e.g., before or after sending uplink message 205). In some examples, the backoff indication may indicate a backoff period, which may be physical time (e.g., in seconds), the number of transmission opportunities, or another time-domain metric. UE 115-a may receive the group common DCI and randomly select time resources for sending uplink message 205-a based on the backoff period (e.g., within or after the backoff period). In some cases, for example, sending UEs 115 may each randomly select time resources within the backoff period, thus distributing the transmission, which may facilitate reception by network entity 105-a. In some examples, for EDT technology, the backoff process can be provided by the Random Access Report (RAR).

[0128] In some cases, network entity 105-a may send a message indicating a limit (e.g., a maximum) transport block size, and network entity 105-a will perform blind decoding of uplink message 205 for that limit transport block size. For example, network entity 105-a may indicate the limit transport block size to UE 115-a. In some examples, UE 115-a may select a transport block size from a set of candidate transport block sizes based on the limit transport block size, and perform uplink message 205-a transmission based on the selected transport block size.

[0129] Figure 3 An example of a process flow 300 supporting improvements for mobile-initiated data according to one or more aspects of this disclosure is shown. Process flow 300 illustrates communication between network entity 105-b and UE 115-c, which may be as described in reference... Figure 1 and Figure 2 Examples of the corresponding devices described. In some examples, steps may be added to or omitted from process flow 300. Additionally or alternatively, some steps may be performed in a different order than shown.

[0130] At 305, network entity 105-b may send an SIB indicating the downlink control configuration. In some examples, the downlink control configuration may indicate the start timing and start offset of the search space associated with a DCI message to be sent in response to an uplink message sent by UE 115-c. Additionally or alternatively, the downlink control configuration may indicate the number of repetitions associated with the transmission of the DCI message.

[0131] In some examples, the SIB (e.g., or a different SIB) may indicate the uplink control configuration. The uplink control configuration may instruct the UE 115-c to send an acknowledgment message in response to a DCI message or in response to a downlink data message scheduled by a DCI message.

[0132] At 310, network entity 105-b may send group common DCI messages to UE 115-c and, in some examples, to other UEs 115. The group common DCI message may indicate a backoff period associated with an uplink transmission performed by UE 115-c.

[0133] At 315, UE 115-c can select the transport block size used to send uplink messages. In some examples, UE 115-c can receive an indication of a limited transport block size from network entity 105-b. UE 115-c can then select the transport block size for sending uplink messages from a set of candidate transport block sizes based on the limited transport block size.

[0134] At 320, UE 115-c may send an uplink message when operating in idle mode. The uplink message may indicate user data at UE 115-c, and may include an identifier associated with UE 115-c via a first bit set. In some examples, the uplink message may be sent based on a selected transport block size. In some cases, such as when UE 115-c receives an indication for a backoff period, the uplink message may be sent via an opportunity from an opportunity set based on the backoff period. In some examples, the uplink message may be a contention-based shared PUR request message or an EDT request message.

[0135] At 325, network entity 105-b may send a DCI message in response to an uplink message. In some examples, at least a portion of the DCI message (e.g., CRC bits) may be scrambled according to an RNTI from among multiple RNTIs. In some examples, the multiple RNTIs may include a first RNTI associated with contention resolution (e.g., a UE-specific RNTI), and the first RNTI may be a first subset of the set of bits of an identifier.

[0136] At 330, UE 115-c can decode DCI messages based on RNTI. In some examples, the RNTI can be a first RNTI, which can be multiple least significant bits of an identifier. In other examples, the RNTI can be a second RNTI among multiple RNTIs, such as a static RNTI, which indicates that the DCI message is used for non-contention resolution purposes. In some examples, to decode a DCI message, UE 115-c can evaluate a first scrambling hypothesis associated with the first RNTI in the search space and a second scrambling hypothesis associated with the second RNTI in the search space.

[0137] At 335, UE 115-c can monitor additional downlink transmissions during the first time period after receiving a DCI message. In some examples, UE 115-c can enter a sleep period after the first time period.

[0138] Therefore, network entity 105-b can convey response messages to uplink messages via DCI (e.g., via Layer 1 signaling), which significantly reduces the overhead at network entity 105-b compared to sending response messages via PDSCH.

[0139] Figure 4 A block diagram 400 is shown of a device 405 supporting improvements for mobile-initiated data according to one or more aspects of this disclosure. Device 405 may be an example of aspects of UE 115 as described herein. Device 405 may include a receiver 410, a transmitter 415, and a communications manager 420. Device 405, or one or more components of device 405 (e.g., receiver 410, transmitter 415, and communications manager 420), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described technologies. Each of these components may communicate with each other (e.g., via one or more buses).

[0140] Receiver 410 may provide components for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to improvements for mobile-initiated data). Information may be passed to other components of device 405. Receiver 410 may utilize a single antenna or a collection of antennas.

[0141] Transmitter 415 may provide components for transmitting signals generated by other components of device 405. For example, transmitter 415 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to improvements for mobile-initiated data), user data, control information, or any combination thereof. In some examples, transmitter 415 may be co-located with receiver 410 in a transceiver module. Transmitter 415 may utilize a single antenna or a collection of multiple antennas.

[0142] The communication manager 420, receiver 410, transmitter 415, or various combinations thereof, or various components thereof, may be examples of components used to perform the various aspects of the improvements for mobile-initiated data described herein. For example, the communication manager 420, receiver 410, transmitter 415, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0143] In some examples, the communication manager 420, receiver 410, transmitter 415, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of the following: a processor, digital signal processor (DSP), central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, microcontroller, discrete gate or transistor logic component, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0144] Additionally or alternatively, the communication manager 420, receiver 410, transmitter 415, or various combinations or components thereof may be implemented in code (e.g., as communication management software or firmware) executed by at least one processor. If implemented in code executed by at least one processor, the functionality of the communication manager 420, receiver 410, transmitter 415, or various combinations or components thereof may be performed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured, either individually or collectively, as components for performing the functions described in this disclosure).

[0145] In some examples, the communication manager 420 may be configured to use a receiver 410, a transmitter 415, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 420 may receive information from the receiver 410, transmit information to the transmitter 415, or integrate with the receiver 410, the transmitter 415, or both to acquire information, output information, or perform various other operations as described herein.

[0146] According to the examples disclosed herein, the communication manager 420 may support wireless communication. For example, the communication manager 420 is capable of, configured to, or operable to support components for: transmitting an uplink message containing user data at the UE based on the UE's idle mode, the uplink message including a first identifier associated with the UE via a bit set. The communication manager 420 is capable of, configured to, or operable to support components for: receiving a downlink control information message in response to the uplink message, at least a portion of the downlink control information message being scrambled according to an RNTI, wherein the RNTI is one of a set of multiple RNTIs, the set of multiple RNTIs including a first RNTI associated with contention resolution and a first identifier.

[0147] By including or configuring a communication manager 420 according to the examples described herein, device 405 (e.g., at least one processor that controls or otherwise couples to receiver 410, transmitter 415, communication manager 420, or a combination thereof) can support techniques for reducing overhead associated with the transmission of mobile-initiated data and resolving competition caused by transmissions from multiple devices.

[0148] Figure 5 A block diagram 500 of a device 505 supporting improvements for mobile-initiated data according to one or more aspects of this disclosure is shown. Device 505 may be an example of aspects of device 405 or UE 115 as described herein. Device 505 may include a receiver 510, a transmitter 515, and a communication manager 520. Device 505, or one or more components of device 505 (e.g., receiver 510, transmitter 515, and communication manager 520), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0149] Receiver 510 may provide components for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to improvements for mobile-initiated data). Information may be passed to other components of device 505. Receiver 510 may utilize a single antenna or a collection of antennas.

[0150] Transmitter 515 may provide components for transmitting signals generated by other components of device 505. For example, transmitter 515 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to improvements for mobile-initiated data), user data, control information, or any combination thereof. In some examples, transmitter 515 may be co-located with receiver 510 in a transceiver module. Transmitter 515 may utilize a single antenna or a collection of multiple antennas.

[0151] Device 505 or its various components may be examples of parts used to perform the various aspects of the improvements for mobile-initiated data described herein. For example, communication manager 520 may include user data component 525, DCI manager 530, or any combination thereof. Communication manager 520 may be examples of aspects of communication manager 420 as described herein. In some examples, communication manager 520 or its various components may be configured to use receiver 510, transmitter 515, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 520 may receive information from receiver 510, transmit information to transmitter 515, or be integrated in combination with receiver 510, transmitter 515, or both to acquire information, output information, or perform various other operations as described herein.

[0152] According to the examples disclosed herein, the communication manager 520 may support wireless communication. The user data component 525 is capable of, configured to, or operable to support components for transmitting an uplink message containing user data at the UE based on the UE's idle mode, the uplink message including a first identifier associated with the UE via a bit set. The DCI manager 530 is capable of, configured to, or operable to support components for receiving a downlink control information message in response to an uplink message, at least a portion of the downlink control information message being scrambled according to an RNTI, wherein the RNTI is one of a set of multiple RNTIs, the set of multiple RNTIs including a first RNTI associated with contention resolution and a first identifier.

[0153] Figure 6A block diagram 600 is shown of a communication manager 620 supporting improvements for mobile-initiated data according to one or more aspects of this disclosure. The communication manager 620 may be an example of aspects of the communication manager 420, communication manager 520, or both as described herein. The communication manager 620 or its various components may be examples of parts for performing the various aspects of the improvements for mobile-initiated data as described herein. For example, the communication manager 620 may include a user data component 625, a DCI manager 630, an RNTI component 635, a monitoring component 640, a sleep component 645, a configuration manager 650, a repeat component 655, a backoff manager 660, a hypothesis component 665, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0154] According to the examples disclosed herein, the communication manager 620 may support wireless communication. The user data component 625 is capable of, configured to, or operable to support components for transmitting an uplink message containing user data at the UE based on the UE's idle mode, the uplink message including a first identifier associated with the UE via a bit set. The DCI manager 630 is capable of, configured to, or operable to support components for receiving a downlink control information message in response to an uplink message, at least a portion of the downlink control information message being scrambled according to an RNTI, wherein the RNTI is one of a set of multiple RNTIs, the set of multiple RNTIs including a first RNTI associated with contention resolution and a first identifier.

[0155] In some examples, the RNTI component 635 is capable of, can be configured to, or is operable to support components for: decoding downlink control information messages based on an RNTI, wherein the RNTI is a first RNTI, and wherein the first RNTI is a UE-specific RNTI comprising a first subset of a set of bits including a first identifier.

[0156] In some examples, the payload of the downlink control information message includes a second subset of the bit set associated with the first identifier. In some examples, resolving contention between the UE and at least a second UE is based on this first RNTI and the payload of the downlink control information message.

[0157] In some examples, uplink messages are contention-based shared PUR request messages or EDT request messages. In some examples, downlink control information messages are used at least in part for contention resolution.

[0158] In some examples, the RNTI component 635 is capable of, configured to, or can operate to support components for decoding downlink control information messages based on an RNTI, wherein the RNTI is a second RNTI, distinct from a first RNTI, within a set of multiple RNTIs. In some examples, the second RNTI is a static RNTI.

[0159] In some examples, downlink control information messages schedule uplink data transmission, downlink data messages, instruct the UE to perform a random access procedure for transmitting user data, or a combination thereof. In some examples, uplink data transmission is scheduled for retransmission of user data by the UE, downlink data messages instruct the UE to switch to connected mode operation, or both.

[0160] In some examples, it is assumed that component 665 is capable of, configured to, or able to operate to support components for decoding downlink control information messages by evaluating a first scrambling hypothesis associated with a first identifier in the search space and by evaluating a second scrambling hypothesis associated with a second RNTI in the search space.

[0161] In some examples, when the uplink message is a contention-based shared PUR request message, the second RNTI is based on the time and frequency resources associated with the uplink message, the multiplexing signature associated with the UE, the demodulation reference signal sequence, or a combination thereof. In some examples, when the uplink message is an EDT request message, the second RNTI is a temporary cell radio network temporary identifier associated with the UE.

[0162] In some examples, the size of the downlink control information message differs from the size of the second downlink control information message, wherein the downlink control information message is associated with a first downlink control information format, which differs from the second downlink control information format associated with the second downlink control information message. In some examples, at least a portion of the second downlink control information message is scrambled with an RNTI having the same value as the RNTI.

[0163] In some examples, the scrambling process associated with the decoded bits of the downlink control information message differs from the scrambling process of the second downlink control information message, wherein the downlink control information message is associated with a first downlink control information format, which differs from the second downlink control information format associated with the second downlink control information message. In some examples, at least a portion of the second downlink control information message is scrambled by an RNTI having the same value as the RNTI.

[0164] In some examples, the downlink control information message includes flags indicating whether the downlink control information message is associated with a contention resolution process.

[0165] In some examples, the downlink control information message includes one or more additional flags that indicate whether the downlink control information message is scheduling uplink data messages, whether the downlink control information message is scheduling downlink data messages, or both.

[0166] In some examples, the monitoring component 640 is capable of, configured to, or operable to support components that, upon receiving a downlink control information message, avoid monitoring additional downlink transmissions when operating in idle mode. In some examples, the monitoring component 640 is capable of, configured to, or operable to support components that monitor additional downlink transmissions based on the transmission of a second uplink message indicating second user data.

[0167] In some examples, monitoring component 640 is a component that is capable of, configured to, or operable to support the following operation: monitoring additional downlink transmissions during a first time period after receiving a downlink control information message. In some examples, sleep component 645 is a component that is capable of, configured to, or operable to support the following operation: entering a sleep period after the first time period.

[0168] In some examples, the configuration manager 650 is capable of, configured to, or operable to support components that receive system information block messages indicating downlink control configuration, which instruct at least one of the following: the start timing of the search space associated with the downlink control information message, the start offset of the search space associated with the downlink control information message, or the number of repetitions associated with the downlink control information message.

[0169] In some examples, the configuration manager 650 is a component that can, is configured to, or is capable of operating to support the following: receiving a system information block message indicating an uplink control configuration that instructs the UE to send an acknowledgment message in response to a downlink control information message or in response to a downlink data message scheduled by the downlink control information message.

[0170] In some examples, the configuration manager 650 is a component that can, is configured to, or is capable of operating to support receiving system information block messages that indicate downlink data message configuration associated with a data message, wherein the downlink control information message schedules the data message.

[0171] In some examples, the repeating component 655 is a component that can, is configured to, or is capable of operating to support determining the number of repetitions for transmitting uplink messages based on downlink signal strength, transmit power limits associated with the UE, or both.

[0172] In some examples, in order to support determining the number of repetitions based on downlink signal strength, the repetition component 655 can be, configured, or operated to support components for determining the number of repetitions used to send uplink messages based on downlink signal strength that meets one or more signal strength thresholds.

[0173] In some examples, the repeating component 655 is capable of, can be configured to, or is operable to support components for selecting one or more resources from a set of resources associated with the uplink message for sending the uplink message, based on determining the number of repetitions for sending the uplink message.

[0174] In some examples, the configuration manager 650 is capable of, configured to, or able to operate to support components for receiving system information block messages indicating a configuration associated with a downlink control information message, wherein the configuration is active for a first NB-IoT carrier associated with the UE.

[0175] In some examples, the backoff manager 660 is capable of, configured to, or can operate to support components for receiving a group common downlink control information message that includes an indication of a backoff period, wherein uplink messages are sent via a time selected from a set of time slots according to the backoff period. In some examples, the indication of the backoff period includes an indication of a time period or an indication of the number of transmission time slots.

[0176] In some examples, the configuration manager 650 is capable of, configured to, or operable to support components for receiving configurations indicating a limit on the transport block size. In some examples, the configuration manager 650 is capable of, configured to, or operable to support components for selecting a transport block size from a set of candidate transport block sizes for sending uplink messages, based on the limit on the transport block size.

[0177] Figure 7A diagram is shown of a system 700 including an improved device 705 supporting mobile-initiated data, according to one or more aspects of this disclosure. Device 705 may be an example of device 405, device 505, or UE 115 as described herein, or may include components thereof. Device 705 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). Device 705 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 720, an input / output (I / O) controller 710, a transceiver 715, an antenna 725, at least one memory 730, code 735, and at least one processor 740. These components may communicate electronically or be coupled in other ways (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 745).

[0178] I / O controller 710 manages the input and output signals of device 705. I / O controller 710 can also manage peripheral devices not integrated into device 705. In some cases, I / O controller 710 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 710 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Alternatively, the I / O controller 710 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 710 may be implemented as part of one or more processors, such as at least one processor 740. In some cases, a user may interact with the device 705 via the I / O controller 710 or via hardware components controlled by the I / O controller 710.

[0179] In some cases, device 705 may include a single antenna 725. However, in other cases, device 705 may have more than one antenna 725, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 715 may communicate bidirectionally via one or more antennas 725, a wired link, or a wireless link as described herein. For example, transceiver 715 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 715 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 725 for transmission; and demodulating packets received from one or more antennas 725. Transceiver 715, or transceiver 715 and one or more antennas 725, may be an example of transmitter 415, transmitter 515, receiver 410, receiver 510, or any combination thereof or components thereof as described herein.

[0180] At least one memory 730 may include random access memory (RAM) and read-only memory (ROM). At least one memory 730 may store computer-readable, computer-executable (e.g., processor-executable) code 735, including instructions that, when executed by at least one processor 740, cause device 705 to perform the various functions described herein. Code 735 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 735 may not be directly executable by at least one processor 740, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 730 may contain a basic I / O system (BIOS), etc., which controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0181] At least one processor 740 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, at least one processor 740 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into at least one processor 740. At least one processor 740 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 730) to cause device 705 to perform various functions (e.g., supporting improved functions or tasks for mobile-initiated data). For example, device 705 or components of device 705 may include at least one processor 740 and at least one memory 730 coupled to or coupled to at least one processor 740, wherein at least one processor 740 and at least one memory 730 are configured to perform the various functions described herein. In some examples, at least one processor 740 may include multiple processors, and at least one memory 730 may include multiple memories. One or more of a plurality of processors may be coupled to one or more of a plurality of memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 740 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuitry (including, for example, one or both of processor circuitry (which may include at least one processor 740) and memory circuitry (which may include at least one memory 730)) or components that receive or receive input and process the input to produce, generate or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, at least one processor 740 or a processing system including at least one processor 740 may be configured, capable of being configured to, or operable to cause device 705 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured to,” and “operable to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 730 or otherwise.

[0182] According to the examples disclosed herein, the communication manager 720 may support wireless communication. For example, the communication manager 720 is capable of, configured to, or operable to support components for: transmitting an uplink message containing user data at the UE based on the UE's idle mode, the uplink message including a first identifier associated with the UE via a bit set. The communication manager 720 is capable of, configured to, or operable to support components for: receiving a downlink control information message in response to an uplink message, at least a portion of the downlink control information message being scrambled according to an RNTI, wherein the RNTI is one of a set of multiple RNTIs, the set of multiple RNTIs including a first RNTI associated with contention resolution and a first identifier.

[0183] By including or configuring a communication manager 720 according to the examples described herein, device 705 can support techniques for reducing overhead associated with the transmission of mobile-initiated data and resolving contention caused by transmissions by multiple devices, thereby improving communication between devices and enhancing the user experience.

[0184] In some examples, the communication manager 720 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using a transceiver 715, one or more antennas 725, or any combination thereof, or otherwise cooperating with them. Although the communication manager 720 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 720 may be supported or executed by at least one processor 740, at least one memory 730, code 735, or any combination thereof. For example, code 735 may include instructions executable by at least one processor 740 to cause device 705 to perform various aspects of the improvements for mobile-initiated data described herein, or at least one processor 740 and at least one memory 730 may be otherwise configured to perform or support such operations individually or jointly.

[0185] Figure 8 A block diagram 800 of a device 805 supporting improvements for mobile-initiated data according to one or more aspects of this disclosure is shown. Device 805 may be an example of aspects of network entity 105 as described herein. Device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. Device 805, or one or more components of device 805 (e.g., receiver 810, transmitter 815, and communication manager 820), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0186] Receiver 810 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 805. In some examples, receiver 810 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 810 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0187] Transmitter 815 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 805. For example, transmitter 815 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 815 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 815 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 815 and receiver 810 may be co-located in a transceiver, which may include or be coupled to a modem.

[0188] The communication manager 820, receiver 810, transmitter 815, or various combinations thereof, or various components thereof, may be examples of components used to perform the various aspects of the improvements for mobile-initiated data described herein. For example, the communication manager 820, receiver 810, transmitter 815, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0189] In some examples, the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of a processor, DSP, CPU, ASIC, FPGA, or other programmable logic device, microcontroller, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0190] Additionally or alternatively, the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be implemented in code (e.g., as communication management software or firmware) executed by at least one processor. If implemented in code executed by at least one processor, the functionality of the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be performed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured, either individually or collectively, as components for performing the functions described in this disclosure).

[0191] In some examples, the communication manager 820 may be configured to use a receiver 810, a transmitter 815, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 820 may receive information from the receiver 810, transmit information to the transmitter 815, or be integrated in combination with the receiver 810, the transmitter 815, or both to acquire information, output information, or perform various other operations as described herein.

[0192] According to the examples disclosed herein, the communication manager 820 may support wireless communication. For example, the communication manager 820 is capable of, configured to, or operable to support components for: receiving uplink messages containing user data at the UE based on the UE's idle mode, the uplink messages including a first identifier associated with the UE via a bit set. The communication manager 820 is capable of, configured to, or operable to support components for: transmitting downlink control information messages in response to uplink messages, at least a portion of the downlink control information messages being scrambled according to an RNTI, wherein the RNTI is one of a set of multiple RNTIs, the set of multiple RNTIs including a first RNTI associated with contention resolution and a first identifier.

[0193] By including or configuring a communication manager 820 according to the examples described herein, device 805 (e.g., at least one processor that controls or otherwise couples to receiver 810, transmitter 815, communication manager 820, or a combination thereof) can support techniques for reducing overhead associated with the transmission of mobile-initiated data and resolving competition caused by transmissions by multiple devices, thereby improving communication between devices and enhancing the user experience.

[0194] Figure 9 A block diagram 900 is shown of a device 905 supporting improvements for mobile-initiated data according to one or more aspects of this disclosure. Device 905 may be an example of aspects of device 805 or network entity 105 as described herein. Device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. Device 905, or one or more components of device 905 (e.g., receiver 910, transmitter 915, and communication manager 920), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0195] Receiver 910 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 905. In some examples, receiver 910 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 910 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0196] Transmitter 915 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 905. For example, transmitter 915 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 915 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 915 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 915 and receiver 910 may be co-located in a transceiver, which may include or be coupled to a modem.

[0197] Device 905 or its various components may be examples of parts used to perform the various aspects of the improvements for mobile-initiated data described herein. For example, communication manager 920 may include user data manager 925, DCI component 930, or any combination thereof. Communication manager 920 may be an example of aspects of communication manager 820 as described herein. In some examples, communication manager 920 or its various components may be configured to use receiver 910, transmitter 915, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 920 may receive information from receiver 910, transmit information to transmitter 915, or be integrated in combination with receiver 910, transmitter 915, or both to acquire information, output information, or perform various other operations as described herein.

[0198] According to the examples disclosed herein, the communication manager 920 may support wireless communication. The user data manager 925 is capable of, configured to, or operable to support components for: receiving uplink messages containing user data at the UE based on the UE's idle mode, the uplink messages including a first identifier associated with the UE via a bit set. The DCI component 930 is capable of, configured to, or operable to support components for: transmitting downlink control information messages in response to uplink messages, at least a portion of the downlink control information messages being scrambled according to an RNTI, wherein the RNTI is one of a set of multiple RNTIs, the set of multiple RNTIs including a first RNTI associated with contention resolution and a first identifier.

[0199] Figure 10A block diagram 1000 is shown of a communication manager 1020 supporting improvements for mobile-initiated data according to one or more aspects of this disclosure. The communication manager 1020 may be an example of a communication manager 820, a communication manager 920, or aspects thereof as described herein. The communication manager 1020 or its various components may be examples of parts for performing the various aspects of the improvements for mobile-initiated data as described herein. For example, the communication manager 1020 may include a user data manager 1025, a DCI component 1030, a configuration manager 1035, a backoff component 1040, or any combination thereof. These components, or each of their components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses), and this communication may include communication within protocol layers of a protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within devices, components, or virtualization components associated with network entity 105, between devices, components, or virtualization components associated with network entity 105), or any combination thereof.

[0200] According to the examples disclosed herein, the communication manager 1020 may support wireless communication. The user data manager 1025 is capable of, configured to, or operable to support components for: receiving uplink messages containing user data at the UE based on the UE's idle mode, the uplink messages including a first identifier associated with the UE via a bit set. The DCI component 1030 is capable of, configured to, or operable to support components for: transmitting downlink control information messages in response to uplink messages, at least a portion of the downlink control information messages being scrambled according to an RNTI, wherein the RNTI is one of a set of multiple RNTIs, the set of multiple RNTIs including a first RNTI associated with contention resolution and a first identifier.

[0201] In some examples, the RNTI is a first RNTI. In some examples, the first RNTI includes a first subset of the bit set of a first identifier. In some examples, the payload of the downlink control information message includes a second subset of the bit set associated with the first identifier. In some examples, resolving contention between the UE and at least a second UE is based on the first RNTI and the payload of the downlink control information message.

[0202] In some examples, the uplink message is a contention-based shared PUR request message or EDT request message. In some examples, the downlink control information message is used at least partially for contention resolution. In some examples, the RNTI is the second RNTI in a set of multiple RNTIs. In some examples, the second RNTI is a static RNTI.

[0203] In some examples, downlink control information messages schedule uplink data transmission, downlink data messages, instruct the UE to perform a random access procedure for transmitting user data, or a combination thereof. In some examples, uplink data transmission is scheduled for retransmission of user data by the UE, downlink data messages instruct the UE to switch to connected mode operation, or both.

[0204] In some examples, when the uplink message is a contention-based shared PUR request message, the second RNTI is based on the time and frequency resources associated with the uplink message, the multiplexing signature associated with the UE, the demodulation reference signal sequence, or a combination thereof. In some examples, when the uplink message is an EDT request message, the second RNTI is a temporary cell radio network temporary identifier associated with the UE.

[0205] In some examples, the size of the downlink control information message differs from the size of the second downlink control information message, wherein the downlink control information message is associated with a first downlink control information format, which differs from the second downlink control information format associated with the second downlink control information message. In some examples, at least a portion of the second downlink control information message is scrambled with an RNTI having the same value as the RNTI.

[0206] In some examples, the scrambling process associated with the decoded bits of the downlink control information message differs from the scrambling process of the second downlink control information message, wherein the downlink control information message is associated with a first downlink control information format, which differs from the second downlink control information format associated with the second downlink control information message. In some examples, at least a portion of the second downlink control information message is scrambled by an RNTI having the same value as the RNTI.

[0207] In some examples, the downlink control information message includes flags indicating whether the downlink control information message is associated with a contention resolution process.

[0208] In some examples, the downlink control information message includes one or more additional flags that indicate whether the downlink control information message is scheduling uplink data messages, whether the downlink control information message is scheduling downlink data messages, or both.

[0209] In some examples, the configuration manager 1035 is capable of, configured to, or operable to support components that send system information block messages indicating downlink control configurations, which instruct at least one of the following: the start timing of the search space associated with the downlink control information message, the start offset of the search space associated with the downlink control information message, or the number of repetitions associated with the downlink control information message.

[0210] In some examples, the configuration manager 1035 is a component that can, is configured to, or is capable of operating to support the following: sending a system information block message indicating an uplink control configuration that instructs the UE to send an acknowledgment message in response to a downlink control information message or in response to a downlink data message scheduled by the downlink control information message.

[0211] In some examples, the configuration manager 1035 is a component that can, is configured to, or is capable of operating to support sending system information block messages that indicate the configuration of a downlink data message associated with a data message, wherein the downlink control information message schedules the data message.

[0212] In some examples, the configuration manager 1035 is a component that can, is configured to, or is capable of operating to support sending a system information block message indicating a configuration associated with a downlink control information message, wherein the configuration is active for a first NB-IoT carrier associated with the UE.

[0213] In some examples, the backoff component 1040 is a component that can, is configured to, or is capable of operating to support the following operation: sending a group common downlink control information message that includes an indication of a backoff period, wherein the uplink message is sent via a time selected from a set of times according to the backoff period.

[0214] In some examples, the indication of a backoff period includes an indication of a time period or an indication of the number of times to send.

[0215] In some examples, the configuration manager 1035 is capable of, can be configured to, or can operate to support components for sending configurations that indicate a limit on transport block size, wherein uplink messages are sent using transport block sizes from a set of candidate transport block sizes in accordance with the limit on transport block size.

[0216] Figure 11A diagram of a system 1100 including an improved device 1105 supporting mobile-initiated data, according to one or more aspects of this disclosure, is shown. Device 1105 may be an example of device 805, device 905, or network entity 105 as described herein, or may include components thereof. Device 1105 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, and this communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1105 may include components supporting output and acquisition of communication, such as a communication manager 1120, a transceiver 1110, an antenna 1115, at least one memory 1125, code 1130, and at least one processor 1135. These components may communicate electronically or otherwise (e.g., operative ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 1140).

[0217] Transceiver 1110 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, transceiver 1110 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, transceiver 1110 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, device 1105 may include one or more antennas 1115 that may be capable of transmitting or receiving wireless transmissions (e.g., concurrently). Transceiver 1110 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., by one or more antennas 1115, by a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1115, from a wired receiver); and demodulating the signal. In some embodiments, transceiver 1110 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1115 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1115 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 1110 may include one or more processors or one or more memory components or configured to be coupled to such processors or memory components, which are operable to perform or support operations based on received or acquired information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some embodiments, transceiver 1110, or transceiver 1110 and one or more antennas 1115, or transceiver 1110 and one or more antennas 1115 and one or more processors or one or more memory components (e.g., at least one processor 1135, at least one memory 1125, or both) may be included in a chip or chip assembly mounted in device 1105. In some examples, transceiver 1110 may be able to operate to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0218] At least one memory 1125 may include RAM, ROM, or any combination thereof. At least one memory 1125 may store computer-readable, computer-executable code 1130 including instructions that, when executed by one or more of the at least one processor 1135, cause the device 1105 to perform the various functions described herein. The code 1130 may be stored in a non-transitory computer-readable (e.g., processor-readable, processor-executable) medium, such as system memory or another type of memory. In some cases, the code 1130 may not be directly executable by one of the at least one processor 1135, but may enable the computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 1125 may contain a BIOS, etc., that controls basic hardware or software operation, such as interaction with peripheral components or devices. In some examples, at least one processor 1135 may include multiple processors, and at least one memory 1125 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein (e.g., as part of a processing system).

[0219] At least one processor 1135 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic units, discrete hardware components, or any combination thereof). In some cases, at least one processor 1135 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into one or more processors in at least one processor 1135. At least one processor 1135 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 1125) to cause device 1105 to perform various functions (e.g., supporting improved functions or tasks for mobile-initiated data). For example, device 1105 or components of device 1105 may include at least one processor 1135 and at least one memory 1125 coupled to one or more processors in at least one processor 1135, wherein at least one processor 1135 and at least one memory 1125 are configured to perform the various functions described herein. At least one processor 1135 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can host functions (e.g., by executing code 1130) to perform the functions of device 1105. At least one processor 1135 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1105 (such as within one or more memories of at least one memory 1125). In some examples, at least one processor 1135 may include multiple processors, and at least one memory 1125 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1135 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuits (including, for example, one or both of processor circuitry (which may include at least one processor 1135) and memory circuitry (which may include at least one memory 1125)) or components that receive or acquire input and process the input to produce, generate, or acquire a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, at least one processor 1135 or a processing system including at least one processor 1135 may be configured, configured to, or operable to cause the device 1105 to perform one or more of the functions described herein.Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 1125 or otherwise.

[0220] In some examples, bus 1140 may support communication at protocol layers (e.g., within a protocol layer) in a protocol stack. In some examples, bus 1140 may support communication associated with logical channels of a protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of device 1105, or communication performed between different components of device 1105 that are co-addressable or may be located in different locations (e.g., where device 1105 may refer to a system in which one or more of communication manager 1120, transceiver 1110, at least one memory 1125, code 1130 and at least one processor 1135 may be located in one component of different components or partitioned between different components).

[0221] In some examples, the communication manager 1120 can manage (e.g., via one or more wired or wireless backhaul links) various aspects of communication with the core network 130. For example, the communication manager 1120 can manage the transfer of data communication between client devices such as one or more UEs 115. In some examples, the communication manager 1120 can manage communication with other network entities 105 and may include a controller or scheduler for coordinating other network entities 105 to control communication with UE 115. In some examples, the communication manager 1120 may support the X2 interface in LTE / LTE-A wireless communication network technology to provide communication between network entities 105.

[0222] According to the examples disclosed herein, the communication manager 1120 may support wireless communication. For example, the communication manager 1120 is capable of, configured to, or operable to support components for: receiving uplink messages containing user data at the UE based on the UE's idle mode, the uplink messages including a first identifier associated with the UE via a bit set. The communication manager 1120 is capable of, configured to, or operable to support components for: transmitting downlink control information messages in response to uplink messages, at least a portion of the downlink control information messages being scrambled according to an RNTI, wherein the RNTI is one of a set of multiple RNTIs, the set of multiple RNTIs including a first RNTI associated with contention resolution and a first identifier.

[0223] By including or configuring a communication manager 1120 according to the examples described herein, device 1105 can support techniques for reducing overhead associated with the transmission of mobile-initiated data and resolving contention caused by transmissions by multiple devices, thereby improving communication between devices and enhancing the user experience.

[0224] In some examples, the communication manager 1120 may be configured to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting) using a transceiver 1110, one or more antennas 1115 (e.g., where applicable), or any combination thereof, or otherwise cooperating with them. Although the communication manager 1120 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1120 may be supported or performed by the transceiver 1110, one or more processors in at least one processor 1135, one or more memories in at least one memory 1125, code 1130, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 1135, at least one memory 1125, code 1130, or any combination thereof). For example, code 1130 may include instructions that can be executed by one or more processors in at least one processor 1135 to cause device 1105 to perform various aspects of the improvements for mobile-initiated data described herein, or at least one processor 1135 and at least one memory 1125 may be otherwise configured to perform or support such operations individually or jointly.

[0225] Figure 12 A flowchart illustrating an improved method 1200 for mobile-initiated data, as exemplified by an example described herein, is shown. Operation of method 1200 can be implemented by a UE or its components as described herein. For example, operation of method 1200 can be achieved by, as referenced... Figures 1 to 7 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0226] At 1205, the method may include: transmitting an uplink message containing user data at the UE based on the UE's idle mode, the uplink message including a first identifier associated with the UE via a bit set. The operation of block 1205 may be based on examples as disclosed herein (such as...). Figure 3 Operation 320) is performed. In some examples, aspects of the operation 1205 can be obtained from, as referenced... Figure 6 The user data component 625 described is used to perform this action.

[0227] At 1210, the method may include: receiving a downlink control information message in response to the uplink message, at least a portion of the downlink control information message being scrambled according to an RNTI, wherein the RNTI is one of a set of multiple RNTIs, the set of multiple RNTIs including a first RNTI associated with contention resolution and a first identifier. The operation of block 1210 may be based on examples as disclosed herein (such as...). Figure 3 Operation 325) is performed. In some examples, aspects of the operation of 1210 can be obtained from, as referenced... Figure 6 The described DCI manager 630 is used to execute this.

[0228] Figure 13 A flowchart illustrating an improved method 1300 for mobile-initiated data, as exemplified by an example described herein, is shown. Operation of method 1300 can be implemented by a UE or its components as described herein. For example, operation of method 1300 can be achieved by, as referenced... Figures 1 to 7 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0229] At 1305, the method may include: transmitting an uplink message containing user data at the UE based on the UE's idle mode, the uplink message including a first identifier associated with the UE via a bit set. The operation of block 1305 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1305 may be as described in references... Figure 6 The user data component 625 described is used to perform this action.

[0230] At 1310, the method may include: receiving a downlink control information message in response to the uplink message, at least a portion of the downlink control information message being scrambled according to an RNTI, wherein the RNTI is one of a set of multiple RNTIs, the set of multiple RNTIs including a first RNTI associated with contention resolution and a first identifier. The operation of block 1310 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1310 may be provided by reference to [reference]. Figure 6 The described DCI manager 630 is used to execute this.

[0231] At 1315, the method may include: decoding a downlink control information message based on an RNTI, wherein the RNTI is a first RNTI, and wherein the first RNTI includes a first subset of the bit set of a first identifier. The operation of block 1315 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1315 may be derived from references... Figure 6 The RNTI component 635 described is used for execution.

[0232] Figure 14 A flowchart illustrating an improved method 1400 for mobile-initiated data, as exemplified by an example described herein, is shown. The operation of method 1400 can be implemented by a network entity or its components as described herein. For example, the operation of method 1400 can be implemented by, as referenced... Figures 1 to 3 as well as Figures 8 to 11 The network entity described herein performs the function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0233] At 1405, the method may include: receiving an uplink message containing user data at the UE based on the UE's idle mode, the uplink message including a first identifier associated with the UE via a bit set. The operation of block 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1405 may be provided by reference to [reference needed]. Figure 10 The user data manager 1025 described is used to execute this.

[0234] At 1410, the method may include: sending a downlink control information message in response to the uplink message, at least a portion of the downlink control information message being scrambled according to an RNTI, wherein the RNTI is one of a set of multiple RNTIs, the set of multiple RNTIs including a first RNTI associated with contention resolution and a first identifier. The operation of block 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1410 may be provided by reference to [reference needed]. Figure 10 The described DCI component 1030 is used to perform this.

[0235] Figure 15 A flowchart illustrating an improved method 1500 for mobile-initiated data, as exemplified by an example described herein, is shown. The operation of method 1500 can be implemented by a network entity or its components as described herein. For example, the operation of method 1500 can be implemented by, as referenced... Figures 1 to 3 as well as Figures 8 to 11 The network entity described herein performs the function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0236] At 1505, the method may include: sending a system information block message indicating a downlink control configuration, the downlink control configuration indicating at least one of the following: a start timing for the search space associated with the downlink control information message, a start offset for the search space associated with the downlink control information message, or a repetition number associated with the downlink control information message. The operation of block 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1505 may be provided by reference to [reference needed]. Figure 10 The configuration manager 1035 described is used to execute this.

[0237] At 1510, the method may include: receiving an uplink message containing user data at the UE based on the UE's idle mode, the uplink message including a first identifier associated with the UE via a bit set. Operation of block 1510 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1510 may be provided by reference to... Figure 10 The user data manager 1025 described is used to execute this.

[0238] At 1515, the method may include: sending a downlink control information message in response to the uplink message, at least a portion of the downlink control information message being scrambled according to an RNTI, wherein the RNTI is one of a set of multiple RNTIs, the set of multiple RNTIs including a first RNTI associated with contention resolution and a first identifier. The operation of block 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1515 may be provided by reference to [reference]. Figure 10 The described DCI component 1030 is used to perform this.

[0239] The following provides an overview of the various aspects of this disclosure:

[0240] Aspect 1: A method for wireless communication performed by a UE, the method comprising: transmitting an uplink message containing user data at the UE, at least in part based on an idle mode of the UE, the uplink message including a first identifier associated with the UE via a set of bits; and receiving a downlink control information message in response to the uplink message, at least a portion of the downlink control information message being scrambled according to an RNTI, wherein the RNTI is one of a plurality of RNTIs, the plurality of RNTIs including a first RNTI associated with contention resolution and the first identifier.

[0241] Aspect 2: According to the method of aspect 1, the method further includes: decoding the downlink control information message at least in part based on the RNTI, wherein the RNTI is the first RNTI, and wherein the first RNTI is a UE-specific RNTI, the UE-specific RNTI including a first subset of the bit set of the first identifier.

[0242] Aspect 3: According to the method of aspect 2, the payload of the downlink control information message includes a second subset of the bit set associated with the first identifier.

[0243] Aspect 4: According to the method of aspect 3, the resolution of the competition between the UE and at least the second UE is based at least in part on the payload of the first RNTI and the downlink control information message.

[0244] Aspect 5: The method according to any one of Aspects 2 to 4, wherein the uplink message is a contention-based shared PUR request message or EDT request message, and the downlink control information message is used at least in part for contention resolution.

[0245] Aspect 6: The method according to aspect 1 or 5 further includes: decoding the downlink control information message at least in part based on the RNTI, wherein the RNTI is a second RNTI among the plurality of RNTIs that is different from the first RNTI.

[0246] Aspect 7: The method according to aspect 6, wherein the second RNTI is a static RNTI.

[0247] Aspect 8: The method according to any one of Aspects 6 to 7, wherein the downlink control information message schedules uplink data transmission, downlink data messages, instructs the UE to perform a random access procedure for transmitting the user data, or a combination thereof.

[0248] Aspect 9: According to the method of aspect 8, wherein the uplink data transmission is scheduled for the UE to retransmit the user data, the downlink data message instructs the UE to switch to connected mode operation, or both.

[0249] Aspect 10: According to the method of aspect 6, the method further includes: decoding the downlink control information message by evaluating a first scrambling hypothesis associated with the first identifier in a search space and by evaluating a second scrambling hypothesis associated with the second RNTI in the search space.

[0250] Aspect 11: The method according to any one of Aspects 6 to 10, wherein when the uplink message is a contention-based shared PUR request message, the second RNTI is based at least in part on time and frequency resources associated with the uplink message, a multiplexing signature associated with the UE, a demodulation reference signal sequence, or a combination thereof.

[0251] Aspect 12: The method according to any one of Aspects 6 to 11, wherein when the uplink message is an EDT request message, the second RNTI is a temporary cell radio network temporary identifier associated with the UE.

[0252] Aspect 13: The method according to any one of Aspects 1 to 12, wherein the size of the downlink control information message is different from the size of the second downlink control information message, wherein the downlink control information message is associated with a first downlink control information format, the first downlink control information format being different from the second downlink control information format associated with the second downlink control information message. RNTI

[0253] Aspect 14: The method according to any one of Aspects 1 to 13, wherein the scrambling process associated with the decoded bits of the downlink control information message is different from the scrambling process of the second downlink control information message, wherein the downlink control information message is associated with a first downlink control information format, the first downlink control information format being different from the second downlink control information format associated with the second downlink control information message. RNTI

[0254] Aspect 15: The method according to any one of Aspects 1 to 14, wherein the downlink control information message includes a flag indicating whether the downlink control information message is associated with a contention resolution process.

[0255] Aspect 16: According to the method of aspect 15, the downlink control information message includes one or more additional flags indicating whether the downlink control information message is scheduling uplink data messages, whether the downlink control information message is scheduling downlink data messages, or both.

[0256] Aspect 17: The method according to any one of Aspects 1 to 16, the method further comprising: after receiving the downlink control information message, avoiding monitoring additional downlink transmissions when operating in the idle mode; and monitoring additional downlink transmissions at least in part based on a second uplink message indicating the transmission of second user data.

[0257] Aspect 18: The method according to any one of Aspects 1 to 16, the method further comprising: monitoring additional downlink transmissions during a first time period after receiving the downlink control information message; and entering a sleep period after the first time period.

[0258] Aspect 19: The method according to any one of Aspects 1 to 18, the method further comprising: receiving a system information block message indicating a downlink control configuration, the downlink control configuration indicating at least one of the following: a start timing for a search space associated with the downlink control information message, a start offset for a search space associated with the downlink control information message, or a number of repetitions associated with the downlink control information message.

[0259] Aspect 20: The method according to any one of Aspects 1 to 19, the method further comprising: receiving a system information block message indicating an uplink control configuration, the uplink control configuration instructing the UE to send an acknowledgment message in response to the downlink control information message or in response to a downlink data message scheduled by the downlink control information message.

[0260] Aspect 21: The method according to any one of aspects 1 to 20, the method further comprising: receiving a system information block message indicating a downlink data message configuration associated with a data message, wherein the downlink control information message schedules the data message.

[0261] Aspect 22: The method according to any one of Aspects 1 to 21, the method further comprising: determining the number of repetitions for transmitting the uplink message based at least in part on downlink signal strength, a transmit power limit associated with the UE, or both.

[0262] Aspect 23: According to the method of aspect 22, determining the number of repetitions based at least in part on the downlink signal strength further includes: determining the number of repetitions for sending the uplink message based at least in part on the downlink signal strength satisfying one or more signal strength thresholds.

[0263] Aspect 24: The method according to any one of Aspects 22 to 23, the method further comprising: selecting one or more resources from a set of resources associated with the uplink message for sending the uplink message, at least in part based on determining the number of repetitions for sending the uplink message.

[0264] Aspect 25: The method according to any one of Aspects 1 to 24, the method further comprising: receiving a system information block message indicating a configuration associated with the downlink control information message, wherein the configuration is active for a first NB-IoT carrier associated with the UE.

[0265] Aspect 26: The method according to any one of aspects 1 to 25, the method further comprising: receiving a group common downlink control information message including an indication of a backoff period, wherein the uplink message is sent via a timing selected from a timing set according to the backoff period.

[0266] Aspect 27: The method according to aspect 26, wherein the indication of the backoff period includes an indication of a time period or an indication of the number of transmission opportunities.

[0267] Aspect 28: The method according to any one of aspects 1 to 27, the method further comprising: receiving a configuration indicating a limit on the transport block size; and selecting a transport block size for sending the uplink message from a set of candidate transport block sizes according to the limit on the transport block size.

[0268] Aspect 29: A method for wireless communication by a network entity, the method comprising: receiving an uplink message containing user data at the UE, at least in part based on an idle mode of the UE, the uplink message including a first identifier associated with the UE via a set of bits; and transmitting a downlink control information message in response to the uplink message, at least a portion of the downlink control information message being scrambled according to an RNTI, wherein the RNTI is one of a plurality of RNTIs, the plurality of RNTIs including a first RNTI associated with contention resolution and the first identifier.

[0269] Aspect 30: The method according to aspect 29, wherein the RNTI is the first RNTI, and the first RNTI includes a first subset of the bit set of the first identifier.

[0270] Aspect 31: According to the method of aspect 30, the payload of the downlink control information message includes a second subset of the set of bits associated with the first identifier.

[0271] Aspect 32: According to the method of aspect 31, the resolution of the competition between the UE and at least the second UE is based at least in part on the payload of the first RNTI and the downlink control information message.

[0272] Aspect 33: The method according to any one of Aspects 30 to 32, wherein the uplink message is a contention-based shared PUR request message or EDT request message, and the downlink control information message is used at least in part for contention resolution.

[0273] Aspect 34: The method according to any one of Aspects 29 or 33, wherein the RNTI is the second RNTI among the plurality of RNTIs.

[0274] Aspect 35: The method according to aspect 34, wherein the second RNTI is a static RNTI.

[0275] Aspect 36: The method according to any one of Aspects 34 to 35, wherein the downlink control information message schedules uplink data transmission, downlink data messages, instructs the UE to perform a random access procedure for transmitting the user data, or a combination thereof.

[0276] Aspect 37: The method according to aspect 36, wherein the uplink data transmission is scheduled for the UE to retransmit the user data, the downlink data message instructs the UE to switch to connected mode operation, or both.

[0277] Aspect 38: The method according to any one of Aspects 34 to 37, wherein when the uplink message is a contention-based shared PUR request message, the second RNTI is based at least in part on time and frequency resources associated with the uplink message, a multiplexing signature associated with the UE, a demodulation reference signal sequence, or a combination thereof.

[0278] Aspect 39: The method according to any one of Aspects 34 to 38, wherein when the uplink message is an EDT request message, the second RNTI is a temporary cell radio network temporary identifier associated with the UE.

[0279] Aspect 40: The method according to any one of Aspects 29 to 39, wherein the size of the downlink control information message is different from the size of the second downlink control information message, wherein the downlink control information message is associated with a first downlink control information format, the first downlink control information format being different from the second downlink control information format associated with the second downlink control information message.

[0280] Aspect 41: The method according to any one of Aspects 29 to 40, wherein the scrambling process associated with the decoded bits of the downlink control information message is different from the scrambling process of the second downlink control information message, wherein the downlink control information message is associated with a first downlink control information format, the first downlink control information format being different from the second downlink control information format associated with the second downlink control information message.

[0281] Aspect 42: The method according to any one of Aspects 29 to 41, wherein the downlink control information message includes a flag indicating whether the downlink control information message is associated with a contention resolution process.

[0282] Aspect 43: According to the method of aspect 42, the downlink control information message includes one or more additional flag bits, the one or more additional flag bits indicating whether the downlink control information message is scheduling uplink data messages, whether the downlink control information message is scheduling downlink data messages, or both.

[0283] Aspect 44: The method according to any one of aspects 29 to 43, the method further comprising: sending a system information block message indicating a downlink control configuration, the downlink control configuration indicating at least one of the following: a start timing for a search space associated with the downlink control information message, a start offset for a search space associated with the downlink control information message, or a number of repetitions associated with the downlink control information message.

[0284] Aspect 45: The method according to any one of Aspects 29 to 44, the method further comprising: sending a system information block message indicating an uplink control configuration, the uplink control configuration instructing the UE to send an acknowledgment message in response to the downlink control information message or in response to a downlink data message scheduled by the downlink control information message.

[0285] Aspect 46: The method according to any one of Aspects 29 to 45, the method further comprising: sending a system information block message indicating a downlink data message configuration associated with a data message, wherein the downlink control information message schedules the data message.

[0286] Aspect 47: The method according to any one of Aspects 29 to 46, the method further comprising: sending a system information block message indicating a configuration associated with the downlink control information message, wherein the configuration is active for a first NB-IoT carrier associated with the UE.

[0287] Aspect 48: The method according to any one of Aspects 29 to 47, the method further comprising: sending a group common downlink control information message including an indication of a backoff period, wherein the uplink message is sent via a timing selected from a set of timings according to the backoff period.

[0288] Aspect 49: The method according to aspect 48, wherein the indication of the backoff period includes an indication of a time period or an indication of the number of transmission opportunities.

[0289] Aspect 50: The method according to any one of Aspects 29 to 49, the method further comprising: sending a configuration indicating a limit on transport block size, wherein the uplink message is sent using a transport block size from a set of candidate transport block sizes in accordance with the limit on transport block size.

[0290] Aspect 51: A UE for wireless communication, the UE comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code, so that the UE performs a method according to any one of aspects 1 to 28.

[0291] Aspect 52: A UE for wireless communication, the UE comprising at least one component for performing the method according to any one of aspects 1 to 28.

[0292] Aspect 53: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by one or more processors to perform the method according to any one of aspects 1 to 28.

[0293] Aspect 54: A network entity for wireless communication, the network entity comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code, so that the network entity performs a method according to any one of Aspects 29 to 50.

[0294] Aspect 55: A network entity for wireless communication, the network entity comprising at least one component for performing the method according to any one of aspects 29 to 50.

[0295] Aspect 56: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by one or more processors to perform a method according to any one of aspects 29 to 50.

[0296] It should be noted that the methods described herein describe possible specific implementations, and the operations and steps can be rearranged or otherwise modified, and other specific implementations are also possible. Furthermore, aspects from two or more of these methods can be combined.

[0297] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks outside of LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0298] The information and signals described herein can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0299] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described functions or operations individually or jointly.

[0300] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, these functions can be stored as one or more instructions or code on a computer-readable (e.g., processor-readable, processor-executable) medium, or transmitted using one or more instructions or code. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functions can also be physically located in various locations, including various portions distributed such that the functions are implemented in different physical locations.

[0301] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

[0302] As used herein, the word "or" in a list of items (e.g., a list of items accompanied by phrases such as "at least one of" or "one or more of") in the claims indicates an inclusive list, such that a list of at least one of, for example, A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0303] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” can refer to any or all of the one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0304] The term "determine" encompasses a variety of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, lookup (such as by searching in a table, database, or other data structure), identification, and similar actions. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), etc. Moreover, "determine" can include parsing, acquiring, selecting, choosing, creating, and other similar actions.

[0305] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numeral and a second numeral for differentiation between similar components. If only the first reference numeral is used in the specification, the description can be applied to any of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.

[0306] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

[0307] The description herein is provided to enable those skilled in the art to implement or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE), the user equipment (UE) comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the UE: Uplink messages containing user data at the UE are sent, at least in part based on the UE's idle mode, and the uplink messages include a first identifier associated with the UE via a set of bits; as well as Receive a downlink control information message in response to the uplink message, at least a portion of the downlink control information message being scrambled according to a radio network temporary identifier (RNTI), wherein the RNTI is one of a plurality of RNTIs, the plurality of RNTIs including a first RNTI associated with contention resolution and the first identifier.

2. The UE of claim 1, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: The downlink control information message is decoded at least in part based on the RNTI, wherein the RNTI is the first RNTI, and wherein the first RNTI is a UE-specific RNTI, the UE-specific RNTI comprising a first subset of the bit set associated with the first identifier.

3. The UE of claim 2, wherein the payload of the downlink control information message includes a second subset of the bit set associated with the first identifier.

4. The UE of claim 3, wherein resolving the competition between the UE and at least a second UE is based at least in part on at least one of the first RNTI and the payload of the downlink control information message.

5. The UE of claim 2, wherein the uplink message is a contention-based shared pre-configured uplink resource (PUR) request message or an early data transmission (EDT) request message, and wherein the downlink control information message is at least partially used for contention resolution.

6. The UE of claim 1, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: The downlink control information message is decoded at least in part based on the RNTI, wherein the RNTI is a second RNTI that is different from the first RNTI among the plurality of RNTIs, and wherein the downlink control information message is associated with uplink transmission, downlink data message, instruction for performing a random access procedure for transmitting user data for the UE, or a combination thereof.

7. The UE of claim 6, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: The downlink control information message is decoded by evaluating a first scrambling hypothesis associated with the first identifier in the search space and by evaluating a second scrambling hypothesis associated with the second RNTI in the search space.

8. The UE of claim 6, wherein when the uplink message is a contention-based shared PUR request message, and wherein the second RNTI is based at least in part on time and frequency resources associated with the uplink message, a multiplexing signature associated with the UE, a demodulation reference signal sequence, or a combination thereof.

9. The UE of claim 6, wherein when the uplink message is an Early Data Transmission (EDT) request message, and wherein the second RNTI is a temporary cell radio network temporary identifier associated with the UE.

10. The UE according to claim 1, wherein the size of the downlink control information message is different from the size of the second downlink control information message, wherein the downlink control information message is associated with a first downlink control information format, and the first downlink control information format is different from the second downlink control information format associated with the second downlink control information message.

11. The UE of claim 1, wherein the scrambling process associated with the decoded bits of the downlink control information message is different from the scrambling process of the second downlink control information message, wherein the downlink control information message is associated with a first downlink control information format, the first downlink control information format being different from the second downlink control information format associated with the second downlink control information message.

12. The UE of claim 1, wherein the downlink control information message includes one or more flag bits, the one or more flag bits indicating whether the downlink control information message is associated with a contention resolution process, whether the downlink control information message is scheduling uplink messages, whether the downlink control information message is scheduling downlink data messages, or a combination thereof.

13. The UE of claim 1, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: Receive a system information block message indicating downlink control configuration, the downlink control configuration indicating at least one of the following: the start timing of the search space associated with the downlink control information message, the start offset of the search space associated with the downlink control information message, or the number of repetitions associated with the downlink control information message.

14. The UE of claim 1, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: The system receives a system information block message indicating uplink control configuration, wherein the uplink control configuration instructs the UE to send an acknowledgment message in response to the downlink control information message or in response to a downlink data message scheduled by the downlink control information message.

15. The UE of claim 1, wherein the one or more processors are individually or jointly further operable to execute the code to cause the UE to: Receive a system information block message indicating the downlink data message configuration associated with a data message, wherein the downlink control information message schedules the data message.

16. The UE of claim 1, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: The number of repetitions used to transmit the uplink message is determined at least in part based on downlink signal strength, transmit power limits associated with the UE, or both.

17. The UE of claim 1, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: Receive a system information block message indicating a configuration associated with the downlink control information message, wherein the configuration is active for a first NB-IoT carrier associated with the UE.

18. The UE of claim 1, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: Receive a group common downlink control information message including an indication of a backoff period, wherein the uplink message is sent via a timing selected from a timing set according to the backoff period.

19. The UE of claim 1, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: The configuration for receiving instructions to limit the transport block size; and The transport block size for sending the uplink message is selected from the set of candidate transport block sizes based on the specified transport block size limit.

20. A method for wireless communication by a user equipment (UE), the method comprising: Uplink messages containing user data at the UE are sent, at least in part based on the UE's idle mode, and the uplink messages include a first identifier associated with the UE via a set of bits; as well as Receive a downlink control information message in response to the uplink message, at least a portion of the downlink control information message being scrambled according to a first radio network temporary identifier (RNTI), wherein the RNTI is one of a plurality of RNTIs, the plurality of RNTIs including a first RNTI associated with contention resolution and the first identifier.

Images