Resource allocation of preamble and payload for messages in two-step random access (RA) procedure in new radio (NR) systems

Abstract

The present disclosure relates generally to resource allocation of preambles and payloads of messages in a two-step random access (RA) procedure in a new radio (NR) system. Embodiments of user equipment (UE), next generation node B (gNB), and communication methods are described throughout. A UE can receive, from a gNB in an unlicensed spectrum, configuration information related to a two-step random access (RA) procedure between the UE and the gNB. The two-step RA procedure can include an uplink MsgA message including a MsgA preamble and a MsgA payload within a random access occasion (RO), and a downlink MsgB message including a MsgB PDCCH and a MsgB payload within another RO. The configuration information can indicate resources allocated for the MsgA preamble and a mapping between the resources allocated for the MsgA preamble and resources allocated for the MsgA payload. The UE can determine the resources allocated for the MsgA payload based on the resources allocated for the MsgA preamble and the mapping.

Description

[0001] This case is a divisional application of the application with international application number PCT / US2019 / 053286, international application date of September 26, 2019, entry into the Chinese national phase date of March 15, 2021, national application number 201980060344.2, entitled "Resource allocation of message preamble and payload in a two-step random access (RA) process in a New Radio (NR) system".

[0002] Priority requirements

[0003] This patent application claims priority to U.S. Provisional Patent Application Serial No. 62 / 737644, filed on September 27, 2018, the entire contents of which are incorporated herein by reference. Technical Field

[0004] The implementation schemes involve wireless communications. Some implementations involve wireless networks, including 3GPP (3rd Generation Partnership Project) networks, 3GPP LTE (Long Term Evolution) networks, 5G networks, and / or New Radio (NR) networks. Some implementations involve random access (RA) procedures, including two-step RA procedures. Some implementations involve the resource allocation of preambles and payloads for messages in the two-step RA procedure for NR systems. Background Technology

[0005] Effective utilization of wireless network resources is crucial for providing users with sufficient bandwidth and acceptable response times. However, many devices often attempt to share the same resources, and some devices may be limited by the communication protocols they use or their hardware bandwidth. Furthermore, wireless devices may need to operate using both newer and legacy protocols. Attached Figure Description

[0006] Figure 1A This is a functional diagram of an exemplary network based on some implementation schemes;

[0007] Figure 1B This is a functional diagram of another exemplary network according to some implementation schemes;

[0008] Figure 2 This is a block diagram of an exemplary machine according to some implementation schemes;

[0009] Figure 3 An exemplary communication circuit is shown according to some aspects;

[0010] Figure 4 The operation of a communication method according to some implementation schemes is illustrated; and

[0011] Figure 5The operation of a communication method according to some implementation schemes is illustrated. Detailed Implementation

[0012] The following description and accompanying drawings fully illustrate specific embodiments, enabling those skilled in the art to practice these embodiments. Other embodiments may incorporate structural, logical, electrical, process, and other variations. Some portions and features of certain embodiments may be included in or replace portions and features of other embodiments. The embodiments set forth in the claims cover all available equivalents of these claims.

[0013] Figure 1A This is a functional diagram of an exemplary network based on some implementation schemes. Figure 1B This is a functional diagram of another exemplary network according to some implementation schemes. In the references herein, "Figure 1" may include... Figure 1A and Figure 1B In some implementations, network 100 may be a 3GPP (3rd Generation Partnership Project) network. In some implementations, network 150 may be a 3GPP network, a New Radio (NR) network, and / or a 5G network. In some implementations, other networks may be used. In some implementations, the network may include one or more of the following: Figure 1A One or more components are shown; Figure 1B One or more components are shown; and one or more additional components. Some embodiments may not necessarily include... Figure 1A and Figure 1B All the components shown.

[0014] Network 100 may include a radio access network (RAN) 101 and a core network 120 (e.g., shown as an evolved packet core (EPC)) coupled together via an S1 interface 115. For simplicity and brevity, only a portion of the core network 120 and RAN 101 are shown. In some embodiments, RAN 101 may include one or more of the following: one or more components of an evolved universal terrestrial radio access network (E-UTRAN), one or more components of an NR network, and / or one or more other components.

[0015] Core network 120 may include a Mobility Management Entity (MME) 122, a Serving Gateway (Serving GW) 124, and a Packet Data Network Gateway (PDN GW) 126. In some embodiments, networks 100, 150 may include (and / or support) one or more evolved Node Bs (eNBs) 104 and / or one or more next-generation Node Bs (gNBs) 105. eNBs 104 and / or gNBs 105 may operate as base stations for communicating with User Equipment (UE) 102. In some embodiments, one or more eNBs 104 may be configured to operate as gNBs 105. Implementations are not limited to these embodiments. Figure 1A The number of eNB 104 shown or Figure 1B The number of gNB 105s shown. The implementation scheme is not limited to... Figure 1A The connectivity of the components shown.

[0016] It should be noted that references to eNB 104 or gNB 105 herein are not restrictive. In some embodiments, one or more operations, methods, and / or technologies (such as those described herein) may be practiced by base station components (and / or other components), including but not limited to gNB 105, eNB 104, serving cell, transceiver point (TRP), and / or others. In some embodiments, base station components may be configured to operate according to one or more of the following: 3GPP LTE protocol / standard, NR protocol / standard, fifth-generation (5G) protocol / standard; and / or other protocols / standards, but the scope of the embodiments is not limited in this respect.

