Time Domain Resource Allocation for PUSCH Transmission

Abstract

A method, a wireless communication device, a network node, and a computer-readable medium are provided that support flexible time resource allocation configuration for Msg3 while reducing signaling overhead in RAR / DCI indicating time resource allocation for PUSCH carrying Msg3. A method for a wireless communication device for random access (RA) includes transmitting a preamble on a physical random access channel (PRACH) (S301), receiving a random access response (RAR) message (S302), and transmitting a message for terminal identification (Msg3) on a physical uplink shared channel (PUSCH) (S303). The time resource allocation of Msg3 is different from the time resource allocation of other messages transmitted on the PUSCH (normal PUSCH).

Description

[Technical field]

[0001] Related Applications This application claims priority to and the benefit of International Application PCT / CN2018 / 077942, filed March 2, 2018, and entitled “TIME DOMAIN RESOURCE ALLOCATION FOR PUSCH TRANSMISSION.”

[0002] FIELD OF THE DISCLOSURE Embodiments herein relate generally to the field of wireless communications, and more particularly, embodiments herein relate to time domain resource allocation for PUSCH transmissions. [Background technology]

[0003] Random Access Procedure The Random Access (RA) procedure is an important function in cellular systems. In Long Term Evolution (LTE), a UE that wants to access the network initiates the random access procedure by transmitting a preamble (Msg1) in the uplink of the Physical Random Access Channel (PRACH). The gNb (Next Generation Node B, or Transmitting / Receiving Point (TRP), i.e., base station, access node), which receives the preamble and detects the random access attempt, responds in the downlink by transmitting a Random Access Response (RAR, Msg2). The RAR holds an uplink scheduling grant for the UE to continue the procedure by transmitting in the uplink the following subsequent message (Msg3) for terminal identification. A similar procedure is conceived for NR (New Radio, e.g., 5G or beyond) (see diagram in Fig. 1). Fig. 1 is a schematic signaling chart showing the messages of the random access procedure.

[0004] Before transmitting the PRACH preamble, the UE receives both a series of synchronization signals and configuration parameters for the broadcast channel of the SS block (e.g., NR-PSS, NR-SSS, NR-PBCH), possibly supplemented with configuration parameters received on further channels.

[0005] Send Msg3 Msg3 is transmitted by using the PUSCH channel. Besides the Msg3 payload, a demodulation reference signal (DMRS) is also transmitted to assist data decoding at the eNB / gNB. In both LTE and NR, for a four-step random access procedure, the first transmission of Msg3 is scheduled by an UL grant included in the RAR. Retransmission of Msg3 is scheduled by an UL grant through the PDCCH. In LTE, repetition of Msg3 can be configured by an UL grant included in the RAR, which extends the coverage of BL / CE UEs.

[0006] RAR UL Grants in LTE and NR In LTE, the uplink grant field of the RAR, also called the random access response grant field, indicates the resources to be used in the uplink. The size of the UL grant field is 20 bits for non-BL / CE UEs. The content of these 20 bits, starting from the MSB and ending with the LSB, is as follows: Hopping flag 1 bit Fixed size resource block assignment 10 bits Truncated modulation coding scheme 4 bits

[0007] If the UE is configured with high level parameter pusch-EnhancementsConfig: Number of repetitions of Msg3: 3 bits or TPC command for scheduled PUSCH 3 bits UL Delay 1 bit CSI Request 1 bit

[0008] For NB-IoT UEs, the size of the UL grant field is 15 bits, and for BL UEs and UEs with extended coverage level 2 or 3, the size of the UL grant field is 12 bits. The contents of the UL grant are listed in Table 6-2 of TS 36.213 for BL / CE UEs. The detailed design of the UL grant in the NR RAR is under consideration.

[0009] Resource Allocation for Msg3 in LTE The frequency resource assignment is indicated by a fixed size resource block assignment field in the UL grant contained in the RAR. The Msg3 transmission timing (without repetition) for non-BL / CE UE is specified as follows:

