MULTIPLE DRX CONFIGURATIONS WITH TRAFFIC FLOW INFORMATION

Systems and methods for signaling of traffic flow information for Discontinuous Reception (DRX) configuration are provided. A method of operating a UE for determining a flow type includes: receiving a configuration of flow identify information with an association between one or more of: Downlink Control Information (DCIs); Radio Network Temporary Identifier (RNTIs); a combination of fields; with one or more DRX configurations; monitoring a Physical Downlink Control Channel (PDCCH) in DRX Active Time; in response to receiving a PDCCH with DCI indication of a flow type, identifying the DRX configuration k associated to the DCI indication; and starting or restarting a corresponding timer in the next symbol after PDCCH reception. In this way, signaling for a flow type, DRX configuration, or DRX parameter value indication from a gNB to a UE can be provided, in order to optimize multiple DRX cycle configurations per Serving Cell, where one or more of the configurations are active simultaneously.

TECHNICAL FIELD

The present disclosure relates generally to Discontinuous Reception (DRX) configurations.

BACKGROUND

The present disclosure relates to the concepts of Discontinuous Reception (DRX), Extended Reality (XR) applications (in general, any type of service) whose traffic comprises multiple traffic flows, as well as Layer 1 signaling for traffic scheduling. A summary of DRX operation is provided and then a description of the specifics of XR traffic relevant to the present disclosure is provided. Additionally, background information regarding signaling at Layer 1 to schedule data traffic is presented with a focus on Physical Downlink Control Channel (PDCCH) and Downlink Control Information (DCI).

DRX is a mechanism which enables the User Equipment (UE) to save energy by not monitoring the Downlink (DL) during certain periods of time, when data traffic is not expected at the UE. The DRX framework consists of two different types of DRX cycles with different periods: a long DRX cycle and an optional short DRX cycle. In principle, the short DRX cycle results in the UE monitoring the DL more often than when the UE operates according to the long DRX cycle. Entering the long or short DRX cycles occurs as follows. If the short DRX cycle is not configured, the UE enters the long DRX cycle after the inactivity timer expires, i.e., when there are no DL or Uplink (UL) transmissions for a period of time. If the optional short DRX cycle is configured, the UE enters this cycle after the DRX inactivity timer expires. If the short DRX cycle is configured and the short cycle timer expires, the UE enters the long DRX cycle.

DRX is controlled by the following main parameters (additional details can be found in 3GPP, TS 38.321, V16.5.0 (2021 June), Section 5.7 Discontinuous Reception (DRX), referred to hereinafter as [1]):drx-onDurationTimer: the duration at the beginning of a DRX cycle;drx-SlotOffset: the delay before starting the drx-onDurationTimer;drx-InactivityTimer: the duration after the Physical Downlink Control Channel (PDCCH) occasion in which a PDCCH indicates a new UL or DL transmission for the Medium Access Control (MAC) entity;drx-RetransmissionTimerDL (per DL Hybrid Automatic Repeat Request (HARQ) process except for the broadcast process): the maximum duration until a DL retransmission is received;drx-RetransmissionTimerUL (per UL HARQ process): the maximum duration until a grant for UL retransmission is received;drx-LongCycleStartOffset: the Long DRX cycle and drx-StartOffset which defines the subframe where the Long and Short DRX cycle starts;drx-ShortCycle (optional): the Short DRX cycle;drx-ShortCycleTimer (optional): the duration the UE shall follow the Short DRX cycle;drx-HARQ-RTT-TimerDL (per DL HARQ process except for the broadcast process): the minimum duration before a DL assignment for HARQ retransmission is expected by the MAC entity;drx-HARQ-RTT-TimerUL (per UL HARQ process): the minimum duration before a UL HARQ retransmission grant is expected by the MAC entity;ps-Wakeup (optional): the configuration to start associated drx-onDurationTimer in case DCI with Cyclic Redundancy Check (CRC) scrambled by Power Saving-Radio Network Temporary Identifier (PS-RNTI) (DCP) is monitored but not detected;ps-TransmitOtherPeriodicCSI (optional): the configuration to report periodic CSI that is not L1-RSRP on Physical Uplink Control Channel (PUCCH) during the time duration indicated by drx-onDurationTimer in case DCP is configured but associated drx-onDurationTimer is not started;ps-TransmitPeriodicLI-RSRP (optional): the configuration to transmit periodic CSI that is L1-RSRP on PUCCH during the time duration indicated by drx-onDurationTimer in case DCP is configured but associated drx-onDurationTimer is not started.

The DRX configuration may take the following values (additional details can be found in 3GPP, TS 38.331, V16.5.0 (2021 June), Section 6.3.2 Radio resource control information elements, referred to hereinafter as [2]).

DRX-Config Information Element

A UE can be configured with up to two DRX parameter sets, each corresponding to a DRX group. A Serving Cell can be assigned to only one DRX group [1]. This means that the UE monitors the DL of a given Serving Cell according to only one long DRX cycle configuration and, optionally, one short DRX cycle configuration.

If the UE uses the long DRX cycle, it monitors the DL by starting the drx-onDurationTimer, if the following condition is fulfilled:

[(SFN×10)+subframe number]modulo(drx-LongCycle)=drx-StartOffset,where SFN is the system frame number.

If the UE uses the short DRX cycle, it monitors the DL by starting the drx-onDurationTimer, if the following condition is fulfilled:

The UE DL monitoring operation according to the long and the short DRX cycles is illustrated inFIG.1.FIG.1illustrates a basic UE DL monitoring when the long and short DRX cycles are configured. The time during which the drx-onDuration Timer or drx-Inactivity Timer is running is part of the Active Time when the UE monitors the DL.

XR Traffic

XR applications typically generate multiple traffic flows and this is modelled accordingly in 3GPP (additional details can be found in 3GPP, S4aV200640, “[FS_XRTraffic] Summary of XR Traffic Models for RANI and Open Issues”, 12 Jan. 2021, referred to hereinafter as [3]). For instance, these flows can correspond to video, audio, and data (control) traffic, respectively. All these flows are assumed to be periodic, but the inter-frame time (i.e., the periodicity) and data rate for each of the flows is different from the other flows. As an example, for DL XR conversational traffic, the inter-frame time of the video, audio, and data flows is 16.67 ms (i.e., 1/60 fps), 20-21.3 ms, and 10 ms, respectively [3]. Another characteristic of XR traffic is that the packet sizes are typically varying, especially for video flows.

