WO2023211347A1 - États de déclenchement apériodiques inactifs pour économie d'énergie - Google Patents

États de déclenchement apériodiques inactifs pour économie d'énergie Download PDF

Info

Publication number
WO2023211347A1
WO2023211347A1 PCT/SE2023/050391 SE2023050391W WO2023211347A1 WO 2023211347 A1 WO2023211347 A1 WO 2023211347A1 SE 2023050391 W SE2023050391 W SE 2023050391W WO 2023211347 A1 WO2023211347 A1 WO 2023211347A1
Authority
WO
WIPO (PCT)
Prior art keywords
csi
trigger states
trigger
states
reporting
Prior art date
Application number
PCT/SE2023/050391
Other languages
English (en)
Inventor
Ajit Nimbalker
Ravikiran Nory
Sina MALEKI
Siva Muruganathan
Ilmiawan SHUBHI
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 WO2023211347A1 publication Critical patent/WO2023211347A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0023—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the signalling
    • H04L1/0026—Transmission of channel quality indication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0023—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the signalling
    • H04L1/0027—Scheduling of signalling, e.g. occurrence thereof

Definitions

  • the present disclosure relates to wireless communications, and in particular, to methods for employing inactive aperiodic trigger states for energy saving.
  • NR Third Generation Partnership Project
  • LTE long term evolution
  • NR will most likely consume more power compared to LTE, e.g., due to the higher bandwidth and more so due to introduction of additional elements such as 64 transmit (TX) / receive (RX) ports with associated digital radio frequency (RF) chains.
  • TX transmit
  • RX receive
  • RF digital radio frequency chains.
  • the network is expected to support a user equipment (UE) with its maximum capability (e.g., throughput, coverage, etc.), the network may need to use full configuration even when the maximum network support is rarely needed by the UEs.
  • UE user equipment
  • maximum capability e.g., throughput, coverage, etc.
  • an increased number of TX/RX ports also leads to an increase to the number of reference signals (e.g., channel state information reference signal (CSI-RS)) needed to be transmitted by the network (and to be measured by the UE) for a proper signal detection.
  • the additional TX/RX ports may result in another additional power consumption, i.e., to transmit a larger number of CSI-RS to the UEs.
  • the larger number of CSI-RS transmissions may also consume the valuable network resources.
  • the network may realize energy saving by applying antenna muting.
  • an NR gNB may deploy large antenna arrays with hundreds of antenna elements and up to 32 ports.
  • the energy cost associated with RF (PA and LNA), digital processing (BF), and baseband processing associated with such an array is high.
  • PA and LNA power amplifier
  • BF digital processing
  • baseband processing associated with such an array is high.
  • maintaining sufficient user and system performance may not require full antenna gNB array.
  • the gNB may then deactivate or mute parts of the antenna panel and transmit with a subset of antenna elements and transmission ports.
  • a CSI-RS resource may span 1, 2, or 4 orthogonal frequency division multiplexing (OFDM) symbols: one symbol for 1, 2, 4, 8, 12 ports; two symbols for 4, 8, 12, 16 ports; and four symbols for 24, 32 ports.
  • a CSI-RS resource may start at any symbol (0-13) within a slot: defined by a single start symbol for 1 symbol CSI-RS, 2 symbol CSI-RS, and 4 symbols with T- OCC span 4; or defined by two start symbol indices in the 4 symbol CSI-RS 2+2 with T-OCC span 2.
  • Components are mapped to frequency with granularity of component size, 1, 2, or 4 subcarriers. The same subcarriers are used across all symbols in a resource.
  • RE level multiplexing with TRS/DMRS is possible in the same OFDM symbol. In most cases RE level multiplexing with DMRS is anyway not possible.
  • Aperiodic CSI-RS transmission is a one-shot CSI-RS transmission that can be triggered by a gNB via Downlink Control Information (DCI) in any slot.
  • DCI Downlink Control Information
  • One-shot means that CSI-RS transmission only happens once per trigger in one slot.
  • the CSI-RS resources i. e. , the resource element locations which consist of subcarrier locations and OFDM symbol locations
  • the transmission of aperiodic CSI-RS is triggered via DCI. As shown in Table 1, aperiodic CSI-RS can be used for aperiodic CSI reporting.
  • the CSI-RS transmissions are preconfigured by higher layer signaling and the pre-configuration includes parameters such as periodicity and slot offset.
  • Periodic CSI-RS is controlled by higher layer signaling only. That is, the periodic CSI-RS transmission starts following Radio Resource Control (RRC) configuration following the configured parameters.
  • RRC Radio Resource Control
  • periodic CSI-RS can be used for periodic CSI reporting, semi-persistent CSI reporting and aperiodic CSI reporting.
  • Semi-Persistent CSI-RS transmission is similar to periodic CSI-RS, where resources for semi-persistent CSI-RS transmissions are preconfigured via higher layer signaling with parameters such as periodicity and slot offset. However, unlike periodic CSI-RS, a dynamic allocation activation signaling via a Medium Access Control (MAC) Control Element (CE) is needed to begin transmission of semi-persistent CSI-RS on the preconfigured resources. Furthermore, semi-persistent CSI-RS is transmitted for a limited time duration until the activated semi-persistent CSI-RS is deactivated via a deactivation signaling via a MAC CE. As shown in Table 1, semi -persistent CSI-RS can be used for semi-persistent CSI reporting and aperiodic CSI reporting.
  • MAC Medium Access Control
  • CE Medium Access Control Element
  • the network may configure CSI-RS with different settings (e.g., number of antenna ports, CSI-RS resources, etc.) and use the UE feedback (e.g., CSI, link quality, etc.) to assess the link conditions and make suitable scheduling decisions (e.g., number of ports, codebook to use, etc.) when scheduling the UE.
  • the network may also use different settings to identify if it can still serve the UE sufficiently well while at the same time reduce network energy cost (e.g., by reducing the number of antenna ports used for the scheduling data to the UE).
  • the network can trigger an aperiodic CSI-RS transmission and reporting via DCI 0 1 and/or DCI 0_2 using the below field (e.g., in DCI 0 1).
  • a UE in connected mode is configured with a first number of trigger states (e.g., 128) via RRC signaling.
  • the DCI field size for A-CSI trigger state indication is limited to 6 bits, implying only maximum of 64 trigger states can be active at a time and only these can be triggered via the DCI (e.g., via DCI 0_l/0_2).
  • a MAC CE is used for Aperiodic CSI trigger state selection to indicate the active trigger states.
  • the active trigger state budget is limited, and the trigger states are used for many purposes such as CSI measurement and reporting for link adaptation, beam management (including Ll-RSRP reporting, LI SINR reporting, etc.).
  • An example showing the split between Active and Inactive trigger states is shown in Figure 1.
  • the Aperiodic CSI Trigger State Subselection MAC CE is identified by a MAC subheader with LCID as specified in Figure 2. It has a variable size consisting of following fields:
  • Serving Cell ID which indicates the identity of the Serving Cell for which the MAC CE applies (length of the field is 5 bits).
  • BWP ID which indicates a DL BWP for which the MAC CE applies as the codepoint of the DCI bandwidth part indicator field as specified in 3GPP TS 38.212.
  • the length of the BWP ID field is 2 bits;
  • • - Ti indicates the selection status of the Aperiodic Trigger States configured within CSI-aperiodicTriggerStateList, as specified in 3GPP TS 38.331. To refers to the first trigger state within the list, Ti to the second one and so on. If the list does not contain entry with index i, MAC entity shall ignore the Ti field. The Ti field is set to 1 to indicate that the Aperiodic Trigger State i shall be mapped to the codepoint of the DCI CSI request field, as specified in 3 GPP TS 38.214.
  • the codepoint to which the Aperiodic Trigger State is mapped is determined by its ordinal position among all the Aperiodic Trigger States with Ti field set to 1, i.e., the first Aperiodic Trigger State with Ti field set to 1 shall be mapped to the codepoint value 1, second Aperiodic Trigger State with Ti field set to 1 shall be mapped to the codepoint value 2 and so on.
  • the maximum number of mapped Aperiodic Trigger States is 63.
  • R is a reserved bit, set to 0.
  • Certain aspects of the disclosure and their embodiments may provide solutions to some of the problems discussed above. For example, particular embodiments trigger CSI-RS transmission and CSI measurement/reporting using inactive trigger states using MAC-CE based triggering or using a DCI-based mechanism (e.g., group common DCI, etc.) that is different from the mechanism used for the active trigger states and/or with relaxed measurement/reporting framework.
  • a DCI-based mechanism e.g., group common DCI, etc.
  • a first aspect of the invention provides a method performed by a wireless device.
  • the method comprises obtaining an Aperiodic-Channel State Information, A-CSI, trigger state configuration comprising a first set of A-CSI trigger states, for which CSI reporting is triggered by a first mechanism, and a second set of A-CSI trigger states, for which CSI reporting is triggered by a second mechanism different from the first mechanism.
  • the method further comprises receiving a trigger for CSI reporting for an A-CSI trigger state from the second set of A-CSI trigger states and reporting CSI for the A-CSI trigger state.
  • a second aspect of the invention provides a method performed by a base station.
  • the method comprises configuring a wireless device with an Aperiodic-Channel State Information, A-CSI, trigger state configuration comprising a first set of A-CSI trigger states, for which CSI reporting is triggered by a first mechanism, and a second set of A-CSI trigger states, for which CSI reporting is triggered by a second mechanism different from the first mechanism.
  • the method further comprises transmitting a trigger for CSI reporting for an A-CSI trigger state from the second set of A-CSI trigger states and receiving CSI reporting for the A-CSI trigger state.
  • a third aspect of the invention provides a wireless device.
  • the wireless device is configured to, and/or comprising processing circuitry configured to, obtain an Aperiodic- Channel State Information, A-CSI, trigger state configuration comprising a first set of A-CSI trigger states, for which CSI reporting is triggered by a first mechanism, and a second set of A- CSI trigger states, for which CSI reporting is triggered by a second mechanism different from the first mechanism.
  • the wireless device is further configured to, and/or the processing circuitry is further configured to, receive a trigger for CSI reporting for an A-CSI trigger state from the second set of A-CSI trigger states and report CSI for the A-CSI trigger state.
  • a fourth aspect of the invention provides a base station.
  • the base station is configured to, and/or comprising processing circuitry configured to, configure a wireless device with an Aperiodic-Channel State Information, A-CSI, trigger state configuration comprising a first set of A-CSI trigger states, for which CSI reporting is triggered by a first mechanism, and a second set of A-CSI trigger states, for which CSI reporting is triggered by a second mechanism different from the first mechanism.
  • the base station is further configured to, and/or the processing circuitry is further configured to, transmit a trigger for CSI reporting for an A-CSI trigger state from the second set of A-CSI trigger states and receive CSI reporting for the A-CSI trigger state.
  • Figure 1 shows an example of active and inactive trigger states.
  • Figure 2 shows an aperiodic CSI Trigger State Subselection MAC CE.
  • Figure 3 shows an example of a common MAC CE in accordance with some embodiments.
  • Figure 4 shows an example of active and inactive trigger states in accordance with some embodiments.
  • Figure 5 illustrates a method performed by a wireless device according to some aspects.
  • Figure 6 illustrates a method performed by a network node according to some aspects.
  • Figure 7 shows an example of a communication system 700 in accordance with some embodiments.
  • FIG. 8 shows a UE 800 in accordance with some embodiments.
  • Figure 9 shows a network node 900 in accordance with some embodiments.
  • FIG 10 is a block diagram of a host 1000, which may be an embodiment of the host 716 of Figure 7, in accordance with various aspects described herein.
  • Figure 11 is a block diagram illustrating a virtualization environment 1100 in which functions implemented by some embodiments may be virtualized.
  • Figure 12 shows a communication diagram of a host 1202 communicating via a network node 1204 with a UE 1206 over a partially wireless connection in accordance with some embodiments.
  • the maximum number of active trigger states for CSI-RS triggering and measurement is limited. Most of the active trigger states are used for link maintenance/scheduling/RRM purposes such as link adaptation, mobility, etc.
  • a base station that wants to reduce its power consumption may not have sufficient trigger state budget to configure multiple hypotheses of CSI-RS configurations (e.g., 32/16/8 CSI-RS ports with different parameter settings such as different power offsets, etc.) that a UE can measure and report to assist base station power consumption reduction.
  • the alternative of increasing the number of simultaneous active states can increase UE measurement and processing complexity.
  • the UE has a first set of A-CSI trigger states (e.g., active trigger states) for which CSI triggering/report can be triggered by a DCI message only.
  • the UE has a second set of A-CSI trigger states (non-active trigger states) for which CSI triggering/report is triggered via a MAC CE, or using a DCI-based mechanism (e.g., group common DCI, etc.) that is different from the mechanism used for the first set of A-CSI trigger states.
  • the measurement/ reporting for the second set of trigger states may be different from that for the first set of trigger states (e.g., relaxed processing timeline, selective reporting, e.g., only if exceeds certain threshold).
  • the trigger states belong to a trigger state list that may have active trigger states and inactive trigger states.
  • the network may use inactive states to trigger CSI transmission/reporting according to CSI-RS configurations that may enable network energy saving (or enable network energy saving state adaptation) without reducing the number of configured active trigger states used for link maintenance/scheduling/RRM purposes for connected mode UEs.
  • the network can trigger certain CSI-RS configurations using the second set to assist network energy savings.
  • A-CSI trigger state and aperiodic trigger state may be interchangeably used herein.
  • a UE has a first set of A-CSI trigger states or aperiodic trigger states (e.g., active trigger states) for which CSI triggering/report can be triggered by a DCI message only.
  • the UE has a second set of A-CSI trigger states (non-active trigger states) for which CSI triggering/report is triggered via a MAC CE or using a DCI-based mechanism (e.g., group common DCI, etc.) that is different from the mechanism used for the first set of A-CSI trigger states.
  • the measurement/reporting for the second set of trigger states may be different from the first set of trigger states (e.g., relaxed processing timeline, selective reporting, e.g., only if exceeds certain threshold).
  • the network may use inactive states to trigger CSI-RS configurations that may enable network energy saving (or enable network energy saving state adaptation) without reducing the number of configured active trigger states used for link maintenance/scheduling/RRM purposes for connected mode UEs.
  • the network may trigger certain CSI-RS configurations using the second set to assist network energy savings.
  • Some embodiments include requesting CSI through inactive A-CSI trigger states.
  • the UE is configured with A-CSI trigger states.
  • the UE has a first set of A- CSI trigger states, and a CSI triggering/report associated with one or more states of the first set of A-CSI trigger states can be triggered by a DCI message only.
  • the UE has a second set of A- CSI trigger states, and a CSI triggering/report associated with one or more states of the second set of A-CSI trigger states can be triggered via a MAC CE or using a mechanism that is different from the mechanism used for the first set of A-CSI trigger states (e.g., using a group common DCI).
  • the first set of A-CSI trigger states are the trigger states indicated by the most recent MAC CE such as “Aperiodic CSI Trigger State Subselection MAC CE”.
  • the second set of A- CSI trigger states are based on at least the total A-CSI trigger states and the first set of A-CSI trigger states.
  • the second set of A-CSI trigger states may be a subset of total A-CSI trigger states that are not in the first set of A-CSI trigger states.
  • another MAC-CE mechanism may be used to select the A-CSI trigger states that are included in the second set.
  • A-CSI trigger states belonging to the second set may be configured along with configuration of each CSI trigger state.
  • a common MAC CE is used to both activate aperiodic trigger states (similar to the functionality of ‘Aperiodic CSI Trigger State Subselection MAC CE’ defined in 3GPP TS 38.321 and discussed above) and to trigger a CSI report associated with one or more inactive A-CSI trigger states.
  • a MAC CE is shown in Figure 3.
  • the MAC CE is used to activate aperiodic trigger states. That is, when S field is set to the first value, the Ti fields set to 1 are mapped to the codepoints of the DCI CSI request field.
  • the MAC CE is used to trigger a CSI report associated with one or more inactive A-CSI trigger states.
  • S is set to the second value, the MAC CE directly triggers the CSI reports corresponding to the Ti fields set to 1 without requiring any DCI triggering.
  • the above MAC CE may be a new MAC CE introduced into 3GPP specifications.
  • the above MAC CE may be a modified version of the ‘Aperiodic CSI Trigger State Subselection MAC CE’ by newly introducing the S field in place of the R field.
  • the second set of states may be useful for requesting CSI for potential configurations that may be beneficial for network energy savings. Because these trigger states are not beneficial for active scheduling of the UE yet, these are not typically active. However, the network may on a sparse basis trigger and receive a UE report on a potential setting with inactive trigger state that can aid network energy saving. This can be done by a new MAC CE or a new LI signaling, e.g., on a relaxed basis (relaxed UE processing time, etc.), and report only if the measurement yields a beneficial outcome (CSI is better than a configured threshold value), or reporting the CSI via an uplink MAC CE) so that any additional impact of CSI measurement/processing on UE is minimized.
  • a one-shot PUSCH resources for uplink transmission of UE report may also be indicated by the trigger.
  • the first set is ‘Active trigger states’
  • the second set can be the trigger states shown in the middle.
  • the second set of trigger states can be triggered using a new MAC-CE, or using a DCI such as a power-saving DCI or a group common DCI, that the UE can process in a relaxed manner compared to the regular CSI processing based on Active trigger states.
  • the network may send RRC reconfiguration or MAC CE updating the active/inactive trigger states.
  • the UE receives configuration of A-CSI trigger states, with the first and second set, and additionally the UE receives a configuration for a group-common DCI which is intended, e.g., for network energy savings purposes.
  • the group-common DCI can be associated with a USS or a CSS, with CSS being the preferred SS such that the DCI can be transmitted to multiple UEs at the same time and save resources for the network.
  • the UE additionally may receive a configuration of start and length of a bitfield which is used to trigger A-CSI trigger states belonging to the second set.
  • the size of the bitfield may be obtained based on a preconfigured criteria, e.g., based on the number of configured states in the second set.
  • the UE may additionally receive a configuration of start and length of the bitfield which determines the resources, e.g., Time/Frequency over which the UE can report the measured CSI. Similar approaches can also be used to define the relevant bitfields in a MAC-CE mechanism.
  • the UE indicates a capability to measure and report CSIs associated with inactive trigger states, and in response the UE receives one or more configurations according to the methods disclosed herein.
  • the UE may do so to help the network to adopt appropriate energy savings measure, e.g., antenna adaptation, and furthermore, avoid reducing its performance if the network decides to adopt an energy saving measure.
  • additional restriction may also be explicitly added.
  • the A- CSI trigger states included in the first set of the A-CSI trigger state should not be included in the second set of the A-CSI trigger state.
  • the UE may derive the second set of A-CSI trigger states based on the number of A-CSI trigger states in the first set of A-CSI trigger states and the number of available codepoints for the A-CSI triggering.
  • the UE may be configured with a total of 16 A-CSI trigger states where 8 of the A-CSI trigger states is configured as the first set of A-CSI trigger state (e.g., set of active trigger states), e.g., the A-CSI trigger state with index 0, 1, 2, 3, 8, 9, 10, and 11.
  • the codepoint of 000, 001, 010, 011, 100, 101, 110, and 111 may refer to the A-CSI trigger state with the index of 4, 5, 6, 7, 12, 13, 14, and 15, respectively.
  • the active A-CSI trigger states may be partitioned into two subsets, wherein a first subset of trigger states follow the legacy trigger/measurement/reporting, while the second subset of trigger states may follow relaxed handling relatively to the first subset of trigger states. This enables a UE to reduce its power consumption/processing complexity because the effective number of active A-CSI trigger states requiring legacy handling are reduced.
  • the first set and second set of trigger states are indicated using the same field in the DCI, e.g., CSI request - 0, 1, 2, 3, 4, 5, or 6 bits determined by higher layer parameter reportTriggerSize.
  • the report trigger size may be configured such that it can accommodate both the first and second sets.
  • FIG. 5 illustrates a method 500 performed by a wireless device (e.g., a UE) according to some aspects.
  • the method 500 comprises obtaining S510 an Aperiodic-Channel State Information, A-CSI, trigger state configuration comprising a first set of A-CSI trigger states, for which CSI reporting is triggered by a first mechanism, and a second set of A-CSI trigger states, for which CSI reporting is triggered by a second mechanism different from the first mechanism.
  • the method 500 further comprises receiving S520 a trigger for CSI reporting for an A-CSI trigger state from the second set of A-CSI trigger states and reporting S530 CSI for the A-CSI trigger state.
  • FIG. 6 illustrates a method 600 performed by a network node (e.g., a base station) according to some aspects.
  • the method 600 comprises configuring S610 a wireless device with an Aperiodic-Channel State Information, A-CSI, trigger state configuration comprising a first set of A-CSI trigger states, for which CSI reporting is triggered by a first mechanism, and a second set of A-CSI trigger states, for which CSI reporting is triggered by a second mechanism different from the first mechanism.
  • the method 600 further comprises transmitting S620 a trigger for CSI reporting for an A-CSI trigger state from the second set of A-CSI trigger states and receiving S630 CSI reporting for the A-CSI trigger state.
  • the communication system 700 includes a telecommunication network 702 that includes an access network 704, such as a radio access network (RAN), and a core network 706, which includes one or more core network nodes 708.
  • the access network 704 includes one or more access network nodes, such as network nodes 710a and 710b (one or more of which may be generally referred to as network nodes 710), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point.
  • 3GPP 3rd Generation Partnership Project
  • the network nodes 710 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 712a, 712b, 712c, and 712d (one or more of which may be generally referred to as UEs 712) to the core network 706 over one or more wireless connections.
  • UE user equipment
  • Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors.
  • the communication system 700 may include any number of wired or wireless networks, network nodes, UEs, 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.
  • the communication system 700 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs 712 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 710 and other communication devices.
  • the network nodes 710 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 712 and/or with other network nodes or equipment in the telecommunication network 702 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 702.
  • the core network 706 connects the network nodes 710 to one or more hosts, such as host 716. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts.
  • the core network 706 includes one more core network nodes (e.g., core network node 708) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 708.
  • Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).
  • MSC Mobile Switching Center
  • MME Mobility Management Entity
  • HSS Home Subscriber Server
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • AUSF Authentication Server Function
  • SIDF Subscription Identifier De-concealing function
  • UDM Unified Data Management
  • SEPP Security Edge Protection Proxy
  • NEF Network Exposure Function
  • UPF User Plane Function
  • the host 716 may be under the ownership or control of a service provider other than an operator or provider of the access network 704 and/or the telecommunication network 702, and may be operated by the service provider or on behalf of the service provider.
  • the host 716 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.
  • the communication system 700 of Figure 7 enables connectivity between the UEs, network nodes, and hosts.
  • the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • the telecommunication network 702 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 702 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 702. For example, the telecommunications network 702 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)/Massive loT services to yet further UEs.
  • URLLC Ultra Reliable Low Latency Communication
  • eMBB Enhanced Mobile Broadband
  • mMTC Massive Machine Type Communication
  • the UEs 712 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network 704 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 704.
  • a UE may be configured for operating in single- or multi-RAT or multi-standard mode.
  • a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).
  • MR-DC multi-radio dual connectivity
  • the hub 714 communicates with the access network 704 to facilitate indirect communication between one or more UEs (e.g., UE 712c and/or 712d) and network nodes (e.g., network node 710b).
  • the hub 714 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs.
  • the hub 714 may be a broadband router enabling access to the core network 706 for the UEs.
  • the hub 714 may be a controller that sends commands or instructions to one or more actuators in the UEs.
  • the hub 714 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data.
  • the hub 714 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 714 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 714 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • the hub 714 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.
  • the hub 714 may have a constant/persistent or intermittent connection to the network node 710b.
  • the hub 714 may also allow for a different communication scheme and/or schedule between the hub 714 and UEs (e.g., UE 712c and/or 712d), and between the hub 714 and the core network 706.
  • the hub 714 is connected to the core network 706 and/or one or more UEs via a wired connection.
  • the hub 714 may be configured to connect to an M2M service provider over the access network 704 and/or to another UE over a direct connection.
  • UEs may establish a wireless connection with the network nodes 710 while still connected via the hub 714 via a wired or wireless connection.
  • the hub 714 may be a dedicated hub - that is, a hub whose primary function is to route communications to/from the UEs from/to the network node 710b.
  • the hub 714 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 710b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
  • a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs.
  • a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc.
  • VoIP voice over IP
  • LME laptop-embedded equipment
  • LME laptop-mounted equipment
  • CPE wireless customer-premise equipment
  • UEs identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • 3GPP 3rd Generation Partnership Project
  • NB-IoT narrow band internet of things
  • MTC machine type communication
  • eMTC enhanced MTC
  • a UE may support device-to-device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle- to-everything (V2X).
  • D2D device-to-device
  • DSRC Dedicated Short-Range Communication
  • V2V vehicle-to-vehicle
  • V2I vehicle-to-infrastructure
  • V2X vehicle- to-everything
  • a 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
  • the UE 800 includes processing circuitry 802 that is operatively coupled via a bus 804 to an input/output interface 806, a power source 808, a memory 810, a communication interface 812, and/or any other component, or any combination thereof.
  • Certain UEs may utilize all or a subset of the components shown in Figure 8. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
  • the processing circuitry 802 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 810.
  • the processing circuitry 802 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field- programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, 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 802 may include multiple central processing units (CPUs).
  • the input/ output interface 806 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices.
  • Examples of an output device include 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.
  • An input device may allow a user to capture information into the UE 800.
  • Examples of an input device 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, a biometric sensor, etc., or any combination thereof.
  • An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.
  • USB Universal Serial Bus
  • the power source 808 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used.
  • the power source 808 may further include power circuitry for delivering power from the power source 808 itself, and/or an external power source, to the various parts of the UE 800 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 808.
  • Power circuitry may perform any formatting, converting, or other modification to the power from the power source 808 to make the power suitable for the respective components of the UE 800 to which power is supplied.
  • the memory 810 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable readonly memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth.
  • the memory 810 includes one or more application programs 814, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 816.
  • the memory 810 may store, for use by the UE 800, any of a variety of various operating systems or combinations of operating systems.
  • the memory 810 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and/or ISIM, other memory, or any combination thereof.
  • RAID redundant array of independent disks
  • HD-DVD high-density digital versatile disc
  • HDDS holographic digital data storage
  • DIMM external mini-dual in-line memory module
  • SDRAM synchronous dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • the UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’
  • eUICC embedded UICC
  • iUICC integrated UICC
  • SIM card removable UICC commonly known as ‘SIM card.’
  • the memory 810 may allow the UE 800 to access instructions, application programs and 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 as or in the memory 810, which may be or comprise a device-readable storage medium.
  • the processing circuitry 802 may be configured to communicate with an access network or other network using the communication interface 812.
  • the communication interface 812 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 822.
  • the communication interface 812 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network).
  • Each transceiver may include a transmitter 818 and/or a receiver 820 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).
  • the transmitter 818 and receiver 820 may be coupled to one or more antennas (e.g., antenna 822) and may share circuit components, software or firmware, or alternatively be implemented separately.
  • communication functions of the communication interface 812 may include cellular communication, Wi-Fi communication, LPWAN communication, 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.
  • GPS global positioning system
  • Communications may be implemented in according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol/intemet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.
  • CDMA Code Division Multiplexing Access
  • WCDMA Wideband Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GSM Global System for Mobile communications
  • LTE Long Term Evolution
  • NR New Radio
  • UMTS Worldwide Interoperability for Microwave Access
  • WiMax Ethernet
  • TCP/IP transmission control protocol/intemet protocol
  • SONET synchronous optical networking
  • ATM Asynchronous Transfer Mode
  • QUIC Hypertext Transfer Protocol
  • HTTP Hypertext Transfer Protocol
  • a UE may provide an output of data captured by its sensors, through its communication interface 812, via a wireless connection to a network node.
  • Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE.
  • the output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).
  • a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection.
  • the states of the actuator, the motor, or the switch may change.
  • the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.
  • a UE when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare.
  • loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-t
  • AR Augmented
  • a UE in the form of an loT device comprises circuitry and/or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 800 shown in Figure 8.
  • a UE 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 UE and/or a network node.
  • the UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device.
  • the UE may implement the 3GPP NB-IoT standard.
  • a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • any number of UEs may be used together with respect to a single use case.
  • a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone.
  • the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed.
  • the first and/or the second UE can also include more than one of the functionalities described above.
  • a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.
  • network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication network.
  • network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)).
  • APs access points
  • BSs base stations
  • eNBs evolved Node Bs
  • gNBs NR NodeBs
  • Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may 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
  • Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
  • DAS distributed antenna system
  • network nodes include multiple transmission point (multi-TRP) 5G access nodes, 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), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs).
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • OFDM Operation and Maintenance
  • OSS Operations Support System
  • SON Self-Organizing Network
  • positioning nodes e.g., Evolved Serving Mobile Location Centers (E-SMLCs)
  • the network node 900 includes a processing circuitry 902, a memory 904, a communication interface 906, and a power source 908.
  • the network node 900 may be composed of multiple physically separate components (e.g., aNodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components.
  • the network node 900 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 NodeBs.
  • each unique NodeB and RNC pair may in some instances be considered a single separate network node.
  • the network node 900 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 904 for different RATs) and some components may be reused (e.g., a same antenna 910 may be shared by different RATs).
  • the network node 900 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 900, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) 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 900.
  • RFID Radio Frequency Identification
  • the processing circuitry 902 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 900 components, such as the memory 904, to provide network node 900 functionality.
  • the processing circuitry 902 includes a system on a chip (SOC). In some embodiments, the processing circuitry 902 includes one or more of radio frequency (RF) transceiver circuitry 912 and baseband processing circuitry 914. In some embodiments, the radio frequency (RF) transceiver circuitry 912 and the baseband processing circuitry 914 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 912 and baseband processing circuitry 914 may be on the same chip or set of chips, boards, or units.
  • SOC system on a chip
  • the processing circuitry 902 includes one or more of radio frequency (RF) transceiver circuitry 912 and baseband processing circuitry 914.
  • the radio frequency (RF) transceiver circuitry 912 and the baseband processing circuitry 914 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of
  • the memory 904 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 the processing circuitry 902.
  • 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-
  • the memory 904 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry 902 and utilized by the network node 900.
  • the memory 904 may be used to store any calculations made by the processing circuitry 902 and/or any data received via the communication interface 906.
  • the processing circuitry 902 and memory 904 is integrated.
  • the communication interface 906 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface 906 comprises port(s)/terminal(s) 916 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface 906 also includes radio front-end circuitry 918 that may be coupled to, or in certain embodiments a part of, the antenna 910. Radio front-end circuitry 918 comprises filters 920 and amplifiers 922.
  • the radio front-end circuitry 918 may be connected to an antenna 910 and processing circuitry 902.
  • the radio front-end circuitry may be configured to condition signals communicated between antenna 910 and processing circuitry 902.
  • the radio front-end circuitry 918 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection.
  • the radio front-end circuitry 918 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 920 and/or amplifiers 922.
  • the radio signal may then be transmitted via the antenna 910.
  • the antenna 910 may collect radio signals which are then converted into digital data by the radio front-end circuitry 918.
  • the digital data may be passed to the processing circuitry 902.
  • the communication interface may comprise different components and/or different combinations of components.
  • the network node 900 does not include separate radio front-end circuitry 918, instead, the processing circuitry 902 includes radio front-end circuitry and is connected to the antenna 910. Similarly, in some embodiments, all or some of the RF transceiver circuitry 912 is part of the communication interface 906. In still other embodiments, the communication interface 906 includes one or more ports or terminals 916, the radio front-end circuitry 918, and the RF transceiver circuitry 912, as part of a radio unit (not shown), and the communication interface 906 communicates with the baseband processing circuitry 914, which is part of a digital unit (not shown).
  • the antenna 910 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna 910 may be coupled to the radio front-end circuitry 918 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • the antenna 910 is separate from the network node 900 and connectable to the network node 900 through an interface or port.
  • the antenna 910, communication interface 906, and/or the processing circuitry 902 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment. Similarly, the antenna 910, the communication interface 906, and/or the processing circuitry 902 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment.
  • the power source 908 provides power to the various components of network node 900 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source 908 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 900 with power for performing the functionality described herein.
  • the network node 900 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 908.
  • the power source 908 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.
  • Embodiments of the network node 900 may include additional components beyond those shown in Figure 9 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.
  • the network node 900 may include user interface equipment to allow input of information into the network node 900 and to allow output of information from the network node 900. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 900.
  • the host 1000 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm.
  • the host 1000 may provide one or more services to one or more UEs.
  • the host 1000 includes processing circuitry 1002 that is operatively coupled via a bus 1004 to an input/output interface 1006, a network interface 1008, a power source 1010, and a memory 1012.
  • processing circuitry 1002 that is operatively coupled via a bus 1004 to an input/output interface 1006, a network interface 1008, a power source 1010, and a memory 1012.
  • Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 8 and 9, such that the descriptions thereof are generally applicable to the corresponding components of host 1000.
  • the memory 1012 may include one or more computer programs including one or more host application programs 1014 and data 1016, which may include user data, e.g., data generated by a UE for the host 1000 or data generated by the host 1000 for a UE.
  • Embodiments of the host 1000 may utilize only a subset or all of the components shown.
  • the host application programs 1014 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems).
  • the host application programs 1014 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network.
  • the host 1000 may select and/or indicate a different host for over-the-top services for a UE.
  • the host application programs 1014 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.
  • HLS HTTP Live Streaming
  • RTMP Real-Time Messaging Protocol
  • RTSP Real-Time Streaming Protocol
  • MPEG-DASH Dynamic Adaptive Streaming over HTTP
  • 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 any device described herein, 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.
  • Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1100 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host.
  • VMs virtual machines
  • the virtual node does not require radio connectivity (e.g., a core network node or host)
  • the node may be entirely virtualized.
  • Applications 1102 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Hardware 1104 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth.
  • Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1106 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1108a and 1108b (one or more of which may be generally referred to as VMs 1108), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein.
  • the virtualization layer 1106 may present a virtual operating platform that appears like networking hardware to the VMs 1108.
  • the VMs 1108 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1106.
  • a virtualization layer 1106 Different embodiments of the instance of a virtual appliance 1102 may be implemented on one or more of VMs 1108, and the implementations may be made in different ways.
  • Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). 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.
  • NFV network function virtualization
  • a VM 1108 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 the VMs 1108, and that part of hardware 1104 that executes that VM be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate virtual network elements.
  • a virtual network function is responsible for handling specific network functions that run in one or more VMs 1108 on top of the hardware 1104 and corresponds to the application 1102.
  • Hardware 1104 may be implemented in a standalone network node with generic or specific components. Hardware 1104 may implement some functions via virtualization. Alternatively, hardware 1104 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1110, which, among others, oversees lifecycle management of applications 1102.
  • hardware 1104 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes 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.
  • some signaling can be provided with the use of a control system 1112 which may alternatively be used for communication between hardware nodes and radio units.
  • UE such as a UE 712a of Figure 7 and/or UE 800 of Figure 8
  • network node such as network node 710a of Figure 7 and/or network node 900 of Figure 9
  • host such as host 716 of Figure 7 and/or host 1000 of Figure 10.
  • host 1202 Like host 1000, embodiments of host 1202 include hardware, such as a communication interface, processing circuitry, and memory.
  • the host 1202 also includes software, which is stored in or accessible by the host 1202 and executable by the processing circuitry.
  • the software includes a host application that may be operable to provide a service to a remote user, such as the UE 1206 connecting via an over-the-top (OTT) connection 1250 extending between the UE 1206 and host 1202.
  • OTT over-the-top
  • a host application may provide user data which is transmitted using the OTT connection 1250.
  • the network node 1204 includes hardware enabling it to communicate with the host 1202 and UE 1206.
  • the connection 1260 may be direct or pass through a core network (like core network 706 of Figure 7) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks.
  • a core network like core network 706 of Figure 7
  • an intermediate network may be a backbone network or the Internet.
  • the UE 1206 includes hardware and software, which is stored in or accessible by UE 1206 and executable by the UE’s processing circuitry.
  • the software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 1206 with the support of the host 1202.
  • a client application such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 1206 with the support of the host 1202.
  • an executing host application may communicate with the executing client application via the OTT connection 1250 terminating at the UE 1206 and host 1202.
  • the UE's client application may receive request data from the host's host application and provide user data in response to the request data.
  • the OTT connection 1250 may transfer both the request data and the user data.
  • the UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT
  • the OTT connection 1250 may extend via a connection 1260 between the host 1202 and the network node 1204 and via a wireless connection 1270 between the network node 1204 and the UE 1206 to provide the connection between the host 1202 and the UE 1206.
  • the connection 1260 and wireless connection 1270, over which the OTT connection 1250 may be provided, have been drawn abstractly to illustrate the communication between the host 1202 and the UE 1206 via the network node 1204, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • the host 1202 provides user data, which may be performed by executing a host application.
  • the user data is associated with a particular human user interacting with the UE 1206.
  • the user data is associated with a UE 1206 that shares data with the host 1202 without explicit human interaction.
  • the host 1202 initiates a transmission carrying the user data towards the UE 1206.
  • the host 1202 may initiate the transmission responsive to a request transmitted by the UE 1206.
  • the request may be caused by human interaction with the UE 1206 or by operation of the client application executing on the UE 1206.
  • the transmission may pass via the network node 1204, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1212, the network node 1204 transmits to the UE 1206 the user data that was carried in the transmission that the host 1202 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1214, the UE 1206 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1206 associated with the host application executed by the host 1202.
  • the UE 1206 executes a client application which provides user data to the host 1202.
  • the user data may be provided in reaction or response to the data received from the host 1202.
  • the UE 1206 may provide user data, which may be performed by executing the client application.
  • the client application may further consider user input received from the user via an input/output interface of the UE 1206. Regardless of the specific manner in which the user data was provided, the UE 1206 initiates, in step 1218, transmission of the user data towards the host 1202 via the network node 1204.
  • the network node 1204 receives user data from the UE 1206 and initiates transmission of the received user data towards the host 1202.
  • the host 1202 receives the user data carried in the transmission initiated by the UE 1206.
  • factory status information may be collected and analyzed by the host 1202.
  • the host 1202 may process audio and video data which may have been retrieved from a UE for use in creating maps.
  • the host 1202 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights).
  • the host 1202 may store surveillance video uploaded by a UE.
  • the host 1202 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs.
  • the host 1202 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and/or transmitting data.
  • 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.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 1202 and/or UE 1206.
  • sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1250 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 may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 1250 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 1204. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 1202.
  • the measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1250 while monitoring propagation times, errors, etc.
  • computing devices described herein may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information 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 may process information 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.
  • computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components.
  • a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface.
  • non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.
  • processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium.
  • some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner.
  • the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and/or by end users and a wireless network generally.
  • a method performed by a wireless device comprising:
  • an A-CSI trigger state configuration comprising a first set of A-CSI trigger states for which CSI triggering/report is triggered by a DCI message only and a second set of A-CSI trigger states for which CSI triggering/report is triggered via a mechanism different from a mechanism used for the first set of A-CSI trigger states;
  • a method performed by a wireless device comprising:
  • a method performed by a base station comprising:
  • A-CSI trigger state configuration comprising a first set of A-CSI trigger states for which CSI triggering/report is triggered by a DCI message only and a second set of A-CSI trigger states for which CSI triggering/report is triggered via a mechanism different from a mechanism used for the first set of A-CSI trigger states;
  • a method performed by a base station comprising:
  • a mobile terminal comprising:
  • - power supply circuitry configured to supply power to the wireless device.
  • a base station comprising:
  • a user equipment comprising:
  • radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry;
  • processing circuitry being configured to perform any of the steps of any of the Group A embodiments;
  • an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry
  • a communication system including a host computer comprising:
  • UE user equipment
  • the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.
  • the communication system of the pervious embodiment further including the base station.
  • the communication system of the previous 3 embodiments wherein:
  • the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data
  • the UE comprises processing circuitry configured to execute a client application associated with the host application. 22.
  • the host computer initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any of the Group B embodiments.
  • a user equipment configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to performs any of the previous 3 embodiments.
  • a communication system including a host computer comprising:
  • UE user equipment
  • the UE comprises a radio interface and processing circuitry, the UE’s components configured to perform any of the steps of any of the Group A embodiments.
  • the cellular network further includes a base station configured to communicate with the UE.
  • the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data
  • a communication system including a host computer comprising:
  • a - communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station
  • the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform any of the steps of any of the Group A embodiments.
  • the communication system of the previous embodiment further including the UE.
  • the communication system of the previous 2 embodiments further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.
  • the communication system of the previous 3 embodiments wherein:
  • the processing circuitry of the host computer is configured to execute a host application
  • the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.
  • the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; and the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.
  • the host computer receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.
  • the user data to be transmitted is provided by the client application in response to the input data.
  • a communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.
  • UE user equipment
  • the communication system of the previous embodiment further including the base station. 42.
  • the communication system of the previous 2 embodiments further including the UE, wherein the UE is configured to communicate with the base station.
  • the processing circuitry of the host computer is configured to execute a host application
  • the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.
  • the host computer receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.

