Local on-device data usage monitoring and controls

Abstract

A method of and an apparatus for network resource usage reporting in a wireless communication device are provided. The method comprises determining that a connection to a non-Internet Protocol (IP)-ba

Description

Technical Field Aspects of the present disclosure relate to software, applications and interfaces in a wireless communications device for measuring data usage over a connection that does not employ Internet Protocol (IP). Such as a connection may be a satellite connection or non-terrestrial network (NTN) connection. Background Wireless communications devices are widely used to communicate various types of information over wireless communication networks. Network infrastructure for such wireless communications networks are typically owned and operated by a service provider or network operator to which the owner of a wireless communication device is subscribed. As part of the terms of that subscription, it may be desirable to keep a record of network resource usage such as calls made or data usage, e.g. for fair use or billing purposes. In a conventional system for network resource usage recording, network resource usage is recorded in the network. For example, the 3rd Generation Partnership Project (3GPP) suite of standards define a number of cellular radio access technologies (RATs) which may provide network data and telephony services to a wireless communication device. Examples of such technologies include Universal Mobile Telecommunications System (UMTS), fourth generation (4G) systems such as Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, and fifth generation (5G) systems which may be referred to as New Radio (NR) systems. In a 3GPP network with offline charging, charging information for network resource usage may be generated and collected by 3GPP network elements concurrently with that resource usage. The charging information is then passed to a charging trigger function (CTF) may generate charging events that are forwarded to a charging data function (CDF), which generates charging data record (CDR) files to be transferred to tire network operator's billing domain for the purpose of subscriber billing. CDRs are formatted collections of information about chargeable events (e.g. time of call set-up, duration of the call, amount of data transferred, etc.) for use in billing and accounting. For each party to be charged for parts of or all charges of a chargeable event a separate CDR is generated, i.e. more than one CDR may be generated for a single chargeable event, e.g. because of its long duration, or because more than one charged party is to be charged. CDRs may be constructed from a set of several charging events, i.e. a n:l relation between event and CDR. In a 3GPP network with online charging, authorization for network resource usage may have to be obtained by the network prior to the actual resource usage occurring. For such charging, a network entity will generate a network usage request after which network will assemble the relevant charging information and generate a charging event towards an Online Charging System (OCS) or a Converged Charging System (CCS) (a CCS may be used when both online and offline charging are implemented in the network). The OCS or CCS determines whether to return an appropriate resource usage authorization based on subscription information it has stored. For both online and offline charging, because operator decisions based on resource usage data involve integrating information from many different network entities and parties, for the conventional systems such as 3GPP’s use of CDRs, the collection of resource usage data has been determined to be implemented most efficiently within the operator network. At the same time as, and indeed as part of, the standardization efforts of 3GPP, there has been great interest in developing satellite i.e. non-terrestrial network (NTN) connectivity for wireless communication devices. NTNs are seen as advantageous for wireless communication devices that are outside of terrestrial wireless coverage as a means of affording them some level of connectivity. The services being offered over NTN connectivity may vary', but particular attention is recently being paid to messaging (including emergency information) and location tracking services. Operators may provide such services through non-Internet Protocol (IP) packet data networks (PDNs). Use of non-IP PDNs for NTN or other connectivity may however introduce technical difficulties for the collection and reporting of network resource usage data. The file transport mechanisms for network usage requests, charging events and CDRs are required to support use of transport layer protocols of the Internet protocol suite such as User Datagram Protocol (UDP), Transmission Control Protocol (TCP) or Stream Control Transmission Protocol (SCTP), and therefore require an IP connection. In the absence of an IP connection, a need therefore exists to enable collection and reporting of network resource usage data for a non-IP-based connection, and in particular a non-IP -based NTN connection. Summary of the Invention According to an aspect of the present invention, a method of network resource usage reporting in a wireless communication device is provided. The method comprises determining that a connection to a non-Intemet Protocol (IP)-based network has been established and initiating one or more on-device network resource usage data counters for the non-IP-based connection based on determining that the connection to the non-IP-based network has been established. The method further comprises establishing a connection to an IP-based network subsequent to the initiating of the one or more network resource usage counters and transmitting network resource usage data recorded by the one or more network resource usage data counters over the IP-based network to a network resource usage data collecting entity. According to a preferred feature, the method further comprises receiving a network resource usage message from the network resource usage data collecting entity and synchronizing the one or more network resource usage counters with the network resource usage data collected by the network resource usage data collecting entity based on the received network resource usage message. In some aspects, the method further comprises permitting data communication over the non-IP-based network based on determining whether there is sufficient remaining data allowance from subscription information stored on the wireless communication device. In such aspects, the permitting of data communication comprises detennining that there is sufficient remaining data allowance. In other such aspects, the permitting of data communication comprises determining that there is insufficient remaining data allowance. Based on detennining that there is insufficient remaining data allowance, the method may further comprise determining that a renewal date for the subscription infomiation has passed since a last network resource usage synchronization with the network resource usage data collecting entity, resetting the data allowance based on determining that the renewal date has passed, and permitting data communication over the non-IP-based network based on the reset data allowance. Alternatively, based on determining that there is insufficient remaining data allowance, the method may further comprise prompting a user to increase the data allowance through a graphical user interface, receiving a user selection of an increased data allowance through the graphical user interface, adjusting the data allowance according to the increased data allowance, and permitting data communication over the non-IP-based network based on the adjusted data allowance. Subsequent to the connection to the IP-based network being established, such a method may also comprise transmitting, over the IP-based network, a message to a network resource usage management entity to trigger a pre-authorized addition of data allowance to a user subscription based on the received user selection. When the method comprises the method further comprises permitting data communication over the non-IP-based network based on determining whether there is sufficient remaining data allowance from subscription information stored on the wireless communication device the one or more network resource usage counters comprise separate counters for different types of data. The one or more network resource usage counters may comprise separate counters for messaging data, location tracking data, and emergency data. In such aspects, the permitting of data communication comprises determining that there is insufficient remaining data allowance for one of the separate counters, and based on determining that there is insufficient remaining data allowance, prompting a user to transfer data allowance from another of the separate counters through a graphical user interface. The permitting further comprises receiving, through the graphical user interface, a user input to transfer data allowance from another of the separate counters to the one of the separate counters, adjusting the data allowance for the one of the separate counters according to the user input, and permitting data communication over the non-IP-based network based on the adjusted data allowance. Subsequent to the connection to the IP-based network being established, the method further comprises transmitting, over the IP network, a message to a network resource usage management entity to synchronize network resource usage data. The non-IP based network may be a satellite network or non-terrestrial network (NTN). According to a further aspect of the invention, an apparatus for network resource usage reporting in a wireless communication device is provided that comprises a memory and at least one processor coupled to the memory. The at least one processor is configured to determine that a connection to a non-Intemet Protocol (IP)-based network has been established and initiate one or more on-device network resource usage data counters for the non-IP-based connection based on determining that the connection to the non-IP-based network has been established, the at least one processor is further configured to establish a connection to an IP-based network subsequent to the initiating of the one or more network resource usage counters and transmit network resource usage data recorded by the one or more network resource usage data counters over the IP-based network to a network resource usage data collecting entity. According to a preferred feature, the at least one processor is further configured to receive a network resource usage message from the network resource usage data collecting entity, and synchronize the one or more network resource usage counters with the network resource usage data collected by the network resource usage data collecting entity based on the received network resource usage message. In some aspects, the at least one processor is further configured to permit data communication over the non-IP-based network based on determining whether there is sufficient remaining data allowance from subscription information stored on the wireless communication device. 13. The apparatus of claim 12, wherein the permitting of data communication comprises determining that there is sufficient remaining data allowance. The non-IP based network may be a satellite network or non-terrestrial network (NTN). Brief Description of the Drawings Fig. 1 is a schematic diagram of a telecommunications device in accordance with an embodiment. Fig. 2 is a schematic diagram illustrating various modules of software running on various processors with interfaces therebetween. Fig. 3 is a further schematic diagram showing the modules of software of Fig. 2 in greater detail. Fig. 4 is a flow diagram for a method of on-device resource usage recording. Fig. 5 is a logic flow diagram for determining permission to communicate via an NTN and synchronizing network resource usage data with operator records. Detailed Description Various aspects of the invention are described below. Fig. 1 shows a schematic diagram of the parts and modules of a telecommunications device, in accordance with an embodiment of the present invention. A single mobile communication device 10 (e.g. smartphone, tablet, wearable, UE) comprises a transceiver / modem module 120 operating according to a first non-IP-based RAT, such as a NTN, and a processor 110. The transceiver / modem module may be a first transceiver / modem module, comprising an on-board modem processor 122 that is connected to processor 110. The OS software running on the processor 110 may comprise a first radio modem driver for communicating with first modem processor 122 via a first interface 126 for AT commands or similar. The communication device 10 may additionally comprise a second transceiver / modem module 130 operating according to a second IP-based RAT such as terrestrial cellular radio, Wi-Fi or the like, comprising an on-board modem processor 132 that is connected to processor 110. Accordingly, the OS software running on processor 110 may have a second modem driver for communicating with modem processor 132 via a second interface 136 (for AT commands or similar). The device is also configured to receive a subscriber identity module (SIM) card 150 and optionally further SIM card(s) 155 corresponding to respective transceiver / modem modules 120, 130 where present. The first transceiver / modem module 120 is connected to a first antenna 124 of a first RAT communication system and the second transceiver / modem module 130 is connected to a second antenna 134 of a second RAT communication system. Alternatively, the first transceiver / modem module 120 and second transceiver / modem module 130 may share an antenna that is switched between the two modules based on which RAT is active. The two modules / antennae can be configured to operate on the same RF band or different RF bands. Each transceiver / modem is preferably impedance matched and / or power matched to its respective antenna. Second transceiver / modem module 130 may, for example, have different transmit power than first transceiver / modem module 120. The multiple transceiver / modem modules do not communicate with each other, but the multiple connectivity methods may be active at the same time where possible. Users interact with the device via application layer software 140, or apps, through a user interface (UI). Fig. 2 shows another schematic diagram of various parts or modules of the device, and communications and interactions therebetween, in accordance with an aspect of the present invention. An OS, 210, such as an Android OS running on the device processor 110, can communicate with a first chipset 220. This chipset may be a modem chipset for connectivity in a first RAT communication system, such as a satellite / NTN (non-terrestrial network) communication system. Control of a modem chipset is typically via attention (AT) commands, sent from the OS 210 to the chipset 220. The OS 210 also communicates with one or more applications, via two-way general interactions 212 between application and platform; these could be Android-specific interactions. Only one application 230 is shown, as an example, in Fig. 2. A D2D framework 240 is provided. Tire application 230 is configured to send D2D API requests or data 232 to the D2D framework 240, and the D2D framework 240 is configured to send D2D notifications or data 234 to the application 230. Hie D2D framework 240 communicates with the OS 210. The D2D framework is configured to send AT commands and data 242 to the OS, and to receive AT command responses and downlink data and / or events 244 from the OS. In other words, the framework 240 converts API requests into AT requests that the modem can understand. There may be a second chipset 250 that communicates with the OS 210 in a similar manner to the first chipset 220. Fig. 3 is a schematic diagram that shows how the D2D framework fits into a typical existing architecture in an Android OS. In this example, excluding applications in the application layer, blocks with solid borders represent elements that are developed by Google and provided to SOC manufacturers / vendors; blocks with dashed borders represent elements created by said vendors to interface with their hardware. A SOC vendor then creates an SOC platform release, which is then licensed to OEMs of the device. In the application layer 310, one may have multiple applications, such as a Dialler application 312, a Messaging application 314, an IP data application 316, and an NTN messaging application 318. In an example, the Dialler, Messaging and IP data applications are configured to be operated using a cellular network for data transmission, while the NTN messaging application is configured to utilise an NTN / satellite network, but it should be noted that there is not always a one-to-one association between applications and RATs. For example, the messaging application 314 may need to message via the NTN or the NTN application may be a generic application capable of messaging via more than one RAT. The former group of applications 312, 314, 316 preferentially communicate with a cellular baseband modem 352 in the baseband layer 350 via an application framework 320 that comprises telephony 322 and radio interface layer (RIL) 324. This preferably makes use of a library 330 such as an RIL library 332 provided by the manufacturer of the cellular chipset. Voice and control data, and other data, may be transmitted to the cellular baseband modem 354 via a kernel, for example a Linux 340, for example comprising a Linux IP stack 342 and a packet driver 344 where appropriate. Note that baseband 350 refers to the modem circuits that are individually integrated but are otherwise separate. As a layer, 350 refers, for each circuit, to that circuit’s physical layer and data link layer (including a medium access control sublayer, where applicable, and may also include a logical link control sublayer, where applicable). The NTN messaging application 318 is configured to send a message to a D2D framework 326. The framework communicates, via CMUX (converter-multiplexer) service module 346 at the Linux kernel 340, with the NTN baseband modem 354. The CMUX service 346 multiplexes AT commands for different logical channels to a serial interface of a universal asynchronous receiver-transmitter (UART) of the baseband chipset. The NTN baseband modem 354 accordingly receives the AT commands. Tire D2D framework exposes D2D APIs to the application layer by abstracting the complex AT command communication. This D2D framework may be part of the Android platform or an application or a standalone service that is installed along with the application. The D2D framework does not simply re-format a message and pass it on to the baseband. For example, the D2D framework provides a notification when a message is received from the NTN baseband. This notification is received by any application that has validly subscribed to the D2D framework for such a service. When an application such as NTN messaging application 318 subscribes to the D2D framework to receive NTN messages, it will receive the notification. Similarly, the D2D framework will transmit a connection state, a signal level, etc. such that the subscribed application is notified. It is possible that different services may be defined such that different applications subscribe for and receive notifications of these different services. The framework is also responsible for initialisation, configuration and shutdown of the NTN system. This allows for efficient use of system resources when client applications are not using the NTN services. Given the higher power consumption and latency commonly associated with NTN connectivity, use of terrestrial networks for data communication is in the near term expected to be prioritized over use of NTNs, with NTNs being used for location tracking and messaging (including emergency messaging) when out of terrestrial network coverage. For this reason, when the NTN connectivity is not based on IP, it is common that there will be no IP connection to a wireless communication device connected to an NTN. NTN Resource Usage Recording In stark contrast to conventional methods for network resource usage recording, the inventors have determined it to be advantageous for a non-IP-based NTN to implement network resource usage recording for a particular user locally on the wireless communication device of the user. The invention therefore relates to a method of operating a wireless communication device (e.g. a smartphone, wearable device, tablet or loT (Internet of Things) device) to record usage data of a non-IP-based network. The method may be implemented by one or more applications in the application layer of the device such as by NTN messaging application 318. Interactions with IP systems may be achieved by NTN messaging application 318 indirectly through API calls between NTN messaging application 318 and one or more applications that may connect to IP networks or through a direct connection to telephony 322 (note neither of these options is shown in Fig. 3). A principle of operation of the method is to record network resource usage data for a non-IP-based network on the wireless communication device as those resources are being consumed. After a connection to an IP-based network is established, the resource usage data may be transmitted over the IP-based network to an operator entity so that resource usage data can be synchronized with the operator. Fig. 4 is a flow diagram for a method of on-device resource usage recording. The method begins at operation 402, where a determination is made that a connection to a non-IP-based network has been established. This operation allows the processing resources associated with network resource usage recording not to be initiated for use before required. Optionally, at operation 404, a determination is made to permit data communication over the non-IP-based network based on subscription information stored on the wireless communication device. For example, if there is sufficient remaining data allowance for a type of data (e.g. all data, messaging data), NTN data transmission or reception may be permitted for the type of data. This operation allows online charging functionality to be implemented even without an IP connection. To determine permissions, NTN messaging application 318 may have access to various elements of subscription information for the user of the wireless communication device. For example, it may store a minimum and maximum data packet size. It may also store the time (e.g. in days) since the resource usage data was last synchronized over IP and the time since last subscription renewal. As discussed in more detail with regard to Fig. 5, these time values enable the determination of whether data allowances may be increased. At operation 406. one or more on-device network resource usage data counters for the non-IP-based connection are initiated. Each of the one or more counters retains a log of how much of each data type has been consumed since the last synchronization over IP. There may be separate counters for different types of data communicated over the non-IP-based network. For example, there may be respective counters for data type “A” and data type “B”. Type “A” data may be transmitted in single packet messages of constant or variable size, and type “B” data may be transmitted in multiple packet messages with a maximum number of packets per message. Data types may include messaging data, location tracking data and emergency data (emergency data may not be charged, but is still reported to the operator). In this way, more fine grained collection of usage data may be achieved than using a single counter and different allowances of the user may be monitored. At operation 408, a connection to an IP-based network is established by the user. The connection to the IP-based network may be established at anytime after the initiation of the one or more counters, including during on-going non-IP-based communication. At operation 410. network resource usage data is transmitted over the IP-based network to a network resource usage data collecting entity. The network resource usage data may be sent in the form of chargeable events or information that may be readily converted by the operator into one or more CDRs. In other examples, the network resource usage data may be triggered to be transmitted (a predetermined time) after a communication session over the non-IP-based connection has ended. In this case, the resource usage data is read out of the one or more counters for transmission to the operator. The one or more counters may then be reset. Alternatively, an operator entity may transmit a confirmation that it has received the network resource usage data or other network resource usage message. The wireless communication device then resets the one or more counters or otherwise synchronizes the one or more counters to the operator’s records in response to the confirmation or other network resource usage message. Transmission of network resource usage data or indications that no further data has been consumed since a last synchronization with the data may occur periodically when connected to an IP-based network. Fig. 5 is a logic flow diagram for determining permission to communicate via an NTN and synchronizing network resource usage data with operator records. It illustrates some aspects of Fig. 4 in greater detail. hi operation 502, it is detennined whether the wireless communication device is connected to an NTN. If it is determined that the device is not connected to an NTN, at operation 504, on-device counters are deactivated or maintained in a deactivated state. At operation 506, the device is then prevented from communicating data over the NTN. On the other hand, if at 502 it is determined that the wireless communication device is connected to an NTN, on-device network resource usage counters are activated at 508. At operation 510, it is then determined whether there is a valid subscription in place for the user of the wireless communication device (with the service provider of that service). This operation may be triggered by receiving a request through a user interface to consume data over satellite. Such a request may take the form of a user selecting a GUI element to send a text message (if the only RAT to which the device is connected is an NTN, it may be inferred that the user is requesting use of data over satellite). If it is determined that there is no valid subscription for the user, the device is prevented from communicating data over the NTN according to operation 506. If on the other hand, a valid subscription is found to be in place, at operation 512 a determination is made as to whether sufficient allowance is remaining for the subscription. For example, a comparison may be made between the size of requested data of a particular type for transmission and the remaining allowance for the current subscription period for the ty pe of data requested. It will also be appreciated that a single request may incorporate data of different types, so multiple such comparisons may be made. If it is detennined that there is a valid subscription for the user, the device is permitted to communicate data over the NTN according to operation 514. Subscription allowances are typically refreshed every renewal period (e.g. monthly or annually). If renewal has occurred in the operator records since the on-device counters were last synchronized with the operator records, the on-device counters may underestimate the remaining allowance. Upon finding insufficient remaining data allowance, a further determination at operation 516 is therefore made as to whether a renewal date has passed since the on device counter(s) were last synchronized with the operator records. If the renewal date lias not passed, the device is again prevented from communicating data over the NTN. If however the renewal date has passed, continuation of the subscription is assumed, the data allowances are refreshed, and the method continues again to operation 514. At some time later, a connection to an IP-based network may be established. Upon such establishment, the network resource usage data as recorded by the on-device counters is transmitted to the operator at operation 518. At operation 520, the operator may synchronize the NTN network resource usage according to the usage data from the on device counters. This may simply take the form of subtracting the amount of consumed data indicated by the on-device counters from that the operator records. Other procedures to reconcile the differences between the on-device counters and the operator records may be employed based on different factors. For example, if one or more data allowances were refreshed in operation 516, this may be indicated in the transmission of operation 518 and used in operation 520 to ensure an accurate reconciliation. At operation 522, the operator may synchronize and / or update the network resource usage on the on-device counters based on the synchronization occurring in operation 520. The method can thereby be repeated with updated on device counters Although not shown in Fig. 5, when it is determined that there is insufficient data allowance in one of the counters (and also optionally after determining that the renewal date has not passed), the user may be presented through a graphical user interface with the option to transfer data allowances between different counters. Thi s transfer may be subject to not exceeding a total value of the data allowances. The user may perform an input for effecting a data allowance transfer and the wireless communication device may permit data communication over the NTN accordingly. Alternatively, when it is determined that there is insufficient data allowance in one or more of the counters (and also optionally after determining that the renewal date has not passed), the user may be presented through a graphical user interface with the option to increase one or more data allowances through a pre-authorized transaction. That is, the user has agreed in principle beforehand to purchase more data when selecting the option. A user input triggers the device to consider the data allowance to be increased. The device allows NTN communication accordingly, and when connected to IP sends a message to the operator that the user has opted to buy more data. It will be appreciated that the procedures of Fig. 5 are not limited to use of an NTN, but to any nonIP-based network. The present invention is not to be limited by the above-described aspects and embodiments, and that many variations are within the scope of the appended claims. The various aspects and embodiments may be combined if necessary and appropriate. The drawings serve as exemplary illustrations of the invention only, to aid understanding of the invention.

