Using hybrid parameter sets to trigger aperiodic channel state information reference signal

Abstract

The devices, systems, and methods described herein can improve aperiodic CSI-RS processing in a hybrid parameter set environment. An exemplary method includes the following operations: receiving a downlink control information DCI message carried by a physical downlink control channel PDCCH on a second carrier, wherein the second carrier uses a second OFDM parameter set; obtaining an aperiodic CSI-RS time slot offset from the DCI message; determining a reference time slot in a first parameter set; determining a time slot of the aperiodic CSI-RS based on the reference time slot and the aperiodic CSI-RS time slot offset; and receiving or sending the aperiodic CSI-RS in the determined time slot.

Description

[0001] Related Applications

[0002] This application claims the benefit of U.S. Provisional Application No. 62 / 774,091, filed on November 30, 2018, entitled “TRIGGERING OF APERIODIC CHANNELSTATE INFORMATION REFERENCE SIGNALS WITH MIXED NUMEROLOGY,” the entire disclosure of which is incorporated herein by reference. Technical Field

[0003] The present disclosure relates generally to the field of wireless network communications, and more particularly to deploying aperiodic channel state information reference signals in a mixed parameter set environment. Background Art

[0004] Generally, unless different meanings are clearly given and / or different meanings are implied in the context of using the term, all terms used in this article will be interpreted according to their common meanings in the relevant technical field. Unless explicitly stated, all references to a / an / the unit, device, assembly, part, step, etc. should be publicly interpreted as referring to at least one instance of the unit, device, assembly, part, step, etc. Unless a step is explicitly described as being after or before another step and / or a step must be after or before another step implicitly, the steps of any method disclosed herein do not have to be performed in the exact order disclosed. Where appropriate, any feature of any embodiment disclosed herein may be applied to any other embodiment. Similarly, any advantage of any embodiment may be applicable to any other embodiment, and vice versa. Through the following description, other purposes, features and advantages of the attached embodiments will be apparent.

