A communication method and apparatus

Abstract

A communication method and device, the method comprising: a first data collection client of a terminal device receiving data collection configuration information, the data collection configuration information being used to instruct the terminal device to collect and report data of a service; the first data collection client receiving first information, the first information being used to notify the terminal device to stop reporting the data of the service; the first data collection client storing the data of the service in a target function module of the terminal device; the terminal device receiving second information, the second information being used to instruct the terminal device to resume / start reporting the data of the service. It can be known that in the scheme, when the first data collection client of the terminal device stops reporting the collected data of the service, the data of the service can be stored in cooperation with the target function module of the terminal device, so that the integrity and reliability of the terminal device reporting the data of the service can be ensured.

Description

Technical Field

[0001] This application relates to the field of communication technology, and more particularly to a communication method and apparatus. Background Technology

[0002] With the continuous development of communication technology, users have increasingly higher requirements for the network service quality of terminal devices. Therefore, in order to meet the growing needs of users, service data of terminal devices can be collected and analyzed to determine the service quality information (or user experience quality) of the terminal devices. Then, the network can be optimized based on the service quality information to provide better network services for terminal devices.

[0003] In one current approach, the terminal device (e.g., a data collection client) first collects service data from the terminal device to determine its service quality information. Then, the data collection client reports this service quality information to the access network device. Further, the access network device continues to report this information to other network elements, such as operation administration and maintenance (OAM) elements and data collection elements. In this reporting scheme, the service quality information is transparent to the access network device; the access network device can perceive that this is service experience quality information reported by the terminal device, but it cannot parse the information within it.

[0004] However, in some scenarios, network congestion may occur in the access network equipment due to various reasons, making it difficult for terminal devices to report their service quality information (or service data) to the access network equipment. In this case, the access network equipment will send an instruction to the terminal device to instruct it to suspend the reporting of service quality information (or service data). After receiving the instruction, the terminal device will cache the service quality information (or service data) in the access layer of the terminal device. However, since the access layer cache space of the terminal device is limited, the service quality information (or service data) can usually be cached by the application on the terminal device. However, when the application on the terminal device is closed, the cached service quality information (or service data) will be lost.

[0005] Therefore, there is an urgent need to propose a communication method that can ensure the integrity and reliability of the service quality information reported by the terminal device side for application (or service data). Summary of the Invention

[0006] A communication method and apparatus that can ensure the integrity and reliability of data reported by terminal devices.

[0007] In a first aspect, embodiments of this application provide a communication method. This method can be executed by a functional module (such as a first data collection client, an access layer, and a target functional module) in a terminal device, or by a chip corresponding to the functional module (such as the first data collection client, the access layer, and the target functional module) in the terminal device. This application does not limit the execution of this method. The method specifically includes the following steps: the first data collection client of the terminal device receives data collection configuration information, which instructs the terminal device to collect and report service data; the first data collection client receives first information, which notifies the terminal device to stop reporting the service data; the first data collection client stores the service data in the target functional module of the terminal device; the terminal device receives second information, which instructs the terminal device to resume / start reporting the service data.

[0008] In this application, after receiving data collection configuration information, the first data collection client of the terminal device can collect data of the terminal device's services and report the collected service data to the data collection network element through the access network device. When the first data collection client receives first information, which notifies the terminal device to stop reporting service data, or when the first data collection client stops or is shut down, it can store or cache the service data in the target functional module of the terminal device. When the terminal device receives second information, it can be instructed to resume / start reporting service data. Therefore, this solution, when the first data collection client of the terminal device stops reporting collected service data, can coordinate with the target functional module of the terminal device (i.e., other available functional modules) to temporarily store the service data to avoid data loss, thereby ensuring the integrity and reliability of the service data reported by the terminal device.

[0009] In one possible implementation, the first data collection client of the terminal device receives data collection configuration information, including: the first data collection client of the terminal device receives the data collection configuration information from the data collection network element.

[0010] For example, the first data collection client of the terminal device can receive the data collection configuration information from the data collection network element through the access network device.

[0011] Through this implementation, the first data collection client of the terminal device receives data collection configuration information from the data collection network element. Then, based on the data collection configuration information, it can collect business data and accurately report the business data of the terminal device to the data collection network element.

[0012] In one possible implementation, the data collection configuration information includes first instruction information, which instructs the first data collection client to send and store the service data in the target functional module of the terminal device when the first data collection client is closed or stopped.

[0013] In this embodiment of the application, sending the service data to the target functional module can be assumed to mean caching or storing the service data in the target functional module.

[0014] Optionally, the first instruction information further instructs the first data collection client to retrieve the stored data of the service from the target function module of the terminal device and report it when restoring / starting the data reporting of the service.

[0015] In one possible implementation, the first instruction information is further used to instruct the first data collection client, when restoring / starting the reporting of data for the service, to check whether the memory in the terminal device stores the data for the service. If the memory contains the data for the service, the first data collection client can retrieve the data for the service from the memory and then report the data for the service to the data collection network element. Optionally, the first data collection client also sends the identification information of the service to the data collection network element.

[0016] With this implementation, when the first data collection client of the terminal device stops or shuts down, it can send the service data collected by the terminal device to other functional modules (i.e., target functional modules) of the terminal device according to the first instruction information in the data collection configuration information, and temporarily store it in the target functional module (optionally, when the first data collection client of the terminal device resumes / starts reporting the service data, it can also obtain the stored service data from the target functional module and report it according to the first instruction information). This can avoid the loss of service data due to the first data collection client stopping or shutting down, and can also ensure the integrity and reliability of the service data reported by the terminal device.

[0017] In one possible implementation, the target functional module is the access layer of the terminal device; the terminal device receiving the second information includes: the access layer of the terminal device receiving the second information; the method further includes: the access layer of the terminal device sending the data of the service to the data collection network element, and optionally, the first data collection client also sending the identification information of the service to the data collection network element.

[0018] With this implementation, when the target functional module is the access layer of a terminal device, the access layer of the terminal device stores the service data when the terminal device pauses or stops reporting the service data (optionally, the access layer of the terminal device can additionally store the service's identification information). When the network side resumes normal communication, the access layer of the terminal device can receive the second information. Furthermore, the access layer of the terminal device sends the service data (optionally, and the service's identification information) to the data collection network element through the access network device, thereby ensuring the accuracy and validity of the service data reported by the terminal device.

[0019] In one possible implementation, the target functional module is a second data collection client of the terminal device; the terminal device receives second information, including: the second data collection client of the terminal device receives second information from the access layer of the terminal device; the method further includes: the second data collection client sends the service data to the access layer of the terminal device according to the second information; the access layer of the terminal device sends the service data to the data collection network element. Optionally, the second data collection client also sends the service identification information to the access layer of the terminal device, and then the access layer of the terminal device also sends the service identification information to the data collection network element.

[0020] In this implementation, the target functional module is the second data collection client of the terminal device (i.e., another available data collection client besides the first data collection client). When the terminal device stops or pauses reporting data for the service, the second data collection client of the terminal device stores the service data (optionally, the second data collection client also stores the service's identification information). When the terminal device resumes reporting the service data, the second data collection client of the terminal device receives second information from the terminal device's access layer, thereby determining that the terminal device has resumed reporting the service data. At this time, the second data collection client reports the service data (optionally, and the service's identification information) to the data collection network element through the terminal device's access layer.

[0021] In one possible implementation, the target functional module is the memory in the terminal device; the terminal device receives second information, including: the first data collection client of the terminal device receives second information from the access layer or application layer of the terminal device; the method further includes: the first data client of the terminal device checks whether the memory in the terminal device has data for the service; if the memory in the terminal device has data for the service, the first data client of the terminal device obtains the data for the service from the memory in the terminal device; the first data client of the terminal device sends the data for the service to the data collection network element, optionally, the first data client of the terminal device also sends the identification information of the service to the data collection network element.

[0022] In this implementation, the target functional module is the terminal device's memory (e.g., permanent storage, local disk, etc.). When the terminal device stops reporting data for the service, the memory in the terminal device stores the service data (optionally, the memory in the terminal device also stores the service's identification information). When the terminal device resumes reporting the service data, the first data collection client of the terminal device receives second information from the terminal device's access layer, or the first data collection client restarts the received second information, thereby determining that the terminal device has resumed reporting the service data. Further, the first data collection client checks whether the memory in the terminal device stores the service data. If the memory contains the service data, the first data collection client can retrieve the service data from the memory and then report the service data (optionally, and the service's identification information) to the data collection network element.

[0023] In one possible implementation, the first data collection client stores the service data in the target functional module of the terminal device, including: the first data collection client sending the service data to the target functional module; optionally, the first data collection client also sending the service identification information to the target functional module; and the first data collection client shutting down or stopping.

[0024] With this implementation, before the first data collection client of the terminal device is closed or stopped, the first data collection client stores the collected service data (optionally, and the service identification information) in the target functional module of the terminal device, thereby avoiding the loss of service data and ensuring the integrity and reliability of the service data reported by the terminal device after recovery / startup.

[0025] In one possible implementation, the data for this service may include, but is not limited to, any one or more of the following: initial playback latency, throughput, and cache service level.

[0026] With this implementation method, data for one or more services of the terminal device (such as user service experience information) can be reported using the solution of this application embodiment, which can ensure the integrity and reliability of the reported service data.

[0027] Secondly, embodiments of this application provide a communication method. This method can be executed by a data collection network element on the network side, or by a module (such as a chip) corresponding to the data collection network element on the network side; this application does not limit this. The method specifically includes the following steps: the data collection network element generates data collection configuration information; wherein, the data collection configuration information includes first indication information, which instructs a first data collection client of the terminal device to send and store the service data of the terminal device in the target functional module of the terminal device when the first data collection client stops or closes; the data collection network element sends the data collection configuration information to the first data collection client of the terminal device, which instructs the terminal device to collect and report the service data.

[0028] In this application, the data collection network element generates data collection configuration information and sends it to the terminal device. This data collection configuration information instructs the terminal device to collect data for the service and report the service data to the data collection network element. The data collection configuration information also includes first instruction information. This first instruction information instructs the terminal device's first data collection client to send and store the terminal device's service data in the terminal device's target functional module when the first data collection client is closed or stopped. Therefore, this solution can prevent the loss of service data collected by the first data collection client, thereby ensuring the integrity and reliability of the service data reported by the terminal device to the data collection network element.

[0029] Optionally, the first instruction information further instructs the first data collection client to obtain the stored data of the service from the target functional module of the terminal device and report it after the data reporting of the service is restored.

[0030] In one possible implementation, the first instruction information is further used to instruct the first data collection client to check whether the memory in the terminal device stores the data of the service when restoring / starting the reporting of the service data. Through this implementation, if the first data collection client checks that the memory in the terminal device contains the data of the service, the first data collection client can effectively obtain the data of the service from the memory and then report the data of the service to the data collection network element.

[0031] In one possible implementation, the data collection network element generates data collection configuration information, including: the data collection network element receiving initial data collection configuration information from the application service provider, wherein the initial data collection configuration information includes second instruction information, which is used to instruct the terminal device to send and store the data of the service in the target functional module of the terminal device when the first data collection client stops or closes; the data collection network element generates the data collection configuration information according to the initial data collection configuration information.

[0032] It should be noted that the first instruction information in the above data collection configuration information can be generated from the second instruction information in the initial data collection configuration information.

[0033] Through this implementation, the data collection network element can receive initial data collection configuration information from the application service provider. The initial data collection configuration information includes second instruction information, which is used to instruct the terminal device to send and store the data of the service in the target functional module of the terminal device when the first data collection client is closed. The data collection network element can effectively generate data collection configuration information based on the initial data collection configuration information.

[0034] In one possible implementation, the initial data collection configuration information includes one or more of the following: data information to be collected, reporting rules, rules for external access, and security authentication information for external access.

[0035] In this implementation, the application service provider sends the initial data collection configuration information and sends the data collection configuration information generated from the initial data collection configuration information to the terminal device through the data collection network element, so as to ensure that the terminal device can effectively report service data to the data collection network element.

[0036] In one possible implementation, the target functional module of the terminal device is any one of the following: the access layer of the terminal device, the first data collection client of the terminal device, the second data collection client of the terminal device, and the memory in the terminal device.

[0037] Through this implementation, the network side instructs the terminal device to stop reporting service data to the data collection network element. When the first data collection client of the terminal device is closed or stopped, the first data collection client of the terminal device can be instructed to temporarily store the service data in different functional modules in the terminal device. That is, the different functional modules in the terminal device work together to temporarily store the service data, thereby avoiding the loss of service data and ensuring the integrity and reliability of the service data reported by the terminal device to the data collection network element.

[0038] In one possible implementation, the data for this service includes, but is not limited to, any one or more of the following: initial playback latency, throughput, and cache service level.

[0039] With this implementation method, data for one or more services of the terminal device (such as user service experience information) can be reported using the solution of this application embodiment, which can ensure the integrity and reliability of the reported service data.

[0040] Thirdly, this application provides a terminal device that can be used to implement the functions of the first data collection client, access layer, and target function module described above. The terminal device may include a communication unit and a processing unit; wherein the communication unit (i.e., executing the function of the first data collection client) is used to receive data collection configuration information, which instructs the terminal device to collect and report service data; receive first information, which notifies the terminal device to stop reporting the service data; the processing unit is used to store the service data in the target function module of the terminal device; the communication unit is also used to receive second information, which instructs the terminal device to resume / start reporting the service data.

[0041] In one possible implementation, when the communication unit receives data collection configuration information, it is specifically used to: receive data collection configuration information from the data collection network element.

[0042] For example, the first data collection client of the terminal device can receive the data collection configuration information from the data collection network element through the access network device.

[0043] In one possible implementation, the data collection configuration information includes first instruction information, which instructs the first data collection client to send and store the data of the service in the target functional module of the terminal device when the first data collection client stops or shuts down.

[0044] Optionally, the first indication information is further used to instruct the first data collection client to obtain the stored data of the service from the target function module of the terminal device and report it when restoring / starting the data reporting of the service.

