Control Information Configuration in Wireless Communication

Abstract

A wireless communication method is provided, including: sending, by a user equipment, a first message to a network device in a wireless network to initiate a two-step random access to the wireless network; and receiving a second message to perform the two-step random access in response to the first message, where the second message includes a field indicating whether a transport block size of a payload of the second message is scaled.

Description

Technical Field

[0001] This patent application relates generally to systems, devices, and techniques for wireless communications. Background Art

[0002] Wireless communication technology is driving the world towards an increasingly connected and networked society. The rapid growth of wireless communications and technological advances have led to greater demands for capacity and connectivity. Other aspects such as energy consumption, equipment cost, spectrum efficiency, and latency are also important to meet the needs of various communication scenarios. Compared with existing wireless networks, next-generation systems and wireless communication technologies need to support an increasing number of users and devices. Summary of the invention

[0003] The present application relates to methods, systems and devices for configuring control information in wireless communications.

[0004] In one aspect, a wireless communication method is disclosed. The wireless communication method provided includes: a user equipment sends a first message to a network device in a wireless network to initiate a 2-step random access to the wireless network; and a second message is received in response to the first message to perform the 2-step random access, the second message including a field indicating whether the transport block size of the payload of the second message is scaled.

[0005] In another aspect, a wireless communication method is disclosed. The provided wireless communication method includes: receiving, by a network device, a first message from a user device in a wireless network to initiate a 2-step random access to the wireless network; and sending a second message in response to the first message to perform the 2-step random access, the second message including a field indicating whether a transport block size of a payload of the second message is scaled.

[0006] In another aspect, a wireless communication device is disclosed that includes a processor configured to perform the disclosed method.

[0007] In another aspect, a computer readable medium having code stored thereon is disclosed. When executed by a processor, the code causes the processor to perform the methods described in this application.

[0008] These and other features are described throughout this application. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 An example of wireless communication including a base station (BS) and a user equipment (UE) based on some embodiments of the disclosed technology is shown.

[0010] Figure 2 An example of a block diagram of a portion of an apparatus in accordance with some embodiments of the disclosed technology is shown.

[0011] Figure 3 A 4-step random access process based on contention conflict between a user equipment and a communication node on the network side is shown.

[0012] Figure 4 An example of a two-step random access procedure between a user equipment and a network-side communication node is shown.

[0013] Figure 5 An example of contents included in msgB PDSCH is shown.

[0014] Figure 6 An example of a MAC (Medium Access Control) structure of msgB PDSCH is shown.

[0015] Figure 7 An example of a table illustrating the DCI (Downlink Control Information) format is shown.

[0016] Figure 8 An example of a SuccessRAR structure included in msgB PDSCH is shown.

[0017] Fig. 9 An example of a table illustrating a DCI format is shown.

[0018] Fig.10 and 11 An example flow chart of a wireless communication method based on some embodiments of the disclosed technology is shown. DETAILED DESCRIPTION

[0019] The disclosed technology provides implementations and examples of control information configuration in wireless communications. In some implementations, the proposed control information configuration can enable a two-step random access procedure between a user device and a network device. Although 5G terminology is used in some cases to facilitate understanding of the disclosed technology, the disclosed technology can be applied to wireless systems and devices using communication protocols other than 5G or 3GPP protocols.

[0020] In the fifth generation (5G) new radio (NR) mobile network, before the user equipment (UE) can send data to the base station (BS), the user equipment (UE) needs to obtain uplink timing synchronization and downlink timing synchronization with the base station (BS). Uplink timing synchronization can be obtained by performing a random access procedure (RACH). The random access procedure is provided to meet the needs of faster and more efficient communication. The present application proposes various configuration schemes for downlink control information in wireless communication.

