[go: up one dir, main page]

WO2025208515A1 - Configuration de code de couverture orthogonale pour message 3 - Google Patents

Configuration de code de couverture orthogonale pour message 3

Info

Publication number
WO2025208515A1
WO2025208515A1 PCT/CN2024/086098 CN2024086098W WO2025208515A1 WO 2025208515 A1 WO2025208515 A1 WO 2025208515A1 CN 2024086098 W CN2024086098 W CN 2024086098W WO 2025208515 A1 WO2025208515 A1 WO 2025208515A1
Authority
WO
WIPO (PCT)
Prior art keywords
msg
occ
dci
network device
terminal device
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2024/086098
Other languages
English (en)
Inventor
Mads LAURIDSEN
Ping Yuan
Rafhael MEDEIROS DE AMORIM
Jing Yuan Sun
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nokia Shanghai Bell Co Ltd
Nokia Solutions and Networks Oy
Nokia Technologies Oy
Original Assignee
Nokia Shanghai Bell Co Ltd
Nokia Solutions and Networks Oy
Nokia Technologies Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Shanghai Bell Co Ltd, Nokia Solutions and Networks Oy, Nokia Technologies Oy filed Critical Nokia Shanghai Bell Co Ltd
Priority to PCT/CN2024/086098 priority Critical patent/WO2025208515A1/fr
Publication of WO2025208515A1 publication Critical patent/WO2025208515A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0014—Three-dimensional division
    • H04L5/0016—Time-frequency-code
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H04W74/006—Transmission of channel access control information in the downlink, i.e. towards the terminal

