Redundancy version (RV) determination for message repetition

Abstract

Various forms of this application relate to random access procedures. In one instance, the UE initiates a random access procedure with a base station and responds by receiving a Random Access Response (RAR) message from the base station in response to the initiated random access procedure. The UE also determines an RV mode comprising a sequence of multiple Redundant Versions (RVs). As part of the random access procedure, the UE also sends uplink (UL) communication to the base station. The UL communication comprises multiple repetitions of a UL message, each repetition being an iteration of the UL message configured by applying the corresponding RV from the multiple RVs to the UL message based on a sequence. The UE also receives downlink messages from the base station based on the UL messages. Other forms, embodiments, and features are also claimed and described.

Description

Technical Field

[0001] This case is a PCT application that claims priority to non-provisional application no. 17 / 365,849 filed with the U.S. Patent and Trademark Office on July 1, 2021, and priority to provisional patent application no. 63 / 049,096 filed with the U.S. Patent and Trademark Office on July 7, 2020. The entire contents of all of the aforementioned applications are incorporated herein by reference as if fully set forth herein and for all applicable purposes.

[0002] In general, the techniques discussed below relate to wireless communication systems, and more specifically, to random access procedures. Some examples may include enabling and providing communication devices configured to improve the reliability and coverage of uplink data transmission in random access procedures. Prior Technology

[0003] In many wireless communication systems, random access procedures (RAMs) provide mobile devices with a means to initiate data transmissions to the network. Typically, RAMs are contention-based, where two or more such mobile devices vying to initiate their own data transmissions contend for radio resources. Sometimes, the RAMs executed by these contending devices can cause conflicts in their transmissions, thus inhibiting network reception from any one of the devices. Various RAMs have been developed to operate in the diverse wireless communication networks deployed today, featuring robust contention resolution mechanisms and fairly high reliability.

[0004] As the demand for mobile broadband access continues to increase, research and development are constantly advancing wireless communication technologies, not only to meet the growing demand for mobile broadband access, but also to improve and enhance the user experience of mobile communications. For example, random access procedures with further improved reliability and coverage can improve the user experience. Summary of the Invention

[0005] To provide a basic understanding of one or more aspects of the content of this case, a simplified overview of these aspects is provided below. This overview is not an exhaustive summary of all anticipated features of the content of this case, and is not intended to identify key or essential elements of all aspects of the content of this case, nor to illustrate the scope of any or all aspects of the content of this case. Its sole purpose is to present some concepts of one or more aspects of the content of this case in a simplified form as an introduction to the more detailed description that follows.

[0006] In general, this case relates to techniques for improving reliability and reducing latency. Features discussed below (e.g., redundancy version control techniques) can bring such benefits to various wireless communication scenarios. These can include, for example, physical uplink shared channels transmitted (and received by base stations) by user equipment via different repetitions of RVs. In some deployments, RV repetition can be performed according to an associated RV pattern. And in some cases, each RV can be based on a specific message to be transmitted or being transmitted by the user equipment (UE). Various other features associated with improved access procedures are discussed below.

[0007] In some embodiments of this application, the UE can initiate a random access procedure with the base station and send uplink (UL) messages to the base station as part of the random access procedure. The UE can receive a request from the base station to retransmit the UL message and determine an RV mode that may include a sequence of multiple redundant versions (RVs). The UE can respond to the received request by sending a UL message retransmission. The UL message retransmission may include multiple repetitions of the UL message. Each repetition can be configured based on the sequence according to the corresponding RV among the multiple RVs.

[0008] In one example, a method for wireless communication operable at a user equipment (UE) is disclosed. The method includes: receiving a Random Access Response (RAR) message from a base station as part of a random access procedure. The method also includes: sending uplink (UL) communication to the base station as part of the random access procedure, the UL communication comprising a plurality of repetitions of a UL message, each repetition being configured via a corresponding RV applying an RV pattern having a plurality of RVs to the UL message. The method further includes: receiving downlink messages from the base station based on the UL messages.

[0009] In another example, an apparatus for wireless communication is disclosed. The apparatus includes: a unit for receiving a Random Access Response (RAR) message from a base station as part of a random access procedure. The apparatus also includes: a unit for transmitting uplink (UL) communication to the base station as part of the random access procedure, the UL communication comprising a plurality of repetitions of a UL message, each repetition being configured via a corresponding RV applying an RV pattern having a plurality of RVs to the UL message. The apparatus further includes: a unit for receiving downlink messages from the base station based on the UL messages.

[0010] In another example, a non-transitory computer-readable medium storing computer-executable code is disclosed. The computer-executable code includes code for causing a user equipment (UE) to: receive a Random Access Response (RAR) message from a base station as part of a random access procedure. The computer-executable code also includes code for causing the UE to: send uplink (UL) communication to the base station as part of the random access procedure, the UL communication comprising a plurality of repetitions of a UL message, each repetition configured via a corresponding RV applying an RV pattern having a plurality of RVs to the UL message. The computer-executable code also includes code for causing the UE to: receive downlink messages from the base station based on the UL messages.

[0011] In another example, an apparatus for wireless communication is disclosed. The apparatus includes: a processor; a transceiver communicatively coupled to the processor; and memory communicatively coupled to the processor. The processor and the memory are configured to: as part of a random access procedure, receive a Random Access Response (RAR) message from a base station via the transceiver. The processor and the memory are also configured to: as part of the random access procedure, transmit uplink (UL) communication to the base station via the transceiver, the UL communication comprising a plurality of repetitions of a UL message, each repetition being configured by applying a corresponding RV of an RV pattern having a plurality of RVs to the UL message. The processor and the memory are also configured to: receive downlink messages from the base station via the transceiver based on the UL messages.

[0012] In another example, a method for wireless communication operable at a base station is disclosed. The method includes: receiving a random access request from a UE for initiating a random access procedure; and responding to the random access request by sending a random access response (RAR) message to the UE. The method also includes: as part of the random access procedure, receiving uplink (UL) communication from the UE, the UL communication comprising a plurality of repetitions of a UL message, each repetition having been configured via a corresponding RV applying an RV pattern having a plurality of RVs to the UL message. The method further includes: decoding the UL communication based on the RV pattern; and sending a downlink message to the UE based on the UL message.

[0013] In another example, an apparatus for wireless communication is disclosed. The apparatus includes: a processor; a transceiver communicatively coupled to the processor; and memory communicatively coupled to the processor. The processor and the memory are configured to: receive a random access request from a UE via the transceiver for initiating a random access procedure; and in response to the random access request, send a random access response (RAR) message to the UE via the transceiver. The processor and the memory are also configured to: as part of the random access procedure, receive uplink (UL) communication from the UE via the transceiver, the UL communication comprising a plurality of repetitions of a UL message, each repetition having been configured via a corresponding RV applying an RV pattern having a plurality of RVs to the UL message. The processor and the memory are also configured to: decode the UL communication based on the RV pattern; and send downlink messages to the UE via the transceiver based on the UL message.

[0014] These and other aspects of the techniques discussed herein will become more fully understood after reviewing the following detailed description. Other aspects, features, and embodiments will become apparent to those skilled in the art to which this invention pertains after reviewing the following description of specific, exemplary embodiments in conjunction with the accompanying drawings. Although the following description may discuss various advantages and features with respect to certain embodiments and drawings, all embodiments may include one or more of the advantageous features discussed herein. In other words, although this description may discuss one or more embodiments having certain advantageous features, one or more of these features may also be used according to the various embodiments discussed herein. Similarly, although this description may discuss exemplary embodiments as device, system, or method embodiments, it should be understood that these exemplary embodiments may be implemented in various devices, systems, and methods. Simple Explanation of the Diagram

[0015] Figure 1 is a schematic diagram of a wireless communication system according to some embodiments.

[0016] Figure 2 is a conceptual illustration of an example of a radio access network according to some embodiments.

[0017] Figure 3 is a conceptual illustration of a procedure for generating different redundancy versions (RVs) for a given transmission, according to some embodiments of the content of this case.

[0018] Figure 4 is a dialing flowchart illustrating a random access procedure according to some embodiments.

[0019] Figure 5 is a conceptual illustration of a Frequency Division Duplex (FDD) and Time Division Duplex (TDD) instance with uplink transmission (or retransmission) according to some embodiments of the present case, the uplink transmission (or retransmission) including multiple repetitions of messages according to the relevant RV mode.

[0020] Figure 6 is a dialing flowchart illustrating a random access procedure employing message repetition according to some embodiments.

[0021] Figure 7 is a block diagram conceptually illustrating an example of a hardware implementation for a scheduling entity according to some embodiments of the present case.

[0022] Figure 8 is a block diagram conceptually illustrating an example of a hardware implementation for a scheduled entity according to some embodiments of the present case.

[0023] Figure 9 is a flowchart illustrating an exemplary program for a random access procedure according to some embodiments of the present case.

[0024] Figure 10 is a flowchart illustrating another exemplary program for a random access procedure according to some embodiments of the present case.

[0025] Figure 11 is a flowchart illustrating another exemplary program for a random access procedure according to some embodiments of the present case. Implementation

[0026] The detailed description below, taken in conjunction with the accompanying drawings, is intended as a description of various configurations, and not as representing only the configurations in which the concepts described herein can be implemented. To provide a thorough understanding of the various concepts, the detailed description includes specific details. However, those skilled in the art to which this invention pertains will readily recognize that these concepts can be implemented without these specific details. In some instances, well-known structures and components are provided in block diagram form to avoid obscuring such concepts.

[0027] Although this description illustrates various forms and embodiments through the illustration of a few examples, it will be understood by those skilled in the art to which this invention pertains that additional implementations and use cases may arise in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, package arrangements, etc. For example, embodiments and / or uses may arise by integrating chip-level embodiments with other non-modular component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, AI-enabled devices, etc.). While some examples may or may not be specific to a particular use case or application, a wide variety of applicability to the described innovations can exist. Implementations can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or OEM devices or systems incorporating one or more forms of the described innovations. In some practical settings, devices incorporating the described forms and features may also necessary include additional components and features for the implementation and embodiment of the claimed and described embodiments. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / converters, etc.). The innovative intentions described herein can be implemented in various devices, chip-level components, systems, distributed arrangements, aggregated devices, disaggregated arrangements, end-user devices, etc., with different sizes, shapes, and constructions.

[0028] In various configurations, this application relates to improving the reliability (and preventing or mitigating latency) of the physical uplink shared channel transmitted by the user equipment (and received by the base station). In some deployments, such benefits can be obtained by utilizing different RVs, depending on the relevant RV pattern. Furthermore, in some scenarios, such benefits can be obtained when the RV is based on a specific message to be transmitted or being transmitted by the user equipment (UE). These techniques can be utilized in various network access scenarios.

[0029] In network access procedures, a wireless device can typically connect to another wireless device. For example, in random access procedures, a UE can send uplink (UL) communications to a base station. The communications may include multiple repetitions of UL messages (e.g., MSG3 messages, further described below). Each repetition may be an iteration of the UL message. UL messages can be configured by applying the corresponding RV in the sequence of RVs to the UL message. UL communications can be used for initial MSG3 messages (sent in response to a response to an access response (RAR) message) or retransmissions of MSG3 messages (sent in response to an MSG3 retransmission request). The sequence of RVs may be fixed and known to both the UE and the base station, or the sequence of RVs may be adaptable and indicated in information transmitted from the base station to the UE. By having the UE send multiple repetitions of UL messages, the base station can have increased capabilities to receive and decode UL messages.

[0030] The following disclosure provides various concepts that can be implemented in a wide variety of telecommunications systems, network architectures, and communication standards. Referring now to Figure 1, which is illustrated as an illustrative example rather than a limitation, this diagram illustrates various aspects of the present invention with reference to a wireless communication system 100. The wireless communication system 100 includes several interaction domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106. With the aid of the wireless communication system 100, the UE 106 can be implemented to perform data communication with an external data network 110 (such as, but not limited to, the Internet).

[0031] RAN 104 can implement any one or more suitable radio communication technologies to provide radio access to UE 106. As an example, RAN 104 can operate according to the 3GPP New Radio (NR) specification (often referred to as 5G). As another example, RAN 104 can operate according to a hybrid of 5G NR and the Evolutionary Universal Terrestrial Radio Access Network (eUTRAN) standard (often referred to as LTE). 3GPP refers to this hybrid RAN as Next Generation RAN or NG-RAN. Of course, many other examples can be utilized within the scope of this case.

[0032] As shown in the figure, RAN 104 includes a plurality of base stations 108. Broadly speaking, a base station is a network element in a radio access network responsible for radio transmission and reception to or from a UE within one or more cells. In different technologies, standards, or contexts, those skilled in the art to which this invention pertains may refer to a base station transceiver (BTS), radio base station, radio transceiver, transceiver functional unit, basic service set (BSS), extended service set (ESS), access point (AP), node B (NB), evolved node B (eNB), gNodeB (gNB), or some other suitable term.

[0033] Radio Access Network 104 supports wireless communication for multiple mobile devices. In 3GPP standards, those skilled in the art may refer to a mobile device as a User Equipment (UE), but it may also be referred to as a Mobile Station (MS), User Station, Mobile Unit, User Unit, Radio Unit, Remote Unit, Mobile Device, Radio Device, Wireless Communication Device, Remote Device, Mobile Subscriber Station, Access Terminal (AT), Mobile Terminal, Wireless Terminal, Remote Terminal, Mobile Phone, Terminal, User Agent, Mobile Service User Client, User Client, or any other suitable term. The UE can be a device that provides access to network services. The UE can take many forms and may include a series of devices.

[0034] In this document, a "mobile" device (also referred to as a UE) does not necessarily need to be mobile and can be stationary. The term mobile device or mobile equipment broadly represents a wide variety of devices and technologies. A UE may include multiple hardware components whose size, shape, and arrangement are configured to facilitate communication; such components may include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc., electrically coupled to each other. For example, some non-limiting examples of mobile devices include mobile stations, cellular phones, smartphones, conversation initiation protocol (SIP) phones, laptops, personal computers (PCs), notebooks, netbooks, smart computers, tablet devices, personal digital assistants (PDAs), and a wide variety of embedded systems, such as those corresponding to the "Internet of Things" (IoT). Additionally, mobile devices can be automobiles or other vehicles, remote sensors or actuators, robots or robotic devices, satellite radio units, Global Positioning System (GPS) devices, object tracking devices, drones, multi-rotor helicopters, quadcopter helicopters, remote control devices, consumer devices and / or wearable devices such as glasses, wearable cameras, virtual reality devices, smartwatches, health or fitness trackers, digital audio players (e.g., MP3 players), cameras, game consoles, etc. Furthermore, mobile devices can be digital home or smart home devices, such as home audio, video and / or multimedia equipment, home appliances, vending machines, smart lighting, home security systems, smart meters, etc. Additionally, mobile devices can be smart energy devices, security devices, solar panels or solar arrays, municipal infrastructure equipment controlling electricity (e.g., smart grids), lighting, water, etc.; industrial automation and enterprise equipment; logistics controllers; agricultural equipment; military defense equipment, vehicles, aircraft, ships, weapons, etc. Furthermore, mobile devices can provide connected medical or remote medical support (e.g., telemedicine). Remote medical devices may include remote medical monitoring devices and remote medical management devices, whose communications may be given preferential treatment or priority access relative to other types of information, such as priority access to the transmission of critical service data, and / or relevant QoS patterns for the transmission of critical service data.

[0035] Radio communication between RAN 104 and UE 106 can be described as utilizing an air interface. Transmissions over the air interface from a base station (e.g., base station 108) to one or more UEs (e.g., UE 106) can be referred to as downlink (DL) transmissions. According to certain embodiments of this application, the term downlink can represent point-to-multipoint transmissions originating from a scheduling entity (further described below; e.g., base station 108). Another way to describe this scheme is to use the term broadcast channel multiplexing. Transmissions from a UE (e.g., UE 106) to a base station (e.g., base station 108) can be referred to as uplink (UL) transmissions. According to another embodiment of this application, the term uplink can represent point-to-point transmissions originating from a scheduled entity (further described below; e.g., UE 106).

[0036] In some instances, access to the empty intermediary plane can be scheduled, where a scheduling entity (e.g., base station 108) allocates resources for communication among some or all devices and apparatuses within its service area or cell. In this context, as further discussed below, the scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities. That is, for scheduled communication, UE 106 (which may be a scheduled entity) can use the resources allocated by scheduling entity 108.

[0037] Base station 108 is not the only entity that can act as a scheduling entity. That is, in some instances, a UE can act as a scheduling entity, scheduling for resources of one or more scheduled entities (e.g., one or more other UEs).

[0038] As shown in Figure 1, scheduling entity 108 can broadcast downlink traffic 112 to one or more scheduled entities 106. Broadly speaking, scheduling entity 108 is a node or device responsible for scheduling traffic (including downlink traffic 112, and in some instances, uplink traffic 116 from one or more scheduled entities 106 to scheduling entity 108) in a wireless communication network. Alternatively, scheduled entity 106 is a node or device that receives downlink control information 114 (including but not limited to scheduling information (e.g., permission), synchronization or timing information, or other control information) from another entity in the wireless communication network (e.g., scheduling entity 108).

