[go: up one dir, main page]

WO2025171665A1 - Configuration de code de couverture orthogonale pour transmissions de canal physique partagé montant associées à un canal d'accès aléatoire - Google Patents

Configuration de code de couverture orthogonale pour transmissions de canal physique partagé montant associées à un canal d'accès aléatoire

Info

Publication number
WO2025171665A1
WO2025171665A1 PCT/CN2024/077455 CN2024077455W WO2025171665A1 WO 2025171665 A1 WO2025171665 A1 WO 2025171665A1 CN 2024077455 W CN2024077455 W CN 2024077455W WO 2025171665 A1 WO2025171665 A1 WO 2025171665A1
Authority
WO
WIPO (PCT)
Prior art keywords
occ
rach
sequence
spreading
baseband processor
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/077455
Other languages
English (en)
Inventor
Chunxuan Ye
Hong He
Sigen Ye
Chunhai Yao
Dawei Zhang
Yuqin Chen
Wei Zeng
Huaning Niu
Ankit Bhamri
Fangli Xu
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.)
Apple Inc
Original Assignee
Apple Inc
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 Apple Inc filed Critical Apple Inc
Priority to PCT/CN2024/077455 priority Critical patent/WO2025171665A1/fr
Publication of WO2025171665A1 publication Critical patent/WO2025171665A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J13/00—Code division multiplex systems
    • H04J13/16—Code allocation
    • H04J13/18—Allocation of orthogonal codes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J13/00—Code division multiplex systems
    • H04J13/0003—Code application, i.e. aspects relating to how codes are applied to form multiplexed channels
    • 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