[0010] If a PDCCH with associated RA-RNTI is detected in subframe n and the corresponding DL-SCH transport block contains a response to the transmitted preamble sequence, the UE shall transmit the UL-SCH transport block in the first subframe n+k1, k1≧6 (n+k1 is the first UL subframe available for PUSCH transmission) according to the information contained in the response, if the UL delay field of the RAR is set to zero, and in case of a TDD serving cell, the first UL subframe for PUSCH transmission is determined based on the UL / DL configuration indicated by higher layers (i.e., the parameter subframeAssignment). The UE shall postpone PUSCH transmission until the next available UL subframe of n+k1 if the field is set to 1.

[0011] For a BL / CE UE with Msg3 PUSCH repetition count Δ configured, the UE shall postpone PUSCH transmission until the next available UL subframe of n+k1+Δ if the UL Delay field is set to 1.

[0012] PDSCH / PUSCH Time Domain Allocation in NR The current time domain allocation for PDSCH (PUSCH) in NR has not yet been finalized in RAN1, but some agreement has been reached in the RAN1 #90bis meeting.

[0013] For RRC connected mode, a 16-row time resource allocation table is signaled to the UE for each bandwidth portion by RRC signaling. Then, an index of the scheduling DCI indicates the exact time resource allocation for the PDSCH.

[0014] Agreement by RAN1 #90bis

[0015] For both slots and minislots, the scheduling DCI may provide an index into a UE-specific table that gives the OFDM symbol used for PDSCH (or PUSCH) transmission. i. Starting OFDM symbol and OFDM symbol length of the allocation ii. FFS: One or more tables iii. FFS: Slot used in case of multi-slot / multi-minislot scheduling, or slot index for cross-slot scheduling iv. FFS: If the SFI supports non-contiguous allocations, it may need to be reconsidered

[0016] At least for Minimum Remaining System Information (RMSI) scheduling i. At least one table input must be fixed in the specification.

[0017] Subcarrier Spacing (SCS) for Msg3 in NR NR supports RACH configuration of (RMSI) including 1 bit carrying SCS for Msg3. Below 6 GHz, the subcarrier spacing for Msg3 can be 15 or 30 kHz. Above 6 GHz, the subcarrier spacing for Msg3 can be 60 or 120 kHz. Summary of the Invention

[0018] Timing of Msg3 transmission and normal PUSCH in NR In TS 38.213, section 8.3, the minimum time between the last symbol in a PDSCH containing an RAR and the first symbol UE of a corresponding Msg3 PUSCH transmission is specified as N_t1+N_t2+N_ta_max+0.5 ms. N_t1 and N_t2 are the UE processing times specified in the tables of TS 38.214. For Numerology 1, N_t1+N_t2 gives approximately 22-25 symbols, and N_ta_max is the maximum timing adjustment that can be provided by a TA command for the RAR, which is approximately 2 slots. For a normal PUSCH transmission, only N_t2, which is 12 symbols, is required.

[0019] The timing of Msg3 is different from normal PUSCH transmission. For the first Msg3 transmission, the gNB should take into account the UE processing time of 0.5 ms required to process the MAC packet for all numerologies, N1 and N2, and the timing advance ranging from 0 to 2 slots. It would be difficult to cover K2 in a single table with 16 rows for both normal PUSCH and Msg3 for all numerologies.

[0020] For NR random access, new signaling is required to indicate the time resource assignment for Msg3 transmission / reception / repetition, including the start position and / or transmission duration, and / or the DMRS configuration related to Msg3 transmission / repetition.

[0021] In this embodiment, a default time resource allocation table for normal PUSCH is predefined, which indicates the timing K2, the starting symbol, and the PUSCH length. The timing of the PUSCH carrying Msg3 is indicated by using the difference in K2 between the normal PUSCH and the PUSCH carrying Msg3.

[0022] In one embodiment, a method is proposed in a wireless communication device for random access (RA), comprising: transmitting a preamble on a physical random access channel (PRACH); receiving a random access response (RAR) message; and transmitting a message for terminal identification on a physical uplink shared channel (PUSCH), wherein a time resource allocation of the message for terminal identification is different from a time resource allocation of other messages transmitted on the PUSCH.