PDCCH for Data Traffic Scheduling at Layer 1

In 3GPP NR standard, DCI is received over the PDCCH. The PDCCH may carry DCI in messages with different formats (additional details can be found in 3GPP, TS 38.212, V16.7.0 (2021 September), Section 7 Downlink transport channels and control information, referred to hereinafter as [5]). DCI formats 0_0, 0_1, and 0_2 are DCI messages used to convey uplink grants to the UE for transmission of the PUSCH. DCI formats 1_0, 1_1, and 1_2 are used to convey downlink grants for transmission of the PDSCH.

In NR, a frame has a duration of 10 ms and consists of 10 subframes. Each subframe consists of 2μslots of 14 OFDM symbols each, where μ=0, 1, 2, 3 for the subcarrier spacing of 15×2μkHz, respectively. Although a slot is a typical unit for radio resource allocation, NR enables transmission to start at any OFDM symbol and last only as many symbols as needed for the communication.

A DCI usually only includes information for time-frequency resource allocation, HARQ process, modulation and coding, and retransmission related information, which at the end are essential for reception of physical layer data signals. If a new transmission is indicated via PDCCH with the DCI formats above, the UE must start/restart the drx-Inactivity Timer in the next symbol after PDCCH reception. These DCI formats can have only specific sizes, which can be achieved by applying padding or truncation, if needed. Improved systems and methods for DRX configuration are needed.

SUMMARY

Systems and methods for signaling of traffic flow information for Discontinuous Reception (DRX) configuration are provided. In some embodiments, a method of operating a User Equipment (UE) for determining a flow type includes: receiving a configuration of flow identify information with an association between one or more of the group consisting of: Downlink Control Information (DCIs); Radio Network Temporary Identifier (RNTIs); a combination of fields; with one or more DRX configurations among a set of one or more DRX configurations; monitoring a Physical Downlink Control Channel (PDCCH) in DRX Active Time; in response to receiving a PDCCH with DCI indication of a flow type, identifying the DRX configuration k associated to the DCI indication; and starting or restarting a corresponding timer for the identified DRX configuration in the next symbol after PDCCH reception. In this way, signaling for a flow type, DRX configuration, or DRX parameter value indication from a gNB to a UE can be provided, in order to optimize multiple DRX cycle configurations per Serving Cell, where one or more of the configurations are active simultaneously.

In some embodiments, a method performed by a network node for indicating a flow type includes: configuring a UE with an association between one or more of the group consisting of: DCIs; RNTIs; a combination of fields; and a flow identity; with one or more DRX configurations among a set of one or more DRX configurations; transmitting a PDCCH, with DCI indication identifying the corresponding DRX configuration k; and determining that a corresponding timer for the identified DRX configuration is started or restarted in the next symbol after PDCCH.

In some embodiments, the flow identity comprises a Logical Channel ID (LCID) and/or a Radio Bearer (RB).

In some embodiments, the configuration is received via Radio Resource Control (RRC).

In some embodiments, the method also includes: starting or restarting a corresponding timer for all DRX configurations for which its drx-onDurationTimer and/or drx-Inactivity Timer are running at that time.

In some embodiments, the corresponding timer associated to the indicated DRX configuration would apply to all selected corresponding timers.

In some embodiments, the method also includes: starting or restarting a corresponding timer for all DRX configurations for which its drx-onDurationTimer and/or drx-InactivityTimer are running at that time where all selected drx-onDurationTimer and/or drx-Inactivity Timer(s) would apply the value pointed by the index.

In some embodiments, the configuration comprises one or more of the group consisting of: an index indicating a DRX configuration; an index indicating a null/empty/default or special DRX configuration index; an index indicating a specific timer value from a plurality of timer values.

In some embodiments, the plurality of timer values comprises a plurality of drx-Inactivity Timer values.

In some embodiments, the corresponding timer comprises a drx-Inactivity Timer (k).

In some embodiments, if the PDCCH is scrambled with a new RNTI, prioritizing one predetermined drx-InactivityTimer value over all other multiple timers.

In some embodiments, if the PDCCH is scrambled with a new RNTI, interpreting some or all of existing DCI or Uplink Control Information, UCI, fields for a new purpose to identify a flow index information.

In some embodiments, when there is a special physical resource allocation indication for the implicit flow information, prioritizing one drx-InactivityTimer value over all other multiple timers or will extract a flow index information.

In some embodiments, a UE includes: processing circuitry and memory wherein the memory comprises instructions configured to cause the UE to: receive a configuration of flow identify information with an association between one or more of the group consisting of: DCIs; RNTIs; a combination of fields; with one or more DRX configurations among a set of one or more DRX configurations; monitor a PDCCH in DRX Active Time; in response to receiving a PDCCH with DCI indication of a flow type, identify the DRX configuration k associated to the DCI indication; and start or restart a corresponding timer for the identified DRX configuration in a next symbol after the PDCCH reception.

In some embodiments, a network node includes: processing circuitry and memory wherein the memory comprises instructions configured to cause the network node to: configure a UE with an association between one or more of the group consisting of: DCIs; RNTIs; a combination of fields; and a flow identity; with one or more DRX configurations among a set of one or more DRX configurations; transmit a PDCCH with DCI indication identifying the corresponding DRX configuration k; and determine that a corresponding timer for the identified DRX configuration is started or restarted in a next symbol after the PDCCH.

DETAILED DESCRIPTION

Some embodiments of this present disclosure are related to Provisional Application No. 63/240,864, filed 3 Sep. 2021: “Methods for Supporting Multiple DRX Configurations.” That application is referred to herein as: [4] and relates to initial solutions to support multiple DRX configurations. Some embodiments of the present disclosure assume that each DRX configuration has a corresponding drx-onDurationTimer, which is started by the UE as disclosed in that previous application.