Definitions

  • This disclosure relates to wireless communication networks including techniques for improving network performance using orthogonal cover codes (OCCs) .
  • OCCs orthogonal cover codes
  • wireless communication networks may be developed to implement fifth generation (5G) or new radio (NR) technology, sixth generation (6G) technology, and so on.
  • 5G fifth generation
  • NR new radio
  • 6G sixth generation
  • An aspect of such technology includes addressing how communication techniques may be extended as radio network components are implemented in non-terrestrial platforms.
  • FIG. 1 is a diagram of an example non-terrestrial network (NTN) .
  • NTN non-terrestrial network
  • FIGs. 2A and 2B are message flow diagrams outlining a 4-step random access channel (RACH) process and a 2-step RACH process, respectively.
  • RACH random access channel
  • FIG. 3A illustrates a media access control (MAC) random access response (RAR) subheader that indicates an OCC index, according to various aspects disclosed.
  • MAC media access control
  • RAR random access response
  • FIG. 3B illustrates a MAC RAR payload that includes OCC information, according to various aspects disclosed.
  • FIG. 4 is a flow diagram of an example method that may be performed by a user equipment (UE) for transmitting a RACH-related PUSCH in a 4-step RACH process with contention-based orthogonal cover code (OCC) spreading, according to various aspects disclosed.
  • UE user equipment
  • OCC contention-based orthogonal cover code
  • FIG. 5 is a flow diagram of an example method that may be performed by a user equipment (UE) for transmitting a RACH-related PUSCH in a 2-step RACH process with contention-based orthogonal cover code (OCC) spreading, according to various aspects disclosed.
  • UE user equipment
  • OCC contention-based orthogonal cover code
  • FIG. 5A illustrates a MAC successRAR subheader that indicates an OCC index, according to various aspects disclosed.
  • FIG. 6 illustrates an example of intra-slot OCC spreading without repetition increase due to OCC coding, in accordance with various aspects disclosed.
  • FIGs. 7A, 7B, 7C illustrate examples of intra-slot OCC spreading with repetition increase due to OCC coding, in accordance with various aspects disclosed.
  • FIGs. 8A, 8B, 8C, 8D illustrate examples of inter-slot OCC spreading with repetition increase due to OCC coding, in accordance with various aspects disclosed.
  • FIG. 9 is a flow diagram of an example method that may be performed by a base station for configuring and/or receiving a RACH-related PUSCH with OCC spreading, according to various aspects disclosed.
  • the UE sends a RACH-related message that includes physical uplink shared channel (PUSCH) transmission that may include uplink (UL) data, a request, or other information.
  • PUSCH physical uplink shared channel
  • the area covered by an NTN cell may be on the order of millions of square kilometers and likely will encompass many more UEs than typical land networks.
  • enhancements to the RACH process that enable multiple UEs to utilize the same or similar time/frequency resources for transmitting RACH-related PUSCH will improve the performance of NTN communication.
  • FIG. 2A illustrates an example 4-step RACH process 210.
  • the UE transmits Msgl which includes a PRACH preamble that serves to identify the UE.
  • Msgl which includes a PRACH preamble that serves to identify the UE.
  • the UE randomly selects the preamble from a set of configured candidate preambles.
  • contention-free RACH the preamble and optionally also dedicated PRACH resources are configured to the UE when the UE enters the INACTIVE or IDLE state.
  • the base station transmits Msg4.
  • Msg4 includes an indication as to whether the RACH process was successful or not and also indicates a cell RNTI (C-RNTI) for use in subsequent communication.
  • C-RNTI may be the TC-RNTI included in the payload of Msg2 and used to scramble Msg3, when the TC-RNTIs associated with these messages match.
  • the UE may send a hybrid automatic repeat request (HARQ) acknowledgement (ACK) message to the base station.
  • HARQ hybrid automatic repeat request
  • ACK hybrid automatic repeat request acknowledgement
  • the UE does not receive Msg4 before the timer expires the UE assumes that the RACH process was not successful and will not transmit HARQ-ACK and may initiate another RACH attempt.
  • FIG. 2B illustrates a two step RACH process 260.
  • the 2-step RACH process may be selected over the 4-step process when latency is a concern, a cell is geographically compact so that timing advance is not as important to decoding UL transmissions, and/or the likelihood of collisions is relatively small.
  • the UE transmits MsgA which includes the information sent in Msg1 and Msg3 of the 4 step RACH process of FIG. 5A.
  • MsgA includes the PRACH preamble (either randomly selected or preconfigured to the UE) and is transmitted using the RO associated with a selected SSB as described with reference to FIG. 2A.
  • MsgA also includes the RACH-related PUSCH.
  • MsgA PUSCH is scrambled based on RA-RNTI, the preamble ID (RAPID) , and the current cell ID.
  • the base station transmits MsgB which includes DCI scrambled based on MsgB-RNTI that schedules MsgB PDSCH.
  • the MsgB PDSCH may include a fallbackRAR media access control sub protocol data unit (MAC subPDU) that includes an uplink grant for the UE to re-transmit MsgA when the base station detects MsgA but cannot decode it. If the base station successfully decodes MsgA, MsgB PDSCH includes a successRAR MAC subPDU that indicates a C-RNTI for use by the UE in subsequent communication.
  • MAC subPDU media access control sub protocol data unit
  • Msg3/MsgA may be significant and throughput and performance, especially in an NTN or crowded land network, may be compromised when only a single UE may utilize certain PRACH resources at a time.
  • Code division multiple access is a technique that is used to allow multiple UEs to communicate with a base station using the same time/frequency resources.
  • an orthogonal cover code may be used to “spread” bits encoding transmissions to generate discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-s-OFDM) based waveforms.
  • An OCC is defined by a code length and includes a set of unique code sequences.
  • the code sequences comprise an ordered series of values that are applied to (e.g., multiply) consecutive modulation symbols before DFT operations in the frequency domain (FD-OCC) or (pre-DFT OCC) , consecutive symbols in a slot (intra-slot OCC) , or across multiple consecutive slots (inter-slot OCC) in which all symbols in a slot are coded by the same code value in the sequence of code values.
  • the coding results in a waveform that is orthogonal in either frequency (FD-OCC) or time (intra-slot or inter-slot OCC) to other waveforms generated based on other sequences in the OCC.
  • repetitions for Msg3 PUSCH may be configured in which the UE repeats the PUSCH portion of Msg3 in a subsequent slot.
  • additional repetitions may be encoded according to a different redundancy version (RV) in which bits encoding the Msg3 PUSCH are placed in a circular buffer and a different starting point in the circular buffer is used to select a sequence of bits for transmission in a given repetition.
  • RV redundancy version
  • a sequence of RVs (e.g., RV 0, RV 2, RV 3, RV 1) may be preconfigured for use in a cyclic manner in Msg3 PUSCH repetition.
  • Described herein are systems, methods, and circuitries that provide techniques for supporting OCC for RACH-related PUSCH, such as PUSCH associated with Msg3 and/or MsgA.
  • signaling solutions are presented for configuration and/or selection of OCC sequence and length as well as different mechanisms for coding RACH-related PUSCH with respect to, for example, retransmissions, repetitions, and RVs.
  • OCC e.g., OCC sequence identifier or index and sequence length
  • the OCC sequence may be assigned or pre-confirmed to the UE by the network (dedicated OCC) or the UE may select an OCC sequence (contention-based OCC) .
  • the UE receives confirmation from the network of the OCC sequence the UE selected to spread the RACH-related PUSCH to indicate that no collision has occurred.
  • FIG. 3 is a flow diagram outlining an example method 300 that may be performed by a UE to transmit a RACH-related PUSCH with OCC spreading.
  • the method includes, at 310, receiving network configuration that includes OCC configuration.
  • the network configuration may be made by way of a system information block 1 (SIB1) or other SIBs.
  • SIB1 system information block 1
  • the OCC configuration may include an OCC length and an OCC spreading scheme (e.g., FD-OCC, intra-slot OCC, or inter-slot OCC) .
  • the OCC configuration may also provide an association between certain PRACH preambles and/or ROs and a UE's capability for OCC for RACH-related PUSCH.
  • certain of the PRACH preambles may be dedicated for use by UEs with the capability to perform OCC spreading of PRACH-related PUSCH.
  • the network configuration received at 310 may also configure PRACH preambles and/or ROs for UEs capable ofMsg3 PUSCH repetition.
  • the set of dedicated PRACH preambles dedicated for OCC-capable UE may be identical to the set of PRACH preambles dedicated to UEs capable of Msg3 repetition.
  • the set of dedicated PRACH preambles for OCC-capable UE may a subset of the set of PRACH preambles dedicated to UEs capable of Msg3 repetition.
  • the set of dedicated PRACH preambles for OCC-capable UE may be different from the set of PRACH preambles dedicated to UEs capable of Msg3 repetition.
  • the set of dedicated PRACH preambles for OCC-capable UE may replace the set of PRACH preambles dedicated to UEs capable of Msg3 repetition.
  • the UE selects one of the dedicated PRACH preambles and/or RO based on its OCC capability and transmits Msgl, including the PRACH preamble.
  • the UE receives Msg2 which includes the RAR.
  • Msg2 may include an explicit configuration of the OCC sequence to be used by the UE for spreading Msg3 PUSCH.
  • the explicit OCC configuration may indicate an OCC sequence identifier or index and/or an OCC length.
  • the DCI format 1_0 of Msg2 which is scrambled based on RA-RNTI, includes bits encoding the OCC sequence identifier or index and/or the OCC sequence length.
  • the bits may be part of reserved or unused bits of the DCI format 1_0.
  • Msg2 does not include an explicit indication of OCC information.
  • the Msg2 may include an indication that OCC spreading for RACH-related PUSCH is supported without an indication of a particular OCC sequence or no information related to OCC.
  • the UE and network independently determine the OCC sequence index as a function of some parameter known to both the UE and the network such as the PRACH preamble ID, TC-RNTI of the UE, or temporary mobile subscriber identity (TMSI) of the UE, and so on, for which the UE has received confirmation based on successfully decoding Msg2.
  • the OCC sequence index may be determined based on (preamble ID) mod (configured OCC length) .
  • the UE transmits Msg3 PUSCH with OCC spreading based on the dedicated OCC information (either explicitly indicated in Msg2 or derived based on information confirmed in Msg2) . More details related to OCC spreading of Msg3 PUSCH transmission are provided below with reference to FIGs. 6-8D.
  • Msg4 contention information does not need to contain confirmation of the OCC used in Msg3.
  • FIG. 4 is a flow diagram outlining an example method 400 that may be performed by a UE to transmit a RACH-related PUSCH with OCC spreading in a 4-step RACH process.
  • the method includes, at 410, receiving network configuration that includes OCC configuration.
  • the network configuration may be made by way of a system information block 1 (SIB1) or other SIBs.
  • SIB1 system information block 1
  • the OCC configuration may include an OCC length and an OCC spreading scheme (e.g., FD-OCC, intra-slot OCC, or inter-slot OCC) .
  • the OCC configuration may also provide an association between certain PRACH preambles and/or ROs and OCC for RACH-related PUSCH.
  • certain of the PRACH preambles may be dedicated for use by UEs with the capability to perform OCC spreading of PRACH-related PUSCH.
  • the OCC configuration may also include a set of candidate OCC sequences from which an OCC sequence will be selected or indicated.
  • the network configuration received at 410 may also configure PRACH preambles dedicated for UEs capable ofMsg3 PUSCH repetition.
  • the set of dedicated PRACH preambles for OCC-capable UE may be identical to the set of PRACH preambles dedicated to UEs capable of Msg3 repetition.
  • the set of dedicated PRACH preambles for OCC-capable UE may a subset of the set of PRACH preambles dedicated to UEs capable of Msg3 repetition.
  • the set of dedicated PRACH preambles for OCC-capable UE may different from the set of PRACH preambles dedicated to UEs capable of Msg3 repetition.
  • the set of dedicated PRACH preambles for OCC-capable UE may replace the set of PRACH preambles dedicated to UEs capable of Msg3 repetition.
  • the DCI format 1_0 of Msg2 which is scrambled based on RA-RNTI, includes bit that indicates whether or not contention-based OCC spreading is enabled.
  • the bit may be part of reserved or unused bits of the DCI format 1 0.
  • a sub-header of a MAC RAR carried by PDSCH scheduled by the DCI format 1_0 includes a bit that indicates whether or not contention-based OCC spreading is enabled.
  • the MAC RAR payload includes a bit that indicates whether or not contention-based OCC spreading is enabled.
  • a new MAC RAR is configured with OCC information and this MAC RAR with OCC information includes a bit that indicates whether or not contention-based OCC spreading is enabled.
  • a bit of a UL grant field in the MAC RAR is repurposed to indicate whether or not contention-based OCC spreading is enabled. For example, one bit of the modulation coding scheme (MCS) field of the UL grant in the MAC RAR may be repurposed to indicate whether or not contention-based OCC spreading is enabled.
  • MCS modulation coding scheme
  • the UE transmits Msg3 PUSCH with OCC spreading based on a randomly selected OCC sequence and a selected OCC length.
  • One or more candidate OCC lengths may be configured by network configuration in step 410. If a single candidate OCC length is configured in step 410, then the UE selects this OCC length. Ifmultiple candidate OCC lengths are configured, the UE may select one of the candidate OCC lengths. In some examples, the UE selects the OCC length based on a configured Msg3 PUSCH repetition number. For example, if Msg2 indicates that the Msg3 PUSCH repetition number is 2, then the UE may select an OCC length of 2. More details related to OCC spreading of Msg3 PUSCH transmission are provided below with reference to FIGs. 6-8D.
  • the UE receives Msg4.
  • Msg4 is configured by the network based on a detected OCC sequence for the Msg3 PUSCH.
  • Msg4 explicitly indicates the detected OCC sequence.
  • the explicit indication may be in the payload of the DCI format 1_0 in Msg4 that schedules Msg4 PDSCH and is scrambled based on TC-RNTI.
  • bits in the Downlink Assignment Index field of the DCI format may be repurposed to carry the indication of the OCC sequence of the detected OCC sequence.
  • the indication of the detected OCC sequence is carried in the payload of the Msg4 PDSCH.
  • This indication in the Msg3 PDSCH may be configured by way of a MAC CE or RRC configuration to include an explicit indication of the detected OCC sequence.
  • the Msg3 PDSCH may be configured by way of a MAC CE or RRC configuration to indicated the UE's ID (e.g., TMSI, RRC Connection Resume ID0, or other ID) in Msg4.
  • the UE ID serves as confirmation that the spread Msg3 PUSCH was decoded without collision with another UE Msg3 PUSCH.
  • the search space for Msg4 PDCCH (DCI) is dependent on the OCC sequence used to spread the Msg3 PUSCH. Ifno Msg4 PDCCH is detected, then the UE may assume that a collision has occurred.
  • the UE transmits Msg4 HARQ-ACK indicating that the detected OCC indicated through Msg4 matches the OCC selected at 440. If the detected OCC does not match the selected OCC, the UE may attempt another RACH process at 420.
  • FIG. 5 is a flow diagram outlining an example method 500 that may be performed by a UE to transmit a RACH-related PUSCH with OCC spreading in a 2-step RACH process.
  • the method includes, at 510, receiving network configuration that includes OCC configuration.
  • the network configuration may be made by way of a system information block 1 (SIB1) or other SIBs.
  • SIB1 system information block 1
  • the OCC configuration may include an OCC length and an OCC spreading scheme (e.g., FD-OCC, intra-slot OCC, or inter-slot OCC) .
  • the OCC configuration may also provide an association between certain PRACH preambles and/or ROs and OCC for RACH-related PUSCH.
  • certain of the PRACH preambles may be dedicated for use by UEs with the capability to perform OCC spreading of PRACH-related PUSCH.
  • the OCC configuration may also include a set of candidate OCC sequences from which an OCC sequence will be selected or indicated.
  • the UE selects one of the dedicated PRACH preambles and/or RO and an OCC sequence.
  • the UE may select the OCC sequence randomly from amongst configured candidate OCC sequences or select an OCC associated by preconfiguration with the selected PRACH preamble ID.
  • the OCC sequence index may be derived based on (preamble ID) mod (configured OCC length) .
  • the UE transmits MsgA including PUSCH spread based on the selected OCC sequence. More details related to OCC spreading ofMsgA PUSCH transmission are provided below with reference to FIGs. 6-8D.
  • the DCI format 1_0 of MsgB which is scrambled based on MsgB-RNTI, includes bits encoding the detected OCC sequence identifier or index and/or the OCC sequence length.
  • the bits may be part of reserved or unused bits of the DCI format 1 0.
  • a sub-header of a MAC successRAR or fallbackRAR carried by physical downlink shared channel (PDSCH) scheduled by the DCI format 1_0 includes one or more octets that carry the detected OCC information such as a sequence index 532 as shown by MAC successRAR sub-header 530' of FIG. 5A.
  • the MAC successRAR or fallback RAR payload includes one or more octets that carry detected OCC information.
  • a new MAC successRAR 530” is configured with detected OCC information 534 as shown in FIG. 5B (or new fallbackRAR not shown) .
  • bits of a UL grant field in the MAC successRAR or fallbackRAR are repurposed to indicate detected OCC information.
  • the UE transmits MsgB HARQ-ACK indicating that the detected OCC indicated in MsgB matches the OCC selected at 520. If the detected OCC does not match the selected OCC, the UE may attempt another RACH process at 420.
  • FIG. 6 illustrates a slot in which OCC spreading based on an OCC sequence [1, -1] (of length 2) reduces the number of OFDM symbols that could be communicated without coding from 14 to 7. It can be seen that the slot includes, for each original OFDM symbol S (n) , a corresponding -S (n) .
  • S (n) is the result of the first sequence value (1) multiplied by the original OFDM symbol.
  • -S (n) is the result of the second sequence value (-1) multiplied by the original OFDM symbol.
  • S2 and -S2 carry demodulation reference symbols (DMRS) and are placed near the beginning and end of the slot. A similar reduction in RBs occurs in FD-OCC without additional repetitions due to OCC.
  • the number of OFDM symbols or RBs is increased by a factor of the length of the OCC sequence.
  • the total number of repetitions of the PUSCH is equal to a number of configured repetitions *the OCC sequence length (e.g., 2 in the illustrated example) .
  • FIGs. 7A-7C illustrate various example coding mechanisms or conventions for handling repetitions and RV cycling in intra-slot OCC or FD-OCC, where the sequence values are applied on a per symbol or RB basis as illustrated in FIG. 6.
  • the configured repetition number is 4 and the configured RV cycling sequence is 0, 2, 3, 1.
  • a RACH related PUSCH is spread to a sequence of eight (OCC length 2 *configured repetition number 4) OCC coded slots 710 based on repetition first, RV cycling second.
  • a RACH related PUSCH is spread to a sequence of eight OCC coded slots 720 based on RV cycling first, repetition second.
  • a RACH related PUSCH is spread to a sequence of eight OCC coded slots 730 based on repetition only, without RV cycling.
  • FIGs. 8A-8D illustrate various example coding mechanisms or conventions for handling configured repetitions and RV cycling in inter-slot OCC, where the sequence values are applied on a per slot basis (e.g., all symbols in the each slot have the same coding value applied) .
  • the configured repetition is 2 and the configured RV cycling sequence is 0, 2, 3, 1.
  • a RACH related PUSCH is spread to a sequence of eight OCC coded slots 810 based on OCC spread first, RV cycling second.
  • FIG. 8B a RACH related PUSCH is spread to a sequence of eight OCC coded slots 820 based on RV cycling first, OCC spread second.
  • FIG. 8A a RACH related PUSCH is spread to a sequence of eight OCC coded slots 810 based on OCC spread first, RV cycling second.
  • a RACH related PUSCH is spread to a sequence of eight OCC coded slots 820 based on RV cycling first, OCC spread second.
  • a RACH related PUSCH is spread to a sequence of eight OCC coded slots 830 based on no RV cycling, OCC spread first, repetition second.
  • a RACH related PUSCH is spread to a sequence of eight OCC coded slots 840 based on no RV cycling, repetition first, OCC spread second.
  • FIG. 9 is a flow diagram outlining an example method 900 that may be performed by a base station to configure and/or receive RACH-related PUSCH transmission with OCC spreading.
  • the method includes, at 910, transmitting an indication that orthogonal cover code (OCC) spreading for random access channel (RACH) related physical uplink shared channel (PUSCH) transmissions is supported. Any of the above techniques for indicated dedicated PRACH preambles or ROs for RACH-related PUSCH with OCC spreading may be used.
  • the base station receives a first RACH-related message based on a PRACH preamble or RACH opportunity (RO) .
  • RACH random access channel
  • RO RACH opportunity
  • the PRACH preamble or RO indicates that a user equipment (UE) intends to apply OCC spreading to RACH-related PUSCH transmissions.
  • the first RACH-related message may be, for example, Msg1 or MsgA PRACH.
  • the method includes, at 930, receiving at least one RACH-related PUSCH transmission spread based on a selected OCC.
  • the term identify when used with reference to some entity or value of an entity is to be construed broadly as encompassing any manner of determining the entity or value of the entity.
  • the term identify is to be construed to encompass, for example, receiving and parsing a communication that encodes the entity or a value of the entity.
  • the term identify should be construed to encompass accessing and reading memory (e.g., device queue, lookup table, register, device memory, remote memory, and so on) that stores the entity or value for the entity.
  • the term encode when used with reference to some entity or value of an entity is to be construed broadly as encompassing any manner or technique for generating a data sequence or signal that communicates the entity to another component.
  • the term select when used with reference to some entity or value of an entity is to be construed broadly as encompassing any manner of determining the entity or value of the entity from amongst a plurality or range of possible choices.
  • the term select is to be construed to encompass accessing and reading memory (e.g., lookup table, register, device memory, remote memory, and so on) that stores the entities or values for the entity and returning one entity or entity value from amongst those stored.
  • the term select is to be construed as applying one or more constraints or rules to an input set of parameters to determine an appropriate entity or entity value.
  • the term select is to be construed as broadly encompassing any manner of choosing an entity based on one or more parameters or conditions.
  • the term derive when used with reference to some entity or value of an entity is to be construed broadly. “Derive” should be construed to encompass accessing and reading memory (e.g., lookup table, register, device memory, remote memory, and so on) that stores some initial value or foundational values and performing processing and/or logical/mathematical operations on the value or values to generate the derived entity or value for the entity.
  • the term derive should be construed to encompass computing or calculating the entity or value of the entity based on other quantities or entities.
  • the term derive should be construed to encompass any manner of deducing or identifying an entity or value of the entity.
  • FIG. 10 is an example network 1000 according to one or more implementations described herein.
  • Example network 1000 may include UEs 1010-1, 1010-2, etc. (referred to collectively as “UEs 1010” and individually as “UE 1010” ) , a radio access network (RAN) 1020, a core network (CN) 1030, application servers 1040, and external networks 1050. See also UEs 110 of FIG. 1)
  • UEs 1010-1, 1010-2, etc. referred to collectively as “UEs 1010” and individually as “UE 1010”
  • RAN radio access network
  • CN core network
  • application servers 1040 application servers
  • external networks 1050 See also UEs 110 of FIG. 1
  • an IoT UE may utilize one or more types of technologies, such as machine-to-machine (M2M) communications or machine-type communications (MTC) (e.g., to exchanging data with an MTC server or other device via a public land mobile network (PLMN) ) , proximity-based service (ProSe) or device-to-device (D2D) communications, sensor networks, IoT networks, and more.
  • M2M or MTC exchange of data may be a machine-initiated exchange
  • an IoT network may include interconnecting IoT UEs (which may include uniquely identifiable embedded computing devices within an Internet infrastructure) with short-lived connections.
  • IoT UEs may execute background applications (e.g., keep-alive messages, status updates, etc. ) to facilitate the connections of the IoT network.
  • UEs 1010 may communicate and establish a connection with (e.g., be communicatively coupled) with RAN 1020, which may involve one or more wireless channels 1014-1 and 1014-2, each of which may comprise a physical communications interface /layer.
  • UEs 1010 may use stored RACH-related PUSCH with OCC spreading instructions and information that enable the UE 1010 to spread RACH-related PUSCH as described above with reference to FIGs. 1-8D.
  • a RAN node may be an E-UTRAN Node B (e.g., an enhanced Node B, eNodeB, eNB, 4G base station, etc. ) , a next generation base station (e.g., a 5G base station, NR base station, next generation eNBs (gNB) , etc. ) .
  • RAN nodes 1022 may include a roadside unit (RSU) , a transmission reception point (TRxP or TRP) , and one or more other types of ground stations (e.g., terrestrial access points) .
  • RSU roadside unit
  • TRxP or TRP transmission reception point
  • ground stations e.g., terrestrial access points
  • RAN node 1022 may be a dedicated physical device, such as a macrocell base station, and/or a low power (LP) base station for providing femtocells, picocells or the like having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.
  • LP low power
  • RAN nodes can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell) .
  • satellites 1060 may operate as bases stations with respect to UEs.
  • references herein to a base station, RAN node, etc. may involve implementations where the base station, RAN node, etc., is a terrestrial network node and also to implementation where the base station, RAN node, etc., is a non-terrestrial network node (e.g., satellite 1060) .
  • a RAN node 1022 may store RACH-related PUSCH with OCC spreading instructions and information that enable the RAN node to configure and decode spread RACH-related PUSCH as described above with reference to FIGs. 1-8D.
  • a downlink resource grid may be used for downlink transmissions from any of the RAN nodes 1022 to UEs 1010, and uplink transmissions may utilize similar techniques.
  • the grid may be a time-frequency grid (e.g., a resource grid or time-frequency resource grid) that represents the physical resource for downlink in each slot.
  • a time-frequency grid e.g., a resource grid or time-frequency resource grid
  • Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively.
  • the duration of the resource grid in the time domain corresponds to one slot in a radio frame.
  • the smallest time-frequency unit in a resource grid is denoted as a resource element.
  • Each resource grid comprises resource blocks, which describe the mapping of certain physical channels to resource elements.
  • Each resource block may comprise a collection of resource elements (REs) ; in the frequency domain, this may represent the smallest quantity of resources that currently may be allocated.
  • REs resource elements
  • the RAN nodes 1022 may be configured to communicate with one another via interface 1023.
  • interface 1023 may be an X2 interface.
  • interface 1023 may be an Xn interface.
  • the X2 interface may be defined between two or more RAN nodes 1022 (e.g., two or more eNBs /gNBs or a combination thereof) that connect to evolved packet core (EPC) or CN 1030, or between two eNBs connecting to an EPC.
  • EPC evolved packet core
  • RAN 1020 may be connected (e.g., communicatively coupled) to CN 1030.
  • CN 1030 may comprise a plurality of network elements 1032, which are configured to offer various data and telecommunications services to customers/subscribers (e.g., users of UEs 1010) who are connected to the CN 1030 via the RAN 1020.
  • CN 1030 may include an evolved packet core (EPC) , a 5G CN, and/or one or more additional or alternative types of CNs.
  • EPC evolved packet core
  • the components of the CN 1030 may be implemented in one physical node or separate physical nodes including components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) .
  • the CN may store RACH-related PUSCH with OCC spreading instructions and information that enable the CN to configure RACH-related PUSCH with OCC spreading as described above with reference to FIGs. 1-8D.
  • CN 1030, application servers 1040, and external networks 1050 may be connected to one another via interfaces 1034, 1036, and 1038, which may include IP network interfaces.
  • FIG. 11 is a diagram of an example of components of a network device according to one or more implementations described herein.
  • the device 1100 can include application circuitry 1102, baseband circuitry 1104, RF circuitry 1106, front-end module (FEM) circuitry 1108, one or more antennas 1110, and power management circuitry (PMC) 1112 coupled together at least as shown.
  • the components of the illustrated device 1100 can be included in a UE or a RAN node.
  • the device 1100 can include fewer elements (e.g., a RAN node may not utilize application circuitry 1102, and instead include a processor/controller to process IP data received from a CN or an Evolved Packet Core (EPC) ) .
  • EPC Evolved Packet Core
  • the device 1100 can include additional elements such as, for example, memory/storage, display, camera, sensor (including one or more temperature sensors, such as a single temperature sensor, a plurality of temperature sensors at different locations in device 1100, etc. ) , or input/output (I/O) interface.
  • additional elements such as, for example, memory/storage, display, camera, sensor (including one or more temperature sensors, such as a single temperature sensor, a plurality of temperature sensors at different locations in device 1100, etc. ) , or input/output (I/O) interface.
  • the components described below can be included in more than one device (e.g., said circuitries can be separately included in more than one device for Cloud-RAN (C-RAN) implementations) .
  • C-RAN Cloud-RAN
  • the application circuitry 1102 can include one or more application processors.
  • the application circuitry 1102 can include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the processor (s) can include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc. ) .
  • the processors can be coupled with or can include memory/storage and can be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to run on the device 1100.
  • processors of application circuitry 1102 can process IP data packets received from an EPC.
  • the baseband circuitry 1104 can include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the baseband circuitry 1104 can include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 1106 and to generate baseband signals for a transmit signal path of the RF circuitry 1106.
  • Baseband circuity 1104 can interface with the application circuitry 1102 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 1106.
  • the baseband circuitry 1104 can include a 3G baseband processor 1104A, a 4G baseband processor 1104B, a 5G baseband processor 1104C, or other baseband processor (s) 1104D for other existing generations, generations in development or to be developed in the future (e.g., 5G, 6G, etc. ) .
  • the baseband circuitry 1104 can handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 1106. In other implementations, some or all of the functionality of baseband processors 1104A-D can be included in modules stored in the memory 1104G and executed via a Central Processing Unit (CPU) 1104E. In some implementations, the baseband circuitry 1104 can include one or more audio digital signal processor (s) (DSP) 1104F.
  • DSP audio digital signal processor
  • memory 1104G may store RACH-related PUSCH with OCC spreading instructions and information that enable the device 1100 to transmit or receive RACH-related PUSCH spread using OCC.
  • RF circuitry 1106 can enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium.
  • the RF circuitry 1106 can include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.
  • RF circuitry 1106 can include a receive signal path which can include circuitry to down-convert RF signals received from the FEM circuitry 1108 and provide baseband signals to the baseband circuitry 1104.
  • RF circuitry 1106 can also include a transmit signal path which can include circuitry to up-convert baseband signals provided by the baseband circuitry 1104 and provide RF output signals to the FEM circuitry 1108 for transmission.
  • the receive signal path of the RF circuitry 1106 can include mixer circuitry 1106A, amplifier circuitry 1106B and filter circuitry 1106C.
  • the transmit signal path of the RF circuitry 1106 can include filter circuitry 1106C and mixer circuitry 1106A.
  • RF circuitry 1106 can also include synthesizer circuitry 1106D for synthesizing a frequency for use by the mixer circuitry 1106A of the receive signal path and the transmit signal path.
  • Examples herein can include subject matter such as a method, means for performing acts or blocks of the method, at least one machine-readable medium including executable instructions that, when performed by a machine or circuitry (e.g., a processor (e.g., processor, etc. ) with memory, an application-specific integrated circuit (ASIC) , a field programmable gate array (FPGA) , or the like) cause the machine to perform acts of the method or of an apparatus or system for concurrent communication using multiple communication technologies according to implementations and examples described.
  • a machine or circuitry e.g., a processor (e.g., processor, etc. ) with memory, an application-specific integrated circuit (ASIC) , a field programmable gate array (FPGA) , or the like
  • ASIC application-specific integrated circuit
  • FPGA field programmable gate array
  • Example 1 is a baseband processor, configured to perform operations including receiving indication that orthogonal cover code (OCC) spreading for random access channel (RACH) related physical uplink shared channel (PUSCH) transmissions is supported; interfacing with a transceiver for transmitting a first RACH-related message based on a PRACH preamble or RACH opportunity, wherein the PRACH preamble or RACH opportunity indicates that a user equipment (UE) intends to apply OCC spreading to RACH-related PUSCH transmissions; and interfacing with a transceiver for transmitting at least one RACH-related PUSCH transmission spread based on a selected OCC.
  • OCC orthogonal cover code
  • Example 2 includes the subject matter of example 1, including or omitting optional elements, wherein the baseband processor is configured to receive a system information block SIB that includes the indication that OCC spreading for RACH-related PUSCH transmissions is supported.
  • SIB system information block
  • Example 3 includes the subject matter of any of examples 1-2, including or omitting optional elements, wherein the indication includes information about an OCC size or an OCC spreading scheme and wherein the spreading scheme is one of intra-slot OCC, inter-slot OCC, and frequency-domain OCC.
  • Example 4 includes the subject matter of any of examples 1-3, including or omitting optional elements, wherein the baseband processor is configured to receive configuration of a set of PRACH preambles or RACH opportunities (ROs) that are dedicated for user equipments (UEs) with capability to apply OCC spreading to RACH-related PUSCH transmissions; and select the PRACH preamble or RACH opportunity from the configured set.
  • the baseband processor is configured to receive configuration of a set of PRACH preambles or RACH opportunities (ROs) that are dedicated for user equipments (UEs) with capability to apply OCC spreading to RACH-related PUSCH transmissions; and select the PRACH preamble or RACH opportunity from the configured set.
  • ROs PRACH preambles or RACH opportunities
  • Example 5 includes the subject matter of example 4, including or omitting optional elements, wherein the set of PRACH preambles or ROs is the same as a set of PRACH preambles or ROs that are dedicated for UEs with capability to transmit RACH-related PUSCH transmission with repetition, is a subset of the set of PRACH preambles or ROs that are dedicated for UEs with capability to transmit RACH-related PUSCH transmission with repetition, is unique from the set of PRACH preambles or ROs that are dedicated for UEs with capability to transmit RACH-related PUSCH transmission with repetition, or replaces the set of PRACH preambles or ROs that are dedicated for UEs with capability to transmit RACH-related PUSCH transmission with repetition.
  • Example 8 includes the subject matter of example 6, including or omitting optional elements, wherein the OCC information includes an indication that OCC spreading for RACH-related PUSCH transmissions is acknowledged and the baseband processor is configured to randomly select an OCC sequence or OCC length from amongst configured OCC sequence or OCC lengths for transmitting the RACH-related PUSCH transmission.
  • Example 9 includes the subject matter of example 6, including or omitting optional elements, wherein the second RACH-related message includes a downlink control information (DCI) format that indicates the OCC information, or the second RACH-related message is based on a modified random access radio network temporary identifier (RA-RNTI) , wherein the modified RA-RNTI includes an RA-RANTI of a UE modified based on a selected OCC sequence, or the second RACH-related message includes a media access control (MAC) random access response (RAR) , a MAC successRAR, or a MAC fallbackRAR, wherein the MAC RAR, MAC successRAR, or fallbackRAR includes a sub-header, a payload, or an uplink grant field that indicates the OCC information, or the second RACH-related message indicates one or more respective OCC sequences for one or more respective retransmissions of the RACH-related PUSCH transmission.
  • DCI downlink control information
  • RA-RNTI modified random access
  • Example 10 includes the subject matter of any of examples example 1-9, including or omitting optional elements, wherein the baseband processor is configured to determine an OCC sequence based on the PRACH preamble, RO, temporary cell radio network temporary identifier (TC-RNTI) , or temporary mobile subscriber identity (TMSI) of a UE.
  • the baseband processor is configured to determine an OCC sequence based on the PRACH preamble, RO, temporary cell radio network temporary identifier (TC-RNTI) , or temporary mobile subscriber identity (TMSI) of a UE.
  • Example 10 includes the subject matter of any of examples example 1-11, including or omitting optional elements, wherein the baseband processor is configured to transmit a retransmission of the RACH-related PUSCH transmission based on the same OCC sequence for the RACH-related PUSCH transmission, a next OCC sequence in a preconfigured series of OCC sequences, an OCC sequence indicated in a RACH-related message received from a base station, or a randomly selected OCC sequence.
  • Example 13 includes the subject matter of any of examples example 1-13, including or omitting optional elements, wherein the baseband processor is configured to receive, in response to the RACH-related PUSCH transmission, a message that indicates receipt of the RACH-related PUSCH transmission spread based on a detected OCC sequence; and transmit an acknowledgement message when the detected OCC sequence matches the selected OCC sequence.
  • Example 14 includes the subject matter of example 13, including or omitting optional elements, wherein the message includes a DCI format that indicates the detected OCC sequence, a physical downlink shared channel (PDSCH) transmission having a payload that indicates the detected OCC sequence, a MAC-CE that indicates the detected OCC sequence, a radio resource control (RRC) message that indicates the detected OCC sequence, a MAC-CE that indicates a correct identifier of a UE, or an RRC message that indicates a correct identifier of a UE.
  • PDSCH physical downlink shared channel
  • RRC radio resource control
  • Example 15 includes the subject matter of example 13, including or omitting optional elements, wherein the baseband processor is configured to monitor a search space associated with the selected OCC sequence and communicate the acknowledgement in response to receiving a RACH-related message in the search space.
  • Example 16 is a user equipment (UE) , including a memory and one or more processors configured to, when executing instructions stored in the memory, cause the UE to: determine an orthogonal cover code (OCC) for use in transmitting RACH-related PUSCH transmissions, wherein the OCC includes a sequence and a length; and transmit at least one RACH-related PUSCH transmission spread based on the OCC, wherein the OCC is applied across modulation symbols (FD-OCC) , orthogonal frequency division multiplexed (OFDM) symbols in a slot (intra-slot OCC) , or consecutive slots (inter-slot OCC) .
  • OCC orthogonal cover code
  • Example 21 is a baseband processor, configured to perform operations including instructing a transceiver to transmit an indication that orthogonal cover code (OCC) spreading for random access channel (RACH) related physical uplink shared channel (PUSCH) transmissions is supported; receiving a first RACH-related message based on a PRACH preamble or RACH opportunity, wherein the PRACH preamble or RACH opportunity indicates that a user equipment (UE) intends to apply OCC spreading to RACH-related PUSCH transmissions; and receiving at least one RACH-related PUSCH transmission spread based on a selected OCC.
  • OCC orthogonal cover code
  • Example 22 is a base station, including a memory and one or more processors configured to, when executing instructions stored in the memory, cause the base station to determine an orthogonal cover code (OCC) for use in receiving RACH-related PUSCH transmissions, wherein the OCC includes a sequence and a length; and receive at least one RACH-related PUSCH transmission spread based on the OCC, wherein the OCC is applied across modulation symbols (FD-OCC) , orthogonal frequency division multiplexed (OFDM) symbols in a slot (intra-slot OCC) , or consecutive slots (inter-slot OCC) .
  • OFDM orthogonal frequency division multiplexed
  • Example 25 is a UE including the baseband processor of examples 16-20.
  • personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users.
  • personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.