Landscapes

  • Engineering & Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne des procédés, un dispositif sans fil et une station de base pour l'utilisation d'états de déclenchement apériodiques inactifs pour l'économie d'énergie. Un aspect de l'invention propose un procédé exécuté par un dispositif sans fil. Le procédé consiste à obtenir une configuration d'états de déclenchement d'A-CSI (informations d'états de canal apériodiques) comprenant un premier ensemble d'états de déclenchement d'A-CSI, pour lesquels le rapport CSI est déclenché par un premier mécanisme, et un deuxième ensemble d'états de déclenchement d'A-CSI, pour lesquels le rapport CSI est déclenché par un deuxième mécanisme différent du premier mécanisme. Le procédé comprend en outre la réception d'un déclencheur de rapport CSI pour un état de déclenchement d'A-CSI à partir du deuxième ensemble d'états de déclenchement d'A-CSI et le rapport CSI pour l'état de déclenchement d'A-CSI.
PCT/SE2023/050391 2022-04-29 2023-04-27 États de déclenchement apériodiques inactifs pour économie d'énergie WO2023211347A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202263363829P 2022-04-29 2022-04-29
US63/363,829 2022-04-29

Publications (1)

Publication Number Publication Date
WO2023211347A1 true WO2023211347A1 (fr) 2023-11-02