[0021] Figure 1An example of a wireless communication system (e.g., a 5G or NR cellular network) including a BS 120 and one or more user equipment (UE) 111, 112, and 113 is shown. In some embodiments, the UE uses an implementation (131, 132, 133) of the disclosed technology to access the BS (e.g., a network), and the disclosed technology then enables subsequent communication (141, 142, 143) from the BS to the UE. The UE can be, for example, a smartphone, a tablet, a mobile computer, a machine-to-machine (M2M) device, an Internet of Things (IoT) device, etc. Although Figure 1 BS 102 is shown, but other network-side communication nodes may be implemented to communicate with the UE. For example, the network-side communication node or BS 102 may include a Node B, an E-UTRA Node B (also referred to as an evolved Node B, eNodeB, or eNB), a gNodeB in a new radio (NR) technology (also referred to as a gNB), a micro station, a femto station, or others.

[0022] Figure 2 An example of a block diagram representation of a portion of an apparatus is shown. An apparatus 210, such as a base station or a wireless device (or UE), may include a processor electronic device 220, such as a microprocessor that implements one or more techniques presented in this application. The apparatus 210 may include a transceiver electronic device 230 to send and / or receive wireless signals through one or more communication interfaces such as an antenna 240. The apparatus 210 may include other communication interfaces for sending and receiving data. The apparatus 210 may include one or more memories (not explicitly shown) that are configured to store information such as data and / or instructions. In some embodiments, the processor electronic device 220 may include at least a portion of the transceiver electronic device 230. In some embodiments, at least some of the disclosed techniques, modules, or functions are implemented using the apparatus 210.

[0023] The traditional contention-based RACH procedure for NR is 4-step RACH. Figure 3 A 4-step random access process based on contention conflict between a UE and a communication node (e.g., eNode B) on the network side is shown. In the first step, the UE sends a RACH preamble (msg1) to the network device. In the second step, in response to the RACH preamble, the network device sends a random access response (msg2). In the third step, the UE sends a Layer 2 / Layer 3 (L2 / L3) message (msg3) to the network. In the fourth step, the network sends a contention conflict resolution message (msg4) to the UE. Since the traditional contention conflict-based RACH process requires four steps, delay may become a problem. Therefore, the two-step RACH, which can significantly reduce the overall initial access delay, has recently received increasing attention.

[0024] Figure 4 An example of a two-step RACH procedure between a UE and a network-side communication node (e.g., a gNB) is shown. At the first step of the two-step RACH procedure, a first message (msgA) is sent from the UE to the gNB. At the second step of the two-step RACH procedure, a second message (msgB) is sent from the gNB to the UE. The msgA of the two-step RACH combines the contents of msg1 and msg3 of the 4-step RACH based on contention conflict, while the msgB of the two-step RACH combines the contents of msg2 and msg4 of the 4-step RACH based on contention conflict. The channel structure of msgA corresponds to a preamble with a PUSCH (physical uplink shared channel) carrying a payload that includes at least the contents of msg3 in the conventional 4-step RACH. In some embodiments, the payload may include a contention conflict resolution ID, and the other payloads are in an idle or inactive mode. In some embodiments, the payload may include at least a C-RNTI (cell-radio network temporary identifier) ​​of the UE in connected mode. The content of msgB may include the content of msg2 and msg4 of 4-step RACH based on contention conflict, and msgB is configured to process the contention conflict resolution function for 2-step RACH.

[0025] In some embodiments, during the two-step RACH, the gNB transmits msgB including the physical downlink control channel (PDCCH) and the physical downlink shared channel (PDSCH). The msgB PDSCH may be scheduled by the DCI (downlink control information) of the msgB PDCCH. The msgB PDCCH and msgB PDSCH are PDCCH and PDSCH associated with msgB. The msgB PDCCH is addressed or associated with the msgB Radio Network Temporary Identifier (msgB-RNTI) or with the C-RNTI of the UE (which has transmitted msgA in the first step of the two-step RACH). In some embodiments, the msgB PDCCH is scrambled by the msgB-RNTI or the C-RNTI. The msgB-RNTI may be a random access RNTI (RA-RNTI) or a new RNTI separated from the traditional message 2 RA-RNTI. If the preamble in msgA is detected by the gNB, then MsgB will be sent from the gNB to the UE. The content of msgB embedded in msgB PDSCH may vary depending on whether the payload in msgA has been successfully decoded.