Landscapes

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

Abstract

L'invention concerne des systèmes, des procédés, des processeurs et des ensembles de circuits permettant de prendre en charge un canal physique partagé montant (PUSCH) associé à un canal d'accès aléatoire (RACH) avec un étalement de code de couverture orthogonal (OCC). Dans un exemple, un procédé comprend la réception d'une indication selon laquelle un étalement de code de couverture orthogonal (OCC) pour des transmissions de canal physique partagé montant (PUSCH) associées à un canal d'accès aléatoire (RACH) est pris en charge ; la transmission d'un premier message associé au RACH sur la base d'un préambule PRACH ou d'une opportunité RACH, le préambule PRACH ou l'opportunité RACH indiquant qu'un équipement utilisateur (UE) a l'intention d'appliquer un étalement OCC à des transmissions PUSCH associées au RACH ; et la transmission d'au moins un étalement de transmission PUSCH lié au RACH sur la base d'un OCC sélectionné.
PCT/CN2024/077455 2024-02-18 2024-02-18 Configuration de code de couverture orthogonale pour transmissions de canal physique partagé montant associées à un canal d'accès aléatoire Pending WO2025171665A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/077455 WO2025171665A1 (fr) 2024-02-18 2024-02-18 Configuration de code de couverture orthogonale pour transmissions de canal physique partagé montant associées à un canal d'accès aléatoire

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/077455 WO2025171665A1 (fr) 2024-02-18 2024-02-18 Configuration de code de couverture orthogonale pour transmissions de canal physique partagé montant associées à un canal d'accès aléatoire