Definitions

  • a communication network can be seen as a facility that enables communications between two or more communication devices, or provides communication devices access to a data network.
  • a mobile or wireless communication network is one example of a communication network.
  • Such communication networks operate in accordance with standards, such as those promulgated by 3GPP (Third Generation Partnership Project) or ETSI (European Telecommunications Standards Institute) .
  • standards such as those promulgated by 3GPP (Third Generation Partnership Project) or ETSI (European Telecommunications Standards Institute) .
  • 3GPP Third Generation Partnership Project
  • ETSI European Telecommunications Standards Institute
  • 5G Fifth Generation
  • example embodiments of the present disclosure provide a solution for an OCC configuration for a random access message 3.
  • an apparatus comprising means for receiving, at a terminal device and from a network device, downlink control information (DCI) for scheduling a random access response (RAR) ; means for receiving the RAR from the network device based on the DCI, wherein at least one of the DCI or the RAR comprises first configuration information associated with an orthogonal cover code (OCC) for transmitting a message 3 (MSG 3) ; and means for transmitting, based on the first configuration information, the MSG 3 to the network device.
  • DCI downlink control information
  • RAR random access response
  • OCC orthogonal cover code
  • a non-transitory computer readable medium comprising program instructions for causing an apparatus to perform at least the method according to any one of the above third to fourth aspect.
  • a computer program comprising instructions, which, when executed by an apparatus, cause the apparatus at least to: receive, from a network device, downlink control information (DCI) for scheduling a random access response (RAR) ; receive the RAR from the network device based on the DCI, wherein at least one of the DCI or the RAR comprises first configuration information associated with an orthogonal cover code (OCC) for transmitting a message 3 (MSG 3) ; and transmit, based on the first configuration information, the MSG 3 to the network device.
  • DCI downlink control information
  • RAR random access response
  • OCC orthogonal cover code
  • a computer program comprising instructions, which, when executed by an apparatus, cause the apparatus at least to: transmit, to a terminal device, downlink control information (DCI) for scheduling a random access response (RAR) ; transmit the RAR to the terminal device based on the DCI, wherein at least one of the DCI or the RAR comprises first configuration information associated with an orthogonal cover code (OCC) for transmitting a message 3 (MSG 3) ; and receive, from the terminal device, the MSG 3 based on the first configuration information.
  • DCI downlink control information
  • RAR random access response
  • OCC orthogonal cover code
  • a terminal device comprising first receiving circuitry configured to receive, at a terminal device and from a network device, downlink control information (DCI) for scheduling a random access response (RAR) ; second receiving circuitry configured to receive the RAR from the network device based on the DCI, in which at least one of the DCI or the RAR comprises first configuration information associated with an orthogonal cover code (OCC) for transmitting a message 3 (MSG 3) ; and transmitting circuitry configured to transmit, based on the first configuration information, the MSG 3 to the network device.
  • DCI downlink control information
  • RAR random access response
  • second receiving circuitry configured to receive the RAR from the network device based on the DCI, in which at least one of the DCI or the RAR comprises first configuration information associated with an orthogonal cover code (OCC) for transmitting a message 3 (MSG 3) ; and transmitting circuitry configured to transmit, based on the first configuration information, the MSG 3 to the network device.
  • OCC orthogonal cover code
  • a network device comprising first transmitting circuitry configured to transmit, at a network device and to a terminal device, downlink control information (DCI) for scheduling a random access response (RAR) ; second transmitting circuitry configured to transmitting the RAR to the terminal device based on the DCI, wherein at least one of the DCI or the RAR comprises first configuration information associated with an orthogonal cover code (OCC) for transmitting a message 3 (MSG 3) ; and receiving circuitry configured to receive, from the terminal device, the MSG 3 based on the first configuration information.
  • DCI downlink control information
  • RAR random access response
  • OCC orthogonal cover code
  • Fig. 1A illustrates an example communication network in which embodiments of the present disclosure may be implemented
  • Fig. 1B illustrates an example of MAC payload consisting of MAC headers and MAC RARs
  • Fig. 1E and Fig. 1F illustrate MAC RAR payload structures for NB-IoT
  • Fig. 1G illustrates a random access symbol group
  • Fig. 2 illustrates a flowchart illustrating a process for OCC configuration for random access MSG 3 according to some embodiments of the present disclosure
  • Fig. 3 illustrates an example process for OCC configuration for random access MSG 3 according to some embodiments of the present disclosure
  • Fig. 4 illustrates another example process for OCC configuration for random access MSG 3 according to some embodiments of the present disclosure
  • Fig. 5 illustrates a flowchart of a method implemented at a terminal device according to some embodiments of the present disclosure
  • Fig. 6 illustrates a flowchart of a method implemented at a network device according to some embodiments of the present disclosure
  • Fig. 7 illustrates a simplified block diagram of an apparatus that is suitable for implementing embodiments of the present disclosure.
  • Fig. 8 illustrates a block diagram of an example computer readable medium in accordance with some embodiments of the present disclosure.
  • references in the present disclosure to “one embodiment, ” “an embodiment, ” “an example embodiment, ” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
  • first and second etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments.
  • the term “and/or” includes any and all combinations of one or more of the listed terms.
  • circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware.
  • circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.
  • IoT-NTN in particular NB-IoT
  • NB-IoT will have to support massive capacity in terms of number and types of UE, some of which with worse characteristics than others (e.g. low cost devices, wearables, etc) .
  • multiplexing of UEs by usage of orthogonal cover codes (OCC) for narrowband physical uplink shared channel (NPUSCH) format 1 and narrowband physical random access channel (NPRACH) should therefore be studied and if beneficial being specified. Therefore, in order to unlock the additional UL capacity potential, there is a need to identify methods to de-couple the UL from the DL as much as possible.
  • OCC orthogonal cover codes
  • NPUSCH narrowband physical uplink shared channel
  • NPRACH narrowband physical random access channel
  • enhancements to enable multiplexing of multiple UEs e.g. up to the minimum of 4 and the maximum allowed by the UL and DL signalling
  • OFC orthogonal cover codes
  • NPUSCH format 1 and NPRACH Multi-tone support for 15 kHz SCS should also be considered.
  • MSG 2 RAR has no spare bits to inform the UE what OCC to apply to MSG 3 PUSCH transmission.
  • a new solution is proposed in some embodiments of the present disclosure. For example, in some embodiments, a solution on how the eNB can signal the OCC code for the (N) PUSCH transmission of message (MSG) 3 is proposed for uplink capacity enhancement, thereby improving communication performance.
  • Fig. 1A illustrates an example communication system 100 (or referred to as communication network) in which embodiments of the present disclosure may be implemented.
  • the system 100 for example, a communication network, includes a plurality of network device (s) and terminal device (s) , such as a terminal device 101 and a network device 103.
  • the terminal device 101 and other terminal devices e.g. a terminal device 102
  • the network device 103 may allocate resources for the successfully accessed terminal device.
  • OCCs ohogonal cover codes
  • more than one terminal device may transmit, to the network device 103, message 3 (MSG 3) using the same allocated resources.
  • the network device 103 may communicate with the terminal device (s) , e.g. the terminal device 101, to transmit some configuration (s) associated with the OCC.
  • the system 100 may include any suitable number of network devices and terminal devices adapted for implementing embodiments of the present disclosure.
  • Communications in the communication system 100 may be implemented according to any proper communication protocol (s) , comprising, but not limited to, cellular communication protocols of the first generation (1G) , the second generation (2G) , the third generation (3G) , the fourth generation (4G) and the fifth generation (5G) and on the like, wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) 802.11 and the like, and/or any other protocols currently known or to be developed in the future.
  • s cellular communication protocols of the first generation (1G) , the second generation (2G) , the third generation (3G) , the fourth generation (4G) and the fifth generation (5G) and on the like, wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) 802.11 and the like, and/or any other protocols currently known or to be developed in the future.
  • IEEE Institute for Electrical and Electronics Engineers
  • the communication may utilize any proper wireless communication technology, comprising but not limited to: Code Division Multiple Access (CDMA) , Frequency Division Multiple Access (FDMA) , Time Division Multiple Access (TDMA) , Frequency Division Duplex (FDD) , Time Division Duplex (TDD) , Multiple-Input Multiple-Output (MIMO) , Orthogonal Frequency Division Multiple (OFDM) , Discrete Fourier Transform spread OFDM (DFT-s-OFDM) and/or any other technologies currently known or to be developed in the future.
  • CDMA Code Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • MIMO Multiple-Input Multiple-Output
  • OFDM Orthogonal Frequency Division Multiple
  • DFT-s-OFDM Discrete Fourier Transform spread OFDM
  • Step 1 transmission of message (MSG) 1 (from the UE to base station) , during which the UE randomly selects one of the subset of available random access preambles (when contention based RA is used) , and transmits the preamble in one of the UL resources reserved as a RA occasion.
  • the UE starts monitoring for PDCCH resources scrambled with RA-RNTI that allocates the PDSCH with the RAR.
  • RA-RNTI depends only on the RACH occasion it corresponds to (i.e. SFN of the occasion where the preamble was transmitted) , multiple UEs might monitor and decode the same RA-RNTI.
  • Step 2 transmission of MSG 2 (from the base station to the UE) , during which the NW will send a random access response (RAR) to the received random access attempts containing: power control information, timing advance command, UL scheduling of MSG 3, and temporary C-RNTI (temporary UE ID) .
  • RAR random access response
  • MSG 2 from the base station to the UE
  • C-RNTI temporary UE ID
  • Fig. 1B illustrates the header and RAR payload.
  • the MAC header is of variable size and consists of the following fields: E, T, R, BI, and RAPID.
  • the E field i.e. an Extension field is a flag indicating if more fields are present in the MAC header or not.
  • the E field is set to “1” to indicate at least another set of E/T/RAPID fields follows.
  • the size of the BI field is 4 bits.
  • the RAPID field i.e. a Random Access Preamble Identifier field identifies the transmitted Random Access Preamble (see 3GPP TS 36.321, clause 5.1.3) .
  • the size of the RAPID field is 6 bits. If the UE is already in connected mode, i.e., if the UE has already an assigned C-RNTI, it ignores the temporary C-RNTI field and proceeds with the next steps (or with the connection in case of contention-free RA) . It should be noted that the RAR content depends on the device type and PRACH format.
  • Step 3 transmission of MSG 3 (from UE to base station) .
  • message 3 is needed (contention-based RA) , it is transmitted by the UE using the information contained in the scheduling provided in MSG 2.
  • the message is scrambled by the UE T-CRNTI. If the contention is resolved successfully for this UE in MSG 4, the UE will adopt the T-CRNTI as C-RNTI, used to identify the UL/DL resources addressed by/from this UE and scramble the information.
  • Step 4 transmission of MSG 4 (from BS to UE) .
  • MSG 4 is utilized to resolve for contention-based procedure when needed.
  • Fig. 1C and Fig. 1D illustrate MAC RAR payload structures for eMTC.
  • Fig. 1C shows an example of MAC RAR structure.
  • Fig. 1D shows an example of MAC RAR for PRACH enhanced coverage level 2 or 3.
  • Fig. 1E and Fig. 1F illustrate MAC RAR payload structures for NB-IoT.
  • Fig. 1E shows an example of MAC RAR for NB-IoT UEs.
  • Fig. 1F shows an example of MAC RAR for NB-IoT UEs using PRACH preamble format 2.
  • the MAC RAR is of fixed size and consists of the following fields. R, i.e.
  • Timing Advance Command field indicates the index value TA (0, 1, 2...1282) used to control the amount of timing adjustment that the MAC entity has to apply (see clause 4.2.3 of TS 36.213 [2] ) , except for NB-IoT UEs using preamble format 2, where the Timing Advance Command field indicates the index value TA (0, 1, 2...1536) .
  • the size of the Timing Advance Command field is 11 bits.
  • the Uplink Grant field indicates the resources to be used on the uplink (see clause 6.2 of TS 36.213 [2] , or for NB-IoT UEs, see clause 16.3.3 of TS 36.213 [2] ) .
  • the size of the UL Grant field is 20 bits, except for NB-IoT UEs, where the size of UL grant field is 15 bits, and except for BL UEs and UEs in enhanced coverage level 2 or 3, where the size of the UL grant field is 12 bits.
  • ER i.e. Extended RAPID bits, indicating the two least significant bits of extended RAPID used when PRACH preamble format 2 is transmitted.
  • the Temporary C-RNTI indicates the temporary identity that is used by the MAC entity during random access.
  • the size of the Temporary C-RNTI field is 16 bits.
  • the MAC RAR is octet aligned.
  • DCI format 6-1A and 6-1B will be used to schedule the RAR.
  • DCI format N1 will be used to schedule the RAR.
  • DCI format 6-1A/1B and N1 when it is scrambled with a RA-RNTI, some of the DCI fields are reserved. This implies it is possible to re-define the fields when OCC is supported in PRACH.
  • the format 6-1A CRC is scrambled with a RA-RNTI, then the following fields among the fields above are reserved: HARQ process number, New data indicator, Downlink Assignment Index, and HARQ-ACK resource offset.
  • the format 6-1B CRC is scrambled with a RA-RNTI then the following fields among the fields above are reserved: HARQ process number, New data indicator, and HARQ-ACK resource offset.
  • the format N1 CRC is scrambled with a RA-RNTI or a G-RNTI, then the following fields among the fields above are reserved for RA-RNTI and not present for G-RNTI: New data indicator and HARQ-ACK resource.
  • the preamble is composed of a sequence of 3-5 identical symbols, which combined with the cyclic prefix is the symbol group.
  • the physical layer random access preamble is based on single-subcarrier frequency-hopping symbol groups.
  • a symbol group is illustrated in Fig. 1G, consisting of a cyclic prefix of length T CP and a sequence of N identical symbols with total length T SEQ .
  • the total number of symbol groups in a preamble repetition unit is denoted by P.
  • the number of time-contiguous symbol groups is given by G.
  • the random access preamble parameters for frame structure 1 may refer to Table 1.
  • the resource block for PUSCH is composed of 7 symbols (with normal CP) and 6 symbols (with extended CP) , while PRACH is spaced on a sequence of [1-2] *24576*Ts (preamble formats 0-3) .
  • the 7 symbols (one slot) corresponds to 15360*Ts and thus the mapping between PUSCH and PRACH is also difficult.
  • there may have multiple preambles which use the same OCC number e.g., both preamble #A and #B use the OCC#1 and OCC#2) .
  • the RARs to allocate the PUSCH resource for MSG 3 corresponding to preamble #A and #B it is NW implementation flexibility to allocate them in the same PUSCH resource (i.e., same subframe and same PRB) but with different OCC (e.g., the PUSCH OCC number for preamble #Acan be OCC#1 and OCC#2 while the PUSCH OCC number for preamble #B may be OCC#3 and OCC#4 ) .
  • the OCC number used in preambles may be different from the ones used in MSG 3 PUSCH. This implies the OCC number for MSG 3 PUSCH may need to be indicated in the RAR, no matter it is explicit or implicit.
  • the PUSCH resource for MSG 3 is scheduled by RAR in the field of UL grant which cannot indicate OCC.
  • a base station may inform a UE how to apply OCC on the (N) PUSCH for message 3 transmission. It may be in principle independent of whether OCC was used for the (N) PRACH. In some other examples, the base station may inform the UE whether to use the OCC on the (N) PUSCH for message 3 transmission.
  • the details of some solutions of the present disclosure may further refer to embodiments shown in Figs 2 to 4.
  • Fig. 2 shows a process for OCC configuration for random access MSG 3 according to some embodiments of the present disclosure.
  • the terminal device 101 and the network device 103 are involved.
  • the terminal device 101 may be a UE or another terminal device.
  • the network device 103 may be a base station, such as an eNB or a gNB, etc.
  • the MSG 3 may be the third message transmitted in a 4-step random access procedure.
  • the MSG 3 may be a message transmitted on uplink shared channel (UL-SCH) containing a cell radio network temporary identifier (C-RNTI) media access control control element (MAC CE) or common control channel service data unit (CCCH SDU) , submitted from upper layer and associated with the UE contention resolution identity, as part of the random access procedure.
  • UL-SCH uplink shared channel
  • C-RNTI cell radio network temporary identifier
  • MAC CE media access control control element
  • CCCH SDU common control channel service data unit
  • the first configuration information may comprise an index of a first OCC among a plurality of OCCs, or an indication that no OCC is to be applied for the transmission of the MSG 3 225.
  • the first OCC among the plurality of OCCs is to be applied for the transmission of the MSG 3 225.
  • the index of a first OCC may be an identity (ID) of the first OCC.
  • the first configuration information may be determined based on the a first TC-RNTI in the RAR 215, an OCC length or a number of a plurality of OCCs, and a mapping rule from a TC-RNTI to an index of an OCC.
  • the mapping rule may be: the OCC ID is based on “TC-RNTI mod OCC length” .
  • the first TC-RNTI mapped to the index of the first OCC among a plurality of OCCs indicates that the first OCC is to be applied for the transmission of the MSG 3 225.
  • the first TC-RNTI mapped to a value different from an index of an OCC among the plurality of OCCs indicates that no OCC is to be applied for the transmission of the MSG 3 225.
  • the value determined based on the mapping rule is different from any OCC ID among a plurality of OCC IDs (OCC IDs of the plurality of OCCs) , it means that no OCC is to be applied for the transmission of the MSG 3 225.
  • the mapping rule indicates that an OCC index may be based on a TC-RNTI and a parameter.
  • such parameter may be the OCC length, the number of the plurality of OCCs, the OCC length plus 1, or the number of the plurality of OCCs plus 1, or any combination thereof.
  • the mapping rule may be: the OCC ID is based on “TC-RNTI mod (OCC length+1) ” .
  • the OCC length or the number of the plurality of OCCs may be indicated in the DCI 205, that is, the network device 103 may indicate, in the DCI 205 and to the terminal device 101, the OCC length or the number of the plurality of OCCs.
  • the OCC length or the number of the plurality of OCCs may be predetermined, e.g. specified in a protocol.
  • the mapping rule is applicable for a plurality of TC-RNTIs.
  • the plurality of TC-RNTIs may correspond to a plurality of value ranges.
  • the mapping rule is applicable for a subset of the plurality of TC-RNTIs.
  • the mapping rule is applicable for TC-RNTI (s) in one of the plurality of value ranges of the plurality of TC-RNTI.
  • the TC-RNTI (s) in the one value range of the plurality of value ranges of the plurality of TC-RNTI may be considered as a subset of the plurality of TC-RNTIs.
  • the “TC-RNTI mod OCC length” or “TC-RNTI mod (OCC length+1) ” function is only applied to the subset of the TC-RNTIs.
  • the mapping rule is applicable for the subset of the plurality of TC-RNTIs
  • the first TC-RNTI which is not one of the subset of a plurality of TC-RNTIs may indicate that no OCC is to be applied for the transmission of the MSG 3 225.
  • the first configuration information may be determined based on a first TC-RNTI in the RAR 215, and the mapping rule from a value range of a TC-RNTI to an OCC index. For example, it may be indicated in the RAR 215 that the TC-RNTI range [X : Y] applies OCC code 1, range [Y+1 : Z] applies OCC code 2 and so forth. Based on the first TC-RNTI and the mapping rule, the terminal device 101 may know what OCC to apply for (N) PUSCH of MSG 3 225.
  • the mapping rule in the examples above may be configured by the network device 103, that is, the network device 103 may configure, to the terminal device 101, the mapping rule.
  • the mapping rule in the examples above may be predetermined.
  • the eNB (or specification) may define the mapping rule from the TC-RNTI to the OCC of MSG 3 225.
  • the TC-RNTI may be included in the MAC RAR payload and is controlled by the network i.e. it can also control the OCC.
  • the first configuration information may be carried in the at least one first bit in the DCI 205 indicating the index of the first OCC to be applied for the transmission of the MSG 3 225.
  • the eNB can use one or more of the reserved bits in the DCI 205 that schedules the RAR (MSG 2) 215 to define the OCC of MSG 3 225.
  • the relevant DCIs are format 6-1A, 6-1B and N1 as mentioned above.
  • the DCI 205 is received in a time resource and a frequency resource.
  • the at least one first bit in the DCI 205 and at least one of the time resource or the frequency resource indicate the index of the first OCC to be applied for the transmission of the MSG 3 225.
  • the network device 103 may define that a DCI 205 transmitted in a certain time/frequency resource corresponds to OCCs in one range, while a DCI 205 in another resource corresponds to OCCs in another range.
  • the first configuration information is carried in the at least one second bit in the DCI 205 indicating whether an OCC is to be applied for the transmission of the MSG 3 225.
  • the at least one second bit as a flag is used for indicating whether an OCC is applied for the transmission of the MSG 3 225.
  • the first configuration information may be determined based on a difference between OCCs for transmitting the MSG 3 225 and for transmitting a message 1 (MSG 1) .
  • the difference may be indicated in the DCI 205 or the RAR 215 or the both.
  • the network device 103 may check, after receiving the MSG 1 from the terminal device 101, whether OCCs for transmitting the MSG 3 225 and for transmitting an MSG 1 are different, and based on the OCCs for transmitting the MSG 3 225 and for transmitting the MSG 1 being different, indicates the first configuration information in the at least one of the DCI 205 or the RAR 215.
  • the network device 103 may check, after receiving the MSG 1 from the terminal device 101, whether OCCs for transmitting the MSG 3 225 and for transmitting the MSG 1 are adjusted to the same, and based on the OCCs for transmitting the MSG 3 225 and for transmitting the MSG 1 failing to be adjusted to the same, indicates the first configuration information in the at least one of the DCI 205 or the RAR 215.
  • the at least one of the DCI 205 or the RAR 215 comprises the first configuration information.
  • the network may change or reconfigure OCC for the MSG 3 225 by indicating the difference between OCCs for transmitting the MSG 3 225 and for transmitting the MSG 1, or a new absolute value of the OCC for transmitting the MSG 3 225, or the mapping rule, etc.
  • the network device 103 may check if OCCs for (N) PRACH and (N) PUSCH can be adjusted such that same occ can be used. If not, the network device 103 may indicates the first configuration information above.
  • the terminal device 101 may transmit (212) , based on the first configuration information, the MSG 3 225 to the network device 103.
  • the network device 103 may receive (214) the MSG 3 225 from the terminal device 101.
  • a solution on how the network device can signal the OCC code for the transmission of the MSG 3 is proposed for uplink capacity enhancement, thereby improving communication performance.
  • the solution is about OCC for the MSG 3.
  • An indication i.e. the first configuration information
  • the network device 103 may configure that the “mod OCC length” or “TC-RNTI mod (OCC length+1) ” function is applied to a plurality of the TC-RNTIs.
  • a TC-RNTI configured for the terminal device 101 may be one of a plurality of TC-RNTIs, and a mapping rule of TC-RNTI mapping to the OCC in the configuration 305 may be applicable for the plurality of TC-RNTIs.
  • the network device 103 may configure that the “TC-RNTI mod OCC length” or “TC-RNTI mod (OCC length+1) ” function is only applied to a subset of the TC-RNTIs.
  • the terminal device 101 may transmit (306) a random access preamble 315, and the network device 103 may receive (308) the random access preamble 315.
  • the network device 103 may transmit (310) a DCI 325 scheduling a random access response (RAR) 335.
  • the terminal device 101 may receive (312) the DCI 325.
  • the network device 103 may transmit (314) the RAR 335 including a MSG 3 scheduling grant and the TC-RNTI.
  • the TC-RNTI may be configured by the network device 103.
  • the terminal device 101 may receive (316) the random access response 335.
  • Fig. 4 illustrates another example process for OCC configuration for random access MSG 3 according to some embodiments of the present disclosure.
  • the terminal device 101 may be a UE.
  • the network device 103 (may be referred to as network) may be an eNB.
  • the terminal device 101 may transmit (402) a random access preamble 405, and the network device 103 may receive (404) the random access preamble 405.
  • the network device 103 may transmit (406) a DCI 415 scheduling a random access response (RAR) 425.
  • the DCI 415 includes indication of OCC for MSG 3 435.
  • the terminal device 101 may receive (408) the DCI 415.
  • one or more reserved bits in the DCI 415 may be used for indicate the OCC.
  • the objective defines multiplexing of at least 4 UEs, i.e. at least 4 OCCs are needed, this corresponds to 2 bits.
  • a flag is needed to indicate whether OCC is even to be used or not, there are 3 bits are needed for the example above.
  • the network device 103 may transmit (410) the RAR 425 including a MSG 3 scheduling grant.
  • the terminal device 101 may receive (412) the RAR 425.
  • the terminal device 101 may determine (414) the OCC to be applied on the MSG 3 435.
  • the terminal device 101 may transmit (416) the MSG 3 435 using the indicated OCC.
  • the network device 103 may receive (418) the MSG 3 435.
  • the first TC-RNTI mapped to an index of a first OCC among a plurality of OCCs indicates that the first OCC is to be applied for the transmission of the MSG 3.
  • the first TC-RNTI mapped to a value different from an index of an OCC among the plurality of OCCs indicates that no OCC is to be applied for the transmission of the MSG 3.
  • the mapping rule is applicable for a plurality of TC-RNTIs.
  • the mapping rule is applicable for at least one TC-RNTI in one of a plurality of value ranges of the plurality of TC-RNTIs.
  • the OCC length or the number of the plurality of OCCs is indicated in the DCI or predetermined.
  • the mapping rule is configured by the network device or predetermined.
  • the first configuration information is carried in at least one second bit in the DCI indicating whether an OCC is to be applied for the transmission of the MSG 3.
  • the terminal device may receive, from the network device, second configuration information indicating whether an OCC is to be applied for the transmission of a message 1 (MSG 1) , wherein the second configuration information is further used for indicating whether an OCC is applied for transmission of the MSG 3.
  • MSG 1 message 1
  • the terminal device may receive, from the network device, third configuration information associated with an OCC for transmitting an MSG 1, wherein the OCC for transmitting the MSG 1 is different from the OCC for transmitting the MSG 3.
  • the first configuration information is determined based on a difference between OCCs for transmitting the MSG 3 and for transmitting an MSG 1, wherein the difference is indicated in the at least one of the DCI or the RAR.
  • the at least one of the DCI or the RAR comprises the first configuration information: OCCs for transmitting the MSG 3 and for transmitting an MSG 1 are different; or OCCs for transmitting the MSG 3 and for transmitting the MSG 1 fail to be adjusted to the same.
  • the DCI is received in a time resource and a frequency resource. At least one first bit in the DCI and at least one of the time resource or the frequency resource indicate an index of a first OCC to be applied for the transmission of the MSG 3.
  • the network device may transmit, to the terminal device, downlink control information (DCI) for scheduling a random access response (RAR) .
  • DCI downlink control information
  • RAR random access response
  • the network device may transmit the RAR to the terminal device based on the DCI, in which at least one of the DCI or the RAR comprises first configuration information associated with an orthogonal cover code (OCC) for transmitting a message 3 (MSG 3) .
  • the network device may receive, from the terminal device, the MSG 3 based on the first configuration information.
  • the first configuration information is determined based on a first TC-RNTI in the RAR, an OCC length or a number of a plurality of OCCs, and a mapping rule from a TC-RNTI to an index of an OCC.
  • the mapping rule is applicable for a plurality of TC-RNTIs, or the mapping rule is applicable for at least one TC-RNTI in one of a plurality of value ranges of the plurality of TC-RNTIs.
  • the mapping rule indicates that an OCC index is based on a TC-RNTI and at least one of the following: the OCC length, the number of the plurality of OCCs, the OCC length plus 1, or the number of the plurality of OCCs plus 1.
  • the network device may indicate, in the DCI and to the terminal device, the OCC length or the number of the plurality of OCCs.
  • the network device may transmit, to the terminal device, second configuration information indicating whether an OCC is to be applied for the transmission of the a message 1 (MSG 1) .
  • the second configuration information may be further used for indicating whether an OCC is applied for transmission of the MSG 3.
  • the network device may transmit, to the terminal device, third configuration information associated with an OCC for transmitting an MSG 1.
  • the OCC for transmitting the MSG 1 may be different from the OCC for transmitting the MSG 3.
  • the network device may check, after receiving an MSG 1 from the terminal device, whether OCCs for transmitting the MSG 3 and for transmitting an MSG 1 are different. Based on the OCCs for transmitting the MSG 3 and for transmitting the MSG 1 being different, the network device may indicate the first configuration information in the at least one of the DCI or the RAR.
  • the first configuration information is determined based on a difference between OCCs for transmitting the MSG 3 and for transmitting an MSG 1.
  • the difference may be indicated in the at least one of the DCI or the RAR.
  • the DCI is transmitted in a time resource and a frequency resource. At least one first bit in the DCI and at least one of the time resource or the frequency resource indicate an index of a first OCC to be applied for the transmission of the MSG 3.
  • an apparatus capable of performing any of the method 500 may comprise means for performing the respective steps of the method 500.
  • the means may be implemented in any suitable form.
  • the means may be implemented in a circuitry or software module.
  • the apparatus comprises means for receiving, from a network device, downlink control information (DCI) for scheduling a random access response (RAR) ; means for receiving the RAR from the network device based on the DCI, in which at least one of the DCI or the RAR comprises first configuration information associated with an orthogonal cover code (OCC) for transmitting a message 3 (MSG 3) ; and means for transmitting, based on the first configuration information, the MSG 3 to the network device.
  • DCI downlink control information
  • RAR random access response
  • OCC orthogonal cover code
  • the first configuration information may be carried in a first temporary connected radio network temporary identifier (TC-RNTI) in the RAR, or a set of bits in the DCI, or the combination thereof.
  • TC-RNTI first temporary connected radio network temporary identifier
  • the first configuration information is determined based on a first TC-RNTI in the RAR, an OCC length or a number of a plurality of OCCs, and a mapping rule from a TC-RNTI to an index of an OCC.
  • the first TC-RNTI mapped to an index of a first OCC among a plurality of OCCs indicates that the first OCC is to be applied for the transmission of the MSG 3.
  • the first TC-RNTI mapped to a value different from an index of an OCC among the plurality of OCCs indicates that no OCC is to be applied for the transmission of the MSG 3.
  • the mapping rule is applicable for a plurality of TC-RNTIs, or the mapping rule is applicable for at least one TC-RNTI in one of a plurality of value ranges of the plurality of TC-RNTIs.
  • the mapping rule is configured by the network device or predetermined.
  • the first configuration information is carried in at least one first bit in the DCI indicating an index of a first OCC to be applied for the transmission of the MSG 3.
  • the first configuration information is carried in at least one second bit in the DCI indicating whether an OCC is to be applied for the transmission of the MSG 3.
  • the apparatus further comprises means for receiving, from the network device, second configuration information indicating whether an OCC is to be applied for the transmission of a message 1 (MSG 1) , in which the second configuration information is further used for indicating whether an OCC is applied for transmission of the MSG 3.
  • MSG 1 message 1
  • the apparatus further comprises means for receiving, from the network device, third configuration information associated with an OCC for transmitting an MSG 1, in which the OCC for transmitting the MSG 1 is different from the OCC for transmitting the MSG 3.
  • the first configuration information is determined based on a difference between OCCs for transmitting the MSG 3 and for transmitting an MSG 1.
  • the difference is indicated in the at least one of the DCI or the RAR.
  • the DCI and/or the RAR comprises the first configuration information: OCCs for transmitting the MSG 3 and for transmitting an MSG 1 are different; or OCCs for transmitting the MSG 3 and for transmitting the MSG 1 fail to be adjusted to the same.
  • the apparatus further comprises means for performing other steps in some embodiments of the method 500.
  • the means comprises at least one processor; and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus.
  • an apparatus capable of performing any of the method 600 may comprise means for performing the respective steps of the method 600.
  • the means may be implemented in any suitable form.
  • the means may be implemented in a circuitry or software module.
  • the first configuration information comprises: an index of a first OCC among a plurality of OCCs, wherein the first OCC is to be applied for the transmission of the MSG 3; or an indication that no OCC is to be applied for the transmission of the MSG 3.
  • the first configuration information is carried in a first temporary connected radio network temporary identifier (TC-RNTI) in the RAR, or a set of bits in the DCI, or the combination thereof.
  • TC-RNTI first temporary connected radio network temporary identifier
  • the first TC-RNTI which is not in one of a plurality of value ranges of a plurality of TC-RNTIs indicates that no OCC is to be applied for the transmission of the MSG 3, wherein the mapping rule is applicable for at least one TC-RNTI in the one of the plurality of value ranges of the plurality of TC-RNTIs.
  • the apparatus further comprises means for transmitting, to the terminal device, second configuration information indicating whether an OCC is to be applied for the transmission of the a message 1 (MSG 1) , in which the second configuration information is further used for indicating whether an OCC is applied for transmission of the MSG 3.
  • MSG 1 message 1
  • the apparatus further comprises means for transmitting, to the terminal device, third configuration information associated with an OCC for transmitting an MSG 1, in which the OCC for transmitting the MSG 1 is different from the OCC for transmitting the MSG 3.
  • the DCI is transmitted in a time resource and a frequency resource. At least one first bit in the DCI and at least one of the time resource or the frequency resource indicate an index of a first OCC to be applied for the transmission of the MSG 3.
  • the processor 710 may be of any type suitable to the local technical network and may include one or more of the following: general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples.
  • the device 700 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.
  • the memory 720 may include one or more non-volatile memories and one or more volatile memories.
  • the non-volatile memories include, but are not limited to, a Read Only Memory (ROM) 724, an electrically programmable read only memory (EPROM) , a flash memory, a hard disk, a compact disc (CD) , a digital video disk (DVD) , and other magnetic storage and/or optical storage.
  • the volatile memories include, but are not limited to, a random access memory (RAM) 722 and other volatile memories that will not last in the power-down duration.
  • the present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium.
  • the computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor, to carry out the method 500 or 600 as described above with reference to Figs. 2-6.
  • program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types.
  • the functionality of the program modules may be combined or split between program modules as desired in various embodiments.
  • Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.
  • Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowcharts and/or block diagrams to be implemented.
  • the program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
  • the computer program codes or related data may be carried by any suitable carrier to enable the device, apparatus or processor to perform various processes and operations as described above.
  • Examples of the carrier include a signal, computer readable medium, and the like.
  • the computer readable medium may be a computer readable signal medium or a computer readable storage medium.
  • a computer readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the computer readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
  • non-transitory is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM) .

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Des modes de réalisation de la présente divulgation concernent une configuration de code de couverture orthogonale (OCC) pour un MSG 3 d'accès aléatoire. Selon un aspect, un équipement terminal reçoit, en provenance d'un dispositif de réseau, des informations de commande de liaison descendante (DCI) pour planifier une réponse d'accès aléatoire (RAR). L'équipement terminal reçoit la RAR en provenance du dispositif de réseau sur la base des DCI. Au moins l'une des DCI ou de la RAR comprend de premières informations de configuration associées à un code de couverture orthogonal (OCC) pour émettre un message 3 (MSG 3). L'équipement terminal émet, sur la base des premières informations de configuration, le MSG 3 vers le dispositif de réseau. Par conséquent, une solution sur la manière dont le dispositif de réseau peut signaler le code OCC pour l'émission de message (MSG) 3 est proposée pour une amélioration de capacité de liaison montante, ce qui permet d'améliorer les performances de communication.
PCT/CN2024/086098 2024-04-03 2024-04-03 Configuration de code de couverture orthogonale pour message 3 Pending WO2025208515A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/086098 WO2025208515A1 (fr) 2024-04-03 2024-04-03 Configuration de code de couverture orthogonale pour message 3

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/086098 WO2025208515A1 (fr) 2024-04-03 2024-04-03 Configuration de code de couverture orthogonale pour message 3