[0023] In another embodiment, a method in a network node for random access (RA) is proposed, comprising: receiving a preamble on a physical random access channel (PRACH); transmitting a random access response (RAR) message; and receiving a message for terminal identification on a physical uplink shared channel (PUSCH), wherein a time resource allocation for the message for terminal identification is different from the time resource allocation for other messages transmitted on the PUSCH.

[0024] In yet another embodiment, a wireless communication device is proposed, comprising at least one processor and a non-transitory computer-readable medium coupled to the at least one processor, the non-transitory computer-readable medium including instructions executable by the at least one processor, whereby the at least one processor is configured to transmit a preamble on a physical random access channel (PRACH), receive a random access response (RAR) message, and transmit a message for terminal identification on a physical uplink shared channel (PUSCH), wherein a time resource allocation of the message for terminal identification is different from a time resource allocation of other messages transmitted on the PUSCH.

[0025] In yet another embodiment, a network node is proposed, comprising at least one processor and a non-transitory computer-readable medium coupled to the at least one processor, the non-transitory computer-readable medium including instructions executable by the at least one processor, whereby the at least one processor is configured to receive a preamble on a Physical Random Access Channel (PRACH), transmit a Random Access Response (RAR) message, and receive a message for terminal identification on a Physical Uplink Shared Channel (PUSCH), wherein a time resource allocation for the message for terminal identification is different from a time resource allocation for other messages transmitted on the PUSCH.

[0026] In yet another embodiment, a computer readable medium is proposed, comprising computer readable code which, when executed on a device, causes the device to perform any of the methods described above.

[0027] The method herein can accommodate flexible time resource allocation configuration for Msg3, while at the same time reducing the signaling overhead in RAR / DCI indicating time resource allocation for PUSCH carrying Msg3.

[0028] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate various embodiments of the present disclosure and, together with the description, serve to explain the principles of the disclosure and to enable those skilled in the art to make and use the embodiments disclosed herein. In the drawings, like reference numbers indicate identical or functionally similar elements. [Brief description of the drawings]

[0029] [Figure 1] 1 is a schematic signaling chart showing messages for a random access procedure. [Diagram 2] 1 is a schematic block diagram illustrating an example wireless communication system in which embodiments herein may be implemented; [Diagram 3] 1 is a schematic flow chart illustrating an example method in a wireless communication device, according to an embodiment herein. [Figure 4] 1 is a schematic flow chart illustrating an example method in a network node, according to embodiments herein. [Diagram 5] 1 is a schematic block diagram illustrating an example wireless communication device according to embodiments herein. [Figure 6] FIG. 2 is a schematic block diagram illustrating an example network node according to embodiments herein. [Figure 7] 1 is a schematic block diagram illustrating an apparatus according to an embodiment herein. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0030] Hereinafter, embodiments of the present specification will be described in detail with reference to the accompanying drawings in which the embodiments are shown. However, these embodiments of the present specification may be embodied in many different forms and should not be construed as being limited to the embodiments set forth herein. Elements of the drawings are not necessarily to scale relative to each other.

[0031] A reference to "one embodiment" or "an embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment is included in at least one embodiment. Thus, the appearances of the phrase "in one embodiment" in various places throughout the specification are not necessarily all referring to the same embodiment.

[0032] As used herein, the term "A, B, or C" means "A" or "B" or "C," and as used herein, the term "A, B, and C" means "A" and "B" and "C," and as used herein, the term "A, B, and / or C" means "A," "B," "C," "A and B," "A and C," "B and C," or "A, B, and C." Additionally, elements preceded by the singular forms "a," "an," and / or "the" are intended to include a plurality of such elements and thus may mean "one or more."

[0033] In the embodiment herein, a default time resource allocation table for normal PUSCH is predefined, which indicates the timing K2, the starting symbol, and the PUSCH length. The timing of the PUSCH carrying Msg3 is indicated by using the difference in K2 between the normal PUSCH and the PUSCH carrying Msg3.

[0034] 2 illustrates a schematic diagram of an example wireless communication system 200 in which embodiments may be implemented. In one embodiment, the wireless communication system 200 may include at least one wireless communication device 201 and at least one network node 202. However, the embodiments herein do not limit the number of wireless communication devices 201 and network nodes 202.

