Determination of random access channel resources and transmit power for multiple physical random access channel transmissions

Abstract

During a random access ("RA") procedure associated with a network node of a new radio ("NR") communication network, a communication device may determine information associated with at least one of the communication device and a channel between the communication device and the network node. The communication device may also determine, based on the information, a number of physical RA channel ("PRACH") transmissions to be sent to the network node as part of the RA procedure prior to receiving the random access response. The communication device may also send the number of PRACH transmissions to the network node as part of the RA procedure.

Description

Technical Field

[0001] The present disclosure relates to wireless communication systems, and more particularly to determination of random access channel ("RACH") resources and transmit power for multiple physical random access channel ("PRACH") transmissions. Background Art

[0002] Figure 1 An example of a new radio (“NR”) network (e.g., a fifth generation (“5G”) network) is illustrated, which includes a 5G core (“5GC”) network 130, network nodes 120a-120b (e.g., 5G base stations (“gNBs”)), and multiple communication devices 110 (also referred to as user equipment (“UE”)).

[0003] Random Access Channel ("RACH") repetition was introduced in the Rel-13 work items ("Wi") of "Further LTE Physical Layer Enhancements for MTC" and "Narrowband IOT (NB-IOT)" to extend coverage in Long Term Evolution ("LTE"), although RACH repetition is currently not supported in NR releases up to Rel-17.

[0004] Repetition of information is a technique for achieving coverage enhancement. It can be used for all physical channels available to coverage enhancement UEs in LTE, such as the Machine Type Communication Physical Downlink Control Channel ("M-PDCCH"), Physical Broadcast Channel ("PBCH"), Physical Downlink Shared Channel ("PDSCH"), Physical Uplink Control Channel ("PUCCH"), Physical Uplink Shared Channel ("PUSCH"), and Physical Random Access Channel ("PRACH").

[0005] The UE may decide the repetition level for the initial PRACH transmission.The repetition levels supported by the cell (eg, 5, 10, and 15 dB) may be included in the system information, and the UE may select one of these repetition levels based on, for example, the estimated channel quality.

[0006] During the initial random access, the UE may measure the downlink ("DL") quality. The UE may select a suitable repetition level for its initial PRACH preamble transmission among 4 levels. If the UE does not receive a random access response ("RAR"), it may increase its PRACH repetition level. The number of repetitions used for the RAR and subsequent messages may depend on the level used for a successful PRACH.

[0007] Coverage enhancement for physical random access PRACH preambles can be achieved in part by relaxing the required PRACH misdetection probability and in part by repetition of the traditional LTE PRACH format. Up to three different repetition levels (plus a zero coverage enhancement level) can be configured, each with its own configurable number of repetitions and attempts to adapt to the coverage situation of the UE. For initial random access, the UE selects its repetition level based on RSRP measurements. If the UE does not receive a RAR after the maximum number of attempts at its current level, it moves to the next higher level. Power ramping is not used for large repetition levels; otherwise the current process is used. Different coverage levels correspond to different PRACH resources (e.g., different combinations of preamble sequences, timing, and narrowband), and the available resources are signaled in the system information block ("SIB").

[0008] RAR messages in LTE can be scheduled with M-PDCCH and associated PDSCH. The UE can know the repetition level, possible starting subframe and frequency resource of the M-PDCCH from its most recent PRACH transmission (combined with the information signaled in the SIB).

[0009] In order to enable different operation modes depending on the coverage extension requirements of the UE, two coverage enhancement modes have been introduced for RRC_CONNECTED LTE UEs: Coverage Extension ("CE") Mode A and CE Mode B. CE Mode A is used for no or small coverage enhancement, requiring a few (e.g., up to tens of) repetitions. CE Mode B is used for medium to large coverage enhancement, requiring several (e.g., hundreds of) repetitions. The CE mode may be signaled to the UE by the network. Summary of the invention

[0010] In accordance with some embodiments, a method of operating a communication device during a random access ("RA") procedure associated with a network node of a new radio ("NR") communication network is provided. The method includes determining information associated with at least one of the communication device and a channel between the communication device and the network node. The method also includes determining, based on the information, a number of physical RA channel ("PRACH") transmissions to send to the network node before receiving a random access response as part of the RA procedure. The method also includes sending the number of PRACH transmissions to the network node as part of the RA procedure.

[0011] According to other embodiments, a method of operating a network node of a new radio ("NR") communication network during a random access ("RA") procedure associated with a communication device is provided. The method includes determining information associated with at least one of the communication device and a channel between the communication device and the network node. The method also includes determining, based on the information, a number of physical RA channel ("PRACH") transmissions to be received from the communication device as part of the RA procedure. The method also includes monitoring the NR communication network for the number of PRACH transmissions from the communication device as part of the RA procedure.

[0012] According to other embodiments, a communication device, a network node, a non-transitory readable medium, a computer program or a computer program product is provided to perform one of the above methods.

[0013] Certain embodiments may provide one or more of the following technical advantages: In some examples, determining RACH resources and transmit power for multiple PRACH transmissions may reduce the time it takes a UE to connect to a communication network and improve the resulting connection. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The accompanying drawings, which are included to provide a further understanding of the present disclosure and are incorporated in and constitute a part of this application, illustrate certain non-limiting embodiments of the inventive concept, in which:

[0015] Figure 1 is a schematic diagram illustrating an example of a fifth generation ("5G") network;

[0016] Figure 2 is a table illustrating an example of a frame structure type 2 random access configuration for preamble formats 0-4;

[0017] Figure 3 is a table illustrating an example of mapping of a frame structure type 2 random access preamble code on time and frequency;

[0018] Figure 4 is a diagram illustrating an example of a PRACH-Config information element;

[0019] Figure 5 is a diagram illustrating an example of a RACH-ConfigCommon information element;

[0020] Figure 6 is a table illustrating an example of random access preamble parameters for frame structure type 2;

[0021] Figure 7 is a table illustrating an example of a random access configuration for FR1 and unpaired spectrum;

[0022] Figure 8 is a table illustrating an example of a random access configuration for FR2 and unpaired spectrum;

[0023] Fig. 9 is a table illustrating an example of a TPC command for a PUSCH;

[0024] Fig.10 is a table illustrating an example of mapping between a PRACH configuration period and an SS / PBCH block to a PRACH opportunity association period;

[0025] Fig.11 is a diagram illustrating an example of a RACH-ConfigCommon IE;

[0026] Fig.12 is a diagram illustrating an example of a BeamFailureRecoveryConfig;

[0027] Figures 13A-13D is a schematic diagram illustrating an example of a scenario associated with multiple PRACH transmissions according to some embodiments;

[0028] Fig.14 is a diagram illustrating an example of a preamble pattern according to some embodiments;

[0029] Fig.15 is a diagram illustrating an example of Msg1 repetition configured using RACH indication and segmentation framework according to some embodiments;

[0030] Figures 16A-16B is a diagram illustrating an example of PRACH opportunities indexed by two PRACH configurations according to some embodiments;

[0031] Figures 17A-17B is a diagram illustrating an example of a RO with a preamble for a specific number of PRACH transmissions according to some embodiments;

[0032] Fig.18 is a flow diagram illustrating an example of a network node coherently combining multiple PRACH transmissions.

[0033] Fig.19 is a flow diagram illustrating an example of a network node incoherently combining multiple PRACH transmissions.

[0034] Fig. 20 is a diagram illustrating an example of a large delay spread caused by transmission using different Tx beams according to some embodiments;

[0035] Figures 21A-21B is a diagram illustrating an example of RO and SSB mapping according to some embodiments;

[0036] Fig. 22 is a diagram illustrating an example of preamble selection for mapping multiple SSBs to one RO according to some embodiments;

[0037] Fig.23 is a flow chart illustrating an example of operations performed by a communication device during a RA procedure according to some embodiments;

[0038] Fig.24 is a flow chart illustrating an example of operations performed by a network node during a RA procedure according to some embodiments;

[0039] Fig.25 is a block diagram of a communication system according to some embodiments;

[0040] Fig.26 is a block diagram of a user equipment according to some embodiments;

[0041] Fig. 27 is a block diagram of a network node according to some embodiments;

[0042] Fig.28 is a block diagram of a host in communication with a user device according to some embodiments;

[0043] Fig.29 is a block diagram of a virtualization environment according to some embodiments; and

[0044] Fig.30 is a block diagram of a host communicating with a user device via a base station over a partially wireless connection according to some embodiments. DETAILED DESCRIPTION

[0045] 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, wherein examples of embodiments of the inventive concept are shown. However, the inventive concept can be embodied in many different forms and should not be construed as being 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 the inventive concept to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be assumed by default to exist / use in another embodiment.

[0046] Considering random access operation for the Long Term Evolution ("LTE") standard, as mentioned above, when signaled, a user equipment ("UE") can move from no coverage enhancement or small coverage enhancement (coverage extension ("CE") mode A) to large coverage enhancement (CE mode B). The idea is to only keep the UE in CE mode B if the UE cannot use small coverage operation for synchronization acquisition, system information acquisition, random access, or data transmission. In enhanced coverage operation, the number of repetitions can be adapted according to the coverage situation of the UE.

[0047] In some examples, the UE is a reduced bandwidth / low complexity ("BL") UE or a coverage enhanced UE. If the random access preamble is sent in a non-terrestrial network, the random access response ("RAR") window starts at the subframe containing the end of the last preamble repetition plus 3+UE-eNB round trip time ("RTT") subframes and has a length of ra-ResponseWindowSize for the corresponding enhanced coverage level. Otherwise, the RAR window starts at the subframe containing the end of the last preamble repetition plus three subframes and has a length of ra-ResponseWindowSize for the corresponding enhanced coverage level.

[0048] In an additional or alternative example, the UE is a narrowband Internet of Things ("NB-IoT") UE. If the random access preamble is sent in a non-terrestrial network, the RAR window starts at a subframe containing the end of the last preamble repetition plus X+UE-eNB RTT subframes and has a length ra-ResponseWindowSize for the corresponding enhanced coverage level, where the value X is determined based on the preamble format used and the number of NPRACH repetitions. Otherwise, the random access response ("RAR") window starts at a subframe containing the end of the last preamble repetition plus X subframes and has a length ra-ResponseWindowSize for the corresponding enhanced coverage level, where the value X is determined based on the preamble format used and the number of NPRACH repetitions.

[0049] The RA-Radio Network Temporary Identifier ("RNTI") associated with the Physical Random Access Channel ("PRACH") in which the random access preamble is transmitted is calculated as:

[0050] RA-RNTI=1+t_id+10*f_id

[0051] Where t_id is the index of the first subframe of the designated PRACH (0≤t_id<10), and f_id is the index of the designated PRACH in ascending frequency domain within that subframe (0≤f_id<6), except for Narrowband Internet of Things ("NB-IoT") UEs, Reduced Bandwidth / Low Capacity ("BL") UEs, or Coverage Enhanced UEs. If the PRACH resource is on a Time Division Duplex ("TDD") carrier, then f_id is set to f RA .

[0052] For BL UEs and coverage enhanced UEs, the RA-RNTI associated with the PRACH in which the random access preamble is transmitted is calculated as:

[0053] RA-RNTI=1+t_id+10*f_id+60*(SFN_id mod(Wmax / 10))

[0054] 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 in the subframe in ascending frequency domain (0≤f_id<6), SFN_id is the index of the first radio frame of the specified PRACH, and Wmax is 400, which is the maximum possible RAR window size in a subframe for BL UEs or coverage enhanced UEs. If the PRACH resource is on a TDD carrier, f_id is set to f RA .

[0055] For NB-IoT UEs, the RA-RNTI associated with the PRACH in which the random access preamble is transmitted is calculated as:

[0056] RA-RNTI=1+floor(SFN_id / 4)+256*carrier_id

[0057] Where SFN_id is the index of the first radio frame of the specified PRACH, and carrier_id is the index of the uplink ("UL") carrier associated with the specified PRACH. The carrier_id of the anchor carrier is 0.

[0058] For BL / CE UEs, for each PRACH coverage enhancement level, there is a PRACH configuration configured by higher layers, which has a PRACH configuration index (prach-ConfigurationIndex), a PRACH frequency offset (prach-FrequencyOffset), the number of PRACH repetitions per attempt (numRepetitionPerPreambleAttempt) and optional PRACH start subframe period (prach-StartingSubframe). PRACH with preamble format 0-3 is sent times, while the PRACH with preamble format 4 is only sent once.

[0059] For BL / CE UEs and for each PRACH coverage enhancement level, if frequency hopping is enabled for the PRACH configuration via the higher layer parameter prach-HoppingConfig, the parameter The value of depends on the system frame number (“SFN”) and the PRACH configuration index.

[0060] If the PRACH configuration index is such that when according to Figure 2 The table in is calculated as follows when PRACH resources appear in each radio frame,

[0061]

[0062] otherwise

[0063]

[0064] Where n f is the system frame number corresponding to the first subframe for each PRACH repetition, Corresponds to the cell-specific higher layer parameter prach-HoppingOffset. If frequency hopping is not enabled for the PRACH configuration, then

[0065] For frame structure type 1 with preamble formats 0-3, there is at most one random access resource per subframe for each PRACH configuration in the PRACH configuration.

[0066] For frame structure type 2 with preamble formats 0-4, for each of the PRACH configurations, there may be multiple random access resources in a UL subframe (or UpPTS for preamble format 4) depending on the UL / DL configuration.

[0067] Figure 2 An example of a table listing PRACH configurations allowed for frame structure type 2 is shown, where the configuration index corresponds to the preamble format, the PRACH density value D RA and version index r RA a specific combination of.

[0068] For frame structure type 2 with PRACH configuration index 0, 1, 2, 20, 21, 22, 30, 31, 32, 40, 41, 42, 48, 49, 50, or frame structure type 2 with PRACH configuration index 51, 53, 54, 55, 56, 57 in UL / DL configuration 3, 4, 5, the UE may assume for handover purposes that the absolute value of the relative time difference between radio frames i in the current cell and the target cell is less than 153600·T s .

[0069] Figure 2 For a specific PRACH density value D RA The required different random access opportunities are listed in the mapping to physical resources. Each quadruple of the format Indicates the location of a specific random access resource, where f RA is the frequency resource index within the considered time instance, Indicates whether the resource reappears in all radio frames, even radio frames or odd radio frames, respectively, respectively indicate whether the random access resource is located in the first half frame or the second half frame, and wherein is the uplink subframe number in which the preamble starts, counting from 0 at the first uplink subframe between 2 consecutive downlink to uplink switching points, except for preamble format 4, in which The start point of the random access preamble format 0-3 shall coincide with the assumption N TA = 0, and the random access preamble frame format 4 should be aligned with the start of the corresponding uplink subframe at the UE 4832·T before the end of the UpPTS at the UE s Starting from, assuming that N TA =0, UpPTS uses the UE's uplink frame timing as a reference.

[0070] If and only if the time multiplexing is not sufficient to accommodate a certain density value D without overlap in time RA When all the opportunities of the required PRACH configurations are allocated, the random access opportunities for each PRACH configuration shall be allocated first in time and then in frequency. For preamble formats 0-3, frequency multiplexing shall be performed according to the following formula

[0071]

[0072] in is the number of uplink resource blocks, is the first physical resource block allocated to the PRACH opportunity under consideration, and where It is the first physical resource block available for PRACH.

[0073] For BL / CE UEs, only a subset of the subframes allowed for preamble transmission are allowed as The allowed starting subframes for PRACH configuration are determined as follows.

[0074] The subframes allowed for preamble transmission for PRACH configuration are enumerated as in and Corresponding to the minimum and maximum absolute subframe numbers respectively The two subframes allowed for preamble transmission.

[0075] If the PRACH starts subframe period is not provided by higher layers, the period of the allowed starting subframes expressed in terms of the subframes allowed for preamble transmission is exist The allowed starting subframes defined above are Given, where j = 0, 1, 2, ...

[0076] If the PRACH starts subframe period If provided by a higher layer, it indicates the period of the allowed starting subframes with the subframes allowed for preamble transmission. The allowed starting subframes defined above are Given, where j = 0, 1, 2, ...

[0077] Not allowed in is defined so that The starting subframe.

[0078] Each random access preamble occupies a bandwidth corresponding to 6 consecutive resource blocks for two frame structures.

[0079] Figure 3 An example of frame structure type 2 random access preamble mapping in time and frequency is illustrated. Figure 4 illustrates an example of a PRACH-Config information element, and Figure 5 The figure shows an example of the RACH-ConfigCommon information element. The physical layer random access preamble is based on a single subcarrier frequency hopping symbol group. The symbol group is Figure 6 is shown in the table, which consists of the length T CP The cyclic prefix sum has a total length T SEQ The total number of symbol groups in the preamble repetition unit is denoted by P. The number of time-continuous symbol groups is given by G.

[0080] A preamble consisting of P symbol groups should be sent For frame structure type 2, when an invalid uplink subframe overlaps with the transmission of G symbol groups without gaps, the G symbol groups are discarded. For frame structure type 2, the transmission of G symbol groups is aligned with the subframe boundary.

[0081] The frequency position of NPRACH transmission is constrained to subcarriers, and when configured as Figure 6 The preamble format 2 described in Frequency hopping should be used within 12 subcarriers and when configured as Figure 6 The preamble format 2 described in SHOULD be used within 36 subcarriers, where the frequency position of the i-th symbol group is determined by Given, where quantity Depends on the frame structure.

