Attention (AT) command for managing data measurement reporting

Abstract

Various embodiments of the method for managing data measurement reports may include: sending an attention AT command from the application processor of a user equipment (UE) to the modem of the UE to configure the modem to send a non-requested result code in response to receiving a pause command or a resumption command related to the transmission of application-level measurement information collected by the UE; receiving a pause command from a network element while transmitting application-level measurement information collected by the UE to a network element; in response to the received pause command and AT command, sending a non-requested result code from the modem to the application processor including a pause indication or pause instruction to temporarily pause the transmission of application-level measurement information; and suspending the transmission of application-level measurement information by the modem in response to the pause command.

Description

[Technical Field]

[0001] This disclosure concerns the Attention (AT) order used for managing data measurement reports. [Previous Technology]

[0002] In Long Term Evolution (LTE), fifth-generation (5G) New Radio (NR) and other communication technologies enable wireless devices to transmit information at high data rates (e.g., gigabits per second). Some communication systems utilize millimeter-wave (mmWave) bands to provide high-bandwidth communication links. Key aspects of wireless communication networks include monitoring and maintaining wireless communication links and the devices using the network, commonly referred to as Radio Access Networks (RANs). [Summary of the Invention]

[0003] Various aspects of this case include methods for managing data measurement reports (such as quality of experience (QoE) reports) using AT commands and result codes exchanged between a data processor of a user equipment (UE) and another processor of the UE (such as an application processor), and devices configured to perform these methods.

[0004] Each state may include: sending an Attention (AT) command from the UE's application processor to the UE's modem to configure the modem to send a non-requested result code in response to receiving a pause command or resume command related to sending application-level measurement information collected by the UE; receiving a pause command from the network element while the UE is sending application-level measurement information collected by the UE to the network element; in response to the received pause command and AT command, sending a non-requested result code from the modem to the application processor including a pause indication or pause instruction to temporarily pause the transmission of application-level measurement information; and suspending the modem from sending application-level measurement information in response to the pause command.

[0005] In some states, the non-requested result code, including a pause indication or pause instruction, may include an indication or instruction to temporarily suspend the transmission of at least a subset of all application-level measurement information in response to a received pause command and AT command. In some states, the non-requested result code, including a pause indication or pause instruction, may include an indication or instruction to temporarily suspend the collection of at least a subset of all application-level measurement information in response to a received pause command and AT command.

[0006] In some states, the non-requested result code, including a pause indication or pause command, may include an indication of an application service instance that provides application-level measurement information based on information in the application measurement profile. In some states, the non-requested result code, including a pause indication or pause command, may also include an indication of the application service type associated with the application service instance.

[0007] In some states, the non-requested result code including the pause indication may include an indication to suspend the collection of RAN Visible QoE (RVQoE) metrics as separate application-level measurement information in response to a received pause command and AT command. In some states, the non-requested result code including the pause indication or pause instruction may include an indication of the application service instance associated with the RAN Visible QoE application-level measurement information. In some states, the non-requested result code including the pause indication may include an indication of the application service type associated with the application service instance associated with the RAN Visible QoE application-level measurement information.

[0008] In some configurations, the AT command may include an indication of whether to enable the UE to display a non-requested result code to the UE's application processor via the UE's modem. In some configurations, a non-requested result code, including a pause indication or pause instruction, may include an indication or instruction for the application processor to continue collecting application-level measurement information and to store the collected application-level measurement information in the application-level memory according to configuration information in the application-level memory. In some configurations, the modem may include the UE's access layer, and the application processor may include the UE's application level.

[0009] Some states may include: receiving a recovery command from a network element while suspending the transmission of application-level measurement information from the UE to the network element; in response to the received recovery command and AT command, sending a non-request result code from the modem to the application processor, including a recovery indication or recovery instruction to resume the transmission of application-level measurement information; and in response to the recovery command, resuming the transmission of application-level measurement information via the modem.

[0010] In some states, the non-requested result code including a recovery indication or recovery instruction may include an indication for the application processor to resume transmitting application-level measurements to the modem, and resuming the transmission of application-level measurement information in response to a recovery command may include resuming the transmission of application-level measurements from the UE's application processor to the UE's modem. In some states, the non-requested result code including a recovery indication or recovery instruction may include an indication or instruction to resume transmitting at least a subset of all application-level measurement information in response to a received recovery command and AT command.

[0011] In some states, resuming the transmission of application-level measurement information in response to the recovery command may include transmitting the application-level measurement information stored in the application-layer memory to the modem. In some states, the non-requested result code including the recovery instruction may include an instruction for resuming the transmission of application-level measurement information for an application service instance. In some states, the non-requested result code including the recovery instruction may also include an instruction for the application service type associated with the application service instance. In some states, the non-requested result code including the recovery instruction may include an instruction for a new application-level measurement profile for the application service that provides the application-level measurement information.

[0012] A further embodiment may include a UE having a processor and a modem configured to perform one or more operations of any of the methods outlined above. A further embodiment may include a non-transitory processor-readable storage medium having processor-executable instructions stored thereon configured to cause the processor and modem of the UE to perform operations of any of the methods outlined above. A further embodiment includes a UE having a device module having functionality for performing any of the methods outlined above. A further embodiment includes a system-on-chip for use in a UE, the system-on-chip including a processor configured to perform one or more operations of any of the methods outlined above. A further embodiment includes a system-in-package including two systems-on-chip for use in a UE, the system-in-package including a processor and a modem configured to perform one or more operations of any of the methods outlined above.

Implementation Method

[0025] Various embodiments will be described in detail with reference to the accompanying drawings. Throughout the drawings, the same element symbols are used as far as possible to denote the same or similar device modules. References to specific examples and implementations are for illustrative purposes and are not intended to limit the scope of the claims.

[0026] Various embodiments provide a method for managing the collection and reporting of performance measurements on a user equipment (UE) in response to network commands via use attention (AT) commands and responses exchanged between the UE's modem processor and another processor of the UE (e.g., an application processor). Various embodiments may include the UE's application processor sending an AT command to the UE's modem, the AT command configuring the modem to send a non-requested result code to a network element in response to receiving a pause command or resumption command related to the collection and transmission of application-level measurement information. The AT command is configured such that when the modem receives a pause command from a network element while collecting application-level measurement information and transmitting it to a network element, the modem sends a non-requested result code to the application processor. This non-requested result code includes a pause indication for temporarily suspending the transmission of application-level measurement information, resulting in a pause in the transmission of application-level measurement information. Furthermore, the modem configured by the AT command will send a non-requested result code to the application processor in response to receiving a resumption command from a network element, the resumption command causing the transmission of application-level measurement information to resume.

[0027] As used herein, the term "User Equipment (UE)" means any or all of the following: terminal equipment, cellular telephone, smartphone, portable computing device, personal or mobile multimedia player, laptop, tablet computer, smart computer, ultrabook, handheld computer, wireless email receiver, multimedia-enabled Internet of Things (IoT) telephone, medical device and equipment, biometric sensor / device, wearable device including smartwatch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet, etc.), entertainment device (e.g., wireless game controller, music and video player, satellite radio, etc.), wireless-enabled Internet of Things (IoT) device including smart instruments / sensors, wireless router device, wireless appliance, industrial manufacturing equipment, large and small machines and appliances for home or business use, computing devices in autonomous and semi-autonomous vehicles, wireless devices integrated into or incorporated into various mobile platforms, GPS devices, and similar electronic devices including memory, wireless communication components and additional programmable processors.

[0028] The term "System-on-a-Chip" (SOC) is used herein to refer to a single integrated circuit (IC) chip that includes multiple resources and / or processors integrated on a single substrate. A single SOC may include circuitry for digital, analog, mixed-signal, and radio frequency functions. A single SOC may also include any number of general-purpose and / or special-purpose processors (digital signal processors, modem processors, video processors, etc.), memory blocks (e.g., ROM, RAM, flash memory, etc.), and resources (e.g., timers, voltage regulators, oscillators, etc.). A SOC may also include software for controlling the integrated resources and processors, as well as software for controlling peripheral devices.

[0029] The term "System-in-Package" (SIP) may be used herein to refer to a single module or package containing multiple resources, computing units, cores, and / or processors on two or more IC chips, substrates, or SOCs. For example, a SIP may include a single substrate on which multiple IC chips or semiconductor dies are stacked in a vertical configuration. Similarly, a SIP may include one or more multi-chip modules (MCMs) on which multiple ICs or semiconductor dies are packaged into a uniform substrate. A SIP may also include multiple independent SOCs coupled together via high-speed communication circuitry and packaged in very close proximity, such as on a single motherboard or in a single UE. Proximity of the SOCs facilitates high-speed communication and the sharing of memory and resources.

[0030] As used herein, the terms "network," "system," "wireless network," "cellular network," and "wireless communication network" may interchangeably represent part or all of a wireless network of carriers associated with a UE and / or a subscription on the UE. The techniques described herein can be used in various wireless communication networks, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), FDMA, Orthogonal FDMA (OFDMA), Single Carrier FDMA (SC-FDMA), and other networks. Typically, any number of wireless networks can be deployed in a given geographic area. Each wireless network can support at least one radio access technology that can operate on one or more frequencies or frequency ranges. For example, a CDMA network can implement Universal Terrestrial Radio Access (UTRA) (including the Wideband Code Division Multiple Access (WCDMA) standard), CDMA2000 (including the IS-2000, IS-95, and / or IS-856 standards), etc. In another instance, a TDMA network can implement GSM Enhanced Data Rate (EDGE), an evolution of GSM. In yet another instance, an OFDMA network can implement Evolved UTRA (E-UTRA) (including the LTE standard), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Fast OFDM, etc. References can be made to wireless networks using the LTE standard; therefore, the terms "Evolved Universal Terrestrial Radio Access," "E-UTRAN," and "eNodeB" are used interchangeably herein to refer to wireless networks. However, such references are provided as examples only and are not intended to exclude wireless networks using other communication standards. For example, although various third-generation (3G), fourth-generation (4G), and fifth-generation (5G) systems are discussed herein, these systems are cited only as examples and can replace future generations of systems (e.g., sixth-generation (6G) or higher) in various examples.

[0031] Key management tasks in wireless communication networks (commonly referred to as radio access networks (RAN)) involve the monitoring and maintenance of wireless communication links and the devices using those links. When a communication link becomes congested or overloaded, the performance and / or efficiency of the communication network may decrease. The communication network uses various performance information reported from the UE to monitor and adjust the wireless communication links.

[0032] To obtain information for monitoring and adjusting wireless communication links, a procedure exists through which the network element can assign the UE to collect certain performance information (such as Quality of Experience (QoE) information) and send the collected information back to the network element (such as in a QoE report). Sometimes, situations or conditions may arise where the network element needs to pause the collection of performance information from the UE, such as by temporarily releasing wireless bandwidth. As currently configured, the network element can only start and stop the procedure for collecting performance information from the UE, which may lead to inefficiencies associated with stopping and restarting such performance measurement and reporting procedures when only a brief pause is required.

