Method for compact TRS configuration for NR ue

Abstract

A method for compact tracking reference signal (TRS) configuration for a new radio (NR) user equipment (UE) is provided. The possibilities and the number of information elements (IEs) included in its structure of a Channel State Information Reference Signal (CSI-RS) configuration framework by which TRSs are traditionally configured in connected mode are very large. It requires an IE that can be used to configure multiple groups (up to 16 groups) of zero power (ZP) and non-zero power (NZP) CSI-RS. Each of the groups may itself include a configuration having up to 64 resources. In order to be able to provide TRS configuration and availability information to UEs in a Radio Resource Control (RRC) idle / inactive state, a compact TRS mechanism by which a network is able to configure a specific TRS to the UE is disclosed.

Description

Divisional application This application is a divisional application of a patent application with application number 202180041032.4, application date April 12, 2021, and invention name “Method for compact TRS configuration for NR UE”. Related technologies

[0001] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 008,383, filed on April 10, 2020, the disclosure of which is hereby incorporated by reference in its entirety. Technical Field

[0002] The present disclosure relates to Tracking Reference Signal (TRS) configuration in a wireless communication system. Background Art

[0003] The 3rd Generation Partnership Project (3GPP) is defining technical specifications for New Radio (NR), such as the fifth generation (5G). In Release 15 (Rel-15) NR, a user equipment (UE) may be configured with up to four carrier bandwidth (BW) parts (BWPs) in the downlink (DL), where a single DL carrier BWP is active at a given time. The UE may be configured with up to four carrier BWPs in the uplink (UL), where a single UL carrier BWP is active at a given time. If the UE is configured with a supplementary UL, the UE may additionally be configured with up to four carrier BWPs in the supplementary UL, where a single supplementary UL carrier BWP is active at a given time.

[0004] For a given parameter set μ 1 The carrier BWP defines a set of consecutive physical resource blocks (PRBs) from 0 to Number, where i is the index of the carrier BWP. A resource block (RB) is defined as 12 consecutive subcarriers in the frequency domain.

[0005] As shown in Table 1, multiple orthogonal frequency division multiplexing (OFDM) parameter sets μ are supported in NR, where the subcarrier spacing Δf and the cyclic prefix for the carrier BWP are configured by different higher layer parameters for DL ​​and UL, respectively. Table 1: Supported transmission parameter sets. μ <![CDATA[Δf=2 μ *15[kHz]]]> Cyclic prefix 0 15 conventional 1 30 conventional 2 60 General, Extended 3 120 conventional 4 240 conventional Physical Channel

[0006] A DL physical channel corresponds to a set of resource elements that carry information originating from higher layers. The following DL physical channels are defined: Physical DL Shared Channel (PDSCH) Physical Broadcast Channel (PBCH) Physical DL Control Channel (PDCCH)

[0007] PDSCH is the primary physical channel used for unicast DL data transmission and also for transmission of random access response (RAR), specific system information blocks and paging information. PBCH carries basic system information required for UE to access the network. PDCCH is used to transmit DL control information (DCI) required for receiving PDSCH (mainly scheduling decisions), and UL scheduling grants to enable transmission on PUSCH.

[0008] A UL physical channel corresponds to a set of resource elements that carry information originating from higher layers. The following UL physical channels are defined: Physical UL Shared Channel (PUSCH) Physical UL Control Channel (PUCCH) Physical Random Access Channel (PRACH)

[0009] PUSCH is the UL counterpart of PDSCH. PUCCH is used by UE to transmit UL control information, including HARQ confirmation, channel state information report, etc. PRACH is used for random access preamble transmission. NR reference symbol

[0010] The ultra-lite design principle in NR aims to minimize the always-on transmissions present in earlier systems (e.g., Long Term Evolution (LTE) Cell-Specific Reference Signal (CRS) reference symbols). Instead, NR provides reference symbols (e.g., Synchronization Signal (SS) Blocks (SSBs)) periodically, by default once every 20 milliseconds (ms). In addition, for connected mode UEs, a set of reference symbols is typically provided for optimal link performance. Some of these reference symbols are described below. Channel State Information Reference Signal (CSI-RS) for tracking

[0011] A UE in Radio Resource Control (RRC) connected mode is expected to receive from the network the RRC layer UE-specific configuration of the configured NZP-CSI-RS-ResourceSet including the parameter trs-Info (e.g., parameters for Tracking Reference Signal (TRS)). For an NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info set to "true", the UE shall assume that antenna ports with the same port index of non-zero power (NZP) CSI-RS resources configured in the NZP-CSI-RS-ResourceSet are the same. For frequency range 1 (FR1), the UE may be configured with one or more NZP CSI-RS sets, where the NZP-CSI-RS-ResourceSet includes four periodic NZP CSI-RS resources in two consecutive time slots, with two periodic NZP CSI-RS resources in each time slot. If no two consecutive time slots are indicated as DL time slots by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigDedicated, the UE may be configured with one or more NZP CSI-RS sets, where the NZP-CSI-RS-ResourceSet includes two periodic NZP CSI-RS resources in one time slot. For frequency range 2 (FR2), a UE may be configured with one or more NZP CSI-RS sets, where the NZP-CSI-RS-ResourceSet includes two periodic CSI-RS resources in one slot, or with a NZP-CSI-RS-ResourceSet of four periodic NZP CSI-RS resources in two consecutive slots, where there are two periodic NZP CSI-RS resources in each slot.

[0012] A UE configured with an NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info may have CSI-RS resources configured as follows: • Periodic, where the CSI-RS resources in the NZP-CSI-RS-ResourceSet are configured with the same period, bandwidth, and subcarrier position. · Periodic CSI-RS resources in one set and aperiodic CSI-RS resources in a second set, where the aperiodic CSI-RS and periodic CSI-RS resources have the same bandwidth (have the same RB location) and the aperiodic CSI-RS and periodic CSI-RS resources are 'QCL-Type-A' and 'QCL-TypeD' (where applicable). For FR2, the UE does not expect the scheduling offset between the last symbol of the PDCCH carrying the triggering DCI and the first symbol of the aperiodic CSI-RS resources to be less than the ThresholdSched-Offset reported by the UE. The UE should expect the periodic CSI-RS resource set and the aperiodic CSI-RS resource set to be configured with the same number of CSI-RS resources and the same number of CSI-RS resources to be configured in one time slot. For an aperiodic CSI-RS resource set (if triggered), and if the associated periodic CSI-RS resource set is configured with four periodic CSI-RS resources in two consecutive time slots (two periodic CSI-RS resources in each time slot), the high-level parameter aperiodicTriggeringOffset indicates the triggering offset of the first time slot for the first two CSI-RS resources in the set.

[0013] The UE does not expect to be configured with a CSI-ReportConfig that is linked to a CSI-ResourceConfig containing an NZP-CSI-RS-ResourceSet configured with trs-Info and that is configured with the higher layer parameter timeRestrictionForChannelMeasurements set to 'configured'.

[0014] The UE does not expect to be configured with a CSI-ReportConfig with the higher layer parameter reportQuantity set to other than "none" for an aperiodic NZP CSI-RS resource set configured with trs-Info.

[0015] The UE is not expected to be configured with CSI-ReportConfig for a periodic NZP CSI-RS resource set configured with trs-Info.

[0016] The UE does not expect to be configured with an NZP-CSI-RS-ResourceSet configured with both trs-Info and repetition.

[0017] Each CSI-RS resource defined in clause 7.4.1.5.3 of Technical Specification (TS) 38.211 is configured by a higher layer parameter NZP-CSI-RS-Resource with the following restrictions: The time domain positions of two CSI-RS resources in one slot or four CSI-RS resources in two consecutive slots (which are the same across two consecutive slots) defined by the higher layer parameter CSI-RS-resourceMapping are given by one of the following: ο For FR1 and FR2, l∈{4,8}, l∈{5,9} or l∈{6,10}, οFor FR2, l∈{0,4}, l∈{1,5}, l∈{2,6}, l∈{3,7}, l∈{7,11}, l∈{8,12} or l∈{9,13}. Single-port CSI-RS resources with density ρ=3 given by Table 7.4.1.5.3-1 of TS 38.211 and the higher layer parameter density configured by CSI-RS-resourceMapping. The bandwidth of the CSI-RS resource given by the high-level parameter freqBand configured by CSI-RS-resourceMapping is 52 and The minimum value among RBs, or equal to RBs. For operation with shared spectrum channel access, the freqBand configured by CSI-RS-resourceMapping is 48 and The minimum value among RBs, or equal to RBs. If the bandwidth of the CSI-RS resource is greater than 52 RBs, the UE is not expected to be configured with 2 μ × a period of 10 time slots. The periodicity and slot offset of the periodic NZP CSI-RS resource as given by the higher-level parameter periodityAndOffset of the NZP-CSI-RS-Resource configuration is 2 μ X p One of the time slots, where X p =10, 20, 40 or 80, where μ is defined in clause 4.3 of TS38.211. • Same powerControlOffset and powerControlOffsetSS given by NZP-CSI-RS-Resource values ​​in all resources. NZP CSI-RS

