Determining prach space tx filter and tx power in multiple TRP transmissions

Abstract

Systems and methods for determining transmit power for a Physical Random Access Channel (PRACH) for multiple transmissions and Reception Point (TRP) transmissions are disclosed. In one embodiment, a method performed by a user equipment (UE) includes receiving a configuration of first and second time advance group (TAG) identifications (IDs) in a serving cell, a first control resource set (CORESET) pool index value, and a second CORESET pool index value. The method also includes receiving a request to transmit a physical random access channel (PRACH) preamble in the serving cell, the request including a PRACH preamble index, information about a downlink reference signal (RS), and information about a physical cell identity (PCI) associated with the downlink RS. The method further includes determining a transmit power for transmission of the PRACH preamble based on the request; and transmitting the PRACH preamble accordingly.

Description

[0001] Related applications This application claims the benefit of provisional patent application serial number 63 / 485699, filed on February 17, 2023, the disclosure of which is incorporated herein by reference in its entirety. Technical Field

[0002] This disclosure relates to cellular communication systems, and more particularly to Physical Random Access Channel (PRACH) transmissions. Background Technology

[0003] The 3GPP New Radio (NR) uses Cyclic Prefix Orthogonal Frequency Division Multiplexing (CP-OFDM) in both the downlink (DL) (i.e., from a network node, gNodeB, or base station to a user equipment or UE) and the uplink (UL) (i.e., from a UE to a gNodeB). Discrete Fourier Transform (DFT) Extended Orthogonal Frequency Division Multiplexing (OFDM) is also supported in the uplink. In the time domain, NR downlink and uplink are organized into equal-sized subframes of 1 millisecond (ms). Subframes are further divided into multiple time slots of equal duration. The time slot length depends on the subcarrier spacing. For a subcarrier spacing of ∆f = 15 kHz, there is only one time slot per subframe, and each time slot consists of 14 OFDM symbols.

[0004] Data scheduling in NR is typically based on time slots. Figure 1A The example shown has 14-symbol time slots, where the first two symbols contain the physical downlink control channel (i.e., the physical downlink control channel (PDCCH)) and the remaining symbols contain the physical shared data channel, i.e., the physical downlink shared channel (PDSCH) or the physical uplink shared channel (PUSCH).