[0005] The next generation of mobile wireless communication systems (5G) or New Radio (NR) supports a variety of use cases and a variety of deployment scenarios. Some deployment scenarios include deployment at both low frequencies (hundreds of MHz) (similar to today's LTE) and very high frequencies (millimetre waves of tens of GHz).

[0006] Similar to LTE, NR uses orthogonal frequency division multiplexing (OFDM) in the downlink (i.e., from the network node, gNB, eNB, or base station to the user equipment (UE)). In the uplink (i.e., from the UE to the gNB), both discrete Fourier transform spread (DFT spread) OFDM and OFDM are supported.

[0007] The basic NR physical resources can therefore be viewed as Figure 1The time-frequency grid shown, where each resource element corresponds to one OFDM subcarrier during one OFDM symbol interval. The resource allocation in a time slot is described by the number of resource blocks (RBs) in the frequency domain and the number of OFDM symbols in the time domain. An RB corresponds to 12 consecutive subcarriers, and a time slot includes 14 OFDM symbols.

[0008] Different subcarrier spacing values ​​are supported in NR. The subcarrier spacing values ​​(also called parameter sets) supported in NR are given by Δf = (15 × 2 μ )kHz, where μ = 0, 1, 2, 3, 4. The possible subcarrier spacings are summarized in Table 1.

[0009] Parameter Set Slot length RB BW 15kHz 1ms 180kHz 30kHz 0.5ms 360kHz 60kHz 0.25ms 720kHz 120kHz 125μs 1.44MHz 240kHz 62.5μs 2.88MHz

[0010] Table 1: Slot lengths under different parameter sets.

[0011] In the time domain, downlink and uplink transmissions in NR are organized into subframes of the same size, similar to LTE, such as Figure 2 The subframe is further divided into time slots, and for (15×2 μ )kHz parameter set, the number of time slots in each subframe is 2 μ .

[0012] NR supports "slot-based" transmission. In each slot, the gNB sends downlink control information (DCI) about which UE the data is to be sent to and on which resources in the current downlink slot the data is to be sent. The DCI is carried on the physical control channel (PDCCH), while the data is carried on the physical downlink shared channel (PDSCH). Summary of the invention

[0013] A general aspect includes a method. The method also includes: receiving a downlink control information DCI message carried by a physical downlink control channel PDCCH on a second carrier, wherein the second carrier uses a second OFDM parameter set; obtaining an aperiodic CSI-RS time slot offset from the DCI message; determining a reference time slot in the first parameter set; determining a time slot of the aperiodic CSI-RS based on the reference time slot and the aperiodic CSI-RS time slot offset; and receiving or sending the aperiodic CSI-RS in the determined time slot. Other embodiments of this aspect include corresponding computer systems, apparatuses, and computer programs recorded on one or more computer storage devices, all of which are configured to perform the actions of the method.

[0014] Various implementations may include one or more of the following features. In the method, the first OFDM parameter set is different from the second OFDM parameter set. The OFDM parameter set is characterized by its subcarrier spacing. In the method, additionally, the wireless device sends a channel state information CSI report based on a measurement of the received aperiodic CSI-RS. The time slot of the aperiodic CSI-RS is determined to be a time slot that is X time slots later than the reference time slot, where X is the aperiodic CSI-RS time slot offset. The time slot of the aperiodic CSI-RS is determined to be a time slot that is X time slots later than the reference time slot, where X is the aperiodic CSI-RS time slot offset. Implementations of the described technology may include hardware, methods or processes, or computer software on a computer-accessible medium.

[0015] One general aspect includes a user equipment UE for receiving an aperiodic CSI-RS on a first carrier. The user equipment also includes: 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 operations, which may include: receiving a downlink control information DCI message carried by a physical downlink control channel PDCCH on a second carrier, wherein the second carrier uses a second OFDM parameter set; obtaining an aperiodic CSI-RS time slot offset from the DCI message; determining a reference time slot in the first parameter set on the first carrier; determining a time slot of the aperiodic CSI-RS based on the reference time slot and the aperiodic CSI-RS time slot offset; and receiving the aperiodic CSI-RS in the determined time slot of the aperiodic CSI-RS, or sending an associated CSI-RS report in the determined time slot. The device also includes a battery connected to the processing circuit and configured to power the UE. Other embodiments of this aspect include corresponding computer systems, apparatus, and computer programs recorded on one or more computer storage devices, each configured to perform the actions of the method.

[0016] Various implementations may include one or more of the following features. In the user equipment, the first OFDM parameter set is different from the second OFDM parameter set. The OFDM parameter set is characterized by its subcarrier spacing. In the user equipment, the wireless device sends a channel state information CSI report based on a measurement of the received aperiodic CSI-RS. Implementations of the described techniques may include hardware, a method or process, or computer software on a computer accessible medium.

[0017] A general aspect includes a communication system. The communication system includes 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 user equipment UE, wherein the cellular network may include at least one base station having a radio interface and a processing circuit, the processing circuit configured to non-periodically transmit CSI-RS information on a first carrier according to a first parameter set and a second carrier according to a second parameter set. Other embodiments of this aspect include corresponding computer systems, apparatuses, and computer programs recorded on one or more computer storage devices, all of which are configured to perform the actions of the method.

[0018] Various implementations may include one or more of the following features. In the communication system, the at least one base station includes a first base station and a second base station, wherein the first base station transmits via the first carrier and the second base station transmits via the second carrier. The first base station and the second base station are non-co-located base stations. The UE is configured to communicate with the base station. Implementations of the described techniques may include hardware, methods or processes, or computer software on a computer-accessible medium.

[0019] A general aspect includes a method. The method also includes: sending a downlink control information DCI message carried by a physical downlink control channel PDCCH on a second carrier, wherein the DCI message includes an aperiodic CSI-RS time slot offset; according to the aperiodic CSI-RS time slot offset, sending the aperiodic CSI-RS in the determined time slot of the aperiodic CSI-RS. Other embodiments of this aspect include corresponding computer systems, apparatuses, and computer programs recorded on one or more computer storage devices, all of which are configured to perform the actions of the method.

[0020] Various implementations may include one or more of the following features. In the method, the first carrier uses a first OFDM parameter set and the second carrier uses a second OFDM parameter set different from the first OFDM parameter set. The first OFDM parameter set and the second OFDM parameter set are characterized by corresponding subcarrier spacings. The method may include: receiving a channel state information CSI report from a wireless device based on a measurement of the received aperiodic CSI-RS. The time slot of the aperiodic CSI-RS is determined to be a time slot that is X time slots later than a reference time slot, where X is the aperiodic CSI-RS time slot offset. Implementations of the described techniques may include hardware, methods or processes, or computer software on a computer-accessible medium. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Figure 1: Examples of NR physical resources;

[0022] Figure 2 : NR time domain structure with 15kHz subcarrier spacing;

[0023] Figure 3 : Diagram of aperiodic CSI reporting;

[0024] Figure 4 : A diagram of a hybrid parameter set triggering of an aperiodic CSI-RS according to the method;

[0025] Figure 5 : A flowchart illustrating an example method in a UE for receiving an aperiodic CSI-RS on a first carrier using a first OFDM parameter set;

[0026] Figure 6 : A wireless network according to some embodiments;

[0027] Figure 7 : a user equipment according to some embodiments;

[0028] Figure 8 : A virtualized environment according to some embodiments;

[0029] Fig. 9 : a telecommunications network connected to a host computer via an intermediate network according to some embodiments;

[0030] Fig.10 : A host computer communicating with a user device via a base station over a partially wireless connection according to some embodiments;

[0031] Fig.11 : A method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments;

[0032] Fig.12 : A method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments;

[0033] Fig.13 : A method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments;

[0034] Fig.14 : A method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments;

[0035] These figures will be better understood by reference to the following detailed description. DETAILED DESCRIPTION

[0036] The PDCCH is typically sent in a control resource set (CORSET) in the first few OFDM symbols in each slot. In operation, the UE may first decode the PDCCH, and if the PDCCH is successfully decoded, the UE may then decode the corresponding PDSCH based on the decoded DCI in the PDCCH.

[0037] PDCCH is also used to dynamically schedule uplink data transmission. For example, similar to the downlink scenario, the UE first decodes the uplink grant in the DCI carried by the PDCCH, and then sends data on the physical uplink shared channel (PUSCH) based on the decoded control information in the uplink grant (such as modulation order, coding rate, and uplink resource allocation, etc.).

[0038] During network connection, each UE is assigned a unique C-RNTI (Cell Radio Network Temporary Identifier). The CRC (Cyclic Redundancy Check) bits attached to the DCI for the UE can be scrambled by the UE's C-RNTI so that the UE can identify its own DCI by checking the CRC bits of the DCI against the assigned C-RNTI.

[0039] DCI format used to schedule PUSCH:

[0040] For UL scheduling of PUSCH, the UL DCI includes at least the following bit fields:

[0041] Frequency domain resource allocation

[0042] Time domain resource allocation

[0043] Modulation and Coding Scheme (MCS)—5 bits

[0044] New data indicator—1 bit

[0045] Redundancy version—2 bits

[0046] HARQ process number—4 bits

[0047] TPC command for the scheduled PUSCH—2 bits

[0048] CSI Request—0, 1, 2, 3, 4, 5, or 6 bits determined by the higher layer parameter ReportTriggerSize.

[0049] DCI format used to schedule PDSCH:

[0050] For DL ​​scheduling of PDSCH, the DL DCI includes at least the following bit fields:

[0051] Frequency domain resource allocation

[0052] Time domain resource allocation

[0053] Modulation and coding scheme—5 bits

[0054] New data indicator—1 bit

[0055] Redundancy version—2 bits

[0056] HARQ process number—4 bits

[0057] ZP CSI-RS trigger—2 bits

[0058] CSI Report

[0059] The gNB uses channel state information (CSI) feedback to obtain DL CSI from the UE in order to determine how to send DL data to the UE on multiple antenna ports. CSI typically includes a channel rank indicator (RI), a precoding matrix indicator (PMI), and a channel quality indicator (CQI). RI is used to indicate the number of data layers that can be sent simultaneously to a specific UE; PMI is used to indicate the precoding matrix on the indicated data layer; and CQI is used to indicate the modulation and coding rate that can be achieved using the indicated rank and precoding matrix. A special type of CSI report is a beam report, in which the gNB sends multiple CSI-RS resources in multiple beams, and the UE feeds back multiple strongest beams in the multiple beams in the form of multiple CSI-RS resource indicators (CRIs) and L1-RSRP (reference signal received power) for each selected resource.

[0060] In NR, in addition to periodic and aperiodic CSI reporting as in LTE, semi-persistent CSI reporting is also supported. Therefore, three types of CSI reporting can be supported in NR as follows:

[0061] First, periodic CSI (P-CSI) reporting on PUCCH. The UE reports CSI periodically. Parameters such as period and slot offset are semi-statically configured through high-layer RRC signaling from the gNB to the UE.

[0062] Second, aperiodic CSI (A-CSI) reporting on PUSCH. This type of CSI reporting involves a one-time (i.e., one-time) CSI report by the UE, which is dynamically triggered by the gNB using DCI. Some parameters related to the configuration of aperiodic CSI reporting are semi-statically configured by RRC, but the triggering is dynamic.

[0063] Third, semi-persistent CSI (SP-CSI) reporting on PUSCH. Similar to periodic CSI reporting, semi-persistent CSI reporting has a period and slot offset that can be semi-statically configured. However, a dynamic trigger from the gNB to the UE may be required to allow the UE to start semi-persistent CSI reporting. A dynamic trigger from the gNB to the UE is required to request the UE to stop semi-persistent CSI reporting.

[0064] CSI Reference Signal (NZP CSI-RS)

[0065] The UE uses non-zero power (NZP) CSI-RS to measure downlink CSI. CSI-RS is transmitted on each transmit (Tx) antenna port at the gNB, and for different antenna ports, CSI-RS is multiplexed in the time domain, frequency domain, and code domain so that the UE can measure the channel between each Tx antenna port at the gNB and each receive antenna port at the UE. The time-frequency resources used to transmit CSI-RS can be referred to as CSI-RS resources.

[0066] In NR, the following three types of CSI-RS transmission are supported:

[0067] First, Periodic CSI-RS (PCSI-RS): CSI-RS is transmitted periodically in a specific time slot. The CSI-RS transmission is semi-statically configured using parameters such as CSI-RS resource, period, and slot offset.

[0068] Second, aperiodic CSI-RS (AP CSI-RS). This is a one-time CSI-RS transmission that can occur in any time slot. Here, one-time means that CSI-RS transmission occurs only once per trigger. The CSI-RS resources within the time slot (i.e., resource element positions including subcarrier positions and OFDM symbol positions) used for aperiodic CSI-RS are semi-statically configured. The transmission of aperiodic CSI-RS is triggered by dynamic signaling through PDCCH using the CSI request field in UL DCI. Multiple aperiodic CSI-RS resources can be included in a CSI-RS resource set, and the triggering of aperiodic CSI-RS is based on the resource set. The time slot offset of CSI-RS relative to the triggering DCI is given by the RRC parameter aperiodicTriggeringOffset, which is given at the CSI-RS resource set level.

[0069] Third, semi-persistent CSI-RS (SP CSI-RS). Similar to periodic CSI-RS, the resources used for semi-persistent CSI-RS transmission are semi-statically configured with parameters such as period and slot offset. However, unlike periodic CSI-RS, dynamic signaling is required to activate and deactivate CSI-RS transmission.

[0070] In case of aperiodic CSI-RS and / or aperiodic CSI reporting, the gNB RRC configures the UE with S_c CSI triggering states. Each triggering state contains the aperiodic CSI reporting setting to be triggered and the associated aperiodic CSI-RS resource set.

[0071] CSI framework in NR:

[0072] In NR, a UE may be configured with N≥1 CSI reporting configurations (i.e., ReportConfigs), M≥1 resource configurations (i.e., ResourceConfigs). At least the following configuration parameters may be signaled via RRC for CSI acquisition.

[0073] N, M, and L are indicated implicitly or explicitly

[0074] In each CSI reporting setting, include at least the following:

[0075] ο Reported CSI parameters, such as RI, PMI, CQI

[0076] o CSI type (if reported), e.g. Type I or Type II

[0077] o Codebook configuration, including codebook subset restrictions

[0078] οTime domain behavior, such as P-CSI, SP-CSI or A-CSI

[0079] o Frequency granularity of CQI and PMI, such as wideband, part-band or sub-band

[0080] o Measurement restriction configuration, such as RBs in the frequency domain and time slots in the time domain

[0081] οCarrier information, in case of cross-carrier triggering

[0082] In each CSI-RS resource setting:

[0083] Configuration of οS≥1 CSI-RS resource set

[0084] ο The configuration of Ks≥1 CSI-RS resources for each resource set s includes at least:

[0085] RE mapping, number of antenna ports, time domain behavior, etc.

[0086] οTime domain behavior: aperiodic, periodic or semi-persistent

[0087] A-CSI reporting on PUSCH

[0088] The A-CSI report on PUSCH is triggered by the DCI (i.e., UL DCI) used to schedule the PUSCH. A special CSI request bit field in the DCI is defined for this purpose. Each value of the CSI request bit field defines a code point, and each code point can be associated with a CSI report triggering state configured by a higher layer. The first code point of all "0" corresponds to no CSI request. For A-CSI reporting, s c Each of the trigger states includes an indication of one or more A-CSI reports to be triggered. Optionally, each triggered A-CSI report may also trigger an aperiodic NZP CSI-RS resource set for channel measurement, an aperiodic CSI-IM for interference measurement, and / or an aperiodic NZP CSI-RS. Therefore, each CSI report trigger state defines at least the following information:

[0089] Resource allocation

[0090] οCSI reference signal (CSI-RS) resources for channel measurement

[0091] οInterference measurement resources for interference measurement

[0092] CSI report configuration:

[0093] o Type of CSI report, i.e. wideband or subband, type I or type II codebook used, etc.

[0094] The bit width of the CSI request field is L c Configurable from 0 to 6 bits. When the number of CSI trigger states S c Greater than the number of code points (i.e. ), using MAC (Media Access Control) CE (Control Element) from S c Select the trigger state with A subset of trigger states is defined so that there is a one-to-one mapping between each code point and the CSI trigger state. Figure 3 Some of these aspects can be seen in the figure of non-periodic CSI reporting in.

[0095] There are certain challenges currently. The current aperiodic CSI-RS triggering process in NR is not clearly defined for the case where the DCI that triggers the aperiodic CSI-RS and the aperiodic CSI-RS itself are sent on carriers or bandwidth parts using different parameter sets. For example, since different parameter sets result in different time slot lengths and therefore different time slot indices, it is unclear how to derive in which time slot the aperiodic CSI-RS resource is sent. Another issue is that in the case where the CSI-RS subcarrier spacing (SCS) is larger than the PDCCH SCS, the aperiodic CSI-RS can be sent non-causally, which will require the UE implementation to buffer OFDM symbols in several time slots in the carrier with a larger SCS when potential aperiodic CSI-RS triggering in the carrier with a smaller SCS is expected, which increases the complexity and memory consumption of the UE implementation.

[0096] Certain aspects of the present disclosure and embodiments thereof may provide solutions to these or other challenges, thereby reducing UE implementation complexity and memory consumption. In the present disclosure, predefined rules are introduced to map the PDCCH reception slot in the parameter set for triggering the PDCCH to the reference slot in the parameter set for the CSI-RS, so that the reference slot is the latest slot that overlaps with the PDCCH reception slot in time. Then, the triggering offset of the aperiodic CSI-RS is applied relative to the reference slot in the CSI-RS parameter set.

[0097] Additionally, in the case where the PDCCH SCS is smaller than the aperiodic CSI-RS SCS, a restriction on the aperiodic CSI-RS slot offset may be applied so that PDCCH decoding may be ensured to be completed earlier in time than the occurrence of the aperiodic CSI-RS.

[0098] Various embodiments are proposed herein to solve one or more of the problems disclosed herein. For example, Figure 5 A method 500 for receiving an aperiodic CSI-RS on a first carrier using a first OFDM parameter set performed by a wireless device according to some embodiments of the present disclosure is shown, and the method 500 may include several operations. Such operations may include: receiving a DCI message carried by a PDCCH on a second carrier using a second OFDM parameter set (operation 502); obtaining an aperiodic CSI-RS time slot offset from the DCI message (operation 504); determining a reference time slot in the first parameter set on the first carrier (operation 506); determining a time slot of the aperiodic CSI-RS based on the reference time slot and the aperiodic CSI-RS time slot offset (operation 508); and receiving the aperiodic CSI-RS in the determined time slot of the aperiodic CSI-RS (operation 510). Additional embodiments of the method 500 may include Figure 5 For example, embodiments of method 500 may include additional operations before, after, between, or as part of the enumerated operations. Some embodiments of method 500 include a set of instructions stored on a computer-readable medium that can be executed by a processor to perform the associated operations.

[0099] Certain embodiments may provide one or more of the following technical advantages. Aperiodic triggering of CSI-RS may be seamlessly supported, independent of the parameter sets of PDCCH and CSI-RS. Existing RRC configuration of aperiodic CSI-RS triggering offset may be reused for mixed parameter set aperiodic CSI-RS triggering cases. By mapping the PDCCH reception time slot to the reference time slot in the CSI-RS parameter set as the latest overlapping time slot, the number of OFDM symbols of the CSI-RS parameter set that the UE needs to buffer in anticipation of a potential aperiodic CSI-RS trigger is minimized, which minimizes UE memory consumption and complexity.

[0100] The technology proposed herein discloses a method for aperiodic CSI-RS triggering, wherein a PDCCH carrying a triggering DCI is sent on a different carrier or bandwidth portion than the triggered aperiodic CSI-RS, wherein additionally, the carrier or bandwidth portion of the PDCCH uses a different parameter set than the carrier or bandwidth portion on which the aperiodic CSI-RS is sent. Here, the parameter set is equivalent to a subcarrier spacing (SCS), and the SCS can be represented by μ, μ, μ, and μ, respectively. CSIRS and μ PDCCH To represent (corresponding to Δf = (15 × 2 μ )kHz SCS). The proposed technique can provide a CSIRS With μ PDCCH All possible relationships between CSIRS >μ PDCCH , μ CSIRS <μ PDCCH and μ CSIRS =μ PDCCH ) is a general solution.

