Patent ID: 12261756

DETAILED DESCRIPTION

Techniques are described for storing and forwarding data, and for monitoring data handling (including the storing and forwarding of data) at a network node or modem. At a network node, store and forward functionality may be used to store data at the network node when a wireless device is unreachable, and to forward the data to the wireless device when the wireless device is available. Furthermore, store and forward functionality may be used to store data at the modem when the modem is not active or not ready to transmit, and to transmit the data over a radio frequency spectrum when the modem becomes active, when the amount of data stored at the modem exceeds a threshold, when the modem is ready to transmit, or a combination thereof. Reports relating to the monitoring may be transmitted to an application server (by the network node) or to an application processor of a wireless device (by the modem). The techniques enable the application server or application processor to monitor the handling of data and not wake a modem of a wireless device outside its normal wakeup schedule, thereby helping the wireless device to conserve battery power.

At a network node, monitoring functionality may include the monitoring of data handling and the transmission of reports relating to the data handling to an application server. In some examples, the application server may use the reports, for example, to determine if and when data has been forwarded to a wireless device. At a modem of a wireless device, in some examples, monitoring functionality may include the monitoring of data handling at the modem and the transmission of reports relating to the data handling to an application processor of the wireless device. The application processor may use the reports to determine if and when data has been transmitted over the radio frequency spectrum. At either or both of the network node and the modem, the data handling that is monitored may include store and forward data handling, among other examples.

In some examples, the described techniques may enable a network node of a wireless communication system to receive, from an application server, an indication of data to be delivered to at least one wireless device (e.g., at least one UE). The network node may determine a handling of the data (e.g., at the network node, at another network node, or at a radio access network (RAN)), and may transmit at least one report relating to the handling of the data to the application server.

In some examples, the described techniques may enable a modem of a wireless device (e.g., a UE) to receive, from an application processor of the wireless device, a request to receive at least one report on events monitored at the modem, and to transmit the at least one report to the application processor.

The following description provides examples, and is not limiting of the scope, applicability, or examples set forth in the claims. Changes may be made in the function and arrangement of elements discussed without departing from the scope of the disclosure.

Various examples may omit, substitute, or add various procedures or components as appropriate. For instance, the methods described may be performed in an order different from that described, and various operations may be added, omitted, or combined. Also, features described with respect to some examples may be combined in other examples.

FIG.1shows an example of a wireless communication system100, in accordance with one or more aspects of the present disclosure. The wireless communication system100may include a radio access network (RAN) including a plurality of base stations105(e.g., eNodeBs (eNBs), gNodeBs (gNBs), and/or radio heads (RHs)), UEs115, and a core network130. The core network130may include one or more network nodes140and may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The base stations105may interface with the core network130through backhaul links132(e.g., S1, N2, etc.) and may perform radio configuration and scheduling for communication with the UEs115, or may operate under the control of a base station controller (not shown). In various examples, the base stations105may communicate, either directly or indirectly (e.g., through core network130), with each other over backhaul links134(e.g., X2, Xn, etc.), which may be wired or wireless communication links.

The base stations105may wirelessly communicate with the UEs115via one or more base station antennas. Each of the base station105sites may provide communication coverage for a respective geographic coverage area110. In some examples, a base station105may be referred to as a base transceiver station, a radio base station, an access point, a radio transceiver, a gNB, a NodeB, an eNodeB (eNB), a Home NodeB, a Home eNodeB, or some other suitable terminology. The geographic coverage area110for a base station105may be divided into sectors (not shown) making up a portion of the coverage area. The wireless communication system100may include base stations105of different types (e.g., macro or small cell base stations). There may be overlapping geographic coverage areas110for different technologies.

In some examples, the wireless communication system100may include an LTE/LTE-A network and may employ narrow-band communication techniques. In LTE/LTE-A networks, the term evolved Node B (eNB) may be used to describe the base stations105. The wireless communication system100may be a Heterogeneous LTE/LTE-A network in which different types of eNBs provide coverage for various geographical regions. For example, each eNB or base station105may provide communication coverage for a macro cell, a small cell, or other types of cell. The term “cell” is a 3GPP term that can be used to describe a base station, a carrier or component carrier associated with a base station, or a coverage area (e.g., sector, etc.) of a carrier or base station, depending on context. In some examples, the wireless communication system100may include a next generation or 5G network that employs narrow-band communication techniques (in which case the base stations105may, in some examples, be replaced by access nodes including radio heads (e.g., smart radio heads) and access node controllers). In some examples, the base station105may also be referred to as a gNodeB, a gNB, an eNodeB, or an eNB.

A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscriptions with the network provider. A small cell may be a lower-powered base station, as compared with a macro cell that may operate in the same or different (e.g., licensed, shared, etc.) radio frequency spectrum bands as macro cells. Small cells may include pico cells, femto cells, and micro cells according to various examples. A pico cell may cover a relatively smaller geographic area and may allow unrestricted access by UEs with service subscriptions with the network provider. A femto cell may also cover a relatively small geographic area (e.g., a home) and may provide restricted access by UEs having an association with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs for users in the home, and the like). An eNB or a gNB for a macro cell may be referred to as a macro eNB or a macro gNB, respectively. An eNB or a gNB for a small cell may be referred to as a small cell eNB, a small cell gNB, a pico eNB, a pico gNB, a femto eNB, a femto gNB, a home eNB, or a home gNB. An eNB or gNB may support one or multiple (e.g., two, three, four, and the like) cells (e.g., component carriers).

The wireless communication system100may support synchronous or asynchronous operation. For synchronous operation, the base stations may have similar frame timing, and transmissions from different base stations may be approximately aligned in time. For asynchronous operation, the base stations may have different frame timing, and transmissions from different base stations may not be aligned in time. The techniques described herein may be used for either synchronous or asynchronous operations.

The communication networks that may accommodate some of the various disclosed examples may be packet-based networks that operate according to a layered protocol stack. In the user plane, communications at the bearer or Packet Data Convergence Protocol (PDCP) layer may be IP-based. A Radio Link Control (RLC) layer may perform packet segmentation and reassembly to communicate over logical channels. A Medium Access Control (MAC) layer may perform priority handling and multiplexing of logical channels into transport channels. The MAC layer may also use Hybrid ARQ (HARQ) to provide retransmission at the MAC layer to improve link efficiency. In the control plane, the Radio Resource Control (RRC) protocol layer may provide establishment, configuration, and maintenance of an RRC connection between a UE115and the base stations105or core network130supporting radio bearers for the user plane data. At the Physical (PHY) layer, the transport channels may be mapped to physical channels.

The UEs115may be dispersed throughout the wireless communication system100, and each UE115may be stationary or mobile. A UE115may also include or be referred to by those skilled in the art as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. A UE115may be a cellular phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a tablet computer, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a NB-LTE device, a M2M device, a MTC device, an eMTC device, a NB-IoT device or the like. A UE may be able to communicate with various types of base stations and network equipment, including macro eNBs, small cell eNBs, gNBs, relay base stations, and the like. A UE115such as an IoT device may, in some examples, be characterized by one or more non-traditional UE characteristics, such as: a lack of mobility, small size data exchanges (e.g., infrequent transmissions and receptions), infrequent data exchanges, delay tolerant data exchanges, or a requirement for long battery life (sometimes measured in years).