[0033] Various embodiments enable the UE to temporarily suspend the transmission of application-level measurement information (e.g., QoE reports) to network elements of the communication network. For example, to resolve or mitigate RAN overload conditions, the UE can receive a command from a network element to temporarily suspend reporting application-level measurement information to the communication network. Various embodiments also enable the UE to resume transmitting application-level measurement information to the communication network in response to a recovery command from a network element, such as when the overload condition has been mitigated or ended.

[0034] In various embodiments, the UE may perform internal configuration operations to enable the UE to receive and appropriately process pause or resume commands from network elements of the communication network. Specifically, the UE's application processor (or another suitable device in the UE's application layer) may send an AT command to the UE's modem (i.e., to the modem processor of the UE's access layer (AS) or another suitable device), which configures the modem to send a non-requested result code in response to receiving a pause or resume command related to sending application-level measurement information collected by the UE. In some embodiments, the AT command and the associated non-requested result code may be represented by +C syntax and additional extensions, arguments, or parameters of command and result codes such as "+CAPPLEVMR", "+CAPPLEVMC", "+CAPPLEVMRNR", or "+CAPPLEVMCNR", as further described below.

[0035] In various embodiments, such pause and resume commands can be received from a network element, which may be a network element configured to perform Operation, Administration and Maintenance (OAM) operations, a network element configured to perform Tracking Collection Entity (TCE) or Measurement Collection Entity (MCE) operations, a RAN network element, and / or another network element. The UE can receive the pause command from the network element while transmitting application-level measurement information collected by the UE (i.e., to the communication network).

[0036] In response to receiving a pause command, the modem may pause the transmission of application-level measurement information to network elements. Additionally, in response to the received pause command and AT command (i.e., in response to previous configuration via receiving an AT command), the UE's modem may send a non-requested result code to the UE's application processor according to the configuration specified in the AT command. In some embodiments, the non-requested result code may include a pause indication to temporarily pause the transmission of application-level measurement information by the application processor. In some embodiments, the application-level measurement information associated with the non-requested result code may relate to RAN-visible QoE metric measurement information. In some embodiments, the non-requested result code may include a pause indication or pause command to temporarily pause the transmission of all application-level measurement information, a subset of application-level measurement information corresponding to RAN-specific visible QoE metric measurement information, or a subset of application-level measurement information not corresponding to RAN-specific visible QoE metric measurement information by the application processor. In some embodiments, the AT command may include an indication of whether to enable the presentation of non-requested result codes (such as sending a notification from the UE's modem to the UE's application processor). In some embodiments, an indication of whether to enable the presentation of unrequested result codes may include syntax such as <n> and an integer indicating whether sending unrequested result codes is allowed (or enabled) (e.g., "0") or prohibited (or disabled) (e.g., "1"). In some embodiments, the unrequested result code command may be an AT "Settings Command" that can enable or disable the presentation of unrequested result codes. In some embodiments, the unrequested result code may also include an indication to pause, for example, the collection of application-level measurement information by the application processor. In some embodiments, the unrequested result code may also include an indication to pause the collection of RAN-specific visible QoE metric measurement information.

[0037] In some embodiments, the non-requested result code sent by the modem to the application processor in response to receiving a pause command may include an indication of an application service instance that is providing application-level measurement information that is being paused. In some embodiments, the non-requested result code may include an indication of an application service instance that provides application-level measurement information based on information in an application measurement profile. In some embodiments, additionally or alternatively, the non-requested result code may also include an indication of the application service type to which the application service instance belongs. The indication of the application service may include, for example, a streaming service, IMS Multimedia Telephony Service (MTSI), Multimedia Broadcast Multicast Service (MBMS), Virtual Reality (VR) service (which may include Augmented Reality (AR), Mixed Reality (MR), Extended Reality (XR), etc.) and / or another suitable service. An instance of an application service instance is a specific data streaming application that supports any of multiple different media streams (e.g., YouTube, Netflix, Disney+), where each media stream may be configured as a "data streaming" application service type. Each application service type may include one or more application service instances. In some embodiments, the indication of the application service may include parameters such as `<app-meas_service_type>` and an integer indication of the application service. In some embodiments, the non-requested result code may include flags, such as values ​​indicating whether to pause or resume application-level measurement reports for all configurations, applications, and / or services. In some embodiments, the non-requested result code may include indications such as a reference ID or values ​​that distinguish one or more application-level report configurations of the same service type. Some embodiments may include two types of configuration information, such as `<app-meas_config-file>` and `<RVQoE Configuration>`. In such embodiments, pause or resume commands may be sent, or may be applied to one or both types of application-level information.

[0038] In some embodiments, the non-requested result code including the pause indication may also instruct the application processor to continue collecting application-level measurement information and store the collected application-level measurement information in either application-layer memory or access-layer memory (e.g., the memory of the UE modem). In some embodiments, the non-requested result code including the pause indication may also instruct the application processor to store application-level measurement information in memory (e.g., application-layer memory) until such memory becomes full, at which point the application processor may stop performing application-level measurements. In some embodiments, the non-requested result code including the pause indication may also instruct the application processor to pause both performing application-level measurements and sending application-level measurement information to the modem.

[0039] In some embodiments, the non-requested result code including a pause indication may include a parameter such as `<pause-resume_reporting>`, which may indicate a temporary pause (or resumption) of application-level measurement reporting for an application (or service) indicated by `<app-meas_service_type>`. In some embodiments, the parameter `<pause-resume_reporting>` may include an indication (e.g., "0") indicating that the application processor should resume transmitting application-level measurement information to the modem, including application-level measurement information stored in memory (e.g., application-layer memory). In some embodiments, the parameter `<pause-resume_reporting>` may include an indication (e.g., "1") indicating that the application processor should pause both the transmission of application-level measurement information to the modem and the application-level measurement procedure. In some embodiments, the indication "1" or other appropriate indication may also indicate that application-level measurement information should be stored in access-layer memory.

[0040] In some embodiments, the parameter <pause-resume_reporting> may include an instruction that the application processor should pause the transmission of application-level measurement data to the modem, continue to perform application-level measurement, and store application-level measurement information until the allocated application-level memory is full, and then stop performing further application-level measurement (e.g., "2").

[0041] In some embodiments, the "+CAPPLEVMC" code (or "+CAPPLEVMCNR", "+CAPPLEVMRNR" or another suitable code) may include a <start-stop_reporting> parameter and a <pause-resume_reporting> parameter. In some embodiments, the inclusion of both the <start-stop_reporting> parameter and the <pause-resume_reporting> parameter with "+CAPPLEVMC" (or "+CAPPLEVMCNR" or "+CAPPLEVMRNR") may instruct the application processor to perform the operation indicated by the value of the <pause-resume_reporting> parameter as described above (e.g., "0", "1" or "2").

[0042] In some embodiments, the non-requested result code including the pause indication may also include an application-level measurement profile for each of one or more applications (or application-level services). In some embodiments, the application-level measurement profile may be represented as a string of octets or another suitable representation. In some embodiments, the non-requested result code including the pause indication may include parameters such as <app-meas_config-file>, which may include an application-level measurement profile for an application (or application-level service). In some embodiments, the non-requested result code including the pause indication may also include parameters such as <config-id> to identify the profile associated with <app-meas_config-file>. In some embodiments, the non-requested result code including the pause indication may also include parameters such as <app-meas_config_file_length>, which may indicate the number of octets (or other data packets or arrangements) of the application-level measurement profile (e.g., <app-meas_config-file>).

[0043] In some embodiments, the non-requested result code including the pause instruction may also include an instruction for a new application-level measurement profile for the application service that provides application-level measurement information. For example, as mentioned above, the parameter <pause-resume_reporting> may include an instruction (e.g., "0") instructing the application processor to resume transmitting application-level measurement information to the modem. In some embodiments, when <pause-resume_reporting>='0' exists in the non-requested result code, the additional presence of optional fields such as <app-meas_config_file_length>, <app-meas_config-file> can indicate to the application processor that a new application-level measurement profile should be applied when the application-level measurement report is resumed. In some embodiments, preset semantics (e.g., <pause-resume_reporting>="0" and the <app-meas_config_file_length> and <app-meas_config-file> fields are not present) can indicate to the application processor that the profile used before the pause instruction remains valid when the measurement report is resumed.

[0044] In some embodiments, the non-requested result code may include parameters indicating application-level measurement information that represents RAN-specific and visible attributes. In some embodiments, such parameters may be represented as <RVQoE Configuration>, indicating RAN-visible QoE configuration parameters. In some embodiments, reporting configuration attributes may include one or more metrics as part of the application-level measurement information (e.g., buffer level, playlist, broadcast delay, and other appropriate attributes), qualitative or digital scores of the application-level measurement information (e.g., QoE scores), periodicity, reporting or event triggering for reporting the application-level measurement information, and / or other appropriate configuration information. In some embodiments, the non-requested result code may include parameters individually indicating the metrics to be reported in the application-level measurement information. In some embodiments, such parameters may be represented as <RVQoE Report>, indicating RAN-visible QoE reporting parameters.

[0045] After receiving a pause command (e.g., when pausing the transmission of application-level measurement information from the UE to network elements), the UE can receive a recovery command from the network elements instructing the UE to resume transmitting application-level measurement information to the communication network. In some embodiments, in response to the received recovery command and a previously received AT command (i.e., an AT command configuring the modem to send a non-requested result code in response to receiving a pause command or a recovery command), the modem can send a non-requested result code to the application processor, the non-requested result code including a recovery indication that the application processor should resume transmitting application-level measurement information. The UE can then respond to the recovery command to resume transmitting application-level measurement information by the modem.

[0046] In some embodiments, the non-requested result code including the recovery instruction may include an instruction that the application processor should resume transmitting application-level measurements to the modem. In some embodiments, the application processor may transmit measurement information stored in memory (e.g., application-layer memory) to the modem application. In some embodiments, the recovery instruction may include an instruction that the application processor should resume sending application-level measurement information. In some embodiments, the recovery instruction may include an instruction that the streaming service, MTSI service, MBMS service, VR service, and / or another suitable service should resume sending application-level measurement information. In some embodiments, the recovery instruction may include an instruction that the application service instance should resume sending application-level measurement information. In some embodiments, the recovery instruction may include an instruction for the application service type associated with one or more application service instances. In some embodiments, the non-requested result code including the recovery instruction may include an instruction for a new application-level measurement profile of the application service for which the application provides application-level measurement information.

[0047] Various embodiments can improve the operation of the UE and the communication network by enabling the UE to pause and resume reporting application-level measurement information to the communication network. This can alleviate RAN overload conditions, such as network equipment congestion or communication link congestion. Various embodiments can improve the efficiency and performance of the UE and the communication network by continuing to perform application-level measurements and storing application-level measurement information while pausing reporting, and then providing the application-level measurement information when reporting resumes. This can provide the communication network with more information about RAN performance than if reporting application-level measurement information is stopped or terminated.

[0048] FIG1 is a system block diagram illustrating an exemplary communication system 100 suitable for implementing any of the various embodiments. The communication system 100 may be a fifth-generation (5G) new radio (NR) network, or any other suitable network such as an LTE network, a 5G network, etc. Although FIG1 illustrates a 5G network, later generation networks may include the same or similar elements. Therefore, references to 5G networks and 5G network elements in the following description are for illustrative purposes and not for limitation.

