WO2024009196A1 - User equipment interpretation of transmit power control (tpc) and timing advance command (tac) in random access response (rar) for multiple physical random access channel (prach) transmissions - Google Patents

User equipment interpretation of transmit power control (tpc) and timing advance command (tac) in random access response (rar) for multiple physical random access channel (prach) transmissions Download PDF

Info

Publication number
WO2024009196A1
WO2024009196A1 PCT/IB2023/056858 IB2023056858W WO2024009196A1 WO 2024009196 A1 WO2024009196 A1 WO 2024009196A1 IB 2023056858 W IB2023056858 W IB 2023056858W WO 2024009196 A1 WO2024009196 A1 WO 2024009196A1
Authority
WO
WIPO (PCT)
Prior art keywords
prach
tac
relative
tpc
prach transmission
Prior art date
Application number
PCT/IB2023/056858
Other languages
French (fr)
Inventor
Ling Su
Jonas SEDIN
Yuande TAN
Anqi HE
Robert Mark Harrison
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 WO2024009196A1 publication Critical patent/WO2024009196A1/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/04—TPC
    • H04W52/06—TPC algorithms
    • H04W52/14—Separate analysis of uplink or downlink
    • H04W52/146—Uplink power control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/08—Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/04—TPC
    • H04W52/30—TPC using constraints in the total amount of available transmission power
    • H04W52/32—TPC of broadcast or control channels
    • H04W52/325—Power control of control or pilot channels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/04—TPC
    • H04W52/38—TPC being performed in particular situations
    • H04W52/50—TPC being performed in particular situations at the moment of starting communication in a multiple access environment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access, e.g. scheduled or random access
    • H04W74/08—Non-scheduled or contention based access, e.g. random access, ALOHA, CSMA [Carrier Sense Multiple Access]
    • H04W74/0833—Non-scheduled or contention based access, e.g. random access, ALOHA, CSMA [Carrier Sense Multiple Access] using a random access procedure
    • 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
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/04—TPC
    • H04W52/18—TPC being performed according to specific parameters
    • H04W52/24—TPC being performed according to specific parameters using SIR [Signal to Interference Ratio] or other wireless path parameters
    • H04W52/242—TPC being performed according to specific parameters using SIR [Signal to Interference Ratio] or other wireless path parameters taking into account path loss
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/04—TPC
    • H04W52/38—TPC being performed in particular situations
    • H04W52/42—TPC being performed in particular situations in systems with time, space, frequency or polarisation diversity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/04—TPC
    • H04W52/54—Signalisation aspects of the TPC commands, e.g. frame structure