[0017] The description herein of one or more operations, techniques and / or methods practiced by components (such as UE 102, eNB 104, gNB 105 and / or other components) is not limiting. In some embodiments, one or more of these operations, techniques and / or methods may be practiced by another component.

[0018] MME 122 manages access-related mobility aspects such as gateway selection and tracking area list management. Service GW 124 terminates the interface to RAN 101 and routes data packets between RAN 101 and core network 120. Additionally, this service GW can serve as a local mobility anchor for inter-eNB handovers and can also provide an anchor for inter-3GPP mobility. Service GW 124 and MME 122 can be implemented in a single physical node or in separate physical nodes.

[0019] In some implementations, UE 102, eNB 104 and / or gNB 105 may be configured to transmit orthogonal frequency division multiplexing (OFDM) communication signals through a multi-carrier communication channel in accordance with orthogonal frequency division multiple access (OFDMA) communication technology.

[0020] In some implementations, network 150 may include one or more components configured to operate according to one or more 3GPP standards (including, but not limited to, NR standards). Figure 1B The network 150 shown may include a next-generation RAN (NG-RAN) 155, which may include one or more gNBs 105. In some embodiments, network 150 may include an E-UTRAN 160, which may include one or more eNBs. The E-UTRAN 160 may be similar to RAN 101 described herein, but the scope of the embodiments is not limited in this respect.

[0021] In some embodiments, network 150 may include MME 165, which may be similar to MME 122 described herein, but the scope of the embodiments is not limited in this respect. In some embodiments, network 150 may include SGW 170, which may be similar to SGW 124 described herein, but the scope of the embodiments is not limited in this respect.

[0022] The implementation plan is not limited to Figure 1B The number or type of components shown. The implementation is also not limited to... Figure 1B The connectivity of the components shown.

[0023] As used herein, the term "circuit" can refer to or include, an application-specific integrated circuit (ASIC), electronic circuit, processor (shared, dedicated, or grouped), and / or memory (shared, dedicated, or grouped), as part of or including, any suitable hardware component that performs one or more software or firmware programs, combinational logic circuits, and / or provides the described functions. In some embodiments, the circuit may be implemented in one or more software or firmware modules, or the functions associated with the circuit may be implemented by one or more software or firmware modules. In some embodiments, the circuit may include logic components that operate at least partially in hardware. The embodiments described herein can be implemented into a system using any appropriately configured hardware and / or software.

[0024] Figure 2This is a block diagram of an exemplary machine according to some implementation schemes. Machine 200 is an exemplary machine on which any one or more of the technologies and / or methods discussed herein can be performed. In alternative implementations, machine 200 may operate as a standalone device or may be connected (e.g., networked) to other machines. Machine 200 may be a UE 102, eNB 104, gNB 105, access point (AP), station (STA), user, device, mobile device, base station, another device, or any machine capable of (sequentially or otherwise) executing instructions specifying the actions to be taken by that machine. Furthermore, although only a single machine is shown, the term "machine" should also be considered as including any collection of machines that individually or collectively execute a set (or more) of instructions to perform any one or more methods discussed herein, such as cloud computing, Software as a Service (SaaS), and other computer cluster configurations.

[0025] Examples as described herein may include or may include logical components or components, modules or mechanisms, or may run on or on logical components or components, modules or mechanisms.

[0026] Machine (e.g., computer system) 200 may include hardware processor 202 (e.g., central processing unit (CPU), graphics processing unit (GPU), hardware processor core, or any combination thereof), main memory 204, and static memory 206, some or all of which may communicate with each other via interconnect links (e.g., bus) 208. Machine 200 may also include one or more of 210-228.

[0027] Storage device 216 may include machine-readable medium 222 on which one or more sets of data structures or instructions 224 (e.g., software) embodied or utilized by any or more of the techniques or functions described herein may be stored. During execution of instructions 224 by machine 200, these instructions may also reside wholly or at least partially within main memory 204, static memory 206, or hardware processor 202. In one example, one or any combination of hardware processor 202, main memory 204, static memory 206, or storage device 216 may constitute a machine-readable medium. In some embodiments, the machine-readable medium may be or may include a non-transitory computer-readable storage medium. In some embodiments, the machine-readable medium may be or may include a computer-readable storage medium.

[0028] Although machine-readable medium 222 is shown as a single medium, the term "machine-readable medium" can include a single or multiple media (e.g., a centralized or distributed database, and / or associated caches and servers) configured to store one or more instructions 224. The term "machine-readable medium" can include any medium capable of storing, encoding, or carrying instructions for execution by machine 200 and causing machine 200 to perform any or more of the techniques disclosed herein, or any medium capable of storing, encoding, or carrying data structures used by or associated with such instructions. Examples of non-limiting machine-readable media can include solid-state memory, as well as optical and magnetic media. Specific examples of machine-readable media can include: non-volatile memory, such as semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM)) and flash memory devices; disks, such as internal hard disks and removable disks; magneto-optical disks; random access memory (RAM); and CD-ROM and DVD-ROM disks. In some examples, machine-readable media can include non-transitory machine-readable media. In some examples, machine-readable media may include machine-readable media that are not transient propagating signals.