[0045] In one possible implementation, the first indication information is further used to instruct the first data collection client, when restoring / starting the reporting of data for the service, to check whether the memory in the terminal device stores the data for the service. If the memory in the terminal device stores the data for the service, the first data collection client can effectively retrieve the data for the service from the memory and then report the data for the service to the data collection network element. Optionally, the first data collection client reports the identification information of the service.

[0046] In one possible implementation, the target functional module is the access layer of the terminal device; when the communication unit receives the second information, it can specifically be used to perform the functions of the access layer of the terminal device: receiving the second information; sending the data of the service (optionally, and the identification information of the service) to the data collection network element.

[0047] In one possible implementation, the target functional module is the second data collection client of the terminal device; when the communication unit receives the second information, it can specifically be used to perform the function of the second data collection client of the terminal device: receiving the second information from the access layer of the terminal device; sending the service data (optionally, and the identification information of the service) to the access layer of the terminal device according to the second information; the communication unit is also used to perform the function of the access layer of the terminal device: sending the service data (optionally, and the identification information of the service) to the data collection network element.

[0048] In one possible implementation, the target functional module is the memory in the terminal device; when the communication unit receives the second information, it can specifically be used to perform the function of the first data collection client of the terminal device: receiving the second information from the access layer or application layer of the terminal device; checking whether the memory in the terminal device stores the data of the service through the processing unit; if the memory in the terminal device stores the data of the service, obtaining the data of the service from the memory in the terminal device; and sending the data of the service (optionally, and the identification information of the service) to the data collection network element.

[0049] In one possible implementation, when the processing unit is stored in the target functional module of the terminal device, it can specifically be used to execute the function of the first data collection client of the terminal device: sending the data of the service (optionally, and the identification information of the service) to the target functional module; the first data collection client is closed or stopped.

[0050] In one possible implementation, the data for the service includes one or more of the following: initial playback latency, throughput, and cached service level.

[0051] Fourthly, this application provides a communication device, including a communication unit and a processing unit; wherein the processing unit is configured to generate data collection configuration information; wherein the data collection configuration information includes first instruction information, the first instruction information being configured to instruct a first data collection client of a terminal device to send and store the service data of the terminal device in the target functional module of the terminal device when the first data collection client stops or closes; the communication unit is configured to send the data collection configuration information to the first data collection client of the terminal device, the data collection configuration information being configured to instruct the terminal device to collect and report the service data.

[0052] Optionally, the first instruction information in the data collection configuration information further instructs the first data collection client to obtain the stored data of the service from the target function module of the terminal device and report it when restoring / starting the data reporting of the service.

[0053] In one possible implementation, the first indication information is further used to instruct the first data collection client to check whether the memory in the terminal device stores the data of the service when it resumes / starts reporting the data of the service.

[0054] In one possible implementation, the processing unit, when generating data collection configuration information, is specifically configured to: receive initial data collection configuration information from the application service provider through the communication unit, wherein the initial data collection configuration information includes second indication information, the second indication information being used to instruct the terminal device to send and store the data of the service in the target functional module of the terminal device when the first data collection client stops or closes; and generate the data collection configuration information according to the initial data collection configuration information.

[0055] In one possible implementation, the initial data collection configuration information includes one or more of the following: data information to be collected, reporting rules, rules for external access, and security authentication information for external access.

[0056] In one possible implementation, the target functional module of the terminal device is any one of the following: the access layer of the terminal device, the first data collection client of the terminal device, the second data collection client of the terminal device, and the memory in the terminal device.

[0057] In one possible implementation, the data for the service includes one or more of the following: initial playback latency, throughput, and cached service level.

[0058] Fifthly, this application provides a terminal device comprising: at least one processor and an interface circuit; the interface circuit being configured to provide input and / or output of a program or instruction to the at least one processor; the at least one processor being configured to execute the program or instruction to enable the communication device to implement the method provided in the first aspect or any of the possible implementations described above.

[0059] In a sixth aspect, this application provides a communication device comprising: at least one processor and an interface circuit; the interface circuit being configured to provide input and / or output of a program or instructions to the at least one processor; the at least one processor being configured to execute the program or instructions such that the communication device can implement the method provided in the second aspect or any of the possible implementations described above.

[0060] In a seventh aspect, embodiments of this application provide a computer storage medium storing a software program that, when read and executed by one or more processors, can implement the method provided in the first aspect or any of the possible implementations described above, or can implement the method provided in the second aspect or any of the possible implementations described above.

[0061] Eighthly, this application provides a computer program product containing instructions that, when executed on a computer, cause the computer to perform the method provided in the first aspect or any of the possible implementations described above, or to implement the method provided in the second aspect or any of the possible implementations described above.

[0062] Ninthly, this application provides a chip system including a processor for supporting a device in implementing the functions involved in the first aspect above, or for supporting a device in implementing the functions involved in the second aspect above.

[0063] In one possible design, the chip system further includes a memory for storing necessary program instructions and data. The chip system can be composed of chips or may include chips and other discrete devices.

[0064] In a tenth aspect, this application also provides a chip system, which includes a processor and an interface. The interface is used to acquire a program or instructions, and the processor is used to invoke the program or instructions to implement or support the device in implementing the functions involved in the first aspect, or to invoke the program or instructions to implement or support the device in implementing the functions involved in the second aspect, such as determining or processing at least one of the data and information involved in the above methods.

[0065] In one possible design, the chip system further includes a memory for storing necessary program instructions and data for the terminal device. The chip system can be composed of chips or may include chips and other discrete components.

[0066] The technical effects that can be achieved by the third aspect or any of the possible implementations described above can be referred to the description of the technical effects that can be achieved by the first aspect or any of the possible implementations described above; the technical effects that can be achieved by the fourth aspect or any of the possible implementations described above can be referred to the description of the technical effects that can be achieved by the second aspect or any of the possible implementations described above, and will not be repeated here. Attached Figure Description

[0067] Figure 1 This is a schematic diagram of a network architecture;

[0068] Figure 2 This is a schematic diagram of a data collection and reporting architecture.

[0069] Figure 3 This is a schematic diagram of a media streaming architecture;

[0070] Figure 4 This is a schematic diagram of an MSd architecture;

[0071] Figure 5 A flowchart illustrating a communication method provided in an embodiment of this application;

[0072] Figure 6 A flowchart illustrating the first embodiment provided in this application;

[0073] Figure 7 A flowchart illustrating the second embodiment provided in this application;

[0074] Figure 8 A flowchart illustrating the third embodiment provided in this application;

[0075] Figure 9 A flowchart illustrating the fourth embodiment provided in this application;

[0076] Figure 10 This is a schematic diagram of the structure of a terminal device provided in an embodiment of this application;

[0077] Figure 11 This is a schematic diagram of the structure of a terminal device provided in an embodiment of this application;

[0078] Figure 12 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0079] Figure 13 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0080] Figure 14 This is a schematic diagram of the structure of a chip device provided in an embodiment of this application. Detailed Implementation

[0081] This application provides a communication method and system, wherein the method and system are based on the same or similar technical concepts. Since the methods and systems solve problems in similar ways, their implementations can refer to each other, and repeated details will not be repeated.

[0082] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0083] Figure 1 This diagram illustrates a network architecture to which a communication method provided in an embodiment of this application applies. Figure 1 As shown, this network architecture can include an access network and a core network. Terminal devices access the data network (DN) through the access network and the core network.

[0084] Terminal devices can be user equipment (UE), mobile stations, mobile terminals, application clients, etc. They can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, etc. Terminal devices can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, urban air mobility vehicles (such as drones, helicopters, etc.), ships, robots, robotic arms, smart home devices, etc. The accompanying drawings and the following embodiments use a UE as an example of a terminal device for illustration; however, any subsequent mention of a UE can be replaced with a terminal device or other examples of terminal devices.

[0085] The access network is used to implement access-related functions. It can provide network access to authorized users in a specific area and determine transmission links of different qualities to transmit user data based on user level, service requirements, etc. The access network forwards control signals and user data between the UE and the core network. The access network can include access network equipment, which can be devices that provide access for the UE, and can include radio access network (RAN) equipment and wired access network equipment. RAN equipment is mainly responsible for functions such as radio resource management, quality of service (QoS) management, data compression, and encryption on the air interface side. RAN equipment can include various forms of base stations, such as macro base stations, micro base stations (also known as small stations), relay stations, access points, balloon stations, etc. In systems using different radio access technologies, the names of equipment with base station functions may differ. For example, in 5G systems, it is called RAN or next-generation Node base station (gNB), and in Long Term Evolution (LTE) systems, it is called evolved Node B (eNB or eNodeB).

[0086] Access network devices and UEs can be fixed or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; on water; or in the air on aircraft, balloons, and satellites. The embodiments of this application do not limit the application scenarios of the access network devices and UEs.

[0087] The core network is responsible for maintaining the subscription data of the mobile network and providing UEs with functions such as session management, mobility management, policy management, and security authentication. The core network includes, but is not limited to, one or more of the following network elements: application function (AF) network element, unified data management (UDM) network element, unified data repository (UDR) network element, policy control function (PCF) network element, session management function (SMF) network element, access and mobility management function (AMF) network element, network repository function (NRF) network element, authentication server function (AUSF) network element, network exposure function (NEF) network element, user plane function (UPF) network element, and network data analytics function (NWDAF) network element.

[0088] AMF network elements are primarily responsible for mobility management in mobile networks, such as user location updates, user network registration, and user handover.

[0089] SMF (Service Provider Function) network elements are primarily responsible for session management in mobile networks, such as session establishment, modification, and release. Specific functions include assigning Internet Protocol (IP) addresses to users and selecting a UPF (User Provider Function) to provide packet forwarding capabilities.

[0090] The UPF network element is mainly responsible for forwarding and receiving user data. It can receive user data from the data network and transmit it to the UE through the access network equipment; it can also receive user data from the UE through the access network equipment and forward it to the data network.

[0091] UDM network elements include functions such as managing contracted data and authorizing user access.

[0092] UDR network elements include functions for storing and retrieving data of various types, such as contract data, policy data, and application data.

[0093] NEF network elements are primarily used to support the opening of capabilities and events.

[0094] An AF (Application Provider) element conveys the application's requests to the network, such as QoS requirements or user state event subscriptions. AFs can be third-party functional entities or application services deployed by operators, such as the IP Multimedia Subsystem (IMS) voice call service.

[0095] The PCF network element primarily supports providing a unified policy framework to control network behavior, providing policy rules to control layer network functions, and is also responsible for acquiring user subscription information related to policy decisions. The PCF network element can provide policies, such as QoS policies and slice selection policies, to AMF and SMF network elements.

[0096] NRF network elements can be used to provide network element discovery functionality, providing network element information corresponding to the network element type based on requests from other network elements. NRF also provides network element management services, such as network element registration, updates, deregistration, and network element status subscription and push.

[0097] The AUSF network element is responsible for authenticating the UE and verifying its legitimacy.

[0098] NWDAF network elements have functions such as providing network data collection and analysis based on big data and artificial intelligence technologies.

[0099] A Data Network (DN) can be used to deploy various services, providing data and / or voice services to the User Equipment (UE). For example, a DN might be the private network of a smart factory. Sensors installed in the workshop can act as UEs, and a control server for these sensors is deployed within the DN. This control server provides services to the sensors. Sensors can communicate with the control server, receive instructions, and transmit collected sensor data back to the control server accordingly. Another example is a DN serving as the internal office network of a company. Employees' mobile phones or computers can act as UEs, accessing information and data resources within the company's internal office network.

[0100] Among them, AF network element, UDM network element, UDR network element, PCF network element, SMF network element, AMF network element, NRF network element, AUSF network element, NEF network element, UPF network element, and NWDAF network element can also be abbreviated as AF, UDM, UDR, PCF, SMF, AMF, NRF, AUSF, NEF, UPF, and NWDAF, respectively. Figure 1 As shown in the image.

[0101] Figure 1Nausf, Nnef, Nnrf, Namf, Npcf, Nsmf, Nudm, Nudr, Naf, and Nnwdaf are the service interfaces provided by AUSF, NEF, NRF, AMF, PCF, SMF, UDM, UDR, AF, and NWDAF, respectively, used to invoke the corresponding service operations. N1, N2, N3, N4, and N6 are interface sequence numbers, with the following meanings:

[0102] 1) N1: The interface between AMF and UE, which can be used to transmit non-access stratum (NAS) signaling (such as QoS rules from AMF) to UE.

[0103] 2) N2: The interface between the AMF and the access network equipment, which can be used to transmit radio bearer control information from the core network side to the access network equipment.

[0104] 3) N3: The interface between the access network device and the UPF, mainly used to transmit uplink and downlink user plane data between the access network device and the UPF.

[0105] 4) N4: The interface between SMF and UPF, which can be used to transmit information between the control plane and the user plane, including the distribution of forwarding rules, QoS rules, traffic statistics rules, etc. from the control plane to the user plane, as well as the reporting of information from the user plane.

[0106] 5) N6: The interface between UPF and DN, used to transmit uplink and downlink user data streams between UPF and DN.

[0107] It is understood that the aforementioned network element or function can be a network component in a hardware device, a software function running on dedicated hardware, or a virtualization function instantiated on a platform (e.g., a cloud platform). As one possible implementation method, the aforementioned network element or function can be implemented by a single device, multiple devices working together, or a functional module within a single device; this application does not specifically limit this.

[0108] Figure 2 This is a schematic diagram of an architecture for data collection and reporting in an embodiment of this application. UE-side data can be the quality of experience (QoE) of services within the UE or other data, which is not limited here. UE-side data can be data acquired by the UE. UE-side data can also be referred to as UE-side data, UE data, or UE data.

[0109] The following is about Figure 2 The various devices in the architecture shown are described.