[0082] Referring now to the random access operation for the 3rd Generation Partnership Project ("3GPP") New Radio ("NR") standard, there are 64 preambles defined in each time-frequency PRACH opportunity, arranged in a cyclic shift order of first increasing logical root sequence C. v The preambles are enumerated in increasing order of logical root sequence indices (starting with the index obtained from the higher layer parameter prach-RootSequenceIndex or rootSequenceIndex-BFR). In the case that 64 preambles cannot be generated from a single root Zadoff-Chu sequence, additional preamble sequences are obtained from root sequences with consecutive logical indices until all 64 sequences are found. The logical root sequence order is cyclic; logical index 0 is in L RA =839 is continuous with 837, and at L RA = 139, it is continuous with 137. The sequence number u is obtained from the logical root sequence index.

[0083] Cyclic shift C v Given by the following formula

[0084]

[0085] The higher-level parameter restrictedSetConfig determines the type of the restricted set (unrestricted, restricted type A, restricted type B).

[0086] The parameters used to determine the root sequence and its cyclic shift in the PRACH preamble code sequence set include: sequence length; logical index to the root sequence table; and preamble code subcarrier spacing ("SCS") (for example, if SCS = 1.25 / 5kH, it is unrestricted, restricted set A or restricted set B).

[0087] The random access preamble can only be used in Figure 7-8 The datagrams are sent in the table in the table and in the time resources given depending on FR1 or FR2 and the spectrum type.

[0088] The random access preamble can only be sent in the frequency resource given by the higher layer parameter msg1-FrequencyStart. RA ∈{0,1,…,M-1} (where M is equal to the higher layer parameter msg1-FDM) are numbered in ascending order starting from the lowest frequency within the initial uplink bandwidth portion during initial access. Otherwise, n RA Numbered in ascending order starting with the lowest frequency within the active uplink bandwidth portion.

[0089] For the purpose of timeslot numbering, the following subcarrier spacing may be assumed: 15 kHz for FR1 and 60 kHz for FR2.

[0090] The number of time domain RACH opportunities within a RACH slot for each PRACH configuration index is fixed.

[0091] For non-paired spectrum, if the UE is not provided with tdd-UL-DL-ConfigurationCommon, a PRACH opportunity in a PRACH slot is valid if it is not preceded by a synchronization signal ("SS") / physical broadcast channel ("PBCH") block in the PRACH slot and is at least N received symbols after the last SS / PBCH block. gap If it starts at symbols, N gap is provided; and if channelAccessMode="semiStatic" is provided, the PRACH opportunities in the PRACH slot do not overlap with the set of consecutive symbols before the start of the next channel occupancy time in which the UE does not transmit, and the candidate SS / PBCH block index of the SS / PBCH block corresponds to the SS / PBCH block index provided by SIB1 or ssb-PositionsInBurst in ServingCellConfigCommon.

[0092] If the UE is provided with tdd-UL-DL-ConfigurationCommon, a PRACH opportunity in a PRACH slot is valid if it is within a UL symbol or if it is not preceded by an SS / PBCH block in the PRACH slot and is at least N blocks after the last downlink symbol. gap If it starts at symbols, N gap is provided; and if channelAccessMode="semiStatic" is provided, the PRACH opportunities in the PRACH slot do not overlap with the set of consecutive symbols before the start of the next channel occupancy time without any transmission. The candidate SS / PBCH block index of the SS / PBCH block corresponds to the SS / PBCH block index provided by system information block 1 ("SIB1") or ssb-PositionsInBurst in ServingCellConfigCommon.

[0093] For preamble format B4, N gap =0.

[0094] For operation on a single carrier in unpaired spectrum, if a UE is configured by higher layers to transmit a Sounding Reference Signal ("SRS"), Physical Uplink Control Channel ("PUCCH"), Physical Uplink Shared Channel ("PUSCH"), or PRACH in a set of symbols in a timeslot, and the UE detects a Downlink Control Information ("DCI") format that indicates to the UE to receive a Channel State Information Reference Signal ("CSI-RS") or Physical Downlink Shared Channel ("PDSCH") in a subset of symbols from the set of symbols, then if the UE does not have the capability to indicate a partialCancellation, then the UE does not expect to cancel transmission of the PUCCH or PUSCH or PRACH in the set of symbols if the first symbol in the set occurs within T2 relative to the last symbol of the Control Resource Set ("CORESET") in which the UE detected the DCI format. proc,2 If the UE indicates the [partialCancellation] capability, the UE is not expected to cancel the transmission of PUCCH or PUSCH or PRACH in symbols from this symbol set that occur within T relative to the last symbol of the CORESET in which the UE detected the DCI format. proc,2 The UE cancels the PUCCH, or PUSCH or actual repetition of PUSCH determined from the PRACH transmission in the remaining symbols from this symbol set [6, TS 38.214].

[0095] PRACH uses the BWP b of carrier f of serving cell c and transmits at a transmit power of P on the indicated PRACH resource. PRACH,b,f,c (i) Transmit using the selected PRACH format.

[0096] P PRACH,b,f,c (i) = min{P CMAX,f,c (i),P PRACH,target,b,f,c (i)+PL b,f,c}[dBm]

[0097] If the UE does not receive a random access response including a preamble identifier corresponding to the preamble sequence sent by the UE within the random access response window, the UE determines the transmit power (if any) to be used for subsequent PRACH transmissions.

[0098] If the UE changes the spatial domain transmit filter before PRACH retransmission, Layer 1 notifies higher layers to suspend the power ramp counter.

[0099] For each random access preamble, the MAC entity shall:

[0100] 1> if PREAMBLE_TRANSMISSION_COUNTER is greater than 1; and

[0101] 1> if notification to suspend the power ramp counter has not been received from lower layers; and

[0102] 1> If the selected SSB or CSI-RS has not changed compared to the selection in the last random access preamble transmission:

[0103] 2>Increase PREAMBLE_POWER_RAMPING_COUNTER by 1.

[0104] 1>Select the value of DELTA_PREAMBLE;

[0105] 1> Set PREAMBLE_RECEIVED_TARGET_POWER to preambleReceivedTargetPower+DELTA_PREAMBLE+

[0106] (PREAMBLE_POWER_RAMPING_COUNTER-1)×

[0107] PREAMBLE_POWER_RAMPING_STEP;

[0108] 1> Calculate the RA-RNTI associated with the PRACH opportunity in which the random access preamble is sent, except for the contention-free random access preamble used for beam failure recovery request;

[0109] 1> Instructs the physical layer to send a random access preamble using the selected PRACH opportunity, the corresponding RA-RNTI (if available), PREAMBLE_INDEX and PREAMBLE_RECEIVED_TARGET_POWER.

[0110] Support for Msg3 repetition was introduced in Rel-17 NR. The UE can be configured to repeat Msg3 via parameters given in the SIB. Unlike LTE, the UE can request repetition for PUSCH transmission and does so by sending a RACH preamble associated with the repetition procedure. The network then indicates the number of repetitions via the MCS field in the RAR or PDCCH carrying DCI format 0_0

[0111] The set of repetition numbers for PUSCH transmissions with PUSCH repetition type A scheduled by a RAR UL grant or DCI format 0_0 with a CRC scrambled by a temporary cell radio network temporary identifier ("TC-RNTI") may be provided to the UE in RACH-ConfigCommon. If the UE requests repetitions for a PUSCH transmission, the UE PUSCH is sent on time slots, where The 2 MSBs of the MCS field in the RAR UL grant or DCI format 0_0 are indicated from the set of four values ​​provided by numberOfMsg3Repetitions, or from {1,2,3,4} if numberOfMsg3Repetitions is not provided. The UE determines the MCS for PUSCH transmission from the 2 LSBs of the MCS field in the RAR UL grant or the 3 LSBs of the MCS field in DCI format 0_0 and determines the redundancy version and RBs to be used for each repetition as described in [6, TS 38.214]. For non-paired spectrum operation, the UE shall The time slot is determined as the first time slot starting from time slot n+k2+Δ time slots, where the repetition of the PUSCH transmission does not include symbols indicated as downlink by tdd-UL-DL-ConfigurationCommon or as symbols of an SS / PBCH block using the index provided by ssb-PositionsInBurst.

[0112] If a UE sends a PUSCH on an active UL BWP b of carrier f in serving cell c using parameter set configuration with index j and PUSCH power control adjustment state with index l, the UE sets the PUSCH transmit power P in PUSCH transmission opportunity i to PUSCH,b,f,c (i,j,q d ,l) is determined as:

[0113]

[0114] Where, for the PUSCH power control adjustment state f of the active UL BWP b for carrier f serving cell c in PUSCH transmission opportunity i, b,f,c (i, l), if the UE receives a random access response message in response to a PRACH transmission on the active UL BWP b of carrier f of serving cell c, then f b,f,c (0,l)=ΔP rampup,b,f,c +δ msg2,b,f,c , where l = 0 and δ msg2,b,f,c is the TPC command value indicated in the random access response grant of the random access response message corresponding to the PRACH transmission on the active UL BWP b of carrier f in serving cell c, and And ΔP rampuprequested,b,f,c provided by higher layers and corresponds to the total power ramp-up from the first to the last random access preamble for carrier f in serving cell c requested by higher layers, is the bandwidth of the PUSCH resource allocation expressed in number of resource blocks for the first PUSCH transmission on active UL BWP b of carrier f serving cell c, and Δ TF,b,f,c (0) is the power adjustment for the first PUSCH transmission on the active UL BWP b of carrier f serving cell c.

[0115] TPC command value δ msg2,b,f,c Used to set the PUSCH transmission power according to Fig. 9 Provide explanation.

[0116] In some examples, a number N of SS / PBCH block indices associated with one PRACH opportunity and a number R of contention-based preambles per valid PRACH opportunity for each SS / PBCH block index are provided to the UE via ssb-perRACH-OccasionAndCB-PreamblesPerSSB.

[0117] If N < 1, one SS / PBCH block index is mapped to 1 / N consecutive valid PRACH opportunities, and the R contention-based preambles with consecutive indices associated with the SS / PBCH block index for each valid PRACH opportunity start from preamble index 0. If N ≥ 1, the R contention-based preambles with consecutive indices associated with the SS / PBCH block index n (0 ≤ n ≤ N-1) for each valid PRACH opportunity start from preamble index 0. Start, where Provided by totalNumberOfRA-Preambles for Type 1 Random Access procedure.

[0118] The SS / PBCH block indices provided by ssb-PositionsInBurst in SIB1 or ServingCellConfigCommon are mapped to valid PRACH opportunities in the following order in which the parameters are described. First, in ascending order of preamble index within a single PRACH opportunity. Second, in ascending order of frequency resource indexes for frequency-reused PRACH opportunities. Third, in ascending order of time resource indexes for time-reused PRACH opportunities within a PRACH slot. Fourth, in ascending order of indexes for PRACH slots.

[0119] In some examples, the association period starting from frame 0 for mapping SS / PBCH blocks to PRACH opportunities is determined based on Fig.10 The minimum value in the set determined by the PRACH configuration period, such that SS / PBCH blocks are mapped to PRACH opportunities at least once in the associated period, where the UE obtains the value of ssb-PositionsInBurst from SIB1 or ServingCellConfigCommon If after an integer number of SS / PBCH blocks in the associated period are mapped to PRACH opportunities, there are If a PRACH opportunity or a set of PRACH preambles for an integer number of SS / PBCH blocks is mapped to the PRACH opportunity or the set of PRACH preambles, no SS / PBCH block is mapped to the PRACH opportunity or the set of PRACH preambles. The association pattern period includes one or more association periods and is determined so that the pattern between PRACH opportunities and SS / PBCH blocks repeats at most once every 160 milliseconds. PRACH opportunities (if any) that are not associated with SS / PBCH blocks after an integer number of association periods are not used for PRACH transmission.

[0120] In some examples, the PRACH opportunities are mapped consecutively for each corresponding SS / PBCH block index. For each SS / PBCH block index, the indexing of the PRACH opportunities indicated by the mask index value is reset for each mapping period of consecutive PRACH opportunities. The UE selects the PRACH opportunity indicated by the PRACH mask index value for the indicated SS / PBCH block index in the first available mapping period for PRACH transmission.

[0121] For the indicated preamble index, the PRACH occasions are ordered: 1) in ascending order of frequency resource index for frequency-reused PRACH occasions; 2) in ascending order of time resource index for time-reused PRACH occasions within a PRACH slot; and 3) in ascending order of index for PRACH slots. Fig.11 An example of a RACH-ConfigCommon information element ("IE") is illustrated.

[0122] In response to a PRACH transmission, the UE attempts to detect a DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI during a window controlled by higher layers. The window starts at the first symbol of the earliest CORESET for which the UE is configured to receive PDCCH for a Type 1-PDCCH CSS set (as defined in clause 10.1), which is at least one symbol after the last symbol of the PRACH opportunity corresponding to the PRACH transmission, where the symbol duration corresponds to the SCS for the Type 1-PDCCH CSS set. The window length, expressed in number of slots, based on the SCS for the Type 1-PDCCH CSS set is provided by ra-ResponseWindow.

[0123] TPC command value δ msg2,b,f,c Used to set the PUSCH transmission power according to Fig. 9 Explanation: The CSI request field is reserved.

[0124] In some examples, if the UE receives a random access response message in response to a PRACH transmission on an active UL BWP b of carrier f of serving cell c, then f b,f,c (0,l)=ΔP rampup,b,f,c +δ msg2,b,f,c , where l = 0 and δ msg2,b,f,c is the TPC command value indicated in the random access response grant of the random access response message corresponding to the PRACH transmission on the active UL BWP b of carrier f in serving cell c.

[0125] Radio Resource Control ("RRC") may configure the following parameters for the RA procedure.

[0126] prach-ConfigurationIndex: The available set of PRACH opportunities for transmission of random access preamble.

[0127] preambleReceivedTargetPower: Initial random access preamble power.

[0128] rsrp-ThresholdSSB: RSRP threshold for selecting SSB. If the random access procedure is initiated for beam failure recovery, the rsrp-ThresholdSSB used to select SSB in candidateBeamRSList refers to the rsrp-ThresholdSSB in BeamFailureRecoveryConfig IE.

[0129] rsrp-ThresholdCSI-RS: RSRP threshold for selecting CSI-RS. If the random access procedure is initiated for beam failure recovery, rsrp-ThresholdCSI-RS is equal to rsrp-ThresholdSSB in the BeamFailureRecoveryConfig IE.

[0130] rsrp-ThresholdSSB-SUL: RSRP threshold used to select between NUL carrier and SUL carrier.

[0131] candidateBeamRSList: A list of reference signals (CSI-RS and / or SSB) identifying candidate beams and associated random access parameters for recovery.

[0132] recoverySearchSpaceId: Search space identifier used to monitor responses to beam failure recovery requests.

[0133] powerRampingStep: Power ramp factor.

[0134] powerRampingStepHighPriority: Power ramping factor in case of priority random access procedure.

[0135] scalingFactorBI: Scaling factor used for the priority random access process.

[0136] ra-PreambleIndex: Random access preamble.

[0137] ra-ssb-OccasionMaskIndex: defines the PRACH occasion(s) associated with the SSB in which the MAC entity may send a random access preamble.

[0138] ra-OccasionList: defines the PRACH occasion(s) associated with the CSI-RS in which the MAC entity can send a random access preamble.

[0139] ra-PreambleStartIndex: The starting index of the random access preamble(s) used for on-demand SI request.

[0140] preambleTransMax: Maximum number of random access preamble transmissions.

[0141] ssb-perRACH-OccasionAndCB-PreamblesPerSSB: defines the number of SSBs mapped to each PRACH opportunity and the number of contention-based random access preambles mapped to each SSB.

[0142] If groupBconfigured is configured, random access preamble group B is configured. Among the contention-based random access preambles associated with an SSB, the first numberOfRA-PreamblesGroupA random access preambles belong to random access preamble group A. The remaining random access preambles associated with an SSB belong to random access preamble group B (if configured). If the cell supports random access preamble group B, random access preamble group B is included for each SSB.

[0143] Beam failure detection and recovery are described below.

[0144] In some examples, for beam failure detection, the gNB configures a beam failure detection reference signal (SSB or channel state information reference signal (“CSI-RS”)) to the UE, and when the number of beam failure instance indications from the physical layer reaches a configured threshold before a configured timer expires, the UE declares a beam failure.

[0145] In an additional or alternative example, SSB-based beam failure detection is based on SSBs associated with an initial DL bandwidth part ("BWP") and can only be configured for the initial DL BWP and a DL BWP containing SSBs associated with the initial DL BWP. For other DL BWPs, beam failure detection can only be performed based on CSI-RS.

[0146] After detecting beam failure, the UE triggers beam failure recovery by initiating a random access procedure on the PCell and selects a suitable beam to perform beam failure recovery (if the gNB has provided dedicated random access resources for certain beams, the UE will give priority to these beams).

[0147] After the random access procedure is completed, beam failure recovery is considered complete.

[0148] In some examples, a medium access control ("MAC") entity should:

[0149] 1> If a beam failure instance indication has been received from a lower layer:

[0150] 2> Start or restart beamFailureDetectionTimer (beam failure detection timer);

[0151] 2>Increase BFI_COUNTER by 1;

[0152] 2> if BFI_COUNTER>= beamFailureInstanceMaxCount:

[0153] 3>Initiate a random access process on SpCell.

[0154] 1> if beamFailureDetectionTimer expires; or