Definitions

  • the present disclosure relates generally to communications, and more particularly to communication methods and related devices and nodes supporting wireless communications.
  • Random access channel (RACH) repetition was introduced in Rel-13 WIs of "Further LTE Physical Layer Enhancements for MTC” and “NarrowBand Internet of things (IOT) (NB-IOT)”to extend coverage.
  • IOT Internet of things
  • 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 decides 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 are included in the system information and the UE selects one of the repetition levels based on e.g., the estimated channel quality.
  • the UE measures the downlink (DL) quality.
  • the UE selects a suitable repetition level for its initial PRACH preamble transmission among, e.g., 4 levels. • If the UE does not receive a random access response (RAR), the UE increases its PRACH repetition level
  • 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 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.
  • the UE chooses 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, the UE 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 a system information block (SIB).
  • SIB system information block
  • the RAR message is scheduled with M-PDCCH and an associated PDSCH.
  • the UE knows 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 SIB).
  • CE (coverage enhancement) mode A for no or small coverage enhancement, requiring a few (e.g., up to a few tens of) repetitions.
  • CE mode B for a medium to large coverage enhancement, requiring several (e.g., hundreds of) repetitions.
  • the CE mode is signaled to the UE by the network.
  • Coverage enhancement modes The UE moves from no or small coverage enhancements (CE mode A) to large coverage enhancements (CE mode B) when signaled. The goal is to only keep a UE in CE mode B if the UE is not able to do synchronization acquisition, system information acquisition, random access or data transmission using small coverage operation. In enhanced coverage operation, the number of repetitions can be adapted according to the UE’s coverage situation.
  • the UE is a BL UE (bandwidth reduced low complexity UE) or a UE in enhanced coverage: if the random access preamble was transmitted in a non-terrestrial network: o RA Response window starts at the subframe that contains the end of the last preamble repetition plus 3 + UE-eNB RTT subframes, as specified in TS 36.213 and has length ra-ResponseWindowSize for the corresponding enhanced coverage level; else: o RA Response 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.
  • o RA Response window starts at the subframe that contains the end of the last preamble repetition plus X + UE-eNB RTT subframes, as specified in TS 36.213 and has length ra-ResponseWindowSize for the corresponding enhanced coverage level, where value X is determined from Table 5.1.4-1 based on the used preamble format and the number of NPRACH repetitions; else: o RA Response 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 from Table 5.1.4-1 based on the used preamble format and the number of NPRACH repetitions.
  • the RA-RNTI random access-radio network temporary identifier associated with the PRACH in which the Random Access Preamble is transmitted, is computed as:
  • RA-RNTI 1 + t_id + 10*f_id where t_id is the index of the first subframe of the specified PRACH (0 ⁇ t_id ⁇ 10), and 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 f RA , where f RA is defined in clause 5.7.1 of TS 36.211.
  • 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 repetitions per attempt lV r P p ACH (numReyetitionPerPreambleAttemyt) and optionally a PRACH starting subframe periodicity 1V S ⁇ CH (prach-StartingSubframe).
  • PRACH of preamble format 0-3 is transmitted lV r p e p ACH > 1 times, whereas PRACH of preamble format 4 is transmitted one time only.
  • the value of the parameter n ⁇ B offset depends on the SFN (system frame number) and the PRACH configuration index and is given by
  • n t is the system frame number corresponding to the first subframe for each PRACH repetition
  • pR ⁇ hop corresponds to a cell-specific higher-layer parameter prach-HoppingOffset.
  • the UE may for handover purposes assume an absolute value of the relative time difference between radio frame in the current cell and the target cell is less than 153600 T s .
  • Table 5.7.1-4 lists the mapping to physical resources for the different random access opportunities needed for a certain PRACH density value, D RA .
  • 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.
  • the frequency multiplexing shall be done according to where N UL RB is the number of uplink resource blocks, n RA PRB is the first physical resource block allocated to the PRACH opportunity considered and where n RA PRB offset is the first physical resource block available for PRACH.
  • n RA sf 0, . . . N RA sf - 1
  • n RA sf 0
  • N repP RACH the periodicity of the allowed starting subframes in terms of subframes allowed for preamble transmission.
  • N PRACH s tart indicates the periodicity of the allowed starting subframes in terms of subframes allowed for preamble transmission.
  • Each random access preamble occupies a bandwidth corresponding to 6 consecutive resource blocks for both frame structures.
  • Table 5.7.1-4 Frame structure type 2 random access preamble mapping in time and frequency
  • the physical layer random access preamble is based on single-subcarrier frequencyhopping symbol groups.
  • a symbol group consists of a cyclic prefix of length T CP and a sequence of N identical symbols with total length T SE Q (an illustration of a symbol group is shown in Figure 10.1.6-1-1 of 3GPP TS 36.211).
  • 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 parameters for frame structure 2 is listed in Table 10.1.6.1-2 below.
  • the preamble consisting of P symbol groups shall be transmitted /V r cp RACH times.
  • frame structure type 2 when an invalid uplink subframe overlaps the transmission of G symbol groups without a gap, the G symbol groups are dropped.
  • frame structure type 2 the transmission of G symbol groups are aligned with the subframe boundary.
  • Frequency hopping shall be used within the 12 subcarriers and 36 subcarriers when preamble format 2 as described in Table 10.1.6.1-1 of 3GPP TS 36.211 is configured, where the frequency location of the i th symbol group is given by The quantity n s (i) depends on the frame structure.
  • [0036] There are 64 preambles defined in each time-frequency PRACH occasion, enumerated in increasing order of first increasing cyclic shift of a logical root sequence, and then in increasing order of the logical root sequence index, starting with the index obtained from the higher-layer parameter prach-RootSequencelndex or rootSequencelndex-BFR. Additional preamble sequences, in case 64 preambles cannot be generated from a single root Zadoff-Chu sequence, are obtained from the root sequences with the consecutive logical indexes until all the 64 sequences are found.
  • the sequence number u is obtained from the logical root sequence index according to Tables 6.3.3.1-3 and 6.3.3.1-4 of 3GPP TS 38.211.
  • the cyclic shift C v is given by where the first and second rows are for unrestricted sets, the third row is for restricted sets type A and B and the fourth and fifth rows are for restricted sets type B, and N cs is given by Tables 6.3.3.1-5 to 6.3.3.1-7 of 3GPP TS 38.211, the higher-layer parameter restrictedSetConfig determines the type of restricted sets (unrestricted, restricted type A, restricted type B), and Tables 6.3.3.1-1 and 6.3.3.1-2 indicate the type of restricted sets supported for the different preamble formats.
  • Parameters for determining the root sequence and their cyclic shifts in the PRACH preamble sequence set may include one or more of: sequence length
  • Random access preambles can only be transmitted in the time resources given by the higher-layer parameter prach-Configurationlndex according to Tables 6.3.3.2-2 to 6.3.3.2-4 of 3GPP TS 38.211 (reproduced below) and depends on FR1 or FR2 and the spectrum type as defined in 3GPP TS 38.104.
  • the candidate SS/PBCH block index of the SS/PBCH block corresponds to the SS/PBCH block index provided by ssb-PositionsInBurst in SIBI or in ServingCellConfigCommon , as described in clause 4.1
  • a PRACH occasion in a PRACH slot is valid if it is within UL symbols, or it does not precede a SS/PBCH block in the PRACH slot and starts at least Ag a p symbols after a last downlink symbol and at least A gap symbols after a last SS/PBCH block symbol, where A gap is provided in Table 8.1-2
  • channelAccessMode "s emiSt atic" is provided, does not overlap with a set of consecutive symbols before the start of a next channel occupancy time where there shall not be any transmissions, as described in [TS 37.213] the candidate SS/PBCH block index of the SS/PBCH block corresponds to the SS/PBCH block index provided by ssb-PositionsInBurst in SI
  • 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
  • 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 [TS38.214], determined from clauses 9 and 9.2.5 or clause 6.1 of [TS38.214], or 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 [TS 38.214], determined from clauses 9 and 9.2.5 or clause 6.1 of [TS 38.214], or 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, as described in TS 38.321.
  • Layer 1 notifies higher layers to suspend the power ramping counter as described in (TS 38.321) [0054] 5.1.3 of 38.321 V17.0.0
  • the MAC (medium access control) entity shall, for each Random Access Preamble: 1> if PREAMBLE_TRANSMISSION_COUNTER is greater than one; and 1> if the notification of suspending power ramping counter has not been received from lower layers; and
  • PREAMBLE_RECEIVED_TARGET_POWER to preambleReceivedTargetPower + DELT A_PRE AMBLE + (PREAMBLE_POWER_RAMPING_COUNTER - 1) x PREAMBLE_POWER_RAMPING_STEP;
  • a UE transmits a PUSCH on active UL BWP b of carrier f of serving cell c using parameter set configuration with index j and PUSCH power control adjustment state with index
  • the UE determines the PUSCH transmission power PpuscH,b,f,c(i,j,q d , l) in PUSCH transmission occasion i as where,
  • -8 msg2,b,f,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, and and ⁇ Prampupr equested ,b ,f ,c i s 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 c, M PUSCH RB,b,f ,c (0) 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 , f,c (0) is the power adjustment of first PUSCH transmission on active UL BWP b of carrier f of serving cell c. [0061] 8.2 of TS 38.213
  • the TPC command value 8 msg2 b c is used for setting the power of the PUSCH transmission, as described in Clause 7.1.1, and is interpreted according to Table 8.2-2.
  • 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.
  • N one SS/PBCH block index is mapped to VN 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 - 1, per valid PRACH occasion start from preamble index n • / N where
  • SS/PBCH block indexes provided by ssb-PositionsInBurst in SIB1 or in ServingCellConfigCommon are mapped to valid PRACH occasions in the following order where the parameters are described in TS 38.211
  • 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 Table 8.1-1 such that W ⁇ B SS/PBCH blocks are mapped at least once to the PRACH occasions within the association period, where a UE obtains W ⁇ B from the value of ssb- PositionsInBurst in SIB 1 or in ServingCellConfigCommon.
  • 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: First, in increasing order of frequency resource indexes for frequency multiplexed PRACH occasions
  • Table 8.1-1 Mapping between PRACH configuration period and SS/PBCH block to PRACH occasion association period
  • RACH-ConfigCommon SEQUENCE ⁇ rach-ConfigGeneric RACH-ConfigGeneric , totalNumberOfRA-Preambles INTEGER (1..63) OPTIONAL, - Need S ssb-perRACH-OccasionAndCB-PreamblesPerSSB CHOICE ⁇ oneEighth ENUMERATED ⁇ n4,n8,nl2,nl6,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64 ⁇ , oneFourth ENUMERATED ⁇ n4,n8,nl2,nl6,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64 ⁇ , oneHalf ENUMERATED ⁇ n4,n8,nl2,nl6,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n
  • ServingCellConfigCommon SEQUENCE ⁇ shortBitmap BIT STRING (SIZE (4)), mediumBitmap BIT STRING (SIZE (8)), longBitmap BIT STRING (SIZE (64)) ⁇ OPTIONAL, - Cond AbsFreqSSB ssb-periodicityServingCell ENUMERATED ⁇ ms5, ms 10, ms20, ms40, ms80, msl60, spare2, sparel ⁇ OPTIONAL, — Need S
  • a UE In response to a PRACH transmission, a UE attempts to detect a DCI format l_0 with CRC scrambled by a corresponding RA-RNTI during a window controlled by higher layers (TS 38.321).
  • 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 as defined in Clause 10.1.
  • 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 msg2 b f c is used for setting the power of the PUSCH transmission, as described in Clause 7.1.1, and is interpreted according to Table 8.2-2.
  • 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 as described in Clause 8 fb,f,c( 0 Prampup,b,f,c 4” 8msg 2 ,b,f,c’ where I 0 and 8 mS g2,b,f,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,
  • RRC configures the following parameters for the Random Access 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 BeamFailureRecovery Config IE; rsrp-ThresholdCSI-RS: an RSRP threshold for the selection of CSI-RS.
  • rsrp-ThresholdCSI-RS is equal to rsrp-ThresholdSSB in BeamFailureRecoveryConfig 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; powerRampingStep'. the power-ramping factor; powerRampingStepHighPriority.
  • CSI-RS and/or SSB reference signals
  • 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 (see clause 7.4)
  • 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- preambleTransMax-.
  • 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 ; if groupBconfigured is configured, then Random Access Preambles group B is configured.
  • 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).
  • 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 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 beam failure detection reference signals
  • SSB-based Beam Failure Detection is based on the SSB associated to the initial DL BWP and can only be configured for the initial DL BWPs and for DL BWPs containing the SSB associated to the initial DL BWP. For other DL BWPs, Beam Failure Detection can only be performed based on CSI-RS.
  • the UE triggers beam failure recovery by initiating a Random Access procedure on the PCell (primary cell); 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).
  • 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 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 q 0 includes RS indexes with QCL-TypeD configuration for the corresponding TCI states.
  • the UE expects the set 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 q 0 that the UE uses to assess the radio link quality is worse than the threshold Q 0U t,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 0U t,LR with a periodicity determined as described in (TS 38.133).
  • 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 Qin,LR threshold.
  • the UE may receive by PRACH-ResourceDedicatedBFR, a configuration for PRACH transmission as described in Clause 8.1.
  • PRACH-ResourceDedicatedBFR a configuration for PRACH transmission as described in Clause 8.1.
  • the UE monitors PDCCH in a search space set provided by recoverySearchSpaceld for detection of a DO 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.
  • BeamFailureRecoveryConfig :: SEQUENCE ⁇ rootSequencelndex-BFR INTEGER (0..137) OPTIONAL, - Need M rach-ConfigBFR RACH-ConfigGeneric OPTIONAL, — Need M rsrp-ThresholdSSB RSRP-Range OPTIONAL, — Need M candidateBeamRSList SEQUENCE (SIZE(L.maxNrofCandidateBeams)) OF PRACH-
  • PRACH-ResourceDedicatedBFR CHOICE ⁇ ssb BFR-SSB-Resource, csi-RS BFR-CSIRS-Resource
  • BFR-SSB-Resource SEQUENCE ⁇ ssb SSB-Index, ra-Preamblelndex INTEGER (0..63),
  • BFR-CSIRS-Resource SEQUENCE ⁇ csi-RS NZP-CSI-RS-Resourceld, ra-OccasionList SEQUENCE (SIZE(L.maxRA-OccasionsPerCSIRS)) OF INTEGER (0..maxRA-Occasions-l) OPTIONAL, — Need R ra-Preamblelndex INTEGER (0..63) OPTIONAL, - Need R
  • candidateBeamRSList [0096] candidateBeamRSList, candidateBeamRSListExt-v 1610
  • the list of reference signals (CSI-RS and/or SSB) identifying the candidate beams for recovery and the associated RA parameters.
  • 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
  • Option 1 Transmission of only a single Msg.1 before the end of a monitored RAR window
  • a UE can be configured to transmit multiple simultaneous Msg.l Note: multiple simultaneous Msg.l transmissions use different frequency resources and/or use the same frequency resource with different preamble indices
  • a UE can be configured to transmit multiple Msg.l over multiple RACH transmission occasions in the time domain before the end of a monitored RAR window
  • a UE can be configured to transmit multiple Msg.1 over dedicated multiple RACH transmission occasions in time domain before the end of a monitored RAR window if the configuration of dedicated multiple RACH transmission occasions in time domain is supported.
  • the time resource used for ‘dedicated RACH in time domain’ is different from the time resources of contention based random access
  • a UE In NR up to Rel-17, a UE is allowed to transmit one PRACH preamble for an attempt. As PRACH was identified as a coverage bottleneck, its coverage can be enhanced by the multiple PRACH transmissions in Rel-18.
  • a method performed by a network node includes receiving multiple physical random access channel, PRACH, transmissions from a user equipment, UE, in Msgl.
  • the method includes responsive to receiving the multiple PRACH transmissions, signaling to the UE one or more of: a single transmit power control, TPC command; multiple TPC values in a random access response, RAR, corresponding to multiple PRACH transmission power of multiple uplink, UL, transmit, Tx, beams; a single timing advance command, TAC; and/or multiple TAC values in a RAR corresponding to multiple PRACH transmissions with multiple UL Tx beams.
  • Certain embodiments may provide one or more of the following technical advantage(s).
  • NR user equipment and network nodes using the embodiments may utilizes multiple NR PRACH transmissions with different UL Tx beams.
  • a method performed by a user equipment includes transmitting multiple physical random access channel, PRACH, transmissions to a network node with a same beam or different beams, in Msgl.
  • the method includes receiving, from the network node one or more of: a single transmit power control, TPC command; multiple TPC values in a random access response, RAR, corresponding to multiple PRACH transmission power of multiple uplink, UL, transmit, Tx, beams; a single timing advance command, TAC; and/or multiple TAC values in a RAR corresponding to multiple PRACH transmissions with multiple UL Tx beams.
  • Figure 1 is an illustration of various scenarios of multiple PRACH transmissions;
  • Figures 2-5 are flowcharts illustrating operations of a network node according to some embodiments;
  • Figures 6-11 are flowcharts illustrating operations of a user equipment according to some embodiments.
  • Figure 12 is a block diagram of a communication system in accordance with some embodiments.
  • Figure 13 is a block diagram of a user equipment in accordance with some embodiments
  • Figure 14 is a block diagram of a network node in accordance with some embodiments.
  • Figure 15 is a block diagram of a host computer communicating with a user equipment in accordance with some embodiments.
  • Figure 16 is a block diagram of a virtualization environment in accordance with some embodiments.
  • Figure 17 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 in accordance with some embodiments.
  • a UE can transmit a PRACH preamble in a PRACH occasion associated with a selected SSB.
  • RAR is QCLed with the SSB which the transmitted PRACH is associated with.
  • TA TPC fields in RAR are based on the received PRACH. If a UE doesn’t receive a RAR which contains its 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.
  • Scenario 1 is where a UE transmits multiple PRACHs with the same beam, i.e., the same UL spatial relation, and all the PRACH transmissions are associated with the same SSB.
  • 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 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.
  • Scenario 2 shows that the 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.
  • Scenario 3 and Scenario 4 are where the multiple PRACH transmissions are associated with different Tx SSB beams. In Scenario 3, there is only PRACH associated with each selected SSB, while in Scenario 4, at least one SSB is associated with more than one PRACH transmission.
  • Scenario 4 is a combination of Scenario 3 and Scenario 2 and can use the solutions of both scenarios and therefore need not be discussed in further detail.
  • contention-free Random Access Resources for beam failure recovery request can be associated with SSBs and/or CSI-RSs, for the sake of brevity, PRACH transmission associated SSB is used instead of PRACH transmission associated with SSB and/or CSI-RS.
  • RAR includes Msg2 RAR for 4-step RACH and fallbackRAR for 2-step RACH.
  • Msg2 RAR for 4-step RACH
  • fallbackRAR for 2-step RACH.
  • gNB Even if the same transmit power and UL Tx beam is used for multiple PRACH transmissions, gNB may receive them with different signal strengths due to the time-varying radio channel. Let alone it is possible that a UE may change its transmission power and/or conduct beam sweeping across multiple PRACH transmissions. If a gNB signals a single TPC in RAR, the gNB and UE need to be aligned on which PRACH transmission is the TPC command applies to for Msg3 transmission. This is a new problem for multiple PRACH transmissions.
  • a UE may adjust its TA during the multiple PRACH transmissions autonomously, which is unknown by gNB. However, both the UE and gNB should be clear the TAC in RAR is based on which of the multiple PRACH transmissions.
  • transmission power of Msg3 is determined by which relies on P L ⁇ ,c ld and Prampuprequested,b,f,c
  • ⁇ ⁇ msg2, b,f,c is a TPC command value indicated in a random access response grant of the random access response message corresponding to a PRACH transmission according to Type-1 random access procedure, or in a random access response grant of the random access response message corresponding to a MsgA transmission according to Type-2 random access procedure with RAR message(s) for fallbackRAR, on active UL BWP b of carrier f of serving cell c, and and AP rampup requested ,b ,f ,c i s 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 c ) 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 6 ⁇ c (0) is the power adjustment of first PUSCH transmission on active UL BWP b of carrier f of serving cell
  • Msg2 gNB After receiving multiple PRACH transmissions from a UE with the same or different beams, in Msg2 gNB signals a single TPC relative to o a reference PRACH transmission, e.g., the PRACH transmitted in the PRACH occasion or transmission occasion with the smallest or the largest PRACH occasion or transmission occasion index, or the first or the last PRACH transmission o the average, the smallest or largest PRACH transmission power of multiple transmissions
  • multiple TPC values in RAR corresponding to multiple PRACH transmissions with multiple UL Tx beams a single TAC relative to o a reference PRACH transmission, e.g., the PRACH transmitted in the PRACH occasion or transmission occasion with the smallest or the largest PRACH occasion or transmission occasion index, or the first or the last PRACH transmission o the average, the smallest or largest timing advance of multiple transmissions multiple TAC values in RAR corresponding to multiple PRACH transmissions with multiple UL Tx beams [0139] If the gNB knows which PRACH transmissions use the same beam, the TPC/TAC value can be beam-specific, so that the UE can determine beam-specific transmission parameters for the following Msg3 transmission with some of these beams.
  • FIG. 2-4 illustrates operations of embodiment 1 from the perspective of the network node.
  • network node 1400 of Figure 14 shall be used to describe the operations.
  • modules may be stored in memory 1404 of Figure 14, and these modules may provide instructions so that when the instructions of a module are executed by respective network node processing circuitry 1402, network node 1400 performs respective operations of the flow chart(s).
  • the network node 1400 receives multiple physical random access channel, PRACH, transmissions from a user equipment, UE, in Msgl.
  • PRACH physical random access channel
  • the network node 1400 responsive to receiving the multiple PRACH transmissions, signals to the UE one or more of: a single transmit power control, TPC, command 205; multiple TPC values in a random access response, RAR, corresponding to multiple PRACH transmission power of multiple uplink, UE, transmit, Tx, beams 207; a single timing advance command, TAC, 209; and/or multiple TAC values in a RAR corresponding to multiple PRACH transmissions with multiple UL Tx beams 211.
  • a single transmit power control, TPC, command 205 multiple TPC values in a random access response, RAR, corresponding to multiple PRACH transmission power of multiple uplink, UE, transmit, Tx, beams 207
  • a single timing advance command, TAC, 209 and/or multiple TAC values in a RAR corresponding to multiple PRACH transmissions with multiple UL Tx beams 211.
  • the network node receives a physical uplink shared channel, PUSCH, that is transmitted using at least one of a power level according to the single TPC command or the multiple TPC values or a timing advance according to the single TAC or the multiple TAC values.
  • PUSCH physical uplink shared channel
  • the network node in block 301 in signaling the single TPC, the network node in block 301, signals a single TPC relative to a reference PRACH transmission.
  • Figure 3 illustrates various embodiments of signaling a single TPC relative to a reference PRACH transmission in blocks 303-307.
  • the network node 1400 signals the single TPC relative to a reference PRACH transmission by signaling a single TPC relative to a PRACH transmitted with a smallest or largest PRACH transmission occasion index.
  • the network node 1400 signals the single TPC relative to a reference PRACH transmission by signaling a single TPC relative to a PRACH transmitted in a first or a last PRACH transmission.
  • the network node 1400 signals the single TPC relative to a reference PRACH transmission by signaling a single TPC relative to an average, smallest, or largest PRACH transmission power of multiple transmissions.
  • the network node in block 401 signals a single TAC relative to a reference PRACH transmission.
  • Figure 4 illustrates various embodiments of signaling a single TPC relative to a reference PRACH transmission in blocks 403-407.
  • the network node 1400 signals the single TAC relative to a reference PRACH transmission by signaling a single TAC relative to a PRACH transmitted with a smallest or largest PRACH transmission occasion index.
  • the network node 1400 signals the single TAC relative to a reference PRACH transmission by signaling a single TAC relative to a PRACH transmitted in a first or a last PRACH transmission.
  • the network node 1400 signals the single TAC relative to a reference PRACH transmission by signaling a single TAC relative to an average, smallest, or largest timing advance of multiple transmissions.
  • FIGs 6-8 illustrates operations of embodiment 1 from the perspective of the UE.
  • UE 1300 of Figure 13 shall be used to describe the operations.
  • modules may be stored in memory 1304 of Figure 13, and these modules may provide instructions so that when the instructions of a module are executed by respective network node processing circuitry 1302, UE 1300 performs respective operations of the flow chart(s).
  • the UE 1300 transmits multiple physical random access channel, PRACH, transmissions to a network node 1400 with a same beam or different beams in Msgl.
  • PRACH physical random access channel
  • the UE 1300 receives from the network node 1400 one or more of: a single transmit power control, TPC, command 605; multiple TPC values in a random access response, RAR, corresponding to multiple PRACH transmission power of multiple uplink, UL, transmit, Tx, beams 607; a single timing advance command, TAC, 609; and/or multiple TAC values in a RAR corresponding to multiple PRACH transmissions with multiple UL Tx beams 611.
  • the UE 1300 in block 701 receives a single TPC relative to a reference PRACH transmission.
  • Figure 7 illustrates various embodiments of receiving a single TPC relative to a reference PRACH transmission in blocks 703-707.
  • the UE 1300 receives the single TPC relative to a reference PRACH transmission by receiving a single TPC relative to a PRACH transmitted with a smallest or largest PRACH transmission occasion index.
  • the UE 1300 receives the single TPC relative to a reference PRACH transmission by receiving a single TPC relative to a PRACH transmitted in a first or a last PRACH transmission.
  • the UE 1300 receives the single TPC relative to a reference PRACH transmission by receiving a single TPC relative to an average, smallest, or largest PRACH transmission power of multiple transmissions.
  • the UE 1300 ramps up power for a subsequent transmission when the UE 1300 does not receive Msg2 or MsgB intended for the UE 1300 in a RAR window corresponding to a prior transmission according to the excerpt below from 3GPP TS 38.321 rev 17.1.0, section 5.1.3.
  • PREAMBLE_RECEIVED_TARGET_POWER to preambleReceivedTargetPower + DELT A_PRE AMBLE + (PREAMBLE_POWER_RAMPING_COUNTER - 1) x PREAMBLE_POWER_RAMPING_STEP;
  • a UE 1300 only ramps up its transmit power by a single step between RAR windows.
  • the PRACH may be repeated within a RAR window.
  • An alternative could be to set the PRACH power control parameters such that UEs in a cell transmit at maximum power, and therefore does not ramp up power, but this may create unnecessary interference.
  • the network can send Msg2 or MsgB when the PRACH is ramped high enough to be successfully received. This would generally avoid the highest power transmissions that typically produce the most interference. While repetition can substantially improve the likelihood that the network will receive PRACH transmission from a UE 1300, the repeated PRACH transmissions within a single RAR window may be insufficient. Therefore, it can be beneficial for a UE 1300 to increment its power ramping counter for each of a plurality of PRACH transmissions contained within a RAR window, and to accumulate the power ramping counter across RAR windows. In this way, multiple RAR windows can be used to increase the PRACH power on top of the increases from repetitions within each window.
  • a UE 1300 transmits a plurality of PRACHs within a first RAR window and within a second RAR window.
  • the UE 1300 increments a preamble power ramping counter for the plurality of PRACH transmissions within each of the first RAR window and the second RAR window, wherein a value of the preamble power ramping counter for a first PRACH transmission in the second RAR window is one greater than a last value of the preamble power ramping counter for a last PRACH transmission in the first RAR window.
  • the UE 1300 multiplies the preamble power ramping counter by a power ramping step value and adds a result of the multiplying to a value indicated by the TPC command to determine at least a portion of a power to transmit a PUSCH.
  • the UE 1300 in block 901 receives a single TAC relative to a reference PRACH transmission.
  • Figure 8 illustrates various embodiments of signaling a single TPC relative to a reference PRACH transmission in blocks 803-807.
  • the UE 1300 receives the single TAC relative to a reference PRACH transmission by receiving a single TAC relative to a PRACH transmitted with a smallest or largest PRACH transmission occasion index.
  • the UE 1300 receives the single TAC relative to a reference PRACH transmission by receiving a single TAC relative to a PRACH transmitted in a first or a last PRACH transmission.
  • the UE 1300 receives the single TAC relative to a reference PRACH transmission by receiving a single TAC relative to an average, smallest, or largest timing advance of multiple transmissions.
  • AP ra mpuprequested ,b ,f ,c corresponds to the total power ramp-up requested by higher layers from the first to the last random access preamble transmitted with the same beam.
  • Figure 5 illustrates operations the network node 1400 performs in some embodiments of Embodiment 2.
  • the network node 1400 signals to the UE 1300 an indication that AP ra mpuprequested,b ,f ,c corresponds to a total power ramp-up requested by higher layers from a first to a last random access preamble transmitted with a same beam.
  • Figure 10 illustrates operations the UE 1300 performs in some embodiments of Embodiment 2.
  • the UE 1300 receives from the network node 1400 an indication that AP ra mpuprequested ,b ,f ,c corresponds to a total power ramp-up requested by higher layers from a first to a last random access preamble transmitted with a same beam.
  • a UE estimates pathloss of the indicated SSB beam to determine Msg3 transmission power. TPC and TAC command are applied to the PRACH transmission associated with the indicated SSB beam.
  • Figure 11 illustrates operations the UE 1300 performs in some embodiments of Embodiment 3.
  • the UE 1300 responsive to multiple PRACH transmissions with different uplink Tx beams are associated with different synchronization signal blocks, SSBs, and the network indicates one SSB in Msg2 estimates a pathloss of the indicated SSB beam to determine Msg3 transmission power.
  • the UE 1300 applies a TPC and/or a TAC command to a PRACH transmission associated with the indicated SSB beam.
  • Figure 12 shows an example of a communication system 1200 in accordance with some embodiments.
  • the communication system 1200 includes a telecommunication network 1202 that includes an access network 1204, such as a radio access network (RAN), and a core network 1206, which includes one or more core network nodes 1208.
  • the access network 1204 includes one or more access network nodes, such as network nodes 1210A and 1210B (one or more of which may be generally referred to as network nodes 1210), 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 1210 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 1212A, 1212B, 1212C, and 1212D (one or more of which may be generally referred to as UEs 1212) to the core network 1206 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 1200 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 1200 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs 1212 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 1210 and other communication devices.
  • the network nodes 1210 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 1212 and/or with other network nodes or equipment in the telecommunication network 1202 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 1202.
  • the core network 1206 connects the network nodes 1210 to one or more hosts, such as host 1216. 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 1206 includes one more core network nodes (e.g., core network node 1208) 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 1208.
  • 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 (SIDE), 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
  • SIDE Subscription Identifier De-concealing function
  • UDM Unified Data Management
  • SEPP Security Edge Protection Proxy
  • NEF Network Exposure Function
  • UPF User Plane Function
  • the host 1216 may be under the ownership or control of a service provider other than an operator or provider of the access network 1204 and/or the telecommunication network 1202 and may be operated by the service provider or on behalf of the service provider.
  • the host 1216 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 1200 of Figure 12 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 (Light Fidelity), and/or any low-power wide-area network (LPWAN) standards such as LoRa (Long Range) and Sigfox.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • 6G wireless local area network
  • WiFi wireless local area network
  • the telecommunication network 1202 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 1202 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1202. For example, the telecommunications network 1202 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)/Massive loT (Internet of Things) services to yet further UEs.
  • URLLC Ultra Reliable Low Latency Communication
  • eMBB Enhanced Mobile Broadband
  • mMTC Massive Machine Type Communication
  • Massive loT Internet of Things
  • the UEs 1212 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network 1204 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1204.
  • 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
  • the hub 1214 communicates with the access network 1204 to facilitate indirect communication between one or more UEs (e.g., UE 1212C and/or 1212D) and network nodes (e.g., network node 1210B).
  • the hub 1214 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs.
  • the hub 1214 may be a broadband router enabling access to the core network 1206 for the UEs.
  • the hub 1214 may be a controller that sends commands or instructions to one or more actuators in the UEs.
  • the hub 1214 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 1214 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1214 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1214 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • the hub 1214 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 1214 may have a constant/persistent or intermittent connection to the network node 1210B.
  • the hub 1214 may also allow for a different communication scheme and/or schedule between the hub 1214 and UEs (e.g., UE 1212C and/or 1212D), and between the hub 1214 and the core network 1206.
  • the hub 1214 is connected to the core network 1206 and/or one or more UEs via a wired connection.
  • the hub 1214 may be configured to connect to an M2M service provider over the access network 1204 and/or to another UE over a direct connection.
  • UEs may establish a wireless connection with the network nodes 1210 while still connected via the hub 1214 via a wired or wireless connection.
  • the hub 1214 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 1210B.
  • the hub 1214 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 1210B, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
  • FIG. 13 shows a UE 1300 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 to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).
  • the UE 1300 includes processing circuitry 1302 that is operatively coupled via a bus 1304 to an input/output interface 1306, a power source 1308, a memory 1310, a communication interface 1312, and/or any other component, or any combination thereof.
  • Certain UEs may utilize all or a subset of the components shown in Figure 13. 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 1302 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 1310.
  • the processing circuitry 1302 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 1302 may include multiple central processing units (CPUs).
  • the input/output interface 1306 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 1300.
  • 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 1308 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 1308 may further include power circuitry for delivering power from the power source 1308 itself, and/or an external power source, to the various parts of the UE 1300 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 1308.
  • Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1308 to make the power suitable for the respective components of the UE 1300 to which power is supplied.
  • the memory 1310 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 readonly memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth.
  • the memory 1310 includes one or more application programs 1314, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1316.
  • the memory 1310 may store, for use by the UE 1300, any of a variety of various operating systems or combinations of operating systems.
  • the memory 1310 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.’
  • eUICC embedded UICC
  • iUICC integrated UICC
  • SIM card removable UICC commonly known as ‘SIM card.’
  • the memory 1310 may allow the UE 1300 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 1310, which may be or comprise a device-readable storage medium.
  • the processing circuitry 1302 may be configured to communicate with an access network or other network using the communication interface 1312.
  • the communication interface 1312 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1322.
  • the communication interface 1312 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 1318 and/or a receiver 1320 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).
  • the transmitter 1318 and receiver 1320 may be coupled to one or more antennas (e.g., antenna 1322) and may share circuit components, software or firmware, or alternatively be implemented separately.
  • communication functions of the communication interface 1312 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 1312, 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 in the form of an loT device comprises circuitry and/or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 1300 shown in Figure 13.
  • 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 14 shows a network node 1400 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 1400 includes a processing circuitry 1402, a memory 1404, a communication interface 1406, and a power source 1408.
  • the network node 1400 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 1400 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 1400 may be configured to support multiple radio access technologies (RATs).
  • RATs radio access technologies
  • some components may be duplicated (e.g., separate memory 1404 for different RATs) and some components may be reused (e.g., a same antenna 1410 may be shared by different RATs).
  • the network node 1400 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1400, 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 1400.
  • RFID Radio Frequency Identification
  • the processing circuitry 1402 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 1400 components, such as the memory 1404, to provide network node 1400 functionality.
  • the processing circuitry 1402 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1402 includes one or more of radio frequency (RF) transceiver circuitry 1412 and baseband processing circuitry 1414. In some embodiments, the radio frequency (RF) transceiver circuitry 1412 and the baseband processing circuitry 1414 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 1412 and baseband processing circuitry 1414 may be on the same chip or set of chips, boards, or units.
  • SOC system on a chip
  • the processing circuitry 1402 includes one or more of radio frequency (RF) transceiver circuitry 1412 and baseband processing circuitry 1414.
  • the radio frequency (RF) transceiver circuitry 1412 and the baseband processing circuitry 1414 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 1404 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 1402.
  • 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 1404 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 1402 and utilized by the network node 1400.
  • the memory 1404 may be used to store any calculations made by the processing circuitry 1402 and/or any data received via the communication interface 1406.
  • the processing circuitry 1402 and memory 1404 is integrated.
  • the communication interface 1406 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE.
  • the communication interface 1406 comprises port(s)/terminal(s) 1416 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface 1406 also includes radio front-end circuitry 1418 that may be coupled to, or in certain embodiments a part of, the antenna 1410.
  • Radio front-end circuitry 1418 comprises filters 1420 and amplifiers 1422.
  • the radio front-end circuitry 1418 may be connected to an antenna 1410 and processing circuitry 1402.
  • the radio front-end circuitry may be configured to condition signals communicated between antenna 1410 and processing circuitry 1402.
  • the radio front-end circuitry 1418 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 1418 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1420 and/or amplifiers 1422. The radio signal may then be transmitted via the antenna 1410. Similarly, when receiving data, the antenna 1410 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1418. The digital data may be passed to the processing circuitry 1402. In other embodiments, the communication interface may comprise different components and/or different combinations of components.
  • the network node 1400 does not include separate radio front-end circuitry 1418, instead, the processing circuitry 1402 includes radio front-end circuitry and is connected to the antenna 1410. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1412 is part of the communication interface 1406. In still other embodiments, the communication interface 1406 includes one or more ports or terminals 1416, the radio front-end circuitry 1418, and the RF transceiver circuitry 1412, as part of a radio unit (not shown), and the communication interface 1406 communicates with the baseband processing circuitry 1414, which is part of a digital unit (not shown).
  • the antenna 1410 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna 1410 may be coupled to the radio front-end circuitry 1418 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • the antenna 1410 is separate from the network node 1400 and connectable to the network node 1400 through an interface or port.
  • the antenna 1410, communication interface 1406, and/or the processing circuitry 1402 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.
  • the antenna 1410, the communication interface 1406, and/or the processing circuitry 1402 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 1408 provides power to the various components of network node 1400 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source 1408 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1400 with power for performing the functionality described herein.
  • the network node 1400 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 1408.
  • the power source 1408 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 1400 may include additional components beyond those shown in Figure 14 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 1400 may include user interface equipment to allow input of information into the network node 1400 and to allow output of information from the network node 1400. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1400.
  • FIG 15 is a block diagram of a host 1500, which may be an embodiment of the host 1216 of Figure 12, in accordance with various aspects described herein.
  • the host 1500 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 1500 may provide one or more services to one or more UEs.
  • the host 1500 includes processing circuitry 1502 that is operatively coupled via a bus 1504 to an input/output interface 1506, a network interface 1508, a power source 1510, and a memory 1512.
  • processing circuitry 1502 that is operatively coupled via a bus 1504 to an input/output interface 1506, a network interface 1508, a power source 1510, and a memory 1512.
  • 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 Figures 13 and 14, such that the descriptions thereof are generally applicable to the corresponding components of host 1500.
  • the memory 1512 may include one or more computer programs including one or more host application programs 1514 and data 1516, which may include user data, e.g., data generated by a UE for the host 1500 or data generated by the host 1500 for a UE.
  • Embodiments of the host 1500 may utilize only a subset or all of the components shown.
  • the host application programs 1514 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 1514 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 1500 may select and/or indicate a different host for over-the-top services for a UE.
  • the host application programs 1514 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. 16 is a block diagram illustrating a virtualization environment 1600 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 1600 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 virtual node does not require radio connectivity (e.g., a core network node or host)
  • the node may be entirely virtualized.
  • Applications 1602 (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 1604 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 1606 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1608 A and 1608B (one or more of which may be generally referred to as VMs 1608), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein.
  • the virtualization layer 1606 may present a virtual operating platform that appears like networking hardware to the VMs 1608.
  • the VMs 1608 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1606.
  • a virtualization layer 1606 Different embodiments of the instance of a virtual appliance 1602 may be implemented on one or more of VMs 1608, 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 1608 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 1608, and that part of hardware 1604 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 1608 on top of the hardware 1604 and corresponds to the application 1602.
  • Hardware 1604 may be implemented in a standalone network node with generic or specific components. Hardware 1604 may implement some functions via virtualization.
  • hardware 1604 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 1610, which, among others, oversees lifecycle management of applications 1602.
  • hardware 1604 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.
  • some signaling can be provided with the use of a control system 1612 which may alternatively be used for communication between hardware nodes and radio units.
  • Figure 17 shows a communication diagram of a host 1702 communicating via a network node 1704 with a UE 1706 over a partially wireless connection in accordance with some embodiments.
  • host 1702 Like host 1500, embodiments of host 1702 include hardware, such as a communication interface, processing circuitry, and memory.
  • the host 1702 also includes software, which is stored in or accessible by the host 1702 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 1706 connecting via an over-the-top (OTT) connection 1750 extending between the UE 1706 and host 1702. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 1750.
  • OTT over-the-top
  • the network node 1704 includes hardware enabling it to communicate with the host 1702 and UE 1706.
  • connection 1760 may be direct or pass through a core network (like core network 1206 of Figure 12) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks.
  • a core network like core network 1206 of Figure 12
  • 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 1706 includes hardware and software, which is stored in or accessible by UE 1706 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 1706 with the support of the host 1702.
  • 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 1706 with the support of the host 1702.
  • an executing host application may communicate with the executing client application via the OTT connection 1750 terminating at the UE 1706 and host 1702.
  • 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 1750 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 1750.
  • the OTT connection 1750 may extend via a connection 1760 between the host 1702 and the network node 1704 and via a wireless connection 1770 between the network node 1704 and the UE 1706 to provide the connection between the host 1702 and the UE 1706.
  • the connection 1760 and wireless connection 1770, over which the OTT connection 1750 may be provided, have been drawn abstractly to illustrate the communication between the host 1702 and the UE 1706 via the network node 1704, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • the host 1702 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 1706.
  • the user data is associated with a UE 1706 that shares data with the host 1702 without explicit human interaction.
  • the host 1702 initiates a transmission carrying the user data towards the UE 1706.
  • the host 1702 may initiate the transmission responsive to a request transmitted by the UE 1706.
  • the request may be caused by human interaction with the UE 1706 or by operation of the client application executing on the UE 1706.
  • the transmission may pass via the network node 1704, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1712, the network node 1704 transmits to the UE 1706 the user data that was carried in the transmission that the host 1702 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1714, the UE 1706 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1706 associated with the host application executed by the host 1702.
  • the UE 1706 executes a client application which provides user data to the host 1702.
  • the user data may be provided in reaction or response to the data received from the host 1702.
  • the UE 1706 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 1706. Regardless of the specific manner in which the user data was provided, the UE 1706 initiates, in step 1718, transmission of the user data towards the host 1702 via the network node 1704.
  • the network node 1704 receives user data from the UE 1706 and initiates transmission of the received user data towards the host 1702.
  • the host 1702 receives the user data carried in the transmission initiated by the UE 1706.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE 1706 using the OTT connection 1750, in which the wireless connection 1770 forms the last segment..
  • factory status information may be collected and analyzed by the host 1702.
  • the host 1702 may process audio and video data which may have been retrieved from a UE for use in creating maps.
  • the host 1702 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights).
  • the host 1702 may store surveillance video uploaded by a UE.
  • the host 1702 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 1702 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 1702 and/or UE 1706.
  • sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1750 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 1750 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 1704. 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 1702.
  • the measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1750 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.
  • 3GPP TS 38.331 v.17.0.0 (2022-03) 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC); Protocol specification (Release 17)
  • RRC Radio Resource Control
  • Protocol specification (Release 17)