[0101] In prior art solutions, only aperiodic CSI-RS triggering is considered where the CSI-RS and the triggering PDCCH have the same parameter set. In this case, it is relatively simple to determine the time slot of the aperiodic CSI-RS as the time slot that is X time slots after the time slot in which the PDCCH is received. For example, if the PDCCH is received in time slot n, the CSI-RS is sent in time slot n+X, where X is the RRC configured aperiodic CSI-RS time slot offset. However, for the mixed parameter set triggering case, it is unclear how to interpret such a time slot offset.

[0102] The solution proposed in this disclosure may rely on a predefined mapping between the PDCCH reception slots in the parameter set defining the PDCCH to the reference slot n' in the parameter set defining the CSI-RS. The indicated slot offset X is then mapped to slot n'+X in the parameter set defining the CSI-RS.

[0103] In some embodiments, the reference time slot n' is a time slot that overlaps with the time slot of the PDCCH in time. For example, the latest time slot in which the CSI-RS parameters are concentrated and overlaps with the time slot of the PDCCH in time is determined as the reference time slot. Alternatively, the earliest time slot in which the CSI-RS parameters are concentrated and overlaps with the time slot of the PDCCH in time is determined as the reference time slot (or more generally determined as a predetermined time slot).

[0104] In another embodiment, a time slot that does not overlap in time is selected as the reference time slot, for example, the earliest time slot in the CSI-RS parameter set that does not overlap in time with the reference time slot. The term "overlapping time slot" includes two concepts. In one embodiment, the time slot timing of the two carriers / bandwidth parts received by the UE is used to determine whether the time slots overlap. In another embodiment, the UE compensates for any potential reception timing differences before determining the reference time slot, that is, the earliest time slots in the subframes of the two parameter sets have the same start time. The two carriers may be transmitted by non-co-located base stations or transmission points, and therefore the propagation delays are different, resulting in different reception times.

[0105] In some embodiments, the UE may implicitly determine the reference time slot as part of the process for determining the aperiodic CSI-RS time slot, i.e., the UE may use the reference time slot as an intermediate calculation in the process of determining the aperiodic CSI-RS time slot and may not explicitly determine the reference time slot.

[0106] In one example, the reference time slot may be determined as Where n is the time slot that triggers the PDCCH. The time slot counters n and n' are usually restarted at each subframe boundary. This maps the reference time slot to:

[0107] ·In μ CSIRS >μ PDCCH In the case of , the latest time slot overlapping with the PDCCH time slot,

[0108] ·In μ CSIRS =μ PDCCH In the case of

[0109] ·In μ CSIRS <μ PDCCH In the case of overlapping time slots of PDCCH time slots,

[0110] This is what is expected.

[0111] exist Figure 4 A diagram of the above example is given in .

[0112] Additional Notes

[0113] Some embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. However, other embodiments are included within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as being limited to the embodiments set forth herein; rather, these embodiments are provided merely as examples to convey the scope of the subject matter to those skilled in the art.

[0114] In one embodiment, when μ CSIRS >μ PDCCH When the aperiodic slot offset X is set, a restriction on the slot offset X is imposed so that the aperiodic slot offset must be greater than a certain value, such as zero. Implementing a non-zero slot offset ensures that the aperiodic CSI-RS is always sent after the PDCCH reception is completed, which eliminates the need for the UE to buffer OFDM symbols on the CSI-RS carrier when a potential aperiodic CSI-RS trigger on the PDCCH carrier is expected.

[0115] In another embodiment, the time slot offset X is scaled based on the parameter set ratio, i.e., in the time slot The CSI-RS is transmitted in , where n is the reference slot determined as above and X is the indicated slot offset. Using the scaled X instead of using X directly can be limited to μ CSIRS >μ PDCCH The timeslots with higher μ values ​​are shorter, so the scaling compensates for this and guarantees that the UE has enough time.

[0116] Using the specification language of TS 38.214, the method proposed in this article can be implemented as follows:

[0117] When aperiodic CSI-RS is used with aperiodic reporting, the CSI-RS offset X is configured per resource set by the higher layer parameter aperiodicTriggeringOffset. The CSI-RS triggering offset has a range of 0 to 4 slots. The UE shall Where n is the time slot in the parameter set of the PDCCH that triggers the DCI, X is the CSI-RS triggering offset in the parameter set of the CSI-RS according to the high-level parameter aperiodicTriggeringOffset, and μ CSIRS and μ PDCCHSubcarrier spacing configuration for CSI-RS and PDCCH, respectively. If not all associated trigger states have the high-level parameter qcl-Type set to "QCL-TypeD" in the corresponding TCI state, the CSI-RS trigger offset is fixed to zero. If the PDCCH SCS is less than the CSI-RS SCS, the CSI-RS trigger offset is greater than zero. The aperiodic trigger offset of the CSI-IM follows the offset of the associated NZP CSI-RS for channel measurement.

[0118] For CSI-RS resource sets associated with resource settings configured using the higher layer parameter resourceType set to "aperiodic", "periodic" or "semi-persistent", the higher layer parameter CSI-AperiodicTriggerStateList is used to configure the trigger state of the report settings (configured using the higher layer parameter reportConfigType set to "aperiodic") and / or the resource settings for channel and / or interference measurements on one or more component carriers. For aperiodic CSI report triggering, a single set of CSI triggering states is higher layer configured, where the CSI triggering state can be associated with any candidate DL BWP. The UE is not expected to receive more than one DCI with non-zero CSI request in each timeslot. For the same aperiodic CSI-RS resource ID configured in multiple aperiodic CSI-RS resource sets (with the same triggering offset in the same aperiodic triggering state), the UE is not expected to be configured with different TCI-StateIds. The UE is not expected to receive more than one aperiodic CSI report request for transmission in a given timeslot. For inactive DL BWP, the UE is not expected to be triggered using CSI reporting. The CSI request field in the DCI is used to initiate the triggering state.

[0119] When all bits of the CSI request field in the DCI are set to zero, no CSI is requested.

[0120] When the number of CSI trigger states configured in CSI-AperiodicTriggerStateList is greater than (where N TS is the number of bits in the DCI CSI request field), the UE receives a selection command [10, TS 38.321] for transferring up to The trigger status is mapped to the code point of the CSI request field in the DCI. TS Configured by the high-level parameter reportTriggerSize, where NTS ∈{0,1,2,3,4,5,6}. When a HARQ / ACK corresponding to a PDSCH carrying a selection command is sent in slot n, The corresponding actions in [10, TS 38.321] and the UE's assumptions on the mapping of the selected CSI triggering states to the codepoints of the DCI CSI request field are applied.

[0121] When the number of CSI trigger states in CSI-AperiodicTriggerStateList is less than or equal to When the CSI request field in the DCI directly indicates the trigger status.

[0122] For each non-periodic CSI-RS resource in the CSI-RS resource set associated with each CSI triggering state, the quasi-co-location RS source and the quasi-co-location type of quasi-co-location configuration are indicated to the UE via high-layer signaling qcl-info (which contains a list of references to the TCI-State of the non-periodic CSI-RS resource associated with the CSI triggering state), as described in subclause 5.1.5. If the State referenced in the list is configured with a reference to an RS associated with "QCL-TypeD", the RS can be an SS / PBCH block located in the same or different CC / DL BWP, or a CSI-RS resource configured to be periodically or semi-persistently located in the same or different CC / DL BWP.

[0123] If, in the parameter set of the aperiodic CSI-RS, the scheduling offset between the last symbol of the PDCCH carrying the triggered DCI and the first symbol of the aperiodic CSI-RS resources in the NZP-CSI-RS-ResourceSet configured without the higher-level parameter trs-Info and without the higher-level parameter repetition is less than the UE-reported threshold beamSwitchTiming as defined in [13, TS 38.306] (when the reported value is one of the values ​​{14, 28, 48}), the UE also applies the QCL assumption of the other DL signal when receiving the aperiodic CSI-RS if there is any other DL signal with the indicated TCI state in the same symbol as the CSI-RS. Another DL signal refers to PDSCH scheduled with an offset greater than or equal to the threshold timeDurationForQCL as defined in [13, TS38.306], aperiodic CSI-RS scheduled with an offset greater than or equal to the UE reported threshold beamSwitchTiming (when the reported value is one of the values ​​{14, 28, 48}), periodic CSI-RS, and semi-persistent CSI-RS.

[0124] If, in the parameter set of aperiodic CSI-RS, the scheduling offset between the last symbol of the PDCCH carrying the triggering DCI and the first symbol of the aperiodic CSI-RS resource is equal to or greater than the UE-reported threshold beamSwitchTiming (when the reported value is one of the values ​​{14, 28, 48}), the UE is expected to apply the QCL assumption in the indicated TCI state for the aperiodic CSI-RS resources in the CSI triggered state indicated by the CSI triggering field in the DCI.

[0125] According to CSI-AperiodicTriggerStateList up to The non-zero code points of the CSI request field in the DCI are mapped to the CSI trigger states in the order of the associated positions of the trigger states, where the code point "1" is mapped to the trigger state in the first position.

[0126] For a UE configured using the higher-layer parameter CSI-AperiodicTriggerStateList, if the resource setting linked to the CSI-ReportConfig has multiple aperiodic resource sets, only one aperiodic CSI-RS resource set in the resource setting is associated with the trigger state, and the UE is configured by the higher layers according to the resource setting and according to the trigger state to select a CSI-IM / NZP CSI-RS resource set from the resource setting.