[0155] 1> If any of beamFailureDetectionTimer, beamFailureInstanceMaxCount, or the reference signal for beam failure detection is reconfigured by upper layers:

[0156] 2> Set BFI_COUNTER to 0.

[0157] 1> If the random access process is successfully completed (:

[0158] 2> Set BFI_COUNTER to 0;

[0159] 2>Stop beamFailureRecoveryTimer (if configured);

[0160] 2> The beam failure recovery process is considered to be successfully completed.

[0161] For each BWP of the serving cell, a set of periodic CSI-RS resource configuration indices can be provided to the UE via failureDetectionResources And provide a set of periodic CSI-RS resource configuration indexes and / or SS / PBCH block indexes to the UE through candidateBeamRSList for radio link quality measurement on the BWP of the serving cell If the UE is not provided with failureDetectionResources, the UE determines the set The periodic CSI-RS resource configuration index includes a value that is the same as the RS index in the RS set indicated by the TCI-State for the corresponding CORESET (the UE uses the corresponding CORESET to monitor the PDCCH), and if there are two RS indices in the TCI state, the set Includes RS index with QCL-TypeD configuration for corresponding TCI state. UE expected set Includes up to two RS indices. UE expected set The single-port RS in.

[0162] In non-DRX mode operation, when the set of UEs used to evaluate the radio link quality The radio link quality of all corresponding resource configurations in is worse than the threshold Q out,LR The physical layer in the UE provides an indication to higher layers. out,LR When the physical layer uses the set of UEs used to evaluate the quality of the radio link The periodicity determined by the maximum value between the shortest period in the SS / PBCH block and 2 milliseconds in the periodic CSI-RS configuration in the SS / PBCH block informs the higher layer. In DRX mode operation, when the radio link quality is worse than the threshold Q out,LR The physical layer provides indications to higher layers periodically.

[0163] Based on the request from the higher layer, the UE provides the higher layer with The periodic CSI-RS configuration index and / or SS / PBCH block index, and the periodic CSI-RS configuration index and / or SS / PBCH block index greater than or equal to Q in,LR The threshold corresponds to the L1-RSRP measurement.

[0164] The UE may receive the configuration for PRACH transmission via PRACH-ResourceDedicatedBFR. For PRACH transmission in slot n and according to the antenna port quasi-colocation parameters associated with the periodic CSI-RS resource configuration or with the index q provided by the higher layers, newThe UE monitors the PDCCH in the search space set provided by recoverySearchSpaceId for detection of DCI formats with CRC scrambled by C-RNTI or MCS-C-RNTI starting from slot n+4 within the window configured by BeamFailureRecoveryConfig. For PDCCH monitoring in the search space set provided by recoverySearchSpaceId and for the corresponding PDSCH reception, the UE assumes the same search space set as and index q new The associated antenna port quasi-colocation parameters have the same antenna port quasi-colocation parameters until the UE receives an activation for the TCI state or any one of the parameters tci-StatesPDCCH-ToAddList and / or tci-StatesPDCCH-ToReleaseList through a higher layer. After the UE detects a DCI format with a CRC scrambled by C-RNTI or MCS-C-RNTI in the search space set provided by recoverySearchSpaceId, the UE continues to monitor PDCCH candidates in the search space set provided by recoverySearchSpaceId until the UE receives a MAC CE activation command for the TCI state or tci-StatesPDCCH-ToAddList and / or tci-StatesPDCCH-ToReleaseList.

[0165] After 28 symbols since the last symbol of the first PDCCH reception in the search space set provided by recoverySearchSpaceId for which the UE detects a DCI format with a CRC scrambled by C-RNTI or MCS-C-RNTI, and until the UE receives an activation command for PUCCH-SpatialRelationInfo or is provided with PUCCH-SpatialRelationInfo for PUCCH resource(s), the UE uses the same spatial filter as used for the last PRACH transmission and with q u =0,q d =q new The PUCCH is transmitted on the same cell as the PRACH transmission with a power determined by 1=0.

[0166] After 28 symbols since the last symbol received for the first PDCCH in the search space set provided by recoverySearchSpaceId (in which the UE detects a DCI format with a CRC scrambled by C-RNTI or MCS-C-RNTI), the UE assumes that the search space with index q new The associated antenna port quasi-colocation parameters are the same antenna port quasi-colocation parameters for PDCCH monitoring in the CORESET with index 0.

[0167] Fig.12 An example of a BeamFailureRecoveryConfig is illustrated. A list of reference signals (CSI-RS and / or SSB) identifying candidate beams for recovery and associated RA parameters. The UE shall consider this list to include all elements of candidateBeamRSList (without suffix) and all elements of candidateBeamRSListExt-v1610. The network configures these reference signals to be within the linked DL BWP of the UL BWP in which the BeamFailureRecoveryConfig is provided (i.e., within a DL BWP with the same bwp-Id).

[0168] Since many features in Rel-17 want to use the Msg1 preamble to indicate the presence of certain features (such as Msg3 repetition, redcap, slicing and small data transmission) at an early stage. The solution is to introduce a common framework for allocating preambles in ROs and conditions for using these preamble groups and combinations of different features (such as Msg3 repetition and Redcap). Using this framework, it is possible to define, for example, RO#1 with a preamble group indicating Redcap and Msg3 repetition, followed by RO#2 with a preamble defining small data transmission and Redcap+Msg3 repetition. Then define the conditions for using these preamble groups.

[0169] In NR, the UE is allowed to send one PRACH preamble for one attempt. Since PRACH is identified as the coverage bottleneck, its coverage can be enhanced through multiple PRACH transmissions.

[0170] In some examples, solutions for PRACH repetition have been adopted in LTE eMTC and NB-IoT and can be rejected or enhanced to support multiple NR PRACH transmissions. For example, new solutions are needed to customize a larger number of NR PRACH configuration indices and more flexible PRACH opportunities in the time and frequency domains. In addition, some new issues are unique to NR, including PRACH transmissions with different UL Tx beams and the association between PRACH opportunities and SSBs.

[0171] Various embodiments described herein provide operations to determine preambles, ROs, and corresponding power, TA, and phase for multiple PRACH transmissions. It also includes mapping of PRACH transmissions to UL Tx beams / SSBs.

[0172] In some embodiments, the UE may send a PRACH preamble in a PRACH opportunity associated with a selected synchronization signal block ("SSB"). The RAR is quasi co-located ("QCL") with the transmitted PRACH and its associated SSB. The timing advance ("TA") and transmit power control ("TPC") fields in the RAR are based on the received PRACH. If the UE does not receive a RAR containing its random access preamble identifier ("RAPID") within the RAR window, it may start a PRACH retransmission, which may be associated with the same SSB as the initial transmission or with a different SSB. Whether to use the same or a different UL Tx beam for the retransmission depends on the UE implementation.

[0173] like Figures 13A-13D As illustrated, there are several scenarios of multiple PRACH transmissions in terms of UL Tx beam and SSB. Fig.13A An example is illustrated in which a UE transmits multiple PRACHs using the same beam (eg, using the same UL spatial relationship), and all PRACH transmissions are associated with the same SSB. Fig. 13B An example is shown where different beams are used for PRACH transmission and are associated with one SSB. The determination of the UL Tx beam depends on the UE implementation and is transparent to the gNB. Figures 13C-13D An example is shown in which multiple PRACH transmissions are associated with different SSB beams. Fig. 13C In , there is a unique PRACH associated with each selected SSB, while in Fig.13D In the embodiment, at least one SSB is associated with more than one PRACH transmission. Fig.13D yes Figures 13B-13C and the embodiments associated with each figure can be applied to Fig.13D Examples in .

[0174] In some embodiments, it is left to the UE implementation to determine the UL Tx beam for Msg1. For UEs with auxiliary beam scanning to have beam correspondence and UEs that cannot refine their Tx beams during the limited time of random access, they can use a wide UL Tx beam, resulting in relatively small receive power at the gNB until the UE can go through the beam refinement process after RRC connection establishment. Multiple PRACH transmissions with different UL Tx beams allow the UE to scan narrow beams with better directivity and higher receive power at the gNB.

[0175] Depending on the value of ssb-perRACH-OccasionAndCB-PreamblesPerSSB, there is an association between a PRACH occasion and an SS block or between a PRACH preamble index and an SS block. It may be referred to as a PRACH transmission associated with an SSB. "Multiple PRACH transmissions" refers to those PRACH transmissions of one RACH attempt, that is, the PRACH transmissions are those made before receiving the RAR, unless otherwise stated.

[0176] Some embodiments herein are applicable to contention-based random access ("CBRA") and contention-free random access ("CFRA"). CFRA resources for beam failure recovery requests may be associated with SSBs and / or CSI-RS. However, for the sake of brevity, PRACH transmissions associated with SSBs are referred to herein instead of PRACH transmissions associated with SSBs and / or CSI-RS.

[0177] Some embodiments herein are applicable to 4-step RACH and 2-step RACH.

[0178] Some embodiments associated with determining single or multiple PRACH transmissions are described below.

[0179] In LTE, eMTC and NB-IoT, the network configures several N PRACH configurations with different numbers of repetitions for coverage enhancement of a cell. The UE will select the appropriate PRACH configuration for RA depending on the coverage level estimate based on RSRP measurement. In a similar way, the NR UE can determine the number of PRACH transmissions based on the measured RSRP and the configured threshold.

[0180] In some embodiments, rsrp-ThresholdMsg3 is reused to determine whether to perform multiple PRACH transmissions configured via a flag in RRC for a specific BWP or a specific preamble feature group. If the RSRP is lower than rsrp-ThresholdMsg3, the UE repeats the PRACH. In addition, the repetition process applies to Msg3 transmissions, and Msg3 is repeated the number of times indicated in the random access response or DCI format 0_0, which has a CRC scrambled by TC-RNTI.

[0181] In additional or alternative embodiments, NUL and SUL may have separate new thresholds for multiple PRACH transmissions. This may be reflected by an offset associated with the threshold to determine whether to select NUL or SUL-rsrp-ThresholdSUL.

[0182] In addition to depending on the RSRP threshold, there are other ways for the UE to select multiple PRACH transmissions. The network typically has fairly limited information about the power headroom available to the UE during initial access, as there are typically no power headroom reports available to the UE during initial access. In contrast, the UE knows how much power it has. In cases where it cannot deliver the required amount of power based on the PRACH target received power and path loss estimates (which are higher than P CMAX,f,c In the case of (i)), it can trigger multiple PRACH transmissions. By allowing the UE to repeat only when needed, uplink resources and UE power can be avoided from being wasted on unnecessary repetitions.

[0183] In some embodiments, the UE determines single or multiple PRACH transmissions based on its power headroom. PRACH,target,f,c +PL b,f,c Greater than its maximum configuration power P CMAX,f,c (i) (hereinafter abbreviated as "Pcmax"), the UE performs multiple PRACH transmissions. Otherwise, the UE performs a single PRACH transmission.

[0184] In additional or alternative embodiments, the gap between the required power and Pcmax, ie, P PRACH,target,f,c +PL b,f,c -P CMAX,f,c (i) It can be scaled to different numbers of PRACH repetitions according to predetermined rules and configured numbers.

[0185] For example, if the gap is 0-3 dB, the UE sends 2 PRACHs; if the gap is 3-6 dB, 4 PRACHs are sent.

[0186] In some embodiments, after the UE sends the first PRACH but fails to receive the RAR or receives the RAR but not for itself, the UE may initiate multiple PRACH transmissions for PRACH retransmissions. In this case, the number of retransmissions and the power of the retransmissions may depend on network configured parameters. It may be configured or predetermined whether the UE can increase both the number of PRACH transmissions and the transmit power for Msg1 retransmissions, or only one of them.

[0187] In some embodiments, the network enables multiple PRACH transmissions through SIBs for specific services. For example, if the establishmentCause in the RRCSetupRequest is set to emergency or for mission-critical services, the UE can initiate multiple PRACH transmissions if the network configures and allows it.

[0188] In NR up to Rel-17, when the gNB detects energy but fails to detect the preamble, it can indicate the BI field in the RAR. A UE that does not receive a RAR with its RAPID can do a PRACH retransmission after the backoff time. As described below, for CBRA, it is a random value between 0 and PREAMBLE_BACKOFF*SCALING_FACTOR_BI. SCALING_FACTOR_BI is set to 1 unless it is configured in beamFailureRecoveryConfig or rach-ConfigDedicated.

[0189] 2> If the random access response contains a MAC sub-PDU with a backoff indicator:

[0190] 3> Set PREAMBLE_BACKOFF to the value of the BI field of the MAC sub-PDU using Table 7.2-1 multiplied by SCALING_FACTOR_BI.

[0191] 2> If the random access process is not completed:

[0192] 3> Choose a random backoff time based on a uniform distribution between 0 and PREAMBLE_BACKOFF;

[0193] 3> If the criteria for selecting a contention-free random access resource are met during the backoff time:

[0194] 4>Execute random access resource selection process;

[0195] 3> Otherwise:

[0196] 4> Perform random access resource selection process after the backoff time.

[0197] The MAC subheader may include a Backoff Indicator ("BI") field, which identifies an overload condition in the cell. The size of the BI field is 4 bits.

[0198] If the NW is not overloaded, UEs in poor coverage can send more PRACH transmissions by using more RACH resources. In case of NW overload, UEs sending a large number of PRACH may cause many preambles from other UEs to be misdetected, then the NW can use different strategies to ensure that all UEs have fair network access opportunities, whether they are in good or poor cell coverage. Fair access cannot be achieved if UEs that sent different numbers of PRACH transmissions in previous attempts use the same backoff time for retransmission. UEs using more PRACH resources must start retransmissions after a larger backoff time.

[0199] In some embodiments, a UE that sent a large number of PRACH transmissions in a previous attempt is configured or indicated with a larger backoff time than a UE that sent a small number of (one or more) PRACH transmissions. For example, PREAMBLE_BACKOFF and / or SCALING_FACTOR_BI may be specific to a particular number of PRACH transmissions.

[0200] To reduce the impact on legacy UEs and facilitate gNB preamble detection, specific preambles and / or ROs may be allocated for UEs capable of multiple PRACH transmissions.

[0201] For the preamble determination for multiple transmissions, a common approach is to send the same preamble multiple times, just like LTE eMTC. In LTE eMTC, since the number of PRACH repetitions is determined by the UE, the eNB can interpret the number by receiving the corresponding preamble. That is, the preamble or PRACH resource is different between repetition levels, but this reduces the PRACH capacity.

[0202] In some embodiments, the UE may send different preambles across multiple ROs associated with the selected SSB.

[0203] In an additional or alternative embodiment, the UE selects a preamble index for the selected SSB for the first PRACH in a conventional manner. For the remaining (one or more) PRACH transmissions, an offset of the preamble index, logical / physical index of the root sequence, and / or cyclic shift is applied relative to the previous PRACH, where the offset pattern may be configured / predetermined. This Fig.14The offset may be modulo-added with some value (eg, modulo-added with the number of available preambles for PRACH), or the offset may be added to form an updated index k according to the following formula: new =mod(k prev -K min +offset,K)+K min , where mod is a modulo operation, k represents the index of the preamble (according to any of the methods mentioned above), K is the number of consecutive preambles allocated for multiple PRACH repetitions, and K min can be the lowest index preamble assigned to multiple PRACH repetitions; in this way, all multiple PRACH transmissions will use the range K min To K min The offset may be different for different repetitions, but at a given time instance in the system frame structure, the offset may be the same for all UEs to maintain orthogonality between UEs in the cell. Alternatively, the offset may be calculated based on k. i =mod(k0-K min +Δ i ,K)+k min Define index k for the i-th repetition i , where Δ i is the offset of the ith repetition, and k0 is the index for the first repetition. See for example Fig.14 The offset may be different in different cells to achieve interference diversity. Alternatively, the index i may refer to a time instance relative to the system frame structure; this may be used to ensure orthogonality between UEs in a cell even if they start their repetition sets at different points in time. The RAPID is determined based on the first PRACH transmission. In addition to being based on the repetition index and / or slot index, Δ i It may also be based on one or more of: configuration, signaling, random number determined by the UE, UE identity (eg IMSI, IMEI).Therefore, UEs in a cell will not collide in all repetitions if their preambles collide in the first repetition.

[0204] 64 preambles are generated based on the cyclic shift and the logical root sequence. Indexes 0 to 63 are first in ascending order of cyclic shift and then in ascending order of logical root sequence. Using the same ordering, preambles with indices 64 to 127, 128 to 191, 192 to 255, ... can be generated. For example, the UE uses preamble indices 0, 64, 128, 192 for 4 PRACH transmissions, respectively. In another example, if one root index can provide 64 preambles with different cyclic shifts, the first preamble uses the logical root index u and the second preamble sent by the UE uses the logical root index u+1. The gNB needs to perform blind detection on subsequent possible preambles in the next RO for SSB. Different repetition levels can share the same set of preambles and ROs.

[0205] In some embodiments, the PRACH opportunities are mapped consecutively for each corresponding SS / PBCH block index. For each SS / PBCH block index, the indexing of the PRACH opportunities indicated by the masked index value is reset for each mapping period of consecutive PRACH opportunities. The UE selects the PRACH opportunity indicated by the PRACH masked index value for the indicated SS / PBCH block index in the first available mapping period for PRACH transmission.

[0206] For the indicated preamble index, the PRACH occasions are ordered: 1) in ascending order of frequency resource index for frequency-reused PRACH occasions; 2) in ascending order of time resource index for time-reused PRACH occasions within a PRACH slot; and 3) in ascending order of index for PRACH slots.