[0035] In one embodiment, the wireless communication system 200 may be embodied as, for example, a UE, a device-to-device (D2D) UE, a proximity capable UE (i.e., ProSe UE), a machine-type UE or a UE capable of machine-to-machine (M2M) communications, a personal digital assistant (PDA), a PAD, a tablet, a mobile terminal, a smartphone, a laptop embedded equipment (LEE), a laptop mounted equipment (LME), a USB dongle, etc.

[0036] In one embodiment, the network node 202 may be embodied as, for example, an eNodeB (eNB), a base station (BS), a network controller, a radio network controller (RNC), a base station controller (BSC), a repeater, a donor node controlled repeater, a base transceiver station (BTS), an access point (AP), a transmission point, a transmitting node, etc. In one embodiment, the network node 202 may be a gNB (Next Generation Node B). In one embodiment, the wireless communication system 200 may be configured in an over-the-top (OTT) scenario.

[0037] The time resource assignment configuration for Msg3 transmission in NR should take into account the minimum gap between RAR and Msg3 specified in NR and the semi-static TDD configuration indicated by higher order parameters, e.g., in RMSI or Radio Resource Control (RRC). The time resource configuration for Msg3 transmission / retransmission / repetition should also be related to at least the transmission duration, and / or the DMRS configuration, and / or the starting position.

[0038] In one embodiment, at least one default time resource allocation table (Table A) is predefined for PUSCHs other than Msg3 (referred to as normal PUSCHs), and a default table (Table B) is predefined for Msg3 to indicate the difference in K2 value between PUSCHs carrying Msg3 and normal PUSCHs (referred to as K2 offset).

[0039] In one embodiment, a K2 offset table (Table B) is formed by a one-to-one mapping between K2 offset values ​​and numerology, for example Table B1 below. TIFF0007600200000001.tif24170

[0040] In another embodiment, the K2 offset table (Table B) supports multiple K2 offset values ​​per numerology or for several numerologies. The K2 offset value used for the PUSCH carrying Msg3 is indicated by some reserved or unused bits in the RAR. For example, the time resource allocation field in the UL grant of the RAR has 4 bits, where 3 bits are used to indicate the row index of Table A and 1 bit is used to signal the K2 offset to choose from Table B. For example, Table B2 below. TIFF0007600200000002.tif24170

[0041] The time resource allocation for the PUSCH carrying Msg3 is indicated by using the default K2 offset table (Table B) in conjunction with the default time resource allocation table for normal PUSCH (Table A).

[0042] The starting position and symbol length of the PUSCH carrying Msg3 is indicated by the time domain resource allocation field in the UL grant of the RAR, which indicates the row index of Table A that the UE uses to read the K2, starting symbol position and length information of the PUSCH carrying Msg3 for the normal PUSCH. The K2 value for the PUSCH carrying Msg3 is obtained by K2+K2 offset for the normal PUSCH.

[0043] In one embodiment, a single default time allocation table (Table C) is used for both normal PUSCH and PUSCH carrying Msg3. This Table C can be formed by combining Tables A and B for each numerology.

[0044] According to the embodiment of the present specification, a default time resource allocation table for normal PUSCH is predefined, which indicates the timing K2, the starting symbol, and the PUSCH length. The timing of the PUSCH carrying Msg3 is indicated by using the difference in K2 between the normal PUSCH and the PUSCH carrying Msg3.

[0045] 3 is a schematic flow chart illustrating an example method 300 in a wireless communication device according to an embodiment herein. In one embodiment, the flow chart of FIG. 3 may be implemented in the wireless communication device 201 of FIG.

[0046] The method 300 may begin at step S301, where the wireless communication device 201 may transmit a preamble (Msg1) on a physical random access channel (PRACH). The method 300 may then proceed to step S302, where the wireless communication device 201 may receive a RAR message (Msg2) transmitted by the network node 202 in response to the preamble. The method 300 may then proceed to step S303, where the wireless communication device 201 may transmit a message for terminal identification (Msg3) on a physical uplink shared channel (PUSCH). The wireless communication device 201 may then further receive a contention resolution message (CRM) (Msg4) from the network node 202, although not shown. In one embodiment herein, the time resource allocation of Msg3 is different from the time resource allocation of any other message transmitted on the PUSCH (sometimes referred to as a normal PUSCH herein).