[0026] msgB PDSCH may include three functional elements: "SuccessRAR", "FallbackRAR" or "Backoff Indicator (BI)". SuccessRAR is a random access response after msgA PUSCH is successfully received and decoded by the base station. FallbackRAR is a random access response after the preamble sequence in msgA is successfully received by the base station but the PUSCH fails to be decoded by the base station. The backoff indicator is a general backoff indication with the same function as the LTE backoff indicator. Figure 5 An example of what is included in the msgB PDSCH is shown, which includes a Success RAR, a Fallback RAR, and a Backoff Indicator. For the case where both the msgA preamble and the payload are successfully detected and decoded, the SuccessRAR in msgB may include the Contention Conflict Resolution ID sent in msgA, the C-RNTI assigned to the UE, or a TA command. For the case where the preamble is successfully detected but the payload in the PUSCH is not successfully decoded, the RACH process will fall back to the traditional 4-step RACH. The FallbackRAR may be the same as the traditional msg2, which includes three fields: TC-RNTI, UL authorization, and TA command. Alternatively, in addition to the previous three fields, RAPID will be added to the FallbackRAR. In the traditional 4-step RACH, RAPID (Random Access Preamble Identifier) ​​is included in the msg2 MAC subheader.

[0027] msgB PDSCH may contain SuccessRAR, FallbackRAR or backoff indicator at the same time, or any combination of the three functional elements. Figure 6 An example of the MAC (Media Access Control) PDU (Protocol Data Unit) structure of msgB PDSCH is shown. Figure 6 In the embodiment, the MAC PDU includes multiple MAC sub-PDUs (eg, MACsubPDU 1 to MACsubPDU n+1), which carry different types of MAC sub-headers and / or different types of MAC RARs (SuccessRAR or FallbackRAR). Figure 6 Only an example is shown, and thus the order and content of the msgB PDSCH are not limited to this example. In some embodiments, for multiple UEs, there may be multiple multiplexed successRARs in one msgB. And a FallbackRAR for one or a group of UEs identified by the same msgB RA-RNTI may also be included. The backoff indicator may be carried in the MAC subheader.

[0028] A HARQ (Hybrid Automatic Repeat Request)-ACK feedback is required for the UE to receive the SuccessRAR in msgB to indicate that the SuccessRAR has been successfully received by the corresponding UE identified by the contention resolution ID. When the HARQ-ACK is received by the gNB, the gNB will not retransmit msgB for the UE that feedbacks the ACK.

[0029] The UE needs to feedback ACK by using PUCCH resources. In addition to some configurations in the system information, PUCCH-related resources can also be indicated by msgB PDCCH or msgB PDSCH. DCI format 1-0 used for scheduling PDSCH can be reused for msgB PDCCH. The CRC (cyclic redundancy check) carried by the DCI in DCI format 1-0 of msg2 for the traditional 4-step RACH is scrambled by RA-RNTI, while the DCI in DCI format 1-0 of msg4 for the traditional 4-step RACH is scrambled by TC-RNTI or C-RNTI. The supported DCI carried by DCI format 1-0 scrambled by different RNTIs is as follows: Figure 7 As shown in the table.