There currently exist certain challenges. In [4] support for multiple DRX configurations were proposed where the UE does not have information about which specific data flow is being scheduled by the PDCCH, according to current standard PDCCH specifications. Consequently, when multiple drx-InactivityTimers are implemented by the UE (i.e., one per DRX configuration) in [4], all drx-InactivityTimers of DRX configurations that are in Active Time are (re-)started, regardless of which flow the scheduled data belonged to. This may lead to an increased, unnecessary overall Active Time, due to DRX configurations corresponding to flows that are not being scheduled. This is illustrated inFIG.2, where the PDCCH schedules a transmission for flow1, but does not indicate for which flow it is.FIG.2illustrates the limitation of multiple DRX configurations without flow indication where the longest drx-InactivityTimer(2) will run, leading to unnecessary UE power consumption [4]. As a result, the UE starts the drx-Inactivity Timers for all three flows, since all three drx-onDuration Timers are running. Since drx-InactivityTimer(2) for flow2is the longest, the Active Time ends at moment T2, although the scheduled data is for flow1and starting drx-InactivityTimer(1) which ends at T1would be sufficient.

Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. The proposed solution provides signaling for a flow type, DRX configuration, or DRX parameter value indication from a gNB to a UE, in order to optimize multiple DRX cycle configurations per Serving Cell, where one or more of the configurations are active simultaneously. Methods are proposed to modify Layer 1 signaling to indicate information connected to the DRX configuration at the moment of scheduling. This information can then be used at the UE for mapping the scheduled flow to the associated DRX configuration and (re-)starting the corresponding drx-InactivityTimer.

Some embodiments of the present disclosure propose methods for dynamic traffic flow indication by L1 and L2 signaling when multiple DRX configurations are activated, in order to signal a UE to properly select/update corresponding specific DRX parameters.

Certain embodiments may provide one or more of the following technical advantage(s). The proposed solution avoids unnecessary start or restart of the drx-Inactivity Timer by fast indication of traffic flow when multiple DRXs are configured, which leads to high power saving gains at the UE.

Some embodiments of the present disclosure have additional advantages compared to the embodiments proposed in [4]. Specifically, the UE is informed about which traffic flow is being scheduled, so it can map this flow to a stored DRX configuration. Consequently, if multiple drx-Inactivity Timers are implemented, the UE can (re-)start only that timer that corresponds to the scheduled flow. This is shown inFIG.3which illustrates a proposed solution, where the Active Time ends at moment T1instead of T2inFIG.2.

FIG.4shows an example of a communication system400in accordance with some embodiments. In the example, the communication system400includes a telecommunication network402that includes an access network404, such as a Radio Access Network (RAN), and a core network406, which includes one or more core network nodes408. The access network404includes one or more access network nodes, such as network nodes410A and410B (one or more of which may be generally referred to as network nodes410), or any other similar Third Generation Partnership Project (3GPP) access node or non-3GPP Access Point (AP). The network nodes410facilitate direct or indirect connection of User Equipment (UE), such as by connecting UEs412A,412B,412C, and412D (one or more of which may be generally referred to as UEs412) to the core network406over one or more wireless connections.

The UEs412may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes410and other communication devices. Similarly, the network nodes410are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs412and/or with other network nodes or equipment in the telecommunication network402to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network402.

In the depicted example, the core network406connects the network nodes410to one or more hosts, such as host416. 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 network406includes one more core network nodes (e.g., core network node408) 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 node408. 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).

The host416may be under the ownership or control of a service provider other than an operator or provider of the access network404and/or the telecommunication network402, and may be operated by the service provider or on behalf of the service provider. The host416may 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.

As a whole, the communication system400ofFIG.4enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system400may 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 Second, Third, Fourth, or Fifth Generation (2G, 3G, 4G, or 5G) standards, or any applicable future generation standard (e.g., Sixth Generation (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.

In some examples, the telecommunication network402is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunication network402may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network402. For example, the telecommunication network402may 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 Internet of Things (IoT) services to yet further UEs.

In some examples, the UEs412are configured to transmit and/or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network404on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network404. Additionally, a UE may be configured for operating in single- or multi-Radio Access Technology (RAT) or multi-standard mode. For example, a UE may operate with any one or combination of WiFi, New Radio (NR), and LTE, i.e., be configured for Multi-Radio Dual Connectivity (MR-DC), such as Evolved UMTS Terrestrial RAN (E-UTRAN) NR-Dual Connectivity (EN-DC).

In the example, a hub414communicates with the access network404to facilitate indirect communication between one or more UEs (e.g., UE412C and/or412D) and network nodes (e.g., network node410B). In some examples, the hub414may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub414may be a broadband router enabling access to the core network406for the UEs. As another example, the hub414may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes410, or by executable code, script, process, or other instructions in the hub414. As another example, the hub414may 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. As another example, the hub414may be a content source. For example, for a UE that is a Virtual Reality (VR) headset, display, loudspeaker or other media delivery device, the hub414may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub414then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub414acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy IoT devices.

The hub414may have a constant/persistent or intermittent connection to the network node410B. The hub414may also allow for a different communication scheme and/or schedule between the hub414and UEs (e.g., UE412C and/or412D), and between the hub414and the core network406. In other examples, the hub414is connected to the core network406and/or one or more UEs via a wired connection. Moreover, the hub414may be configured to connect to a Machine-to-Machine (M2M) service provider over the access network404and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes410while still connected via the hub414via a wired or wireless connection. In some embodiments, the hub414may be a dedicated hub—that is, a hub whose primary function is to route communications to/from the UEs from/to the network node410B. In other embodiments, the hub414may be a non-dedicated hub—that is, a device which is capable of operating to route communications between the UEs and the network node410B, but which is additionally capable of operating as a communication start and/or end point for certain data channels.

In some embodiments, a method to dynamically indicate a flow type via L1 or L2 signaling to optimize multiple DRX configurations when multiple traffic flows are present with a different periodicity are provided.

Traffic Flow Indication for Multiple DRX Operations

The following embodiments are based on the fact that the NW has configured the UE via e.g., Radio Resource Control (RRC) with an association between, for example, DCIs, RNTIs, a combination of fields, a flow identity (e.g., Logical Channel ID (LCID) or Radio Bearer (RB)), with one or more DRX configurations among a set of one or more DRX configurations.(A) In the first embodiment, the PDCCH may indicate the traffic flow type for corresponding PDSCH data scheduled.(A1) When a new DL is indicated by the PDCCH, the PDCCH may also indicate an index corresponding to one DRX configuration from a plurality/list of DRX configurations provided to the UE, or to a specific value such as a value for the drx-InactivityTimer among a plurality of values. This index can be indicated 1) by introducing new fields in an existing DCI format or 2) by reusing some of the existing DCI fields but with higher layer signaling to tell the new purpose of the fields for flow indication, or 3) by introducing a new DCI format. In any case, the mapping between a specific DCI indication and a corresponding DRX configuration set should be predetermined.(A2) It is also possible that the existing DCI can be scrambled with a new RNTI, in order to indicate the special purpose of the DCI. For example, a gNB can signal a UE that the new scrambled DCI is intended for the UE to choose a predetermined drx-InactivityTimer out of multiple timers, which can be the shortest or the longest. In another example, the new RNTI with existing DCI format can tell a UE a different purpose of bits in existing DCI fields that at the end works as a short message of detailed flow information. The detailed flow information can be the slot index of start and/or end time of resource allocation of corresponding traffic flow. This can be useful for a UE to choose which DRX parameter set to be used for an indicated time window.(A3) Instead of using a new RNTI, a special configuration of existing physical resource allocation can implicitly indicate a UE the flow information. As non-limiting examples, a special CCE (control channel element) allocation, a special time (or frequency) domain resource assignment, or a special HARQ process number can be sent in DCI, which can be reserved in advance by RRC signaling, and then a UE will choose the predetermined drx-InactivityTimer. It is also possible to combine all those dimensions of the CCE allocation, the special time-frequency domain resource assignment, a special HARQ process in order to deliver more traffic flow information.

