WO2019083426A1 - Signalisation de configuration de signal de référence de démodulation de liaison montante - Google Patents

Signalisation de configuration de signal de référence de démodulation de liaison montante

Info

Publication number
WO2019083426A1
WO2019083426A1 PCT/SE2018/050678 SE2018050678W WO2019083426A1 WO 2019083426 A1 WO2019083426 A1 WO 2019083426A1 SE 2018050678 W SE2018050678 W SE 2018050678W WO 2019083426 A1 WO2019083426 A1 WO 2019083426A1
Authority
WO
WIPO (PCT)
Prior art keywords
bit field
field value
uplink
dmrs
network node
Prior art date
Application number
PCT/SE2018/050678
Other languages
English (en)
Inventor
Jingya Li
Florent Munier
Laetitia Falconetti
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2019083426A1 publication Critical patent/WO2019083426A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
    • H04L5/0051—Allocation of pilot signals, i.e. of signals known to the receiver of dedicated pilots, i.e. pilots destined for a single user or terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H04L5/0094—Indication of how sub-channels of the path are allocated

Definitions

  • Embodiments of the present disclosure are directed to wireless communications and, more particularly, to signaling of uplink demodulation reference signal configuration.
  • data transmissions in both downlink e.g., from a network node or eNB to a user device or UE
  • uplink e.g., from a user device or UE to a network node or eNB
  • LTE uses Orthogonal Frequency Division Multiplexing (OFDM) in the downlink and Single Carrier OFDM (SC-OFDM) in the uplink.
  • OFDM Orthogonal Frequency Division Multiplexing
  • SC-OFDM Single Carrier OFDM
  • the basic LTE downlink physical resource can thus be seen as a time-frequency grid as illustrated in FIGURE 2, where each resource element corresponds to one OFDM subcarrier during one OFDM symbol interval.
  • resource allocation in LTE is typically described in terms of resource blocks (RBs), where a resource block corresponds to one slot (0.5 ms) in the time domain and 12 contiguous subcarriers in the frequency domain. Resource blocks are numbered in the frequency domain, starting with 0 from one end of the system bandwidth.
  • Mg is the number resource blocks (RBs) contained in the uplink system bandwidth
  • Mjf 12
  • Mjf 12
  • Downlink data transmissions from an eNB to a UE is typically (but not
  • the base station transmits control information about to which terminals data is transmitted and upon which resource blocks the data is transmitted, in the current downlink subframe.
  • This control signaling is typically transmitted in the first 1, 2, 3 or 4 OFDM symbols in each subframe.
  • a downlink system with 3 OFDM symbols as control is illustrated in FIGURE 4.
  • uplink transmissions from a UE to an eNB are also typically (but not exclusively) dynamically scheduled through the downlink control channel.
  • a downlink or an uplink physical channel corresponds to a set of resource elements carrying information that may originate from higher layers, while a downlink or an uplink physical signal is used by the physical layer but does not carry information originating from higher layers.
  • EPDCCH Physical Downlink Control Channel
  • DMRS o DeModulation Reference Signal
  • CSI-RS o Channel State Information Reference Signals
  • PDSCH is used mainly for carrying user traffic data and higher layer messages in the downlink and is transmitted in a DL subframe outside of the control region as shown in FIGURE 4.
  • Both PDCCH and EPDCCH are used to carry Downlink Control Information (DCI) such as PRB allocation, modulation level and coding scheme (MCS), precoder used at the transmitter, etc.
  • DCI Downlink Control Information
  • MCS modulation level and coding scheme
  • PDCCH is transmitted in the first one to four OFDM symbols in a DL subframe, i.e. the control region, while EPDCCH is transmitted in the same region as PDSCH.
  • DMRS DeModulation Reference Signal
  • DMRS DeModulation Reference Signal
  • the PUSCH is used to carry uplink data or/and uplink control information from the UE to the eNodeB.
  • the PUCCH is used to carry uplink control information from the UE to the eNodeB.
  • DMRS for PUSCH is used to carry uplink control information from the UE to the eNodeB.
  • DMRS for PUSCH is used for PUSCH demodulations. More specifically, the DMRS is used by the network node or eNB for uplink channel estimation in the RBs scheduled for the associated PUSCH. DMRS is time multiplexed with associated PUSCH and occupies the same RBs as the PUSCH. The DMRS is transmitted on the REs of the 3rd SC-OFDM symbol of each slot of a subframe as shown in FIGURE 5, where only one RB is shown.
  • DMRS occupies all the subcarriers in the 4th symbols of each slot as shown in FIGURE 5.
  • RPF repetition factor
  • PA Power Amplifier
  • n ⁇ RS is configured by higher layers
  • n ⁇ ' [RS1 is given by the cyclic shift for DMRS field in most recent uplink-related DCI for the transport block associated with the corresponding PUSCH transmission where the value of is given in Table 5.5.2.1.1-1 of TS36.211, which is copied in Table 3.
  • n PN (n s ) is a cell specific number generated pseudo- randomly in a slot by slot basis.
  • 3 ⁇ 4 E (0,1, is the slot index within a subframe.
  • t£?( ) is a reference signal sequence and is defined by a cyclic shift a of a base sequence r u v (n) according to:
  • r uv (0),...,r uv (M s ⁇ s -1) depends on the sequence length M s .
  • r u v (n) is generated through cyclic extension of a Zadoff-Chu (ZC) sequence X 3 ⁇ 4 .(HS) as follows:
  • r UiV (n) x q (nmodN ⁇ ), 0 ⁇ n ⁇ M, sc where the q' root Zadoff-Chu sequence is defined by: . 7zqm(m+l)
  • the length N ⁇ ? of the Zadoff-Chu sequence is given by the largest prime number such that Nfc ⁇ M S ⁇ S .
  • the base sequences have a constant amplitude over frequency and also maintain the zero auto -correlation cyclic shift orthogonality property of the Zadoff-Chu sequences, which allows generating multiple orthogonal sequences by using different cyclic shifts on a single base sequence.
  • extension not truncation, in general provides better CM for 3 and more RBs.
  • at least 30 base sequences can be generated this way.
  • base sequences for one and two RBs were obtained by computer searches. Only QPSK based sequences were selected to reduce memory size for storage and computational complexity.
  • Table 1 Definition of ⁇ ( ⁇ ) for M ⁇ ⁇ N ⁇ in LTE.
  • a phase shift of a reference signal sequence does not change its PAPR or CM. Also, the magnitude of a reference signal sequence's autocorrelation or cross correlation with other reference signal sequences does not change if the reference signal is pi
  • a reference signal u v u v is equivalent to u v , where ' is a real number.
  • a given reference sequence ru v ⁇ n -* with sequence number u (for example, corresponding to a row in Table 1, Table 2) will have a given value of PAPR or CM.
  • a sequence u ' v with sequence number Ul and a sequence 112 v with sequence number u 2 will have some cross-correlation C " , ' u ⁇ ' 1 ' ⁇ , where and are correlation lags.
  • Good reference signal sequences should have low PAPR or CM and low cross-correlation.
  • the CM for a signal, r ⁇ t). with 3.84MHz nominal bandwidth is defined according to:
  • up to 8 orthogonal DMRS sequences are available. These sequences can be used to support uplink MIMO transmission with 4 layers (which is the maximum number layers that are supported in uplink in LTE), each assigned with one cyclic shift, or uplii
  • MU-MIMO MIMO for up to 8 UEs, each with one MIMO layer.
  • UEs with partially overlapped PUSCH bandwidth can be paired for MU-MIMO.
  • IFDMA Interleaved Frequency Division Multiplexing
  • RPF repetition factor 2
  • uplink DMRS is transmitted on only half of the subcarriers, either even numbered or odd numbered subcarriers.
  • FIGURE 6 An example with 2RBs is shown in FIGURE 6, where a DMRS for one UE can be assigned on the DMRS REs at even numbered subcarriers while a DMRS for another UE can be assigned on the other half of subcarriers, i.e., DMRS REs at odd numbered subcarriers. Since the two DMRS sequences are transmitted on different subcarriers, they are orthogonal to each other. In this example, the length of each of the two DMRS sequences are transmitted on different subcarriers, they are orthogonal to each other. In this example, the length of each of the two DMRS sequences are transmitted on different subcarriers, they are orthogonal to each other. In this example, the length of each of the two DMRS sequences are transmitted on different subcarriers, they are orthogonal to each other. In this example, the length of each of the two DMRS sequences are transmitted on different subcarriers, they are orthogonal to each other. In this example, the length
  • DMRS sequence is 12 and thus the existing length 12 (i.e. base sequence u v can be used.
  • An uplink grant for a 1ms TTI can be sent using either DCI format 0 or DCI format 4, depending on the uplink transmission mode configured. For UEs supporting uplink MIMO transmission, DCI format 4 is used. Otherwise, DCI format 0 is used.
  • DCI format 4 is used for UEs supporting uplink MIMO transmission. Otherwise, DCI format 0 is used.
  • MIMO is supported in the uplink, a separate DMRS sequence is needed for each MIMO layer. Up to 4 layers are supported in uplink MIMO in LTE, thus up to four DMRS sequences are needed.
  • the cyclic shifts and OCC codes are dynamically signaled in UL DCI through a Cyclic Shift Field of 3 bits. This field is used to indicate a cyclic shift n (2)
  • Table 3 is used for UL DMRS configuration, if the higher-layer-parameter ul-DMRS- IFDMA is set and the Cyclic Shift Field mapping table for DMRS bit field is present in the most recent uplink-related DCI, and the Cyclic Shift Field mapping table for DMRS bit field indicates the use of Table 4.
  • Packet data latency is one of the performance metrics that vendors, operators, and end- users (via speed test applications) regularly measures. Latency measurements are done in all phases of a radio access network system lifetime, when verifying a new software release or system component, when deploying a system and when the system is in commercial operation.
  • LTE Long Term Evolution
  • Packet data latency is important not only for the perceived responsiveness of the system; it is also a parameter that indirectly influences the throughput of the system.
  • HTTP/TCP is the dominating application and transport layer protocol suite used on the internet today.
  • the typical size of HTTP based transactions over the internet are in the range of a few 10's of kilobytes up to 1 megabyte.
  • the TCP slow start period is a significant part of the total transport period of the packet stream.
  • the performance is latency limited.
  • improved latency improves the average throughput, for this type of TCP based data transactions.
  • Radio resource efficiency could be positively impacted by latency reductions.
  • Lower packet data latency could increase the number of transmissions possible within a certain delay bound; hence higher Block Error Rate (BLER) targets could be used for the data transmissions freeing up radio resources potentially improving the capacity of the system.
  • BLER Block Error Rate
  • TTI transmission time interval
  • a TTI corresponds to one subframe (SF) of length 1 millisecond.
  • One such 1 ms TTI is constructed by using 14 OFDM or SC-FDMA symbols in the case of normal cyclic prefix and 12 OFDM or SC-FDMA symbols in the case of extended cyclic prefix.
  • SF subframe
  • One such 1 ms TTI is constructed by using 14 OFDM or SC-FDMA symbols in the case of normal cyclic prefix and 12 OFDM or SC-FDMA symbols in the case of extended cyclic prefix.
  • short TTI or sTTI such as a slot or a few symbols.
  • An sTTI may have any duration in time and comprise resources on a number of OFDM or SC-FDMA symbols within a 1 ms SF.
  • the duration of the uplink short TTI is 0.5 ms, i.e., seven SC-FDMA symbols for the case with normal cyclic prefix.
  • the durations of the uplink short TTIs within a subframe are of 2 or 3 symbols.
  • the "R" in FIGURES 7 and 8 indicate the DMRS symbols
  • S indicate the SRS symbols.
  • short PDSCH sPDSCH
  • sPUSCH short PUSCH
  • At least 2 contiguous TTIs can be shared/multiplexed.
  • DMRS sharing When the same UE is scheduled on consecutive sTTIs, an effective way to reduce the overhead of reference signals for UL data transmission is DMRS sharing. This means that the DMRS is not transmitted in each sTTI. Instead, a certain periodicity in terms o
  • FIGURE 9 illustrates an example of DMRS sharing for the case of a 2/3 -symbol sTTI configuration in an uplink subframe.
  • DMRS transmitted in sTTI 0 and sTTI 3 are used for the channel estimation for sTTI 1 and sTTI 4, respectively.
  • DMRS multiplexing refers to multiple UEs that may share the same SC- FDMA symbol for transmission of the DMRS but have separate SC-FDMA symbols for the data.
  • FIGURE 10a and 10b illustrate examples of DMRS multiplexing for two different 2/3- symbol sTTI configurations within an uplink subframe.
  • sTTI 1 and 2 in FIGURE 10a the DMRS from different UEs are multiplexed in the same SC-FDMA symbol marked with "R.”
  • sTTI 3 and 4 in FIGURE 10b the DMRS from different UEs are multiplexed in the same SC-FDMA symbol marked with "R.”
  • the orthogonality between the multiplexed DMRS from different UEs needs to be ensured to guarantee good channel estimation and successful data decoding.
  • the IFDMA-based DMRS multiplexing method discussed above for MU-MIMO transmission on PUSCH can also be used for supporting DMRS multiplexing on sPUSCH with partially overlapped frequency allocations.
  • Different from DMRS multiplexing for MU- MIMO transmissions on PUSCH in most cases, there is at most one DMRS symbol per sPUSCH transmission. This implies that OCC cannot be used for DMRS multiplexing when considering sPUSCH transmissions.
  • New signaling method needs to be designed to support IFDMA-based DMRS multiplexing for sPUSCH transmissions with partially overlapped frequency allocation.
  • a method performed in a network node for uplink (UL) demodulation reference signal (DMRS) configuration includes determining a first bit field value, the first bit field value indicating a repetition factor (RPF).
  • the method may further include determining a second bit field value, the second bit field value indicating at least one of a cyclic shift and a comb index.
  • the method includes configuring an uplink DMRS configuration, wherein the uplink DMRS configuration comprises the first bit field value and the second bit field value and transmitting the uplink DMRS configuration to a wireless device.
  • the network node may include processing circuitry and an interface operably coupled to the processing circuity.
  • the processing circuitry may be configured to determine a first bit field value, the first bit field value indicating a repetition factor (RPF).
  • the processing circuitry may also determine a second bit field value, the second bit field value indicating at least one of a cyclic shift and a comb index.
  • the processing circuitry may also configure an uplink DMRS configuration, wherein the uplink DMRS configuration comprises the first bit field value and the second bit field value.
  • the interface may be configured to transmit the uplink DMRS configuration to a wireless device.
  • the first bit field value and the second bit field value are each one bit. In some embodiments, the first bit field value indicates a RPF of 1 or an RPF of 2.
  • values associated with the at least one of the cyclic shift and the comb index are indicated by the second bit field value according to a mapping table.
  • the UL DMRS configuration is transmitted in an uplink- related downlink control information (DCI) transmission.
  • the UL DMRS configuration is for uplink short transmission time interval (sTTI) transmissions by the wireless device
  • Also disclosed is a computer program product comprising a non-transitc
  • a wireless device for uplink demodulation reference signal (DMRS) configuration includes receiving a transmission from a network node, the transmission comprising an uplink demodulation reference signal (DMRS) configuration.
  • the method may further include detecting a first bit field value from the uplink DMRS configuration, the first bit field value indicating a repetition factor (RPF).
  • the method may further include detecting a second bit field value from the uplink DMRS configuration, the second bit field value indicating at least one of a cyclic shift and a comb index.
  • the method may further include determining an uplink DMRS based at least in part on the repetition factor, the cyclic shift, and the comb index.
  • the wireless device may include an interface operably coupled to a wireless device.
  • the interface may be configured to receive a transmission from a network node, the transmission comprising an uplink demodulation reference signal (DMRS) configuration.
  • the processing circuity may be configured to detect a first bit field value from the uplink DMRS configuration, the first bit field value indicating a repetition factor (RPF).
  • the processing circuity may be further configured to detect a second bit field value from the uplink DMRS configuration, the second bit field value indicating at least one of a cyclic shift and a comb index.
  • the processing circuity may be configured to determine an uplink DMRS based at least in part on the repetition factor, the cyclic shift, and the comb index.
  • the uplink DMRS may be transmitted to a network node on a short physical uplink shared channel (sPUSCH).
  • sPUSCH short physical uplink shared channel
  • the values associated with the at least one of the cyclic shift and the comb index are indicated by the second bit field value according to a mapping table.
  • the mapping table is stored in a memory of the wireless device.
  • the first bit field value and the second bit field value are each one bit.
  • the first bit field value indicates a RPF of 1 or an RPF of 2.
  • the uplink DMRS is used for uplink short trans
  • the transmission comprises an uplink- related downlink control information (DCI) transmission.
  • DCI downlink control information
  • a computer program product comprising a non -transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the wireless device described above.
  • Certain embodiments of the present disclosure may provide one or more technical advantages. For example, in certain embodiments, a signaling method for UL DMRS configuration for uplink short TTI transmissions is disclosed. One bit is used for indicating
  • n (2) the RPF value (1 or 2), and one bit is used for indicating the cyclic shift parameter DMRS "* 5 n (2)
  • the signaling method can support multiplexing of DMRS of different UEs for uplink short TTI transmissions, and DMRS port multiplexing to support 4-layer transmission of sPUSCH.
  • the signaling method may reduce the signaling overhead from 4 bits in UL DCI for legacy UL DMRS configuration to 2 bits in UL sDCI for UL DMRS for sPUSCH.
  • FIGURE 1 illustrates an example radio frame, including sub-frames, according to certain embodiments
  • FIGURE 2 illustrates an example time-frequency grid of a downlink physical resource, according to certain embodiments
  • FIGURE 3 illustrates an example uplink resource grid, according to certain embodiments
  • FIGURE 4 illustrates an example downlink subframe, according to certain embodiments
  • FIGURE 5 illustrates an example DMRS allocation in a RB of a subframe, according to certain embodiments
  • FIGURE 6 illustrates an example uplink DMRS with interleaved frequency division multiplexing (IFDMA), according to certain embodiments
  • FIGURE 7 illustrates an example of a 7-symbol sTTI configuration, according to certain embodiments
  • FIGURE 8 illustrates an example of a 2/3-symbol sTTI configuration, according to certain embodiments
  • FIGURE 9 illustrates an example of DMRS sharing for a 2/3-symbol sTTI configuration, according to certain embodiments.
  • FIGURES 10a and 10b illustrate examples of DMRS multiplexing for two, 2/3- symbol sTTI configurations
  • FIGURE 11 illustrates two sPUSCH transmissions with partially overlapped frequency allocation, according to certain embodiments.
  • FIGURE 12 illustrates an example wireless network, according to
  • FIGURE 13 illustrates an example user equipment, according to certain embodiments
  • FIGURE 14 illustrates a flowchart of an example method in a user equipment for the signaling of uplink DMRS configuration, according to certain embodiments
  • FIGURE 15 illustrates a flowchart of an example method in a network node for the signaling of uplink DMRS configuration, according to certain embodiments
  • FIGURE 16 illustrates an example wireless device, according to certain embodiments.
  • FIGURE 17 illustrates an example network node, according to certain embodiments.
  • FIGURE 18 illustrates an example virtualization environment, according to certain embodiments.
  • FIGURE 19 illustrates an example telecommunication network connected via an intermediate network to a host computer, according to certain embodiments
  • FIGURE 20 illustrates an example host computer communicating via a base station with a user equipment over a partially wireless connection, according to certain embodiments
  • FIGURE 21 is a flowchart illustrating a method implemented, according to certain embodiments.
  • FIGURE 22 is a flowchart illustrating a method implemented in a communication system, according to certain embodiments.
  • FIGURE 23 is a flowchart illustrating a method implemented in a communication system, according to certain embodiments.
  • FIGURE 24 is a flowchart illustrating a method implemented in a communication system, according to certain embodiments.
  • DMRS multiplexing/sharing can be used to reduce the DMRS overhead.
  • different UEs can be allocated with different frequency resources, where part of their frequency allocation is overlapped, as shown in FIGURE 11.
  • DMRS multiplexing should also be supported in this partially overlapped frequency allocation case to reduce the DMRS overhead, and at the same time, keep the scheduling flexibility.
  • the supported DMRS and data combinations implies that maximum two UEs can be multiplexed by sharing the same symbol for UL DMRS.
  • each comb supports only up to 2 layers multiplexing for IFDMA DMRS for 2/3-symbol sPUSCH. Therefore, the number of bits used for signaling the UL DMRS configuration for sPUSCH can be further reduced to reduce the signaling overhead.
  • the DMRS of different UEs can be multiplexed on the same SC- FDMA symbol by using different cyclic shifts.
  • signaling DMRS configuration for uplink sTTI transmissions may include using 1-bit field to indicate an RPF value and using 1-bit field to indicate the cyclic shift and comb index.
  • the bit for the indication of the cyclic shift and comb index may be determined using a mapping table.
  • Embodiments of the present disclosure may provide one or more technical benefits not found in current solutions. Certain embodiments may allow for a reduction in the signaling overhead (e.g., from 4 bits in UL DCI for legacy UL DMRS configuration to 2 bits in UL sDCI for UL DMRS for sPUSCH).
  • FIGURE 12 illustrates an example wireless network, according to certain embodiments.
  • the wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system.
  • the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures.
  • 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 the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • WLAN wireless local area network
  • WiMax Worldwide Interoperability for Microwave Access
  • Bluetooth Z-Wave and/or ZigBee standards.
  • Network 106 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), 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 to enable communication between devices.
  • PSTNs public switched telephone networks
  • WANs wide-area networks
  • LANs local area networks
  • WLANs wireless local area networks
  • wired networks wireless networks, metropolitan area networks, and other networks to enable communication between devices.
  • Network node 160 and WD 110 comprise various components described in more detail below. These components work together to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network.
  • the wireless network may comprise 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.
  • network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network.
  • network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base statior
  • Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations.
  • a base station may be a relay node or a relay donor node controlling a relay.
  • a network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • RRUs remote radio units
  • RRHs Remote Radio Heads
  • a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
  • network nodes include multi-standard radio (MSR) equipment 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.
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • MCEs multi-cell/multicast coordination entities
  • core network nodes e.g., MSCs, MMEs
  • O&M nodes OSS nodes
  • SON nodes e.g., positioning nodes
  • network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.
  • network node 160 includes processing circuitry 170, device readable medium 180, interface 190, auxiliary equipment 184, power source 186, power circuitry 187, and antenna 162.
  • network node 160 illustrated in the example wireless network of Figure 1 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein.
  • the components of network node 160 are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium 180 may comprise mult
  • network node 160 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components.
  • network node 160 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes.
  • a single RNC may control multiple NodeB's.
  • each unique NodeB and RNC pair may in some instances be considered a single separate network node.
  • network node 160 may be configured to support multiple radio access technologies (RATs).
  • RATs radio access technologies
  • Network node 160 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 160, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 160.
  • Processing circuitry 170 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry 170 may include processing information obtained by processing circuitry 170 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing information obtained by processing circuitry 170 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • Processing circuitry 170 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application- specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 160
  • processing circuitry 170 may execute instructions stored in device readable medium 180 or in memory within processing circuitry 170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein.
  • processing circuitry 170 may include a system on a chip (SOC).
  • processing circuitry 170 may include one or more of radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174.
  • radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units.
  • part or all of RF transceiver circuitry 172 and baseband processing circuitry 174 may be on the same chip or set of chips, boards, or units
  • processing circuitry 170 executing instructions stored on device readable medium 180 or memory within processing circuitry 170.
  • some or all of the functionality may be provided by processing circuitry 170 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner.
  • processing circuitry 170 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 170 alone or to other components of network node 160, but are enjoyed by network node 160 as a whole, and/or by end users and the wireless network generally.
  • Device readable medium 180 may comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, 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 memory devices that store information, data, and/or instructions that may be used by processing circuitry 170.
  • Device readable medium 180 may be used to store any calculations made by processing circuitry 170 and/or any data received via interface 190. In some embodiments, processing circuitry 170 and device readable medium 180 may be considered to be integrated.
  • Interface 190 is used in the wired or wireless communication of signaling and/or data between network node 160, network 106, and/or WDs 110. As illustrated, interface 190 comprises port(s)/terminal(s) 194 to send and receive data, for example to and from network 106 over a wired connection. Interface 190 also includes radio front end circuitry 192 that may be coupled to, or in certain embodiments a part of, antenna 162. Radio front end circuitry 192 comprises filters 198 and amplifiers 196. Radio front end circuitry 192 may be connected to antenna 162 and processing circuitry 170. Radio front end circuitry may be configured to condition signals communicated between antenna 162 and processing circuitry 170.
  • Radio front end circuitry 192 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 192 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 198 and/or amplifiers 196. The radio signal may then be transmitted via antenna 162. Similarly, when receiving data, antenna 162 may collect radio signals which are then converted into digital data by radio front end circuitry 192. The digital data may be passed to processing circuitry 170. In other embodiments, the interface may comprise different components and/or different combinations of components.
  • network node 160 may not include separate radio front end circuitry 192, instead, processing circuitry 170 may comprise radio front end circuitry and may be connected to antenna 162 without separate radio front end circuitry 192.
  • processing circuitry 170 may comprise radio front end circuitry and may be connected to antenna 162 without separate radio front end circuitry 192.
  • all or some of RF transceiver circuitry 172 may be considered a part of interface 190.
  • interface 190 may include one or more ports or terminals 194, radio front end circuitry 192, and RF transceiver circuitry 172, as part of a radio unit (not shown), and interface 190 may communicate with baseband processing circuitry 174, which is part of a digital unit (not shown).
  • Antenna 162 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna 162 may be coupled to radio front end circuitry 190 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna 162 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omni-directional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In certain embodiments, antenna 162 may be separate from network node 160 and may be connectable to network node 160 through an interface or port.
  • Antenna 162, interface 190, and/or processing circuitry 170 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna 162, interface 190, and/or processing circuitry 170 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.
  • Power circuitry 187 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node 160 with power for performing the functionality described herein. Power circuitry 187 may receive power from power source 186. Power source 186 and/or power circuitry 187 may be configured to provide power to the various components of network node 160 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 186 may either be included in, or external to, power circuitry 187 and/or network node 160. For example, network node 160 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry 187. As a further exa further exa
  • source 186 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 187.
  • the battery may provide backup power should the external power source fail.
  • Other types of power sources, such as photovoltaic devices, may also be used.
  • network node 160 may include additional components beyond those shown in FIGURE 12 that may be responsible for providing certain aspects of the network node's functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein.
  • network node 160 may include user interface equipment to allow input of information into network node 160 and to allow output of information from network node 160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 160.
  • wireless device refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices.
  • the term WD may be used interchangeably herein with user equipment (UE).
  • Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air.
  • a WD may be configured to transmit and/or receive information without direct human interaction.
  • a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network.
  • Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop -mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE), a vehicle- mounted wireless terminal device, etc.
  • a WD may support device-to-device (D2D) communication, for example by implementing a 3 GPP standard for sidelink cor
  • V2V vehicle-to-vehicle
  • V2I vehicle-to-infrastructure
  • V2X vehicle-to-everything
  • a WD may represent a machine or other device that performs monitoring and/or measurements and transmits the results of such monitoring and/or measurements to another WD and/or a network node.
  • the WD may in this case be a machine-to-machine (M2M) device, which may in a 3 GPP context be referred to as an MTC device.
  • M2M machine-to-machine
  • the WD may be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard.
  • machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.).
  • a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • a WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal.
  • a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.
  • wireless device 110 includes antenna 111, interface 114, processing circuitry 120, device readable medium 130, user interface equipment 132, auxiliary equipment 134, power source 136 and power circuitry 137.
  • WD 110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD 110.
  • Antenna 111 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 114. In certain alternative embodiments, antenna 111 may be separate from WD 110 and be connectable to WD 110 through an interface or port. Antenna 111, interface 114, and/or processing circuitry 120 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received fro
  • radio front end circuitry and/or antenna 111 may be considered an interface.
  • interface 114 comprises radio front end circuitry 112 and antenna 111.
  • Radio front end circuitry 112 comprise one or more filters 118 and amplifiers 116.
  • Radio front end circuitry 114 is connected to antenna 111 and processing circuitry 120 and is configured to condition signals communicated between antenna 111 and processing circuitry 120.
  • Radio front end circuitry 112 may be coupled to or a part of antenna 111.
  • WD 110 may not include separate radio front end circuitry 112; rather, processing circuitry 120 may comprise radio front end circuitry and may be connected to antenna 111.
  • Radio front end circuitry 112 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 112 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 118 and/or amplifiers 116. The radio signal may then be transmitted via antenna 111. Similarly, when receiving data, antenna 111 may collect radio signals which are then converted into digital data by radio front end circuitry 112. The digital data may be passed to processing circuitry 120. In other embodiments, the interface may comprise different components and/or different combinations of components.
  • Processing circuitry 120 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application- specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other WD 110 components, such as device readable medium 130, WD 110 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 120 may execute instructions stored in device readable medium 130 or in memory within processing circuitry 120 to provide the functionality disclosed herein.
  • processing circuitry 120 includes one or more of RI
  • processing circuitry 122 may comprise different components and/or different combinations of components.
  • processing circuitry 120 of WD 110 may comprise a SOC.
  • RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126 may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry 124 and application processing circuitry 126 may be combined into one chip or set of chips, and RF transceiver circuitry 122 may be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry 122 and baseband processing circuitry 124 may be on the same chip or set of chips, and application processing circuitry 126 may be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126 may be combined in the same chip or set of chips.
  • RF transceiver circuitry 122 may be a part of interface 114.
  • RF transceiver circuitry 122 may condition RF signals for processing circuitry 120.
  • processing circuitry 120 executing instructions stored on device readable medium 130, which in certain embodiments may be a computer- readable storage medium.
  • some or all of the functionality may be provided by processing circuitry 120 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner.
  • processing circuitry 120 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 120 alone or to other components of WD 110, but are enjoyed by WD 110, and/or by end users and the wireless network generally.
  • Processing circuitry 120 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry 120, may include processing information obtained by processing circuitry 120 by, for example, c ⁇
  • Device readable medium 130 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 120.
  • Device readable medium 130 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or nonvolatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 120.
  • processing circuitry 120 and device readable medium 130 may be integrated.
  • User interface equipment 132 may provide components that allow for a human user to interact with WD 110. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment 132 may be operable to produce output to the user and to allow the user to provide input to WD 110. The type of interaction may vary depending on the type of user interface equipment 132 installed in WD 110. For example, if WD 110 is a smart phone, the interaction may be via a touch screen; if WD 110 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected).
  • usage e.g., the number of gallons used
  • a speaker that provides an audible alert
  • User interface equipment 132 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 132 is configured to allow input of information into WD 110 and is connected to processing circuitry 120 to allow processing circuitry 120 to process the input information. User interface equipment 132 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment 132 is also configured to allow output of information from WD 110, and to allow processing circuitry 120 to output infoi
  • User interface equipment 132 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment 132, WD 110 may communicate with end users and/or the wireless network and allow them to benefit from the functionality described herein.
  • Auxiliary equipment 134 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment 134 may vary depending on the embodiment and/or scenario.
  • Power source 136 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used.
  • WD 110 may further comprise power circuitry 137 for delivering power from power source 136 to the various parts of WD 110 which need power from power source 136 to carry out any functionality described or indicated herein.
  • Power circuitry 137 may in certain embodiments comprise power management circuitry.
  • Power circuitry 137 may additionally or alternatively be operable to receive power from an external power source; in which case WD 110 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable.
  • Power circuitry 137 may also in certain embodiments be operable to deliver power from an external power source to power source 136. This may be, for example, for the charging of power source 136. Power circuitry 137 may perform any formatting, converting, or other modification to the power from power source 136 to make the power suitable for the respective components of WD 110 to which power is supplied.
  • the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in FIGURE 12.
  • the wireless network of FIGURE 12 only depicts network 106, network nodes 160 and 160b, and WDs 110, 110b, and 110c. In practic
  • network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device.
  • network node 160 and wireless device (WD) 110 are depicted with additional detail.
  • the wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices' access to and/or use of the services provided by, or via, the wireless network.
  • FIGURE 13 illustrates an example user equipment, according to certain embodiments.
  • a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device.
  • a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller).
  • a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).
  • UE 200 may be any UE identified by the 3 rd Generation Partnership Project (3 GPP), including a NB-IoT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • UE 200 as illustrated in FIGURE 13, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3 rd Generation Partnership Project (3 GPP), such as 3GPP's GSM, UMTS, LTE, and/or 5G standards.
  • 3 GPP 3 rd Generation Partnership Project
  • the term WD and UE may be used interchangeable. Accordingly, although FIGURE 2 is a UE, the components discussed herein are equally applicable to a WD, and vice- versa.
  • UE 200 includes processing circuitry 201 that is operatively coupled to input/output interface 205, radio frequency (RF) interface 209, network connection interface 211, memory 215 including random access memory (RAM) 217, read-only memory (ROM) 219, and storage medium 221 or the like, communication subsystem 231, power source 233, and/or any other component, or any combination thereof.
  • Storage medium 221 includes operating system 223, application program 225, and data 227. In other embodiments, storage medium 221 may include other similar types of information. Certain UEs may utilize all of the components shown in FIGURE 13, or only a s
  • processing circuitry 201 may be configured to process computer instructions and data.
  • Processing circuitry 201 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine- readable computer programs in the memory, such as one or more hardware -implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above.
  • the processing circuitry 201 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.
  • input/output interface 205 may be configured to provide a communication interface to an input device, output device, or input and output device.
  • UE 200 may be configured to use an output device via input/output interface 205.
  • An output device may use the same type of interface port as an input device.
  • a USB port may be used to provide input to and output from UE 200.
  • the output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof.
  • UE 200 may be configured to use an input device via input/output interface 205 to allow a user to capture information into UE 200.
  • the input device may include a touch- sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like.
  • the presence- sensitive display may include a capacitive or resistive touch sensor to sense input from a user.
  • a sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof.
  • the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.
  • RF interface 209 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenn
  • connection interface 211 may be configured to provide a communication interface to network 243a.
  • Network 243a may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof.
  • network 243a may comprise a Wi-Fi network.
  • Network connection interface 211 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like.
  • Network connection interface 211 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.
  • RAM 217 may be configured to interface via bus 202 to processing circuitry 201 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers.
  • ROM 219 may be configured to provide computer instructions or data to processing circuitry 201.
  • ROM 219 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory.
  • Storage medium 221 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives.
  • storage medium 221 may be configured to include operating system 223, application program 225 such as a web browser application, a widget or gadget engine or another application, and data file 227.
  • Storage medium 221 may store, for use by UE 200, any of a variety of various operating systems or combinations of operating systems.
  • Storage medium 221 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-di
  • RAID redundant array of independent disks
  • floppy disk drive flash memory
  • USB flash drive external hard disk drive
  • thumb drive thumb drive
  • pen drive key drive
  • high-di high-di
  • Storage medium 221 may allow UE 200 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off- load data, or to upload data.
  • An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium 221, which may comprise a device readable medium.
  • processing circuitry 201 may be configured to communicate with network 243b using communication subsystem 231.
  • Network 243a and network 243b may be the same network or networks or different network or networks.
  • Communication subsystem 231 may be configured to include one or more transceivers used to communicate with network 243b.
  • communication subsystem 231 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.2, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like.
  • RAN radio access network
  • Each transceiver may include transmitter 233 and/or receiver 235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter 233 and receiver 235 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.
  • the communication functions of communication subsystem 231 may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof.
  • communication subsystem 231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Netwoi
  • Network 243b may be a cellular network, a Wi-Fi network, and/or a near- field network.
  • Power source 213 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE 200.
  • communication subsystem 231 may be configured to include any of the components described herein.
  • processing circuitry 201 may be configured to communicate with any of such components over bus 202.
  • any of such components may be represented by program instructions stored in memory that when executed by processing circuitry 201 perform the corresponding functions described herein.
  • the functionality of any of such components may be partitioned between processing circuitry 201 and communication subsystem 231.
  • the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.
  • Embodiments of the present disclosure provide a signaling method for UL DMRS configuration and, in particular, configuration(s) for uplink short TTI transmissions.
  • the UL DMRS configurations include one or more of the RPF value (1 n(2)
  • the signaling method may include:
  • mapping table shown in Table 6 may be implemented.
  • Table 6 allows for different cyclic shifts for all layers and users. This allows a better separation in case of intercarrier interference.
  • the minimum cyclic shift distance between users may be 4 for a given comb index and 1 between two comb indexes.
  • Table 7 provides an additional non-limiting example of mapping of 1-bit cyclic shift field in uplink- related DCI format to DMRS 1 and .
  • Table 7 Mapping of the 1-bit Cyclic Shift Field in uplink-related DCI format to n ° MRS ⁇ and Table 8 provides another non-limiting example of mapping of 1-bit cyclic shift filed in
  • uplink-related DCI format to DMRs i and m .
  • the mapping shown in Table 8 attempts to maximize and differentiate the cyclic shift distance between users.
  • the foregoing embodiments illustrate various examples for indicating UL DMRS related aspects by sDCI, including cyclic shift and comb index, as well as providing example mappings of 1-bit cyclic shift field in uplink-related DCI format.
  • the foregoing examples are merely illustrative, any suitable cyclic shift values and/or comb indices may be used.
  • FIGURE 14 illustrates a flowchart of an example method in a wireless device for uplink DMRS configuration, according to certain embodiments.
  • the method begins at step 1401 with wireless device 110 receiving a transmission from a network node.
  • the transmission may include an uplink demodulation reference signal (DMRS) configuration.
  • DMRS uplink demodulation reference signal
  • the uplink DMRS configuration may be received as part of an uplink-related DCI.
  • the wireless device may determine a first bit field val
  • the first bit field value indicates a repetition factor (RPF) value (e.g., 1 or 2).
  • RPF repetition factor
  • wireless device 110 determines a second bit field value.
  • the second bit field value indicates a cyclic shift and a comb index.
  • the cyclic shift and a comb index may be determined according to a mapping table, such as Tables 5-8.
  • wireless device 110 may store one or more mapping tables in in readable medium 130. Accordingly, in certain embodiments, based on the value of the second bit field (e.g., 0 or 1), wireless device 110 may determine the cyclic shift and the comb index using a mapping table stored in memory (e.g., Table 8).
  • the first bit field value and the second bit field value are each 1 bit. This may reduce the signaling needed to transmit DMRS configuration information, thereby reducing latency and signaling overhead.
  • wireless device 110 may configure an uplink DMRS based at least in part on the repetition factor, the cyclic shift, and the comb index.
  • wireless device 110 may transmit the uplink DMRS to network node 160.
  • the uplink DMRS may be transmitted to the network node 160 using the short physical uplink shared channel (sPUSCH).
  • the uplink DMRS may be used for uplink short transmission time interval (sTTI) transmissions.
  • FIGURE 15 illustrates a flowchart of an example method in a network node for uplink DMRS configuration, according to certain embodiments.
  • the method begins at step 1501, wherein network node 160 determines a first bit field value.
  • the first bit field value may indicate a repetition factor (RPF).
  • RPF repetition factor
  • the first bit field value may indicate a RPF of 1 or an RPF of 2.
  • the network node 160 may determine a second bit field value.
  • the second bit field value may indicate a cyclic shift and a comb index.
  • the bit field may correspond to a mapping table (e.g., any of mapping tables 5-8) that provides for different cyclic shift and comb indices based on the bit field value.
  • network node 160 may configure an uplink DMRS configuration.
  • the uplink DMRS configuration comprises the first bit field value and the second bit field value.
  • the uplink DMRS is configured pursuant to an uplink-related DCI format.
  • the network node 160 may transmit the uplink DMRS configuration to the wireless device 110.
  • the uplink DMRS configuration may be transmitted in an uplink-related DCI transmissio
  • the wireless device may utilize the uplink DMRS configuration for uplink sTTI transmissions.
  • FIGURE 16 illustrates an example wireless device, according to certain embodiments.
  • the apparatus may be implemented in a wireless device (e.g., wireless device 110 shown in Figure 1).
  • Apparatus 1600 is operable to carry out the example method described with reference to FIGURE 14 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 14 is not necessarily carried out solely by apparatus 1600. At least some operations of the method can be performed by one or more other entities, including virtual apparatuses.
  • Apparatus 1600 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments.
  • the processing circuitry may be used to cause receiving unit 1602, determining unit 1604, storage unit 1606, and communication unit 1608 and any other suitable units of apparatus 1600 to perform corresponding functions according one or more embodiments of the present disclosure.
  • apparatus 1600 includes receiving unit 1602, determining unit 1604, storage unit 1606, and communication unit 1608.
  • receiving unit 1602 may receive a transmission from a network node 160.
  • the transmission may include an uplink demodulation reference signal (DMRS) configuration.
  • DMRS uplink demodulation reference signal
  • the uplink DMRS configuration may be received as part of an uplink- related DCI.
  • Determining unit 1604 may detect a first bit field value from the uplink DMRS configuration, the first bit field value indicating a repetition factor (RPF). Dete
  • the second bit field value may also detect a second bit field value from the uplink DMRS configuration, the second bit field value indicating a cyclic shift and a comb index.
  • the first bit field value and the second bit field value may each be one bit.
  • Determining unit 1604 may also determine an uplink DMRS based at least in part on the repetition factor, the cyclic shift, and the comb index.
  • determining unit 1604 may determine the cyclic shift and the comb index using a mapping table.
  • the mapping table may be stored by storage unit 1606.
  • communication unit 1608 may transmit the uplink DMRS to a network node 160 on a short physical uplink shared channel (sPUSCH).
  • sPUSCH short physical uplink shared channel
  • communication unit 1608 may use the uplink DMRS for an uplink sTTI transmission.
  • FIGURE 17 illustrates an example network node, according to certain embodiments.
  • the apparatus may be implemented in a network node (e.g., network node 160 shown in Figure 1).
  • Apparatus 1600 is operable to carry out the example method described with reference to FIGURE 15 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 15 is not necessarily carried out solely by apparatus 1700. At least some operations of the method can be performed by one or more other entities, including virtual apparatuses.
  • Apparatus 1700 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments.
  • the processing circuitry may be used to cause receiving unit 1702 and determining ⁇
  • apparatus 1700 includes communication unit 1702 and determining unit 1704.
  • determining unit 1704 may determine a first bit field value.
  • the first bit field value may indicate a repetition factor (RPF) (e.g., an RPF 1 or 2).
  • Determining unit 1704 may also determine a second bit field value.
  • the second bit field value may indicate a cyclic shift and a comb index.
  • the second bit field value may only indicate cyclic shift value(s). In certain embodiments, this may occur if, for example, RPF-0.
  • the second bit field value may indicate both cyclic shift value(s) and comb index(ices).
  • the bit field may correspond to a mapping table (e.g., mapping tables 5-8) that provides the values for different cyclic shift and comb indices based on the bit field value.
  • Determining unit 1704 may further configure an uplink DMRS configuration comprising the first bit field value and the second bit field value.
  • the uplink DMRS configuration may conform to an uplink-related DCI (or sDCI) format.
  • Communication unit 1702 may transmit the uplink DMRS configuration to a wireless device. For example, communication unit 1702 may transmit the uplink DMRS configuration as part of a uplink-related DCI transmission.
  • FIGURE 18 is a schematic block diagram illustrating a virtualization environment 300 in which functions implemented by some embodiments may be virtualized.
  • virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources.
  • virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines c
  • some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 300 hosted by one or more of hardware nodes 330. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.
  • the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node)
  • the network node may be entirely virtualized.
  • the functions may be implemented by one or more applications 320 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Applications 320 are run in virtualization environment 300 which provides hardware 330 comprising processing circuitry 360 and memory 390.
  • Memory 390 contains instructions 395 executable by processing circuitry 360 whereby application 320 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.
  • Virtualization environment 300 comprises general-purpose or special-purpose network hardware devices 330 comprising a set of one or more processors or processing circuitry 360, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors.
  • processors or processing circuitry 360 which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors.
  • Each hardware device may comprise memory 390-1 which may be non-persistent memory for temporarily storing instructions 395 or software executed by processing circuitry 360.
  • Each hardware device may comprise one or more network interface controllers (NICs) 370, also known as network interface cards, which include physical network interface 380.
  • NICs network interface controllers
  • Each hardware device may also include non-transitory, persistent, machine -readable storage media 390-2 having stored therein software 395 and/or instructions executable by processing circuitry 360.
  • Software 395 may include any type of software including software for instantiating one or more virtualization layers 350 (also referred to as hypervisors), software to execute virtual machines 340 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.
  • Virtual machines 340 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 350 or hypervisor. Different embodiments of the instance of virtual appliance 320 may be implemented on one or more of virtual machines 340, and the implementations may be made in different ways.
  • processing circuitry 360 executes software 395 to instantiate the hypervisor or virtualization layer 350, which may sometimes be referred to as a virtual machine monitor (VMM).
  • VMM virtual machine monitor
  • Virtualization layer 350 may present a virtual operating platform that appears like networking hardware to virtual machine 340.
  • hardware 330 may be a standalone network node with generic or specific components. Hardware 330 may comprise antenna 3225 and may implement some functions via virtualization. Alternatively, hardware 330 may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) 3100, which, among others, oversees lifecycle management of applications 320.
  • CPE customer premise equipment
  • MANO management and orchestration
  • NFV network function virtualization
  • NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
  • virtual machine 340 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine.
  • Each of virtual machines 340, and that part of hardware 330 that executes that virtual machine be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines 340, forms a separate virtual network elements (VNE).
  • VNE virtual network elements
  • VNF Virtual Network Function
  • one or more radio units 3200 that each include
  • Radio units 3200 may communicate directly with hardware nodes 330 via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.
  • control system 3230 which may alternatively be used for communication between the hardware nodes 330 and radio units 3200.
  • a communication system includes telecommunication network 410, such as a 3GPP-type cellular network, which comprises access network 411, such as a radio access network, and core network 414.
  • Access network 411 comprises a plurality of base stations 412a, 412b, 412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 413a, 413b, 413c.
  • Each base station 412a, 412b, 412c is connectable to core network 414 over a wired or wireless connection 415.
  • a first UE 491 located in coverage area 413c is configured to wirelessly connect to, or be paged by, the corresponding base station 412c.
  • a second UE 492 in coverage area 413a is wirelessly connectable to the corresponding base station 412a. While a plurality of UEs 491, 492 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 412.
  • Telecommunication network 410 is itself connected to host computer 430, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm.
  • Host computer 430 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider.
  • Connections 421 and 422 between telecommunication network 410 and host computer 430 may extend directly from core network 414 to host computer 430 or may go via an optional intermediate network 420.
  • Intermediate network 420 may be one of, or a combination of more than one
  • intermediate network 420 may be a backbone network or the Internet; in particular, intermediate network 420 may comprise two or more sub-networks (not shown).
  • the communication system of Figure 19 as a whole enables connectivity between the connected UEs 491, 492 and host computer 430.
  • the connectivity may be described as an over-the-top (OTT) connection 450.
  • Host computer 430 and the connected UEs 491, 492 are configured to communicate data and/or signaling via OTT connection 450, using access network 411, core network 414, any intermediate network 420 and possible further infrastructure (not shown) as intermediaries.
  • OTT connection 450 may be transparent in the sense that the participating communication devices through which OTT connection 450 passes are unaware of routing of uplink and downlink communications.
  • base station 412 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer 430 to be forwarded (e.g., handed over) to a connected UE 491. Similarly, base station 412 need not be aware of the future routing of an outgoing uplink communication originating from the UE 491 towards the host computer 430.
  • Host Computer Embodiments
  • FIGURE 20 illustrates an example host computer communicating via a base station with a user equipment over a partially wireless connection, according to certain embodiments.
  • host computer 510 comprises hardware 515 including communication interface 516 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 500.
  • Host computer 510 further comprises processing circuitry 518, which may have storage and/or processing capabilities.
  • processing circuitry 518 may comprise one or more programmable processors, application- specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • Host computer 510 further comprises software 511, whid
  • Software 511 includes host application 512.
  • Host application 512 may be operable to provide a service to a remote user, such as UE 530 connecting via OTT connection 550 terminating at UE 530 and host computer 510. In providing the service to the remote user, host application 512 may provide user data which is transmitted using OTT connection 550.
  • Communication system 500 further includes base station 520 provided in a telecommunication system and comprising hardware 525 enabling it to communicate with host computer 510 and with UE 530.
  • Hardware 525 may include communication interface 526 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 500, as well as radio interface 527 for setting up and maintaining at least wireless connection 570 with UE 530 located in a coverage area (not shown in FIGURE 20) served by base station 520.
  • Communication interface 526 may be configured to facilitate connection 560 to host computer 510. Connection 560 may be direct or it may pass through a core network (not shown in FIGURE 20) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system.
  • hardware 525 of base station 520 further includes processing circuitry 528, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • processing circuitry 528 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • Base station 520 further has software 521 stored internally or accessible via an external connection.
  • Communication system 500 further includes UE 530 already referred to. Its hardware 535 may include radio interface 537 configured to set up and maintain wireless connection 570 with a base station serving a coverage area in which UE 530 is currently located. Hardware 535 of UE 530 further includes processing circuitry 538, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • UE 530 further comprises software 531, which is stored in or accessible by UE 530 and executable by processing circuitry 538.
  • Software 531 includes client application 532. Client application 532 may be operable to provide a service to a human or non-human user via UE 530, with the support of host computer 510. In host computer 510,
  • host application 512 may communicate with the executing client application 532 via OTT connection 550 terminating at UE 530 and host computer 510.
  • client application 532 may receive request data from host application 512 and provide user data in response to the request data.
  • OTT connection 550 may transfer both the request data and the user data.
  • Client application 532 may interact with the user to generate the user data that it provides.
  • host computer 510, base station 520 and UE 530 illustrated in FIGURE 20 may be similar or identical to host computer 430, one of base stations 412a, 412b, 412c and one of UEs 491, 492 of Figure 19, respectively.
  • the inner workings of these entities may be as shown in Figure 5 and independently, the surrounding network topology may be that of Figure 19.
  • OTT connection 550 has been drawn abstractly to illustrate the communication between host computer 510 and UE 530 via base station 520, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • Network infrastructure may determine the routing, which it may be configured to hide from UE 530 or from the service provider operating host computer 510, or both. While OTT connection 550 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).
  • Wireless connection 570 between UE 530 and base station 520 is in accordance with the teachings of the embodiments described throughout this disclosure.
  • One or more of the various embodiments improve the performance of OTT services provided to UE 530 using OTT connection 550, in which wireless connection 570 forms the last segment. More precisely, the teachings of these embodiments may improve the signaling overhead and reduce latency, which may provide faster internet access for users.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • OTT connection 550 may be implemented in software 511 and hardware 515 of host computer 510 or in software 531 and hardware 535 of UE 530, or both.
  • sensors (not shown) may be deployed in or in association with communication devices through which OTT connection 550 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 511, 531 may compute or estimate the monitored quantities.
  • the reconfiguring of OTT connection 550 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station 520, and it may be unknown or imperceptible to base station 520. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling facilitating host computer 510's measurements of throughput, propagation times, latency and the like.
  • the measurements may be implemented in that software 511 and 531 causes messages to be transmitted, in particular empty or 'dummy' messages, using OTT connection 550 while it monitors propagation times, errors etc.
  • FIGURE 21 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 19 and 20. For simplicity of the present disclosure, only drawing references to FIGURE 21 will be included in this section.
  • the host computer provides user data.
  • substep 611 (which may be optional) of step 610, the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE.
  • step 630 the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure.
  • step 640 the UE executes a client application associated with the host application executed by the host computer.
  • FIGURE 22 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference
  • step 710 of the method the host computer provides user data.
  • the host computer provides the user data by executing a host application.
  • step 720 the host computer initiates a transmission carrying the user data to the UE.
  • the transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure.
  • step 730 (which may be optional), the UE receives the user data carried in the transmission.
  • FIGURE 23 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 19 and 20. For simplicity of the present disclosure, only drawing references to FIGURE 23 will be included in this section.
  • step 810 the UE receives input data provided by the host computer. Additionally or alternatively, in step 820, the UE provides user data.
  • substep 821 (which may be optional) of step 820, the UE provides the user data by executing a client application.
  • substep 811 (which may be optional) of step 810, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer.
  • the executed client application may further consider user input received from the user.
  • the UE initiates, in substep 830 (which may be optional), transmission of the user data to the host computer.
  • step 840 of the method the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.
  • FIGURE 24 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 19 and 20. For simplicity of the present disclosure, only drawing references to FIGURE 24 will be included in this section.
  • the base station receives user data from the UE.
  • the base station initiates transmission of the received user data to the host computer.
  • step 930 (w
  • the host computer receives the user data carried in the transmission initiated by the base station.
  • the term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
  • steps may be performed in any suitable order.
  • references in the specification to "one embodiment,” “an embodiment,” “an example embodiment,” etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to implement such feature, structure, or characteristic in connection with other embodiments, whether or not explicitly described.

Abstract

Selon certains modes de réalisation, l'invention concerne un nœud de réseau pour une configuration de signal de référence de démodulation de liaison montante (DMRS). Le nœud de réseau peut comprendre des circuits de traitement couplés fonctionnellement à un émetteur-récepteur. Les circuits de traitement peuvent être configurés : pour déterminer une première valeur de champ binaire, la première valeur de champ binaire indiquant un facteur de répétition (RPF); pour déterminer une seconde valeur de champ binaire, la seconde valeur de champ binaire indiquant au moins un décalage cyclique et/ou un indice de peigne; et pour configurer une configuration DMRS de liaison montante, la configuration DMRS de liaison montante comprenant la première valeur de champ binaire et la seconde valeur de champ binaire. L'émetteur-récepteur peut être configuré pour transmettre la configuration DMRS de liaison montante à un dispositif sans fil.
PCT/SE2018/050678 2017-10-27 2018-06-25 Signalisation de configuration de signal de référence de démodulation de liaison montante WO2019083426A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201762577939P 2017-10-27 2017-10-27
US62/577,939 2017-10-27

Publications (1)

Publication Number Publication Date
WO2019083426A1 true WO2019083426A1 (fr) 2019-05-02

Family

ID=62842184

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2018/050678 WO2019083426A1 (fr) 2017-10-27 2018-06-25 Signalisation de configuration de signal de référence de démodulation de liaison montante

Country Status (2)

Country Link
AR (1) AR113408A1 (fr)
WO (1) WO2019083426A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4214907A4 (fr) * 2020-10-06 2024-03-20 Huawei Tech Co Ltd Système et procédé pour générer un signal de référence à faible rapport de puissance moyenne de crête

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140036850A1 (en) * 2011-04-13 2014-02-06 Sharp Kabushiki Kaisha Wireless communication system, mobile station apparatus and base station apparatus
US20170289924A1 (en) * 2016-03-31 2017-10-05 Samsung Electronics Co., Ltd. Method and apparatus for transmitting uplink demodulation reference signals

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140036850A1 (en) * 2011-04-13 2014-02-06 Sharp Kabushiki Kaisha Wireless communication system, mobile station apparatus and base station apparatus
US20170289924A1 (en) * 2016-03-31 2017-10-05 Samsung Electronics Co., Ltd. Method and apparatus for transmitting uplink demodulation reference signals

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
HUAWEI ET AL: "Summary of email discussion [90-11] on sPDSCH/sPUSCH design", vol. RAN WG1, no. Prague, Czech Republic; 20171009 - 20171013, 8 October 2017 (2017-10-08), XP051340340, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN1/Docs/> [retrieved on 20171008] *
HUAWEI ET AL: "UL DMRS design for sPUSCH", vol. RAN WG1, no. Prague, Czech Republic; 20171009 - 20171013, 8 October 2017 (2017-10-08), XP051340330, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN1/Docs/> [retrieved on 20171008] *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4214907A4 (fr) * 2020-10-06 2024-03-20 Huawei Tech Co Ltd Système et procédé pour générer un signal de référence à faible rapport de puissance moyenne de crête

Also Published As

Publication number Publication date
AR113408A1 (es) 2020-04-29

Similar Documents

Publication Publication Date Title
JP7360486B2 (ja) ダウンリンク共有チャネルの性能向上のための方法およびシステム
KR102397166B1 (ko) 시간 영역 리소스 할당 표들의 선택
CN111630928B (zh) 用于随机接入期间数据传输中的msg3的多个tbs
US11456835B2 (en) Low overhead aperiodic triggering of multi-symbol SRS
US20210409178A1 (en) Implicit sounding reference signal aperiodic triggering offset
US11705984B2 (en) Method for determining demodulation reference signal for multiple access transmission
EP3888418B1 (fr) Fonctionnement d&#39;une unité centrale divisée de couche inférieure
WO2021126045A1 (fr) Procédés permettant à un dispositif sans fil à faible largeur de bande d&#39;accéder à une cellule nouvelle radio par l&#39;intermédiaire d&#39;un ensemble de ressources de commande large bande
CN113615109A (zh) 与无线通信网络中参考信号的配置有关的方法、设备和机器可读介质
JP2023509799A (ja) 低複雑度ユーザ機器のためのランダムアクセス
WO2023031794A1 (fr) Nombre accru de ports de signal de référence de démodulation
US20230396387A1 (en) Concept for Flexible SRS Bandwidth Adaptation
WO2019145834A1 (fr) Systèmes et procédés de mappage de ressources pour attribuer un message de dci sur de multiples porteuses composantes
WO2019083426A1 (fr) Signalisation de configuration de signal de référence de démodulation de liaison montante
US11757691B2 (en) Method and apparatus for multiple access transmission
WO2022215010A1 (fr) Peigne de transmission de signaux de référence de sondage de valeur 8
EP4320787A1 (fr) Répétition de signal de référence de sondage améliorée
WO2021091446A1 (fr) Indication de la relation spatiale pour srs
CN113169783A (zh) 从低层分割中央单元向无线电单元发送频率变化的波束权重
CN114557028A (zh) Lte-m和nb-iot的有效资源预留

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18738020

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18738020

Country of ref document: EP

Kind code of ref document: A1