[0110] The data collection AF (DCAF) receives configuration information from the application service provider (ASP) for configuring data collection and reporting functions. For example, the network side can interact with the DCAF through the provisioning AF in the ASP and enable the DCAF's data collection and reporting functions. The DCAF then generates data collection and reporting configuration information and sends it to the data collection client, enabling the client to collect data and report data collection reports based on the received configuration information. The DCAF can also receive data collection reports reported by the data collection client.

[0111] The data collection client may include: a direct data collection client (DDCC), an indirect data collection client (IDCC), or an application server (AS).

[0112] DCAF can process data in data collection reports, such as format conversion, data anonymization, and data aggregation, and send the processed UE-side data to the subscribing network element or third-party entity according to the subscription requests of other network elements or third-party entities.

[0113] The Direct Data Collection Client (DDCC) is the data collection function entity in the UE. The DDCC receives data collection and reporting configuration information from the DCAF via the R2 interface and performs data collection and reporting based on this configuration information. Figure 2 As shown, the DDCC can send the collected UE-side data to the DCAF via the R2 interface. The DDCC can be at the operating system level within the UE, meaning different applications may share a single DDCC; or each application may have its own dedicated DDCC, in which case the DDCC may be a functional entity integrated within the application. This application does not limit the deployment method of the DDCC; it depends on the functional implementation and application scenario.

[0114] The UE application (APP) can share relevant UE-side data with DDCC through the R7 interface.

[0115] Application Service Providers (ASPs) can receive UE-side data from the UE application via the R8 interface. The R8 interface is a pure application layer implementation. Within the ASP, an Indirect Data Collection Client (IDCC) can be considered to exist. The Service Activation AF sends data collection reports to the Data Center Activation AF (DCAF) via the R1 interface, and the IDCC sends the UE-side data collected at the application layer to the DCAF via the R3 interface. Prior to this, the IDCC also receives data collection and reporting configuration information from the DCAF via the R3 interface.

[0116] The application server (AS) can receive data collection and reporting configuration information from the DCAF through the R4 interface, then collect data according to the data collection and reporting configuration information, obtain a data collection report, and send the data collection report to the DCAF through the R4 interface. The data collection report includes access log information of the application server, etc.

[0117] NWDAF can subscribe to and receive UE-side data from DCAF via the R5 interface, and then analyze the UE-side data.

[0118] ASP may also obtain data collected by DCAF. For example, the Event Consumer AF in ASP can subscribe to the collected data from DCAF through the R6 interface, such as the application server's access log information, and receive the subscribed data information from DCAF.

[0119] In one implementation, the data collection and reporting architecture provided in this application is compatible with 5G media streaming or streaming media (5GMS) architecture, such as... Figure 3 As shown. For example, Figure 3 The 5GMS architecture shown can be used as Figure 2 The general data collection and reporting architecture shown is a specific instance of an architecture in the media field.

[0120] See Figure 3 As shown, this 5GMS architecture mainly includes 5GMS applications, 5GMS clients, 5GMS application function network elements (5GMS AFs), 5GMS application servers (5GMS ASs), and 5GMS application providers. Among these, 5GMS applications can also be referred to as 5GMS-Aware applications. (Reference) Figure 3 NEF and PCF are network elements in the 5G architecture. For definitions of 5G network elements, please refer to [link / reference needed]. Figure 1The architecture is shown. The 5GMS AF interacts with the 5G network through the N33 and N5 interfaces. 5GMS application providers and applications can be deployed by the application service providers themselves. When the 5GMS AF and 5GMS AS are in an external untrusted area, the M3 interface between them depends on a third-party provider. The 5GMS AF and 5GMS AS can be deployed by third-party application service providers or by the operator itself; this is not limited here.

[0121] Among them, 5GMS applications, 5GMS clients, 5GMS application function network elements, 5GMS application servers, and 5GMS application providers are respectively Figure 2 Specific examples of UE applications, DDCC, data collection AF, application servers, and application service providers in the 5GMS domain.

[0122] 5GMS applications can be considered as APPs on the UE side.

[0123] 5GMS Application Providers are primarily servers that provide content or services for applications (APPs).

[0124] 5GMS AF is a type of AF defined by 3GPP, designed to enable information exchange between external servers and the 3GPP network, such as capability opening or parameter provision. This 5GMS AF is a dedicated AF for media streaming services; in addition to the functions of the aforementioned data collection AF, it also supports media streaming service-related functions such as media streaming session management.

[0125] The 5GMS application server (5GMS AS) can be deployed and managed by a mobile network operator (MNO) or deployed by an external third party as a media streaming application server, similar to a content delivery network (CDN) server.

[0126] The 5GMS client includes a Media Session Handler (MSH) and a Media Stream Handler. The MSH primarily interacts with the 5GMS AF (Active Front-End) to create, control, and transmit media sessions. It also provides an application programming interface (API) for upper-layer 5GMS applications. The Media Stream Handler primarily transmits, encodes, decodes, and plays media streams with the 5GMS AS (Active Front-End), and provides APIs for upper-layer 5GMS applications and the MSH to enable media playback and session control. For downlink media streaming services, the MSH can also be called a media player (MP); for uplink media streaming services, it can be called a media streamer (MS).

[0127] Figure 4 This is a schematic diagram of the 5G downlink Media Streaming (5GMSd) architecture. This architecture represents a common application scenario where a user interface (UE) selects a media stream for playback via live streaming or video-on-demand. Figure 4 The 5GMSd architecture shown can be used as Figure 2 This illustrates another specific instance of the general data collection and reporting architecture in the media field. For the downlink media stream 5GMS architecture, to characterize it as a downlink media stream scenario, downlink symbols are added to each module. For example, 5GMS AF is called 5GMSd AF in downlink media stream services, and similarly, there is 5GMSd AS. All interface information is also processed similarly; for example, the M5 interface will be referred to as M5d. Here, "d" is short for downlink. Note that this overview uses the downlink media stream 5GMS architecture as an example; the following process and solution can also be applied to uplink streaming media 5GMS application scenarios.

[0128] The 5GMSd client includes various sub-functions, among which the Media Session Handling (MSH) function in the 5GMSd client supports some or all of the following sub-modules:

[0129] 1) Core Functions: Implements the core functions of session establishment, management, and control.

[0130] 2) Parameter Collection and Reporting Submodule: Configures parameter collection and reporting for the UE's media stream services, enabling the UE to collect and report parameters, that is, the UE reports the collected parameter information to 5GMSd AF.

[0131] 3) Consumption Collection & Reporting Submodule: Configures the consumption collection and reporting of the UE's media stream services, enabling the UE to collect and report its consumption information, that is, the UE reports the collected consumption information to 5GMSd AF.

[0132] 4) Network Assistance and QoS Adjustment Submodule: Interacts with the network via 5GMSd AF or directly with access network equipment to request policy adjustments (such as QoS adjustments) or network assistance from the network side.

[0133] The media stream processing function in the 5GMSd client (also known as the media player in the downlink direction) includes some or all of the following sub-modules: media data decryption sub-module, usage policy and logging sub-module, digital rights management (DRM) client sub-module, media data decoding sub-module, and media display and rendering sub-module.

[0134] The 5GMSd application provider creates a service provisioning session and sends relevant feature information, such as parameter collection and reporting feature information, to the 5GMSd AF. The 5GMSd AF determines the service access information (SAI) based on the parameter collection and reporting feature information sent by the 5GMSd application provider and returns the SAI or its index information to the 5GMSd application provider. Subsequently, when the 5GMSd application starts a media streaming service, it obtains the SAI from the 5GMSd application provider through the M8d interface. Then, the 5GMSd application sends the SAI to the Media Session Handling Function (MSH) through the M6d interface. The MSH then configures and executes the service based on the parameter collection and reporting configuration information in the SAI. Alternatively, when a 5GMSd application starts a media streaming service, the 5GMSd application obtains the index information of the SAI from the 5GMSd application provider through the M8d interface, and sends the index information of the SAI to the MSH through the M6d interface. The MSH obtains the SAI corresponding to the index information of the SAI from the 5GMSd AF through the M5d interface, and then the MSH collects and reports configuration information based on the parameters in the SAI to perform configuration and execution.

[0135] Specifically, MSH configures and executes based on the parameter collection and reporting configuration information in SAI, including: MSH configures the media player to collect parameters based on the parameter collection and reporting configuration information, and MSH reports the collected parameters to 5GMSd AF through the M5d interface based on the parameter collection and reporting configuration information.

[0136] It should be noted that the processing logic for uplink media streaming services is similar to that for downlink media streaming services, and will not be elaborated upon here. For uplink media streaming services, corresponding uplink symbols will be added, such as 5GMSu AF, 5GMSu AS, M4u, M5u, etc., which will not be elaborated upon here. Here, "u" is short for uplink.

[0137] Currently, data collection and reporting schemes mainly include those based on access network devices. This access network device-based scheme can be as follows: the data collection network element sends data collection and reporting configuration information to the access network device. Upon receiving this configuration information, the access network device sends it to the UE via a radio resource control (RRC) message. Specifically, the access network device sends the data collection and reporting configuration information from the data collection network element to the UE's Access Spectrum (AS). The AS layer of the terminal device then forwards this configuration information to the upper service layer, such as the MSH side. After receiving the configuration information, the UE collects data according to it and reports the collected data to the access network device in the form of a data report. The access network device then reports the data report back to the data collection network element. Data collection and reporting can include at least one of parameter collection and reporting, or usage collection and reporting. In this scheme, the access network device senses the data collection and reporting configuration information and sends it to the UE. It can also receive data reports from the UE and send them to the OAM network element, and the access network device senses that the UE is reporting the data report. However, the access network device cannot see the specific content of the data collection and reporting configuration information, nor can it see the specific content of the data report sent by the UE. That is, the data report is sent from the access network device to the data collection network element in the form of a container. Here, "sense the data collection and reporting configuration information" means that the access network device knows that the purpose of the data collection and reporting configuration information is to instruct the UE to perform data collection and reporting based on the access network device. "Sense the data report" means that the access network device knows that the data report contains UE data, and that the data report is generated by the UE after collecting data based on the data collection and reporting configuration information based on the access network device. Furthermore, the data collection network element can be the aforementioned 5GMS(d / u)AF, DCAF, or OAM, etc.

[0138] Currently, data collection and reporting solutions based on access network devices have the following problems:

[0139] (1) When network congestion occurs on the RAN side, the network side can instruct the UE side to suspend the reporting of service data via RRC signaling. However, although the UE's AS layer stops reporting service data at this time, the UE's application layer cannot perceive this suspension information. That is, the UE's application layer will continue to measure and report the UE's service data. Correspondingly, the UE's access AS layer will continue to receive service data from the UE's application layer during the service data suspension period on the UE side. However, due to the limited buffer of the AS layer, it will be difficult for the AS layer to store a large amount of UE application layer service data, resulting in the loss of service data.

[0140] (2) When the application on the UE is closed, the saved business data will also be deleted.

[0141] Therefore, this application provides a communication method and apparatus. The method includes: a first data collection client of a terminal device receiving data collection configuration information, which instructs the terminal device to collect service data and report the service data to a data collection network element through an access network device; the first data collection client receiving first information, which notifies the terminal device to stop or suspend reporting the service data; optionally, the first instruction information further instructs the terminal device to send the data in the target functional module to the data collection network element after resuming data reporting; the first data collection client storing the service data in the target functional module of the terminal device; and the terminal device receiving second information, which instructs the terminal device to resume / start reporting the service data. It can be seen that in this solution, when the first data collection client of the terminal device stops or suspends reporting the service data it has collected, it can work with the target functional module of the terminal device to store the service data, and when resuming / starting reporting the service data, it sends the service data stored in the target functional module to the data collection network element, thereby ensuring the integrity and reliability of the service data reported by the terminal device.

[0142] In this embodiment, the data collection network element is a network element used to determine configuration information, such as data collection configuration information. The data collection network element can be as described above. Figure 2 Data collection in AF or ASP, or the above Figure 3 5GMS AF or 5GMS application providers, or Figure 4The data collection network element in this application embodiment can be a 5GMSd AF or 5GMSd application provider, or a 5GMSu AF or 5GMSu application provider in uplink media streaming services, or a network element in future communications such as 6th generation (6G) networks that has the functions of the aforementioned data collection AF, ASP, 5GMS AF, 5GMS application provider, 5GMSd AF, 5GMSd application provider, 5GMSu AF, and 5GMSu application provider. Alternatively, the data collection network element in this application embodiment can also be an OAM network element, which can be set up independently or integrated into other network elements, such as integrated into the data collection AF, 5GMS AF, 5GMSd AF, 5GMSu AF, 5GMS application provider, 5GMSd application provider, or 5GMSu application provider, etc.

[0143] In this embodiment of the application, the data collection network element may be a data collection AF, 5GMS AF, 5GMSd AF, or 5GMSuAF, etc.

[0144] The technical solution of this application is described below with reference to specific embodiments.

[0145] Figure 5 This is a flowchart illustrating a communication method proposed in an embodiment of this application. This method can be executed by functional modules (such as a first data collection client, access layer, and target functional module) in a terminal device, or by the chip corresponding to the functional modules (such as the first data collection client, access layer, and target functional module) of the terminal device. Alternatively, this embodiment can also be implemented by a controller or control device connected to the functional modules (such as the first data collection client, access layer, and target functional module) of the terminal device. Furthermore, this application does not limit the specific form of the functional modules (such as the first data collection client, access layer, and target functional module) in the terminal device executing this embodiment. In addition, the execution object of the network-side method can be referred to the foregoing specific description of the execution object of the terminal device-side method, which will not be repeated here. Please refer to... Figure 5 The specific process of this method is as follows:

[0146] S501: The data collection network element receives initial data collection configuration information from the application service provider.

[0147] The initial data collection configuration information includes, but is not limited to, any one or more of the following:

[0148] The data to be collected, reporting rules, rules for external access, and security authentication information for external access.

[0149] Optionally, the initial data collection configuration information includes second instruction information, which instructs the terminal device to send service data to the target functional module of the terminal device when the first data collection client is closed. The target functional module can be determined by the data collection network element.