As non-limiting examples, all the above flow indication via PDCCH can also be applied for PDCCH for uplink PUSCH transmission by Uplink Control Information (UCI). This allows a UE to indicate a traffic flow information without waiting for DCI transmission.(B) The second embodiment is extracting LCID/flow information in the MAC PDU:(B1) In a MAC PDU, each MAC subheader contains an LCID which indicates if the MAC subPDU is user data/signaling, i.e., RBs, or if the MAC subPDU is a MAC CE. For each DRX configuration that the NW wants to affect, the network will include 1-bit indication in the MAC subheader, corresponding to an RB associated to one of the DRX configurations which the network wants to affect.(B2) Alternatively to the above, a MAC CE could be added in the MAC PDU to include one or more indexes, e.g., DRX configuration index/LCID/flow. These indexes can indicate:a) flows for which there is no more data in the current DRX cycle, orb) flows that have already been scheduled by PDCCH, but not yet transmitted in a PDSCH/PUSCH, orc) DRX configuration which does not need to re-start the inactivity timer.

UE Behavior at the Reception of Flow Indication

In some embodiments, corresponding methods for the UE to operate DRX after receiving the flow indication are provided. When a network (e.g., gNB) sends multiple selected DRX cycle configurations to the UE, which can be numbered from1to n, the UE can know which DRX is coupled with which LCID/RB.

FIG.5illustrates a proposed modifications for the UE to combine the multiple DRX cycle configurations, in order to start/restart the drx-InactivityTimers. The proposed modifications compared to the 3GPP Rel-16 solution are shown in bold. Parameter k refers to any of the 1 to n DRX cycle configurations. The UE receives a configuration with an association between one or more of the group consisting of: DCIs; RNTIs; a combination of fields; and a flow identity; with one or more DRX configurations among a set of one or more DRX configurations (step500); monitors a PDCCH in DRX Active Time (step502); in response to receiving a PDCCH with DRX DCI indication, identifies (500) the DRX configuration k associated to the DCI indication (step504); and/or starts or restarts drx-Inactivity Timer (k) in the next symbol after PDCCH reception (step508).

In some embodiments, the UE starts/restarts/stops the drx-InactivityTimers depending on whether and which flows are indicated by the network, as follows.(A) If the PDCCH indicates the traffic flow type:(A1) If the PDCCH indicates an index:(A1.1) If the index indicates a DRX configuration:a) The UE starts or re-starts the corresponding timers (e.g., drx-InactivityTimer) for the indicated DRX configuration, if its drx-onDurationTimer and/or drx-InactivityTimer is running at that time, while the other DRX configurations would not be affected (seeFIG.5), orb) The UE starts or re-starts the drx-InactivityTimer for all DRX configurations for which its drx-onDurationTimer and/or drx-InactivityTimer are running at that time. One option follows:b.1) One option is that the drx-InactivityTimer associated to the indicated DRX configuration would apply to all selected drx-InactivityTimer(s); alternatively.(A1.2) If the index indicates a null/empty/default or special DRX configuration index:a) The UE starts or re-starts the drx-InactivityTimer for all DRX configurations given the drx-onDurationTimer and/or drx-InactivityTimer for each associated DRX configuration is running at that time. The value to apply for each started or re-started timer is the corresponding for its own configuration.(A1.3) If the index indicates a specific timer value from a plurality of timer (e.g., drx-InactivityTimer) values:a) The UE starts or re-starts the drx-InactivityTimer for all DRX configurations given the drx-onDurationTimer and/or drx-InactivityTimer for each associated DRX configuration is running at that time. All selected drx-InactivityTimer(s) would apply the value pointed by the index.(A2) If the PDCCH is scrambled with a new RNTI, a UE can have two different cases to follow. First, it can prioritize one predetermined drx-InactivityTimer value over all other multiple timers. Second, a UE interprets some or all of existing DCI or UCI fields for a new purpose to identify a flow index information and follows the same procedure described in A1.1 and A1.2 above.(A3) When there is a special physical resource allocation indication for the implicit flow information (as described in 6.1.1-A3), a UE will prioritize one drx-InactivityTimer value over all other multiple timers or will extract a flow index information to follow the same procedure in A1.1 and A1.2 above.