[0039] Typically, base station 108 may include a backload interface for communicating with the backload portion 120 of a wireless communication system. Backload 120 can provide a link between base station 108 and core network 102. Furthermore, in some instances, a backload network can provide interconnection between the respective base stations 108. Various types of backload interfaces can be used, such as direct physical connections, virtual networks, or backload interfaces using any suitable transport network.

[0040] The core network 102 may be part of the wireless communication system 100 and may be independent of the radio access technology used in the RAN 104. In some instances, the core network 102 may be configured according to a 5G standard (e.g., 5GC). In other instances, the core network 102 may be configured according to 4G Evolved Packet Core (EPC) or any other suitable standard or configuration.

[0041] For example, rather than limiting, Figure 2 provides a schematic diagram of RAN 200. In some instances, RAN 200 may be identical to RAN 104, as described above and shown in Figure 1. The geographical area covered by RAN 200 may be divided into multiple cellular regions (cells), which user equipment (UEs) may uniquely identify based on an identifier broadcast from an access point or base station. Figure 2 illustrates macro cells 202, 204, and 206, and small cell 208, each of which may include one or more sectors (not shown). A sector is a sub-region of a cell. All sectors within a cell are served by the same base station. Radio links within a sector may be identified via a single logical identifier belonging to that sector. In a cell divided into multiple sectors, the multiple sectors within the cell may be formed via multiple sets of antennas, each antenna responsible for communicating with UEs within a portion of the cell.

[0042] Figure 2 illustrates two base stations 210 and 212 in cells 202 and 204; and a third base station 214 in cell 206, which controls the remote radio head (RRH) 216. That is, the base stations can have integrated antennas, or can be wired to an antenna or RRH via feed cables. In the illustrated example, cells 202, 204, and 206 can be referred to as macrocells because base stations 210, 212, and 214 support cells with large sizes. Furthermore, base station 218 is illustrated in small cells 208 (e.g., microcells, picocells, femtocells, home base stations, home node Bs, home eNodeBs, etc.), where small cells 208 can overlap with one or more macrocells. In this example, cell 208 can be referred to as a small cell because base station 218 supports cells with relatively small sizes. Cell size settings can be made according to system design and component constraints.

[0043] RAN 200 may include any number of wireless base stations and cells. Furthermore, the RAN may include relay nodes to extend the size or coverage area of ​​a given cell. Base stations 210, 212, 214, and 218 provide wireless access points to the core network for any number of mobile devices. In some instances, base stations 210, 212, 214, and / or 218 may be identical to the base station / schedule entity 108 described above and shown in Figure 1.

[0044] Figure 2 also includes a quadcopter or drone 220, which can be configured to act as a base station. That is, in some instances, the cell may not be stationary, and the geographic area of ​​the cell may move depending on the location of the mobile base station (e.g., the quadcopter 220).

[0045] In RAN 200, a cell may include UEs capable of communicating with one or more sectors of each cell. Furthermore, each base station 210, 212, 214, 218, and 220 may be configured to provide access points to core network 102 (see Figure 1) to all UEs in the corresponding cell. For example, UEs 222 and 224 may communicate with base station 210; UEs 226 and 228 may communicate with base station 212; UEs 230 and 232 may communicate with base station 214 via RRH 216; UE 234 may communicate with base station 218; and UE 236 may communicate with mobile base station 220. In some instances, UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240 and / or 242 may be the same as the UE / scheduled entity 106 described above and shown in Figure 1.

[0046] In some instances, mobile network nodes (e.g., quadcopter 220) can be configured to act as UEs. For example, quadcopter 220 can operate in cell 202 by communicating with base station 210.

[0047] In another configuration of RAN 200, sidelink signals can be used between UEs without relying on scheduling or control information from the base station. For example, two or more UEs (e.g., UEs 226 and 228) can communicate with each other using point-to-point (P2P) or sidelink signal 227 without relaying the communication via a base station (e.g., base station 212). In another instance, UE 238 is shown communicating with UEs 240 and 242. Here, UE 238 can act as a scheduling entity or a primary sidelink device, and UEs 240 and 242 can act as scheduled entities or non-primary (e.g., secondary) sidelink devices. In yet another instance, a UE can act as a scheduling entity in a device-to-device (D2D), point-to-point (P2P), or vehicle-to-vehicle (V2V) network and / or mesh network. In a mesh network example, UEs 240 and 242 can optionally communicate directly with each other, in addition to communicating with scheduling entity 238. Therefore, in a wireless communication system with scheduled access to time and frequency resources and with cellular, P2P, or mesh configurations, the scheduling entity and one or more scheduled entities can use the scheduled resources to communicate.

[0048] In radio access network 200, the ability of a UE to communicate while on the move (regardless of its location) is referred to as mobility. Access and Mobility Management Functions (AMF, not shown, but part of core network 102 in Figure 1) typically set up, maintain, and release various physical channels between the UE and the radio access network. AMF may also include Security Context Management Functions (SCMF) that manage the security context of both control plane and user plane functions, and Security Anchoring Functions (SEAF) that perform authentication.

[0049] In various implementations, the air interface in RAN 200 can utilize licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum typically provides exclusive use of a portion of the spectrum by means of licenses purchased from government regulatory agencies by mobile network service providers. Unlicensed spectrum provides shared use of a portion of the spectrum without requiring a government-approved license. Although some technical rules are usually still required to access unlicensed spectrum, in general, any service provider or device can obtain access. Shared spectrum can fall between licensed and unlicensed spectrum, where some technical rules or restrictions may be required to access the spectrum, but the spectrum can still be shared by multiple service providers and / or multiple RATs. For example, a licensee of a portion of licensed spectrum can provide licensed shared access (LSA) to share the spectrum with other parties (e.g., with conditions determined by the appropriate licensee for access).

[0050] The air interface in RAN 200 can use one or more duplex algorithms. Duplex represents a point-to-point communication link where two endpoints can communicate with each other in both directions. Full-duplex means that two endpoints can communicate with each other simultaneously. Half-duplex means that at any given time, only one endpoint can use the given resources to send information to the other endpoint. In radio links, full-duplex channels typically rely on physical isolation between the transmitter and receiver and appropriate interference cancellation techniques. Full-duplex simulation is often implemented for radio links using Frequency Division Duplex (FDD) or Time Division Duplex (TDD). In FDD, transmissions in different directions operate at different carrier frequencies. In TDD, transmissions in different directions on a given channel are separated from each other using time division multiplexing. That is, at some times, the channel is dedicated to transmission in one direction, and at other times, the channel is dedicated to transmission in the other direction, where the direction can change very quickly (e.g., several times per time slot).

[0051] The air interface in the radio access network 200 can utilize one or more multiplexing and multiplexing access algorithms to achieve simultaneous communication between various devices. For example, the 5G NR specification provides multiplexing access for UL transmissions from UEs 222 and 224 to base station 210, and multiplexing for DL ​​transmissions from base station 210 to one or more UEs 222 and 224 using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP). Additionally, for UL transmissions, the 5G NR specification provides support for Discrete Fourier Transform Spread Spectrum OFDM (DFT-s-OFDM) with CP (also known as Single Carrier FDMA (SC-FDMA)). However, within the scope of this application, multiplexing and multiplexing access are not limited to the above schemes. For example, the UE can utilize Time Division Multiple Access (TDMA), Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Sparse Code Multiple Access (SCMA), Resource Extended Multiple Access (RSMA), or other suitable multiplexing schemes to provide UL multiplexing access. Furthermore, the base station can utilize Time Division Multiple Access (TDM), Code Division Multiple Access (CDM), Frequency Division Multiple Access (FDM), Orthogonal Frequency Division Multiple Access (OFDM), Sparse Code Multiple Access (SCM), or other suitable multiplexing schemes to multiplex the DL transmissions to the UE.

[0052] To achieve a low block error rate (BLER) while still maintaining a very high data rate, channel coding can be used for transmissions on the radio access network 200. That is, wireless communication can typically utilize appropriate error-correcting block codes. In typical block codes, information messages or sequences are broken down into code blocks (CBs), and then an encoder (e.g., a transcoder) at the transmitting device mathematically adds redundancy to the information message. This redundancy in the encoded information message improves message reliability and corrects for bit errors that may occur due to noise.

[0053] In the 5G NR specification, quasi-cyclic low-density parity checking (LDPC) with two different basemaps can be used to decode user data: one basemap for large code blocks and / or high code rates, and the other for other cases. Polar coding can be used based on nested sequences to decode control information and Entity Broadcast Channel (PBCH). For these channels, puncturing, shortening, and rework are performed for rate matching.

[0054] However, those skilled in the art will understand that various forms of the present invention can be implemented using any suitable channel code. Various implementations of the scheduling entity 108 and the scheduled entity 106 may include appropriate hardware and capabilities (e.g., encoders, decoders, and / or transcoders) to use one or more of these channel codes for wireless communication.

[0055] As mentioned above, additional techniques can further improve transmission reliability when used in conjunction with channel coding. For example, Hybrid Automatic Repeat Request (HARQ) is a technique well known to those skilled in the art to which this invention pertains, where the receiving device can verify the integrity of the received packets using any suitable integrity checking mechanism, such as checksums or cyclic redundancy checks (CRC). If the integrity of the transmission is confirmed, the receiving device can send an ACK; otherwise, it can send a NACK. In response to a NACK, the transmitting device can send a HARQ retransmission, which can implement append merging, incremental redundancy, etc. For append merging, the retransmission typically includes the same information as the original transmission. Here, the receiving device can use maximum ratio merging of the corresponding transmissions to merge the received power of sequential transmissions and improve the probability of accurate bit assumptions. However, for incremental redundancy, each retransmission typically includes information different from the original transmission and information that is different from each other. The transmitting device generates multiple sets of encoded information and configures each retransmission with different redundancy versions (RVs) by punching the encoder output. At each retransmission point, the receiving device receives additional information, thereby increasing the probability of a correct assumption at each retransmission point.

[0056] Figure 3 illustrates a conceptual diagram of a procedure 300 for generating packets with an RV corresponding to a determined RV mode for a given transmission, according to some aspects of the present invention. For example, the transmitting device may begin procedure 300 using information bits 302 that the transmitting device can transmit. The transmitting device may calculate Cyclic Redundancy Check (CRC) bits and append or append these CRC bits to the information bits. In some scenarios, the transmitting device may scramble the CRC bits using an appropriate Radio Network Temporary Identifier (RNTI) (e.g., suitable for the transmission type), as indicated in block 304. Alternatively, the transmitting device may utilize an appropriate channel decoding algorithm 306, as described above, to generate decoded bits 308. The encoder of the transmitting device may implement one or more blocks 306 and 304 to modify information bits 302 and generate decoded bits 308 as output. To generate different RVs for the decoded bits 308, the transmitting device can utilize redundancy version 310 to appropriately "punch" the decoded bits 308 output by the encoder. Redundancy version 310 can represent an RV of redundancy version (RV) mode. When the transmitting device applies an RV of RV mode to the decoded bits 308, the transmitting device generates different RVs 312, 314, 316, 318 for the decoded bits 308 intended for transmission. Each of RVs 312, 314, 316, 318 can correspond to a specific RV of the decoded bits 308. Each RV of the decoded bits 308 can contain different numbers of decoded bits and / or different portions of the complete set of decoded bits 308. In particular, as shown in FIG3, RV 312 corresponds to RV-0, RV 314 corresponds to RV-1, RV 316 corresponds to RV-2, and RV 318 corresponds to RV-3. Figure 3 further illustrates three instance RV configurations 320, 322, and 324 that the transmitting device can generate for RVs 312, 314, 316, and 318. Each of RV configurations 320, 322, and 324 can be associated with a different RV mode used by the transmitting device to generate each corresponding RV configuration 320, 322, and 324.

[0057] In an exemplary RV configuration 320, RV 312 (corresponding to RV-0) is the entire transmission of decoded bits 308 (e.g., the entire string of decoded bits 308), while each of RVs 314, 316, and 318 has a different segment of the string of decoded bits 308. For example, RV 314 has only the first (or beginning) portion of the string of decoded bits 308, RV 316 has only the middle portion of the string of decoded bits 308, and RV 318 has the end portion of the string of decoded bits 308.

[0058] In another exemplary RV configuration 322, RV 312 is the entire transmission of decoded bits 308, and each of RVs 314, 316, and 318 has a different but overlapping portion of the string of decoded bits 308. For example, RV 314 has the last two-thirds of the string of decoded bits 308, RV 316 has the last half of the string of decoded bits 308, and RV 318 has the last one-third of the string of decoded bits 308.

[0059] In another exemplary RV configuration 324, RV 312 is the entire transmission of decoded bits 308 in the order defined by the string of decoded bits 308. In this configuration (different from configurations 320, 322), the other RVs 314, 316, 318 all have the entire string of decoded bits 308, but are cyclically shifted by different amounts (e.g., the entire string of decoded bits 308 is in each of RVs 314, 316, 318, but the difference between RVs 314, 316, 318 is that they are each cyclically shifted versions of decoded bits 308 with different starting positions).

[0060] RV configurations 320, 322, and 324 can be defined by various RV arrangements and compositions. For example, as shown, RV 312 has a start point "A" and an end point "Z" defining the decoded bit string of RV 312 (e.g., the order of decoded bits 308). In this configuration, RV 314 has a start position approximately one-third of the distance from "A", and therefore RV 314 effectively "skips" the transmission of the first third of the decoded bit string, and transmits them after the remaining two-thirds of the decoded bit string has been transmitted (as defined by the start position). Similarly, in this configuration, RV 316 has a start position approximately half the distance from "A", and therefore RV 316 "skips" the transmission of the first half of the decoded bit string, and transmits them after the second half of the decoded bit string has been transmitted (as defined by the start position). Finally, in this configuration, RV 318 has a starting position approximately two-thirds the distance from "A", and therefore RV 318 "skips" the first two-thirds of the transmission of the decoded bit string, and sends the rest after the last third of the decoded bit string has been sent (as defined by the starting position). Thus, effectively, RVs 314, 316, and 318 adjust the order of the decoded bit string, or in other words, each of RVs 314, 316, and 318 manipulates the order of the decoded bit string as defined by the string of decoded bits 308 (or RV 312, which is substantially similar to the string of decoded bits 308).

[0061] Those skilled in the art will recognize that these examples are merely illustrative in nature and are not intended to provide all suitable RV configurations. That is, any suitable RV configuration can be used within the scope of this invention.

[0062] Regardless of the specific RV configuration (e.g., 320, 322, 324, or any other suitable RV configuration), using different RVs in different retransmissions can help ensure that the base station correctly receives and decodes the message defined in the string of decoded bits. For example, if the base station receives multiple repetitions of a packet or message (according to different corresponding RVs, such as RV 312 (RV-0) and RV 316 (RV-2) configurations), this can increase the likelihood that the base station can reliably receive (and decode) the message. More specifically, by receiving and appropriately combining multiple RVs, the base station is more likely to successfully receive and decode the message.

[0063] As shown in Figure 3, the UE can utilize (or determine) a specific RV (at 310) to generate any one of RVs 312, 314, 316, and 318 based on the RV configuration (e.g., configurations 320, 322, and 324). Further utilization of RVs will be described in more detail below.

[0064] Figure 4 is a dialing flowchart 400 of an exemplary random access procedure as described in the 3GPP specification for 5G NR. As shown, a scheduled entity 402, such as a UE, communicates with a scheduling entity 404, such as a base station or gNB. The following description refers to the scheduled entity 402 as a UE and the scheduling entity 404 as a base station; however, it is understood that other scheduled entities and scheduling entities may be appropriately substituted in other configurations.

[0065] As shown in the figure, UE 402 can receive system information (e.g., via System Information Block (SIB) 401) from base station 404. For example, base station 404 can periodically broadcast system information on the corresponding cell, and / or UE 402 can request on-demand transmission of system information. The SIB may contain system information, including cell access information, which, when received by UE 402, enables UE 402 to initiate a random access procedure.

[0066] UE 402 may send a RACH preamble signal 403 to base station 404 on the Physical Random Access Channel (PRACH). This message 403 may be equivalently referred to as Random Access Request or Message 1 (MSG1). If base station 404 receives MSG1 403, base station 404 may derive the Random Access Radio Network Temporary Identifier (RA-RNTI) corresponding to UE 402 (e.g., based on MSG1 403).

[0067] If base station 404 correctly receives and decodes the MSG1 transmission, then in response, base station 404 may send a random access response 406 to the UE. For example, base station 404 may send a PDCCH (which includes a DCI with a CRC scrambled via RA-RNTI) and a corresponding PDSCH (which includes a RAR, which is equivalently referred to as message 2 (MSG2)).

[0068] Therefore, after sending MSG1 403, UE 402 can monitor the random access response message 406 from base station 404. That is, UE 402 can monitor the PDCCH, which includes a DCI with a CRC scrambled via RA-RNTI. However, if base station 404 does not correctly receive or decode the MSG1 transmission, base station 404 may not send such a response. Here, if UE 402 does not receive its expected response, for example, after an appropriate timeout period, UE 402 may subsequently retransmit MSG1 403 once or multiple times.