[0030] Figure 7 Four different DCI formats are shown, scrambled by RA-RNTI, TC-RNTI, msgB-RNTI and C-RNTI respectively. Figure 7 Among the four DCI formats shown, the DCI format using msgB-RNTI scrambling is used to implement the 2-step random access suggested in some embodiments of the disclosed technology. Figure 7 In the DCI format scrambled by msgB-RNTI, the concept of reinterpretation is used to explain the DCI format scrambled by RA-RNTI, TC-RNTI and C-RNTI compared to the interpretation of the corresponding fields in the DCI format scrambled by RA-RNTI, TC-RNTI and C-RNTI. Figure 7It can be observed that the DCI format 1_0 with CRC scrambled by TC-RNTI or C-RNTI has fields for PUCCH resource indication, such as: PUCCH resource indicator, TPC command for scheduled PUCCH, PDSCH-to-HARQ_feedback timing indicator, and fields for HARQ indication for downlink msgB, such as: new data indicator, redundancy version, HARQ process number. These two fields need to be used for PUCCH transmission and msgB retransmission. Therefore, msgB PDCCH DCI preferably reuses all fields in DCI format 1-0 CRC scrambled by TC-RNTI or C-RNTI, but the CRC scrambling sequence is replaced by msgB-RNTI. In addition, for the msgB PDCCH DCI format, some revisions or additions may be required based on the fields in DCI format 1-0 CRC scrambled by TC-RNTI or C-RNTI.

[0031] For the case of msgA sent in PUSCH using C-RNTI, the DCI format 1-0 CRC scrambled by C-RNTI for 2-step RACH msgBPDCCH is valid in the case of msgA sent in PUSCH with C-RNTI. If msgA is sent in PUSCH using contention resolution ID, the msgB PDCCH DCI can be modified based on the DCI format 1-0 CRC scrambled by TC-RNTI.

[0032] As mentioned above, in some embodiments, for multiple UEs, there may be multiple multiplexed SuccessRARs in one msgB. And the HARQ-ACK feedback for receiving the SuccessRAR carried in the PUCCH is required. The "TPC command for scheduled PUCCH" field in the DCI format 1-0 CRC scrambled by the TC-RNTI may be used only for one UE TPC command indication, rather than for multiple UEs. The total number of bits in the DCI is limited and is not allowed to be changed for backward compatibility reasons, so a better way to indicate the PUCCH TPC command for multiple UEs is to include a 2-bit TPC command for each UE in the content of the successRAR for each specific UE. For example, in Figure 8 In the successRAR structure, 2 bits are provided for "TPC command for scheduled PUCCH". The 2 bits of "TPC command for scheduled PUCCH" in the DCI format 1-0 CRC scrambled by msgB-RNTI may be reserved or left blank.

[0033] from Figure 7It can also be observed that the TB scaling field in the DCI format 1-0 CRC scrambled by RA-RNTI does not exist in the DCI format 1-0 CRC scrambled by msgB-RNTI (or TC-RNTI). TB scaling is an important parameter of the downlink initial access message. TB scaling is configured to scale the transport block (TB) size of the downlink payload of the initial access message for the purpose of reducing the code rate and improving the robustness of downlink signaling reception. It would be very beneficial to include this TB scaling information as DCI information for msgB. In some embodiments, the TB scaling information includes i) whether the TB size of the payload of msgB is scaled. In some embodiments, the TB scaling information also includes how to scale msgB, such as a scaling factor. A typical TB scaling factor can be set so that 00 represents 100%, 01 represents 50%, and 10 represents 25%.

[0034] To include TB scaling information, some reserved bits or empty bits in the DCI format 1-0 CRC scrambled by msgB-RNTI for msgB can be reinterpreted as a TB scaling field. As an example, Figure 7 The table shown shows that the reserved 2 bits for "downlink allocation index" or the reserved bits "TP command for scheduled PUCCH" can be reinterpreted as a TB scaling field. When the structure of the DCI format 1-0 CRC scrambled by msgB-RNTI (e.g., the fields with specific functions in the DCI format and the value range of each field) is modified according to the structure of the legacy format, the corresponding fields in the DCI format 1-0 CRC scrambled by msgB-RNTI, such as "downlink allocation index" or the reserved bits "TP command for scheduled PUCCH" are reserved. In this case, the reserved bits in the corresponding fields can be reinterpreted as a TB scaling field. In some embodiments, when the structure of the DCI format 1-0 CRC scrambled by msgB-RNTI is the same as that of the legacy format, the corresponding fields in the DCI format 1-0 CRC scrambled by msgB-RNTI, such as "downlink allocation index" or the reserved bits "TP command for scheduled PUCCH" are not reserved. In this case, the reserved bits in the corresponding field may be reinterpreted as the TB scaling field. "Downlink Allocation Index" was originally a counter for DAI (Downlink Allocation Index), but is not really used in the DCI format 1-0 CRC scrambled by msgB-RNTI.