After the UE performs the actions in one of the steps above (A1/2/3), the UE will eventually enter the sleep period and will stop monitoring the PDCCH. When the following DRX period starts, for those DRX configurations which modified their values, the UE will follow one of the following:The UE would continue using the timer values associated to the DRX configuration indicated by the index, orThe UE would re-apply the timer values initially provided in the RRC configuration for each corresponding DRX configuration.(B) Prior to the UE receiving a PDSCH, a PDCCH is received by the UE. When the UE receives a PDCCH indicating a new transmission, it starts/restarts all drx-InactivityTimers of DRX configurations for which the drx-onDurationTimer and/or drx-InactivityTimer are running, as in our proposal in [4]. Additionally, the UE extracts flow information/LCID(s) from the MAC PDU transmitted in the PDSCH:(B1) When the UE receives a PDSCH, it extracts the LCID from the MAC subheaders of the MAC PDU and checks if the additional field indicates the end of the traffic for this LCID. If the end of the traffic is indicated, the UE will not restart the drx-InactivityTimer for the DRX configuration associated with this LCID until its next DRX cycle.(B2) Alternatively, if there is a MAC CE in the MAC PDU indicating index(es): B2.a) If the index(es) indicate flows for which there is no more data, the UE will not restart the drx-InactivityTimer for the DRX configuration(s) associated with them, until their next respective DRX cycle; orB2.b) If the index(es) indicate flows that have already been scheduled by PDCCH, but are not yet transmitted, the UE can stop all running drx-InactivityTimers that do not correspond to DRX configurations associated with the indicated flows or with the LCID in the current MAC subheader.B2.c) If the index(es) indicate a DRX configuration, the UE will not restart the drx-InactivityTimer for the indicated DRX configuration(s). Alternatively, the UE will restart the drx-InactivityTimer for the indicated DRX configuration(s).(B3) Alternatively to (B1/2), the UE can increment a counter for every PDCCH scheduling new DL/UL transmissions. When a scheduled PDSCH/PUSCH for a new transmission occurs, the UE decrements this counter. If the counter is zero (i.e., no new DL/UL transmission is expected after this one), the UE can check the LCID(s) in the current PDSCH/PUSCH and can stop all running drx-InactivityTimers of DRX configurations that are not associated with the LCID(s) in the current PDSCH/PUSCH.

FIG.6shows a UE600in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged, and/or operable to communicate wirelessly with network nodes and/or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, Voice over Internet Protocol (VOIP) phone, wireless local loop phone, desktop computer, Personal Digital Assistant (PDA), wireless camera, 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. Other examples include any UE identified by the 3GPP, including a Narrowband Internet of Things (NB-IoT) UE, a Machine Type Communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.

The UE600includes processing circuitry602that is operatively coupled via a bus604to an input/output interface606, a power source608, memory610, a communication interface612, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown inFIG.6. 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 circuitry602is 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 memory610. The processing circuitry602may 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. For example, the processing circuitry602may include multiple Central Processing Units (CPUs).

In some embodiments, the power source608is 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 source608may further include power circuitry for delivering power from the power source608itself, and/or an external power source, to the various parts of the UE600via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging the power source608. Power circuitry may perform any formatting, converting, or other modification to the power from the power source608to make the power suitable for the respective components of the UE600to which power is supplied.