[0127] When aperiodic CSI-RS is used with aperiodic reporting, the higher-level parameter aperiodicTriggeringOffset configures the CSI-RS offset X per resource set. The CSI-RS triggering offset has a range of 0 to 4 slots. The UE shall CSI is sent in , where n is the time slot that triggers DCI in the parameter set of PDCCH, X is the CSI-RS triggering offset according to the high-level parameter aperiodicTriggeringOffset in the parameter set of CSI-RS, and μ CSIRS and μ PDCCH Subcarrier spacing configuration for CSI-RS and PDCCH, respectively. If not all associated trigger states have the high-level parameter qcl-Type set to "QCL-TypeD" in the corresponding TCI state, the CSI-RS trigger offset is fixed to zero. If the PDCCH SCS is less than the CSI-RS SCS, the CSI-RS trigger offset is greater than zero. The aperiodic trigger offset of the CSI-IM follows the offset of the associated NZP CSI-RS for channel measurement.

[0128] The UE does not expect the aperiodic CSI-RS to be sent before the OFDM symbol carrying its triggering DCI. If interference measurement is performed on the aperiodic NZP CSI-RS, the UE is not expected to be configured with an aperiodic trigger offset for the NZP CSI-RS for interference measurement that is different from the associated NZP CSI-RS for channel measurement. If the UE is configured with a single carrier for uplink, the UE is not expected to send more than one aperiodic CSI report triggered by different DCIs on overlapping OFDM symbols.

[0129] Although the subject matter described herein may be implemented in any suitable type of system using any suitable components, the embodiments disclosed herein are directed to wireless networks such as Figure 6 For simplicity, Figure 6 The wireless network of FIG. 60 only depicts network 606, network nodes 660 and 660b, and WD 610, 610b, and 610c. In practice, the wireless network may further include any additional units suitable for supporting communication between wireless devices or between a wireless device and another communication device (e.g., a landline phone, a service provider, or any other network node or terminal device). In the components shown, network node 660 and wireless device (WD) 610 are depicted in additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate wireless devices to access and / or use services provided by or via the wireless network.

[0130] A wireless network may include and / or be connected to any type of communication, telecommunication, data, cellular and / or radio network or other similar type of system. In some embodiments, a wireless network may be configured to operate according to a specific standard or other type of predefined rules or procedures. Thus, specific embodiments of a wireless network may implement: communication standards such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards such as IEEE 802.11 standards; and / or any other suitable wireless communication standards such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-wave, and / or ZigBee standards.

[0131] Network 606 may include one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTN), packet data networks, optical networks, wide area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks that enable communications between devices.

[0132] The network node 660 and the WD 610 include various components described in more detail below. These components work together to provide network node and / or wireless device functions, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may include any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals (whether via wired or wireless connections).

[0133] As used herein, a network node refers to a device that is capable of, configured, arranged and / or operable to communicate directly or indirectly with a wireless device and / or with other network nodes or devices in a wireless network to enable and / or provide wireless access to a wireless device and / or perform other functions (e.g., management) in a wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, node Bs, evolved node Bs (eNBs), and NR node Bs (gNBs)). Base stations can be classified based on the amount of coverage provided by the base station (or in other words, their transmit power levels), and then they can also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station can be a relay node or a relay donor node that controls a relay. A network node may also include one or more (or all) parts of a distributed radio base station (e.g., a centralized digital unit and / or a remote radio unit (RRU) (sometimes also referred to as a remote radio head (RRH))). Such a remote radio unit may or may not be integrated with an antenna as an antenna-integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Other examples of network nodes include multi-standard radio (MSR) devices such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and / or MDTs. As another example, a network node may be a virtual network node as described in more detail below. However, more generally, a network node may represent any suitable device (or group of devices) that is capable of, configured, arranged, and / or operable to enable and / or provide access to a wireless network by a wireless device or to provide a certain service to a wireless device that has accessed a wireless network.

[0134] exist Figure 6 In the embodiment, the network node 660 includes a processing circuit 670, a device readable medium 680, an interface 690, an auxiliary device 684, a power supply 686, a power supply circuit 687, and an antenna 662. Figure 6 The network node 660 shown in the example wireless network of can represent a device including the combination of hardware components shown, but other embodiments can include network nodes with different combinations of components. It should be understood that the network node includes any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. In addition, although the components of the network node 660 are depicted as a single box located within a larger box or nested within multiple boxes, in reality, the network node may include multiple different physical components that make up a single shown component (for example, the device readable medium 680 may include multiple separate hard drives and multiple RAM modules).

[0135] Similarly, the network node 660 may include multiple physically separated components (e.g., a node B component and an RNC component, or a BTS component and a BSC component, etc.), each of which may have its own corresponding components. In some cases where the network node 660 includes multiple separate components (e.g., a BTS and a BSC component), one or more separate components may be shared between multiple network nodes. For example, a single RNC may control multiple node Bs. In such a scenario, in some cases, each unique node B and RNC pair may be considered as a single separate network node. In some embodiments, the network node 660 may be configured to support multiple radio access technologies (RATs). In such an embodiment, some components may be replicated (e.g., separate device-readable media 680 for different RATs), while some components may be reused (e.g., the same antenna 662 may be shared by the RAT). The network node 660 may also include multiple groups of various example components for different wireless technologies (e.g., GSM, WCDMA, LTE, NR, Wi-Fi, or Bluetooth wireless technologies) integrated into the network node 660. These wireless technologies may be integrated into the same or different chips or chipsets and other components within the network node 660.

[0136] The processing circuit 670 is configured to perform any determination, calculation, or similar operation (e.g., certain obtaining operations) described herein as being provided by the network node. These operations performed by the processing circuit 670 may include: processing information obtained by the processing circuit 670, for example, by converting the obtained information into other information, comparing the obtained information or the converted information with information stored in the network node, and / or performing one or more operations based on the obtained information or the converted information; and making a determination as a result of the processing.

[0137] The processing circuit 670 may include a combination of one or more of a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and / or encoded logic operable to provide network node 660 functionality, either alone or in combination with other network node 660 components (e.g., device readable medium 680). For example, the processing circuit 670 may execute instructions stored in the device readable medium 680 or in a memory within the processing circuit 670. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, the processing circuit 670 may include a system on a chip (SOC).

[0138] In some embodiments, processing circuitry 670 may include one or more of radio frequency (RF) transceiver circuitry 672 and baseband processing circuitry 674. In some embodiments, radio frequency (RF) transceiver circuitry 672 and baseband processing circuitry 674 may be on separate chips (or chipsets), boards, or units (e.g., a radio unit and a digital unit). In alternative embodiments, some or all of RF transceiver circuitry 672 and baseband processing circuitry 674 may be on the same chip or chipset, board, or unit.

[0139] In certain embodiments, some or all of the functions described herein as being provided by a network node, base station, eNB, or other such network device may be performed by processing circuit 670 executing instructions stored on a device-readable medium 680 or a memory within processing circuit 670. In alternative embodiments, some or all of the functions may be provided by processing circuit 670 without the need to execute instructions stored on a separate or separate device-readable medium, such as in a hardwired manner. In any of these embodiments, processing circuit 670 can be configured to perform the described functions regardless of whether instructions stored on a device-readable storage medium are executed. The benefits provided by such functions are not limited to processing circuit 670 or other components of network node 660, but are enjoyed by network node 660 as a whole and / or generally by end users and wireless networks.

[0140] Device readable medium 680 may include any form of volatile or non-volatile computer readable memory, including but not limited to permanent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disk (CD), or digital video disk (DVD)), and / or any other volatile or non-volatile, non-transitory device readable and / or computer executable storage device that stores information, data, and / or instructions that can be used by processing circuit 670. Device readable medium 680 may store any suitable instructions, data, or information, including computer programs, software, applications (including one or more of logic, rules, code, tables, etc.), and / or other instructions that can be executed by processing circuit 670 and utilized by network node 660. Device readable medium 680 may be used to store any calculations performed by processing circuit 670 and / or any data received via interface 690. In some embodiments, processing circuit 670 and device readable medium 680 may be considered integrated.

[0141] Interface 690 is used for wired or wireless communication of signaling and / or data between network node 660, network 606 and / or WD 610. As shown, interface 690 includes port / terminal 694 to send and receive data from network 606 to network 606, for example, by wired connection. Interface 690 also includes radio front-end circuit 692 that can be coupled to antenna 662 or as a part of antenna 662 in some embodiments. Radio front-end circuit 692 includes filter 698 and amplifier 696. Radio front-end circuit 692 can be connected to antenna 662 and processing circuit 670. Radio front-end circuit 692 can be configured to adjust the signal transmitted between antenna 662 and processing circuit 670. Radio front-end circuit 692 can receive digital data that will be sent to other network nodes or WD via wireless connection. Radio front-end circuit 692 can use the combination of filter 698 and / or amplifier 696 to convert digital data into radio signals with appropriate channel and bandwidth parameters. Radio signals can then be transmitted via antenna 662. Similarly, when receiving data, antenna 662 may collect radio signals, which may then be converted into digital data by radio front end circuit 692. The digital data may be passed to processing circuit 670. In other embodiments, the interface may include different components and / or different combinations of components.

[0142] In some alternative embodiments, the network node 660 may not include a separate radio front end circuit 692, but rather, the processing circuit 670 may include the radio front end circuit and may be connected to the antenna 662 without a separate radio front end circuit 692. Similarly, in some embodiments, all or a portion of the RF transceiver circuit 672 may be considered part of the interface 690. In other embodiments, the interface 690 may include one or more ports or terminals 694, the radio front end circuit 692, and the RF transceiver circuit 672 as part of a radio unit (not shown), and the interface 690 may communicate with a baseband processing circuit 674 that is part of a digital unit (not shown).

[0143] Antenna 662 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals. Antenna 662 may be coupled to radio front-end circuit 690 and may be any type of antenna capable of wirelessly sending and receiving data and / or signals. In some embodiments, antenna 662 may include one or more omnidirectional, sector or flat panel antennas operable to send / receive radio signals between, for example, 2 GHz and 66 GHz. Omnidirectional antennas may be used to send / receive radio signals in any direction, sector antennas may be used to send / receive radio signals from devices within a specific area, and flat panel antennas may be line of sight antennas for sending / receiving radio signals in a relatively straight line. In some cases, the use of more than one antenna may be referred to as MIMO. In some embodiments, antenna 662 may be separated from network node 660 and may be connected to network node 660 via an interface or port.

[0144] Antenna 662, interface 690 and / or processing circuit 670 may be configured to perform any receiving operation and / or certain obtaining operation described herein as being performed by a network node. Any information, data and / or signal may be received from a wireless device, another network node and / or any other network device. Similarly, antenna 662, interface 690 and / or processing circuit 670 may be configured to perform any sending operation described herein as being performed by a network node. Any information, data and / or signal may be sent to a wireless device, another network node and / or any other network device.