[0035] If the "TPC command for scheduled PUCCH" of each UE is indicated in the successRAR of each UE, the 2 bits of the TPC command for scheduled PUCCH in the DCI may be reserved and reinterpreted as a TB scaling field.

[0036] In the case where the successRAR in msgB is transmitted using SRB (Signaling Radio Bearer) data, multiplexing of the successRARs of multiple UEs in msgB is not allowed. In this case, the "TPC command for the scheduled PUCCH" in the DCI information can be maintained in the DCI and does not need to be retained.

[0037] If the successRAR in msgB is sent without SRB data, multiplexing of the successRARs of multiple UEs in msgB is allowed. In this case, the "TPC command for scheduled PUCCH" in the DCI can be retained or saved in the DCI information. If this field is saved in the DCI, it is not mandatory to provide the "TPC command for scheduled PUCCH" in all successRARs in one msgB. The "TPC command for scheduled PUCCH" of at least one UE is provided in the DCI, while the other "TPC command for scheduled PUCCH" is provided in the successRAR.

[0038] Fig. 9 An example of a table illustrating a DCI format is shown. Figure 7 Compared with the table in Figure 7 For DCI formats with CRC scrambled by msgB-RNTI, some fields are reinterpreted. Fig. 9 The DCI format shown in shows the final field included in the DCI format, where the CRC is scrambled by msgB-RNTI. Fig. 9In the DCI format 1_0 with a CRC scrambled by msgB-RNTI, the structure includes an identifier of the DCI format, frequency domain resource allocation, time domain resource allocation, VRB to PRB mapping, modulation and coding scheme, and TB scaling. Other fields such as new data indicator, redundancy version, HARQ process number, TPC command for scheduled PUCCH, PUCCH resource indicator, PDSCH-to-HARQ_feedback timing indicator can be optionally included in the structure or retained in the structure. The structure of the DCI format refers to the fields with specific functions in the DCI format and the number of bits in each field. The order or sequence of each field is not included in the definition of the structure and can therefore be changed in various ways. The downlink allocation index is not used for DCI format 1_0 with a CRC scrambled by msgB-RNTI. In some embodiments, the same payload size as other traditional DCI formats 1_0 can be maintained in the DCI format.

[0039] Fig.10 An example of a wireless communication scheme based on some embodiments of the disclosed technology is shown. In step 1010, the method includes: a user device sends a first message to a network device in a wireless network to initiate a 2-step random access to the wireless network. In step 1020, the method includes: receiving a second message in response to the first message to perform a 2-step random access, the second message including a field indicating whether a transport block size of a payload of the second message is scaled.

[0040] Fig.11 Another example of a wireless communication scheme based on some embodiments of the disclosed technology is shown. In step 1110, the method includes: receiving, by a network device, a first message from a user device in a wireless network to initiate a 2-step random access to the wireless network. In step 1120, the method includes: sending a second message in response to the first message to perform a 2-step random access, the second message including a field indicating whether a transport block size of a payload of the second message is scaled.

[0041]

[0046] Additional features of the above-described methods / techniques that may preferably be implemented in some embodiments are described below using a clause-based description format.