[0018] The UE may be configured with one or more NZP CSI-RS resource set configurations indicated by the higher layer parameters CSI-ResourceConfig and NZP-CSI-RS-ResourceSet. Each NZP CSI-RS resource set includes K≥1 NZP CSI-RS resources.

[0019] The following parameters for which the UE shall assume non-zero transmit power for CSI-RS resources are configured via the higher layer parameters NZP-CSI-RS-Resource, CSI-ResourceConfig and NZP-CSI-RS-ResourceSet for each CSI-RS resource configuration: nzp-CSI-RS-ResourceId determines the CSI-RS resource configuration identifier. periodicityAndOffset defines the CSI-RS period and slot offset of periodic / semi-persistent CSI-RS. All CSI-RS resources in a set are configured with the same period, while the slot offsets of different CSI-RS resources can be the same or different. resourceMapping defines the port number, code division multiplexing (CDM) type, and OFDM symbol and subcarrier occupancy of CSI-RS resources within a slot given in clause 7.4.1.5 of TS 38.211. nrofPorts in resourceMapping defines the number of CSI-RS ports, where the allowed values ​​are given in clause 7.4.1.5 of TS38.211. The density in resourceMapping defines the CSI-RS frequency density per CSI-RS port per PRB, and the CSI-RS PRB offset for density values ​​of 1 / 2, where the allowed values ​​are given in clause 7.4.1.5 of TS 38.211. For density 1 / 2, the odd / even PRB allocation indicated in density is relative to the common resource block (CRB) grid. The cdm-Type in resourceMapping defines the CDM value and mode, where the allowed values ​​are given in clause 7.4.1.5 of TS 38.211. • powerControlOffset is the ratio of PDSCH energy per resource element (EPRE) to NZP CSI-RS EPRE assumed when the UE derives CSI feedback and takes values ​​in the range of [-8, 15] decibels (dB) with a 1 dB step size. • powerControlOffsetSS is the ratio of the assumed NZP CSI-RS EPRE to the synchronization signal (SS) / physical broadcast channel (PBCH) block EPRE. ·ScramblingID defines the scrambling ID of the CSI-RS with a length of 10 bits. The BWP-Id in the CSI-ResourceConfig defines in which BWP the configured CSI-RS is located. repetition in NZP-CSI-RS-ResourceSet is associated with a CSI-RS resource set and defines whether the UE can assume that the CSI-RS resources in the NZP CSI-RS resource set are transmitted using the same DL spatial domain transmit filter as described in clause 5.1.6.1.2 and can only be configured if the higher layer parameter reportQuantity associated with all reporting settings linked to the CSI-RS resource set is set to "cri-RSRP", "cri-SINR" or "none". qcl-InfoPeriodicCSI-RS contains a reference to a TCI-State indicating a quasi co-located (QCL) source RS and the QCL type. If the TCI-State is configured with reference to an RS with a "QCL-TypeD" association, the RS can be an SS / PBCH block located in the same or different component carrier (CC) / DL BWP or a CSI-RS resource configured as periodic in the same or different CC / DL BWP. The trs-Info in the NZP-CSI-RS-ResourceSet is associated with a CSI-RS resource set and for this resource set the UE may assume that the antenna ports with the same port index of the NZP CSI-RS resources configured in the NZP-CSI-RS-ResourceSet are the same as described in clause 5.1.6.1.1 and this trs-Info may be configured when the reporting setting is not configured or when the higher layer parameter reportQuantity associated with all reporting settings linked to the CSI-RS resource set is set to 'none'.

[0020] All CSI-RS resources in a set are configured with the same density and the same nrofPorts, except for NZP CSI-RS resources used for interference measurement. The UE expects all CSI-RS resources in a resource set to be configured with the same starting RB and number of RBs and the same cdm-Type.

[0021] The bandwidth and initial CRB index of the CSI-RS resources within the BWP (as defined in clause 7.4.1.5 of TS 38.211) are determined based on the higher-layer parameters nrofRB and startingRB, respectively, within the CSI-FrequencyOccupation information element (IE), which is configured by the higher-layer parameter freqBand within the CSI-RS-resourceMapping IE. Both nrofRB and startingRB are configured as integer multiples of 4 RBs, and the reference point of startingRB is CRB 0 on the CRB grid. If The UE shall assume that the initial CRB index of the CSI-RS resource is Otherwise N initial RB =startingRB. If The UE shall assume that the bandwidth of the CSI-RS resource is otherwise In all cases, the UE should expect NZP-CSI-RS-Resource

[0022] Figure 1 The NZP-CSI-RS-Resource IE is shown. The NZP-CSI-RS-Resource IE is used to configure the NZP CSI-RS transmitted in the cell including the IE, and the UE can be configured to measure on this cell (see TS 38.214, section 5.2.2.3.1). The fields used for the NZP-CSI-RS-Resource IE are further described in Table 2 below. Table 2 NZP-CSI-RS-ResourceId

[0023] Figure 2 The NZP-CSI-RS-ResourceId IE is shown. The NZP-CSI-RS-ResourceId IE is used to identify one NZP-CSI-RS-Resource. NZP-CSI-RS-ResourceSet

[0024] Figure 3The NZP-CSI-RS-ResourceSet IE is shown. The NZP-CSI-RS-ResourceSet IE is the NZP CSI-RS resource set (their IDs) and set specific parameters. The fields used for the NZP-CSI-RS-ResourceSet IE are further described in Table 3 below. Table 3 NZP-CSI-RS-ResourceSetId

[0025] Figure 4 The NZP-CSI-RS-ResourceSetId IE is shown. The NZP-CSI-RS-ResourceSetId IE is used to identify one NZP-CSI-RS-ResourceSet. CSI-ResourceConfig

[0026] Figure 5 The CSI-ResourceConfig IE is shown. The CSI-ResourceConfig IE defines a set of one or more NZP-CSI-RS-ResourceSet, CSI-IM-ResourceSet and / or CSI-SSB-ResourceSet. The fields used for the CSI-ResourceConfig IE are further described in Table 4 below. CSI-ResourceConfigId

[0027] Figure 6 The CSI-ResourceConfigId IE is shown. The CSI-ResourceConfigId IE is used to identify the CSI-ResourceConfig. CSI-ResourcePeriodicityAndOffset

[0028] Figure 7 The CSI-ResourcePeriodicityAndOffset IE is shown. The CSI-ResourcePeriodicityAndOffset IE is used to configure the period and corresponding offset for periodic and semi-persistent CSI resources and for periodic and semi-persistent reporting on the PUCCH. Both the period and the offset are given in number of slots. A period value of slots4 corresponds to 4 slots, slots5 corresponds to 5 slots, and so on. CSI-RS-resourceMapping

[0029] Figure 8 The CSI-RS-resourceMapping IE is shown. The CSI-RS-resourceMapping IE is used to configure resource element mapping of CSI-RS resources in the time domain and frequency domain. The fields used for CSI-RS-resourceMapping are further described in Table 5 below. Table 5 CSI-FrequencyOccupation

[0030] Fig. 9 The CSI-FrequencyOccupation IE is shown. The CSI-FrequencyOccupation IE is used to configure the frequency domain occupancy of the channel state information measurement resources (eg, NZP-CSI-RS-Resource, CSI-IM-Resource). The fields used for the CSI-FrequencyOccupation IE are further described in Table 6 below. Table 6 Problems with existing solutions

[0031] There are certain challenges at present. In NR, in connected mode, periodic, semi-periodic or aperiodic CSI-RS / TRS (TRS or CSI RS for tracking) is provided to the UE so that the UE can measure the channel quality, and / or track the reference signal to fine-tune its time and frequency synchronization. Although some individual UEs may be idle / inactive, such RS cannot be disabled. However, during RRC_Idle / Inactive, the UE is unaware of the potential existence of such RS. Therefore, the UE typically relies on SSB signals during RRC_Idle / Inactive for, for example, automatic gain control (AGC) settings, synchronization and / or cell quality measurements.