[0150] The first data collection client is located in the terminal device, and the first data collection client may be located in the application performing the business, or the first data collection client may be independent of the application performing the business. This application does not limit this.

[0151] Optionally, the data collection network element can be a standalone data collection network element DCAF, 5GMS AF, or OAM.

[0152] S502: The data collection network element generates data collection configuration information.

[0153] In one implementation, the data collection network element generates data collection configuration information, including: the data collection network element receiving initial data collection configuration information from an application service provider; and the data collection network element generating the data collection configuration information based on the initial data collection configuration information.

[0154] Optionally, the data collection configuration information includes first instruction information, which instructs the first data collection client to send and store the service data in the target functional module of the terminal device when the first data collection client stops or shuts down (or before stopping). The target functional module of the terminal device can be the access layer, the second data collection client, or the memory of the terminal device.

[0155] In this embodiment of the application, sending the service data to the target functional module can be assumed to mean caching or storing the service data in the target functional module.

[0156] Optionally, when the target functional module of the terminal device is a memory, the first indication information will also instruct the first data collection client to check whether the memory in the terminal device stores the data of the service when restoring / starting the data of the reporting service (including each time the first data collection client starts). If the first data collection client finds that the memory in the terminal device contains the data of the service, the first data collection client can obtain the data of the service from the memory, and then report the data of the service (optionally, and the identification information of the service) to the data collection network element.

[0157] In addition, the first instruction information in the data collection configuration information can be generated based on the second instruction information in the aforementioned initial data collection configuration information.

[0158] S503: The data collection network element sends the data collection configuration information to the terminal device.

[0159] For example, the data collection network element can send the data collection configuration information to the terminal device through the access network device.

[0160] S504: The first data collection client of the terminal device receives the data collection configuration information, which is used to instruct the terminal device to collect and report business data.

[0161] For example, the access layer of the terminal device receives data collection configuration information from the data collection network element through the access network device, and sends the data collection configuration information to the first data collection client at the upper layer.

[0162] For example, after the first data collection client of the terminal device receives the data collection configuration information, when the terminal device starts the application (APP) for performing the service, the first data collection client of the terminal device can collect the service data according to the data collection configuration information, and report the service data to the data collection network element through the access network device.

[0163] The data for this service may include, but is not limited to, any one or more of the following: initial playback latency, throughput, and caching service level.

[0164] S505: The first data collection client of the terminal device receives first information, which is used to notify the terminal device to stop reporting the data of the service.

[0165] As an example, if network congestion occurs, the access network device will send a reporting suspension indication to the access layer of the terminal device via an RRC message. This reporting suspension indication is used to notify the terminal device to stop sending the service data to the data collection network element. Further, the access layer of the terminal device sends a first message to the terminal device's first data collection client. This first message is used to notify the terminal device to stop (or suspend) reporting the service data. Correspondingly, the first data collection client receives the first message. After receiving the first message, the first data collection client will stop sending the service data to the terminal device's access layer, but will still continue to collect service data.

[0166] For example, this first information can be sent via an AT Command between the access layer and the upper layer.

[0167] S506: The first data collection client of this terminal device stores the service data in the target functional module of the terminal device.

[0168] In one possible implementation, the first data collection client sends the service's data to the target functional module (optionally, the first data collection client also sends the service's identification information to the target functional module), and further, the first data collection client is shut down. The shutdown of the first data collection client may be due to being closed or suspended, and the service's identification information may include service type, service application identifier, etc.

[0169] Therefore, this process occurs when (or before) the first data collection client of the terminal device is stopped or shut down. Optionally, the first data collection client, according to the first instruction information, sends the service data to the target functional module of the terminal device when or before the first data collection client is stopped or shut down.

[0170] For example, when performing step S506, the following implementation methods may be included but are not limited to:

[0171] In the first implementation, the target functional module is the access layer of the terminal device. The first data collection client stores the service data in the target functional module of the terminal device, including: the first data collection client sends the service data to the access layer of the terminal device. Optionally, the first data collection client sends the service identification information to the access layer of the terminal device, and then the first data collection client closes.

[0172] Therefore, when the terminal device stops reporting the data of the service and before the first data collection client is closed, the data of the service can be effectively stored through the access layer of the terminal device (optionally, the identification information of the service will also be stored), thereby avoiding the loss of the service data.

[0173] In the second implementation, the target functional module is the second data collection client of the terminal device. The first data collection client stores the service data in the target functional module of the terminal device. This includes: the first data collection client sending the service data to the second data collection client. Optionally, the first data collection client will also send the service identification information to the second data collection client, and then the first data collection client will close.

[0174] Therefore, when the terminal device stops reporting the data of the service and before the first data collection client is closed, the data of the service can be effectively stored through the second data collection client of the terminal device (optionally, the identification information of the service will also be stored), thereby avoiding the loss of the service data.

[0175] It should be noted that the second data collection client can also be an active functional module in the terminal device that is not easily stopped or turned off. The second data collection client can be used to collect data from other services (or business data from other applications).

[0176] In the third implementation, the target functional module is the memory in the terminal device. The first data collection client stores the service data in the target functional module of the terminal device, including: the first data collection client sends the service data to the memory in the terminal device. Optionally, the first data collection client also sends the service identification information to the memory in the terminal device, and then the first data collection client closes.

[0177] Optionally, the memory in the terminal device can be a permanent memory, the local disk of the terminal device, or other storage devices that are not easily lost. This application does not make any specific limitations on this.

[0178] Therefore, when the terminal device stops reporting the data of the service and before the first data collection client is closed, the data of the service can be effectively stored in the memory of the terminal device (optionally, the identification information of the service will also be stored), thereby avoiding the loss of the service data.

[0179] The first implementation method, the first implementation method, and the first implementation method described above can all be based on the situation that the first data collection client of the terminal device is easily stopped or shut down. Therefore, when the first data collection client is shut down or before it is shut down, it sends the data of the service it has collected or stored (optionally, and the identification information of the service) to the target functional module in the terminal device, and the target functional module stores it, thereby effectively avoiding the loss of the service data.

[0180] In this embodiment of the application, if the first data collection client of the terminal device is not easily stopped or closed, after receiving the first information, the first data collection client of the terminal device can continue to store (i.e. cache) the data of the service (i.e., the target functional module of the terminal device is the first data collection client).

[0181] S507: The terminal device receives second information, which instructs the terminal device to resume / start sending the data of the service to the data collection network element.

[0182] As an example, if normal communication is restored on the network side, the access network device will send a reporting instruction to the access layer of the terminal device via an RRC message. This reporting instruction is used to notify the terminal device to resume sending data for the service to the data collection network element, or to resume service data reporting. Further, the access layer of the terminal device sends a second message to the target functional module. This second message instructs the terminal device to resume / start reporting data for the service, and the target functional module receives this second message. For example, this second message can be sent from the terminal device's access layer to the upper service layer via an AT Command.

[0183] For example, based on the several implementations of step S506 above, the execution of step S507 specifically includes the following:

[0184] Based on the first implementation method described above (the target functional module is the access layer of the terminal device), the terminal device receives the second information, including: the access layer of the terminal device receives the second information.

[0185] After receiving the second information, the access layer of the terminal device further includes: sending the data of the service to the data collection network element. Optionally, the access layer of the terminal device also sends the identification information of the service to the data collection network element.

[0186] Optionally, the access layer of the terminal device sends the service data to the access network device. Optionally, the access layer of the terminal device also sends the service identification information to the access network device. Correspondingly, the access network device sends the service data to the data collection network element. Optionally, the access network device also sends the service identification information to the data collection network element.

[0187] Based on the second implementation method described above (the target functional module is the second data collection client of the terminal device), the terminal device receives the second information, including: the second data collection client of the terminal device receives the second information from the access layer of the terminal device.

[0188] After receiving the second information, the second data collection client of the terminal device further includes: the second data collection client sending the service data to the access layer of the terminal device according to the second information; optionally, the second data collection client also sending the service identification information to the access layer of the terminal device; the access layer of the terminal device sending the service data to the data collection network element; optionally, the access layer of the terminal device also sending the service identification information to the data collection network element.

[0189] Optionally, the second data collection client sends the service data to the access layer of the terminal device. Optionally, the second data collection client also sends the service identification information to the access layer of the terminal device. Then, the access layer of the terminal device sends the service data to the access network device. Optionally, the access layer of the terminal device also sends the service identification information to the access network device. Finally, the access network device sends the service data to the data collection network element. Optionally, the access network device also sends the service identification information to the data collection network element.

[0190] Based on the third implementation method described above (the target functional module is the memory in the terminal device), the terminal device receives the second information, including:

[0191] In one possible implementation, the first data collection client of the terminal device receives second information from the access layer or application layer of the terminal device.

[0192] After receiving the second information, the first data collection client of the terminal device further includes: checking whether the memory of the terminal device contains data for the service; if the memory of the terminal device contains data for the service, the first data client of the terminal device obtains the data for the service from the memory of the terminal device; the first data client of the terminal device sends the data for the service to the data collection network element, and optionally, the first data collection client also sends the identification information of the service to the data collection network element.

[0193] Optionally, the first data collection client sends the service data to the access layer of the terminal device. Optionally, the first data collection client also sends the service identification information to the access layer of the terminal device. Then, the access layer of the terminal device sends the service data to the access network device. Optionally, the access layer of the terminal device also sends the service identification information to the access network device. Finally, the access network device sends the service data to the data collection network element. Optionally, the access network device also sends the service identification information to the data collection network element.

[0194] It should be noted that if the first data collection client of the terminal device is not easily stopped or shut down, it can continue to store the service data after receiving the first information (i.e., the target functional module of the terminal device is the first data collection client). In this case, the target functional module of the terminal device receives the second information, including: the first data collection client of the terminal device receiving second information from the access layer of the terminal device; furthermore, the first data collection client of the terminal device sending the service data to the access network device through the access layer of the terminal device; and finally, the access network device sending the service data to the data collection network element.

[0195] It should be understood that, in the embodiments of this application, the access layer of the terminal device can serve as a functional module for direct communication between the terminal device and external devices or network elements. Therefore, other functional modules in the terminal device (such as the first data collection client, memory, second data collection client, etc.) can interact or communicate with external devices or network elements through the access layer of the terminal device. Furthermore, "storage" in the embodiments of this application can be understood as "caching," and this application does not impose specific limitations on it.

[0196] In summary, this application provides a communication method and apparatus. The method includes: a first data collection client of a terminal device receiving data collection configuration information, which instructs the terminal device to collect and report service data; the first data collection client receiving first information, which notifies the terminal device to stop reporting the service data; the first data collection client storing the service data in a target functional module of the terminal device; and the terminal device receiving second information, which instructs the terminal device to resume / start reporting the service data. It can be seen that in this solution, when the first data collection client of the terminal device stops reporting the collected service data, it can coordinate with the target functional module of the terminal device to store the service data, thereby ensuring the integrity and reliability of the service data reported by the terminal device.

[0197] The following specific embodiments further illustrate the communication method proposed in this application.

[0198] Example 1

[0199] In this embodiment, the first data collection client of the terminal device (such as UE1) is associated with the first application (i.e., the first APP) of the UE1. The first data collection client may be located inside the first APP, or the first data collection client may be bound to at least one APP of the UE1, and the first APP is included in the at least one APP. Therefore, when the first APP is closed, the first data collection client will also be closed.