[0049] The communication system 100 may include a heterogeneous network architecture, which includes a core network 140 and various mobile devices (illustrated as UEs 120a-120e). The communication system 100 may also include multiple base stations (illustrated as BSs 110a, 110b, 110c, and 110d) and other network entities. A base station is an entity that communicates with the UE and may also be referred to as a Node B, an LTE Evolution Node B (eNodeB or eNB), an Access Point (AP), a Radio Headend, a Transmit / Receive Point (TRP), a New Radio Base Station (NR BS), a 5G Node B (NB), a Next Generation Node B (gNodeB or gNB), etc. Each base station can provide communication coverage for a specific geographic area. In 3GPP, the term "cell" can refer to the coverage area of ​​a base station, the base station subsystem serving that coverage area, or a combination thereof, depending on the context in which the term is used. Core network 140 can be any type of core network, such as LTE core network (e.g., Evolved Packet Core (EPC) network), 5G core network, etc.

[0050] Base stations 110a-110d can provide communication coverage for macrocells, picocells, femtocells, another type of cell, or combinations thereof. Macrocells can cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access for UEs with service subscriptions. Picocells can cover a relatively small geographic area and can allow unrestricted access for UEs with service subscriptions. Femtocells can cover a relatively small geographic area (e.g., a home) and can allow restricted access for UEs associated with that femtocell (e.g., UEs in a Closed Subscriber Group (CSG)). A macrocell base station can be referred to as a macro BS. A picocell base station can be referred to as a pico BS. A base station used for femtocells can be referred to as a femto BS or a home BS. In the example illustrated in Figure 1A, base station 110a can be a macro BS for macrocell 102a, base station 110b can be a pico BS for picocell 102b, and base station 110c can be a femto BS for femtocell 102c. Base stations 110a-110d can support one or more (e.g., three) cells. The terms "eNB", "base station", "NR BS", "gNB", "TRP", "AP", "node B", "5G NB" and "cell" are used interchangeably in this document.

[0051] In some instances, the cells may not be stationary, and the geographical area of ​​the cells may move depending on the location of the mobile base station. In some instances, base stations 110a-110d may interconnect with each other and with one or more other base stations or network nodes (not shown) in communication system 100 via any suitable transport network through various types of backhaul interfaces (such as direct physical connections, virtual networks, or combinations thereof). Base stations 110a-110d may communicate with core network 140 via wired or wireless communication link 126. UEs 120a-120e may communicate with base stations 110a-110d via wireless communication link 122.

[0052] The wired communication link 126 can use various wired networks (e.g., Ethernet, TV cable, telephone, fiber optic and other forms of physical network connection), which can use one or more wired communication protocols, such as Ethernet, point-to-point communication protocol, high-order data link control (HDLC), high-level data communication control protocol (ADCCP) and transmission control protocol / internet protocol (TCP / IP).

[0053] The communication system 100 may also include a relay station (e.g., relay BS 110d). A relay station is an entity that can receive data transmissions from an upstream station (e.g., a base station or a UE) and send data transmissions to a downstream station (e.g., a UE or a base station). A relay station may also be a UE capable of relaying transmissions for other UEs. In the example shown in FIG1A, relay station 110d can perform macro communication with base station 110a and UE 120d to facilitate communication between base station 110a and UE 120d. A relay station may also be referred to as a relay base station, repeater, etc.

[0054] The communication system 100 can be a heterogeneous network, which includes different types of base stations, such as macro base stations, pico base stations, femto base stations, repeater base stations, etc. These different types of base stations can have different transmission power levels, different coverage areas, and different effects on interference in the communication system 100. For example, macro base stations can have high transmission power levels (e.g., 5 to 40 watts), while pico base stations, femto base stations, and repeater base stations can have lower transmission power levels (e.g., 0.1 to 2 watts).

[0055] The network controller 130 can be coupled to a group of base stations and can provide coordination and control for these base stations. The network controller 130 can communicate with the base stations via backhaul. The base stations can also communicate with each other, for example, directly or indirectly via wireless or wired backhaul.

[0056] UEs 120a-120e can be distributed throughout the communication system 100, and each UE can be fixed or mobile. UEs can also be referred to as access terminals, wireless devices, terminals, mobile stations, user units, stations, etc.

[0057] Macro base station 110a can communicate with communication network 140 via wired or wireless communication link 126. UE 120a-120d can communicate with base station 110a-110d via wireless communication link 122.

[0058] Wireless communication links 122 and 124 may include a plurality of carrier signals, frequencies, or frequency bands, each of which may include a plurality of logical channels. Wireless communication links 122 and 124 may utilize one or more radio access technologies (RATs). Examples of RATs that can be used in wireless communication links include 3GPP LTE, 3G, 4G, 5G (e.g., NR), GSM, Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Global System for Microwave Access (WiMAX), Time Division Multiple Access (TDMA), and cellular RATs for other mobile phone communication technologies. Further examples of RATs that can be used in one or more of the various wireless communication links within the communication system 100 include mid-range protocols such as Wi-Fi, LTE-U, LTE-Direct, LAA, and MuLTEfire, and relatively short-range RATs such as ZigBee, Bluetooth, and Bluetooth Low Energy (LE).

[0059] Some wireless networks (e.g., LTE) utilize Orthogonal Frequency Division Multiplexing (OFDM) on the downlink and Single Carrier Frequency Division Multiplexing (SC-FDM) on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, which are also commonly referred to as tones, frequency bands, etc. Each subcarrier can be modulated with data. Typically, modulation symbols are transmitted using OFDM in the frequency domain and SC-FDM in the time domain. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the spacing between subcarriers can be 15 kHz, and the minimum resource allocation (called a "resource block") can be 12 subcarriers (or 180 kHz). Therefore, for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, the nominal Fast File Transfer (FFT) size can be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth can also be divided into subbands. For example, a subband can cover 1.08 MHz (i.e., 6 resource blocks), and there can be 1, 2, 4, 8, or 16 subbands for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, respectively.

[0060] Although the description of some embodiments may use terminology and examples associated with LTE technology, various embodiments may be applicable to other wireless communication systems, such as New Radio (NR) or 5G networks. NR may utilize OFDM with a cyclic prefix (CP) on both the uplink (UL) and downlink (DL) and includes support for half-duplex operation using Time Division Duplex (TDD). A single component carrier bandwidth of 100 MHz may be supported. An NR resource block may span 12 subcarriers with a subcarrier bandwidth of 75 kHz over a duration of 0.1 ms. Each radio frame may include 50 subframes of 10 ms length. Therefore, each subframe may have a length of 0.2 ms. Each subframe may indicate the link direction for data transmission (i.e., DL or UL), and the link direction of each subframe may be dynamically switched. Each subframe may include DL / UL data and DL / UL control data. Beamforming may be supported and the beam direction may be dynamically configured. It can also support precoded multiple-input multiple-output (MIMO) transmission. The MIMO configuration in DL can support up to eight transmit antennas, with each UE having up to eight streams and up to two streams in multilayer DL transmission. Multilayer transmission with up to two streams per UE can be supported. Up to eight serving cells can be used to support the aggregation of multiple cells. Alternatively, NR can support different spatial interfaces besides OFDM-based interfaces.

[0061] Some UEs can be considered Machine-Type Communication (MTC) or Evolved or Enhanced Machine-Type Communication (eMTC) UEs. MTC and eMTC wireless devices include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., which can communicate with base stations, another device (e.g., remote devices), or some other entity. The wireless computing platform can be provided (e.g., via wired or wireless communication links) for networks (e.g., wide area networks such as the Internet or cellular networks) or for connections to networks. Some UEs can be considered Internet of Things (IoT) devices, or can be implemented as NB-IoT (Narrowband Internet of Things) devices. UEs 120a-120e can be included within a housing of components that house the UE, such as processor components, memory components, similar components, or combinations thereof.

[0062] Typically, any number of communication systems and wireless networks can be deployed in a given geographical area. Each communication system and wireless network can support a specific Radio Access Technology (RAT) and can operate on one or more frequencies. RAT can also be referred to as radio technology, air interface, etc. Frequency can also be referred to as carrier, frequency channel, etc. Each frequency can support a single RAT in a given geographical area to avoid interference between communication systems with different RATs. In some cases, 4G / LTE and / or 5G / NR RAT networks can be deployed. For example, a 5G Non-Standalone (NSA) network can use a 4G / LTE RAT on the 4G / LTE RAN side of a 5G NSA network and a 5G / NR RAT on the 5G / NR RAN side of a 5G NSA network. The 4G / LTE RAN and 5G / NR RAN can both be interconnected and connected to the 4G / LTE core network (e.g., Evolved Packet Core (EPC) network) in the 5G NSA network. Other exemplary network configurations may include a 5G standalone (SA) network, in which the 5G / NR RAN is connected to the 5G core network.

[0063] In some implementations, two or more UEs 120a-120e (e.g., illustrated as UE 120a and UE 120e) can communicate directly using one or more sidelink channels 124 (e.g., without using base stations 110a-110d as intermediaries). For example, UEs 120a-120e can communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-the-world (V2X) protocols (which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or similar protocols), mesh networks or similar networks, or combinations thereof. In such cases, UEs 120a-120e can perform scheduling operations, resource selection operations, and other operations described elsewhere herein as being performed by base stations 110a-110d.

[0064] Figure 2 is a block diagram illustrating an exemplary computing and wireless modem system 200 suitable for implementing any of the various embodiments. The various embodiments can be implemented on multiple single-processor and multi-processor computer systems, including system-on-a-chip (SOC) or system-in-package (SIP).

[0065] Referring to Figures 1 and 2, the exemplary computing system 200 shown (which may be a SIP in some embodiments) includes two SOCs 202 and 204 coupled to a clock 206, a voltage regulator 208, and a transceiver 266 configured to transmit and receive wireless communications to / from a UE (e.g., 120a-120e) or a base station (e.g., 110a-110d) via an antenna (not shown). In some embodiments, the first SOC 202 may operate as a central processing unit (CPU) of a UE that executes instructions for a software application by performing arithmetic, logic, control, and input / output (I / O) operations specified by instructions. In some embodiments, the second SOC 204 may operate as a dedicated processing unit. For example, the second SOC 204 may operate as a dedicated 5G processing unit responsible for managing high-capacity, high-speed (e.g., 5 Gbps, etc.) and / or very high-frequency short-wavelength (e.g., 28 GHz millimeter-wave spectrum, etc.) communications.

[0066] The first SOC 202 may include a digital signal processor (DSP) 210, a modem processor 212, a graphics processor 214, an application processor (AP) 216, one or more coprocessors 218 (e.g., vector coprocessors) connected to the processor, memory 220, custom circuitry 222, system components and resources 224, an interconnect / bus module 226, one or more temperature sensors 230, a thermal management unit 232, and a thermal power envelope (TPE) component 234. The second SOC 204 may include a 5G modem processor 252, a power management unit 254, an interconnect / bus module 264, multiple mmWave transceivers 256, memory 258, and various additional processors 260, such as application processors, packet processors, etc.