Publications (1)

Publication Number Publication Date
WO2025208515A1 true WO2025208515A1 (fr) 2025-10-09

Family

ID=97265979

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/086098 Pending WO2025208515A1 (fr) 2024-04-03 2024-04-03 Configuration de code de couverture orthogonale pour message 3

Country Status (1)

Country Link
WO (1) WO2025208515A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107466113A (zh) * 2016-06-03 2017-12-12 北京佰才邦技术有限公司 一种Msg3传输方法、装置和相关设备
WO2018174577A1 (fr) * 2017-03-22 2018-09-27 엘지전자 주식회사 Procédé de réalisation d'une procédure d'accès aléatoire et appareil associé
CN111357380A (zh) * 2017-11-17 2020-06-30 瑞典爱立信有限公司 与无线通信中的随机接入相关的改进
US20220248477A1 (en) * 2021-02-01 2022-08-04 Qualcomm Incorporated Random access channel message repetition indication for retransmission
US20230319893A1 (en) * 2020-12-04 2023-10-05 Vivo Mobile Communication Co., Ltd. Random access method and apparatus, terminal, and network side device

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107466113A (zh) * 2016-06-03 2017-12-12 北京佰才邦技术有限公司 一种Msg3传输方法、装置和相关设备
WO2018174577A1 (fr) * 2017-03-22 2018-09-27 엘지전자 주식회사 Procédé de réalisation d'une procédure d'accès aléatoire et appareil associé
CN111357380A (zh) * 2017-11-17 2020-06-30 瑞典爱立信有限公司 与无线通信中的随机接入相关的改进
US20230319893A1 (en) * 2020-12-04 2023-10-05 Vivo Mobile Communication Co., Ltd. Random access method and apparatus, terminal, and network side device
US20220248477A1 (en) * 2021-02-01 2022-08-04 Qualcomm Incorporated Random access channel message repetition indication for retransmission