[0032] The problem with SSB measurement is that SSBs occur at long time intervals (e.g. 20 ms) and sometimes the UE may need to be away from deep sleep for an extended time before it can e.g. read its paging message after a previously available SSB reception, which results in a waste of UE energy.

[0033] Exposing the CSI-RS or TRS for tracking available during RRC_Connected to RRC_Idle is considered to be a solution to help UE reduce power consumption during RRC_Idle / Inactive. In particular, providing such information via system information (SI) (e.g., SI blocks (SIBs), such as SIB1, SIB2, ... SIBn) is considered to be a feasible mechanism. However, if the TRS configuration follows the same method as Rel-15 / 16, this generates a large overhead on the network side and also occupies a large portion of SI. Typically, the TRS configuration in the current version of Rel-15 / 16 includes several parameters with always the same configuration. However, the TRS configuration needs to be explicitly configured because it follows the same method for configuration as other types of CSI-RS. Summary of the invention

[0034] A method for compact tracking reference signal (TRS) configuration for new radio (NR) user equipment (UE) is provided. The channel state information reference signal (CSI-RS) configuration framework, through which TRS is traditionally configured in connected mode, is very large in terms of the number of possibilities and information elements (IEs) included in its structure. It requires IEs that can be used to configure multiple groups (up to 16 groups) of zero power (ZP) and non-zero power (NZP) CSI-RS. Each of these groups itself can include a configuration with up to 64 resources.

[0035] In order to provide TRS configuration and availability information to UEs in radio resource control (RRC) idle / inactive states, a compact TRS mechanism is disclosed, by which the network can configure a specific TRS for the UE. In addition, the method can indicate to the UE whether the configured RS is applicable to all RRC states (e.g., connected, idle, or inactive) or to a specific RRC state. Specifically, the present disclosure provides a mechanism that requires setting different configuration parameters to configure a compact TRS for the UE. In addition, the present disclosure provides methods and mechanisms by which the UE can communicate its capabilities to the network or provide auxiliary information so that an appropriate compact TRS is configured for the UE.

[0036] In this regard, the embodiments described herein provide a mechanism for UEs to be efficiently configured using a compact TRS. The compact TRS removes the redundant portions of the traditional TRS while providing the network with the flexibility to further expose the TRS to idle UEs. The embodiments utilize the compact TRS to achieve power savings, especially during RRC_Idle / Inactive mode. In addition, the compact TRS significantly reduces the network overhead in configuring the TRS.

[0037] Various embodiments are proposed herein to solve one or more problems disclosed herein. In some embodiments, a method for compactly configuring a TRS IE performed by a wireless device is provided. The method includes: receiving a compact TRS IE from a high-layer signaling of a network, wherein the compact TRS IE is received without CSI-RS configuration; and configuring at least one TRS according to the compact TRS IE.

[0038] In some embodiments, the compact TRS IE is available in idle / inactive mode or connected mode.

[0039] In some embodiments, the compact TRS IE is received when the wireless device is in one of an idle mode or an inactive mode. In some embodiments, the compact TRS IE is received via at least one of system information SI, RRC configuration, or RRC release. In some embodiments, the wireless device utilizes the compact TRS IE to save power during the idle mode or the inactive mode. In some embodiments, configuring the at least one TRS according to the compact TRS IE comprises: configuring a frequency position of a TRS opportunity within an initial bandwidth part BWP of the idle mode or the inactive mode. In some embodiments, configuring the at least one TRS according to the compact TRS IE comprises: configuring a frequency position of a TRS opportunity so that the TRS opportunity is not limited by an initial BWP of the idle mode or the inactive mode.

[0040] In some embodiments, according to the compact TRS IE, configuring the at least one TRS includes: configuring quasi-co-located QCL information for the at least one TRS according to a high-level qcl-InfoPeriodicCSI-RS configuration.

[0041] In some embodiments, according to the compact TRS IE, configuring the at least one TRS includes: configuring QCL information for the at least one TRS based on the associated synchronization signal block SSB.

[0042] In some embodiments, the method further comprises providing capability signaling indicating the wireless device's ability to utilize the compact TRSIE.

[0043] In some embodiments, the method further comprises: providing compact TRS configuration assistance information. In some embodiments, providing the compact TRS configuration assistance information comprises: indicating a preference for parameters to be included in the compact TRS IE. In some embodiments, providing the compact TRS configuration assistance information comprises: indicating at least one preferred compact TRS configuration.

[0044] In some embodiments, the method further comprises deploying the at least one TRS for measurement and / or tracking purposes.

[0045] In some embodiments, the compact TRS IE includes the following parameters: powerControlOffsetSS, scramblingID, firstOFDMSymbolInTimeDomain, startingRB, and nrofRBs. In some embodiments, the compact TRS IE optionally includes one or more of the following parameters: periodicityAndOffset, aperiodicTriggeringOffset, or qcl-InfoPeriodicCSI-RS.

[0046] In some embodiments, the compact TRS IE omits one or more of the following parameters: bwp-Id, resourceType, repetition, aperiodicTriggeringOffset, trs-Info, powerControlOffset, frequencyDomainAllocation, nrofPorts, firstOFDMSymbolInTimeDomain2, cdm-Type, or density.

[0047] In some embodiments, the compact TRS IE omits each of the following parameters: bwp-Id, resourceType, repetition, trs-Info, powerControlOffset, frequencyDomainAllocation, nrofPorts, firstOFDMSymbolInTimeDomain2, cdm-Type, and density.

[0048] In some embodiments, the compact TRS IE includes a TRS-Config IE.

[0049] In some embodiments, the compact TRS IE includes a CSI-RS-for-tracking-Resource IE.

[0050] In some embodiments, a wireless device for compactly configuring a TRS is provided. The wireless device comprises a processing circuit configured to perform any of the steps of any of the above embodiments.

[0051] In some embodiments, a method for compactly configuring a TRS performed by a network node is provided. The method includes: determining at least one TRS configuration for a wireless device; and providing a compact TRS IE to the wireless device based on the at least one TRS configuration, wherein the compact TRS IE is provided without providing a CSI-RS configuration.

[0052] In some embodiments, when the compact TRS IE is provided to multiple mobile devices through SI or broadcast, the network node considers common preferred parameter configurations from the mobile devices.

[0053] In some embodiments, the method further comprises: receiving capability signaling indicating an ability of the wireless device to utilize the compact TRSIE; and determining the at least one TRS configuration in response to receiving the capability signaling.

[0054] In some embodiments, the method further comprises: receiving compact TRS configuration assistance information; and determining the at least one TRS configuration according to the capability signaling. In some embodiments, the compact TRS configuration assistance information comprises a preference for parameters to be included in the compact TRS IE. In some embodiments, the compact TRS configuration assistance information comprises at least one preferred compact TRS configuration.

[0055] In some embodiments, a network node for compactly configuring a TRS is provided. The network node comprises a processing circuit configured to perform any of the steps of any of the above embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0056] 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.

[0057] Figure 1 The NZP-CSI-RS-Resource information element (IE) is shown;

[0058] Figure 2 The NZP-CSI-RS-ResourceId IE is shown;

[0059] Figure 3 The NZP-CSI-RS-ResourceSet IE is shown;

[0060] Figure 4 The NZP-CSI-RS-ResourceSetId IE is shown;

[0061] Figure 5The CSI-ResourceConfig IE is shown;

[0062] Figure 6 The CSI-ResourceConfigId IE is shown;

[0063] Figure 7 The CSI-ResourcePeriodicityAndOffset IE is shown;

[0064] Figure 8 The CSI-RS-resourceMapping IE is shown;

[0065] Fig. 9 The CSI-FrequencyOccupation IE is shown;

[0066] Fig.10 An example of a cellular communication system in which embodiments of the present disclosure may be implemented is shown;

[0067] Fig.11 An example of TRS-Config IE is shown;

[0068] Fig.12 A more compact example of a TRS-Config IE is shown when the bandwidth part (BWP) is the same as the initial BWP for the user equipment (UE);

[0069] Fig.13 is a flow chart illustrating a method for compactly configuring a tracking reference signal (TRS) according to one embodiment;

[0070] Fig.14 is a flow chart illustrating a method for providing a compact TRS configuration according to one embodiment;

[0071] Fig.15 is a schematic block diagram of a network node according to some embodiments of the present disclosure;

[0072] Fig.16 is a schematic block diagram illustrating a virtualization embodiment of a network node according to some embodiments of the present disclosure;

[0073] Fig.17 is a schematic block diagram of a network node according to some other embodiments of the present disclosure;

[0074] Fig.18 is a schematic block diagram of a wireless communication device according to some embodiments of the present disclosure;