[0067] Each processor 210, 212, 214, 216, 218, 252, 260 may include one or more cores, and each processor / core may perform operations independently of other processors / cores. For example, the first SOC 202 may include a processor executing a first type of operating system (e.g., FreeBSD, LINUX, OS X, etc.) and a processor executing a second type of operating system (e.g., Microsoft WINDOWS 10). Additionally, any one or all of processors 210, 212, 214, 216, 218, 252, 260 may be included as part of a processor cluster architecture (e.g., synchronous processor cluster architecture, asynchronous or heterogeneous processor cluster architecture, etc.).

[0068] The first SOC 202 and the second SOC 204 may include various system components, resources, and custom circuitry for managing sensor data, analog-to-digital conversion, wireless data transmission, and for performing other specialized operations, such as decoding data packets and processing encoded audio and video signals for presentation in a web browser. For example, the system components and resources 224 of the first SOC 202 may include power amplifiers, voltage regulators, oscillators, phase-locked loops, peripheral bridges, data controllers, memory controllers, system controllers, access ports, timers, and other similar components for supporting processors and software clients running on the UE. The system components and resources 224 and / or custom circuitry 222 may also include circuitry for interfacing with peripheral devices such as cameras, electronic displays, wireless communication devices, and external memory chips.

[0069] The first SOC 202 and the second SOC 204 can communicate via interconnect / bus module 250. Various processors 210, 212, 214, 216, and 218 can be interconnected via interconnect / bus module 226 to one or more memory elements 220, system components and resources 224, as well as custom circuitry 222 and thermal management unit 232. Similarly, processor 252 can be interconnected via interconnect / bus module 264 to power management unit 254, mmWave transceiver 256, memory 258, and various additional processors 260. Interconnect / bus modules 226, 250, and 264 may include reconfigurable gate arrays and / or implement bus architectures (e.g., CoreConnect, AMBA, etc.). Communication can be provided via advanced interconnects such as on-chip high-performance networks (NoCs). Interconnect / bus modules 226, 250, and 264 can be configured individually and / or in various combinations as AT interfaces to enable processors 210, 212, 214, 216, 218, 252, and 260 to exchange AT commands and / or responses with each other.

[0070] The first SOC 202 and / or the second SOC 204 may also include input / output modules (not shown) for communicating with resources outside the SOC, such as clock 206, voltage regulator 208, and one or more wireless transceivers 266. Resources outside the SOC (e.g., clock 206, voltage regulator 208) may be shared by two or more internal SOC processors / cores.

[0071] In addition to the example SIP 200 discussed above, various embodiments can be implemented in various computing systems, which may include a single processor, multiple processors, multi-core processors or any combination thereof.

[0072] Figure 3 is a component block diagram illustrating a software architecture 300, which includes a radio protocol stack for the user and control plane in wireless communication, also known as a radio protocol stack, suitable for implementing any of various embodiments. Referring to Figures 1-3, UE 320 may implement software architecture 300 to facilitate communication between UE 320 (e.g., UE 120a-120e, 200) and base station 350 (e.g., base station 110a-110d) of a communication system (e.g., 100). In some embodiments, layers in software architecture 300 may form logical connections with corresponding layers in the software of base station 350. Software architecture 300 may be distributed among one or more processors (e.g., processors 212, 214, 216, 218, 252, 260). Although an illustration is provided for a single radio protocol stack (or a wireless protocol stack), in a multi-SIM (Subscriber Identity Module) UE, the software architecture 300 may include multiple protocol stacks, each of which may be associated with a different SIM (e.g., in a dual-SIM wireless communication device, the two protocol stacks are associated with two SIMs respectively). Although described below with reference to the LTE communication layer, the software architecture 300 may support any of the various standards and protocols used for wireless communication, and / or may include additional protocol stacks supporting any of the various standards and protocols for wireless communication.

[0073] The software architecture 300 may include a Non-Access Layer (NAS) 302 and an Access Layer (AS) 304. NAS 302 may include functions and protocols supporting packet filtering, security management, mobility control, communication period management, and traffic and signal transmission between the UE's SIM and its core network 140. AS 304 may include functions and protocols supporting communication between the SIM and entities of the supported access network (e.g., base stations). In particular, AS 304 may include at least three layers (Layer 1, Layer 2, and Layer 3), each layer may include various sublayers.

[0074] In the user and control planes, Layer 1 (L1) of AS 304 can be a physical layer (PHY) 306, which can monitor functions that enable transmission and / or reception via the air intermediate plane through a wireless transceiver (e.g., 266). Examples of such physical layer 306 functions may include Cyclic Redundancy Check (CRC) appending, decoding blocks, scrambling and descrambling, modulation and demodulation, signal measurement, MIMO, etc. Physical layer 306 may include various logical channels, including a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH). As an example, PHY layer 306 may support channel state information (CSI) measurement and reporting (e.g., channel quality indicator (CQI) measurement and reporting).

[0075] In the user and control planes, Layer 2 (L2) of AS 304 may be responsible for the link between UE 320 and base station 350 on physical layer 306. In various embodiments, Layer 2 may include a Media Access Control (MAC) sublayer 308, a Radio Link Control (RLC) sublayer 310, a Packet Data Convergence Protocol (PDCP) sublayer 312, and a Service Data Adaptation Protocol (SDAP) sublayer 317, each of which forms a logical connection that terminates at base station 350.

[0076] In the control plane, layer 3 (L3) of AS 304 may include a Radio Resource Control (RRC) sublayer 3. Although not shown, software architecture 300 may include additional third-layer sublayers and various upper layers above the third layer. In various embodiments, RRC sublayer 313 may provide functions including broadcasting system information, paging, and establishing and releasing RRC signaling transfer connections between wireless device 320 and base station 350.

[0077] In various embodiments, SDAP sublayer 317 can provide a mapping between Quality of Service (QoS) streams and Data Radio Bearers (DRBs). In various embodiments, PDCP sublayer 312 can provide uplink functions, including multiplexing between different radio bearers and logical channels, sequence numbering, handover data processing, integrity protection, encryption, and header compression. In the downlink, PDCP sublayer 312 can provide functions including packet ordering, duplicate packet detection, integrity verification, decryption, and header decompression.

[0078] In the uplink, the RLC sublayer 310 can provide segmentation and concatenation of upper-layer data packets, retransmission of lost data packets, and Automatic Repeat Request (ARQ). In the downlink, the functions of the RLC sublayer 310 may include reordering of data packets to compensate for out-of-order reception, reassembly of upper-layer data packets, and ARQ.

[0079] In the uplink, the MAC sublayer 308 can provide functions including multiplexing between logical and transport channels, random access procedures, logical channel prioritization, and hybrid ARQ (HARQ) operations. In the downlink, MAC layer functions can include intracellular channel mapping, demultiplexing, discontinuous reception (DRX), and HARQ operations.

[0080] Although the software architecture 300 provides the ability to transfer data via physical media, the software architecture 300 may further include at least one host layer 314 to provide data transfer services to various applications in the UE 320. In some embodiments, application-specific functions provided by at least one host layer 314 may provide an interface between the software architecture and the general-purpose processor.

[0081] In other embodiments, the software architecture 300 may include one or more higher logical layers (e.g., transport, communication, presentation, application, etc.) that provide host layer functionality. In some embodiments, the software architecture 300 may include an application level where the logical connection terminates at another device (e.g., an end-user device, a server, etc.). In some embodiments, the software architecture 300 may also include a hardware interface 316 in AS 304 between the physical layer 306 and the communication hardware (e.g., one or more radio frequency (RF) transceivers).

[0082] Figure 4A is a message flow diagram illustrating various forms of a method 400 for managing data measurement reports according to various embodiments. Figures 4B and 4C are tables illustrating extended commands 450 and 460 and possible responses. Figures 4D, 4E, 4F, and 4G are tables illustrating command and non-request result codes 470, 472, 474, and 476 according to various embodiments. Figure 4H is a table illustrating commands for reporting measurements 478 according to various embodiments. Referring to Figures 1-4E, various operations of method 400 can be performed by the UE's data unit 402 (e.g., in the UE access layer), the UE's application processor (AP) 404 (e.g., in the UE application layer), network elements of the radio access network (e.g., RAN 406), network elements configured to perform OAM operations (e.g., OAM 408), and network elements configured to perform Tracking Collection Entity (TCE) operations or Multicell / Multicast Coordination Entity (MCW) operations (e.g., TCE / MCE 410).

[0083] Application processor 404 may send AT command 420 to modem 402 to configure modem 402 to receive pause or resume commands from communication network elements such as OAM 408, and to respond appropriately to such pause or resume commands. In some embodiments, AT command 420 may configure modem 402 to send a non-requested result code in response to receiving a pause or resume command relating to the transmission of application-level measurement information collected by UE (e.g., application processor 404). In some embodiments, AT command 420 may include +C syntax commands such as "+CAPPLEVMR", "+CAPPLEVMCNR", "+CAPPLEVMRNR", or "+CAPPLEVMC", and may include additional extensions, arguments, or parameters.

[0084] For example, AT command 420 may include +CAPPLEVMR command 450 (FIG. 4B). As another example, AT command 420 may include +CAPPLEVMC command 470 (FIG. 4C). Various embodiments may also include +CAPPLEVMCNR command. In various embodiments, AT command 420 may enable modem 402 to present non-requested result codes (e.g., +CAPPLEVMR, +CAPPLEVMCNR, +CAPPLEVMRNR, or +CAPPLEVMC), which may include various parameters, such as <app-meas_service_type>, <pause-resume_reporting>, <appmeas_config_file_length>, and <app-meas_config-file>. In some embodiments, the various parameters may correspond to commands from communication network elements (such as pause or resume commands instructing the UE to pause or resume application-level measurement reports). In some embodiments, a non-requested result code may include an integer type <n> that indicates, for example, whether to disable the presentation of non-requested result codes (e.g., "0") or to enable the UE's modem to present non-requested result codes to the UE's application processor (e.g., "1"). In some embodiments, a non-requested result code may include an indication of an application or application service that is the target of an application-level measurement configuration. In some embodiments, the indication of an application or service may be represented by the value of the <app-meas_service_type> parameter. Instances of applications or services include streaming services, MTSI services, MBMS services, VR services, or another suitable service or application.

[0085] In some embodiments, the non-request result code may include parameters (e.g., <pause-resume_reporting>) that indicate one or more additional operations to the application processor 404. For example, a non-requested result code may include a value of "0" for <pause-resume_reporting>, which instructs the application processor 404 to resume application-level measurement data transfer to the modem 402 (e.g., to the access layer), including the transfer of any data stored in application (APP) layer memory (e.g., APP layer buffer) during the pause. As another example, the non-requested result code may include a value of "1" for <pause-resume_reporting>, which instructs the application processor 404 to pause application-level measurement information transfer to the modem 402 and pause measurement operations. As another example, the non-requested result code may include a value of "2" for <pause-resume_reporting>, which instructs the application processor 404 to pause application-level measurement data transfer to the modem 402 and continue recording application-level measurements until the allocated application-level memory is full, after which further measurements are stopped. In some embodiments, a value of "2" for <pause-resume_reporting> may instruct or command the application processor to store application-level measurement information in application-level memory.