Claims

1. A method of network resource usage reporting in a wireless communication device, comprising:determining that a connection to a non-Intemet Protocol (IP)-based network has been established;initiating one or more on-device network resource usage data counters for the non-IP-based connection based on determining that the connection to the non-IP-based network has been established;establishing a connection to an IP-based network subsequent to the initiating of the one or more network resource usage counters; andtransmitting network resource usage data recorded by the one or more network resource usage data counters over the IP-based network to a network resource usage data collecting entity.

2. The method of claim 1, further comprising:receiving a network resource usage message from the network resource usage data collecting entity; andsynchronizing the one or more network resource usage counters with the network resource usage data collected by the network resource usage data collecting entity based on the received network resource usage message.

3. The method of claim 1, further comprising permitting data communication over the non-IP-based network based on determining whether there is sufficient remaining data allowance from subscription information stored on the wireless communication device.

4. The method of claim 3, wherein the permitting of data communication comprises determining that there is sufficient remaining data allowance.

5. The method of claim 3, wherein the permitting of data communication comprises: determining that there is insufficient remaining data allowance;based on determining that there is insufficient remaining data allowance, determining that a renewal date for the subscription information lias passed since a last network resource usage synchronization with the network resource usage data collecting entity;resetting the data allowance based on determining that the renewal date has passed; andpermitting data communication over the non-IP-based network based on the reset data allowance.