The communication links125shown in wireless communication system100may include downlinks (DL), from a base station105to a UE115, or uplinks (ULs), from a UE115to a base station105. The downlinks may also be called forward links, while the uplinks may also be called reverse links. The communication links125may include, for example, resources for wide-band physical control channels (e.g., a PRACH, physical downlink control channel (PDCCH), enhanced PDCCH (ePDCCH), or physical uplink control channel (PUCCH)), wide-band physical data channels (e.g., a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH)), narrow-band physical control channels (e.g., a narrow-band PRACH, narrow-band PDCCH, a narrow-band ePDCCH, or a narrow-band PUCCH), and narrow-band physical data channels (e.g., a narrow-band PDSCH or narrow-band PUSCH). In some cases, a UE115may communicate with the core network130, for example, through communication link135.

In some examples, each communication link125may include one or more carriers, where each carrier may be a signal made up of multiple sub-carriers (e.g., waveform signals of different frequencies) modulated according to the various radio technologies described above. Each modulated signal may be sent on a different sub-carrier and may carry control information (e.g., reference signals, control channels, etc.), overhead information, user data, etc. The communication links125may transmit bidirectional communications using a frequency division duplexing (FDD) operation (e.g., using paired spectrum resources) or a time division duplexing (TDD) operation (e.g., using unpaired spectrum resources). Frame structures for FDD operation (e.g., frame structure type 1) and TDD operation (e.g., frame structure type 2) may be defined.

Wireless communication systems (e.g., LTE/LTE-A networks) have been optimized to cater to the non-traditional characteristics of IoT devices. The optimizations include, for example, Power Saving Mode (PSM) and Extended Idle Discontinuous Reception (Extended I-DRX) Mode.

In PSM, a wireless device may not perform access stratum (AS) or non-access stratum (NAS) procedures (e.g. page monitoring, mobility management related procedures, etc.) in the absence of mobile-originated (MO) data, except for periodic registration. Upon a MO data event and/or periodic registration event, a wireless device may find a suitable cell and enter a Connected Mode to perform data transfer and/or to register with a network. The network typically transitions a wireless device back to PSM upon completion of a data transfer and/or periodic registration exchange (possibly after waiting for some period of inactivity).

When mobile-terminated (MT) traffic arrives at a network node from an application server for a wireless device, the network may not be able to reach the wireless device until the wireless device initiates a connection with the network (e.g., due to an MO data event and/or periodic registration event). When MO data events are infrequent (which may be typical for an IoT device) and periodic registration timers are configured to be long (e.g., a few hours) to optimize device battery life, a wireless device may not be reachable for a long duration. During this period of time when the wireless device is unreachable, an application server may resend a data packet to the wireless device multiple times. The multiple transmissions of the data packet may be unnecessary.

To address some of the limitation of PSM, a Service Capability Exposure Functionality (SCEF) server has been introduced in the core network for PSM. In some cases, the SCEF server may also provide an Application Program Interface (API) to the application server, enabling the application server to communicate with the core network. In some other cases, an application server may subscribe to reachability monitoring via the SCEF server. In turn, the SCEF server may indicate to the application server when a wireless device becomes reachable, so that the application server can start sending MT data that it has for the wireless device. However, in such cases, it may take a long time for the data to reach the wireless device, since the data has to come all the way from the application server. The network may therefore have to keep the wireless device in Connected Mode for a long time, resulting in device battery consumption.

When a power saving function is enabled (e.g., in Extended I-DRX Mode), a wireless device periodically wakes up to monitor paging on a downlink. The frequency of periodic wake ups may be determined based at least in part on the latency requirements of a service that the wireless device is using. When the power saving function is enabled (e.g., Extended I-DRX Mode), a wireless device may perform required AS or NAS procedures (if any) for mobility management, similarly to what occurs during an LTE/LTE-A Idle mode, so that the network has tracking area level information of the wireless device and can reach the wireless device for paging.

Upon receiving a paging message (e.g., a paging message indicating that MT data is pending) from a network, or upon an MO data/signaling event, a wireless device in a power saving mode (e.g., Extended I-DRX Mode) may enter a Connected Mode for data/signaling exchange. The network may transition the wireless device back to Idle Mode upon completion of a data/signaling exchange (and possibly after waiting for some period of inactivity).

In some examples, a power saving mode (e.g., Extended I-DRX Mode) enables long (extended) DRX cycles in the order of tens of minutes. In 5G, these cycle lengths (e.g., DRX cycle lengths) may be further extended to an order of hours/days.

Building on LTE/LTE-A Idle Mode, a store and forward (S&F) functionality may be implemented in the core network for MT data transmitted when a power saving function is enabled (e.g., Extended I-DRX Mode). In some cases, a network function may provide the S&F functionality in the core network. In some examples, the network function may be or include a serving gateway (S-GW), a Session Management Function (SMF), a user plane function (UPF), or any other network function capable of S&F functionality. When MT data arrives at a S-GW (as one example of a network function providing the S&F functionality in the core network) from an application server, the S-GW may notify a MME or any other function capable of providing control plane functionality in a core network (e.g., Access and Mobility Management Function (AMF)) of receipt of the data via a Downlink Data Notification (DDN) message. In the DDN reply message, the MME or AMF may ask the S-GW, or any other network function with S&F functionality, to store the data for an extended time if a wireless device to which the data is being transmitted is using an extended DRX cycle. In some other cases, the S-GW or another function with S&F functionality may also handle data tunneling and data routing in a network.

Following reception of the DDN message, a function with S&F functionality, such as the S-GW, may then store the data pending further notification from the MME or AMF. In the meantime, the MME or AMF may page the wireless device at the next occasion per its (extended) DRX (paging) cycle. Once the wireless device receives the page and enters a Connected Mode, the MME or AMF may notify the S-GW. The S-GW may then forward the data to the wireless device. However, no notification is provided to the application server regarding whether the packet is dropped or stored. Hence, the application server may end up resending a data packet multiple times unnecessarily.

Thus, PSM enables the monitoring of data handling in the network node (via an SCEF server), but does not provide store and forward functionality for data handled in the network node. A wireless device operating in PSM may therefore be kept in Connected Mode for a longer time when an application server has MT data to send to the wireless device. If the wireless device is battery-operated, extending the time that a wireless device remains in Connected Mode can adversely affect the wireless device's battery. In contrast, activating or enabling a power save function (e.g., Extended I-DRX) may provide store and forward functionality for data handled in the core network, but may not provide for monitoring data handling in the core network. Thus, when a power saving function is enabled (e.g., in Extended I-DRX), an application server may not be aware of the status of data packets transmitted to a wireless device (e.g., the application server may not receive indications of when data packets are stored or lost in the core network), and the application server may resend a data packet multiple times and unnecessarily increase the traffic load on the core network.

The present disclosure describes techniques for enabling the monitoring of data handling at a one or more network nodes (e.g., one or more nodes of a core network, or one or more nodes that handle data between the core network and a RAN). The monitoring functionality may be enabled in a control path defined by one or more network nodes, with components of the control path controlling and/or monitoring events associated with a data path defined by one or more network nodes (in which the network nodes that define the data path may or may not include some or all of the network nodes that define the control path).

In some examples, the monitoring of the data handling may include a monitoring of store and forward functionality at one or more network nodes. The store and forward functionality may be introduced in the data path. The use of store and forward functionality may reduce delays in the transmission of data from an application server to at least one wireless device, while the monitoring functionality may provide the application server with visibility into the handling of data prior to delivery of the data to the at least one wireless device, including visibility into when store and forward functionality is invoked, and visibility into how the store and forward functionality affects the handling of the data.