[0086] In some embodiments, a value of "1" for <pause-resume_reporting> can instruct or command the application processor to store application-level measurement information, or to send application-level measurement information to the modem 402 for storage in the access layer memory. In some embodiments, a value of "1" for <pause-resume_reporting> can instruct the modem to store application-level measurement information in the access layer memory, and the modem can prevent the sending of non-requested result codes to the application processor as long as the access layer memory is available. In response to a determination that the access layer memory is full (and in some cases, in the absence of a recovery command from the network), the modem can send a non-requested result code including a value of "1" for <pause-resume_reporting> to instruct or command the application processor to suspend the execution of application-level measurements and to suspend the sending of application-level measurement information to the modem.

[0087] In some embodiments, the non-requested result code may include parameters including an application-level measurement profile for the application or service indicated by the <app-meas_service_type> parameter. In some embodiments, the application-level measurement profile may be represented by a string of one or more octets. In such embodiments, the non-requested result code may include parameters, which may be represented by <app-meas_config_file_length>, indicating the number of octets in the profile. In some embodiments, the additional presence of parameters such as <app-meas_config_file_length> and app-meas_config-file> when the value of the <pause-resume_reporting> parameter is "0" may instruct or command the application processor 404 to apply a new application-level measurement profile when the application-level measurement report resumes. In some embodiments, when the value of the <pause-resume_reporting> parameter is "0", the absence of the <app-meas_config_file_length> and <app-meas_config-file> parameters can indicate or command the application processor 404 to keep the configuration file used before the pause command (i.e., the currently used configuration file) valid when resuming reporting of application-level measurement information.

[0088] The data transfer unit 402 may perform operations 422 for application-level measurement reporting. Such operations 422 may include receiving a startup message from the OAM 408, exchanging RRC signal transmissions between the RAN 406 and the data transfer unit 402, and periodically sending application-level measurement reports from the data transfer unit 402 to the TCE / MCE 410. In some embodiments, operations 422 may also include the data transfer unit 402 sending an indication to the RAN 406 of one or more capabilities of the UE related to the application-level measurement report.

[0089] OAM 408 may send a pause command 424 to RAN 406. RAN 406 may send a message 426 to data center 402 that includes or indicates the pause command. In some embodiments, message 426 may be, or may be included in, an RRC signal transmission to data center 402. In some embodiments, OAM 408 may send the pause command 424 to RAN 406 as part of a managed QoE initiation procedure. In some embodiments, in a signal transmission-based QoE initiation procedure, OAM 408 may send QoE measurement configuration messages to network elements of the core network (CN), and the network elements of the core network may send the pause command 424 to RAN 406.

[0090] In response to the received pause command and AT command 420 in message 426, modem 402 may send a non-request result code 428 to application processor 404. In some embodiments, non-request result code 428 may include a pause indication that instructs the application processor to temporarily pause the transmission of all application-level measurement information. In some embodiments, non-request result code 428 may also include an indication or instruction to pause the application processor's collection of all application-level measurement information. In some embodiments, non-request result code 428 may include an indication or instruction to temporarily pause the transmission of RAN-visible QoE application-level measurement information. In some embodiments, non-request result code 428 may include a pause indication or pause instruction to temporarily pause the application processor's transmission and collection of application-level measurement information. In some embodiments, non-request result code 428 may include +C syntax, such as "+CAPPLEVMR", "CAPPLEVMCNR", or "+CAPPLEVMC", and may include additional extensions, arguments, or parameters, such as one or more of the extensions or parameters described above.

[0091] The modem 402 and application processor 404 can perform operation 432 to pause the transmission of application-level measurement information, and they can also pause the application-level measurement procedure. In some embodiments, based on the extension or parameters of the non-request result code 428, the application processor 404 can perform optional operation 432 to continue collecting application-level measurement information and store the collected application-level measurement information according to the configuration information in memory. In some embodiments, the application processor 404 can store the collected application-level measurement information in application-layer memory. In some embodiments, the application processor 404 can perform optional operation 434 to store the collected application-level measurement information in access-layer memory, or send the collected application-level measurement information to the modem 402 for storage in access-layer memory.

[0092] OAM 408 may send a recovery command 436 to RAN 406. RAN 406 may send a message 438 to data center 402 that includes or indicates the recovery command. In some embodiments, message 436 may be included in an RRC signal transmission to data center 402. In some embodiments, OAM 408 may send the recovery command 436 to RAN 406 as part of a managed QoE de-booting procedure. In some embodiments, in a signal transmission-based QoE de-booting procedure, OAM 408 may send a QoE de-booting configuration message to network elements of the core network (CN), and the network elements of the core network may send a recovery command 424 to RAN 406.

[0093] In response to the received recovery command and AT command 420 in message 438, modem 402 may send a non-requested result code 440 to application processor 404. In some embodiments, non-requested result code 440 may include a recovery indication that instructs or commands the application processor to resume the transmission of all application-level measurement information. In some embodiments, non-requested result code 440 may also include an indication or instruction for resuming the collection of all application-level measurement information in the event of a suspension of such measurements. In some embodiments, non-requested result code 440 may include a recovery indication that instructs or commands the application processor to resume the transmission of a subset of application-level measurement information, such as, strictly speaking, RAN-visible QoE application-level measurement information. In some embodiments, non-requested result code 440 may include +C syntax, such as "+CAPPLEVMR", "CAPPLEVMCNR", or "+CAPPLEVMC", and may include additional extensions, arguments, or parameters, such as one or more of those extensions or parameters as described above.

[0094] In response to a recovery instruction, application processor 404 may send an AT command 442, including application-level measurement information, to modem 402. In some embodiments, the application-level measurement information may include a QoE report.

[0095] The modem 402 may send application-level measurement information to the RAN 406 in message 446. In some embodiments, message 446 may be, or may be included in, an RRC signal transmission to the RAN 406.

[0096] RAN 406 can send application-level measurement information to TCE / MCE 410 in message 448.

[0097] Referring to Figures 4D and 4E, in some embodiments, the application processor (UE APP) may send AT commands (e.g., setup commands) to the modem (UE AS), such as +CAPPLEVMC=1, or +CAPPLEVMCNR=1, or +CAPPLEVMR=1. In some embodiments, the modem may respond with non-request result codes 470 or 472. Non-request result codes 470 or 472 may include +CAPPLEVMC, or +CAPPLEVMCNR, or +CAPPLEVMR codes, which include various extensions, arguments, or parameters. Parentheses indicate parameters that may optionally be included in non-request result codes 470 and 472 in some embodiments. In some embodiments, non-request result codes 470 and / or 472 may be enhanced to include one or more of a list of application-specific Quality of Experience (QoE) configurations associated with a single service type or multiple service types (e.g., not just one service type-specific QoE configuration), a flag (or other indication) for pausing or resuming QoE measurement reports for all QoE configurations, and / or a QoE reference ID for distinguishing multiple QoE configurations for an application service type, wherein a pause or resume command may be applied to the one or more service types. In some embodiments, multiple entries in the application-specific QoE configuration list may include up to a specified number N entries (e.g., N=64). In some embodiments, if all active applications on the UE belong to a single service, the QoE_Reference_ID may be present in the non-request result code. In some embodiments, if at least one active application on the UE belongs to a different service type, the presence of <meas_config_app_layer_ID> without <QoE_Reference_ID> would be sufficient (and may preferably be efficient). Other possible parameters may include <meas_config_app_layer_id>, <start-stop_measurement>, <ran_visible_release_only>, <app-meas_config_file_length>, <app-meas_config-file_file>, <transmission_of_session_start-end>, <ran_visible_perioity>, <number_of_buffer_level_entries>, <report_playing_delay>, and <app-meas_service_type>.

[0098] In some embodiments, extensions to non-request result codes 470 and 472 may enable the identification of individual application service instances for pause or resume commands of application-level measurement reports. In some embodiments, parameters or extensions may include configurations or configuration lists. For example, the parameter <QoE_Reference_IDListLength> may include a list of application-specific QoE configurations that may be associated with one or more service types to which pause or resume commands may be applied. In some embodiments, parameters or extensions may include flags or other indications, such as <pause-resume_all>, to pause or resume QoE measurement reports for all QoE configurations. Another flag may indicate that QoE measurement reports for one or more application or QoE configurations should be paused or resumed. In some embodiments, parameters or extensions may include reference IDs to differentiate between QoE measurement report configurations of the same service type (e.g., <QoE_Reference_ID_1>, <QoE_Reference_ID_2>, etc.).

[0099] For example, referring to Figure 4D, non-request result codes 470 and 472 can provide information for two application services. For the first application service, the parameter <app-meas_service_type> = 1 can indicate that the streaming service is the target of QoE measurements (e.g., "QoE measurement set for VR service"). As other instances, <app-meas_service_type> = 2 can indicate "QoE measurement set for MTSI service", and <app-meas_service_type> = 3 can indicate "QoE measurement set for VR service". The parameter <start-stop_reporting> = 2 can indicate that the function is covered by pause / resume signaling. The parameter <QoE_Reference_IDListLength> = 2 can represent two entries in the list, such as "YouTube" and "Netflix". In this example, the parameters <pause-resume_reporting_1> and <pause-resume_reporting_2> are set to '99' to indicate that the parameter is overridden by <pause-resume_all> set to 2 (in some embodiments, it may be assumed that it has the same meaning as <pause-resume_reporting>=2). Some embodiments may omit parameters such as <app-meas_config_file_length> and <app-meas_config-file> for either service. The parameter <app-meas_config-file> may include an application-level measurement profile indicated by the <app-meas_service_type> parameter. In some embodiments, <app-meas_config-file> may not undergo general character conversion according to +CSCS. The parameter <app-meas_config_file_length> may indicate the number of octets of the <app-meas_config-file> parameter.

[0100] For the second service, the parameter <app-meas_service_type> = 3 can indicate the MBMS service for QoE measurements. In some embodiments, the <start-stop_reporting> parameter can be redundant for the second service. The parameter <QoE_Reference_IDListLength> = 1 can represent a single entry in the list, such as "Verizon_NFL". The parameter <pause-resume_reporting_1> = 1 can instruct or command the application processor to pause the measurement or collection of application-level measurement information for this application service type and to pause the transmission of application-level measurement information to the modem. The parameter <app-meas_config_file_length_1> can indicate the length, such as 500 bytes. The parameter <app-meas_config_file_1> can include information such as ASCII encoded character strings, and in some embodiments, it can include 500 bytes of information corresponding to the <app-meas_config_file_length_1> parameter.

[0101] In some embodiments, extensions to the non-requested result codes 470 and 472 may include a variety of other possible parameters. The parameter <transmission_of_session_start-end> may include an indication of whether a communication period start-end is required (e.g., 0 = Not required or 1 = Required). The parameter <ran_visible_periodicity> may indicate a period with values ​​such as "0" indicating 120 ms, "1" indicating 240 ms, "2" indicating 480 ms, "3" indicating 640 ms, or "4" indicating 1024 ms. The parameter <number_of_buffer_level_entries> may indicate the number of buffer level entries, such as 1-8. The parameter <report_initial_playing_delay> may include an indication of whether an initial play delay report is required, for example, "0" indicating "no initial play delay report" or "1" indicating "initial play delay report required". The `<meas_config_app_layer_id>` parameter can be used in QoE measurement configurations to indicate the identifier of the QoE measurement configuration received in the `<app-meas_config-file>`. When a QoE measurement configuration is released, `<meas_config_app_layer_id>` can indicate which measurement to release. In some embodiments, the absence of the `<meas_config_app_layer_id>` parameter can indicate that all measurement configurations are released.