[0029] Instruction 224 may also be transmitted or received via communication network 226 using a transmission medium via network interface device 220, utilizing any of a plurality of transmission protocols. In one example, network interface device 220 may include multiple antennas for wireless communication using at least one of single-input multiple-output (SIMO), multiple-input multiple-output (MIMO), or multiple-input single-output (MISO) technologies. In some examples, network interface device 220 may use multi-user MIMO technology for wireless communication. The term “transmission medium” should be considered to include any intangible medium capable of storing, encoding, or carrying instructions for execution by machine 200, and includes digital or analog communication signals or other intangible media used to facilitate communication of such software.

[0030] Figure 3Exemplary communication circuitry according to some aspects is illustrated. It should be noted that, in some aspects, devices such as UE102, eNB 104, gNB 105, machine 200, and / or other devices may include one or more components of communication circuitry 300. Communication circuitry 300 may include protocol processing circuitry 305 that implements one or more of Media Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP), Radio Resource Control (RRC), and Non-Access Stratum (NAS) functions. Communication circuitry 300 may also include digital baseband circuitry 310 that implements one or more physical layer (PHY) functions. Communication circuitry 300 may also include transmitting circuitry 315, receiving circuitry 320, and / or antenna array circuitry 330. Communication circuitry 300 may also include radio frequency (RF) circuitry 325. In one aspect of this disclosure, RF circuitry 325 may include multiple parallel RF chains for one or more of the transmit or receive functions, each chain connected to one or more antennas of antenna array 330.

[0031] In some implementations, the processing circuitry may perform one or more of the operations and / or other operations described herein. In a non-limiting example, the processing circuitry may include one or more components, such as processor 202, protocol processing circuitry 305, digital baseband circuitry 310, similar components, and / or other components.

[0032] In some implementations, the transceiver may transmit one or more elements (including, but not limited to, those described herein) and / or receive one or more elements (including, but not limited to, those described herein). In a non-limiting example, the transceiver may include one or more components, such as transmitting circuitry 315, receiving circuitry 320, radio frequency circuitry 325, similar components, and / or other components.

[0033] Although the UE 102, eNB 104, gNB 105, machine 200, and / or other devices described herein may each be shown as having several individual functional elements, one or more of these functional elements may be combined and implemented by a combination of software-configurable elements, such as processing elements including digital signal processors (DSPs), one or more microprocessors, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), radio frequency integrated circuits (RFICs), and various combinations of hardware and logic circuits for performing at least the functions described herein. In some embodiments, a functional element may refer to one or more processes running on one or more processing elements.

[0034] Implementations may be implemented in one or a combination of hardware, firmware, and software. Implementations may also be implemented as instructions stored on a computer-readable storage device that can be read and executed by at least one processor to perform the operations described herein. A computer-readable storage device may include any non-transitory mechanism for storing information in a machine-readable (e.g., computer) form. For example, a computer-readable storage device may include read-only memory (ROM), random access memory (RAM), disk storage media, optical storage media, flash memory devices, and other storage devices and media. Some implementations may include one or more processors and may be configured via instructions stored on the computer-readable storage device.

[0035] It should be noted that, in some implementations, the means of UE 102, eNB 104, gNB 105, machine 200, and / or other devices may include Figures 2 to 3 The various components and / or other parts shown. Therefore, in some embodiments, the techniques and operations performed by the device described herein can be performed by the device's apparatus.

[0036] According to some implementation schemes, UE 102 can receive configuration information related to a two-step random access (RA) procedure between UE 102 and gNB 105 in unlicensed spectrum. This two-step RA procedure may include: an uplink MsgA message comprising a MsgA preamble and MsgA payload within a random access opportunity (RO); and a downlink MsgB message comprising a MsgB physical downlink control channel (PDCCH) and MsgB payload within another RO. The configuration information may indicate: the allocation of resources for the MsgA preamble; and a mapping between the resources allocated for the MsgA preamble and the resources allocated for the MsgA payload. UE 102 may determine the resources allocated for the MsgA payload based on the resources allocated for the MsgA preamble and this mapping. UE 102 may transmit the MsgA preamble in the resources allocated for the MsgA preamble during the RO period obtained by UE 102. UE 102 may also transmit the MsgA payload in the resources determined for the MsgA payload during the RO period obtained by UE 102. These implementations will be described in more detail below.

[0037] Figure 4 The operation of a communication method according to some implementation schemes is illustrated. Figure 5 The operation of another communication method according to some implementation schemes is illustrated. It is important to note that... Figures 4-5Compared to the operations or processes shown, embodiments of methods 400 and 500 may include additional or even fewer operations or processes. Furthermore, embodiments of methods 400 and 500 are not necessarily limited to... Figures 4-5 The chronological order is shown. In the description of methods 400 and 500, reference may be made to one or more accompanying drawings, but it should be understood that methods 400 and 500 can be practiced using any other suitable systems, interfaces, and components.