[0200] When UE1 reports the Quality of Experience (QoE) report (corresponding service data) of the first application to the network side, if network congestion occurs on the base station side, the access network RAN ​​device will instruct UE1 to suspend the reporting of the QoE report of the first application. UE1 will cache the QoE report of the first application in UE1's first data collection client. When UE1's first application is closed (or before UE1's first application is closed), that is, when or before the first data collection client is closed, UE1's first data collection client will send the cached QoE report of the first application to UE1's access layer (i.e., AS layer), where UE1's access layer will cache and report the QoE report of the first application. (Reference) Figure 6 As shown, the specific process of the method in this embodiment is as follows:

[0201] S601: The application provider sends initial data collection configuration information to the data collection network element.

[0202] Accordingly, the data collection network element receives the initial data collection configuration information, which includes one or more of the following: data information to be collected, reporting rules, rules for external access, and security authentication information for external access.

[0203] Optionally, the data collection network element (network-side network element) can be an independent data collection network element (such as DC-AF, or 5GMS AF, or 5GMSd AF, or 5GMSu AF) or OAM.

[0204] Optionally, the initial data collection configuration information may also include second instruction information, which is used to instruct the first data collection client of UE1 to send the QoE report of the first APP to the access layer of UE1 when the first APP of UE1 is closed (or before the first APP of UE1 is closed), that is, when or before the first data collection client is closed.

[0205] S602: The data collection network element sends data collection configuration information to the first data collection client of UE1.

[0206] Accordingly, the first data collection client of UE1 receives the data collection configuration information. This data collection configuration information is generated by the data collection network element based on the aforementioned initial data collection configuration information, and it is used to instruct UE1 to report the QoE of UE1's first application to the data collection network element after the first application is started.

[0207] For example, the data collection configuration information can be sent from the data collection network element to the access network device side. The access network device sends the data collection configuration information to the access layer of UE1 through an RRC message, and then the access layer of UE1 sends the data collection configuration information to the first data collection client of UE1.

[0208] Optionally, the data collection configuration information may also include first indication information. If the initial data collection configuration information also includes second indication information, the first indication information may be generated based on the second indication information in the initial data collection configuration information. The first indication information is used to instruct the first data collection client of UE1 to send the cached QoE report of the first APP to the access layer of UE1 when the first APP is closed (or before the first APP is closed), or when the first data collection client of UE1 is closed or before it is closed, if there is a cached QoE report of the first APP.

[0209] S603: The first application of UE1 starts running.

[0210] After the first application of UE1 starts running, the first data collection client of UE1 starts collecting the QoE of the first application, obtains the QoE report of the first application, and reports the QoE report according to the data collection configuration information.

[0211] The QoE of the first APP may include, but is not limited to, any one or more of the following: initial playback latency, throughput, and cache level information.

[0212] Optionally, step S603 can also occur before step S602, that is, after the first APP of UE1 starts running, it obtains data collection configuration information from the data collection network element and performs QoE report collection and reporting based on the data collection configuration information.

[0213] S604: The access network RAN ​​device instructs the access layer of UE1 to suspend the reporting of QoE reports for the first APP.

[0214] For example, when network congestion occurs at the base station, the RAN device sends a pause indication message to the access layer of UE1 via an RRC message. This pause indication message instructs UE1 to pause / stop the data collection network element from reporting the QoE report of the first APP. Accordingly, the access layer of UE1 receives the pause indication message.

[0215] S605: The access layer of UE1 sends the first information to the first data collection client of UE1.

[0216] Accordingly, the first data collection client of UE1 receives the first information, which is used to notify UE1 not to report the QoE report of the first APP to the data collection network element.

[0217] Optionally, the first information can be sent from the access layer of UE1 to the upper layer via AT Command. That is, the access layer of UE1 sends the first information to the first data collection client of UE1 via AT Command, thereby instructing UE1 not to report QoE reports to the data collection network element.

[0218] It should be understood that the first data collection client of UE1 will continue to collect service data based on the first information, but will suspend reporting to the data collection network element, that is, it will only collect service data and not report it.

[0219] S606: The first data collection client of UE1 caches the QoE report of the first APP.

[0220] Based on the above step S605, after the first data collection client of UE1 learns that the reporting of the QoE report of the first APP is suspended, it no longer sends the QoE report of the first APP to the access layer of UE1, but caches the QoE report of the first APP.

[0221] S607: The first collection client of UE1 determines that the first APP will be closed or cleared in the background.

[0222] Step S607 is an optional step.

[0223] For example, when the first data collection client caches the QoE report of the first APP, the first APP bound to the first data collection client may be closed or cleaned up in the background for some reason, such as user operation causing the first APP to be closed, or UE1 performing cleanup causing the first APP to be closed.

[0224] Since closing or cleaning up the first app in UE1 will also cause the first data collection client in UE1 to close and stop caching, the first data collection client in UE1 will be notified that the first app is about to be closed or cleaned up.

[0225] S608: The first data collection client of UE1 sends the QoE report of the first APP to the access layer of UE1.

[0226] Optionally, the first data collection client of UE1 performs this step S608 according to the first instruction information.

[0227] If the situation described in step S607 exists, when the first APP of UE1 may be closed or cleaned up, or when the first data collection client of UE1 is closed or before being closed, the initial data collection configuration information in step S601 may also include second instruction information, and the data collection configuration information in step S602 may also include first instruction information.

[0228] Correspondingly, the access layer of UE1 receives the QoE report of the first APP.

[0229] S609: UE1's access layer caches the QoE report of the first APP.

[0230] The access layer of UE1 will cache the QoE report of the first APP as much as possible according to its own caching capacity and discard the redundant QoE report. The redundant QoE report may be a random QoE report, the earliest collected QoE report, or the latest collected QoE report. This application does not make specific limitations on this.

[0231] S610: The access network device instructs the access layer of UE1 to resume reporting of QoE measurement results (i.e., send the second information).

[0232] For example, when the network on the base station side returns to normal (i.e., no congestion or congestion recovery), the access network RAN ​​device sends recovery indication information (i.e., second information) to the access layer of UE1. This recovery indication information is used to instruct UE1 to resume / start reporting QoE reports to the data collection network element. Accordingly, the access layer of UE1 receives the recovery indication information.

[0233] S611: The access layer of UE1 sends the cached QoE report of the first APP to the data collection network element through the RAN device.

[0234] For example, the access layer of UE1 first sends the cached QoE report of the first APP to the RAN device, and the RAN device then sends the QoE report of the first APP to the data collection network element.

[0235] Upon receiving the QoE report from the first application, the data collection network element can send it to a third party for processing to optimize the network. Subsequent steps for this data collection network element can be referenced from existing technologies and will not be described in detail here.

[0236] In this implementation, if network congestion occurs on the base station side during the collection and reporting of QoE reports for the first application by the first data collection client of UE1, causing a suspension of QoE reporting for the first application, the first data collection client of UE1 will cache the QoE reports for the first application. However, if the first application bound to the first data collection client of UE1 is closed or cleared in the background, the first data collection client of UE1 will also be closed. Therefore, when the first data collection client of UE1 is closed or cleared (or before it is closed or cleared), it sends the cached QoE reports for the first application to the access layer (AS layer) of UE1. The access layer of UE1 caches the QoE reports for the first application and reports the QoE reports for the first application to the data collection network element on the network side after QoE reporting resumes, thereby ensuring the integrity and reliability of the reported QoE reports for the first application as much as possible.

[0237] Example 2

[0238] In this second embodiment, the first data collection client of the terminal device (such as UE1) is associated with the first application (i.e., the first APP) of the UE1. The first data collection client may be located inside the first APP, or the first data collection client may be bound to at least one APP of the UE1, and the first APP is included in the at least one APP. Therefore, when the first APP is closed, the first data collection client will also be closed.

[0239] When UE1 reports the Quality of Experience (QoE) report (corresponding service data) of the first application to the network side, if network congestion occurs on the base station side, the access network (RAN) device will instruct UE1 to suspend reporting the QoE report of the first application. UE1 caches the QoE report of the first application in its first data collection client. When UE1's first application is closed (or before UE1's first application is closed), or when UE1's first data collection client is closed or before it is closed, UE1's first data collection client sends the cached QoE report of the first application (optionally, along with the identification information of the first application) to other active data collection clients (i.e., available data collection clients) in UE1, such as UE1's second data collection client. The second data collection client of UE1 then caches and reports the QoE report of the first application (optionally, along with the identification information of the first application). (Reference) Figure 7 As shown, the specific process of the method in this second embodiment is as follows:

[0240] S701: The application provider sends initial data collection configuration information to the data collection network element.

[0241] Accordingly, the data collection network element receives the initial data collection configuration information, which includes one or more of the following: data information to be collected, reporting rules, rules for external access, and security authentication information for external access.

[0242] Optionally, the data collection network element (network-side network element) can be an independent data collection network element (such as DC-AF, or 5GMS AF, or 5GMSd AF, or 5GMSu AF) or OAM.

[0243] Optionally, the initial data collection configuration information may also include second instruction information, which is used to instruct the first data collection client of UE1 to send the QoE report of the first APP to the second data collection client of UE1 when the first APP of UE1 is closed (or before the first APP of UE1 is closed), or when or before the first data collection client is closed. Optionally, the first data collection client of UE1 may also send the identification information of the first APP to the second data collection client of UE1.

[0244] The identification information of the first APP can be the ID of the first APP or the service type of the first APP, etc.

[0245] S702: The data collection network element sends data collection configuration information to the first data collection client of UE1.

[0246] Accordingly, the first data collection client of UE1 receives the data collection configuration information. This data collection configuration information is generated by the data collection network element based on the aforementioned initial data collection configuration information, and it is used to instruct UE1 to report the QoE of UE1's first APP to the data collection network element after the first APP is activated.

[0247] For example, the data collection configuration information can be sent from the data collection network element to the access network device side. The access network device sends the data collection configuration information to the access layer of UE1 via RRC message, and then the access layer of UE1 sends the data collection configuration information to the first data collection client of UE1 via AT Command.

[0248] Optionally, the data collection configuration information may also include first indication information. If the initial data collection configuration information may also include second indication information, the first indication information may be generated based on the second indication information in the initial data collection configuration information. The first indication information is used to instruct the first data collection client of UE1 to send the cached QoE report of the first APP (optionally, and the identification information of the first APP) to the second data collection client of UE1 when the first APP is closed (or before the first APP is closed), or when the first data client of UE1 is closed or before it is closed, if there is a cached QoE report of the first APP.

[0249] It should be noted that UE1 may include multiple data collection clients. Different applications (APPs) may correspond to different data collection clients. That is, one APP corresponds to one data collection client, or multiple APPs correspond to one data collection client. This application does not make specific limitations in this regard.

[0250] Therefore, in step S702, the data collection network element can send the data collection configuration information to different data collection clients in UE1 respectively. This embodiment takes the first APP and the first data collection client in UE1 as examples to describe the method of this application in detail. Therefore, other APPs and data collection clients in UE1 or other UEs can be executed by referring to the first APP and the first data collection client in UE1 or the UE1 method. It will not be described in detail here.

[0251] S703: The first application of UE1 starts running.

[0252] After the first application of UE1 starts running, the first data collection client of UE1 starts collecting the QoE of the first application, obtains the QoE report of the first application, and reports the QoE report according to the data collection configuration information.

[0253] The QoE of the first APP may include, but is not limited to, any one or more of the following: initial playback latency, throughput, and cache level information.

[0254] Optionally, step S703 can be performed before step S702, that is, after the first APP of UE1 starts running, it obtains data collection configuration information from the data collection network element and performs QoE report collection and reporting based on the data collection configuration information.

[0255] S704: The access network RAN ​​device instructs the access layer of UE1 to suspend the reporting of QoE reports for the first APP.

[0256] For example, when network congestion occurs at the base station, the RAN device sends a pause indication message to the access layer of UE1 via an RRC message. This pause indication message instructs UE1 to pause or stop reporting QoE reports to the data collection network element. Accordingly, the access layer of UE1 receives this pause indication message.

[0257] S705: The access layer of UE1 sends the first information to the first data collection client of UE1.

[0258] Accordingly, the first data collection client of UE1 receives the first information, which is used to notify UE1 to suspend or stop reporting QoE reports to the data collection network element.

[0259] Optionally, the first information can be sent from the access layer of UE1 to the upper layer of UE1 via AT Command. That is, the access layer of UE1 sends the first information to the first data collection client of UE1 via AT Command, thereby instructing UE1 not to report QoE reports to the data collection network element.

[0260] It should be understood that the first data collection client of UE1 will continue to collect service data based on the first information, but will suspend reporting to the data collection network element, that is, it will only collect service data and not report it.

[0261] S706: The first data collection client of UE1 caches the QoE report of the first APP.

[0262] Based on the above step S705, after the first data collection client of UE1 learns that the reporting of the QoE report of the first APP is suspended, it no longer sends the QoE report of the first APP to the access layer of UE1, but caches the QoE report of the first APP.

[0263] S707: The first collection client of UE1 determines that the first APP will be closed or cleared in the background.

[0264] Step S707 is an optional step.

[0265] For example, when the first data collection client caches the QoE report of the first APP, the first APP bound to the first data collection client may be closed or cleaned up in the background for some reason, such as the first APP being closed due to user operation, or the first APP being closed when UE1 performs cleanup.

[0266] Since closing or cleaning up the first app in UE1 will also cause the first data collection client in UE1 to close and stop caching, the first data collection client in UE1 will be notified that the first app is about to be closed or cleaned up.

[0267] The above steps S701-S707 are the same as those described above. Figure 6 Steps S601-S607 correspond one-to-one and can be referenced together.

[0268] S708: The first data collection client of UE1 sends the QoE report of the first APP to the second data collection client of UE1.

[0269] Optionally, the first data collection client of UE1 performs this step S708 according to the first instruction information.

[0270] Optionally, the first data collection client of the UE1 may also send the identification information of the first APP to the second data collection client of the UE1.

[0271] If the situation described in step S707 exists, i.e., when the first APP of UE1 may be closed or cleaned up, or when / before the first data collection client of UE1 is closed, then the initial data collection configuration information in step S701 also includes second indication information, and the data collection configuration information in step S702 also includes first indication information.

[0272] Accordingly, the second data collection client of UE1 receives the QoE report of the first APP (optionally, as well as the identification information of the first APP).

[0273] S709: The second data collection client of UE1 caches the QoE report of the first APP.

[0274] Optionally, the second data collection client of the UE1 may also cache the identification information of the first APP.

[0275] S710: The access network device instructs the access layer of UE1 to resume reporting of QoE measurement results.

[0276] For example, when the network on the base station side returns to normal (i.e., no congestion or congestion recovery), the access network RAN ​​device sends a recovery indication message to the access layer of UE1 via an RRC message. This recovery indication message is used to instruct UE1 to resume reporting QoE reports to the data collection network element. Accordingly, the access layer of UE1 receives the recovery indication message.

[0277] S711: The access layer of UE1 sends second information to the second data collection client of UE1.

[0278] Correspondingly, the second data collection client of UE1 receives the second information, which is used to instruct UE1 to report a QoE report (optionally, and the identification information of the corresponding APP) to the data collection network element.

[0279] S712: The second data collection client of UE1 sends the QoE report of the first APP to the access layer of UE1.

[0280] Optionally, the second data collection client of the UE1 also sends the identification information of the first APP to the access layer of the UE1.

[0281] S713: The access layer of UE1 sends the QoE report of the first APP to the data collection network element through the RAN equipment.

[0282] Optionally, the access layer of UE1 may also send the identification information of the first APP to the data collection network element through the RAN device.

[0283] For example, the access layer of UE1 first sends the QoE report of the first APP (optionally, and the identification information of the first APP) to the RAN device, and the RAN device then sends the QoE report of the first APP (optionally, and the identification information of the first APP) to the data collection network element.

[0284] After receiving the QoE report (optionally, along with the identification information of the first application) from the data collection network element, it can send it to a third party for processing to optimize the network. Subsequent steps of the data collection network element can be found in existing technologies and will not be described in detail here.

[0285] In this second implementation, if network congestion occurs on the base station side during the process of collecting and reporting the QoE report of the first APP, causing the reporting of the QoE report of the first APP to be suspended, the first data collection client of UE1 will cache the QoE report of the first APP. However, if the first APP bound to the first data collection client of UE1 is closed or cleared in the background, the first data collection client of UE1 will also be closed. Therefore, when the first data collection client of UE1 is shut down or cleared (or before it is shut down or cleared), it sends the cached QoE report of the first APP (optionally, and the identification information of the first APP) to other active data collection clients of UE1 (i.e. other available data collection clients in UE1), such as the second data collection client in UE1. The second data collection client caches the QoE report of the first APP (optionally, and the identification information of the first APP) and reports the QoE report of the first APP (optionally, and the identification information of the first APP) to the data collection network element on the network side, thereby ensuring the integrity and reliability of the reported QoE report of the first APP as much as possible.