The memory610may be or be configured to include memory such as Random Access Memory (RAM), Read Only Memory (ROM), Programmable ROM (PROM), Erasable PROM (EPROM), Electrically EPROM (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory610includes one or more application programs614, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data616. The memory610may store, for use by the UE600, any of a variety of various operating systems or combinations of operating systems.

The memory610may 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 RAM (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a tamper resistant module in the form of a Universal Integrated Circuit Card (UICC) including one or more Subscriber Identity Modules (SIMs), such as a Universal SIM (USIM) and/or Internet Protocol Multimedia Services Identity Module (ISIM), other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as a ‘SIM card.’ The memory610may allow the UE600to 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 memory610, which may be or comprise a device-readable storage medium.

The processing circuitry602may be configured to communicate with an access network or other network using the communication interface612. The communication interface612may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna622. The communication interface612may 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 transmitter618and/or a receiver620appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter618and receiver620may be coupled to one or more antennas (e.g., the antenna622) and may share circuit components, software, or firmware, or alternatively be implemented separately.

In the illustrated embodiment, communication functions of the communication interface612may include cellular communication, WiFi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, NFC, 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. Communications may be implemented according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband CDMA (WCDMA), GSM, LTE, NR, UMTS, WiMax, Ethernet, Transmission Control Protocol/Internet Protocol (TCP/IP), Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), Quick User Datagram Protocol Internet Connection (QUIC), Hypertext Transfer Protocol (HTTP), and so forth.

FIG.7shows a network node700in accordance with some embodiments. As used herein, 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. Examples of network nodes include, but are not limited to, APs (e.g., radio APs), Base Stations (BSs) (e.g., radio BSs, Node Bs, evolved Node Bs (eNBs), and NR Node Bs (gNBs)).

BSs 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 BSs, pico BSs, micro BSs, or macro BSs. A BS 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 BS such as centralized digital units and/or Remote Radio Units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such RRUs may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio BS may also be referred to as nodes in a Distributed Antenna System (DAS).

The network node700includes processing circuitry702, memory704, a communication interface706, and a power source708. The network node700may be composed of multiple physically separate components (e.g., a Node B component and an RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node700comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple Node Bs. In such a scenario, each unique Node B and RNC pair may in some instances be considered a single separate network node. In some embodiments, the network node700may be configured to support multiple RATs. In such embodiments, some components may be duplicated (e.g., separate memory704for different RATs) and some components may be reused (e.g., an antenna710may be shared by different RATs). The network node700may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node700, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, Long Range Wide Area Network (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 the network node700.

The processing circuitry702may comprise a combination of one or more of a microprocessor, controller, microcontroller, CPU, DSP, ASIC, FPGA, 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 node700components, such as the memory704, to provide network node700functionality.

In some embodiments, the processing circuitry702includes a System on a Chip (SOC). In some embodiments, the processing circuitry702includes one or more of Radio Frequency (RF) transceiver circuitry712and baseband processing circuitry714. In some embodiments, the RF transceiver circuitry712and the baseband processing circuitry714may 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 RF transceiver circuitry712and the baseband processing circuitry714may be on the same chip or set of chips, boards, or units.

The memory704may 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, RAM, 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 circuitry702. The memory704may 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 circuitry702and utilized by the network node700. The memory704may be used to store any calculations made by the processing circuitry702and/or any data received via the communication interface706. In some embodiments, the processing circuitry702and the memory704are integrated.

The communication interface706is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface706comprises port(s)/terminal(s)716to send and receive data, for example to and from a network over a wired connection. The communication interface706also includes radio front-end circuitry718that may be coupled to, or in certain embodiments a part of, the antenna710. The radio front-end circuitry718comprises filters720and amplifiers722. The radio front-end circuitry718may be connected to the antenna710and the processing circuitry702. The radio front-end circuitry718may be configured to condition signals communicated between the antenna710and the processing circuitry702. The radio front-end circuitry718may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry718may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of the filters720and/or the amplifiers722. The radio signal may then be transmitted via the antenna710. Similarly, when receiving data, the antenna710may collect radio signals which are then converted into digital data by the radio front-end circuitry718. The digital data may be passed to the processing circuitry702. In other embodiments, the communication interface706may comprise different components and/or different combinations of components.

In certain alternative embodiments, the network node700does not include separate radio front-end circuitry718; instead, the processing circuitry702includes radio front-end circuitry and is connected to the antenna710. Similarly, in some embodiments, all or some of the RF transceiver circuitry712is part of the communication interface706. In still other embodiments, the communication interface706includes the one or more ports or terminals716, the radio front-end circuitry718, and the RF transceiver circuitry712as part of a radio unit (not shown), and the communication interface706communicates with the baseband processing circuitry714, which is part of a digital unit (not shown).

The antenna710may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. The antenna710may be coupled to the radio front-end circuitry718and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In certain embodiments, the antenna710is separate from the network node700and connectable to the network node700through an interface or port.

The antenna710, the communication interface706, and/or the processing circuitry702may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node700. Any information, data, and/or signals may be received from a UE, another network node, and/or any other network equipment. Similarly, the antenna710, the communication interface706, and/or the processing circuitry702may be configured to perform any transmitting operations described herein as being performed by the network node700. Any information, data, and/or signals may be transmitted to a UE, another network node, and/or any other network equipment.

The power source708provides power to the various components of the network node700in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source708may further comprise, or be coupled to, power management circuitry to supply the components of the network node700with power for performing the functionality described herein. For example, the network node700may be connectable to an external power source (e.g., the power grid or an electricity outlet) via input circuitry or an interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source708. As a further example, the power source708may 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 node700may include additional components beyond those shown inFIG.7for 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. For example, the network node700may include user interface equipment to allow input of information into the network node700and to allow output of information from the network node700. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node700.

FIG.8is a block diagram of a host800, which may be an embodiment of the host416ofFIG.4, in accordance with various aspects described herein. As used herein, the host800may be or comprise various combinations of 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 host800may provide one or more services to one or more UEs.

The host800includes processing circuitry802that is operatively coupled via a bus804to an input/output interface806, a network interface808, a power source810, and memory812. 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 asFIGS.6and7, such that the descriptions thereof are generally applicable to the corresponding components of the host800.

The memory812may include one or more computer programs including one or more host application programs814and data816, which may include user data, e.g., data generated by a UE for the host800or data generated by the host800for a UE. Embodiments of the host800may utilize only a subset or all of the components shown. The host application programs814may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), Moving Picture Experts Group (MPEG), VP9) and audio codecs (e.g., Free Lossless Audio Codec (FLAC), Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, and heads-up display systems). The host application programs814may 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. Accordingly, the host800may select and/or indicate a different host for Over-The-Top (OTT) services for a UE. The host application programs814may 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 (DASH or MPEG-DASH), etc.

Hardware904includes 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 layers906(also referred to as hypervisors or VM Monitors (VMMs)), provide VMs908A and908B (one or more of which may be generally referred to as VMs908), and/or perform any of the functions, features, and/or benefits described in relation with some embodiments described herein. The virtualization layer906may present a virtual operating platform that appears like networking hardware to the VMs908.

The VMs908comprise virtual processing, virtual memory, virtual networking, or interface and virtual storage, and may be run by a corresponding virtualization layer906. Different embodiments of the instance of a virtual appliance902may be implemented on one or more of the VMs908, 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.

In the context of NFV, a VM908may 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 VMs908, and that part of the hardware904that executes that VM, be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs908, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs908on top of the hardware904and corresponds to the application902.

The hardware904may be implemented in a standalone network node with generic or specific components. The hardware904may implement some functions via virtualization. Alternatively, the hardware904may 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 orchestration910, which, among others, oversees lifecycle management of the applications902. In some embodiments, the hardware904is 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 RAN or a BS. In some embodiments, some signaling can be provided with the use of a control system912which may alternatively be used for communication between hardware nodes and radio units.

FIG.10shows a communication diagram of a host1002communicating via a network node1004with a UE1006over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as the UE412A ofFIG.4and/or the UE600ofFIG.6), the network node (such as the network node410A ofFIG.4and/or the network node700ofFIG.7), and the host (such as the host416ofFIG.4and/or the host800ofFIG.8) discussed in the preceding paragraphs will now be described with reference toFIG.10.

Like the host800, embodiments of the host1002include hardware, such as a communication interface, processing circuitry, and memory. The host1002also includes software, which is stored in or is accessible by the host1002and 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 UE1006connecting via an OTT connection1050extending between the UE1006and the host1002. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection1050.

The network node1004includes hardware enabling it to communicate with the host1002and the UE1006via a connection1060. The connection1060may be direct or pass through a core network (like the core network406ofFIG.4) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.