[0047] In one embodiment, the Msg3 time resource allocation has a timing offset (sometimes referred to as a K2 offset) from the time resource allocations of other messages transmitted on the PUSCH. In one embodiment, the Msg3 time resource allocation may be used to specify the minimum time between the last symbol of the PDSCH containing the RAR and the first symbol UE of the corresponding Msg3 PUSCH transmission. Note that there may be only one time resource allocation or multiple time resource allocations.

[0048] In one embodiment, the time resource allocation for the normal PUSCH may depend on the numerology used, for example, the time resource allocation for the normal PUSCH may depend on the subcarrier spacing (SCS) used, or other parameters.

[0049] In one embodiment, the time resource allocation for the normal PUSCH is indicated by the network node 202 via Residual Minimum System Information (RMSI), RRC, and / or Downlink Control Information (DCI). In one embodiment, the time resource allocation for the normal PUSCH is indicated by the network node 202 via any other message.

[0050] In one embodiment, the time resource allocation for the normal PUSCH may be placed and / or transmitted in a first predefined table or a first configuration table, which may be referred to as Table A. In one embodiment, more than one Table A is defined.

[0051] In one embodiment, the timing offset (i.e., K2 offset) may also depend on the numerology used. In one approach, there may be a one-to-one mapping between K2 offset values ​​and numerology. In another approach, there may be more than one possible K2 offset for a numerology. As used herein, numerology may include the subcarrier spacing (SCS) or other parameters used.

[0052] In one embodiment, the timing offset (K2 offset) may also be indicated by the network node via RMSI, RRC, DCI, and / or any other message. In one embodiment, the timing offset (K2 offset) may also be indicated by the network node 202 in the RAR message (Msg2). In one embodiment, the wireless communication device 201 (e.g., UE) has a priori knowledge of the K2 offset used for Msg3, so there is no need for the network node 202 to indicate the timing offset (K2 offset).

[0053] In one embodiment, the K2 offset may be located and / or transmitted in a second predefined table or a second configuration table (sometimes referred to as Table B). For example, Table B may be embodied as Table B1 described above, since there is a one-to-one mapping between K2 offset values ​​and numerologies. As yet another example, Table B may be embodied as Table B2 described above, where there may be more than one alternative K2 offset value for a numerology.

[0054] In one embodiment, Tables A and B may be combined into a single default time allocation table (Table C) used for both normal PUSCH and PUSCH carrying Msg3. This Table C may be formed by combining Tables A and B for each numerology.

[0055] The above steps are merely examples, and the wireless communication device 201 may perform any of the operations described in connection with FIG.

[0056] 4 is a schematic flow chart illustrating an example method 400 in a network node according to an embodiment herein. In one embodiment, the flow chart of FIG. 4 may be implemented in the network node 202 of FIG.

[0057] The method 400 may begin at step S401, where the network node 202 may receive a preamble (Msg1) on a physical random access channel (PRACH), which may instruct a wireless communication device (UE) to attempt to access the network node 202. Of course, more than one UE may attempt to access the network node 202. The method 400 may then proceed to step S402, where the network node 202 may, in response to the preamble, transmit a RAR message (Msg2) to the UE to attempt to access the network node 202. Msg2 may include an uplink (UL) grant for one or more UEs. The method 400 may then proceed to step S403, where the network node 202 may receive a message for terminal identification (Msg3) from one or more UEs on a physical uplink shared channel (PUSCH). Next, although not shown, the network node 202 may further transmit a Contention Resolution Message (CRM) (Msg4) to one or more UEs. In one embodiment herein, the time resource allocation for Msg3 is different from the time resource allocation for any other message transmitted on the PUSCH (sometimes referred to herein as the normal PUSCH).

[0058] In one embodiment, the Msg3 time resource allocation has a timing offset (sometimes referred to as a K2 offset) from the time resource allocations of other messages transmitted on the PUSCH. In one embodiment, the Msg3 time resource allocation may be used to specify the minimum time between the last symbol of the PDSCH containing the RAR and the first symbol UE of the corresponding Msg3 PUSCH transmission. Note that there may be only one time resource allocation or multiple time resource allocations.