[0038] In some embodiments, UE 102 may perform one or more operations of method 400, but the embodiments are not limited to the execution of method 400 and / or the operation of UE 102 thereto. In some embodiments, another device and / or component (such as gNB 105, eNB 104, and / or others) may perform one or more operations of method 400. In some embodiments, another device and / or component (such as gNB 105, eNB 104, and / or others) may perform one or more operations that are similar to, related to, and / or opposite to one or more operations of method 400. In a non-limiting example, in some embodiments, gNB 105 may perform operations that are the same as, similar to, opposite to, and / or related to the operation of method 400. In some embodiments, UE 102 may perform operations that are the same as, similar to, opposite to, and / or related to the operation of method 400.

[0039] In some embodiments, gNB 105 may perform one or more operations of method 500, but the embodiments are not limited to gNB 105 performing method 500 and / or its operations. In some embodiments, another device and / or component (such as UE 102, eNB 104, and / or others) may perform one or more operations of method 500. In some embodiments, another device and / or component (such as UE 102, eNB 104, and / or others) may perform one or more operations that are similar to, related to, and / or opposite to one or more operations of method 500. In a non-limiting example, in some embodiments, UE 102 may perform operations that are the same as, similar to, opposite to, and / or related to the operations of method 500. In some embodiments, gNB 105 may perform operations that are the same as, similar to, opposite to, and / or related to the operations of method 500.

[0040] It should be noted that one or more operations of one method (such as 400, 500, and / or other methods described herein) may be identical, similar, related, and / or opposite to one or more operations of another method (such as 400, 500, and / or other methods described herein). For example, in some embodiments, the operation of method 400 may be identical, similar, related, and / or opposite to the operation of method 500. In a non-limiting example, the operation of method 400 may include receiving elements (such as frames, blocks, messages, and / or other elements) by UE 102, and the operation of method 500 may include transmitting the same elements (and / or similar elements) by gNB 105. In some cases, at least some of the descriptions of operations and techniques described as part of one method (such as 400, 500, and / or other methods described herein) may be related to another method (such as 400, 500, and / or other methods described herein).

[0041] The methods 400, 500, and other methods described herein can be applied to eNB 104, gNB 105, and / or UE 102 operating according to 3GPP standards, 5G standards, NR standards, and / or other standards. However, the implementation is not limited to those components performing those methods, and they can also be performed by other devices such as Wi-Fi access points (APs) or user stations (STAs). Furthermore, methods 400, 500, and other methods described herein can be implemented by wireless devices configured to operate in other suitable types of wireless communication systems, including systems configured to operate according to various IEEE standards such as IEEE 802.11. Methods 400 and 500 are also applicable to devices of gNB 105, UE 102, eNB 104, and / or the other device described above.

[0042] In some embodiments, the means of the device (including, but not limited to, UE 102, eNB 104, gNB 105, and / or others) may include memories that can be configured to store one or more elements, and the means may use them to perform one or more operations. The means may include processing circuitry capable of performing one or more operations (including, but not limited to, operations of one or more methods, such as 400, 500, and / or other methods described herein). The processing circuitry may include a baseband processor. The baseband circuitry and / or the processing circuitry may perform one or more operations described herein. The means may include a transceiver for transmitting and / or receiving one or more blocks, messages, and / or other elements.

[0043] Implementations are not limited to the references herein to the transmission, reception, and / or exchange of elements such as frames, messages, requests, indicators, signals, or other elements. In some embodiments, such elements may be generated, encoded, or otherwise processed by processing circuitry for transmission by a transceiver or other component housing. In some embodiments, such elements may be received by a transceiver or other component and may be decoded, detected, or otherwise processed by processing circuitry. In some embodiments, the processing circuitry and the transceiver may be included in the same device. In some embodiments, the transceiver may be separate from the device including the processing circuitry.

[0044] One or more elements described herein (such as messages, operations, and / or others) may be included in 3GPP protocols, 3GPP LTE protocols, 4G protocols, 5G protocols, NR protocols, and / or other protocols, but implementations are not limited to the use of these elements. In some implementations, other elements may be used, including other elements in the same standard / protocol, other elements in another standard / protocol, and / or other elements. Furthermore, the scope of implementations is not limited to the use of elements included in the standards.

[0045] In some implementations, UE 102, eNB 104 and / or gNB 105 may be configured to operate in accordance with 3GPP protocols, NR protocols and / or other protocols.

[0046] At operation 405, UE 102 may exchange signaling with gNB 105. Such signaling may include one or more messages. In some implementations, UE 102 and gNB 105 may exchange signaling multiple times. Such signaling may be exchanged multiple times throughout method 400. For example, UE 102 and gNB 105 may exchange signaling before operations 410-415. UE 102 and gNB 105 may exchange additional signaling after operations 410-415 and / or at another point in method 400.

[0047] In some implementations, one or more operations (including operations of the methods described herein 400, 500 and / or other methods) may be performed as part of a two-step random access (RA) procedure between UE 102 and gNB 105, but the scope of the implementations is not limited in this respect. Although some operations are described herein as part of a two-step RA procedure, it should be understood that in some implementations, one or more of these operations may be performed and may not necessarily be performed as part of a two-step RA procedure.