[0145] The power circuit 687 may include or be coupled to a power management circuit and is configured to provide power for performing the functions described herein to the components of the network node 660. The power circuit 687 may receive power from the power supply 686. The power supply 686 and / or the power circuit 687 may be configured to provide power to the various components of the network node 660 in a form suitable for the various components (e.g., with the voltage and current level required by each corresponding component). The power supply 686 may be included in the power circuit 687 and / or the network node 660 or outside it. For example, the network node 660 may be connected to an external power source (e.g., a power outlet) via an input circuit or interface (e.g., a cable), whereby the external power source provides power to the power circuit 687. As another example, the power supply 686 may include a power source in the form of a battery or battery pack connected to the power circuit 687 or integrated therein. If the external power supply fails, the battery can provide backup power. Other types of power supplies, such as photovoltaic devices, may also be used.

[0146] Alternative embodiments of network node 660 may include Figure 6 Additional components beyond those shown, which may be responsible for providing certain aspects of the functionality of the network node, including any functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 660 may include a user interface device to allow information to be input into the network node 660 and to allow information to be output from the network node 660. This may allow a user to perform diagnostics, maintenance, repair, and other management functions for the network node 660.

[0147] As used herein, wireless device (WD) refers to a device capable of, configured, arranged and / or operable to wirelessly communicate with a network node and / or other wireless devices. Unless otherwise specified, the term WD may be used interchangeably with user equipment (UE) in this article. Wireless communication may involve the use of electromagnetic waves, radio waves, infrared waves and / or other types of signals suitable for transmitting information through the air to send and / or receive wireless signals. In some embodiments, WD may be configured to send and / or receive information without direct human interaction. For example, WD may be designed to send information to the network in a predetermined schedule when triggered by an internal or external event or in response to a request from the network. Examples of WD include, but are not limited to, smart phones, mobile phones, cellular phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablet computers, laptop computers, laptop computer built-in devices (LEEs), laptop computer installation devices (LMEs), smart devices, wireless user premises equipment (CPEs), vehicle installation wireless terminal devices, etc. WD can support device-to-device (D2D) communication, for example, by implementing 3GPP standards for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and vehicle-to-everything (V2X), and in this case can be referred to as a D2D communication device. As another specific example, in an Internet of Things (IoT) scenario, WD can represent a machine or other device that performs monitoring and / or measurement and sends the results of such monitoring and / or measurement to another WD and / or network node. In this case, WD can be a machine-to-machine (M2M) device, which can be referred to as an MTC device in the 3GPP context. As a specific example, WD can be a UE that implements the 3GPP narrowband Internet of Things (NB-IoT) standard. Specific examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or household or personal appliances (e.g., refrigerators, televisions, etc.), personal wearable devices (e.g., watches, fitness trackers, etc.). In other cases, WD can represent a vehicle or other device that can monitor and / or report its operating status or other functions associated with its operation. WD as described above can represent an endpoint of a wireless connection, in which case the device can be referred to as a wireless terminal. Furthermore, the WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.

[0148] As shown, wireless device 610 includes antenna 611, interface 614, processing circuit 620, device readable medium 630, user interface device 632, auxiliary device 634, power supply 636 and power supply circuit 637. WD 610 can include multiple groups of one or more of the components shown for different wireless technologies supported by WD 610 (e.g., GSM, WCDMA, LTE, NR, Wi-Fi, WiMAX or Bluetooth wireless technology, to name a few). These wireless technologies can be integrated into the same or different chips or chipsets as other components in WD 610.

[0149] Antenna 611 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals, and is connected to interface 614. In some alternative embodiments, antenna 611 may be separated from WD 610 and may be connected to WD 610 via an interface or port. Antenna 611, interface 614 and / or processing circuit 620 may be configured to perform any receiving or transmitting operation described herein as being performed by WD. Any information, data and / or signal may be received from a network node and / or another WD. In some embodiments, radio front end circuit and / or antenna 611 may be considered as an interface.

[0150] As shown, the interface 614 includes a radio front-end circuit 612 and an antenna 611. The radio front-end circuit 612 includes one or more filters 618 and an amplifier 616. The radio front-end circuit 614 is connected to the antenna 611 and the processing circuit 620 and is configured to adjust the signal transmitted between the antenna 611 and the processing circuit 620. The radio front-end circuit 612 may be coupled to the antenna 611 or as part of the antenna 611. In some embodiments, the WD 610 may not include a separate radio front-end circuit 612; instead, the processing circuit 620 may include a radio front-end circuit and may be connected to the antenna 611. Similarly, in some embodiments, part or all of the RF transceiver circuit 622 may be considered as part of the interface 614. The radio front-end circuit 612 may receive digital data sent to other network nodes or WDs via a wireless connection. The radio front-end circuit 612 may use a combination of filters 618 and / or amplifiers 616 to convert the digital data into a radio signal with appropriate channel and bandwidth parameters. The radio signal may then be transmitted via the antenna 611. Similarly, when receiving data, antenna 611 may collect radio signals, which are then converted into digital data by radio front end circuit 612. The digital data may be passed to processing circuit 620. In other embodiments, the interface may include different components and / or different combinations of components.

[0151] Processing circuit 620 may include a combination of one or more of a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and / or encoded logic operable to provide WD 610 functionality alone or in combination with other WD 610 components (e.g., device readable medium 630). Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuit 620 may execute instructions stored in device readable medium 630 or in a memory within processing circuit 620 to provide functionality disclosed herein.

[0152] As shown, the processing circuit 620 includes one or more of the RF transceiver circuit 622, the baseband processing circuit 624, and the application processing circuit 626. In other embodiments, the processing circuit may include different components and / or different combinations of components. In some embodiments, the processing circuit 620 of the WD 610 may include a SOC. In some embodiments, the RF transceiver circuit 622, the baseband processing circuit 624, and the application processing circuit 626 may be on a separate chip or chipset. In alternative embodiments, part or all of the baseband processing circuit 624 and the application processing circuit 626 may be combined into one chip or chipset, and the RF transceiver circuit 622 may be on a separate chip or chipset. In other alternative embodiments, part or all of the RF transceiver circuit 622 and the baseband processing circuit 624 may be on the same chip or chipset, and the application processing circuit 626 may be on a separate chip or chipset. In other alternative embodiments, part or all of the RF transceiver circuit 622, the baseband processing circuit 624, and the application processing circuit 626 may be combined in the same chip or chipset. In some embodiments, RF transceiver circuitry 622 may be part of interface 614. RF transceiver circuitry 622 may condition RF signals for processing circuitry 620.

[0153] In some embodiments, some or all of the functions described herein as being performed by the WD may be provided by a processing circuit 620 that executes instructions stored on a device-readable medium 630 (which may be a computer-readable storage medium in some embodiments). In alternative embodiments, some or all of the functions may be provided by the processing circuit 620 without the need to execute instructions stored on a separate or separate device-readable medium, such as in a hardwired manner. In any of these specific embodiments, the processing circuit 620 can be configured to perform the described functions regardless of whether instructions stored on a device-readable storage medium are executed. The benefits provided by such functions are not limited to the processing circuit 620 or other components of the WD 610, but are enjoyed by the WD 610 as a whole and / or generally by end users and wireless networks.

[0154] Processing circuit 620 may be configured to perform any determination, calculation, or similar operation (e.g., certain acquisition operations) described herein as being performed by WD. Such operations performed by processing circuit 620 may include: processing information obtained by processing circuit 620, such as by converting the obtained information into other information, comparing the obtained information or the converted information with information stored by WD 610, and / or performing one or more operations based on the obtained information or the converted information; and making determinations as a result of the processing.

[0155] The device-readable medium 630 is operable to store computer programs, software, applications (including one or more of logic, rules, codes, tables, etc.), and / or other instructions executable by the processing circuit 620. The device-readable medium 630 may include a computer memory (e.g., random access memory (RAM) or read-only memory (ROM), a mass storage medium (e.g., a hard disk), a removable storage medium (e.g., a compact disk (CD) or a digital video disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable storage device that stores information, data, and / or instructions that may be used by the processing circuit 620. In some embodiments, the processing circuit 620 and the device-readable medium 630 may be considered to be integrated.

[0156] The user interface device 632 can provide a component that allows a human user to interact with the WD 610. This interaction can have a variety of forms, such as visual, auditory, tactile, etc. The user interface device 632 can be operable to generate output to the user and allow the user to provide input to the WD 610. The type of interaction can vary according to the type of user interface device 632 installed in the WD 610. For example, if the WD 610 is a smart phone, the interaction can be via a touch screen; if the WD 610 is a smart meter, the interaction can be through a screen that provides usage (such as the number of gallons used) or a speaker that provides an audible alarm (such as if smoke is detected). The user interface device 632 may include an input interface, device and circuit and an output interface, device and circuit. The user interface device 632 is configured to allow information to be input to the WD 610, and is connected to the processing circuit 620 to allow the processing circuit 620 to process the input information. The user interface device 632 may include, for example, a microphone, a proximity sensor or other sensor, a key / button, a touch display, one or more cameras, a USB port or other input circuits. The user interface device 632 is also configured to allow information to be output from the WD 610, and to allow the processing circuit 620 to output information from the WD 610. The user interface device 632 may include, for example, a speaker, a display, a vibration circuit, a USB port, a headphone jack, or other output circuits. Using one or more input and output interfaces, devices, and circuits of the user interface device 632, the WD 610 can communicate with an end user and / or a wireless network and allow them to benefit from the functionality described herein.

[0157] Auxiliary device 634 is operable to provide more specific functions that may not normally be performed by a WD. This may include specialized sensors for measuring for various purposes, interfaces for other communication types such as wired communications, etc. The inclusion and type of components of auxiliary device 634 may vary depending on the embodiment and / or scenario.

[0158] In some embodiments, the power supply 636 can take the form of a battery or a battery pack. Other types of power supplies can also be used, such as an external power supply (e.g., a power outlet), a photovoltaic device, or a battery. WD 610 may also include a power circuit 637 for delivering power from the power supply 636 to various parts of WD 610, which require power from the power supply 636 to perform any function described or indicated herein. In some embodiments, the power circuit 637 may include a power management circuit. The power circuit 637 may be additionally or alternatively operable to receive power from an external power source. In this case, WD 610 may be connected to an external power source (e.g., a power outlet) via an input circuit or interface (e.g., a power cord). In some embodiments, the power circuit 637 may also be operable to deliver power from an external power source to the power supply 636. This can be used, for example, to charge the power supply 636. The power circuit 637 may perform any formatting, conversion, or other modifications to the power from the power supply 636 so that the power is suitable for the corresponding components of the WD 610 to which the power is provided.

[0159] Figure 7 An embodiment of a UE 700 is shown in accordance with various aspects described herein. For example, the UE 700 may perform an embodiment of the method 500 and provide other features as described herein. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user who owns and / or operates the associated equipment. Rather, a UE may represent a device that is intended to be sold to or operated by a human user but may not be, or may not initially be, associated with a particular human user (e.g., a smart sprinkler controller). Alternatively, a 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). The UE 700 may be any UE identified by the Third Generation Partnership Project (3GPP), including a NB-IoT UE, a Machine Type Communication (MTC) UE, and / or an enhanced MTC (eMTC) UE. As Figure 7 As shown, UE 700 is an example of a WD that is configured to communicate according to one or more communication standards promulgated by the Third Generation Partnership Project (3GPP), such as 3GPP's GSM, UMTS, LTE, and / or 5G standards. As previously mentioned, the terms WD and UE may be used interchangeably. Therefore, although Figure 7 It is UE, but the components discussed in this article are also applicable to WD and vice versa.

[0160] exist Figure 7In the embodiment, UE 700 includes a processing circuit 701, which is operatively coupled to an input / output interface 705, a radio frequency (RF) interface 709, a network connection interface 711, a memory 715 (including a random access memory (RAM) 717, a read-only memory (ROM) 719, and a storage medium 721, etc.), a communication subsystem 731, a power supply 733 and / or any other components or any combination thereof. The storage medium 721 includes an operating system 723, an application 725, and data 727. In other embodiments, the storage medium 721 may include other similar types of information. Some UEs may utilize Figure 7 All components shown may be used, or only a subset of these components may be used. The level of integration between components may vary from one UE to another. In addition, some UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0161] exist Figure 7 In the embodiment of the present invention, the processing circuit 701 can be configured to process computer instructions and data. The processing circuit 701 can be configured to implement any sequential state machine operable to execute machine instructions stored as a machine-readable computer program in a memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic and appropriate firmware; one or more stored programs, general-purpose processors (e.g., microprocessors or digital signal processors (DSPs)) and appropriate software; or any combination of the above. For example, the processing circuit 701 may include two central processing units (CPUs). The data may be information in a form suitable for use by a computer.