[0102] The <ran_visible_release_only> parameter can include an indication of whether all application-level measurements of <meas_config_app_layer_id> should be released, or whether only RAN-visible application-level measurements should be released. For example, "0" indicates "release RAN-visible application-level measurements of <meas_config_app_layer_id>", and "1" indicates "release all application-level measurements of <meas_config_app_layer_id>".

[0103] Referring to Figures 4F and 4G, in some embodiments, the application processor (UE APP) may send AT commands (e.g., setup commands) to the modem (UE AS), such as +CAPPLEVMC=1, +CAPPLEVMCNR=1, +CAPPLEVMRNR=1, or +CAPPLEVMR=1. In some embodiments, the modem may respond with non-request result codes 474 or 476. In some embodiments, the AT command and non-request result codes 474 or 476 may relate to RAN-visible QoE (RVQoE) configuration and reporting. Non-request result codes 474 or 476 may include +CAPPLEVMC, +CAPPLEVMCNR, +CAPPLEVMRNR, or +CAPPLEVMR codes, which include various extensions, arguments, or parameters. Parentheses indicate parameters that may optionally be included in non-request result codes 474 and 476 in some embodiments. In some embodiments, non-request result code 474 may include extensions, arguments, or parameters formatted to extend the application-level measurement configuration of the +CAPPLEVMC (or +CAPPLEVMCNR) setup command. In some embodiments, non-request result code 474 may include extensions, arguments, or parameters formatted to extend the application-level pause or resume +CAPPLEVMR (or +CAPPLEVMRNR) setting command. In some embodiments, non-request result codes 474 or 476 may include one or more extensions, arguments, or parameters of the RVQoE measurement configuration, which may include the RVQoE metric to be measured (e.g., buffer level, playlist, broadcast delay), the RVQoE value (e.g., a qualitative or digital QoE score), and other configuration attributes such as periodicity and event triggering for reporting RVQoE. In some embodiments, the RVQoE parameters to be measured may include, for example, the <number_of_buffer_level_entries> parameter, the <report_initial_playout_delay> parameter, and the <app-meas_service_type> parameter. In some embodiments, non-request result codes 474 or 476 may include one or more extensions, arguments, or parameters of the RVQoE measurement configuration and associated report pause / resume, which are separate and independent from the currently defined application measurement configuration and associated report pause / resume. In some embodiments, non-request result code 474 or 476 may include one or more extensions, arguments, or parameters to support a dedicated RVQoE measurement or application measurement profile for each application instance of a given service type, or a common RVQoE and application measurement profile for all application instances of that service type.

[0104] Referring to FIG. 4H, in some embodiments, the application processor (UE APP) may send an action command 478, such as +CAPPLEVMR, to report one or more measurements (and / or measurement reports). In some embodiments, the action command 478 may relate to RVQoE configuration and reporting. The action command 478 may include various extensions, arguments, or parameters. Parentheses indicate parameters that may optionally be included in the action command 478. In some embodiments, the action command 478 may include an application-level measurement reporting action command to report existing application measurements and / or RVQoE measurements. In some embodiments, the modem (UE APP) may report service-type application measurements and / or RVQoE measurements. In some embodiments, the modem may report such measurements based on one or more previously received profiles for each measurement type.

[0105] Figure 5 is a flowchart illustrating a method 500 for managing data measurement reports that can be executed by a UE according to various embodiments. Referring to Figures 1-5, method 500 can be implemented by a processor (e.g., 210, 212, 214, 216, 218, 252, 260, 402, 404) of a UE (e.g., 120a-120e, 320).

[0106] In block 502, the UE's application processor can send an AT command to the UE's modem to configure the modem to send a non-requested result code in response to (e.g., via the modem) receiving a pause command or resume command related to the transmission of application-level measurement information collected by the UE. For example, application processor 404 can send AT command 420 to modem 402. The device module for performing the operation of block 502 may include application processors 216, 404 and modem processors 212, 252, 402.

[0107] In block 504, the UE's modem can receive a pause command from the network element while the UE (e.g., the modem) is sending application-level measurement information collected by the UE to the network element. For example, modem 402 can receive message 426, which includes or indicates a pause command, from OAM 408 via RAN 406. The device module for performing the operation of block 504 may include modem processors 212, 252, 402 and radio transceiver 266.

[0108] In block 506, the modem can send a non-requested result code to the application processor. This non-requested result code includes a pause indication or pause instruction to temporarily suspend the transmission of application-level measurement information in response to a received pause command and AT command. For example, modem 402 can send non-requested result code 428 to application processor 404. In some embodiments, a non-requested result code including a pause indication or pause instruction may include an indication or instruction to suspend (e.g., temporarily suspend) the transmission of all application-level measurement information in response to a received pause command and AT command. In some embodiments, a non-requested result code including a pause indication or pause instruction may include an indication or instruction to temporarily suspend the transmission of a subset of all application-level measurement information in response to a received pause command and AT command. In some embodiments, a non-requested result code including a pause indication or pause instruction may include an indication or instruction to temporarily suspend the collection of all application-level measurement information in response to a received pause command and AT command. In some embodiments, a non-requested result code including a pause indication or pause instruction may include an indication or instruction to temporarily suspend the collection of a subset of all application-level measurement information in response to a received pause command and AT command. The device module for performing the operation of block 506 may include application processors 216 and 404 and modem processors 212, 252 and 402.

[0109] In some embodiments, a non-requested result code including a pause indication or pause instruction can instruct or command the application processor to pause (e.g., temporarily pause) the transmission of application-level measurement information from a specific application. In some embodiments, a non-requested result code including a pause indication or pause instruction can instruct or command the application processor to pause the transmission of application-level measurement information from all currently executing applications in the UE, wherein the application processor is transmitting application-level measurement information to the modem for the UE. In some embodiments, a non-requested result code including a pause indication can instruct or command the application processor to pause the transmission of application-level measurement information from a subset of currently executing applications. For example, in some embodiments, the non-requested result code may include an indication to pause one or more application service instances. In some embodiments, the non-requested result code may include an indication of one or more application service types associated with a specific application service instance. In some embodiments, a non-requested result code including a pause indication may also include an indication of whether to enable the presentation of non-requested result codes from the UE's modem to the UE's application processor (e.g., sending a notification from the UE's modem to the UE's application processor). In some embodiments, the non-requested result code including the pause instruction may also include an instruction to the application processor to continue collecting application-level measurement information and to store the collected application-level measurement information in application-layer memory.

[0110] In some embodiments, the non-requested result code including a pause indication may include an indication or instruction to pause the collection of RAN Visible QoE (RVQoE) metrics as separate application-level measurement information in response to a received pause command and AT command. In some embodiments, the non-requested result code including a pause indication may include an indication of the application service instance associated with the RAN Visible QoE application-level measurement information based on information in the application measurement profile. In some embodiments, the non-requested result code including a pause indication may include an indication of the application service type associated with the application service instance associated with the RAN Visible QoE application-level measurement information.

[0111] In some embodiments, the non-requested result code may include a pause indication to temporarily suspend the application processor from sending application-level measurement information. In some embodiments, the application-level measurement information associated with the non-requested result code may relate to RAN-visible QoE metric measurement information. In some embodiments, the non-requested result code may include a pause indication or pause command to pause the temporary application processor from sending all application-level measurement information, a subset of application-level measurement information corresponding to RAN-specific visible QoE metric measurement information, or a subset of application-level measurement information not corresponding to RAN-specific visible QoE metric measurement information.

[0112] In some embodiments, the non-request result code may also include an indication or instruction to suspend the application processor's collection of all application-level measurement information. In some embodiments, the non-request result code may include an indication or instruction to temporarily suspend the transmission of RAN-visible QoE application-level measurement information. In some embodiments, the non-request result code may include a pause indication or pause instruction to temporarily suspend the application processor's transmission and collection of application-level measurement information.

[0113] In block 508, the UE can respond to a pause command by pausing the transmission of application-level measurement information by the modem. For example, modem 402 and application processor 404 can pause the transmission of application-level measurement information for all running applications, for a specific application, or for a subset of all running applications. In some embodiments, application processor 404 can further pause the execution of application-level measurement procedures for all running applications, for a specific application, or for a subset of all running applications. The device module for performing the operations of block 508 may include application processors 216, 404 and modem processors 212, 252, 402.

[0114] Figure 6 is a flowchart illustrating an operation 600 that can be executed by a UE as part of a method 500 for managing data measurement reports, according to various embodiments. Referring to Figures 1-6, operation 600 can be implemented by a processor (e.g., 210, 212, 214, 216, 218, 252, 260, 402, 404) of the UE (e.g., 120a-120e, 320).

[0115] After suspending the transmission of application-level measurement information by the modem in response to the pause command in block 508 as described above, the UE can receive a recovery command from network components. For example, modem 402 can receive message 438, which includes or indicates a recovery command, from OAM 408 via RAN 406. The device module for performing the operation of block 602 may include modem processors 212, 252, 402 and radio transceiver 266.

[0116] In block 604, the modem may respond to the received recovery command and AT command by sending an unsolicited result code including a recovery indication to the application processor to resume the transmission of application-level measurement information. For example, in response to the received recovery command and AT command 420 in message 438, modem 402 may send an unsolicited result code 440 to application processor 404. In some embodiments, the unsolicited result code including a recovery indication may also include an indication for the application processor to resume transmitting application-level measurements to the modem. In some embodiments, the unsolicited result code including a recovery indication may include an indication for all executing applications, a specific application, or an indication for a subset of all executing applications for which the application processor had previously suspended the transmission of application-level measurement information to the modem. In some embodiments, the unsolicited result code including a recovery indication may relate to a subset of all currently executing applications, indicating which executing application(s) should be resumed via the transmission of application-level measurement information from the application processor to the modem. In some embodiments, the non-request result code may include a recovery indication that instructs or commands the application processor to resume sending a subset of application-level measurement information, such as RAN-visible QoE application-level measurement information.

[0117] In some embodiments, the non-requested result code including the recovery indication may also include an indication to apply one or more new application-level measurement profiles, which correspond to an application service that provides application-level measurement information. The device module for performing the operation of block 604 may include application processors 216, 404 and modem processors 212, 252, 402.

[0118] In block 606, the UE may respond to a recovery command by resuming the transmission of application-level measurement information by the modem. In some embodiments, resuming the transmission of application-level measurement information in response to a recovery command may include resuming the transmission of application-level measurements for a specific application of the UE, all executed applications, or a subset of all executed applications of the UE to the modem of the UE. In some embodiments, resuming the transmission of application-level measurement information in response to the recovery command may include transmitting application-level measurement information stored in memory to the modem. For example, in some embodiments, application processor 404 may send an AT command 442 including application-level measurement information to modem 402, and modem 402 may send application-level measurement information to RAN 406 in message 446. The device module for performing the operations of block 602 may include modem processors 212, 252, 402, application processors 216, 404, and radio transceiver 266.