The UE1006includes hardware and software, which is stored in or accessible by the UE1006and 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 the UE1006with the support of the host1002. In the host1002, an executing host application may communicate with the executing client application via the OTT connection1050terminating at the UE1006and the host1002. In providing the service to the user, 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 connection1050may 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 connection1050.

The OTT connection1050may extend via the connection1060between the host1002and the network node1004and via a wireless connection1070between the network node1004and the UE1006to provide the connection between the host1002and the UE1006. The connection1060and the wireless connection1070, over which the OTT connection1050may be provided, have been drawn abstractly to illustrate the communication between the host1002and the UE1006via the network node1004, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

As an example of transmitting data via the OTT connection1050, in step1008, the host1002provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE1006. In other embodiments, the user data is associated with a UE1006that shares data with the host1002without explicit human interaction. In step1010, the host1002initiates a transmission carrying the user data towards the UE1006. The host1002may initiate the transmission responsive to a request transmitted by the UE1006. The request may be caused by human interaction with the UE1006or by operation of the client application executing on the UE1006. The transmission may pass via the network node1004in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step1012, the network node1004transmits to the UE1006the user data that was carried in the transmission that the host1002initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step1014, the UE1006receives the user data carried in the transmission, which may be performed by a client application executed on the UE1006associated with the host application executed by the host1002.

In some examples, the UE1006executes a client application which provides user data to the host1002. The user data may be provided in reaction or response to the data received from the host1002. Accordingly, in step1016, the UE1006may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input/output interface of the UE1006. Regardless of the specific manner in which the user data was provided, the UE1006initiates, in step1018, transmission of the user data towards the host1002via the network node1004. In step1020, in accordance with the teachings of the embodiments described throughout this disclosure, the network node1004receives user data from the UE1006and initiates transmission of the received user data towards the host1002. In step1022, the host1002receives the user data carried in the transmission initiated by the UE1006.

One or more of the various embodiments improve the performance of OTT services provided to the UE1006using the OTT connection1050, in which the wireless connection1070forms the last segment. More precisely, the teachings of these embodiments may improve the e.g., data rate, latency, power consumption, etc. and thereby provide benefits such as e.g., reduced user waiting time, relaxed restriction on file size, improved content resolution, better responsiveness, extended battery lifetime, etc.

In an example scenario, factory status information may be collected and analyzed by the host1002. As another example, the host1002may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host1002may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host1002may store surveillance video uploaded by a UE. As another example, the host1002may store or control access to media content such as video, audio, VR, or AR which it can broadcast, multicast, or unicast to UEs. As other examples, the host1002may 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.

In some examples, 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. There may further be an optional network functionality for reconfiguring the OTT connection1050between the host1002and the UE1006in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection1050may be implemented in software and hardware of the host1002and/or the UE1006. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection1050passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or by supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection1050may include message format, retransmission settings, preferred routing, etc.; the reconfiguring need not directly alter the operation of the network node1004. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency, and the like by the host1002. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection1050while monitoring propagation times, errors, etc.

EMBODIMENTS

Group A Embodiments

Embodiment 1: A method performed by a user equipment for determining a flow type, the method comprising one or more of: a. receiving (500) a configuration with an association between one or more of the group consisting of: DCIs; RNTIs; a combination of fields; and a flow identity; with one or more DRX configurations among a set of one or more DRX configurations; b. monitoring (502) a PDCCH in DRX Active Time; c. in response to receiving (504) a PDCCH with DRX DCI indication, identifying (506) the DRX configuration k associated to the DCI indication; and d. starting or restarting (508) a corresponding timer for the indicated DRX configuration in the next symbol after PDCCH reception.

Embodiment 2: The method of embodiment 1 wherein the flow identity comprises an LCID or an RB.

Embodiment 3: The method of any of embodiments 1-2 wherein the configuration is received via RRC.

Embodiment 4: The method of any of embodiments 1-3 further comprising: starting or restarting a corresponding timer for all DRX configurations for which its drx-onDurationTimer and/or drx-Inactivity Timer are running at that time.

Embodiment 5: The method of any of embodiments 1-4 wherein the corresponding timer associated to the indicated DRX configuration would apply to all selected corresponding timers.

Embodiment 6: The method of any of embodiments 1-5 further comprising: starting or restarting a corresponding timer for all DRX configurations for which its drx-onDurationTimer and/or drx-InactivityTimer are running at that time where all selected drx-InactivityTimer(s) would apply the value pointed by the index.

Embodiment 7: The method of any of embodiments 1-6 wherein the configuration comprises one or more of the group consisting of: an index indicating a DRX configuration; an index indicating a null/empty/default or special DRX configuration index; an index indicating a specific timer value from a plurality of timer (e.g., a drx-InactivityTimer) values.

Embodiment 8: The method of any of embodiments 1-7 wherein the corresponding timer comprises a drx-InactivityTimer(k).

Embodiment 9: The method of any of embodiments 1-8 wherein, if the PDCCH is scrambled with a new RNTI, prioritizing one predetermined drx-InactivityTimer value over all other multiple timers.

Embodiment 10: The method of any of embodiments 1-8 wherein, if the PDCCH is scrambled with a new RNTI, interpreting some or all of existing DCI or UCI fields for a new purpose to identify a flow index information.

Embodiment 11: The method of any of embodiments 1-10 wherein, when there is a special physical resource allocation indication for the implicit flow information, prioritizing one drx-InactivityTimer value over all other multiple timers or will extract a flow index information.

Embodiment 12: The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host via the transmission to the network node.

Group B Embodiments

Embodiment 13: A method performed by a network node for indicating a flow type, the method comprising one or more of: a. configuring a user equipment with an association between one or more of the group consisting of: DCIs; RNTIs; a combination of fields; and a flow identity; with one or more DRX configurations among a set of one or more DRX configurations; b. transmitting a PDCCH with DRX DCI indication identifying the DRX configuration k associated to the DCI indication; and c. determining that a corresponding timer for the indicated DRX configuration is started or restarted in the next symbol after PDCCH.