[0207] In an additional or alternative embodiment, the preamble selected for each RO depends on where the msg1 preamble group is located in the RO. This can be considered as a virtual preamble, with the same relative index with respect to the starting preamble configured for multiple PRACH transmissions in the RO. For example, we only consider K=2, i.e. the gNB supports only two PRACH transmissions. If the preamble group for msg1 repetition in RO#1 is 30-35, then the preamble group msg1 repetition in RO#2 is 19-24. If the UE selects preamble 30 in RO#1, then preamble 30 is mapped to the first preamble in RO#2, which is preamble 19. This is important because if there is no specific RO used only for msg1 repetition, but rather preamble groups in different ROs, then there needs to be a mapping. This can be done in Fig.15 Seen in.

[0208] In an additional or alternative embodiment, when the UE selects a virtual preamble using the above method, the UE will use the first preamble as the selected RAPID when detecting RAR. In addition, when selecting RA-RNTI / msgB-RNTI, the first RACH opportunity will be used to calculate RA-RNTI.

[0209] The pattern given by the PRACH Config Index is repeated once per RACH configuration period. Fig.16A An example of PRACH configuration index #160 in FR1 TDD is illustrated. For 30 KHz SCS, there are two time domain PRACH opportunities in a radio frame. Fig. 16B PRACH configuration index #127 in FR2 is shown. For 120KHz SCS, there are eight time domain PRACH opportunities in the radio frame. These time domain PRACH opportunities and the RO of FDM are divided between multiple SSBs and possibly between different repetition levels (i.e., the number of PRACH transmissions). For simplicity, we assume that in the time domain PRACH opportunity, there is at least one RO associated with the selected SSB and the determined repetition level. Otherwise, the time domain PRACH opportunities associated with SSBs other than the selected SSB and the time domain PRACH opportunities for other repetition levels are skipped for the RO determination.

[0210] In an additional or alternative embodiment, the preamble pattern is not based on a fixed offset (or modulo a fixed offset) from one transmission to the next in a repeated set as in the above-described embodiments, but follows some other pattern, such as a pattern that achieves even better interference diversity between cells. In this case, in order to limit the search space for the gNB, the pattern can be fixed with respect to the frame structure in the cell. The UE can still be allowed to start transmission at any time domain RO in the pattern, or the UE can be restricted to start transmission only at certain time domain RO within the pattern and / or radio frame structure in the cell.

[0211] For a specific number of PRACH repetitions sent by an LTE eTMC UE, if there are random access resources in each subframe, the subframe of the first PRACH transmission is explicitly determined by the configured periodicity or implicitly determined by the repetition factor so that the time domain PRACH resources used for the said number of PRACH repetitions do not overlap. Similarly, in NR, periodicity can also be configured for multiple PRACH transmissions, where multiple PRACH transmissions of RACH attempts are within the period. The unit of the period can be predetermined as an association period, a PRACH configuration period, a radio frame, a subframe, a time slot with an SCS for time slot numbering. In the time domain PRACH opportunity associated with the selected SSB, for K PRACH transmissions, the RO index i=mod(i,K)=0 for the first PRACH transmission.

[0212] For example, for PRACH configuration index #127 in FR2 and TDD, if the period is the PRACH configuration period, there are eight time domain PRACH opportunities in the period for the selected SSB. Assume that 2, 4, and 8 PRACH transmissions for RACH attempts are supported. For 8 PRACH transmissions, the time domain PRACH opportunity for the first PRACH has index 0. For 4 PRACH transmissions, the UE can send the first PRACH transmission in RO#0 or RO#4. For 2 PRACH transmissions, the first RO is RO#0, 2, 4, 6. Fig.17A As shown, each RO must have different preambles for 2, 4, and 8 PRACH transmissions. This adds further segmentation in the preamble group for multiple PRACH transmissions. This is a legacy issue in LTE eMTC, but can be solved with NR preamble groups.

[0213] In some embodiments, for a plurality of PRACH transmissions of an attempt, a set of PRACH opportunities is determined in one or more of the following ways.

[0214] In some examples, K represents the number of (one or more) PRACH transmissions supported by the gNB, including K=1 and K>1. The gNB is able to configure preambles for a portion of all K values ​​in the RO. One approach is to associate a ra-ssb-OccasionMaskIndex with the K value. For the selected SSB, in the time domain PRACH occasions in the period with (one or more) preambles configured for K PRACH transmissions, the RO for the first PRACH transmission of an attempt has its RO index i as mod(i,K)=0. For example, Fig. 17BThe right part of shows that for 2-PRACH transmission, the UE can start transmission in RO#0 or RO#6. RO#2 and RO#4 do not have a preamble for 2-PRACH transmission.

[0215] In an additional or alternative example, if there are multiple FDM ROs associated with the selected SSB at a time instance, the UE can use the same frequency resources, or hop between frequency domain PRACH resources across PRACH transmissions. The configuration of PRACH frequency hopping, including enabling / disabling frequency hopping, frequency hopping offset in units of PRB or RO, and frequency hopping interval indicating how long the frequency hopping lasts, is configured in SIB1 or predetermined.

[0216]

[0217] Where K represents the number of time-domain PRACHs in one hop, RO start (i) represents the RO index in the frequency domain for the i-th PRACH transmission of an attempt, and F represents the number of ROs for FDM for a specific number of PRACH transmissions associated with the selected SSB.

[0218] For example, suppose Fig. 16B The PRACH configuration index 127, RO offset = 4RO, msg1-FDM = 8. For index 127, K = 2. For 8 PRACH transmissions, the UE alternates between two frequency hopping offsets after two PRACH transmissions.

[0219] In additional or alternative examples, for the hybrid PRACH preamble format "Ax / By", it either cannot be used with multiple PRACH transmissions, or the UE sends multiple PRACH transmissions for Ax.

[0220] In NR up to Rel-17, the available RO is determined by the MAC entity and if the physical layer checks that the PRACH is valid and there is no conflict resulting in PRACH drop, the UE sends the PRACH. UL beam switching time can also be a reason for PRACH drop. One coverage enhancement in Rel-17 is PUSCH repetition based on available slots. DL slots and slots of SSB transmission are not considered as available slots to avoid dropping PUSCH transmissions. However, transmission based on available slots is not suitable for PRACH. First, PRACH time domain resources occur in specific time instances. Second, PRACH conflicts between UEs need to be considered. If a PRACH transmission is dropped, postponing it may increase PRACH conflicts. Unlike PUSCH transmissions where the repetition factor is scheduled by the gNB, the number of PRACH repetitions is determined by the UE if the LTE eMTC rule is reused. In addition to the available slot count, some methods are possible to reduce the impact of PRACH drops.

[0221] In some embodiments, for multiple PRACH transmissions, if a PRACH transmission in an available RO determined by the MAC entity is discarded because the physical layer considers it invalid or due to contention handling, it is not postponed.

[0222] For RedCap UE, if the RO overlaps with a DL reception, it is up to the UE implementation to determine whether to send PRACH.

[0223] For case 8 where valid RO overlaps with dynamic DL reception, it is up to the UE to determine whether to receive the dynamically scheduled DL or send the PRACH.

[0224] For case 8 where the valid RO overlaps with UE-specific configured DL reception (eg, PDCCH in USS, SPS PDSCH, CSI-RS or DLPRS), it is left to the UE implementation to determine whether to receive DL or send PRACH.

[0225] In an additional or alternative embodiment, if the valid RO overlaps with dynamically scheduled or UE-specific configured DL reception and the RedCap UE does not send PRACH in the RO, it is not deferred.

[0226] In some embodiments, if the UE determines that (one or more) PRACH transmissions are to be dropped, it may be configured or predetermined whether the UE is allowed to change its repetition level (which is determined, for example, according to an RSRP threshold). The predetermined method may be that the UE determines based on whether the random access is triggered by the physical layer or a higher layer, whether it is CBRA or CFRA.

[0227] For example, a UE for CBRA is allowed to select a higher repetition factor than the one determined based on the RSRP threshold to make up for some or all of the dropped transmissions. Or, if the UE wants to send four PRACH transmissions, but the last two will be dropped. It can therefore select a lower repetition factor of 2, which has similar performance but with shorter latency. How to balance between latency and repetition factor depends on the UE implementation. However, even if the determined repetition factor and changes depend on the UE implementation, it is beneficial for the gNB to know that the UE can change the repetition level because it can determine the number of Msg3 repetitions based on the repetition level of the PRACH. Additionally, for some delay-sensitive trigger events, such as CFRA for HO or beam failure recovery, a UE-determined repetition level upgrade is not desirable.

[0228] For NB-IoT and LTE eMTC, multiple PRACH transmissions of an attempt have the same transmit power based on the same path loss estimate. However, if multiple NRPRACH transmissions span a long time or the radio channel changes very quickly, the UE may update the higher layer filtered RSRP multiple times depending on its filter input rate and PRACH transmit power. Changes in PRACH transmit power can affect the TPC commands in the RAR.

[0229] In some embodiments, it may be predetermined or configured whether the UE is allowed to change the PRACH transmit power among multiple PRACH transmissions in an attempt.

[0230] When the gNB receives multiple repetitions of the same random access preamble from the UE, it can perform coherent combining or non-coherent combining. Coherent combining means that the gNB combines the repetitions of the RACH preamble and processes the combined signal without calculating the modulus value. With non-coherent combining, the gNB estimates each repetition independently and then adds the modulus values ​​of each repetition.

[0231] Fig.18 An example of a coherent combination between repetitions is illustrated.

[0232] Fig.19 An example of incoherent combinations between repetitions is illustrated.

[0233] For coherent combining, in cases where the UE does not guarantee phase continuity across PRACH repetitions, the gNB has to align the phases of all received PRACH repetitions by phase compensation before combining them. This will increase the gNB implementation complexity. If the UE maintains phase continuity across some PRACH repetitions, the gNB can coherently combine them without phase pre-compensation. The output sequence of the coherent combination can be treated as one detected PRACH sequence and non-coherently combined with the repetitions for which the UE cannot maintain the same phase. It is possible for the UE to maintain phase continuity between PRACH repetitions, especially when the corresponding ROs are continuous in time.

[0234] Some occurrences of violating the phase continuity agreed upon for Rel-17 DMRS bundling can be reused for multiple PRACH transmissions, including a gap of at least 14 symbols between two PUSCH transmissions. In addition, some other approaches can be considered.

[0235] In some embodiments, the gNB determines whether some / all PRACH transmissions from a UE are phase-aligned in one or more of the following ways. In some examples, the gNB determines whether some / all PRACH transmissions from a UE are phase-aligned based on an explicit or implicit indication protected by a preamble sequence. This may be used if the actual cell radius is smaller than the maximum cell radius designed for the PRACH format.

[0236] In an additional or alternative example, the gNB determines whether some / all PRACH transmissions from the UE are phase-aligned based on specific preambles configured for different levels of PRACH phase continuity. For example, preambles #0-9 are configured for phase continuity between 2 PRACH repetitions, and preambles #10-19 are configured for phase continuity between 4 PRACH repetitions. In addition, if all preambles #0-19 are associated with a total of 4 PRACH repetitions according to SIB1, the transmission of preambles #0-9 indicates that the UE can switch beams after the first two PRACH transmissions, and the phase can change after the beam switch.

[0237] In an additional or alternative example, the gNB determines whether some / all PRACH transmissions from a UE are phase consistent based on the following: For a UE transmitting multiple PRACHs, support of phase continuity is mandatory unless a violation event occurs. Alternatively, if it is an optional UE capability, the UE implicitly indicates its capability through the first PRACH transmission.

[0238] In some embodiments, it may be predetermined whether the UE is applied to adjust the TA between multiple PRACH transmissions utilizing the same beam.

[0239] Embodiments associated with multiple PRACH transmissions utilizing different beams are described below.

[0240] In some embodiments, the UE may inform the gNB (e.g., implicitly through a specific preamble) whether a different Tx beam will be used for PRACH transmission. Otherwise, the gNB assumes that the same Tx beam is used. In additional or alternative embodiments, the same Tx beam or different Tx beams is determined by the beam correspondence capability of the UE. For example, if the capability beamCorrespondenceWithoutUL-BeamSweeping is supported in the UE, it transmits PRACH using the same Tx beam.

[0241] In an additional or alternative embodiment, the UE wants network assistance to reduce the beam refinement time and therefore transmits multiple beams, which potentially increases the received power at the gNB. In this case, the number of Tx beams can be decided by the network via the SIB. The UE can select the Tx beam based on the received SSB RSRP, for example, if the gNB allows PRACH transmission with two Tx beams according to the SIB configuration, and the UE has a higher SSB RSRP received by two panels, but does not have a higher SSB RSRP received by the other panel, then the UE can transmit one beam on each of the two panels.

[0242] In additional or alternative embodiments, the number of PRACH transmissions is determined based on the number of Tx beams of the UE.

[0243] For example, if the UE determines this value based on the RSRP measurement of the SSB and the configured threshold, it will transmit multiple PRACHs using each of its Tx beams. In another example, the number of PRACH transmissions is equal to the number of its Tx beams, so that each PRACH is transmitted in a different beam. In some such embodiments, the network may indicate the number of repetitions that the UE should use when transmitting PRACH, which may be considered as a candidate number of repetitions. If the number of different Tx beams that the UE can transmit is less than the indicated or "candidate" number of repetitions, the UE may transmit a number of PRACHs equal to the number of different Tx beams and not transmit the remaining PRACHs in the candidate number of repetitions indicated by the network.

[0244] There are 64 preambles in one PRACH transmission opportunity. The network can detect 64 PRACHs sent in the same time-frequency PRACH opportunity. To keep it simple, we only consider preambles with the same root sequence but different cyclic shifts. For the unrestricted set, if N CS=2, then the short sequence PRACH can have 64 cyclic shifts, which are determined by C v =vN CS (v = 0, 1, ... 63) and a root index. For a single PRACH transmission, 64 simultaneously transmitted PRACHs are received by the gNB and fall into the corresponding non-overlapping time domain search window. N CS Indicated by the gNB via zeroCorrelationZoneConfig based on the UL delay spread of the channel for a single PRACH transmission.

[0245] If the UE transmits PRACH with different Tx beams, if some Tx beams are not well aligned with the gNB, or different TAs are applied to different Tx beams, the delay spread of multiple PRACH transmissions with different Tx beams may be larger than the delay spread configured by the gNB for a single PRACH transmission. Fig. 20 In the example above, the UE sends a preamble with v=0 in three ROs using different beams. The second PRACH transmission arrives with a longer delay than the first but still falls in the correct search window. The third transmission has an even longer delay than the configured Ncs and falls in another window and will be erroneously detected as a preamble v=1. To avoid false detections, the UE may have to restrict its Tx beams with fewer degrees of freedom so that they can all utilize the N-based search window. CS A search window of N is received. However, it is difficult for the UE to determine the angle range. Therefore, in some embodiments, N CS Configured for multiple PRACH transmissions using different Tx beams, which is faster than the conventional N for single PRACH transmission. CS Bigger.

[0246] In a separate RO, the logical root sequence index obtained from the higher layer parameter prach-RootSequenceIndex or rootSequenceIndex-BFR can be used with the new N CS It is applied in combination to PRACH transmission using different Tx beams. However, in the case of shared RO, the logical root sequence index needs to be considered.

[0247] In additional or alternative embodiments, in the case of different N CS In the case of a shared RO of the preamble, with a new N CS The logical root sequence index of the first preamble code can be one or more of the following.

[0248] In some examples, the logical root sequence index is configured separately in SIB1, or determined by a configured offset relative to prach-RootSequenceIndex or rootSequenceIndex-BFR.