[0048] In some implementations, a two-step RA procedure may include an uplink MsgA message and a downlink MsgB message. It should be noted that the term "two-step RA procedure" is not limiting. It should be understood that one or more operations of the two-step RA procedure described herein may be associated with a procedure that does not include exactly two operations. For example, a two-step RA procedure may include two operations, more than two operations, or fewer than two operations. In some implementations, the implementation is also not limited to performing "steps," as one or more "operations" may be performed as part of a two-step RA procedure (and / or other processes and / or procedures).

[0049] Furthermore, the terms MsgA and MsgB are used in some descriptions herein, but it should be understood that the scope of the embodiments is not limited by such descriptions. In some embodiments, one or more similar messages, messages with different names, different messages, and / or other messages may be used.

[0050] Furthermore, it should be understood that in some embodiments, some of the messages described herein may be the same or similar. In one non-limiting example, in some embodiments, operations based on the MsgA message and / or portions thereof (such as the MsgA preamble and MsgA payload) may be the same or similar to operations associated with elements such as Msg1, the Msg1 message, the Msg1 preamble, the Msg1 payload, and / or other elements. In another non-limiting example, operations based on the MsgB message and / or portions thereof (such as the MsgB PDCCH, the MsgB preamble, the MsgB payload, and / or other elements) may be the same or similar to operations associated with elements such as Msg2, the Msg2 message, the Msg2PDCCH, the Msg2 preamble, the Msg2 payload, and / or other elements.

[0051] In some implementations, the MsgA message may include a MsgA preamble and a MsgA payload. The MsgA preamble and MsgA payload may be transmitted by UE 102. The MsgA preamble and MsgA payload may be received by gNB 105. In some implementations, the MsgA preamble and the corresponding MsgA payload may be transmitted within a random access opportunity (RO). In some implementations, the MsgA preamble may be transmitted within a random access opportunity (RO), and the MsgA payload may be transmitted within another opportunity linked to the random access opportunity (e.g., a Physical Uplink Shared Channel (PUSCH) opportunity, PO).

[0052] In some implementations, the MsgB message may include a MsgB PDCCH and a MsgB payload. The MsgB PDCCH and MsgB payload may be transmitted by gNB 105. The MsgB PDCCH and MsgB payload may be received by UE 102. In some implementations, the MsgB payload may be a Physical Downlink Shared Channel (PDSCH). In some implementations, the MsgB payload may include a PDSCH. In some implementations, the MsgB payload may be included in the PDSCH. In some implementations, the MsgB preamble and the corresponding MsgB payload may be transmitted within another RO. Implementations are not limited to the term "MsgB payload" as described herein. It should be understood that in some implementations, PDSCH, MsgB PDSCH, and / or other elements may be used. Implementations are not limited to the term "MsgB PDCCH" as described herein. It should be understood that in some implementations, PDCCH, MsgB preamble, and / or other elements may be used. For example, in some implementations, the MsgB message may include a MsgB preamble and a MsgB payload.

[0053] In some implementations, one or more elements may be transmitted and / or received in unlicensed spectrum, although the scope of the implementations is not limited in this respect. While the description of some operations herein may relate to the transmission and / or reception of some elements in unlicensed spectrum, it should be understood that in some implementations (e.g., licensed spectrum), one or more of those elements may be transmitted and / or received in spectrum that is not necessarily unlicensed spectrum.

[0054] In some implementations, signaling at operation 405 may include configuration information. In some implementations, the configuration information may be transmitted by gNB 105 and / or received by UE 102. In some implementations, the configuration information may be included in a System Information Block (SIB) (such as SIB1 and / or others) received from gNB 105. In some implementations, SIBs and / or other signaling may be broadcast by gNB 105, but the scope of the implementations is not limited in this respect. In some implementations, the configuration information may be included in dedicated signaling received from gNB 105. However, the implementations are not limited to the above, as in some implementations, the configuration information may be included in any suitable message / element.

[0055] In some implementations, the configuration information may indicate one or more of the following: resources allocated for the MsgA preamble; information related to the mapping between resources allocated for the MsgA preamble and resources allocated for the MsgA payload; information related to the type of multiplexing between resources allocated for the MsgA preamble and resources allocated for the MsgA payload; and / or others. In some implementations, resources (such as resources for the MsgA preamble, resources for the MsgA payload, resources for the MsgB PDCCH, resources for the MsgB payload, and / or other resources) may include time resources and / or frequency resources.

[0056] In some implementations, the configuration information may indicate one or more of the following: allocating resources (including but not limited to time-domain and frequency-domain resources) for the MsgA preamble; allocating resources (including but not limited to time-domain and frequency-domain resources) for the MsgA payload; the relationship between the resources for the MsgA preamble and the resources for the MsgA payload; the relationship between the number of transmissions of the MsgA preamble and the number of transmissions of the MsgA payload; and / or others. It should be noted that in some cases, the term "resources" in this description may be replaced by "radio resources." For example, resources may be radio resources or may include radio resources.