[0042] 1. A wireless communication method, comprising: a user equipment sends a first message to a network device in a wireless network to initiate a 2-step random access to the wireless network; and receiving a second message in response to the first message to perform the 2-step random access, the second message including a field indicating whether the transport block size of the payload of the second message is scaled. The network device may include Figure 1 BS 120 is shown, and user equipment may include Figure 1 In some embodiments, Figure 4 A 2-step random access to a wireless network is shown. Figure 7-9 An example of a field indicating whether the transport block size of the payload of the second message is scaled is discussed.

[0043] 2. The wireless communication method according to clause 1, wherein the field is located at a position in the second message that includes a reserved bit or a null bit in a conventional format.

[0044] 3. The wireless communication method of clause 1, wherein the field further indicates a scaling factor of the second message.

[0045] 4. The wireless communication method of clause 1, wherein the second message is scrambled by a first identifier specific to the second message.

[0046] 5. A wireless communication method according to clause 2, wherein the second message includes downlink control information having a structure different from a conventional format.

[0047] 6. A wireless communication method according to clause 2, wherein the second message includes downlink control information having the same structure as a legacy format.

[0048] 7. A wireless communication method according to clause 4, wherein the first identifier is a msgB-RNTI (Radio Network Temporary Identifier).

[0049] 8. A wireless communication method according to clause 5 or clause 6, wherein the legacy format is scrambled by RA (Random Access)-RNTI, TC (Temporary Cell)-RNTI or C (Cell)-RNTI.

[0050] 9. A wireless communication method according to clause 1, wherein the second message includes a PDCCH (Physical Downlink Control Channel) and a PDSCH (Physical Downlink Shared Channel).

[0051] 10. A wireless communication method according to clause 9, wherein the PDSCH includes at least one of the following: a first element corresponding to a response to receiving a PUSCH (Physical Uplink Shared Channel) included in the first message and successfully decoding the PUSCH, a second element corresponding to a response to receiving a preamble sequence in the first message but not successfully decoding the PUSCH, or a third element corresponding to a backoff indication.

[0052] 11. A wireless communication method according to clause 10, wherein the first element comprises at least one of: a contention resolution ID, a C-RNTI allocated to the user equipment, or a TA (timing advance) command.

[0053] 12. A wireless communication method according to clause 10, wherein the second element comprises at least one of: a preamble identifier, a TC_RNTI, a UL (uplink) grant or a TA command.

[0054] 13. A wireless communication method according to clause 10, wherein the PDSCH includes a MAC structure, and the MAC structure includes multiple MAC sub-PDUs.

[0055] 14. A wireless communication method, comprising: receiving, by a network device, a first message from a user equipment in a wireless network to initiate a 2-step random access to the wireless network; and sending, in response to the first message, a second message to perform the 2-step random access, the second message including a field indicating whether a transport block size of a payload of the second message is scaled. The network device may include Figure 1 BS 120 is shown, and user equipment may include Figure 1 In some embodiments, a 2-step random access to a wireless network is performed as follows: Figure 4 Reference Figure 7-9 An example of a field indicating whether the transport block size of the payload of the second message is scaled is discussed.

[0056] 15. A wireless communication method according to clause 14, wherein the field is located at a position in the second message that contains reserved bits or null bits for a legacy format.

[0057] 16. A wireless communication method according to clause 14, wherein the field further indicates a scaling factor of the second message.

[0058] 17. A method of wireless communication as described in clause 14, wherein the second message is scrambled by a first identifier specific to the second message.

[0059] 18. A method of wireless communication as described in clause 15, wherein the second message includes downlink control information having a structure different from a legacy format.

[0060] 19. A wireless communication method according to clause 15, wherein the second message comprises downlink control information having the same structure as a legacy format.

[0061] 20. A wireless communication method according to clause 17, wherein the first identifier is a msgB-RNTI (Radio Network Temporary Identifier).

[0062] 21. A wireless communication method according to clause 18 or clause 19, wherein the legacy format is scrambled by RA (Random Access)-RNTI, TC (Temporary Cell)-RNTI or C (Cell)-RNTI.