[0286] Example 3

[0287] In this third embodiment, the first data collection client of the terminal device (such as UE1) is associated with the first application (i.e., the first APP) of the UE1. The first data collection client may be located inside the first APP, or the first data collection client may be bound to at least one APP of UE1, and the first APP is included in the at least one APP. Therefore, when the first APP is closed, the first data collection client will also be closed.

[0288] When UE1 reports the Quality of Experience (QoE) report (corresponding service data) of the first application to the network side, if network congestion occurs on the base station side, the access network RAN ​​device will instruct UE1 to suspend the reporting of the QoE report of the first application via RRC message. UE1 caches the QoE report of the first application in UE1's first data collection client. When UE1's first application is closed (or before UE1's first application is closed), or when UE1's first data collection client is closed or before it is closed, UE1's first data collection client sends the cached QoE report of the first application (optionally, along with the identification information of the first application) to the memory (e.g., permanent storage, local disk, etc.) in UE1. The memory in UE1 caches the report and, when service data collection and reporting resumes or restarts, reports the QoE report of the first application (optionally, along with the identification information of the first application). Figure 8 As shown, the specific process of the method in this embodiment three is as follows:

[0289] S801: The application provider sends initial data collection configuration information to the data collection network element.

[0290] Accordingly, the data collection network element receives the initial data collection configuration information, which includes one or more of the following: data information to be collected, reporting rules, rules for external access, and security authentication information for external access.

[0291] Optionally, the data collection network element (network-side network element) can be an independent data collection network element (such as DC-AF, or 5GMS AF, or 5GMSd AF, or 5GMSu AF) or OAM.

[0292] Optionally, the initial data collection configuration information may also include second instruction information, which is used to instruct the first data collection client of UE1 to send the QoE report of the first APP to the memory in UE1 when the first APP of UE1 is closed (or before the first APP of UE1 is closed), or when or before the first data collection client is closed.

[0293] Optionally, the first data collection client of the UE1 may also send the identification information of the first APP to the memory in the UE1.

[0294] Optionally, the second instruction information is further used to instruct the first data collection client of UE1 to actively check whether the memory contains a QoE report to be sent when service data collection and reporting is initiated. If it exists, the first data collection client of UE1 retrieves the QoE report to be sent from the memory of UE1 and sends it.

[0295] The identification information of the first APP can be the ID of the first APP or the service type of the first APP, etc.

[0296] S802: The data collection network element sends data collection configuration information to the first data collection client of UE1.

[0297] Accordingly, the first data collection client of UE1 receives the data collection configuration information. This data collection configuration information is generated by the data collection network element based on the aforementioned initial data collection configuration information, and it is used to instruct UE1 to report the QoE of UE1's first APP to the data collection network element after the first APP is activated.

[0298] For example, the data collection configuration information can be sent to the access network device through the data collection network element. The access network device then sends the data collection configuration information to the access layer of UE1 via an RRC message, and the access layer of UE1 then sends the data collection configuration information to the first data collection client of UE1.

[0299] Optionally, the data collection configuration information may also include first indication information. If the initial data collection configuration information may also include second indication information, the first indication information may be generated based on the second indication information in the initial data collection configuration information. The first indication information is used to instruct the first data collection client of UE1 to send the stored QoE report of the first APP (optionally, and the identification information of the first APP) to the memory in UE1 when the first APP is closed (or before the first APP is closed), or when the first data collection client of UE1 is closed or before it is closed, if the QoE report of the first APP is stored.

[0300] Optionally, the first instruction information may also instruct the first data collection client of UE1 to check whether the memory in UE1 stores the data of the service when the service is started or when the data collection and reporting of the service begins. If the first data collection client of UE1 checks that the memory of UE1 contains the data of the service, the first data collection client of UE1 can obtain the data of the service from the memory of UE1 and then report the data of the service (optionally, and the identification information of the service) to the data collection network element.

[0301] It should be noted that UE1 may include multiple data collection clients. Different applications (APPs) may correspond to different data collection clients. That is, one APP corresponds to one data collection client, or multiple APPs correspond to one data collection client. This application does not make specific limitations in this regard.

[0302] Therefore, in step S802, the data collection network element can send the data collection configuration information to different data collection clients in UE1 respectively. This embodiment takes the first APP and the first data collection client in UE1 as examples to describe the method of this application in detail. Therefore, other APPs and data collection clients in UE1 or other UEs can be executed by referring to the first APP and the first data collection client in UE1 or the UE1 method. It will not be described in detail here.

[0303] S803: The first application of UE1 starts running.

[0304] After the first application of UE1 starts running, the first data collection client of UE1 starts collecting the QoE of the first application, obtains the QoE report of the first application, and reports the QoE report according to the data collection configuration information.

[0305] Optionally, the QoE of the first APP may include, but is not limited to, any one or more of the following: such as initial playback latency, throughput, and cache level information.

[0306] Optionally, step S803 can be performed before step S802, that is, after the first APP of UE1 starts running, it obtains data collection configuration information from the data collection network element and performs QoE report collection and reporting based on the data collection configuration information.

[0307] S804: The access network RAN ​​device instructs the access layer of UE1 to suspend the reporting of QoE reports for the first APP.

[0308] For example, when network congestion occurs at the base station, the access network RAN ​​device sends a pause indication message to the access layer of UE1 via an RRC message. This pause indication message is used to instruct UE1 to pause / stop reporting QoE reports to the data collection network element. Accordingly, the access layer of UE1 receives the pause indication message.

[0309] S805: The access layer of UE1 sends the first information to the first data collection client of UE1.

[0310] Accordingly, the first data collection client of UE1 receives the first information, which is used to notify UE1 to suspend or stop reporting QoE reports to the data collection network element.

[0311] Optionally, the first information can be sent from the access layer of UE1 to the upper layer of UE1 via AT Command. That is, the access layer of UE1 sends the first information to the first data collection client of UE1 via AT Command, thereby instructing UE1 not to report QoE reports to the data collection network element.

[0312] S806: The first data collection client of UE1 caches the QoE report of the first APP.

[0313] Based on the above step S805, after the first data collection client of UE1 learns that the reporting of the QoE report of the first APP is suspended, it no longer sends the QoE report of the first APP to the access layer of UE1, but caches the QoE report of the first APP.

[0314] S807: The first collection client of UE1 determines that the first APP will be closed or cleared in the background.

[0315] Step S807 is an optional step.

[0316] For example, when the first data collection client caches the QoE report of the first APP, the first APP bound to the first data collection client may be closed or cleaned up in the background for some reason, such as the first APP being closed due to user operation, or the first APP being closed when UE1 performs cleanup.

[0317] Since closing or cleaning up the first app in UE1 will also cause the first data collection client in UE1 to close and stop caching, the first data collection client in UE1 will be notified that it is about to be closed or cleaned up.

[0318] The above steps S801-S807 and the above Figure 6 Steps S601-S607 correspond one-to-one with those described above. Figure 7 Steps S701-S707 correspond one-to-one and can be referenced together.

[0319] S808: The first data collection client of UE1 sends the QoE report of the first APP to the memory in UE1.

[0320] Optionally, the first data collection client of UE1 performs this step S808 according to the first instruction information.

[0321] Optionally, the first data collection client of the UE1 may also send the identification information of the first APP to the memory in the UE1.

[0322] If the situation described in step S807 exists, i.e., when the first APP of UE1 may be closed or cleaned up, or when the first data collection client of UE1 is closed or before it is closed, then the initial data collection configuration information in step S801 also includes second indication information, and the data collection configuration information in step S802 also includes first indication information.

[0323] Accordingly, the memory in UE1 receives the QoE report of the first APP (optionally, as well as the identification information of the first APP).

[0324] S809: The memory in UE1 caches the QoE report of the first APP.

[0325] Optionally, the memory in the UE1 may also cache the identification information of the first APP.

[0326] S810: The access network RAN ​​equipment instructs the access layer of UE1 to resume reporting of QoE measurement results.

[0327] For example, when the network on the base station side returns to normal (i.e., no congestion or congestion recovery), the RAN device sends a recovery indication message to the access layer of UE1 via an RRC message. This recovery indication message is used to instruct UE1 to resume reporting QoE reports to the data collection network element. Accordingly, the access layer of UE1 receives the recovery indication message.

[0328] S811: The access layer of UE1 sends the second information to the first data collection client of UE1.

[0329] Correspondingly, the first data collection client of UE1 receives the second information, which is used to instruct UE1 to resume or start reporting QoE reports to the data collection network element (optionally, and the identification information of the corresponding APP).

[0330] S812A: The first data collection client of UE1 is restarted.

[0331] Due to reasons such as the user's use of the first APP, the first data collection client bound to the first APP was also restarted when it was reopened.

[0332] S812B: The first application was restarted.

[0333] Step S812B is an optional step, which causes the first APP to be restarted due to certain triggering methods.

[0334] S813: The first data collection client of UE1 checks whether the memory in UE1 has cached the QoE report of the first APP.

[0335] Optionally, the first data collection client of the UE1 also checks whether the memory in the UE1 has cached the identification information of the first APP.

[0336] If the memory cache in UE1 contains the QoE report of the first APP (optionally, and the identification information of the first APP), then the following step S814 is executed.

[0337] S814: The first data collection client of UE1 retrieves the QoE report of the first APP from the memory in UE1.

[0338] Optionally, the first data collection client of the UE1 may also obtain the identification information of the first APP from the memory in the UE1.

[0339] S815: The first data collection client of UE1 sends the QoE report of the first APP to the access layer of UE1.

[0340] Optionally, the first data collection client of the UE1 also sends the identification information of the first APP to the access layer of the UE1.

[0341] As one possible implementation, steps S813-S815 can be performed in the following way:

[0342] The first data collection client of UE1 sends a third message to the memory of UE1. This third message is used to query and request the QoE report of the first APP (optionally, and the identification information of the first APP). After receiving the third message, the memory of UE1 returns a response message to the first data collection client of UE1. This response message indicates that the memory of UE1 stores the QoE report of the first APP (optionally, and the identification information of the first APP), or it indicates that the memory of UE1 does not store the QoE report of the first APP (optionally, and the identification information of the first APP). When the response message indicates that the memory of UE1 stores the QoE report of the first APP (optionally, and the identification information of the first APP), the response message includes the QoE report of the first APP (optionally, and the identification information of the first APP).

[0343] S816: The access layer of UE1 sends the QoE report of the first APP to the data collection network element through the RAN equipment.

[0344] Optionally, the access layer of UE1 may also send the identification information of the first APP to the data collection network element through the RAN device.

[0345] For example, the access layer of UE1 first sends the QoE report of the first APP (optionally, and the identification information of the first APP) to the RAN device, and the RAN device then sends the QoE report of the first APP (optionally, and the identification information of the first APP) to the data collection network element.

[0346] After receiving the QoE report (optionally, along with the identification information of the first application) from the data collection network element, it can send it to a third party for processing to optimize the network. Subsequent steps of the data collection network element can be found in existing technologies and will not be described in detail here.

[0347] In this third embodiment, if network congestion occurs on the base station side during the collection and reporting of QoE reports of the first APP by the first data collection client of UE1, causing a suspension of reporting of QoE reports of the first APP, the first data collection client of UE1 will cache the QoE reports of the first APP. However, if the first APP bound to the first data collection client of UE1 is closed or cleared in the background, the first data collection client of UE1 will also be closed. Therefore, when the first data collection client of UE1 is closed or cleared (or before it is closed or cleared), it sends the cached QoE reports of the first APP (optionally, along with the identification information of the first APP) to the memory in UE1 (e.g., permanent memory, local disk, etc. in UE1), so that the memory in UE1 can cache the QoE reports of the first APP (optionally, along with the identification information of the first APP). When the network on the base station side is restored or the first APP or the first data collection client is restarted, the first data collection client of UE1 can obtain the QoE report of the first APP (optionally, and the identification information of the first APP) from the memory of UE1, and report the QoE report of the first APP (optionally, and the identification information of the first APP) to the data collection network element on the network side, thereby ensuring the integrity and reliability of the QoE report of the first APP.

[0348] Example 4

[0349] In this fourth embodiment, the first data collection client of the terminal device (such as UE1) is separate from the first application (i.e., the first APP) of UE1. That is, the first data collection client of UE1 can be an intermediate layer suite integrated into the operating system or system level of UE1. The first data collection client can be used to collect and report data and / or information (such as QoE reports) of at least one APP of UE1. The first APP is included in the at least one APP, and the first data collection client cannot be easily closed due to the APP of UE1 being closed or other reasons.

[0350] When UE1 reports the Quality of Experience (QoE) report (corresponding service data) of the first application to the network side, if network congestion occurs on the base station side, the access network (RAN) device will instruct UE1 to suspend reporting the QoE report of the first application. UE1 will cache the QoE report of the first application in its first data collection client. If the first application of UE1 is closed, the first data collection client of UE1 will continue to cache the QoE report of the first application and report the QoE report of the first application (optionally, along with the identification information of the first application). (Reference) Figure 9 As shown, the specific process of the method in this embodiment four is as follows:

[0351] S901: The application provider sends initial data collection configuration information to the data collection network element.

[0352] Accordingly, the data collection network element receives the initial data collection configuration information, which includes one or more of the following: data information to be collected, reporting rules, rules for external access, and security authentication information for external access.

[0353] Optionally, the data collection network element (network-side network element) can be an independent data collection network element (such as DC-AF, or 5GMS AF, or 5GMSd AF, or 5GMSu AF) or OAM.

[0354] Optionally, the initial data collection configuration information may also include second instruction information, which is used to instruct the first data collection client of UE1 to cache the QoE report of the first APP during the QoE report suspension reporting period.

[0355] It should be noted that the second instruction information is used to instruct the first data collection client of UE1 to cache the QoE reports of the corresponding APP during the pause in the reporting of the QoE reports of the APP it collects. Therefore, the collection, reporting and caching of the QoE reports of the first APP by the first data collection client in this embodiment is only an example.

[0356] S902: The data collection network element sends data collection configuration information to the first data collection client of UE1.

[0357] Accordingly, the first data collection client of UE1 receives the data collection configuration information. This data collection configuration information is generated by the data collection network element based on the aforementioned initial data collection configuration information, and it is used to instruct UE1 to report the QoE of UE1's first APP to the data collection network element after the first APP is activated.

[0358] For example, the data collection configuration information can be sent to the access network device through the data collection network element. The access network device then sends the data collection configuration information to the access layer of UE1 via an RRC message, and the access layer of UE1 then sends the data collection configuration information to the first data collection client of UE1.

[0359] Optionally, the data collection configuration information may also include first indication information. If the initial data collection configuration information may also include second indication information, the first indication information may be generated based on the second indication information in the initial data collection configuration information. The first indication information is used to instruct the first data collection client of UE1 to cache the QoE report of the first APP during the QoE report suspension reporting period.

[0360] It should be noted that UE1 may include multiple data collection clients. Different applications (APPs) may correspond to different data collection clients. That is, one APP corresponds to one data collection client, or multiple APPs correspond to one data collection client. This application does not make specific limitations in this regard.

[0361] Therefore, in step S902, the data collection network element can send the data collection configuration information to different data collection clients in UE1. For example, the access layer can send the data collection configuration information to the upper layer, and correspondingly, different data collection clients in the upper layer will receive the data collection configuration information. This embodiment uses the first APP and the first data collection client in UE1 as an example to describe the method of this application in detail. Therefore, other APPs and data collection clients in UE1, or other UEs, can be implemented by referring to the first APP and the first data collection client in UE1 or the same method as UE1, and will not be described in detail here.

[0362] S903: The first application of UE1 has started running.

[0363] After the first application of UE1 starts running, the first data collection client of UE1 starts collecting the QoE of the first application, obtains the QoE report of the first application, and reports the QoE report according to the data collection configuration information.

[0364] Optionally, the QoE of the first APP may include, but is not limited to, any one or more of the following: such as initial playback latency, throughput, and cache level information.

[0365] Optionally, step S903 can be performed before step S902, that is, after the first APP of UE1 starts running, it obtains data collection configuration information from the data collection network element and performs QoE report collection and reporting based on the data collection configuration information.

[0366] S904: The RAN device instructs the access layer of UE1 to suspend the reporting of QoE reports.

[0367] For example, when network congestion occurs at the base station, the RAN device sends a pause indication message to the access layer of UE1 via an RRC message. This pause indication message instructs UE1 to pause / stop reporting QoE reports to the data collection network element. Accordingly, the access layer of UE1 receives this pause indication message.

[0368] The pause instruction is used to instruct the UE to pause or stop QoE reporting or service data reporting, and is not targeted at any specific app.

[0369] S905: The access layer of UE1 sends the first information to the first data collection client of UE1.

[0370] Accordingly, the first data collection client of UE1 receives the first information, which is used to notify UE1 to suspend or stop reporting QoE reports to the data collection network element.

[0371] Optionally, the first information can be sent from the access layer of UE1 to the upper layer of UE1 via AT Command. That is, the access layer of UE1 sends the first information to the first data collection client of UE1 via AT Command, thereby instructing UE1 not to report QoE reports to the data collection network element.

[0372] It should be understood that the first data collection client of UE1 will continue to collect service data based on the first information, but will suspend reporting to the data collection network element, that is, it will only collect service data and not report it.

[0373] S906: The first data collection client of UE1 caches the QoE report of the first APP.

[0374] Based on the above step S905, after the first data collection client of UE1 learns that the reporting of the QoE report of the first APP is suspended, it no longer sends the QoE report of the first APP to the access layer of UE1, but caches the QoE report of the first APP.

[0375] S907: The first collection client of UE1 determines that the first APP will be closed or cleared in the background.

[0376] Step S907 is an optional step.

[0377] For example, when the first data collection client caches the QoE report of the first APP, the first APP bound to the first data collection client may be closed or cleaned up in the background for some reason. That is, the first data collection client is closed, for example, due to user operation causing the first APP to be closed, or due to UE1 performing cleanup causing the first APP to be closed.

[0378] Since closing or cleaning up the first app in UE1 will also cause the first data collection client in UE1 to close and stop caching, the first data collection client in UE1 can be notified when it is about to be closed or cleaned up.

[0379] The above steps S801-S807 and the above Figure 6 Steps S601-S607 correspond one-to-one with those described above. Figure 7 Steps S701-S707 correspond one-to-one, or are consistent with the above. Figure 8Steps S801-S807 correspond one-to-one and can be referenced together.

[0380] S908: The first data collection client of UE1 continues to cache the QoE report of the first APP.

[0381] S909: The RAN equipment instructs the access layer of UE1 to resume reporting of QoE measurement results.

[0382] For example, when the network on the base station side returns to normal (i.e., no congestion or congestion recovery), the RAN device sends a recovery indication message to the access layer of UE1 via an RRC message. This recovery indication message is used to instruct UE1 to resume reporting QoE reports to the data collection network element. Accordingly, the access layer of UE1 receives the recovery indication message.

[0383] S910: The access layer of UE1 sends the second information to the first data collection client of UE1.

[0384] Correspondingly, the first data collection client of UE1 receives the second information, which is used to instruct UE1 to resume or start reporting QoE reports to the data collection network element.

[0385] S911: The first data collection client of UE1 sends the QoE report of the first APP to the access layer of UE1.

[0386] Correspondingly, the access layer of UE1 receives the QoE report of the first APP.

[0387] S912: The access layer of UE1 sends the QoE report of the first APP to the data collection network element through the RAN equipment.

[0388] For example, the access layer of UE1 first sends the QoE report of the first APP to the RAN device, and the RAN device then sends the QoE report of the first APP to the data collection network element.

[0389] After receiving the QoE report from the first application, the data collection network element can send it to a third party for processing to optimize the network. Subsequent steps for the data collection network element can be found in existing technologies and will not be described in detail here.

[0390] In this fourth implementation, if network congestion at the base station causes a pause in reporting the QoE report of the first APP during the collection and reporting process of the first data collection client of UE1, the first data collection client will cache the QoE report of the first APP. If the first APP is closed or cleared in the background, the first data collection client is not easily closed because it is separate from the first APP. Therefore, the first data collection client of UE1 can continue to cache the QoE report of the first APP even when the first APP is closed or cleared. When the network at the base station recovers, the first data collection client of UE1 can send the cached QoE report of the first APP to the data collection network element on the network side, thereby ensuring the integrity and reliability of the reported QoE report of the first APP.

[0391] Based on the same concept, in order to achieve the functions of the methods provided in the embodiments of this application, this application also provides a terminal device. The terminal device may include a hardware structure and / or software modules, implementing the above functions in the form of a hardware structure, software modules, or a combination of hardware and software modules. Whether a particular function is executed in the form of a hardware structure, software module, or a combination of hardware and software modules depends on the specific application and design constraints of the technical solution.

[0392] refer to Figure 10 As shown, the terminal device 1000 may include a first data collection unit 1001, an access layer unit 1002, a second data collection unit 1003, and a memory unit 1004. The first data collection unit 1001 can be used to implement the function of the first data collection client in the above embodiments; the access layer unit 1002 can be used to implement the function of the access layer in the above embodiments; the second data collection unit 1003 can be used to implement the function of the second data collection client in the above embodiments; and the memory unit 1004 can be used to implement the function of the memory in the above embodiments. The first data collection unit 1001, the access layer unit 1002, the second data collection unit 1003, and the memory unit 1004 can all belong to the target functional modules (units) in the above embodiments, and different units can be interconnected.

[0393] In addition, refer to Figure 11As shown in the illustration, a terminal device 1100 provided in this application embodiment may include a communication unit 1101 and a processing unit 1102, wherein the communication unit 1101 and the processing unit 1102 are coupled to each other. The terminal device 1100 can be used to support communication. The communication unit 1101 may also be referred to as a communication module, communication interface, transceiver module, or transceiver unit. The communication unit 1101 can be used to support information and / or data interaction (or communication) between the first data collection unit 1001, access layer unit 1002, second data collection unit 1003, and memory unit 1004 in the above method embodiments and other units in the terminal device (and external devices). Furthermore, the communication unit 1101 may have wireless communication capabilities, for example, it can communicate with other communication devices via wireless communication.

[0394] The processing unit 1102 can also be referred to as a processing module, which can be used to support the processing actions of the first data collection unit 1001, the access layer unit 1002, the second data collection unit 1003, and the memory 1004, including but not limited to: generating information and messages sent by the communication unit 1101, and / or storing the service data received by the communication unit 1101, etc.

[0395] Optionally, the terminal device 1100 may also include a storage unit 1103, which can be used to support the storage operations of the first data collection unit 1001, the access layer unit 1002, the second data collection unit 1003, and the memory unit 1004.

[0396] Specifically, the first data collection unit 1001 receives data collection configuration information, which is used to instruct the terminal device to collect and report service data; receives first information, which is used to notify the terminal device to stop reporting the service data; the first data collection unit 1001 also stores the service data in the target function module of the terminal device; and receives second information, which is used to instruct the terminal device to resume / start reporting the service data.

[0397] In one possible implementation, when the first data collection unit 1001 receives data collection configuration information, it may specifically receive the data collection configuration information from the data collection network element.

[0398] In one possible implementation, the data collection configuration information includes first indication information, which is used to instruct the first data collection unit 1001 to send and store the data of the service in the target functional module (unit) of the terminal device when it is turned off or stopped.

[0399] In one possible implementation, the first indication information is further used to instruct the first data collection unit 1001 to check whether the memory unit 1004 stores the data of the service when it recovers or / starts reporting the data of the service.

[0400] In one possible implementation, the target functional module is the access layer unit 1002; the access layer unit 1002 can receive second information and send the service data to the data collection network element.

[0401] In one possible implementation, the target functional module is the second data collection unit 1003; the second data collection unit 1003 can receive second information from the access layer unit 1002; according to the second information, it sends the service data to the access layer unit 1002; the access layer unit 1002 sends the service data to the data collection network element, and optionally, also sends the service identification information to the data collection network element.

[0402] In one possible implementation, the target functional module is the memory unit 1004; the first data collection unit 1001 receives second information from the access layer unit 1002; checks whether the memory unit 1004 stores the service data; if the memory unit 1004 stores the service data, it obtains the service data from the memory unit 1004; and sends the service data to the data collection network element, optionally also sending the service identification information to the data collection network element.

[0403] In one possible implementation, when the first data collection unit 1001 stores the service data in the target functional module of the terminal device, it may specifically send the service data (optionally, and the service identification information) to the target functional module; the first data collection unit 1001 may be turned off or stopped.

[0404] In one possible implementation, the data for the service includes one or more of the following: initial playback latency, throughput, and cached service level.

[0405] Based on the same concept, this application also provides a communication device. This communication device can be used to implement the functions of the above-mentioned data collection network element (entity). The communication device may include hardware structures and / or software modules, implementing the above functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Whether a particular function is implemented using hardware structures, software modules, or a combination of hardware structures and software modules depends on the specific application and design constraints of the technical solution.

[0406] like Figure 12 As shown in the illustration, a communication device 1200 provided in this application embodiment may include a communication unit 1201 and a processing unit 1202. Optionally, the communication device 1200 may further include a storage unit 1203. The communication unit 1201, processing unit 1202, and storage unit 1203 are coupled to each other. The communication device 1200 can be used to execute the steps performed by the data collection network element as shown in the above method embodiments. The communication device 1200 can be used to support communication. The communication unit 1201 may also be referred to as a communication module, communication interface, transceiver module, or transceiver unit. The communication unit 1201 may have wireless communication functionality, for example, it can communicate with other communication devices via wireless communication. The processing unit 1202 may also be referred to as a processing module, and can be used to support the communication device 1200 in performing the processing actions of the data collection network element in the above method embodiments, including but not limited to: generating data collection configuration information sent by the communication unit 1201.

[0407] Specifically, the processing unit 1202 is used to generate data collection configuration information; wherein, the data collection configuration information includes first instruction information, which is used to instruct the first data collection client of the terminal device to send and store the service data of the terminal device in the target function module of the terminal device when the first data collection client stops or closes; the communication unit 1201 is used to send the data collection configuration information to the first data collection client of the terminal device, and the data collection configuration information is used to instruct the terminal device to collect and report the service data.

[0408] In one possible implementation, the first indication information is further used to instruct the first data collection client to check whether the data of the service is stored in the memory of the terminal device when it resumes / starts reporting the data of the service.

[0409] In one possible implementation, when the processing unit 1202 generates data collection configuration information, it may specifically be used to receive initial data collection configuration information from an application service provider. The initial data collection configuration information includes second indication information, which is used to instruct the terminal device to send and store the data of the service in the target functional module of the terminal device when the first data collection client is closed / stopped. The data collection configuration information is generated according to the initial data collection configuration information.

[0410] In one possible implementation, the initial data collection configuration information includes one or more of the following: data information to be collected, reporting rules, rules for external access, and security authentication information for external access.

[0411] In one possible implementation, the target functional module of the terminal device is any one of the following: the access layer of the terminal device, the first data collection client of the terminal device, the second data collection client of the terminal device, and the memory in the terminal device.

[0412] In one possible implementation, the data for the service includes one or more of the following: initial playback latency, throughput, and cached service level.

[0413] This application also provides a communication device, which can be a terminal device, a processor of the terminal device, or a chip. This communication device can be used to perform the operations performed by the terminal device in the above method embodiments. The communication device can also be a data collection network element (entity), a processor of the data collection network element, or a chip. This communication device can be used to perform the operations performed by the data collection network element in the above method embodiments.

[0414] Figure 13 A simplified structural diagram of a communication device is shown. (For example...) Figure 13 As shown, the communication device 1300 may include a processor 1302. Optionally, the communication device 1300 may also include a transceiver 1301, a memory 1303, and a communication bus 1304. The transceiver 1301, processor 1302, and memory 1303 can be interconnected via the communication line 1304. The communication line 1304 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The communication line 1304 can be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, Figure 13 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0415] The processor 1302 can also be referred to as a processing unit, processing board, processing module, processing device, etc. The processor 1302 can be a CPU, microprocessor, ASIC, or one or more integrated circuits used to control the execution of the program of the present application.

