WO2024009198A1 - Détermination de faisceaux pour transmissions en liaison montante suivant de multiples transmissions sur un canal physique d'accès aléatoire avec différents faisceaux - Google Patents

Détermination de faisceaux pour transmissions en liaison montante suivant de multiples transmissions sur un canal physique d'accès aléatoire avec différents faisceaux Download PDF

Info

Publication number
WO2024009198A1
WO2024009198A1 PCT/IB2023/056873 IB2023056873W WO2024009198A1 WO 2024009198 A1 WO2024009198 A1 WO 2024009198A1 IB 2023056873 W IB2023056873 W IB 2023056873W WO 2024009198 A1 WO2024009198 A1 WO 2024009198A1
Authority
WO
WIPO (PCT)
Prior art keywords
prach
indication
transmitting
network node
transmission
Prior art date
Application number
PCT/IB2023/056873
Other languages
English (en)
Inventor
Ling Su
Jonas SEDIN
Yuande TAN
Anqi HE
Robert Mark Harrison
Chunhui Zhang
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
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 Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2024009198A1 publication Critical patent/WO2024009198A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/06—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
    • H04B7/0686—Hybrid systems, i.e. switching and simultaneous transmission
    • H04B7/0695—Hybrid systems, i.e. switching and simultaneous transmission using beam selection
    • H04B7/06952—Selecting one or more beams from a plurality of beams, e.g. beam training, management or sweeping
    • 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
    • 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
    • H04W74/0838—Random access procedures, e.g. with 4-step access using contention-free random access [CFRA]