[0059] In one embodiment, the time resource allocation for the normal PUSCH may depend on the numerology used, for example, the time resource allocation for the normal PUSCH may depend on the subcarrier spacing (SCS) used, or other parameters.

[0060] In one embodiment, the network node 202 may indicate the time resource allocation for the normal PUSCH via RMSI, RRC, and / or DCI. In one embodiment, the network node 202 may indicate the time resource allocation for the normal PUSCH via any other message.

[0061] In one embodiment, the time resource allocation for the normal PUSCH may be placed and / or transmitted in a first predefined table or a first configuration table, which may be referred to as Table A. In one embodiment, more than one Table A is defined.

[0062] In one embodiment, the timing offset (i.e., K2 offset) may also depend on the numerology used. In one approach, there may be a one-to-one mapping between K2 offset values ​​and numerology. In another approach, there may be more than one possible K2 offset for a numerology. As used herein, numerology may include the subcarrier spacing (SCS) or other parameters used.

[0063] In one embodiment, the network node 202 may also indicate the timing offset (K2 offset) via RMSI, RRC, DCI, and / or any other message. In one embodiment, the network node 202 may indicate the timing offset (K2 offset) in the RAR message (Msg2). In one embodiment, the wireless communication device 201 (e.g., UE) has a priori knowledge of the K2 offset used for Msg3, so there is no need for the network node 202 to indicate the timing offset (K2 offset).

[0064] In one embodiment, the K2 offset may be located and / or transmitted in a second predefined table or a second configuration table (sometimes referred to as Table B). For example, Table B may be embodied as Table B1 described above, since there is a one-to-one mapping between K2 offset values ​​and numerologies. As yet another example, Table B may be embodied as Table B2 described above, where there may be more than one alternative K2 offset value for a numerology.

[0065] In one embodiment, Tables A and B may be combined into a single default time allocation table (Table C) used for both normal PUSCH and PUSCH carrying Msg3. This Table C may be formed by combining Tables A and B for each numerology.

[0066] The above steps are merely examples, and the network node 202 may perform any of the operations described in connection with FIG.

[0067] FIG. 5 is a schematic block diagram illustrating an example wireless communication device 201, according to embodiments herein.

[0068] In one embodiment, the wireless communication device 201 may include at least one processor 501 and a non-transitory computer-readable medium 502 coupled to the at least one processor 501. The non-transitory computer-readable medium 502 includes instructions executable by the at least one processor 501, thereby configuring the at least one processor 501 to perform steps of the exemplary method 300 as shown in the schematic flow chart of Figure 3, which will not be described in detail here.

[0069] It should be noted that the wireless communication device 201 may be embodied in hardware, software, firmware, and / or any combination thereof, For example, the wireless communication device 201 may include multiple units, circuit configurations, or modules, each of which may be used to perform the steps of the example method 300 associated with the wireless communication device 201 or any steps illustrated in FIG.

[0070] FIG. 6 is a schematic block diagram illustrating an example network node 202, according to embodiments herein.

[0071] In one embodiment, the network node 202 may include at least one processor 601 and a non-transitory computer-readable medium 602 coupled to the at least one processor 601. The non-transitory computer-readable medium 602 includes instructions executable by the at least one processor 601, thereby configuring the at least one processor 601 to perform steps of the exemplary method 400 as illustrated in the schematic flow chart of Figure 4, the details of which will not be described here.

[0072] It should be noted that the network node 202 may be embodied in hardware, software, firmware, and / or any combination thereof. For example, the network node 202 may include multiple units, circuitry, or modules, each of which may be used to perform the steps of the example method 400 associated with the network node 202 or any steps illustrated in FIG. 2.

[0073] 7 is a schematic block diagram illustrating an apparatus 700 according to an embodiment herein. In one embodiment, the apparatus 700 may be configured as any of the apparatuses described above, such as a wireless communication device 201 or a network node 202.