In some examples, monitoring functionality may be provided at one or more of the network nodes140described with reference toFIG.1by providing the network node140with a data handling monitor120. The data handling monitor120may be an example of aspects of the data handling monitor220described with reference toFIG.2, among other examples.

The data handling monitor120may receive an indication of data to be delivered to at least one wireless device (e.g., at least one UE115) from an application server150in communication with the core network130; determine a handling of the data (e.g., at the network node140, at another network node140, or at one of the base stations105); and transmit at least one report relating to the handling of the data to the application server150. The application server150may be an example of aspects of the application server230,230-a,230-b, and/or230-cdescribed with reference toFIGS.2-5, among other examples.

The present disclosure also describes techniques for enabling the monitoring of data handling at a modem by an application processor (e.g., within a wireless device or UE115). In the absence of such monitoring functionality, an application processor of a wireless device may not be aware of the status of a modem of the wireless device. For example, an application processor may not know whether a modem is active (or ready to transmit) or not active (e.g., dormant, or not ready to transmit), or the application processor may not know when the modem is scheduled to transition from an inactive state to an active state. When an application processor does not know the status of a modem, the application processor may send application data to the modem for transmission over a radio frequency spectrum, and may cause the modem to transition from an inactive state to an active state to transmit the data.

In IoE applications, in which the amount of data to be transmitted is small and delay tolerant, and in which the preservation of battery life may be more critical than making a data transmission, it may be more desirable to hold the data until a modem becomes active than to wake the modem at a non-scheduled wakeup time to make a data transmission. Also, it may be more battery-efficient to wait until the amount of data to be transmitted exceeds a threshold amount before transitioning the modem from an inactive state to an active state (e.g., due to the overhead associated with such a state transition).

By enabling a modem to transmit reports on modem events to an application processor, the application processor may store data to be transmitted over a radio frequency spectrum until the modem is an active state. Alternatively, the application processor may transmit the data to the modem; the modem may temporarily store the data; and the modem may transmit reports on the handling of the data (e.g., the storage and transmission of data) to the application processor, so that the application processor may regulate its transmission of additional data to the modem and/or determine whether data needs to be retransmitted to the modem (e.g., because a data packet is dropped).

In some examples, a modem620of a UE115described with reference toFIG.1may provide the UE115with modem monitoring functionality. For example, the modem620may receive, from an application processor of the UE115, a request to receive at least one report on events monitored at the modem620. The modem620may transmit the at least one report to the application processor of the UE115. The modem620may be an example of aspects of the modem620-adescribed with reference toFIG.6, among other examples.

FIG.2shows an example architecture200of one or more network nodes140-a, in accordance with one or more aspects of the present disclosure. The network node(s)140-amay be examples of aspects of the network nodes140described with reference toFIG.1, or examples of other network nodes that handle data between the core network130and a RAN.

The network node(s)140-amay include a data path205and a control path210(also referred to as a user plane path205and a control plane path210, respectively). The data path205may optionally include data store and forward functionality, such as a store and forward (S&F) manager215, or any other network function with S&F functionality such as a SMF and/or UPF. The control path210may include monitoring functionality, such as one or more data handling monitors220. One or more application server interfaces225may provide an interface to the data path205and the control path210(or components thereof) to an application server230. One or more RAN interfaces235may provide an interface to the data path205and the control path210to a RAN240. The application server230may communicate with one or more wireless devices (e.g., UEs) connected to the RAN240, by means of the network node(s)140-aand the RAN240.

In some examples, the data path205may receive, from the application server230, data to deliver to at least one wireless device connected to the RAN240. Components of the data path205may handle the data (e.g., receive, transmit, store, drop, or process the data) at the network node(s)140-a. Components of the control path210(e.g., the data handing monitor(s)220) may monitor the handling of the data at the network node(s)140-aand transmit at least one report relating to the handling of the data to the application server230.

In some examples, one or more of the network node(s)140-amay determine that a wireless device to which data is to be delivered is unreachable, and the S&F manager215may store the data at one or more of the network node(s)140-afor a period of time (e.g., until the wireless device becomes reachable, or until a maximum time to store the data at the network node(s)140-ais reached). If the wireless device that was unreachable becomes reachable, the S&F manager215may forward the stored data to the wireless device. Information pertaining to the storing and forwarding of the data may be collected by one or more of the data handling monitor(s)220and reported to the application server230.

In some examples, components of the control path210may receive, from the application server230, a data handling request applicable to data received from the application server230. The data handling request may include, for example, a first indication of whether to store data at one or more of the network node(s)140-a, prior to delivery of the data to a wireless device, when the wireless device to which the data is to be delivered is unreachable; a second indication of a maximum time to store data at one or more of the network node(s)140-a; a maximum number of data packets to store at one or more of the network node(s)140-awhen the wireless device is unreachable; or a combination thereof.

In some examples, components of the control path210may receive, from the application server230, a data handling monitoring request applicable to data received from the application server230. The data handling monitoring request may indicate to one or more of the network node(s)140-a, for example, that reports relating to data handling at the network node(s)140-ashould be provided to the application server230, or that a certain type or types of information (or reports) should be provided to the application server230.

In some examples, the information transmitted to the application server230in the at least one report relating to the handling of data at the network node(s)140-amay include, for example, a first indication of data packets received at one or more of the network node(s)140-a; a second indication of data packets stored at one or more of the network node(s)140-a; a third indication of an expected data packet storage time; a fourth indication of a maximum data packet storage time; a fifth indication of a number of data packets queued for delivery to at least one wireless device; a sixth indication of data packets forwarded to at least one wireless device; a seventh indication of data packets dropped at a core network (e.g., data packets dropped by the S&F manager215because of expiration of a maximum data packet storage time); an eighth indication of data packets dropped in the RAN240; a ninth indication of data packets successfully received by at least one wireless device; or a combination thereof.

FIG.3shows an example architecture300of a core network130-a(e.g., a plurality of network nodes), in accordance with one or more aspects of the present disclosure. The core network130-ais an example of aspects of the core network130-adescribed with reference toFIG.1. The core network130-amay include a data path205-aand a control path210-a(also referred to as a user plane path205-aand a control plane path210-a, respectively).

The core network130-amay include a packet network function305(e.g., a packet gateway (P-GW)) to provide an interface between the core network130-aand other packet data networks, a S&F network function310providing S&F functionality (e.g., a serving gateway (S-GW), a SMF, a UPF, etc.), a control plane network entity315such as a mobility management entity (MME), or another network function with control plane functionality (e.g., an AMF), and a Service Capability Exposure Functionality (SCEF) server320. The S&F network function310may include a store and forward (S&F) manager215-a, a mobility anchor325, and a controller330. In some examples, the packet network function305, the S&F manager215-a, and the mobility anchor325may define portions of the data path205-a, and the SCEF server320, the control plane network entity315, and the controller330may define portions of the control path210-a. In some examples, the core network130-amay define a network node, or one or more of the packet network function305, the S&F network function310, the control plane network entity315, or the SCEF server320may each define one or more network nodes. In some examples, the S&F network function310, another S&F network function, or another network node may be located outside of the core network130-a(e.g., between the core network130-aand a RAN240-a).

