CSI-RS transmission and reception using a unified TCI state for multiple trp
By receiving the unified TCI state of the CSI-RS resource set triggered by DCI in the user equipment, the association of CSI-RS resources in multiple TRP scenarios is simplified, and the activation and indication problems of the unified TCI state framework in multiple TRP scenarios is solved, and the problem of improving the activation and indication of the unified TCI state framework in multiple TRP scenarios is improved. The flexibility of beam management and reduce signaling overhead.
Patent Information
- Application Number
- CN202380035370.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-03-04
- Filing Date
- 2023-03-06
- Publication Date
- 2024-12-03
AI Technical Summary
The existing unified transmission configuration indicator (TCI) state framework is difficult to support the activation and indication of multiple unified TCI states in multiple TRP scenarios, resulting in limited beam management flexibility, large signaling overhead and high cost in mobile scenarios.
Provide a system and method to receive downlink control information triggering the CSI-RS resource set through a user equipment (UE), and to receive CSI-RS resources using a unified TCI state based on the DCI, simplifying CSI-RS resources and multiple The association of the unified TCI state of activation/indication supports CSI-RS transmission of multiple TRPs.
It realizes the simple association between CSI-RS resources and multiple unified TCI states under the unified TCI state framework, improves the flexibility of beam management, and reduces signaling overhead and costs in mobile scenarios.
Smart Images