[0162] In the depicted embodiment, the input / output interface 705 may be configured to provide a communication interface to an input device, an output device, or an input and output device. The UE 700 may be configured to use an output device via the input / output interface 705. The output device may use the same type of interface port as the input device. For example, a USB port may be used to provide input to the UE 700 or to provide output from the UE 700. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, a transmitter, a smart card, another output device, or any combination thereof. The UE 700 may be configured to use an input device via the input / output interface 705 to allow a user to capture information into the UE 700. The input device may include a touch-sensitive display or a presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a webcam, etc.), a microphone, a sensor, a mouse, a trackball, a steering wheel, a trackpad, a scroll wheel, a smart card, etc. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from the 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, another similar sensor, or any combination thereof. For example, the input device can be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

[0163] exist Figure 7 In the embodiment of the present invention, the RF interface 709 can be configured to provide a communication interface to RF components such as transmitters, receivers and antennas. The network connection interface 711 can be configured to provide a communication interface to the network 743a. The network 743a can include a wired and / or wireless network, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a telecommunications network, another similar network or any combination thereof. For example, the network 743a can include a Wi-Fi network. The network connection interface 711 can be configured to include a receiver and a transmitter interface, which is used to communicate with one or more other devices through a communication network according to one or more communication protocols (such as Ethernet, TCP / IP, SONET, ATM, etc.). The network connection interface 711 can implement receiver and transmitter functions suitable for communication network links (such as optical, electrical, etc.). The transmitter and receiver functions can share circuit components, software or firmware, or can be implemented separately instead.

[0164] RAM 717 may be configured to be connected to processing circuit 701 via bus 702 to provide storage or caching of data or computer instructions during the execution of software programs such as operating systems, applications, and device drivers. ROM 719 may be configured to provide computer instructions or data to processing circuit 701. For example, ROM 719 may be configured to store unchanged low-level system code or data for basic system functions (e.g., basic input and output (I / O), startup, reception of keystrokes stored in non-volatile memory from a keyboard). Storage medium 721 may be configured to include memories such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), disk, optical disk, floppy disk, hard disk, removable cassette, or flash drive. In one example, storage medium 721 may be configured to include operating system 723, application 725 such as a web browser application, a widget or gadget engine, or another application, and data file 727. The storage medium 721 may store any one of various operating systems or a combination of operating systems for use by the UE 700 .

[0165] The storage medium 721 may be configured to include multiple physical drive units, such as a redundant array of independent disks (RAID), a floppy disk drive, a flash memory, a USB flash drive, an external hard drive, a thumb drive, a pen drive, a key drive, a high-density digital versatile disk (HD-DVD) optical drive, an internal hard drive, a Blu-ray optical drive, a holographic digital data storage (HDDS) optical drive, an external mini dual in-line memory module (DIMM), a synchronous dynamic random access memory (SDRAM), an external micro DIMM SDRAM, a smart card memory (e.g., a user identity module or a removable user identity (SIM / RUIM) module), other memory, or any combination thereof. The storage medium 721 may allow the UE 700 to access computer executable instructions, applications, etc. stored on a temporary or non-temporary storage medium to unload data or upload data. An article of manufacture such as utilizing a communication system may be tangibly embodied in the storage medium 721, which may include a device-readable medium.

[0166] exist Figure 7In the embodiment of the present invention, the processing circuit 701 may be configured to communicate with the network 743b using the communication subsystem 731. The network 743a and the network 743b may be the same network or different networks. The communication subsystem 731 may be configured to include one or more transceivers for communicating with the network 743b. For example, the communication subsystem 731 may be configured to include one or more transceivers for communicating with one or more remote transceivers of another device (e.g., another WD, UE or base station of a radio access network (RAN)) capable of wireless communication according to one or more communication protocols (e.g., IEEE 802.11, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, etc.). Each transceiver may include a transmitter 733 and / or a receiver 735 to respectively implement a transmitter or receiver function (e.g., frequency allocation, etc.) suitable for a RAN link. In addition, the transmitter 733 and the receiver 735 of each transceiver may share circuit components, software or firmware, or may be implemented separately instead.

[0167] In the illustrated embodiment, the communication functions of the communication subsystem 731 may include data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near-field communication, location-based communication (GPS) such as using a global positioning system to determine the location, another similar communication function, or any combination thereof. For example, the communication subsystem 731 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. The network 743b may include a wired and / or wireless network, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a telecommunications network, another similar network, or any combination thereof. For example, the network 743b may be a cellular network, a Wi-Fi network, and / or a near-field network. The power supply 713 may be configured to provide alternating current (AC) or direct current (DC) power to the components of the UE 700.

[0168] The features, benefits and / or functions described herein may be implemented in one of the components of UE 700, or may be divided among multiple components of UE 700. In addition, the features, benefits and / or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, the communication subsystem 731 may be configured to include any component described herein. In addition, the processing circuit 701 may be configured to communicate with any such component on the bus 702. In another example, any such component may be represented by a program instruction stored in a memory, which performs the corresponding function described herein when executed by the processing circuit 701. In another example, the function of any such component may be divided between the processing circuit 701 and the communication subsystem 731. In another example, the non-computationally intensive functions of any such component may be implemented with software or firmware, while the computationally intensive functions may be implemented with hardware.

[0169] Figure 8 is a schematic block diagram illustrating a virtualized environment 800 in which functions implemented by some embodiments may be virtualized. In the present context, virtualization means creating a virtual version of an apparatus or device, which may include a virtualized hardware platform, storage devices, and networking resources. As used herein, virtualization may be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or a device (e.g., a UE, a wireless device, or any other type of communication device) or a component thereof, and relates to an implementation in which at least a portion of the functions are implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines, or containers executed on one or more physical processing nodes in one or more networks).

[0170] In some embodiments, some or all of the functionality described herein may be implemented as virtual components performed by one or more virtual machines implemented in one or more virtual environments 800 hosted by one or more hardware nodes 830. Furthermore, in embodiments where the virtual nodes are not radio access nodes or do not require radio connectivity (e.g., core network nodes), the network nodes may be fully virtualized.