[0249] In an additional or alternative example, the logical root sequence index is equal to (offset + with the traditional N CS The maximum logical root sequence index of the leading code of L is obtained according to the circular order according to the traditional rules, that is, the logical index 0 is in L RA =839 is continuous with 837 and at L RA = 139 is continuous with 137, regardless of whether the maximum logical root sequence index can still generate a new N CS The default offset can be 1.

[0250] In an additional or alternative example, the logical root sequence index is similar to that with the traditional N CS If the maximum logical root sequence index is the same as the maximum logical root sequence index of the preamble, the remaining preambles can still be generated with a new N CS The leading code is

[0251] The UL beam switching time is required by the UE to perform Tx beam switching, especially switching across the UE panel. Fig. 16B The PRACH configuration index 127 in FR2 TDD is shown with a gap of two symbols between two PRACH opportunities in two consecutive PRACH time slots. In some embodiments, if the beam switching time is greater than the gap, the UE may not be ready to transmit in the second PRACH opportunity with a different beam, and therefore it transmits PRACH in the PRACH opportunity without changing the beam. Otherwise, in some embodiments, determining the number of PRACH transmissions actually sent by the UE includes determining the number of PRACH transmissions based on the UL beam switching time and the amount of time between the PRACH opportunities, such that the time between any two consecutive transmissions is greater than the beam switching time.

[0252] In some embodiments, the PRACH opportunity is determined using one or more of the following approaches.

[0253] In some examples, the UE selects an SSB taking into account its beam switching time so that multiple PRACH transmissions using different Tx beams in the RO associated with the selected SSB can be sent without new discarding rules (such as UE autonomous discarding).

[0254] Since the determination of SSB depends on the UE implementation, if the UE wants to switch Tx beams within or across panels, it can estimate whether the gap of RO for the selected SSB is sufficient for beam switching. In case the beam switching time is greater than the gap of RO, it can select Tx beams transmitted from a single panel, or select different SSBs or less number of repetitions so that the beam switching time will be less than the gap of RO, in another example, the UE can activate different panels before doing beam switching, which can reduce the beam switching time and thus the beam switching time is less than the gap of RO. It all depends on the UE implementation or its own decision. From the perspective of gNB and standards, the UE should not drop PRACH transmission due to its own reasons (such as when the beam switching time is greater than the gap of RO), which is unknown to the gNB and thus affects the detection rate.

[0255] If the UE can send multiple PRACHs associated with multiple SSBs, the selection of multiple SSBs follows the same rules.

[0256] In an additional or alternative example, the network may select a PRACH configuration index where the gap between consecutive PRACH ROs will be larger than the maximum UE beam switching time so that no UE autonomous discarding will occur in different PRACH beam transmissions.

[0257] In an additional or alternative example, the MAC entity may take into account the possible occurrence of UL beam switching time when determining the next available PRACH opportunity.

[0258] In an additional or alternative example, the MAC entity does not consider the UL beam switching time when determining the next available PRACH opportunity. A PRACH opportunity is valid if it starts at least N symbols after the last symbol of the PRACH opportunity corresponding to the previous PRACH transmission. N represents the UL beam switching time. It can be predetermined whether a PRACH transmission in a PRACH opportunity that is considered invalid by the physical layer can be postponed.

[0259] In an additional or alternative embodiment, if the UL beam switching time of the UE is unknown to the gNB, the gNB may use a predetermined value to determine in which PRACH opportunities to receive PRACH for the UE. The UE reports the time after the RRC connection is established. The UE may report separate beam switching times for multiple PRACH transmissions associated with one SSB and with multiple SSBs.

[0260] In NR up to Rel-17, according to 7.1.1 in 38.213, the transmit power of PRACH depends on the PL b,f,cThe UE determines the PL based on the SS / PBCH blocks associated with the PRACH transmission. b,f,c .

[0261] P PRACH,b,f,c (i) = min{P CMAX,f,c (i),P PRACH,target,f,c +PL b,f,c}[dBm]

[0262] The UE may scan its DL Rx beams received over time for the same SSB index and calculate different DL path loss estimates with different DL Rx beams, which may be used to determine the PRACH UL Tx power and the corresponding UL Tx beam.

[0263] In some embodiments, the PRACH transmit power may be one or more of the following.

[0264] In some examples, the same transmit power is used for all UL Tx beams based on a predetermined / minimum / maximum / average DL path loss estimate. The UE maintains one PREAMBLE_POWER_RAMPING_COUNTER for all UL Tx beams.

[0265] In an additional or alternative example, the PRACH transmit power utilizing a UL Tx beam is based on a DL path loss estimate of the corresponding DL Rx beam.The UE maintains a PREAMBLE_POWER_RAMPING_COUNTER for each UL Tx beam.

[0266] For the transmit power of Msg 1 retransmission, the following existing rules in 38.213 for PRACH retransmission with one UL Tx beam can be reused for different UL Tx beams. If the UE changes the spatial domain transmission filter before PRACH retransmission, Layer 1 notifies higher layers to suspend the power ramp counter.

[0267] Msg1 retransmission may use a different UL Tx beam than the previous attempt. For the second example above, since the UE maintains one power control loop for one UL Tx beam, the above rule may be reused. For example, if beams #0, #1 are used in one attempt, and beams #1, #2 are used for a subsequent attempt, the power ramp counter for beam #1 is incremented by 1, but the power ramp counter for beam #2 is not incremented by 1.

[0268] In the first example above, the specification can be updated as follows. If the UE changes any of the spatial domain transmission filters before PRACH retransmission, Layer 1 notifies the higher layers to suspend the power ramp counter as described in. The UE can determine different timing advance values ​​for different beams, especially for UEs with multiple panels. If the difference in TA values ​​is within the CP, a single TA can be applied to all beams. Otherwise, the UE either discards the use of the UL Tx beam that causes the difference between TAs to be greater than the CP, or the UE can send a PRACH with a different TA.

[0269] In some embodiments, it may be predetermined whether the UE may apply different timing advances for PRACH transmissions utilizing different beams.

[0270] If the UE is power-limited, that is, P PRACH,target,f,c +PL b,f,c ≥P CMAX,f,c (i) Although it transmits PRACH at the same power, it is helpful that the gNB knows which beam has the smallest PL. Further, this may imply that the UE will use the DL Rx beam corresponding to the first PRACH transmission to receive Msg2.

[0271] In some embodiments, the order of different UL Tx beams for multiple PRACH transmissions is determined according to the PL estimates that increase with the corresponding DL Rx beams. Alternatively, the first UL Tx beam corresponds to the DL Rx beam with the smallest PL estimate.

[0272] In some embodiments, the mapping between UL Tx beam and PRACH transmission can be predetermined or configured. One predetermined way is that the UE does not use the same UL Tx beam to send two consecutive PRACHs in the time domain. That is, each PRACH is sent using a unique beam. Another predetermined way is to use the same UL Tx beam across PRACH opportunities in a PRACH slot or consecutive PRACH slots. The UE can switch Tx beams on PRACH opportunities in non-continuous PRACH slots.

[0273] Using the mapping, the gNB can implicitly know the number of UL Tx beams used by the UE. With this knowledge, the gNB can indicate one of the Tx beams for subsequent UL transmissions.

[0274] Embodiments associated with multiple PRACH transmissions utilizing different Tx beams associated with different SSBs are described below.

[0275] In some embodiments, the UE transmits multiple PRACHs using different beams that may be associated with multiple SSBs.

[0276] PRACH transmissions associated with multiple SSBs can bring more spatial diversity gain. On the one hand, the selected SSB may not be the strongest beam due to short-term blocking or other implementation concerns (such as latency). Therefore, if PRACH repetitions are associated with one SSB, although the UE can adjust the UL Tx beams, they may not be ideal beams for the gNB. On the other hand, the received RSRP of two adjacent SSBs is similar, especially in overlapping coverage areas. Therefore, PRACH transmissions associated with different SSBs can bring spatial diversity gain compared to one SSB.

[0277] In some embodiments, whether the UE is allowed to send attempted multiple PRACH transmissions associated with more than one SSB may be configured to the UE (e.g., in SIB1) or predetermined by one or more of the following parameters. These parameters may be SSB-general or SSB-specific. In some examples, an indication of whether the UE is allowed to send PRACH associated with different SSBs. If the gNB makes such a configuration but does not configure a specific number of SSBs with which the PRACH transmission may be associated, it is left to the UE to determine. In an additional or alternative example, the number of selected SSBs with which the PRACH transmission is associated. For example, a value of 2 allows the UE to select two adjacent SSBs. The absence of a parameter or a default value indicates that the PRACH transmission is only allowed to be associated with one SSB. In an additional or alternative example, the maximum number of selected SSBs with which multiple PRACH transmissions are associated.

[0278] In an additional or alternative example, SSB combinations. For example, if the UE is configured with 2 SSBs for PRACH transmission and there are 4 SSBs in the cell, it can be configured with SSB combinations of {SSB#0, SSB1}, {SSB#1, SSB2}, {SSB#2, SSB3}, {SSB#3, SSB#0}. If it is a UE configured with a maximum of 2 SSBs, if the UE selects only one SSB, some additional SSB combinations are {SSB#0, SSB0}, {SSB#1, SSB1}, {SSB#2, SSB2}, {SSB#3, SSB3}. In other words, if the UE has selected the first SSB#X, SSB#Y can be selected such that Y=mod(X-1,N) or Y=mod(X+1,N), where N is the number of SSBs. This assumes that the SSBs sent by the network are spatially adjacent. For the mTRP scenario, the UE selects one SSB from the TRP and the gNB may provide a combination of SSB indices from each TRP.

[0279] If the coverage and UE density is non-uniform across the SSBs of a cell, then per-SSB configuration is beneficial. If the configuration is per-cell, then it applies to all its SSBs.

[0280] Since the RSRP of multiple selected SSBs may be different, the corresponding repetition levels of the SSBs are also different. However, this may increase the gNB combination complexity.

[0281] In some embodiments, it may be predetermined whether different numbers of PRACH transmissions are allowed for different selected SSBs. If the same number of PRACH transmissions is applicable to the selected SSBs, it may be based on the RSRP of the particular SSB and the number of UL Tx beams that the UE will use for PRACH transmissions associated with the SSB.

[0282] For example, the UE may transmit that the UE pairs its antenna panels and SSBs. For the two selected SSBs, the two panels have different numbers of antenna elements and therefore different numbers of UL Tx beams.

[0283] In some embodiments, retransmissions of Msg1 may be associated with the same or different number of SSBs.If the first RACH attempt has a PRACH transmission associated with the same SSB, the next attempt may have a PRACH transmission associated with multiple SSBs.

[0284] In some examples, the UE calculates the path loss based on the "SS block transmit power" and the SS block RSRP. At least as a NW implementation, different SS blocks in an SS burst set may be transmitted with different powers and / or with different Tx beamforming gains. The RMSI only indicates a single transmit power for an SS block in Rel-15.

[0285] In NR, a RACH transmission opportunity is defined as the time-frequency resource on which a PRACH message 1 is sent with a single specific tx beam using the configured PRACH preamble format.

[0286] In some embodiments, if a PRACH transmission is associated with multiple SSBs, the PRACH timing may be determined in one or more of the following options.

[0287] With respect to multiple PRACH transmissions associated with multiple SSBs, in some examples, a PRACH transmission associated with one SSB precedes a PRACH transmission associated with another SSB. In additional or alternative examples, PRACH transmissions associated with different selected SSBs may be interleaved.

[0288] Regarding the determination of the RO for the first PRACH transmission, in some examples, the first PRACH may be associated with the SSB having the strongest RSRP. In an additional or alternative example, the UE determines a PRACH opportunity associated with any one of the selected SSBs.

[0289] These examples can be used in different configurations. Consider that the UE selects SSB#0 and SSB#1 for the RACH procedure. In some examples, one SSB mapped to two ROs is Fig.21A is applied to reduce delay. If SSB#0 has a higher RSRP than SSB#1, then Fig.21A The selected RO according to option a is also shown. However, if SSB#1 has a higher RSRP than SSB#0, the UE first starts with the RO associated with SSB#1 and then starts with the next available RO associated with SSB#0, and these ROs are not consecutive. However, if the UE determines the PRACH opportunity associated with any of the selected SSBs, it can have the following Fig.21A The selected RO is shown.

[0290] In an additional or alternative example, one SSB may be mapped to one RO, such as Fig.21B shown.

[0291] In some embodiments, a preamble associated with one SSB in a RO may be divided into a preamble for PRACH transmission associated with one SSB and a preamble for PRACH transmission associated with multiple SSBs.

[0292] In the example of possible SSB combinations of {SSB#0}, {SSB#1}, {SSB#2}, {SSB#3}, {SSB#0,SSB1}, {SSB#1,SSB2}, {SSB#2,SSB3}, {SSB#3,SSB#0}, different PRACH resources will be configured for {SSB#0}, {SSB#0,SSB1} and {SSB#3,SSB#0} so that the gNB can determine whether the UE will send PRACH repetitions for SSB#0 alone or for SSB#0 with another adjacent SSB.

[0293] In some embodiments, when different preambles in the RO are associated with multiple SSBs and PRACH repetition is enabled, the UE sends one preamble in the RO for one selected SSB. It selects a preamble index offset, which is applied to the starting preamble for the selected SSB.

[0294] Fig. 22ssb-perRACH-OccasionAndCB-PreamblesPerSSB is shown configured as 4, i.e., 4 SSBs have corresponding 4 preambles in RO. If the UE selects offset 0, it can send preamble index #0, 16, 32, 48 for the corresponding SSB (if selected). More generally, the UE selects preamble index i for PRACH repetition 1, so SSBn is the same as preamble index Associatedly, N is the total number of SSBs.

[0295] In additional or alternative embodiments, multiple PRACH transmissions may be ordered such that associated SSBs have decreasing / increasing SSB RSRP or SSB index.

[0296] In some embodiments, the PRACH transmit power is determined in one or more of the following ways.

[0297] In some examples, the UE maintains the same transmit power for all PRACH transmissions, which is independently determined based on the lowest or average PL of the selected SSBs or the PL of the reference SSB (e.g., the SSB with the smallest index). The UE maintains one PREAMBLE_POWER_RAMPING_COUNTER for all UL Tx beams. The reference SSB for path loss estimation can be determined in the same manner as the previous attempt, but using the latest SSB(s) before the PRACH retransmission.

[0298] In an additional or alternative example, the UE maintains the same transmit power for PRACH transmissions associated with the same SSB, which is independently determined based on the RSRP of the received SSB. The UE maintains a PREAMBLE_POWER_RAMPING_COUNTER for each selected SSB. The reference SSB for path loss estimation may be the latest SSB with an index prior to the PRACH transmission associated with the same SSB index. Since the UE maintains a counter for each SSB, the conventional rules may be reused. In some examples, the rules may be updated as follows:

[0299] 1>If all The selected SSB or CSI-RS is not changed from the selection in the last random access preamble transmission:

[0300] This means that as long as one of the SSBs in the set of SSBs used for the retransmission is different from the SSB of the previous attempt, the power ramp counter is not incremented.

[0301] In the following description, although the communication device may be any one of the wireless devices 2512A, 2512B, wired or wireless devices UE 2512C, UE 2512D, UE 2600, virtualized hardware 2904, virtual machines 2908A, 2908B, or UE 3006, UE 2600 (also referred to herein as the communication device 2600) shall be used to describe the functionality of the operation of the communication device. Reference will now be made to some embodiments of the present invention. Fig.23 Flowchart to discuss (using Fig.26 The operation of the communication device 2600 is implemented by the structure of the block diagram. For example, the module can be stored in Fig.26 The modules may be stored in the memory 2610, and these modules may provide instructions, so that when the instructions of the modules are executed by the corresponding communication device processing circuit 2602, the processing circuit 2602 performs the corresponding operations of the flowchart.

[0302] Fig.23 An example of operations performed by a communication device during an RA procedure associated with a network node of a NR communication network is illustrated.

[0303] At block 2310 , the processing circuit 2602 receives an indication of PRACH transmission configuration information from a network node via the communication interface 2612 .

[0304] At block 2320, the processing circuit 2602 determines the rsrp-ThresholdMsg3 threshold based on a flag in the RRC message. In some embodiments, the RRC message is associated with a particular BWP or preamble feature group.

[0305] At block 2330 , the processing circuit 2602 determines information associated with at least one of a communication device and a channel between the communication device and a network node.

[0306] At block 2340, the processing circuit 2602 determines a number of PRACH transmissions to be sent to the network node as part of the RA procedure and based on the information (before receiving the RAR). In some embodiments, determining the information includes: determining an RSRP associated with the channel. Determining the number of PRACH transmissions includes: 1) determining the number of PRACH transmissions based on a comparison of the RSRP with a predetermined threshold; 2) determining that a repetition procedure is applicable to Msg3 transmissions based on the RSRP and the threshold; and 3) repeating the Msg3 transmission by at least the number indicated in the random access response.

[0307] In additional or alternative embodiments, determining the information includes determining a power headroom for the communication device.Determining the number of PRACH transmissions includes determining the number of PRACH transmissions based on a comparison of an amount of power required for the PRACH transmissions and the power headroom.

[0308] In additional or alternative embodiments, determining the number of PRACH transmissions to send to the network node includes: receiving an indication of a number of candidates for PRACH transmissions; and determining the number of PRACH transmissions as the lesser of the number of candidates and the number of different Tx beams that the communication device can use for the PRACH transmissions.

[0309] In an additional or alternative embodiment, determining the number of PRACH transmissions includes determining the number of PRACH transmissions based on an uplink UL beam switching time and an amount of time between PRACH opportunities such that a time between any two consecutive transmissions is greater than the beam switching time.

[0310] At block 2345, the processing circuit 2602 determines a periodicity associated with the PRACH transmission based on the association period.

[0311] At block 2350, processing circuit 2602 sends the number of PRACH transmissions to the network node via communication interface 2612. In some embodiments, sending the number of PRACH transmissions includes sending a plurality of different preambles across a plurality of ROs associated with a SSB associated with a portion of the PRACH transmissions.

[0312] In an additional or alternative embodiment, the number of PRACH transmissions includes at least two PRACH transmissions. Sending the number of PRACH transmissions includes: 1) sending a first PRACH transmission of the at least two PRACH transmissions at a first RO in the plurality of ROs using a first preamble based on a position of a preamble group associated with the first PRACH transmission within the first RO; and 2) sending a second PRACH transmission of the at least two PRACH transmissions at a second RO in the plurality of ROs using a second preamble based on a position of a preamble group associated with the second PRACH transmission within the second RO.

[0313] In additional or alternative embodiments, the number of PRACH transmissions includes at least two PRACH transmissions each associated with a different uplink UL transmission Tx beam.Sending the number of PRACH transmissions includes sending the at least two PRACH transmissions using different UL Tx beams.

[0314] In an additional or alternative embodiment, the number of PRACH transmissions includes at least two PRACH transmissions. Sending the number of PRACH transmissions includes: 1) sending a first PRACH transmission of the at least two PRACH transmissions using a first preamble index; 2) determining a second preamble index based on the first preamble index and an offset (e.g., a logical index or a cyclic shift of a root sequence); and 3) sending a second PRACH transmission of the at least two PRACH transmissions using the second preamble index.