Definitions

  • the present disclosure is related to wireless communication systems and more particularly to beam determination for uplink (“UL”) transmissions following multiple physical random access channel (“PRACH”) transmissions with different beams.
  • UL uplink
  • PRACH physical random access channel
  • FIG. 1 illustrates an example of a new radio (“NR”) network (e.g., a 5th Generation (“5G”) network) including a 5G core (“5GC”) network 130, network nodes 120a-b (e.g., 5G base station (“gNB”)), multiple communication devices 110 (also referred to as user equipment (“UE”)).
  • NR new radio
  • 5G 5th Generation
  • 5GC 5G core
  • gNB 5G base station
  • UE user equipment
  • Random access channel (“RACH”) repetition was introduced in Rel-13 work items (“WIs”) of "Further LTE Physical Layer Enhancements for MTC” and “NarrowBand IOT (NB-IOT)” to extend coverage in Long Term Evolution (“LTE”), although RACH repetition is not presently supported in NR releases up to Rel-17.
  • WIs Rel-13 work items
  • NB-IOT NarrowBand IOT
  • M-PDCCH machine-type communication physical downlink control channel
  • PBCH physical broadcast channel
  • PDSCH physical downlink shared channel
  • PUCCH physical uplink control channel
  • PUSCH physical uplink shared channel
  • PRACH physical random access channel
  • the UE can decide the repetition level for the initial PRACH transmission.
  • the repetition levels that the cell supports e.g., 5, 10, and 15 dB
  • the repetition levels that the cell supports can be included in the system information and the UE can select one of these based on, for example, the estimated channel quality.
  • the UE can measure the downlink (“DL”) quality.
  • the UE can select a suitable repetition level for its initial PRACH preamble transmission among 4 levels. If the UE does not receive a random access response (“RAR”) it can increase its PRACH repetition level. A number of repetitions for RAR and following messages can depend on the level for the successful PRACH
  • Coverage enhancement for the physical random access PRACH preamble can be achieved partly through relaxation of the required PRACH misdetection probability and partly through repetition of the legacy LTE PRACH formats.
  • a maximum of three different repetition levels (plus the zero coverage enhancement level) can be configured, where each level has its own configurable number of repetitions and attempts in order to adapt to the UE’s coverage situation.
  • For initial random access the UE choses its repetition level based on RSRP measurements. If the UE does not receive a RAR after the maximum number of attempts of its current level, it moves to the next higher one. No power ramping is used for large repetition levels; otherwise the current procedure is used.
  • Different coverage levels correspond to different PRACH resources (e.g., different combinations of preamble sequences, timing and narrowbands) and the available resources are signaled in SIB.
  • the RAR message in LTE can be scheduled with M-PDCCH and an associated PDSCH.
  • the UE can know the repetition level, possible start subframe, and frequency resource of the M-PDCCH from its most recent PRACH transmission (in combination with information signaled in system information block (“SIB”)).
  • SIB system information block
  • CE mode A coverage extension
  • CE mode B coverage extension
  • the CE mode can be signaled to the UE by the network.
  • a method of operating a communication device during a random access (“RA”) procedure associated with a network node of a new radio (“NR”) communications network includes transmitting a plurality of physical random access channel (“PRACH”) transmissions to the network node using at least one uplink (“UL”) transmission (“TX”) beam.
  • PRACH physical random access channel
  • TX uplink
  • the method further includes receiving an indication of a first UL Tx beam of the at least one UL Tx beam from the network node.
  • the method further includes determining to use the first UL Tx beam for message 3 (“Msg3”) transmission to the network node based on the indication.
  • the method further including transmitting the Msg3 transmission to the network node using the first UL Tx beam.
  • a method of operating a network node of a new radio (“NR”) communications network during a random access (“RA”) procedure associated with a communication device includes receiving a plurality of physical random access channel (“PRACH”) transmissions from the communication device using at least one uplink (“UL”) transmission (“Tx”) beam.
  • PRACH physical random access channel
  • the method further includes determining a first UL Tx beam of the at least one UL Tx beam for the communication device to use for message 3 (“Msg3”) transmission.
  • Msg3 message 3
  • the method further includes transmitting an indication of the first UL Tx beam to the communication device.
  • the method further includes receiving the Msg3 transmission from the communication device using the first UL Tx beam.
  • a communication device network node, non- transitory readable medium, computer program, or computer program product is provided to perform one of the above methods.
  • Certain embodiments may provide one or more of the following technical advantages.
  • identification of a UL Tx beam to use for Msg3 transmissions reduces the time it takes for a UE to connect to a communications network.
  • FIG. 1 is a schematic diagram illustrating an example of a 5 th generation (“5G”) network
  • FIG. 2 is a table illustrating an example of frame structure type 2 random access configurations for preamble formats 0-4;
  • FIG. 3 is a table illustrating an example of frame structure type 2 random access preamble mapping in time and frequency
  • FIG. 4 is a table illustrating an example of random access preamble parameters for frame structure type 2;
  • FIG. 5 is a table illustrating an example of random access configurations for FR1 and unpaired spectrum
  • FIG. 6 is a table illustrating an example of random access configurations for FR2 and unpaired spectrum
  • FIG. 7 is a table illustrating an example of a TPC command for PUSCH
  • FIG. 8 is a table illustrating an example of mapping between PRACH configuration period and SS/PBCH block to PRACH occasion association period
  • FIG. 9 is a diagram illustrating an example of a RACH-ConfigCommon IE
  • FIG. 10 is a diagram illustrating an example of a BeamFailureRecoveryConfig
  • FIGS. 11A-D are schematic diagrams illustrating examples of scenarios associated with multiple PRACH transmissions in accordance with some embodiments.
  • FIG. 12 is a flow chart illustrating an example of operations performed by a communication device for UL Tx beam determination during a RA procedure in accordance with some embodiments;
  • FIG. 13 is a flow chart illustrating an example of operations performed by a network node for UL Tx beam determination during a RA procedure in accordance with some embodiments
  • FIG. 14 is a block diagram of a communication system in accordance with some embodiments.
  • FIG. 15 is a block diagram of a user equipment in accordance with some embodiments.
  • FIG. 16 is a block diagram of a network node in accordance with some embodiments.
  • FIG. 17 is a block diagram of a host computer communicating with a user equipment in accordance with some embodiments.
  • FIG. 18 is a block diagram of a virtualization environment in accordance with some embodiments.
  • FIG. 19 is a block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments.
  • the UE can move from no or small coverage enhancements (CE mode A) to large coverage enhancements (CE mode B) when signaled.
  • CE mode A no or small coverage enhancements
  • CE mode B large coverage enhancements
  • the idea is to only keep a UE in CE mode B if it is not able to do synchronization acquisition, system information acquisition, random access or data transmission using small coverage operation.
  • the number of repetitions can be adapted according to the UE’s coverage situation.
  • a UE is a bandwidth reduced/low complexity (“BL”) UE or a UE in enhanced coverage.
  • BL bandwidth reduced/low complexity
  • a random access response (“RAR”) window starts at the subframe that contains the end of the last preamble repetition plus 3 + UE-eNB round trip time (“RTT”) subframes and has length ra-ResponseWindowSize for the corresponding enhanced coverage level. Otherwise, the RAR window starts at the subframe that contains the end of the last preamble repetition plus three subframes and has length ra-ResponseWindowSize for the corresponding enhanced coverage level.
  • RTT UE-eNB round trip time
  • a UE is a narrowband internet-of-things (“NB-IoT”) UE. If the random access preamble was transmitted in a non-terrestrial network, the RAR window starts at the subframe that contains the end of the last preamble repetition plus X + UE-eNB RTT subframes and has length ra-ResponseWindowSize for the corresponding enhanced coverage level, where value X is determined based on the used preamble format and the number of NPRACH repetitions.
  • NB-IoT narrowband internet-of-things
  • the RAR window starts at the subframe that contains the end of the last preamble repetition plus X subframes and has length ra- ResponseWindowSize for the corresponding enhanced coverage level, where value X is determined based on the used preamble format and the number of NPRACH repetitions.
  • RNTI RA-radio network temporary identifier
  • RA-RNTI 1 + t_id + 10*f_id
  • t_id is the index of the first subframe of the specified PRACH (0 ⁇ t_id ⁇ 10)
  • f_id is the index of the specified PRACH within that subframe, in ascending order of frequency domain (0 ⁇ f_id ⁇ 6) except for NB-IoT UEs, BL UEs or UEs in enhanced coverage. If the PRACH resource is on a TDD carrier, the f_id is set to .
  • RA-RNTI associated with the PRACH in which the Random Access Preamble is transmitted is computed as:
  • RA-RNTI l+t_id + 10*f_id + 60*(SFN_id mod (Wmax/10))
  • t_id is the index of the first subframe of the specified PRACH (0 ⁇ t_id ⁇ 10)
  • f_id is the index of the specified PRACH within that subframe, in ascending order of frequency domain (0 ⁇ f_id ⁇ 6)
  • SFN_id is the index of the first radio frame of the specified PRACH
  • Wmax 400, maximum possible RAR window size in subframes for BL UEs or UEs in enhanced coverage.
  • the f_id is set to .
  • the RA-RNTI associated with the PRACH in which the Random Access Preamble is transmitted is computed as:
  • RA-RNTI 1 + floor(SFN_id/4) + 256*carrier_id
  • SFN_id is the index of the first radio frame of the specified PRACH
  • carrier_id is the index of the UL carrier associated with the specified PRACH.
  • the carrier_id of the anchor carrier is 0.
  • PRACH configuration index (prach- Configurationlndex), a PRACH frequency offset Hp BBoffs£.t (prach-FrequencyOffset), a number of PRACH repetitions per attempt A 1 ’ 1 ⁇ ' 11 (pumRepetitionPerPreambleAttempf) and optionally a PRACH starting subframe periodicity N TM'' C " (prach-StartingSubframe).
  • PRACH of preamble format 0-3 is transmitted 1 times, whereas PRACH of preamble format 4 is transmitted one time only.
  • the value of the parameter iipp Boffset depends on the system frame number
  • FIG. 2 illustrates an example of a table that lists PRACH configurations allowed for frame structure type 2 where the configuration index corresponds to a certain combination of preamble format, PRACH density value, D R and version index, r ⁇ .
  • FIG. 2 lists the mapping to physical resources for the different random access opportunities needed for a certain PRACH density value, D R .
  • Each quadruple of the format indicates the location of a specific random access resource, where A.
  • o,l,2 indicates whether the resource is reoccurring in all radio frames, in even radio frames, or in odd radio frames, respectively
  • o,l indicates whether the random access resource is located in first half frame or in second half frame, respectively
  • uplink subframe number where the preamble starts counting from 0 at the first uplink subframe between 2 consecutive downlink- to-uplink switch points, with the exception of preamble format 4 where is denoted as (*).
  • the random access opportunities for each PRACH configuration shall be allocated in time first and then in frequency if and only if time multiplexing is not sufficient to hold all opportunities of a PRACH configuration needed for a certain density value D RA without overlap in time.
  • n f A 0
  • a PRACH starting subframe periodicity /v]' 1 ]''' " indicates the periodicity of the allowed starting subframes in terms of subframes allowed for preamble transmission.
  • the allowed starting subframes defined over -1 are given
  • Each random access preamble occupies a bandwidth corresponding to 6 consecutive resource blocks for both frame structures.
  • PRACH-ParametersListCE-rl3 SEQUENCE (SIZE(l..maxCE-Level-rl3)) OF PRACH- ParametersCE-r 13
  • PRACH-ParametersCE-rl3 SEQUENCE ⁇ prach-Configlndex-r 13 INTEGER (0..63), prach-FreqOffset-rl3 INTEGER (0..94), prach-StartingSubframe-rl3 ENUMERATED ⁇ sf2, sf4, sf8, sfl6, sf32, sf64, sfl28, sf256 ⁇ OPTIONAL, -
  • RACH-CE-LevelInfo-rl3 SEQUENCE ⁇ preambleMappinglnfo-r 13 SEQUENCE ⁇ firstPreamble-r 13 INTEGER(0..63), lastPreamble-rl3 INTEGER(0..63)
  • ra-ResponseWindowSize-rl3 ENUMERATED ⁇ sf20, sf5O, sf8O, sfl20, sfl8O, sf240, sf320, sf400 ⁇ , mac-ContentionResolutionTimer-rl3 ENUMERATED ⁇ sf8O, sflOO, sfl20, sfl6O, sf200, sf240, sf480, sf960 ⁇ , rar-HoppingConfig-rl3 ENUMERATED ⁇ on, off ⁇ ,
  • FIG. 3 illustrates an example of frame structure type 2 random access preamble mapping in time and frequency
  • the physical layer random access preamble is based on singlesubcarrier frequency-hopping symbol groups.
  • a symbol group is illustrated in a table in FIG. 4, consisting of a cyclic prefix of length r CP and a sequence of N identical symbols with total length r 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 preamble consisting of P symbol groups shall be transmitted times.
  • Frequency hopping shall be used within the 12 subcarriers and 36 subcarriers when preamble format 2 as described in FIG. 4 is configured, where the frequency location of the i th symbol group is given by where The quantity n ⁇ (i) depends on the frame structure.
  • the cyclic shift C v is given by where the higher-layer parameter restrictedSetConfig determines the type of restricted sets (unrestricted, restricted type A, restricted type B).
  • SCS preamble subcarrier spacing
  • Random access preambles can only be transmitted in the time resources given by the higher-layer parameter prach-Configurationlndex according to the tables in FIGS. 5-6 and depends on FR1 or FR2 and a spectrum type.
  • Random access preambles can only be transmitted in the frequency resources given by the higher-layer parameter ms gl -Frequency Start.
  • the PRACH frequency resources n RA G ⁇ 0,1, ... , M — 1 ⁇ , where M equals the higher-layer parameter msgl-FDM, are numbered in increasing order within the initial uplink bandwidth part during initial access, starting from the lowest frequency. Otherwise, n RA are numbered in increasing order within the active uplink bandwidth part, starting from the lowest frequency.
  • the following subcarrier spacing can be assumed: 15 kHz for FR1 and 60 kHz for FR2.
  • a number of time domain RACH occasions within a RACH slot for each PRACH configuration index is fixed.
  • SS synchronization signal
  • the candidate SS/PBCH block index of the SS/PBCH block corresponds to the SS/PBCH block index provided by ssb-PositionsInBurst in SIB1 or in ServingCellConfigCommon.
  • a UE For operation on a single carrier in unpaired spectrum, if a UE is configured by higher layers to transmit SRS, or PUCCH, or PUSCH, or PRACH in a set of symbols of a slot and the UE detects a DO format indicating to the UE to receive CSI-RS or PDSCH in a subset of symbols from the set of symbols, then if the UE does not indicate the capability of [partialCancellation], the UE does not expect to cancel the transmission of the PUCCH or PUSCH or PRACH in the set of symbols if the first symbol in the set occurs within T proc 2 relative to a last symbol of a CORESET where the UE detects the DO format; otherwise, the UE cancels the PUCCH, or the PUSCH, or an actual repetition of the PUSCH determined from the PRACH transmission in the set of symbols.
  • the UE does not expect to cancel the transmission of the PUCCH or PUSCH or PRACH in symbols from the set of symbols that occur within T proc 2 relative to a last symbol of a CORESET where the UE detects the DO format.
  • the UE cancels the PUCCH, or the PUSCH, or an actual repetition of the PUSCH [6, TS 38.214], determined from the PRACH transmission in remaining symbols from the set of symbols.
  • a PRACH is transmitted using the selected PRACH format with transmission power PpRACH,b,f,c (0 on the indicated PRACH resource, with BWP b of carrier f of serving cell c.
  • the UE determines a transmission power for a subsequent PRACH transmission, if any.
  • Layer 1 If prior to a PRACH retransmission, a UE changes the spatial domain transmission filter, Layer 1 notifies higher layers to suspend the power ramping counter.
  • the MAC entity shall, for each Random Access Preamble:
  • a UE can be configured by parameters given in an SIB to repeat Msg3. Unlike LTE, the UE can request repetitions for PUSCH transmission, and does so by transmitting a RACH preamble associated with the repetition procedure.
  • the network then indicates the number of repetitions Np ⁇ g ⁇ H via an MCS field in either RAR or in a PDCCH carrying DO format 0_0.
  • a UE can be provided in RACH-ConfigCommon a set of numbers of repetitions for a PUSCH transmission with PUSCH repetition Type A that is scheduled by a RAR UL grant or by a DO format 0_0 with CRC scrambled by a TC-RNTI. If the UE requests repetitions for the PUSCH transmission, the UE transmits the PUSCH over N ⁇ KCU slots, where N ⁇ tcu is indicated by the 2 MSBs of the MCS field in the RAR UL grant or in the DO format 0_0 from a set of four values provided by numberOfMsg3Repetitions or from ⁇ 1, 2, 3, 4 ⁇ if numberOfMsg3Repetitions is not provided.
  • the UE determines an MCS for the PUSCH transmission by the 2 LSBs of the MCS field in the RAR UL grant or by the 3 LSBs of the MCS field in the DO format 0_0, and determines a redundancy version and RBs for each repetition as described in [6, TS 38.214].
  • the UE determines the slots as the first slots starting from slot n + k 2 + A where a repetition of the PUSCH transmission does not include a symbol indicated as downlink by tdd-UL-DL-ConfigurationCommon or indicated as a symbol of an SS/PBCH block with index provided by ssb-PositionsInBurst.
  • a UE transmits a PUSCH on active UL BWP b of carrier f of serving cell ⁇ - using parameter set configuration with index j and PUSCH power control adjustment state with index I
  • AP , b is provided by higher layers and corresponds to the total power ramp-up requested by higher layers from the first to the last random access preamble for carrier f in the serving cell is the bandwidth of the PUSCH resource assignment expressed in number of resource blocks for the first PUSCH transmission on active UL BWP b of carrier f of serving cell C, and A TF b c (0) is the power adjustment of first PUSCH transmission on active UL BWP b of carrier f of serving cell C
  • the TPC command value ⁇ msg 2,b, f,c is used for setting the power of the PUSCH transmission is interpreted according to FIG. 7 [0079]
  • a UE is provided a number N of SS/PBCH block indexes associated with one PRACH occasion and a number R of contention based preambles per SS/PBCH block index per valid PRACH occasion by ssb-perRACH-OccasionAndCB- PreamblesPerSSB.
  • one SS/PBCH block index is mapped to N consecutive valid PRACH occasions and R contention based preambles with consecutive indexes associated with the SS/PBCH block index per valid PRACH occasion start from preamble index 0. If N > 1, R contention based preambles with consecutive indexes associated with SS/PBCH block index n, 0 ⁇ n ⁇ N - 1, per valid PRACH occasion start from preamble index n • / N where
  • SS/PBCH block indexes provided by ssb-PositionsInBurst in SIB 1 or in ServingCellConfigCommon are mapped to valid PRACH occasions in the following order where the parameters are described.
  • an association period, starting from frame 0, for mapping SS/PBCH blocks to PRACH occasions is the smallest value in the set determined by the PRACH configuration period according to FIG. 8 such that SS/PBCH blocks are mapped at least once to the PRACH occasions within the association period, where a UE obtains v., ! from the value of ssb-PositionsInBurst in SIB/ or in ServingCellConfigCommon. If after an integer number of SS/PBCH blocks to PRACH occasions mapping cycles within the association period there is a set of PRACH occasions or PRACH preambles that are not mapped to v“' !
  • An association pattern period includes one or more association periods and is determined so that a pattern between PRACH occasions and SS/PBCH blocks repeats at most every 160 msec. PRACH occasions not associated with SS/PBCH blocks after an integer number of association periods, if any, are not used for PRACH transmissions.
  • the PRACH occasions are mapped consecutively per corresponding SS/PBCH block index.
  • the indexing of the PRACH occasion indicated by the mask index value is reset per mapping cycle of consecutive PRACH occasions per SS/PBCH block index.
  • the UE selects for a PRACH transmission the PRACH occasion indicated by PRACH mask index value for the indicated SS/PBCH block index in the first available mapping cycle.
  • the ordering of the PRACH occasions is: 1) in increasing order of frequency resource indexes for frequency multiplexed PRACH occasions; 2) in increasing order of time resource indexes for time multiplexed PRACH occasions within a PRACH slot; and 3) in increasing order of indexes for PRACH slots.
  • FIG. 9 illustrates an example of a RACH-ConfigCommon information element (“IE”).
  • IE RACH-ConfigCommon information element
  • a UE In response to a PRACH transmission, a UE attempts to detect a DO format l_0 with CRC scrambled by a corresponding RA-RNTI during a window controlled by higher layers.
  • the window starts at the first symbol of the earliest CORESET the UE is configured to receive PDCCH for Typel-PDCCH CSS set, as defined in Clause 10.1, that is at least one symbol, after the last symbol of the PRACH occasion corresponding to the PRACH transmission, where the symbol duration corresponds to the SCS for Typel-PDCCH CSS set.
  • the length of the window in number of slots, based on the SCS for Typel-PDCCH CSS set, is provided by ra-ResponseWindow.
  • the TPC command value 8 m.r ⁇ is used for setting the power of the PUSCH transmission is interpreted according to FIG. 7.
  • the CSI request field is reserved.
  • the UE receives a random access response message in response to a PRACH transmission on active UL BWP b of carrier f of serving cell C, , , is a TPC command value indicated in the random access response grant of the random access response message corresponding to the PRACH transmission on active UL BWP b of carrier f in the serving cell C
  • Radio resource control can configure the following parameters for a RA procedure.
  • prach-Configurationlndex- the available set of PRACH occasions for the transmission of the Random Access Preamble.
  • preambleReceivedTargetPower initial Random Access Preamble power.
  • rsrp-ThresholdSSB an RSRP threshold for the selection of the SSB. If the Random Access procedure is initiated for beam failure recovery, rsrp-ThresholdSSB used for the selection of the SSB within candidateBeamRSList refers to rsrp-ThresholdSSB in BeamFailureRecoveryConfig IE. [0093] rsrp-ThresholdCSI-RS an RSRP threshold for the selection of CSI-RS. If the Random Access procedure is initiated for beam failure recovery, rsrp-ThresholdCSI-RS is equal to rsrp-ThresholdSSB in BeamFailureRecovery Config IE.
  • rsrp-ThresholdSSB-SUL an RSRP threshold for the selection between the NUL carrier and the SUL carrier.
  • candidateBeamRSList a list of reference signals (CSI-RS and/or SSB) identifying the candidate beams for recovery and the associated Random Access parameters.
  • recoverySearchSpaceld the search space identity for monitoring the response of the beam failure recovery request.
  • scalingFactorBP a scaling factor for prioritized Random Access procedure.
  • ra-Preamblelndex Random Access Preamble.
  • ra-ssb-OccasionMasklndex' defines PRACH occasion(s) associated with an SSB in which the MAC entity may transmit a Random Access Preamble.
  • ra-OccasionList defines PRACH occasion(s) associated with a CSI-RS in which the MAC entity may transmit a Random Access Preamble.
  • ra-PreambleStartlndex' the starting index of Random Access Preamble(s) for on- demand SI request.
  • preambleTransMax' the maximum number of Random Access Preamble transmission.
  • ssb-perRACH-OccasionAndCB-PreamblesPerSSB' defines the number of SSBs mapped to each PRACH occasion and the number of contention-based Random Access Preambles mapped to each SSB.
  • Random Access Preambles group B is configured. Amongst the contention-based Random Access Preambles associated with an SSB, the first numberOfRA-PreamblesGroupA Random Access Preambles belong to Random Access Preambles group A. The remaining Random Access Preambles associated with the SSB belong to Random Access Preambles group B (if configured). If Random Access Preambles group B is supported by the cell Random Access Preambles group B is included for each SSB.
  • the gNB configures the UE with beam failure detection reference signals (SSB or channel state information reference signal (“CSI- RS”)) and the UE declares beam failure when the number of beam failure instance indications from the physical layer reaches a configured threshold before a configured timer expires.
  • SSB beam failure detection reference signals
  • CSI- RS channel state information reference signal
  • SSB-based Beam Failure Detection is based on the SSB associated to the initial DL bandwidth part (“BWP”) and can only be configured for the initial DL BWPs and for DL BWPs containing the SSB associated to the initial DL BWP.
  • BWP initial DL bandwidth part
  • Beam Failure Detection can only be performed based on CSI-RS.
  • the UE After beam failure is detected, the UE triggers beam failure recovery by initiating a Random Access procedure on the PCell and selects a suitable beam to perform beam failure recovery (if the gNB has provided dedicated Random Access resources for certain beams, those will be prioritized by the UE).
  • the media access control (“MAC”) entity shall:
  • a UE can be provided, for each BWP of a serving cell, a set ⁇ q 0 of periodic CSI-RS resource configuration indexes by failureDetectionResources and a set q of periodic CSI-RS resource configuration indexes and/or SS/PBCH block indexes by candidateBeamRSList for radio link quality measurements on the BWP of the serving cell.
  • the UE determines the set ⁇ q 0 to include periodic CSI-RS resource configuration indexes with same values as the RS indexes in the RS sets indicated by TCI-State for respective CORESETs that the UE uses for monitoring PDCCH and, if there are two RS indexes in a TCI state, the set ⁇ 0 includes RS indexes with QCL-TypeD configuration for the corresponding TCI states.
  • the UE expects the set ⁇ 0 to include up to two RS indexes.
  • the UE expects single port RS in the set ⁇ q 0 .
  • the physical layer in the UE provides an indication to higher layers when the radio link quality for all corresponding resource configurations in the set ⁇ 0 that the UE uses to assess the radio link quality is worse than the threshold Q O ut,LR.
  • the physical layer informs the higher layers when the radio link quality is worse than the threshold QOUI,LR with a periodicity determined by the maximum between the shortest periodicity among the periodic CSI-RS configurations and/or SS/PBCH blocks in the set q ⁇ 0 that the UE uses to assess the radio link quality and 2 msec.
  • the physical layer provides an indication to higher layers when the radio link quality is worse than the threshold Q O ut,LR with a periodicity.
  • the UE Upon request from higher layers, the UE provides to higher layers the periodic CSI- RS configuration indexes and/or SS/PBCH block indexes from the set ⁇ ?] and the corresponding Ll-RSRP measurements that are larger than or equal to the Qi n ,LR threshold.
  • the UE may receive by PRACH-ResourceDedicatedBFR, a configuration for PRACH transmission.
  • PRACH-ResourceDedicatedBFR a configuration for PRACH transmission.
  • the UE monitors PDCCH in a search space set provided by recoverySearchSpaceld for detection of a DCI format with CRC scrambled by C-RNTI or MCS-C-RNTI starting from slot n+4 within a window configured by BeamFailureRecoveryConfig.
  • the UE assumes the same antenna port quasi-collocation parameters as the ones associated with index q new until the UE receives by higher layers an activation for a TCI state or any of the parameters tci- StatesPDCCH-ToAddList and/or tci-StatesPDCCH-ToReleaseList.
  • the UE After the UE detects a DCI format with CRC scrambled by C-RNTI or MCS-C-RNTI in the search space set provided by recoverySearchSpaceld, the UE continues to monitor PDCCH candidates in the search space set provided by recoverySearchSpaceld until the UE receives a MAC CE activation command for a TCI state or tci-StatesPDCCH-ToAddList and/or tci-StatesPDCCH-ToReleaseList.
  • the UE After 28 symbols from a last symbol of a first PDCCH reception in a search space set provided by recoverySearchSpaceld for which the UE detects a DCI format with CRC scrambled by C-RNTI or MCS-C-RNTI and until the UE receives an activation command for PUCCH-SpatialRelationlnfo [11, TS 38.321] or is provided PUCCH-SpatialRelationlnfo for PUCCH resource(s), the UE transmits a PUCCH on a same cell as the PRACH transmission using a same spatial filter as for the last PRACH transmission and a power determined with
  • FIG. 10 illustrates an example of a BeamFailureRecoveryConfig.
  • the UE shall consider this list to include all elements of candidateBeamRSList (without suffix) and all elements of candidateBeamRSListExt-vl610.
  • the network configures these reference signals to be within the linked DL BWP (i.e., within the DL BWP with the same bwp-Id) of the UL BWP in which the BeamFailureRecoveryConfig is provided.
  • NR new radio
  • UE user equipment
  • Tx uplink
  • Msgl uplink
  • Msg3 uplink
  • UEs (sometimes referred to herein as communication devices) that fulfil the beam correspondence requirement with the uplink beam sweeping and UEs not able to refine its Tx beam during the limited time of random access (“RA”) may use a wide UL Tx beam, resulting in relatively small output transmission power until it receives signaling of one or more UL spatial relations from a gNB when radio resource control (“RRC”) connection is established.
  • RRC radio resource control
  • multiple physical random access channel (“PRACH”) transmissions with different UL Tx beams will allow a UE to sweep narrow beams with better directivity and higher antenna gain.
  • PRACH physical random access channel
  • a UE may refine its beam at the random access until it is configured an UL spatial relation (e.g., Msgl transmitting a wider beam but Msg3 transmission with a narrow beam).
  • an UL spatial relation e.g., Msgl transmitting a wider beam but Msg3 transmission with a narrow beam.
  • the UE may take a long time to refine its beam (e.g., the uplink signal-to-noise ratio (“SNR”) could improve 20 dB within 1 second.
  • SNR uplink signal-to-noise ratio
  • a network could help to decrease the beam refining time, it could directly benefit the network with potential uplink traffic improvement.
  • beam refinement at a UE is implementation specific and depends on how many panels a UE has equipped and how many antenna elements are within each of panels. It may also depend other factors, like UE speed and UE rotation.
  • Various embodiments described herein provide operations to detect a Msg2 random access response (“RAR”) and determine an UL Tx beam for UL transmissions from the RAR after a UE transmits multiple PRACH transmissions with different UL Tx beams.
  • RAR Msg2 random access response
  • a UE can transmit a PRACH preamble in a PRACH occasion associated with a selected synchronization signal block (“SSB”).
  • a RAR is quasi-colocated (“QCLed”) with the SSB which the transmitted PRACH is associated with.
  • Timing advances (“TAs”) and transmit power control (“TPC”) fields in a RAR are based on the received PRACH.
  • TAs Timing advances
  • TPC transmit power control
  • a UE doesn’t receive a RAR that includes its random access preamble identifier (“RAPID”) within the RAR window, it can start the PRACH retransmission, which may be associated with the same SSB as initial transmission or a different SSB. Whether to use the same or different UL Tx beam for the retransmission is up to UE implementation.
  • RAPID random access preamble identifier
  • FIGS. 11 A-D There are several scenarios of multiple PRACH transmissions in terms of UL Tx beam and SSB, as illustrated in FIGS. 11 A-D.
  • FIG. 11 A illustrates an example in which a UE transmits multiple PRACHs with the same beam (e.g., with a same UL spatial domain transmission filter), and all the PRACH transmissions are associated with the same SSB.
  • FIG. 11B illustrates an example in which different beams are used for PRACH transmissions and associated with one SSB.
  • the determination of UL Tx beams is up to UE implementation and is transparent to gNB.
  • FIGS. 11C-D illustrate examples in which the multiple PRACH transmissions are associated with different SSB beams.
  • FIG. 11 A illustrates an example in which a UE transmits multiple PRACHs with the same beam (e.g., with a same UL spatial domain transmission filter), and all the PRACH transmissions are associated with the same SSB.
  • FIG. 11B illustrates an example in
  • FIG. 11C there is only PRACH associated with each selected SSB, while in FIG. 11D, at least one SSB is associated with more than one PRACH transmission.
  • FIG. 11D is a combination of FIGS. 11B-C and embodiments associated with each can be applied to the example in FIG. 1 ID.
  • UE implementation it is up to UE implementation to determine UL Tx beam for Msgl.
  • UEs with assisted beam sweeping to have beam correspondence and UEs not able to refine their Tx beam during the limited time of random access they may use a wide UL Tx beam, resulting in relatively small received power at the gNB until the UE can go through beam refinement procedures after an RRC connection is established.
  • Multiple PRACH transmission with different UL Tx beams allows UE to sweep narrow beams with better directivity and higher received power at the gNB.
  • a UL Tx beam that carried a PRACH transmission can be indicated by the gNB to carry Msg3 so that higher beamforming gain can be expected for Msg3.
  • the Tx beam can also carry following UL transmissions until a new Tx beam for UL transmission is indicated, e.g., PUCCH transmission for Msg4 HARQ feedback, or a PUSCH transmission containing UECapabilitylnformation or other information needed shortly after a RACH procedure.
  • a new Tx beam for UL transmission is indicated, e.g., PUCCH transmission for Msg4 HARQ feedback, or a PUSCH transmission containing UECapabilitylnformation or other information needed shortly after a RACH procedure.
  • PRACH occasion there is an association between PRACH occasion and SS block or between PRACH preamble index and SS block.
  • PRACH transmission associated with an SSB it is called PRACH transmission associated with an SSB.
  • Multiple PRACH transmissions refers to those of one RACH attempt, unless otherwise stated.
  • CFRA resources for a beam failure recovery request can be associated with SSBs and/or CSLRSs.
  • PRACH transmission associated SSB is referred to herein instead of PRACH transmission associated with SSB and/or CSLRS.
  • RAR can include Msg2 RAR for 4-step RACH and fallbackRAR for 2-step RACH.
  • RAR can include Msg2 RAR for 4-step RACH and fallbackRAR for 2-step RACH.
  • multiple PRACH transmissions with different UE Tx beams are associated with one SSB or multiple SSBs.
  • RA-RNTI is derived from the PRACH resource as follows. With multiple PRACH transmissions, multiple RA-RNTIs can be generated. [0131] The RA-RNTI associated with the PRACH occasion in which the Random Access Preamble is transmitted, is computed as follows, wherein s_id, t_id, f_id, and ul_carrier_id are as defined in 3GPP TS 38.321 subclause 5.1.3:
  • RA-RNTI 1 + s_id + 14 x t_id + 14 x 80 x f_id + 14 x 80 x 8 x ul_carrier_id
  • a UE Tx beam to be used for Msg3 transmission is indicated in one or more of the following ways.
  • the UL Tx beam is a beam used to previously transmit a PRACH and is identified by the previous PRACH transmission.
  • a UL Tx beam may be alternatively termed a ‘spatial domain transmission filter’ in 3GPP specifications.
  • a UE computes the RA-RNTIs associated with the PRACH occasions where the multiple PRACH transmissions occur; a gNB selects and indicates one PRACH transmission by using its corresponding RA-RNTI to scramble CRC of Msg2 PDCCH; the UE monitors PDCCH for its RA-RNTIs.
  • the UE may not switch UL beam for every PRACH transmission (e.g., due to beam switching time or configuration). Therefore, for the multiple consecutive PRACH transmissions with the same beam, one RA-RNTI is generated, which can be based on the PRACH occasion of the first PRACH of the set of transmissions.
  • the RA-RNTI of indicated PRACH transmission can be used to generate initialization ID Cinit for Msg3 PUSCH scrambling.
  • the RAPID in RAR indicates one particular UL Tx beam is to be used for Msg3 transmission.
  • a UE transmits a PRACH with a different preamble index for each of the K PRACH transmissions.
  • the first PRACH preamble is selected randomly, while the remaining K-l preambles are selected according to a predefined pattern based on the first preamble.
  • Different preamble indices are used, since RA- RNTI identifies a RACH occasion, but not the preamble used in the RACH occasion; RAPID identifies the preamble index used for the PRACH.
  • the RAPID field does not identify the RACH occasion in Rel-17, some additional rules are needed to tie the preamble index to the RACH occasion, and therefore to the UL Tx beam used in the RACH occasion.
  • the preamble is uniquely identified with a RACH occasion and the UL Tx beam used in the RACH occasion to transmit the PRACH.
  • the UE will then know to use the UL Tx beam for Msg3.
  • a new MAC subheader field is added in the MAC subheader for RAR to indicate one of the multiple PRACH transmissions or one of the multiple Tx beams.
  • the new MAC subheader field identifies the RACH occasion where the desired Tx beam was used to transmit the PRACH based on the RA-RNTI formula, for example an ‘RO ID’ can be calculated with the formula below and the RO ID can be carried in the MAC subheader.
  • the UE will use the UL Tx beam that it used to transmit the PRACH in the RACH occasion identified by the RO ID as the beam for Msg3 transmission.
  • RO_ID 1 + s_id + 14 x t_id + 14 x 80 x f_id + 14 x 80 x 8 x ul_carrier_id, where s_id, t_id, f_id, and ul_carrier_id are as defined in 3GPP TS 38.321 subclause 5.1.3
  • the gNB may not know how many Tx beams a UE uses for K PRACH transmissions. Lor example, if there are two UE Tx beams, the gNB doesn’t know which repetitions are transmitted with beam#l and which with beam#2, and it is totally up to UE implementation. The gNB can only indicate one PRACH in Msg2 with log2(K) bits, rather than 1 bit to indicate one of the two beams.
  • a mapping between UL Tx beams and the PRACH transmissions can be predetermined or configured. For example, the same UL Tx beam is used across PRACH occasions in a PRACH slot or consecutive PRACH slots. A UE can switch Tx beam over PRACH occasions in non-consecutive PRACH slots.
  • a UL Tx beam of one of the K PRACH transmissions can be indicated by DCI 0_0 with CRC scrambled by TC- RNTI.
  • a reserved fields HARQ process number and New data indicator
  • a reserved state of a field can be used for this indication.
  • some bit(s) of a field can be repurposed.
  • Msg3 retransmission uses the same UL Tx beam(s) as initial transmission.
  • the UE may track the DL SSB with finer beam before initiating the PRACH or UE may decide to transmit PRACH with one of its antenna panel but need further beam refining within this panel, a UE also could use wider beam on each of its antenna panel.
  • UE could associate each of UL Tx beam with different beam.
  • the UE could either reduce the beams to fit in the K transmissions, for example, choose wider beam on each panel so total beam number at each panel can be reduced.
  • the UE could make further beam refining and based on the network selected best beam in Msg2.
  • the UE may adapt its beam refinement process to the network configuration.
  • the network could schedule the PRACH resource and for the UE without the capability, the different PRACH resource could be allocated. It could be beneficial to define an additional UE capability associated with this feature.
  • the gNB Based on whether a UE will further refine its Tx beam before being configured with a UL spatial relation, the gNB doesn't indicate an UL beam in Msg2 RAR for a UE, that indicates such a capability. Otherwise, the gNB indicates a UL Tx beam in Msg2 RAR.
  • multiple PRACH transmissions with different UL Tx beams are associated with different SSBs.
  • a UE determines its DL Rx beam for Msg2 with the assumption that PDCCH and PDSCH for Msg2 is QCLed with the SSB to which its transmitted preamble is associated.
  • the gNB sends one RAR with a reference SSB’s beam.
  • a UE assumes the PDCCH/PDSCH DMRS conveying Msg2 RAR is QCL'ed with the reference SSB.
  • the reference SSB among the multiple SSBs can be RRC configured or predetermined. For example, the SSB associated with the RO with the smallest index, the SSB with smallest index. [0143] Regarding “the SSB associated with the RO with the smallest index”, if the first RO of multiple PRACH transmissions is associated with the SSB with the strongest RSRP, RAR is sent in the direction of the strongest SSB.
  • the UE receives one RAR with a wide beam to cover the multiple SSBs the PRACHs are associated with. For example, if the multiple PRACH transmissions are associated with two adjacent SSBs, SSB#0 and SSB#1, the UE receives Msg2 PDCCH and PDSCH with a wide beam to cover both SSBs, as it is not sure in which SSB’s beam the gNB may transmit Msg2 to it.
  • the UE monitors and receives RAR with multiple beams simultaneously. If the UE has multiple Rx chains, it doesn’t know in which SSB’s direction the gNB sends RAR toward it, it can monitor Msg2 PDCCH with the selected SSB beams.
  • the gNB sends multiple RARs toward a UE and each RAR corresponds to the PRACH transmissions associated with one SSB.
  • the PDCCH/PDSCH DMRS of Msg2 RAR is QCL’ed with the corresponding SSB.
  • the UE monitors RAR with any one of its selected SSB beams.
  • the multiple RARs toward the UE may correspond to one RA-RNTI.
  • each RAR corresponds to one RA-RNTI, where UE monitors PDCCH with its multiple RA-RNTIs.
  • the RAR monitoring window is extended to accommodate this. This extension would be specifically for PRACH repetitions. It could for instance be scaled with the number of PRACH repetitions, or be a constant amount, such as 20 ms. There can be a flag for the network to configure this for PRACH repetitions.
  • gNB can indicate an UL Tx beam for Msg3 transmission. Otherwise, if it is still up to UE implementation to determine UL Tx beam(s) like in Msg3 repetition, it would cause ambiguity to gNB with which SSB beam(s) it should receive Msg3.
  • At least a beam is indicated as a UL Tx beam of Msg3 transmission with a new MAC subheader in RAR.
  • the new field can indicate one or more of the N SSBs.
  • gNB only indicates one SSB beam in Msg2, determination of UL Tx beam(s) is the same as the Rel-17 Msg3 repetition behavior, i.e., up to UE implementation. gNB will receive Msg3 repetition with this SSB beam. It is possible that gNB indicates multiple SSBs, Msg3 repetition can benefit from the spatial diversity gain. A mapping between SSB beams and Msg3 repetitions has to be configured or predetermined with UE capability taken into account, so that gNB knows in which direction to receive a Msg3 repetition.
  • At least one of the selected SSBs, which the multiple PRACH transmissions are associated with is indicated in DCI 0_0 with CRC scrambled by TC-RNTI, which will be used by gNB to receive Msg3 retransmission.
  • TC-RNTI which will be used by gNB to receive Msg3 retransmission.
  • a reserved fields HARQ process number and New data indicator
  • a reserved state of a field can be used for this indication.
  • some bit(s) of a field can be repurposed.
  • Msg3 retransmission uses the same UL Tx beam(s) as initial Msg3 transmission.
  • the communication device may be any of the wireless device 1412A, 1412B, wired or wireless devices UE 1412C, UE 1412D, UE 1500, virtualization hardware 1804, virtual machines 1808 A, 18O8B, or UE 1906
  • the UE 1500 (also referred to herein as communication device 1500) shall be used to describe the functionality of the operations of the communication device. Operations of the communication device 1500 (implemented using the structure of the block diagram of FIG. 15) will now be discussed with reference to the flow charts of FIG. 12 according to some embodiments of inventive concepts.
  • modules may be stored in memory 1510 of FIG. 15, and these modules may provide instructions so that when the instructions of a module are executed by respective communication device processing circuitry 1502, processing circuitry 1502 performs respective operations of the flow charts.
  • FIG. 12 illustrates an example of operations performed by a communication device during a RA procedure associated with a network node of a NR communications network.
  • processing circuitry 1502 transmits, via communication interface 1512, a plurality of PRACH transmission to the network node using at least one UL Tx beam.
  • transmitting the plurality of PRACH transmissions includes transmitting the plurality of PRACH transmissions using a second UL Tx beam that is wider than the first UL Tx beam.
  • the first UL Tx beam can be within an envelope of the second UL Tx beam.
  • Transmitting the plurality of PRACH transmissions can further include performing a beam refining procedure to generate the first UL Tx beam from the second UL Tx beam,
  • processing circuitry 1502 determines a plurality of RA-RNTIs that are each associated with one of the plurality of PRACH transmissions.
  • processing circuitry 1502 receives, via communication interface 1512, an indication of a first UL Tx beam of the at least one UL Tx beam from the network node.
  • receiving the indication of the first UL Tx beam includes receiving an indication to proceed with the beam refining procedure.
  • processing circuitry 1502 determines to use the first UL Tx beam for Msg3 transmissions to the network node based on the indication.
  • receiving the indication of the first UL Tx beam includes receiving an indication of a RA-RNTI of the plurality of RA-RNTIs
  • determining the first UL Tx beam for Msg3 transmission includes determining that the first UL Tx beam is associated with the RA-RNTI.
  • transmitting the plurality of PRACH transmissions includes transmitting a plurality of preambles that each have an associated RAPID.
  • Receiving the indication of the first UL Tx beam includes receiving an indication of a RAPID associated with a preamble of the plurality of preambles. Determining to use the first UL Tx beam for Msg3 transmission includes determining that the preamble is associated with the first UL Tx beam.
  • receiving the indication of the first UL Tx beam includes receiving an indication of a PRACH transmission of the plurality of PRACH transmissions in a MAC subheader field. Determining to use the first UL Tx beam for Msg3 transmission includes determining that the first UL Tx beam is associated with the PRACH transmission.
  • receiving the indication of the first UL Tx beam includes receiving an indication of a RO. Determining to use the first UL Tx beam for Msg3 transmission comprises determining that the first UL Tx beam is associated with the RO. In some examples, receiving the indication of the RO includes receiving an indication of a RO ID defined by:
  • RO ID 1 + s_id + 14 x t_id + 14 x 80 x f_id + 14 x 80 x 8 x ul_carrier_id, wherein s_id, t_id, f_id, and ul_carrier_id are as defined in 3GPP TS 38.321.
  • transmitting the plurality of PRACH transmissions includes transmitting the plurality of PRACH transmissions associated with a plurality of SSBs.
  • Receiving the indication of the first UL Tx beam includes receiving a RAR associated with a first SSB of the plurality of SSBs.
  • Determining to use the first UL Tx beam for Msg3 transmission includes determining that the first UL Tx beam was associated with the first SSB of the plurality of SSBs.
  • processing circuitry 1502 transmits, via communication interface 1512, the Msg3 transmission to the network node using the first UL Tx beam.
  • the Msg3 transmission includes a first Msg3 transmission.
  • Transmitting the Msg3 transmission to the network node includes, responsive to transmitting the first Msg3 transmission, determining that a response to the first Msg3 transmission has not been received within a threshold period of time. Responsive to determining that the response to the Msg3 transmission has not been received within the threshold period of time, retransmitting the first Msg3 transmission using the first UL Tx beam.
  • processing circuitry 1502 receives, via communication interface 1512, an indication of a second UL Tx beam from the network node in DCI. [0163] At block 1270, processing circuitry 1502 retransmits, via communication interface 1512, the Msg3 transmission using the second UL Tx beam.
  • processing circuitry 1502 transmits, via communication interface 1512, at least one of a PUSCH and a PUCCH using the first UL Tx beam or the second UL Tx beam.
  • FIG. 12 Various operations from the flow chart of FIG. 12 may be optional with respect to some embodiments of communication devices and related methods.
  • blocks 1220, 1260, 1270, and 1280 of FIG. 12 may be optional.
  • the network node may be any of the network node 1410A, 1410B, core network node 1408, network node 1600, virtualization hardware 1804, virtual machines 18O8A, 18O8B, or network node 1904
  • the network node 1600 shall be used to describe the functionality of the operations of the network node. Operations of the network node 1600 (implemented using the structure of the block diagram of FIG. 16) will now be discussed with reference to the flow chart of FIG. 13 according to some embodiments of inventive concepts.
  • modules may be stored in memory 1604 of FIG. 16, and these modules may provide instructions so that when the instructions of a module are executed by respective network node processing circuitry 1602, processing circuitry 1602 performs respective operations of the flow chart.
  • FIG. 13 illustrates an example of operations performed by a network node of a NR communications network during a RA procedure associated with a communication device.
  • processing circuitry 1602 receives, via communication interface 1606, a plurality of PRACH transmissions from a communication device using at least one UL Tx beam.
  • processing circuitry 1602 determines a first UL Tx beam of the at least one UL Tx beam for the communication device to use for Msg3 transmission.
  • processing circuitry 1602 determines a RA-RNTI that is associated with a PRACH transmission of the PRACH transmissions that is associated with the first UL Tx beam.
  • processing circuitry 1602 transmits, via communication interface 1606, an indication of the first UL Tx beam to the communication device.
  • transmitting the indication of the first UL Tx beam includes transmitting an indication of the RA-RNTI to the communication device.
  • receiving the plurality of PRACH transmissions includes receiving a plurality of preambles that each have an associated RAPID and transmitting the indication of the first UL Tx beam includes transmitting an indication of the RAPID associated with the first UL Tx beam to the communication device.
  • transmitting the indication of the first UL Tx beam includes transmitting an indication of a PRACH transmission of the plurality of PRACH transmissions in a MAC subheader field.
  • transmitting the indication of the first UL Tx beam comprises transmitting an indication of a RO.
  • receiving the plurality of PRACH transmissions includes receiving the plurality of PRACH transmissions using a second UL Tx beam that is wider than the first UL Tx beam, the first UL Tx beam being within an envelope of the second UL Tx beam.
  • Transmitting the indication of the first UL Tx beam includes transmitting an indication that the communication device perform a beam refining procedure associated with the second UL Tx beam.
  • receiving the plurality of PRACH transmissions includes receiving the plurality of PRACH transmissions associated with a plurality of SSBs.
  • Transmitting the indication of the first UL Tx beam includes transmitting a RAR associated with a first SSB of the plurality of SSBs.
  • processing circuitry 1602 receives, via communication interface 1606, the Msg3 transmission from the communication device using the first UL Tx beam.
  • the Msg3 transmission includes a first Msg3 transmission
  • receiving the Msg3 transmission includes, responsive to transmitting a RAR to the communication device, determining that the first Msg3 transmission has not been received within a threshold period of time. Responsive to determining that the first Msg3 transmission has not been received within the threshold period of time, monitoring for a Msg3 retransmission from the communication device using the first UL Tx beam.
  • processing circuitry 1602 transmits, via communication interface 1606, an indication of a second UL Tx beam to the communication device in DCI.
  • processing circuitry 1602 receives, via communication interface 1606, a Msg3 retransmission from the communication device using the second UL Tx beam. [0180] At block 1380, processing circuitry 1602 receives at least one of a PUSCH and a PUCCH using the first UL Tx beam. [0181] Various operations from the flow chart of FIG. 13 may be optional with respect to some embodiments of network entities and related methods. In some examples, blocks 1330, 1360, 1370, and 1380 of FIG. 13 may be optional.
  • FIG. 14 shows an example of a communication system 1400 in accordance with some embodiments.
  • the communication system 1400 includes a telecommunication network 1402 that includes an access network 1404, such as a radio access network (RAN), and a core network 1406, which includes one or more core network nodes 1408.
  • the access network 1404 includes one or more access network nodes, such as network nodes 1410a and 1410b (one or more of which may be generally referred to as network nodes 1410), or any other similar 3 rd Generation Partnership Project (3GPP) access node or non-3GPP access point.
  • 3GPP 3 rd Generation Partnership Project
  • the network nodes 1410 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 1412a, 1412b, 1412c, and 1412d (one or more of which may be generally referred to as UEs 1412) to the core network 1406 over one or more wireless connections.
  • UE user equipment
  • Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors.
  • the communication system 1400 may include any number of wired or wireless networks, network nodes, UEs, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
  • the communication system 1400 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs 1412 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 1410 and other communication devices.
  • the network nodes 1410 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 1412 and/or with other network nodes or equipment in the telecommunication network 1402 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 1402.
  • the core network 1406 connects the network nodes 1410 to one or more hosts, such as host 1416. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts.
  • the core network 1406 includes one more core network nodes (e.g., core network node 1408) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 1408.
  • Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).
  • MSC Mobile Switching Center
  • MME Mobility Management Entity
  • HSS Home Subscriber Server
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • AUSF Authentication Server Function
  • SIDF Subscription Identifier De-concealing function
  • UDM Unified Data Management
  • SEPP Security Edge Protection Proxy
  • NEF Network Exposure Function
  • UPF User Plane Function
  • the host 1416 may be under the ownership or control of a service provider other than an operator or provider of the access network 1404 and/or the telecommunication network 1402, and may be operated by the service provider or on behalf of the service provider.
  • the host 1416 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.
  • the communication system 1400 of FIG. 14 enables connectivity between the UEs, network nodes, and hosts.
  • the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any low- power wide-area network (LPWAN) standards such as LoRa and Sigfox.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • the telecommunication network 1402 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 1402 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1402. For example, the telecommunications network 1402 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)ZMassive loT services to yet further UEs.
  • URLLC Ultra Reliable Low Latency Communication
  • eMBB Enhanced Mobile Broadband
  • mMTC Massive Machine Type Communication
  • the UEs 1412 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network 1404 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1404.
  • a UE may be configured for operating in single- or multi-RAT or multi-standard mode.
  • a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved- UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).
  • MR-DC multi-radio dual connectivity
  • E-UTRAN Evolved- UMTS Terrestrial Radio Access Network
  • EN-DC New Radio - Dual Connectivity
  • the hub 1414 communicates with the access network 1404 to facilitate indirect communication between one or more UEs (e.g., UE 1412c and/or 1412d) and network nodes (e.g., network node 1410b).
  • the hub 1414 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs.
  • the hub 1414 may be a broadband router enabling access to the core network 1406 for the UEs.
  • the hub 1414 may be a controller that sends commands or instructions to one or more actuators in the UEs.
  • the hub 1414 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data.
  • the hub 1414 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1414 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1414 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • the hub 1414 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.
  • the hub 1414 may have a constant/persistent or intermittent connection to the network node 1410b.
  • the hub 1414 may also allow for a different communication scheme and/or schedule between the hub 1414 and UEs (e.g., UE 1412c and/or 1412d), and between the hub 1414 and the core network 1406.
  • the hub 1414 is connected to the core network 1406 and/or one or more UEs via a wired connection.
  • the hub 1414 may be configured to connect to an M2M service provider over the access network 1404 and/or to another UE over a direct connection.
  • UEs may establish a wireless connection with the network nodes 1410 while still connected via the hub 1414 via a wired or wireless connection.
  • the hub 1414 may be a dedicated hub - that is, a hub whose primary function is to route communications to/from the UEs from/to the network node 1410b.
  • the hub 1414 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 1410b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
  • FIG. 15 shows a UE 1500 in accordance with some embodiments.
  • a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs.
  • Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc.
  • VoIP voice over IP
  • LME laptop-embedded equipment
  • LME laptop-mounted equipment
  • CPE wireless customer-premise equipment
  • UEs identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • 3GPP 3rd Generation Partnership Project
  • NB-IoT narrow band internet of things
  • MTC machine type communication
  • eMTC enhanced MTC
  • a UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle- to-everything (V2X).
  • D2D device-to-device
  • DSRC Dedicated Short-Range Communication
  • V2V vehicle-to-vehicle
  • V2I vehicle-to-infrastructure
  • V2X vehicle- to-everything
  • a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device.
  • a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller).
  • a UE may represent a device that is not intended for sale
  • the UE 1500 includes processing circuitry 1502 that is operatively coupled via a bus 1504 to an input/output interface 1506, a power source 1508, a memory 1510, a communication interface 1512, and/or any other component, or any combination thereof.
  • Certain UEs may utilize all or a subset of the components shown in FIG. 15. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
  • the processing circuitry 1502 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 1510.
  • the processing circuitry 1502 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above.
  • the processing circuitry 1502 may include multiple central processing units (CPUs).
  • the input/output interface 1506 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices.
  • Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof.
  • An input device may allow a user to capture information into the UE 1500.
  • Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like.
  • the presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user.
  • a sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof.
  • An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.
  • USB Universal Serial Bus
  • the power source 1508 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used.
  • the power source 1508 may further include power circuitry for delivering power from the power source 1508 itself, and/or an external power source, to the various parts of the UE 1500 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 1508.
  • Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1508 to make the power suitable for the respective components of the UE 1500 to which power is supplied.
  • the memory 1510 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read- only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth.
  • the memory 1510 includes one or more application programs 1514, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1516.
  • the memory 1510 may store, for use by the UE 1500, any of a variety of various operating systems or combinations of operating systems.
  • the memory 1510 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and/or ISIM, other memory, or any combination thereof.
  • RAID redundant array of independent disks
  • HD-DVD high-density digital versatile disc
  • HDDS holographic digital data storage
  • DIMM external mini-dual in-line memory module
  • SDRAM synchronous dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • the UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’
  • the memory 1510 may allow the UE 1500 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data.
  • An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 1510, which may be or comprise a device-readable storage medium.
  • the processing circuitry 1502 may be configured to communicate with an access network or other network using the communication interface 1512.
  • the communication interface 1512 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1522.
  • the communication interface 1512 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network).
  • Each transceiver may include a transmitter 1518 and/or a receiver 1520 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).
  • the transmitter 1518 and receiver 1520 may be coupled to one or more antennas (e.g., antenna 1522) and may share circuit components, software or firmware, or alternatively be implemented separately.
  • communication functions of the communication interface 1512 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short- range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof.
  • GPS global positioning system
  • Communications may be implemented in according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol/internet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.
  • a UE may provide an output of data captured by its sensors, through its communication interface 1512, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE.
  • the output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).
  • a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection.
  • the states of the actuator, the motor, or the switch may change.
  • the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.
  • a UE when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare.
  • loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal-
  • AR Augmented Reality
  • VR
  • a UE may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another UE and/or a network node.
  • the UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device.
  • the UE may implement the 3GPP NB-IoT standard.
  • a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • any number of UEs may be used together with respect to a single use case.
  • a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone.
  • the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed.
  • the first and/or the second UE can also include more than one of the functionalities described above.
  • a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.
  • FIG. 16 shows a network node 1600 in accordance with some embodiments.
  • network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication network.
  • network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)).
  • APs access points
  • BSs base stations
  • Node Bs Node Bs
  • eNBs evolved Node Bs
  • gNBs NR NodeBs
  • Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations.
  • a base station may be a relay node or a relay donor node controlling a relay.
  • a network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • RRUs remote radio units
  • RRHs Remote Radio Heads
  • Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
  • DAS distributed antenna system
  • network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs).
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • OFDM Operation and Maintenance
  • OSS Operations Support System
  • SON Self-Organizing Network
  • positioning nodes e.g., Evolved Serving Mobile Location Centers (E-SMLCs)
  • the network node 1600 includes a processing circuitry 1602, a memory 1604, a communication interface 1606, and a power source 1608.
  • the network node 1600 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components.
  • the network node 1600 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes.
  • a single RNC may control multiple NodeBs.
  • each unique NodeB and RNC pair may in some instances be considered a single separate network node.
  • the network node 1600 may be configured to support multiple radio access technologies (RATs).
  • RATs radio access technologies
  • some components may be duplicated (e.g., separate memory 1604 for different RATs) and some components may be reused (e.g., a same antenna 1610 may be shared by different RATs).
  • the network node 1600 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1600, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1600.
  • RFID Radio Frequency Identification
  • the processing circuitry 1602 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 1600 components, such as the memory 1604, to provide network node 1600 functionality.
  • the processing circuitry 1602 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1602 includes one or more of radio frequency (RF) transceiver circuitry 1612 and baseband processing circuitry 1614. In some embodiments, the radio frequency (RF) transceiver circuitry 1612 and the baseband processing circuitry 1614 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 1612 and baseband processing circuitry 1614 may be on the same chip or set of chips, boards, or units.
  • SOC system on a chip
  • the processing circuitry 1602 includes one or more of radio frequency (RF) transceiver circuitry 1612 and baseband processing circuitry 1614.
  • the radio frequency (RF) transceiver circuitry 1612 and the baseband processing circuitry 1614 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of
  • the memory 1604 may comprise any form of volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device-readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry 1602.
  • volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or
  • the memory 1604 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry 1602 and utilized by the network node 1600.
  • the memory 1604 may be used to store any calculations made by the processing circuitry 1602 and/or any data received via the communication interface 1606.
  • the processing circuitry 1602 and memory 1604 is integrated.
  • the communication interface 1606 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE.
  • the communication interface 1606 comprises port(s)/terminal(s) 1616 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface 1606 also includes radio front-end circuitry 1618 that may be coupled to, or in certain embodiments a part of, the antenna 1610.
  • Radio front-end circuitry 1618 comprises filters 1620 and amplifiers 1622.
  • the radio front-end circuitry 1618 may be connected to an antenna 1610 and processing circuitry 1602.
  • the radio front-end circuitry may be configured to condition signals communicated between antenna 1610 and processing circuitry 1602.
  • the radio front-end circuitry 1618 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection.
  • the radio front-end circuitry 1618 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1620 and/or amplifiers 1622. The radio signal may then be transmitted via the antenna 1610. Similarly, when receiving data, the antenna 1610 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1618. The digital data may be passed to the processing circuitry 1602. In other embodiments, the communication interface may comprise different components and/or different combinations of components.
  • the network node 1600 does not include separate radio front-end circuitry 1618, instead, the processing circuitry 1602 includes radio front-end circuitry and is connected to the antenna 1610. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1612 is part of the communication interface 1606. In still other embodiments, the communication interface 1606 includes one or more ports or terminals 1616, the radio front-end circuitry 1618, and the RF transceiver circuitry 1612, as part of a radio unit (not shown), and the communication interface 1606 communicates with the baseband processing circuitry 1614, which is part of a digital unit (not shown).
  • the antenna 1610 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna 1610 may be coupled to the radio front-end circuitry 1618 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • the antenna 1610 is separate from the network node 1600 and connectable to the network node 1600 through an interface or port.
  • the antenna 1610, communication interface 1606, and/or the processing circuitry 1602 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment. Similarly, the antenna 1610, the communication interface 1606, and/or the processing circuitry 1602 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment.
  • the power source 1608 provides power to the various components of network node 1600 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source 1608 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1600 with power for performing the functionality described herein.
  • the network node 1600 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1608.
  • the power source 1608 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.
  • Embodiments of the network node 1600 may include additional components beyond those shown in FIG. 16 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein.
  • the network node 1600 may include user interface equipment to allow input of information into the network node 1600 and to allow output of information from the network node 1600. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1600.
  • FIG. 17 is a block diagram of a host 1700, which may be an embodiment of the host 1416 of FIG. 14, in accordance with various aspects described herein.
  • the host 1700 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm.
  • the host 1700 may provide one or more services to one or more UEs.
  • the host 1700 includes processing circuitry 1702 that is operatively coupled via a bus 1704 to an input/output interface 1706, a network interface 1708, a power source 1710, and a memory 1712.
  • processing circuitry 1702 that is operatively coupled via a bus 1704 to an input/output interface 1706, a network interface 1708, a power source 1710, and a memory 1712.
  • Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as FIGS. 15 and 16, such that the descriptions thereof are generally applicable to the corresponding components of host 1700.
  • the memory 1712 may include one or more computer programs including one or more host application programs 1714 and data 1716, which may include user data, e.g., data generated by a UE for the host 1700 or data generated by the host 1700 for a UE.
  • Embodiments of the host 1700 may utilize only a subset or all of the components shown.
  • the host application programs 1714 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems).
  • the host application programs 1714 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network.
  • the host 1700 may select and/or indicate a different host for over-the-top services for a UE.
  • the host application programs 1714 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.
  • HLS HTTP Live Streaming
  • RTMP Real-Time Messaging Protocol
  • RTSP Real-Time Streaming Protocol
  • MPEG-DASH Dynamic Adaptive Streaming over HTTP
  • FIG. 18 is a block diagram illustrating a virtualization environment 1800 in which functions implemented by some embodiments may be virtualized.
  • virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources.
  • virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components.
  • Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1800 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host.
  • VMs virtual machines
  • the node may be entirely virtualized.
  • Applications 1802 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Hardware 1804 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth.
  • Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1806 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1808a and 1808b (one or more of which may be generally referred to as VMs 1808), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein.
  • the virtualization layer 1806 may present a virtual operating platform that appears like networking hardware to the VMs 1808.
  • the VMs 1808 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1806.
  • a virtualization layer 1806 Different embodiments of the instance of a virtual appliance 1802 may be implemented on one or more of VMs 1808, and the implementations may be made in different ways.
  • Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
  • NFV network function virtualization
  • a VM 1808 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non- virtualized machine.
  • Each of the VMs 1808, and that part of hardware 1804 that executes that VM be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate virtual network elements.
  • a virtual network function is responsible for handling specific network functions that run in one or more VMs 1808 on top of the hardware 1804 and corresponds to the application 1802.
  • Hardware 1804 may be implemented in a standalone network node with generic or specific components. Hardware 1804 may implement some functions via virtualization.
  • hardware 1804 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1810, which, among others, oversees lifecycle management of applications 1802.
  • hardware 1804 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.
  • FIG. 19 shows a communication diagram of a host 1902 communicating via a network node 1904 with a UE 1906 over a partially wireless connection in accordance with some embodiments.
  • Eike host 1700 embodiments of host 1902 include hardware, such as a communication interface, processing circuitry, and memory.
  • the host 1902 also includes software, which is stored in or accessible by the host 1902 and executable by the processing circuitry.
  • the software includes a host application that may be operable to provide a service to a remote user, such as the UE 1906 connecting via an over-the-top (OTT) connection 1950 extending between the UE 1906 and host 1902. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 1950.
  • the network node 1904 includes hardware enabling it to communicate with the host 1902 and UE 1906.
  • the connection 1960 may be direct or pass through a core network (like core network 1406 of FIG. 14) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks.
  • an intermediate network may be a backbone network or the Internet.
  • the UE 1906 includes hardware and software, which is stored in or accessible by UE 1906 and executable by the UE’s processing circuitry.
  • the software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 1906 with the support of the host 1902.
  • a client application such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 1906 with the support of the host 1902.
  • an executing host application may communicate with the executing client application via the OTT connection 1950 terminating at the UE 1906 and host 1902.
  • the UE's client application may receive request data from the host's host application and provide user data in response to the request data.
  • the OTT connection 1950 may transfer both the request data and the user data.
  • the UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 1950.
  • the OTT connection 1950 may extend via a connection 1960 between the host 1902 and the network node 1904 and via a wireless connection 1970 between the network node 1904 and the UE 1906 to provide the connection between the host 1902 and the UE 1906.
  • the connection 1960 and wireless connection 1970, over which the OTT connection 1950 may be provided, have been drawn abstractly to illustrate the communication between the host 1902 and the UE 1906 via the network node 1904, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • the host 1902 provides user data, which may be performed by executing a host application.
  • the user data is associated with a particular human user interacting with the UE 1906.
  • the user data is associated with a UE 1906 that shares data with the host 1902 without explicit human interaction.
  • the host 1902 initiates a transmission carrying the user data towards the UE 1906.
  • the host 1902 may initiate the transmission responsive to a request transmitted by the UE 1906.
  • the request may be caused by human interaction with the UE 1906 or by operation of the client application executing on the UE 1906.
  • the transmission may pass via the network node 1904, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1912, the network node 1904 transmits to the UE 1906 the user data that was carried in the transmission that the host 1902 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1914, the UE 1906 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1906 associated with the host application executed by the host 1902.
  • the UE 1906 executes a client application which provides user data to the host 1902.
  • the user data may be provided in reaction or response to the data received from the host 1902.
  • the UE 1906 may provide user data, which may be performed by executing the client application.
  • the client application may further consider user input received from the user via an input/output interface of the UE 1906. Regardless of the specific manner in which the user data was provided, the UE 1906 initiates, in step 1918, transmission of the user data towards the host 1902 via the network node 1904.
  • the network node 1904 receives user data from the UE 1906 and initiates transmission of the received user data towards the host 1902.
  • the host 1902 receives the user data carried in the transmission initiated by the UE 1906.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE 1906 using the OTT connection 1950, in which the wireless connection 1970 forms the last segment. More precisely, the teachings of these embodiments may allow identification of a UL Tx beam to use for Msg3 transmissions.
  • factory status information may be collected and analyzed by the host 1902.
  • the host 1902 may process audio and video data which may have been retrieved from a UE for use in creating maps.
  • the host 1902 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights).
  • the host 1902 may store surveillance video uploaded by a UE.
  • the host 1902 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs.
  • the host 1902 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and/or transmitting data.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 1902 and/or UE 1906.
  • sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1950 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 1950 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 1904. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 1902.
  • the measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1950 while monitoring propagation times, errors, etc.
  • computing devices described herein may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein.
  • Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing circuitry may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components.
  • a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface.
  • non-computationally intensive functions of any of such components may be implemented in software or firmware and computational
  • processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium.
  • some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner.
  • the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and/or by end users and a wireless network generally.