[0063] 22. A wireless communication method according to clause 14, wherein the second message comprises a PDCCH (Physical Downlink Control Channel) and a PDSCH (Physical Downlink Shared Channel).

[0064] 23. A wireless communication method according to clause 22, wherein the PDSCH includes at least one of the following: a first element corresponding to a response to receiving a PUSCH (Physical Uplink Shared Channel) included in the first message and successfully decoding the PUSCH, a second element corresponding to a response to receiving a preamble sequence in the first message but not successfully decoding the PUSCH, or a third element corresponding to a backoff indication.

[0065] 24. A wireless communication method according to clause 23, wherein the first element comprises at least one of: a contention resolution ID, a C-RNTI allocated to the user equipment, or a TA (timing advance) command.

[0066] 25. A wireless communication method according to clause 23, wherein the second element comprises at least one of: a preamble identifier, a TC_RNTI, a UL (uplink) grant or a TA command.

[0067] 26. A wireless communication method according to clause 23, wherein the PDSCH includes a MAC structure, and the MAC structure includes multiple MAC sub-PDUs.

[0068] 27. A communications device comprising a processor configured to implement a method according to any one or more of clauses 1 to 26.

[0069] 28. A computer readable medium having stored thereon code which, when executed, causes a processor to implement the method according to any one or more of clauses 1 to 26.

[0070] This manual together with the attached Figure 1 The present invention is to be considered as exemplary, where exemplary means example and does not imply an ideal or preferred embodiment unless otherwise specified. As used herein, the use of "or" is intended to include "and / or" unless the context clearly indicates otherwise.

[0071] Some embodiments described herein are described in the general context of methods or processes, which may be implemented in one embodiment by a computer program product embodied in a computer-readable medium, including computer executable instructions such as program code executed by a computer in a networked environment. Computer-readable media may include removable and non-removable storage devices, including but not limited to read-only memory (ROM), random access memory (RAM), compact disk (CD), digital versatile disk (DVD), etc. Therefore, computer-readable media may include non-transitory storage media. In general, program modules may include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. Computer or processor executable instructions, associated data structures, and program modules represent examples of program codes for executing the steps of the methods disclosed herein. A specific sequence of such executable instructions or associated data structures represents an example of corresponding behavior for implementing the functions described in these steps or processes.

[0072] In some disclosed embodiments, a device or module of hardware circuit, software or a combination thereof can be used to implement. For example, a hardware circuit implementation may include discrete analog and / or digital components, which are, for example, integrated as a part of a printed circuit board. Alternatively or additionally, the disclosed components or modules may be implemented as application specific integrated circuits (ASICs) and / or field programmable gate arrays (FPGAs) devices. Some embodiments additionally or alternatively include a digital signal processor (DSP), which is a dedicated microprocessor with an architecture optimized for the operational requirements of digital signal processing related to the functions disclosed in the present application. Similarly, various components or subcomponents within each module may be implemented in software, hardware or firmware. The connection between the modules and / or the components within the modules may be provided using any of the connection methods and media known in the art, including but not limited to communication using appropriate protocols over the Internet, wired or wireless networks.

[0073] Although the present application contains many details, these details should not be interpreted as limitations on the scope of the claimed invention or the content that can be claimed, but should be interpreted as descriptions of specific features of specific embodiments. Certain features described herein in the context of separate embodiments may also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments. In addition, although the above-mentioned features may be described as working in a specific combination, and even initially required to be so, one or more features from the required combination may be cut out from the required combination in some cases, and the required combination may be directed to a sub-combination or a change in a sub-combination. Similarly, although operations are described in a specific order in the accompanying drawings, this should not be understood as requiring these operations to be performed in the specific order or sequential order shown, or requiring the execution of all described operations to implement the desired result.

[0074] Only some implementations and examples are described herein, and other implementations, improvements and variations may be made based on what is described and illustrated in this disclosure.