Publications (1)

Publication Number Publication Date
WO2025171665A1 true WO2025171665A1 (fr) 2025-08-21

Family

ID=90364488

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/077455 Pending WO2025171665A1 (fr) 2024-02-18 2024-02-18 Configuration de code de couverture orthogonale pour transmissions de canal physique partagé montant associées à un canal d'accès aléatoire

Country Status (1)

Country Link
WO (1) WO2025171665A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018133437A1 (fr) * 2017-01-23 2018-07-26 Telefonaktiebolaget Lm Ericsson (Publ) Procédé et dispositif d'accès aléatoire en deux étapes
WO2020223836A1 (fr) * 2019-05-03 2020-11-12 Qualcomm Incorporated Techniques permettant de sélectionner des préambules d'accès aléatoire et des formats de charge utile dans des communications sans fil
WO2022027376A1 (fr) * 2020-08-05 2022-02-10 Apple Inc. Procédure rach pour des réseaux non terrestres pour un équipement utilisateur

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018133437A1 (fr) * 2017-01-23 2018-07-26 Telefonaktiebolaget Lm Ericsson (Publ) Procédé et dispositif d'accès aléatoire en deux étapes
WO2020223836A1 (fr) * 2019-05-03 2020-11-12 Qualcomm Incorporated Techniques permettant de sélectionner des préambules d'accès aléatoire et des formats de charge utile dans des communications sans fil
WO2022027376A1 (fr) * 2020-08-05 2022-02-10 Apple Inc. Procédure rach pour des réseaux non terrestres pour un équipement utilisateur

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Discussion on SAN PUSCH demodulation requirements", vol. RAN WG4, no. Electronic meeting; 20220221 - 20220303, 14 February 2022 (2022-02-14), XP052111438, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG4_Radio/TSGR4_102-e/Docs/R4-2204028.zip R4-2204028 discussion on satellites access node PUSCH demodulation requirement .docx> [retrieved on 20220214] *
WEI ZENG ET AL: "Discussion on PRACH coverage enhancement", vol. 3GPP RAN 1, no. Athens, GR; 20230227 - 20230303, 17 February 2023 (2023-02-17), XP052248509, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/TSG_RAN/WG1_RL1/TSGR1_112/Docs/R1-2301374.zip R1-2301374 Discussion on PRACH coverage enhancement.docx> [retrieved on 20230217] *