Landscapes

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

Abstract

Pendant une procédure d'accès aléatoire (« RA ») associée à un nœud de réseau d'un réseau de communication New Radio (« NR »), un dispositif de communication peut procéder aux opérations consistant à : transmettre une pluralité de transmissions sur un canal physique d'accès aléatoire (« PRACH ») au nœud de réseau au moyen d'au moins un faisceau de transmission (« Tx ») en liaison montante (« UL ») ; recevoir du nœud de réseau une indication d'un premier faisceau UL Tx parmi ledit au moins un faisceau UL Tx ; sur la base de l'indication, déterminer d'utiliser le premier faisceau UL Tx pour une transmission d'un message 3 (« Msg3 ») au nœud de réseau ; et transmettre la transmission de Msg3 au nœud de réseau au moyen du premier faisceau UL Tx.
PCT/IB2023/056873 2022-07-04 2023-06-30 Détermination de faisceaux pour transmissions en liaison montante suivant de multiples transmissions sur un canal physique d'accès aléatoire avec différents faisceaux WO2024009198A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CNPCT/CN2022/103644 2022-07-04
CN2022103644 2022-07-04

Publications (1)

Publication Number Publication Date
WO2024009198A1 true WO2024009198A1 (fr) 2024-01-11

Family

ID=87158414

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2023/056873 WO2024009198A1 (fr) 2022-07-04 2023-06-30 Détermination de faisceaux pour transmissions en liaison montante suivant de multiples transmissions sur un canal physique d'accès aléatoire avec différents faisceaux