Abstract

A method performed by a network node (1210A, 1210B, 1400, 1602, 1704) includes receiving (201) multiple physical random access channel, PRACH, transmissions from a user equipment, UE, (1212A, 1212B, 1212C, 1212D, 1300, 1608A, 1608B, 1706) in Msg1. The method includes responsive to receiving the multiple PRACH transmissions, signaling (203) to the UE (1212A, 1212B, 1212C, 1212D, 1300, 1608A, 1608B, 1706) one or more of: a single transmit power control, TPC, command (205); multiple TPC values in a random access response, RAR, corresponding to multiple PRACH transmission power of multiple uplink, UE, transmit, Tx, beams (207); a single timing advance command, TAC, (209); and/or multiple TAC values in a RAR corresponding to multiple PRACH transmissions with multiple UE Tx beams (211). Analogous network nodes, computer program, and computer program products are provided. Analogous UE methods, UEs, computer program, and computer program products are provided.

Description

USER EQUIPMENT INTERPRETATION OF TRANSMIT POWER CONTROL (TPC) AND TIMING ADVANCE COMMAND (TAC) IN RANDOM ACCESS RESPONSE (RAR) FOR MULTIPLE PHYSICAL RANDOM ACCESS CHANNEL (PRACH) TRANSMISSIONS
TECHNICAL FIELD
[0001] The present disclosure relates generally to communications, and more particularly to communication methods and related devices and nodes supporting wireless communications.
BACKGROUND
[0002] Random access channel (RACH) repetition was introduced in Rel-13 WIs of "Further LTE Physical Layer Enhancements for MTC" and “NarrowBand Internet of things (IOT) (NB-IOT)”to extend coverage.
[0003] RACH repetition LTE (long term evolution) eMTC (enhanced machine type communication) , NB-IoT
[0004] Repetition of the information is the main technique to achieve coverage enhancements. It is used for all physical channels available for coverage enhanced user equipments (UEs), i.e., 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) and PRACH (physical random access channel).
[0005] The UE decides the repetition level for the initial PRACH transmission. The repetition levels that the cell supports (e.g., 5, 10, and 15 dB) are included in the system information and the UE selects one of the repetition levels based on e.g., the estimated channel quality.
[0006] During the initial random access:
• The UE measures the downlink (DL) quality.
• The UE selects a suitable repetition level for its initial PRACH preamble transmission among, e.g., 4 levels. • If the UE does not receive a random access response (RAR), the UE increases its PRACH repetition level
• The numbers of repetitions for RAR and following messages will depend on the level for the successful PRACH
[0007] 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 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 chooses 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, the UE 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 a system information block (SIB).
[0008] The RAR message is scheduled with M-PDCCH and an associated PDSCH. The UE knows 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 SIB).
[0009] To enable different operation modes depending on a UE’s need of coverage extension, two coverage enhancement modes have been introduced for RRC_CONNECTED (radio resource control_connected) UEs:
• CE (coverage enhancement) mode A for no or small coverage enhancement, requiring a few (e.g., up to a few tens of) repetitions.
• CE mode B for a medium to large coverage enhancement, requiring several (e.g., hundreds of) repetitions.
• The CE mode is signaled to the UE by the network.
[0010] Coverage enhancement modes: The UE moves from no or small coverage enhancements (CE mode A) to large coverage enhancements (CE mode B) when signaled. The goal is to only keep a UE in CE mode B if the UE is not able to do synchronization acquisition, system information acquisition, random access or data transmission using small coverage operation. In enhanced coverage operation, the number of repetitions can be adapted according to the UE’s coverage situation.
[0011] 36.321 V17.0.0 [0012] If the UE is a BL UE (bandwidth reduced low complexity UE) or a UE in enhanced coverage: if the random access preamble was transmitted in a non-terrestrial network: o RA Response window starts at the subframe that contains the end of the last preamble repetition plus 3 + UE-eNB RTT subframes, as specified in TS 36.213 and has length ra-ResponseWindowSize for the corresponding enhanced coverage level; else: o RA Response 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.
[0013] If the UE is an NB-IoT UE: if the random access preamble was transmitted in a non-terrestrial network: o RA Response window starts at the subframe that contains the end of the last preamble repetition plus X + UE-eNB RTT subframes, as specified in TS 36.213 and has length ra-ResponseWindowSize for the corresponding enhanced coverage level, where value X is determined from Table 5.1.4-1 based on the used preamble format and the number of NPRACH repetitions; else: o RA Response 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 from Table 5.1.4-1 based on the used preamble format and the number of NPRACH repetitions.
[0014] The RA-RNTI (random access-radio network temporary identifier associated with the PRACH in which the Random Access Preamble is transmitted, is computed as:
RA-RNTI= 1 + t_id + 10*f_id where t_id is the index of the first subframe of the specified PRACH (0< t_id <10), and 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 fRA , where fRA is defined in clause 5.7.1 of TS 36.211.
[0015] For BL UEs and UEs in enhanced coverage, 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)) where 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, and Wmax is 400, maximum possible RAR window size in subframes for BL UEs or UEs in enhanced coverage. If the PRACH resource is on a TDD carrier, the f_id is set to fRA, where
Figure imgf000006_0001
is defined in clause 5.7.1 of TS 36.211.
[0016] For NB-IoT UEs, 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 where SFN_id is the index of the first radio frame of the specified PRACH and carrier_id is the index of the UL carrier associated with the specified PRACH. The carrier_id of the anchor carrier is 0.
[0017] LTE eMTC (Section 5.7.1 in 36.211)
[0018] For BL/CE UEs, for each PRACH coverage enhancement level, there is a PRACH configuration configured by higher layers with a PRACH configuration index (prach- Configurationlndex), a PRACH frequency offset «pRBOftset (prach-FrequencyOffset , a number of
PRACH repetitions per attempt lVr PpACH (numReyetitionPerPreambleAttemyt) and optionally a PRACH starting subframe periodicity 1VS^CH (prach-StartingSubframe). PRACH of preamble format 0-3 is transmitted lVr p epACH > 1 times, whereas PRACH of preamble format 4 is transmitted one time only.
[0019] For BL/CE UEs and for each PRACH coverage enhancement level, if frequency hopping is enabled for a PRACH configuration by the higher-layer parameter prach- HoppingConfig, the value of the parameter n^B offset depends on the SFN (system frame number) and the PRACH configuration index and is given by
[0020] In case the PRACH configuration index is such that a PRACH resource occurs in every radio frame when calculated as below from Table 5.7.1-2 or Table 5.7.1-4, if ty mod 2 = 0
Figure imgf000006_0002
if ty mod 2 = 1
[0021] otherwise
Figure imgf000006_0003
where nt is the system frame number corresponding to the first subframe for each PRACH repetition, pR^hop corresponds to a cell-specific higher-layer parameter prach-HoppingOffset. If frequency hopping is not enabled for the PRACH configuration then HpBB offset =
Figure imgf000007_0001
[0022] For frame structure type 1 with preamble format 0-3, for each of the PRACH configurations there is at most one random access resource per subframe.
[0023] For frame structure type 2 with preamble formats 0-4, for each of the PRACH configurations there might be multiple random access resources in an UL subframe (or UpPTS for preamble format 4) depending on the UL/DL configuration [see table 4.2-2]. Table 5.7.1-3 lists PRACH configurations allowed for frame structure type 2 where the configuration index corresponds to a certain combination of preamble format, PRACH density value, Z)RA and version index, rK i.
[0024] For frame structure type 2 with PRACH configuration indices 0, 1, 2, 20, 21, 22, 30, 31, 32, 40, 41, 42, 48, 49, 50, or with PRACH configuration indices 51, 53, 54, 55, 56, 57 in UL/DL configuration 3, 4, 5, the UE may for handover purposes assume an absolute value of the relative time difference between radio frame in the current cell and the target cell is less than 153600 Ts.
Table 5.7.1-3: Frame structure type 2 random access configurations for preamble formats 0-4
Figure imgf000007_0007
[0025] Table 5.7.1-4 lists the mapping to physical resources for the different random access opportunities needed for a certain PRACH density value, DRA. Each quadruple of the format
Figure imgf000007_0002
^R ’ RA ) indicates the location of a specific random access resource, where fRA is a frequency resource index within the considered time instance,
Figure imgf000007_0003
= 0,1,2 indicates whether the resource is reoccurring in all radio frames, in even radio frames, or in odd radio frames, respectively,
Figure imgf000007_0004
= 0,1 indicates whether the random access resource is located in first half frame or in second half frame, respectively, and where
Figure imgf000007_0005
is the 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
Figure imgf000007_0006
is denoted as (*). The start of the random access preamble formats 0-3 shall be aligned with the start of the corresponding uplink subframe at the UE assuming NTA = 0 and the random access preamble format 4 shall start 4832 • Ts before the end of the UpPTS at the UE, where the UpPTS (Uplink
Pilot Time Slot) is referenced to the UE's uplink frame timing assuming N TA = 0.
[0026] 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 DRA without overlap in time. For preamble format 0-3, the frequency multiplexing shall be done according to
Figure imgf000008_0001
where NUL RB is the number of uplink resource blocks, nRA PRB is the first physical resource block allocated to the PRACH opportunity considered and where nRA PRB offset is the first physical resource block available for PRACH.
[0027] For BL/CE UEs, only a subset of the subframes allowed for preamble transmission are allowed as starting subframes for the NrepP RACH repetitions. The allowed starting subframes for a PRACH configuration are determined as follows:
Enumerate the subframes that are allowed for preamble transmission for the PRACH configuration as nRA sf = 0, . . . NRA sf - 1 where nRA sf = 0 and nRA sf = nRA sf — 1 correspond to the two subframes allowed for preamble transmission with the smallest and the largest absolute subframe number , respectively.
If a PRACH starting subframe periodicity N PRACH s ta rt isnot provided by higher layers, the periodicity of the allowed starting subframes in terms of subframes allowed for preamble transmission is NrepP RACH. The allowed starting subframes defined over nPA = 0, . . . — 1 are given by jNrepP RACH where j = 0, 1, 2, ...
If a PRACH starting subframe periodicity N PRACH s tart is provided by higher layers, it indicates the periodicity of the allowed starting subframes in terms of subframes allowed for preamble transmission. The allowed starting subframes defined over = 0, . . . — 1 are given by j N PRACH s tart + NrepP RACH where j = 0, 1, 2, ...
No starting subframe defined over NRA sf = 0, . . . — 1 such that NRA sf > NRA sf — NrepP RACH is allowed.
[0028] Each random access preamble occupies a bandwidth corresponding to 6 consecutive resource blocks for both frame structures. Table 5.7.1-4: Frame structure type 2 random access preamble mapping in time and frequency
Figure imgf000009_0003
[0029] NB-IoT (section 10.1.6 of 36.211)
[0030] The physical layer random access preamble is based on single-subcarrier frequencyhopping symbol groups. A symbol group consists of a cyclic prefix of length TCP and a sequence of N identical symbols with total length TSEQ (an illustration of a symbol group is shown in Figure 10.1.6-1-1 of 3GPP TS 36.211). 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 parameters for frame structure 2 is listed in Table 10.1.6.1-2 below.
Table 10.1.6.1-2: Random access preamble parameters for frame structure type 2
Figure imgf000009_0004
[0031] The preamble consisting of P symbol groups shall be transmitted /VrcpRACH times. For frame structure type 2, when an invalid uplink subframe overlaps the transmission of G symbol groups without a gap, the G symbol groups are dropped. For frame structure type 2, the transmission of G symbol groups are aligned with the subframe boundary.
[0032] The frequency location of the NPRACH transmission is constrained within
Figure imgf000009_0001
= 12 sub-carriers, and within NR C A = 36 subcarriers when preamble format 2 as described in Table 10.1.6.1-1 of 3GPP TS 36.211 is configured. Frequency hopping shall be used within the 12 subcarriers and 36 subcarriers when preamble format 2 as described in Table 10.1.6.1-1 of 3GPP TS 36.211 is configured, where the frequency location of the ith symbol group is given by
Figure imgf000009_0002
The quantity ns (i) depends on the frame structure.
[0033] NR specification up to Rel-17 [0034] Sequence generation
[0035] Clause 6.3.3.1 in 38.211
[0036] There are 64 preambles defined in each time-frequency PRACH occasion, enumerated in increasing order of first increasing cyclic shift of a logical root sequence, and then in increasing order of the logical root sequence index, starting with the index obtained from the higher-layer parameter prach-RootSequencelndex or rootSequencelndex-BFR. Additional preamble sequences, in case 64 preambles cannot be generated from a single root Zadoff-Chu sequence, are obtained from the root sequences with the consecutive logical indexes until all the 64 sequences are found. The logical root sequence order is cyclic; the logical index 0 is consecutive to 837 when LRA = 839 and is consecutive to 137 when LRA = 139. The sequence number u is obtained from the logical root sequence index according to Tables 6.3.3.1-3 and 6.3.3.1-4 of 3GPP TS 38.211.
[0037] The cyclic shift Cv is given by
Figure imgf000010_0001
where the first and second rows are for unrestricted sets, the third row is for restricted sets type A and B and the fourth and fifth rows are for restricted sets type B, and Ncs is given by Tables 6.3.3.1-5 to 6.3.3.1-7 of 3GPP TS 38.211, the higher-layer parameter restrictedSetConfig determines the type of restricted sets (unrestricted, restricted type A, restricted type B), and Tables 6.3.3.1-1 and 6.3.3.1-2 indicate the type of restricted sets supported for the different preamble formats.
[0038] Parameters for determining the root sequence and their cyclic shifts in the PRACH preamble sequence set may include one or more of: sequence length
A logic index to the root sequence table (Table 6.3.3.1-3 to Table 6.3.3.1-4B in 38.211)
- A preamble SCS (Table 6.3.3.1-5 to Table 6.3.3.1-7 in 38.211) o if SCS = 1.25/5kHz unrestricted, restricted set A, or restricted set B
[0039] Mapping to physical resources
[0040] Clause 6.3.3.2 in 38.211 [0041] Random access preambles can only be transmitted in the time resources given by the higher-layer parameter prach-Configurationlndex according to Tables 6.3.3.2-2 to 6.3.3.2-4 of 3GPP TS 38.211 (reproduced below) and depends on FR1 or FR2 and the spectrum type as defined in 3GPP TS 38.104.
[0042] For the purpose of slot numbering in the tables, the following subcarrier spacing shall be assumed:
15 kHz for FRl
60 kHz for FR2.
[0043] Number of time domain RACH occasions within a RACH slot for each PRACH configuration index is fixed.
Table 6.3.3.2-3: Random access configurations for FR1 and unpaired spectrum
Figure imgf000011_0001
Table 6.3.3.2-4: Random access configurations for FR2 and unpaired spectrum
Figure imgf000011_0002
Figure imgf000011_0003
[0044] Validity check and collision handling
[0045] Section 8.1 of 38.213. V17.1.0
[0046] For unpaired spectrum, if a UE is not provided tdd-UL-DL-ConfigurationCommon, a PRACH occasion in a PRACH slot is valid if it does not precede a SS/PBCH block in the PRACH slot and starts at least lVgap symbols after a last SS/PBCH block reception symbol, where lVgap is provided in Table 8.1-2 and, if channelAccessMode = "semiStatic" is provided, does not overlap with a set of consecutive symbols before the start of a next channel occupancy time where the UE does not transmit [TS 37.213]. the candidate SS/PBCH block index of the SS/PBCH block corresponds to the SS/PBCH block index provided by ssb-PositionsInBurst in SIBI or in ServingCellConfigCommon , as described in clause 4.1 If a UE is provided tdd-UL-DL-ConfigurationCommon, a PRACH occasion in a PRACH slot is valid if it is within UL symbols, or it does not precede a SS/PBCH block in the PRACH slot and starts at least Agap symbols after a last downlink symbol and at least Agap symbols after a last SS/PBCH block symbol, where Agap is provided in Table 8.1-2, and if channelAccessMode = "s emiSt atic" is provided, does not overlap with a set of consecutive symbols before the start of a next channel occupancy time where there shall not be any transmissions, as described in [TS 37.213] the candidate SS/PBCH block index of the SS/PBCH block corresponds to the SS/PBCH block index provided by ssb-PositionsInBurst in SIBI or in ServingCellConfigCommon, as described in clause 4.1.
[0047] For preamble format B4 (TS 38.211), Agap = 0.
[0048] Section 11.1 of 38.213 V17.1.0
[0049] 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 Tproc 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 [TS38.214], determined from clauses 9 and 9.2.5 or clause 6.1 of [TS38.214], or the PRACH transmission in the set of symbols.
If the UE indicates the capability of [partialCancellation], 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 Tproc 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 [TS 38.214], determined from clauses 9 and 9.2.5 or clause 6.1 of [TS 38.214], or the PRACH transmission in remaining symbols from the set of symbols.
[0050] MSG1 power determination
[0051] Section 7.4 of 38.213 V17.1.0
[0052] 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.
Figure imgf000013_0001
[0053] If within a random access response window, as described in Clause 8.2, the UE does not receive a random access response that contains a preamble identifier corresponding to the preamble sequence transmitted by the UE, the UE determines a transmission power for a subsequent PRACH transmission, if any, as described in TS 38.321.
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 as described in (TS 38.321) [0054] 5.1.3 of 38.321 V17.0.0
[0055] The MAC (medium access control) entity shall, for each Random Access Preamble: 1> if PREAMBLE_TRANSMISSION_COUNTER is greater than one; and 1> if the notification of suspending power ramping counter has not been received from lower layers; and
1> if SSB (synchronization signal block) or CSI-RS (channel state informationreference signal) selected is not changed from the selection in the last Random Access Preamble transmission:
2> increment PREAMBLE_POWER_RAMPING_COUNTER by 1.
1> select the value of DELTA_PREAMBLE according to clause 7.3;
1> set PREAMBLE_RECEIVED_TARGET_POWER to preambleReceivedTargetPower + DELT A_PRE AMBLE + (PREAMBLE_POWER_RAMPING_COUNTER - 1) x PREAMBLE_POWER_RAMPING_STEP;
1> except for contention-free Random Access Preamble for beam failure recovery request, compute the RA-RNTI associated with the PRACH occasion in which the Random Access Preamble is transmitted;
1> instruct the physical layer to transmit the Random Access Preamble using the selected PRACH occasion, corresponding RA-RNTI (if available), PREAMBLEJNDEX and PREAMBLE_RECEIVED_TARGET_POWER. [0056] Msg3 transmission power
[0057] 7.1.1 of 38.213 V17.1.0
[0058] If a UE transmits a PUSCH on active UL BWP b of carrier f of serving cell c using parameter set configuration with index j and PUSCH power control adjustment state with index
I, the UE determines the PUSCH transmission power PpuscH,b,f,c(i,j,qd, l) in PUSCH transmission occasion i as
Figure imgf000014_0001
where,
[0059] For the PUSCH power control adjustment state fb,f,c(i, l) for active UL BWP b of carrier f of serving cell c in PUSCH transmission occasion i
[0060] If 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 as described in Clause 8
Figure imgf000014_0002
-8msg2,b,f,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, and
Figure imgf000014_0003
and Δ Prampupr equested ,b ,f ,c 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 c,
Figure imgf000014_0004
MPUSCH RB,b,f ,c(0) 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 ATF ,b , f,c(0) is the power adjustment of first PUSCH transmission on active UL BWP b of carrier f of serving cell c. [0061] 8.2 of TS 38.213
[0062] The TPC command value 8msg2 b c is used for setting the power of the PUSCH transmission, as described in Clause 7.1.1, and is interpreted according to Table 8.2-2.
Table 8.2-2: TPC Command 8msg2 b c for PUSCH
Figure imgf000015_0003
[0063] an association between DL signal/channel, and a subset of RACH resources and/or a subset of preamble indices
[0064] Clause 8.1 in 38.213
[0065] 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.
[0066] if N < 1, one SS/PBCH block index is mapped to VN 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
Figure imgf000015_0001
1, R contention based preambles with consecutive indexes associated with SS/PBCH block index n, 0 N - 1, per valid PRACH occasion start from preamble index n •
Figure imgf000015_0002
/ N where
^tota mble 's provided by totalNumberOfRA-Preambles for Type-1 random access procedure. [0067] SS/PBCH block indexes provided by ssb-PositionsInBurst in SIB1 or in ServingCellConfigCommon are mapped to valid PRACH occasions in the following order where the parameters are described in TS 38.211
- First, in increasing order of preamble indexes within a single PRACH occasion
- Second, in increasing order of frequency resource indexes for frequency multiplexed PRACH occasions
- Third, in increasing order of time resource indexes for time multiplexed PRACH occasions within a PRACH slot
- Fourth, in increasing order of indexes for PRACH slots [0068] 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 Table 8.1-1 such that W^B SS/PBCH blocks are mapped at least once to the PRACH occasions within the association period, where a UE obtains W^B from the value of ssb- PositionsInBurst in SIB 1 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 W^fB SS/PBCH blocks, no SS/PBCH blocks are mapped to the set of PRACH occasions or PRACH preambles. 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.
[0069] 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.
[0070] For the indicated preamble index, the ordering of the PRACH occasions is: First, in increasing order of frequency resource indexes for frequency multiplexed PRACH occasions
Second, in increasing order of time resource indexes for time multiplexed PRACH occasions within a PRACH slot
Third, in increasing order of indexes for PRACH slots Table 8.1-1: Mapping between PRACH configuration period and SS/PBCH block to PRACH occasion association period
Figure imgf000016_0001
[0071] From 3GPP TS 38.331 V17.0.0
RACH-ConfigCommon IE
RACH-ConfigCommon ::= SEQUENCE { rach-ConfigGeneric RACH-ConfigGeneric , totalNumberOfRA-Preambles INTEGER (1..63) OPTIONAL, - Need S ssb-perRACH-OccasionAndCB-PreamblesPerSSB CHOICE { oneEighth ENUMERATED {n4,n8,nl2,nl6,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64}, oneFourth ENUMERATED {n4,n8,nl2,nl6,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64}, oneHalf ENUMERATED {n4,n8,nl2,nl6,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64}, one ENUMERATED {n4,n8,nl2,nl6,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64}, two ENUMERATED {n4,n8,nl2,nl6,n20,n24,n28,n32}, four INTEGER (1..16), eight INTEGER (1..8), sixteen INTEGER (1..4) } OPTIONAL, - Need M groupBconfigured SEQUENCE { ra-Msg3SizeGroupA ENUMERATED {b56, bl44, b208, b256, b282, b480, b640, b800, blOOO, b72, spared, spare5,spare4, spare3, spare2, sparel }, messagePowerOffsetGroupB ENUMERATED { minusinfinity, dBO, dB5, dB8, dB10, dB12, dB15, dB18}, numberOfRA-PreamblesGroupA INTEGER (1..64) } OPTIONAL, — Need R ra-ContentionResolutionTimer ENUMERATED { sf8, sfl6, sf24, sf32, sf40, sf48, sf56, sf64}, rsrp-ThresholdSSB RSRP-Range OPTIONAL, — Need R rsrp-ThresholdSSB-SUL RSRP-Range OPTIONAL, - Cond SUL prach-RootSequencelndex CHOICE { 1839 INTEGER (0..837), 1139 INTEGER (0..137) }, msg 1 -SubcarrierSpacing SubcarrierSpacing OPTIONAL, — Cond L139 restrictedSetConfig ENUMERATED {unrestrictedSet, restrictedSetTypeA, restrictedSetTypeB } , msg3-transformPrecoder ENUMERATED {enabled} OPTIONAL, — Need R
[[ ra-PrioritizationForAccessIdentity-rl6 SEQUENCE { ra-Prioritization-r 16 RA-Prioritization, ra-PrioritizationForAI-rl6 BIT STRING (SIZE (2)) } OPTIONAL, — Cond InitialBWP-Only prach-RootSequence!ndex-rl6 CHOICE { 1571 INTEGER (0..569), 11151 INTEGER (0..1149) } OPTIONAL - Need R ]], [[ ra-PrioritizationForSlicing-rl7 RA-PrioritizationForSlicing-rl7 OPTIONAL, — Cond InitialBWP-Only featureCombinationPreambles-r 17 SEQUENCE (SIZE(l..maxFeatureCombPreambles- FFS-rl7)) OF FeatureCombinationPreambles-rl7 OPTIONAL — Need R ]] ServingCellConfigCommon IE
ServingCellConfigCommon ::= SEQUENCE { shortBitmap BIT STRING (SIZE (4)), mediumBitmap BIT STRING (SIZE (8)), longBitmap BIT STRING (SIZE (64)) } OPTIONAL, - Cond AbsFreqSSB ssb-periodicityServingCell ENUMERATED { ms5, ms 10, ms20, ms40, ms80, msl60, spare2, sparel } OPTIONAL, — Need S
[0072] RAR
[0073] Section 8.2 in 38.213 V17.L0
[0074] In response to a PRACH transmission, a UE attempts to detect a DCI format l_0 with CRC scrambled by a corresponding RA-RNTI during a window controlled by higher layers (TS 38.321). 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 as defined in Clause 10.1. The length of the window in number of slots, based on the SCS for Typel-PDCCH CSS set, is provided by ra-ResponseWindow .
[0075] The TPC command value 8msg2 b f c is used for setting the power of the PUSCH transmission, as described in Clause 7.1.1, and is interpreted according to Table 8.2-2. The CSI request field is reserved
Table 8.2.2: TPC Command 8mSg2 b c for PUSCH
Figure imgf000018_0001
[0076] Section 7.1.1
If 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 as described in Clause 8 fb,f,c( 0 Prampup,b,f,c 4” 8msg2,b,f,c’ where I 0 and 8mSg2,b,f,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,
[0077] SSB selection in MAC
[0078] In TS 38.321
[0079] RRC configures the following parameters for the Random Access 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 BeamFailureRecovery Config IE; 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 BeamFailureRecoveryConfig 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; powerRampingStep'. the power-ramping factor; powerRampingStepHighPriority. the power-ramping factor in case of prioritized Random Access procedure; scalingFactorBI'. 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 (see clause 7.4); 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 ; if groupBconfigured is configured, then Random Access Preambles group B is configured.
Amongst the contention-based Random Access Preambles associated with an SSB (as defined in TS 38.213), 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).
NOTE 2: If Random Access Preambles group B is supported by the cell Random Access Preambles group B is included for each SSB.
[0080] Beam failure recovery
[0081] Section 9.2.8 in 38.300
[0082] Beam failure detection and recovery
[0083] For beam failure detection, the gNB configures the UE with beam failure detection reference signals (SSB or 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.
[0084] SSB-based Beam Failure Detection is based on the SSB associated to the initial DL BWP and can only be configured for the initial DL BWPs and for DL BWPs containing the SSB associated to the initial DL BWP. For other DL BWPs, Beam Failure Detection can only be performed based on CSI-RS.
[0085] After beam failure is detected, the UE: triggers beam failure recovery by initiating a Random Access procedure on the PCell (primary cell); 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).
[0086] Upon completion of the Random Access procedure, beam failure recovery is considered complete.
[0087] Section 5.17 in 38.321 [0088] The MAC entity shall:
1> if beam failure instance indication has been received from lower layers: 2> start or restart the beamFailureDetectionTimer, 2> increment BFI_COUNTER by 1;
2> if BFI_COUNTER >= beamFailurelnstanceMaxCount:
3> initiate a Random Access procedure (see clause 5.1) on the SpCell (secondary primary Cell).
1> if the beamFailureDetectionTimer expires; or
1> if beamFailureDetectionTimer, beamFailurelnstanceMaxCount, or any of the reference signals used for beam failure detection is reconfigured by upper layers: 2> set BFI_COUNTER to 0.
1> if the Random Access procedure is successfully completed (see clause 5.1): 2> set BFI_COUNTER to 0;
2> stop the beamFailureRecoveryTimer, if configured;
2> consider the Beam Failure Recovery procedure successfully completed.
[0089] Section 6 of TS 38.213
[0090] A UE can be provided, for each BWP of a serving cell, a set q0 of periodic CSI-RS resource configuration indexes by failureDetectionResources and a set
Figure imgf000021_0001
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. If the UE is not provided failureDetectionResources, the UE determines the set q0 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 q0 includes RS indexes with QCL-TypeD configuration for the corresponding TCI states. The UE expects the set to include up to two RS indexes. The UE expects single port RS in the set q0.
[0091] In non-DRX mode operation, 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 q0 that the UE uses to assess the radio link quality is worse than the threshold Q0Ut,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 q0 that the UE uses to assess the radio link quality and 2 msec. In DRX mode operation, the physical layer provides an indication to higher layers when the radio link quality is worse than the threshold Q0Ut,LR with a periodicity determined as described in (TS 38.133).
[0092] 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
Figure imgf000022_0001
and the corresponding Ll-RSRP measurements that are larger than or equal to the Qin,LR threshold.
[0093] The UE may receive by PRACH-ResourceDedicatedBFR, a configuration for PRACH transmission as described in Clause 8.1. For PRACH transmission in slot n and according to antenna port quasi co-location parameters associated with periodic CSI-RS resource configuration or with SS/PBCH block associated with index qnew provided by higher layers (TS 38.321), the UE monitors PDCCH in a search space set provided by recoverySearchSpaceld for detection of a DO format with CRC scrambled by C-RNTI or MCS-C-RNTI starting from slot n + 4 within a window configured by BeamFailureRecoveryConfig. For PDCCH monitoring in a search space set provided by recoverySearchSpaceld and for corresponding PDSCH reception, the UE assumes the same antenna port quasi-collocation parameters as the ones associated with index qnew 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. 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.
[0094] 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 (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 a power determined as described in Clause 7.2.1 with qu = 0, qd = qnew, and I = 0.
[0095] After 28 symbols from a last symbol of a first PDCCH reception in a search space set provided by recoverySearchSpaceld where a UE detects a DCI format with CRC scrambled by C-RNTI or MCS-C-RNTI, the UE assumes same antenna port quasi-collocation parameters as the ones associated with index qnew for PDCCH monitoring in a CORESET with index 0. BeamFailureRecoveryConfig ::= SEQUENCE { rootSequencelndex-BFR INTEGER (0..137) OPTIONAL, - Need M rach-ConfigBFR RACH-ConfigGeneric OPTIONAL, — Need M rsrp-ThresholdSSB RSRP-Range OPTIONAL, — Need M candidateBeamRSList SEQUENCE (SIZE(L.maxNrofCandidateBeams)) OF PRACH-
ResourceDedicatedBFR OPTIONAL, — Need M ssb-perRACH-Occasion ENUMERATED {oneEighth, oneFourth, oneHalf, one, two, four, eight, sixteen} OPTIONAL, — Need M ra-ssb-OccasionMasklndex INTEGER (0..15) OPTIONAL, — Need M recoverySearchSpaceld SearchSpaceld OPTIONAL, — Need R ra-Prioritization RA-Prioritization OPTIONAL, — Need R beamFailureRecoveryTimer ENUMERATED {mslO, ms20, ms40, ms60, ms80, mslOO, msl50, ms200} OPTIONAL, - Need M
PRACH-ResourceDedicatedBFR ::= CHOICE { ssb BFR-SSB-Resource, csi-RS BFR-CSIRS-Resource
}
BFR-SSB-Resource ::= SEQUENCE { ssb SSB-Index, ra-Preamblelndex INTEGER (0..63),
}
BFR-CSIRS-Resource ::= SEQUENCE { csi-RS NZP-CSI-RS-Resourceld, ra-OccasionList SEQUENCE (SIZE(L.maxRA-OccasionsPerCSIRS)) OF INTEGER (0..maxRA-Occasions-l) OPTIONAL, — Need R ra-Preamblelndex INTEGER (0..63) OPTIONAL, - Need R
}
[0096] candidateBeamRSList, candidateBeamRSListExt-v 1610
[0097] The list of reference signals (CSI-RS and/or SSB) identifying the candidate beams for recovery and the associated RA parameters. 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
[0098] There currently exist certain challenge(s). In NR Rel-15, multiple PRACH transmissions was discussed for CFRA with some agreements, but it was not specified in the end. These agreements that were not specified in the end are:
[0099] Agreements:
[0100] For contention-free random access, the following options are under evaluation Option 1 : Transmission of only a single Msg.1 before the end of a monitored RAR window
Option 2: A UE can be configured to transmit multiple simultaneous Msg.l Note: multiple simultaneous Msg.l transmissions use different frequency resources and/or use the same frequency resource with different preamble indices Option 3: A UE can be configured to transmit multiple Msg.l over multiple RACH transmission occasions in the time domain before the end of a monitored RAR window
[0101] Agreements:
[0102] For contention free case, a UE can be configured to transmit multiple Msg.1 over dedicated multiple RACH transmission occasions in time domain before the end of a monitored RAR window if the configuration of dedicated multiple RACH transmission occasions in time domain is supported.
• Note: The time resource used for ‘dedicated RACH in time domain’ is different from the time resources of contention based random access
• Note: Multiple Msgl can be transmitted with same or different UE TX beams [0103] RACH Indication and Partitioning
[0104] As many features in rel-17 wanted to utilize msgl preambles to indicate early on the existence of certain features such as Msg3 repetitions, redcap, slicing and Short Data Transmissions. The solution was to introduce a common framework for allocating preambles in ROs and conditions for using these preambles groups as well as the combination of different features, such as Msg3 repetitions and Redcap. With this framework, it is possible to for instance define an RO#1 with a preamble group indicating Redcap and Msg3 repetitions, and then an RO#2 with a preamble group defining Short Data transmissions and Redcap+Msg3 Repetitions. The conditions to use these preamble groups are then defined. SUMMARY
[0105] In NR up to Rel-17, a UE is allowed to transmit one PRACH preamble for an attempt. As PRACH was identified as a coverage bottleneck, its coverage can be enhanced by the multiple PRACH transmissions in Rel-18.
[0106] Solutions for PRACH repetitions have been adopted in LTE eMTC and NB-IoT, including transmitting with the same transmit (Tx) power and how to interpret TPC and TAC command in RAR for Msg3. However, these may be not suitable for NR PRACH transmissions, especially for multiple NR PRACH transmissions with different UL Tx beams.
[0107] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. According to some embodiments, a method performed by a network node includes receiving multiple physical random access channel, PRACH, transmissions from a user equipment, UE, in Msgl. The method includes responsive to receiving the multiple PRACH transmissions, signaling to the UE one or more of: a single transmit power control, TPC command; multiple TPC values in a random access response, RAR, corresponding to multiple PRACH transmission power of multiple uplink, UL, transmit, Tx, beams; a single timing advance command, TAC; and/or multiple TAC values in a RAR corresponding to multiple PRACH transmissions with multiple UL Tx beams.
[0108] Analogous network nodes, computer programs, and computer program products are provided.
[0109] Certain embodiments may provide one or more of the following technical advantage(s). NR user equipment and network nodes using the embodiments may utilizes multiple NR PRACH transmissions with different UL Tx beams.
[0110] According to some other embodiments, a method performed by a user equipment includes transmitting multiple physical random access channel, PRACH, transmissions to a network node with a same beam or different beams, in Msgl. The method includes receiving, from the network node one or more of: a single transmit power control, TPC command; multiple TPC values in a random access response, RAR, corresponding to multiple PRACH transmission power of multiple uplink, UL, transmit, Tx, beams; a single timing advance command, TAC; and/or multiple TAC values in a RAR corresponding to multiple PRACH transmissions with multiple UL Tx beams.
[0111] Analogous UEs, computer programs, and computer program products are provided. BRIEF DESCRIPTION OF THE DRAWINGS
[0112] The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this application, illustrate certain non-limiting embodiments of inventive concepts. In the drawings:
[0113] Figure 1 is an illustration of various scenarios of multiple PRACH transmissions; [0114] Figures 2-5 are flowcharts illustrating operations of a network node according to some embodiments;
[0115] Figures 6-11 are flowcharts illustrating operations of a user equipment according to some embodiments;
[0116] Figure 12 is a block diagram of a communication system in accordance with some embodiments;
[0117] Figure 13 is a block diagram of a user equipment in accordance with some embodiments
[0118] Figure 14 is a block diagram of a network node in accordance with some embodiments;
[0119] Figure 15 is a block diagram of a host computer communicating with a user equipment in accordance with some embodiments;
[0120] Figure 16 is a block diagram of a virtualization environment in accordance with some embodiments; and
[0121] Figure 17 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 in accordance with some embodiments.
DETAILED DESCRIPTION
[0122] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art, in which examples of embodiments of inventive concepts are shown. Inventive concepts may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of present inventive concepts to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present/used in another embodiment. [0123] In NR Rel-15~17, a UE can transmit a PRACH preamble in a PRACH occasion associated with a selected SSB. RAR is QCLed with the SSB which the transmitted PRACH is associated with. TA, TPC fields in RAR are based on the received PRACH. If a UE doesn’t receive a RAR which contains its 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.
[0124] In Rel-18 Further NR Coverage Enhancements WI, one objective is to support multiple PRACH transmissions.
[0125] Specify following PRACH coverage enhancements (RAN 1 , RAN2) o Multiple PRACH transmissions with same beams for 4-step RACH procedure o Study, and if justified, specify PRACH transmissions with different beams for 4- step RACH procedure o Note 1: The enhancements of PRACH are targeting for FR2, and can also apply to FR1 when applicable. o Note 2: The enhancements of PRACH are targeting short PRACH formats, and can also apply to other formats when applicable.
[0126] There are several scenarios of multiple PRACH transmissions in terms of UL Tx beam and SSB, as illustrated in Figure 1. Scenario 1 is where a UE transmits multiple PRACHs with the same beam, i.e., the same UL spatial relation, and all the PRACH transmissions are associated with the same SSB.
[0127] In NR up to Rel-17, 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 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.
[0128] Scenario 2 shows that the 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. Scenario 3 and Scenario 4 are where the multiple PRACH transmissions are associated with different Tx SSB beams. In Scenario 3, there is only PRACH associated with each selected SSB, while in Scenario 4, at least one SSB is associated with more than one PRACH transmission. Scenario 4 is a combination of Scenario 3 and Scenario 2 and can use the solutions of both scenarios and therefore need not be discussed in further detail. [0129] Depending on the value of ssb-perRACH-OccasionAndCB-PreamblesPerSSB, there is an association between PRACH occasion and SS block or between PRACH preamble index and SS block. For brevity, it is called PRACH transmission associated with an SSB. “Multiple PRACH transmissions” refers to those of one RACH attempt, unless otherwise stated.
[0130] The embodiments described herein apply to CBRA and CFRA unless otherwise stated. Since contention-free Random Access Resources for beam failure recovery request can be associated with SSBs and/or CSI-RSs, for the sake of brevity, PRACH transmission associated SSB is used instead of PRACH transmission associated with SSB and/or CSI-RS.
[0131] The embodiments described apply to 4-step RACH and 2-step RACH. RAR includes Msg2 RAR for 4-step RACH and fallbackRAR for 2-step RACH. For the sake of brevity, it is call Msg2 RAR.
[0132] TAC and TPC in Msg2 RAR
[0133] Even if the same transmit power and UL Tx beam is used for multiple PRACH transmissions, gNB may receive them with different signal strengths due to the time-varying radio channel. Let alone it is possible that a UE may change its transmission power and/or conduct beam sweeping across multiple PRACH transmissions. If a gNB signals a single TPC in RAR, the gNB and UE need to be aligned on which PRACH transmission is the TPC command applies to for Msg3 transmission. This is a new problem for multiple PRACH transmissions.
[0134] Similarly, a UE may adjust its TA during the multiple PRACH transmissions autonomously, which is unknown by gNB. However, both the UE and gNB should be clear the TAC in RAR is based on which of the multiple PRACH transmissions.
[0135] According to 7.1.1 in 38.213 V17.1.0, transmission power of Msg3 is determined by which relies on P L ^ ,c ld and Prampuprequested,b,f,c
Figure imgf000028_0001
[0136] If the UE receives a random access response message in response to a PRACH transmission or a MsgA transmission on active UL BWP b of carrier f of serving cell c as described in clause 8
Figure imgf000028_0002
■ ^msg2, b,f,c is a TPC command value indicated in a random access response grant of the random access response message corresponding to a PRACH transmission according to Type-1 random access procedure, or in a random access response grant of the random access response message corresponding to a MsgA transmission according to Type-2 random access procedure with RAR message(s) for fallbackRAR, on active UL BWP b of carrier f of serving cell c, and
Figure imgf000029_0001
and APrampup requested ,b ,f ,c 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 c
Figure imgf000029_0002
) 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 ATF 6 ^ c(0) is the power adjustment of first PUSCH transmission on active UL BWP b of carrier f of serving cell c.
[0137] Embodiment 1
[0138] After receiving multiple PRACH transmissions from a UE with the same or different beams, in Msg2 gNB signals a single TPC relative to o a reference PRACH transmission, e.g., the PRACH transmitted in the PRACH occasion or transmission occasion with the smallest or the largest PRACH occasion or transmission occasion index, or the first or the last PRACH transmission o the average, the smallest or largest PRACH transmission power of multiple transmissions
The average value is more robust given the reference PRACH transmission may be mis-detected. multiple TPC values in RAR corresponding to multiple PRACH transmissions with multiple UL Tx beams a single TAC relative to o a reference PRACH transmission, e.g., the PRACH transmitted in the PRACH occasion or transmission occasion with the smallest or the largest PRACH occasion or transmission occasion index, or the first or the last PRACH transmission o the average, the smallest or largest timing advance of multiple transmissions multiple TAC values in RAR corresponding to multiple PRACH transmissions with multiple UL Tx beams [0139] If the gNB knows which PRACH transmissions use the same beam, the TPC/TAC value can be beam-specific, so that the UE can determine beam-specific transmission parameters for the following Msg3 transmission with some of these beams.
[0140] Figures 2-4 illustrates operations of embodiment 1 from the perspective of the network node. In the description that follows, network node 1400 of Figure 14 shall be used to describe the operations. For example, modules may be stored in memory 1404 of Figure 14, and these modules may provide instructions so that when the instructions of a module are executed by respective network node processing circuitry 1402, network node 1400 performs respective operations of the flow chart(s).
[0141] Turning to Figure 2, in block 201, the network node 1400 receives multiple physical random access channel, PRACH, transmissions from a user equipment, UE, in Msgl.
[0142] In block 203, the network node 1400, responsive to receiving the multiple PRACH transmissions, signals to the UE one or more of: a single transmit power control, TPC, command 205; multiple TPC values in a random access response, RAR, corresponding to multiple PRACH transmission power of multiple uplink, UE, transmit, Tx, beams 207; a single timing advance command, TAC, 209; and/or multiple TAC values in a RAR corresponding to multiple PRACH transmissions with multiple UL Tx beams 211.
[0143] In block 213, the network node receives a physical uplink shared channel, PUSCH, that is transmitted using at least one of a power level according to the single TPC command or the multiple TPC values or a timing advance according to the single TAC or the multiple TAC values.
[0144] Turning to Figure 3, in some embodiments, in signaling the single TPC, the network node in block 301, signals a single TPC relative to a reference PRACH transmission. Figure 3 illustrates various embodiments of signaling a single TPC relative to a reference PRACH transmission in blocks 303-307.
[0145] In block 303, the network node 1400 signals the single TPC relative to a reference PRACH transmission by signaling a single TPC relative to a PRACH transmitted with a smallest or largest PRACH transmission occasion index.
[0146] In block 305, the network node 1400 signals the single TPC relative to a reference PRACH transmission by signaling a single TPC relative to a PRACH transmitted in a first or a last PRACH transmission.
[0147] In block 307, the network node 1400 signals the single TPC relative to a reference PRACH transmission by signaling a single TPC relative to an average, smallest, or largest PRACH transmission power of multiple transmissions. [0148] Turning to Figure 4, in some embodiments, in signaling the single TAC, the network node in block 401, signals a single TAC relative to a reference PRACH transmission. Figure 4 illustrates various embodiments of signaling a single TPC relative to a reference PRACH transmission in blocks 403-407.
[0149] In block 403, the network node 1400 signals the single TAC relative to a reference PRACH transmission by signaling a single TAC relative to a PRACH transmitted with a smallest or largest PRACH transmission occasion index.
[0150] In block 405, the network node 1400 signals the single TAC relative to a reference PRACH transmission by signaling a single TAC relative to a PRACH transmitted in a first or a last PRACH transmission.
[0151] In block 407, the network node 1400 signals the single TAC relative to a reference PRACH transmission by signaling a single TAC relative to an average, smallest, or largest timing advance of multiple transmissions.
[0152] Figures 6-8 illustrates operations of embodiment 1 from the perspective of the UE. In the description that follows, UE 1300 of Figure 13 shall be used to describe the operations. For example, modules may be stored in memory 1304 of Figure 13, and these modules may provide instructions so that when the instructions of a module are executed by respective network node processing circuitry 1302, UE 1300 performs respective operations of the flow chart(s).
[0153] Turning to Figure 6, in block 601, the UE 1300 transmits multiple physical random access channel, PRACH, transmissions to a network node 1400 with a same beam or different beams in Msgl.
[0154] In block 603, the UE 1300 receives from the network node 1400 one or more of: a single transmit power control, TPC, command 605; multiple TPC values in a random access response, RAR, corresponding to multiple PRACH transmission power of multiple uplink, UL, transmit, Tx, beams 607; a single timing advance command, TAC, 609; and/or multiple TAC values in a RAR corresponding to multiple PRACH transmissions with multiple UL Tx beams 611.
[0155] Turning to Figure 7, in some embodiments, in receiving the single TPC, the UE 1300 in block 701, receives a single TPC relative to a reference PRACH transmission. Figure 7 illustrates various embodiments of receiving a single TPC relative to a reference PRACH transmission in blocks 703-707. [0156] In block 703, the UE 1300 receives the single TPC relative to a reference PRACH transmission by receiving a single TPC relative to a PRACH transmitted with a smallest or largest PRACH transmission occasion index.
[0157] In block 705, the UE 1300 receives the single TPC relative to a reference PRACH transmission by receiving a single TPC relative to a PRACH transmitted in a first or a last PRACH transmission.
[0158] In block 707, the UE 1300 receives the single TPC relative to a reference PRACH transmission by receiving a single TPC relative to an average, smallest, or largest PRACH transmission power of multiple transmissions.
[0159] In NR releases up through Rel-17, the UE 1300 ramps up power for a subsequent transmission when the UE 1300 does not receive Msg2 or MsgB intended for the UE 1300 in a RAR window corresponding to a prior transmission according to the excerpt below from 3GPP TS 38.321 rev 17.1.0, section 5.1.3.
1> set PREAMBLE_RECEIVED_TARGET_POWER to preambleReceivedTargetPower + DELT A_PRE AMBLE + (PREAMBLE_POWER_RAMPING_COUNTER - 1) x PREAMBLE_POWER_RAMPING_STEP;
[0160] Consequently, a UE 1300 only ramps up its transmit power by a single step between RAR windows. However, when the PRACH is repeated, the PRACH may be repeated within a RAR window. When the UE 1300 is transmitting less than its full power at the beginning of a RAR window, it may be beneficial for the UE 1300 to ramp up its power for PRACHs in the RAR window, rather than only ramping up once during a RAR window. This will allow higher transmission power to be received by the gNB. An alternative could be to set the PRACH power control parameters such that UEs in a cell transmit at maximum power, and therefore does not ramp up power, but this may create unnecessary interference. If UEs ramp during PRACH repetitions within a RAR window, the network can send Msg2 or MsgB when the PRACH is ramped high enough to be successfully received. This would generally avoid the highest power transmissions that typically produce the most interference. While repetition can substantially improve the likelihood that the network will receive PRACH transmission from a UE 1300, the repeated PRACH transmissions within a single RAR window may be insufficient. Therefore, it can be beneficial for a UE 1300 to increment its power ramping counter for each of a plurality of PRACH transmissions contained within a RAR window, and to accumulate the power ramping counter across RAR windows. In this way, multiple RAR windows can be used to increase the PRACH power on top of the increases from repetitions within each window. [0161] Turning to Figure 8, in some embodiments where a TPC command is relative to a last PRACH transmission, a UE 1300 transmits a plurality of PRACHs within a first RAR window and within a second RAR window. In block 801, for a plurality of PRACH transmissions within each of a first RAR window and a second RAR window occurring at a later time than the first RAR window, the UE 1300 increments a preamble power ramping counter for the plurality of PRACH transmissions within each of the first RAR window and the second RAR window, wherein a value of the preamble power ramping counter for a first PRACH transmission in the second RAR window is one greater than a last value of the preamble power ramping counter for a last PRACH transmission in the first RAR window.
[0162] In block 803, the UE 1300 multiplies the preamble power ramping counter by a power ramping step value and adds a result of the multiplying to a value indicated by the TPC command to determine at least a portion of a power to transmit a PUSCH.
[0163] Turning to Figure 9, in some embodiments, in receiving the single TAC, the UE 1300 in block 901, receives a single TAC relative to a reference PRACH transmission. Figure 8 illustrates various embodiments of signaling a single TPC relative to a reference PRACH transmission in blocks 803-807.
[0164] In block 903, the UE 1300 receives the single TAC relative to a reference PRACH transmission by receiving a single TAC relative to a PRACH transmitted with a smallest or largest PRACH transmission occasion index.
[0165] In block 905, the UE 1300 receives the single TAC relative to a reference PRACH transmission by receiving a single TAC relative to a PRACH transmitted in a first or a last PRACH transmission.
[0166] In block 907, the UE 1300 receives the single TAC relative to a reference PRACH transmission by receiving a single TAC relative to an average, smallest, or largest timing advance of multiple transmissions.
[0167] Embodiment 2
[0168] In the second embodiment, APrampuprequested ,b ,f ,c corresponds to the total power ramp-up requested by higher layers from the first to the last random access preamble transmitted with the same beam.
[0169] Figure 5 illustrates operations the network node 1400 performs in some embodiments of Embodiment 2. Turning to Figure 5, in block 501, the network node 1400 signals to the UE 1300 an indication that APrampuprequested,b ,f ,c corresponds to a total power ramp-up requested by higher layers from a first to a last random access preamble transmitted with a same beam. [0170] Figure 10 illustrates operations the UE 1300 performs in some embodiments of Embodiment 2. Turning to Figure 10, in block 1001, the UE 1300 receives from the network node 1400 an indication that APrampuprequested ,b ,f ,c corresponds to a total power ramp-up requested by higher layers from a first to a last random access preamble transmitted with a same beam.
[0171] Embodiment 3
[0172] If the multiple PRACH transmissions with different UL Tx beams are associated with different SSBs, and gNB indicates one SSB in Msg2, a UE estimates pathloss of the indicated SSB beam to determine Msg3 transmission power. TPC and TAC command are applied to the PRACH transmission associated with the indicated SSB beam.
[0173] Figure 11 illustrates operations the UE 1300 performs in some embodiments of Embodiment 3. Turning to Figure 11, in bock 1101, the UE 1300, responsive to multiple PRACH transmissions with different uplink Tx beams are associated with different synchronization signal blocks, SSBs, and the network indicates one SSB in Msg2 estimates a pathloss of the indicated SSB beam to determine Msg3 transmission power. In block 1103, the UE 1300 applies a TPC and/or a TAC command to a PRACH transmission associated with the indicated SSB beam.
[0174] Figure 12 shows an example of a communication system 1200 in accordance with some embodiments.
[0175] In the example, the communication system 1200 includes a telecommunication network 1202 that includes an access network 1204, such as a radio access network (RAN), and a core network 1206, which includes one or more core network nodes 1208. The access network 1204 includes one or more access network nodes, such as network nodes 1210A and 1210B (one or more of which may be generally referred to as network nodes 1210), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 1210 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 1212A, 1212B, 1212C, and 1212D (one or more of which may be generally referred to as UEs 1212) to the core network 1206 over one or more wireless connections.
[0176] 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. Moreover, in different embodiments, the communication system 1200 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 1200 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
[0177] The UEs 1212 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 1210 and other communication devices. Similarly, the network nodes 1210 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 1212 and/or with other network nodes or equipment in the telecommunication network 1202 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 1202.
[0178] In the depicted example, the core network 1206 connects the network nodes 1210 to one or more hosts, such as host 1216. 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 1206 includes one more core network nodes (e.g., core network node 1208) 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 1208. 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 (SIDE), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).
[0179] The host 1216 may be under the ownership or control of a service provider other than an operator or provider of the access network 1204 and/or the telecommunication network 1202 and may be operated by the service provider or on behalf of the service provider. The host 1216 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. [0180] As a whole, the communication system 1200 of Figure 12 enables connectivity between the UEs, network nodes, and hosts. In that sense, 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 (Light Fidelity), and/or any low-power wide-area network (LPWAN) standards such as LoRa (Long Range) and Sigfox.
[0181] In some examples, the telecommunication network 1202 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 1202 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1202. For example, the telecommunications network 1202 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)/Massive loT (Internet of Things) services to yet further UEs.
[0182] In some examples, the UEs 1212 are configured to transmit and/or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 1204 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1204. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, 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).
[0183] In the example, the hub 1214 communicates with the access network 1204 to facilitate indirect communication between one or more UEs (e.g., UE 1212C and/or 1212D) and network nodes (e.g., network node 1210B). In some examples, the hub 1214 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 1214 may be a broadband router enabling access to the core network 1206 for the UEs. As another example, the hub 1214 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 1210, or by executable code, script, process, or other instructions in the hub 1214. As another example, the hub 1214 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. As another example, the hub 1214 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1214 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1214 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub 1214 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.
[0184] The hub 1214 may have a constant/persistent or intermittent connection to the network node 1210B. The hub 1214 may also allow for a different communication scheme and/or schedule between the hub 1214 and UEs (e.g., UE 1212C and/or 1212D), and between the hub 1214 and the core network 1206. In other examples, the hub 1214 is connected to the core network 1206 and/or one or more UEs via a wired connection. Moreover, the hub 1214 may be configured to connect to an M2M service provider over the access network 1204 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 1210 while still connected via the hub 1214 via a wired or wireless connection. In some embodiments, the hub 1214 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 1210B. In other embodiments, the hub 1214 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 1210B, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
[0185] Figure 13 shows a UE 1300 in accordance with some embodiments. As used herein, 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. Other examples include any UE 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.
[0186] 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). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, 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).
Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).
[0187] The UE 1300 includes processing circuitry 1302 that is operatively coupled via a bus 1304 to an input/output interface 1306, a power source 1308, a memory 1310, a communication interface 1312, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 13. 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.
[0188] The processing circuitry 1302 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 1310. The processing circuitry 1302 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. For example, the processing circuitry 1302 may include multiple central processing units (CPUs).
[0189] In the example, the input/output interface 1306 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 1300. 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.
[0190] In some embodiments, the power source 1308 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 1308 may further include power circuitry for delivering power from the power source 1308 itself, and/or an external power source, to the various parts of the UE 1300 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 1308. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1308 to make the power suitable for the respective components of the UE 1300 to which power is supplied.
[0191] The memory 1310 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 readonly memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 1310 includes one or more application programs 1314, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1316. The memory 1310 may store, for use by the UE 1300, any of a variety of various operating systems or combinations of operating systems. [0192] The memory 1310 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. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 1310 may allow the UE 1300 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 1310, which may be or comprise a device-readable storage medium.
[0193] The processing circuitry 1302 may be configured to communicate with an access network or other network using the communication interface 1312. The communication interface 1312 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1322. The communication interface 1312 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 1318 and/or a receiver 1320 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 1318 and receiver 1320 may be coupled to one or more antennas (e.g., antenna 1322) and may share circuit components, software or firmware, or alternatively be implemented separately.
[0194] In the illustrated embodiment, communication functions of the communication interface 1312 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. 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. [0195] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 1312, 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).
[0196] As another example, 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. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, 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.
[0197] 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. Non-limiting examples of such an 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- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and/or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 1300 shown in Figure 13. [0198] As yet another specific example, in an loT scenario, 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. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, 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.
[0199] In practice, any number of UEs may be used together with respect to a single use case. For example, 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. When the user makes changes from the remote controller, 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. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.
[0200] Figure 14 shows a network node 1400 in accordance with some embodiments. As used herein, 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. Examples of 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)).
[0201] 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. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
[0202] Other examples of 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).
[0203] The network node 1400 includes a processing circuitry 1402, a memory 1404, a communication interface 1406, and a power source 1408. The network node 1400 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. In certain scenarios in which the network node 1400 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 1400 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 1404 for different RATs) and some components may be reused (e.g., a same antenna 1410 may be shared by different RATs). The network node 1400 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1400, 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 1400.
[0204] The processing circuitry 1402 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 1400 components, such as the memory 1404, to provide network node 1400 functionality.
[0205] In some embodiments, the processing circuitry 1402 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1402 includes one or more of radio frequency (RF) transceiver circuitry 1412 and baseband processing circuitry 1414. In some embodiments, the radio frequency (RF) transceiver circuitry 1412 and the baseband processing circuitry 1414 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 1412 and baseband processing circuitry 1414 may be on the same chip or set of chips, boards, or units. [0206] The memory 1404 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 1402. The memory 1404 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 1402 and utilized by the network node 1400. The memory 1404 may be used to store any calculations made by the processing circuitry 1402 and/or any data received via the communication interface 1406. In some embodiments, the processing circuitry 1402 and memory 1404 is integrated. [0207] The communication interface 1406 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface 1406 comprises port(s)/terminal(s) 1416 to send and receive data, for example to and from a network over a wired connection. The communication interface 1406 also includes radio front-end circuitry 1418 that may be coupled to, or in certain embodiments a part of, the antenna 1410. Radio front-end circuitry 1418 comprises filters 1420 and amplifiers 1422. The radio front-end circuitry 1418 may be connected to an antenna 1410 and processing circuitry 1402. The radio front-end circuitry may be configured to condition signals communicated between antenna 1410 and processing circuitry 1402. The radio front-end circuitry 1418 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 1418 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1420 and/or amplifiers 1422. The radio signal may then be transmitted via the antenna 1410. Similarly, when receiving data, the antenna 1410 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1418. The digital data may be passed to the processing circuitry 1402. In other embodiments, the communication interface may comprise different components and/or different combinations of components.
[0208] In certain alternative embodiments, the network node 1400 does not include separate radio front-end circuitry 1418, instead, the processing circuitry 1402 includes radio front-end circuitry and is connected to the antenna 1410. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1412 is part of the communication interface 1406. In still other embodiments, the communication interface 1406 includes one or more ports or terminals 1416, the radio front-end circuitry 1418, and the RF transceiver circuitry 1412, as part of a radio unit (not shown), and the communication interface 1406 communicates with the baseband processing circuitry 1414, which is part of a digital unit (not shown).
[0209] The antenna 1410 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. The antenna 1410 may be coupled to the radio front-end circuitry 1418 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In certain embodiments, the antenna 1410 is separate from the network node 1400 and connectable to the network node 1400 through an interface or port. [0210] The antenna 1410, communication interface 1406, and/or the processing circuitry 1402 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 1410, the communication interface 1406, and/or the processing circuitry 1402 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.
[0211] The power source 1408 provides power to the various components of network node 1400 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1408 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1400 with power for performing the functionality described herein. For example, the network node 1400 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 1408. As a further example, the power source 1408 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.
[0212] Embodiments of the network node 1400 may include additional components beyond those shown in Figure 14 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. For example, the network node 1400 may include user interface equipment to allow input of information into the network node 1400 and to allow output of information from the network node 1400. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1400.
[0213] Figure 15 is a block diagram of a host 1500, which may be an embodiment of the host 1216 of Figure 12, in accordance with various aspects described herein. As used herein, the host 1500 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 1500 may provide one or more services to one or more UEs.
[0214] The host 1500 includes processing circuitry 1502 that is operatively coupled via a bus 1504 to an input/output interface 1506, a network interface 1508, a power source 1510, and a memory 1512. 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 Figures 13 and 14, such that the descriptions thereof are generally applicable to the corresponding components of host 1500.
[0215] The memory 1512 may include one or more computer programs including one or more host application programs 1514 and data 1516, which may include user data, e.g., data generated by a UE for the host 1500 or data generated by the host 1500 for a UE. Embodiments of the host 1500 may utilize only a subset or all of the components shown. The host application programs 1514 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 1514 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. Accordingly, the host 1500 may select and/or indicate a different host for over-the-top services for a UE. The host application programs 1514 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.
[0216] Figure 16 is a block diagram illustrating a virtualization environment 1600 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, 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 1600 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. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized.
[0217] Applications 1602 (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.
[0218] Hardware 1604 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 1606 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1608 A and 1608B (one or more of which may be generally referred to as VMs 1608), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. The virtualization layer 1606 may present a virtual operating platform that appears like networking hardware to the VMs 1608.
[0219] The VMs 1608 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1606. Different embodiments of the instance of a virtual appliance 1602 may be implemented on one or more of VMs 1608, 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.
[0220] In the context of NFV, a VM 1608 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 1608, and that part of hardware 1604 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. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 1608 on top of the hardware 1604 and corresponds to the application 1602.
[0221] Hardware 1604 may be implemented in a standalone network node with generic or specific components. Hardware 1604 may implement some functions via virtualization.
Alternatively, hardware 1604 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 1610, which, among others, oversees lifecycle management of applications 1602. In some embodiments, hardware 1604 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. In some embodiments, some signaling can be provided with the use of a control system 1612 which may alternatively be used for communication between hardware nodes and radio units.
[0222] Figure 17 shows a communication diagram of a host 1702 communicating via a network node 1704 with a UE 1706 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 1212A of Figure 12 and/or UE 1300 of Figure 13), network node (such as network node 1210A of Figure 12 and/or network node 1400 of Figure 14), and host (such as host 1216 of Figure 12 and/or host 1500 of Figure 15) discussed in the preceding paragraphs will now be described with reference to Figure 17.
[0223] Like host 1500, embodiments of host 1702 include hardware, such as a communication interface, processing circuitry, and memory. The host 1702 also includes software, which is stored in or accessible by the host 1702 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 1706 connecting via an over-the-top (OTT) connection 1750 extending between the UE 1706 and host 1702. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 1750. [0224] The network node 1704 includes hardware enabling it to communicate with the host 1702 and UE 1706. The connection 1760 may be direct or pass through a core network (like core network 1206 of Figure 12) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.
[0225] The UE 1706 includes hardware and software, which is stored in or accessible by UE 1706 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 1706 with the support of the host 1702. In the host 1702, an executing host application may communicate with the executing client application via the OTT connection 1750 terminating at the UE 1706 and host 1702. In providing the service to the user, 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 1750 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 1750. [0226] The OTT connection 1750 may extend via a connection 1760 between the host 1702 and the network node 1704 and via a wireless connection 1770 between the network node 1704 and the UE 1706 to provide the connection between the host 1702 and the UE 1706. The connection 1760 and wireless connection 1770, over which the OTT connection 1750 may be provided, have been drawn abstractly to illustrate the communication between the host 1702 and the UE 1706 via the network node 1704, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
[0227] As an example of transmitting data via the OTT connection 1750, in step 1708, the host 1702 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 1706. In other embodiments, the user data is associated with a UE 1706 that shares data with the host 1702 without explicit human interaction. In step 1710, the host 1702 initiates a transmission carrying the user data towards the UE 1706. The host 1702 may initiate the transmission responsive to a request transmitted by the UE 1706. The request may be caused by human interaction with the UE 1706 or by operation of the client application executing on the UE 1706. The transmission may pass via the network node 1704, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1712, the network node 1704 transmits to the UE 1706 the user data that was carried in the transmission that the host 1702 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1714, the UE 1706 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1706 associated with the host application executed by the host 1702.
[0228] In some examples, the UE 1706 executes a client application which provides user data to the host 1702. The user data may be provided in reaction or response to the data received from the host 1702. Accordingly, in step 1716, the UE 1706 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input/output interface of the UE 1706. Regardless of the specific manner in which the user data was provided, the UE 1706 initiates, in step 1718, transmission of the user data towards the host 1702 via the network node 1704. In step 1720, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 1704 receives user data from the UE 1706 and initiates transmission of the received user data towards the host 1702. In step 1722, the host 1702 receives the user data carried in the transmission initiated by the UE 1706. [0229] One or more of the various embodiments improve the performance of OTT services provided to the UE 1706 using the OTT connection 1750, in which the wireless connection 1770 forms the last segment..
[0230] In an example scenario, factory status information may be collected and analyzed by the host 1702. As another example, the host 1702 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 1702 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 1702 may store surveillance video uploaded by a UE. As another example, the host 1702 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host 1702 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.
[0231] In some examples, 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. There may further be an optional network functionality for reconfiguring the OTT connection 1750 between the host 1702 and UE 1706, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 1702 and/or UE 1706. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1750 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 1750 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 1704. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 1702. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1750 while monitoring propagation times, errors, etc.
[0232] Although the computing devices described herein (e.g., UEs, network nodes, hosts) 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. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, 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. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.
[0233] In certain embodiments, some or all of the functionality described herein may be provided by 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. In alternative embodiments, 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. In any of those particular embodiments, whether executing instructions stored on a non- transitory computerreadable storage medium or not, 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.
[0234] Explanations are provided below for various abbreviations/acronyms used in the present disclosure.
Abbreviation Explanation
BWP Bandwidth Part
CBRA Contention Based Random Access
CE Coverage Extension CFRA Contention Free Random Access
CP Cyclic Prefix
CSI Channel State Information
DL Downlink
DMRS Demodulation Reference Signal
FDM Frequency-Division Multiplexing
FFT Fast Fourier Transform
LTE Long-Term Evolution
MAC Medium Access Control
NB-IoT Narrowband loT
NUL Normal Uplink
PDSCH Physical Downlink Shared Channel
PBCH Physical Broadcast Channel
PRACH physical random access channel
PUSCH Physical Uplink Shared Channel
QCL Quasi-Colocated
RAR Random Access Response
RSRP Reference Signal Received Power
RO PRACH occasion or PRACH transmission occasion
RAPID random access preamble identity
RNTI Radio Network Temporary Identifier
SI System Information
SIB System Information Block
SSB Synchronization Signal Beam
SUL Supplementary Uplink
TA Timing Advance
TAC Timing Advance Command
TDM Time-Division Multiplexing
TPC Transmit power control
[0235] References are identified below
[1] 3rd Generation Partnership Project (3GPP) Technical Standard (TS) 36.321 v.17.0.0. (2022-03); 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification (Release 17) [2] 3GPP TS 36.211 v 17.1.0 (2022-03); 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E- UTRA); Physical channels and modulation (Release 17)
[3] 3GPP TS 38.211 V17.1.0 (2022-03)3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical channels and modulation (Release 17)
[4] 3GPP TS 38.213 V17.1.0 (2022-03) 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for control (Release 17)
[5] 3GPP TS 38.321 v.17.0.0 (2022-03) 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Medium Access Control (MAC) protocol specification (Release 17)
[6] 3GPP TS 38.331 v.17.0.0 (2022-03) 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC); Protocol specification (Release 17) [7] 3GPP TS 38.300 NR; NR and NG-RAN Overall description; Stage-2 (Release 17)