6. The method of claim 3, wherein the permitting of data communication comprises:determining that there is insufficient remaining data allowance;based on determining that there is insufficient remaining data allowance, prompting a user to increase the data allowance through a graphical user interface;receiving a user selection of an increased data allowance through the graphical user interface;adjusting the data allowance according to the increased data allowance;permitting data communication over the non-IP-based network based on the adjusted data allowance; andsubsequent to the connection to the IP-based network being established, transmitting, over the IP-based network, a message to a network resource usage management entity to trigger a preauthorized addition of data allowance to a user subscription based on the received user selection.

7. The method of claim 3, wherein the one or more network resource usage counters comprise separate counters for different types of data.

8. The method of claim 7, wherein the one or more network resource usage counters comprise separate counters for at least two of messaging data, location tracking data, and emergency data.

9. The method of claim 7 or 8, wherein the pennitting of data communication comprises:determining that there is insufficient remaining data allowance for one of the separate counters;based on determining that there is insufficient remaining data allowance, prompting a user to transfer data allowance from another of the separate counters through a graphical user interface;receiving, through the graphical user interface, a user input to transfer data allowance from another of the separate counters to the one of the separate counters;adjusting the data allowance for the one of the separate counters according to the user input;permitting data communication over the non-IP-based network based on the adjusted data allowance; andsubsequent to the connection to the IP-based network being established, transmitting, over the IP network, a message to a network resource usage management entity to synchronize network resource usage data.