Similar Documents

Publication Publication Date Title
EP3906747B1 (fr) Procédé et appareil de réalisation d&#39;une communication dans un système de communication sans fil
CN112753274B (zh) 用于支持用于2步随机接入过程的方法和装置
US20230018487A1 (en) Random access procedure for latency reduction
CN112118218B (zh) 无线通信系统中的控制信息传输方法和装置
US12137478B2 (en) Efficient messaging in a procedure for accessing a communication channel
KR20200036797A (ko) 무선통신 시스템에서 랜덤 액세스 방법 및 장치
CN113905453B (zh) 随机接入的方法和设备
CN110771249B (zh) 信息传输方法以及装置、随机接入方法以及装置、通信系统
US20100322096A1 (en) Method of improving component carrier identification in a random access procedure in a wireless communication system and related communication device
CN114208300B (zh) 两步随机接入中接收和发送随机接入响应的方法及装置
US20120026965A1 (en) Method for allocating resources in a broadband wireless access system
US12245289B2 (en) Communications device, infrastructure equipment and methods for differentiating between 2-step RACH and 4-step RACH
CN107026721B (zh) 前导序列的发送和接收方法、装置及系统
CN115362745A (zh) 优先化多媒体优先级和任务关键服务的随机接入的方法及其装置
CN114175838B (zh) 在无线通信系统中执行2步随机接入过程的方法和设备
CN103369663A (zh) 避免随机存取响应碰撞的方法
CN114467356B (zh) 用于无线网络中数据传输的方法和系统
CN111989978B (zh) 随机接入的方法和设备
WO2025171665A1 (fr) Configuration de code de couverture orthogonale pour transmissions de canal physique partagé montant associées à un canal d&#39;accès aléatoire
KR102876205B1 (ko) 무선통신시스템에서 2단계 랜덤엑세스 절차에서 백오프를 수행하는 방법 및 장치
WO2016134883A1 (fr) Appareils, procédés et programmes d&#39;ordinateur pour un émetteur-récepteur mobile et un émetteur-récepteur de station de base dans un système de communication mobile
US20180338328A1 (en) Systems and methods for early collision detection in enhanced lte/5g nr random access
WO2025171641A1 (fr) Bloc de signal de synchronisation à la demande pour cellules secondaires
US20250008557A1 (en) Method for accessing a communication network, association method, terminal, base station, and corresponding computer programs
US20240163777A1 (en) Network slicing-based random access method and apparatus, and storage medium

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: 24711111

Country of ref document: EP

Kind code of ref document: A1