[0075] Fig.19 is a schematic block diagram of a wireless communication device according to some other embodiments of the present disclosure. DETAILED DESCRIPTION

[0076] The embodiments set forth below represent information that enables those skilled in the art to implement the embodiments, and illustrate the best mode of implementing the embodiments. When reading the following description according to the accompanying drawings, those skilled in the art will understand the concepts of the present disclosure, and will recognize the application of these concepts not specifically mentioned herein. It should be understood that these concepts and applications fall within the scope of the present disclosure.

[0077] Radio Node: As used herein, a "radio node" is a radio access node or a wireless communication device.

[0078] Radio access node: As used herein, a "radio access node" or "radio network node" or "radio access network node" is any node in a radio access network (RAN) of a cellular communication network for wirelessly sending and / or receiving signals. Some examples of radio access nodes include, but are not limited to, a base station (e.g., a new radio (NR) base station (gNB) in a third generation partnership project (3GPP) fifth generation (5G) NR network or an enhanced or evolved node B (eNB) in a 3GPP long term evolution (LTE) network), a high power or macro base station, a low power base station (e.g., a micro base station, a pico base station, a home eNB, etc.), a relay node, a network node implementing part of the functionality of a base station (e.g., a network node implementing a gNB central unit (gNB-CU) or a network node implementing a gNB distributed unit (gNB-DU)), or a network node implementing part of the functionality of some other type of radio access node.

[0079] Core network node: As used herein, a "core network node" is any type of node in a core network or any node that implements a core network function. Some examples of core network nodes include, for example, a mobility management entity (MME), a packet data network gateway (P-GW), a service capability exposure function (SCEF), a home subscriber server (HSS), etc. Some other examples of core network nodes include nodes that implement access and mobility management function (AMF), user plane function (UPF), session management function (SMF), authentication server function (AUSF), network slice selection function (NSSF), network exposure function (NEF), network function (NF) repository function (NRF), policy control function (PCF), unified data management (UDM), etc.

[0080] Communication Device: As used herein, a "communication device" is any type of device that can access an access network. Some examples of communication devices include, but are not limited to: mobile phones, smart phones, sensor devices, meters, vehicles, household appliances, medical devices, media players, cameras, or any type of consumer electronics, such as but not limited to televisions, radios, lighting devices, tablet computers, notebook computers, or personal computers (PCs). A communication device may be a portable, handheld, computer- or vehicle-mounted mobile device capable of transmitting voice and / or data via a wireless or wired connection.

[0081] Wireless communication device: One type of communication device is a wireless communication device, which may be any type of wireless device that can access (i.e., be served by) a wireless network (e.g., a cellular network). Some examples of wireless communication devices include, but are not limited to: User Equipment (UE) in a 3GPP network, Machine Type Communication (MTC) devices, and Internet of Things (IoT) devices. Such wireless communication devices may be or may be integrated into a mobile phone, a smart phone, a sensor device, an instrument, a vehicle, a home appliance, a medical device, a media player, a camera, or any type of consumer electronic product, such as, but not limited to, a television, a radio, a lighting device, a tablet computer, a notebook computer, or a personal computer. A wireless communication device may be a portable, handheld, computer- or vehicle-mounted mobile device capable of transmitting voice and / or data via a wireless connection.

[0082] Network node: As used herein, a "network node" is any node that is part of the RAN or core network of a cellular communication network / system.

[0083] Note that the description given herein focuses on a 3GPP cellular communication system, and therefore, 3GPP terminology or terminology similar to 3GPP terminology is often used. However, the concepts disclosed herein are not limited to a 3GPP system.

[0084] Note that in the description of this document, the term "cell" may be mentioned; however, particularly with respect to 5G NR concepts, beam may be used instead of cell, and therefore, it is important to note that the concepts described herein apply equally to both cells and beams.

[0085] Fig.10An example of a cellular communication system 1000 in which embodiments of the present disclosure may be implemented is shown. In the embodiments described herein, the cellular communication system 1000 is a 5G system (5GS) including an NR RAN or an LTE RAN (i.e., an Evolved Universal Terrestrial Radio Access (E-UTRA) RAN) or an Evolved Packet System (EPS) including an LTE RAN. In this example, the RAN includes base stations 1002-1 and 1002-2, which are referred to as eNBs in LTE (when connected to an Evolved Packet Core (EPC)) and gNBs in 5G NR (e.g., LTE RAN nodes connected to a 5G Core (5GC), which are referred to as gn-eNBs), which control corresponding (macro) cells 1004-1 and 1004-2. Base stations 1002-1 and 1002-2 are collectively referred to as base stations 1002 and individually as base stations 1002 herein. Likewise, (macro) cells 1004-1 and 1004-2 are collectively referred to herein as (macro) cells 1004 and individually as (macro) cells 1004. The RAN may also include a plurality of low-power nodes 1006-1 to 1006-4 that control corresponding small cells 1008-1 to 1008-4. The low-power nodes 1006-1 to 1006-4 may be small base stations (e.g., pico or femto base stations) or remote radio heads (RRHs), etc. It is noteworthy that, although not shown, one or more of the small cells 1008-1 to 1008-4 may be provided alternatively by the base station 1002. The low-power nodes 1006-1 to 1006-4 are generally collectively referred to herein as low-power nodes 1006 and individually as low-power nodes 1006. Likewise, the small cells 1008-1 to 1008-4 are generally collectively referred to herein as small cells 1008 and individually as small cells 1008. The cellular communication system 1000 also includes a core network 1010, which is referred to as 5G Core (5GC) in 5GS. The base station 1002 (and optionally the low power node 1006) are connected to the core network 1010.

[0086] The base station 1002 and the low power node 1006 provide services to wireless communication devices 1012-1 to 1012-5 in the corresponding cells 1004 and 1008. The wireless communication devices 1012-1 to 1012-5 are collectively referred to herein as wireless communication devices 1012 and individually as wireless communication devices 1012. In the following description, the wireless communication device 1012 is generally a UE, but the present disclosure is not limited thereto.

[0087] In the embodiments described herein, methods and mechanisms are provided that a network (e.g., an NRRAN of a cellular communication system 1000) can utilize to configure a UE (e.g., a wireless communication device 1012) with one or more tracking resource signals (TRS) in a compact manner. The underlying configuration can be performed through different mechanisms (e.g., a system information (SI) update, a radio resource control (RRC) configuration, or an RRC release command).

[0088] Furthermore, the compact TRS mechanisms described herein do not require reporting from the UE. For example, the UE may use these compact TRS mechanisms for measurement and tracking purposes without providing feedback to the network. Aspect 1: Compact TRS configuration and resource mapping

[0089] Configuring a UE with a compact TRS involves several parameters. In one example, a specific NZP-CSI-RS-Resource (e.g., a TRS-config information element (IE) including the most relevant fields from CSI-RS-resourceMapping and NZP-CSI-RS-Resourceset) may be configured for a compact TRS. Below, an example embodiment of how to configure the relevant parameters in a compact manner is described. NZP-CSI-RS-Resource IE:

[0090] In one example, the IE may be simply referred to as CSI-RS-for-tracking-Resource IE, or TRS-config IE to clarify that this is a compact TRS configuration. nzp-CSI-RS-ResourceId:

[0091] In one example, this parameter does not need to be explicitly configured, especially if the Compact TRS IE is configured as a standalone NZP-CSI-RS-Resource IE as described above.

[0092] In another example, the parameter may be referred to simply with respect to a compact TRS configuration, clarifying that this is different from other types of channel state information reference signal (CSI-RS) configurations (e.g., TRS-config or compact CSI-RS for tracking, etc.). resourceMapping:

[0093] In one example, a separate CSI-RS-resourceMapping IE for compact TRS may be configured. In another preferred method, all relevant resource mapping fields may be moved to the compact TRS IE. powerControlOffset:

[0094] Power offset of Physical Downlink Shared Channel (PDSCH) Resource Element (RE) to Non-Zero Power (NZP) CSI-RS RE. In one example, this field is removed from the compact TRS configuration because the UE is not expected to report anything after receiving a TRS. Power Control Offset Synchronization Signal (SS):

[0095] The power control offset SS is the ratio of the NZP CSI-RS energy per resource element (EPRE) to the secondary synchronization signal / physical broadcast channel (PBCH) block EPRE of the SS.

[0096] In one example, the ratio may be configured to be 1 or 0 decibels (dB). In this case, in one method, the compact TRS may not include the IE indicating that the power control offset SS is configured to 1 to reduce the size. For example, if the compact TRS is present in idle mode, the network may wish to configure this parameter to 1 and therefore not explicitly configure this parameter in the compact TRS.