10. The method of any preceding claim, wherein the non-IP based network is a satellite network or non-terrestrial network (NTN).

11. An apparatus for network resource usage reporting in a wireless communication device, comprising:a memory; andat least one processor coupled to the memory and configured to:determine that a connection to a non-Intemet Protocol (IP)-based network has been established;initiate one or more on-device network resource usage data counters for the non-IP-based connection based on determining that the connection to the non-IP-based network has been established;establish a connection to an IP-based network subsequent to the initiating of the one or more network resource usage counters; andtransmit network resource usage data recorded by the one or more network resource usage data counters over the IP-based network to a network resource usage data collecting entity.

12. The apparatus of claim 11, wherein the at least one processor is further configured to:receive a network resource usage message from the network resource usage data collecting entity; andsynchronize the one or more network resource usage counters with the network resource usage data collected by the network resource usage data collecting entity based on the received network resource usage message.

13. The apparatus of claim 11, wherein the at least one processor is further configured to permitdata communication over the non-IP-based network based on determining whether there is sufficient remaining data allowance from subscription information stored on the wireless communication device.

14. The apparatus of claim 13, wherein the permitting of data communication comprisesdetermining that there is sufficient remaining data allowance.

15. The apparatus of any of claims 11-14, wherein the non-IP based network is a satellite networkor non-terrestrial network (NTN).

Images