Family

ID=86286366

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2023/050391 WO2023211347A1 (fr) 2022-04-29 2023-04-27 États de déclenchement apériodiques inactifs pour économie d'énergie

Country Status (1)

Country Link
WO (1) WO2023211347A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021098057A1 (fr) * 2020-02-14 2021-05-27 Zte Corporation Conception et configuration de signalisations de référence
WO2021149837A1 (fr) * 2020-01-21 2021-07-29 Sharp Kabushiki Kaisha Appareil terminal, appareil de station de base, et procédé de communication
WO2022087564A1 (fr) * 2020-10-22 2022-04-28 Qualcomm Incorporated Mesures de signaux de référence apériodiques pour de multiples points d'émission et de réception

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021149837A1 (fr) * 2020-01-21 2021-07-29 Sharp Kabushiki Kaisha Appareil terminal, appareil de station de base, et procédé de communication
WO2021098057A1 (fr) * 2020-02-14 2021-05-27 Zte Corporation Conception et configuration de signalisations de référence
WO2022087564A1 (fr) * 2020-10-22 2022-04-28 Qualcomm Incorporated Mesures de signaux de référence apériodiques pour de multiples points d'émission et de réception

Non-Patent Citations (6)

* Cited by examiner, † Cited by third party
Title
3GPP TS 38.212
3GPP TS 38.214
3GPP TS 38.321
3GPP TS 38.331
ERICSSON: "On MAC CE design for eURLLC", vol. RAN WG2, no. Electronic meeting; 20200224 - 20200306, 13 February 2020 (2020-02-13), XP051848603, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG2_RL2/TSGR2_109_e/Docs/R2-2000799.zip R2-2000799 on MAC CE design for eURLLC.docx> [retrieved on 20200213] *
ERICSSON: "Summary of CSI reporting v1", vol. RAN WG1, no. Athens, Greece; 20180226 - 20180302, 26 February 2018 (2018-02-26), XP051398396, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fran/WG1%5FRL1/TSGR1%5F92/Docs/> [retrieved on 20180226] *