[0074] In one embodiment, the apparatus 700 may include at least one processor, such as, but not limited to, a central processing unit (CPU) 701, a computer readable medium 702, and a memory 703. The memory 703 may include volatile (e.g., random access memory (RAM)) and / or non-volatile memory (e.g., a hard disk or flash memory). In one embodiment, the computer readable medium 702 may be configured to store computer programs and / or instructions that, when executed by the processor 701, cause the processor 701 to perform any of the methods described above.

[0075] In one embodiment, computer readable medium 702 (e.g., a non-transitory computer readable medium) may be stored in memory 703. In another embodiment, the computer program may be stored remotely, such as in a computer program product 704 (which may also be embodied as a computer readable medium) and accessible by processor 701, such as via carrier 705.

[0076] The computer readable medium 702 and / or the computer program product 704 may be distributed and / or stored on a removable computer readable medium, such as a diskette, a CD (compact disc), a DVD (digital video disc), flash or similar removable memory media (e.g., compact flash, SD (secure digital), memory stick, mini SD card, MMC multimedia card, smart media), HD-DVD (high definition DVD) or Blu-ray DVD, USB (universal serial bus) based removable memory media, magnetic tape media, optical storage media, magneto-optical media, bubble memory, or may be distributed as a propagated signal over a network (e.g., Ethernet, ATM, ISDN, PSTN, X.25, Internet, local area network (LAN), or similar network capable of carrying data packets to infrastructure nodes).

[0077] Exemplary embodiments are described herein with reference to block diagrams and / or flowchart illustrations of computer-implemented methods, apparatus (systems and / or devices), and / or non-transitory computer program products. It will be understood that blocks of the block diagrams and / or flowchart illustrations, and combinations of blocks in the block diagrams and / or flowchart illustrations, can be realized by computer program instructions executed by one or more computer circuits. These computer program instructions may be provided to general-purpose computer circuits, special-purpose computer circuits, and / or processor circuits of other programmable data processing circuits that produce machines, whereby the instructions executing via the processor of the computer and / or other programmable data processing apparatus transform and control transistors, values ​​stored in memory locations, and other hardware components in such circuitry to implement the functions / operations specified in one or more blocks of the block diagrams and / or flowcharts, thereby creating means (functionality) and / or structure for implementing the functions / operations specified in the blocks of the block diagrams and / or flowcharts.

[0078] These computer program instructions may also be stored on a tangible computer readable medium that can instruct a computer or other programmable data processing apparatus to function in a particular manner, whereby the instructions stored on the computer readable medium create an article of manufacture containing instructions that implement the functions / acts specified in one or more blocks of the block diagrams and / or flowcharts. Thus, embodiments of the inventive concepts may be embodied in the form of hardware and / or software (including firmware, resident software, microcode, etc.) running on a processor, such as a digital signal processor, which may collectively be referred to as "circuitry," "modules," or variations thereof.

[0079] Many variations and modifications can be made to the embodiments without substantially departing from the principles of the disclosed inventive concept. All such variations and modifications are intended to be included herein within the scope of the inventive concept. Accordingly, the subject matter disclosed above should be considered illustrative rather than limiting, and the accompanying example embodiments are intended to encompass all such modifications, improvements, and other embodiments that are within the spirit and scope of the inventive concept. Thus, to the maximum extent permitted by law, the scope of the inventive concept should be determined by the broadest permissible interpretation of this disclosure, including the example embodiments set forth below and their equivalents, and should not be limited or restricted by the detailed description set forth above.

[0080] Abbreviation 3GPP 3rd Generation Partnership Project CRM Conflict Resolution Messages DCI Downlink Control Information DMRS demodulation reference signal LTE Long Term Evolution NR new radio OFDM Orthogonal Frequency Division Multiplexing OTT Over the Top PBCH Physical Broadcast Channel PDCCH Physical Downlink Control Channel PDSCH Physical Downlink Shared Channel PRACH Physical Random Access Channel PSS Primary Synchronization Signal PUSCH Physical Uplink Shared Channel RA Random Access RAN Radio Access Network RAR Random Access Response RMSI Minimum System Information Remaining RRC Radio Resource Control SCS Subcarrier Spacing SSS Secondary Synchronization Signal TDD time division duplex UL Uplink

Claims