Country Status (1)

Country Link
WO (1) WO2024009198A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170367120A1 (en) * 2016-06-15 2017-12-21 Convida Wireless, Llc Random access procedures in next gen networks
WO2021152540A1 (fr) * 2020-01-29 2021-08-05 Lenovo (Singapore) Pte. Ltd. Indication de correspondance de faisceaux à l'aide d'une procédure de rach
US20220095382A1 (en) * 2017-03-23 2022-03-24 Convida Wireless, Llc Beam training and initial access
WO2022080728A1 (fr) * 2020-10-15 2022-04-21 엘지전자 주식회사 Procédé d'exécution d'une procédure d'accès à un canal et dispositif associé

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170367120A1 (en) * 2016-06-15 2017-12-21 Convida Wireless, Llc Random access procedures in next gen networks
US20220095382A1 (en) * 2017-03-23 2022-03-24 Convida Wireless, Llc Beam training and initial access
WO2021152540A1 (fr) * 2020-01-29 2021-08-05 Lenovo (Singapore) Pte. Ltd. Indication de correspondance de faisceaux à l'aide d'une procédure de rach
WO2022080728A1 (fr) * 2020-10-15 2022-04-21 엘지전자 주식회사 Procédé d'exécution d'une procédure d'accès à un canal et dispositif associé
EP4231760A1 (fr) * 2020-10-15 2023-08-23 Lg Electronics, Inc. Procédé d'exécution d'une procédure d'accès à un canal et dispositif associé

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
3GPP TS 38.321
OPPO: "Summary of Email discussion [105#50][NR-U] RACH 4-step and SR", vol. RAN WG2, no. Xi'an, China; 20190406 - 20190412, 6 April 2019 (2019-04-06), XP051700631, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings%5F3GPP%5FSYNC/RAN2/Docs/R2%2D1903282%2Ezip> [retrieved on 20190406] *