[0315] In an additional or alternative embodiment, the number of PRACH transmissions includes at least two PRACH transmissions each associated with a different transmit power. Sending the number of PRACH transmissions includes: 1) sending the at least two PRACH transmissions using different transmit powers; 2) determining each of the different transmit powers based on at least one of the corresponding path loss values; and 3) determining the different transmit powers based on different values ​​of a power ramp counter.

[0316] In additional or alternative embodiments, the number of PRACH transmissions includes at least two PRACH transmissions each associated with a different timing advance TA.Sending the number of PRACH transmissions includes sending the at least two PRACH transmissions using different TAs.

[0317] In additional or alternative embodiments, the number of PRACH transmissions includes at least two PRACH transmissions.Sending the number of PRACH transmissions includes sending the at least two PRACH transmissions in an order based on a path loss associated with each of the at least two PRACH transmissions.

[0318] In an additional or alternative embodiment, the number of PRACH transmissions includes at least two PRACH transmissions each associated with a different synchronization signal block SSB. Sending the number of PRACH transmissions includes: sending at least two PRACH transmissions using U1Tx beams associated with different SSBs.

[0319] In additional or alternative embodiments, sending the number of PRACH transmissions includes sending an indication that the communications device will send at least two PRACH transmissions using different UL TX beams.

[0320] In an additional or alternative embodiment, the number of PRACH transmissions includes at least two PRACH transmissions. Sending the number of PRACH transmissions includes: sending a first PRACH transmission of the at least two PRACH transmissions using a first preamble index; determining a second preamble index by applying the same offset between the first preamble index and a starting preamble index configured for multiple PRACH transmissions in the first RO to a starting preamble index configured for multiple PRACH transmissions in the second RO; and sending a second PRACH transmission of the at least two PRACH transmissions using the second preamble index.

[0321] In some embodiments, sending the number of PRACH transmissions comprises sending the number of PRACH transmissions with periodicity. In additional or alternative embodiments, sending the number of PRACH transmissions with periodicity comprises sending the number of PRACH transmissions during a time period equal to one or more association periods.

[0322] In additional or alternative embodiments, sending the number of PRACH transmissions includes sending the number of PRACH transmissions during a time period starting from a resource opportunity RO index i defined as mod(I,K)=0, where K is the number of PRACH transmissions.

[0323] In additional or alternative embodiments, for a time instance associated with the number of PRACH transmissions, there are a plurality of frequency division multiplexing FDM resource opportunities RO associated with the selected synchronization signal block SSB. In some examples, sending the number of PRACH transmissions includes: based on the number of FDM ROs configured for the number of PRACH transmissions associated with the selected SSB, hopping between the plurality of FDM ROs across the number of PRACH transmissions.

[0324] In an additional or alternative embodiment, sending the number of PRACH transmissions includes: RO index RO in the frequency domain defined by start (i) sends the i-th PRACH transmission among the number of PRACH transmissions:

[0325]

[0326] Wherein K represents the number of time-domain PRACH opportunities of one hop, and F represents the number of ROs of FDM used for the number of PRACH transmissions.

[0327] In an additional or alternative embodiment, sending the number of PRACH transmissions includes: sending a first PRACH transmission of the number of PRACH transmissions; after sending the first PRACH transmission, determining that the first PRACH transmission is discarded; and in response to determining that the first PRACH transmission is discarded, sending all remaining PRACH transmissions of the number of PRACH transmissions.

[0328] At block 2360, processing circuit 2602 determines that the RAR has not been received. At block 2370, processing circuit 2602 determines at least one of a number of PRACH retransmissions and a transmit power for the PRACH retransmissions based on network configured parameters. At block 2380, processing circuit 2602 sends a number of PRACH retransmissions via communication interface 2612.

[0329] From Fig.23 Various operations of the flowcharts of may be optional for some embodiments of the communication device and related methods. In some examples, Fig.23 Boxes 2310, 2320, 2360, 2370, and 2380 may be optional.

[0330] In the following description, although the network node may be any one of the network nodes 2510A, 2510B, the core network node 2508, the network node 2700, the virtualized hardware 2904, the virtual machine 2908A, 2908B, or the network node 3004, the network node 2700 should be used to describe the functionality of the operation of the network node. Fig.24 Flowchart to discuss (using Fig. 27 The operation of the network node 2700 is implemented by the structure of the block diagram. For example, the module can be stored in Fig. 27 The modules are stored in the memory 2704, and these modules can provide instructions, so that when the instructions of the modules are executed by the corresponding network node processing circuit 2702, the processing circuit 2702 performs the corresponding operations of the flowchart.

[0331] Fig.24 An example of operations performed by a network node of a NR communication network during a RA procedure associated with a communication device is illustrated.

[0332] At block 2410 , the processing circuit 2702 sends an indication of PRACH transmission configuration information to the communications device via the communications interface 2706 .

[0333] At block 2420 , the processing circuit 2702 sends, via the communication interface 2706 , an indication of the rsrp-ThresholdMsg3 threshold via a flag in an RRC message.

[0334] At block 2430 , the processing circuit 2702 determines information associated with at least one of a communication device and a channel between the communication device and a network node.

[0335] At block 2440, the processing circuit 2702 determines a number of PRACH transmissions to be received from the communication device as part of the RA procedure based on the information. In some embodiments, determining the information includes determining an RSRP associated with the channel. Determining the number of PRACH transmissions includes determining the number of PRACH transmissions based on a comparison of the RSRP with a predetermined threshold.

[0336] In additional or alternative embodiments, determining the information includes determining a power headroom for the communication device.Determining the number of PRACH transmissions includes determining the number of PRACH transmissions based on a comparison of an amount of power required for the number of PRACH transmissions and the power headroom.

[0337] At block 2450, the processing circuit 2702 monitors the NR communication network for the number of PRACH transmissions from the communication device via the communication interface 2706. In some embodiments, monitoring the NR communication network for the number of PRACH transmissions includes monitoring the NR communication network for a plurality of different preambles spanning a plurality of RA channel opportunities RO associated with a synchronization signal block associated with a portion of the PRACH transmissions.

[0338] In an additional or alternative embodiment, the number of PRACH transmissions includes at least two PRACH transmissions each associated with a different uplink UL transmission Tx beam. Monitoring the NR communication network for the number of PRACH transmissions includes: monitoring the NR communication network for at least two PRACH transmissions via different UL Tx beams.

[0339] In additional or alternative embodiments, the number of PRACH transmissions includes at least two PRACH transmissions each associated with a different transmit power. Monitoring the NR communication network includes monitoring the NR communication network for at least two PRACH transmissions using different transmit powers.

[0340] In an additional or alternative embodiment, the number of PRACH transmissions includes at least two PRACH transmissions each associated with a different timing advance TA. Monitoring the NR communication network includes monitoring the NR communication network for at least two PRACH transmissions using different TAs.

[0341] In additional or alternative embodiments, the number of PRACH transmissions includes at least two PRACH transmissions. Monitoring the NR communication network includes monitoring the NR communication network for the at least two PRACH transmissions in an order based on a path loss associated with each of the at least two PRACH transmissions.

[0342] In an additional or alternative embodiment, the number of PRACH transmissions includes at least two PRACH transmissions each associated with a different synchronization signal beam SSB. Monitoring the NR communication network includes: monitoring the NR communication network for at least two PRACH transmissions using different SSBs.

[0343] At block 2460, the processing circuit 2702 determines that a PRACH transmission has not been received.

[0344] At block 2470 , the processing circuit 2702 monitors the NR communications network via the communications interface 2706 for a number of PRACH retransmissions based on a network configured parameter.

[0345] From Fig.24Various operations of the flowcharts of may be optional for some embodiments of network entities and related methods. In some examples, Fig.24 Boxes 2410, 2420, 2460, and 2470 may be optional.

[0346] Fig.25 An example of a communication system 2500 is shown in accordance with some embodiments.

[0347] In this example, the communication system 2500 includes a telecommunications network 2502 including an access network 2504 such as a radio access network (RAN) and a core network 2506 including one or more core network nodes 2508. The access network 2504 includes one or more access network nodes, such as network nodes 2510a and 2510b (one or more of which may be generally referred to as network nodes 2510), or any other similar third generation partnership project (3GPP) access nodes or non-3GPP access points. The network nodes 2510 facilitate direct or indirect connection of user equipment (UE), such as by connecting UE 2512a, 2512b, 2512c, and 2512d (one or more of which may be generally referred to as UE 2512) to the core network 2506 via one or more wireless connections.

[0348] Example wireless communications over wireless connections include sending and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transferring information without the use of wires, cables, or other material conductors. In addition, in different embodiments, the communication system 2500 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 a wired or wireless connection. The communication system 2500 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar types of systems.

[0349] UE 2512 may be any of a variety of communication devices, including wireless devices that are arranged, configured and / or operable to communicate wirelessly with network node 2510 and other communication devices. Similarly, network node 2510 is arranged, capable, configured and / or operable to communicate directly or indirectly with UE 2512 and / or with other network nodes or devices in telecommunication network 2502 to enable and / or provide network access (such as wireless network access) and / or perform other functions (such as management in telecommunication network 2502).

[0350] In the depicted example, core network 2506 connects network node 2510 to one or more hosts, such as host 2516. These connections may be direct or indirect connections via one or more intermediate networks or devices. In other examples, the network node may be directly coupled to the host. Core network 2506 includes one or more core network nodes (e.g., core network node 2508) constructed with hardware and software components. The features of these components may be substantially similar to those described with respect to UE, network nodes, and / or hosts, so that their descriptions are generally applicable to the corresponding components of core network node 2508. Example core network nodes include one or more functions of a mobile switching center (MSC), a mobility management entity (MME), a home subscriber server (HSS), an access and mobility management function (AMF), a session management function (SMF), an authentication server function (AUSF), a subscription identifier de-hiding function (SIDF), a unified data management (UDM), a security edge protection agent (SEPP), a network open function (NEF), and / or a user plane function (UPF).

[0351] The host 2516 may be under the ownership or control of a service provider other than the operator or provider of the access network 2504 and / or the telecommunications network 2502, and may be operated by or on behalf of the service provider. The host 2516 may host various applications to provide one or more services. Examples of such applications include real-time and pre-recorded audio / video content, data collection services (such as retrieving and editing data about various environmental conditions detected by multiple UEs), analysis functions, social media, functions for controlling or otherwise interacting with remote devices, functions for alarm and monitoring centers, or any other such functions performed by a server.

[0352] As a whole, Fig.25 The communication system 2500 enables connections between UEs, network nodes, and hosts. In this sense, the communication system can be configured to operate according to predefined rules or procedures such as specific standards, including but 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 standards (e.g., 6G); Wireless Local Area Network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard (WiFi); and / or any other appropriate wireless communication standards, such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC), ZigBee, LiFi, and / or any low power wide area network (LPWAN) standards such as LoRa and Sigfox.

[0353] In some examples, telecommunication network 2502 is a cellular network implementing 3GPP standardized features. Thus, telecommunication network 2502 can support network slicing to provide different logical networks to different devices connected to telecommunication network 2502. For example, telecommunication network 2502 can provide ultra-reliable low-latency communication (URLLC) services to some UEs, while providing enhanced mobile broadband (eMBB) services to other UEs, and / or providing massive machine type communication (mMTC) / massive IoT services to additional UEs.

[0354] In some examples, UE 2512 is configured to send and / or receive information without direct human interaction. For example, when triggered by an internal or external event, or in response to a request from access network 2504, the UE can be designed to send information to access network 2504 according to a predetermined schedule. Additionally, the UE can be configured to operate in a single RAT or multi-RAT or multi-standard mode. For example, the UE can operate using any one or a combination of Wi-Fi, NR (New Radio), and LTE, i.e., configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) New Radio-Dual Connectivity (EN-DC).

[0355] In this example, hub 2514 communicates with access network 2504 to facilitate indirect communication between one or more UEs (e.g., UE 2512c and / or 2512d) and a network node (e.g., network node 2510b). In some examples, hub 2514 can be a controller, a router, a content source, and analysis, or any of the other communication devices described herein with respect to the UE. For example, hub 2514 can be a broadband router that enables the UE to access core network 2506. As another example, hub 2514 can be a controller that sends commands or instructions to one or more actuators in the UE. The commands or instructions can be received from the UE, the network node 2510, or received through executable code, scripts, processes, or other instructions in hub 2514. As another example, hub 2514 can be a data collector that acts as a temporary storage device for UE data, and in some embodiments, analysis or other processing of the data can be performed. As another example, hub 2514 can be a content source. For example, for a UE that is a VR headset, display, speaker, or other media delivery device, the hub 2514 can retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, and then the hub 2514 provides it to the UE directly, after performing local processing, and / or after adding additional local content. In another example, the hub 2514 acts as a proxy server or coordinator for the UE, particularly when one or more of the UEs are low-energy IoT devices.

[0356] Hub 2514 can have a constant / persistent or intermittent connection to network node 2510b. Hub 2514 can also allow different communication schemes and / or scheduling between hub 2514 and UE (e.g., UE 2512c and / or 2512d) and between hub 2514 and core network 2506. In other examples, hub 2514 is connected to core network 2506 and / or one or more UEs via a wired connection. In addition, hub 2514 can be configured to be connected to an M2M service provider and / or to another UE via a direct connection via access network 2504. In some scenarios, a UE can establish a wireless connection with network node 2510 while still being connected via hub 2514 via a wired or wireless connection. In some embodiments, hub 2514 can be a dedicated hub, that is, its main function is to route communications from network node 2510b to UE / from UE to network node 2510b. In other embodiments, hub 2514 may be a non-dedicated hub, that is, a device that is operable to route communications between UEs and network node 2510b, but is also capable of operating as a communications origin and / or endpoint for certain data channels.

[0357] Fig.26UE 2600 according to some embodiments is shown. As used herein, UE refers to a device capable of, configured, arranged and / or operable to wirelessly communicate with a network node and / or other UEs. Examples of UEs include, but are not limited to, smart phones, mobile phones, cellular phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablet computers, laptops, laptop embedded devices (LEEs), laptop mounted devices (LMEs), smart devices, wireless customer premises equipment (CPEs), vehicle-mounted or vehicle embedded / integrated wireless devices, etc. Other examples include any UE identified by the Third Generation Partnership Project (3GPP), including narrowband Internet of Things (NB-IoT) UEs, machine type communications (MTC) UEs, and / or enhanced MTC (eMTC) UEs.

[0358] The UE may support device-to-device (D2D) communications, for example by implementing 3GPP standards for sidelink communications, dedicated short-range communications (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, the UE may not necessarily have a user in the sense of a human user owning and / or operating the associated device. Instead, the UE may represent a device that is intended to be sold to or operated by a human user, but the device may not be associated with a particular human user, or may not initially be associated with that particular human user (e.g., a smart sprinkler controller). Alternatively, the UE may represent a device that is not intended to be sold to or operated by an end user, but the device may be associated with a user or operated for the benefit of a user (e.g., a smart meter).

[0359] UE 2600 includes a processing circuit 2602, which is operably coupled to an input / output interface 2606, a power supply 2608, a memory 2610, a communication interface 2612, and / or any other components, or any combination thereof, via a bus 2604. Some UEs may utilize Fig.26 All or a subset of the components shown in . The level of integration between components may vary from one UE to another UE. In addition, some UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0360] The processing circuit 2602 is configured to process instructions and data, and may be configured to implement any sequential state machine operable to execute instructions stored in the memory 2610 as a machine-readable computer program. The processing circuit 2602 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 and appropriate firmware; one or more stored computer programs, general-purpose processors such as microprocessors or digital signal processors (DSPs), and appropriate software; or any combination of the above. For example, the processing circuit 2602 may include multiple central processing units (CPUs).

[0361] In this example, the input / output interface 2606 can be configured to provide one or more interfaces to an input device, an output device, or one or more input and / or output devices. Examples of output devices include speakers, sound cards, video cards, displays, monitors, printers, actuators, transmitters, smart cards, another output device, or any combination thereof. An input device can allow a user to capture information into the UE 2600. Examples of input devices include touch-sensitive or presence-sensitive displays, cameras (e.g., digital cameras, digital video cameras, web cameras, etc.), microphones, sensors, mice, trackballs, direction pads, trackpads, rollers, smart cards, etc. The presence-sensitive display can include a capacitive or resistive touch sensor to sense input from a user. The sensor can be, for example, 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 can use an interface port of the same type as an input device. For example, a universal serial bus (USB) port can be used to provide input devices and output devices.

[0362] In some embodiments, the power supply 2608 is configured as a battery or a battery pack. Other types of power supplies may be used, such as an external power supply (e.g., an electrical socket), a photovoltaic device, or a power battery. The power supply 2608 may also include a power circuit for delivering power from the power supply 2608 itself and / or an external power supply to various parts of the UE 2600 via an input circuit or an interface such as a power cable. The delivered power may be used, for example, to charge the power supply 2608. The power circuit may perform any formatting, conversion, or other modification to the power from the power supply 2608 so that the power is suitable for various components of the UE 2600 to which the power is supplied.

[0363] The memory 2610 may be or be configured to include a memory such as a random access memory (RAM), a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic disk, an optical disk, a hard disk, a removable tape cartridge, a flash drive, etc. In one example, the memory 2610 includes one or more application programs 2614, such as an operating system, a web browser application, a widget, a gadget engine, or other application, and corresponding data 2616. The memory 2610 may store any of a variety of operating systems or a combination of operating systems for use by the UE 2600.