Claims

1. A method performed by a network node (1210A, 1210B, 1400, 1602, 1704) comprising: receiving (201) multiple physical random access channel, PRACH, transmissions from a user equipment, UE, (1212A, 1212B, 1212C, 1212D, 1300, 1608A, 1608B, 1706) in Msgl; responsive to receiving the multiple PRACH transmissions, signaling (203) to the UE (1212A, 1212B, 1212C, 1212D, 1300, 1608A, 1608B, 1706) one or more of: a single transmit power control, TPC, command (205); multiple TPC values in a random access response, RAR, corresponding to multiple PRACH transmission power of multiple uplink, UL, transmit, Tx, beams (207); a single timing advance command, TAC, (209); and/or multiple TAC values in a RAR corresponding to multiple PRACH transmissions with multiple UL Tx beams (211); and receiving (213) a physical uplink shared channel, PUSCH, that is transmitted using at least one of a power level according to the single TPC command or the multiple TPC values or a timing advance according to the single TAC or the multiple TAC values.
2. The method of Claim 1, wherein signaling the single TPC comprises signaling (301) a single TPC relative to a reference PRACH transmission.
3. The method of Claim 2, wherein signaling the single TPC relative to a reference PRACH transmission comprises signaling (303) a single TPC relative to a PRACH transmitted with a smallest or largest PRACH transmission occasion index.
4. The method of Claim 2, wherein signaling the single TPC relative to a reference PRACH transmission comprises signaling (305) a single TPC relative to a PRACH transmitted in a first or a last PRACH transmission.
5. The method of Claim 2, wherein signaling the single TPC relative to a reference PRACH transmission comprises signaling (307) a single TPC relative to an average, smallest, or largest PRACH transmission power of multiple transmissions.
6. The method of any of Claims 1-2, wherein signaling the single TAC comprises signaling (401) a single TAC relative to a reference PRACH transmission.
7. The method of Claim 6, wherein signaling the single TAC relative to a reference PRACH transmission comprises signaling (403) a single TAC relative to a PRACH transmitted with a smallest or largest PRACH transmission occasion index.
8. The method of Claim 6, wherein signaling the single TAC relative to a reference PRACH transmission comprises signaling (405) a single TAC relative to a PRACH transmitted in a first or a last PRACH transmission.
9. The method of Claim 6, wherein signaling the single TAC relative to a reference PRACH transmission comprises signaling (407) a single TAC relative to an average, smallest, or largest timing advance of multiple transmissions.
10. The method of any of Claims 1-9, further comprising signaling (501) to the UE (1212A, 1212B, 1212C, 1212D, 1300, 1608A, 1608B, 1706) an indication that Prampuprequested ,b ,c corresponds to a total power ramp-up requested by higher layers from a first to a last random access preamble transmitted with a same beam.
11. A method performed by a user equipment, UE, (1212A, 1212B, 1212C, 1212D, 1300, 1608A, 1608B, 1706) comprising: transmitting (601) multiple physical random access channel, PRACH, transmissions to a network node (120A, 1210B, 1400, 1602, 1704) with a same beam or different beams, in Msgl and receiving (603) from the network node (120A, 1210B, 1400, 1602, 1704) one or more of: a single transmit power control, TPC, command (605); multiple TPC values in a random access response, RAR, corresponding to multiple PRACH transmission power of multiple uplink, UL, transmit, Tx, beams (607); and a single timing advance command, TAC (609); multiple TAC values in a RAR corresponding to multiple PRACH transmissions with multiple UL Tx beams (611); and transmitting (613) a physical uplink shared channel, PUSCH, using at least one of a power level according to the TPC command or the TPC values or a timing advance according to the TAC or the TAC values.
12. The method of Claim 11, wherein receiving the single TPC command comprises receiving (701) a single TPC command relative to a reference PRACH transmission.
13. The method of Claim 12, wherein receiving the single TPC command relative to a reference PRACH transmission comprises receiving (703) a single TPC command relative to a PRACH transmitted with a smallest or largest PRACH transmission occasion index.
14. The method of Claim 12, wherein receiving the single TPC command relative to a reference PRACH transmission comprises receiving (705) a single TPC command relative to a PRACH transmitted in a first or a last PRACH transmission.
15. The method of Claim 12, wherein receiving the single TPC command relative to a reference PRACH transmission comprises receiving (707) a single TPC command relative to an average, smallest, or largest PRACH transmission power of multiple transmissions.
16. The method of any of Claims 12-15, further comprising: for a plurality of PRACH transmissions within each of a first RAR window and a second RAR window occurring at a later time than the first RAR window, incrementing (801) a preamble power ramping counter for the plurality of PRACH transmissions within each of the first RAR window and the second RAR window, wherein a value of the preamble power ramping counter for a first PRACH transmission in the second RAR window is at least one greater than a last value of the preamble power ramping counter for a last PRACH transmission in the first RAR window; and multiplying (803) the preamble power ramping counter by a power ramping step value and adding a result of the multiplying to a value indicated by the TPC command to determine at least a portion of the power to transmit the PUSCH.
17. The method of any of Claims 11-12, wherein receiving the single TAC comprises receiving (901) a single TAC relative to a reference PRACH transmission.
18. The method of Claim 17, wherein receiving the single TAC relative to a reference PRACH transmission comprises receiving (903) a single TAC relative to a PRACH transmitted with a smallest or largest PRACH transmission occasion or transmission occasion index.
19. The method of Claim 17, wherein receiving the single TAC relative to a reference PRACH transmission comprises receiving (905) a single TAC relative to a PRACH transmitted in a first or a last PRACH transmission.
20. The method of Claim 17, wherein receiving the single TAC relative to a reference PRACH transmission comprises receiving (907) a single TAC relative to an average, smallest, or largest timing advance of multiple transmissions.
21. The method of any of Claims 11-20, further comprising receiving (1001) from the network node (120A, 1210B, 1400, 1602, 1704) an indication that APrampuprequested,b,f,c corresponds to a total power ramp-up requested by higher layers from a first to a last random access preamble transmitted with a same beam.
22. The method of any of Claims 11-20, further comprising: responsive to multiple PRACH transmissions with different uplink Tx beams are associated with different synchronization signal blocks, SSBs, and the network node (120A, 1210B, 1400, 1602, 1704) indicates one SSB in Msg2: estimating (1101) a pathloss of the indicated SSB beam to determine Msg3 transmission power; and applying (1103) a TPC command and/or a TAC to a PRACH transmission associated with the indicated SSB beam.
23. A network node (1210A, 1210B, 1400, 1602, 1704) adapted to perform according to any of Claims 1-10.
24. A network node (1210A, 1210B, 1400, 1602, 1704) comprising: processing circuitry (1402); and memory (1404) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the UE to perform operations according to any of Claims 1-10.
25. A computer program comprising program code to be executed by processing circuitry (1402) of a network node (1210A, 1210B, 1400, 1602, 1704), whereby execution of the program code causes the network node (1210A, 1210B, 1400, 1602, 1704) to perform according to any of Claims 1-10.
26. A computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry (1402) of a network node (1210A, 1210B, 1400, 1602, 1704), whereby execution of the program code causes the network node (1210A, 1210B, 1400, 1602, 1704) to perform according to any of Claims 1-10.
27. A user equipment, UE, (1212A, 1212B, 1212C, 1212D, 1300, 1608A, 1608B, 1706) adapted to perform according to any of Claims 11-22.
28. A user equipment, UE, (1212A, 1212B, 1212C, 1212D, 1300, 1608A, 1608B, 1706) comprising: processing circuitry (1302); and memory (1310) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the UE to perform operations according to any of Claims 11-22.
29. A computer program comprising program code to be executed by processing circuitry (1302) of a user equipment, UE, (1212A, 1212B, 1212C, 1212D, 1300, 1608A, 1608B, 1706), whereby execution of the program code causes the UE (1212A, 1212B, 1212C, 1212D, 1300, 1608A, 1608B, 1706) to perform according to any of Claims 11-22.
30. A computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry (1302) of a user equipment, UE (1212A, 1212B, 1212C, 1212D, 1300, 1608A, 1608B, 1706), whereby execution of the program code causes the UE (1212A, 1212B, 1212C, 1212D, 1300, 1608A, 1608B, 1706) to perform according to any of Claims 11-22.
PCT/IB2023/056858 2022-07-04 2023-06-30 User equipment interpretation of transmit power control (tpc) and timing advance command (tac) in random access response (rar) for multiple physical random access channel (prach) transmissions WO2024009196A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CNPCT/CN2022/103625 2022-07-04
CN2022103625 2022-07-04