Embodiment 14: The method of embodiment 13 wherein the flow identity comprises an LCID or an RB.

Embodiment 15: The method of any of embodiments 13-14 wherein the configuration is transmitted via RRC.

Embodiment 16: The method of any of embodiments 13-15 wherein the configuration comprises one or more of the group consisting of: an index indicating a DRX configuration; an index indicating a null/empty/default or special DRX configuration index; an index indicating a specific timer value from a plurality of timer (e.g., a drx-InactivityTimer) values.

Embodiment 17: The method of any of embodiments 13-16 wherein the corresponding timer comprises a drx-InactivityTimer(k).

Embodiment 18: The method of any of embodiments 13-17 wherein, if the PDCCH is scrambled with a new RNTI, the user equipment prioritizes one predetermined drx-Inactivity Timer value over all other multiple timers.

Embodiment 19: The method of any of embodiments 13-17 wherein, if the PDCCH is scrambled with a new RNTI, the user equipment interprets some or all of existing DCI or UCI fields for a new purpose to identify a flow index information.

Embodiment 20: The method of any of embodiments 1-10 wherein, when there is a special physical resource allocation indication for the implicit flow information, the user equipment prioritizes one drx-InactivityTimer value over all other multiple timers or will extract a flow index information.

Embodiment 21: The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment.

Group C Embodiments

Embodiment 22: A user equipment for determining a flow type, comprising: processing circuitry configured to perform any of the steps of any of the Group A embodiments; and power supply circuitry configured to supply power to the processing circuitry.

Embodiment 23: A network node for determining a flow type, the network node comprising: processing circuitry configured to perform any of the steps of any of the Group B embodiments; power supply circuitry configured to supply power to the processing circuitry.

Embodiment 24: A user equipment (UE) for determining a flow type, the UE comprising: an antenna configured to send and receive wireless signals; 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; the 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; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.

Embodiment 25: A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A embodiments to receive the user data from the host.

Embodiment 26: The host of the previous embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data to the UE from the host.

Embodiment 27: The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

Embodiment 28: A method implemented by a host operating in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the UE performs any of the operations of any of the Group A embodiments to receive the user data from the host.

Embodiment 29: The method of the previous embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE.

Embodiment 30: The method of the previous embodiment, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.

Embodiment 31: A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A embodiments to transmit the user data to the host.

Embodiment 32: The host of the previous embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data from the UE to the host.

Embodiment 33: The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

Embodiment 34: A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, receiving user data transmitted to the host via the network node by the UE, wherein the UE performs any of the steps of any of the Group A embodiments to transmit the user data to the host.

Embodiment 35: The method of the previous embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE.

Embodiment 36: The method of the previous embodiment, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.

Embodiment 37: A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.

Embodiment 38: The host of the previous embodiment, wherein: the processing circuitry of the host is configured to execute a host application that provides the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host.

Embodiment 39: A method implemented in a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the network node performs any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.

Embodiment 40: The method of the previous embodiment, further comprising, at the network node, transmitting the user data provided by the host for the UE.

Embodiment 41: The method of any of the previous 2 embodiments, wherein the user data is provided at the host by executing a host application that interacts with a client application executing on the UE, the client application being associated with the host application.

Embodiment 42: A communication system configured to provide an over-the-top service, the communication system comprising: a host comprising: processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.

Embodiment 43: The communication system of the previous embodiment, further comprising: the network node; and/or the user equipment.

Embodiment 44: A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to initiate receipt of user data; and a network interface configured to receive the user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to receive the user data from a user equipment (UE) for the host.

Embodiment 45: The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

Embodiment 46: The host of the any of the previous 2 embodiments, wherein the initiating receipt of the user data comprises requesting the user data.

Embodiment 47: A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, initiating receipt of user data from the UE, the user data originating from a transmission which the network node has received from the UE, wherein the network node performs any of the steps of any of the Group B embodiments to receive the user data from the UE for the host.

Embodiment 48: The method of the previous embodiment, further comprising at the network node, transmitting the received user data to the host.

At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s).3GPP Third Generation Partnership Project5G Fifth Generation5GC Fifth Generation Core5GS Fifth Generation SystemAF Application FunctionAMF Access and Mobility FunctionAN Access NetworkAP Access PointASIC Application Specific Integrated CircuitAUSF Authentication Server FunctionCPU Central Processing UnitCRC Cyclic Redundancy CheckDCI Downlink Control InformationDCP DCI with CRC scrambled by PS-RNTIDL DownlinkDN Data NetworkDRX Discontinuous ReceptionDSP Digital Signal ProcessoreNB Enhanced or Evolved Node BEPS Evolved Packet SystemE-UTRA Evolved Universal Terrestrial Radio AccessFPGA Field Programmable Gate ArraygNB New Radio Base StationgNB-DU New Radio Base Station Distributed UnitHSS Home Subscriber ServerIoT Internet of ThingsIP Internet ProtocolLCID Logical Channel IDLTE Long Term EvolutionMAC Medium Access ControlMME Mobility Management EntityMTC Machine Type CommunicationNEF Network Exposure FunctionNF Network FunctionNR New RadioNRF Network Function Repository FunctionNSSF Network Slice Selection FunctionNW NetworkOFDM Orthogonal Frequency Division MultiplexingOTT Over-the-TopPC Personal ComputerPCF Policy Control FunctionPDCCH Physical Downlink Control ChannelPDU Packet Data Unit.P-GW Packet Data Network GatewayPS-RNTI Power Saving Radio Network Temporary IdentifierPUCCH Physical Uplink Control ChannelQoS Quality of ServiceRAM Random Access MemoryRAN Radio Access NetworkRB Radio BearerRNTI Radio Network Temporary IdentifierROM Read Only MemoryRRC Radio Resource ControlRRH Remote Radio HeadRTT Round Trip TimeSCEF Service Capability Exposure FunctionSMF Session Management FunctionUCI Uplink Control InformationUDM Unified Data ManagementUE User EquipmentUL UplinkUPF User Plane FunctionXR Extended Reality