[0069] In the dialing flow 400 shown, UE 402 receives a response 406 from base station 404. The response 406 includes: a PDCCH carrying a DCI with a CRC scrambled via RA-RNTI; and a corresponding PDSCH carrying MSG2 / RAR. In addition, the random access response message 406 may provide UE 402 with permission or scheduling information indicating UL resources for UE 402 to use for UL transmissions (e.g., for MSG3, further described below). Furthermore, the random access response message 406 may provide UE 402 with a Temporary Cellular Radio Network Temporary Identifier (TC-RNTI). UE 402 may employ the TC-RNTI in subsequent stages of the random access procedure of dialing flow 400, as further described below.

[0070] When UE 402 receives the Random Access Response 406, the UE may then send Random Access Procedure Message 3 (MSG3) 408. Here, MSG3 may include any suitable information, and in some instances, may be located on the PUSCH. Here, UE 402 may utilize the resources corresponding to the UL permission received in the DCI in RAR message 406.

[0071] After sending MSG3 408, UE 402 can monitor the PDCCH transmission as a response from base station 404. Here, if base station 404 correctly receives and decodes MSG3 408, base station 404 can send the corresponding random access procedure message 4 (MSG4).

[0072] In some cases, such as the scenario shown in Figure 4, base station 404 may fail to correctly receive or decode MSG3 408. This failure could be attributed to interference between similar signals (e.g., multiple UEs transmitting), insufficient transmission power of UE 402 to MSG3, or a considerable distance between UE 402 and the base station. In some cases, base station 404 may decide to send an MSG3 retransmission request 410 after failing to correctly receive (and decode) MSG3 408 for a period of time. In other configurations, base station 404 may decide whether to request a retransmission of MSG3 based on other parameters and conditions (e.g., the number of correctly decoded MSG3s).

[0073] Therefore, base station 404 can send a UE retransmission request for MSG3. In some configurations, the MSG3 retransmission request message 410 may include a PDCCH carrying a DCI with a CRC scrambled via the TC-RNTI indicated in the Random Access Response message 406.

[0074] In the MSG3 retransmission request message 410, the base station 404 may include resource configuration or permission for the time and frequency resources for the UE 402 to use for the corresponding MSG3 retransmission.

[0075] In response to MSG3 retransmission request 410, UE 402 may send MSG3 retransmission 412. In some instances, UE 402 may apply RV to MSG3 retransmission 412, as indicated by the RV information element signaled to UE 402 as part of MSG3 retransmission request 410.

[0076] If UE 402 does not receive MSG4 transmission 414, it can send multiple retransmissions of MSG3. In some existing networks, this problem may occur somewhat frequently due to unreliable MSG3 reception at the gNB. Furthermore, when the UE uses multiple retransmissions of MSG3, this can lead to increased latency in the RACH procedure.

[0077] According to one aspect of this case, the UE can employ MSG3 repetition (described further below) to improve MSG3 reliability and extend MSG3 coverage within a given cell. In some instances, the UE can use MSG3 repetition solely for MSG3 UE retransmissions; while in other instances, the UE can multiplex MSG3 repetition for both initial MSG3 transmission and MSG3 retransmission.

[0078] In another aspect of this application, to potentially further improve MSG3 reliability and coverage, the UE may apply different RVs in the corresponding MSG3 repetitions. Some aspects of this application involve the UE deciding which RV to use for a given repetition in the transmission (and / or retransmission) of MSG3 employing MSG3 repetition.

[0079] For example, Figure 5 illustrates a conceptual diagram of a transmission (e.g., an MSG3 transmission). In some deployments, as shown, a transmission may include multiple (e.g., two or more) repetitions of a given packet or message. In some scenarios, the repetition may employ an RV corresponding to an RV mode. Alternatively or additionally, some RVs used may be determined via the RV mode corresponding to the corresponding packet or message in the repetition. For example, a first example 500 illustrates such a transmission on a time-division duplex (TDD) carrier. A second example 502 illustrates such a transmission on a frequency-division duplex (FDD) carrier. As further described below, the UE may determine the appropriate RV mode for a transmission including multiple repetitions of a specific message, for example, by transmitting the corresponding repetitions on a physical uplink shared channel (PUSCH) in multiple corresponding time slots.

[0080] In Example 500, two time slots, labeled 504 and 505, are illustrated on a TDD carrier. The first time slot 504 includes a first region 506 (which may include uplink, downlink, or a suitable combination thereof) and an uplink short pulse region 508. The uplink short pulse region 508 may include a PUSCH on which a given UE has resource allocation or permission for uplink transmission. As shown, the second time slot 505 has a similar format, including a first region 510 and an uplink short pulse region 512. According to one aspect of this invention, the UE can transmit multiple repetitions of a given packet or message on the PUSCH in the corresponding time slot, depending on the determined RV mode.

[0081] Although time slots 504 and 505 are shown as consecutive, in other instances these time slots may not be consecutive. That is, gaps between one or more time slots may appear between repetitions of messages transmitted as described herein. Furthermore, although only two time slots 504 and 505 are illustrated for instance 500, in other instances the UE may transmit any suitable number of r repetitions corresponding to the appropriate RV mode across the set of time slots.

[0082] In Example 502, the uplink component carrier of the FDD carrier includes two uplink time slots 514 and 516, and the downlink component carrier includes two downlink time slots 518 and 520. The first uplink time slot 514 may include a PUSCH on which a given UE has resource assignments or permissions for uplink transmission. According to one aspect of this invention, the UE can transmit multiple repetitions of a given packet or message on the PUSCH in the corresponding uplink time slot according to the determined RV mode. Similar to Example 500, in Example 502, although uplink time slots 514 and 516 are shown as consecutive, in other examples, these UL time slots may not be consecutive. That is, gaps between one or more time slots may appear between repetitions of messages transmitted as described herein. In addition, although only two uplink time slots 514 and 516 are illustrated for Example 502, in other examples, the UE may transmit any suitable number of r repetitions corresponding to the determined RV mode. RV mode determination for transmission repetition

[0083] According to various aspects of the present invention, as mentioned above, the UE can perform multiplexing on a given transmission (e.g., MSG3 of the RACH procedure). Repeating can be defined based on a determined RV pattern. Here, an RV pattern refers to a sequence or series of r RVs. In some scenarios, a given RV pattern can include any appropriate number of r RVs, where r is a two (2) or larger integer. Other r values ​​can be used as needed or for operational performance characteristics of interest. Figure 6 is a dialing flowchart 600 of an exemplary random access procedure involving UE 602 and base station 604 according to some aspects of the present invention, where UE 602 uses MSG3 repeating.

[0084] As shown in the figure, UE 602 can receive system information (e.g., via a System Information Block, SIB) 601 from base station 604. For example, base station 604 can periodically broadcast system information on the corresponding cell, and / or UE 602 can request on-demand transmission of system information. The SIB may contain system information, including cell access information, which, when received by UE 602, enables UE 602 to initiate a random access procedure. In some embodiments of this invention, the system information message (e.g., SIB) may also include RV configuration information, as further described below in conjunction with Figure 9. For example, the UE may use the RV configuration message received in the system information message to configure the RV mode for initial MSG3 transmission and / or MSG3 retransmission.

[0085] UE 602 may send a random access request or RACH preamble signal 603 to base station 604 on the Physical Random Access Channel (PRACH). This message 603 may be equivalently referred to as message 1 (MSG1). If base station 604 receives MSG1 603, base station 604 may derive the Random Access Radio Network Temporary Identifier (RA-RNTI) corresponding to UE 602 (e.g., based on MSG1 603).

[0086] If base station 604 correctly receives and decodes the MSG1 transmission, it can send a random access response 606 to the UE in response. For example, base station 604 can send a PDCCH including a DCI with a CRC scrambled via RA-RNTI; a DCI for scheduling the corresponding PDSCH; and the corresponding PDSCH including a RAR, which is equivalently referred to as message 2 (MSG2). In various instances, the DCI for scheduling the PDSCH carrying the RAR message 606 can utilize DCI format 1_0. Furthermore, the random access response message 606 can provide UE 602 with permission or scheduling information indicating UL resources for UE 602 to use for UL transmissions (e.g., for MSG3). Additionally, the random access response message 606 can provide UE 602 with a TC-RNTI. UE 602 can use the TC-RNTI in subsequent stages of the random access procedure of the dialing flow 600, as described further below.

[0087] Therefore, after sending MSG1 603, UE 602 can monitor the random access response message 606 from base station 604. That is, UE 602 can monitor the PDCCH, which includes a DCI with a CRC scrambled via RA-RNTI. However, if base station 604 does not correctly receive or decode the MSG1 transmission, base station 604 may not send such a response. Here, if UE 602 does not receive its expected response, for example, after an appropriate timeout period, UE 602 may subsequently retransmit MSG1 603 once or multiple times.

[0088] In the dialing flow 600 shown, UE 602 receives a random access response message 606 from base station 604. Here, the random access response message 606 may include a PDCCH carrying a DCI with a CRC scrambled via RA-RNTI.

[0089] In some configurations, UE 602 can be configured to not utilize or employ MSG3 repetition as described herein for the initial MSG3 transmission 608. In such instances, UE 602 can utilize the RV notified to UE 602 by base station 604, for example, in the Random Access Response message 606. That is, in some instances, base station 604 can provide an RV information element in the Random Access Response message 606, which UE 602 can use for the initial, non-repeating MSG3 transmission.

[0090] Furthermore, corresponding to the RACH procedure supporting MSG3 repetition for the initial MSG3 transmission, the Random Access Response (RAR) message 606 can provide the UE with an RV configuration message, as further described below in conjunction with Figure 9. For example, the DCI used for scheduling the PDSCH carrying the RAR message 606 can utilize DCI format 1_0, and can utilize one or more bits in DCI format 1_0 (e.g., reserved bits in existing specifications) to indicate the RV configuration message. Specifically, according to existing specifications for 3GPP 5G NR, in different configurations, a DCI with format 1_0 can include a set of 14 or 16 reserved bits. Therefore, the base station or gNB can use one or more of these otherwise reserved bits as repurposed bits to provide the RV configuration message to the UE.

[0091] When UE 602 receives the Random Access Response 606, the UE may then send Random Access Procedure Message 3 (MSG3) 608. Here, MSG3 may include any suitable information, and in some instances, may be located on the PUSCH. Here, UE 602 may utilize the resources corresponding to the UL permission received in the DCI in RAR message 606.

[0092] In some instances, UE 602 may determine the RV mode and repeat the initial MSG3 transmission 608, as further described below in conjunction with Figure 9. However, in other instances, UE 602 may not implement repetition for the initial MSG3 transmission 608 and may transmit the initial MSG3 transmission without repetition, as disclosed herein.

[0093] After sending MSG3 608, UE 602 can monitor PDCCH transmissions from base station 604. Here, if base station 604 correctly receives and decodes MSG3 608, base station 604 can send the corresponding random access procedure message 4 (MSG4). Such MSG4 transmissions may include a PDCCH containing a DCI with a CRC scrambled via the TC-RNTI indicated in random access response message 606. The transmission may also include a corresponding PDSCH carrying MSG4.

[0094] In some cases, such as the scenario shown in Figure 6, base station 604 may not correctly receive or decode MSG3 608. In some cases, base station 604 may decide to send an MSG3 retransmission request 610 after failing to correctly receive (and decode) MSG3 608 for a period of time. In other configurations, base station 604 may decide whether to request MSG3 retransmission based on other parameters and conditions (e.g., the number of correctly decoded MSG3s).

[0095] Therefore, base station 604 can send a UE retransmission request for MSG3. In some configurations, the MSG3 retransmission request message 610 may include a PDCCH carrying a DCI with a CRC scrambled via the TC-RNTI indicated in the Random Access Response message 606.

[0096] According to one aspect of this case, corresponding to the RACH procedure that is not supported for initial MSG3 transmission 608 but only for MSG3 retransmission, the MSG3 retransmission request message 610 can provide RV configuration information to the UE, as further described below in conjunction with Figure 9. For example, the DCI in the MSG3 retransmission request message 610 can utilize DCI format 0_0. According to the existing 3GPP specifications for 5G NR, DCI format 0_0 includes the following information (and other information): one (reserved) bit identified as a new data indicator; two bits (RV information element) used to indicate the redundant version; and four (reserved) bits identified as the HARQ procedure number. Therefore, the base station or gNB can use one or more bits (e.g., the retargeted one-bit new data indicator and / or the four-bit HARQ procedure number) as the retargeted bit in DCI format 0_0 or use the redundant version field in DCI format 0_0 to indicate RV configuration information to the UE.

[0097] According to one aspect of this case, corresponding to the RACH procedure supporting MSG3 repetition for initial MSG3 transmission 608 and MSG3 retransmission 612, the UE receiving the MSG3 retransmission request 610 may already have an existing RV configuration and determined RV mode for MSG3 repetition corresponding to initial MSG3 transmission 608 (and / or system information message 601). Here, in some instances, such a UE can continue to use the existing RV configuration and determined RV mode for MSG3 retransmission 612.

[0098] However, in another instance, the base station or gNB can override such existing RV configurations and / or determined RV modes, and signal the new RV configuration and / or RV mode indication to the UE via DCI format 0_0 for the MSG3 retransmission request message 610. For example, the DCI in the MSG3 retransmission request message 610 can utilize DCI format 0_0, and can utilize one or more bits in DCI format 0_0 (e.g., a retargeted 1-bit new data indicator and / or a 4-bit HARQ procedure number) to indicate the RV configuration message.

[0099] In the MSG3 retransmission request message 610, the base station 604 may also include resource configuration or permission for the time and frequency resources used by the UE 602 for the corresponding MSG3 retransmission.

[0100] In response to MSG3 retransmission request 610, UE 602 may send MSG3 retransmission 612. According to one aspect of this case, UE 602 may determine RV mode and use repetition for MSG3 retransmission 612, as further described below in conjunction with Figure 9.

[0101] This procedure can be repeated multiple times, wherein if UE 602 does not receive MSG4 transmission 614, it sends multiple retransmissions of MSG3. In the example shown, base station 604 sends MSG4 transmission 614 after correctly receiving and decoding MSG3 retransmission 612.

[0102] Figure 7 is a block diagram illustrating an example of the hardware implementation of a scheduling entity 700 employing a processing system 714. For example, the scheduling entity 700 may be a user equipment (UE) as shown in any one or more of Figures 1, 2, 4, and / or 6. In another example, the scheduling entity 700 may be a base station as shown in any one or more of Figures 1, 2, 4, and / or 6.

[0103] Scheduling entity 700 may include a processing system 714 having one or more processors 704. Examples of processors 704 include microprocessors, microcontrollers, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, individual hardware circuitry, and other suitable hardware configured to perform the various functions described herein. In various instances, scheduling entity 700 may be configured to perform any one or more of the functions described herein. That is, the processor 704 utilized in scheduling entity 700 may be configured (e.g., in coordination with memory 705) to implement any one or more of the processes and programs described below and shown in Figures 6, 9, 10, and / or 11.

[0104] Processing system 714 can be implemented using a bus architecture, typically represented by bus 702. Depending on the specific application and overall design constraints of processing system 714, bus 702 may include any number of interconnecting buses and bridges. Bus 702 communicatively couples together various circuits including one or more processors (typically represented by processor 704), memory 705, and computer-readable media (typically represented by computer-readable media 706). Bus 702 may also connect various other circuits such as timing sources, peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further. Bus interface 708 provides an interface between bus 702 and transceiver 710. Transceiver 710 provides a communication interface or unit for communicating with various other devices over a transmission medium. Depending on the nature of the device, a user interface 712 (e.g., keypad, display, speaker, microphone, joystick) may also be provided. Of course, this type of user interface 712 is optional, and some instances (such as base stations) may omit it.

[0105] In some embodiments of this application, processor 704 may include communication circuitry 740, configured (e.g., in coordination with memory 705) for various functions, including, for example, configuration and / or transmission on downlink traffic channels and / or downlink control channels. Additionally, communication circuitry 740 may be configured to, for example, transmit system information (including cell access information) in a System Information Block (SIB). For example, communication circuitry 740 may be configured to implement one or more of the functions described below with respect to Figures 6, 9, 10, and / or 11, including, for example, blocks 601, 606, 610, 614, 1102, 1104, 1108, and / or 1112 (when scheduling entity 700 is implementing a base station) and blocks 603, 608, 612, 902, 904, 908, 910, 1004, 1008, and 1010 (when scheduling entity 700 is implementing a UE). Processor 704 may also include RV mode determination circuitry 742, which can determine the RV mode for transmission to the UE and for decoding transmissions from the UE (e.g., based on RV information elements, RV configuration messages, and / or RV sequences or tables of RV sequences stored in memory 705 and / or computer-readable media 706). For example, RV mode determination circuitry 742 may be configured to implement one or more of the functions described below with respect to Figures 6, 9, 10, and / or 11, including, for example, blocks 904, 905, 906, 912, and / or 1008 (when scheduling entity 700 is implementing the UE) and blocks 1108 and / or 1110 (when scheduling entity 700 is implementing the base station). Additionally, processor 704 may also include first RV determination circuitry 744, which can determine the first or initial RV within the selected RV mode. For example, first RV determination circuitry 744 can determine which RV will be the first RV within the RV mode. For example, the first RV determination circuit 744 may be configured to implement one or more of the functions described below with respect to Figures 6, 9, 10 and / or 11, including, for example, at least a portion of one or more of blocks 904, 905, 906 and 1008 (when the scheduling entity 700 is implementing the UE) and including block 1108 (when the scheduling entity 700 is implementing the base station).