Publications (1)

Publication Number Publication Date
WO2024009196A1 true WO2024009196A1 (en) 2024-01-11

Family

ID=87158091

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2023/056858 WO2024009196A1 (en) 2022-07-04 2023-06-30 User equipment interpretation of transmit power control (tpc) and timing advance command (tac) in random access response (rar) for multiple physical random access channel (prach) transmissions

Country Status (1)

Country Link
WO (1) WO2024009196A1 (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2779759A1 (en) * 2011-11-08 2014-09-17 LG Electronics Inc. Method and device for setting uplink transmission power in wireless communication system
US20180324716A1 (en) * 2017-05-04 2018-11-08 Ofinno Technologies, Llc RACH Power Adjustment
US20200008188A1 (en) * 2018-07-02 2020-01-02 Qualcomm Incorporated Contention-free concurrent physical random access channel transmissions
US20210176780A1 (en) * 2018-07-04 2021-06-10 Lg Electronics Inc. Method for performing uplink transmission in wireless communication system, and apparatus therefor

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2779759A1 (en) * 2011-11-08 2014-09-17 LG Electronics Inc. Method and device for setting uplink transmission power in wireless communication system
US20180324716A1 (en) * 2017-05-04 2018-11-08 Ofinno Technologies, Llc RACH Power Adjustment
US20200008188A1 (en) * 2018-07-02 2020-01-02 Qualcomm Incorporated Contention-free concurrent physical random access channel transmissions
US20210176780A1 (en) * 2018-07-04 2021-06-10 Lg Electronics Inc. Method for performing uplink transmission in wireless communication system, and apparatus therefor

Similar Documents

Publication Publication Date Title
US11272534B2 (en) Contention-free random access with multiple SSB
US20220007391A1 (en) Support for Transmission in Preconfigured UL Resources
KR102435369B1 (en) System and method for prioritizing channel state information reports
US20220132578A1 (en) RACH Report with Beam Selection Information
WO2019096679A1 (en) Random access procedure
US20220408478A1 (en) Determination of PRACH Occasions and PUSCH Occasions for 2-Step Random Access
KR20210066916A (en) Implicit sounding reference signal aperiodic trigger offset
US20220078853A1 (en) Random Access in a Wireless Communication System
EP3925369B1 (en) Two-step random access procedure
US11304237B2 (en) Random access with different TTI durations
US20220346157A1 (en) Configuration for Random Access Procedure
US20230354432A1 (en) Random Access for Low-Complexity User Equipment
US20220394776A1 (en) Wireless device, a network node, and methods therein for determining an identity of a wireless device during a random access procedure
WO2021246926A1 (en) Methods, apparatuses and computer programs to fetch random access channel reports in dual connectivity
WO2023209695A1 (en) Determining channels and signals for applying a time advance
WO2023037004A1 (en) Sidelink transmissions in unlicensed spectrum
WO2020192440A1 (en) Method, apparatus for monitoring pdcch in random access procedure
WO2024009196A1 (en) User equipment interpretation of transmit power control (tpc) and timing advance command (tac) in random access response (rar) for multiple physical random access channel (prach) transmissions
WO2024009198A1 (en) Beam determination for uplink transmissions following multiple physical random access channel transmissions with different beams
WO2024009199A1 (en) Determination of random access channel resource and transmission power for multiple physical random access channel transmissions
WO2024045176A1 (en) Coverage enhancement (ce) random access (ra) signaling and configuring
WO2024045173A1 (en) Improved contention free random access (cfra) fallback
WO2022167918A1 (en) Two-step rach adapation for reduced capability devices
WO2024072308A1 (en) Time alignment for inter-cell mobility
WO2023062610A1 (en) Multi-slot physical layer downlink control channel (pdcch) monitoring

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

Country of ref document: EP

Kind code of ref document: A1