[0097] In another example, the value may be explicitly configured, or may be explicitly configured only when it is not 1. In yet another example, the UE may be configured differently for connected mode and idle mode (eg, higher or lower value for connected mode, 1 for idle mode). Scrambled ID:

[0098] In one example, the scrambling ID of the compact TRS may be configured in the same manner as in Rel-15 / 16.

[0099] In another example, the scrambling ID of the compact TRS may be associated with the RRC state (eg, for connected mode, a different ID may be used than that used in idle mode).

[0100] In one aspect, the scrambling ID may be the same or based on the cell identity; in this case, the field for the scrambling ID may be omitted. Period and offset:

[0101] In one example, the compact TRS period and offset are configured as in Rel-15 / 16, but with reduced possibilities (e.g., possibilities associated with only a period of 10, 20, 40, or 80 ms or other values ​​in terms of number of time slots). In another example, the period can be explicitly configured according to a set of values ​​in milliseconds (ms).

[0102] In another example, the compact TRS period can be associated with a specific SS block (SSB) period, for example, the same period as the SSB, or a portion of the SSB period, or a multiple of the SSB period. In addition, the offset indicator can indicate the offset between the compact TRS and the SSB.

[0103] In another example, the compact TRS period can be associated with one paging occasion (PO) or multiple POs. For example, the compact TRS period can be configured to be every PO, or a multiple of a PO period, or a portion of a PO period. In addition, the offset indicator can indicate the offset between the compact TRS and the PO.

[0104] In another example, the compact TRS cycle can be associated with a discontinuous reception (DRX) cycle (e.g., connected mode DRX (C-DRX), idle mode DRX (I-DRX)) or a portion of a DRX cycle or a multiple of a DRX cycle. In addition, the offset indicator can indicate an offset between the compact TRS and a specific portion of the DRX cycle (e.g., the end of the cycle, the beginning of the cycle, or the activation duration of C-DRX).

[0105] In another example, the compact TRS may be configured with separate periods for different RRC states. For example, the compact TRS period may be shorter for connected mode and longer for idle mode, or vice versa. Alternatively, the compact TRS period may be configured differently for connected mode and idle mode. For example, for connected mode, the UE may be configured with a TRS with a period of 40ms, but with a period equivalent to PO in idle mode. qcl-InfoPeriodicCSI-RS:

[0106] The parameters typically contain a reference to a TCI-State indicating a quasi-co-located (QCL) source reference signal (RS) and the QCL type. In one example, the same process as in Rel-15 / 16 can be used for compact TRS.

[0107] In another example, particularly when compact TRS is configured as part of SI update, or when compact TRS is employed during idle mode, QCL information may be configured in conjunction with one or more specific SSBs. That is, the UE is configured to receive the TRS in the same QCL configured for the associated SSB. Thus, multiple TRSs may be provided in a cell, each TRS being associated with one / more SSBs provided in the cell. Conditional existence:

[0108] In one example, the field remains the same as in Rel-15 / 16. That is, if the compact TRS configuration is periodic, the field can be present, and if the compact TRS configuration is not periodic, or if there are also non-periodic elements (e.g., in the case of frequency range 2 (FR2)), the field is not present.

[0109] In another example, this field is not configured at all in compact TRS because periodic elements exist in all types of TRS configurations, and if the field aperiodicTriggeringOffset is additionally configured, this field indicates that aperiodic elements also exist (for example, as in the case of FR2).

[0110] In another example, the field may additionally indicate which RRC states the compact TRS configuration applies to. For example, the field may indicate whether the compact TRS configuration applies to both connected mode (e.g., RRC_Connected UE) and idle mode UE (e.g., RRC_Idle / Inactive UE), or only to connected mode UE, or only to a single state or a specific set of states. In a related implementation, this part is configured only when the TRS configuration also applies to idle UEs, or in an alternative solution, if the field does not exist, the field can be used for all RRC states. In addition, the field can also be configured with its different possibilities for different RRC states as a separate field in the compact TRS configuration IE. NZP-CSI-RS-ResourceSet IE:

[0111] In one example, all fields in this IE may be moved to the general compact TRS configuration. Otherwise, it may become an independent compact TRS group configuration IE (eg, TRS-config-set IE). nzp-CSI-RS-ResourceId:

[0112] In one example, this parameter does not need to be explicitly configured, especially if the Compact TRS IE is configured as a standalone NZP-CSI-RS-Resource IE as described above.

[0113] In another example, the parameter may be simply referred to with respect to a compact TRS configuration, clarifying that this is different from other types of CSI-RS configurations (eg, TRS-config or compact CSI-RS for tracking, etc.). repetition:

[0114] In one example, this field is removed and not configured for compact TRS configuration because there is no expected reporting for TRS. trs-Info:

[0115] In one example, this field is not configured for compact TRS configuration because it is clear that this configuration is related to TRS. aperiodicTriggeringOffset:

[0116] In one example, this field is configured only when the compact TRS involves a non-periodic component (such as in the case of TRS for FR2). The configuration can be the same as in the case of Rel-15 / 16. If this field is not present, the UE assumes that all parameters are periodic.

[0117] In the case where compact TRS is provided for idle UEs only, aperiodicTriggeringOffset is omitted entirely for the structure indicated in the compact TRS configuration. bwp-Id:

[0118] bwp-Id is currently configured as part of the CSI-ResourceConfig IE in Rel-15 / 16. In one example, the bwp-Id and bandwidth (BW) related configurations can be moved under the compact TRS configuration IE. Another option is to make a specific compact TRS resource configuration and include this field in it. The following examples can adapt to both possibilities.

[0119] In one example, the TRS is configured with a specific bandwidth part in a bandwidth part (BWP) configured for a specific cell. In this case, the BWP (and associated subcarrier spacing) in which the TRS is provided is identified by the UE via the bwp-Id. In another example, particularly if the intent is to employ TRS during idle mode, the UE may be configured with the same BWP as it should use during idle mode. For example, an initial BWP may be configured for the UE during idle mode, and the same BWP may be configured for compact TRS. Therefore, in one approach, the associated IE (e.g., bwp-Id) related to the BWP configuration may remain optional, meaning that if omitted, the UE should assume the same BWP as for the idle mode of the TRS.

[0120] Similarly, information about the BW of the TRS available in the BWP may optionally be provided to the UE. The reason for the optional nature of this IE is that the TRS is typically intended for wideband transmission and covers the entire BWP (e.g., 52 resource blocks (RBs) as described above). However, if the initial BWP accommodates more than 52 RBs (e.g., 96 RBs in the case of 15 KHz subcarrier spacing), such an optional indicator may be used to inform the UE whether the TRS covers the entire BWP (96 RBs in this case) or only the default 52 RBs, or possibly a smaller number of resource blocks (e.g., corresponding to the SSB bandwidth).

[0121] In another example, the BWP or BWP subset configured by the UE for TRS may be the same as the BWP or BWP subset configured for SSB. For example, an IE may be added to the compact TRS configuration related to the BWP, which indicates that the BWP is associated with a specific SSB, thereby meaning that the BWP of the compact TRS configuration is the same as the specific SSB.

[0122] A UE in idle / inactive mode may not need to operate at a bandwidth larger than the bandwidth corresponding to the initial BWP or the bandwidth of Coreset 0 (e.g., if there is no initial DL BWP). Therefore, in another example, the UE may assume that the TRS is transmitted in PRBs corresponding to a reference bandwidth or a set of physical RBs (PRBs). The reference bandwidth may be an SSB bandwidth, a bandwidth corresponding to Coreset 0, or a bandwidth corresponding to the initial BWP. In the case where the network may indicate the initial BWP in the SI (e.g., an SI block (SIB), such as SIB1), a UE in idle / inactive mode may assume that the TRS only exists in a subset of PRBs of the initial BWP - this subset of PRBs may be explicitly indicated via the BW field in the TRS configuration, or implicitly indicated (the default may be the PRBs of the bandwidth corresponding to Coreset 0). This enables the network to keep the frequency span of the TRS as small as possible to assist UEs in idle / inactive mode. The frequency position and span of the TRS as well as the starting RB and number of RBs may be provided as part of the configuration (eg, in the element freqBand as part of a separate Compact TRS Resource Mapping IE) or directly as part of the Compact TRS Configuration IE. CSI-RS-ResourceMapping:

[0123] In one example, all fields in this IE may be moved to the general compact TRS configuration. Otherwise, it may become an independent compact TRS group resource mapping configuration IE (eg, TRS-config-ResourceMapping IE). frequencyDomainAllocation:

[0124] In one example, this field is not configured as part of the Compact TRS IE, or in other words, is not included because for TRS it is always relevant to the Rel-15 / 16 specifications associated with the following case: non-combined data model (CDM), number of ports is 1, and density is 3 (e.g., row 1 of Table 7.4.1.5.3-1 of 3GPP technical specification TS 38.211). Number of ports

[0125] In one example, a compact TRS does not include a port number because a TRS is associated with only one port and this is the same among all underlying RS resources. CDM-type:

[0126] In one example, for compact TRS, there is no CDM, and thus this line is not configured for compact TRS. In other words, there is no need to consider the CDM-type as part of the compact TRS configuration, and the UE assumes by default that there is no configured CDM type. density:

[0127] density defines the CSI-RS frequency density per CSI-RS port per PRB, and the CSI-RS PRB offset in the case of a density value of 1 / 2. For compact TRS, in one example, the density is always the same and is determined by the specification (e.g., density is 3), and therefore this field does not need to be explicitly configured for compact TRS. firstOFDMSymbolInTimeDomain:

[0128] When it comes to time density, TRS resources are always separated by 4 symbols and do not need to be signaled. However, the time start symbol indicated by firstOFDMSymbolInTimeDomain can be configured (for example, it can be one of the values ​​{4,5,6} for frequency range 1 (FR1) and FR2, or an additional value {0,1,2,3,7,8,9} for the start symbol can be included for FR2). freqBand:

[0129] This parameter is responsible for determining the number of RBs and the starting RB.

[0130] Fig.11 and 12 An example is provided of how a Compact TRS Configuration IE may appear, with elements as described in Aspect 1. Fig.11An example of TRS-Config IE is shown. Fig.12 A more compact example of the TRS-Config IE is shown when the BWP is the same as the initial BWP for the UE. Aspect 2: UE capability signaling and auxiliary information for compact TRS

[0131] In one example, the UE indicates to the network through capability signaling that the UE can support compact TRS. In another method, the UE indicates to the network that the UE can use TRS for purposes other than tracking, such as achieving power saving (eg, in idle mode).

[0132] Then, the network decides whether to configure the compact TRS as disclosed in aspect 1 for the UE.

[0133] In one example, the UE provides additional assistance information rather than just capabilities. For example, the UE provides preferences related to the underlying parameters of the compact TRS discussed in aspect 1 or a subset thereof. In a related implementation, the UE may decide to even transmit a specific preferred compact TRS configuration or a set of specific TRS configurations.

[0134] The network may then decide to consider the UE preferences and configure one or more compact TRSs for the UE in this way. In a related implementation, particularly when compact TRSs are configured via SI, or when TRSs are broadcast to all UEs, the network may consider the most common preferred parameter configurations from the UEs.

[0135] Fig.13 13 is a flow chart illustrating a method for compactly configuring a TRS according to one embodiment. The method may be implemented in a wireless device. Optional steps are indicated by dashed lines. In optional step 1300, the wireless device provides capability signaling indicating the wireless device's ability to utilize a compact TRS IE. In optional step 1302, the wireless device provides compact TRS configuration assistance information. In step 1304, the wireless device receives a compact TRS IE from the network. In an exemplary aspect, the compact TRS IE is received without a CSI-RS configuration. In step 1306, the wireless device configures at least one TRS according to the compact TRS IE. In optional step 1308, the wireless device deploys at least one TRS for measurement and / or tracking purposes.

[0136] Fig.1414 is a flow chart illustrating a method for providing a compact TRS configuration according to one embodiment. The method may be implemented in a base station. Optional steps are represented by dashed lines. In optional step 1400, the base station receives capability signaling indicating the capability of the wireless device to utilize a compact TRS IE. In optional step 1402, the base station receives compact TRS configuration assistance information. In step 1404, the base station determines at least one TRS configuration for the wireless device. In step 1406, the base station provides a compact TRS IE to the wireless device based on the at least one TRS configuration. In an exemplary aspect, a compact TRS IE is provided without providing a CSI-RS configuration.

[0137] Fig.15 1 is a schematic block diagram of a network node 1500 according to some embodiments of the present disclosure. Optional features are represented by dashed boxes. The network node 1500 may be, for example, a base station 1002 or 1006 or another network node that implements all or part of the functionality of the base station 1002 or gNB described herein. As shown, the network node 1500 includes a control system 1502, which includes one or more processors 1504 (e.g., a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), etc.), a memory 1506, and a network interface 1508. The one or more processors 1504 are also referred to herein as processing circuits. In addition, the network node 1500 may include one or more radio units 1510, each of which includes one or more transmitters 1512 and one or more receivers 1514 coupled to one or more antennas 1516. The radio unit 1510 may be referred to as a radio interface circuit or as part of a radio interface circuit. In some embodiments, the radio unit 1510 is external to the control system 1502 and is connected to the control system 1502 via, for example, a wired connection (e.g., an optical cable). However, in some other embodiments, the radio unit 1510 and possibly the antenna 1516 are integrated with the control system 1502. The one or more processors 1504 operate to provide one or more functions of the network node 1500 as described herein. In some embodiments, the functions are implemented in software, which is stored, for example, in the memory 1506 and executed by the one or more processors 1504.

[0138] Fig.16 1 is a schematic block diagram illustrating a virtualized embodiment of a network node 1500 according to some embodiments of the present disclosure. The discussion is equally applicable to radio access nodes and other types of network nodes. In addition, other types of network nodes may have similar virtualized architectures. Again, optional features are represented by dashed boxes.

[0139] As used herein, a "virtualized" network node is an implementation of a network node 1500 in which at least a portion of the functionality of the network node 1500 is implemented as a virtual component (e.g., via a virtual machine executed on a physical processing node in the network). As shown, in this example, the network node 1500 may include a control system 1502 and / or one or more radio units 1510, as described above. The control system 1502 may be connected to the radio unit 1510 via, for example, an optical cable, etc. The network node 1500 includes one or more processing nodes 1600, one or more processing nodes 1600 coupled to the network 1602 or included as part of the network 1602. If present, the control system 1502 or the radio unit is connected to the processing node 1600 via the network 1602. Each processing node 1600 includes one or more processors 1604 (e.g., CPU, ASIC, FPGA, etc.), a memory 1606, and a network interface 1608.

[0140] In this example, the functionality 1610 of the network node 1500 described herein is implemented at one or more processing nodes 1600 or distributed in any desired manner between one or more processing nodes 1600 and the control system 1502 and / or the radio unit 1510. In some specific embodiments, some or all of the functionality 1610 of the network node 1500 described herein is implemented as a virtual component executed by one or more virtual machines implemented in a virtual environment hosted by the processing node 1600. One of ordinary skill in the art will appreciate that additional signaling or communication between the processing node 1600 and the control system 1502 is used in order to perform at least some of the desired functionality 1610. It is worth noting that in some embodiments, the control system 1502 may not be included, in which case the radio unit 1510 communicates directly with the processing node 1600 via an appropriate network interface.

[0141] In some embodiments, a computer program comprising instructions is provided, which, when executed by at least one processor, causes the at least one processor to perform the functions of the network node 1500 or the functions of a node (e.g., processing node 1600) that implements one or more functions 1610 of the network node 1500 in a virtual environment according to any embodiment described herein. In some embodiments, a carrier comprising the above-mentioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium (e.g., a non-transitory computer-readable medium such as a memory).

[0142] Fig.17is a schematic block diagram of a network node 1500 according to some other embodiments of the present disclosure. The network node 1500 includes one or more modules 1700, each of which is implemented in software. The modules 1700 provide the functionality of the network node 1500 described herein. The discussion is equally applicable to Fig.16 1600 , where module 1700 may be implemented at one of processing nodes 1600 or distributed among multiple processing nodes 1600 and / or between processing node 1600 and control system 1502 .

[0143] Fig.18 1800 is a schematic block diagram of a wireless communication device 1800 according to some embodiments of the present disclosure. As shown, the wireless communication device 1800 includes one or more processors 1802 (e.g., CPU, ASIC, FPGA, etc.), a memory 1804, and one or more transceivers 1806, each transceiver including one or more transmitters 1808 and one or more receivers 1810 coupled to one or more antennas 1812. The transceiver 1806 includes a radio front-end circuit connected to the antenna 1812, and the radio front-end circuit is configured to condition the signal transmitted between the antenna 1812 and the processor 1802, as will be understood by a person of ordinary skill in the art. The processor 1802 is also referred to as a processing circuit herein. The transceiver 1806 is also referred to as a radio circuit herein. In some embodiments, the functions of the above-mentioned wireless communication device 1800 can be implemented in whole or in part in software, for example, stored in the memory 1804 and executed by the processor 1802. Note that the wireless communication device 1800 may include a processor that is not in the embodiment of the present invention. Fig.18 Additional components shown in the figure, such as one or more user interface components (e.g., input / output interfaces including displays, buttons, touch screens, microphones, speakers, etc. and / or any other components for allowing information to be input into the wireless communication device 1800 and / or allowing information to be output from the wireless communication device 1800), power sources (e.g., batteries and associated power circuits), etc.