An application server230-amay communicate with wireless devices (e.g., UEs) connected to the RAN240-avia the core network130-a. The application server230-amay communicate with the core network130-aon a user plane (e.g., over the data path205-a) and a control plane (e.g., over the control path210-a). For example, the application server230-amay transmit data that is to be delivered to at least one wireless device over the data path205-ato the packet network function305. The packet network function305may transmit the data to the S&F network function310. When a wireless device of the at least one wireless device is available (e.g., in a Connected Mode), the S&F network function310may forward the data to the RAN240-a, via the mobility anchor325, for delivery to the at least one wireless device. When a wireless device of the at least one wireless device is not available, the S&F manager215-amay cause the data to be stored at the core network130-a(e.g., at the S&F network function310, or any other network function with S&F functionality, such as SMF, UPF, etc.).

The controller330may monitor the handling of data at the core network130-a, and in some examples may monitor the S&F manager215-aand the mobility anchor325. The controller330may also monitor the RAN240-aand/or communications between the core network130-a(or S&F network function310) and the RAN240-a(e.g., by subscribing to monitoring events provided by the RAN240-a). The control plane network entity315may also monitor the handling of data at the core network130-a(e.g., at the S&F network function310), and may monitor the RAN240-aand/or communications between the core network130-aand the RAN240-a(e.g., by subscribing to monitoring events provided by the RAN240-a). In some examples, the controller330, control plane network entity315, and/or any other network function with control plane functionality (e.g., an AMF or SMF) may collect information associated with the handling of data at the core network130-aand forward the collected information (a report relating to the handling of data at the core network130-a) to the application server230-avia the SCEF server320. In some examples, the SCEF server320may provide an Application Program Interface (API) to the application server230-a, enabling the application server230-ato communicate with the core network130-a.

Furthermore, in some examples, the controller330may collect information associated with the handling of data at the core network130-aand forward the collected information to a control plane network entity, such as the control plane network entity315, or any other network function with control plane functionality (e.g., an AMF). In these latter examples, the control plane network entity315or the control plane network function, may forward the information received from the controller330to the application server230-avia the SCEF server320. The information may be forwarded with or without additional information collected by the control plane network entity315or the control plane network function.

The information relating to the handling of data at the core network130-amay include, for example, a first indication of data packets received at the core network130-a(e.g., at the S&F network function310-a); a second indication of data packets stored at the core network130-a(e.g., at the S&F network function310-a); a third indication of an expected data packet storage time; a fourth indication of a maximum data packet storage time; a fifth indication of a number of data packets queued for delivery to at least one wireless device; a sixth indication of data packets forwarded to at least one wireless device; a seventh indication of data packets dropped in the core network130-a(e.g., data packets dropped by the S&F manager215-abecause of expiration of a maximum data packet storage time); an eighth indication of data packets dropped in the RAN240-a; a ninth indication of data packets successfully received by at least one wireless device; or a combination thereof. The information relating to the handling of data at the core network130-amay be collected per wireless device (e.g., per UE) and access point name (APN).

In some examples, the application server230-amay transmit a data handling request or data handling monitoring request to the SCEF server320on the control plane. The data handling request may include, for example, a first indication of whether to store data at the core network130-a, prior to delivery of the data to a wireless device, when the wireless device to which the data is transmitted is unreachable; a second indication of a maximum time to store data at the core network130-a; a maximum number of data packets to store at the core network130-a; or a combination thereof. In some examples, one or more of the decision to store data at the core network130-a, the maximum time to store data, or the maximum number of data packets to store at the core network130-amay be based on a parameter (or set of parameters) of the core network130-a.

In some examples, the S&F network function310or S&F manager215-amay control whether the S&F network function310or S&F manager215-astores data packets at the core network130-a, and/or may control the maximum time to store data or the maximum number of data packets to store. In some examples, the control plane network entity315may control whether the S&F network function310or S&F manager215-astores data packets at the core network130-b, and may indicate to the S&F network function310or S&F manager215-athe maximum time to store data or the maximum number of data packets to store. In either set of examples, the control plane network entity315or S&F network function310may or may not receive data handling parameters (e.g., an indication of whether to store data at the core network130-a, a maximum time to store data, or a maximum number of data packets to store) from the SCEF server320. In some examples, store and forward data handling parameters may be based at least in part on available memory for storing data at the core network130-a, or on a traffic load of the core network130-a.

In some examples, a data handling monitoring request may indicate that the application server230-ais subscribing to reports relating to the handling of data at the core network130-a. In some examples, a data handling monitoring request may indicate a type or types of information (or reports) that the application server230-awants to receive.

The SCEF server320may transmit reports relating to the handling of data at the network node, to the application server230-a, on demand, periodically, in response to a trigger event, or a combination thereof. In some examples, the SCEF server320may transmit the reports reactively, when the reports are received from the S&F network function310, control plane network entity315, or a control plane network function, such as an AMF. In some examples, the SCEF server320may subscribe (e.g., with the S&F network function310or control plane network entity315) to receive information related to data handling from the S&F network function310or control plane network entity315. In some examples, the SCEF server320may request reports from the S&F network function310or control plane network entity315. In some examples, the SCEF server320may provide an API to the application server, enabling the application server to communication with the core network130-a.

When a report relating to data handling at the core network130-ais to include an indication of data packets successfully received by at least one wireless device, the S&F network function310or control plane network entity315may subscribe (e.g., with the RAN240-a) to receive such information from the RAN240-a.

FIG.4shows a message flow400for monitoring data handling at a core network130-b, directly via a S&F network function310-a(i.e., without transmitting information collected at the S&F network function310-athrough a control plane network entity315-a), in accordance with one or more aspects of the present disclosure. By way of example, the message flow400occurs between a UE115-a, a RAN240-b, the control plane network entity315-a(e.g., MME, AMF, amongst other examples of network functions with control plane functionality), the S&F network function310-a(e.g., S-GW, SMF or UPF, amongst other examples of network functions providing S&F functionality), a packet network function305-a(e.g., a P-GW), a SCEF server320-a, and an application server (AS)230-b. As shown, the control plane network entity315-a, S&F network function310-a, packet network function305-a, and SCEF server320-amay be part of the core network130-b. The UE115-ais an example of aspects of the UEs115described with reference toFIG.1. The RAN240-b, control plane network entity315-a, S&F network function310-a, packet network function305-a, SCEF server320-a, and AS230-bare examples of aspects of the RAN240, control plane network entity315, S&F Network Function310, packet network function305, SCEF server320, and application server230described with reference toFIG.2or3. For purposes of this description, each of the packet network function305-a, S&F network function310-a, control plane network entity315-a, and SCEF server320-amay be provided by one or more network nodes, or by the same or different network nodes.

At405, the UE115-amay register with the RAN240-band negotiate a power saving mode with the RAN240-b, control plane network entity315-a, and/or S&F network function310-a.

At410, data handling monitoring may be configured for the AS230-b. In some examples, configuration of the data handling monitoring may begin with the AS's transmission of a data handling monitoring request (e.g., a Monitoring Request message) to the SCEF server320-a(e.g., at415). At415-a, the SCEF server320-amay forward the data handling monitoring request (e.g., the Monitoring Request message, or parameters thereof, or a request based at least in part thereon) to the S&F network function310-a, to subscribe to reports from the S&F network function310-arelated to data handling at the core network130-b. At420, the S&F network function310-amay return an acknowledgement of the data handling monitoring request (e.g., a Monitoring Accept message) to the SCEF server320-a. At420-a, the SCEF server320-amay forward the acknowledgement (e.g., the Monitoring Accept message, or an acknowledgement based at least in part thereon) to the AS230-b.