[0119] Figure 7 is a component block diagram of a UE 700 suitable for use with various embodiments. Referring to Figures 1-7, various embodiments including method 500 and operation 600 can be performed in various UEs (e.g., UEs 120a-120e, 320), such as UE 700. UE 700 may include a first SOC 202 (e.g., SOC-CPU) coupled to a second SOC 204 (e.g., a SOC with 5G capability). The first SOC 202 and the second SOC 204 may be coupled to internal memory 716, a display 712, and a speaker 714. Additionally, UE 700 may include an antenna 704 for transmitting and receiving electromagnetic radiation, which may be connected to a wireless data link and / or to a cellular transceiver 266 coupled to one or more processors in the first SOC 202 and / or the second SOC 204. UE 700 may also include a menu selection button or rocker switch 720 for receiving user input.

[0120] The UE 700 may also include a voice encoding / decoding (CODEC) circuit 710, which digitizes the sound received from the microphone into data packets suitable for wireless transmission and decodes the received voice data packets to generate an analog signal provided to the speaker to produce sound. Furthermore, one or more processors among the first SOC 202, the second SOC 204, the wireless transceiver 266, and the CODEC 710 may include digital signal processor (DSP) circuitry (not shown separately).

[0121] The processors of the wireless network computing device 700 and UE 700 can be any programmable microprocessor, microcomputer, or one or more multiprocessor chips that can be configured by software instructions (applications) to perform various functions (including those described in the various embodiments below). In some mobile devices, multiple processors may be provided, such as one processor within SOC 204 dedicated to wireless communication functions and one processor within SOC 202 dedicated to executing other applications. Software applications may be stored in memories 426, 430, 716 before being accessed and loaded into the processor. The processor may include sufficient internal memory to store application software instructions.

[0122] FIG8 is a block diagram of components of a network computing device 800 suitable for use with various embodiments. Referring to FIG1-8, various embodiments can be implemented on various network computing devices, such as network computing device 800, which serves as a network element of a communication network, such as network elements of base stations 110a-110d, 350, RAN 406, OAM 408, TCE / MCE 410, etc. Such network computing devices may include at least the components shown in FIG8. Network computing device 800 may typically include a processor 801 coupled to volatile memory 802 and mass non-volatile memory such as disk drive 803. Network computing device 800 may also include peripheral memory access devices coupled to processor 801, such as floppy disk drive, compact disk (CD) or digital video disc (DVD) drive 806. The network computing device 800 may also include a network access port 804 (or interface) coupled to the processor 801 for establishing data connections with networks (such as the Internet and / or local area networks) coupled to other system computers and servers. The network computing device 800 may include one or more antennas 807 for transmitting and receiving electromagnetic radiation that can be connected to a wireless communication link. The network computing device 800 may include additional access ports for coupling to peripheral devices, external memory, or other devices, such as USB, FireWire, Thunderbolt, etc.

[0123] As used in this case, the terms "part," "module," "system," etc. are intended to include computer-related entities, such as, but not limited to, hardware, firmware, combinations of hardware and software, software, or software in execution configured to perform a specific operation or function. For example, a part may be, but is not limited to, a program, a processor, an object, an executable program, an execution thread, a program, and / or a computer running on a processor. By way of illustration, both the application and the UE executed on the UE may be referred to as parts. One or more components may reside within a program and / or execution thread, and the components may be located on one processor or core and / or distributed between two or more processors or cores. In addition, these parts can be executed from various non-temporary computer-readable media on which various instructions and / or data structures are stored. Parts may communicate via local and / or remote programs, function or program dialing, electronic signals, data packets, memory read / write, and other known communication methods for networks, computers, processors, and / or programs related to the program.

[0124] A variety of different cellular and mobile communication services and standards can be obtained or expected in the future, all of which can be realized and benefit from various embodiments. Such services and standards include, e.g., 3rd Generation Partner Program (3GPP), Long Term Evolution (LTE) System, 3rd Generation Wireless Mobile Communication Technology (3G), 4th Generation Wireless Mobile Communication Technology (4G), 5th Generation Wireless Mobile Communication Technology (5G), Mobile Communication Global System (GSM), Universal Mobile Telecommunications System (UMTS), 3GSM, Universal Packet Radio Service (GPRS), CDMAC Multiplexer System Access (GPRS), c DMA1020™), GSM Evolved Enhanced Data Rate (EDGE), Advanced Mobile Phone System (AMPS), Digital AMPS (IS-136 / TDMA), Evolved Data Optimization (EV-DO), Digitally Enhanced Powerless Wire Telecommunications (DECT), Global Interoperability Microwave Access (WiMAX), Wireless Area Network (WLAN), Wi-Fi Protected Access I&WPA2 (Wi). Each of these technologies involves, for example, the transmission and reception of voice, data, signal transmission and / or content messages. It is to be understood that any reference to terminology and / or technical details relating to individual telecommunications standards or technologies is for illustrative purposes only and that it is not desirable to limit the scope of the claim to a particular communication system or technology, except as specifically stated in the claim language.

[0125] The various embodiments illustrated and described are provided by way of example only to illustrate the various features of the claimed item. However, the features shown and described with respect to any given embodiment are not necessarily limited to the associated embodiment, but can be used or combined with other embodiments shown and described. Furthermore, the claimed item is not intended to be limited to any one example embodiment. For example, one or more operations of methods 500 and 600 may replace or be combined with one or more operations of methods 500 and 600.

[0126] Examples of implementations are described in the following paragraphs. Although some of the following examples of implementations are described according to the exemplary methods, further example implementations may include: the exemplary method discussed in the following paragraphs is implemented by a UE, the UE including a processor configured to perform the operations of the exemplary method; the exemplary method discussed in the following paragraphs is implemented by a UE, the UE including a modem processor configured to perform the operations of the exemplary method; the exemplary method discussed in the following paragraphs is implemented by a UE, the UE including units for performing the functionality of the exemplary method; and the exemplary method discussed in the following paragraphs is implemented as a non-transitory processor-readable storage medium having processor-executable instructions stored thereon, the processor-executable instructions being configured to cause a processor of the UE or a modem processor to perform the operations of the exemplary method.

[0127] Example 1. A method for managing data measurement reports performed by a user equipment (UE), the method comprising: sending an attention (AT) command from an application processor of the UE to a modem of the UE to configure the modem to send a non-requested result code in response to receiving a pause command or a resumption command relating to the transmission of application-level measurement information collected by the UE; receiving a pause command from a network element while the UE is transmitting application-level measurement information collected by the UE to a network element; in response to the received pause command and AT command, sending a non-requested result code from the modem to the application processor including a pause indication or a pause instruction for temporarily suspending the transmission of application-level measurement information; and suspending the transmission of application-level measurement information by the modem in response to the pause command.

[0128] Example 2. According to the method of Example 1, the non-requested result code including the pause indication or pause instruction includes an indication or instruction to temporarily suspend the transmission of all application-level measurement information in response to a received pause command and AT command.

[0129] Example 3. According to the method of Example 1 or 2, the non-requested result code including the pause indication or pause instruction includes an indication or instruction that temporarily suspends the transmission of at least a subset of all application-level measurement information in response to a received pause command and AT command.

[0130] Example 4. The method according to any one of Examples 1-3, including a non-requested result code for a pause instruction or pause command, including an instruction or command to temporarily suspend the collection of all application-level measurement information in response to a received pause command and AT command.

[0131] Example 5. The method according to any one of Examples 1-4, including a non-requested result code of a pause indication or pause instruction, comprising an indication or instruction to temporarily suspend the collection of at least a subset of all application-level measurement information in response to a received pause command and AT command.

[0132] Example 6. The method according to any one of request items 1-5, including a non-requested result code for a pause indication or pause instruction, includes an indication of an application service instance that provides application-level measurement information based on information in the application measurement profile.

[0133] Example 7. According to the method of Example 6, the non-requested result code of the recovery indication or recovery instruction also includes an indication of the application service type associated with the application service instance.

[0134] Example 8. The method of any one of Examples 1-7, wherein the AT command includes an indication of whether to enable the presentation of a non-requested result code by the UE's modem to the UE's application processor.

[0135] Example 9. The method according to any one of Examples 1-8, including a non-requested result code for a pause indication or pause instruction, includes an indication or instruction for the application processor to continue collecting application-level measurement information and to store the collected application-level measurement information according to configuration information in the application-layer memory.

[0136] Example 10. The method of any one of Examples 1-9, wherein the modem includes the access layer of the UE and the application processor includes the application level of the UE.

[0137] Example 11. The method according to any one of Examples 1-10 also includes receiving a recovery command from the network element when the transmission of application-level measurement information from the UE to the network element is suspended; in response to the received recovery command and AT command, sending a non-requested result code from the modem to the application processor including a recovery indication or recovery instruction to resume the transmission of application-level measurement information; and in response to the recovery command, resuming the transmission of application-level measurement information via the modem.

[0138] Example 12. According to the method of Example 11, the non-requested result code of the recovery indication or recovery command may include an indication for the application processor to resume transmitting application-level measurements to the modem, and resuming the transmission of application-level measurement information in response to the recovery command may include resuming the transmission of application-level measurements from the UE's application processor to the UE's modem.

[0139] Example 13. According to the method of Example 12, the non-requested result code including the recovery indication or recovery instruction includes the indication or instruction to resume sending all application-level measurement information in response to the received recovery command and AT command.

[0140] Example 14. According to the method of Example 12, the non-requested result code including the recovery indication or recovery instruction includes an indication or instruction that, in response to a received recovery command and AT command, recovers the transmission of at least a subset of all application-level measurement information.

[0141] Example 15. According to the method of Example 11, the transmission of application-level measurement information in response to a recovery command includes transmitting application-level measurement information stored in application-layer memory to the modem.

[0142] Example 16. According to the method of Example 11, the non-requested result code, including the recovery indication or recovery instruction, includes an indication to recover the application service instance that sends application-level measurement information.

[0143] Example 17. According to the method of Example 16, the non-requested result code of the recovery indication or recovery instruction also includes an indication of the application service type associated with the application service instance.

[0144] Example 18. According to the method of Example 11, the non-requested result code including the recovery indication or recovery instruction includes an indication of a new application-level measurement profile for an application service that provides application-level measurement information.

[0145] The above method description and flowchart are provided as illustrative examples only and are not intended to require or imply that the operations of the various embodiments must be performed in the presented order. As will be appreciated by those skilled in the art to which this invention pertains, the order of operations in the foregoing embodiments can be performed in any order. Words such as "after," "following," and "next" are not intended to limit the order of operations; these words are used to guide the reader in understanding the description of the method. Furthermore, any reference to an element of a claim in the singular form, such as the use of the article "the," should not be construed as limiting the element to the singular.

[0146] The various illustrative logic blocks, modules, components, circuits, and algorithmic operations described in conjunction with the embodiments disclosed herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability between hardware and software, various illustrative components, blocks, modules, circuits, and operations have been described above in their functional forms. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art to which this invention pertains may implement the described functionality in different ways for each specific application, but such implementation decisions should not be construed as causing a departure from the scope of this claim.