[0364] The memory 2610 may be configured to include a plurality of physical drive units, such as a redundant array of independent disks (RAID), a flash memory, a USB flash drive, an external hard drive, a thumb drive, a pen drive, a key drive, a high-density digital versatile disk (HD-DVD) optical drive, an internal hard drive, a Blu-ray optical drive, a holographic digital data storage (HDDS) optical drive, an external mini dual in-line memory module (DIMM), a synchronous dynamic random access memory (SDRAM), an external micro DIMM SDRAM, a smart card memory (such as a tamper-proof module in the form of a universal integrated circuit card (UICC), including one or more user identity modules (SIMs), such as USIM and / or ISIM), other memories, or any combination thereof. The UICC may be, for example, an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC commonly referred to as a “SIM card”. The memory 2610 may allow the UE 2600 to access instructions, applications, etc. stored on a temporary or non-temporary storage medium to offload data or upload data. An article of manufacture, such as an article of manufacture utilizing a communication system, may be tangibly embodied as or in memory 2610, which may be or include a device-readable storage medium.

[0365] The processing circuit 2602 may be configured to communicate with an access network or other network using a communication interface 2612. The communication interface 2612 may include one or more communication subsystems and may include an antenna 2622 or be communicatively coupled to the antenna 2622. The communication interface 2612 may include one or more transceivers for communication, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or network node in the access network). Each transceiver may include a transmitter 2618 and / or a receiver 2620 suitable for providing network communications (e.g., optical, electrical, frequency allocation, etc.). In addition, the transmitter 2618 and the receiver 2620 may be coupled to one or more antennas (e.g., antenna 2622) and may share circuit components, software or firmware, or may be implemented separately alternatively.

[0366] In the illustrated embodiment, the communication functionality of the communication interface 2612 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near field communication, location-based communication such as using a global positioning system (GPS) to determine location, another similar communication functionality, or any combination thereof. Communication may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, code division multiple 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 the like.

[0367] Regardless of the type of sensor, the UE may provide an output of data captured by its sensor via a wireless connection to a network node through its communication interface 2612. The data captured by the UE's sensor may be transmitted to the network node via another UE via a wireless connection. The output may be periodic (e.g., every 15 minutes if it reports a sensed temperature), random (e.g., in order to load balance reports from multiple sensors), in response to a trigger event (e.g., sending an alarm when moisture is detected), in response to a request (e.g., a user-initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0368] As another example, the UE includes an actuator, motor, or switch associated with a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input, the state of the actuator, motor, or switch can change. For example, the UE can include a motor that adjusts a control surface or rotor of a drone in flight based on the received input, or adjusts a robotic arm performing a medical procedure based on the received input.

[0369] When in the form of an Internet of Things (IoT) device, a UE may be a device used in one or more application areas including, but not limited to, urban wearable technology, extended industrial applications, and healthcare. Non-limiting examples of such IoT devices are the following devices or devices embedded in the following devices: a connected refrigerator or freezer, a television, connected lighting, an electric meter, a robotic vacuum cleaner, a voice-activated smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / humidity sensor, an electric door lock, a connected doorbell, an air conditioning system (such as 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 device for tactile enhancement or sensory enhancement, a sprinkler, an animal or item tracking device, a sensor for monitoring plants or animals, an industrial robot, an unmanned aerial vehicle (UAV), and any kind of medical device (such as a heart rate monitor or a remotely controlled surgical robot). In addition to the description of Fig.26 In addition to the other components described for the UE 2600 shown in FIG. 2 , a UE in the form of an IoT device includes circuitry and / or software depending on the intended application of the IoT device.

[0370] As another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and / or measurement and sends the results of such monitoring and / or measurement to another UE and / or a network node. In this case, the UE may be an M2M device, which may be referred to as an MTC device in the 3GPP context. As a specific example, a UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, bus, truck, ship, and airplane, or other device that is capable of monitoring and / or reporting its operating status or capable of performing other functions associated with its operation.

[0371] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE may be or be integrated into a drone and provide the drone's speed information (obtained via a speed sensor) to a second UE that is a remote controller for 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 speed of the drone. The first and / or second UE may also include more than one of the above functions. For example, the UE may include a sensor and an actuator and handle the communication of data for the speed sensor and the actuator.

[0372] Fig. 27 A network node 2700 according to some embodiments is shown. As used herein, a network node refers to a device capable of, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or other network nodes or devices in a telecommunications 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 NRNodeBs (gNBs)).

[0373] Base stations may be classified based on the amount of coverage they provide (or, stated differently, based on their transmit power level), and thus may be referred to as a femto base station, a pico base station, a micro base station, or a macro base station, depending on the amount of coverage provided. A base station may be a relay node or a relay donor node that controls a relay. A network node may also include one or more (or all) parts of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU), which is sometimes referred to as a remote radio head (RRH). Such a remote radio unit may or may not be integrated with an antenna as an antenna-integrated radio. Portions of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0374] Other examples of network nodes include a multi-transmission point (multi-TRP) 5G access node, a multi-standard radio (MSR) device such as an MSR BS, a network controller such as a radio network controller (RNC) or a base station controller (BSC), a base transceiver station (BTS), a transmission point, a transmission node, a multi-cell / multicast coordination entity (MCE), an operation and maintenance (O&M) node, an operation support system (OSS) node, a self-organizing network (SON) node, a positioning node (e.g., an evolved serving mobile positioning center (E-SMLC)) and / or a minimization of drive tests (MDT).

[0375] The network node 2700 includes a processing circuit 2702, a memory 2704, a communication interface 2706, and a power supply 2708. The network node 2700 may be composed of multiple physically separated components (e.g., a NodeB component and an RNC component, or a BTS component and a BSC component, etc.), each of which may have its own corresponding components. In certain scenarios where the network node 2700 includes multiple separated components (e.g., BTS and BSC components), one or more of the separated components may be shared between several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair may be considered as a single separated network node in some cases. In some embodiments, the network node 2700 may be configured to support multiple radio access technologies (RATs). In such an embodiment, some components may be repeated (e.g., separate memories 2704 for different RATs), and some components may be reused (e.g., the same antenna 2710 may be shared by different RATs). The network node 2700 may also include multiple sets of various illustrated components for different wireless technologies, such as GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, radio frequency identification (RFID), or Bluetooth wireless technologies, integrated into the network node 2700. These wireless technologies may be integrated into the same or different chips or chipsets and other components within the network node 2700.

[0376] The processing circuit 2702 may include a combination of one or more of a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic that is operable to provide the functionality of the network node 2700 alone or in conjunction with other network node 2700 components (such as memory 2704).

[0377] In some embodiments, processing circuitry 2702 includes a system on chip (SOC). In some embodiments, processing circuitry 2702 includes one or more of radio frequency (RF) transceiver circuitry 2712 and baseband processing circuitry 2714. In some embodiments, radio frequency (RF) transceiver circuitry 2712 and baseband processing circuitry 2714 may be on separate chips (or chipsets), boards, or units, such as a radio unit and a digital unit. In alternative embodiments, part or all of RF transceiver circuitry 2712 and baseband processing circuitry 2714 may be on the same chip or chipset, board, or unit.

[0378] The memory 2704 may include any form of volatile or non-volatile computer-readable memory, including but not limited to persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disk (CD) or digital video disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory device that stores information, data and / or instructions that can be used by the processing circuit 2702. The memory 2704 may store any suitable instructions, data or information, including computer programs, software, applications, including one or more of logic, rules, codes, tables and / or other instructions that can be executed by the processing circuit 2702 and utilized by the network node 2700. The memory 2704 may be used to store any calculations made by the processing circuit 2702 and / or any data received via the communication interface 2706. In some embodiments, the processing circuit 2702 and the memory 2704 are integrated.

[0379] The communication interface 2706 is used for wired or wireless communication of signaling and / or data between network nodes, access networks and / or UEs. As shown, the communication interface 2706 includes one or more ports / terminals 2716, for example, sending data to the network and receiving data from the network through a wired connection. The communication interface 2706 also includes a radio front-end circuit 2718, which can be coupled to the antenna 2710, or is a part of the antenna 2710 in some embodiments. The radio front-end circuit 2718 includes a filter 2720 and an amplifier 2722. The radio front-end circuit 2718 can be connected to the antenna 2710 and the processing circuit 2702. The radio front-end circuit can be configured to adjust the signal transmitted between the antenna 2710 and the processing circuit 2702. The radio front-end circuit 2718 can receive digital data to be sent to other network nodes or UEs via a wireless connection. The radio front-end circuit 2718 can use a combination of a filter 2720 and / or an amplifier 2722 to convert digital data into a radio signal with appropriate channel and bandwidth parameters. The radio signal can then be sent via the antenna 2710. Similarly, when receiving data, antenna 2710 may collect radio signals, which are then converted into digital data by radio front end circuit 2718. The digital data may be passed to processing circuit 2702. In other embodiments, the communication interface may include different components and / or different combinations of components.

[0380] In certain alternative embodiments, the network node 2700 does not include a separate radio front end circuit 2718, but rather the processing circuit 2702 includes the radio front end circuit and is connected to the antenna 2710. Similarly, in some embodiments, all or part of the RF transceiver circuit 2712 is part of the communication interface 2706. In other embodiments, the communication interface 2706 includes one or more ports or terminals 2716, the radio front end circuit 2718, and the RF transceiver circuit 2712 as part of a radio unit (not shown), and the communication interface 2706 communicates with the baseband processing circuit 2714 as part of a digital unit (not shown).

[0381] Antenna 2710 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals. Antenna 2710 may be coupled to radio front end circuit 2718 and may be any type of antenna capable of wirelessly sending and receiving data and / or signals. In some embodiments, antenna 2710 is separate from network node 2700 and may be connected to network node 2700 via an interface or port.

[0382] Antenna 2710, communication interface 2706 and / or processing circuit 2702 may be configured to perform any receiving operation and / or certain acquisition operations described herein as being performed by a network node. Any information, data and / or signal may be received from a UE, another network node and / or any other network device. Similarly, antenna 2710, communication interface 2706 and / or processing circuit 2702 may be configured to perform any sending operation described herein as being performed by a network node. Any information, data and / or signal may be sent to a UE, another network node and / or any other network device.

[0383] The power supply 2708 provides power to the various components of the network node 2700 in a form suitable for the various components (e.g., at the voltage and current levels required by each corresponding component). The power supply 2708 may further include or be coupled to a power management circuit to supply power to the components of the network node 2700 for performing the functions described herein. For example, the network node 2700 may be connected to an external power source (e.g., a power grid, an electrical outlet) via an input circuit or interface such as a cable, whereby the external power source supplies power to the power circuit of the power supply 2708. As another example, the power supply 2708 may include a power source in the form of a battery or battery pack, which is connected to the power circuit or integrated in the power circuit. If the external power supply fails, the battery can provide backup power.

[0384] An embodiment of the network node 2700 may include Fig. 27Additional components beyond those shown are used to provide certain aspects of the network node functionality, including any functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 2700 may include a user interface device to allow information to be input into the network node 2700 and to allow information to be output from the network node 2700. This may allow a user to perform diagnostics, maintenance, repair, and other management functions of the network node 2700.

[0385] Fig.28 is a block diagram of a host 2800 according to various aspects described herein, and the host 2800 may be Fig.25 25. As used herein, host 2800 may be or include various combinations of hardware and / or software, including processing resources in a standalone server, blade server, cloud-implemented server, distributed server, virtual machine, container, or server farm. Host 2800 may provide one or more services to one or more UEs.

[0386] Host 2800 includes processing circuitry 2802, which is operably coupled to input / output interface 2806, network interface 2808, power supply 2810, and memory 2812 via bus 2804. Other components may be included in other embodiments. The features of these components may be substantially similar to those described with respect to previous figures (such as Fig.26 and Fig. 27 ) describes features of the device so that its description is generally applicable to corresponding components of the host 2800.

[0387] Memory 2812 may include one or more computer programs, including one or more host applications 2814 and data 2816, which may include user data (e.g., data generated by the UE for the host 2800 or data generated by the host 2800 for the UE). An embodiment of the host 2800 may utilize only a subset or all of the components shown. The host application 2814 may be implemented in a container-based architecture and may provide support for video codecs (e.g., generic 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, and G.711), including code conversion for multiple different categories, types, or implementations of UEs (e.g., mobile phones, desktop computers, wearable display systems, head-up display systems). The host application 2814 may also provide user authentication and license checks, and may periodically report health status, routing, and content availability to a central node (such as a device in a core network or on the edge). Thus, the host 2800 can select and / or indicate different hosts for over-the-top services for the UE. The host application 2814 can support various protocols, such as HTTP Live Streaming (HLS) protocol, Real-time Messaging Protocol (RTMP), Real-time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[0388] Fig.29 2900, in which the functions implemented by some embodiments can be virtualized. In this context, virtualization means creating a virtual version of a device or equipment, which can include virtualizing a hardware platform, a storage device, and a network resource. As used herein, virtualization can be applied to any device or component thereof described herein, and relates to such an implementation, in which at least a portion of a function is implemented as one or more virtual components. Some or all of the functions described herein can be implemented as virtual components performed by one or more virtual machines (VMs), which are implemented in one or more virtual environments 2900 hosted by one or more hardware nodes (such as hardware computing devices operating as network nodes, UEs, core network nodes, or hosts). In addition, in an embodiment where a virtual node does not require a radio connection (e.g., a core network node or a host), the node can be fully virtualized.

[0389] Application 2902 (which may alternatively be referred to as a software instance, a virtual appliance, a network function, a virtual node, a virtual network function, etc.) runs in a virtualized environment Q400 to implement some features, functions and / or benefits of some embodiments disclosed herein.

[0390] The hardware 2904 includes processing circuitry, memory storing software and / or instructions executable by the hardware processing circuitry, and / or other hardware devices described herein, such as network interfaces, input / output interfaces, etc. The software may be executed by the processing circuitry to instantiate one or more virtualization layers 2906 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 2908a and 2908b (one or more of which may be generally referred to as VMs 2908), and / or perform any of the functions, features, and / or benefits described in connection with some of the embodiments described herein. The virtualization layer 2906 may present a virtual operating platform that looks like network hardware to the VMs 2908.

[0391] VM 2908 includes virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and can be run by a corresponding virtualization layer 2906. Different embodiments of instances of virtual devices 2902 can be implemented on one or more of VM 2908 and can be implemented in different ways. Virtualization of hardware is referred to as network function virtualization (NFV) in some contexts. NFV can be used to integrate many network device types onto industry-standard high-volume server hardware, physical switches, and physical storage, which can be located in data centers and customer premises equipment.

[0392] In the context of NFV, VM 2908 can be a software implementation of a physical machine that runs programs as if they were executed on a physical, non-virtualized machine. Each of VM 2908 and the portion of hardware 2904 on which the VM executes, whether hardware dedicated to the VM and / or hardware shared by the VM with other VMs in the VM, form a separate virtual network element. Still in the context of NFV, a virtual network function is responsible for handling a specific network function running in one or more VMs 2908 on top of hardware 2904 and corresponds to application 2902.

[0393] Hardware 2904 can be implemented in a stand-alone network node with general or specific components. Hardware 2904 can implement some functions via virtualization. Alternatively, hardware 2904 can be part of a larger hardware cluster (e.g., in a data center or CPE), where many hardware nodes work together and are managed via management and coordination 2910, where management and coordination 2910 especially supervises the life cycle management of application 2902. In some embodiments, hardware 2904 is coupled to one or more radio units, each of which includes one or more transmitters and one or more receivers that can be coupled to one or more antennas. The radio unit can communicate directly with other hardware nodes via one or more appropriate network interfaces, and can be used in combination with virtual components to provide radio capabilities to virtual nodes such as radio access nodes or base stations. In some embodiments, a control system 2912 can be used to provide some signaling, which can be alternatively used for communication between hardware nodes and radio units.

[0394] Fig.30 A communication diagram showing a host 3002 communicating with a UE 3006 via a network node 3004 over a partial wireless connection according to some embodiments.

[0395] Now refer to Fig.30 Describes the UE (such as Fig.25 UE2512a and / or Fig.26 UE 2600), network nodes (such as Fig.25 The network node 2510a and / or Fig. 27 network nodes 2700) and hosts (such as Fig.25 Host 2516 and / or Fig.28 An example implementation of host 2800).

[0396] Similar to the host 2800, an embodiment of the host 3002 includes hardware, such as a communication interface, a processing circuit, and a memory. The host 3002 also includes software stored in or accessible by the host 3002 and executable by the processing circuit. The software includes a host application that is operable to provide services to a remote user, such as a UE 3006 connected via an over-the-top transfer (OTT) connection 3050 extending between the UE 3006 and the host 3002. In providing services to the remote user, the host application can provide user data sent using the OTT connection 3050.

[0397] The network node 3004 includes hardware that enables it to communicate with the host 3002 and the UE 3006. The connection 3060 can be direct or through a core network (such as Fig.25The core network 2506 of the present invention) and / or one or more other intermediate networks, such as one or more public, private or managed networks. For example, the intermediate network can be a backbone network or the Internet.