[0005] NR supports different subcarrier spacing (SCS) values. The supported SCS values ​​(also known as different sets of parameter numbers) are determined by ∆f = (15 × 2) / ( ... μ The time slot duration is given by kHz, where μ∈{0,1,2,3,4}. ∆f=15kHz is the basic subcarrier spacing. ms.

[0006] In the frequency domain, the system bandwidth is divided into resource blocks (RBs), each corresponding to twelve (12) adjacent subcarriers. RBs are numbered starting from 0, beginning at one end of the system bandwidth. The basic NR physical time-frequency resource grid is... Figure 1B The diagram shows only one RB within a 14-symbol slot. One OFDM subcarrier during an OFDM symbol interval forms a resource element (RE).

[0007] Downlink transmissions to the UE can be dynamically scheduled by sending downlink control information (DCI) in the downlink (DL) DCI format carried on the PDCCH. The UE first detects and decodes the PDCCH, and if decoding is successful, the UE decodes the corresponding PDSCH according to the scheduling information in the DCI.

[0008] Similarly, uplink data transmission can be dynamically scheduled using the uplink (UL) DCI format carried on the PDCCH. The UE first decodes the uplink grant in the DCI, and then transmits data through the Physical Uplink Shared Channel (PUSCH) according to the control information contained in the uplink path grant.

[0009] and search space set A control resource set (CORESET) consists of multiple RBs in the frequency domain and one to three consecutive OFDM symbols in the time domain. In NR Release 15, a UE can be configured with up to three (3) CORESETs per bandwidth portion (BWP).

[0010] A set of PDCCH candidates is defined in the PDCCH search space (SS) set associated with the CORESET. The UE monitors the set of PDCCH candidates to detect PDCCH. The SS set can be a common search space (CSS) set or a UE-specific search space (USS) set. The UE can be configured with up to ten (10) SS sets per BWP for monitoring PDCCH candidates.

[0011] Status and QCL The CORESET Transmit Configuration Indicator (TCI) status contains quasi-coordinated positioning (QCL) information between the demodulation reference signal (DMRS) of the PDCCH transmitted in the CORESET and one or two DL reference signals (RS). The DL reference signals are, for example, Channel State Information Reference Signals (CSI-RS) or synchronization signals and Physical Broadcast Channel Blocks (SSBs). Two antenna ports are said to be QCL if certain channel parameters associated with one of the two antenna ports can be inferred from the other antenna port. Supported QCL information types in NR include: 'QCL-Type A': {Doppler frequency shift, Doppler spread, average delay, delay spread} 'QCL-Type B': {Doppler frequency shift, Doppler spread} 'QCL-Type C': {Doppler shift, average delay} 'QCL-Type D': {Space Rx parameter} For each CORESET, the TCI state list can be configured by Radio Resource Control (RRC), and one of the TCI states is activated by the Media Access Control (MAC) Control Element (CE). For example, if the SSB is configured as a QCL-type D source RS in the activated TCI state of the CORESET, the UE can use the same receive beam used to receive the SSB to receive the PDCCH transmitted in the CORESET.

[0012] In NR Rel-17, a unified TCI state framework was introduced, in which multiple common TCI states can be activated by the MAC CE, and one of the activated TCI states is indicated by the DCI for multiple DL and / or UL channels or signals. In this case, CORESET can follow the indicated common TCI state.

[0013] As defined in 3GPP TS 38.211, the Physical Broadcast Channel (PBCH), Primary Synchronization Signal (PSS), and Secondary Synchronization Signal (SSS) are transmitted in consecutive OFDM symbols and form SS / PBCH blocks (or simply SSBs). Multiple SSBs or SSB burst sets can be configured within each half-frame or 5ms. SSB burst sets are transmitted periodically in multiples of 5ms. The maximum number L of SSBs in an SSB burst set depends on the carrier frequency, where L=4 represents a carrier frequency up to 3GHz, L=8 represents a carrier frequency between 3GHz and 6GHz, and L=64 represents a carrier frequency from 6GHz to 52.6GHz. Within a half-frame, the SSB index increases from 0 to L-1. The same transmission power is used for all SSB transmissions within the cell.

[0014] The SSB is used by the UE to obtain time and frequency synchronization with the cell and to detect the cell's physical layer cell identifier (ID).

[0015] When accessing a cell from an idle cell, information about the SSB and physical layer cell ID is typically obtained by the UE from the SSB in the PBCH, the MIB (Master Information Block), or the SIB (System Information Block) in the PDSCH. When the UE is configured with one or more secondary cells (SCells) or with an additional secondary cell group (SCG), or when a special cell (SpCell) (MCG (Primary Cell Group) and SCG (Secondary Cell Group)) are reconfigured, the cell's SSB can be obtained via dedicated signaling. Figure 2 As shown ServingCellConfigCommon Configure using information elements (IE).

[0016] Physical random access procedure Before initiating the physical random access procedure, Layer 1 or the physical layer receives the SSB index set from the higher layer and provides the corresponding Reference Signal Received Power (RSRP) measurement set to the higher layer.

[0017] The Physical Random Access procedure is triggered by a higher layer or by a PDCCH command when requesting a Physical Random Access Channel (PRACH) transmission. The configuration performed by the higher layer for PRACH transmission includes the following: • Configuration of PRACH transmission according to 3GPP TS 38.211 (see, for example, v17.4.0) • Preamble index, preamble SCS, PRACH target received power, corresponding RA-RNTI (RACH radio network temporary identifier), and PRACH resources.

[0018] Transmit the PRACH preamble at the indicated PRACH resource with transmission power according to the PRACH configuration.

[0019] PRACH configuration can be cell-specific or UE-specific. Cell-specific PRACH configuration is achieved via... RACH- ConfigCommon The information element (IE) performs this, while the UE-specific PRACH configuration is done via... RACH- ConfigDedicated Both are performed by IE and are described in 3GPP TS 38.331.

[0020] For a Type 1 (or 4-step) random access procedure, at each PRACH timing, a total of [number] [units] are provided to the UE. The PRACH preamble is used for both contention-based random access (CBRA) and contention-free random access (CFRA). If it is not configured, the default is used. =64. Also included by being contained in RACH-ConfigCommon In IE, it is called ssb- perRACH-OccasionAndCB-PreamblesPerSSB The parameters provide the UE with N SSB indices associated with a PRACH timing and R contention-based preambles for each SSB index per valid PRACH timing.

[0021] If N < 1, an SSB index is mapped to 1 / N consecutive valid PRACH times, and R contention-based preambles have consecutive indices associated with the SSB index for each valid PRACH time, starting from preamble index 0. Figure 3A An example is shown where N=1 / 2, R=32. =64, and 4 SSBs.

[0022] If N≥1, then there are R contention-based preamble indexes with consecutive indices associated with the SSB index n (0≤n≤N-1) for each valid PRACH timing. start. Figure 3B An example is given where N=4 and R=4. =64, and 4 SSBs. In this example, for each PRACH timing, PRACH preambles 0 to 3 are assigned to SSB #0 of CBRA, and PRACH preambles 4 to 5 are assigned to SSB #0 of CFRA, PRACH preambles 16 to 19 are assigned to SSB #1 of CBRA, and PRACH preambles 20 to 31 are assigned to SSB #1 of CFRA, and so on.

[0023] The association between the CFRA preamble and the SSB can also be reconfigured via the higher parameter ssb-perRACH-Occasion in the RACH-ConfigDedicated IE, which provides the UE with information about the number N of SS / PBCH block indices associated with a PRACH occasion. The UE can also provide information within the PRACH occasion about the mapping between the SSB index or CSI-RS resource and the preamble index.

[0024] Random access procedure initiated by the command The random access procedure can be initiated by either the gNodeB or the UE. When UL time alignment may have been lost, the random access procedure can be initiated by sending a PDCCH command from the gNodeB to the UE for UL synchronization. The DCI format 1-0 carries the PDCCH command when the DCI's Cyclic Redundancy Check (CRC) is scrambled by the UE's C-RNTI (Cell Radio Network Temporary Identifier) ​​and the DCI's "Frequency Domain Resource Allocation" field contains all 1s. The PDCCH command contains the following information: • Random access preamble index: 6 bits, according to the higher layer parameter “ra-PreambleIndex” in Clause 5.1.2 of 3GPP TS 38.321 (see, for example, v17.3.0).

[0025] • SS / PBCH Index: 6 bits. If the value of "Random Access Preamble Index" is not all zero, this field indicates the SS / PBCH that should be used to determine the timing of RACH (Random Access Channel) transmission; otherwise, this field will be reserved.

[0026] • PRACH Mask Index. According to Clause 5.1.1 of 3GPP TS 38.321, if the value of the "Random Access Preamble Index" is not all zero, this field indicates the RACH timing associated with the SS / PBCH indicated by the "SS / PBCH Index" used for PRACH transmission; otherwise, this field is reserved.

[0027] If the PRACH preamble index is non-zero, a contention-free random access (CFRA) procedure is triggered, in which the PRACH preamble is only allocated to the UE in the corresponding PRACH resource.

[0028] If the PRACH preamble index is zero and a CFRA PRACH resource associated with an SSB is already provided in the UE-specific PRACH configuration in the rach-ConfigDedicated IE, the UE first selects an SSB with an SS-RSRP (SSB-based reference signal received power) higher than the configured threshold, and then selects a PRACH preamble based on the selected SSB. If the PRACH preamble index is zero and a CFRA resource associated with a CSI-RS is already provided in the rach-ConfigDedicated IE, the UE first selects a CSI-RS with a CSI-RSRP higher than the configured threshold (rsrp-ThresholdCSI-RS), and then selects a PRACH preamble based on the selected CSI-RS. If the PRACH preamble index is zero and no CFRA PRACH resource associated with an SSB or CSI-RS is provided, the PDCCH command triggers a contention-based random access (CBRA) procedure, in which the UE randomly selects a PRACH preamble from the set of PRACH preambles configured for the CBRA in the serving cell. Note that in this scenario, more than one UE in the same PRACH resource can select the same preamble code, and contention may occur. If a cell group is configured, the CBRA triggered by the PDCCH command is only allowed for the SpCell, i.e., the primary cell in the primary cell group (MCG) or secondary cell group (SCG). The rach-ConfigDedicated IE is described in 3GPP TS38.331, and the detailed procedure is described in section 5.1.2 of 3GPP TS38.321.

[0029] If the UE is configured with two UL carriers for the serving cell and the UE detects a PDCCH command, the UE uses the UL / SUL indicator field value from the detected PDCCH command to determine the UL carrier for the corresponding PRACH transmission.

[0030] A PRACH opportunity is a time and frequency resource (i.e., multiple RBs in multiple OFDM symbols) allocated for a PRACH transmission. Multiple PRACH opportunities can be configured within a PRACH configuration period consisting of multiple radio frames. PRACH opportunities can be multiplexed in time or frequency.

[0031] From a physical layer perspective, a random access procedure triggered by a PDCCH command includes the UE transmitting a random access preamble (Msg1) in the PRACH, transmitting a RAR (Random Access Response) message (Msg2) with a PDCCH and a corresponding PDSCH, and, where applicable, transmitting a PUSCH authorized and scheduled by the RAR UL, and, if the RACH procedure is contention-based, transmitting a PDSCH for contention resolution.

[0032] Power control According to 3GPP TS 38.213 (see, for example, v17.4.0), the UE at the transmission timing i Based on service cells c The DL reference signal (RS) is used to determine the serving cell. c carrier f UL BWP activities b PRACH transmission power for: in, This refers to the timing of transmission in 3GPP TS 38.101-1 (e.g., see v17.8.0), TS 38.101-2 (e.g., see v17.8.0), and TS 38.101-3 (e.g., see v17.8.0). i Service area within c carrier f The maximum output power of the defined UE configuration. This is in TS 38.321 (for example, see v17.3.0) for the serving cell. c carrier f UL BWP activities b The described PRACH target receive power is provided by a higher layer, and Based on serving the community c The PRACH transmission on the DL BWP is associated with the carrier of the DL RS. f ULBWP activities b The path loss, calculated by the UE in dB. =referenceSignalPower – Higher layer filtering RSRP [dB] RSRP is defined in 3GPP TS 38.215 (see, for example, v17.2.0), and higher-level filter configurations are defined in TS 38.331. If the active DL BWP is the initial DL BWP and is used for SS / PBCH blocks and CORESET multiplexing modes 2 or 3, as described in Clause 13 of TS 38.213, then the UE determines the SS / PBCH block associated with the PRACH transmission based on the SS / PBCH block. .

[0033] If the PRACH transmission from the UE is in response to the detection of a PDCCH command by the UE that triggered the CBRA procedure, then referenceSignalPower From higher-level parameters " ss-PBCH-BlockPower "supply.

[0034] If the PRACH transmission from the UE is in response to the detection of a PDCCH command by the UE that triggered the CFRA procedure, and depends on the DL RS quasi-co-location with the PDCCH command, as described in Clause 10.1 of 38.213, then referenceSignalPower Depend on" ss-PBCH-BlockPower "Provide, or, if the UE is configured with resources for periodic CSI-RS reception, as described in Clause 6 of 38.213, then..." referenceSignalPower pass" ss-PBCH- BlockPower "and" powerControlOffsetSS "obtained, among which" powerControlOffsetSS Provide the CSI-RS transmission power offset relative to the SS / PBCH block transmission power, as described in TS 38.214. If the active TCI state of the PDCCH providing the PDCCH command includes two RSs, the UE expects one RS to be configured with 'typeD'. qcl-Type And if an RS is an SSB, then by ss-PBCH-BlockPower supply referenceSignalPower Otherwise, if an RS is a CSI-RS, then through ss-PBCH-BlockPower and powerControlOffsetSS get referenceSignalPower If not provided to the UE powerControlOffsetSS Then the UE is assumed to have an offset of 0 dB.

[0035] UL time alignment Different UEs within a serving cell may be located at different positions within the cell and therefore at different distances from the base station (e.g., NRgNodeB). If all UEs transmit to the gNodeB at the same time, transmissions from different UEs may arrive at the gNodeB at different times. If these times fall outside a certain reception time window, the UEs will interfere with each other, leading to demodulation difficulties at the gNodeB. To ensure that uplink (UL) transmissions from UEs arrive at the base station within the reception window, an uplink timing alignment process is used.

[0036] Uplink transmission timing is aligned by applying timing advance at the UE transmitter relative to the received downlink timing. Its main function is to compensate for the different propagation delays between different UEs.

[0037] To achieve time alignment between different UEs, base stations (e.g., gNodeB, eNodeB) derive the timing advance (TA) value required for concurrent signaling notification so that each UE can be used for UL transmission.

[0038] 7.1 Obtaining the Initial Timing Advance (TA) In NR, the UE typically acquires the DL slot and symbol timing (referred to as DL timing) based on the SSB and initial UL timing via a random access procedure. During the random access procedure, the UE uses the DL timing as a reference and the same transmission filter or beam used when receiving the SSB to transmit the PRACH preamble in the PRACH resource associated with the SSB. Timing correction in the form of TA is then measured and sent from the base station to the UE in the RAR. The TA is carried by the Timing Advance Command (TAC) in the RAR.

[0039] 7.2 Scheduled Group (TAG) A UE can be configured with multiple serving cells. Some cells may not cooperate in positioning, and different TAs may be required for UL transmissions to these cells. To inform the UE whether two cells have the same or different TAs, a timing advance group (TAG) is introduced in the NR. Cells that cooperate in positioning and can share the same TA value belong to the same TAG and can be configured with the same TAG identifier or index (ID). Cells that do not cooperate in positioning and require different TAs can be configured in different cell groups.

[0040] Each serving cell can have an associated TAG identifier. Two serving cells configured with the same TAG identifier will be assumed by the UE to belong to the same TAG.

[0041] According to TS38.213, when a timing advance command is received from a TAG, the UE adjusts the uplink timing for PUSCH / SRS / PUCCH transmissions on all serving cells in the TAG based on the received timing advance command. The uplink timing for PUSCH / SRS / PUCCH transmissions is the same for all serving cells in the TAG.

[0042] Multi-TRP scheduling based on multiple DCI In NR Release 16, multi-DCI-based DL and UL scheduling was introduced, where the UE can receive two DCI formats (first and second DCI formats) carried by two PDCCHs (first and second PDCCHs) in two separate CORESETs (first and second CORESETs). The first and second CORESETs are associated with first and second CORESET pool indices, respectively. The first and second DCI formats schedule first and second PDSCHs transmitted from first and second Transmit and Receive Points (TRPs), respectively, or schedule first and second PUSCHs to first and second TRPs, respectively.

[0043] exist Figure 4 An example is shown where PDCCH1 in CORESET1 (CORESET pool index = 0) schedules PDSCH1 from TRP1, while PDCCH2 in CORESET2 (CORESET pool index = 1) schedules PDSCH2 from TRP2. Similarly, PDCCH in CORESET1 can schedule PUSCH toward TRP1, and PDCCH in CORESET2 can schedule PUSCH toward TRP2.

[0044] For multiple DCI and multiple TRP operations, the UE needs to be configured with two CORESET pool indices, each CORESET pool index being associated with a TRP. Each CORESET pool is a collection of CORESETs configured with the same CORESET pool index.

[0045] In cases where one of the TRPs is associated with a PCI (Physical Cell Identifier) ​​different from that of the serving cell, this different PCI is also referred to as the supplementary PCI, and according to 3GPP TS 38.331 v17.2.0, via... Figure 5A As shown SSB- MTC-AdditionalPCI-r17 The higher-level parameter "additionalPCI-r17" in IE is provided to UE.

[0046] Multiple UEs can be configured in the serving cell SSB-MTC-AdditionalPCI-r17 IE, each SSB-MTC- Additional PCI-r17Associated with additional PCI. Multiple SSB-MTC-AdditionalPCI-r17 Each IE is assigned an index "AdditionalPCIIndex-r17", ranging from 1 to the maximum configurable number of additional PCIes. According to 3GPP TS38.331 v17.2.0, in Figure 5B As shown ServingCellConfig In IE, multiple SSB-MTC- Additional PCI-r17 IE is configured as "additionalPCI-ToAddModList-r17".

[0047] According to 3GPP TS 38.331 v17.2.0, such as Figure 5C As shown, additional PCI information is included in each TCI state associated with the TRP. 9 Two TAs In multi-DCI-based UL transmissions, the UL timing may actually differ between different TRPs due to factors such as propagation delay differences and / or timing differences. In NR Rel-18, it has been agreed that different TAs can be supported for UL transmissions to different TRPs. Therefore, two TAGs will be introduced for serving cells configured with multi-DCI-based scheduling.

[0048] It is also agreed that a PDCCH command can be sent from one TRP to trigger CFRA-based PRACH transmissions toward different TRPs. Summary of the Invention

[0049] A system and method are disclosed for determining transmit power and spatial transmission (Tx) filters for Physical Random Access Channel (PRACH) transmissions for multiple transmit and receive points (TRP). In one embodiment, a method performed by a user equipment (UE) includes receiving from a network node a first Time Advance Group (TAG) identifier (ID) and a second TAG ID, as well as a first CORESET having a first control resource set (CORESET) pool index value and a second CORESET having a second CORESET pool index value. The method further includes receiving from the network node a request to transmit a PRACH preamble in the serving cell, wherein the request includes a PRACH preamble index associated with the PRACH preamble, information about a downlink reference signal (RS), and information about a physical cell identifier (PCI) associated with the downlink RS. The method further includes determining a transmit power for transmitting the PRACH preamble based on the information about the downlink RS and the information about the PCI included in the request; and transmitting the PRACH preamble according to the determined transmit power. In this way, when more than one Timing Advance Group (TAG) or Timing Advance (TA) is configured for the serving cell, the requested PRACH preamble is transmitted with the correct transmission power.

[0050] In one embodiment, the request is carried in the Physical Downlink Control Channel (PDCCH).

[0051] In one embodiment, the request is a PDCCH command carried in the downlink control information (DCI) format.

[0052] In one embodiment, the first TAG ID is different from the second TAG ID, and the first CORESET pool index value is different from the second CORESET pool index value.

[0053] In one embodiment, the downlink RS is a synchronization reference signal (SS) and a physical broadcast channel (PBCH) block (SSB).

[0054] In one embodiment, the PCI is the PCI of the serving cell or a PCI different from the PCI of the serving cell.

[0055] In one embodiment, the information regarding the PCI associated with the downlink RS indicates the PCI, and the downlink RS is associated with the PCI indicated by the information regarding the PCI included in the request.

[0056] In one embodiment, the method further includes receiving the configuration of the downlink RS and the transmission power of the downlink RS before receiving the request.

[0057] In one embodiment, the information about the downlink RS includes an index of the downlink RS.

[0058] In one embodiment, the information regarding the PCI includes an indication of whether the PCI is the PCI of the serving cell or a PCI different from the PCI of the serving cell.

[0059] In one embodiment, the request is received in the DCI of one of the first CORESET and the second CORESET.

[0060] In one embodiment, the request is a PDCCH command carried in the DCI format; the downlink RS is an SSB; the information about the downlink RS is the SSB index of the SSB; the information about the PCI is the PCI; and determining the transmission power for the transmission of the PRACH preamble includes determining the spatial Tx filter and the transmission power for the transmission of the PRACH preamble based on the SSB index and the PCI included in the PDCCH command.

[0061] In one embodiment, the method further includes determining a spatial filter for transmitting the PRACH preamble based on the downlink RS and the PCI. In one embodiment, the spatial filter is a spatial filter used when receiving the downlink RS.

[0062] In one embodiment, determining the transmission power for transmitting the PRACH preamble includes: calculating the path loss as the difference between the transmission power of the downlink RS and the reference signal received power (RSRP) measured based on the downlink RS; and determining the transmission power for transmitting the PRACH preamble based on the calculated path loss.

[0063] In one embodiment, the request is received on the serving cell of the UE.

[0064] In one embodiment, the method further includes receiving configuration information that configures the UE via one or more of the following: a first set of downlink RSs having a first transmit power associated with a first PCI, wherein the first PCI is the PCI of the serving cell; a first PRACH configuration and a first set of PRACH preambles associated with the first PCI; a Transport Configuration Indicator (TCI) status list; a second set of downlink RSs having a second transmit power associated with a second PCI; and a second PRACH configuration and a second set of PRACH preambles associated with the second PCI. In one embodiment, the first PCI and the second PCI are different. In one embodiment, the PCI indicated in the request is one of the first PCI and the second PCI. In one embodiment, if the first PCI is indicated in the request, then the PRACH preamble indicated in the request is one of the first set of PRACH preambles, and if the second PCI is indicated in the request, then the PRACH preamble indicated in the request is one of the second set of PRACH preambles. In one embodiment, if the first PCI is indicated in the request, then the downlink RS indicated in the request is one of the first set of downlink RSs, and if the second PCI is indicated in the request, then the downlink RS indicated in the request is one of the second set of downlink RSs. In one embodiment, the UE is activated by a first TCI state from the TCI state list for the first CORESET and a second TCI state from the TCI state list for the second CORESET. In one embodiment, the first SSB set is configured with a first SSB transmission power, and the second SSB set is configured with a second SSB transmission power, wherein the values ​​of the first SSB transmission power and the second SSB transmission power are the same or different.

[0065] A corresponding embodiment of the UE is also disclosed. In one embodiment, a UE is adapted to receive from a network node a configuration of a first TAG ID and a second TAG ID in the serving cell, as well as a first CORESET with a first CORESET pool index value and a second CORESET with a second CORESET pool index value. The UE is also adapted to receive from the network node a request to transmit a PRACH preamble in the serving cell, wherein the request includes a PRACH preamble index associated with the PRACH preamble, information about a downlink reference RS, and information about a PCI associated with the downlink RS. The UE is also adapted to determine a transmission power for transmitting the PRACH preamble based on the information about the downlink RS and the information about the PCI included in the request; and to transmit the PRACH preamble according to the determined transmission power.

[0066] Embodiments of a method performed by a network node are also disclosed. In one embodiment, a method performed by a network node includes transmitting to a UE a first TAG ID and a second TAG ID in the serving cell, as well as a first CORESET having a first CORESET pool index value and a second CORESET having a second CORESET pool index value. The method further includes transmitting to the UE a request to transmit a PRACH preamble code in the serving cell, wherein the request includes a PRACH preamble code index associated with the PRACH preamble code, information about a downlink reference RS, and information about a PCI associated with the downlink RS.

[0067] A corresponding embodiment of a network node is also disclosed. In one embodiment, a network node is adapted to transmit to the UE a configuration of a first TAG ID and a second TAG ID in the serving cell, as well as a first CORESET with a first CORESET pool index value and a second CORESET with a second CORESET pool index value. The network node is also adapted to transmit to the UE a request to transmit a PRACH preamble code in the serving cell, wherein the request includes a PRACH preamble code index associated with the PRACH preamble code, information about a downlink reference RS, and information about a PCI associated with the downlink RS. Attached Figure Description

[0068] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate various aspects of this disclosure and, together with the description, serve to explain the principles of this disclosure.

[0069] Figure 1AThe new air interface (NR) time-domain structure with a subcarrier spacing of 15 kHz is shown; Figure 1B The NR physical time-frequency resource grid is shown; Figure 2 NR is shown ServingCellConfigCommon Information element (IE); Figure 3A An example of mapping a synchronization signal block (SSB) to a physical random access channel (PRACH) preamble is shown, where N = 1 / 2 and R = 32; Figure 3B An example of an SSB-to-PRACH preamble mapping is shown, where N=4 and R=4; Figure 4 An example of scheduling based on multiple downlink control information (DCI) from two transmit and receive points (TRPs) is shown; Figure 5A It shows SSB-MTC IE; Figure 5B It shows ServingCellConfig IE; Figure 5C It shows TCI-State IE; Figure 6 An example of a PRACH transmission to a TRP initiated by a Physical Downlink Control Channel (PDCCH) command received from a different TRP, according to an embodiment of the present disclosure, is shown. Figure 7 This is a flowchart illustrating a method performed by a user equipment (UE) according to an embodiment of the present disclosure; Figure 8 The operation of a UE, a first TRP (TRP1), and a second TRP (TRP2) according to an embodiment of the present disclosure is illustrated; Figure 9 An example of an alternative embodiment is shown, wherein a PDCCH command received from a first TRP initiates a PRACH transmission to both the first TRP and the second TRP; Figure 10 This illustrates an embodiment of a device for use according to the present disclosure. Figure 9 The flowchart of the UE operation example is shown in the image; Figure 11 Examples of communication systems according to some embodiments are shown; Figure 12 A UE according to some embodiments is shown; Figure 13 A network node according to some embodiments is shown; Figure 14Based on the block diagram of the host described in this article, the host can be... Figure 11 An example of a host computer; Figure 15 This is a block diagram illustrating a virtualized environment in which functions implemented by some embodiments can be virtualized; and Figure 16 A communication diagram is shown, illustrating a host communicating with a UE via a network node through a partial wireless connection, according to some embodiments. Detailed Implementation

[0070] The embodiments described below illustrate information enabling those skilled in the art to practice the embodiments, and depict the best mode for practicing the embodiments. Those skilled in the art will understand the concepts of this disclosure and recognize the application of these concepts, which are not specifically set forth herein, when reading the following description in conjunction with the accompanying drawings. It should be understood that these concepts and applications fall within the scope of this disclosure.

[0071] There are currently some challenges. The existing New Radio (NR) specifications do not explicitly specify which spatial filters should be used for Physical Random Access Channel (PRACH) transmissions. The general understanding is that for initial contention-based random access (CBRA) PRACH transmissions within PRACH resources associated with a Synchronization Signal Block (SSB), the User Equipment (UE) will use the spatial domain filter received by it from the SSB.

[0072] In addition, to determine the PRACH transmission power, the path loss was calculated as follows: = referencesSignalPower – Higher-level filtering RSRP in dBm If the PRACH transmission is based on contention-free random access (CFRA) and initiated by a physical downlink control channel (PDCCH) command, then according to the 3GPP Technical Specification (TS) 38.213, it is determined based on the downlink (DL) reference signal (RS). referenceSignalPower For this DL reference signal, the demodulation reference signal (DMRS) of the PDCCH command is a quasi-cooperative positioning (QCL). According to the following copied specification text, if the QCL type DRS associated with the PDCCH command is an SSB, then the SSB transmit power should be used as the reference signal power; otherwise, if the QCL type DRS is a periodic channel state information reference signal (CSI-RS), then the CSI-RS transmit power should be used as... referenceSignalPower It is speculated that, Higher-level filtering RSRP"This is the reference signal received power (RSRP) measured on QCL type D RS. However, this is not explicitly specified in the 3GPP specifications."

[0073] “ If the PRACH transmission from the UE is in response to the PDCCH command issued by the UE that triggered the contention-free random access procedure... The detection, and depending on the DM-RS of the PDCCH command as described in Clause 10.1 and its quasi-co-location DL RS, then ReferenceSignalPower is provided by ss-PBCH-BlockPower, or if the UE is configured for periodicity. The resources received by CSI-RS, or the PRACH transmissions associated with the link recovery process, are linked in the corresponding index as described in Clause 6. The aforementioned periodic CSI-RS configuration is associated, then referenceSignalPower is connected via ss-PBCH-BlockPower and powerControlOffsetSS is obtained, where powerControlOffsetSS provides the CSI-RS transmission power relative to SS / PBCH block transmission power offset [6, TS 38.214]. If powerControlOffsetSS is not provided to the UE, the UE assumes... The offset is set to 0 dB. If the active TCI state of the PDCCH providing the PDCCH command includes two RSs, the UE expects one RS to be... The qcl-Type is configured with 'typeD', and the UE uses the value provided by powerControlOffsetSS when applying it. Use an RS. " When a CFRA-based PRACH transmission intended for a second transmit and receive point (TRP) is initiated by a PDCCH command received from the first TRP, it is problematic to derive the spatial filter and / or transmit power of the PRACH transmission using the QCL-type RS associated with the PDCCH command, because the PRACH will be sent to the wrong TRP and / or have the wrong transmit power.

[0074] Certain aspects of this disclosure and its embodiments may provide solutions to these or other challenges. In one embodiment, a method is proposed for determining a spatial filter and / or transmit power for PRACH transmissions initiated by a PDCCH command in a serving cell configured with two timing advances (TAs). In one embodiment, the method is performed by a UE. In one embodiment, the method includes one or more of the following: • The UE receives a PDCCH command from the first TRP to transmit a PRACH to the second TRP, wherein the PDCCH command contains ○ PRACH Preamble Index ○ PRACH preamble mask ○ SSB Index ○ Information on the Physical Cell Identifier (PCI) associated with the SSB index • Determine the space transfer (Tx) filter and transfer power for PRACH transmission to the second TRP based on the PCI in the SSB and PDCCH commands indicated by the SSB index, for example, ○ Determine the spatial Tx filter based on SSB ○ Path loss is calculated as the difference between the configured SSB transmission power for the SSB and the measured RSRP based on the SSB. ○ Determine the transmission power based on path loss and other power control parameters • Transmit the PRACH preamble based on the determined spatial Tx filter and the transmission power calculated based on path loss.

[0075] In one embodiment, when a PRACH transmission to a second TRP is initiated by a PDCCH command received from a first TRP, the SSB index and PCI information indicated in the PDCCH command are used together to derive the spatial Tx filter and transmission power for the PRACH transmission.

[0076] Certain embodiments may provide one or more of the following technical advantages. Embodiments of this disclosure ensure that when more than one Timing Advance Group (TAG) or TA is configured for the serving cell, PRACH transmissions initiated by PDCCH commands are delivered to the intended TRP with the correct transmission power.

[0077] Note that TRP can be, for example, a network node, base station, antenna equipment, antenna panel, spatial relationship, Transmission Configuration Indicator (TCI) status, serving cell, cell, component carrier (CC), carrier, etc. The terms "TRP", "TAG", "Timing Advance Timer", and "CORESET Pool Index" are related and may sometimes be used interchangeably in the following text.

[0078] Note regarding PCI: The serving cell is always associated with a PCI. In one example embodiment, this PCI is configured by the "physCellId" in the Information Element (IE) ServingCellConfigCommon described in 3GPP TS 38.331 v17.2.0. Alternatively, the UE can be configured with an additional PCI using, for example, additionalPCI-ToAddModList-r17 in the ServingCellConfig IE, and the additional PCI is additionalPCI-r17 in the corresponding SSB-MTC-AdditionalPCI-r17. Multiple TRP operations are possible with or without an additional PCI.

[0079] Note regarding TAGs: A UE can be configured with two advance timing timers. When a TAG is configured for the serving cell, these timers can be associated with one TAG. Alternatively, a TAG can be associated with one advance timing timer, but the serving cell may have two TAGs configured, either using the existing IE of the TAG or through a new sub-TAG.

[0080] Figure 6An example of a PRACH transmission to one TRP initiated by a PDCCH command received from a different TRP is illustrated, wherein a PRACH transmission to TRP2 is initiated by a PDCCH command received from TRP1. SSB #n1 is transmitted from TRP1 with a transmission power of x dBm, and SSB #n2 is transmitted from TRP2 with a transmission power of y dBm. TRP1 is associated with PCI #k1 and Control Resource Set (CORESET) pool index 0, and TRP2 is associated with PCI #k2 and CORESET pool index 1. Furthermore, TRP1 is associated with TAG1, and TRP2 is associated with TAG2. This document discloses embodiments of a method for how a UE transmits PRACH to TRP2.

[0081] Figure 7 This is a flowchart illustrating a method performed by a UE according to an embodiment of the present disclosure. Optional steps are indicated by dashed lines / boxes. Furthermore, although these steps are shown in a specific order, they can be performed in any order. Figure 7 As shown, the method includes one or more of the following steps: Step 700: Configure the UE in the serving cell with one or more of the following: • A first CORESET with a first CORESET pool index and a second CORESET with a second CORESET pool index, wherein the first and second CORESET pool indices are different. • First TA and second TA, or first TAG identifier (ID) and second TAG ID Alternatively, a TAG ID can be associated with two time alignment timers. • A first set of SSBs having a first SSB transmission power associated with a first PCI, wherein the first PCI is the PCI of the serving cell. • The first PRACH configuration and the first PRACH preamble set associated with the first PCI • TCI Status List • A second set of SSBs with second SSB transmission power associated with the second PCI • The second PRACH configuration and the second PRACH preamble set associated with the second PCI.

[0082] The UE is activated by the first TCI state from the TCI state list for the first CORESET and the second TCI state from the TCI state list for the second CORESET, wherein... • The first PCI is the PCI of the serving cell and is defined by the IE as described in 3GPP TS 38.331 v17.2.0. ServingCellConfigCommon Configure using "physCellId" • The second PCI is the IE described in 3GPP TS 38.331 v17.2.0. ServingCellConfig In additional PCI - ToAddModList - r17 Configuration SSB-MTC-AdditionalPCI-r17 “ in additional PCI-r17 "Additional PCI configuration."

[0083] In step 700, the first and second TAG IDs are different and are associated with the first and second time alignment timers, respectively. Alternatively, the first and second TAG IDs can be the same.

[0084] In step 700, the first and second CORESET pool indices are associated with the first and second TAG IDs, respectively, or with the first and second timers if the first and second TAG IDs are the same, i.e., one TAG ID has two timers.

[0085] In step 700, the first SSB set is configured with a first SSB transmission power, and the second SSB set is configured with a second SSB transmission power. The values ​​of the first and second SSB transmission powers may be the same or different.

[0086] In step 700, when additionalPCI-ToAddModList-r17 is configured in the IEServingCellConfig of the serving cell in 3GPP TS 38.331 v17.2.0, the first PCI is different from the second PCI.

[0087] In step 700, the first and second PCIs are associated with the first and second PCI indices, respectively, wherein the PCI indices are as described in step 702.

[0088] In step 700, one of the following two associations is possible: • The first core set is associated with the first PCI, and the second core set is associated with the second PCI. • The first CORESET is associated with the second PCI, and the second CORESET is associated with the first PCI.

[0089] Step 702: The UE receives the PDCCH command in the downlink control information (DCI) format 1_0 carried by the PDCCH in the first CORESET, wherein the PDCCH command contains • PRACH preamble index • PRACH preamble mask • First SSB Index • PCI index associated with the first SSB index The PCI index is an integer and has values ​​from 0 to 1. maxNrofAdditionalPCI-r17 The value of , where maxNrofAdditionalPCI-r17 It is predefined or configured, and • If the PCI index value is zero or the PCI index field does not exist, it indicates the first PCI, i.e., the PCI of the serving cell. • Otherwise, if the PCI index value is non-zero, then the PCI index corresponds to the use of ServingCellConfig In additionalPCI-ToAddModList-r17 Configuration SSB-MTC-AdditionalPCI-r17 of additional PCIIndex-r17 The corresponding PCI is the second PCI, and it is determined by... SSB-MTC-AdditionalPCI-r17 In PhysCellId Provided.

[0090] If not configured in the service cell additionalPCI-ToAddModList-r17 If so, the PCI index will always be set to 0 or the field will not exist. If the serving cell configuration contains... additional PCI-ToAddModList- r17 Then the PCI index can be set to 0 to... maxNrofAdditionalPCI-r17 Any value within the range.

[0091] If the PRACH preamble index is non-zero, whether the PRACH preamble index comes from the first or second PRACH preamble set is determined by the PCI index contained in the PDCCH command. If the PCI index indicates the first PCI, the PRACH preamble comes from the first PRACH preamble set; otherwise, the PRACH preamble comes from the second PRACH preamble set.

[0092] If the preamble index is zero, and if a dedicated CFRA PRACH resource (e.g., via a RACH-ConfigDedicated IE) is not configured for the PCI indicated by the PCI index, then the PRACH transport is a CBRA-based PRACH transport. The PRACH preamble is selected from a set of PRACH preambles associated with the PCI indicated by the PCI index in the PDCCH command, where the PCI is one of the first and second PCIs, and the PRACH preamble set is one of the first and second PRACH preamble sets.

[0093] In step 702, if the preamble index is zero, and an SSB associated with a CFRA resource is provided in the dedicated RACH configuration IE (e.g., RACH-ConfigDedicated IE) for the PCI indicated by the PCI index in the PDCCH command, where a one-to-one mapping between the preamble index and the SSB index is provided for the SSB list, then if the PCI index indicates the first PCI, the UE selects an SSB with an SSB-RSRP higher than the configured threshold rsrp-ThresholdSSB in the first SSB set, and selects the PRACH preamble corresponding to the selected SSB; otherwise, the UE selects an SSB with an SSB-RSRP higher than the configured threshold in the second SSB set, and selects the PRACH preamble corresponding to the selected SSB.

[0094] In step 702, if the preamble index is zero, and a CSI-RS associated with a CFRA resource is provided in the dedicated RACH configuration IE (e.g., RACH-ConfigDedicated IE) for the PCI indicated by the PCI index in the PDCCH command, where a one-to-one mapping between the preamble index and CSI-RS resources is provided for the SSB list, a first set of CSI-RSs is associated with a first PCI index, and a second set of CSI-RSs is associated with a second PCI index. If the PCI index indicates the first PCI, then the UE selects a CSI-RS with a CSI-RSRP higher than the configured threshold rsrp-ThresholdCSI-RS in the first set of CSI-RSs, and selects a PRACH preamble corresponding to the selected CSI-RS; otherwise, the UE selects a CSI-RS with a CSI-RSRP higher than the configured threshold in the second set of CSI-RSs, and selects a PRACH preamble corresponding to the selected CSI-RS.

[0095] In step 702, if the PCI index indicates a first PCI, then the first SSB index is associated with the first SSB set, and if the PCI index indicates a second PCI, then the first SSB index is associated with the second SSB set.

[0096] Step 704: The UE determines the spatial domain Tx filter and transmission power for the PRACH transmission triggered by the PDCCH command. In one embodiment, this determination step includes: • If the PRACH preamble index is nonzero, the spatial domain Tx filter is determined based on the first SSB index indicated by the first SSB index and the PCI index contained in the PDCCH command. • If the PRACH preamble index is nonzero, the path loss is calculated based on the configured SSB transmit power for the first SSB and the previously measured RSRP for the first SSB.

[0097] ○ If the PCI index included in the PDCCH command indicates the first PCI, i.e., the serving cell PCI, then the first SSB transmission power is used, and the first SSB transmission power is determined by the... ServingCellConfigCommon IE configuration ss-PBCH- BlockPower Give Otherwise, if the PCI index indicates a second PCI that is not the serving cell PCI, then the second SSB transmission power is used, and the second SSB transmission power is determined by... ss-PBCH-BlockPower-r17 Give, the ss-PBCH-BlockPower-r17 With the same value as the PCI index additional PCIIndex-r17 Configured in the associated SSB-MTC-AdditionalPCI-r17.

[0098] • If the PRACH preamble index is zero and provides an SSB associated with the CFRA resource for the PCI indicated by the PCI index in the PDCCH command, ○ The spatial domain Tx filter is determined based on the selected SSB associated with the PCI indicated by the PCI index, or ○ Determine the spatial domain Tx filter based on the selected CSI-RS associated with the PCI indicated by the PCI index. ○ Calculate path loss based on the configured SSB / CSI-RS transmission power for the selected SSB / CSI-RS and the previously measured RSRP based on the selected SSB / CSI-RS. ■ If the PCI index included in the PDCCH command indicates the first PCI, i.e. the serving cell PCI, then the first SSB transmission power is used.

[0099] ■ Otherwise, if the PCI index contained in the PDCCH command indicates a second PCI, then the second SSB is used to transmit power.

[0100] • Calculate the transmission power based on the determined path loss and additional power control parameters. In step 704, determining the spatial Tx filter based on the first SSB indicated by the first SSB index and the PCI index includes using the same spatial domain Rx filter previously used to receive the first SSB as the spatial domain Tx filter.

[0101] In step 704, the path loss calculation based on the SSB transmission power for the SSB and the previously measured RSRP based on the SSB includes calculating the path loss in dB by subtracting the RSRP in dBm from the SSB transmission power in dBm.

[0102] Step 706: The UE transmits the PRACH preamble based on the determined spatial domain Tx filter and the calculated transmission power. In step 706, the PRACH preamble is transmitted at the PRACH timing indicated by the preamble mask, the first SSB index, and the PCI index.

[0103] Note steps 704 and 706 above. If the serving cell is not configured with additionalPCI-ToAddModList-r17, the SSB index is explicit. If additionalPCI-ToAddModList-r17 is configured, the UE needs to use the PCI index along with the SSB index to determine the correct SSB beam to use in these steps.

[0104] Figure 8 The operation of a UE 800, a first TRP (TRP1) 802, and a second TRP (TRP2) 804 according to one embodiment of this disclosure is illustrated. Optional steps are indicated by dashed lines / boxes. Furthermore, although these steps are shown in a specific order, they can be performed in any order. The first TRP 802 is associated with a first CORESET pool having CORSET pool index = 0 in this example, and is also associated with a first TAG (TAG#0) and a first PCI (PCI #0). The second TRP 804 is associated with a second CORESET pool having CORSET pool index = 1 in this example, and is also associated with a second TAG (TAG#1) and a second PCI (PCI #1). As shown, the process includes any one or more of steps 806-822.

[0105] The first TRP 802 transmits the first SSB (SSB #1) at the first TX power (P0) (step 806), and the second TRP 804 transmits the second SSB (SSB #2) at the second TX power (P1) (step 808). The UE 800 measures the first RSRP (RSRP #1) based on the first SSB (SSB #1) and the second RSRP (RSRP #2) based on the second SSB (SSB #2) (step 810).

[0106] In this example, optionally, UE 800 receives a PDCCH command indicating a first PRACH preamble (PRACH preamble #1), a first SSB (SSB #1), and a first PCI (step 812). UE 800 determines the spatial TX filter and TX power of the first PRACH preamble (PRACH preamble #1) based on the first SSB (SSB #1), the first RSRP (RSRP #1), and the first PCI (step 814). UE 800 transmits the first PRACH preamble (PRACH preamble #1) using (i.e., with) the spatial TX filter and TX power determined in step 814 (step 816).

[0107] UE 800 receives a PDCCH command indicating a second PRACH preamble (PRACH preamble #2), a second SSB (SSB #2), and a second PCI (step 818). UE 800 determines the spatial TX filter and TX power of the second PRACH preamble (PRACH preamble #2) based on the second SSB (SSB #2), the second RSRP (RSRP #2), and the second PCI (step 820). UE 800 transmits the second PRACH preamble (PRACH preamble #2) using the spatial TX filter and TX power determined in step 820 (step 822).

[0108] The following describes an alternative embodiment related to the scenario where a PDCCH command received from one of the TRPs initiates a PRACH transmission to both TRPs. An example of this scenario is in Figure 9 As shown in the image.

[0109] Figure 10 This illustrates an embodiment of a device for use according to the present disclosure. Figure 9 The flowchart illustrates the operation of a UE as an example. Optional steps are indicated by dashed lines / boxes. Furthermore, although these steps are shown in a specific order, they can be performed in any order. Figure 10 As shown, the UE performs one or more of the following steps: • Step 1000: The serving cell configures the UE with: ○ A first CORESET with a first coreset pool index and a second CORESET with a second coreset pool index, wherein the first and second coreset pool indices are different. ○ The first and second tags associated with the serving cell, or alternatively, a tag other than the first and second advance timing timers. ○ The first set of SSBs, each SSB having an SSB index associated with the first PCI. ○ List of PRACH preambles ○ TCI status list for the first and second CORESETs ○ The second set of SSBs associated with the second PCI The UE is activated by the first TCI state from the TCI state list for the first CORESET and the second TCI state from the TCI state list for the second CORESET.

[0110] • Step 1002: The UE receives a PDCCH command in downlink DCI format carried by the PDCCH in the first CORESET, wherein the PDCCH command contains ○ First PRACH preamble index, and optional second PRACH preamble index ○ First SSB Index and Second SSB Index ○ First preamble mask and optional second preamble mask ○ The first PCI index associated with the first SSB index, and the second PCI index associated with the second SSB index. Note that in some cases, the first PCI index may not be explicitly indicated by the PDCCH command. In such cases, the UE assumes a predefined value for the first PCI index. For example, in one embodiment, the UE may assume that the first PCI index has a value of 0, in which case the first PCI corresponds to the serving cell TRP.

[0111] Also note that if the UE is not configured with additionalPCI-ToAddModList, the first PCI and the second PCI are the same, and the PDCCH command provides index 0 for the PCI, or the PCI index is not included in the PDCCH command.

[0112] • Step 1004: The UE determines a first spatial domain Tx filter and a second spatial domain Tx filter for the first PRACH transmission and the second PRACH transmission triggered by the PDCCH command, respectively. In one embodiment, this determination includes: ○ The first spatial domain Tx filter is determined based on the first SSB indicated by the first SSB index. The second spatial domain Tx filter is determined based on the second SSB indicated by the second SSB index. • Step 1006: The UE determines a first transmission power and a second transmission power for the first PRACH transmission and the second PRACH transmission triggered by the PDCCH command, respectively. In one embodiment, this determination includes: ○ Calculate the first path loss based on the SSB transmission power of the first SSB in the first configuration and the first RSRP based on the previously measured first SSB. ○ Calculate the second path loss based on the SSB transmission power of the second SSB in the second configuration and the second RSRP based on the previously measured second SSB. ○ Calculate the first transmission power based on the first determined path loss and the first set of power control parameters. ○ Calculate the second transmission power based on the second determined path loss and the second power control parameter set. • Step 1008: The UE transmits the first PRACH preamble based on the determined first spatial domain Tx filter and the calculated first transmission power, and transmits the second PRACH preamble based on the determined second spatial domain Tx filter and the calculated second transmission power.

[0113] In step 1004, determining the first spatial Tx filter based on the first SSB indicated by the first SSB index includes using the same first spatial domain Rx filter previously used to receive the first SSB as the first spatial domain Tx filter.

[0114] In step 1004, determining the second spatial Tx filter based on the second SSB indicated by the second SSB index includes using the same second spatial domain Rx filter previously used to receive the second SSB as the second spatial domain Tx filter.

[0115] In step 1006, calculating the first path loss based on the configured first SSB transmission power for the first SSB and the previously measured first RSRP based on the first SSB includes subtracting the first RSRP from the first SSB transmission power.

[0116] In step 1006, the calculation of the second path loss based on the configured second SSB transmission power for the second SSB and the previously measured second RSRP based on the second SSB includes subtracting the second RSRP from the second SSB transmission power.

[0117] In step 1008, the first PRACH preamble is transmitted at the first PRACH timing indicated by the first preamble mask and the first SSB index.

[0118] In step 1008, the second PRACH preamble is transmitted at the second PRACH timing indicated by the second preamble mask and the second SSB index.

[0119] Regarding the steps above, note the SSB index. If the serving cell does not have an additionalPCI-ToAddModList configured, the SSB index is explicit. If an additionalPCI-ToAddModList is configured, the UE needs to use the PCI index along with the SSB index to determine the correct SSB beam to use in these steps.

[0120] Figure 11 An example of a communication system 1100 according to some embodiments is shown.

[0121] In the example, communication system 1100 includes a telecommunications network 1102, which includes an access network 1104 such as a radio access network (RAN) and a core network 1106, which includes one or more core network nodes 1108. Access network 1104 includes one or more access network nodes, such as network nodes 1110A and 1110B (one or more of which may be generally referred to as network node 1110) or any other similar 3GPP access node or non-3GPP access point (AP). Network node 1110 facilitates direct or indirect connection of user equipment (UE), such as connecting UE 1112A, 1112B, 1112C, and 1112D (one or more of which may be generally referred to as UE 1112) to core network 1106 via one or more wireless connections.

[0122] Examples of wireless communication via wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information without the use of wires, cables, or other conductors. Furthermore, in various embodiments, communication system 1100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that can facilitate or participate in the transmission of data and / or signals, whether via wired or wireless connections. Communication system 1100 may include any type of communication, telecommunications, data, cellular, radio network, and / or other similar system and / or be connected to any type of communication, telecommunications, data, cellular, radio network, and / or other similar system via an interface.

[0123] UE 1112 can be any communication device of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with network node 1110 and other communication devices. Similarly, network node 1110 is arranged, capable, configured, and / or operable to communicate directly or indirectly with UE 1112 and / or with other network nodes or devices in telecommunication network 1102 to enable and / or provide network access (such as wireless network access) and / or to perform other functions (such as management in telecommunication network 1102).

[0124] In the depicted example, core network 1106 connects network node 1110 to one or more hosts (such as host 1116). These connections may be direct or indirect, via one or more intermediate networks or devices. In other examples, network nodes may be directly coupled to hosts. Core network 1106 includes one or more core network nodes (e.g., core network node 1108) constructed from hardware and software components. The characteristics of these components may be substantially similar to those described with respect to UEs, network nodes, and / or hosts, such that the description generally applies to the corresponding components of core network node 1108. Example core network nodes include one or more of the following: Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier Dehiding Function (SIDF), Unified Data Management (UDM), Secure Edge Protection Agent (SEPP), Network Open Function (NEF), and / or User Plane Function (UPF).

[0125] Host 1116 may be owned or controlled by a service provider other than the operator or provider of telecommunications network 1102 and / or access network 1104, and may be operated by or on behalf of the service provider. Host 1116 may host various applications to provide one or more services. Examples of such applications include live and pre-recorded audio / video content, data collection services (such as retrieving and compiling data on various environmental conditions detected by multiple UEs), analytics functionality, social media, functionality for controlling or otherwise interacting with remote devices, functionality for alarm and monitoring centers, or any other such functionality performed by a server.

[0126] on the whole, Figure 11The communication system 1100 enables connectivity between the UE, network nodes, and hosts. In that sense, the communication system 1100 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 second, third, fourth, or fifth generation (2G, 3G, 4G, or 5G) standards, or any applicable future generation standard (e.g., sixth generation (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 suitable wireless communication standards, such as 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.

[0127] In some examples, telecommunications network 1102 is a cellular network implementing 3GPP standardized features. Therefore, telecommunications network 1102 can support network slicing to provide different logical networks to different devices connected to it. For example, telecommunications network 1102 can provide ultra-reliable low-latency communication (URLLC) services to some UEs while providing enhanced mobile broadband (eMBB) services to other UEs, and / or massive machine-type communication (mMTC) / massive Internet of Things (IoT) services to yet another UE.

[0128] In some examples, UE 1112 is configured to transmit and / or receive information without direct human interaction. For example, the UE may be designed to transmit information to access network 1104 according to a predetermined schedule when triggered by internal or external events or in response to a request from access network 1104. Additionally, the UE may be configured to operate in single-radio access technology (RAT), multi-RAT, or multi-standard modes. For example, the UE may operate with any or a combination of WiFi, New Radio (NR), and LTE, i.e., configured for multiple radio dual connectivity (MR-DC), such as Evolved UMTS Terrestrial Radio Access Network (E-UTRAN) NR-Dual Connectivity (EN-DC).

[0129] In the example, hub 1114 communicates with access network 1104 to facilitate indirect communication between one or more UEs (e.g., UE 1112C and / or 1112D) and network nodes (e.g., network node 1110B). In some examples, hub 1114 may be a controller, router, content source, and analytics tool, or any other communication device described herein with respect to a UE. For example, hub 1114 may be a broadband router for enabling access to core network 1106 for a UE. As another example, hub 1114 may be a controller that sends commands or instructions to one or more actuators in a UE. Commands or instructions may be received from the UE, network node 1110, or may be received via executable code, scripts, procedures, or other instructions in hub 1114. As another example, hub 1114 may be a data collector that acts as a temporary storage device for UE data, and in some embodiments, data analysis or other processing may be performed. As another example, hub 1114 may be a content source. For example, for a UE that is a virtual reality (VR) headset, display, speaker, or other media delivery device, hub 1114 can retrieve VR assets, video, audio, or other media or data related to sensory information via network nodes. Hub 1114 then provides the VR assets, video, audio, or other media or data related to sensory information to the UE either directly, after performing local processing, and / or after adding additional local content. In another example, hub 1114 acts as a proxy server or coordinator for the UE, particularly if one or more of the UEs are low-power IoT devices.

[0130] Hub 1114 may have a constant / persistent or intermittent connection to network node 1110B. Hub 1114 may also be configured with different communication schemes and / or scheduling between hub 1114 and UEs (e.g., UEs 1112C and / or 1112D) and between hub 1114 and core network 1106. In other examples, hub 1114 is connected to core network 1106 and / or one or more UEs via a wired connection. Furthermore, hub 1114 may be configured to connect to a machine-to-machine (M2M) service provider via access network 1104 and / or to another UE via a direct connection. In some scenarios, a UE can establish a wireless connection to network node 1110 while still being connected via hub 1114, either via a wired or wireless connection. In some embodiments, hub 1114 may be a dedicated hub, that is, a hub whose primary function is to route communication from network node 1110B to UE / and vice versa. In other embodiments, hub 1114 may be a non-dedicated hub, that is, a device capable of operating to route communication between UE and network node 1110b, but also capable of operating as a communication start and / or end point for certain data channels.

[0131] Figure 12 A UE 1200 according to some embodiments is illustrated. As used herein, UE refers to a device capable of, configured to, arranged to, and / or operable for wireless communication with network nodes and / or other UEs. Examples of UEs include, but are not limited to, smartphones, mobile phones, cellular phones, Voice over Internet Protocol (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, tablets, 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 3GPP, including Narrowband Internet of Things (NB-IoT) UEs, Machine Type Communication (MTC) UEs, and / or Enhanced MTC (eMTC) UEs.

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

[0133] UE 1200 includes processing circuitry 1202, which is operatively coupled via bus 1204 to input / output interface 1206, power supply 1208, memory 1210, communication interface 1212, and / or any other component, or any combination thereof. Some UEs may utilize... Figure 12 All or a subset of the components shown. The level of integration between components can vary from one UE to another. Furthermore, some UEs may contain multiple instances of components, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0134] Processing circuitry 1202 is configured to process instructions and data and can be configured to implement any sequential state machine that operates to execute instructions stored in memory 1210 as a machine-readable computer program. Processing circuitry 1202 can 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 along with appropriate firmware; one or more stored computer programs, a general-purpose processor such as a microprocessor or digital signal processor (DSP), along with appropriate software; or any combination of the above. For example, processing circuitry 1202 may include multiple central processing units (CPUs).

[0135] In the example, input / output interface 1206 can be configured to provide one or more interfaces to input devices, output devices, 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, other output devices, or any combination thereof. Input devices can allow users to capture information into UE 1200. Examples of input devices include touch-sensitive or presence-sensitive displays, cameras (e.g., digital cameras, digital camcorders, webcams, etc.), microphones, sensors, mice, trackballs, orientation pads, trackpads, scroll wheels, smart cards, etc. Presence-sensitive displays may include capacitive or resistive touch sensors to sense input from the user. Sensors may be, for example, accelerometers, gyroscopes, tilt sensors, force sensors, magnetometers, light sensors, proximity sensors, biosensors, etc., or any combination thereof. Output devices can use the same type of interface port as input devices. For example, a Universal Serial Bus (USB) port can be used to provide both input and output devices.

[0136] In some embodiments, power supply 1208 is configured as a battery or battery pack. Other types of power sources, such as external power sources (e.g., electrical outlets), photovoltaic devices, or power cells, can be used. Power supply 1208 may further include power supply circuitry for delivering power from power supply 1208 itself and / or external power sources to various parts of UE 1200 via an interface or input circuitry such as a power cable. The delivered power can be used, for example, for charging power supply 1208. The power supply circuitry can perform any formatting, conversion, or other modification on the power from power supply 1208 to adapt the power to the corresponding components of the UE 1200 being powered.

[0137] Memory 1210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable ROM (EPROM), electrical EPROM (EEPROM), disk, optical disk, hard disk, removable magnetic tape, flash drive, etc. In one example, memory 1210 includes one or more applications 1214 (such as an operating system, web browser application, widget, gadget engine, or other application) and corresponding data 1216. Memory 1210 can store any operating system or combination of operating systems from a wide variety of operating systems used by UE 1200.

[0138] The memory 1210 can be configured to include multiple physical drive units such as a redundant array of independent disks (RAID), flash memory, USB flash drive, external hard drive, thumb drive, pen drive, key drive, high-density digital universal disc (HD-DVD) optical disc drive, internal hard drive, Blu-ray disc drive, holographic digital data storage (HDDS) optical disc drive, external mini dual in-line memory module (DIMM), synchronous dynamic RAM (SDRAM), external micro DIMM SDRAM, tamper-proof smart card memory such as a Universal Integrated Circuit Card (UICC) (including one or more Subscriber Identity Modules (SIMs) such as Universal SIM (USIM) and / or Internet Protocol Multimedia Service Identity Module (ISIM)), other memory, or any combination thereof. The UICC can be, for example, an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC commonly referred to as a "SIM card". The memory 1210 can allow the UE 1200 to access instructions, applications, etc., stored on temporary or non-temporary storage media to offload or upload data. Articles of manufacture, such as those utilizing communication systems, may be tangibly embodied in or contained in memory 1210, which may be or include a device-readable storage medium.

[0139] Processing circuitry 1202 can be configured to communicate with an access network or other network using communication interface 1212. Communication interface 1212 may include one or more communication subsystems and may include or be communicatively coupled to antenna 1222. Communication interface 1212 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., a network node in the access network or another UE). Each transceiver may include a transmitter 1218 and / or a receiver 1220 adapted to provide network communication (e.g., optical, electrical, frequency allocation, etc.). Furthermore, transmitter 1218 and receiver 1220 may be coupled to one or more antennas (e.g., antenna 1222) and may share circuitry, software, or firmware, or alternatively, transmitter 1218 and receiver 1220 may be implemented separately.

[0140] In the illustrated embodiments, the communication functions of the communication interface 1212 may include cellular communication, WiFi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communication such as Bluetooth and NFC, location-based communication such as using a Global Positioning System (GPS) to determine location, another similar communication function, 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 Multiplexing Access (CDMA), Wideband CDMA (WCDMA), GSM, LTE, NR, UMTS, WiMax, Ethernet, Transmission Control Protocol / Internet Protocol (TCP / IP), Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), Fast User Datagram Protocol Internet Connection (QUIC), Hypertext Transfer Protocol (HTTP), etc.

[0141] Regardless of the sensor type, the UE can provide the output of data captured by its sensors via its communication interface 1212 or via a wireless connection to a network node. Data captured by the UE's sensors can be transmitted via another UE via a wireless connection to a network node. The output can be periodic (e.g., every 15 minutes if it reports the sensed temperature), random (e.g., balancing the load of reports from several sensors), responsive to a triggered event (e.g., sending an alarm when humidity is detected), responsive to a request (e.g., a user-initiated request), or a continuous stream (e.g., live video feed of a patient).

[0142] As another example, the UE includes actuators, motors, or switches associated with a communication interface configured to receive wireless input from a network node via a wireless connection. The state of the actuator, motor, or switch can change in response to the received wireless input. For example, the UE may include a motor for adjusting the control surfaces or rotors of a drone in flight based on the received input, or for adjusting the motor of a robotic arm performing medical procedures based on the received input.

[0143] When a UE is in the form of an IoT device, it can be a device for use in one or more application domains, including but not limited to urban wearable technology, extended industrial applications, and healthcare. Non-limiting examples of such IoT devices are devices or devices embedded in the following: connected refrigerators or freezers, televisions, connected lighting fixtures, electricity meters, robotic vacuum cleaners, voice-controlled smart speakers, home security cameras, motion detectors, thermostats, smoke detectors, door / window sensors, flood / humidity sensors, electric door locks, connected doorbells, heat pump-like air conditioning systems, autonomous vehicles, monitoring systems, weather monitoring devices, vehicle parking monitoring devices, electric vehicle charging stations, smartwatches, fitness trackers, head-mounted displays for augmented reality (AR) or VR, wearable devices for haptic or sensory enhancement, sprinklers, animal or object tracking devices, sensors for monitoring plants or animals, industrial robots, unmanned aerial vehicles (UAVs), and any kind of medical device such as heart rate monitors or remotely controlled surgical robots. (Except as per the above...) Figure 12 In addition to the other components described in UE 1200 shown, UEs in the form of IoT devices include circuitry and / or software that depend on the intended application of the IoT device.

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

[0145] In practice, any number of UEs can be used together for a single use case. For example, the first UE can be an unmanned aerial vehicle (UAV) or can be integrated into the UAV and provide the UAV's speed information (obtained via a speed sensor) to a second UE, which acts as a remote controller for operating the UAV. When a user makes a change from the remote controller, the first UE can adjust a throttle valve on the UAV (e.g., by controlling an actuator) to increase or decrease the UAV's speed. The first and / or second UEs can also include more than one of the functionalities described above. For example, the UE can include sensors and actuators and handle the transmission of data from both the speed sensor and the actuator.

[0146] Figure 13A network node 1300 according to some embodiments is shown. As used herein, a network node refers to a device that is capable of, configured to, arranged to, and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or devices in a telecommunications network. Examples of network nodes include, but are not limited to, APs (e.g., radio APs) and base stations (BSs) (e.g., radio BSs, Node Bs, evolved Node Bs (eNBs), and NR Node Bs (gNBs)).

[0147] BSs can be classified based on the coverage they provide (or, in other words, their transmit power levels), and therefore, depending on the coverage provided, a BS can be called a femtoBS, picoBS, microBS, or macroBS. A BS can be a relay node or a relay donor node for control relays. Network nodes can also include one or more (or all) portions of a distributed radio BS, such as a centralized digital unit and / or a remote radio unit (RRU) sometimes referred to as a remote radio headend (RRH). Such an RRU may or may not be integrated with an antenna as an antenna-integrated radio device. A portion of a distributed radio BS can also be referred to as a node in a distributed antenna system (DAS).

[0148] Other examples of network nodes include multi-transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) devices such as MSR BS, network controllers such as radio network controllers (RNC) or BS controllers (BSC), base transceiver stations (BTS), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCE), operation and maintenance (O&M) nodes, operation support system (OSS) nodes, self-organizing network (SON) nodes, location nodes (such as evolved servicing mobile location centers (E-SMLC)), and / or minimized drive tests (MDT).

[0149] Network node 1300 includes processing circuitry 1302, memory 1304, communication interface 1306, and power supply 1308. Network node 1300 may consist of multiple physically separate components (e.g., Node B components and RNC components, or BTS components and BSC components, etc.), each of which may have its own corresponding components. In some scenarios where network node 1300 includes multiple separate components (e.g., BTS and BSC components), one or more of these separate components may be shared among several network nodes. For example, a single RNC can control multiple Node Bs. In such scenarios, each unique Node B and RNC pair may be considered a single separate network node in some instances. In some embodiments, network node 1300 may be configured to support multiple RATs. In such embodiments, some components may be replicated (e.g., separate memory 1304 for different RATs) and some components may be reused (e.g., antenna 1310 may be shared by different RATs). Network node 1300 may also include multiple sets of various described components for integrating into network node 1300 different wireless technologies, such as GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, RFID, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chips or chipsets and other components within network node 1300.

[0150] Processing circuitry 1302 may include a combination of one or more of a microprocessor, controller, microcontroller, CPU, DSP, ASIC, FPGA, or any other suitable computing device or resource, or a combination of hardware, software, and / or coding logic operable to provide functionality of network node 1300, either alone or in combination with other network node 1300 components such as memory 1304.

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

[0152] Memory 1304 may include any form of volatile or non-volatile computer-readable memory, including, but not limited to, permanent storage devices, solid-state memory, remotely mounted memory, magnetic media, optical media, RAM, ROM, mass storage media (e.g., hard disks), removable storage media (e.g., flash drives, CDs, or DVDs), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory that stores information, data, and / or instructions that can be used by processing circuitry 1302. Memory 1304 may store any suitable instructions, data, or information, including applications, software, computer programs, and / or other instructions that contain one or more of logic, rules, codes, tables, and can be executed by processing circuitry 1302 and utilized by network node 1300. Memory 1304 may be used to store any calculations performed by processing circuitry 1302 and / or any data received via communication interface 1306. In some embodiments, processing circuitry 1302 and memory 1304 are integrated.

[0153] Communication interface 1306 is used in wired or wireless communication of signaling and / or data between network nodes, access networks, and / or UEs. As illustrated, communication interface 1306 includes one or more ports / terminals 1316 for transmitting data to and receiving data from the network, for example, via a wired connection. Communication interface 1306 also includes radio front-end circuitry 1318 that may be coupled to antenna 1310 or, in some embodiments, is part of antenna 1310. Radio front-end circuitry 1318 includes filter 1320 and amplifier 1322. Radio front-end circuitry 1318 may be connected to antenna 1310 and processing circuitry 1302. Radio front-end circuitry may be configured to modulate the signal transmitted between antenna 1310 and processing circuitry 1302. Radio front-end circuitry 1318 may receive digital data to be transmitted to other network nodes or UEs via a wireless connection. Radio front-end circuitry 1318 may use a combination of filter 1320 and / or amplifier 1322 to convert digital data into radio signals with appropriate channel and bandwidth parameters. Radio signals can then be transmitted via antenna 1310. Similarly, upon receiving data, antenna 1310 can collect radio signals and then convert them into digital data via radio front-end circuitry 1318. The digital data can then be transmitted to processing circuitry 1302. In other embodiments, communication interface 1306 may include different components and / or different combinations of components.

[0154] In some alternative embodiments, network node 1300 does not include a separate radio front-end circuitry 1318; instead, processing circuitry 1302 includes radio front-end circuitry and is connected to antenna 1310. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1312 is part of communication interface 1306. In other embodiments, communication interface 1306 includes one or more ports or terminals 1316, radio front-end circuitry 1318, and RF transceiver circuitry 1312 as part of a radio unit (not shown), and communication interface 1306 communicates with baseband processing circuitry 1314, which is part of a digital unit (not shown).

[0155] Antenna 1310 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals. Antenna 1310 may be coupled to radio front-end circuitry 1318 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, antenna 1310 is separate from network node 1300 and may be connected to network node 1300 via an interface or port.

[0156] Antenna 1310, communication interface 1306, and / or processing circuitry 1302 can be configured to perform any receive operation and / or certain acquire operation described herein as being performed by network node 1300. Any information, data, and / or signals can be received from the UE, another network node, and / or any other network device. Similarly, antenna 1310, communication interface 1306, and / or processing circuitry 1302 can be configured to perform any transmit operation described herein as being performed by network node 1300. Any information, data, and / or signals can be transmitted to the UE, another network node, and / or any other network device.

[0157] Power supply 1308 provides power to various components of network node 1300 in a form suitable for the respective components (e.g., at the voltage and current levels required by each respective component). Power supply 1308 may further include or be coupled to power management circuitry to power the components of network node 1300 for performing the functionality described herein. For example, network node 1300 may be connectable to an external power source (e.g., mains or electrical outlet) via input circuitry or interface such as a cable, thereby supplying power to the power circuitry of power supply 1308. As another example, power supply 1308 may include a power source in the form of a battery or battery pack, connected to or integrated into the power circuitry. The battery can provide backup power in the event of an external power failure.

[0158] Embodiments of network node 1300 may include, except Figure 13Additional components beyond those shown herein are used to provide certain aspects of the functionality of the network node, including any functionality described herein and / or any functionality necessary to support the topics described herein. For example, network node 1300 may include user interface devices for allowing information to be input to and output from network node 1300. This allows users to perform diagnostic, maintenance, repair, and other management functions for network node 1300.

[0159] Figure 14 It is based on the various aspects described in this article, and may be Figure 11 A block diagram of host 1400 in an embodiment of host 1116. As used herein, host 1400 can be or include various combinations of hardware and / or software, including standalone servers, blade servers, cloud-implemented servers, distributed servers, virtual machines, containers, or processing resources in a server farm. Host 1400 can provide one or more services to one or more UEs.

[0160] Host 1400 includes processing circuitry 1402, which is operatively coupled via bus 1404 to input / output interface 1406, network interface 1408, power supply 1410, and memory 1412. Other components may be included in other embodiments. These components may be characterized substantially similarly to those relating to... Figure 12 and Figure 13 The features described in the previous diagrams of the apparatus make their description generally applicable to the corresponding components of host 1400.

[0161] Memory 1412 may include one or more computer programs, including one or more host applications 1414 and data 1416, the data 1416 including user data (e.g., data generated by the UE for the host 1400 or data generated by the host 1400 for the UE). Embodiments of the host 1400 may utilize only a subset or all of the components shown. The host application 1414 may be implemented in a container-based architecture, and the host application 1414 may provide support for video codecs (e.g., Universal Video Codec (VVC), High Efficiency Video Codec (HEVC), Advanced Video Codec (AVC), Moving Picture Experts Group (MPEG), VP9) and audio codecs (e.g., Lossless Audio Codec (FLAC), Advanced Audio Codec (AAC), MPEG, G.711), including code translation for multiple different categories, types, or implementations of the UE (e.g., mobile phone, desktop computer, wearable display system, head-up display system). Host application 1414 can also provide user authentication and authorization checks and periodically report health, routing, and content availability to a central node (such as a device in the core network or at the edge). Therefore, host 1400 can select and / or instruct different hosts for the UE to use over-the-top (OTT) services. Host application 1414 can support various protocols, such as HTTP Live Streaming (HLS), Real-time Messaging Protocol (RTMP), Real-time Streaming Protocol (RTSP), and HTTP-based Dynamic Adaptive Streaming (DASH or MPEG-DASH).

[0162] Figure 15 This is a block diagram illustrating a virtualization environment 1500 in which functionality implemented by some embodiments can be virtualized. In this context, virtualization means creating a virtual version of a device or apparatus that may include a virtualized hardware platform, storage devices, and networking resources. As used herein, virtualization can be applied to any apparatus or component thereof described herein and relates to an implementation where at least a portion of its functionality is implemented as one or more virtual components. Some or all of the functionality described herein can be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1500 hosted by one or more hardware nodes, such as hardware computing devices operating as network nodes, UEs, core network nodes, or hosts. Furthermore, in embodiments where virtual nodes do not require radio connectivity (e.g., core network nodes or hosts), the nodes can be fully virtualized.

[0163] Running application 1502 (which may alternatively be referred to as a software instance, virtual device, network function, virtual node, virtual network function, etc.) in virtualization environment 1500 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0164] Hardware 1504 includes processing circuitry, memory storing software and / or instructions executable by the hardware processing circuitry, and / or other hardware devices as described herein, such as network interfaces, input / output interfaces, etc. The processing circuitry can execute software to instantiate one or more virtualization layers 1506 (also referred to as a hypervisor or VM monitor (VMM)), provide VMs 1508A and 1508B (one or more of which may be generally referred to as VM 1508), and / or perform any of the functions, features, and / or benefits described in relation to some embodiments described herein. Virtualization layer 1506 can present a virtual operating platform to VM 1508 that appears to be networked hardware.

[0165] VM 1508 includes virtual processing, virtual memory, virtual networking or interfaces, and virtual storage devices, and can run through a corresponding virtualization layer 1506. Different embodiments of instances of virtual device 1502 can be implemented on one or more VMs within VM 1508, and can be implemented in different ways. Hardware virtualization is referred to in some contexts as Network Functions Virtualization (NFV). NFV can be used to consolidate many types of network devices into industry-standard high-capacity server hardware, physical switches, and physical storage devices that can be located in data centers and customer premises.

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

[0167] Hardware 1504 can be implemented in a standalone network node with general or specific components. Hardware 1504 can utilize virtualization to implement some functions. Alternatively, hardware 1504 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 orchestration 1510, which, among other things, oversees the lifecycle management of application 1502. In some embodiments, hardware 1504 is coupled to one or more radio units, each including one or more transmitters and one or more receivers that can be coupled to one or more antennas. The radio units can communicate directly with other hardware nodes via one or more suitable network interfaces and can be combined with virtual components to provide radio capabilities, such as RAN or BS, to virtual nodes. In some embodiments, a control system 1512 can be used to provide signaling, which can alternatively be used for communication between hardware nodes and radio units.

[0168] Figure 16 A communication diagram is shown illustrating how host 1602 communicates with UE 1606 via network node 1604 through a partial wireless connection, according to some embodiments. Reference will now be made to... Figure 16 Describe the UEs discussed in the preceding paragraphs (such as...) Figure 11 UE1112A and / or Figure 12 UE 1200), network nodes (such as Figure 11 Network node 1110A and / or Figure 13 Network node 1300) and hosts (such as Figure 11 Host 1116 and / or Figure 14 Example implementations of the host 1400 according to various embodiments.

[0169] Like host 1400, embodiments of host 1602 include hardware such as a communication interface, processing circuitry, and memory. Host 1602 also includes software stored in or accessible by host 1602 and executable by the processing circuitry. The software includes a host application operable to provide services to remote users of UE 1606, such as those connected via an OTT connection 1650 extending between UE 1606 and host 1602. In providing services to remote users, the host application can provide user data transmitted using the OTT connection 1650.

[0170] Network node 1604 includes hardware that enables it to communicate with host 1602 and UE 1606 via connection 1660. Connection 1660 can be direct or via a core network (like...). Figure 11 The core network (similar to 1106) and / or one or more other intermediate networks (such as one or more public, private, or hosted networks). For example, an intermediate network could be a backbone network or the Internet.

[0171] UE 1606 includes hardware and software, the software being stored in or accessible by UE 1606 and executable by the UE's processing circuitry. The software includes client applications, such as web browsers or carrier-specific "apps," operable to provide services to human or non-human users via UE 1606 with the support of host 1602. In host 1602, the executing host application can communicate with the executing client application via OTT connection 1650 terminated at both UE 1606 and host 1602. When providing services to a user, the UE's client application can receive request data from the host application of the host and provide user data in response to the request data. OTT connection 1650 can transmit both request data and user data. The UE's client application can interact with the user to generate the user data it provides to the host application via OTT connection 1650.

[0172] OTT connection 1650 can be extended via connection 1660 between host 1602 and network node 1604 and via wireless connection 1670 between network node 1604 and UE 1606 to provide connectivity between host 1602 and UE 1606. Connection 1660 and wireless connection 1670, on which OTT connection 1650 can be provided, have been abstractly depicted to illustrate communication between host 1602 and UE 1606 via network node 1604, without explicitly mentioning any intermediate devices or the precise routing of messages via these devices.

[0173] As an example of data transmission via OTT connection 1650, in step 1608, host 1602 provides user data, which can be executed by executing a host application. In some embodiments, the user data is associated with a specific human user interacting with UE 1606. In other embodiments, the user data is associated with UE 1606, which shares data with host 1602 without explicit human interaction. In step 1610, host 1602 initiates a transmission carrying user data toward UE 1606. Host 1602 may initiate the transmission in response to a request transmitted by UE 1606. The request may be caused by human interaction with UE 1606 or by operation of a client application executed on UE 1606. According to the teachings of the embodiments described throughout this disclosure, the transmission may pass through network node 1604. Therefore, in step 1612, according to the teachings of the embodiments described throughout this disclosure, network node 1604 transmits the user data carried in the transmission initiated by host 1602 to UE 1606. In step 1614, UE 1606 receives user data carried in the transmission, which can be executed by a client application that is executed on UE 1606 and associated with a host application executed by host 1602.

[0174] In some examples, UE 1606 executes a client application that provides user data to host 1602. User data can be provided as a response to or in response to data received from host 1602. Therefore, in step 166, UE 1606 can provide user data, which can be done by executing the client application. When providing user data, the client application may further consider user input received from a user via the input / output interface of UE 1606. Regardless of the specific manner in which user data is provided, UE 1606 initiates a transmission of user data to host 1602 via network node 1604 in step 1618. In step 1620, in accordance with the teachings of the embodiments described throughout this disclosure, network node 1604 receives user data from UE 1606 and initiates a transmission of the received user data to host 1602. In step 1622, host 1602 receives the user data carried in the transmission initiated by UE 1606.

[0175] One or more embodiments in various implementations use OTT connection 1650 to improve the performance of OTT services provided to UE 1606, wherein wireless connection 1670 forms the final segment.

[0176] In the example scenario, factory status information can be collected and analyzed by host 1602. As another example, host 1602 can process audio and video data already acquired from the UE for map creation. As another example, host 1602 can collect and analyze real-time data to help control traffic congestion (e.g., control traffic lights). As another example, host 1602 can store surveillance video uploaded by the UE. As another example, host 1602 can store or control access to media content, such as video, audio, VR, or AR, which can be broadcast, multicast, or unicast to the UE. As other examples, host 1602 can be used for energy pricing, remote control of non-time-critical electrical loads to balance generation demand, location services, presentation services (such as compiled maps based on data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing, and / or transmitting data.

[0177] In some examples, measurement procedures may be provided for the purpose of monitoring data rates, latency, and other factors that improve upon one or more of the embodiments. Optional network functionality may also be available for reconfiguring the OTT connection 1650 between host 1602 and UE 1606 in response to changes in measurement results. The measurement procedures and / or network functionality for reconfiguring the OTT connection 1650 may be implemented in the software and hardware of host 1602 and / or in the software and hardware of UE 1606. In some embodiments, sensors (not shown) may be deployed in or associated with other devices traversed by the OTT connection 1650; the sensors may participate in the measurement procedure by supplying values ​​of the monitored quantities as described above or by supplying values ​​of other physical quantities from which the software can calculate or estimate the monitored quantities. Reconfiguration of the OTT connection 1650 may include message formats, retransmission settings, preferred routing, etc.; reconfiguration does not require a direct change to the operation of network node 1604. Such procedures and functionalities may be known and practiced in the art. In some embodiments, the measurements may involve dedicated UE signaling, which helps host 1602 measure throughput, propagation time, latency, and the like. These measurements can be implemented because the software uses OTT connection 1650 to transmit messages (especially empty or “pseudo” messages) while monitoring propagation time, errors, etc.

[0178] While the computing devices described herein (e.g., UE, network node, host) may include combinations of the hardware components shown, 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 processing circuitry that processes information by, for example, converting acquired information into other information, comparing the acquired or converted information with information stored in a network node, and / or performing one or more operations based on the acquired or converted information, and making a determination as a result of said processing. Furthermore, although components are depicted as single boxes located within larger boxes or nested within multiple boxes, in practice, a computing device may include multiple different physical components constituting a single illustrated component, and functionality may be partitioned between individual components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of a component may be partitioned between processing circuitry and the communication interface. In another example, non-computationally intensive functions of any such component may be implemented in software or firmware, and computationally intensive functions may be implemented in hardware.

[0179] In some embodiments, some or all of the functionality described herein may be provided by processing circuitry that executes instructions stored in 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 functionality may be provided by processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, the processing circuitry may be configured to perform the described functionality regardless of whether instructions stored on a non-transitory computer-readable storage medium are executed. The benefits provided by such functionality are not limited to individual processing circuitry or other components of the computing device, but are enjoyed by the computing device as a whole and / or generally by the end user and wireless network.

[0180] Some exemplary embodiments of this disclosure are as follows: Group A Implementation Examples Example 1: A method performed by a user equipment (UE), the method comprising any one or more of the following: • Receive (702) a PDCCH command for transmitting the PRACH preamble code from the first TRP to the second TRP; • Determine (704) the spatial Tx filter and transmission power used for the transmission of the PRACH preamble to the second TRP; and • Transmit the PRACH preamble code (706) according to the determined spatial Tx filter and the determined transmission power.

[0181] Example 2: According to the method described in Example 1, the PDCCH command includes a PRACH preamble index, a PRACH preamble mask, an SSB index, and a PCI associated with the SSB index.

[0182] Example 3: According to the method of Example 2, wherein determining the spatial Tx filter and the transmission power for the transmission of the PRACH preamble to the second TRP includes determining the spatial Tx filter and the transmission power for the transmission of the PRACH preamble to the second TRP based on the SSB index and the PCI included in the PDCCH command.

[0183] Example 4: According to the method of Example 2, wherein determining the spatial Tx filter and the transmission power for the transmission of the PRACH preamble to the second TRP includes: determining the spatial Tx filter for the transmission of the PRACH preamble based on the SSB index.

[0184] Example 5: According to the method of Example 2 or 4, wherein determining the spatial Tx filter and the transmission power for the transmission of the PRACH preamble to the second TRP includes: calculating the path loss between the configured SSB transmission power as an SSB associated with the SSB index and the RSRP measured based on the SSB associated with the SSB index; and determining the transmission power for the transmission of the PRACH preamble based on the path loss (and optionally one or more other power control parameters).

[0185] Example 6: The method according to any one of Examples 1 to 5, wherein the PDCCH command is received on the serving cell of the UE, wherein the serving cell is configured with two timing advances or two timing advance groups.

[0186] Example 7: The method according to any one of Examples 1 to 5, wherein the UE is configured in the serving cell to receive the PDCCH command by one or more of the following: • A first CORESET with a first CORESET pool index and a second CORESET with a second CORESET pool index, wherein the first CORESET pool index and the second CORESET pool index are different; • The first TA and the second TA, or the first TAG ID and the second TAG ID, or a TAG ID associated with two time alignment timers; • A first set of SSBs having a first SSB transmission power associated with a first PCI, wherein the first PCI is the PCI of the serving cell. • The first PRACH configuration and the first PRACH preamble set associated with the first PCI; • TCI status list; • A second SSB set having a second SSB transmission power associated with the second PCI; • The second PRACH configuration and the second PRACH preamble set associated with the second PCI.

[0187] Example 8: According to the method described in Example 7, wherein the second PCI is the PCI of the cell associated with the second TRP to which the PRACH preamble is transmitted.

[0188] Example 9: The method according to Example 7 or 8, wherein the UE is activated by a first TCI state from the TCI state list for the first CORESET and a second TCI state from the TCI state list for the second CORESET.

[0189] Example 10: The method according to any one of Examples 7 to 9, wherein the first SSB set is configured with a first SSB transmission power, and the second SSB set is configured with a second SSB transmission power, wherein the values ​​of the first SSB transmission power and the second SSB transmission power are the same or different.

[0190] Example 11: The method according to any one of Examples 7 to 10, wherein one of the following two associations is possible: • The first CORESET is associated with the first PCI, and the second CORESET is associated with the second PCI, or • The first CORESET is associated with the second PCI, and the second CORESET is associated with the first PCI.

[0191] Example 12: A method performed by a user equipment (UE), the method comprising any one or more of the following: • Receive (1002) a PDCCH command from the first TRP to transmit the first PRACH preamble to the first TRP and the second PRACH preamble to the second TRP; • Determine (1004) the first spatial Tx filter for the transmission of the first PRACH preamble to the first TRP; • Determine (1004) the second spatial Tx filter for the transmission of the second PRACH preamble to the first TRP; • Determine (1006) the first Tx power used for the transmission of the first PRACH preamble to the first TRP; • Determine (1006) the second Tx power used for the transmission of the second PRACH preamble to the second TRP; • Transmit the first PRACH preamble (1008) according to the determined first spatial Tx filter and the determined first transmission power; and • Transmit the second PRACH preamble (1008) according to the determined second space Tx filter and the determined second transmission power.

[0192] Example 13: The method according to Example 12, wherein the PDCCH command includes any one or more of the following: • The index of the first PRACH preamble associated with the first PRACH preamble; • Optionally, the second PRACH preamble index associated with the second PRACH preamble; • First PRACH preamble mask; • Optionally, a second PRACH preamble mask; • First SSB index; • Second SSB index; • The first PCI index associated with the first SSB index; and • The second PCI index associated with the second SSB index.

[0193] Example 14: According to the method of Example 13, wherein: determining the first spatial Tx filter includes determining the first spatial Tx filter for transmission of the first PRACH preamble based on the first SSB index; and determining the second spatial Tx filter includes determining the second spatial Tx filter for transmission of the second PRACH preamble based on the second SSB index.

[0194] Example 15: The method according to Example 13 or 14, wherein determining the first transmission power for the transmission of the first PRACH preamble includes any one or more of the following: calculating a first path loss between the configured SSB transmission power as an SSB associated with the first SSB index and the RSRP measured based on the SSB associated with the first SSB index; and determining the first transmission power for the transmission of the first PRACH preamble based on the first path loss (and optionally one or more other power control parameters).

[0195] Example 16: The method according to any one of Examples 13 to 15, wherein determining the second transmission power for the transmission of the second PRACH preamble includes any one or more of the following: calculating a second path loss between the configured SSB transmission power as an SSB associated with the second SSB index and the RSRP measured based on the SSB associated with the second SSB index; and determining the second transmission power for the transmission of the second PRACH preamble based on the second path loss (and optionally one or more other power control parameters).

[0196] Example 17: The method according to any one of the foregoing embodiments further includes: providing user data; and forwarding the user data to the host via the transmission to the network node.

[0197] Group B Implementation Example Example 18: A method performed by a first TRP, the method comprising: transmitting (818) a PDCCH command to a second TRP to transmit a PRACH preamble code to the UE.

[0198] Example 19: According to the method described in Example 18, wherein the PDCCH command includes a PRACH preamble index, a PRACH preamble mask, an SSB index, and a PCI associated with the SSB index.

[0199] Example 20: The method according to Example 18 or 19, wherein the PDCCH command further instructs the UE to transmit another PRACH preamble to the first TRP.

[0200] Example 21: The method according to any one of the foregoing embodiments further includes: obtaining user data; and forwarding the user data to a host or user equipment.

[0201] Group C Implementation Example Example 22: A user equipment includes: a processing circuit configured to perform any step as described in any of the examples in Group A; and a power supply circuit configured to supply power to the processing circuit.

[0202] Example 23: A network node comprising: processing circuitry configured to perform any step as described in any of the examples in Group B; and power supply circuitry configured to supply power to the processing circuitry.

[0203] Example 24: A user equipment (UE) includes: an antenna configured to transmit and receive wireless signals; a radio front-end circuit connected to the antenna and connected to a processing circuit, configured to modulate signals transmitted between the antenna and the processing circuit; the processing circuit being configured to perform any step as described in any of the examples in Group A; an input interface connected to the processing circuit and configured to allow input of information to be processed by the processing circuit into the UE; an output interface connected to the processing circuit and configured to output information from the UE that has been processed by the processing circuit; and a battery connected to the processing circuit and configured to supply power to the UE.

[0204] Example 25: A host configured to operate in a communication system to provide over-the-top (OTT) services, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE includes a communication interface and processing circuitry configured to perform any step as described in any of the examples in Group A to receive the user data from the host.

[0205] Example 26: A host as described in the preceding examples, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data from the host to the UE.

[0206] Example 27: A host as described in the two preceding examples, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executed on the UE, the client application being associated with the host application.

[0207] Example 28: A method implemented by a host operating in a communication system further comprising a network node and a user equipment (UE), the method comprising: providing user data to the UE; and initiating a transmission carrying the user data to the UE via a cellular network including the network node, wherein the UE performs any operation as described in any of the examples in Group A to receive the user data from the host.

[0208] Example 29: The method as described in the foregoing embodiments further includes: on the host, executing a host application associated with a client application executed on the UE to receive the user data from the UE.

[0209] Example 30: The method as described in the foregoing embodiments further includes: transmitting input data to the client application executed on the UE by the host, the input data being provided by executing the host application, wherein, in response to the input data from the host application, the user data is provided by the client application.

[0210] Example 31: A host configured to operate in a communication system to provide over-the-top (OTT) services, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE includes a communication interface and processing circuitry configured to perform any step as described in any of the examples in Group A to transmit the user data to the host.

[0211] Example 32: A host as described in the preceding examples, wherein the cellular network further includes network nodes configured to communicate with the UE to transmit the user data from the UE to the host.

[0212] Example 33: A host as described in the two preceding examples, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executed on the UE, the client application being associated with the host application.

[0213] Example 34: A method implemented by a host configured to operate in a communication system further comprising a network node and a user equipment (UE), the method comprising: receiving user data transmitted from the UE to the host via the network node, wherein the UE performs any step as described in any of the examples in Group A to transmit the user data to the host.

[0214] Example 35: The method as described in the foregoing embodiments further includes: on the host, executing a host application associated with a client application executed on the UE to receive the user data from the UE.

[0215] Example 36: The method as described in the foregoing embodiments further includes: transmitting input data to the client application executed on the UE by the host, the input data being provided by executing the host application, wherein, in response to the input data from the host application, the user data is provided by the client application.

[0216] Example 37: A host configured to operate in a communication system to provide over-the-top (OTT) services, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node being configured to perform any operation as described in any of the Group B examples to transmit the user data from the host to the UE.

[0217] Example 38: A host as described in the preceding examples, wherein: the processing circuitry of the host is configured to execute a host application that provides the user data; and the UE includes processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host.

[0218] Example 39: A method implemented in a host configured to operate in a communication system further comprising a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network including the network node, wherein the network node performs any of the operations described in any of the Group B examples to transmit the user data from the host to the UE.

[0219] Example 40: The method as described in the foregoing embodiments further includes, at the network node, transmitting the user data provided by the host to the UE.

[0220] Example 41: The method as described in any one of the preceding two examples, wherein the user data is provided on the host by executing a host application that interacts with a client application executed on the UE, the client application being associated with the host application.

[0221] Example 42: A communication system configured to provide an over-the-top service, the communication system comprising: a host including: processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node being configured to perform any operation as described in any of the Group B embodiments to transmit the user data from the host to the UE.

[0222] Example 43: The communication system as described in the foregoing examples further includes: the network node; and / or the user equipment.

[0223] Example 44: A host configured to operate in a communication system to provide over-the-top (OTT) services, the host comprising: processing circuitry configured to initiate the reception of user data; and a network interface configured to receive the user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, the processing circuitry of the network node being configured to perform any operation as described in any of the Group B examples to receive the user data from a user equipment (UE) for the host.

[0224] Example 45: A host as described in the two preceding examples, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executed on the UE, the client application being associated with the host application.

[0225] Example 46: The host as described in any one of the two preceding examples, wherein initiating the reception of the user data includes requesting the user data.

[0226] Example 47: A method implemented by a host configured to operate in a communication system further comprising a network node and a user equipment (UE), the method comprising: on the host, initiating the reception of user data from the UE, the user data originating from a transmission, the network node having received the transmission from the UE, wherein the network node performs any step as described in any of the examples in Group B to receive the user data from the UE for the host.

[0227] Example 48: The method described in the foregoing embodiments further includes transmitting the received user data to the host at the network node.

[0228] Those skilled in the art will recognize improvements and modifications to the embodiments of this disclosure. All such improvements and modifications are considered to be within the scope of the concepts disclosed herein.

Claims

1. A method performed by a user equipment (UE), the method comprising: Receive from the network node the configuration of the first advance group TAG ID and the second TAG ID of the serving cell, as well as the configuration of the first CORESET with the first control resource set CORESET pool index value and the second CORESET with the second CORESET pool index value; The network node receives (702) a request to transmit a Physical Random Access Channel (PRACH) preamble in the serving cell, wherein the request includes a PRACH preamble index associated with the PRACH preamble, information about a downlink reference signal (RS), and information about a Physical Cell Identifier (PCI) associated with the downlink RS. Based on the information about the downlink RS and the information about the PCI included in the request, the transmission power for the transmission of the PRACH preamble is determined (704); as well as The PRACH preamble is transmitted according to the determined transmission power (706).

2. The method according to claim 1, wherein, The request is carried in the Physical Downlink Control Channel (PDCCH).

3. The method according to claim 1, wherein, The request is a PDCCH command carried in the downlink control information (DCI) format.

4. The method according to claim 1, wherein, The first TAG ID is different from the second TAG ID, and the first CORESET pool index value is different from the second CORESET pool index value.

5. The method according to claim 1, wherein, The downlink RS consists of the synchronization reference signal SS and the physical broadcast channel PBCH block SSB.

6. The method according to claim 1, wherein, The PCI is the PCI of the serving cell or a PCI different from the PCI of the serving cell.

7. The method according to claim 1, wherein, The information regarding the PCI associated with the downlink RS indicates the PCI, and the downlink RS is associated with the PCI indicated by the information regarding the PCI included in the request.

8. The method of claim 1, further comprising receiving the configuration of the downlink RS and the transmission power of the downlink RS before receiving the request.

9. The method according to claim 1, wherein, The information regarding the downlink RS includes the index of the downlink RS.

10. The method according to claim 1, wherein, The information regarding the PCI includes an indication of whether the PCI is the PCI of the serving cell or a PCI different from the PCI of the serving cell.

11. The method according to claim 1, wherein, The request is received in the DCI of one of the first CORESET and the second CORESET.

12. The method according to claim 1, wherein: The request is a PDCCH command carried in the downlink control information (DCI) format; The downlink RS is the synchronization reference signal SS and the physical broadcast channel PBCH block SSB; The information regarding the downlink RS is the SSB index of the SSB; The information regarding the PCI is the PCI; as well as Determining (704) the transmission power for the transmission of the PRACH preamble includes determining (704) the spatial Tx filter and the transmission power for the transmission of the PRACH preamble based on the SSB index and the PCI included in the PDCCH command.

13. The method according to claim 1, wherein, The method further includes determining (704) a spatial filter for the transmission of the PRACH preamble based on the downlink RS and the PCI.

14. The method according to claim 13, wherein, The spatial filter is used when receiving the downlink RS.

15. The method according to claim 1, wherein, Determining (704) the transmission power used for the transmission of the PRACH preamble includes: Calculate (704) the path loss as the difference between the transmitted power of the downlink RS and the received power RSRP of the reference signal measured based on the downlink RS; and The transmission power (704) for the transmission of the PRACH preamble is determined based on the calculated path loss.

16. The method according to any one of claims 1 to 15, wherein, The request is received on the serving cell of the UE.

17. The method according to any one of claims 1 to 15, further comprising receiving (700) configuration information, the configuration information configuring the UE by one or more of the following: • A first set of downlink RSs having a first transmission power associated with a first PCI, wherein the first PCI is the PCI of the serving cell; • The first PRACH configuration and the first PRACH preamble set associated with the first PCI; • Transport Configuration Indicator (TCI) status list; • A second set of downlink RSs with a second transmission power associated with the second PCI; as well as • The second PRACH configuration and the second PRACH preamble set associated with the second PCI.

18. The method according to claim 17, wherein, The first PCI and the second PCI are different.

19. The method according to claim 17 or 18, wherein, The PCI indicated in the request is one of the first PCI and the second PCI.

20. The method according to any one of claims 17 to 19, wherein, If the first PCI is indicated in the request, then the PRACH preamble indicated in the request is one of the first PRACH preamble sets, and if the second PCI is indicated in the request, then the PRACH preamble indicated in the request is one of the second PRACH preamble sets.

21. The method according to any one of claims 17 to 20, wherein, If the first PCI is indicated in the request, then the downlink RS indicated in the request is one of the first set of downlink RSs, and if the second PCI is indicated in the request, then the downlink RS indicated in the request is one of the second set of downlink RSs.

22. The method according to any one of claims 17 to 21, wherein, The UE is activated by a first TCI state from the TCI state list for the first CORESET and a second TCI state from the TCI state list for the second CORESET.

23. The method according to any one of claims 17 to 22, wherein, The first SSB set is configured with a first SSB transmission power, and the second SSB set is configured with a second SSB transmission power, wherein the values ​​of the first SSB transmission power and the second SSB transmission power are the same or different.

24. A user equipment (UE), suitable for: Receive from the network node the configuration of the first advance group TAG ID and the second TAG ID of the serving cell, as well as the configuration of the first CORESET with the first control resource set CORESET pool index value and the second CORESET with the second CORESET pool index value; The network node receives (702) a request to transmit a Physical Random Access Channel (PRACH) preamble in the serving cell, wherein the request includes a PRACH preamble index associated with the PRACH preamble, information about a downlink reference signal (RS), and information about a Physical Cell Identifier (PCI) associated with the downlink RS. Based on the information about the downlink RS and the information about the PCI included in the request, the transmission power for the transmission of the PRACH preamble is determined (704); as well as The PRACH preamble is transmitted according to the determined transmission power (706).

25. The UE according to claim 24 is also suitable for performing the method according to any one of claims 2 to 23.

26. A user equipment (UE), comprising: This includes the communication interface for both the transmitter and receiver; The processing circuitry associated with the communication interface is configured to cause the UE to: Receive from the network node the configuration of the first advance group TAG ID and the second TAG ID of the serving cell, as well as the configuration of the first CORESET with the first control resource set CORESET pool index value and the second CORESET with the second CORESET pool index value; The network node receives (702) a request to transmit a Physical Random Access Channel (PRACH) preamble in the serving cell, wherein the request includes a PRACH preamble index associated with the PRACH preamble, information about a downlink reference signal (RS), and information about a Physical Cell Identifier (PCI) associated with the downlink RS. Based on the information about the downlink RS and the information about the PCI included in the request, the transmission power for the transmission of the PRACH preamble is determined (704); as well as The PRACH preamble is transmitted according to the determined transmission power (706).

27. The UE according to claim 26, wherein, The processing circuit is further configured to cause the UE to perform the method according to any one of claims 2 to 23.

28. A method performed by a network node, the method comprising: Transmit to the User Equipment (UE) the configuration of the first advance group TAG identifier ID and the second TAG ID in the serving cell, as well as the configuration of the first CORESET with the first control resource set CORESET pool index value and the second CORESET with the second CORESET pool index value; as well as A request is transmitted to the UE to transmit a Physical Random Access Channel (PRACH) preamble code in the serving cell, wherein the request includes a PRACH preamble code index associated with the PRACH preamble code, information about a downlink reference signal (RS), and information about a physical cell identifier (PCI) associated with the downlink RS.

29. A network node, suitable for: Transmit to the User Equipment (UE) the configuration of the first advance group TAG identifier ID and the second TAG ID in the serving cell, as well as the configuration of the first CORESET with the first control resource set CORESET pool index value and the second CORESET with the second CORESET pool index value; and A request is transmitted to the UE to transmit a Physical Random Access Channel (PRACH) preamble code in the serving cell, wherein the request includes a PRACH preamble code index associated with the PRACH preamble code, information about a downlink reference signal (RS), and information about a physical cell identifier (PCI) associated with the downlink RS.

30. A network node, including processing circuitry, the processing circuitry being configured to cause the network node to: Transmit to the User Equipment (UE) the configuration of the first advance group TAG identifier ID and the second TAG ID in the serving cell, as well as the configuration of the first CORESET with the first control resource set CORESET pool index value and the second CORESET with the second CORESET pool index value; and A request is transmitted to the UE to transmit a Physical Random Access Channel (PRACH) preamble code in the serving cell, wherein the request includes a PRACH preamble code index associated with the PRACH preamble code, information about a downlink reference signal (RS), and information about a physical cell identifier (PCI) associated with the downlink RS.

Images