1. A method (300) for random access (RA) in a wireless communication device (201), comprising: Transmitting a preamble on a physical random access channel (PRACH) (S301); Receiving a Random Access Response (RAR) message (S302); Transmitting a message for terminal identification on a physical uplink shared channel (PUSCH) (S303); A time resource allocation of the message for terminal identification is different from a time resource allocation of another message transmitted on the PUSCH, the time resource allocation of the message for terminal identification has a timing offset with respect to a time resource allocation of the other message transmitted on the PUSCH; A method (300), wherein a time resource allocation for the other message transmitted on the PUSCH is included in a first predefined table or a first configuration table.

2. 2. The method (300) of claim 1, wherein a time resource allocation for the other message transmitted on the PUSCH depends on a numerology used.

3. The method (300) of claim 1 or 2, wherein a time resource allocation for the other message to be transmitted on the PUSCH is indicated by a network node (202) via Residual Minimum System Information (RMSI). A method (400) for random access (RA) in a network node (202), comprising: Receiving a preamble on a physical random access channel (PRACH) (S401); Sending a Random Access Response (RAR) message (S402); Receiving a message for terminal identification on a physical uplink shared channel (PUSCH) (S403); A time resource allocation of the message for terminal identification is different from a time resource allocation of another message transmitted on the PUSCH, the time resource allocation of the message for terminal identification has a timing offset with respect to a time resource allocation of the other message transmitted on the PUSCH; A method (400), wherein a time resource allocation for the other message transmitted on the PUSCH is included in a first predefined table or a first configuration table.

5. 5. The method (400) of claim 4, wherein time resource allocation for the other message transmitted on the PUSCH depends on the numerology used.

6. The method (400) of claim 4 or 5, further comprising indicating a time resource allocation for the other message transmitted on the PUSCH via a remaining minimum system information (RMSI).

7. At least one processor (501); a non-transitory computer-readable medium (502) coupled to the at least one processor (501), the non-transitory computer-readable medium (502) including instructions executable by the at least one processor (501), whereby the at least one processor (501) A preamble is transmitted on a physical random access channel (PRACH) (S301); A random access response (RAR) message is received (S302); A message for identifying the terminal is transmitted (S303) on a physical uplink shared channel (PUSCH); A time resource allocation of the message for terminal identification is different from a time resource allocation of another message transmitted on the PUSCH, the time resource allocation of the message for terminal identification has a timing offset with respect to a time resource allocation of the other message transmitted on the PUSCH; A wireless communication device (201), wherein a time resource allocation for the other message transmitted on the PUSCH is included in a first predefined table or a first configuration table.

8. The wireless communication device (201) of claim 7, wherein time resource allocation for the other message transmitted on the PUSCH depends on the numerology used.

9. 9. The wireless communication device (201) of claim 7 or 8, wherein the time resource allocation of the further message to be transmitted on the PUSCH is indicated by a network node (202) via Residual Minimum System Information (RMSI).

10. At least one processor (601); a non-transitory computer-readable medium (602) coupled to the at least one processor (601), the non-transitory computer-readable medium (602) including instructions executable by the at least one processor (601), whereby the at least one processor (601) Receive a preamble via a physical random access channel (PRACH) (S401); Send a random access response (RAR) message (S402); A physical uplink shared channel (PUSCH) is configured to receive a message for identifying a terminal (S403); A time resource allocation of the message for terminal identification is different from a time resource allocation of another message transmitted on the PUSCH, the time resource allocation of the message for terminal identification has a timing offset with respect to a time resource allocation of the other message transmitted on the PUSCH; A network node (202), wherein a time resource allocation for said further message transmitted on said PUSCH is included in a first predefined table or a first configuration table.

11. 11. The network node (202) of claim 10, wherein time resource allocation for the further message transmitted on the PUSCH depends on the numerology used.

12. The at least one processor:

12. The network node (202) of claim 10 or 11, further configured to indicate a time resource allocation of the further message transmitted on the PUSCH via a remaining minimum system information (RMSI).

13. A computer program which, when executed on an apparatus (700), causes said apparatus (700) to carry out the method (300) of any one of claims 1 to 3.

14. A computer program which, when executed on an apparatus (700), causes said apparatus (700) to carry out the method (400) of any one of claims 4 to 6.

Images