[0057] In some implementations, the signaling at operation 405 may include one or more of the following: Radio Resource Control (RRC) messages, Downlink Control Information (DCI), Physical Downlink Control Channel (PDCCH), and / or other elements. The information included in the signaling may include, but is not limited to, one or more of the following: configuration information for the two-step RA procedure; information relating to resources for the preamble of MsgA, the payload of MsgA, the PDCCH of MsgB, the payload of MsgB, and / or other resources; information relating to the number of transmissions of elements such as the preamble of MsgA, the payload of MsgA, the PDCCH of MsgB, the payload of MsgB, and / or others; one or more other elements described herein; and / or other elements.

[0058] At operation 410, UE 102 can determine the resources of the preamble of MsgA and / or the payload of MsgA. At operation 415, UE 102 can determine the resources of the PDCCH of MsgB and / or the payload of MsgB.

[0059] In some implementations, UE 102 may determine the resources allocated for the MsgA payload based on the resources allocated for the MsgA preamble and the mapping. In some implementations, the mapping may be related to the type of multiplexing between the resources allocated for the MsgA preamble and the resources allocated for the MsgA payload. In some implementations, UE 102 may determine the resources allocated for the MsgA payload based on the resources allocated for the MsgA preamble and the type of multiplexing. In some implementations, the type of multiplexing may be one of the following: Time Division Multiplexing (TDM); Frequency Division Multiplexing (FDM); a combination of TDM and FDM; and / or others. In some implementations, the mapping may be based on TDM, FDM, a combination of TDM and FDM; and / or others.

[0060] Any suitable arrangement of TDM, FDM, or a combination of TDM / FDM can be used. In a non-limiting example, if the mapping is based on TDM (and / or if the type of multiplexing is TDM), the resources of the MsgA preamble and the MsgA payload can be temporally continuous and can be in the same frequency range. In another non-limiting example, if the mapping is based on FDM (and / or if the type of multiplexing is FDM), the resources of the MsgA preamble and the MsgA payload can be in different frequency ranges and can be within the same time instance. In yet another non-limiting example, if the mapping is based on a combination of TDM and FDM (and / or if the type of multiplexing is a combination of TDM and FDM): the resources of the MsgA preamble and the MsgA payload can be temporally continuous and can be in different frequency ranges.

[0061] At operation 420, UE 102 may compete for the random access opportunity (RO). At operation 420, any suitable technology may be used, including but not limited to Listen-After-Speak (LBT).

[0062] At operation 425, UE 102 may transmit the preamble of MsgA. At operation 430, UE 102 may transmit the payload of MsgA. In some embodiments, UE 102 may transmit both the preamble of MsgA and the payload of MsgA in the same RO, but the scope of the embodiments is not limited in this respect.

[0063] In some implementations, UE 102 may perform one or more of the following: during the RO period obtained by UE 102, transmitting the MsgA preamble in the resources allocated for the MsgA preamble; during the RO period obtained by UE, transmitting the MsgA payload in the resources allocated for the MsgA preamble; and / or others.

[0064] In some implementations (including, but not limited to, implementations in which configuration information is included in the SIB and / or other broadcast signaling), UE 102 may perform one or more of the following: initiate a two-step RA procedure to initiate a Radio Resource Control (RRC) setup procedure, RRC recovery, RRC reconstruction, and / or others; encode the MsgA payload to include an RRC setup request message, an RRC recovery request message, an RRC reconstruction request message, and / or other RRC messages; and / or others.

[0065] In some implementations, configuration information may be included in dedicated signaling received from gNB 105 (including, but not limited to, dedicated signaling received from gNB 105 when UE 102 is operating in RRC connection mode). Examples of dedicated signaling may include, but are not limited to, RRC reconfiguration request messages, Media Access Control (MAC) control elements (CE), and Physical Downlink Control Channel (PDCCH).

[0066] In some implementations, configuration information may indicate the relationship or mapping between the radio resources of the MsgA preamble and the radio resources of the MsgA payload. In some implementations, the relationship may be one or more of the following: a radio resource pair for transmitting the MsgA payload applied to a radio resource for transmitting the MsgA preamble (i.e., a one-to-one mapping between radio resources for MsgA preamble transmission and radio resources for MsgA payload transmission); multiple radio resource pairs for transmitting the MsgA payload applied to a radio resource for transmitting the MsgA preamble (i.e., a one-to-many mapping between radio resources for MsgA preamble transmission and radio resources for MsgA payload transmission); multiple radio resource pairs for transmitting the MsgA payload applied to multiple radio resources for transmitting the MsgA preamble; a radio resource pair for transmitting the MsgA payload applied to multiple radio resources for transmitting the MsgA preamble (a many-to-one mapping between radio resources for MsgA preamble transmission and radio resources for MsgA payload transmission); and / or others. In some implementations, this relationship or mapping may be related to the number of times the MsgA preamble is transmitted and the number of times the MsgA payload is transmitted.

[0067] At operation 435, UE 102 can receive the PDCCH of MsgB. At operation 440, UE 102 can receive the payload of MsgB.

[0068] For clarity in the following discussion, the RO obtained by UE 102 is referred to as, but not limited to, the first RO. UE 102 may perform one or more of the following: transmit the MsgA preamble and / or MsgA payload during the first RO; detect the MsgB PDCCH during the second RO obtained by gNB 105; determine the timing synchronization of the MsgB payload based on the detection of the MsgB PDCCH and / or other PDCCHs; decode the MsgB payload, wherein the MsgB payload may be received during the second RO based on the determined timing synchronization; and / or others.