[0106] Processor 704 is responsible for managing bus 702 and general processing, including executing software stored on computer-readable media 706. When executed by processor 704, this software causes processing system 714 to perform the various functions described below for any particular device. Processor 704 may also use computer-readable media 706 and memory 705 to store data manipulated by processor 704 while executing software.

[0107] One or more processors 704 in the processing system can execute software. Whether referred to as software, firmware, intermediary software, microcode, hardware description language, or other terms, software should be broadly interpreted to mean instructions, instruction sets, code, code fragments, program code, program, subprogram, software module, application, software application, software suite, convention, subconvention, object, executable file, executable thread, program, function, etc. Software may reside on computer-readable media 706. Computer-readable media 706 may be non-transitory computer-readable media. For example, non-transitory computer-readable media includes magnetic storage devices (e.g., hard disks, floppy disks, magnetic tapes), optical discs (e.g., CDs or DVDs), smart cards, flash memory devices (e.g., cards, sticks, or key floppy disk drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electronically erasable PROM (EEPROM), temporary storage, removable disks, and any other suitable media for storing software and / or instructions that can be accessed and read by a computer. Computer-readable media 706 may be located in, outside of, or distributed among multiple entities including processing system 714. Computer-readable media 706 may be embodied in a computer program product. For example, a computer program product may include computer-readable media with encapsulation material. Those skilled in the art will recognize how the functions described herein can be optimally implemented based on the specific application and the overall design constraints imposed on the system as a whole.

[0108] In one or more of these media, computer-readable storage 706 may store computer-executable code including communication instructions 752, which configures scheduling entity 700 for various functions, including, for example, configuring and / or transmitting on downlink traffic channels and / or downlink control channels, and receiving on uplink traffic channels and / or uplink control channels. Additionally, communication instructions 752 may be configured to, for example, transmit system information (including cell access information) in a System Information Block (SIB). For example, communication instruction 752 can be configured to cause scheduling entity 700 to perform one or more of the functions described below with respect to Figures 6, 9, 10 and / or 11, including, for example, blocks 601, 606, 610, 614, 1102, 1104, 1108 and / or 1112 (when implementing a base station) and blocks 603, 608, 612, 902, 904, 908, 910, 1004, 1008 and 1010 (when implementing a UE). As further shown in Figure 7, computer-readable storage medium 706 may include RV mode determination instruction 754 for appropriately instructing RV mode determination circuit 742, and may include first RV determination instruction 756 for appropriately instructing first RV determination circuit 744. For example, the RV mode determination instruction 754 can be configured to cause the scheduling entity 700 to perform one or more of the functions described below with respect to Figures 6, 9, 10, and / or 11, including, for example, blocks 904, 905, 906, 912, and / or 1008 (when the scheduling entity 700 is implementing a UE) and including blocks 1108 and / or 1110 (when the scheduling entity 700 is implementing a base station). Additionally, the first RV determination instruction 756 can be configured to cause the scheduling entity 700 to perform one or more of the functions described below with respect to Figures 6, 9, 10, and / or 11, including, for example, at least a portion of one or more blocks 904, 905, 906, and 1008 (when the scheduling entity 700 is implementing a UE) and including block 1108 (when the scheduling entity 700 is implementing a base station).

[0109] In one configuration, the scheduling entity 700 includes: a unit for transmitting on a downlink traffic channel and / or a downlink control channel; a unit for receiving on an uplink traffic channel and / or an uplink control channel; a unit for determining an RV mode; and a unit for determining a first RV within the relevant RV mode. In one embodiment, the aforementioned unit may be a processor 704 as shown in FIG. 7, configured to perform the functions described therein. In another embodiment, the aforementioned unit may be a circuit or any device configured to perform the functions described therein.

[0110] Of course, in the above examples, the circuitry included in processor 704 is provided only as an example, and may include other units for performing the described functions in various forms of the present invention, including but not limited to instructions stored in computer-readable storage medium 706, or any other suitable means or units described in any of Figures 1, 2, 4, 6, 7 and / or 8 and utilizing, for example, the programs and / or algorithms described herein with respect to Figures 6, 9, 10 and / or 11.

[0111] Figure 8 is a conceptual diagram illustrating an example of a hardware implementation of an exemplary scheduled entity 800 employing a processing system 814. Depending on the specific details of this application, the processing system 814 may include elements having one or more processors 804, or any portion of those elements, or any combination of those elements. For example, the scheduled entity 800 may be a user equipment (UE) as shown in any one or more of Figures 1, 2, 4, and / or 6.

[0112] Processing system 814 may be substantially the same as processing system 714 shown in FIG. 7, including bus interface 808, bus 802, memory 805, processor 804, and computer-readable media 808. Furthermore, the scheduled entity 800 may include user interface 812 and transceiver 810, which are substantially similar to those user interfaces and transceivers described above in FIG. 7. That is, processor 804, as utilized in scheduled entity 800, may be configured (e.g., coordinated with memory 805) to implement any one or more of the programs described below and shown in FIG. 6, 9, and / or 10.

[0113] In some embodiments of this application, processor 804 may include communication circuitry 840, which is configured (e.g., coordinated with memory 805) for various functions, including, for example, transmitting (e.g., via transceiver 810) on an uplink traffic channel and / or an uplink control channel and / or receiving (e.g., via transceiver 810) on a downlink traffic channel and / or a downlink control channel. For example, communication circuitry 840 may be configured to implement one or more of the functions described below with respect to Figures 6, 9, and / or 10, including, for example, blocks 603, 608, 612, 902, 904, 908, 910, 1004, 1008, and 1010. Processor 804 may also include RV mode determination circuitry 842 for determining the RV mode intended for the scheduled entity (e.g., based on RV information elements and / or one or more RV information elements stored in memory), and may include first RV determination circuitry 844 for determining the desired RV to begin within the relevant RV mode (e.g., determined by a second index value). For example, RV mode determination circuitry 842 may be configured to implement one or more of the functions described below with respect to Figures 6, 9, and / or 10, including, for example, blocks 904, 905, 906, 912, and 1008. For example, first RV determination circuitry 844 may be configured to implement one or more of the functions described below with respect to Figures 6, 9, and / or 10, including, for example, at least a portion of one or more blocks 904, 905, 906, and 1008.

[0114] Furthermore, the computer-readable storage medium 806 may store computer-executable code including communication instructions 852, which will be configured by the scheduling entity 800 for various functions, including, for example, transmitting on the uplink traffic channel and / or uplink control channel; and / or receiving and demodulating the downlink traffic channel and / or downlink control channel (e.g., via transceiver 810). For example, the communication instructions 852 may be configured to cause the scheduling entity 800 to perform one or more of the functions described below with respect to Figures 6, 9, and / or 10, including, for example, blocks 603, 608, 612, 902, 904, 910, 1004, 1008, and 1010. As shown in Figure 8, the computer-readable storage medium 806 may include RV mode determination instructions 854 for appropriately instructing RV mode determination circuitry 842, and may include first RV determination instructions 856 for appropriately instructing first RV determination circuitry 844. For example, the RV mode determination instruction 854 can be configured to cause the scheduled entity 800 to perform one or more of the functions described below with respect to Figures 6, 9 and / or 10, including, for example, blocks 904, 905, 906, 912 and 1008. For example, the first RV determination instruction 856 can be configured to cause the scheduled entity 800 to perform one or more of the functions described below with respect to Figures 6, 9 and / or 10, including, for example, blocks 904, 905, 906 and 1008.

[0115] In some instances, memory 805 also includes one or more RV modes 860. Each of the RV modes 860 can be associated with an RV identifier, allowing processor 804 to selectively access RV modes from one or more RV modes 860 in memory 805.

[0116] In one configuration, the scheduled entity 800 includes: a unit for transmitting on an uplink traffic channel and / or an uplink control channel; a unit for receiving and demodulating a downlink traffic channel and / or a downlink control channel; a unit for determining an RV mode; and a unit for determining a first RV within the relevant RV mode. In one embodiment, the aforementioned unit may be a processor 804, as shown in FIG. 8, configured to perform the functions described therein. In another embodiment, the aforementioned unit may be a circuit or any device configured to perform the functions described therein.

[0117] Of course, in the above examples, the circuitry included in processor 804 is provided only as an example, and may include other units for performing the described functions in various forms of the present invention, including but not limited to instructions stored in computer-readable storage medium 806, or any other suitable means or units described in any of Figures 4, 6, 7 and / or 8 and utilizing, for example, the programs and / or algorithms described herein with respect to Figures 6, 9 and / or 10.

[0118] Figure 9 is a flowchart illustrating an exemplary program 900 for employing a repetitive RV pattern for decision-making and message transmission according to some forms of the present invention. As described below, specific implementations may omit some or all of the shown features, and all embodiments may be implemented without some of the shown features. In some instances, the scheduled entity 800 shown in Figure 8 may be configured to execute program 900. In some instances, any suitable means or unit for performing the functions or algorithms described below may execute program 900.

[0119] In some instances, the UE's RV mode determination procedure can employ a fixed, static, or predetermined RV mode, for example, stored in the UE's memory. Such a fixed mode can be agreed upon and specified in relevant specifications or standards. Using a fixed mode reduces communication between the base station and the UE, and the reduced processing can lead to a more efficient RV determination procedure. In other instances, the UE can select an RV mode from a plurality of available RV modes (e.g., a table stored in memory). In this instance, the base station or gNB can signal the appropriate RV mode selection information element to indicate to the UE which RV mode to select from the plurality of available RV modes 860 for the corresponding transmission. And in other instances, the UE can determine the RV mode in any suitable manner based on signal transmissions received from the base station or gNB. In a particular instance, the UE can receive an explicit indication of the RV mode signaled from the base station to indicate the RV mode available to the UE for the corresponding transmission. Furthermore, in a more advanced example, base station 604 can use a signal notification to repeatedly enable an instruction, indicating whether the UE should re-enable the corresponding transmission.

[0120] In another embodiment of this invention, the number of repetitions r used for a given transmission employing the repetitions described herein need not be the same as the number of RVs in the RV mode applied to that transmission. For example, the UE may periodically repeat the determined mode until it transmits a given number of repetitions r. Therefore, in another embodiment of this invention, the base station or gNB may signal a repetition quantity information element to indicate the number of repetitions r (e.g., MSG3 repetition) to be transmitted by the UE in the corresponding transmission.

[0121] In various instances, at block 902, the base station or gNB may provide the UE with one or more such RV configuration parameters in the RV configuration message. That is, the base station or gNB may send the RV configuration message to the UE, which includes, for example, any one or any suitable combination of the following: RV mode selection information element, explicit indication of RV mode, repeated activation indication and / or repeated quantity information element.

[0122] For example, a base station can include such RV configuration messages within its DCI. For instance, as mentioned above, a DCI transmitted by the base station in conjunction with an MSG3 retransmission request 610 can utilize a DCI with format 0_0, and can utilize one or more bits in DCI format 0_0 (e.g., reserved bits in existing specifications) to indicate RV configuration messages. Specifically, a DCI with format 0_0 can include reserved fields, such as a 1-bit new data indicator and a 4-bit HARQ procedure number indicator. Therefore, one or more of these otherwise reserved bits can be repurposed for use by the base station or gNB to signal to the UE an RV configuration message including one or more RV configuration parameters, as described above.

[0123] In another example, as mentioned above, corresponding to the RACH procedure of dialing stream 600, where transmission duplication as disclosed herein is enabled for the initial MSG3 transmission 608, the DCI transmitted by the base station in conjunction with the RAR message 606 can utilize DCI format 1_0, and can utilize one or more bits in DCI format 1_0 (e.g., reserved bits in existing specifications) to indicate the RV configuration message. Specifically, according to existing specifications for 3GPP 5G NR, in different configurations, a DCI with format 1_0 can include a set of 14 or 16 reserved bits. Therefore, the base station or gNB can use one or more of these otherwise reserved bits as retargeted bits to provide the RV configuration message to the UE.

[0124] Therefore, the base station or gNB can include such RV configuration information in the DCI carried in conjunction with the Random Access Response message 606 in the PDCCH. Thus, the UE can determine the RV re-configuration for the initial MSG3 transmission 608 based on the received RV configuration information. And in some instances, if the determined RV re-configuration is not overridden by the MSG3 retransmission request, the UE can determine the RV re-configuration for the MSG3 retransmission 612 based on the RV configuration information received in the DCI carried in conjunction with the Random Access Response message 606 in the PDCCH.

[0125] Similarly, the base station or gNB can include such RV configuration information in the DCI carried in conjunction with the MSG3 retransmission request 610 in the PDCCH. Therefore, the UE can determine the RV reconfiguration for MSG3 retransmission 612 based on the received RV configuration information.

[0126] In another embodiment of this application, at block 904, the base station or gNB can signal to the UE an RV information element to indicate the first RV for the UE to apply to a first message transmission (e.g., the first or initial repetition among multiple repetitions). For example, as described above with respect to FIG6, base station 604 can signal to the UE an MSG3 retransmission request 610 by sending a PDCCH with a DCI having a CRC scrambled via TC-RNTI, where the DCI is format 0_0. Again, such DCI format 0_0 includes a two-bit RV information element in the existing 3GPP specification for 5G NR (e.g., a two-bit redundancy version field in DCI format 0_0). According to one embodiment of this application, the UE can use such an RV information element as an indication of the RV for the first repetition (e.g., MSG3 retransmission 612) among multiple repetitions to be applied to a given transmission.

[0127] Furthermore, in some instances, base station 604 can signal to RAR / MSG2 606 by sending a PDCCH with a DCI scrambled via RA-RNTI, where the DCI is format 1_0. According to another embodiment of the present invention, one or more otherwise reserved bits in the existing 3GPP specifications for 5G NR can be repurposed to indicate RV information elements. According to one embodiment of the present invention, the UE can use such RV information elements as an indication of the RV for the first repetition of a plurality of repetitions to be applied to a given transmission (e.g., the initial MSG3 transmission 608, and if not covered, the MSG3 retransmission 612).

[0128] Therefore, at block 905, the UE can determine the RV mode. Here, the UE can determine the RV mode based on any one or any suitable combination of the following: a fixed, static, or predetermined mode stored in the UE's memory; an RV mode selection information element combined with a plurality of available RV modes; an RV mode explicitly notified by a signal; a repeat activation indication; and / or a repeat quantity information element, as described above.

[0129] At block 906, the UE decides whether to use the RV information element. In some instances, such as shown at block 908, the UE may use the first RV of the RV mode as the initial RV and send the first repetition of r repetitions, where the determined first RV is applied to generate the first repetition of the transmission (e.g., MSG3 transmission and / or retransmission). For example, even in instances where the base station or gNB signals the UE to notify the UE of the RV information element (e.g., in Random Access Response Message 606 and / or MSG3 Retransmission Request 610), the UE may, in some examples, ignore such RV indications and directly apply the determined RV mode without considering such RV indications.

[0130] In other instances, at block 910, the UE may use the RV information element as an indication of the RV for the first repetition of a plurality of repetitions to be applied to a given transmission. That is, the UE may use repetitions as described in this application to send a corresponding transmission, wherein the RV corresponding to the received RV information element (also referred to as the initial or starting RV) is applied to the first or initial repetition of the message being transmitted or retransmitted.

[0131] Furthermore, at block 912, the UE can determine the subsequent RV to be applied to subsequent repetitions after the first repetition based on the RV pattern and the RV information element. For example, a given RV pattern can indicate an RV sequence or set. In some instances, the RV pattern can include instances of each potential RV that the UE can apply to a given transmission within its set. For example, if a given RV pattern has a length of x=4, then the RV pattern can correspond to {0,2,3,1}. Here, each potential RV from 0 to 3 that the UE can apply to a given transmission is included in the RV pattern. Therefore, in another aspect of the present invention, the UE can identify the index k of the RV corresponding to the received RV information element within the determined RV pattern. For example, the RV pattern can be indexed according to the index pattern {0,1,…x–1} based on the index k. For example, in the exemplary RV pattern {0,2,3,1} provided above, RV 0 corresponds to index k=0; RV 2 corresponds to index k=1; RV 3 corresponds to index k=2; and RV 1 corresponds to index k=3. Furthermore, individual RVs within an RV pattern can be indicated by RV{k} (e.g., the first RV in an RV pattern can be indicated by RV{0}, the second RV in an RV pattern can be indicated by RV{1}, and so on, up to R{x-1}).

[0132] Therefore, in this example, if the UE determines the RV mode to be {0,2,3,1} and receives a 2-bit RV information element (e.g., 2) indicating [0b10], the UE can identify the initial RV index corresponding to the received RV information element 2 at index k=1 within the determined RV mode.

[0133] Therefore, the first or initial repetition sent by the UE can occur in block 908 (applying, for example, RV 0 with index k=0) or block 910 (applying, for example, RV 2 with index k=1, depending on the received RV information element). To continue, at block 912, the UE can apply subsequent RVs to generate subsequent repetitions based on the cyclical application of the RV pattern (starting from the initial RV). For example, in block 912, the UE can cyclically pass through sub-blocks 912a, 912b, and 912c, applying the next RV in the RV pattern to MSG3 to generate the next repetition each time it passes through a sub-block, and then send the next repetition, until each of the r repetitions has been sent (e.g., n=r). The cyclical application of the RV pattern is such that the index k is incremented (e.g., k=k+1) each time it passes through sub-blocks 912a-c, until the end of the RV pattern is reached (i.e., when index k=x-1), at which point the next RV is the first RV in the RV pattern (i.e., index k=0). For example, in the exemplary RV pattern {0,2,3,1} provided above, when the initial RV is the first RV in the RV pattern (index k=0) and the number of repetitions r=6, the six repetitions can be applied in the following order: RV 0 - Block 908 or 910, where k=0, first transmission (n=1) RV 2 - Block 912, k=1, Second Transmission (n=2) RV 3 - Block 912, k=2, Third Transmission (n=3) RV 1 - Block 912, k=3, Fourth Transmission (n=4) RV 0 - Block 912, k=0, Fifth Transmission (n=5) RV 2 - Block 912, k=1, Sixth Transmission (n=6)

[0134] Therefore, the index k increments with each transmission until it reaches the last index of the RV mode (k=x-1), and then k can be reset to 0 for subsequent transmissions. In the above example, the initial RV is the first RV in the RV mode (index k=0). In some embodiments, for the initial MSG3 transmission (see MSG3 608 in FIG. 6), the RV for the first repetition is the first RV in the RV mode (index k=0), and the RV for repetition cycles through the RV mode, starting from the first RV in the RV mode until the last RV, and then looping back to the first RV (as stated in the above example). In some instances, the first RV in the RV mode (index k=0) is fixed (e.g., not indicated by the RV information element provided by the base station), such as those described with respect to blocks 906 and 908. In other instances, the first RV in the RV mode (index k=0) is indicated by the RV information element provided by the base station (see, for example, blocks 904, 906, and 910).

[0135] However, the initial RV can be any RV in the RV pattern other than the RV with index k=0. The index k of the initial RV can be indicated by the RV information element. For example, the UE can determine in block 910 that the initial RV is the RV with index k=2. Therefore, in this example, and with the number of repetitions r=6 and the exemplary RV pattern {0,2,3,1} provided above, the six repetitions sent can apply RVs in the following order: RV 3, RV 1, RV 0, RV 2, RV 3, RV 1. In some instances, for MSG3 retransmission (see MSG3 retransmission 612 in Figure 6), the RV used for the first repetition is the RV specified by the RV information element in block 904, and the UE sends the first repetition with that specified RV out of the r repetitions in block 910.

[0136] The UE can continue via the procedure shown in block 912 until the number of repetitions n sent is equal to the number of repetitions r to be sent.

[0137] Figure 10 is a flowchart illustrating an exemplary procedure 1000 for employing repeated RV pattern decision-making and message transmission according to some forms of the present invention. As described below, specific implementations may omit some or all of the shown features, and all embodiments may be implemented without some of the shown features. In some instances, the scheduled entity 800 shown in Figure 8 may be configured to execute procedure 1000. However, procedure 1000 may also be implemented by other wireless communication devices. For simplicity, the flowchart of Figure 10 is described below with respect to the wireless communication device of Figure 6 (i.e., UE 602 (which may take the form of the scheduled entity 800 of Figure 8) and base station 604 (which may take the form of scheduling entity 700)). In some instances, any suitable means or unit for performing the functions or algorithms described below may execute procedure 1000.

[0138] At block 1004, as part of a random access procedure, UE 602 receives a Random Access Response (RAR) message from base station 604. For example, referring to FIG6, UE 602 receives RAR / MSG2 606 from base station 604. The base station may send RAR / MSG2 606 in response to UE 602 initiating a random access procedure. For example, base station 604 may send RAR / MSG2 606 in response to receiving and decoding random access request 603 (also referred to as RACH preamble signal or message 1 (MSG1)). Referring to FIG6, UE 602 may send MSG1 to base station 604 on the physical random access channel (PRACH). MSG1 603 indicates UE 602's request to initiate a connection with base station 604. As also mentioned in Figure 6, RAR / MSG2 606 may include a PDCCH, which includes a DCI with a CRC scrambled via RA-RNTI; a DC for scheduling the corresponding PDSCH; and the corresponding PDSCH. Referring to the scheduled entity 800 in Figure 8 as an example of UE 602, in order to receive RAR messages, processor 804 may receive RAR / MSG2 606 via transceiver 810.

[0139] At block 1008, as part of a random access procedure, UE 602 sends uplink (UL) communication to base station 604. The UL communication comprises multiple repetitions of the UL message, each repetition being configured via a corresponding RV applying an RV mode with multiple redundancy versions (RVs) to the UL message. In some instances, the UL communication corresponds to the initial MSG3 transmission 608 of FIG. 6. For example, the UL communication sent by UE 602 in block 1008 includes the initial MSG3 (e.g., the entire message) and repetitions of the MSG3. In other instances, the UL communication corresponds to the MSG3 retransmission 612 of FIG. 6 sent in response to a retransmission request received from base station 604 (see MSG3 retransmission request 610). In these instances, the UL communication sent by UE 602 in block 1008 is a UL communication retransmission, which may include both a retransmitted MSG3 (e.g., the entire MSG3) and a duplicate of MSG3, or may include a duplicate of MSG3 but not the entire MSG3.

[0140] As part of block 1008, UE 602 can determine the RV mode. In some instances, the RV mode is a fixed RV mode (also known as a static or predetermined RV mode), and UE 602 determines the RV mode by accessing memory storing the fixed RV mode. For example, referring to the scheduled entity 800 in FIG8 as an example of UE 602, in order to determine the RV mode, processor 804 can access the fixed RV mode stored in memory 805. Using a fixed RV mode can reduce communication and improve the efficiency of determining the RV mode. In some instances, UE 602 determines the RV mode based on information transmitted by base station 604 and received by UE 602. Referring to the scheduled entity 800 in FIG8 as an example of UE 602, in order to determine the RV mode based on information transmitted by base station 604, processor 804 can receive such information transmitted by base station 604 via transceiver 810 and process such information to determine the RV mode. For example, base station 604 may transmit RV mode selection information elements (e.g., RV mode identifier) ​​to UE 602 to indicate which RV mode (e.g., stored in memory 805) should be selected and applied by UE 602. In another instance, UE 602 may receive an explicit indication of the RV mode from base station 604, which defines the RV mode for UE 602 to use for a corresponding transmission. For example, the explicit indication may include each RV of the RV mode. By determining the RV mode based on information transmitted by base station 604, UE 602 and base station 604 can adapt and select RV modes specific to different scenarios (e.g., different data error rates, different numbers of UEs attempting to schedule via random access procedures, etc.).

[0141] In some instances where UE 602 determines the RV mode based on information transmitted by base station 604, base station 604 may include such information within the RV configuration message in the DCI, as previously described. For example, and referring to Figure 6 above and its corresponding description, base station 604 may use one or more bits in a DCI with DCI format 0_0 combined with MSG3 retransmission request 610, or one or more bits in a DCI with DCI format 1_0 combined with RAR message 606, to send the RV configuration message. Thus, in at least some instances, previously unused bits in the DCI can be used to provide the RV configuration message without adding a new message to the random access procedure.

[0142] In some instances, determining the RV pattern includes: determining which RV within the RVs constituting the RV pattern is the starting RV (i.e., the first RV in the sequence to be applied to the message to generate the first repetition). The starting RV can be the first RV in the RV pattern, or it can be another RV within the RV pattern. For example, returning to the exemplary RV pattern {0,2,3,1}, the starting RV can be the first RV in the RV pattern (i.e., RV{0}), which can be described as the RV in the RV pattern with index k=0, in this instance, the RV is RV 0. Alternatively, the starting RV can be another RV in the RV pattern with a different index (e.g., index k=1, 2, or 3). In some instances, the starting RV is fixed and determined by the UE 602 via access memory (e.g., memory 805 can store the starting RV and one or more RV patterns 860). Alternatively, in some instances, the UE 602 determines the starting RV based on information transmitted by the base station 604. For example, the information transmitted by base station 604 may include the value of the index k of the starting RV (e.g., as part of the DCI), which may also be referred to as the RV information element (see, for example, the RV information element described with respect to blocks 904, 906, and 910 of FIG. 9). Having a fixed starting RV can reduce communication and improve the efficiency of RV mode determination, while allowing base station 604 to specify the starting RV allows UE 602 and base station 604 to adapt the RV mode to different scenarios (e.g., different data error rates, the number of UEs attempting to schedule via random access procedures, etc.). For example, in a particular scenario, a specific RV within the RV mode may be more likely to result in successful MSG3 transmission. Therefore, in some instances, starting from that specific RV may be beneficial.

[0143] In some instances, determining the RV mode includes determining the number of repetitions r to be generated and transmitted by UE 602. The number of repetitions can be the number of RVs within the RV mode (e.g., r=4 in instance RV mode {0,2,3,1}) or another number greater than or less than the number of RVs within the RV mode (e.g., r=1, 2, 3, 5, 6, 7, etc.). In some instances, the number of repetitions r is fixed and determined by UE 602 via access memory (e.g., memory 805 can store the number of repetitions r and one or more RV modes 860). Alternatively, in some instances, UE 602 determines the number of repetitions r based on information transmitted by base station 604. For example, the information transmitted by base station 604 may include the number of repetitions r (e.g., as part of DCI). Having a fixed number of repetitions r can reduce communication and improve the efficiency of RV mode determination. It also allows base station 604 to specify the number of repetitions r, enabling UE 602 and base station 604 to adapt the RV mode to different scenarios (e.g., different data error rates, the number of UEs attempting scheduling via random access procedures, etc.). Furthermore, the value of r is not limited by the number of RVs in the RV mode, because UE 602 can cyclically repeat the determined RV mode until it sends a given number of repetitions r. For example, when UE 602 determines an RV mode {0,2,3,1} with a starting RV at index k=0 (i.e., RV{0}) and a repetition number r=6, UE 602 applies the following RV sequence to generate repetitions: RV 0, RV 2, RV 3, RV 1, RV 0, RV 2. By cyclically repeating the RV mode, UE 602 can generate more RVs than within the RV mode, potentially increasing the likelihood that base station 604 can decode the transmission.

[0144] Furthermore, as mentioned, in block 1008, each of the UL communications is configured by applying the corresponding RV of the RV pattern to the UL message. For example, referring to FIG3, the UL message (MSG3) may be "decoded bits 308", and the UE 602 may generate multiple repetitions of the UL message by applying the corresponding RV of a plurality of RVs (which may be collectively represented by redundant versions (RV) 310 in FIG3) to the UL message via multiple RVs based on the RV pattern. For example, returning to the exemplary RV pattern {0,2,3,1}, and assuming the starting RV is at index k=0 and the number of repetitions r=6, the UE 602 may generate and send repetitions including: RV 0 of the UL message, RV 2 of the UL message, RV 3 of the UL message, RV 1 of the UL message, RV 0 of the UL message, and RV 2 of the UL message. As discussed with respect to block 912 of Figure 9, the RV pattern can be applied cyclically, such that the index k increments with each repeated transmission (e.g., k = k + 1) until the end of the RV pattern is reached (i.e., when index k = x - 1), at which point the next RV is the first RV in the RV pattern (i.e., index k = 0). Similar to the RVs and decoded bits 308 described with respect to Figure 3, the specific operation that generates repetition on the UL message is indicated by the corresponding RV and may include, for example, shift operations on the UL message, selection of a specific portion of the UL message, selection of the entire UL message, or other operations.

[0145] In some instances, UE 602 transmits UL communication on the entity uplink shared channel (PUSCH). For example, UE 602 may transmit corresponding repetitions of UL communication in multiple corresponding time slots on the PUSCH. Referring to the scheduled entity 800 in FIG8 as an example of UE 602, in order to transmit UL communication to the base station in block 1008 of procedure 1000, processor 804 may transmit UL communication via transceiver 810.

[0146] At block 1010, UE 602 receives downlink messages from base station 604 based on UL messages. The downlink messages are, for example, MSG4 614 in Figure 6. The downlink messages may include scheduling information for use by UE 602 in further uplink communications with base station 604. For example, the downlink messages may include a temporary identity (temporary_C-RNTI) of UE 602, which may have been sent in whole or in part to base station 604 in previous communications from UE 602 (e.g., in UL messages / MSG3). In some instances, UE 602 is configured to recognize the temporary identity within the downlink messages and elevate the temporary identity (temporary_C-RNTI) to an identity (C-RNTI), which is subsequently used by UE 602 for further uplink communications with base station 604.

[0147] As mentioned above regarding block 1008, in some instances of procedure 1000, the UL communication of block 1008 is initial UL communication, which includes a UL message (e.g., the entire MSG3) and multiple repetitions of the UL message. Referring to FIG6, this UL communication can be sent in response to a Random Access Response message (RAR / MSG2). In these instances, the RV mode applied to generate the repetitions of the UL communication can be referred to as the initial RV mode. Additionally, in these instances, UE 602 can also receive a retransmission request for retransmitting the UL communication from base station 604 (e.g., MSG3 retransmission request 610 in FIG6). In response, UE 602 can also determine a retransmission RV mode that includes a retransmission sequence of redundant versions (RVs). UE 602 can also send a UL communication retransmission in response to the retransmission request. UL communication retransmission can include multiple repetitions of the UL message retransmission, each of which is configured via a corresponding RV applying an RV mode with multiple RVs to the UL message retransmission. UL message retransmissions can be UL messages (e.g., the entire MSG3), subsets of UL messages, modified or encoded versions of UL messages, or messages otherwise linked to UL messages (e.g., linked as part of the same random access procedure).

[0148] In some instances, UE 602 reuses the RV mode mentioned in block 1008 as the retransmission RV mode. In other words, UE 602 determines the retransmission RV mode as the initial RV mode. In other instances, UE 602 uses one of the techniques described above with respect to block 1008 to determine the retransmission RV mode. For example, the retransmission RV mode may be fixed, and UE 602 determines the retransmission RV mode (e.g., from one or more RV modes 860 in memory 805) by accessing the fixed RV mode from memory. In other instances, UE 602 determines the retransmission RV mode based on information transmitted by base station 604 and received by UE 602. For example, base station 604 may transmit an RV mode selection information element (e.g., an RV mode identifier) ​​to UE 602 to indicate which of the plurality of RV modes (e.g., stored in memory 805) should UE 602 select and apply as the retransmission RV mode. In another instance, UE 602 may receive an explicit indication of the RV mode from base station 604, which defines the retransmission RV mode for UE 602 to use for corresponding retransmissions. In some instances, similar to the RV modes discussed in block 1008, the retransmission RV mode is associated with the initial RV and / or the number of repetitions r (which operates similarly to those described above), but applies to the retransmission RV mode. One or both of the initial RV and / or the number of repetitions r may be fixed values ​​stored in memory (e.g., memory 805) and accessed by UE 602, or they may be determined by UE 602 based on information transmitted from base station 604.

[0149] In some instances where UE 602 determines the retransmission RV mode, the starting RV for the retransmission RV mode, and / or the number of repetitions r based on information transmitted by base station 604, base station 604 may include such information within the RV configuration message in the DCI, as previously described. For example, and referring to FIG6, as previously mentioned, base station 604 may use one or more bits in a DCI with DCI format 0_0 in conjunction with MSG3 retransmission request 610 to transmit the RV configuration message. In some instances, the starting RV for the retransmission RV mode may be indicated in one or more bits (e.g., a two-bit RV information element) in a DCI with DCI format 0_0, the DCI having a CRC scrambled via TC-RNTI, as previously mentioned.

[0150] As mentioned, in some instances, UE 602 receives RV configuration messages from base station 604 and determines the retransmission RV mode based on the RV configuration messages. In some of these instances, the initial RV mode mentioned in block 1008 (i.e., for initial UL communication) is a fixed RV mode known to both UE 602 and base station 604. Therefore, initial UL communication (see MSG3 608 in Figure 6) can be associated with RV techniques that include sending repeated RVs according to the fixed RV mode, while the RV technique for UL communication retransmission (see MSG3 retransmission 612 in Figure 6) is adaptable based on the RV configuration messages to allow UE 602 and base station 604 to select and / or adjust the retransmission RV mode according to a specific scenario.

[0151] In some instances, the initial RV mode used for initial UL communication (e.g., MSG3 608 in Figure 6) can be a fixed RV mode, and multiple repetitions of the UL message are configured by sequentially applying multiple RVs to the UL message according to the RV mode, starting with the first RV in the sequence of multiple RVs of the RV mode (i.e., the RV with index 0), and continuing sequentially and cyclically according to the RV mode, looping back from the end of the sequence to the beginning of the sequence, until each of the multiple repetitions of the UL message is configured. Furthermore, in some instances, a RV configuration message for UL communication retransmission from the base station can be indicated in the redundant version field of the DCI format 0_0 or in one or more retargeted bits from a reserved bit set, the DCI format 0_0 having a cyclic redundancy check (CRC) scrambled via a temporary cellular radio network temporary identifier (TC-RNTI), the RV configuration message indicating the starting RV of the retransmission RV mode. For example, a two-bit RV information element indicated in the DCI can provide the index value of the starting RV within the retransmission RV mode. Subsequently, the multiple repetitions of UL message retransmission are configured by sequentially applying the retransmission sequence of the RV to the UL message retransmission according to the retransmission RV mode, starting from the initial RV of the retransmission RV mode, and continuing sequentially and cyclically according to the retransmission RV mode, looping back from the end of the retransmission sequence to the beginning of the retransmission sequence, until each of the multiple repetitions of the UL message retransmission is configured.

[0152] In other instances, the initial RV mode used for initial UL communication (e.g., MSG3 608 in Figure 6) is a first fixed RV mode, and the retransmission RV mode used for UL communication retransmission (e.g., MSG3 retransmission 612 in Figure 6) is a second fixed RV mode. Here, the first and second fixed RV modes can be the same RV mode applied by starting with the same initial RV, can be the same RV mode but applied by starting with a different initial RV, or can be different RV modes.

[0153] In some instances of procedure 1000, UE 602 also receives a repeat enable instruction from base station 604. The repeat enable instruction may be an indication (e.g., a binary indication) regarding whether UE 602 will include repeats of UL messages in UL communications. Therefore, base station 604 is configured to disable repeats for UE 602, for example, in situations with low network traffic or where communication is sufficiently reliable without repeats. The repeat enable instruction may be provided by base station 604 and received by UE 602 as part of an RV configuration message. As previously mentioned, and referring to FIG6, the RV configuration message may be, for example, part of a SIB 601, RAR / MSG2 606, or MSG3 retransmission request 610.

[0154] Figure 11 is a flowchart illustrating an exemplary procedure 1100 for employing repeated RV pattern decision-making and message transmission according to some forms of the present invention. As described below, specific implementations may omit some or all of the shown features, and all embodiments may be implemented without some of the shown features. In some instances, the scheduled entity 700 shown in Figure 7 may be configured to execute procedure 1100. However, procedure 1100 may also be implemented by other wireless communication devices. For simplicity, the flowchart of Figure 11 is described below with respect to the wireless communication device of Figure 6 (i.e., UE 602 (which may take the form of the scheduled entity 800 of Figure 8) and base station 604 (which may take the form of the scheduling entity 700)). In some instances, any suitable means or unit for performing the functions or algorithms described below may execute procedure 1100.

[0155] At block 1102, base station 604 receives a random access request from UE 602 to initiate a random access procedure. For example, referring to FIG6, UE 602 sends random access request 603 (also referred to as RACH preamble or message 1 (MSG1)) to base station 604 on the physical random access channel (PRACH). MSG1 603 instructs UE 602 to initiate a connection request with base station 604. Therefore, this transmission of MSG1 603 initiates a random access procedure with base station 604. Referring to scheduling entity 700 in FIG7 as an example of base station 604, processor 704 can receive random access request 603 via transceiver 710.

[0156] At block 1104, base station 604 responds to a random access request by sending a Random Access Response (RAR) message to UE 602. For example, referring to FIG6, UE 602 receives RAR / MSG2 606 from base station 604. Base station 604 responds by receiving and decoding MSG1 603 to send RAR / MSG2 606. As mentioned with respect to FIG6, RAR / MSG2 606 may include a PDCCH, which includes a DCI with a CRC scrambled via RA-RNTI; a DCI for scheduling the corresponding PDSCH; and the corresponding PDSCH. Referring to the scheduling entity 700 in FIG7 as an example of base station 604, in order to send the RAR message, processor 704 may send RAR / MSG2 606 via transceiver 710.

[0157] In block 1108, as part of a random access procedure, base station 604 receives uplink (UL) communication from the UE. UL communication comprises multiple repetitions of a UL message, each repetition being configured via a corresponding RV applying an RV mode with multiple redundancy versions (RVs) to the UL message. In some instances, UL communication corresponds to the initial MSG3 transmission 608 of FIG. 6. For example, the UL communication received by base station 604 in block 1108 includes the initial MSG3 (e.g., the entire MSG3) and repetitions of the MSG3. In other instances, UL communication corresponds to the MSG3 retransmission 612 of FIG. 6 sent in response to a retransmission request received from base station 604 (see MSG3 retransmission request 610). In these instances, the UL communication received by base station 604 in block 1108 is a UL communication retransmission, which may include both the retransmitted MSG3 (e.g., the entire MSG3) and repetitions of the MSG3, or may include repetitions of the MSG3 but not the complete MSG3.

[0158] As part of block 1108, base station 604 can determine the RV mode. In some instances, the RV mode is a fixed RV mode (also referred to as a static or predetermined RV mode), and base station 604 determines the RV mode by accessing memory storing the fixed RV mode. For example, referring to scheduling entity 700 in FIG7 as an example of base station 604, processor 704 can access the fixed RV mode stored in memory 705 to determine the RV mode. Using a fixed RV mode can reduce communication and improve the efficiency of determining the RV mode. In some instances, base station 604 sends communication indicating the RV mode to UE 602 (e.g., via transceiver 710), as described with respect to block 1008 of FIG10.

[0159] In some instances, determining the RV pattern includes determining which RV within the RVs constituting the RV pattern is the starting RV (i.e., the first RV in the sequence to be applied to the message to generate the first repetition). The starting RV can be the first RV in the RV pattern, or it can be another RV within the RV pattern. For example, returning to the exemplary RV pattern {0,2,3,1}, the starting RV can be the first RV in the RV pattern (i.e., RV{0}), which can be described as the RV in the RV pattern with index k=0, in this instance, the RV is RV 0. Alternatively, the starting RV can be another RV in the RV pattern with a different index (e.g., index k=1, 2, or 3). In some instances, the starting RV is fixed and determined by base station 604 via access memory (e.g., memory 705 can store the starting RV and one or more RV patterns). Alternatively, in some instances, base station 604 determines the starting RV based on detected scenarios or conditions (e.g., different data error rates, the number of UEs attempting to schedule via random access procedures, etc.). For example, in certain scenarios, a specific RV within the RV mode may be more likely to result in a successful MSG3 transfer. Therefore, in some instances, it may be beneficial to start with that specific RV.

[0160] In some instances, determining the RV mode includes determining the number of repetitions r to be generated and transmitted by UE 602. The number of repetitions can be the number of RVs within the RV mode (e.g., r=4 in instance RV mode {0,2,3,1}) or another number greater or less than the number of RVs within the RV mode (e.g., r=1, 2, 3, 5, 6, 7, etc.). In some instances, the number of repetitions r is fixed and determined by base station 604 via access memory (e.g., memory 705 can store the number of repetitions r and one or more RV modes). Alternatively, in some instances, base station 604 determines the number of repetitions r based on detected scenarios or conditions (e.g., different data error rates, the number of UEs attempting to schedule via random access procedures, etc.). For example, in a particular scenario, a specific number of repetitions r may be more likely to result in successful MSG3 transmission. Therefore, in some instances, starting with that specific value of r may be advantageous.

[0161] Furthermore, as mentioned, in block 1108, each of the UL communications is repeatedly configured via the corresponding RV applying the RV mode to the UL message. In some instances, the UE may generate repetitions, as described with respect to block 1008 of Figure 10.

[0162] At block 1110, base station 604 decodes UL communication based on RV mode. For example, based on the determined RV mode, base station 604 can resolve UL communication into one or more of MSG3 and MSG3 repetitions (e.g., by knowing one or more repetitions of MSG3 and / or the length and format of each item in MSG3 from the RV mode). Furthermore, to decode individual portions of the UL communication (e.g., MSG3 and / or repetitions), base station 604 can perform the opposite operation to that performed by UE 602 using the RV mode to generate portions. Additionally, base station 604 can combine selected portions of the UL communication (e.g., portions of MSG3 and / or repetitions) to generate MSG3 from the portions of the UL communication. Base station 604 can identify and select specific portions to be used in the combination based on its evaluation of the portions of the UL communication and the likelihood that the decoded data in each corresponding portion is valid or accurate. As an example for illustrative purposes only, if we assume that the UL communication includes the same data bytes in three different parts (e.g., the original MSG and two different repetitions), and that the data bytes are identical in two of the three parts, then base station 604 can determine that the data bytes should be received in the two (equivalent) parts and ignore the data bytes in the third (different) part (assuming that the data bytes contain errors).

[0163] At block 1112, base station 604 sends downlink messages to UE 602 based on UL messages. For example, base station 604 may decide to send a downlink message after correctly decoding MSG3 from the UL communication received in block 1108. For example, the downlink message is MSG4 614 of FIG. 6. The downlink message may include scheduling information for UE 602 to use in additional uplink communications with base station 604. For example, the downlink message may include a temporary identity (temporary_C-RNTI) of UE 602, which may have been sent in whole or in part to base station 604 in earlier communications from UE 602 (e.g., in UL message / MSG3). In some instances, UE 602 is configured to recognize the temporary identity within the downlink message and promote the temporary identity (temporary_C-RNTI) to an identity (C-RNTI), which is subsequently used by UE 602 for further uplink communications with base station 604.

[0164] As mentioned above regarding block 1108, in some instances of procedure 1100, the UL communication in block 1108 is the initial UL communication, which includes the UL message (e.g., the entire MSG3) and multiple repetitions of the UL message. Referring to FIG6, this UL communication can be sent in response to a Random Access Response message (RAR / MSG2). In these instances, the RV mode mentioned in block 1108 can be referred to as the initial RV mode. Additionally, in these instances, base station 604 can also send a retransmission request to UE 602 for retransmitting the UL communication (e.g., MSG3 retransmission request 610 in FIG6). In response, base station 604 can also determine a retransmission RV mode that includes a retransmission sequence of redundant versions (RVs). Base station 604 can also respond to the retransmission request to receive UL communication retransmissions from UE 602. UE communication retransmission may include a plurality of repetitions of UE message retransmission, each of which is an iteration of UL message retransmission configured by applying a sequence of RV-based retransmission sequences to the corresponding RV of the UL message retransmission. UL message retransmission may be a UL message (e.g., the entire MSG3), a subset of a UL message, a modified or encoded version of a UL message, or a message otherwise linked to a UL message (e.g., linked as part of the same random access procedure).

[0165] In some instances, base station 604 will reuse the RV mode mentioned in block 1108 as the retransmission RV mode. In other instances, base station 604 will use one of the techniques described above regarding block 1108 to determine the retransmission RV mode.

[0166] As described herein, a UE (e.g., UE 602) or a base station (e.g., base station 604) may use RV modes to generate or decode UL communications, as described with respect to block 1008 of FIG10 and blocks 1108-1110 of FIG11. In some of these instances, the RV mode may be defined according to the redundant version of Table 6.1.2.1-2 for PUSHC transmissions from 3GPP Technical Specification (TS) 38.214 (V16.6.0). For example, in some instances, the repeating RV mode applied to the initial MSG3 transmission is a fixed mode following the first row of the table (e.g., starting from RV[0]), or a mode following one of the four rows of the table, wherein the base station indicates a specific row and / or the starting RV to the UE. Furthermore, in some instances, the repeating RV mode applied to MSG3 retransmissions is a fixed mode following the first row of the table (e.g., starting from RV[0]), or a mode following one of the four rows of the table, wherein the base station indicates a specific row to the UE. In each case, the RV pattern can be applied cyclically, as described above and as indicated by the modular operation elements in the table. Table 6.1.2.1-2: Redundant Versions for PUSCH Transmission rvid indicated by DCI of scheduling PUSCH The rvid to be applied to the nth transmission timing (repetition type A) or the nth actual repetition (repetition type B) n modulo 4 = 0 n modulo 4 = 1 n modulo 4 = 2 n modulo 4 = 3 0 0 2 3 1 2 2 3 1 0 3 3 1 0 2 1 1 0 2 3 Other examples with multiple characteristics:

[0167] Example 1: A method, apparatus, and non-transitory computer-readable medium for wireless communication operable at a user equipment (UE). As part of a random access procedure, the UE receives a Random Access Response (RAR) message from a base station. As part of the random access procedure, the UE also sends uplink (UL) communication to the base station. The UL communication includes a plurality of repetitions of a UL message, each repetition being configured via a corresponding RV applying an RV mode with multiple RVs to the UL message. The UE also receives downlink messages from the base station based on the UL messages.

[0168] Example 2: According to the method, apparatus and nontransitory computer-readable medium of Example 1, wherein the UL communication includes the UL message and the plurality of repetitions of the UL message, and wherein the transmission of the UL communication is in response to the Random Access Response (RAR) message.

[0169] Example 3: The method, apparatus and nontransitory computer-readable medium according to any one of Examples 1 to 2 also include: the UE receiving a retransmission request from the base station for retransmitting the UL communication; and responding to the retransmission request to send a UL communication retransmission, the UL communication retransmission including a plurality of repetitions of UL message retransmission, each of the plurality of repetitions being configured via a corresponding RV of a retransmission RV mode having a plurality of RVs applied to the UL message retransmission.

[0170] Example 4: The method, apparatus and nontransitory computer-readable medium according to Example 3 also include: the UE receiving RV configuration information from the base station, wherein the retransmission RV mode is determined based on the RV configuration information, and wherein the RV mode is a fixed RV mode.

[0171] Example 5: According to the method, apparatus, and non-transitory computer-readable medium of Example 4, the RV configuration message from the base station is indicated in the redundancy version field of DCI format 0_0, which has a cyclic redundancy check (CRC) scrambled via a temporary cellular radio network temporary identifier (TC-RNTI). The RV configuration message indicates the starting RV of the retransmission RV mode; wherein the plurality of repetitions of the UL message retransmission are configured by: applying the RV of the retransmission RV mode to the UL message retransmission, starting from the starting RV of the retransmission RV mode. The process begins, and continues sequentially and cyclically according to the retransmission RV pattern, looping back from the end of the retransmission RV pattern to the beginning of the retransmission RV pattern, until each of the plurality of repetitions of the UL message retransmission is configured; and wherein the plurality of repetitions of the UL message are configured by: sequentially applying the plurality of RVs to the UL message according to the RV pattern, starting from the first RV of the RV pattern, and continuing sequentially and cyclically according to the RV pattern, looping back from the end of the RV pattern to the beginning of the RV pattern, until each of the plurality of repetitions of the UL message is configured.

[0172] Example 6: The method, apparatus, and nontransitory computer-readable medium according to any one of Examples 3 to 5, wherein the RV mode is a first fixed RV mode, and wherein the retransmission RV mode is a second fixed RV mode.

[0173] Example 7: A method, apparatus, and nontransitory computer-readable medium according to any one of Examples 2 to 3, wherein the RV pattern is a first fixed RV pattern, and wherein the plurality of repetitions are configured by: sequentially applying the plurality of RVs to the UL message according to the RV pattern, starting from the first RV of the RV pattern, and continuing sequentially and cyclically according to the RV pattern, looping back from the end of the RV pattern to the beginning of the RV pattern, until each of the plurality of repetitions is configured.

[0174] Example 8: The method, apparatus and nontransitory computer-readable medium of Example 1, wherein the UL communication is a UL communication retransmission sent in response to a request received from the base station for retransmission of the UL message.

[0175] Example 9: The method, apparatus, and nontransitory computer-readable medium according to any one of Examples 1 to 3 and 8, wherein the RV mode is a fixed RV mode.

[0176] Example 10: The method, apparatus and nontransitory computer-readable medium according to any one of Examples 1 to 3 and 8 also include: the UE receiving from the base station the RV information element of the starting RV indicating the RV mode; and applying the plurality of RVs to the UL message to generate the repetitions, regardless of the received RV information element.

[0177] Example 11: The method, apparatus and nontransitory computer-readable medium according to any one of Examples 1 to 3 and 8 also include: the UE receiving from the base station an RV information element indicating the starting RV of the RV mode; and the UE applying the starting RV to the UL message to generate a first repetition of the plurality of repetitions.

[0178] Example 12: The method, apparatus and nontransitory computer-readable medium according to Example 11 also include: the UE sequentially applying the plurality of RVs to the UL message according to the RV pattern, starting from the next RV after the starting RV in the RV pattern, to generate subsequent repetitions in the plurality of repetitions.

[0179] Example 13: The method, apparatus and nontransitory computer-readable medium according to Example 12 also include: the UE continuing to sequentially and cyclically apply the plurality of RVs to the UL message according to the RV pattern, looping back from the end of the RV pattern to the beginning of the RV pattern, to generate additional subsequent repetitions in the plurality of repetitions.

[0180] Example 14: According to the method, apparatus and non-transitory computer-readable medium of Example 11, wherein the UL communication is a UL communication retransmission sent in response to a request for retransmission of the UL message received from the base station, and wherein the RV information element received from the base station is indicated in the redundancy version field of DCI format 0_0, which has a cyclic redundancy check (CRC) scrambled via a temporary cellular radio network temporary identifier (TC-RNTI).

[0181] Example 15: The method, apparatus and nontransitory computer-readable medium according to any one of Examples 1 to 3 and 8 also include: the UE receiving RV configuration information from the base station; and the UE determining the RV mode based on the RV configuration information.

[0182] Example 16: According to the method, apparatus and non-transitory computer-readable medium of Example 15, the RV configuration message includes one or more of the following: an explicit indication of an RV mode; an RV mode selection information element for selecting the RV mode from a plurality of available RV modes; a repeat enable indication for enabling the repeat of the UL message in the UL communication; or a repeat quantity information element indicating the number of the plurality of repeats.

[0183] Example 17: The method, apparatus and nontransitory computer-readable medium of Example 15, wherein the RV configuration message is an initial RV configuration message, and wherein receiving the initial RV configuration message includes: receiving from the base station a first downlink control information (DCI) associated with a random access response (RAR) message, the first DCI including one or more bits configured to indicate the initial RV configuration message.

[0184] Example 18: The method, apparatus and nontransitory computer-readable medium of Example 17, wherein the one or more bits configured to indicate the initial RV configuration message include one or more repurposed bits from a reserved set of bits in DCI format 1_0, which has cyclic redundancy check (CRC) scrambled via random access radio network temporary identifier (RA-RNTI).

[0185] Example 19: The method, apparatus and nontransitory computer-readable medium of Example 15, wherein the RV configuration message is a retransmitted RV configuration message, and wherein receiving the retransmitted RV configuration message includes: receiving downlink control information (DCI) associated with a request for retransmitting the UL message, the DCI including one or more bits configured to indicate the retransmission of the RV configuration message.

[0186] Example 20: The method, apparatus and nontransitory computer-readable medium of Example 15, wherein the one or more bits configured to indicate the retransmission of the RV configuration message include one or more bits in DCI format 0_0, the DCI format 0_0 having a cyclic redundancy check (CRC) scrambled via a temporary cellular radio network temporary identifier (TC-RNTI).

[0187] Example 21: The method, apparatus and nontransitory computer-readable medium according to Example 20, wherein one or more bits in the DCI format 0_0 correspond to one or both of the new data indicator field or the HARQ program number field.

[0188] Example 22: The method, apparatus and nontransitory computer-readable medium according to Example 15 also include: the UE receiving a system information block (SIB) from the base station, wherein the RV configuration message is received in at least one of the following: the SIB; the RAR message; or a request from the base station to retransmit the UL message.

[0189] Example 23: The method, apparatus and nontransitory computer-readable medium of any of Examples 1 to 22, wherein sending the UL communication to the base station as part of the random access procedure includes: sending the UL communication via a Physical Uplink Shared Channel (PUSCH).

[0190] Example 24: A method, apparatus, and non-transitory computer-readable medium for wireless communication operable at a base station. The base station receives a random access request from a UE for initiating a random access procedure, and responds to the random access request by sending a random access response (RAR) message to the UE. As part of the random access procedure, the base station also receives uplink (UL) communication from the UE. The UL communication comprises a plurality of repetitions of a UL message, each repetition having been configured via a corresponding RV applying an RV pattern having a plurality of RVs to the UL message. The base station also decodes the UL communication based on the RV pattern and sends downlink messages to the UE based on the UL message.

[0191] Example 25: The method, apparatus and nontransitory computer-readable medium of Example 24, wherein the UL communication includes the UL message and the plurality of repetitions of the UL message, and wherein the reception of the UL communication is based on the Random Access Response (RAR) message.

[0192] Example 26: The method, apparatus, and nontransitory computer-readable medium according to any one of Examples 24 to 25 also include: the base station sending a retransmission request for retransmitting the UL communication from the base station; and receiving the UL communication retransmission in response to the retransmission request. Here, the UL communication retransmission includes a plurality of repetitions of the UL message retransmission, each of the plurality of repetitions having been configured via a corresponding RV of a retransmission RV mode having a plurality of RVs applied to the UL message retransmission.

[0193] Example 27: The method, apparatus and nontransitory computer-readable medium according to Example 26 also include: sending an RV configuration message to the UE, wherein the retransmission RV mode is indicated by the RV configuration message, and wherein the RV mode is a fixed RV mode.

[0194] Example 28: The method, apparatus and nontransitory computer-readable medium according to Example 24 also include: sending a request to the UE for retransmission of the UL message, wherein the UL communication is a UL communication retransmission sent in response to the request for retransmission of the UL message.

[0195] This document provides several embodiments of wireless communication networks with reference to exemplary implementations. As will be readily apparent to those skilled in the art, the various embodiments described herein can be extended to other telecommunications systems, network architectures, and communication standards.

[0196] For example, various forms can be implemented in other systems defined by 3GPP, such as Long Term Evolution (LTE), Evolved Packet System (EPS), Universal Mobile Telecommunications System (UMTS), and / or Global System for Mobile Communications (GSM). These forms can also be extended to systems defined by 3GPP2, such as CDMA2000 and / or Evolved Data Optimization (EV-DO). Other examples can be implemented in systems using IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra Wideband (UWB), Bluetooth, and / or other suitable systems. The specific telecommunications standards, network architecture, and / or communication standards employed depend on the specific application and the overall design constraints imposed on the system.

[0197] The term "exemplary" as used herein means "serving as an example, illustration, or explanation." Any implementation or pattern described herein as "exemplary" is not necessarily to be construed as superior or advantageous to other patterns in this document. Similarly, the term "pattern" does not require that all patterns in this document include the features, advantages, or modes of operation discussed. The term "coupling" is used herein to refer to direct or indirect coupling between two objects. For example, if object A physically contacts object B, and object B contacts object C, then objects A and C can still be considered coupled to each other, even if they are not physically in direct contact with each other. For example, a first object can be coupled to a second object, even if the first object never physically contacts the second object. The terms "circuit" and "electronic circuit" are used broadly to include hardware implementations of electronic devices and conductors (wherein such electronic devices and conductors, when connected and configured, perform the functions described in the present invention, without limitation on the type of electronic circuit) and software implementations of information and instructions (wherein such information and instructions, when executed by a processor, perform the functions described in the present invention).

[0198] One or more of the components, steps, features, and / or functions shown in Figures 1-11 can be rearranged and / or combined into a single component, step, feature, or function, or embodied in several components, steps, or functions. Additional elements, components, steps, and / or functions can also be added without departing from the novel features disclosed herein. The apparatus, devices, and / or components shown in Figures 1-11 can be configured to perform one or more of the methods, features, or steps described herein. The novel algorithms described herein can also be efficiently implemented in software and / or embedded in hardware.

[0199] It should be understood that the specific order or hierarchy of steps in the disclosed methods is merely illustrative of exemplary procedures. It should be understood that the specific order or hierarchy of steps in these methods may be rearranged based on design preferences. The appended method request provides the elements of each step in the order of the instances provided, but is not intended to limit us to the specific order or hierarchy provided, unless expressly stated therein.

[0200] The applicant provides this description so that anyone skilled in the art to which this invention pertains can implement the various embodiments described herein. Those skilled in the art to which this invention pertains will readily recognize various modifications to these embodiments and can apply the general principles defined herein to other embodiments. The applicant does not intend to limit the claims to the embodiments shown herein, but assigns them the full scope consistent with the wording of the claims, wherein references to singular elements, unless explicitly stated otherwise, are not intended to mean "one and only one," but rather "one or more." Unless otherwise explicitly stated, the term "some" is used herein to mean one or more. The phrase "at least one" in the list of items refers to any combination of those items, including a single member. For example, "at least one of a, b, or c" is intended to cover: a; b; c; a and b; a and c; b and c; and a, b, and c. All structural and functional equivalents of the elements of the various forms described throughout this case are expressly incorporated herein by reference and are intended to be included in the claims, and are known or would be known to one of ordinary skill in the art to which this invention pertains. Furthermore, no disclosure herein is intended to be offered to the public, whether or not such disclosure is expressly stated in the claims.

[0201] 100: Wireless Communication System 102: Core Network 104: Radio Access Network (RAN) 106: User Equipment (UE) 108:Base station 110: External Data Network 112: Downlink throughput 114: Downlink Control Information 116: Uplink transmission volume 118: Uplink Control 120: Reload Section 200:RAN 202: Macrocells 204: Macrocells 206: Macrocells 208: Small cells 210:Base station 212:Base station 214:Base station 216:RRH 218:Base station 220: Mobile Base Station 222:UE 224:UE 226:UE 228:UE 230:UE 232:UE 234:UE 236:UE 238:UE 240:UE 242:UE 300: Program 302: Information Bits 304: Square 306: Square 308 bits 310: Redundant Version 312: Redundant Version 314: Redundant Version 316: Redundant Version 318: Redundant Version 320:RV Configuration 322:RV Configuration 324:RV Configuration 400: Call Flowchart 401: System Information 402:UE 403: Message 404:Base station 406: Random Access Response Message 408: Random Access Procedure Message 3 (MSG3) 410: MSG3 retransmission request 412:MSG3 retransmission 414: MSG4 transmission 500: First Instance 502: Second instance 504: First Time Slot 505: Second Time Slot 506: Area 1 508: Uplink short pulse region 510: Area 1 512: Uplink short pulse region 514: Uplink time slot 516: Uplink time slot 518: Downlink time slot 520: Downlink slot 600: Call Flowchart 601: System Information 602:UE 603: Message 604:Base station 606: Random Access Response 608: Initial MSG3 transfer 610: MSG3 retransmission request 612: MSG3 retransmission 614: MSG4 transmission 700: Scheduling Entity 702: Busbar 704: Processor 705: Memory 706: Computer-readable media 708: Bus Interface 710: Transceiver 712: User Interface 714: Processing System 740: Communication Circuit 742: RV mode determining circuit 744: First RV Determining Circuit 752: Communication Commands 754: RV mode determines instructions 756: First RV Decision Instruction 800: Scheduled Entity 802: Busbar 804: Processor 805: Memory 806: Computer-readable storage media 808: Computer-readable media 810: Transceiver 812: User Interface 814: Processing System 840: Communication Circuit 842: RV mode determining circuit 844: First RV Determining Circuit 852: Communication Commands 854: RV mode determines instructions 856: First RV Decision Instruction 900: Program 902: Square 904: Square 905: Square 906: Square 908: Square 910: Square 912: Square 912a: Sub-block 912b: Sub-block 912c: Sub-block 1000: Program 1004: Square 1008: Square 1010: Square 1100: Program 1102: Square 1104: Square 1108: Square 1110: Square 1112: Square RV-0: Redundant Version RV-1: Redundant Version RV-2: Redundant Version RV-3: Redundant Version RAN: Radio Access Network RRH: Remote Radio Header Terminal SIB: System Information Block MSG4: Random Access Message 4 UL: Uplink DL: Downlink FDD: Frequency Division Duplex TDD: Time-sharing duplex

[0202] Domestic storage information (please note in order of storage institution, date, and number) none Overseas storage information (please note in the order of storage country, institution, date, and number) none

Claims

1. A method of wireless communication operable at a user equipment (UE), the method comprising the steps of: receiving a random access response (RAR) message from a base station as part of a random access procedure; sending an uplink (UL) communication to the base station as part of the random access procedure, the UL communication comprising a plurality of repetitions of a UL message, each repetition being configured by applying a corresponding RV to the UL message via an RV pattern comprising a series of redundant versions (RVs), wherein the series of RVs comprises two or more different RVs, wherein the two or more repetitions of the plurality of repetitions are configured by applying different RVs in the series of RVs, and wherein the UL message is a message of the random access procedure 3; and receiving a downlink message from the base station based on the UL message, wherein the downlink message is a message of the random access procedure 4.

2. The method according to claim 1, wherein the UL communication includes the UL message and the plurality of repetitions of the UL message, and wherein the transmission of the UL communication is in response to the Random Access Response (RAR) message.

3. The method according to claim 1 also includes the following steps: receiving a retransmission request from the base station for retransmitting the UL communication; and responding to the retransmission request by sending a UL communication retransmission, the UL communication retransmission including a plurality of repetitions of a UL message retransmission, each of the plurality of repetitions being configured via a corresponding RV of a retransmission RV mode comprising a series of RVs in the UL message retransmission application, wherein the series of RVs comprises two or more different RVs.

4. The method according to request item 3 also includes the following steps: receiving an RV configuration message from the base station, wherein the retransmission RV mode is determined based on the RV configuration message, and wherein the RV mode is a fixed RV mode.

5. According to the method of request item 4, wherein the RV configuration message from the base station is indicated in a redundancy version field of a DCI format 0_0, the DCI format 0_0 having a cyclic redundancy check (CRC) scrambled via a temporary cellular radio network temporary identifier (TC-RNTI), the RV configuration message indicating an initial RV of the retransmission RV mode, The plurality of repetitions of the UL message retransmission are configured by applying the RV of the retransmission RV mode to the UL message retransmission, starting from the first RV of the retransmission RV mode, and continuing sequentially and cyclically according to the retransmission RV mode, looping back from the end of the retransmission RV mode to the beginning of the retransmission RV mode, until each of the plurality of repetitions of the UL message retransmission is configured, and the plurality of repetitions of the UL message are configured by applying the series of RVs sequentially to the UL message according to the RV mode, starting from the first RV of the RV mode, and continuing sequentially and cyclically according to the RV mode, looping back from the end of the RV mode to the beginning of the RV mode, until each of the plurality of repetitions of the UL message is configured.

6. According to the method of request item 3, wherein the RV mode is a first fixed RV mode, and wherein the retransmission RV mode is a second fixed RV mode.

7. The method according to request 1, wherein the RV pattern is a first fixed RV pattern, and wherein the plurality of repetitions are configured by: sequentially applying the series of RVs to the UL message according to the RV pattern, starting from a first RV of the RV pattern, and continuing sequentially and cyclically according to the RV pattern, looping back from an end of the RV pattern to the beginning of the RV pattern, until each of the plurality of repetitions is configured.

8. The method according to claim 1 also includes the following steps: receiving from the base station an RV information element indicating an initial RV mode; and applying the plurality of RVs to the UL message to generate such repetitions, regardless of the received RV information element.

9. The method according to claim 1 also includes the following steps: receiving from the base station an RV information element indicating an initial RV of the RV mode; and applying the initial RV to the UL message to generate a first repetition of the plurality of repetitions.

10. The method according to request item 9 also includes the following steps: applying the series of RVs sequentially to the UL message according to the RV pattern, starting from the next RV after the starting RV in the RV pattern, to generate subsequent repetitions in the plurality of repetitions.

11. The method according to request 10 also includes the following steps: continuing to apply the plurality of RVs sequentially and cyclically to the UL message according to the RV pattern, looping back from one end of the RV pattern to the beginning of the RV pattern to generate additional subsequent repetitions in the plurality of repetitions.

12. The method according to claim 9, wherein the UL communication is a UL communication retransmission sent in response to a request received from the base station for retransmission of the UL message, and wherein the RV information element received from the base station is indicated in a redundancy version field of a DCI format 0_0 having a cyclic redundancy check (CRC) scrambled via a temporary cellular radio network temporary identifier (TC-RNTI).

13. The method according to request item 1 also includes the following steps: receiving an RV configuration message from the base station; and determining the RV mode based on the RV configuration message.

14. The method according to claim 13, wherein the RV configuration message includes one or more of the following: an explicit indication of an RV mode; an RV mode selection information element for selecting the RV mode from a plurality of available RV modes; a repeat enable indication for enabling the repeats of the UL message in the UL communication; or a repeat quantity information element indicating a number of the plurality of repeats.

15. The method according to request item 14, wherein the RV configuration message is an initial RV configuration message, and wherein receiving the initial RV configuration message includes: The base station receives a first downlink control information (DCI) associated with a random access response (RAR) message, the first DCI including one or more bits configured to indicate the initial RV configuration message.

16. The method of request item 15, wherein the one or more bits configured to indicate the initial RV configuration message include one or more repurposed bits from a reserved set of bits in a DCI format 1_0, the DCI format 1_0 having a cyclic redundancy check (CRC) scrambled via a random access radio network temporary identifier (RA-RNTI).

17. The method of request item 16, wherein the RV configuration message is a retransmission RV configuration message, and wherein receiving the retransmission RV configuration message includes the following steps: receiving downlink control information (DCI) associated with a request for retransmission of the UL message, the DCI including one or more bits configured to indicate the retransmission RV configuration message.

18. The method of claim 17, wherein the one or more bits configured to indicate the retransmission of the RV configuration message include one or more bits in a DCI format 0_0, the DCI format 0_0 having a cyclic redundancy check (CRC) scrambled via a temporary cellular radio network temporary identifier (TC-RNTI).

19. The method of request item 18, wherein the one or more bits in the DCI format 0_0 correspond to one or both of a new data indicator field or a HARQ procedure number field.

20. The method of claim 1, wherein sending the UL communication to the base station as part of the random access procedure includes: The UL communication is sent via a Physical Uplink Shared Channel (PUSCH).

21. An apparatus for wireless communication, the apparatus comprising: A unit for receiving a Random Access Response (RAR) message from a base station as part of a random access procedure; a unit for sending an uplink (UL) communication to the base station as part of the random access procedure, the UL communication comprising a plurality of repetitions of a UL message, each repetition being configured by applying a corresponding RV to the UL message via an RV pattern comprising a series of redundant versions (RVs), wherein the series of RVs comprises two or more different RVs, wherein the two or more repetitions of the plurality of repetitions are configured by applying different RVs in the series of RVs, and wherein the UL message is a message 3 of the random access procedure; and a unit for receiving a downlink message from the base station based on the UL message, wherein the downlink message is a message 4 of the random access procedure.

22. The apparatus according to claim 21, wherein the UL communication includes the UL message and the plurality of repetitions of the UL message, and wherein a unit for transmitting the UL communication responds to the Random Access Response (RAR) message to transmit the UL communication.

23. The apparatus according to claim 21 also includes: A unit for receiving a retransmission request from the base station for retransmitting the UL communication; and a unit for sending a UL communication retransmission in response to the retransmission request, the UL communication retransmission including a plurality of repetitions of a UL message retransmission, each of the plurality of repetitions being configured via a corresponding RV of a retransmission RV mode comprising a series of RVs in the UL message retransmission application, wherein the series of RVs comprises two or more different RVs.

24. The apparatus according to claim 23 also includes: A unit for receiving an RV configuration message from the base station, wherein the retransmission RV mode is determined based on the RV configuration message, and wherein the RV mode is a fixed RV mode.

25. The apparatus according to claim 24, wherein the RV configuration message from the base station is indicated in a redundancy version field of a DCI format 0_0, the DCI format 0_0 having a cyclic redundancy check (CRC) scrambled via a temporary cellular radio network temporary identifier (TC-RNTI), the RV configuration message indicating an initial RV of the retransmission RV mode, The plurality of repetitions of the UL message retransmission are configured by applying the RV of the retransmission RV mode to the UL message retransmission, starting from the first RV of the retransmission RV mode, and continuing sequentially and cyclically according to the retransmission RV mode, looping back from the end of the retransmission RV mode to the beginning of the retransmission RV mode, until each of the plurality of repetitions of the UL message retransmission is configured, and the plurality of repetitions of the UL message are configured by applying the series of RVs sequentially to the UL message according to the RV mode, starting from the first RV of the RV mode, and continuing sequentially and cyclically according to the RV mode, looping back from the end of the RV mode to the beginning of the RV mode, until each of the plurality of repetitions of the UL message is configured.

26. The apparatus according to claim 23, wherein the RV mode is a first fixed RV mode, and wherein the retransmission RV mode is a second fixed RV mode.

27. The apparatus according to claim 21, wherein the RV pattern is a first fixed RV pattern, and wherein the plurality of repetitions are configured by: sequentially applying the series of RVs to the UL message according to the RV pattern, starting from a first RV of the RV pattern, and continuing sequentially and cyclically according to the RV pattern, looping back from an end of the RV pattern to the beginning of the RV pattern, until each of the plurality of repetitions is configured.

28. The apparatus according to claim 21 also includes: A unit for receiving an RV information element indicating the RV mode of an initial RV from the base station; And a unit for applying the plurality of RVs to the UL message to generate such repetitions, regardless of the received RV information elements.

29. The apparatus according to claim 21 also includes: A unit for receiving an RV information element indicating the RV mode of an initial RV from the base station; And a unit for applying the starting RV to the UL message to generate a first repetition of the plurality of repetitions.

30. The apparatus according to claim 29 also includes: Units used to apply the series of RVs sequentially to the UL message according to the RV pattern, starting from the next RV after the starting RV in the RV pattern, to generate subsequent repetitions in the plurality of repetitions.

31. The apparatus according to claim 30 also includes: Units for continuing to apply the plurality of RVs sequentially and cyclically to the UL message according to the RV pattern, looping back from one end of the RV pattern to the beginning of the RV pattern to generate additional subsequent repetitions in the plurality of repetitions.

32. The apparatus according to claim 29, wherein the UL communication is a UL communication retransmission sent in response to a request received from the base station for retransmission of the UL message, and wherein the RV information element received from the base station is indicated in a redundancy version field of a DCI format 0_0 having a cyclic redundancy check (CRC) scrambled via a temporary cellular radio network temporary identifier (TC-RNTI).

33. The apparatus according to claim 21 also includes: A unit used to receive RV configuration information from the base station; And a unit for determining the RV mode based on the RV configuration information.

34. The apparatus according to claim 33, wherein the RV configuration message includes one or more of the following: an explicit indication of an RV mode; an RV mode selection information element for selecting the RV mode from a plurality of available RV modes; a repeat enable indication for enabling the repeats of the UL message in the UL communication; or a repeat quantity information element indicating a number of the plurality of repeats.

35. The apparatus according to claim 34, wherein the RV configuration message is an initial RV configuration message, and wherein the unit for receiving the initial RV configuration message includes: A unit for receiving a first downlink control information (DCI) associated with a random access response (RAR) message from the base station, the first DCI including one or more bits configured to indicate the initial RV configuration message.

36. The apparatus according to claim 35, wherein the one or more bits configured to indicate the initial RV configuration message include one or more repurposed bits from a reserved set of bits in a DCI format 1_0, the DCI format 1_0 having a cyclic redundancy check (CRC) scrambled via a random access radio network temporary identifier (RA-RNTI).

37. The apparatus according to claim 36, wherein the RV configuration message is a retransmitted RV configuration message, and wherein the unit for receiving the retransmitted RV configuration message includes: A unit for receiving downlink control information (DCI) associated with a request to retransmit the UL message, the DCI including one or more bits configured to indicate the retransmission of the RV configuration message.

38. The apparatus according to claim 37, wherein the one or more bits configured to indicate the retransmission of the RV configuration message include one or more bits in a DCI format 0_0, the DCI format 0_0 having a cyclic redundancy check (CRC) scrambled via a temporary cellular radio network temporary identifier (TC-RNTI).

39. The apparatus according to claim 38, wherein the one or more bits in the DCI format 0_0 correspond to one or both of a new data indicator field or a HARQ program number field.

40. The apparatus according to claim 21, wherein the unit for transmitting the UL communication to the base station as part of the random access procedure comprises: A unit used to transmit the UL communication via a physical uplink shared channel (PUSCH).

41. An apparatus for wireless communication, the apparatus comprising: One processor; A transceiver is communicatively coupled to the processor; The transceiver is communicatively coupled to a memory, wherein the processor and the memory are configured to: receive a Random Access Response (RAR) message from a base station as part of a random access procedure; send an uplink (UL) communication to the base station via the transceiver as part of the random access procedure, the UL communication comprising a plurality of repetitions of a UL message, each repetition being configured by applying a corresponding RV to the UL message using an RV pattern comprising a series of redundancy versions (RVs), wherein the series of RVs comprises two or more different RVs, wherein the two or more repetitions of the plurality of repetitions are configured by applying different RVs in the series of RVs, and wherein the UL message is a message 3 of the random access procedure; and receive a downlink message from the base station via the transceiver based on the UL message, wherein the downlink message is a message 4 of the random access procedure.

42. The apparatus according to claim 41, wherein the UL communication includes the UL message and the plurality of repetitions of the UL message, and wherein the processor and memory are configured to send the UL communication in response to the Random Access Response (RAR) message.

43. The apparatus according to claim 41, wherein the processor and memory are also configured to: receive a retransmission request from the base station for retransmitting the UL communication; and in response to the retransmission request send a UL communication retransmission, the UL communication retransmission comprising a plurality of repetitions of a UL message retransmission, each of the plurality of repetitions being configured via a corresponding RV of a retransmission RV mode comprising a series of RVs in the UL message retransmission application, wherein the series of RVs comprises two or more different RVs.

44. The apparatus according to request 43, wherein the processor and memory are also configured to: receive an RV configuration message from the base station, wherein the retransmission RV mode is determined based on the RV configuration message, and wherein the RV mode is a fixed RV mode.

45. The apparatus according to claim 44, wherein the RV configuration message from the base station is indicated in a redundancy version field of a DCI format 0_0, the DCI format 0_0 having a cyclic redundancy check (CRC) scrambled via a temporary cellular radio network temporary identifier (TC-RNTI), the RV configuration message indicating an initial RV of the retransmission RV mode, The plurality of repetitions of the UL message retransmission are configured by applying an RV of the retransmission RV mode to the UL message retransmission, starting from the starting RV of the retransmission RV mode, and continuing sequentially and cyclically according to the retransmission RV mode, looping back from the end of the retransmission RV mode to the beginning of the retransmission RV mode, until each of the plurality of repetitions of the UL message retransmission is configured, and the plurality of repetitions of the UL message are configured by applying the series of RVs sequentially to the UL message according to the RV mode, starting from the first RV of the RV mode, and continuing sequentially and cyclically according to the RV mode, looping back from the end of the RV mode to the beginning of the RV mode, until each of the plurality of repetitions of the UL message is configured.

46. ​​The apparatus according to claim 43, wherein the RV mode is a first fixed RV mode, and wherein the retransmission RV mode is a second fixed RV mode.

47. The apparatus according to claim 41, wherein the RV pattern is a first fixed RV pattern, and wherein the plurality of repetitions are configured by: sequentially applying the series of RVs to the UL message according to the RV pattern, starting from a first RV of the RV pattern, and continuing sequentially and cyclically according to the RV pattern, looping back from an end of the RV pattern to the beginning of the RV pattern, until each of the plurality of repetitions is configured.

48. The apparatus according to claim 41, wherein the processor and memory are also configured to: receive from the base station an RV information element indicating an initial RV of the RV mode; and apply the plurality of RVs to the UL message to generate the repetitions, regardless of the received RV information element.

49. The apparatus according to claim 41, wherein the processor and memory are also configured to: receive from the base station an RV information element indicating an initial RV of the RV mode; and apply the initial RV to the UL message to generate a first repetition of the plurality of repetitions.

50. The apparatus according to claim 49, wherein the processor and memory are also configured to: apply the series of RVs sequentially to the UL message according to the RV pattern, starting from the next RV after the starting RV in the RV pattern, to generate subsequent repetitions in the plurality of repetitions.

51. The apparatus according to claim 50, wherein the processor and memory are also configured to: continue to apply the plurality of RVs sequentially and cyclically to the UL message according to the RV pattern, looping back from one end of the RV pattern to the beginning of the RV pattern to generate additional subsequent repetitions in the plurality of repetitions.

52. The apparatus according to claim 49, wherein the UL communication is a UL communication retransmission sent in response to a request received from the base station for retransmission of the UL message, and wherein the RV information element received from the base station is indicated in a redundancy version field of a DCI format 0_0 having a cyclic redundancy check (CRC) scrambled via a temporary cellular radio network temporary identifier (TC-RNTI).

53. The apparatus according to request 41, wherein the processor and memory are also configured to: receive an RV configuration message from the base station; and determine the RV mode based on the RV configuration message.

54. The apparatus according to claim 53, wherein the RV configuration message includes one or more of the following: an explicit indication of an RV mode; an RV mode selection information element for selecting the RV mode from a plurality of available RV modes; a repeat enable indication for enabling the repeats of the UL message in the UL communication; or a repeat quantity information element indicating a number of the plurality of repeats.

55. The apparatus according to claim 54, wherein the RV configuration message is an initial RV configuration message, and in order to receive the initial RV configuration message, and wherein the processor and memory are also configured to: receive from the base station a first downlink control information (DCI) associated with a random access response (RAR) message, the first DCI including one or more bits configured to indicate the initial RV configuration message.

56. The apparatus according to claim 55, wherein the one or more bits configured to indicate the initial RV configuration message include one or more repurposed bits from a reserved set of bits in a DCI format 1_0, the DCI format 1_0 having a cyclic redundancy check (CRC) scrambled via a random access radio network temporary identifier (RA-RNTI).

57. The apparatus according to claim 56, wherein the RV configuration message is a retransmission RV configuration message, and wherein, in order to receive the retransmission RV configuration message, the processor and memory are also configured to: receive downlink control information (DCI) associated with a request for retransmission of the UL message, the DCI including one or more bits configured to indicate the retransmission RV configuration message.

58. The apparatus according to claim 57, wherein the one or more bits configured to indicate that the retransmitted RV configuration message includes one or more bits in DCI format 0_0, the DCI format 0_0 having a cyclic redundancy check (CRC) scrambled via a temporary cellular radio network temporary identifier (TC-RNTI).

59. The apparatus according to claim 58, wherein the one or more bits in the DCI format 0_0 correspond to one or both of a new data indicator field or a HARQ program number field.

60. The apparatus according to claim 41, wherein, as part of the random access procedure, in order to send the UL communication to the base station, the processor and memory are also configured to send the UL communication via a physical uplink shared channel (PUSCH).

61. A method of wireless communication operable at a base station, the method comprising the steps of: receiving from a UE a random access request for initiating a random access procedure; responding to the random access request by sending a random access response (RAR) message to the UE; as part of the random access procedure, receiving from the UE an uplink (UL) communication comprising a plurality of repetitions of a UL message, each repetition having been configured by applying an RV pattern comprising a series of redundant versions (RVs) to the UL message, wherein the series of RVs comprises two or more different RVs, wherein the two or more repetitions of the plurality of repetitions are configured by applying different RVs in the series of RVs, and wherein the UL message is a message of the random access procedure 3; decoding the UL communication based on the RV pattern; and sending a downlink message to the UE based on the UL message, wherein the downlink message is a message of the random access procedure 4.

62. The method of claim 61, wherein the UL communication includes the UL message and the plurality of repetitions of the UL message, and wherein the reception of the UL communication is based on the Random Access Response (RAR) message.

63. The method according to claim 62 also includes the following steps: sending a retransmission request from the base station for retransmitting the UL communication; and responding to the retransmission request to receive a UL communication retransmission, the UL communication retransmission including a plurality of repetitions of a UL message retransmission, each of the plurality of repetitions having been configured via a corresponding RV of a retransmission RV mode comprising a series of RVs in the UL message retransmission application, wherein the series of RVs comprises two or more different RVs.

64. The method according to request item 63 also includes the following steps: sending an RV configuration message to the UE, wherein the retransmission RV mode is indicated by the RV configuration message, and wherein the RV mode is a fixed RV mode.

65. The method according to request item 61 also includes the following steps: sending a request to the UE for retransmission of the UL message, wherein the UL communication is a UL communication retransmission sent in response to the request for retransmission of the UL message.

66. An apparatus for wireless communication, comprising: One processor; A transceiver is communicatively coupled to the processor; The transceiver and a memory are communicatively coupled to the processor, wherein the processor and the memory are configured to: receive a random access request from a UE via the transceiver for initiating a random access procedure; respond to the random access request by sending a random access response (RAR) message to the UE via the transceiver; as part of the random access procedure, receive an uplink (UL) communication from the UE via the transceiver, the UL communication comprising a plurality of repetitions of a UL message, each repetition having been configured by applying an RV pattern comprising a series of RVs to the UL message, wherein the series of RVs comprises two or more different RVs, wherein the two or more repetitions of the plurality of repetitions are configured by applying different RVs in the series of RVs, and wherein the UL message is a message of the random access procedure 3; decode the UL communication based on the RV pattern; and send a downlink message to the UE via the transceiver based on the UL message, wherein the downlink message is a message of the random access procedure 4.

67. The apparatus according to claim 66, wherein the UL communication includes the UL message and the plurality of repetitions of the UL message, and wherein the reception of the UL communication is based on the Random Access Response (RAR) message.

68. The apparatus according to claim 67, wherein the processor and memory are also configured to: send a retransmission request to the UE for retransmitting the UL communication; and in response to the retransmission request to receive a UL communication retransmission, the UL communication retransmission comprising a plurality of repetitions of a UL message retransmission, each of the plurality of repetitions having been configured via a corresponding RV of a retransmission RV mode comprising a series of RVs in the UL message retransmission application, wherein the series of RVs comprises two or more different RVs.

69. The apparatus according to request 68, wherein the processor and memory are also configured to: send an RV configuration message to the UE via the transceiver, wherein the retransmission RV mode is indicated by the RV configuration message, and wherein the RV mode is a fixed RV mode.

70. The apparatus according to claim 66, wherein the processor and memory are also configured to: send a request to the UE via the transceiver for retransmitting the UL message, wherein the UL communication is a UL communication retransmission sent in response to the request for retransmitting the UL message.

Images