At425, the UE115-amay release its connection with the network (e.g., transition from a Connected Mode to an Idle Mode or PSM), and the control plane network entity315-amay enable store and forward (S&F) functionality for data transmitted to the UE115-a.

At430, the AS230-bmay transmit a MT data packet to the UE115-a. The MT data packet may be received at the packet network function305-aat430, and transmitted to the S&F network function310-aat430-a. At435, the S&F network function310-amay store the data packet; and at440, the S&F network function310-amay transmit a DDN to the control plane network entity315-a. Because the UE115-areleased its connection with the network at425, the control plane network entity315-amay return a DDN Hold message to the S&F network function310-aat445. At450, the S&F network function310-amay transmit, to the SCEF server320-a, a report indicating that the data packet is stored at the core network130-b; and at450-a, the SCEF server320-amay transmit the report (or a report based thereon) to the AS230-b.

At455, the control plane network entity315-amay transmit a paging message to the UE115-ain accordance with a sleep cycle or extended DRX cycle of the UE115-a. At455-a, the paging message may be received by the RAN240-band forwarded to the UE115-a.

At or before460, the UE115-amay wake up or otherwise enter a Connected Mode with the network. While connected to the network, the UE115-amay receive the paging message transmitted at455-a, and in some examples may transmit a scheduling request (SR), tracking area update (TAU), or other message to the RAN240-b. In response to receiving an indication that the UE115-ais in Connected Mode, the control plane network entity315-amay indicate to the S&F network function310-athat stored data may be transmitted to the UE115-a. At465, the S&F network function310-amay transmit the data stored at435to the UE115-a. In some examples, the S&F network function310-amay also or alternatively transmit, to the UE115-a, other data stored or received for transmission to the UE115-a.