[0398] UE 3006 includes hardware and software that is stored in or accessible by UE 3006 and can be executed by the processing circuit of UE. The software includes a client application, such as a web browser or an operator-specific "application", which is operable to provide services to human or non-human users via UE 3006 with the support of host 3002. In host 3002, the executing host application can communicate with the executing client application via an OTT connection 3050 that terminates at UE 3006 and host 3002. In the process of providing services to users, the client application of the UE can receive request data from the host application of the host and provide user data in response to the request data. The OTT connection 3050 can transmit the request data and the user data. The client application of the UE can interact with the user to generate the user data that it provides to the host application via the OTT connection 3050.

[0399] The OTT connection 3050 may extend via a connection 3060 between the host 3002 and the network node 3004 and via a wireless connection 3070 between the network node 3004 and the UE 3006 to provide connectivity between the host 3002 and the UE 3006. The connection 3060 and the wireless connection 3070 over which the OTT connection 3050 may be provided are drawn abstractly to illustrate communications between the host 3002 and the UE 3006 via the network node 3004 without explicit reference to any intermediate devices and the precise routing of messages via those devices.

[0400] As an example of sending data via the OTT connection 3050, in step 3008, the host 3002 provides user data, which can be performed by executing a host application. In some embodiments, the user data is associated with a specific human user interacting with the UE 3006. In other embodiments, the user data is associated with the UE 3006, which shares data with the host 3002 without explicit human interaction. In step 3010, the host 3002 initiates a transmission carrying the user data to the UE 3006. The host 3002 may initiate the transmission in response to a request sent by the UE 3006. The request may be caused by human interaction with the UE 3006 or by the operation of a client application executed on the UE 3006. According to the teachings of the embodiments described throughout the present disclosure, the transmission may be through the network node 3004. Therefore, according to the teachings of the embodiments described throughout the present disclosure, in step 3012, the network node 3004 sends the user data carried in the transmission initiated by the host 3002 to the UE 3006. In step 3014 , UE 3006 receives user data carried in the transmission, which may be performed by a client application executing on UE 3006 that is associated with a host application executed by host 3002 .

[0401] In some examples, UE 3006 executes a client application that provides user data to host 3002. The user data may be provided in reaction to or in response to data received from host 3002. Thus, in step 3016, UE 3006 may provide the 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 the input / output interface of UE 3006. Regardless of the specific manner of providing the user data, in step 3018, UE 3006 initiates transmission of the user data to host 3002 via network node 3004. In step 3020, in accordance with the teachings of the embodiments described throughout the present disclosure, network node 3004 receives user data from UE 3006 and initiates transmission of the received user data to host 3002. In step 3022, host 3002 receives the user data carried in the transmission initiated by UE 3006.

[0402] One or more of the various embodiments improves the performance of OTT services provided to UE 3006 using OTT connection 3050 in which wireless connection 3070 forms the last leg. More precisely, the teachings of these embodiments may allow identification of a UL Tx beam to be used for Msg3 transmission.

[0403] In an example scenario, the host 3002 may collect and analyze plant status information. As another example, the host 3002 may process audio and video data that may have been retrieved from the UE for use in creating a map. As another example, the host 3002 may collect and analyze real-time data to help control vehicle congestion (e.g., control traffic lights). As another example, the host 3002 may store surveillance videos uploaded by the UE. As another example, the host 3002 may store media content (such as video, audio, VR, or AR) that it may broadcast, multicast, or unicast to the UE, or control access to the media content. As other examples, the host 3002 may be used for energy pricing, remote control of non-time-critical power loads to balance power generation needs, positioning services, presentation services (such as compiling charts based on data collected from remote devices, etc.), or any other function of collecting, retrieving, storing, analyzing, and / or sending data.

[0404] In some examples, a measurement process may be provided for the purpose of monitoring data rates, delays, and other factors improved by one or more embodiments. There may also be an optional network function for reconfiguring the OTT connection 3050 between the host 3002 and the UE 3006 in response to changes in the measurement results. The measurement process and / or network function for reconfiguring the OTT connection may be implemented in the software and hardware of the host 3002 and / or the UE 3006. In some embodiments, sensors (not shown) may be deployed in or associated with other devices through which the OTT connection 3050 passes; the sensors may participate in the measurement process by supplying the values ​​of the monitored quantities illustrated above or supplying the values ​​of other physical quantities according to which the software can calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 3050 may include message formats, retransmission settings, preferred routes, etc.; the reconfiguration does not require direct changes to the operation of the network node 3004. Such processes and functions may be known and practiced in the art. In some embodiments, the measurement may involve dedicated UE signaling, which facilitates the host 3002 to measure throughput, propagation time, delay, etc. The measurements can be achieved by software enabling the sending of messages, particularly empty messages or "dummy" messages, using the OTT connection 3050 while monitoring propagation times, errors, etc.

[0405] Although the computing devices described herein (e.g., UE, network node, host) may include the illustrated combination of hardware components, other embodiments may include computing devices with different combinations of components. It should be understood that these computing devices may include any suitable combination of hardware and / or software required to perform the tasks, features, functions and methods disclosed herein. The determination, calculation, acquisition or similar operations described herein may be performed by a processing circuit, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or the converted information with the information stored in the network node, and / or performing one or more operations based on the obtained information or the converted information, and making a determination as a result of the processing. In addition, although the components are depicted as being located in a larger box or a single box nested in multiple boxes, in practice, the computing device may include multiple different physical components that make up a single illustrated component, and the functions may be divided between separate components. For example, a communication interface may be configured to include any one of the components described herein, and / or the functions of the components may be divided between the processing circuit and the communication interface. In another example, the non-computationally intensive functions of any such component may be implemented in software or firmware, and the computationally intensive functions may be implemented in hardware.

[0406] In some embodiments, some or all of the functions described herein may be provided by a processing circuit that executes instructions stored in a memory, which in some 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 functions may be provided by a processing circuit without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hardwired manner. In any of these specific embodiments, the processing circuit may be configured to perform the described functions, regardless of whether instructions stored on a non-transitory computer-readable storage medium are executed. The benefits provided by such functions are not limited to the processing circuit itself or other components of the computing device, but are enjoyed by the computing device as a whole and / or generally by end users and wireless networks.

Claims

1. A method of operating a communication device during a random access (RA) procedure associated with a network node of a New Radio (NR) communication network, the method comprising: determining (2330) information associated with at least one of the communication device and a channel between the communication device and the network node; determining (2340) a number of physical RA channel PRACH transmissions to be sent to the network node before receiving a random access response as part of the RA procedure based on the information; and The number of PRACH transmissions is sent (2350) to the network node as part of the RA procedure.

2. The method of claim 1, further comprising: determining (2345) a periodicity associated with the PRACH transmission based on an association period, The sending of the number of PRACH transmissions comprises: sending the number of PRACH transmissions using the periodicity.

3. The method of claim 2, wherein: Sending the number of PRACH transmissions using the periodicity includes sending the number of PRACH transmissions during a time period, the time period being equal to one or more associated periods.

4. The method according to any one of claims 2 to 3, wherein: Sending the number of PRACH transmissions includes sending the number of PRACH transmissions during a time period starting from a resource opportunity RO index I defined as mod(I,K)=0, where K is the number of PRACH transmissions.

5. The method according to any one of claims 1 to 4, wherein: For the time instances associated with said number of PRACH transmissions, there are a plurality of frequency division multiplexing FDM resource opportunities RO associated with the selected synchronization signal block SSB, and Wherein sending the number of PRACH transmissions comprises: based on the number of ROs of FDM configured for the number of PRACH transmissions associated with the selected SSB, jumping between the multiple FDM ROs across the number of PRACH transmissions.

6. The method of claim 5, wherein: Sending the number of PRACH transmissions includes: RO index RO in the frequency domain defined by start (i) sends the i-th PRACH transmission among the number of PRACH transmissions: Wherein, K represents the number of time-domain PRACH opportunities of one hop, and F represents the number of ROs of FDM used for the number of PRACH transmissions.

7. The method according to any one of claims 1 to 4, wherein: Sending the number of PRACH transmissions comprises: sending a first PRACH transmission of the number of PRACH transmissions; After sending the first PRACH transmission, determining that the first PRACH transmission is discarded; and In response to determining that the first PRACH transmission is discarded, all remaining PRACH transmissions of the number of PRACH transmissions are transmitted.

8. The method according to any one of claims 1 to 7, wherein: Determining the information includes: determining a reference signal received power RSRP associated with the channel, and Wherein, determining the number of PRACH transmissions includes: determining the number of PRACH transmissions based on a comparison of the RSRP with a predetermined threshold; Determining, based on the RSRP and the threshold, that a repetition process is applicable to Msg3 transmission; and The Msg3 transmission is repeated at least the number of times indicated in the random access response.

9. The method of claim 8, wherein: The predetermined threshold includes the rsrp-ThresholdMsg3 threshold, The method further comprises: The rsrp-ThresholdMsg3 threshold is determined (2320) based on a flag in a radio resource control RRC message associated with a particular bandwidth part BWP or preamble signature group.

10. The method according to any one of claims 1 to 9, wherein: Determining the information includes: determining a power headroom of the communication device, and The determining the number of PRACH transmissions comprises: determining the number of PRACH transmissions based on a comparison between an amount of power required for PRACH transmission and the power headroom.

11. The method according to any one of claims 1 to 10, further comprising: In response to sending the number of PRACH transmissions, determining (2360) that a RA response RAR has not been received during a predetermined time period; In response to determining that the RAR has not been received during the predetermined time period, determining (2370) at least one of a number of PRACH retransmissions and a transmit power for the PRACH retransmissions based on a network configured parameter; as well as The number of PRACH retransmissions is sent (2380).

12. The method of any one of claims 1 to 11, further comprising: An indication of PRACH transmission configuration information is received (2310) from the network node via a system information block (SIB), the PRACH transmission configuration information enabling the communication device to send a plurality of PRACH transmissions.

13. The method according to any one of claims 1 to 12, wherein: Transmitting the number of PRACH transmissions includes transmitting a plurality of different preambles across a plurality of RA channel opportunities (RO) associated with a synchronization signal block associated with the PRACH transmissions.

14. The method of claim 13, wherein: The number of PRACH transmissions includes at least two PRACH transmissions, Wherein, sending the number of PRACH transmissions includes: transmitting the first PRACH transmission at a first RO of the plurality of ROs using a first preamble based on a position of a preamble group associated with a first PRACH transmission of the at least two PRACH transmissions within the first RO; and The second PRACH transmission of the at least two PRACH transmissions is transmitted at a second RO of the plurality of ROs using a second preamble based on a position of a preamble group associated with the second PRACH transmission within the second RO.

15. The method according to any one of claims 1 to 14, wherein: The number of PRACH transmissions includes at least two PRACH transmissions, Wherein, sending the number of PRACH transmissions includes: sending a first PRACH transmission of the at least two PRACH transmissions using a first preamble index; determining a second preamble index based on the first preamble index and at least one of a logical index and a cyclic shift of a root sequence; and A second PRACH transmission of the at least two PRACH transmissions is sent using the second preamble index.

16. The method according to any one of claims 1 to 15, wherein: The number of PRACH transmissions includes at least two PRACH transmissions, Wherein, sending the number of PRACH transmissions includes: sending a first PRACH transmission of the at least two PRACH transmissions using a first preamble index; determining a second preamble index by applying the same offset between the first preamble index and a starting preamble index configured for multiple PRACH transmissions in the first RO to a starting preamble index configured for multiple PRACH transmissions in the second RO; and A second PRACH transmission of the at least two PRACH transmissions is sent using the second preamble index.

17. The method according to any one of claims 1 to 16, wherein: Determining the number of PRACH transmissions to send to the network node comprises: receiving an indication of a number of candidates for a PRACH transmission; and determining the number of PRACH transmissions as the smaller of the number of candidates and the number of different transmission Tx beams that the communication device can use for PRACH transmissions, wherein the number of PRACH transmissions includes at least two PRACH transmissions each associated with a different uplink UL Tx beam, and Wherein, sending the number of PRACH transmissions includes: using the different UL Tx beams to send the at least two PRACH transmissions.

18. The method of claim 17, wherein: Sending the number of PRACH transmissions further comprises sending an indication that the communications device will send the at least two PRACH transmissions using the different UL TX beams.

19. The method according to any one of claims 1 to 18, wherein: Determining the number of PRACH transmissions includes determining the number of PRACH transmissions based on an uplink (UL) beam switching time and an amount of time between PRACH opportunities such that the time between any two consecutive transmissions is greater than the beam switching time.

20. The method of any one of claims 1 to 19, wherein: The number of PRACH transmissions includes at least two PRACH transmissions each associated with a different transmit power, and Wherein, sending the number of PRACH transmissions includes: sending the at least two PRACH transmissions using the different transmit powers; and Each of the different transmit powers is determined according to at least one of the corresponding path loss values.

21. The method of claim 20, wherein: Sending the number of PRACH transmissions further comprises: The different transmit powers are determined according to different values ​​of the power ramp counter.

22. The method of any one of claims 1 to 21, wherein: The number of PRACH transmissions includes at least two PRACH transmissions each associated with a different timing advance TA, and The sending of the number of PRACH transmissions comprises: sending the at least two PRACH transmissions using the different TAs.

23. The method of any one of claims 1 to 22, wherein: The number of PRACH transmissions includes at least two PRACH transmissions, and Wherein sending the number of PRACH transmissions comprises sending the at least two PRACH transmissions in an order based on a path loss associated with each of the at least two PRACH transmissions.

24. The method of any one of claims 1 to 23, wherein: The number of PRACH transmissions includes at least two PRACH transmissions each associated with a different synchronization signal block SSB, and Wherein, sending the number of PRACH transmissions includes: using the UL Tx beam associated with the different SSBs to send the at least two PRACH transmissions.

25. A method of operating a network node of a New Radio (NR) communications network during a random access (RA) procedure associated with a communications device, the method comprising: determining (2430) information associated with at least one of the communication device and a channel between the communication device and the network node; determining (2440) a number of physical RA channel PRACH transmissions to be received from the communication device as part of the RA procedure based on the information; as well as As part of the RA procedure, the NR communication network is monitored (2450) for the number of PRACH transmissions from the communication device.

26. The method of claim 25, wherein: Determining the information includes: determining a reference signal received power RSRP associated with the channel, and Wherein, determining the number of PRACH transmissions includes: determining the number of PRACH transmissions based on a comparison between the RSRP and a predetermined threshold.

27. The method of claim 26, wherein: The predetermined threshold includes the rsrp-ThresholdMsg3 threshold, The method further comprises: The indication of the rsrp-ThresholdMsg3 threshold is sent (2420) via a flag in a radio resource control RRC message associated with a specific bandwidth part BWP or preamble signature group.

28. The method of any one of claims 25 to 27, wherein: Determining the information includes: determining a power headroom of the communication device, and Wherein, determining the number of PRACH transmissions comprises: determining the number of PRACH transmissions based on a comparison between an amount of power required for the number of PRACH transmissions and the power headroom.

29. The method of any one of claims 25-28, further comprising: In response to monitoring the NR communications network, determining (2460) that a PRACH transmission has not been received during a predetermined time period; as well as In response to determining that the PRACH transmission has not been received during the predetermined time period, monitoring (2470) the NR communication network for a number of PRACH retransmissions based on a network configured parameter.

30. The method of any one of claims 25-29, further comprising: An indication of PRACH transmission configuration information is sent (2410) from the network node via a system information block (SIB), the PRACH transmission configuration information enabling the communication device to send a plurality of PRACH transmissions.

31. The method of any one of claims 25 to 30, wherein: Monitoring the NR communication network for the number of PRACH transmissions includes monitoring the NR communication network for multiple different preamble codes spanning multiple RA channel opportunities RO associated with a synchronization signal block associated with a portion of the PRACH transmission.

32. The method of any one of claims 25 to 31, wherein: The number of PRACH transmissions includes at least two PRACH transmissions each associated with a different uplink UL transmission Tx beam, and Wherein, monitoring the NR communication network for the number of PRACH transmissions includes: monitoring the NR communication network for the at least two PRACH transmissions via the different ULTx beams.

33. The method of any one of claims 25 to 32, wherein: The number of PRACH transmissions includes at least two PRACH transmissions each associated with a different transmit power, and Wherein, monitoring the NR communication network includes: monitoring the NR communication network for the at least two PRACH transmissions using the different transmit powers.

34. The method of any one of claims 25 to 33, wherein: The number of PRACH transmissions includes at least two PRACH transmissions each associated with a different timing advance TA, and Among them, monitoring the NR communication network includes: monitoring the NR communication network for the at least two PRACH transmissions using the different TAs.

35. The method of any one of claims 25 to 34, wherein: The number of PRACH transmissions includes at least two PRACH transmissions, and Wherein, monitoring the NR communication network includes: monitoring the NR communication network for the at least two PRACH transmissions in an order based on a path loss associated with each of the at least two PRACH transmissions.

36. The method of any one of claims 25 to 35, wherein: The number of PRACH transmissions includes at least two PRACH transmissions each associated with a different synchronization signal beam SSB, and Among them, monitoring the NR communication network includes: monitoring the NR communication network for the at least two PRACH transmissions using the different SSBs.

37. A communication device (2600), the communication device comprising: Processing circuit (2602); as well as A memory (2610) coupled to the processing circuit and having instructions stored therein, the instructions executable by the processing circuit to cause the communication device to perform operations including those of any of claims 1-24.

38. A network node (2700) for configuring a successful handover report SHR, the network node comprising: Processing circuit (2702); as well as A memory (2704) coupled to the processing circuit and having instructions stored therein, the instructions being executable by the processing circuit to cause the network node to perform operations including those of any of claims 25-36.

Images