[0069] It should be noted that the description herein may relate to the transmission / reception of elements (such as the MsgA preamble, MsgA payload, MsgB PDCCH, MsgB payload, and / or others) during RO, but the scope of the embodiments is not limited in this respect. It should be understood that in some embodiments, one or more elements (including but not limited to the MsgA preamble, MsgA payload, MsgB PDCCH, and MsgB payload) may be transmitted / received, and may not necessarily be transmitted / received within RO.

[0070] In some implementations, the configuration information may indicate the allocation of resources for the MsgB PDCCH. In some implementations, the configuration information may indicate the allocation of resources for the MsgB payload.

[0071] In some implementations, UE 102 may determine the resources allocated for the MsgB payload based on the Random Access Radio Network Temporary Identifier (RA-RNTI) of the downlink control information (DCI) in the MsgB PDCCH.

[0072] In some implementations, the MsgB payload may include one or more of the following: an RRC setup response message, an RRC recovery response message, an RRC reconstruction response message, another RRC message, one or more other messages, one or more other elements, and / or others.

[0073] In some implementations, configuration information may indicate a relationship or mapping between time-domain and / or frequency-domain resources of the MsgA preamble transmission and time-domain and / or frequency-domain resources of the MsgA payload transmission, wherein the relationship is in one or more of the following: one time resource and / or frequency resource of the MsgA payload transmission corresponds to one time resource and / or frequency resource of the MsgA preamble transmission; multiple time resources and / or frequency resources of the MsgA payload transmission correspond to one time resource and / or frequency resource of the MsgA preamble transmission; one time resource and / or frequency resource of the MsgA payload transmission corresponds to multiple time resources and / or frequency resources of the MsgA preamble transmission; and / or others.

[0074] In some implementations, UE 102 may receive the MsgB PDCCH from gNB 105. UE 102 may determine the allocation of time and frequency resources for the MsgB payload based on the reception of the MsgB PDCCH. UE 102 may receive the MsgB payload based on the determined time and frequency resources for the MsgB payload.

[0075] In some implementations, configuration information may indicate the allocation of resources for the MsgB PDCCH. UE 102 may determine the allocation of resources for the MsgB payload based on the Random Access Radio Network Temporary Identifier (RA-RNTI) of the downlink control information (DCI) in the MsgB PDCCH.

[0076] At operation 505, gNB 105 can exchange signaling with UE 102. At operation 510, gNB 105 can determine the resources for the preamble and / or payload of MsgA. At operation 515, gNB 105 can determine the resources for the PDCCH of MsgB and / or the payload of MsgB. At operation 520, gNB 105 can receive the preamble of MsgA. At operation 525, gNB 105 can receive the payload of MsgA. At operation 530, gNB 105 can contend for RO. At operation 535, gNB 105 can transmit the PDCCH of MsgB. At operation 540, gNB 105 can transmit the payload of MsgB.

[0077] In some implementations, gNB 105 may allocate resources for the MsgA preamble of uplink MsgA messages and resources for the MsgA payload of MsgA messages. MsgA messages may be included in a two-step random access (RA) process, but the scope of the implementation is not limited in this respect. In some implementations, the two-step RA process may also include downlink MsgB messages. In some implementations, MsgB messages may include MsgB PDCCH and MsgB payload. In some implementations, gNB 105 may transmit signaling indicating one or more of the following: allocating resources for the MsgA preamble, allocating resources for the MsgA payload, and / or others. In some implementations, signaling may include one or more of the following: broadcast signaling, System Information Block (SIB), dedicated signaling, and / or others.

[0078] In some implementations, gNB 105 may perform one or more of the following: during a first RO, detecting the MsgA preamble in the resources allocated for the MsgA preamble; determining a synchronization timing for receiving the MsgA payload based on the detection of the MsgA preamble and / or other parameters; during the first RO and according to the synchronization timing, detecting the MsgA preamble in the resources allocated for the MsgA payload; competing for a second RO; transmitting the MsgB PDCCH and the MsgB payload in the second RO; and / or other parameters.

[0079] In some implementations, gNB 105 may allocate resources for the MsgA preamble and resources for the MsgA payload according to the type of multiplexing. Non-limiting examples of multiplexing types may include, but are not limited to: TDM, FDM, combinations of TDM and FDM, and / or others.

[0080] This summary is provided to comply with Section 1.72(b) of Title 37 of the Federal Regulations, which requires a summary of the specification to enable the reader to determine the nature and purpose of the technical disclosure. It is understood that understanding the summary will not be used to limit or interpret the scope or meaning of the claims. Accordingly, the following claims are incorporated into the detailed description, wherein each claim exists independently as a separate embodiment.

Claims