[0171] These functions may be implemented by one or more applications 820 (which may alternatively be referred to as software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operable to implement certain features, functions, and / or benefits of some embodiments disclosed herein. The applications 820 run in a virtualized environment 800, which provides hardware 830 including processing circuitry 860 and memory 890. The memory 890 contains instructions 895 executable by the processing circuitry 860, whereby the applications 820 are operable to provide one or more features, benefits, and / or functions disclosed herein.

[0172] The virtualization environment 800 includes a general or special network hardware device 830, which includes a set of one or more processors or processing circuits 860, which can be commercial off-the-shelf (COTS) processors, application-specific integrated circuits (ASICs), or any other type of processing circuit including digital or analog hardware components or special processors. Each hardware device may include a memory 890-1, which can be a non-persistent memory for temporarily storing instructions 895 or software executed by the processing circuit 860. Each hardware device may include one or more network interface controllers (NICs) 870 (also known as network interface cards), which include a physical network interface 880. Each hardware device may also include a non-transitory persistent machine-readable storage medium 890-2 in which software 895 and / or instructions executable by the processing circuit 860 are stored. The software 895 may include any type of software including software for instantiating one or more virtualization layers 850 (also known as hypervisors), software for executing virtual machines 840, and software that allows it to perform functions, features, and / or benefits related to some embodiments described herein.

[0173] The virtual machine 840 includes virtual processing, virtual memory, virtual network or interface, and virtual storage, and may be run by a corresponding virtualization layer 850 or hypervisor. Different embodiments of instances of the virtual device 820 may be implemented on one or more virtual machines 840 and may be implemented in different ways.

[0174] During operation, processing circuitry 860 executes software 895 to instantiate a hypervisor or virtualization layer 850, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 850 may present to virtual machines 840 a virtual operating platform that appears to be networked hardware.

[0175] like Figure 8 As shown, hardware 830 can be an independent network node with common or specific components. Hardware 830 can include antenna 8225, and some functions can be implemented via virtualization. Alternatively, hardware 830 can be part of a larger hardware cluster (e.g., such as in a data center or customer premises equipment (CPE)), where many hardware nodes work together and are managed by management and orchestration (MANO) 8100, which, among other items, oversees the life cycle management of application 820.

[0176] In some contexts, virtualization of hardware is referred to as network function virtualization (NFV). NFV can be used to consolidate many network equipment types onto industry-standard high-volume server hardware, physical switches, and physical storage devices that can be located in data centers and customer premises equipment.

[0177] In the context of NFV, a virtual machine 840 may be a software implementation of a physical machine that runs a program as if the program were executed on a physical, non-virtual machine. Each virtual machine 840 and the portion of the hardware 830 that executes the virtual machine (hardware dedicated to the virtual machine and / or hardware shared by the virtual machine with other virtual machines 840) form a separate virtual network element (VNE).

[0178] Still in the context of NFV, a virtual network function (VNF) is responsible for handling specific network functions running in one or more virtual machines 840 on top of the hardware networking infrastructure 830 and corresponds to Figure 8 Application 820.

[0179] In some embodiments, one or more radio units 8200, each including one or more transmitters 8220 and one or more receivers 8210, may be coupled to one or more antennas 8225. The radio unit 8200 may communicate directly with the hardware node 830 via one or more appropriate network interfaces, and may be used in combination with virtual components to provide a virtual node with radio capabilities, such as a radio access node or base station.

[0180] In some embodiments, some signaling may be implemented using a control system 8230 , which may alternatively be used for communications between the hardware node 830 and the radio unit 8200 .

[0181] refer to Fig. 9According to an embodiment, a communication system includes a telecommunication network 910 such as a 3GPP type cellular network, which includes an access network 911 such as a radio access network and a core network 914. The access network 911 includes a plurality of base stations 912a, 912b, 912c (e.g., NB, eNB, gNB) or other types of wireless access points, each defining a corresponding coverage area 913a, 913b, 913c. Each base station 912a, 912b, 912c may be connected to the core network 914 via a wired or wireless connection 915. A first UE 991 located in the coverage area 913c is configured to be wirelessly connected to or paged by the corresponding base station 912c. A second UE 992 in the coverage area 913a may be wirelessly connected to the corresponding base station 912a. Although multiple UEs 991, 992 are shown in this example, the disclosed embodiments are equally applicable to situations where a single UE is in the coverage area or a single UE is connected to the corresponding base station 912.

[0182] The telecommunications network 910 itself is connected to a host computer 930, which may be embodied in the hardware and / or software of a stand-alone server, a cloud-implemented server, a distributed server, or as processing resources in a server farm. The host computer 930 may be under the ownership or control of a service provider, or may be operated by or on behalf of a service provider. The connections 921 and 922 between the telecommunications network 910 and the host computer 930 may extend directly from the core network 914 to the host computer 930, or may be via an optional intermediate network 920. The intermediate network 920 may be one of a public, private, or managed network, or a combination of more than one thereof; the intermediate network 920 (if any) may be a backbone network or the Internet; in particular, the intermediate network 920 may include two or more sub-networks (not shown).

[0183] Overall, Fig. 9The communication system of the present invention realizes the connectivity between the connected UE 991, 992 and the host computer 930. The connectivity can be described as an over-the-top (OTT) connection 950. The host computer 930 and the connected UE 991, 992 are configured to use the access network 911, the core network 914, any intermediate network 920 and possible other infrastructure (not shown) as intermediaries to transmit data and / or signaling via the OTT connection 950. The OTT connection 950 can be transparent in the sense that the participating communication devices through which the OTT connection 950 passes do not know the routes of the uplink and downlink communications. For example, the base station 912 may not be notified or need not be notified of the past routes of the incoming downlink communications with data originating from the host computer 930 to be forwarded (e.g., handed over) to the connected UE 991. Similarly, the base station 912 does not need to know the future routes of the outgoing uplink communications from the UE 991 to the host computer 930.

[0184] Now refer to Fig.10 1010 is a system for performing a communication of a plurality of communication devices of the communication system 1000. The system 1010 includes a processor 1018, which may have a storage and / or processing capability. In particular, the processing circuit 1018 may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these items (not shown) suitable for executing instructions. The host computer 1010 also includes software 1011, which is stored in the host computer 1010 or can be accessed by the host computer 1010 and can be executed by the processing circuit 1018. The software 1011 includes a host application 1012. The host application 1012 is operable to provide services to a remote user, such as a UE 1030 connected via an OTT connection 1050 terminating at the UE 1030 and the host computer 1010. In providing services to the remote user, the host application 1012 may provide user data sent using the OTT connection 1050.

[0185] The communication system 1000 also includes a base station 1020 provided in the telecommunication system, and the base station 1020 includes hardware 1025 that enables it to communicate with the host computer 1010 and the UE 1030. The hardware 1025 may include a communication interface 1026 for establishing and maintaining a wired or wireless connection with different communication devices of the communication system 1000, and a communication interface 1026 for establishing and maintaining a connection with a network located in a coverage area ( Fig.10The communication interface 1026 may be configured to facilitate a connection 1060 with the host computer 1010. The connection 1060 may be direct, or the connection 1060 may be through a core network (eg, a wireless network) of the telecommunications system. Fig.10 1020) and / or through one or more intermediate networks external to the telecommunications system. In the illustrated embodiment, the hardware 1025 of the base station 1020 also includes processing circuitry 1028, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these items (not shown) suitable for executing instructions. The base station 1020 also has software 1021 stored internally or accessible via an external connection.

[0186] The communication system 1000 also includes the UE 1030 already mentioned. The hardware 1035 of the UE 1030 may include a radio interface 1037, which is configured to establish and maintain a wireless connection 1070 with a base station serving the coverage area where the UE 1030 is currently located. The hardware 1035 of the UE 1030 also includes a processing circuit 1038, which may include one or more programmable processors, application-specific integrated circuits, field programmable gate arrays, or a combination of these items (not shown) suitable for executing instructions. The UE 1030 also includes software 1031 stored in the UE 1030 or accessible by the UE 1030 and executable by the processing circuit 1038. The software 1031 includes a client application 1032. The client application 1032 is operable to provide services to human or non-human users via the UE 1030 with the support of the host computer 1010. In the host computer 1010, the executing host application 1012 can communicate with the executing client application 1032 via the OTT connection 1050 terminated at the UE 1030 and the host computer 1010. In providing services to users, the client application 1032 can receive request data from the host application 1012 and provide user data in response to the request data. The OTT connection 1050 can transmit both the request data and the user data. The client application 1032 can interact with the user to generate user data provided by the user.

[0187] Notice, Fig.10 The host computer 1010, base station 1020 and UE 1030 shown can be respectively Fig. 9 The host computer 930, one of the base stations 912a, 912b, 912c, and one of the UEs 991, 992 may be similar or identical. That is, the internal working principles of these entities may be as follows: Fig.10 shown, and independently, the surrounding network topology can be Fig. 9 The surrounding network topology.

[0188] exist Fig.10 In the figure, the OTT connection 1050 has been abstractly drawn to illustrate the communication between the host computer 1010 and the UE 1030 via the base station 1020, without explicit reference to any intermediate devices and the precise routing of the messages via these devices. The network infrastructure can determine the routing, and the network infrastructure can be configured to hide the routing from the UE 1030 or from the service provider operating the host computer 1010, or both. When the OTT connection 1050 is active, the network infrastructure can further make a decision according to which the network infrastructure dynamically changes the routing (e.g., based on load balancing considerations or reconfiguration of the network).

[0189] The wireless connection 1070 between the UE 1030 and the base station 1020 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments may improve the performance of OTT services provided to the UE 1030 using the OTT connection 1050 (where the wireless connection 1070 forms the last segment). More specifically, the teachings of these embodiments may improve the operation and performance of a UE that accesses an OTT service using the OTT connection 1050.

[0190] The measurement process may be provided for the purpose of monitoring data rates, delays, and other factors on which one or more embodiments are improved. In response to changes in the measurement results, there may also be an optional network function for reconfiguring the OTT connection 1050 between the host computer 1010 and the UE 1030. The measurement process and / or network function for reconfiguring the OTT connection 1050 may be implemented in the software 1011 and hardware 1015 of the host computer 1010 or in the software 1031 and hardware 1035 of the UE 1030, or in both. In an embodiment, a sensor (not shown) may be deployed in a communication device through which the OTT connection 1050 passes or associated with such a communication device; the sensor may participate in the measurement process by providing the value of the monitored quantity of the above example or providing the value of other physical quantities from which the software 1011, 1031 can calculate or estimate the monitored quantity. The reconfiguration of the OTT connection 1050 may include message formats, retransmission settings, preferred routes, etc. The reconfiguration does not need to affect the base station 1020, and it may be unknown or imperceptible to the base station 1020. Such processes and functions may be known and practiced in the art. In certain embodiments, the measurements may involve proprietary UE signaling that facilitates host computer 1010 measurements of throughput, propagation time, latency, etc. The measurements may be achieved because software 1011 and 1031 causes messages, particularly empty or "dummy" messages, to be sent using OTT connection 1050 during its monitoring of propagation time, errors, etc.

[0191] Fig.11is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Fig. 9 and Fig.10 In order to simplify the present disclosure, only the host computer, base station and UE described in this section are included. Fig.11 Reference is made to the accompanying drawings of . In step 1110, the host computer provides user data. In sub-step 1111 of step 1110 (which may be optional), the host computer provides the user data by executing a host application. In step 1120, the host computer initiates a transmission to the UE carrying the user data. In step 1130 (which may be optional), in accordance with the teachings of the embodiments described throughout the present disclosure, the base station sends the user data carried in the transmission initiated by the host computer to the UE. In step 1140 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0192] Fig.12 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Fig. 9 and Fig.10 In order to simplify the present disclosure, only the host computer, base station and UE described in this section are included. Fig.12 . In step 1210 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides the user data by executing a host application. In step 1220, the host computer initiates a transmission carrying the user data to the UE. According to the teachings of the embodiments described throughout the present disclosure, the transmission may be through a base station. In step 1230 (which may be optional), the UE receives the user data carried in the transmission.

[0193] Fig.13 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Fig. 9 and Fig.10 In order to simplify the present disclosure, only the host computer, base station and UE described in this section are included. Fig.13. In step 1310 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 1320, the UE provides user data. In sub-step 1321 (which may be optional) of step 1320, the UE provides user data by executing a client application. In sub-step 1311 (which may be optional) of step 1310, the UE executes a client application, which provides user data in response to the received input data provided by the host computer. When providing user data, the executed client application may further consider user input received from the user. Regardless of the specific manner of providing user data, the UE initiates transmission of user data to the host computer in sub-step 1330 (which may be optional). In step 1340 of the method, in accordance with the teachings of the embodiments described throughout the present disclosure, the host computer receives user data sent from the UE.