[0144] In some embodiments, a computer program comprising instructions is provided, which when executed by at least one processor causes the at least one processor to perform the functions of the wireless communication device 1800 according to any embodiment described herein. In some embodiments, a carrier comprising the above-mentioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium (e.g., a non-transitory computer-readable medium such as a memory).

[0145] Fig.191 is a schematic block diagram of a wireless communication device 1800 according to some other embodiments of the present disclosure. The wireless communication device 1800 includes one or more modules 1900, each of which is implemented in software. The modules 1900 provide the functions of the wireless communication device 1800 described herein.

[0146] Any suitable steps, methods, features, functions or benefits disclosed herein may be performed by one or more functional units or modules of one or more virtual devices. Each virtual device may include a plurality of such functional units. These functional units may be implemented via processing circuits that may include one or more microprocessors or microcontrollers and other digital hardware that may include digital signal processors (DSPs), dedicated digital logic, etc. The processing circuit may be configured to execute program codes stored in a memory, and the memory may include one or more types of memory, such as a read-only memory (ROM), a random access memory (RAM), a cache memory, a flash memory device, an optical storage device, etc. The program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols and instructions for executing one or more technologies described herein. In some embodiments, the processing circuit may be used to cause the corresponding functional unit to perform the corresponding functions according to one or more embodiments of the present disclosure.

[0147] Although the processes in the figures may illustrate a particular order of operations performed by a particular embodiment of the present disclosure, it should be understood that such order is exemplary (e.g., alternative embodiments may perform operations in a different order, combine particular operations, overlap particular operations, etc.). Group A Embodiment

[0148] Embodiment 1: A method for compactly configuring a TRS, performed by a wireless device, the method comprising at least one of the following: receiving a compact TRS IE from a network; and configuring at least one TRS according to the compact TRS IE.

[0149] Embodiment 2: The method according to embodiment 1, wherein the compact TRS IE is available in idle mode and connected mode.

[0150] Embodiment 3: A method according to any one of Embodiments 1 to 2, wherein the compact TRS IE is received through at least one of SI, RRC configuration, or RRC release.

[0151] Embodiment 4: The method according to any one of embodiments 1 to 3 further includes: providing capability signaling indicating the capability of the wireless device to utilize the compact TRS IE.

[0152] Embodiment 5: The method according to any one of Embodiments 1 to 4 further includes: providing compact TRS configuration auxiliary information.

[0153] Embodiment 6: The method of embodiment 5, wherein providing compact TRS configuration assistance information comprises indicating a preference for parameters to be included in the compact TRS IE.

[0154] Embodiment 7: The method according to any one of Embodiments 5 to 6, wherein providing compact TRS configuration auxiliary information includes: indicating at least one preferred compact TRS configuration.

[0155] Embodiment 8: The method according to any one of embodiments 1 to 7 further includes: deploying at least one TRS for measurement purposes and / or tracking purposes.

[0156] Embodiment 9: The method according to any one of Embodiments 1 to 8, wherein the compact TRS IE includes a TRS-Config IE.

[0157] Embodiment 10: The method according to any one of Embodiments 1 to 9, wherein the compact TRS IE includes a CSI-RS-for-tracking-Resource IE.

[0158] Embodiment 11: The method according to any of the preceding embodiments further comprises: providing user data; and forwarding the user data to a host computer via transmission to a base station. Group B Example

[0159] Embodiment 12: A method for compactly configuring a TRS, performed by a base station, the method comprising at least one of: determining at least one TRS configuration for a wireless device; and providing a compact TRS IE to the wireless device based on the at least one TRS configuration.

[0160] Embodiment 13: The method according to embodiment 12, wherein the compact TRS IE is available when the wireless device is in idle mode and connected mode.

[0161] Embodiment 14: The method according to any one of Embodiments 12 to 13, wherein the compact TRS IE is provided through at least one of SI, RRC configuration or RRC release.

[0162] Embodiment 15: The method according to embodiment 14, wherein when the compact TRS IE is provided to multiple mobile devices through SI or broadcast, the network considers common preferred parameter configurations from the mobile devices.

[0163] Embodiment 16: The method according to any one of embodiments 12 to 15 further includes: receiving capability signaling indicating the capability of the wireless device to utilize the compact TRS IE; and determining at least one TRS configuration in response to receiving the capability signaling.

[0164] Embodiment 17: The method according to any one of Embodiments 12 to 16 further includes: receiving compact TRS configuration auxiliary information; and determining at least one TRS configuration based on the capability signaling.

[0165] Embodiment 18: The method of Embodiment 17, wherein the compact TRS configuration assistance information includes preferences for parameters to be included in the compact TRS IE.

[0166] Embodiment 19: The method according to any one of Embodiments 16 to 18, wherein the compact TRS configuration auxiliary information includes at least one preferred compact TRS configuration.

[0167] Embodiment 20: The method according to any one of embodiments 12 to 19, wherein the compact TRS IE includes a TRS-Config IE.

[0168] Embodiment 21: The method according to any one of Embodiments 12 to 20, wherein the compact TRS IE includes a CSI-RS-for-tracking-Resource IE.

[0169] Embodiment 22: The method according to any one of the preceding embodiments further includes: acquiring user data; and forwarding the user data to a host computer or a wireless device. Group C Example

[0170] Embodiment 23: A wireless device for compactly configuring a TRS, the wireless device comprising: a processing circuit configured to perform any steps of any Group A embodiments; and a power supply circuit configured to supply power to the wireless device.

[0171] Embodiment 24: A base station for compactly configuring a TRS, the base station comprising: a processing circuit configured to perform any steps of any Group B embodiments; and a power supply circuit configured to supply power to the base station.

[0172] Embodiment 25: A UE for compactly configuring a TRS, 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 transmitted between the antenna and the processing circuit; the processing circuit is configured to perform any steps of any Group A embodiments; 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.

[0173] Embodiment 26: A communication system comprising a host computer, the host computer comprising: a processing circuit configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a UE; wherein the cellular network comprises a base station having a radio interface and a processing circuit, the processing circuit of the base station being configured to perform any steps of any Group B embodiments.

[0174] Embodiment 27: The communication system according to the previous embodiment further includes: a base station.

[0175] Embodiment 28: The communication system according to the first two embodiments further includes: UE, wherein the UE is configured to communicate with the base station.

[0176] Embodiment 29: A method implemented in a communication system including a host computer, a base station and a UE, the method comprising: providing user data at the host computer; and initiating, at the host computer, a transmission carrying the user data to the UE via a cellular network including the base station, wherein the base station performs any steps of any Group B embodiments.

[0177] Embodiment 30: The method according to the previous embodiment further includes: sending user data at a base station.

[0178] Embodiment 31: A UE configured to communicate with a base station, the UE comprising a radio interface and a processing circuit configured to perform the methods of the first three embodiments.

[0179] Embodiment 32: A communication system comprising a host computer, the host computer comprising: a processing circuit configured to provide user data; a communication interface configured to forward the user data to a cellular network for transmission to a UE; wherein the UE comprises a radio interface and a processing circuit, and the components of the UE are configured to perform any steps of any Group A embodiments.

[0180] Embodiment 33: A communication system according to the previous embodiment, wherein the cellular network further includes a base station configured to communicate with the UE.

[0181] Embodiment 34: A method implemented in a communication system including a host computer, a base station and a UE, the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network including the base station, wherein the UE performs any steps of any Group A embodiments.

[0182] Embodiment 35: The method according to the previous embodiment further includes: at the UE, receiving user data from the base station.

[0183] Embodiment 36: A communication system comprising a host computer, the host computer comprising: a communication interface configured to receive user data originating from a transmission from a UE to a base station; wherein the UE comprises a radio interface and a processing circuit, the processing circuit of the UE being configured to perform any steps of any Group A embodiments.

[0184] Embodiment 37: The communication system according to the previous embodiment further includes a UE.