[0416] Transceiver 1301 can also be referred to as a transceiver module, transceiver unit, transceiver, transceiver circuit, transceiver device, communication interface, etc. Optionally, the devices in transceiver 1301 used to implement the transmitting function can be considered as transmitting units or transmitting modules, and the devices in transceiver 1301 used to implement the receiving function can be considered as receiving units or receiving modules. That is, transceiver 1301 may include a transmitter and a receiver, radio frequency circuitry, an antenna, and input / output devices. A transmitter may also be referred to as a transmitter module, transmitting unit, transmitting circuit, etc. A receiver may also be referred to as a receiver module, receiving unit, receiving circuit, etc. Radio frequency circuitry is mainly used for converting baseband signals to radio frequency signals and processing radio frequency signals. An antenna is mainly used for transmitting and receiving radio frequency signals in the form of electromagnetic waves. Input / output devices, such as touchscreens, displays, and keyboards, are mainly used to receive user input data and output data to the user. It should be noted that some types of communication devices may not have input / output devices.

[0417] The memory 1303 is mainly used to store software programs and data.

[0418] When data needs to be transmitted, the processor 1302 performs baseband processing on the data to be transmitted and outputs a baseband signal to the radio frequency (RF) circuit. The RF circuit then processes the baseband signal and transmits it outward as an electromagnetic wave through the antenna. When data is sent to the communication device, the RF circuit receives the RF signal through the antenna, converts it into a baseband signal, and outputs the baseband signal to the processor 1302. The processor 1302 converts the baseband signal back into data and processes the data. For ease of explanation, Figure 13 Only one memory, processor, and transceiver are shown in the illustration. In actual communication device products, there may be one or more processors and one or more memories. Memory can also be called storage medium or storage device, etc. Memory can be set up independently of the processor or integrated with the processor; this application does not limit this.