Similar Documents

Publication Publication Date Title
US9642161B2 (en) Cross-scheduling for random access response
US20210160866A1 (en) Time domain resource allocation for pusch transmission
US20100322096A1 (en) Method of improving component carrier identification in a random access procedure in a wireless communication system and related communication device
US11917614B2 (en) Uplink control information transmission method and apparatus
EP3573402B1 (fr) Procédé de communication et terminal
EP2745600A1 (fr) Procédés, dispositifs et systèmes d'émission et de réception d'ordres d'accès aléatoire en programmation croisée
US12022523B2 (en) Mechanism for first random access mode falling back to second random access mode
US20250133601A1 (en) Method of transmission with repetition, terminal device and network device
WO2025208515A1 (fr) Configuration de code de couverture orthogonale pour message 3
EP4661577A1 (fr) Procédé de communication sans fil, dispositif terminal et dispositif de réseau
WO2023065249A1 (fr) Accès aléatoire à une cellule secondaire
US12082262B2 (en) Mechanism for providing multiple transmission opportunities
WO2025208585A1 (fr) Réponse d'accès aléatoire avec code de couverture orthogonal utilisé
WO2025208584A1 (fr) Réponse d'accès aléatoire avec un code de couverture orthogonal utilisé
WO2021056462A1 (fr) Terminaison de fenêtre de surveillance dans une procédure d'accès aléatoire
WO2025217838A1 (fr) Configuration basée sur rar pour msg4
WO2024229783A1 (fr) Format de préambule prach dans sbfd
US12107792B2 (en) Bit reduction in resource information
WO2025217835A1 (fr) Attribution de ressources pour message
US12495449B2 (en) Determination for uplink repetitions
WO2025208565A1 (fr) Attribution de c-rnti
WO2024207161A1 (fr) Transmission de signal de référence de sondage
WO2024207324A1 (fr) Indication de type de dispositif
WO2025091455A1 (fr) Amélioration de message 3
US20240179657A1 (en) Acquiring timing advance value

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24933468

Country of ref document: EP

Kind code of ref document: A1