1. A method for wireless communication, comprising: transmitting configuration information related to a two-step random access (RA) procedure between a user equipment (UE) and a base station, wherein the two-step RA procedure comprises: an uplink MsgA message comprising a MsgA preamble and a MsgA payload, and a downlink MsgB message comprising a MsgB physical downlink control channel (PDCCH) and a MsgB payload, wherein the configuration information indicates: resources allocated for MsgA preamble transmission, and information related to a mapping between the resources allocated for the MsgA preamble transmission and resources allocated for MsgA payload transmission, wherein the mapping specifies one resource for the MsgA payload for each multiple of resources used to transmit the MsgA preamble, and wherein the resources allocated for MsgA payload transmission comprise multiple frequency-multiplexed resources; receiving the MsgA preamble transmission from the UE in a resource for the MsgA preamble within the resources allocated for the MsgA preamble transmission; determining a related resource for the MsgA payload based on the resources allocated for the MsgA preamble transmission and the mapping; and receiving the MsgA payload from the UE for transmission in the resource determined for the MsgA payload.

2. The method of claim 1, wherein the mapping is based on time-division multiplexing (TDM), frequency-division multiplexing (FDM), or a combination of TDM and FDM.

3. The method of claim 2, wherein: if the mapping is based on TDM: the resources allocated for the MsgA preamble transmission and the resources allocated for the MsgA payload transmission are consecutive in time and within the same frequency range, if the mapping is based on FDM: the resources allocated for the MsgA preamble transmission and the resources allocated for the MsgA payload transmission are within different frequency ranges and in the same time instance, and if the mapping is based on the combination of TDM and FDM: the resources allocated for the MsgA preamble transmission and the resources allocated for the MsgA payload transmission are consecutive in time and within different frequency ranges.

4. The method of claim 1, wherein: the resources allocated for the MsgA preamble transmission comprise time resources and / or frequency resources, the resources allocated for the MsgA payload transmission comprise time resources and / or frequency resources.

5. The method of claim 1, wherein the configuration information is included in a system information block (SIB).

6. The method of claim 1, the MsgA payload comprising a radio resource control (RRC) setup request message, a RRC resume request message, or a RRC reestablishment request message.

7. The method of claim 1, wherein the configuration information is included in dedicated signaling when the UE is operating in a radio resource control (RRC) connected mode.

8. The method of claim 7, wherein the dedicated signaling comprises one or more of: an RRC reconfiguration request message, a medium access control (MAC) control element (CE), and a physical downlink control channel (PDCCH).

9. The method of claim 1, wherein a MsgB payload is transmitted based on an allocation of time resources and frequency resources of the MsgB payload.

10. A method for wireless communication, comprising: receiving configuration information related to a two-step random access (RA) procedure between a user equipment (UE) and a base station, wherein the two-step RA procedure comprises: an uplink MsgA message comprising a MsgA preamble and a MsgA payload, and a downlink MsgB message comprising a MsgB physical downlink control channel (PDCCH) and a MsgB payload, wherein the configuration information indicates: resources allocated for MsgA preamble transmission, and information related to a mapping between the resources allocated for the MsgA preamble transmission and resources allocated for MsgA payload transmission, wherein the mapping specifies one resource for the MsgA payload for each multiple of resources used to transmit the MsgA preamble, and wherein the resources allocated for MsgA payload transmission comprise a plurality of frequency multiplexed resources; transmitting, to the base station, the MsgA preamble transmission in a resource for the MsgA preamble within the resources allocated for the MsgA preamble transmission; determining a related resource for the MsgA payload based on the resources allocated for the MsgA preamble transmission and the mapping; and transmitting, to the base station, the MsgA payload for transmission in the resource determined for the MsgA payload.

11. The method of claim 10, wherein the mapping is based on time division multiplexing (TDM), frequency division multiplexing (FDM), or a combination of TDM and FDM.

12. The method of claim 11, wherein: if the mapping is based on TDM: the resources allocated for the MsgA preamble transmission and the resources allocated for the MsgA payload transmission are contiguous in time and within a same frequency range, if the mapping is based on FDM: the resources allocated for the MsgA preamble transmission and the resources allocated for the MsgA payload transmission are within different frequency ranges and in a same time instance, and if the mapping is based on the combination of TDM and FDM: the resources allocated for the MsgA preamble transmission and the resources allocated for the MsgA payload transmission are contiguous in time and within different frequency ranges.

13. The method of claim 10, wherein: the resources allocated for the MsgA preamble transmission comprise time resources and / or frequency resources, the resources allocated for the MsgA payload transmission comprise time resources and / or frequency resources.

14. The method of claim 10, wherein the configuration information is included in a system information block (SIB).

15. The method of claim 10, the MsgA payload comprises a radio resource control (RRC) setup request message, a RRC resume request message, or a RRC reestablishment request message.

16. The method of claim 10, wherein the configuration information is included in dedicated signaling when the UE is operating in a radio resource control (RRC) connected mode.

17. The method of claim 16, wherein the dedicated signaling comprises one or more of: a RRC reconfiguration request message, a medium access control (MAC) control element (CE), and a physical downlink control channel (PDCCH).

18. The method of claim 10, wherein a MsgB payload is transmitted based on an allocation of time resources and frequency resources of the MsgB payload.

19. An apparatus, the apparatus comprising a processor configured to cause a user equipment to implement a method according to any of claims 10-18.

20. The apparatus of claim 19, further comprising a radio operatively coupled to the processor.

Images