[0185] Embodiment 38: The communication system according to the first two embodiments further includes: a base station, wherein the base station includes a radio interface configured to communicate with the UE and a communication interface configured to forward user data carried by the transmission from the UE to the base station to a host computer.

[0186] Embodiment 39: A method implemented in a communication system including a host computer, a base station and a UE, the method comprising: at the host computer, receiving user data sent from the UE to the base station, wherein the UE performs any steps of any Group A embodiments.

[0187] Embodiment 40: The method according to the previous embodiment further includes: at the UE, providing user data to the base station.

[0188] Embodiment 41: A communication system comprising a host computer, the host computer comprising a communication interface configured to receive user data originating from a transmission from a UE to a base station, wherein the base station comprises a radio interface and a processing circuit, and the processing circuit of the base station is configured to perform any steps of any Group B embodiments.

[0189] Embodiment 42: The communication system according to the previous embodiment further includes: a base station.

[0190] Embodiment 43: The communication system according to the first two embodiments further includes a UE, wherein the UE is configured to communicate with a base station.

[0191] Embodiment 44: A method implemented in a communication system including a host computer, a base station and a UE, the method comprising: at the host computer, receiving from the base station user data originating from a transmission that the base station has received from the UE, wherein the UE performs any steps of any Group A embodiments.

[0192] Embodiment 45: The method according to the previous embodiment further includes: receiving user data from the UE at the base station.

[0193] Embodiment 46: The method according to the previous two embodiments further includes: at the base station, initiating transmission of the received user data to a host computer.

[0194] 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 be within the scope of the concepts disclosed herein.

Claims

1. A method for compactly configuring a Tracking Reference Signal (TRS) Information Element (IE) performed by a wireless device (1012), the method comprising: receiving (1304) a compact TRS IE from a higher layer signaling of a network, wherein the compact TRS IE is received without a channel state information reference signal CSI-RS configuration; and At least one TRS is configured (1306) according to the compact TRS IE.

2. The method according to claim 1, wherein: The compact TRS IE is available in idle / inactive mode or connected mode.

3. The method according to any one of claims 1 to 2, wherein: The compact TRS IE is received when the wireless device is in one of an idle mode or an inactive mode.

4. The method according to claim 3, wherein: The compact TRS IE is received through at least one of system information SI, radio resource control RRC configuration, or RRC release.

5. The method according to any one of claims 3 to 4, wherein: The wireless device utilizes the compact TRS IE to save power during the idle mode or the inactive mode.

6. The method according to any one of claims 3 to 5, wherein: According to the compact TRS IE, configuring the at least one TRS comprises: configuring a frequency position of a TRS opportunity within an initial bandwidth part BWP of the idle mode or the inactive mode.

7. The method according to any one of claims 3 to 6, wherein: According to the compact TRS IE, configuring the at least one TRS includes configuring a frequency position of a TRS opportunity so that the TRS opportunity is not restricted by an initial bandwidth part BWP of the idle mode or the inactive mode.

8. The method according to any one of claims 1 to 7, wherein: According to the compact TRS IE, configuring the at least one TRS includes: configuring quasi-co-site QCL information for the at least one TRS according to the high-level qcl-InfoPeriodicCSI-RS configuration.

9. The method according to any one of claims 1 to 8, wherein: According to the compact TRS IE, configuring the at least one TRS includes: configuring quasi-co-site QCL information for the at least one TRS based on the associated synchronization signal block SSB.

10. The method according to any one of claims 1 to 9, further comprising: Capability signaling is provided (1300) indicating the wireless device's ability to utilize the compact TRS IE.

11. The method according to any one of claims 1 to 10, further comprising: Compact TRS configuration assistance information is provided (1302).

12. The method according to claim 11, wherein: Providing (1302) the compact TRS configuration assistance information includes indicating a preference for parameters to be included in the compact TRS IE.

13. The method according to any one of claims 11 to 12, wherein: Providing (1302) the compact TRS configuration assistance information includes indicating at least one preferred compact TRS configuration.

14. The method according to any one of claims 1 to 13, further comprising: The at least one TRS is deployed (1308) for measurement and / or tracking purposes.

15. The method according to any one of claims 1 to 14, wherein: The compact TRS IE includes the following parameters: powerControlOffsetSS, scramblingID, firstOFDMSymbolInTimeDomain, startingRB, and nrofRBs.

16. The method according to claim 15, wherein: The compact TRS IE optionally includes one or more of the following parameters: periodicityAndOffset, aperiodicTriggeringOffset, or qcl-InfoPeriodicCSI-RS.

17. The method according to any one of claims 1 to 16, wherein: The compact TRS IE omits one or more of the following parameters: bwp-Id, resourceType, repetition, aperiodicTriggeringOffset, trs-Info, powerControlOffset, frequencyDomainAllocation, nrofPorts, firstOFDMSymbolInTimeDomain2, cdm-Type, or density.

18. The method according to any one of claims 1 to 17, wherein: The compact TRS IE omits each of the following parameters: bwp-Id, resourceType, repetition, trs-Info, powerControlOffset, frequencyDomainAllocation, nrofPorts, firstOFDMSymbolInTimeDomain2, cdm-Type, and density.

19. The method according to any one of claims 1 to 18, wherein: The compact TRS IE includes a TRS-Config IE.

20. The method according to any one of claims 1 to 19, wherein: The compact TRS IE includes CSI-RS-for-tracking-Resource IE.

21. A wireless device for compactly configuring a tracking reference signal (TRS), the wireless device comprising: Processing circuitry configured to perform any of the steps of any of claims 1 to 20.

22. A method for providing a compact tracking reference signal (TRS) configuration performed by a network node (1500), the method comprising: determining (1404) at least one TRS configuration for the wireless device (1012); as well as Based on the at least one TRS configuration, a compact TRS information element (IE) is provided (1406) to the wireless device (1012), wherein the compact TRS IE is provided without providing a channel state information reference signal (CSI-RS) configuration.

23. The method according to claim 22, wherein: The compact TRS IE is available when the wireless device (1012) is in idle mode and connected mode.

24. The method according to any one of claims 22 to 23, wherein: The compact TRS IE is provided when the wireless device is in one of an idle mode or an inactive mode.

25. The method according to any one of claims 22 to 24, wherein: The compact TRS IE is provided through at least one of system information SI, radio resource control RRC configuration or RRC release.

26. The method according to claim 25, wherein: When the compact TRS IE is provided to multiple mobile devices through SI or broadcast, the network node considers the common preferred parameter configuration from the mobile devices.

27. The method according to any one of claims 22 to 26, further comprising: receiving (1400) capability signaling indicating a capability of the wireless device to utilize the compact TRS IE; as well as In response to receiving (1400) the capability signaling, the at least one TRS configuration is determined (1404).

28. The method according to any one of claims 22 to 27, further comprising: Receiving (1402) compact TRS configuration assistance information; as well as Based on the capability signaling, the at least one TRS configuration is determined (1404).

29. The method according to claim 28, wherein: The compact TRS configuration assistance information includes preferences for parameters to be included in the compact TRS IE.

30. The method according to any one of claims 28 to 29, wherein: The compact TRS configuration auxiliary information includes at least one preferred compact TRS configuration.

31. The method according to any one of claims 22 to 30, wherein: The compact TRS IE includes the following parameters: powerControlOffsetSS, scramblingID, periodicityAndOffset, firstOFDMSymbolInTimeDomain, startingRB, and nrofRBs.

32. The method according to claim 31, wherein: The compact TRS IE optionally includes one or more of the following parameters: aperiodicTriggeringOffset or qcl-InfoPeriodicCSI-RS.

33. The method according to any one of claims 22 to 32, wherein: The compact TRS IE omits one or more of the following parameters: bwp-Id, resourceType, repetition, aperiodicTriggeringOffset, trs-Info, powerControlOffset, frequencyDomainAllocation, nrofPorts, firstOFDMSymbolInTimeDomain2, cdm-Type, or density.

34. The method according to any one of claims 22 to 33, wherein: The compact TRS IE omits each of the following parameters: bwp-Id, resourceType, repetition, trs-Info, powerControlOffset, frequencyDomainAllocation, nrofPorts, firstOFDMSymbolInTimeDomain2, cdm-Type, and density.

35. The method according to any one of claims 22 to 34, wherein: The compact TRS IE includes a TRS-Config IE.

36. The method according to any one of claims 22 to 35, wherein: The compact TRS IE includes CSI-RS-for-tracking-Resource IE.

37. A network node (1500) for compactly configuring a tracking reference signal (TRS), the network node comprising: Processing circuitry configured to perform any of the steps of any of claims 22 to 36.

Images