Similar Documents

Publication Publication Date Title
WO2023209135A1 (fr) Indication de configuration de transmission dans un réseau de communication
WO2023152180A1 (fr) Interface de liaison montante d&#39;unité radio à entrées multiples et sorties multiples massives
WO2023211347A1 (fr) États de déclenchement apériodiques inactifs pour économie d&#39;énergie
WO2024152307A1 (fr) Procédé et appareils pour la transmission sans fil
WO2024138619A1 (fr) Procédés et appareils de communication sans fil
WO2024125362A1 (fr) Procédé et appareil de commande de liaison de communication entre dispositifs de communication
US20240340939A1 (en) Machine learning assisted user prioritization method for asynchronous resource allocation problems
US20240334226A1 (en) Early radio measurement relaxation reporting
US20240250725A1 (en) Adaptive hybrid precoding strategy for cell-free massive multiple input multiple output
US20240259921A1 (en) Signalling Approaches for Disaster PLMNS
WO2024040388A1 (fr) Procédé et appareil de transmission de données
WO2024210787A1 (fr) Informations de capacité d&#39;équipement utilisateur relatives à un temps de syntonisation de fréquence radio
WO2024209399A1 (fr) Motifs de saut de fréquence de prs et de srs et configuration d&#39;intervalle de mesure et de ppw associée dans le positionnement
WO2023095093A1 (fr) Signalisation mac ce destinée à supporter des fonctionnements à la fois conjoints et séparés de tci dl/ul
WO2024218713A1 (fr) Interface pour partitionner des fonctions de réseau en bande de base
WO2024171164A1 (fr) Configuration de saut de fréquence via une bande passante (bwp)
WO2024141989A1 (fr) Amplification de puissance adaptative pour signal de référence de sondage
WO2024033731A1 (fr) Rapport de faisceau basé sur un groupe pour une transmission et une réception simultanées à panneaux multiples
WO2023166448A1 (fr) Rapport de mesurage b1/a4 optimisé
WO2024035327A1 (fr) Économies d&#39;énergie de nœud de réseau par l&#39;intermédiaire d&#39;un mécanisme de réponse d&#39;accès aléatoire flexible
WO2023073677A2 (fr) Mesures dans un réseau de communication
WO2024210805A1 (fr) Systèmes et procédés de négociation d&#39;informations de communication sensible au temps
WO2024157177A1 (fr) Procédés et nœuds pour indication de puissance de sortie srs
WO2024028838A1 (fr) Économie d&#39;énergie de réseau dans un ng-ran scindé
WO2023152043A1 (fr) Mesure et notification efficaces de l1-rsrp entre cellules

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: 23721036

Country of ref document: EP

Kind code of ref document: A1