[0419] Optionally, the transceiver 1301 and memory 1303 may include one or more circuit boards, each of which may include one or more processors and one or more memories. The processor is used to read and execute programs in the memory to implement baseband processing functions and control the communication device. If multiple circuit boards exist, they can be interconnected to enhance processing capabilities. As an optional implementation, multiple circuit boards may share one or more processors, or multiple circuit boards may share one or more memories, or multiple circuit boards may simultaneously share one or more processors.

[0420] When the communication device 1300 is used as a terminal device, the transceiver 1301 is mainly used to implement the transmitting and receiving functions of the terminal device. The processor 1302 is the control center of the terminal device, used to control the terminal device to execute the processing operations on the terminal device side in the above method embodiments. The memory 1303 is mainly used to store the computer program code and data on the terminal device side.

[0421] In the embodiments of this application, a transceiver with transceiver function can be regarded as a transceiver module (transceiver unit) of a terminal device, and a processor with processing function can be regarded as a processing module (processing unit) of a terminal device.

[0422] In one implementation, processor 1302 is used to execute Figures 5-9 In the embodiment shown, the transceiver 1301 is used to execute the processing actions on the terminal device side. Figures 5-9 Transceiver operations on the terminal device side. For example, transceiver 1301 is used to perform... Figure 5 In the illustrated embodiment, S503 may specifically involve receiving data collection configuration information, which instructs the terminal device to collect and report service data. The processor 1302 is used to execute... Figure 5 The processing operation of S506 in the illustrated embodiment can specifically store the service data in the target functional module of the terminal device.

[0423] It should be understood that Figure 13 This is merely an example and not a limitation; the terminal device described above, which includes a transceiver module and a processing module, may not rely on... Figure 13 The structure shown.

[0424] When the communication device functions as a data collection network element (entity), transceiver 1301 primarily implements the data collection network element's transmission and reception functions. Processor 1302 is the control center of the data collection network element, used to control the data collection network element to execute the processing operations on the data collection network element side in the above method embodiments. Memory 1303 is mainly used to store the computer program code and data of the data collection network element.

[0425] In one implementation, transceiver 1301 is used to perform... Figures 5-9 The transceiver-related processes performed by the data collection network element in the illustrated embodiment, for example, are executed by transceiver 1301. Figure 5 In the illustrated embodiment, S503 may specifically involve sending data collection configuration information, which instructs the terminal device to collect and report service data. The processor 1302 is used to execute... Figures 5-9 The illustrated embodiment includes processing-related procedures performed by the data collection network element, for example, the processor 1302 is used to execute... Figure 5In the embodiment shown, S502 can specifically be generating data collection configuration information based on the initial data collection configuration information.

[0426] It should be understood that Figure 13 This is merely an example and not a limitation; the second communication device described above, including the processor, memory, and transceiver, may be independent of... Figure 13 The structure shown.

[0427] When the aforementioned communication device (terminal equipment side or data collection network element side) is used as a chip, Figure 14 A simplified schematic diagram of a chip device 1400 is shown, which includes an interface circuit 1401 and a processor 1402. The interface circuit 1401 and the processor 1402 are coupled to each other. It can be understood that the interface circuit 1401 can be a transceiver or an input / output interface, and the processor can be a processing module, microprocessor, or integrated circuit integrated on the chip. In the above method embodiments, the transmitting operation of the terminal device (or data collection network element) can be understood as the output of the chip device, and the receiving operation of the terminal device (or data collection network element) can be understood as the input of the chip device.

[0428] Optionally, the chip device 1400 may further include a memory 1403 for storing instructions executed by the processor 1402, or storing input data required by the processor 1402 to execute instructions, or storing data generated after the processor 1402 executes instructions. Optionally, the memory 1403 may also be integrated with the processor 1402.

[0429] This application also provides a computer-readable storage medium storing computer instructions for implementing the methods executed by a terminal device or a data collection network element in the above method embodiments.

[0430] For example, when the computer program is executed by a computer, it enables the computer to implement the method executed by the terminal device or data collection network element in the above method embodiments.

[0431] This application also provides a computer program product containing instructions that, when executed by a computer, cause the computer to implement the method described in the above method embodiments, which is executed by a terminal device or a data collection network element.

[0432] This application also provides a communication system, which includes the terminal device and data collection network element (entity) in the above embodiments.

[0433] This application also provides a chip device, including a processor, configured to call computer programs or computer instructions stored in the memory, so that the processor executes the above-described... Figure 5A communication method of the embodiment shown.

[0434] In one possible implementation, the input of the chip device corresponds to the above. Figure 5 The receiving operation in the illustrated embodiment corresponds to the output of the chip device described above. Figure 5 The sending operation in the illustrated embodiment.

[0435] Optionally, the processor is coupled to the memory via an interface.

[0436] Optionally, the chip device further includes a memory storing computer programs or computer instructions.

[0437] The processor mentioned above can be a general-purpose central processing unit, a microprocessor, an application-specific integrated circuit (ASIC), or one or more devices used to control the above. Figure 5 The illustrated embodiment is an integrated circuit for program execution of a communication method. The memory mentioned above can be read-only memory (ROM) or other types of static storage devices capable of storing static information and instructions, such as random access memory (RAM).

[0438] It should be noted that, for the sake of convenience and brevity, the explanations and beneficial effects of the relevant contents in any of the communication devices provided above can be referred to the corresponding method embodiments provided above, and will not be repeated here.

[0439] In this application, the terminal device or data collection network element may include a hardware layer, an operating system layer running on top of the hardware layer, and an application layer running on top of the operating system layer. The hardware layer may include hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also known as main memory). The operating system layer may be any one or more computer operating systems that implement business processing through processes, such as Linux, Unix, Android, iOS, or Windows. The application layer may include applications such as browsers, address books, word processing software, and instant messaging software.

[0440] The module division in this embodiment is illustrative and represents only one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional modules in each embodiment of this application can be integrated into a single processor, exist as separate physical entities, or be integrated into a single module. The integrated modules described above can be implemented in hardware or as software functional modules.

[0441] Through the above description of the embodiments, those skilled in the art will clearly understand that the embodiments of this application can be implemented in hardware, firmware, or a combination thereof. When implemented in software, the above functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any medium that facilitates the transfer of a computer program from one place to another. Storage media can be any available medium accessible to a computer. For example, but not limited to, computer-readable media can include RAM, ROM, electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, magnetic disk storage media, or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible to a computer. Furthermore, any connection can suitably be a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of the medium. As used in embodiments of this application, disks and discs include compact discs (CDs), laser discs, optical discs, digital video discs (DVDs), floppy disks, and Blu-ray discs, wherein disks typically magnetically copy data, while discs optically copy data using lasers. The combinations above should also be included within the scope of protection for computer-readable media.

[0442] In summary, the above descriptions are merely embodiments of this application and are not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made based on the disclosure of this application should be included within the scope of protection of this application.

Claims

1. A communication method, characterized in that, include: The first data collection client of the terminal device receives data collection configuration information. This data collection configuration information instructs the terminal device to collect and report service data. The data collection configuration information includes first instruction information, which instructs the first data collection client to send and store the service data in the target functional module of the terminal device when the first data collection client stops or closes. The target functional module is any one of the following: The terminal device's access layer, the first data collection client, the terminal device's second data collection client, and the terminal device's memory; The first data collection client receives first information, which is used to notify the terminal device to stop reporting the data of the service. In response to the first information, the first data collection client stores the data of the service in the target functional module; The terminal device receives second information, which instructs the terminal device to resume / start reporting the data of the service.

2. The method according to claim 1, characterized in that, The first data collection client of the terminal device receives data collection configuration information, including: The first data collection client of the terminal device receives the data collection configuration information from the data collection network element.

3. The method according to claim 1, characterized in that, The first indication information is also used to instruct the first data collection client to check whether the memory in the terminal device stores the data of the service when it resumes / starts reporting the data of the service.

4. The method according to claim 1 or 2, characterized in that, The terminal device receives the second information, including: The access layer of the terminal device receives the second information; The method further includes: The access layer of the terminal device sends the service data to the data collection network element.

5. The method according to claim 1 or 2, characterized in that, The terminal device receives the second information, including: The second data collection client of the terminal device receives second information from the access layer of the terminal device; The method further includes: The second data collection client sends the service data to the access layer of the terminal device based on the second information; The access layer of the terminal device sends the service data to the data collection network element.

6. The method according to any one of claims 1 to 3, characterized in that, The terminal device receives the second information, including: The first data collection client of the terminal device receives second information from the access layer or application layer of the terminal device; The method further includes: The first data client of the terminal device checks whether the memory in the terminal device stores the data of the service; If the terminal device stores the data of the service in its memory, the first data client of the terminal device obtains the data of the service from the memory in the terminal device; The first data client of the terminal device sends the data of the service to the data collection network element.

7. The method according to any one of claims 1 to 6, characterized in that, The first data collection client stores the service data in the target functional module of the terminal device, including: The first data collection client sends the data of the service to the target function module; The first data collection client is closed or stopped.

8. The method according to any one of claims 1 to 7, characterized in that, The data for the service includes one or more of the following: initial playback latency, throughput, and cache service level.

9. A communication method, characterized in that, include: Data collection network elements generate data collection configuration information; The data collection configuration information is used to instruct the terminal device to collect and report service data. The data collection configuration information includes first instruction information, which instructs the terminal device's first data collection client to send and store the service data in the terminal device's target functional module when the first data collection client is stopped or closed. The target functional module is any one of the following: The terminal device's access layer, the first data collection client, the terminal device's second data collection client, and the terminal device's memory; The data collection network element sends the data collection configuration information to the first data collection client of the terminal device.

10. The method according to claim 9, characterized in that, The first indication information is also used to instruct the first data collection client to check whether the memory in the terminal device stores the data of the service when it resumes / starts reporting the data of the service.

11. The method according to claim 9, characterized in that, The data collection network element generates data collection configuration information, including: The data collection network element receives initial data collection configuration information from the application service provider. The initial data collection configuration information includes second indication information, which is used to instruct the terminal device to send and store the data of the service in the target functional module of the terminal device when the first data collection client is closed or stopped. The data collection network element generates the data collection configuration information based on the initial data collection configuration information.

12. The method according to claim 11, characterized in that, The initial data collection configuration information includes one or more of the following: data information to be collected, reporting rules, rules for external access, and security authentication information for external access.

13. The method according to any one of claims 9 to 12, characterized in that, The data for the service includes one or more of the following: initial playback latency, throughput, and cache service level.

14. A terminal device, characterized in that, Includes modules or units for performing the method according to any one of claims 1-8.

15. A communication device, characterized in that, Includes modules or units for performing the method according to any one of claims 9-13.

16. A communication device, characterized in that, The device includes a processor and an interface circuit. The interface circuit is used to receive signals from other communication devices besides the communication device and transmit them to the processor, or to send signals from the processor to other communication devices besides the communication device. The processor is used to implement the method as described in any one of claims 1-8, or to implement the method as described in any one of claims 9-13, through logic circuits or execution code instructions.

17. A communication system, characterized in that, include: A terminal device for performing the method of any one of claims 1 to 8, and a data collection network element for performing the method of any one of claims 9 to 13.

18. A computer program product, characterized in that, Includes a computer program that, when executed by a communication device, implements the method as described in any one of claims 1-13.

19. A computer-readable storage medium, characterized in that, The storage medium stores a computer-readable program or instructions that, when executed by a communication device, implement the method as described in any one of claims 1-13.

Images