[0194] Fig.14 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Fig. 9 and Fig.10 In order to simplify the present disclosure, only the host computer, base station and UE described in this section are included. Fig.14 In step 1410 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step 1420 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 1430 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0195] Any appropriate 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 these functional units. These functional units may be implemented via a processing circuit, which may include one or more microprocessors or microcontrollers and other digital hardware that may include a digital signal processor (DSP), dedicated digital logic, etc. The processing circuit may be configured to execute program codes stored in a memory, which 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 implementations, 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.

[0196] abbreviation

[0197] At least some of the following abbreviations may be used in the present disclosure. If there is an inconsistency between the abbreviations, the above usage should be preferred. If listed multiple times below, the first listing should take precedence over subsequent listings.

[0198] 1x RTT CDMA2000 1x Radio Transmission Technology

[0199] 3GPP Third Generation Partnership Project

[0200] 5G Fifth Generation

[0201] ABS Almost Blank Subframe

[0202] ARQ Automatic Repeat Request

[0203] AWGN Additive White Gaussian Noise

[0204] BCCH Broadcast Control Channel

[0205] BCH Broadcast Channel

[0206] CA Carrier Aggregation

[0207] CC Carrier Component

[0208] CCCH SDU Common Control Channel SDU

[0209] CDMA Code Division Multiple Access

[0210] CGI Cell Global Identifier

[0211] CIR Channel Impulse Response

[0212] CP Cyclic Prefix

[0213] CPICH Common Pilot Channel

[0214] CPICH Ec / No CPICH received energy per chip divided by the power density in the frequency band

[0215] CQI Channel Quality Information

[0216] C-RNTI Cell RNTI

[0217] CSI Channel State Information

[0218] DCCH Dedicated Control Channel

[0219] DL Downlink

[0220] DM Demodulation

[0221] DMRS Demodulation Reference Signal

[0222] DRX Discontinuous Reception

[0223] DTX Discontinuous Transmission

[0224] DTCH Dedicated Traffic Channel

[0225] DUT Device Under Test

[0226] E-CID Enhanced Cell ID (positioning method)

[0227] E-SMLC Evolved Serving Mobile Location Center

[0228] ECGI Evolved CGI

[0229] eNB E-UTRAN Node B

[0230] ePDCCH Enhanced Physical Downlink Control Channel

[0231] E-SMLC Evolved Serving Mobile Location Center

[0232] E-UTRA Evolved UTRA

[0233] E-UTRAN Evolved UTRAN

[0234] FDD Frequency Division Duplex

[0235] FFS needs further study

[0236] GERAN GSM EDGE Radio Access Network

[0237] Base stations in gNB NR

[0238] GNSS Global Navigation Satellite System

[0239] GSM Global System for Mobile Communications

[0240] HARQ Hybrid Automatic Repeat Request

[0241] HO Handover

[0242] HSPA High Speed ​​Packet Access

[0243] HRPD High Rate Packet Data

[0244] LOS Line of Sight

[0245] LPP LTE Positioning Protocol

[0246] LTE Long Term Evolution

[0247] MAC Media Access Control

[0248] MBMS Multimedia Broadcast Multicast Service

[0249] MBSFN Multimedia Broadcast Multicast Service Single Frequency Network

[0250] MBSFN ABS MBSFN Almost Blank Subframe

[0251] MDT Minimized Drive Test

[0252] MIB Master Information Block

[0253] MME Mobility Management Entity

[0254] MSC Mobile Switching Center

[0255] NPDCCH Narrowband Physical Downlink Control Channel

[0256] NR New Radio

[0257] OCNG OFDMA Channel Noise Generator

[0258] OFDM Orthogonal Frequency Division Multiplexing

[0259] OFDMA Orthogonal Frequency Division Multiple Access

[0260] OSS Operation Support System

[0261] OTDOA observed time difference of arrival

[0262] O&M Operation and Maintenance

[0263] PBCH Physical Broadcast Channel

[0264] P-CCPCH Primary Common Control Physical Channel

[0265] PCell Primary Cell

[0266] PCFICH Physical Control Format Indicator Channel

[0267] PDCCH Physical Downlink Control Channel

[0268] PDP Profile Delay Profile

[0269] PDSCH Physical Downlink Shared Channel

[0270] PGW Packet Gateway

[0271] PHICH Physical Hybrid ARQ Indicator Channel

[0272] PLMN Public Land Mobile Network

[0273] PMI Precoder Matrix Indicator

[0274] PRACH Physical Random Access Channel

[0275] PRS Positioning Reference Signal

[0276] PSS Primary Synchronization Signal

[0277] PUCCH Physical Uplink Control Channel

[0278] PUSCH Physical Uplink Shared Channel

[0279] RACH Random Access Channel

[0280] QAM Quadrature Amplitude Modulation

[0281] RAN Radio Access Network

[0282] RAT Radio Access Technology

[0283] RLM Radio Link Management

[0284] RNC Radio Network Controller

[0285] RNTI Radio Network Temporary Identifier

[0286] RRC Radio Resource Control

[0287] RRM Radio Resource Management

[0288] RS reference signal

[0289] RSCP Received Signal Code Power

[0290] RSRP Reference Symbol Received Power or Reference Signal Received Power

[0291] RSRQ Reference Signal Received Quality or Reference Symbol Received Quality

[0292] RSSI Received Signal Strength Indicator

[0293] RSTD Reference Signal Time Difference

[0294] SCH Synchronization Channel

[0295] SCell Secondary Cell

[0296] SDU Service Data Unit

[0297] SFN System Frame Number

[0298] SGW Service Gateway

[0299] SI System Information

[0300] SIB System Information Block

[0301] SNR Signal to Noise Ratio

[0302] SON Self-Optimizing Network

[0303] SS Sync Signal

[0304] SSS Secondary synchronization signal

[0305] TDD Time Division Duplex

[0306] TDOA Time Difference of Arrival

[0307] TOA Time of Arrival

[0308] TSS third synchronization signal

[0309] TTI Transmission Time Interval

[0310] UE User Equipment

[0311] UL Uplink

[0312] UMTS Universal Mobile Telecommunications System

[0313] USIM Universal Subscriber Identity Module

[0314] UTDOA Uplink Time Difference of Arrival

[0315] UTRA Universal Terrestrial Radio Access

[0316] UTRAN Universal Terrestrial Radio Access Network

[0317] WCDMA Wideband CDMA

[0318] WLAN Wide Area Network

Claims

1. A method performed by a wireless device for receiving an aperiodic CSI-RS on a first carrier, wherein: The first carrier uses a first OFDM parameter set, and the method includes: Receiving a downlink control information DCI message carried by a physical downlink control channel PDCCH on a second carrier, wherein the second carrier uses a second OFDM parameter set; Obtaining an aperiodic CSI-RS time slot offset from the DCI message; Determining a reference time slot in the first OFDM parameter set; determining a time slot of the aperiodic CSI-RS based on the reference time slot and the aperiodic CSI-RS time slot offset; and The aperiodic CSI-RS is received in the determined time slot, or an associated channel state information CSI report is sent in the determined time slot.

2. The method according to claim 1, wherein: The first OFDM parameter set is different from the second OFDM parameter set.

3. The method according to claim 1, wherein: The OFDM numerology set is characterized by its subcarrier spacing.

4. The method according to claim 1, wherein: The time slot of the aperiodic CSI-RS is determined as a time slot that is X time slots later than the reference time slot, where X is the aperiodic CSI-RS time slot offset.

5. The method according to claim 1, wherein: Determining the time slot of the aperiodic CSI-RS based on the reference time slot and the aperiodic CSI-RS time slot offset includes: calculating the time slot in: n is the time slot that triggers the DCI in the parameter set of PDCCH, X is the CSI-RS triggering offset in the CSI-RS parameter set according to the higher layer parameter aperiodicTriggeringOffset, and μ CSIRS and μ PDCCH They are the subcarrier spacing configurations used for CSI-RS and PDCCH respectively.

6. A user equipment UE, configured to receive a non-periodic CSI-RS on a first carrier, wherein: The first carrier uses a first OFDM parameter set, and the UE includes: an antenna configured to transmit and receive wireless signals; a radio front end circuit connected to the antenna and to the processing circuit and configured to condition signals transmitted between the antenna and the processing circuit; The processing circuit is configured to perform operations comprising: Receiving a downlink control information DCI message carried by a physical downlink control channel PDCCH on a second carrier, wherein the second carrier uses a second OFDM parameter set; Obtaining an aperiodic CSI-RS time slot offset from the DCI message; Determining, on the first carrier, a reference time slot in the first OFDM parameter set; determining a time slot of the aperiodic CSI-RS based on the reference time slot and the aperiodic CSI-RS time slot offset; and Receiving the aperiodic CSI-RS in the determined time slot of the aperiodic CSI-RS, or sending an associated channel state information CSI report in the determined time slot; and A battery is connected to the processing circuit and is configured to provide power to the UE.

7. The user equipment according to claim 6, wherein: The first OFDM parameter set is different from the second OFDM parameter set.

8. The user equipment according to claim 6, wherein: The OFDM numerology set is characterized by its subcarrier spacing.

9. The user equipment according to claim 6, wherein: The time slot of the aperiodic CSI-RS is determined as a time slot that is X time slots later than the reference time slot, where X is the aperiodic CSI-RS time slot offset.

10. The user equipment according to claim 6, wherein: Determining the time slot of the aperiodic CSI-RS based on the reference time slot and the aperiodic CSI-RS time slot offset includes: calculating the time slot in: n is the time slot that triggers the DCI in the parameter set of PDCCH, X is the CSI-RS triggering offset in the CSI-RS parameter set according to the higher layer parameter aperiodicTriggeringOffset, and μCSIRS and μPDCCH They are the subcarrier spacing configurations used for CSI-RS and PDCCH respectively.

11. A method for transmitting an aperiodic CSI-RS on a first carrier, performed by a base station, the method comprising: Sending a downlink control information DCI message carried by a physical downlink control channel PDCCH on a second carrier, wherein the DCI message includes an aperiodic CSI-RS time slot offset; The aperiodic CSI-RS is transmitted in a time slot of the aperiodic CSI-RS determined according to the aperiodic CSI-RS time slot offset and a reference time slot in a first OFDM parameter set of the first carrier.

12. The method according to claim 11, wherein: The second carrier uses a second set of OFDM parameters that is different from the first set of OFDM parameters.

13. The method according to claim 12, wherein: The first OFDM parameter set and the second OFDM parameter set are characterized by corresponding subcarrier spacing.

14. The method according to claim 11, further comprising: A channel state information (CSI) report is received from the wireless device based on the measurement of the received aperiodic CSI-RS.

15. The method according to claim 11, wherein: The time slot of the aperiodic CSI-RS is determined as a time slot that is X time slots later than the reference time slot, where X is the aperiodic CSI-RS time slot offset.

Images