Claims

1. A wireless communication method, comprising: sending, by a user equipment, a first message msgA to a network device in a wireless network to initiate a two-step random access to the wireless network; and receiving, in response to the first message, a second message msgB to perform the two-step random access, the second message including a physical downlink shared channel PDSCH and a physical downlink control channel PDCCH associated with a msgB radio network temporary identifier msgB-RNTI, the PDSCH being scheduled by a downlink control information DCI scrambled by the msgB-RNTI, wherein the DCI scrambled by the msgB-RNTI includes a plurality of fields, the plurality of fields being included in a conventional DCI format scrambled by a temporary cell radio network temporary identifier TC-RNTI, and wherein the DCI scrambled by the msgB-RNTI further includes a field not included in the conventional DCI format and indicating whether a transport block size of a payload of the second message is scaled and a scaling factor of the second message.

2. The wireless communication method according to claim 1, wherein the DCI scrambled by the msgB-RNTI has a structure different from the conventional DCI format.

3. The wireless communication method according to claim 1, wherein the PDSCH includes at least one of the following: a first element corresponding to a physical uplink shared channel PUSCH received in response to and successfully decoded in the first message, a second element corresponding to a preamble sequence received in the first message but not successfully decoded the PUSCH, or a third element corresponding to a backoff indication.

4. The wireless communication method according to claim 3, wherein the first element includes at least one of the following: a contention conflict resolution ID, a C-RNTI assigned to the user equipment, or a timing advance TA command.

5. The wireless communication method according to claim 3, wherein the second element includes at least one of the following: a preamble identifier, a TC_RNTI, an uplink UL grant, or a TA command.

6. The wireless communication method according to claim 3, wherein the PDSCH includes a MAC structure, the MAC structure including a plurality of MAC sub-PDUs.

7. A wireless communication method, comprising: receiving, by a network device, a first message msgA from a user equipment in a wireless network to initiate a two-step random access to the wireless network; and sending, in response to the first message, a second message msgB to perform the two-step random access, the second message including a physical downlink shared channel PDSCH and a physical downlink control channel PDCCH associated with a msgB radio network temporary identifier msgB-RNTI, the PDSCH being scheduled by a downlink control information DCI scrambled by the msgB-RNTI, Among them, the DCI scrambled by the msgB-RNTI includes a plurality of fields, the plurality of fields are included in a conventional DCI format scrambled by a temporary cell radio network temporary identifier TC-RNTI, and Among them, the DCI scrambled by the msgB-RNTI further includes a field not included in the conventional DCI format and indicates whether the transport block size of the payload of the second message is scaled and the scaling factor of the second message.

8. The wireless communication method according to claim 7, Among them, The DCI scrambled by the msgB-RNTI has a structure different from the conventional DCI format.

9. The wireless communication method according to claim 7, Among them, The PDSCH includes at least one of the following: a first element corresponding to a physical uplink shared channel PUSCH included in the first message and successfully decoding the PUSCH, a second element corresponding to receiving a preamble sequence in the first message but not successfully decoding the PUSCH, or a third element corresponding to a backoff indication.

10. The wireless communication method according to claim 9, Among them, The first element includes at least one of the following: a contention conflict resolution ID, a C-RNTI assigned to the user equipment, or a timing advance TA command.

11. The wireless communication method according to claim 9, Among them, The second element includes at least one of the following: a preamble identifier, a TC_RNTI, an uplink UL grant, or a TA command.

12. The wireless communication method according to claim 9, Among them, The PDSCH includes a mac structure, and the mac structure includes a plurality of MAC sub-PDUs.

13. A communication device, comprising a processor and a memory, the processor is configured to read instructions from the memory to implement the method according to any one or more of claims 1 to 12.

14. A computer-readable medium, on which code is stored, and when the code is executed, it causes the processor to implement the method according to any one or more of claims 1 to 12.

Images