Figure CN119072889A_ABST
Abstract
Description
Related applications
[0001] This application claims the benefit of provisional patent application serial number 63 / 316,559, filed on March 4, 2022, the disclosure of which is incorporated herein by reference in its entirety. Technical Field
[0002] The present disclosure generally relates to determining a unified transmission configuration indication (TCI) state. Background Art
[0003] The next generation of mobile wireless communication systems (5G) or New Radio (NR) will support a diverse set of use cases and multiple deployment scenarios. The latter include deployments at both low frequencies (below 6 GHz) and very high frequencies (up to tens of GHz).
[0004] NR frame structure and resource grid
[0005] NR uses CP-OFDM (Cyclic Prefix Orthogonal Frequency Division Multiplexing) in both the downlink (i.e., from the network node, gNB or base station to the user equipment or UE) and uplink (i.e., from the UE to the gNB). DFT-spread OFDM is also supported in the uplink. In the time domain, the NR downlink and uplink are organized into subframes of equal size, each of 1ms. The subframes are further divided into multiple slots of equal duration. The slot length depends on the subcarrier spacing. For There is only one time slot in each subframe, and each time slot consists of 14 OFDM symbols.
[0006] Data scheduling in NR is usually based on time slots. Figure 1 An example of a time slot with 14 symbols is shown, in which the first two symbols contain the Physical Downlink Control Channel (PDCCH) and the remaining symbols contain the Physical Shared Data Channel (PDCH), i.e. PDSCH (Physical Downlink Shared Channel) or PUSCH (Physical Uplink Shared Channel).
[0007] NR supports different subcarrier spacing values. The supported subcarrier spacing values (also called different parameter sets) are determined by Given, where . is the basic subcarrier spacing. The time slot duration at different subcarrier spacings is given by Given.
[0008] In the frequency domain, the system bandwidth is divided into resource blocks (RBs), each RB corresponds to 12 consecutive subcarriers, and the RBs are numbered starting with 0 from one end of the system bandwidth. Figure 2The basic NR physical time-frequency resource grid is shown in Figure 2, where only one resource block (RB) within a slot consisting of 14 symbols is shown. One OFDM subcarrier during one OFDM symbol interval forms one resource element (RE).
[0009] Downlink transmission and uplink transmission can be dynamically scheduled, where, for each PDSCH or PUSCH transmission, the gNB sends a DL assignment or uplink grant to the UE via downlink control information (DCI) on the PDCCH (physical downlink control channel); or downlink transmission and uplink transmission can also be semi-persistently scheduled (SPS), where one or more DL SPS or UL configuration grant (CG) are semi-statically configured, and each of the one or more DL SPS or UL CG can be activated or deactivated by DCI.
[0010] CORESET and Search Space
[0011] The UE monitors a set of PDCCH candidates to find potential PDCCHs. PDCCH candidates are determined by the control resource set (CORESET). A control channel element (CCE) is composed of 6 resource element groups (REGs), where a REG is equal to one RB during one OFDM symbol. It is called CCE aggregation level.
[0012] The PDCCH candidate sets are defined in PDCCH search space (SS) sets. SS sets can be common search space (CSS) sets or UE-specific search space (USS) sets. For each bandwidth part (BWP), the UE can be configured with up to 10 SS sets for monitoring PDCCH candidates.
[0013] Each SS set is associated with a CORESET. CORESET consists of resource blocks and in the time domain In NR Release 15, for each BWP, the UE can be configured with up to 3 CORESETs.
[0014] TCI Status and QCL
[0015] The transmission configuration indication (TCI) state contains the quasi co-location (QCL) information between two antenna ports. If the specific channel parameters associated with one of the two antenna ports can be inferred from the other antenna port, the two antenna ports are said to be QCL. The antenna ports are defined by reference signals (RS). Therefore, the TCI state is used in NR to indicate the QCL relationship between the source RS and the target RS. The source RS can be one of the non-zero power channel state information reference signal (NZP CSI-RS), tracking RS (TRS) and synchronization signal block (SSB), while the target RS can be the demodulation reference signal (DMRS) of PDCCH or PDSCH, or CSI-RS.
[0016] The QCL information types supported in NR include: • “QCL Type A”: {Doppler shift, Doppler spread, average delay, delay spread} • “QCL Type B”: {Doppler shift, Doppler spread} • “QCL Type C”: {Doppler shift, average delay} • “QCL Type D”: {Spatial Rx parameters}
[0017] A TCI state list can be RRC configured in the higher layer parameter PDSCH-Config information element (IE) (see 3GPP TS 38.331 Section 6.3.2 for details), and up to eight TCI states in the list can be activated using a medium access control (MAC) control element (CE). In NR Release 15, the MAC CE activates one TCI state for each TCI code point in the TCI field in the DCI, where up to eight TCI code points can be supported (see 3GPP TS 38.321 Section 6.1.3.14 for details). In NR Release 16, the MAC CE can activate up to two TCI states for each TCI code point (see 3GPP TS 38.321 Section 6.1.3.24 for details). For dynamically scheduled PDSCH, one of the TCI code points is indicated in the TCI field of the DCI (DCI format 1_1 or DCI format 1_2) that schedules the PDSCH for PDSCH reception. For example, if SSB or CSI-RS is configured as QCL type D source RS in the activated TCI state indicated to PDSCH, the UE will use the same receive beam (or spatial filter) used to receive SSB or CSI-RS to receive PDSCH.
[0018] For each CORESET, a list of TCI states may be RRC configured, one of which is activated by a MAC CE. For example, if SSB is configured as a QCL type D source RS in the activated TCI state of a CORESET, the UE may receive the PDCCH sent in the CORESET using the same receive beam used to receive the SSB.
[0019] Beam management with a unified TCI framework
[0020] In NR, downlink beam management is performed by communicating the spatial QCL (“Type D”) assumption to the UE via the TCI state.
[0021] This framework allows great flexibility for the network to instruct the UE to receive signals from different spatial directions in the DL, but at the cost of large signaling overhead and slow beam switching. These limitations are particularly significant and costly when UE mobility is considered. An example is that beam updates using DCI can only be performed for PDSCH, and MAC-CE and / or RRC are required to update beams for other reference signals / channels, resulting in additional overhead and latency.
[0022] Furthermore, in most cases, the network sends and receives both data and control to and from the UE in the same direction. Therefore, using separate frameworks for different channels / signals (the spatial relationship of the TCI states respectively) would complicate the implementation.
[0023] In Release 17, a unified TCI state based beam indication framework was introduced to simplify beam management in FR2, where a common beam represented by a TCI state can be activated / indicated to the UE and is applicable to multiple channels / signals such as PDCCH and PDSCH. The common beam framework is also called the unified TCI state framework.
[0024] The new framework can be RRC configured in one of two operation modes, namely, "joint DL / UL TCI" or "separate DL / UL TCI". For "joint DL / UL TCI", one common joint TCI state is used for both DL signals / channels and UL signals / channels. For "separate DL / UL TCI", one DL-only common TCI state is used for DL channels / signals, and one UL-only common TCI state is used for UL signals / channels. The TCI states configured under the newly introduced Release 17 framework will be referred to as unified TCI states hereinafter.
[0025] The unified TCI state of DL or joint DL and UL includes identifiers of two QCL source reference signals as shown below, wherein the first RS is a QCL source RS of one of the {Type A, Type B, Type C} QCL types, and the second RS is a QCL source RS of QCL type D. The second RS is used to indicate a spatial beam or filter associated with the unified TCI state. DLorJoint-TCIState-r17 ::= SEQUENCE { tci-StateUnifiedId-r17 DLorJoint-TCIState-Id-r17, tci-StateType-r17 ENUMERATED {DLOnly, JointULDL}, qcl-Type1-r17 QCL-Info, qcl-Type2-r17 QCL-Info OPTIONAL -- Need R } QCL-Info ::= SEQUENCE { cell ServCellIndex OPTIONAL, -- Need R bwp-Id BWP-Id OPTIONAL, -- Cond CSI-RS-Indicated referenceSignal CHOICE { csi-rs NZP-CSI-RS-ResourceId, ssb SSB-Index }, qcl-Type ENUMERATED {typeA, typeB, typeC, typeD}, ...,
[0026] The unified TCI state is updated in a similar way to how the TCI state of PDSCH is updated in Release 15 / 16, i.e., by one of the following two alternative ways: • Two-stage: Use RRC signaling to configure multiple unified TCI states in the higher-level parameter PDSCH-config, and use MAC-CE to activate one of the configured unified TCI states • Three stages: configure multiple unified TCI states in PDSCH-config using RRC signaling, activate up to 8 unified TCI states using MAC-CE, and indicate one of the activated unified TCI states using a 3-bit TCI state bit field in DCI
[0027] An activated or indicated unified TCI state shall be used in subsequent PDCCH, PDSCH and NZP CSI-RS transmissions until a new unified TCI state is activated or indicated.
[0028] Both the existing DCI format 1_1 and DCI format 1_2 can be reused for beam indication (i.e., TCI status indication / update) both with and without DL assignment. For DCI format 1_1 and DCI format 1_2 with DL assignment, the ACK / NACK of the PDSCH can be used as an indication of successful reception of the beam indication. For DCI format 1_1 and DCI format 1_2 without DL assignment, a new ACK / NACK mechanism is used, which is similar to the mechanism of SPS PDSCH release with type 1 HARQ-ACK codebook and type 2 HARQ-ACK codebook, where the UE reports ACK upon successful reception of the beam indication DCI.
[0029] For DCI based beam indication, the first timeslot for applying the indicated TCI is at least Y symbols after the last symbol of the acknowledgment of the joint or individual DL / UL beam indication. The Y symbols are configured by the gNB based on the UE capabilities, which are also reported in symbols.
[0030] Multiple TRP PDCCH repetition
[0031] In NR Release 17, PDCCH repetition was introduced to enable more robust PDCCH reception, where PDCCH is transmitted through two transmit and receive points (TRPs) on different time or frequency resources.
[0032] Figure 3 An example is shown in which a PDCCH is repeated on two TRPs at different times. A first PDCCH repetition is sent in a PDCCH candidate in CORESET#c1 associated with SS set #s1, and a second PDCCH repetition is sent in another PDCCH candidate in CORESET#c2 associated with SS set #s2, wherein SS set #s1 and SS set #s2 are linked. Each of CORESET#c1 and CORESET#c2 is activated using a transmission configuration indicator (TCI) state associated with the corresponding TRP.
[0033] The two linked SS sets need to be configured with the same set of parameters, such as period, slot offset, number of monitoring opportunities within a slot, etc. For a given CCE aggregation level and two linked SS sets, the position of a PDCCH candidate in one SS set can be obtained from the PDCCH candidate in the other SS set. When performing PDCCH detection, the UE can detect the PDCCH separately in each PDCCH candidate, or jointly detect the PDCCH by soft combining of the two PDCCH candidates.
[0034] SFN PDCCH
[0035] In NR Release 17, single frequency network (SFN) based PDCCH is also introduced to achieve more robust PDCCH reception, where PDCCH is transmitted from two TRPs simultaneously in the same time and frequency resources. Figure 4 An example is shown in , where a single CORESET and associated SS set are associated with two TRPs. This is indicated to the UE both by the RRC configuration of the SFN PDCCH and by the CORESET being activated with two TCI states.
[0036] Multi-TRP PDSCH solution
[0037] In NR Release 16, PDSCH transmission through two TRPs was introduced, including a non-coherent joint transmission (NC-JT) scheme, two frequency domain multiplexing (FDM) schemes, and two time domain multiplexing (TDM) schemes. In these multi-TRP PDSCH schemes, each TRP is represented by an indicated TCI state. In NC-JT, PDSCH is transmitted through two TRPs in the same time and frequency resources, where different MIMO layers of PDSCH are transmitted from different TRPs. For example, for a total of 3 layers, 2 layers can be transmitted from the first TRP and 1 layer can be transmitted from the second TRP. For NC-JT-based PDSCH scheduling, two TCI states are indicated in the TCI code point of the DCI that schedules the PDSCH. The DMRS ports in the first CDM group and the second CDM group are associated with the first TCI state and the second TCI state, respectively.
[0038] In the FDM scheme, different frequency domain resources of the PDSCH are allocated to different TRPs. In FDM scheme A, a single PDSCH is transmitted from two TRPs, wherein a portion of the PDSCH is transmitted from one TRP and the rest is transmitted from the other TRP. In FDM scheme B, the PDSCH is repeated on two TRPs. For FDM-based multi-TRP PDSCH scheduling, two TCI states are indicated in the TCI code point of the DCI that schedules the PDSCH. The DMRS ports in the first group of scheduled RBs and the second group of scheduled RBs are associated with the first TCI state and the second TCI state, respectively.
[0039] In the TDM scheme, the PDSCH is repeated multiple times, each time the PDSCH is repeated on one of the two TRPs. In TDM scheme A, the PDSCH is repeated twice within a time slot, once from each TRP. Whereas in TDM scheme B (or slot-based TDM scheme), the PDSCH is repeated in consecutive time slots, either in a cyclic manner from two TRPs (wherein the PDSCH is sent alternately from the first TRP in one time slot and from the second TRP in the next time slot), or in a sequential manner (wherein the PDSCH is sent alternately from the first TRP and the second TRP every two consecutive time slots). For TDM-based multi-TRPPDSCH scheduling, two TCI states are indicated in the TCI code points of the DCI that schedules the PDSCH. The DMRS ports in the first group of PDSCH transmission opportunities and the second group of PDSCH transmission opportunities are associated with the first TCI state and the second TCI state, respectively. The first group of PDSCH transmission opportunities and the second group of PDSCH transmission opportunities are determined according to the mapping type (i.e., cyclic mapping or sequential mapping). Figure 5 An example of TDM scheme B is shown, where four PDSCH repetitions are scheduled from two TRPs. In the case of cyclic mapping, the first PDSCH opportunity and the third PDSCH opportunity are associated with the first TCI state indicated in the DCI, and the second PDSCH opportunity and the fourth PDSCH opportunity are associated with the second TCI state indicated in the DCI. In the case of sequential mapping, the first PDSCH opportunity and the second PDSCH opportunity are associated with the first TCI state indicated in the DCI, and the third PDSCH opportunity and the fourth PDSCH opportunity are associated with the second TCI state indicated in the DCI.
[0040] CSI-RS
[0041] Channel State Information Reference Signal (CSI-RS) is used in NR for channel state information CSI measurements in the downlink. CSI-RS is transmitted on an antenna port at the gNB and is used by the UE to measure the downlink channel associated with that antenna port. CSI-RS used for this purpose is also called non-zero power (NZP) CSI-RS. Antenna ports are also called CSI-RS ports. The number of CSI-RS ports supported in a CSI-RS resource in NR can be one of {1, 2, 4, 8, 12, 16, 24, 32}. Multiple CSI-RS resources can be configured. A CSI-RS resource set can contain one or more CSI-RS resources.
[0042] A CSI-RS resource can be aperiodic, periodic, or semi-persistent (SP). The CSI-RS resources in a CSI-RS resource set are transmitted together and have the same time domain configuration, i.e., aperiodic, periodic, or semi-persistent.
[0043] Aperiodic CSI-RS transmission is triggered by one of DCI format 0_1 or DCI format 0_2. SP CSI-RS transmission is activated and deactivated by MAC CE.
[0044] In frequency range 2 (FR2), each CSI-RS resource is also associated with a beam specified by a QCL source reference signal (RS) with type D. For periodic, the QCL source RS is RRC configured. For aperiodic CSI-RS, the QCL type D source RS is configured in the associated aperiodic CSI trigger state, where the index of the trigger state is indicated in the DCI that triggers the aperiodic CSI-RS. For SP CSI-RS, the QCL source RS is indicated in the corresponding activation MAC CE. These are further explained below.
[0045] QCL configuration of aperiodic CSI-RS resources
[0046] The "CSI-AperiodicTriggerStateList" information element (IE) defined in 3GPP TS 38.331 is used in NR to configure a list of aperiodic CSI trigger states for the UE, each aperiodic CSI trigger state is defined by the parameter "CSI-AperiodicTriggerState", as shown below. Each codepoint of the "CSI request" field in the DCI (DCI format 1_1 or DCI format 1_2) is associated with one of the trigger states in the list, which is described in 3GPP TS 38.214 section 5.2.1.5.1. Upon receiving a DCI with a CSI request codepoint indicating a trigger state, the UE receives the NZP CSI-RS resources in the NZP CSI-RS resource set indicated by the parameter "resourceset" in the trigger state according to the QCL information configured by the parameter "qcl-info". The QCL information contains the TCI state ID for each NZP CSI-RS resource in the NZP CSI-RS resource set. CSI-AperiodicTriggerStateList information element --ASN1START -- TAG-CSI-APERIODICTRIGGERSTATELIST-START CSI-AperiodicTriggerStateList ::= SEQUENCE (SIZE (1..maxNrOfCSI-AperiodicTriggers)) OF CSI-AperiodicTriggerState CSI-AperiodicTriggerState ::= SEQUENCE { associatedReportConfigInfoList SEQUENCE (SIZE(1..maxNrofReportConfigPerAperiodicTrigger)) OF CSI-AssociatedReportConfigInfo, ... } CSI-AssociatedReportConfigInfo ::= SEQUENCE { reportConfigId CSI-ReportConfigId, resourcesForChannel CHOICE { nzp-CSI-RS SEQUENCE { resourceSet INTEGER(1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig), qcl-info SEQUENCE (SIZE(1..maxNrofAP-CSI-RS-ResourcesPerSet)) OF TCI-StateId OPTIONAL -- Cond Aperiodic }, csi-SSB-ResourceSet INTEGER (1..maxNrofCSI-SSB-ResourceSetsPerConfig) }, csi-IM-ResourcesForInterference INTEGER(1..maxNrofCSI-IM-ResourceSetsPerConfig) OPTIONAL, -- Cond CSI-IM-ForInterference nzp-CSI-RS-ResourcesForInterference INTEGER (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig) OPTIONAL, -- Cond NZP-CSI-RS-ForInterference ... } -- TAG-CSI-APERIODICTRIGGERSTATELIST-STOP --ASN1STOP
[0047] QCL information of SP CSI-RS resources
[0048] The QCL information of the SP CSI-RS resources in the CSI-RS resource set is indicated in the corresponding MAC CE of the activated CSI-RS resource set. The MAC CE is described in TS 38.321 Section 6.1.3.12 and the format is included in Figure 6 In which, the TCI state ID is indicated for each CSI-RS resource in the SP CSI-RS resource set. The meaning of each field is as follows: • A / D: This field indicates whether the indicated SP CSI-RS and CSI-IM resource set is activated or deactivated. This field is set to 1 to indicate activation, otherwise it indicates deactivation; • Serving Cell ID: This field indicates the identity of the serving cell to which the MAC CE applies. The length of this field is 5 bits; • BWP ID: This field indicates the DL BWP used by the MAC CE as the code point for the DCI Bandwidth Part Indicator field as specified in TS 38.212. The length of the BWP ID field is 2 bits; • SP CSI-RS Resource Set ID: This field contains the index of the NZP-CSI-RS-ResourceSet containing the semi-persistent NZP CSI-RS resources as specified in TS 38.331, which indicates the semi-persistent NZP CSI-RS resource set that should be activated or deactivated. The length of this field is 6 bits; • IM: This field indicates the presence of the octet containing the SP CSI-IM Resource Set ID field. If the IM field is set to 1, the octet containing the SP CSI-IM Resource Set ID field is present. If the IM field is set to 0, the octet containing the SP CSI-IM Resource Set ID field is not present; • SP CSI-IM Resource Set ID: This field contains the index of the CSI-IM-ResourceSet containing the semi-persistent CSI-IM resources as specified in TS 38.331 [5], which indicates the semi-persistent CSI-IM resource set that should be activated or deactivated. The length of this field is 6 bits; •TCI Status ID i : This field contains the TCI-StateId of the TCI state as specified in TS 38.331, which is used as the QCL source for the resources within the semi-persistent NZP CSI-RS resource set indicated by the SP CSI-RS Resource Set ID field. TCI State ID0 indicates the TCI state of the first resource within the set, TCI State ID1 indicates the TCI state of the second resource within the set, and so on. The length of this field is 7 bits. If the A / D field is set to 0, the octet containing the TCI State ID field is not present; •R: Reserved bit, set to 0.
[0049] For periodic NZP CSI-RS resources, QCL information is configured in the NZP CSI-RS resource, as shown in the following parameter "qcl-InfoPeriodicCSI-RS": NZP-CSI-RS-Resource information element --ASN1START -- TAG-NZP-CSI-RS-RESOURCE-START NZP-CSI-RS-Resource ::= SEQUENCE { nzp-CSI-RS-ResourceId NZP-CSI-RS-ResourceId, resourceMapping CSI-RS-ResourceMapping, powerControlOffset INTEGER (-8..15), powerControlOffsetSS ENUMERATED{db-3, db0, db3,db6} OPTIONAL, -- Need R scramblingID ScramblingId, periodicityAndOffset CSI-ResourcePeriodicityAndOffset OPTIONAL, -- CondPeriodicOrSemiPersistent qcl-InfoPeriodicCSI-RS TCI-StateIdOPTIONAL, -- Cond Periodic ... } -- TAG-NZP-CSI-RS-RESOURCE-STOP --ASN1STOP
[0050] Improved systems and methods for determining unified TCI status are needed. Summary of the invention
[0051] Systems and methods are provided for channel state information-reference signal (CSI-RS) transmission and reception using unified transmission configuration indication (TCI) states for multiple TRPs. In some embodiments, a method for determining a unified TCI state performed by a user equipment (UE) includes: receiving downlink control information (DCI) that triggers a CSI-RS resource set; and receiving one or more CSI-RS resources using a unified TCI state based on the DCI. In this way, a simple way to associate a CSI-RS resource with one of multiple activated / indicated unified TCI states (or common beams) for multi-TRP-based transmission under a unified TCI state framework is provided.
[0052] Certain aspects of the present disclosure and embodiments thereof may provide solutions to these or other challenges. An implicit association of a CSI-RS resource with one of two (i.e., first and second) activated / indicated unified TCI states:
[0053] If a single AP CSI-RS resource is included in the NZP CSI-RS resource set triggered by DCI: If the DCI is carried by a PDCCH in a CORESET associated with an SS set that is not linked to any other SS set, the AP CSI-RS resource is received using a unified TCI state (or common beam) for receiving the PDCCH. If the DCI is carried by repeated PDCCHs in two CORESETs associated with one of the two linked SS sets, respectively, the AP CSI-RS is received using a unified TCI state (or common beam) for receiving the PDCCH in one of the two CORESETs. One of the two CORESETs may be a CORESET associated with the SS set having the smaller SS set index of the two SS sets. If the DCI is carried by an SFN PDCCH in a CORESET associated with two unified TCI states (or common beams), one of the unified TCI states (or common beams), i.e., the first unified TCI state or the second unified TCI state, is used to receive the AP CSI-RS.
[0054] If two AP CSI-RS resources or AP CSI-RS resource groups are in a CSI-RS resource set triggered by DCI, the first AP CSI-RS resource and the second AP CSI-RS resource or AP CSI-RS resource group are associated with a first unified TCI state and a second unified TCI state (or common beam), respectively, wherein the first CSI-RS resource and the second CSI-RS resource are in the order configured in the CSI-RS resource set. If a single SP CSI-RS resource in the NZP CSI-RS resource set is activated by a MAC CE: if the MAC CE is carried by a PDSCH received using a single unified TCI state (or common beam), the SP CSI-RS resource is also received using the unified TCI state (or common beam). If the MAC CE is carried by a PDSCH received using both the first unified TCI state and the second unified TCI state (or common beam) at the same or different times, one of the two unified TCI states (or common beams) is also used to receive the SP CSI-RS.
[0055] If two SP CSI-RS resources or two groups of SP CSI-RS resources are in the NZP CSI-RS resource set activated by the MAC CE, the first SP CSI-RS resource and the second SP CSI-RS resource or the SP CSI-RS resource group are associated with the first unified TCI state and the second unified TCI state (or common beam), respectively, wherein the first CSI-RS resource and the second CSI-RS resource are in the order configured in the CSI-RS resource set. If more than two AP or SP CSI-RS resources in the CSI-RS resource set are triggered by DCI or activated by MAC CE, the CSI-RS resources are received according to the QCL information configured or indicated for each CSI-RS resource in the corresponding aperiodic CSI triggering state or in the activated MAC CE.
[0056] Explicit configuration of unified TCI state pointer for each NZP CSI-RS resource. For AP CSI-RS, a unified TCI state pointer may be configured for the associated CSI-RS resource set or for each NZP CSI-RS resource in a CSI-RS resource set in the associated aperiodic CSI triggering state. For SP CSI-RS, a unified TCI state pointer may be indicated for each SP CSI-RS resource in the activation MAC CE. For periodic CSI-RS, a unified TCI state pointer may be configured in each periodic NZP CSI-RS resource.
[0057] A method of associating a NZP CSI-RS resource with one of a first unified TCI state and a second unified TCI state that has been activated and indicated to a UE. The association may be implicit or explicit or a mixture of the two.
[0058] In case of implicit association, the NZP CSI-RS resources are associated with the unified TCI state of the corresponding PDCCH triggering the NZP CSI-RS or the PDSCH carrying the corresponding MAC CE for activating the NZP CSI-RS resources.
[0059] If the PDCCH or PDSCH is associated with two unified TCI states and the triggered or activated NZP CSI-RS resource set contains one NZP CSI-RS resource, the NZP CSI-RS resource is associated with the first unified TCI state or the second unified TCI state of the two unified TCI states.
[0060] If the NZP CSI-RS resource set contains two NZP CSI-RS resources or two groups of NZP CSI-RS resources, the first NZP CSI-RS resource and the second NZP CSI-RS resource or NZP CSI-RS resource group are associated with a first unified TCI state and a second unified TCI state, respectively.
[0061] If an NZP CSI-RS resource set contains more than two NZP CSI-RS resources, the TCI state pointer is configured for each NZP CSI-RS resource in the associated aperiodic CSI triggering state or in the activation MAC CE.
[0062] In the case of explicit association, for AP CSI-RS, in the associated aperiodic CSI triggering state, for SP CSI-RS, in the activated MAC CE, or for AP / SP / periodic NZP CSI-RS, directly in the NZP CSI-RS resource or resource set, a TCI state pointer is configured for each NZP CSI-RS resource, where the TCI state pointer points to one of the first activated / indicated unified TCI state or the second activated / indicated unified TCI state. BRIEF DESCRIPTION OF THE DRAWINGS
[0063] The accompanying drawings incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.
[0064] Figure 1shows that data scheduling in New Radio (NR) is typically based on a slot having 14 symbols, of which the first two symbols contain a Physical Downlink Control Channel (PDCCH) and the remaining symbols contain a Physical Shared Data Channel (PDCH), i.e. a Physical Downlink Shared Channel (PDSCH) or a Physical Uplink Shared Channel (PUSCH);
[0065] Figure 2 The basic NR physical time-frequency resource grid is shown, where only one resource block (RB) within a slot consisting of 14 symbols is shown;
[0066] Figure 3 shows the PDCCH repeated at two transmit and receive points (TRP) at different times;
[0067] Figure 4 A single control resource set (CORESET) and associated search space (SS) set are shown to be associated with two TRPs;
[0068] Figure 5 An example of a time domain multiplexing (TDM) scheme B for scheduling four PDSCH repetitions from two TRPs is shown;
[0069] Figure 6 A medium access control (MAC) control element (CE) described in Section 6.1.3.12 of TS 38.321 is shown, wherein a TCI state ID is indicated for each CSI-RS resource in a semi-persistent (SP) channel state information reference signal CSI-RS resource set;
[0070] Figure 7 An example of CSI-RS transmission under a unified TCI state framework for downlink (DL) multi-TRP transmission from two TRPs (ie, TRP1 and TRP2) according to some embodiments of the present disclosure is shown (where two unified TCI states are activated and indicated);
[0071] Figure 8 An example of a communication system according to some embodiments is shown;
[0072] Fig. 9 A user equipment (UE) according to some embodiments is shown;
[0073] Fig.10 shows a network node according to some embodiments;
[0074] Fig.11 is a block diagram of a host according to various aspects described herein, which host may be Figure 8 An embodiment of a host;
[0075] Fig.12 is a block diagram illustrating a virtualization environment in which functionality implemented by some embodiments may be virtualized; and
[0076] Fig.13 A communication diagram is shown in which a host communicates with a UE via a network node over a partially wireless connection according to some embodiments. DETAILED DESCRIPTION
[0077] There are some challenges. In the unified TCI state framework introduced in NR Release 17, only a single unified TCI state can be activated or indicated at any time. Therefore, it is only applicable to data transmission from a single TRP. However, NR Release 16 already supports PDSCH transmission from multiple TRPs (or multi-TRP, or mTRP), and NR Release 17 further supports PDCCH transmission from multiple TRPs. The unified TCI framework introduced in Release 17 does not support the mTRP PDSCH and PDCCH schemes supported by Release 16 and Release 17, which rely on the Release 15 TCI state / spatial relationship framework.
[0078] It has been decided in 3GPP that the unified TCI state framework will be extended to support the mTRP scheme in NR Release 18. In order to support the mTRP PDSCH and PDCCH schemes, multiple unified TCI states need to be activated / indicated to the UE. How to associate CSI-RS transmission with one or more of the multiple unified TCI states is a problem.
[0079] The embodiments set forth below present information that enables those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. After reading the following description according to the accompanying drawings, those skilled in the art will understand the conception of the present disclosure and will recognize the application of these concepts that are not specifically provided herein. It should be understood that these concepts and applications fall within the scope of the present disclosure.
[0080] It can be envisioned that when the unified TCI state framework is configured to support DL transmission of multiple TRPs in the DL BWP from the serving cell, multiple unified TCI states (each state is associated with one TRP) need to be activated / indicated for the UE via a combination of RRC, MAC CE and DCI signaling, where the unified TCI state list is configured by RRC, a subset of unified TCI states is activated for each TCI code point by MAC CE, and one DCI format (e.g., DCI format 1_1 or DCI format 1_2) indicates one TCI code point. In the BWP of the serving cell, the unified TCI state will be used for subsequent DL transmissions to the UE of all or a subset of channels or signals (including PDCCH, PDSCH and CSI-RS).
[0081] In the following, the unified TCI state associated with the TCI code point indicated in the DCI is referred to as the activated / indicated unified TCI state. The terms activated / indicated unified TCI state, activated unified TCI state, indicated unified TCI state, indicated TCI state, and common beam are used interchangeably. In addition, the terms CSI-RS and NZP CSI-RS are used interchangeably.
[0082] Embodiments related to implicit association between CSI-RS and activated / indicated unified TCI state
[0083] Figure 7 An example of CSI-RS transmission in a unified TCI state framework for DL multi-TRP transmission from two TRPs (i.e., TRP1 and TRP2) is shown (where two unified TCI states are activated and indicated); an aperiodic CSI-RS resource set can be triggered by DCI, or an SP CSI-RS resource set can be activated by MAC
[0084] Aperiodic CSI-RS
[0085] For each aperiodic CSI-RS resource in a CSI-RS resource set triggered by a DCI format, it shall be sent according to one of the two indicated unified TCI states (or in other words, associated with one of a first indicated unified TCI state and a second indicated unified TCI state).
[0086] In one embodiment, if a CSI-RS resource set with a single CSI-RS resource is triggered by a DCI format, and the DCI format is sent in one of two common beams or associated with one of two indicated unified TCI states, the CSI-RS resource is sent in the same common beam as the corresponding common beam that triggered the DCI. In other words, the CSI-RS resource is associated with the same activated / indicated unified TCI state as the activated / indicated unified TCI state of the PDCCH that carries the triggered DCI in the same BWP. Figure 7 This is shown in . If the CSI-RS overlaps with another DL channel or signal, the unified TCI state of the other DL channel or signal will be used for the CSI-RS.
[0087] In the case where the PDCCH carrying the triggered DCI is associated with two unified TCI states (i.e., the PDCCH is repeated in two CORESETs (each CORESET is activated using one of the two unified TCI states) (or repeated from two TRPs) or sent in a CORESET activated using two unified TCI states (i.e., sent from two TRPs in SFN manner)), in one embodiment, the triggered CSI-RS resource is always associated with the first (or second) activated / indicated unified TCI state. In another embodiment, if the time offset between the start of the CSI-RS and the end of the PDCCH (in the case of PDCCH repetition with two PDCCH candidates, the end of the PDCH is the end of the PDCCH candidate that ends later in time) is greater than a predefined threshold, one of the first activated / indicated TCI state and the second activated / indicated TCI state is indicated in the DCI, or in one of the CSI-RS resource, CSI-RS resource set, or aperiodic CSI triggering state. In another embodiment, the CSI-RS resource is associated with one of the two activated / indicated TCI states.
[0088] If two AP CSI-RS resources in a CSI-RS resource set are triggered by DCI, the first AP CSI-RS resource and the second AP CSI-RS resource are associated with a first unified TCI state and a second unified TCI state, respectively, wherein the first CSI-RS resource and the second CSI-RS resource are in the order configured in the CSI-RS resource set. In another embodiment, the two AP CSI-RS resources in the CSI-RS resource set may be configured in two resource groups (e.g., two channel measurement resource (CMR) groups), wherein the first AP CSI-RS resource belongs to the first resource group and the second AP CSI-RS resource belongs to the second resource group. In this case, the first AP CSI-RS resource belonging to the first resource group is associated with the first unified TCI state, and the second AP CSI-RS resource belonging to the second resource group is associated with the second unified TCI state.
[0089] If the triggered CSI-RS resource set contains more than two CSI-RS resources, in one embodiment, the CSI-RS resources in the CSI-RS resource set are received using QCL information configured in a non-periodic CSI triggering state, wherein the configured QCL source RS may be different from the QCL source RS in the indicated unified TCI state.
[0090] In an alternative embodiment, when more than two CSI-RS resources are configured in a triggered CSI-RS resource set, the more than two CSI-RS resources in the triggered CSI-RS set are configured to belong to two resource groups (i.e., a first subset of AP CSI-RS resources belongs to a first resource group, and a second subset of AP CSI-RS resources belongs to a second resource group, wherein the two subsets are mutually exclusive sets). Then, the first subset of AP CSI-RS resources belonging to the first resource group is associated with a first unified TCI state. The second subset of AP CSI-RS resources belonging to the second resource group is associated with a second unified TCI state.
[0091] SP CSI-RS
[0092] For each SP CSI-RS resource in the CSI-RS resource set activated by the MAC CE, the SP CSI-RS shall be transmitted using one of the two activated / indicated unified TCI states (or common beams).
[0093] In one embodiment, if an SP CSI-RS resource set with a single SP CSI-RS resource is activated by a MAC CE and a single activated / indicated unified TCI state (or common beam) is used to receive the PDSCH carrying the MAC CE, the CSI-RS resource is received using the same activated / indicated unified TCI state (or common beam) as the corresponding PDSCH. In other words, the SP CSI-RS resource is associated with the same TCI state as the PDSCH carrying the activated MAC CE. Figure 7 This is shown in .
[0094] In the case of a PDSCH carrying this activation, the MAC CE is associated with two TCI states (i.e., the PDSCH is one of the mTRP schemes), and in one embodiment, the activated SP CSI-RS resources are always associated with the first (or second) activated / indicated unified TCI state. Note that the mTRP scheme here refers to any of the following schemes: A PDSCH reception scheme in which a first subset of PDSCH layers is received using a first activated / indicated unified TCI state and a second subset of PDSCH layers is received using a second activated / indicated unified TCI state, wherein the first subset of PDSCH layers and the second subset of PDSCH layers are mutually exclusive sets. This scheme is referred to as a non-coherent joint transmission (NC-JT) scheme. A PDSCH repetition scheme involving multiple PDSCH transmission opportunities, wherein a first subset of PDSCH transmission opportunities is received using a first activated / indicated uniform TCI state, and a second subset of PDSCH transmission opportunities is received using a second activated / indicated uniform TCI state; note that different PDSCH transmission opportunities can be in the frequency domain or the time domain (e.g., frequency domain repetition or time domain repetition).
[0095] In another embodiment, the associated one of the first TCI state and the second TCI state is indicated in the DCI or in one of the CSI-RS resource, the CSI-RS resource set, or the aperiodic CSI triggering state.
[0096] If two SP CSI-RS resources in the SP CSI-RS resource set are activated by the MAC CE, the first SP CSI-RS resource and the second SP CSI-RS resource are associated with the first common beam and the second common beam, respectively, wherein the first CSI-RS resource and the second CSI-RS resource are in the order configured in the SP CSI-RS resource set. In another embodiment, the two SP CSI-RS resources in the CSI-RS resource set may be configured in two resource groups (or channel measurement resource groups), wherein the first SP CSI-RS resource belongs to the first resource group and the second SP CSI-RS resource belongs to the second resource group. In this case, the first SP CSI-RS resource belonging to the first resource group is associated with the first unified TCI state, and the second SP CSI-RS resource belonging to the second resource group is associated with the second unified TCI state.
[0097] If the SP CSI-RS resource set contains multiple CSI-RS resources (i.e., more than two CSI-RS resources), the CSI-RS resources are received according to the QCL information indicated for each CSI-RS resource in the corresponding activation MAC CE, where the QCL source RS indicated in the MAC CE may be different from the QCL source RS in the indicated unified TCI state.
[0098] In an alternative embodiment, when more than two CSI-RS resources are configured in a triggered CSI-RS resource set, the more than two CSI-RS resources in the triggered CSI-RS set are configured to belong to two resource groups (i.e., a first subset of SP CSI-RS resources belongs to a first resource group, and a second subset of SP CSI-RS resources belongs to a second resource group, wherein the two subsets are mutually exclusive sets). Then, the first subset of SP CSI-RS resources belonging to the first resource group is associated with a first unified TCI state. The second subset of SP CSI-RS resources belonging to the second resource group is associated with a second unified TCI state.
[0099] Embodiments related to an explicit association between a NZP CSI-RS resource and one of the indicated unified TCI states
[0100] Instead of implicitly associating the NZP CSI-RS resources with one of the activated / indicated unified TCI states based on the triggering PDCCH of the aperiodic CSI-RS resources or the PDSCH carrying the activation MACCE of the SP NZP CSI-RS resources, the TCI state pointer (or common beam index) is explicitly configured for the NZP CSI-RS resources.
[0101] For example, if the MAC CE activates up to three unified TCI states for each TCI code point, as shown below, where the TCI state in each row is associated with the same TCI state pointer. For example, the TCI state in the first row is associated with TCI state pointer = 1, the TCI state in the second row is associated with TCI state pointer = 2, and the TCI state in the last row is associated with TCI state pointer = 3. Therefore, if TCI code point 3 is indicated in the DCI, three unified TCI states {x3, y3, z3} will be indicated. In this case, if the NZP CSI-RS resource is configured with TCI state pointer = 1, the NZP CSI-RS resource will be sent / received according to TCI state x3. The next time if TCI code point 5 is indicated in the DCI, three new unified TCI states {x5, y5, z5} will be indicated, and the NZP CSI-RS resource will be sent / received according to TCI state x5. In this way, the NZP CSI-RS resource is associated with one of the activated / indicated unified TCI states (or common beams), while the actual TCI state (or actual beam) may be different at different times due to, for example, beam changes tracking UE movement. For a BWP, serving cell, or a list of serving cells transmitting NZP CSI-RS, the indicated unified TCI state can be a unified DL and UL TCI state or a DL-only TCI state.
[0102] The following table is an example of associating the activated unified TCI state of a TCI code point with the TCI state pointer:
[0103] In one embodiment, a TCI state pointer is configured in each NZP CSI-RS resource to indicate the unified TCI state to be used for sending / receiving the CSI-RS resource when a set of unified TCI states is activated / indicated. An example is shown below, where the parameter "unified-tci-State-Pointer" is a new parameter for selecting one of multiple activated / indicated unified TCI states for the NZP CSI-RS resource, and "maxNrofIndicated-TCI-States" is the maximum number of unified TCI states that can be activated for a TCI code point. By doing so, there is no need to use MAC CE to activate the TCI state of the SP CSI-RS resource. For periodic NZP CSI-RS resources, if "unified-tci-State-Pointer" is configured for the CSI-RS resource, the traditional parameter qcl-InfoPeriodicCSI-RS is ignored. NZP-CSI-RS-Resource information element --ASN1START -- TAG-NZP-CSI-RS-RESOURCE-START NZP-CSI-RS-Resource ::= SEQUENCE { nzp-CSI-RS-ResourceId NZP-CSI-RS-ResourceId, resourceMapping CSI-RS-ResourceMapping, powerControlOffset INTEGER (-8..15), powerControlOffsetSS ENUMERATED{db-3, db0, db3,db6} OPTIONAL, -- Need R scramblingID ScramblingId, periodicityAndOffset CSI-ResourcePeriodicityAndOffset OPTIONAL, -- CondPeriodicOrSemiPersistent qcl-InfoPeriodicCSI-RS TCI-StateIdOPTIONAL, -- Cond Periodic unified-tci-State-Pointer = INTEGER (1..maxNrofIndicated-TCI-States) ... } -- TAG-NZP-CSI-RS-RESOURCE-STOP --ASN1STOP
[0104] Alternatively, a TCI state pointer is configured in each NZP CSI-RS resource set to indicate a unified TCI state to be used for all NZP CSI-RS resources in the transmit / receive CSI-RS resource set, as shown below. NZP-CSI-RS-ResourceSet information element --ASN1START -- TAG-NZP-CSI-RS-RESOURCESET-START NZP-CSI-RS-ResourceSet ::= SEQUENCE { nzp-CSI-ResourceSetId NZP-CSI-RS-ResourceSetId, nzp-CSI-RS-Resources SEQUENCE (SIZE(1..maxNrofNZP-CSI-RS-ResourcesPerSet)) OF NZP-CSI-RS-ResourceId, OPTIONAL,-- Need S aperiodicTriggeringOffset INTEGER(0..6) OPTIONAL,-- Need S OPTIONAL, -- Need R ..., [[ aperiodicTriggeringOffset-r16 INTEGER(0..31) OPTIONAL--Need S ]] Unified-tci-State-Pointer = INTEGER (1..maxNrofIndicated-TCI-States) } -- TAG-NZP-CSI-RS-RESOURCESET-STOP --ASN1STOP
[0105] For non-periodic NZP CSI-RS resources, in an alternative embodiment, the TCI state pointer is explicitly configured in the corresponding non-periodic CSI trigger state, as shown below. In this case, if the UE is triggered using the non-periodic CSI trigger state, the UE shall assume that the QCL assumptions of all NZP CSI-RS resources associated with the non-periodic CSI trigger state shall be received using the TCI state associated with the configured TCI state pointer. Note that the non-periodic CSI trigger state may contain multiple CSI report configurations, each with an associated NZP CSI-RS resource set for channel measurement. This embodiment means that the configured TCI state pointer applies to NZP CSI-RS resources in all associated NZP CSI-RS resource sets. The following is an example of configuring the TCI state pointer (or common beam index) for all CSI-RS resource sets associated with the non-periodic CSI trigger state. CSI-AperiodicTriggerStateList ::= SEQUENCE (SIZE (1..maxNrOfCSI-AperiodicTriggers)) OF CSI-AperiodicTriggerState CSI-AperiodicTriggerState ::= SEQUENCE { associatedReportConfigInfoList SEQUENCE (SIZE(1..maxNrofReportConfigPerAperiodicTrigger)) OF CSI-AssociatedReportConfigInfo, ... [[ unified-tci-State-PointerINTEGER (1..maxNrofIndicated-TCI-States) ]] }
[0106] In another embodiment, as schematically shown below, the TCI state pointer is explicitly configured according to the "CSI-AssociatedReportConfigInfo", that is, the TCI state pointer is configured for the NZP CSI-RS resource set. In this case, if the non-periodic trigger state is used to trigger the UE, the UE should assume that all NZP CSI-RS resources associated with the "CSI-AssociatedReportConfigInfo" should be received using the unified TCI state indicated by the TCI state pointer. Compared with the aforementioned embodiment, one benefit of this solution is that the solution provides greater flexibility, because, for example, one non-periodic CSI trigger state can be associated with two different "CSI-AssociatedReportConfigInfo" or CSI reports, each of which is associated with a common beam or unified TCI state, which may be useful, for example, when the network wants to schedule the UE to measure and report two CSI associated with two different TRPs (where each TRP is associated with a common beam). The following is an example of configuring a TCI state pointer (or common beam index) for a CSI-RS resource set associated with an aperiodic CSI triggering state. CSI-AssociatedReportConfigInfo ::= SEQUENCE { reportConfigId CSI-ReportConfigId, resourcesForChannel CHOICE { nzp-CSI-RS SEQUENCE { resourceSet INTEGER(1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig), qcl-info SEQUENCE (SIZE(1..maxNrofAP-CSI-RS-ResourcesPerSet)) OF TCI-StateIdOPTIONAL -- CondAperiodic }, csi-SSB-ResourceSet INTEGER (1..maxNrofCSI-SSB-ResourceSetsPerConfig) }, csi-IM-ResourcesForInterference INTEGER(1..maxNrofCSI-IM-ResourceSetsPerConfig)OPTIONAL, -- Cond CSI-IM-ForInterference nzp-CSI-RS-ResourcesForInterference INTEGER (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig) OPTIONAL, -- Cond NZP-CSI-RS-ForInterference ... [[ unified-tci-State-PointerINTEGER (1..maxNrofIndicated-TCI-States) ]] }
[0107] In another embodiment, the TCI state pointer is explicitly configured for each NZP CSI-RS resource by introducing a list of "unified TCI state pointers" as shown below. In this case, the UE shall assume that the QCL assumption for each NZP CSI-RS resource in the CSI-RS resource set indicated in the non-periodic CSI triggering state is determined according to the associated "unified TCI state pointer" configured in the parameter field "follow-unified-tci-State-r18". For example, if the value of the k-th unified TCI state pointer in the list is 2, the second indicated unified TCI state applies to the k-th NZP CSI-RS resource in the NZP CSI-RS resource set. When "follow-unified-tci-State-r18" is present, the UE shall ignore the parameter "qcl-info".
[0108] One benefit of this solution compared to the previous embodiments is that it provides even more flexibility since here a common beam index can be determined for each NZP CSI-RS resource. This is useful for example for CSI feedback associated with multiple TRPs, where different NZP CSI-RS resources in a CSI-RS resource set can be associated with different TRPs (and therefore with different TCI states / common beams).
[0109] The next table shows an example of configuring a separate TCI state pointer (or common beam index) for each aperiodic NZP CSI-RS resource in a CSI-RS resource set associated with an aperiodic CSI triggering state. CSI-AperiodicTriggerStateList information element --ASN1START -- TAG-CSI-APERIODICTRIGGERSTATELIST-START CSI-AperiodicTriggerStateList ::= SEQUENCE (SIZE (1..maxNrOfCSI-AperiodicTriggers)) OF CSI-AperiodicTriggerState CSI-AperiodicTriggerState ::= SEQUENCE { associatedReportConfigInfoList SEQUENCE (SIZE(1..maxNrofReportConfigPerAperiodicTrigger)) OF CSI-AssociatedReportConfigInfo, ... } CSI-AssociatedReportConfigInfo ::= SEQUENCE { reportConfigId CSI-ReportConfigId, resourcesForChannel CHOICE { nzp-CSI-RS SEQUENCE { resourceSet INTEGER (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig), qcl-info SEQUENCE (SIZE(1..maxNrofAP-CSI-RS-ResourcesPerSet)) OF TCI-StateId OPTIONAL --Cond Aperiodic follow-unified-tci-State-r18 SEQUENCE (SIZE(1..maxNrofAP-CSI-RS-ResourcesPerSet)) OF unified-TCI-State-Pointer }, csi-SSB-ResourceSet INTEGER (1..maxNrofCSI-SSB-ResourceSetsPerConfig) }, csi-IM-ResourcesForInterference INTEGER(1..maxNrofCSI-IM-ResourceSetsPerConfig) OPTIONAL, -- Cond CSI-IM-ForInterference nzp-CSI-RS-ResourcesForInterference INTEGER (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig) OPTIONAL, -- Cond NZP-CSI-RS-ForInterference ... } Unified-TCI-State-Pointer ::= INTEGER(1..maxNrofIndicated-TCI-States) -- TAG-CSI-APERIODICTRIGGERSTATELIST-STOP --ASN1STOP
[0110] In the above, each TCI state pointer points to a unified TCI state activated and indicated for a BWP transmitting a CSI-RS.
[0111] If multiple unified TCI states are used to activate / indicate a UE in a BWP, and the scheduling offset between the last symbol of the PDCCH that triggers the DCI carrying the aperiodic CSI-RS transmission in the same BWP and the first symbol of the aperiodic CSI-RS resource in the NZP CSI-RS resource set is less than a threshold reported by the UE, the UE needs to determine how to receive the aperiodic CSI-RS (e.g., which TCI states or beams to use for reception) before decoding the DCI.
[0112] In one embodiment, if the triggered aperiodic CSI-RS resource overlaps with another DL signal / channel in an OFDM symbol, the aperiodic CSI-RS is associated with the same unified TCI state as the other DL signal / channel, wherein the other DL signal / channel may be any one of a periodic CSI-RS, an SP CSI-RS, another aperiodic CSI-RS, or a PDSCH. If there is a PDSCH associated with two unified TCI states in the same symbol as the CSI-RS, the UE applies the first unified TCI state of the two unified TCI states when receiving the aperiodic CSI-RS.
[0113] If the triggered aperiodic CSI-RS resource does not overlap with any DL signal or channel, and if the parameter enableTwoDefaultTCI-States is not configured (i.e., the UE is able to use one TCI state for DL reception before DCI decoding), the UE applies the first indicated unified TCI state. Otherwise, if the UE is configured with the parameter enableTwoDefaultTCI-States (i.e., the UE is able to use two TCI states for DL reception before DCI decoding), the UE applies the first indicated unified TCI state and / or the second indicated unified TCI state to the aperiodic CSI-RS reception according to the unified TCI state pointer configured for the aperiodic CSI-RS resource.
[0114] Figure 8 An example of a communication system 800 is shown in accordance with some embodiments.
[0115] In this example, the communication system 800 includes: a telecommunications network 802, which includes an access network 804 (such as a radio access network (RAN)); and a core network 806, which includes one or more core network nodes 808. The access network 804 includes one or more access network nodes, such as network nodes 810A and 810B (one or more of which may be generally referred to as network nodes 810), or any other similar third generation partnership project (3GPP) access nodes or non-3GPP access points (APs). The network nodes 810 facilitate direct or indirect connection of user equipment (UE), such as connecting UE 812A, 812B, 812C, and 812D (one or more of which may be generally referred to as UE 812) to the core network 806 through one or more wireless connections.
[0116] Example wireless communications via wireless connections include sending and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information without using wiring, cables, or other material conductors. In addition, in different embodiments, the communication system 800 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 communication of data and / or signals (whether via a wired connection or via a wireless connection). The communication system 800 may include any type of communication, telecommunication, data, cellular, radio network, and / or other similar types of systems, and / or be connected to any type of communication, telecommunication, data, cellular, radio network, and / or other similar types of system interfaces.
[0117] UE 812 may be any of a variety of communication devices, including wireless devices that are arranged, configured and / or operable to wirelessly communicate with network node 810 and other communication devices. Similarly, network node 810 is arranged, capable, configured and / or operable to communicate directly or indirectly with UE 812 and / or with other network nodes or devices in telecommunication network 802 to enable and / or provide network access (such as wireless network access) and / or to perform other functions (such as management) in telecommunication network 802.
[0118] In the depicted example, the core network 806 connects the network node 810 to one or more hosts (such as the host 816). These connections may be direct connections or indirect connections via one or more intermediate networks or devices. In other examples, the network node may be directly coupled to the host. The core network 806 includes one or more core network nodes (e.g., core network node 808) composed of hardware and software components. The features of these components may be substantially similar to those described with respect to the UE, the network node, and / or the host, so that their descriptions are generally applicable to the corresponding components of the core network node 808. The example core network node includes the functions of one or more of the following items: a mobile switching center (MSC), a mobility management entity (MME), a home subscriber server (HSS), an access and mobility management function (AMF), a session management function (SMF), an authentication server function (AUSF), a subscription identifier cancellation function (SIDF), a unified data management (UDM), a security edge protection agent (SEPP), a network open function (NEF), and / or a user plane function (UPF).
[0119] The host 816 may be owned or under the control of a service provider other than the operator or provider of the access network 804 and / or the telecommunications network 802, and may be operated by or on behalf of the service provider. The host 816 may host a variety of applications to provide one or more services. Examples of such applications include real-time and pre-recorded audio / video content, data collection services (e.g., retrieving and compiling data about various environmental conditions detected by multiple UEs), analysis functions, social media, functions for controlling or otherwise interacting with remote devices, functions for alarm and monitoring centers, or any other such functions performed by a server.
[0120] As a whole, Figure 8 The communication system 800 implements the connection between the UE, the network node and the host. In this sense, the communication system 800 can be configured to operate according to predefined rules or procedures such as a specific standard, which includes but is not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE) and / or other suitable second generation (2G), third generation (3G), fourth generation (4G) or fifth generation (5G) standards, or any applicable future generation standards (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 Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low power wide area network (LPWAN) standards such as LoRa and Sigfox.
[0121] In some examples, the telecommunication network 802 is a cellular network that implements 3GPP standardized features. Therefore, the telecommunication network 802 can support network slicing to provide different logical networks to different devices connected to the telecommunication network 802. For example, the telecommunication network 802 can provide ultra-reliable low-latency communication (URLLC) services to some UEs, while providing enhanced mobile broadband (eMBB) services to other UEs, and / or providing massive machine type communication (mMTC) / massive Internet of Things (IoT) services to yet other UEs.
[0122] In some examples, UE 812 is configured to send and / or receive information without direct human interaction. For example, the UE may be designed to send information to the access network 804 according to a predetermined schedule when triggered by an internal or external event or in response to a request from the access network 804. In addition, the UE may be configured to operate in a single or multiple radio access technology (RAT) or multi-standard mode. For example, the UE may operate using any one or a combination of WiFi, new radio (NR), and LTE, i.e., configured as multi-radio dual connectivity (MR-DC), such as evolved UMTS terrestrial RAN (E-UTRAN) NR dual connectivity (EN-DC).
[0123] In this example, the hub 814 communicates with the access network 804 to facilitate indirect communication between one or more UEs (e.g., UE 812C and / or 812D) and a network node (e.g., network node 810B). In some examples, the hub 814 can be a controller, a router, a content source and analyzer, or any other communication device described herein with respect to the UE. For example, the hub 814 can be a broadband router that enables the UE to access the core network 806. As another example, the hub 814 can be a controller that sends commands or instructions to one or more actuators in the UE. The command or instruction can be received from the UE, the network node 810, or received by an executable code, script, process, or other instruction in the hub 814. As another example, the hub 814 can be a data collector that acts as a temporary storage device for UE data, and in some embodiments, analysis or other processing of the data can be performed. As another example, the center 814 can be a content source. For example, for a UE that is a virtual reality (VR) headset, display, speaker, or other media delivery device, the hub 814 can retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, and then the hub 814 provides it directly to the UE after performing local processing and / or after adding additional local content. In yet another example, if one or more of the UEs are low-energy IoT devices, the hub 814 acts as a proxy server or coordinator for the UEs.
[0124] The hub 814 may have a continuous / persistent or intermittent connection to the network node 810B. The hub 814 may also allow different communication schemes and / or scheduling between the hub 814 and the UE (e.g., UE 812C and / or 812D) and between the hub 814 and the core network 806. In other examples, the hub 814 is connected to the core network 806 and / or one or more UEs via a wired connection. In addition, the hub 814 may be configured to be connected to a machine-to-machine (M2M) service provider through the access network 804, and / or to another UE through a direct connection. In some scenarios, the UE may establish a wireless connection with the network node 810 while still being connected through the hub 814 via a wired or wireless connection. In some embodiments, the hub 814 may be a dedicated hub, that is, a hub whose main function is to route communications from the network node 810B to the UE / route communications from the UE to the network node 810B. In other embodiments, hub 814 may be a non-dedicated hub - ie, a device operable to route communications between UEs and network node 810B but additionally capable of operating as a communications origin and / or endpoint for certain data channels.
[0125] Fig. 9 A UE 900 according to some embodiments is shown. As used herein, a UE refers to a device capable of, configured, arranged and / or operable to wirelessly communicate with a network node and / or other UEs. Examples of UEs include, but are not limited to, smart phones, mobile phones, cellular phones, voice over 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, tablet computers, laptop computers, laptop embedded devices (LEEs), laptop mounted devices (LMEs), smart devices, wireless client 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.
[0126] The UE may, for example, support device-to-device (D2D) communications by implementing 3GPP standards for sidelink communications, dedicated short-range communications (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, the UE may not necessarily have a user in the sense of a human user who owns and / or operates the associated device. Alternatively, the UE may represent a device that is intended to be sold to or operated by a human user but may not or may not initially be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, the UE may represent a device that is not intended to be sold to or operated by an end user but may be associated with or operated for the benefit of a user (e.g., a smart power meter).
[0127] UE 900 includes a processing circuit 902, which is operatively coupled to an input / output interface 906, a power supply 908, a memory 910, a communication interface 912, and / or any other components or any combination thereof via a bus 904. Some UEs may utilize Fig. 9 All or a subset of the components shown. The level of integration between components may vary from UE to UE. In addition, some UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
[0128] The processing circuit 902 is configured to process instructions and data, and may be configured to implement any sequential state machine operable to execute instructions stored in the memory 910 as a machine-readable computer program. The processing circuit 902 may be implemented as: one or more hardware-implemented state machines (e.g., implemented in discrete logic, field programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors (such as microprocessors or digital signal processors (DSPs)) together with appropriate software; or any combination of the above. For example, the processing circuit 902 may include multiple central processing units (CPUs).
[0129] In this example, the input / output interface 906 can be configured to provide one or more interfaces to an input device, an output device, or one or more input and / or output devices. Examples of output devices include speakers, sound cards, video cards, displays, monitors, printers, actuators, transmitters, smart cards, another output device, or any combination thereof. An input device can allow a user to capture information into the UE 900. Examples of input devices include touch-sensitive or presence-sensitive displays, cameras (e.g., digital cameras, digital video cameras, web cameras, etc.), microphones, sensors, mice, trackballs, directional keyboards, trackpads, rollers, smart cards, etc. The presence-sensitive display can include a capacitive or resistive touch sensor to sense input from a user. The sensor can be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device can use an interface port of the same type as an input device. For example, a universal serial bus (USB) port can be used to provide input devices and output devices.
[0130] In some embodiments, the power supply 908 is configured as a battery or a battery pack. Other types of power supplies may be used, such as an external power supply (e.g., a power socket), a photovoltaic device, or a battery. The power supply 908 may also include a power supply circuit for delivering power from the power supply 908 itself and / or an external power supply to various parts of the UE 900 via an input circuit or an interface such as a power cable. The delivered power may be used, for example, to charge the power supply 908. The power supply circuit may perform any formatting, conversion, or other modification on the power from the power supply 908 so that the power is suitable for the corresponding components of the UE 900 to which the power is supplied.
[0131] The memory 910 may be or be configured to include a memory such as a random access memory (RAM), a read-only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically EPROM (EEPROM), a magnetic disk, an optical disk, a hard disk, a removable tape, a flash drive, etc. In one example, the memory 910 includes one or more application programs 914, such as an operating system, a web browser application, a widget, a gadget engine, or other applications, and corresponding data 916. The memory 910 may store any one of a variety of operating systems or a combination of operating systems used by the UE 900.
[0132] The memory 910 may be configured to include a plurality of physical drive units, such as a redundant array of independent disks (RAID), a flash memory, a USB flash drive, an external hard disk drive, a thumb drive, a pen drive, a key drive, a high density digital versatile disk (HD-DVD) optical drive, a built-in hard disk drive, a Blu-ray optical drive, a holographic digital data storage (HDDS) optical drive, an external mini dual in-line memory module (DIMM), a synchronous dynamic random access memory (SDRAM), an external micro DIMM SDRAM, a smart card memory (e.g., a tamper-proof module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs) such as a universal SIM (USIM) and / or an Internet Protocol Multimedia Services Identity Module (ISIM), other memories, or any combination thereof. The UICC may be, for example, an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC commonly referred to as a “SIM card”. The memory 910 may allow the UE to 900 accesses instructions, applications, etc. stored on a temporary or non-temporary storage medium to unload data or upload data. An article of manufacture (such as an article of manufacture utilizing a communication system) may be tangibly embodied as or in a memory 910, which may be or include a device-readable storage medium.
[0133] The processing circuit 902 may be configured to communicate with an access network or other network using a communication interface 912. The communication interface 912 may include one or more communication subsystems and may include an antenna 922 or be communicatively coupled to the antenna 922. The communication interface 912 may include one or more transceivers for communication (such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network)). Each transceiver may include a transmitter 918 and / or a receiver 920 suitable for providing network communications (e.g., optical, electrical, frequency allocation, etc.). In addition, the transmitter 918 and the receiver 920 may be coupled to one or more antennas (e.g., antenna 922) and may share circuit components, software or firmware, or may be implemented separately as an alternative.
[0134] In the illustrated embodiment, the communication functionality of the communication interface 912 may include cellular communication, WiFi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, NFC, location-based communication (e.g., using a global positioning system (GPS) to determine location), another type of communication functionality, or any combination thereof. Communication may be implemented according to one or more communication protocols and / or standards such as IEEE 802.11, code division multiple access (CDMA), wideband CDMA (WCDMA), GSM, LTE, NR, UMTS, WiMax, Ethernet, transmission control protocol / Internet protocol (TCP / IP), synchronous optical network (SONET), asynchronous transfer mode (ATM), fast user datagram protocol Internet connection (QUIC), hypertext transfer protocol (HTTP), etc.
[0135] Regardless of the type of sensor, the UE may provide an output of the data captured by its sensor through its communication interface 912 or via a wireless connection to a network node. The data captured by the UE's sensor may be transmitted via another UE via a wireless connection to a network node. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to balance the load of reports from several sensors), in response to a trigger event (e.g., sending an alarm when humidity is detected), in response to a request (e.g., a user-initiated request), or a continuous stream (e.g., a live video feed of a patient).
[0136] As another example, the UE includes an actuator, motor, or switch associated with a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input, the state of the actuator, motor, or switch can change. For example, the UE can include a motor that adjusts a control surface or rotor of a drone in flight based on the received input, or adjusts a robotic arm performing a medical procedure based on the received input.
[0137] When the UE is in the form of an IoT device, the UE can be a device used in one or more application areas, including but not limited to urban wearable technology, extended industrial applications, and healthcare. Non-limiting examples of such IoT devices are the following devices or devices embedded in the following devices: connected refrigerators or freezers, televisions, connected lighting devices, electricity meters, robotic vacuum cleaners, voice-controlled smart speakers, home security cameras, motion detectors, thermostats, smoke detectors, door and window sensors, flood / humidity sensors, electronic door locks, connected doorbells, air conditioning systems (such as heat pumps), autonomous vehicles, monitoring systems, weather monitoring devices, vehicle parking monitoring devices, electric vehicle charging stations, smart watches, fitness trackers, head-mounted displays for augmented reality (AR) or VR, wearable devices for tactile enhancement or sensory enhancement, sprinklers, animal tracking or item tracking devices, sensors for monitoring plants or animals, industrial robots, unmanned aerial vehicles (UAVs), and any kind of medical equipment (such as heart rate monitors or teleoperated surgical robots). In addition to the above, Fig. 9 In addition to the other components depicted in the illustrated UE 900 , a UE in the form of an IoT device may include circuitry and / or software depending on the intended application of the IoT device.
[0138] As yet another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and / or measurement and sends the results of such monitoring and / or measurement to another UE and / or a network node. In this case, the UE may be an M2M device, which may be referred to as an MTC device in the 3GPP context. As a specific example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle (such as a car, bus, truck, ship, and airplane) or other device that is capable of monitoring and / or reporting its operating status or other functions associated with its operation.
[0139] In fact, for a single use case, any number of UEs may be used together. For example, a first UE may be a drone or integrated in a drone and provide the drone's speed information (obtained via a speed sensor) to a second UE, which is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone's speed. The first UE and / or the second UE may also include more than one of the above functions. For example, a UE may include a sensor and an actuator and handle data communications for both the speed sensor and the actuator.
[0140] Fig.10A network node 1000 according to some embodiments is shown. As used herein, a network node refers to a device capable of, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or 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), base stations (BSs) (e.g., radio BSs, Node Bs, evolved Node Bs (eNBs), and NR Node Bs (gNBs)).
[0141] BSs can be classified based on the amount of coverage they provide (or in other words, based on their transmit power level), etc., and therefore, depending on the amount of coverage provided, the BS can be called a femto BS, a pico BS, a micro BS, or a macro BS. The BS can be a relay node or a relay donor node that controls a relay. The network node can also include one or more (or all) parts 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 head (RRH). These RRUs may or may not be integrated with antennas as antenna-integrated radio devices. Parts of a distributed radio BS may also be referred to as nodes in a distributed antenna system (DAS).
[0142] Other examples of network nodes include a multi-transmission point (multi-TRP) 5G access node, a multi-standard radio (MSR) device (such as an MSR BS), a network controller (such as a radio network controller (RNC) or a BS controller (BSC)), a base transceiver station (BTS), a transmission point, a transmission node, a multi-cell / multicast coordination entity (MCE), an operation and maintenance (O&M) node, an operation support system (OSS) node, a self-organizing network (SON) node, a positioning node (e.g., an evolved serving mobile location center (E-SMLC)), and / or a minimization of drive tests (MDT).
[0143] The network node 1000 includes a processing circuit 1002, a memory 1004, a communication interface 1006, and a power supply 1008. The network node 1000 may be composed of multiple physically separated components (e.g., a Node B component and an RNC component, or a BTS component and a BSC component, etc.), which may have their own corresponding components. In certain scenarios where the network node 1000 includes multiple separate components (e.g., BTS and BSC components), one or more separate components may be shared between several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique "NodeB and RNC pair" may be considered as a single separate network node in some cases. In some embodiments, the network node 1000 may be configured to support multiple RATs. In such an embodiment, some components may be duplicated (e.g., separate memory 1004 exists for different RATs), and some components may be reused (e.g., antenna 1010 may be shared by different RATs). The network node 1000 may also include multiple sets of the various components shown for different wireless technologies (e.g., GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, Long Range Wide Area Network (LoRaWAN), Radio Frequency Identification (RFID), or Bluetooth wireless technologies) integrated into the network node 1000. These wireless technologies may be integrated into the same or different chips or chipsets and other components within the network node 1000.
[0144] The processing circuit 1002 may include a combination of one or more of the following: a microprocessor, a controller, a microcontroller, a CPU, a DSP, an ASIC, an FPGA, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic that is operable to provide network node 1000 functionality alone or in combination with other network node 1000 components (e.g., memory 1004).
[0145] In some embodiments, the processing circuit 1002 includes a system on a chip (SOC). In some embodiments, the processing circuit 1002 includes one or more of a radio frequency (RF) transceiver circuit 1012 and a baseband processing circuit 1014. In some embodiments, the RF transceiver circuit 1012 and the baseband processing circuit 1014 may be on separate chips (or chipsets), boards, or units (e.g., a radio unit and a digital unit). In alternative embodiments, part or all of the RF transceiver circuit 1012 and the baseband processing circuit 1014 may be on the same chip or chipset, board, or unit set.
[0146] The memory 1004 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 disk), removable storage media (e.g., flash drive, compact disk (CD) or digital video disk (DVD)), and / or any other volatile memory or non-volatile, non-transitory device-readable and / or computer-executable memory device that stores information, data and / or instructions that can be used by the processing circuit 1002. The memory 1004 may store any suitable instructions, data or information, including computer programs, software, applications including one or more of logic, rules, codes, tables, and / or other instructions that can be executed by the processing circuit 1002 and used by the network node 1000. The memory 1004 may be used to store any calculations performed by the processing circuit 1002 and / or any data received via the communication interface 1006. In some embodiments, the processing circuit 1002 and the memory 1004 are integrated together.
[0147] The communication interface 1006 is used for wired or wireless communication of signaling and / or data between network nodes, access networks and / or UEs. As shown, the communication interface 1006 includes a port / terminal 1016 for sending data to and receiving data from the network, for example, via a wired connection. The communication interface 1006 also includes a radio front-end circuit 1018, which can be coupled to the antenna 1010, or in some embodiments, to a part of the antenna 1010. The radio front-end circuit 1018 includes a filter 1020 and an amplifier 1022. The radio front-end circuit 1018 can be connected to the antenna 1010 and the processing circuit 1002. The radio front-end circuit 1018 can be configured to adjust the signal transmitted between the antenna 1010 and the processing circuit 1002. The radio front-end circuit 1018 can receive digital data to be sent to other network nodes or UEs via a wireless connection. The radio front-end circuit 1018 can use a combination of a filter 1020 and / or an amplifier 1022 to convert the digital data into a radio signal with appropriate channel and bandwidth parameters. The radio signal may then be transmitted via antenna 1010. Similarly, when data is received, antenna 1010 may collect the radio signal, which may then be converted to digital data by radio front end circuit 1018. The digital data may be passed to processing circuit 1002. In other embodiments, communication interface 1006 may include different components and / or different combinations of components.
[0148] In certain alternative embodiments, the network node 1000 does not include a separate radio front end circuit 1018; instead, the processing circuit 1002 includes the radio front end circuit and is connected to the antenna 1010. Similarly, in some embodiments, all or some of the RF transceiver circuit 1012 is part of the communication interface 1006. In yet another embodiment, the communication interface 1006 includes one or more ports or terminals 1016, the radio front end circuit 1018, and the RF transceiver circuit 1012 as part of a radio unit (not shown), and the communication interface 1006 communicates with the baseband processing circuit 1014, which is part of the digital unit (not shown).
[0149] Antenna 1010 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals. Antenna 1010 may be coupled to radio front end circuit 1018 and may be any type of antenna capable of wirelessly sending and receiving data and / or signals. In some embodiments, antenna 1010 is separate from network node 1000 and may be connected to network node 1000 via an interface or port.
[0150] The antenna 1010, the communication interface 1006 and / or the processing circuit 1002 may be configured to perform any receiving operation and / or certain obtaining operations performed by the network node 1000 described herein. Any information, data and / or signal may be received from a UE, another network node and / or any other network device. Similarly, the antenna 1010, the communication interface 1006 and / or the processing circuit 1002 may be configured to perform any sending operation performed by the network node 1000 described herein. Any information, data and / or signal may be sent to a UE, another network node and / or any other network device.
[0151] The power supply 1008 provides power to the various components of the network node 1000 in a form suitable for the various components (e.g., at the voltage and current levels required by each corresponding component). The power supply 1008 may also include power management circuitry or be coupled to power management circuitry to supply power to the components of the network node 1000 for performing the functions described herein. For example, the network node 1000 may be connected to an external power source (e.g., a power grid or a power outlet) via an input circuit or interface (such as a cable), whereby the external power source supplies power to the power circuit of the power supply 1008. As another example, the power supply 1008 may include a power source in the form of a battery or battery pack, which is connected to the power circuit or integrated in the power circuit. If the external power source fails, the battery can provide backup power.
[0152] Embodiments of network node 1000 may include beyond Fig.10Additional components to the components shown are used to provide certain aspects of the functionality of the network node (including any functionality described herein and / or any functionality required to support the subject matter described herein). For example, the network node 1000 may include a user interface device to allow information to be input into the network node 1000 and to allow information to be output from the network node 1000. This may allow a user to perform diagnostic, maintenance, repair, and other management functions for the network node 1000.
[0153] Fig.11 is a block diagram of a host 1100 according to various aspects described herein, which host 1100 may be Figure 8 100 is an embodiment of a host 816 of the present invention. As used herein, the host 1100 can be or include various combinations of hardware and / or software (including processing resources in a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, a container, or a server cluster). The host 1100 can provide one or more services to one or more UEs.
[0154] Host 1100 includes processing circuitry 1102, which is operably coupled to input / output interface 1106, network interface 1108, power supply 1110, and memory 1112 via bus 1104. Other components may be included in other embodiments. The features of these components may be substantially similar to those described with respect to previous figures (such as Fig. 9 and Fig.10 ) so that its description is generally applicable to corresponding components of the host 1100.
[0155] The memory 1112 may include one or more computer programs including data 1116 and one or more host applications 1114, which may include user data, such as data generated by a UE for the host 1100, or data generated by the host 1100 for the UE. An embodiment of the host 1100 may utilize only a subset or all of the components shown. The host application 1114 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), Moving Picture Experts Group (MPEG), VP9) and audio codecs (e.g., Free Lossless Audio Codec (FLAC), Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for a variety of different categories, types, or implementations of UE (e.g., mobile phones, desktop computers, wearable display systems, and head-up display systems). The host application 1114 may also provide user authentication and permission checks, and may periodically report health status, routing, and content availability to a central node (such as a device in a core network or a device on the edge of a core network). Thus, the host 1100 can select and / or indicate to the UE a different host for an over-the-top (OTT) service. The host application 1114 can support various protocols, such as HTTP Live Streaming (HLS) protocol, Real-time Messaging Protocol (RTMP), Real-time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (DASH or MPEG-DASH), etc.
[0156] Fig.12 1 is a block diagram showing a virtualized environment 1200 in which the functions implemented by some embodiments may be virtualized. In this context, virtualization means creating a virtual version of an apparatus or device that may include a virtualized hardware platform, storage device, and network resources. As used herein, virtualization may be applied to any device or component thereof described herein, and involves an implementation in which at least a portion of the functions are implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1200 hosted by one or more of a hardware node (such as a hardware computing device operating as a network node, UE, core network node, or host). In addition, in embodiments where a virtual node does not require a radio connection (e.g., a core network node or host), the node may be fully virtualized.
[0157] An application 1202 (which may alternatively be referred to as a software instance, a virtual application, a network function, a virtual node, a virtual network function, etc.) runs in a virtualized environment 1200 to implement some features, functions, and / or benefits of some embodiments disclosed herein.
[0158] Hardware 1204 includes processing circuitry, memory storing software and / or instructions that can be executed by the hardware processing circuitry, and / or other hardware devices described herein (such as network interfaces, input / output interfaces, etc.). The software can be executed by the processing circuitry to instantiate one or more virtualization layers 1206 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1208A and VMs 1208B (one or more of which can be generally referred to as VMs 1208), and / or perform any functions, features, and / or benefits described in connection with some embodiments described herein. Virtualization layer 1206 can present a virtual operating platform to VMs 1208 that looks like network hardware.
[0159] VM 1208 includes virtual processing, virtual memory, virtual network or interface, and virtual storage, and can be run by corresponding virtualization layer 1206. Different embodiments of instances of virtual device 1202 can be implemented on one or more VMs 1208, and these implementations can be made in different ways. In some contexts, virtualization of hardware is referred to as network function virtualization (NFV). NFV can be used to unify many types of network equipment into industry standard high-capacity server hardware, physical switches, and physical storage, which can be located in data centers and customer premises equipment.
[0160] In the context of NFV, VM 1208 can be a software implementation of a physical machine that runs programs as if they were executed on a physical, non-virtualized machine. Each VM 1208 and the hardware portion of 1204 that executes the VM (whether it is hardware dedicated to the VM and / or hardware shared by the VM and other VMs 1208) form a separate virtual network element. Still in the context of NFV, a virtual network function is responsible for handling a specific network function running in one or more VMs 1208 on the hardware 1204 and corresponding to an application 1202.
[0161] The hardware 1204 may be implemented in a standalone network node with general or specific components. The hardware 1204 may implement some functions via virtualization. Alternatively, the hardware 1204 may be part of a larger hardware cluster (e.g., in a data center or CPE), where many hardware nodes work together and are managed by management and coordination 1210, which oversees, among other things, the lifecycle management of the application 1202. In some embodiments, the hardware 1204 is coupled to one or more radio units, each of which includes one or more transmitters and one or more receivers that may be coupled to one or more antennas. The radio unit may communicate directly with other hardware nodes via one or more appropriate network interfaces, and may be used in conjunction with virtual components to provide radio capabilities to virtual nodes (e.g., RAN or BS). In some embodiments, some signaling may be provided by using a control system 1212, which may alternatively be used for communication between hardware nodes and radio units.
[0162] Fig.13 A communication diagram is shown in which a host 1302 communicates with a UE 1306 via a network node 1304 over a partially wireless connection according to some embodiments. Fig.13 Describe the UE discussed in the previous paragraph (such as Figure 8 UE 812A and / or Fig. 9 UE 900), network nodes (such as Figure 8 The network node 810A and / or Fig.10 network nodes 1000) and hosts (such as Figure 8 Host 816 and / or Fig.11 An example implementation of a host 1100 according to various embodiments.
[0163] Similar to the host 1100, an embodiment of the host 1302 includes hardware, such as a communication interface, a processing circuit, and a memory. The host 1302 also includes software that is stored in the host 1302 or can be accessed by the host 1302 and can be executed by the processing circuit. The software includes a host application that is operable to provide services to a remote user, such as a UE 1306 connected via an OTT connection 1350 extending between the UE 1306 and the host 1302. In providing services to the remote user, the host application can provide user data sent using the OTT connection 1350.
[0164] The network node 1304 includes hardware that enables it to communicate with the host 1302 and the UE 1306 via a connection 1360. The connection 1360 may be a direct connection or through a core network (such as Figure 8The core network 806 of the present invention and / or one or more other intermediate networks (such as one or more public, private or managed networks) are connected. For example, the intermediate network can be a backbone network or the Internet.
[0165] UE 1306 includes hardware and software, which is stored in UE 1306 or accessible by UE 1306 and can be executed by the processing circuit of UE. The software includes a client application (such as a web browser or operator-specific "app"), which is operable to provide services to human or non-human users via UE 1306 with the support of host 1302. In host 1302, the executing host application can communicate with the executing client application via OTT connection 1350, which terminates UE 1306 and host 1302. When providing services to users, the client application of UE can receive request data from the host application of the host and provide user data in response to the request data. OTT connection 1350 can send both request data and user data. The client application of UE can interact with the user to generate user data provided to the host application via OTT connection 1350.
[0166] The OTT connection 1350 may extend via a connection 1360 between the host 1302 and the network node 1304 and via a wireless connection 1370 between the network node 1304 and the UE 1306 to provide connectivity between the host 1302 and the UE 1306. The connection 1360 and the wireless connection 1370 through which the OTT connection 1350 may be provided have been drawn abstractly to illustrate communications between the host 1302 and the UE 1306 via the network node 1304 without explicitly involving any intermediate devices and the precise routing of messages via those devices.
[0167] As an example of sending data via OTT connection 1350, in step 1308, host 1302 provides user data, which can be performed by executing a host application. In some embodiments, the user data is associated with a specific human user who interacts with UE 1306. In other embodiments, the user data is associated with UE 1306, which shares data with host 1302 without explicit human interaction. In step 1310, host 1302 initiates a transmission to UE 1306, which carries the user data. Host 1302 may initiate the transmission in response to a request sent by UE 1306. The request may be caused by human interaction with UE 1306 or by the operation of a client application executed on UE 1306. In accordance with the teachings of the embodiments described throughout the present disclosure, the transmission may be delivered via network node 1304. Thus, in step 1312, in accordance with the teachings of the embodiments described throughout the present disclosure, network node 1304 sends the user data carried in the transmission initiated by host 1302 to UE 1306. In step 1314, UE 1306 receives the user data carried in the transmission, which may be performed by a client application executing on UE 1306 that is associated with a host application executed by host 1302.
[0168] In some examples, UE 1306 executes a client application that provides user data to host 1302. User data may be provided as a reaction or response to data received from host 1302. Therefore, in step 1316, UE 1306 may provide user data, which may be performed by executing the client application. When providing user data, the client application may also consider user input received from a user via an input / output interface of UE 1306. Regardless of the specific manner in which user data is provided, in step 1318, UE 1306 initiates a transmission of user data to host 1302 via network node 1304. In step 1320, in accordance with the teachings of the embodiments described throughout the present disclosure, network node 1304 receives user data from UE 1306 and initiates sending the received user data to host 1302. In step 1322, host 1302 receives the user data carried in the transmission initiated by UE 1306.
[0169] One or more of the various embodiments improve the performance of OTT services provided to UE 1306 using OTT connection 1350, in which wireless connection 1370 forms the final part. More specifically, the teachings of these embodiments can improve, for example, data rate, latency, power consumption, etc., and thereby provide benefits such as reduced user waiting time, relaxed restrictions on file size, improved content resolution, better responsiveness, extended battery life, etc.
[0170] In an example scenario, the host 1302 may collect and analyze plant status information. As another example, the host 1302 may process audio and video data that may have been retrieved from the UE for creating a map. As another example, the host 1302 may collect and analyze real-time data to help control vehicle congestion (e.g., control traffic lights). As another example, the host 1302 may store monitoring videos uploaded by the UE. As another example, the host 1302 may store or control access to media content such as video, audio, VR, or AR, which may be broadcast, multicast, or unicast to the UE. As other examples, the host 1302 may be used for energy pricing, remote control of non-time-critical power loads to balance power generation demand, positioning services, presentation services (e.g., compiling charts based on data collected from remote devices, etc.), or any other function of collecting, retrieving, storing, analyzing, and / or sending data.
[0171] In some examples, a measurement process may be provided for monitoring data rate, latency, and other factors that are the object of improvement of one or more embodiments. There may also be an optional network function for reconfiguring the OTT connection 1350 between the host 1302 and the UE 1306 in response to changes in the measurement results. The measurement process and / or the network function for reconfiguring the OTT connection 1350 may be implemented in the software and hardware of the host 1302 and / or the UE 1306. In some embodiments, sensors (not shown) may be deployed in other devices through which the OTT connection 1350 passes, or associated with the other devices; the sensors may participate in the measurement process by providing the values of the monitored quantities shown above, or by providing the values of other physical quantities from which the software can calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 1350 may include message formats, retransmission settings, preferred routes, etc.; the reconfiguration does not require direct changes to the operation of the network node 1304. Such processes and functions may be known and practiced in the art. In some embodiments, the measurements may involve proprietary UE signaling that facilitates the host 1302 to measure throughput, propagation time, latency, etc. The measurements may be accomplished by software using the OTT connection 1350 to send messages (particularly empty or "dummy" messages) while monitoring propagation time, errors, etc.
[0172] Although the computing devices (e.g., UE, network node, host) described herein may include a combination 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 a processing circuit, which may process information by, for example, converting the obtained information to other information, comparing the obtained information or the converted information with the information stored in the network node, and / or performing one or more operations based on the obtained information or the converted information, and making a determination based on the result of the processing. In addition, although the components are depicted as a single box located within a larger box or nested within multiple boxes, in fact, the computing device may include multiple different physical components constituting a single illustrated component, and the functions may be divided between separate components. For example, a communication interface may be configured to include any component described herein, and / or the functions of the components may be divided between the processing circuit and the communication interface. In another example, the non-computationally intensive functions of any such component may be implemented in software or firmware, and the computationally intensive functions may be implemented in hardware.
[0173] In some embodiments, some or all of the functions described herein may be provided by a processing circuit that executes instructions stored in a memory, which in some embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functions may be provided by a processing circuit, for example, in a hardwired manner, without executing instructions stored on a separate or discrete device-readable storage medium. In any of these specific embodiments, the processing circuit may be configured to perform the described functions, regardless of whether instructions stored on a non-transitory computer-readable storage medium are executed. The benefits provided by such functionality are not limited to separate processing circuits or to other components of a computing device, but are enjoyed by the computing device as a whole and / or are generally enjoyed by end users and wireless networks.
[0174] Example
[0175] Group A Embodiment
[0176] Embodiment 1: A method for determining a unified transmission configuration indication (TCI) state performed by a user equipment, the method comprising one or more of the following items: a. if a single aperiodic (AP) channel state information-reference signal (CSI-RS) resource is included in a non-zero power (NZP) CSI-RS resource set triggered by downlink control information (DCI): i. if the DCI is carried by a physical downlink control channel (PDCCH) in a control resource set (CORESET) associated with a SS set that is not linked to any other search space (SS) set, receiving the AP using a unified TCI state for receiving the PDCCH CSI-RS resource; ii. If the DCI is carried by repeated PDCCHs in two CORESETs respectively associated with one of the two linked SS sets, the APCSI-RS is received using a unified TCI state for receiving the PDCCH in one of the two CORESETs, and one of the two CORESETs may be a CORESET associated with the SS set having the smaller SS set index of the two SS sets; iii. If the DCI is carried by a single frequency network SFN PDCCH in a CORESET associated with two unified TCI states, the AP CSI-RS is received using one of the unified TCI states (i.e., the first unified TCI state or the second unified TCI state); b. If two AP CSI-RS resources or AP CSI-RS resource groups are in the CSI-RS resource set triggered by the DCI, the first AP CSI-RS resource and the second AP CSI-RS resource or AP The CSI-RS resource groups are associated with the first unified TCI state and the second unified TCI state, respectively, wherein the first CSI-RS resource and the second CSI-RS resource are in the order configured in the CSI-RS resource set; c. If a single semi-persistent SP CSI-RS resource in the NZP CSI-RS resource set is activated by the media access control MAC control element CE: i. If the MAC CE is carried by a physical downlink shared channel PDSCH received using a single unified TCI state, the SP CSI-RS resource is also received using the unified TCI state; ii. If the MAC CE is carried by a PDSCH received using both the first unified TCI state and the second unified TCI state at the same or different times, the SP CSI-RS is also received using one of the two unified TCI states; d.If two SP CSI-RS resources or two groups of SP CSI-RS resources are in the NZP CSI-RS resource set activated by the MAC CE, the first SP CSI-RS resource and the second SP CSI-RS resource or the SP CSI-RS resource group are associated with the first unified TCI state and the second unified TCI state, respectively, wherein the first CSI-RS resource and the second CSI-RS resource are in the order configured in the CSI-RS resource set; e. If more than two AP or SP CSI-RS resources in the CSI-RS resource set are triggered by DCI or activated by MAC CE, the CSI-RS resources are received according to the quasi co-location (QCL) information configured or indicated for each CSI-RS resource in the corresponding aperiodic CSI triggering state or in the activated MAC CE. .
[0177] Embodiment 2: A method for determining a unified TCI state performed by a user equipment, the method comprising one or more of the following items: a. For AP CSI-RS, a unified TCI state pointer can be configured for an associated CSI-RS resource set or for each NZP CSI-RS resource in a CSI-RS resource set in an associated non-periodic CSI triggering state; b. For SP CSI-RS, a unified TCI state pointer can be indicated for each SP CSI-RS resource in an activated MAC CE; c. For periodic CSI-RS, a unified TCI state pointer can be configured in each periodic NZP CSI-RS resource.
[0178] Embodiment 3: The method according to any of the above embodiments further includes:
[0179] providing user data; and forwarding the user data to the host via a transmission to a network node.
[0180] Group B Example
[0181] Embodiment 4: A method for indicating a unified transmission configuration indication TCI state, performed by a network node, the method comprising one or more of the following items: a. If a single aperiodic (AP) channel state information-reference signal (CSI-RS) resource is included in a non-zero power (NZP) CSI-RS resource set triggered by downlink control information (DCI): i. If the DCI is carried by a physical downlink control channel (PDCCH) in a control resource set (CORESET) associated with an SS set that is not linked to any other search space (SS) set, the AP CSI-RS resource is received using a unified TCI state for receiving the PDCCH; ii. If the DCI is carried by a PDCCH repeated in two CORESETs respectively associated with one of two linked SS sets, the AP is received using a unified TCI state for receiving the PDCCH in one of the two CORESETs. CSI-RS, one of the two CORESETs may be a CORESET associated with the SS set having the smaller SS set index in the two SS sets; iii. if the DCI is carried by a single frequency network SFN PDCCH in a CORESET associated with two unified TCI states, one of the unified TCI states (i.e., the first unified TCI state or the second unified TCI state) is used to receive the AP CSI-RS; b. if two AP CSI-RS resources or AP CSI-RS resource groups are in a CSI-RS resource set triggered by DCI, the first AP CSI-RS resource and the second AP CSI-RS resource or AP CSI-RS resource group are associated with the first unified TCI state and the second unified TCI state, respectively, wherein the first CSI-RS resource and the second CSI-RS resource are in the order configured in the CSI-RS resource set; c. if a single semi-persistent SP CSI-RS resource in the NZP CSI-RS resource set is activated by the media access control MAC control unit CE: i. if MAC CE is carried by a physical downlink shared channel PDSCH received using a single unified TCI state, then the unified TCI state is also used to receive SP CSI-RS resources; ii. If the MAC CE is carried by a PDSCH received using both the first unified TCI state and the second unified TCI state at the same or different times, then one of the two unified TCI states is also used to receive SP CSI-RS; d.If two SP CSI-RS resources or two groups of SP CSI-RS resources are in the NZP CSI-RS resource set activated by the MAC CE, the first SP CSI-RS resource and the second SP CSI-RS resource or the SP CSI-RS resource group are associated with the first unified TCI state and the second unified TCI state, respectively, wherein the first CSI-RS resource and the second CSI-RS resource are in the order configured in the CSI-RS resource set; e. If more than two AP or SP CSI-RS resources in the CSI-RS resource set are triggered by DCI or activated by MAC CE, the CSI-RS resources are received according to the quasi co-location (QCL) information configured or indicated for each CSI-RS resource in the corresponding aperiodic CSI triggering state or in the activated MAC CE. .
[0182] Embodiment 5: A method for indicating a unified transmission configuration indicating a TCI state, performed by a network node, the method comprising one or more of the following items: a. For AP CSI-RS, a unified TCI state pointer can be configured for an associated CSI-RS resource set or for each NZP CSI-RS resource in a CSI-RS resource set in an associated non-periodic CSI trigger state; b. For SP CSI-RS, a unified TCI state pointer can be indicated for each SP CSI-RS resource in an activated MAC CE; c. For periodic CSI-RS, a unified TCI state pointer can be configured in each periodic NZP CSI-RS resource.
[0183] Embodiment 6: The method according to any of the aforementioned embodiments further includes: obtaining user data; and forwarding the user data to a host or a user device.
[0184] Group C Example
[0185] Embodiment 7: A user device for determining a unified transmission configuration indication TCI state, comprising: a processing circuit configured to execute any steps described in any embodiment of Group A; and a power supply circuit configured to supply power to the processing circuit.
[0186] Embodiment 8: A network node for indicating a unified transmission configuration indication (TCI) status, the network node comprising: a processing circuit configured to execute any steps described in any embodiment of Group B; a power supply circuit configured to supply power to the processing circuit.
[0187] Embodiment 9: A user equipment (UE) for determining a unified transmission configuration indication (TCI) state, the UE comprising: an antenna configured to send and receive wireless signals; a radio front-end circuit connected to the antenna and a processing circuit and configured to adjust signals communicated between the antenna and the processing circuit; a processing circuit configured to perform any steps described in any of the embodiments in Group A; an input interface connected to the processing circuit and configured to allow information to be input into the UE for processing by the processing circuit; an output interface connected to the processing circuit and configured to output information that has been processed by the processing circuit from the UE; and a battery connected to the processing circuit and configured to supply power to the UE.
[0188] Embodiment 10: A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: a processing circuit configured to provide user data; and a network interface configured to initiate sending user data to a cellular network for sending to a user equipment (UE), wherein the UE comprises a communication interface and a processing circuit, the communication interface and processing circuit of the UE being configured to perform any steps described in any of the embodiments in Group A to receive user data from the host.
[0189] Embodiment 11: The host according to the above embodiment, wherein the cellular network further comprises a network node, which is configured to communicate with the UE to send user data from the host to the UE.
[0190] Embodiment 12: A host according to the two aforementioned embodiments, wherein: the processing circuit of the host is configured to execute a host application to provide 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.
[0191] Embodiment 13: A method implemented by a host operating in a communication system, the communication system also including a network node and a user equipment (UE), the method comprising: providing user data to the UE; and initiating a transmission to the UE via a cellular network including the network node, the transmission carrying the user data, wherein the UE performs any operation described in any of the embodiments in Group A to receive the user data from the host.
[0192] Embodiment 14: The method according to the aforementioned embodiment further includes: at a host, executing a host application associated with a client application executed on a UE to receive user data from the UE.
[0193] Embodiment 15: The method according to the aforementioned embodiment further includes: at the host, sending input data to the client application executed on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.
[0194] Embodiment 16: A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: a processing circuit configured to provide user data; and a network interface configured to initiate sending user data to a cellular network for sending to a user equipment (UE), wherein the UE comprises a communication interface and a processing circuit, the communication interface and processing circuit of the UE being configured to perform any steps described in any of the embodiments in Group A to send user data to the host.
[0195] Embodiment 17: The host according to the above embodiment, wherein the cellular network further comprises a network node configured to communicate with the UE to send user data from the UE to the host.
[0196] Embodiment 18: A host according to the first two embodiments, wherein: the processing circuit of the host is configured to execute a host application to provide 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.
[0197] Embodiment 19: A method implemented by a host configured to operate in a communication system, the communication system also including a network node and a user equipment (UE), the method comprising: at the host, receiving user data sent to the host by the UE via the network node, wherein the UE performs any steps described in any embodiment of Group A to send user data to the host.
[0198] Embodiment 20: The method according to the aforementioned embodiment further includes: at a host, executing a host application associated with a client application executed on a UE to receive user data from the UE.
[0199] Embodiment 21: The method according to the aforementioned embodiment further includes: at the host, sending input data to the client application executed on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.
[0200] Embodiment 22: A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: a processing circuit configured to provide user data; and a network interface configured to initiate sending user data to a network node in a cellular network to send to a user equipment (UE), the network node having a communication interface and a processing circuit, the processing circuit of the network node being configured to perform any operation described in any of the embodiments in Group B to send user data from the host to the UE.
[0201] Embodiment 23: A host according to the preceding embodiment, wherein: a processing circuit of the host is configured to execute a host application, which provides user data; and the UE includes a processing circuit, which is configured to execute a client application associated with the host application to receive a transmission of user data from the host.
[0202] Embodiment 24: A method implemented in a host configured to operate in a communication system, the communication system also including a network node and a user equipment (UE), the method comprising: providing user data to the UE; and initiating a transmission to the UE via a cellular network including the network node, the transmission carrying the user data, wherein the network node performs any operation described in any of the embodiments in Group B to send the user data from the host to the UE.
[0203] Embodiment 25: The method according to the aforementioned embodiment further includes: at the network node, sending user data provided by the host to the UE.
[0204] Embodiment 26: A method according to any one of the two preceding embodiments, wherein user data is provided at the host by executing a host application, the host application interacting with a client application executed on the UE, the client application being associated with the host application.
[0205] Embodiment 27: A communication system configured to provide an over-the-top service, the communication system comprising: a host, including: a processing circuit configured to provide user data to a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate sending the user data to a cellular network node for sending to the UE, the network node having a communication interface and a processing circuit, the processing circuit of the network node being configured to perform any operation described in any of the embodiments in Group B to send the user data from the host to the UE.
[0206] Embodiment 28: The communication system according to the aforementioned embodiment further includes: a network node; and / or a user equipment.
[0207] Embodiment 29: A host is configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: a processing circuit configured to initiate reception of user data; and a network interface configured to receive user data from a network node in a cellular network, the network node having a communication interface and a processing circuit, the processing circuit of the network node being configured to perform any operation described in any of the embodiments in Group B for the host to receive user data from a user equipment (UE).
[0208] Embodiment 30: A host according to the first two embodiments, wherein: the processing circuit of the host is configured to execute a host application to provide 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.
[0209] Embodiment 31: A host according to any one of the preceding two embodiments, wherein initiating reception of user data comprises requesting user data.
[0210] Embodiment 32: A method implemented by a host configured to operate in a communication system, the communication system also including a network node and a user equipment (UE), the method comprising: at the host, initiating reception of user data from the UE, the user data originating from a transmission already received by the network node from the UE, wherein the network node performs any steps described in any of the embodiments in Group B to receive user data from the UE for the host.
[0211] Embodiment 33: The method according to the aforementioned embodiment further includes: at the network node, sending the received user data to the host.
[0212] At least some of the following abbreviations may be used in the present disclosure. If there is an inconsistency between abbreviations, how it is used above shall take precedence. If listed multiple times below, the first listing shall take precedence over any subsequent listings. •3GPP 3rd Generation Partnership Project •5G fifth generation •5GC fifth generation core •5GS fifth generation system •AF application function •AMF access and mobility functions •AN access network •AP Access Point • ASIC Application Specific Integrated Circuit •AUSF authentication server function •CPU Central Processing Unit •DN Data Network • DSP digital signal processor • eNB enhancement or evolved NodeB •EPS Evolved Packet System • E-UTRA Evolved Universal Terrestrial Radio Access • FPGA Field Programmable Gate Array • gNB New Radio Base Station • gNB-DU New Radio Base Station Distributed Unit •HSS Home Subscriber Server •IoT • Internet Protocol • LTE Long Term Evolution •MME mobility management entity •MTC Machine Type Communication •NEF network open function •NF network function • NR New Radio • NRF Network Function Repository Function •NSSF network slice selection function •OTT Over the Top •PC Personal Computer •PCF policy control function •P-GW Packet Data Network Gateway •QoS Quality of Service • RAM Random Access Memory • RAN Radio Access Network • ROM Read Only Memory •RRH Remote Radio Head •RTT Round Trip Time •SCEF service capability exposure function •SMF session management function •UDM unified data management •UE User Equipment •UPF user plane function
[0213] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered to fall within the scope of the concepts disclosed herein.
Claims
1. A method for determining a unified transmission configuration indication (TCI) state, performed by a user equipment (UE) (900), the method comprising: Receiving a configuration of an aperiodic AP channel state information (CSI) triggering state and a configuration of a CSI report associated with the aperiodic CSI triggering state, wherein the AP CSI triggering state includes an indication of a first non-zero power CSI reference signal (NZP) CSI-RS resource set in the CSI report configuration; Receiving first downlink control information DCI, where the first DCI indicates a first unified TCI state and a second unified TCI state; receiving second downlink control information DCI, where the second DCI indicates the aperiodic CSI triggering state; determining one of the first unified TCI state and the second unified TCI state based on an RRC configured TCI state pointer in the CSI reporting configuration; and The CSI-RS in the first NZP CSI-RS resource set is received using a spatial filter determined based on the determined unified TCI state.
2. The method according to claim 1, wherein: The TCI state pointer has two logic values, and wherein a first logic value is indicating the first unified TCI state, and a second logic value is indicating the second unified TCI state.
3. The method according to any one of claims 1 to 2, wherein: The second DCI is received within a specific time period after the first DCI ends.
4. The method according to any one of claims 1 to 3, wherein: A single aperiodic AP CSI-RS resource is included in the first NZP CSI-RS resource set triggered by the second downlink control information DCI.
5. The method according to any one of claims 2 to 4, wherein: If the second DCI is carried by a physical downlink control channel PDCCH in a control resource set CORESET associated with an SS set not linked to any other search space SS set, the AP CSI-RS resources are received using the same unified TCI state used to receive the PDCCH, wherein the unified TCI state is one of the first unified TCI state and the second unified TCI state.
6. The method according to any one of claims 2 to 5, wherein: If the second DCI is carried by PDCCHs repeated in two CORESETs respectively associated with one of two linked SS sets, the AP CSI-RS is received using a unified TCI state for receiving the PDCCH in one of the two CORESETs.
7. The method according to any one of claims 2 to 6, wherein: One of the two CORESETs may be a CORESET associated with the one of the two SS sets having a smaller SS set index of the two SS sets.
8. The method according to any one of claims 2 to 7, wherein: If the second DCI is carried by a single frequency network SFN PDCCH in a CORESET associated with two unified TCI states, the AP CSI-RS is received using one of the unified TCI states, namely the first unified TCI state or the second unified TCI state.
9. The method according to claim 1, wherein: Two AP CSI-RS resources or AP CSI-RS resource groups are included in the first NZP CSI-RS resource set triggered by the second DCI, and the first AP CSI-RS resource or AP CSI-RS resource group and the second AP CSI-RS resource or AP CSI-RS resource group are associated with the first unified TCI state and the second unified TCI state, respectively.
10. The method according to claim 9, wherein: The first AP CSI-RS resource and the second AP CSI-RS resource are in the order configured in the first NZP CSI-RS resource set.
11. The method according to claim 1, wherein: A single semi-persistent SP CSI-RS resource in the first NZP CSI-RS resource set is activated by a medium access control MAC element CE.
12. The method according to claim 11, wherein: If the MAC CE is carried by a physical downlink shared channel PDSCH received using a single unified TCI state, the SPCSI-RS resources are also received using the single unified TCI state, wherein the single unified TCI state is one of the first unified TCI state and the second unified TCI state.
13. The method according to any one of claims 11 to 12, wherein: If the MAC CE is carried by a PDSCH received using both the first unified TCI state and the second unified TCI state at the same or different times, the SP CSI-RS is also received using one of the first unified TCI state and the second unified TCI state.
14. The method according to claim 1, wherein: Two SP CSI-RS resources or two SP CSI-RS resource groups are included in a first NZP CSI-RS resource set activated by the MAC CE, and the first SP CSI-RS resource or SP CSI-RS resource group and the second SP CSI-RS resource or SP CSI-RS resource group are associated with the first unified TCI state and the second unified TCI state, respectively.
15. The method according to claim 14, wherein: The first SP CSI-RS resources and the second SP CSI-RS resources are in the order configured in the first NZP CSI-RS resource set.
16. The method according to claim 1, wherein: More than two AP or SP CSI-RS resources in the first NZP CSI-RS resource set are triggered by the second DCI or activated by the MAC CE, and the CSI-RS resources are received according to the quasi-co-site QCL information configured or indicated for each CSI-RS resource in the non-periodic CSI triggering state or in the activated MAC CE.
17. The method according to any one of claims 1 to 16, wherein: For AP CSI-RS, in the aperiodic CSI triggering state, a unified TCI state pointer is configured for the first NZP CSI-RS resource set or for each NZP CSI-RS resource in the first NZP CSI-RS resource set.
18. The method according to any one of claims 1 to 17, wherein: For SP CSI-RS, a unified TCI state pointer is indicated for each SP CSI-RS resource in the activation MAC CE.
19. The method according to any one of claims 1 to 18, wherein: For periodic CSI-RS, a unified TCI state pointer is configured in each periodic NZP CSI-RS resource.
20. The method according to any one of claims 16 to 19, wherein: The unified TCI state pointer indicates which of the first unified TCI state, the second unified TCI state, and the third unified TCI state will be used to receive the CSI-RS in each NZP CSI-RS resource in the first NZP CSI-RS resource set, wherein the third unified TCI state is the unified TCI state indicated in the QCL information configured in the non-periodic CSI trigger state.
21. A method for indicating a unified transmission configuration indication (TCI) state, performed by a network node (1000), the method comprising: Sending a configuration of an aperiodic AP channel state information (CSI) triggering state and a configuration of a CSI report associated with the aperiodic CSI triggering state, wherein the AP CSI triggering state includes an indication of a first non-zero power CSI reference signal (NZP) CSI-RS resource set in the CSI report configuration; Sending first downlink control information DCI, where the first DCI indicates a first unified TCI state and a second unified TCI state; Sending second downlink control information DCI, where the second DCI indicates the aperiodic CSI triggering state, wherein the second DCI is sent within a specific time period after the first DCI ends; and One or more CSI-RS resources in the first NZP CSI-RS resource set are transmitted using one of a first unified TCI state, a second unified TCI state, and a third unified TCI state.
22. The method according to claim 21, wherein: A single aperiodic AP CSI-RS resource is included in the first NZP CSI-RS resource set triggered by the second downlink control information DCI.
23. The method according to claim 22, wherein: If the second DCI is carried by a physical downlink control channel PDCCH in a control resource set CORESET associated with an SS set not linked to any other search space SS set, the AP CSI-RS resources are sent using the same unified TCI state used to send the PDCCH, wherein the unified TCI state is one of a first unified TCI state, a second unified TCI state, and a third unified TCI state.
24. The method according to any one of claims 22 to 23, wherein: If the second DCI is carried by PDCCHs repeated in two CORESETs respectively associated with one of two linked SS sets, the AP CSI-RS is transmitted using a unified TCI state for transmitting the PDCCH in one of the two CORESETs.
25. The method according to any one of claims 22 to 24, wherein: One of the two CORESETs may be a CORESET associated with the one of the two SS sets having a smaller SS set index of the two SS sets.
26. The method according to any one of claims 22 to 25, wherein: If the second DCI is carried by a single frequency network SFN PDCCH in a CORESET associated with two unified TCI states, the AP CSI-RS is sent using one of the unified TCI states, namely the first unified TCI state or the second unified TCI state.
27. The method of claim 21, wherein: Two AP CSI-RS resources or AP CSI-RS resource groups are included in the first NZP CSI-RS resource set triggered by the second DCI, and the first AP CSI-RS resource or AP CSI-RS resource group and the second AP CSI-RS resource or AP CSI-RS resource group are associated with the first unified TCI state and the second unified TCI state, respectively.
28. The method according to claim 27, wherein: The first CSI-RS resource and the second CSI-RS resource are in an order configured in the first NZP CSI-RS resource set.
29. The method according to claim 21, wherein: A single semi-persistent SP CSI-RS resource in the NZP CSI-RS resource set is activated by the medium access control MAC element CE.
30. The method of claim 29, wherein: If the MAC CE is carried by a physical downlink shared channel PDSCH sent using a single unified TCI state, the SPCSI-RS resources are also sent using the single unified TCI state, wherein the single unified TCI state is one of the first unified TCI state and the second unified TCI state.
31. The method according to any one of claims 29 to 30, wherein: If the MAC CE is carried by a PDSCH transmitted using both the first unified TCI state and the second unified TCI state at the same or different times, the SP CSI-RS is also transmitted using one of the first unified TCI state and the second unified TCI state.
32. The method of claim 21, wherein: Two SP CSI-RS resources or two SP CSI-RS resource groups are included in a first NZP CSI-RS resource set activated by the MAC CE, and the first SP CSI-RS resource or SP CSI-RS resource group and the second SP CSI-RS resource or SP CSI-RS resource group are associated with the first unified TCI state and the second unified TCI state, respectively.
33. The method of claim 32, wherein: The first SP CSI-RS resources and the second SP CSI-RS resources are in the order configured in the first NZP CSI-RS resource set.
34. The method of claim 21, wherein: More than two APs or SPCSI-RS resources in the first CSI-RS resource set are triggered by the second DCI or activated by the MAC CE, and the CSI-RS resources are sent according to the quasi-co-site QCL information configured or indicated for each CSI-RS resource in the non-periodic CSI triggering state or in the activated MAC CE.
35. The method according to any one of claims 21 to 31, wherein: For AP CSI-RS, in the aperiodic CSI triggering state, a unified TCI state pointer is configured for the first NZP CSI-RS resource set or for each NZP CSI-RS resource in the first NZP CSI-RS resource set.
36. The method according to any one of claims 21 to 32, wherein: For SP CSI-RS, a unified TCI state pointer is indicated for each SP CSI-RS resource in the activation MAC CE.
37. The method according to any one of claims 21 to 36, wherein: For periodic CSI-RS, a unified TCI state pointer is configured in each periodic NZP CSI-RS resource.
38. A method according to any one of claims 34 to 37, wherein: The unified TCI state pointer indicates which of the first unified TCI state, the second unified TCI state, and the third unified TCI state will be used to send the CSI-RS in each NZP CSI-RS resource in the first NZP CSI-RS resource set, wherein the third unified TCI state is the unified TCI state indicated in the QCL information configured in the non-periodic CSI trigger state.
39. A user equipment UE (900) for determining a unified transmission configuration indication TCI state, comprising: The processing circuit (902) is configured to perform the steps: Receiving a configuration of an aperiodic AP channel state information (CSI) triggering state and a configuration of a CSI report associated with the aperiodic CSI triggering state, wherein the AP CSI triggering state includes an indication of a first non-zero power CSI reference signal (NZP) CSI-RS resource set in the CSI report configuration; Receiving first downlink control information DCI, where the first DCI indicates a first unified TCI state and a second unified TCI state; receiving second downlink control information DCI, where the second DCI indicates the aperiodic CSI triggering state; determining one of the first unified TCI state and the second unified TCI state based on an RRC configured TCI state pointer in the CSI reporting configuration; and The CSI-RS in the first NZP CSI-RS resource set is received using a spatial filter determined based on the determined unified TCI state.
40. The UE (900) according to claim 39, wherein The processing circuit (902) is further configured to perform the steps according to any one of claims 2 to 20.
41. A network node (1000) for indicating a unified transmission configuration indication (TCI) state, comprising: The processing circuit (1002) is configured to: Sending a configuration of an aperiodic AP channel state information (CSI) triggering state and a configuration of a CSI report associated with the aperiodic CSI triggering state, wherein the AP CSI triggering state includes an indication of a first non-zero power CSI reference signal (NZP) CSI-RS resource set in the CSI report configuration; Sending first downlink control information DCI, where the first DCI indicates a first unified TCI state and a second unified TCI state; Sending second downlink control information DCI, where the second DCI indicates the aperiodic CSI triggering state, wherein the second DCI is sent within a specific time period after the first DCI ends; and One or more CSI-RS resources in the first NZP CSI-RS resource set are transmitted using one of a first unified TCI state, a second unified TCI state, and a third unified TCI state.
42. The network node (1000) according to claim 41, wherein The processing circuit (1002) is further configured to perform the steps of any one of claims 22 to 38.