At470, the S&F network function310-amay transmit, to the SCEF server320-a, another report. The report may indicate that the data packet was forwarded to the UE115-a, or that the data packet was successfully received by the UE115-a(when information on successful delivery is received from the UE115-aor RAN240-b. The SCEF server320-amay transmit the report (or a report based thereon) to the AS230-bat470-a.

In some examples, reports transmitted by the S&F network function310-a, such as the reports transmitted at450and470, may be based at least in part on information relating to data packets received at the core network130-b(e.g., at the S&F network function310-a); information relating to data packets stored at the core network130-b(e.g., at the S&F network function310-a); information relating to one or more expected data packet storage times; information relating to one or more maximum data packet storage times; information relating to numbers of data packets queued for delivery to wireless devices; information relating to data packets forwarded to wireless devices; information relating to data packets dropped in the core network130-b; information relating to data packets dropped in the RAN; or combinations thereof. In some examples, reports transmitted by the S&F network function310-amay also or alternatively be based on information collected by the RAN240-band provided to the S&F network function310-a, such as information relating to data packets successfully received by wireless devices.

In some examples, the messages transmitted and operations performed during the message flow400may be performed in other orders, or may include other or different messages or operations.

FIG.5shows a message flow500for monitoring data handling at a core network130-c, through a control plane network entity315-b, in accordance with one or more aspects of the present disclosure. By way of example, the message flow500occurs between a UE115-b, a RAN240-b, the control plane network entity315-b(e.g., MME, AMF, amongst some examples of network functions with control plane functionality), the S&F network function310-b(e.g., S-GW, SMF or UPF, amongst some examples of network functions providing S&F functionality), a packet network function305-b(e.g., a P-GW), a SCEF server320-b, and an AS230-c. As shown, the control plane network entity315-b, S&F network function310-b, packet network function305-b, and SCEF server320-bmay be part of the core network130-c. The UE115-bis an example of aspects of the UEs115described with reference toFIG.1or4. The RAN240-c, control plane network entity315-b, S&F network function310-b, packet network function305-b, SCEF server320-b, and AS230-care examples of aspects of the RAN240, control plane network entity315, S&F network function310, packet network function305, SCEF server320, and application server230described with reference toFIG.2,3, or4. For purposes of this description, each of the packet network function305-b, S&F network function310-b, control plane network entity315-b, and SCEF server320-bmay be provided by one or more network nodes, or by the same or different network nodes.

At505, the UE115-bmay register with the RAN240-cand negotiate a power saving mode with the RAN240-b, control plane network entity315-b, and/or S&F network function310-b.

At510, data handling monitoring may be configured for the AS230-c. In some examples, configuration of the data handling monitoring may begin with the AS's transmission of a data handling monitoring request (e.g., a Monitoring Request message) to the SCEF server320-b(e.g., at515). At515-a, the SCEF server320-bmay forward the data handling monitoring request (e.g., the Monitoring Request message, or parameters thereof, or a request based at least in part thereon) to the control plane network entity315-b, to subscribe to reports from the control plane network entity315-brelated to data handling at the core network130-c. At515-b, the control plane network entity315-bmay forward the data handling monitoring request (e.g., the Monitoring Request message, or parameters thereof, or a request based at least in part thereon) to the S&F network function310-b, to subscribe to reports from the S&F network function310-brelated to data handling at the core network130-c. At520, the S&F network function310-bmay return an acknowledgement of the data handling monitoring request (e.g., a Monitoring Accept message) to the control plane network entity315-b. At520-a, the control plane network entity315-bmay forward the Monitoring Accept message (or an acknowledgement based at least in part thereon) to the SCEF server320-b. At520-b, the SCEF server320-bmay forward the acknowledgement (e.g., the Monitoring Accept message, or an acknowledgement based at least in part thereon) to the AS230-c.

At525, the UE115-bmay release its connection with the network (e.g., transition from a Connected Mode to an Idle Mode or PSM), and the control plane network entity315-bmay enable S&F functionality for data transmitted to the UE115-b.

At530, the AS230-cmay transmit a MT data packet to the UE115-b. The MT data packet may be received at the packet network function305-bat530, and transmitted to the S&F network function310-bat530-b. At535, the S&F network function310-bmay store the data packet; and at540, the S&F network function310-bmay transmit a DDN with a queue status (i.e., data packet queue status) to the control plane network entity315-b. Because the UE115-breleased its connection with the network at525, the control plane network entity315-bmay return a DDN Hold message to the S&F network function310-bat545. At550, the control plane network entity315-bmay transmit, to the SCEF server320-b, a report indicating that the data packet is stored at the core network130-c; and at550-b, the SCEF server320-bmay transmit the report (or a report based thereon) to the AS230-c. In some examples, the DDN Hold message transmitted at545may include a data handling monitoring request pertaining to the data stored at535.

At555, the control plane network entity315-bmay transmit a paging message to the UE115-bin accordance with a sleep cycle or extended DRX cycle of the UE115-b. At555-b, the paging message may be received by the RAN240-cand forwarded to the UE115-b.

At or before560, the UE115-bmay wake up or otherwise enter a Connected Mode with the network. While connected to the network, the UE115-bmay receive the paging message transmitted at555-b, and in some examples may transmit a SR, TAU, or other message to the RAN240-c. In response to receiving an indication that the UE115-bis in Connected Mode, the control plane network entity315-bmay indicate to the S&F network function310-bthat stored data may be transmitted to the UE115-b. At565, the S&F network function310-bmay transmit the data stored at535to the UE115-b. In some examples, the S&F network function310-bmay also or alternatively transmit, to the UE115-b, other data stored or received for transmission to the UE115-b.

At570, the control plane network entity315-bmay transmit, to the SCEF server320-b, another report relating to the handling of data at the core network130-c. The report may indicate that the data packet was forwarded to the UE115-b, or that the data packet was successfully received by the UE115-b(when information on successful delivery is received from the UE115-bor RAN240-c. The SCEF server320-bmay transmit the report (or a report based thereon) to the AS230-cat570-a.

In some examples, reports transmitted by the control plane network entity315-b, such as the reports transmitted at550and570, may be based at least in part on information collected by the S&F network function310-band transmitted to the control plane network entity315-b. The collected information may include, for example, information relating to data packets received at the network node140-b(e.g., at the S&F network function310-b); information relating to data packets stored at the network node140-b(e.g., at the S&F network function310-b); information relating to one or more expected data packet storage times; information relating to one or more maximum data packet storage times; information relating to numbers of data packets queued for delivery to wireless devices; information relating to data packets forwarded to wireless devices; information relating to data packets dropped in the core network130-c; information relating to data packets dropped in the RAN; or combinations thereof.

In some examples, reports transmitted by the control plane network entity315-bmay also or alternatively be based on information collected by the control plane network entity315-b, such as information relating to one or more expected data packet storage times, or information relating to one or more maximum data packet storage times. In some examples, reports transmitted by the control plane network entity315-bmay also or alternatively be based on information collected by the RAN240-cand provided to the control plane network entity315-b, such as information relating to data packets successfully received by wireless devices. Reports transmitted by the control plane network entity315-bmay also or alternatively be based on information inferred by the control plane network entity315-b. For example, the control plane network entity315-bmay infer that a data packet is dropped upon expiration of a maximum data packet storage time.

In some examples, the messages transmitted and operations performed during the message flow500may be performed in other orders, or may include other or different messages or operations.

FIG.6shows an example architecture600of a wireless device (e.g., a UE115-c), in accordance with one or more aspects of the present disclosure. The UE115-cis an example of aspects of the UE115described with reference toFIG.1,4, or5. The UE115-cmay include an application processor615and a modem620-a. The modem620-amay be coupled to a wireless interface625including one or more transceivers and antennas through which data and control information may be transmitted or received over a radio frequency spectrum (e.g., to a network node140or core network130). The components of the UE115-c(including components of the application processor615and modem620-a) may define a data path605and a control path610(also referred to as a user plane path605and a control plane path610). The data path605and control path610may respectively enable the transmission of data and control information (or signals) between the application processor615and the modem620-a.

In some examples, the application processor615may transmit, to the modem620-a, a request to receive at least one report on events monitored at the modem. The request may be transmitted via the control path610, and may be transmitted prior to or with a data transmission over the data path605. The request may indicate to the modem620-a, for example, that reports relating to modem events should be transmitted to the application processor615, or that a certain type or types of information (or reports) should be transmitted to the application processor615.

In response to receiving the request from the application processor615(or proactively, in the absence of a request), the modem620-amay transmit at least one report (e.g., at least one status report) to the application processor615. In some examples, the at least one report may include a modem status or a data packet status. The modem status may include, for example, a first indication of an expected wait time until the modem620-abecomes active or ready to transmit; a second indication of a modem state transition from not active or not ready to transmit, to active; a third indication of a modem state transition from active to not active; or a combination thereof. The data packet status may include, for example, a first indication of data packets received and stored in a modem memory630; a second indication of data packets queued at the modem620-a; a third indication of data packets dropped by the modem620-a; a fourth indication of data packets transmitted by the modem620-a; a fifth indication of data packets successfully received by a device (e.g., a base station or network node) to which the modem620-atransmits over the radio frequency spectrum; or a combination thereof. In some examples, the at least one report may be transmitted to the application processor615on demand, periodically, in response to a trigger event, or a combination thereof.

In some examples, the modem620-amay receive data to transmit over a radio frequency spectrum (e.g., via the wireless interface625) from the application processor615. The data may be received over the data path605. In some examples, the modem620-amay receive an indication from the application processor615that the data is delay tolerant. The indication may be received over the data path605with the data, or over the control path610prior to receiving, with, or after receiving the data. In some examples, the modem620-amay store the data received from the application processor615in the modem memory630, based at least in part on receiving the indication that the data is delay tolerant. In some examples, the modem620-amay transmit a report, to the application processor615, indicating that the data is stored in the modem memory630. The application processor615may also indicate to the modem620-awhen data to be transmitted is delay sensitive, in which case the modem620-amay be configured to wake and transmit the delay sensitive data.

In some examples, the modem620-amay determine that the modem620-ais not active, and may store the data received from the application processor615in the modem memory630based at least in part on determining that the modem620-ais not active. In some examples, the modem620-amay transmit a report to the application processor615indicating that the modem620-ais not active, and the application processor615may temporarily store data to be transmitted over a radio frequency spectrum in an application processor memory (not shown) or the modem memory630. The modem620-amay also transmit, to the application processor615, a report that the data is stored in the modem memory630.

When the modem620-abecome active, the modem620-amay transmit the data stored in the modem memory630over the radio frequency spectrum. In some examples, transmission of the data may trigger the transmission of a report from the modem620-ato the application processor615.

FIG.7is a flow chart illustrating an example of a method700for wireless communication, in accordance with one or more aspects of the present disclosure. For clarity, the method700is described below with reference to aspects of a network node140(e.g., a S&F network function310or control plane network entity315) described with reference toFIG.1,2,3,4, or5. In some examples, one or more components of a network node140may execute one or more sets of codes to control the functional elements of the network node140to perform the functions described below. Additionally or alternatively, the component(s) of the network node140may perform one or more of the functions described below using special-purpose hardware.

At block705, the method700may optionally include receiving from an application server, at a network node of a wireless communication system, a data handling request applicable to data transmitted by the application server. The operation(s) at block705may be performed by components of the control path210described with reference toFIG.2or3, or the S&F Network Function310or control plane network entity315described with reference toFIG.3,4, or5, or any other network function with S&F functionality (e.g., S-GW, SMF, UPF, etc.) or control plane functionality (e.g., MME, AMF, etc.).

At block710, the method700may optionally include receiving from the application server, at the network node, a data handling monitoring request applicable to data transmitted by the application server. The operation(s) at block710may be performed by components of the control path210described with reference toFIG.2or3, or the S&F network function310or control plane network entity315described with reference toFIG.3,4, or5, or any other network function with S&F functionality (e.g., S-GW, SMF, UPF, etc.) or control plane functionality (e.g., MME, AMF, etc.).

At block715, the method700may include receiving from the application server, at the network node, an indication of data to be delivered to at least one wireless device. The operation(s) at block715may be performed by components of the data path205described with reference toFIG.2or3, or the S&F network function310or control plane network entity315described with reference toFIG.3,4, or5, or any other network function with S&F functionality (e.g., S-GW, SMF, UPF, etc.) or control plane functionality (e.g., MME, AMF, etc.).

At block720, the method700may include determining a handling of the data (e.g., a handling of the data at the network node performing the method700, or a handling of the data at another network node (e.g., a node of a core network or a node that handles the data between the core network and a RAN). In some examples, the data may be handled according to a data handling request received at block705. The operation(s) at block720may be performed by components of the data path205described with reference toFIG.2or3, or the S&F network function310or control plane network entity315described with reference toFIG.3,4, or5, or any other network function with S&F functionality (e.g., S-GW, SMF, UPF, etc.) or control plane functionality (e.g., MME, AMF, etc.).

At block725, the method700may include transmitting, to the application server, at least one report relating to the handling of the data. In some examples, the at least one report may be based at least in part on a data handling monitoring request received at block710. The operation(s) at block725may be performed by components of the data path205described with reference toFIG.2or3, or the S&F network function310or control plane network entity315described with reference toFIG.3,4, or5, or any other network function with S&F functionality (e.g., S-GW, SMF, UPF, etc.) or control plane functionality (e.g., MME, AMF, etc.).

In some examples of the method700, the data handling request may include a first indication of whether to store the data, prior to delivery of the data to a wireless device of the at least one wireless device, when the wireless device is unreachable; a second indication of a maximum time to store the data when the wireless device is unreachable; a maximum number of data packets to store when the wireless device is unreachable; or a combination thereof.

In some examples of the method700, the at least one report relating to the handling of the data includes a first indication of data packets received (e.g., at the network node performing the method700, or at another network node); a second indication of data packets stored (e.g., at the network node or at another network node); a third indication of an expected data packet storage time; a fourth indication of a maximum data packet storage time; a fifth indication of a number of data packets queued for delivery to the at least one wireless device; a sixth indication of data packets forwarded to the at least one wireless device; a seventh indication of data packets dropped at a core network; an eighth indication of data packets dropped in a RAN coupling the core network to the at least one wireless device; a ninth indication of data packets successfully received by the at least one wireless device; or a combination thereof.

In some examples of the method700, the at least one report relating to the handling of the data may be transmitted to the application server on demand, periodically, in response to a trigger event, or a combination thereof.

In some examples of the method700, transmitting the at least one report, at block725, may include collecting information associated with the handling of the data at a serving gateway, and forwarding the collected information to the application server via a SCEF server.

In some examples of the method700, transmitting the at least one report, at block725, may include collecting information associated with the handling of the data from a serving gateway, at a MME, SMF, or AMF, and forwarding the collected information from the MME to the application server via a SCEF server. In these examples, the MME may add information to the collected information before forwarding the collected information from the MME to the application server via the SCEF server.

FIG.8is a flow chart illustrating an example of a method800for wireless communication, in accordance with one or more aspects of the present disclosure. For clarity, the method800is described below with reference to aspects of a network node140(e.g., a S&F network function310or control plane network entity315) described with reference toFIG.1,2,3,4, or5. In some examples, one or more components of a network node140may execute one or more sets of codes to control the functional elements of the network node140to perform the functions described below. Additionally or alternatively, the component(s) of the network node140may perform one or more of the functions described below using special-purpose hardware.

At block805, the method800may include receiving from an application server, at a network node of a wireless communication system, an indication of data to be delivered to at least one wireless device. The operation(s) at block805may be performed by components of the data path205described with reference toFIG.2or3, or the S&F network function310or control plane network entity315described with reference toFIG.3,4, or5, or any other network function with S&F functionality (e.g., S-GW, SMF, UPF, etc.) or control plane functionality (e.g., MME, AMF, etc.).

At block810, the method800may optionally include determining that a wireless device of the at least one wireless device is unreachable. Additionally or alternatively, the operation(s) at block810may include receiving a request to store the data received at block805(e.g., receiving a request from a MME at a S-GW) or receiving a notification that the data received at block805is stored (e.g., receiving a notification from a S-GW at a MME). The operation(s) at block810may be performed by components of the control path210described with reference toFIG.2or3, or the S&F network function310or control plane network entity315described with reference toFIG.3,4, or5, or any other network function with S&F functionality (e.g., S-GW, SMF, UPF, etc.) or control plane functionality (e.g., MME, AMF, etc.).

At block815, the method800may include determining a handling of the data (e.g., a handling of the data at the network node performing the method800, or a handling of the data at another network node (e.g., a node of a core network or a node that handles the data between the core network and a RAN). In some examples, the determined handling of the data may include a storage of the data prior to delivery of the data to a wireless device of the at least one wireless device. In some examples, the data may be stored because the wireless device is unreachable, as determined at block810. The operation(s) at block815may be performed by components of the data path205described with reference toFIG.2or3, or the S&F network function310or control plane network entity315described with reference toFIG.3,4, or5, or any other network function with S&F functionality (e.g., S-GW, SMF, UPF, etc.) or control plane functionality (e.g., MME, AMF, etc.).

At block820, the method800may include transmitting, to the application server, at least one report relating to the handling of the data. In some examples, the at least one report may be based at least in part on a storage of the data determined at block815. The operation(s) at block820may be performed by components of the data path205described with reference toFIG.2or3, or the S&F network function310or control plane network entity315described with reference toFIG.3,4, or5, or any other network function with S&F functionality (e.g., S-GW, SMF, UPF, etc.) or control plane functionality (e.g., MME, AMF, etc.).

At block825, the method800may optionally include determining, after the wireless device is unreachable for a period of time, that the wireless device is reachable. Additionally or alternatively, the operation(s) at block825may include receiving a request to forward stored data to a wireless device (e.g., receiving a request from a MME at a S-GW) or receiving a notification that stored data has been forwarded to a wireless device (e.g., receiving a notification from a S-GW at a MME). The operation(s) at block825may be performed by components of the control path210described with reference toFIG.2or3, or the S&F network function310or control plane network entity315described with reference toFIG.3,4, or5, or any other network function with S&F functionality (e.g., S-GW, SMF, UPF, etc.) or control plane functionality (e.g., MME, AMF, etc.).

At block830, the method800may include determining a handling of the data (e.g., a handling of the data at the network node performing the method800, or a handling of the data at another network node (e.g., a node of a core network or a node that handles the data between the core network and a RAN). In some examples, the determined handling of the data may include a forwarding of stored data to a wireless device of the at least one wireless device. The operation(s) at block830may be performed by components of the data path205described with reference toFIG.2or3, or the S&F network function310or control plane network entity315described with reference toFIG.3,4, or5, or any other network function with S&F functionality (e.g., S-GW, SMF, UPF, etc.) or control plane functionality (e.g., MME, AMF, etc.).

At block835, the method800may include transmitting, to the application server, at least one report relating to the handling of the data. In some examples, the at least one report may be based at least in part on the forwarding of the data determined at block830. The operation(s) at block835may be performed by components of the data path205described with reference toFIG.2or3, or the S&F network function310or control plane network entity315described with reference toFIG.3,4, or5, or any other network function with S&F functionality (e.g., S-GW, SMF, UPF, etc.) or control plane functionality (e.g., MME, AMF, etc.).

In some examples of the method800, the at least one report relating to the handling of the data includes a first indication of data packets received (e.g., at the network node performing the method800, or at another network node); a second indication of data packets stored (e.g., at the network node or at another network node); a third indication of an expected data packet storage time; a fourth indication of a maximum data packet storage time; a fifth indication of a number of data packets queued for delivery to the at least one wireless device; a sixth indication of data packets forwarded to the at least one wireless device; a seventh indication of data packets dropped at a core network; an eighth indication of data packets dropped in a RAN coupling the core network to the at least one wireless device; a ninth indication of data packets successfully received by the at least one wireless device; or a combination thereof.

In some examples of the method800, the at least one report relating to the handling of the data may be transmitted to the application server on demand, periodically, in response to a trigger event, or a combination thereof.

In some examples of the method800, transmitting the at least one report, at block835, may include collecting information associated with the handling of the data at a serving gateway, and forwarding the collected information to the application server via a SCEF server.

In some examples of the method800, transmitting the at least one report, at block835, may include collecting information associated with the handling of the data from a serving gateway, at a MME, SMF, or AMF, and forwarding the collected information from the MME to the application server via a SCEF server. In these examples, the MME may add information to the collected information before forwarding the collected information from the MME to the application server via the SCEF server.

In some examples, aspects of the method700and800described with reference toFIGS.7and8may be combined.

FIG.9is a flow chart illustrating an example of a method900for wireless communication, in accordance with one or more aspects of the present disclosure. For clarity, the method900is described below with reference to aspects of a wireless device or UE115described with reference toFIG.1,4,5, or6. In some examples, a wireless device may execute one or more sets of codes to control the functional elements of the wireless device to perform the functions described below. Additionally or alternatively, the wireless device may perform one or more of the functions described below using special-purpose hardware.

At block905, the method900may include receiving from an application processor of a wireless device, at a modem of the wireless device, a request to receive at least one report on events monitored at the modem. The operation(s) at block905may be performed by the modem620-adescribed with reference toFIG.6.

At block910, the method900may include transmitting the at least one report (e.g., at least one status report) to the application processor. The operation(s) at block910may be performed by the modem620-adescribed with reference toFIG.6.

In some examples of the method900, the at least one report may include a modem status or a data packet status. The modem status may include, for example, a first indication of an expected wait time until the modem becomes active; a second indication of a modem state transition from not active to active; a third indication of a modem state transition from active to not active; or a combination thereof. The data packet status may include, for example, a first indication of data packets received and stored in a modem memory; a second indication of data packets queued at the modem; a third indication of data packets dropped by the modem; a fourth indication of data packets transmitted by the modem; a fifth indication of data packets successfully received by a device to which the modem transmits over the radio frequency spectrum; or a combination thereof.

In some examples of the method900, the at least one report may be transmitted to the application processor on demand, periodically, in response to a trigger event, or a combination thereof.

FIG.10is a flow chart illustrating an example of a method1000for wireless communication, in accordance with one or more aspects of the present disclosure. For clarity, the method1000is described below with reference to aspects of a wireless device or UE115described with reference toFIG.1,4,5, or6. In some examples, a wireless device may execute one or more sets of codes to control the functional elements of the wireless device to perform the functions described below. Additionally or alternatively, the wireless device may perform one or more of the functions described below using special-purpose hardware.

At block1005, the method1000may include receiving from an application processor of a wireless device, at a modem of the wireless device, a request to receive at least one report on events monitored at the modem. The operation(s) at block1005may be performed by the modem620-adescribed with reference toFIG.6.

At block1010, the method1000may include receiving from the application processor, at the modem, data to transmit over a radio frequency spectrum. The operation(s) at block1010may be performed by the modem620-adescribed with reference toFIG.6.

At block1015, the method1000may optionally include receiving from the application processor, at the modem, an indication that the data is delay tolerant. The operation(s) at block1015may be performed by the modem620-adescribed with reference toFIG.6.

In some examples, the operations at two or more of blocks1005,1010, or1015may be combined in a same transmission.

At block1020, the method1000may optionally include determining that the modem is not active. The operation(s) at block1020may be performed by the modem620-adescribed with reference toFIG.6.

At block1025, the method1000may include storing the data received at block1010in a modem memory. In some examples, the data may be stored in the modem memory based at least in part on receiving an indication that the data is delay tolerant (at block1015) and/or determining that the modem is not active (at block1020). The operation(s) at block1025may be performed by the modem620-aor modem memory630described with reference toFIG.6.

At block1030, the method1000may optionally include determining that the modem is active after the modem is not active for a period of time. The operation(s) at block1030may be performed by the modem620-adescribed with reference toFIG.6.

At block1035, the method1000may include transmitting the stored data over the radio frequency spectrum. In some examples, the stored data may be transmitted based at least in part on determining the modem is active (at block1030). The operation(s) at block1035may be performed by the modem620-adescribed with reference toFIG.6.

At block1040, and before, during, or after one or more of blocks1005,1010,1015,1020,1025,1030, or1035, the method1000may include transmitting at least one report (e.g., at least one status report) to the application processor. The operation(s) at block1040may be performed by the modem620-adescribed with reference toFIG.6.

In some examples of the method1000, the at least one report may include a modem status or a data packet status. The modem status may include, for example, a first indication of an expected wait time until the modem becomes active or ready to transmit; a second indication of a modem state transition from not active or not ready to transmit, to active; a third indication of a modem state transition from active to not active; or a combination thereof. The data packet status may include, for example, a first indication of data packets received and stored in a modem memory; a second indication of data packets queued at the modem; a third indication of data packets dropped by the modem; a fourth indication of data packets transmitted by the modem; a fifth indication of data packets successfully received by a device to which the modem transmits over the radio frequency spectrum; or a combination thereof.

In some examples of the method1000, the at least one report may be transmitted to the application processor on demand, periodically, in response to a trigger event, or a combination thereof.

In some examples, aspects of the method900and1000described with reference toFIGS.9and10may be combined.

Techniques described herein may be used for various wireless communication systems such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and other systems. The terms “system” and “network” are often used interchangeably. A CDMA system may implement a radio technology such as CDMA2000, Universal Terrestrial Radio Access (UTRA), etc. CDMA2000 covers IS-2000, IS-95, and IS-856 standards. IS-2000 Releases 0 and A may be referred to as CDMA2000 1×, 1×, etc. IS-856 (TIA-856) may be referred to as CDMA2000 1×EV-DO, High Rate Packet Data (HRPD), etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. A TDMA system may implement a radio technology such as Global System for Mobile Communications (GSM). An OFDMA system may implement a radio technology such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM™, etc. UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS). 3GPP LTE and LTE-A are new releases of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization named 3GPP. CDMA2000 and UMB are described in documents from an organization named “3rd Generation Partnership Project 2” (3GPP2). The techniques described herein may be used for the systems and radio technologies mentioned above as well as other systems and radio technologies, including cellular (e.g., LTE) communications over an unlicensed or shared bandwidth. The description above, however, describes an LTE/LTE-A system for purposes of example, and LTE terminology is used in much of the description above, although the techniques are applicable beyond LTE/LTE-A applications.

The detailed description set forth above in connection with the appended drawings describes examples and does not represent all of the examples that may be implemented or that are within the scope of the claims. The terms “example” and “exemplary,” when used in this description, mean “serving as an example, instance, or illustration,” and not “preferred” or “advantageous over other examples.” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some instances, well-known structures and apparatuses are shown in block diagram form in order to avoid obscuring the concepts of the described examples.

Information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed with a general-purpose processor, a digital signal processor (DSP), an ASIC, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope and spirit of the disclosure and appended claims. For example, due to the nature of software, functions described above can be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Components implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations. As used herein, including in the claims, the term “or,” when used in a list of two or more items, means that any one of the listed items can be employed by itself, or any combination of two or more of the listed items can be employed. For example, if a composition is described as containing components A, B, or C, the composition can contain A alone; B alone; C alone; A and B in combination; A and C in combination; B and C in combination; or A, B, and C in combination. Also, as used herein, including in the claims, “or” as used in a list of items (for example, a list of items prefaced by a phrase such as “at least one of” or “one or more of”) indicates a disjunctive list such that, for example, a list of “at least one of A, B, or C” means A or B or C or AB or AC or BC or ABC (i.e., A and B and C).

Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage medium may be any available medium that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, computer-readable media can comprise RAM, ROM, EEPROM, flash memory, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

The previous description of the disclosure is provided to enable a person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not to be limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel techniques disclosed herein.