Similar Documents

Publication Publication Date Title
US11272534B2 (en) Contention-free random access with multiple SSB
US20220132578A1 (en) RACH Report with Beam Selection Information
US20220408478A1 (en) Determination of PRACH Occasions and PUSCH Occasions for 2-Step Random Access
US20220078853A1 (en) Random Access in a Wireless Communication System
WO2023209695A1 (fr) Détermination de canaux et de signaux pour appliquer une avance temporelle
WO2023037004A1 (fr) Transmissions sur la liaison latérale dans une bande de fréquence non soumise à licence
WO2024009198A1 (fr) Détermination de faisceaux pour transmissions en liaison montante suivant de multiples transmissions sur un canal physique d&#39;accès aléatoire avec différents faisceaux
WO2024009196A1 (fr) Interprétation d&#39;équipement utilisateur d&#39;un contrôle de puissance de transmission (tpc) et d&#39;une commande d&#39;avance de synchronisation (tac) dans une réponse d&#39;accès aléatoire (rar) pour de multiples transmissions de canal physique à accès aléatoire (prach)
WO2024045176A1 (fr) Signalisation et configuration d&#39;accès aléatoire (ra) d&#39;amélioration de couverture (ce)
WO2024009199A1 (fr) Détermination d&#39;une ressource d&#39;un canal d&#39;accès aléatoire et d&#39;une puissance de transmission pour de multiples transmissions sur un canal physique d&#39;accès aléatoire
WO2024045173A1 (fr) Repli d&#39;accès aléatoire sans contention amélioré (cfra)
WO2024095231A1 (fr) Inclusion conditionnelle d&#39;une combinaison de caractéristiques dans un rapport de ra
WO2023079525A1 (fr) Ressources de pucch pour dispositifs sans fil à largeur de bande réduite
WO2024072307A1 (fr) Bwp et mobilité inter-cellules l1-l2
WO2024072308A1 (fr) Alignement temporel pour mobilité intercellulaire
WO2024035327A1 (fr) Économies d&#39;énergie de nœud de réseau par l&#39;intermédiaire d&#39;un mécanisme de réponse d&#39;accès aléatoire flexible
WO2024025451A1 (fr) Transmissions de petites données dans réseau sans fil
WO2022167918A1 (fr) Adaptation rach à deux étapes pour dispositifs à capacité réduite
WO2024102048A1 (fr) Adressage d&#39;ue avec des codes wus
WO2024094889A1 (fr) Temporisateur d&#39;inactivité pendant une transmission/réception discontinue de cellule
WO2024069583A1 (fr) Gestion de transmissions ul se chevauchant dans le temps
WO2023059240A1 (fr) Amélioration d&#39;un rapport d&#39;accès aléatoire avec indication d&#39;accès aléatoire effectué vers mn ou sn
WO2023277753A1 (fr) Mécanismes pour cg-sdt associés à de multiples faisceaux ssb
WO2023165970A1 (fr) Mise en œuvre d&#39;une transmission ou transmission d&#39;un bloc de signal de synchronisation de liaison latérale
WO2023062610A1 (fr) Surveillance de canal physique de contrôle descendant multi-créneau

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

Country of ref document: EP

Kind code of ref document: A1