[0147] The hardware used to implement the various illustrative logics, logic blocks, modules, and circuits described in conjunction with the embodiments disclosed herein may be implemented or performed by a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, individual gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any known processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of receiver intelligent objects, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors with a DSP core, or any other such configuration. Alternatively, some operations or methods may be performed by circuitry specific to a given function.

[0148] In one or more embodiments, the described functionality may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functionality may be stored as one or more instructions or code on a non-transitory computer-readable storage medium or a non-transitory processor-readable storage medium. The operation of the methods or algorithms disclosed herein may be implemented in a processor-executable software module or processor-executable instructions, which may reside on a non-transitory computer-readable or processor-readable storage medium. A non-transitory computer-readable or processor-readable storage medium may be any storage medium accessible by a computer or processor. By way of example and not limitation, such non-transitory computer-readable or processor-readable storage media may include RAM, ROM, EEPROM, flash memory, CD-ROM or other optical disc storage devices, magnetic storage devices or other magnetic storage objects, or any other medium that can be used to store desired program code in the form of instructions or data structures and is accessible by a computer. As used in this case, magnetic disks and optical disks include CDs, laser discs, optical discs, DVDs, floppy disks, and Blu-ray discs. Magnetic disks generally reproduce data magnetically, while optical disks reproduce data optically using lasers. The above combinations also fall within the scope of non-transitory computer-readable and processor-readable media. Furthermore, the operation of a method or algorithm may reside as one or any combination or set of code and / or instructions on non-transitory processor-readable and / or computer-readable storage media that can be incorporated into a computer program product.

[0149] The foregoing description of the disclosed embodiments is intended to enable anyone skilled in the art to draft or use the claims. Various modifications to these embodiments will readily be apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments without departing from the scope of the claims. Therefore, this application is not intended to be limited to the embodiments shown herein, but should be given the broadest scope consistent with the appended claims and the principles and novel features disclosed herein. [Simplified Explanation of the Diagram]

[0013] The accompanying drawings, which are incorporated herein and form part of this specification, illustrate exemplary embodiments of the requested item and, together with the general description provided above and the detailed description provided below, serve to explain the features of the requested item.

[0014] Figure 1 is a system block diagram illustrating an exemplary communication system suitable for implementing any of the various embodiments.

[0015] Figure 2 is a block diagram illustrating an exemplary computing and wireless modem system suitable for implementing any of the various embodiments.

[0016] Figure 3 is a diagram illustrating an example of a software architecture including a stack of radio protocols for user and control planes in wireless communications, according to various embodiments.

[0017] Figure 4A is a message flow diagram illustrating various methods for managing data measurement reports according to various embodiments.

[0018] Figures 4B and 4C are tables illustrating extended commands and possible responses.

[0019] Figures 4D, 4E, 4F and 4G are tables illustrating command and non-request result codes according to various embodiments.

[0020] Figure 4H is a table illustrating the action commands for reporting measurements according to various embodiments.

[0021] Figure 5 is a flowchart illustrating a method for managing data measurement reports that can be executed by a UE according to various embodiments.

[0022] Figure 6 is a flowchart illustrating operations that can be performed by the UE as part of a method for managing data measurement reports according to various embodiments.

[0023] Figure 7 is a component block diagram of a UE suitable for use with various embodiments.

[0024] Figure 8 is a component block diagram of a network computing device suitable for use with various embodiments. [Biomaterial Storage]

[0151] Domestic storage information (please note in order of storage institution, date, and number): None. International storage information (please note in order of storage country, institution, date, and number): None.

Claims

1. A method for managing data measurement reports executed by a user equipment (UE), comprising the steps of: sending an Attention (AT) command from an application processor of the UE to a modem of the UE to configure the modem to send a non-requested result code in response to receiving a pause command or a resume command relating to the transmission of application-level measurement information collected by the UE; receiving a pause command from the network element while the UE is transmitting the application-level measurement information collected by the UE to a network element; in response to the received pause command and the AT command, sending a non-requested result code from the modem to the application processor including a pause indication or a pause instruction to temporarily suspend the transmission of the application-level measurement information, wherein the non-requested result code of the pause indication or the pause instruction includes an indication or instruction to temporarily suspend the collection of at least a subset of all application-level measurement information in response to the received pause command and the AT command; and in response to the pause command, suspending the modem from transmitting the application-level measurement information.

2. The method according to Request 1, including the non-requested result code of the pause indication or the pause instruction, comprising an indication or instruction that temporarily suspends the transmission of at least a subset of all application-level measurement information in response to the received pause command and the AT command.

3. According to the method of request item 1, a non-requested result code including the pause indication or the pause instruction includes an indication of an application service instance that provides application-level measurement information based on information in an application measurement profile.

4. According to the method of request item 3, including the non-requested result code of the pause indication or the pause instruction, it also includes an indication of an application service type associated with the application service instance.

5. The method according to request item 1, wherein the AT command includes an indication of whether to enable the modem of the UE to present the non-requested result code to the application processor of the UE.

6. The method according to request item 1, including the non-requested result code of the pause instruction or pause command, includes an instruction or command to continue collecting application-level measurement information for the application processor and to store the collected application-level measurement information according to configuration information in the application layer memory.

7. The method according to request item 1 also includes: While suspending the transmission of application-level measurement information from the UE to the network element, a recovery command is received from the network element; In response to the received recovery command and the AT command, and based on the configuration information, the modem sends a non-requested result code to the application processor, including a recovery indication or recovery instruction to resume sending application-level measurement information; and in response to the recovery command, resumes the sending of application-level measurement information by the modem.

8. According to the method of request item 7, wherein: The non-requested result code of the recovery indication or the recovery command includes an indication for the application processor to resume transmitting application-level measurements to the modem; and resuming the transmission of application-level measurement information in response to the recovery command includes resuming the transmission of application-level measurements from the UE's application processor to the UE's modem.

9. The method according to request item 8, including the non-requested result code of the recovery indication or the recovery instruction, comprising an indication or instruction to resume sending at least a subset of all application-level measurement information in response to the received recovery command and the AT command.

10. The method according to request item 7, wherein responding to the recovery command to resume sending application-level measurement information includes transmitting application-level measurement information stored in application-layer memory to the modem.

11. The method according to request item 7, including the non-requested result code of the recovery instruction or recovery command including an instruction to restore the application service instance that sends application-level measurement information.

12. The method according to request item 11, including the non-requested result code of the recovery indication or the recovery instruction, also includes an indication of the application service type associated with the application service instance.

13. According to the method of request item 7, including the non-requested result code of the recovery instruction or the recovery command including an instruction for a new application-level measurement profile of the application service that provides the application-level measurement information.

14. A user equipment (UE), comprising: An application processor; A modem, wherein: the application processor is configured to send an Attention (AT) command to the modem to configure the modem to send a non-requested result code in response to receiving a pause command or a resume command relating to the transmission of application-level measurement information collected by the UE; and the modem is configured to: receive a pause command from a network element while the UE is transmitting the application-level measurement information collected by the UE to a network element; in response to the received pause command and the AT command, send a non-requested result code to the application processor including a pause indication or a pause instruction to temporarily suspend the transmission of the application-level measurement information, wherein the non-requested result code of the pause indication or the pause instruction includes an indication or instruction to temporarily suspend the collection of at least a subset of all application-level measurement information in response to the received pause command and the AT command; and suspend the transmission of the application-level measurement information in response to the pause command.

15. The UE according to request item 14, including the non-requested result code of the pause indication or the pause instruction, which includes an indication or instruction that temporarily suspends the transmission of at least a subset of all application-level measurement information in response to the received pause command and the AT command.

16. The UE according to request item 14, including the non-requested result code of the pause indication or the pause instruction, includes an indication of an application service instance that provides application-level measurement information based on information in an application measurement profile.

17. The UE according to request item 16, including the non-requested result code of the pause indication or the pause instruction, also includes an indication of the application service type associated with the application service instance.

18. The UE according to request item 14, wherein the AT command includes an indication of whether to enable the modem of the UE to present the non-requested result code to the application processor of the UE.

19. The UE according to request item 14, including the non-requested result code of the pause indication or the pause instruction, includes an indication or instruction for the application processor to continue collecting application-level measurement information and to store the collected application-level measurement information in application-layer memory.

20. The UE according to request item 14, wherein the modem is also configured to: receive a recovery command from the network element while suspending the transmission of application-level measurement information from the UE to the network element; in response to the received recovery command and the AT command, send a non-requested result code, including a recovery indication or recovery instruction to the application processor according to configuration information; and in response to the recovery command, resume the transmission of application-level measurement information.

21. According to request item 20, for the UE, where: The non-requested result code, including the recovery indication or the recovery instruction, includes an indication for the application processor to resume transmitting application-level measurements to the modem; and the modem is also configured to resume transmitting application-level measurements from the UE's application processor to the UE's modem.

22. The UE according to request item 21, including the non-requested result code of the recovery indication or the recovery instruction, comprising an indication or instruction that, in response to the received recovery command and the AT command, resumes the transmission of at least a subset of all application-level measurement information.

23. According to request item 20, the UE, wherein the application processor is also configured to transmit application-level measurement information stored in application-layer memory to the modem.

24. The UE according to request item 20, including the non-requested result code of the recovery indication or the recovery instruction, includes an indication to resume sending application service instances of application-level measurement information.

25. The UE according to request item 24, including the non-requested result code of the recovery indication or the recovery instruction, also includes an indication of the application service type associated with the application service instance.

26. According to request item 20, the non-requested result code of the recovery indication or the recovery instruction includes an indication of a new application-level measurement profile of the application service that provides the application-level measurement information.

27. A user equipment (UE), comprising: An application processor; A data machine; A device module for sending an Attention (AT) command from an application processor to a modem to configure the modem to send a non-requested result code in response to receiving a pause command or a resume command related to sending application-level measurement information collected by the UE; a device module for receiving a pause command from a network element while the UE is sending application-level measurement information collected by the UE to a network element; a device module for sending a non-requested result code from the modem to the application processor in response to the received pause command and the AT command, including a pause indication or a pause instruction to temporarily pause the sending of application-level measurement information, wherein the non-requested result code of the pause indication or the pause instruction includes an indication or instruction to temporarily pause the collection of at least a subset of all application-level measurement information in response to the received pause command and the AT command; and a device module for suspending the modem from sending the application-level measurement information in response to the pause command.

28. A non-transitory processor-readable medium having processor-executable instructions stored thereon, the processor-executable instructions being configured to cause a processing device in a user equipment (UE) to perform an operation, the operation including: An application processor of the UE sends an Attention (AT) command to a modem of the UE to configure the modem to send a non-requested result code in response to receiving a pause command or a resume command related to the transmission of application-level measurement information collected by the UE; while the UE is transmitting the application-level measurement information collected by the UE to a network element, a pause command is received from the network element; in response to the received pause command and the AT command, a non-requested result code is sent from the modem to the application processor, including a pause indication or a pause instruction to temporarily suspend the transmission of the application-level measurement information, wherein the non-requested result code of the pause indication or the pause instruction includes an indication or instruction to temporarily suspend the collection of at least a subset of all application-level measurement information in response to the received pause command and the AT command; and in response to the pause command, the modem suspends the transmission of the application-level measurement information.

Images