Data collection for ai / ML models in communication systems
The network and terminal device configuration optimizes data collection and reporting for AI/ML models by adhering to server-defined requirements, enhancing efficiency and resource management, and handling emergencies and user consent issues.
Patent Information
- Application Number
- PCT/CN2025/093541
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-08
- Publication Date
- 2026-11-12
AI Technical Summary
Existing data collection and reporting processes for AI/ML models in communication systems are inefficient and do not adequately address the needs of OTT servers, fail to handle emergency scenarios, and lack comprehensive data collection requirements, leading to suboptimal performance and potential resource mismanagement.
A network device and terminal device configuration that allows for controlled data collection and reporting based on server-defined requirements, including selection criteria, data storage time management, error reporting, and resource availability, ensuring efficient data collection and handling of emergency scenarios.
Enables efficient data collection and reporting tailored to server needs, optimizing resource utilization and ensuring data quality, while addressing emergency situations and user consent revocation scenarios.
Smart Images

Figure CN2025093541_12112026_PF_FP_ABST
Abstract
Description
DATA COLLECTION FOR AI / ML MODELS IN COMMUNICATION SYSTEMSTECHNICAL FIELD
[0001] Embodiments of the invention relate to a network device and a terminal device for data collection as input to AI / ML models in communication systems and networks. Furthermore, embodiments of the invention also relate to corresponding methods and a computer program.BACKGROUND
[0002] 3GPP is studying the process of data collection by a user equipment (UE) where the data is used for training an artificial intelligence / machine learning (AI / ML) model to optimize services of the network e.g., positioning, beamforming, channel estimation, etc.
[0003] The data collected by UEs is expected to be standardized and the reporting of the collected data is expected to occur over the user plane.
[0004] The collected data is expected to be sent to a network function (NF) in the communication network and then to an over-the-top (OTT) server which may be arranged outside the network. The interaction between the OTT server and the network is based on exposure services.SUMMARY
[0005] An objective of embodiments of the invention is to provide a solution which mitigates or solves the drawbacks and problems of conventional solutions.
[0006] Another objective of embodiments of the invention is to provide an improved solution for data collection for AI / ML models compared to conventional solutions.
[0007] The above and further objectives are solved by the subject matter of the independent claims. Further embodiments of the invention can be found in the dependent claims.
[0008] According to a first aspect of the invention, the above mentioned and other objectives are achieved with a network device configured to: receive a first message from a server, the first message indicating a request for data; determine a data report according to a reporting configuration and based on data collected by at least one terminal device in a set of terminal devices; and transmit a second message to the server, the second message indicating the data report.
[0009] A general advantage of the network device according to the first aspect is that it allows the network device to control the data collection process in accordance with the requirements of the server in order to meet the desired data collection service in the most efficient manner. Thus, the data collection configuration is tuned to desired service needs.
[0010] In an implementation form of a network device according to the first aspect, the reporting configuration indicates any of: reporting of data from individual terminal devices, reporting of data from two or more terminal devices, reporting of data collected after a time period has elapsed, reporting of data collected by a percentage of terminal devices in the set of terminal devices, reporting of data collected by a subset of terminal devices in the set of terminal devices, and a selection criterion for selection of at least one terminal device in the set of terminal devices or in an area of interest, AoI.
[0011] An advantage with this implementation form is that it allows the server to negotiate how data reporting is performed and based on that takes necessary application level actions once data arrives in accordance with the reporting configuration.
[0012] In an implementation form of a network device according to the first aspect, the reporting configuration at least indicates the selection criterion, and wherein the selection criterion indicates a percentage or a ratio of terminal devices not previously been used for data collection; and wherein the network device is configured to: select at least one terminal device in the set of terminal devices for data collection based on the selection criterion.
[0013] An advantage with this implementation form is that it permits the server to control the degree of new terminal devices used in data collection compared to a previous set of terminal devices. Using new terminal devices for data collection allows data diversity and hence the server can adapt the selection criterion based on its needs with respect to data from different terminal devices participating in data collection.
[0014] In an implementation form of a network device according to the first aspect, the reporting configuration is: indicated by the first message, or pre-configured in the network device.
[0015] An advantage with this implementation form is that it allows a standardized behavior of the network device where this may be achieved by explicit signaling or by pre-configuration.
[0016] In an implementation form of a network device according to the first aspect, the first message indicates any of: an identity of at least one terminal device, an identity of an AoI, and an identity of a use case applicable for data collection.
[0017] In an implementation form of a network device according to the first aspect, the data collected by the terminal device meets a data storage time requirement.
[0018] An advantage with this implementation form is that data fulfilling the data storage time requirement can immediately be sent to the server without requesting terminal devices for data collection.
[0019] In an implementation form of a network device according to the first aspect, the data storage time requirement defines a time period the data collected by the terminal device has been stored in the network device.
[0020] An advantage with this implementation form is that it allows the server to request new collected data depending on how long the collected data has been stored in the network device. If the time period is too long then the collected data may not reflect the scenario at hand and thus the storage time requirement permits the server to ensure that collected data stored in the network device is representative of the actual conditions of the terminal devices.
[0021] In an implementation form of a network device according to the first aspect, the network device is configured to:
[0022] transmit a third message to at least one terminal device in the set of terminal devices, the third message indicating a request for data based on a data collecting configuration.
[0023] An advantage with this implementation form is that it allows the network device or the server to instruct the terminal devices to comply with the data collection configuration when collecting data. Hence, this enables an end-to-end data collecting configuration to be performed in the communication system to get the desired outcome.
[0024] In an implementation form of a network device according to the first aspect, the data collecting configuration comprises any of: an error reporting for data collection, an identity of a use case applicable for data collection, a priority level for data collection, and a priority level for data reporting.
[0025] An advantage with this implementation form is that it allows the server to know when error events occur at the terminal device. Further, the terminal device can report data based on a priority as desired by the server.
[0026] In an implementation form of a network device according to the first aspect, the data collecting configuration has an urgency level; and wherein the network device is configured to: page the terminal device when the urgency level is high.
[0027] An advantage with this implementation form is that this helps the network device to determine how to use its resources since paging uses resources over multiple RAN nodes. So, if the urgency is low then the network device can save resources by not immediately paging terminal devices.
[0028] In an implementation form of a network device according to the first aspect, the data collecting configuration is indicated by the first message, determined by the network device, or pre-configured in the network device.
[0029] In an implementation form of a network device according to the first aspect, the network device is configured to: receive a fourth message from the terminal device, the fourth message indicating at least one part of the requested data.
[0030] In an implementation form of a network device according to the first aspect, the network device is configured to: transmit a fifth message to the terminal device upon reception of the fourth message, the fifth message indicating an acknowledgement, ACK, of correctly received data in the fourth message or a negative acknowledgement, NACK, of incorrectly received data in the fourth message.
[0031] An advantage with this implementation form is that it enables the network device to verify the received data to make sure that the data satisfies the desired content and format, and / or that security aspects are met. Thus, the network device can trigger data collection if there is a problem with the data content or format. Otherwise, the terminal device will not know if there has been problem with the reported data. Thus, this enables a recovery mechanism for data collection that has experienced problems with data content or format.
[0032] In an implementation form of a network device according to the first aspect, the network device is configured to: receive a sixth message from the terminal device, the sixth message indicating data collection and reporting resources of the terminal device; and select at least one terminal device in the set of terminal devices for data collection based on the sixth message.
[0033] An advantage with this implementation form is that it provides the network device with insights about resources that can be used for improved selection of terminal devices for data collection.
[0034] In an implementation form of a network device according to the first aspect, the data collection and reporting resources comprises any of: a memory size, a maximum data size, a maximum storage time, a power level description, and a power saving setting.
[0035] An advantage with this implementation form is that it allows the selection of terminal devices based on desired data size and resource availability in the terminal devices. Otherwise, some terminal devices may be selected but the data collection may not succeed if the selected terminal devices do not have enough resources for data collection.
[0036] In an implementation form of a network device according to the first aspect, the network device is configured to: receive a seventh message from the terminal device, the seventh message indicating an error event during data collection.
[0037] An advantage with this implementation form is that it allows the terminal device to inform the network device when error events have occurred and thus the network device can understand why data collection and reporting may be delayed.
[0038] In an implementation form of a network device according to the first aspect, the seventh message indicates data collected until the error event during the data collection.
[0039] An advantage with this implementation form is that it enables the terminal device to share some data that may be used for AI / ML model training although the data may not be complete. In this way, already collected data is not wasted.
[0040] In an implementation form of a network device according to the first aspect, the network device is configured to: transmit an eight message to the server, the eight message indicating the error event during data collection.
[0041] An advantage with this implementation form is that it informs the server about any error events. This gives the server insights about the data collection process at the terminal devices.
[0042] In an implementation form of a network device according to the first aspect, the eight message indicates data collected until the error event during the data collection.
[0043] An advantage with this implementation form is that it allows any data reported by the terminal device, even when not completed, to be forwarded to the server.
[0044] In an implementation form of a network device according to the first aspect, the server is an application server and the data is input data to an artificial intelligence / machine learning, AI / ML, model.
[0045] According to a second aspect of the invention, the above mentioned and other objectives are achieved with a terminal device configured to: receive a third message from a network device, the third message indicating a request for data based on a data collection configuration; and start collecting data based on the third message.
[0046] An advantage of the terminal device according to the second aspect is that it allows the network device to control the data collection process at the terminal device in accordance with the requirements of a server in order to meet the desired data collection service in the most efficient manner. Thus, the data collection configuration is tuned to desired service needs.
[0047] In an implementation form of a terminal device according to the second aspect, the data collection configuration comprises any of: an error reporting for data collection, an identity of a use case applicable for data collection, a priority level for data collection, and a priority level for data reporting.
[0048] An advantage with this implementation form is that it allows the network device / server to know when error events occur at the terminal device. Further, the terminal device can report data based on a priority as desired by the network device / server.
[0049] In an implementation form of a terminal device according to the second aspect, the terminal device is configured to: complete collecting data based on the third message; and transmit a fourth message to the network device, the fourth message indicating the requested data according to the data collection configuration.
[0050] In an implementation form of a terminal device according to the second aspect, the terminal device is configured to: stop collecting data upon an establishment of an emergency service by the terminal device.
[0051] Thereby a procedure for handling data collection and establishment of an emergency service is provided.
[0052] In an implementation form of a terminal device according to the second aspect, the terminal device is configured to: continue collecting data upon a release of the emergency service; and transmit a fourth message to the network device, the fourth message indicating the requested data according to the data collection configuration.
[0053] In an implementation form of a terminal device according to the second aspect, the terminal device is configured to: delete data collected before the establishment of the emergency service; restart collecting data based on the third message upon the release of the emergency service; and transmit a fourth message to the network device, the fourth message indicating the requested data according to the data collection configuration.
[0054] In an implementation form of a terminal device according to the second aspect, the emergency service comprises an emergency call of a packet data unit, PDU, session.
[0055] In an implementation form of a terminal device according to the second aspect, the terminal device is configured to: stop collecting data upon reception of a user input indicating a revocation of a user consent for collecting data by the terminal device.
[0056] Thereby a procedure for handling data collection in situation of revocation of a user consent for collecting data is provided.
[0057] In an implementation form of a terminal device according to the second aspect, the terminal device is configured to: delete data collected before the revocation of the user consent.
[0058] In an implementation form of a terminal device according to the second aspect, the terminal device is configured to: transmit a fourth message to the network device, the fourth message indicating data collected before the revocation of the user consent.
[0059] In an implementation form of a terminal device according to the second aspect, the terminal device is configured to: receive a fifth message from the network device after having transmitted the fourth message, the fifth message indicating an ACK of correctly received data in the fourth message or a NACK of incorrectly received data in the fourth message; delete collected data stored in the terminal device when the fifth message indicates the ACK; and retransmit the fourth message to the network device when the fifth message indicates the NACK, or restart collecting data based on the third message when the fifth message indicates the NACK.
[0060] An advantage with this implementation form is that it enables the network device to verify the received data to make sure that the data satisfies the desired content and format, and / or that security aspects are met. Thus, the network device can trigger data collection if there is a problem with the data content or format. Otherwise, the terminal device will not know if there has been problem with the reported data. Thus, this enables a recovery mechanism for data collection that has experienced problems with data content or format.
[0061] In an implementation form of a terminal device according to the second aspect, the terminal device is configured to: transmit a sixth message to the network device, the sixth message indicating data collection and reporting resources of the terminal device.
[0062] An advantage with this implementation form is that it provides the network device with insights about resources that can be used for improved selection of terminal devices for data collection.
[0063] In an implementation form of a terminal device according to the second aspect, the data collection and reporting resources comprises any of: a memory size, a maximum data size, a maximum storage time, a power level description, and a power saving setting.
[0064] An advantage with this implementation form is that it allows the selection of terminal devices based on desired data size and resource availability in the terminal devices. Otherwise, some terminal devices may be selected but the data collection may not succeed if the selected terminal devices do not have enough resources for data collection.
[0065] In an implementation form of a terminal device according to the second aspect, the terminal device is configured to: transmit a seventh message to the network device, the seventh message indicating an error event during the data collection.
[0066] An advantage with this implementation form is that it allows the terminal device to inform the network device when error events have occurred and thus the network device can understand why data collection and reporting may be delayed.
[0067] In an implementation form of a terminal device according to the second aspect, the seventh message indicates data collected until the error event during the data collection.
[0068] An advantage with this implementation form is that it enables the terminal device to share some data that may be used for AI / ML model training although the data may not be complete. In this way, already collected data is not wasted.
[0069] According to a third aspect of the invention, the above mentioned and other objectives are achieved with a method for a network device, the method comprises: receiving a first message from a server, the first message indicating a request for data; determining a data report according to a reporting configuration and based on data collected by at least one terminal device in a set of terminal devices; and transmitting a second message to the server, the second message indicating the data report.
[0070] The method according to the third aspect can be extended into implementation forms corresponding to the implementation forms of the network device according to the first aspect. Hence, an implementation form of the method comprises the feature (s) of the corresponding implementation form of the network device.
[0071] The advantages of the methods according to the third aspect are the same as those for the corresponding implementation forms of the network device according to the first aspect.
[0072] According to a fourth aspect of the invention, the above mentioned and other objectives are achieved with a method for a terminal device, the method comprises: receiving a third message from a network device, the third message indicating a request for data based on a data collection configuration; and start collecting data based on the third message.
[0073] The method according to the fourth aspect can be extended into implementation forms corresponding to the implementation forms of the terminal device according to the second aspect. Hence, an implementation form of the method comprises the feature (s) of the corresponding implementation form of the terminal device.
[0074] The advantages of the methods according to the fourth aspect are the same as those for the corresponding implementation forms of the terminal device according to the second aspect.
[0075] Embodiments of the invention also relate to a computer program, characterized in program code, which when run by at least one processor causes the at least one processor to execute any method according to embodiments of the invention.
[0076] Further, embodiments of the invention also relate to a computer program product comprising a computer readable medium and the mentioned computer program, wherein the computer program is included in the computer readable medium, and may comprises one or more from the group of: read-only memory (ROM) , programmable ROM (PROM) , erasable PROM (EPROM) , flash memory, electrically erasable PROM (EEPROM) , hard disk drive, etc.
[0077] Further applications and advantages of embodiments of the invention will be apparent from the following detailed description.BRIEF DESCRIPTION OF THE DRAWINGS
[0078] The appended drawings are intended to clarify and explain different embodiments of the invention, in which:
[0079] FIG. 1 shows a network device according to embodiments of the invention;
[0080] FIG. 2 shows a flow chart of a method for a network device according to embodiments of the invention;
[0081] FIG. 3 shows a terminal device according to embodiments of the invention;
[0082] FIG. 4 shows a flow chart of a method for a terminal device according to embodiments of the invention;
[0083] FIG. 5 shows a communication system according to embodiments of the invention; and
[0084] FIG. 6 shows a signaling diagram illustrating embodiments of the invention;
[0085] FIG. 7 shows a signaling diagram illustrating in detail the overall procedure for providing new data collection requirements and data collection configuration parameters according to embodiments of the invention;
[0086] FIG. 8 shows a signaling diagram illustrating reporting of error during data collection according to embodiments of the invention;
[0087] FIG. 9 shows a flow chart UE behavior for data collection during a PDU session for emergency according to embodiments of the invention; and
[0088] FIG. 10 shows a signaling diagram illustrating revocation of user consent for data collection according to embodiments of the invention.DETAILED DESCRIPTION
[0089] Solutions for data collection and reporting for AI / ML models have been proposed in which a NF will collect data from the UE and then forward the data to the OTT server. The collected data will be sent over the user plane. Some configuration parameters for data collection are expected to be provided to the UE via the communication network and the configuration parameters will be used for data collection and reporting data.
[0090] Furthermore, the OTT server may provide some data collection requirements that the network can use to request the UE to collect and report data. For example, a time window may be provided where the time window represents the time period in which data is to be collected. Another aspect that has been proposed is the size of the data to be collected which is a parameter that the OTT server provides to the UE via the network.
[0091] In the present disclosure, the following issues have been identified in regards of data collection and reporting for AI / ML models in communication systems and networks: 1. The data collection and reporting process can benefit from requirements of the OTT server or the NF without which the process can be quite inefficient and will not meet the use cases. The requirements for data collection and reporting discussed so far are not comprehensive and thus new requirements are proposed that can be used to enhance data collection and reporting based on the needs of the OTT server. 2. In cases, the data collection process may not be possible e.g., during emergency calls, where the UE may have limited resources. These cases need to be addressed. 3. Solutions for user consent revocation have not been addressed. How the UE behaves with respect to any collected data prior to revocation of user consent is also not yet described and this can lead to the UE sending data although the user has revoked consent for data collection.
[0092] Therefore, the present disclosure proposes solutions at least addressing these identified issues. In this respect at least one network device and at least one terminal device are proposed being configured to and capable of: · New data collection and reporting requirements that come from the OTT server and / or from the network are defined and described. · New UE and network behavior with regards to data collection when the UE has an emergency call. · New network behavior regarding selection of UEs that take into account UE availability or network congestion status in order to accept or reject a request for data collection. · New procedures in which revocation of user consent leads to the stop of data collection.
[0093] FIG. 1 shows a network device 100 according to an embodiment of the invention. In the embodiment shown in FIG. 1, the network device 100 comprises a processor 102, a transceiver 104 and a memory 106. The processor 102 is coupled to the transceiver 104 and the memory 106 by communication means 108 known in the art. The network device 100 may be configured for wireless and / or wired communications in a communication system. The wireless communication capability may be provided with an antenna or antenna array 110 coupled to the transceiver 104, while the wired communication capability may be provided with a wired communication interface 112 e.g., coupled to the transceiver 104.
[0094] The processor 102 may be referred to as one or more general-purpose central processing units (CPUs) , one or more digital signal processors (DSPs) , one or more application-specific integrated circuits (ASICs) , one or more field programmable gate arrays (FPGAs) , one or more programmable logic devices, one or more discrete gates, one or more transistor logic devices, one or more discrete hardware components, or one or more chipsets. The memory 106 may be a read-only memory, a random access memory (RAM) , or a non-volatile RAM (NVRAM) . The transceiver 104 may be a transceiver circuit, a power controller, or an interface providing capability to communicate with other communication modules or communication devices. The transceiver 104, memory 106 and / or processor 102 may be implemented in separate chipsets or may be implemented in a common chipset. That the network device 100 is configured to perform certain actions can in this disclosure be understood to mean that the network device 100 comprises suitable means, such as e.g., the processor 102 and the transceiver 104, configured to perform the actions.
[0095] According to embodiments of the invention, the network device 100 is configured to: receive a first message 510 from a server 600, the first message 510 indicating a request for data; determine a data report R according to a reporting configuration and based on data D collected by at least one terminal device 300 in a set of terminal devices 300a, 300b, ..., 300n; and transmit a second message 520 to the server 600, the second message 520 indicating the data report R.
[0096] Furthermore, in an embodiment of the invention, the network device 100 for a communication system 500 comprises a transceiver configured to receive a first message 510 from a server 600, the first message 510 indicating a request for data. The network device 100 comprises a processor configured to determine a data report R according to a reporting configuration and based on data D collected by at least one terminal device 300 in a set of terminal devices 300a, 300b, ..., 300n. The transceiver is configured to transmit a second message 520 to the server 600, the second message 520 indicating the data report R.
[0097] Moreover, in yet another embodiment of the invention, the network device 100 for a communication system 500 comprises a processor and a memory having computer readable instructions stored thereon which, when executed by the processor, cause the processor to: receive a first message 510 from a server 600, the first message 510 indicating a request for data; determine a data report R according to a reporting configuration and based on data D collected by at least one terminal device 300 in a set of terminal devices 300a, 300b, ..., 300n; and transmit a second message 520 to the server 600, the second message 520 indicating the data report R.
[0098] FIG. 2 shows a flow chart of a corresponding method 200 which may be executed in a network device 100, such as the one shown in FIG. 1. The method 200 comprises: receiving 202 a first message 510 from a server 600, the first message 510 indicating a request for data; determining 204 a data report R according to a reporting configuration and based on data D collected by at least one terminal device 300 in a set of terminal devices 300a, 300b, ..., 300n; and transmitting 206 a second message 520 to the server 600, the second message 520 indicating the data report R.
[0099] FIG. 3 shows a terminal device 300 according to an embodiment of the invention. In the embodiment shown in FIG. 3, the terminal device 300 comprises a processor 302, a transceiver 304 and a memory 306. The processor 302 is coupled to the transceiver 304 and the memory 306 by communication means 308 known in the art. The terminal device 300 further comprises an antenna or antenna array 310 coupled to the transceiver 304, which means that the terminal device 300 is configured for wireless communications in a communication system.
[0100] The processor 302 may be referred to as one or more general-purpose CPU, one or more DSPs, one or more ASICs, one or more FPGAs, one or more programmable logic devices, one or more discrete gates, one or more transistor logic devices, one or more discrete hardware components, one or more chipsets. The memory 306 may be a read-only memory, a RAM, or a NVRAM. The transceiver 304 may be a transceiver circuit, a power controller, or an interface providing capability to communicate with other communication modules or communication devices, such as network nodes and network servers. The transceiver 304, the memory 306 and / or the processor 302 may be implemented in separate chipsets or may be implemented in a common chipset. That the terminal device 300 is configured to perform certain actions can in this disclosure be understood to mean that the terminal device 300 comprises suitable means, such as e.g., the processor 302 and the transceiver 304, configured to perform the actions.
[0101] The terminal device herein may be denoted as a user device, a user equipment (UE) , a mobile station, an internet of things (IoT) device, a sensor device, a wireless terminal and / or a mobile terminal, and is enabled to communicate wirelessly in a wireless communication system, sometimes also referred to as a cellular radio system. The UEs may further be referred to as mobile telephones, cellular telephones, computer tablets or laptops with wireless capability. The UEs in this context may be, for example, portable, pocket-storable, hand-held, computer-comprised, or vehicle-mounted mobile devices, enabled to communicate voice and / or data, via a radio access network (RAN) , with another communication entity, such as another receiver or a server. The UE may further be a station, which is any device that contains an IEEE 802.11-conformant media access control (MAC) and physical layer (PHY) interface to the wireless medium (WM) . The UE may be configured for communication in 3GPP related long term evolution (LTE) , LTE-advanced, fifth generation (5G) wireless systems, such as new radio (NR) , and their evolutions, as well as in IEEE related Wi-Fi, worldwide interoperability for microwave access (WiMAX) and their evolutions.
[0102] According to embodiments of the invention, the terminal device 300 is configured to: receive a third message 530 from a network device 100, the third message 530 indicating a request for data based on a data collection configuration; and start collecting data based on the third message 530.
[0103] Furthermore, in an embodiment of the invention, the terminal device 300 for a communication system 500 comprises a transceiver configured to: receive a third message 530 from a network device 100, the third message 530 indicating a request for data based on a data collection configuration. The terminal device 300 comprises a processor configured to start collecting data based on the third message 530.
[0104] Moreover, in yet another embodiment of the invention, the terminal device 300 for a communication system 500 comprises a processor and a memory having computer readable instructions stored thereon which, when executed by the processor, cause the processor to: receive a third message 530 from a network device 100, the third message 530 indicating a request for data based on a data collection configuration; and start collecting data based on the third message 530.
[0105] FIG. 4 shows a flow chart of a corresponding method 400 which may be executed in a terminal device 300, such as the one shown in FIG. 3. The method 400 comprises: receiving 402 a third message 530 from a network device 100, the third message 530 indicating a request for data based on a data collection configuration; and start collecting 404 data based on the third message 530.
[0106] FIG. 5 shows a communication system 500 according to an embodiment of the invention. The communication system 500 in the disclosed embodiment comprises a network device 100 and a terminal device 300 configured to communicate and operate in the communication system 500. For simplicity, the shown communication system 500 only comprises one network device 100 and one terminal device 300. However, the communication system 500 may comprise any number of network devices 100 and any number of terminal devices 300 without deviating from the scope of the invention.
[0107] The network device 100 may use a communication interface for communicating with a communication network such as e.g., a core network. Thus, the network device 100 is configured to communicate with a server 600 such as an application server handling and executing AI / ML architectures and models. The application server may be an OTT server.
[0108] It is shown in FIG. 5 how a server 600 transmits a first message 510 indicating a request for data to the network device 100. Upon reception of the first message 510, the network device 100 determines a data report R according to a reporting configuration and based on data D collected by at least one terminal device 300 in a set of terminal devices 300a, 300b, ..., 300n. Thereafter, the network device 100 transmits a second message 520 to the server 600. The second message 520 indicates the data report R.
[0109] In embodiments of the invention, the reporting configuration may be indicated by the first message 510, or being pre-configured in the network device 100 itself.
[0110] The reporting configuration may indicate one or more of: · Reporting of data from individual terminal devices implying that whenever the network device 100 receives data from any terminal device, the network device 100 forwards the received data to the server 600; · Reporting of data from two or more terminal devices implying that the network device 100 reports data when data has been received from more than one terminal device; · Reporting of data collected after a time period T has elapsed implying that the network device 100 can start a timer with a value T that guards the data reporting period where the network device 100 may receive data from terminal devices during this period. When the period has elapsed, e.g. when the timer expires, the network device 100 may forward any received data from the at least one terminal device to the server 600. If not all of the terminal devices have reported data within the timer period T, the network device 100 may ignore any data received after the timer period T or may send any data received after the timer period T, wherein in the case the network device 100 sends data received after the timer period T the network device 100 may use any of the reporting configuration defined herein while doing so; · Reporting of data collected by a percentage of terminal devices in the set of terminal devices 300a, 300b, ..., 300n implying that the network device 100 may, based on the reporting configuration, send data to the server 600 when data have been reported by a certain percentage of the terminal devices. If more data arrives later, the network device 100 may ignore any data received after the initial report or may send any additional data received after the initial report. The additional data received after the initial report may be reported according to the reporting configuration defined herein; · Reporting of data collected by a subset of terminal devices in the set of terminal devices 300a, 300b, ..., 300n implying that the subset is completely with the set; and · Selection criterion for selection of at least one terminal device in the set of terminal devices 300a, 300b, ..., 300n or in an AoI.
[0111] When the reporting configuration indicates the selection criterion, the network device 100 may use the selection criterion for selecting terminal devices for data collection. Thus, the network device 100 selects at least one terminal device 300 in a set of terminal devices 300a, 300b, ..., 300n for data collection based on the selection criterion. Especially, the selection criterion may indicate a percentage or a ratio of terminal devices not previously been used for data collection. Hence, these terminal devices may be denoted new terminal devices for data collection which forms a percentage or a ratio of the total terminal devices in the set.
[0112] The first message 510 may also indicate further information for data collection and reporting. Thus, in embodiments of the invention, the first message 510 may indicate one or more of: · An identity of at least one terminal device 300; · An identity of an AoI; and · An identity of a use case applicable for data collection. There may be different use cases for which data collection is required where the type of data or the conditions for collecting data can vary based on the associated use case. The server may submit a request for data collection for more than one use case. The identity of a use case can identify which data is meant for which use case and also when the terminal device reports the data. Thus, an identity of a use case can be used to inform the network device and / or server which use case the data is being reported for.
[0113] The communication system 500 may be a communication system according to the 3GPP standard such as e.g., a 5G system or future networks (6G) .
[0114] Further details related to embodiments of the invention will now be described in a 3GPP context. Thus, 3GPP terminology, definitions, expressions and system architecture may be used. Especially, the network device 100 according to embodiments of the invention may in these embodiments be configured to perform any of the described functions of one or more NFs. The terminal device 300 according to embodiments of the invention may be configured to perform any of the described functions of a UE. It may however be noted that embodiments of the invention are not limited thereto.
[0115] Embodiments of the invention can be applied to any suitable communication systems and networks such as 3GPP 4G (EPS) , 5G (5GS) , and 6G networks. The messages referenced in the proposed solution may be NAS messages according to the communication system they apply to and hence the NAS message names may be the same or different depending on the communication system in question. If needed, new types of messages may be defined in comprising new information elements or fields or bits, etc. Thus, all NAS messages may be new or existing NAS messages. However, also other types of communication messages may be employed when implementing the proposed solution disclosed herein.
[0116] In the following disclosed examples, embodiments and aspects of the invention, the network device 100 may comprise one or more devices and one or more functions configured to act in communication systems and networks. Thus, the network device 100 may comprise a NF 140 and / or an AMF 150.
[0117] In examples of the invention, the disclosed solution for sending data collection requirements to the UE may be done over the control plane, e.g., using NAS messages, or over the user plane based on an existing user plane connection between the UE 300 and the NF 140. Mentioned NF 140 which collects data from the UE (s) may be referred to as UE-data repository (UE-DR) , but this is to be considered as an example labeling only and not limited thereto. Hence, other NFs can also be used for performing the corresponding functions. For example, existing NFs such as the current network data analytics function (NWDAF) can be used to collect data from UEs whereas a new NF e.g., a data collection function (DCF) may also be defined. However, for describing further embodiments of the proposed solution the term NF may be used in a 3GPP context.
[0118] It may be noted that the NEF may be used as a NF in between the UE-DR and the OTT server. However, this is to be considered an example only and other NFs may perform the role or function. Alternatively, the OTT server may communicate directly with the UE-DR. All the proposals of the NEF may therefore apply to another network entity.
[0119] FIG. 6 shows a signaling diagram illustrating embodiments of the invention. More specifically, the interaction between a NF 140 and a UE 300 for new data collection and reporting is illustrated. Further, interaction between the NF 140 and the OTT server 600 is also illustrated.
[0120] In step I in FIG. 6, the UE 300 transmits a sixth message 560 to the NF 140. The sixth message 560 indicates the data collection and reporting resources of the UE 300 and thus the capability of the UE in this regard.
[0121] In step II in FIG. 6, the NF 140 receives the sixth message 560. By demodulating and decoding the sixth message 560, the NF 140 obtains the information about the data collection and reporting resources of the UE 300. Therefore, the NF 140 may select which UEs in a set or list of UEs that should collect and report data to the NF 140 and in the end to the OTT server 60.
[0122] It is proposed that the UE 300 may inform the NF 140 about changes in its local resources that can affect the data collection process. The UE 300 may send such indications / reports to the NF 140 using NAS messages that are forwarded by the AMF 150 to the NF 140, or via the user plane based on an existing connection that the UE 300 has with the NF 140.
[0123] The UE 300 may send an indication to the NF 140 to inform the NF 140 about the local resources that are available in the UE 300, such as but not limited to: · A memory size in the UE 300, which may be available or absolute memory capacity and is how much memory the UE 300 may have available for data collection; · A maximum data size that can be collected by the UE 300 describes an upper limit on the data that can be collected by the UE; · A maximum storage time the UE 300 may be able to store data before reporting the data to the NF 140 and the UE may have memory limitations such that it cannot store collected data for a very long time period; · A power saving setting e.g., whether the UE 300 applies power saving settings or not, which may lead to UE 300 unavailability. The UE 300 may also indicate low power which can also mean that UE 300 is unavailable for data collection. The UE 300 may turn off its radio functions or use extended discontinuous reception (DRX) which can impact the UE availability and impact the data collection process. The UE power level may be low such that the UE will need to stop collecting data as it uses memory, processing and power for sending the data.
[0124] The UE 300 may send other indications to the NF 140 when there are changes to these resources e.g., when UE power increases or when UE free memory increases and hence indicates that more data can be collected by the UE. The NF 140 may use this information about the resources from the UE to select UEs for data collection. In one example, the OTT server 600 may provide a request for data collection and may include a data size that is required for the data to be collected. The NF 140 may then select UEs for data collection based on the resources available at the UE 300 as indicated by the UE 100 per the solution above. It may be noted that the above indications may also be sent to the AMF 150 directly and hence the AMF 150 may use these indications for UE selection if the selection is performed by the AMF 150.
[0125] In step III in FIG. 6, the NF 140 transmits a third message 530 to the UE 300. The third message 530 may be considered as a new data collection request. More particularly, the third message 530 indicates a request for data based on a data collecting configuration. The data collecting configuration may be indicated · By the first message 510 i.e. carried or comprised in the first message 510; · Determined by the NF 140; or · Pre-configured in the NF 140.
[0126] In embodiments of the invention, the data collecting configuration may comprise one or more of: · An error reporting for data collection which requires the UE 300 to report any error that the UE 300 encounters as part of data collection. Example errors may relate to lack of resources to collect data, low power levels that can hinder data collection or other problems related to radio conditions that can impact data collection. These are only examples and are not exhaustive. However, any other event which can impact (e.g., stop, pause, terminate, delay, etc. ) data collection which may be considered as an error should therefore lead the UE 300 to report it when encountered or detected. · An identity of a use case applicable for data collection where the identity may represent a data collection request, where optionally the data collection request may be for a particular use case for which the data is needed to train a AI / ML model. It is noted that the OTT server 600 may request collection of more than one data set even for the same use case and as such the identity of a use case may also be used for this scenario to uniquely identify the request and data collected and reported in response to the request. · A priority level for data collection where this indicates the priority for data collection to be performed at the UE 300. The priority level may be represented in any way. For example, “high” or “medium” or “low” priority levels may be defined, or an integer may be defied to designate a high or medium or low priority level. The UE 300 may determine which request for data has highest priority and collect and optionally report the data associated with the highest priority. The UE 300 may also use this priority parameter as a means to prioritize the resources locally in the UE 300 in order to collect data. For example when the UE 300 has limited resources e, and the UE 300 is requested to collect and report more than one data set (e.g. for more than one use case) , the UE 300 may first collect data for the higher priority use case or data set, report the data, and then move on to use the resources for the next data set or use case of the next highest priority, and so on. If more than one use case or data set are of the same priority level, the UE 300 may randomly select one of them to be collected or reported first. · A priority level for data reporting where this indicates which collected data should be reported first even if the data was not actually collected first. For example, a set of data may be used for two use cases and so the same data is collected at the same time for two use cases. However, the UE 300 may report the data for one use case before reporting the data for the other use case although the data used for both use cases is the same. This may assume that the data is reported on a use case basis. The UE 300 may also use this priority level for data reporting parameter to prioritize reporting as explained above.
[0127] The data collecting configuration may also have an urgency level among a plurality of urgency levels which is used by the NF 140. The urgency level may be high or low or any intermediate value between the high and low value. Therefore, the NF 140 may page the terminal device 300 when the urgency level is high. If the urgency is low, the AMF 150 may decide to wait a duration in case the UE transitions to connected mode for other reason, and if not the AMF 150 can page the UE 300. How long the AMF 150 decides to wait is up to AMF configuration and / or policy.
[0128] In step IV in FIG. 6, the UE 100 receives the third message 530 from the NF 140. The UE 300 demodulates and decoded the third message 530 and is informed about the request for data by the NF 140.
[0129] The present disclosure provides different procedures considering not only data collection per see without errors but also scenarios involving emergency services, revocation of user consent and error detection.
[0130] In step V in FIG. 6, the UE 100 completes collection of all requested data according to the data collecting configuration. Thus, the UE 300 transmits a fourth message 540 to the NF 140 in step XI. The fourth message 540 indicates the requested data. The NF 140 receives the fourth message 540 in step XII and demodulates and decodes the fourth message 540 to obtain the data therein.
[0131] In step VI in FIG. 6, an emergency service is initiated in the UE 100. The emergency service may comprise an emergency call of a packet data unit (PDU) session. Generally, the UE 300 stop collecting data upon an establishment of an emergency service by the UE 300. Thereafter, the UE 300 may continue or restart collecting data.
[0132] Thus, in an embodiment of the invention, the UE 300 continues collecting data upon a release of the emergency service, and transmits a fourth message 540 to the NF 140. The fourth message 540 indicates the requested data according to the data collection configuration.
[0133] In another embodiment of the invention, the UE 300 deletes data collected before the establishment of the emergency service. Thereafter, the UE 300 restarts collecting data based on the third message 530 upon the release of the emergency service, and transmits a fourth message 540 to the NF 140. The fourth message 540 indicates the requested data according to the data collection configuration.
[0134] In step VII in FIG. 6, a data collection consent is revoked by a user of the UE 300. The user may be a person handling the UE 300 and thus provides input to the UE 300 e.g. via a user interface such as a GUI. The UE 300 may stop collecting data upon reception of a user input indicating a revocation of a user consent for collecting data. The UE 300 may also delete data collected before the revocation of the user consent. However, before deleting the data, the UE may transmit a fourth message 540 to the NF 140. The fourth message 540 may indicate the data collected before the revocation of the user consent.
[0135] The UE 300 may receive a message from the network e.g. the AMF 150 or UE-DR where the message indicates that the data collection should be terminated. This may be due to revocation of user consent or due to other reasons. When the UE 300 determines that the data collection should be terminated, either by receiving an explicit message from the network or via the user interaction with the UE, the UE 300 may stop collecting data and may also delete data collected before the revocation of the user consent. However, before deleting the data, the UE 300 may transmit a fourth message 540 to the NF 140. The fourth message 540 may indicate the data collected before the revocation of the user consent.
[0136] In step VIII in FIG. 6, an error event is detected by the UE 300 when collecting data requested by the NF 140. Thus, the UE 300 transmits a seventh message 570 to the NF 140, where the seventh message 570 indicates an error event during the data collection. The seventh message 570 may also indicate data collected until the error event during the data collection.
[0137] In step IX in FIG. 6, the NF 140 receives the seventh message 570 from the UE 300. The NF 140 demodulates and decodes the seventh message 570 and thus is informed about the error event at the UE 300.
[0138] The NF 300 in step IX informs the OTT server 600 about the error event by transmitting an eight message 580 to the OTT server 600. The eight message 580 indicates the error event during data collection. If the seventh message 570 also included the data collected until the error event, this data may also be forwarded by the NF 140 to the OTT server 600. In other words, the eight message 580 may also indicate data collected until the error event during the data collection of the UE 300 in such cases.
[0139] In step X in FIG. 6, the OTT server 600 receives the eight message 580 from the NF 140. The OTT server 600 demodulates and decodes the eight message 580 to obtain the information therein.
[0140] In step XI in FIG. 6, as previously mentioned, the UE 300 transmits a fourth message 540 to the NF 500. The fourth message 540 indicates or comprises all requested data or a part of the requested data depending on the scenario and use case, e.g. completed data collection, emergency services, revocation of user consent and error detection.
[0141] The present disclosure also provides an ACK / NACK procedure between the NF 140 and the UE 300 for handling transmission errors and other faults in regards of the fourth message 540.
[0142] In step XIII in FIG. 6, the NF 140 therefore transmits a fifth message 550 to the UE 300. The fifth message 550 indicates either ACK of correctly received data in the fourth message 540 or a NACK of incorrectly received data in the fourth message 540.
[0143] In step XIV in FIG. 6, the UE 300 receives the fifth message 550 from the NF 140. The UE 300 demodulates and decodes the fifth message 550 and obtains the information therein. Depending on whether ACK or NACK is signaled by the NF 140, the UE 300 proceeds in different ways.
[0144] If ACK is signaled, the UE 300 may delete already collected data stored in the UE 300. However, if NACK is signaled, the UE 300 may retransmit the fourth message 540 to the NF 140, or restart collecting data based on the third message 530. The UE 300 may therefore collect and send data to the NF 140. The UE 300 saves the data until a response is received from the NF 140. If the NF 140 have responded with an ACK, this means that data correctly has been received by the NF 140. Thus, the UE 300 can delete the saved data. If however the NF 140 responded with a NACK, this means that data was not correctly received at the NF 140. The UE 300 may in this case react by re-transmitting saved data, and delete the saved data and then re-collect data and send the re-collected data to the NF 140.
[0145] In the following disclosure aspects of the invention are described more in detail with reference to Figs. 7 to 10.
[0146] FIG. 7 shows a signaling diagram illustrating in detail an overall procedure for providing data collection requirements and data collection configuration parameters according to embodiments of the invention. Generally, the disclosed solution may follow an overall procedure, where an objective may be to clarify how the requirements from the OTT server 600 translate into actions in the network device 100 and the UE 300. Some of the new requirements may be implemented as OTT server requirements while other requirements may be requirements provided by the network device 100. However, any combination of these requirements may be submitted by the OTT server 600 or by the network device 100.
[0147] Step 1 in FIG. 7: the OTT server 600 submits a request for data collection and may provide any of the configuration parameters listed above in a first message 510. For example, the OTT server 600 may provide a configuration parameter which represents a time duration within which it is acceptable to get any stored data from the network if the data has been stored for a period that does not exceed the indicated time duration. The OTT server 600 may provide other requirements or configuration parameters for data collection as listed earlier. The OTT server 600 may also provide a list of UEs 300 for which the data collection is to be performed.
[0148] Step 2 in FIG. 7: the NEF 730 verifies if the OTT server 600 is allowed or authorized to submit the request. The NEF 730 may verify with the UDM 720 if the request from the OTT server 600 can be authorized.
[0149] Step 2a in FIG. 7: if for a UE 300, or optionally part of a list of UEs provided by the OTT server 600, the user consent does not exist for the data collection, or a user does not consent to data collection and reporting, the NEF 730 rejects the request from the OTT server 600. The rejection may be for all UEs or for a subset of UEs in a set of UEs. The NEF 730 indicates to the OTT server the UEs for which user consent is not available.
[0150] Step 3 in FIG. 7: the NEF 730 forwards the request to the NF 140 and this includes all the parameters which are received from the OTT server 600. The NEF 730 may indicate which parameters are addressed for the UE 300 and which are addressed for the NF 140. For example, some parameters such as which use case data needs to be reported first, or whether the UE 300 have to report errors in data collection, etc. are for the UE 300. These parameters may be indicated by the NEF 730 as UE related parameters. Alternatively, the NEF 730 may forward all the parameters as received from the OTT server 600 and let the NF 140 make the distinction between parameters targeted for the UE 300 or parameters targeted for the network.
[0151] Step 4 in FIG. 7: if the NF 140 receives a parameter representing the maximum duration for which data has been stored in the NF 140. Thus, the NF 140 verifies if there is stored data, for at least one UE or AoI, which meets the time duration requirement. If data has been stored less than the time duration requirement, the NF 140 may forward the data to the NEF 730 and the OTT server 600, or to the OTT server 600 via the NEF 730, as described in Step 5 and Step 6. Thus, the data D collected by terminal device 300 meets a data storage time requirement in this case.
[0152] However, if collected data has been stored in the NF 140 for a time duration that exceeds the storage time requirement received from the NEF 730 or the OTT server 600, then the NF 140 may trigger new data collection requests sent to one or more UEs. The NF 140 may in this case delete any stored data in the NF 140 since new data collection will be initiated. The NF 140 may act upon any other parameters which may be received as described per parameter. For example, if an urgency level is high, then the NF 140 may perform UE selection and may send a message to the UE 300 for data collection via the user plane or the control plane.
[0153] Step 5 in FIG. 7: the NF 140 forwards data to the NEF 730 which is to be sent to the OTT server 600. This happens if the storage time requirement discussed above is satisfied.
[0154] Step 6 in FIG. 7: the NEF 730 forwards the data to the OTT server 600.
[0155] Step 7 in FIG. 7: The NF 140 sends a request to the AMF 150 for data collection, where the request may be for an individual UE or a set of UEs. The NF 140 may also inform the AMF 150 that the urgency level is high. The reception of a high urgency level indication from the NF 140 triggers the AMF 150 to prioritize the request and hence can page at least one UE immediately in order to initiate data collection and optionally send a necessary NAS message to the UE containing the reporting configuration or trigger the user plane establishment in case the reporting configuration is sent over the user plane. The high urgency level may also trigger the AMF 150 to prioritize UE selection, if this is an AMF responsibility, and trigger the selected UEs for data collection e.g., by paging the UEs and / or forwarding necessary NAS messages with control information. The NF 140 may provide parameters for the UE 300 and explicitly indicate this which triggers the AMF 150 to send these parameters in a NAS message to the UE 300. Alternatively, the NF 140 may send these parameters to the UE 300 via the user plane when assumed that there is a user plane connection that can be established between the UE 300 and the NF 140.
[0156] Step 8 in FIG. 7: the AMF 150 receives a request for data collection for at least one UE. The AMF 150 may perform UE selection based on local policies. For a set of UEs, either selected or within an AoI, the AMF 150 may determine whether to page the UEs for data collection at least based on the urgency parameter received from the NF 140. If the urgency parameter is set as high, the AMF 150 can page the UEs immediately. If the urgency parameter is set as low, the AMF 150 can wait for an implementation dependent time to page the UEs if the UEs do not transit to connected mode for other reasons. The urgency level may also inform the AMF 150 that UE selection, if it is an AMF responsibility, should be done quickly or not based on the urgency level value and also take the necessary actions towards the selected UEs as previously explained.
[0157] Step 9 in FIG. 7: the UE 300 is in connected mode.
[0158] Step 10a in FIG. 7: the AMF 150 may forward a NAS message to the UE 300, which includes data collection configuration and reporting parameters as described previously. For every configuration and parameter, the UE 300 behaves accordingly. For example, if the UE 300 receives information about data collection for more than one use case and the UE 300 is requested to report data for one of the use cases before another in an order, the UE 300 may ensure that the reporting, and optionally the collection of the data, is first performed for the use case for which the network indicated to be desired first, and so on in the set order. If the UE 300 has limited resources for data collection, these resources may be used by the UE 300 to collect and report the necessary data for the first desired use case, after which the UE 300 may delete the data in order to free up memory and then move on to collect and report data for the second use case that is desired by the network. If the UE 300 receives a configuration to report errors or error events as part of data collection, the UE 300 may comply with this as described later in this section. In general, the description provided for each of the parameters that are meant for the UE 300 can be considered as proposed new behavior when receiving the parameter in question by the UE.
[0159] Step 10b in FIG. 7: the AMF 150 may inform the radio access network (RAN) 710 that data collection should be triggered for a UE 300 in question. This can be a result of the indication from the NF 140.
[0160] Step 11 in FIG. 7: the UE 300 performs data collection according to the data collecting configuration which may include as preciously stated, an error reporting for data collection, an identity of a use case applicable for data collection, a priority level for data collection, and a priority level for data reporting.
[0161] Step 12 in FIG. 7: the UE 300 reports the collected data according to the data collecting configuration over the user plane to the NF 140.
[0162] Step 13 in FIG. 7: the NF 140 forwards the reported data to the NEF. The NF 140 may forward the data in accordance with a data reporting strategy and / or configuration parameters which may have been previously received from the OTT server 600 via the NEF 730. For example, the NF 140 may forward the data as received from individual UEs, or after a certain percentage of UEs report data to the NF 140, or after a certain time period has elapsed. The NF 140 may behave as described for the related parameter herein. The data report may also include a list of UEs from which the data is collected.
[0163] Step 14 in FIG. 7: the NEF 730 forwards the received data to the OTT server 600.
[0164] FIG. 8 shows a signaling diagram illustrating reporting of error event during data collection. In the case the UE 300 receives a data collection requirement or configuration parameter for data collection such that the UE 300 is requested to report any errors encountered during data collection, the UE 300 should inform the NF 140 when any error event is encountered. It is remembered that the error reporting for data collection may be comprised in the data collecting configuration.
[0165] The error events may include, but are not limited to, lack of memory, lack of power, or lack of other resources that hinder data collection, or other problems related to radio link failure or rejections from the network that would not permit data to be collected. The error event may not be reported immediately e.g., if the network rejects the UE 300 due to congestion, and in such cases the UE 300 can save the error event and report at a later time instance.
[0166] It may also be noted that the parameters or configuration provided to the UE 300 may also indicate if the UE 300 should send any data that has already been collected up until the error event has been detected. If so, the UE 300 can include the data collected so far in an error report. The UE 300 may also save and report the time instance or period when the error event was encountered or detected, the location of the error event e.g., tracking area identity, global cell identity or the error event, GPS position for the error event, etc. If the NF 140 receives the error report from the UE 300, the NF 140 may save the indicated error event and may also inform the OTT server 600 about the error event associated with at least one reporting UE.
[0167] In step 1 in FIG. 8: the UE 300 receives a parameter requesting to report error events encountered during data collection. The UE 300 records this requirement or configuration and starts to collect data.
[0168] Step 2 in FIG. 8: the UE 300 detects that an error event has occurred during data collection e.g., lack of enough memory or low power in the UE 300 such that data collection cannot be continued by the UE 300.
[0169] Step 3 in FIG. 8: the UE 300 reports the error event to the NF 140. The UE 300 may do so by using a NAS message which may be sent to the AMF 150, but the UE 300 can indicate in the NAS message that the content is for the NF 140 and based on such indication the AMF 150 forwards the content to the NF 140, where in this case the content may include at least an error event report. Alternatively, if the UE 300 is using the user plane to communicate with the NF 140 regarding the control plane aspects of data collection, e.g., error reporting or other aspects, the UE 300 may also send the error report using the user plane. The UE 300 may regardless of using NAS or user plane indicate the type of error event that led to the error report e.g., lack of memory or other resources. The UE 300 may also include a time stamp of when the error event was determined to have occurred and may also indicate a location where the error event occurred. The location may be in any form that represents the UE location. The NF 140 may keep a local note of the error event, optionally with the timer and location associated with the error event. It is further noted that the UE 300 may also send any collected data thus far e.g., based on configuration information in the UE 300. Alternatively, the UE 300 may delete the data collected when the error event has been encountered such that the data collection cannot be completed and thus not reported.
[0170] Step 4 in FIG. 8: the NF 140 forwards the error report to the NEF, and may also include data from the UE 300 if previously received by the NF 140.
[0171] Step 5 in FIG. 8: the NEF 730 forwards the error report to the OTT server 600 and optionally includes data received from the NF 140.
[0172] FIG. 9 shows a flow chart for UE behavior for data collection during a PDU session in emergency situations. Generally, the UE 300 may already be performing data collection or may have been configured to collect data when an emergency situation occurs. The UE 300 may have an emergency call and hence may establish a PDU session for emergency services. When the UE 300 establishes a PDU session for emergency services, the UE 300 stops the data collection procedure. The termination of data collection may be based on default UE behavior or explicit indication from the network via control signaling, where the network in this regard may refer to any NF such as the AMF, SMF, etc.
[0173] Once the PDU session for emergency call has been released, the UE 300 may re-start the data collection procedure. The UE 300 may save any data collected before the establishment of the PDU session for emergency call and hence may continue to collect data on top of what has already been collected prior to the emergency call. Alternatively, the UE 300 may delete the collected data and restart collecting data from the beginning when the PDU session for emergency call has been released.
[0174] If the network, e.g. the AMF 150, is responsible for UE selection, or gets a request to trigger a UE for data collection, the AMF 150 may verify if a certain UE in question has a PDU session for emergency call running. If so, the AMF 150 may reject the request for the UE, or may inform the NF 140 that as part of the list of UEs which the NF 140 may have selected, in which at least one UE has not been used for data collection due to the UE being unavailable. The AMF 150 may indicate and inform the reason for the unavailability, or the AMF 150 may not indicate the reason other than general indication of the UE being unavailable. The AMF 150 may also choose to not select a UE for data collection based on its mobility. For example, the AMF150 may know that a UE 300 is performing handover such that the UE 300 may be leaving the 5G system to another system or the UE 300 may be leaving an AoI and entering another area which is not a desired area for data collection. The AMF 150 may, based on such knowledge, decide to not select the UE 300 in question. The AMF 150 may therefore select UEs for which there is no current handover ongoing. The AMF 150 may also decide to not choose the UE 300 for which a back-off timer (or congestion control timer) has been provided to it, or may not choose the UE 300 for which the AMF 150 knows that the UE 300 is unavailable either due to congestion or power saving mechanisms being used by the UE 300.
[0175] FIG. 10 shows a signaling diagram illustrating revocation of user consent for data collection. The user of the UE 300 may revoke consent for data collection e.g. due to privacy considerations. When this occurs, the UE 300 terminates data collection and optionally deletes any data which has been collected prior to the revocation of the user consent. Alternatively, the UE 300 may report any data which was collected prior to the revocation of the user consent but may not collect any new data thereafter due to the revocation. The UE 300 may also determine what to do with data previously collected before the revocation of the user consent based on a pre-configuration in the UE 300 or an explicit indication from the network to either report or not report and optionally delete the data which has been collected before the revocation of the user consent.
[0176] Step 1 in FIG. 10: the UE 300 may be involved in data collection or may have received data collection configuration parameters.
[0177] Step 2 in FIG. 10: the UDM 720 determines that a user of the UE 300 has revoked its consent for data collection.
[0178] Step 3 in FIG. 10: the UDM 720 informs the NF 140 about the revocation of the user consent for at least one UE 300.
[0179] Step 4 in FIG. 10: the NF 140 sends a request to the AMF 150 which can include an indication of user revocation to the AMF 150 and may also include the indication that is to be forwarded to the UE 300.
[0180] Step 5 in FIG. 10: the AMF 150 forwards the indication from the NF 140 to the UE 300 using a NAS message. The indication informs the UE 300 to terminate data collection or informs the UE 300 to terminate data collection due to user consent revocation. The NAS message may also include an action to be performed by the UE 300 with respect to any data that has been collected thus far.
[0181] The action may be to delete any collected data, or to report any collected data which was collected before the revocation of the consent, or to delete any reported data if the data was collected before the revocation with a certain time period. Mentioned time period may be explicitly indicated or may be pre-configured in the UE 300. It is noted that the information about how to handle data collected before the revocation of the user consent may also be sent to the UE 300 as part of the data collection configuration parameters. Although the indication may have been sent to the UE 300 using NAS messages, the NF 140 may also send the indication and / or information about how to handle data collected before revocation of user consent using the user plane. As such, the present solution is not restricted to using NAS messages as a means to transport the information to the UE 300.
[0182] Step 6a in FIG. 10: the AMF 150 may inform the RAN 710 to stop any data collection procedures for the UE 300.
[0183] Step 6b in FIG. 10: the RAN 710 may send an instruction to the UE 300 terminating the data collection or release any radio configurations that were used for data collection.
[0184] Step 7 in FIG. 10: when the UE 300 determines that the user consent has been revoked the UE 300 stops / terminates the data collection process. The UE 300 may determine to delete any data that has been collected before the revocation of the user consent, or may determine to send the data collected prior to the revocation. Note that the UE 300 may locally determine that the user consent has been revoked e.g. based on the user interaction with the graphical user interface (GUI) . This may happen after step 1 in FIG. 10. When this occurs, the UE 300 may take the actions proposed in step 7 in FIG. 10 directly i.e., without necessarily waiting for a message to be received from the AMF or the NF 140 about user revocation. The UE 300 can also then behave as described in Step 8 in FIG. 10 even when the revocation is determined to have been performed locally within the UE 300.
[0185] Step 8 in FIG. 10: the UE 300 sends an indication or an acknowledgement of termination of data collection. The UE 300 may also send already collected data as described above. The UE 300 may in such case send the collected data to the AMF but the collected data is destined for the NF 140. The UE 300 may send the collected data in a NAS message. Alternatively, the UE 300 may send the collected data indication to the NF 140 using the user plane although this is not shown in the FIG.
[0186] Step 9 in FIG. 10: the AMF 150 forwards the content of the NAS message to the NF 140.
[0187] Step 10 in FIG. 10: the NF 140 may acknowledge the termination of data collection indication to the UDM 720, or may indicate to the UDM 720 that the UE 300 has terminated data collection due to user consent revocation.
[0188] Step 11a in FIG. 10: the UDM 720 informs the NEF 730 about the termination of data collection due to user consent revocation and requests the NEF 730 to forward the indication to the OTT server 600. It is noted that the NF 140 may be the entity that informs the NEF 730 and requests the NEF 730 to forward the indication to the OTT server 600.
[0189] Step 11b in FIG. 10: the NEF 730 indicates to the OTT server 600 that at least one UE 300 has terminated data collection due to revocation of user consent.
[0190] Moreover, any method according to embodiments of the invention may be implemented in a computer program, having code means, which when run by processing means causes the processing means to execute the steps of the method. The computer program is included in a computer readable medium of a computer program product. The computer readable medium may comprise essentially any memory, such as previously mentioned a ROM, a PROM, an EPROM, a flash memory, an EEPROM, or a hard disk drive.
[0191] Moreover, it should be realized that the network device and the terminal device comprise the necessary communication capabilities in the form of e.g., functions, means, units, elements, etc., for performing or implementing embodiments of the invention. Examples of other such means, units, elements and functions are: processors, memory, buffers, control logic, encoders, decoders, rate matchers, de-rate matchers, mapping units, multipliers, decision units, selecting units, switches, interleavers, de-interleavers, modulators, demodulators, inputs, outputs, antennas, amplifiers, receiver units, transmitter units, DSPs, TCM encoder, TCM decoder, power supply units, power feeders, communication interfaces, communication protocols, etc. which are suitably arranged together for performing the solution.
[0192] Therefore, the processor (s) of the network device and the terminal device may comprise, e.g., one or more instances of a CPU, a processing unit, a processing circuit, a processor, an ASIC, a microprocessor, or other processing logic that may interpret and execute instructions. The expression “processor” may thus represent a processing circuitry comprising a plurality of processing circuits, such as e.g., any, some or all of the ones mentioned above. The processing circuitry may further perform data processing functions for inputting, outputting, and processing of data comprising data buffering and device control functions, such as call processing control, user interface control, or the like.
[0193] Finally, it should be understood that the invention is not limited to the embodiments described above, but also relates to and incorporates all embodiments within the scope of the appended independent claims.
Claims
1.A network device (100) configured to:receive a first message (510) from a server (600) , the first message (510) indicating a request for data;determine a data report (R) according to a reporting configuration and based on data (D) collected by at least one terminal device (300) in a set of terminal devices (300a, 300b, ..., 300n) ; andtransmit a second message (520) to the server (600) , the second message (520) indicating the data report (R) .2.The network device (100) according to claim 1, wherein the reporting configuration indicates any of: reporting of data from individual terminal devices, reporting of data from two or more terminal devices, reporting of data collected after a time period (T) has elapsed, reporting of data collected by a percentage of terminal devices in the set of terminal devices (300a, 300b, ..., 300n) , reporting of data collected by a subset of terminal devices in the set of terminal devices (300a, 300b, ..., 300n) , and a selection criterion for selection of at least one terminal device in the set of terminal devices (300a, 300b, ..., 300n) or in an area of interest, AoI.3.The network device (100) according to claim 2, wherein the reporting configuration at least indicates the selection criterion, and wherein the selection criterion indicates a percentage or a ratio of terminal devices not previously been used for data collection; and wherein the network device (100) is configured to:select at least one terminal device (300) in the set of terminal devices (300a, 300b, ..., 300n) for data collection based on the selection criterion.4.The network device (100) according to claim 2 or 3, wherein the reporting configuration is:indicated by the first message (510) , orpre-configured in the network device (100) .5.The network device (100) according to any one of the preceding claims, wherein the first message (510) indicates any of: an identity of at least one terminal device (300) , an identity of an AoI, and an identity of a use case applicable for data collection.6.The network device (100) according to any one of the preceding claims, wherein the data (D) collected by the terminal device (300) meets a data storage time requirement.7.The network device (100) according to claim 6, wherein the data storage time requirement defines a time period the data (D) collected by the terminal device (300) has been stored in the network device (100) .8.The network device (100) according to any one of the preceding claims, configured to:transmit a third message (530) to at least one terminal device (300) in the set of terminal devices (300a, 300b, ..., 300n) , the third message (530) indicating a request for data based on a data collecting configuration.9.The network device (100) according to claim 8, wherein the data collecting configuration comprises any of: an error reporting for data collection, an identity of a use case applicable for data collection, a priority level for data collection, and a priority level for data reporting.10.The network device (100) according to claim 9, wherein the data collecting configuration has an urgency level; and wherein the network device (100) is configured to:page the terminal device (300) when the urgency level is high.11.The network device (100) according to claim 10, wherein the data collecting configuration isindicated by the first message (510) ,determined by the network device (100) , orpre-configured in the network device (100) .12.The network device (100) according to any one of claims 8 to 11, configured to:receive a fourth message (540) from the terminal device (300) , the fourth message (540) indicating at least one part of the requested data.13.The network device (100) according to claim 12, configured to:transmit a fifth message (550) to the terminal device (300) upon reception of the fourth message (540) , the fifth message (550) indicating an acknowledgement, ACK, of correctly received data in the fourth message (540) or a negative acknowledgement, NACK, of incorrectly received data in the fourth message (540) .14.The network device (100) according to any one of the preceding claims, configured to:receive a sixth message (560) from the terminal device (300) , the sixth message (560) indicating data collection and reporting resources of the terminal device (300) ; andselect at least one terminal device (300) in the set of terminal devices (300a, 300b, ..., 300n) for data collection based on the sixth message (560) .15.The network device (100) according to claim 14, wherein the data collection and reporting resources comprises any of: a memory size, a maximum data size, a maximum storage time, a power level description, and a power saving setting.16.The network device (100) according to any one of the preceding claims, configured to:receive a seventh message (570) from the terminal device (300) , the seventh message (570) indicating an error event during data collection.17.The network device (100) according to claim 16, wherein the seventh message (570) indicates data collected until the error event during the data collection.18.The network device (100) according to claim 16 or 17, configured to:transmit an eight message (580) to the server (600) , the eight message (580) indicating the error event during data collection.19.The network device (100) according to claim 18, wherein the eight message (580) indicates data collected until the error event during the data collection.20.The network device (100) according to any one of the preceding claims, wherein the server (600) is an application server and the data is input data to an artificial intelligence / machine learning, AI / ML, model.21.A terminal device (300) configured to:receive a third message (530) from a network device (100) , the third message (530) indicating a request for data based on a data collection configuration; andstart collecting data based on the third message (530) .22.The terminal device (300) according to claim 21, wherein the data collection configuration comprises any of: an error reporting for data collection, an identity of a use case applicable for data collection, a priority level for data collection, and a priority level for data reporting.23.The terminal device (300) according to claim 21 or 22, configured to:complete collecting data based on the third message (530) ; andtransmit a fourth message (540) to the network device (100) , the fourth message (540) indicating the requested data according to the data collection configuration.24.The terminal device (300) according to claim 21, configured to:stop collecting data upon an establishment of an emergency service by the terminal device (300) .25.The terminal device (300) according to claim 24, configured to:continue collecting data upon a release of the emergency service; andtransmit a fourth message (540) to the network device (100) , the fourth message (540) indicating the requested data according to the data collection configuration.26.The terminal device (300) according to claim 24, configured to:delete data collected before the establishment of the emergency service;restart collecting data based on the third message (530) upon the release of the emergency service; andtransmit a fourth message (540) to the network device (100) , the fourth message (540) indicating the requested data according to the data collection configuration.27.The terminal device (300) according to any one of claims 24 to 26, wherein the emergency service comprises an emergency call of a packet data unit, PDU, session.28.The terminal device (300) according to any one of claims 24 to 27, configured to:stop collecting data upon reception of a user input (710) indicating a revocation of a user consent for collecting data by the terminal device (300) .29.The terminal device (300) according to claim 28, configured to:delete data collected before the revocation of the user consent.30.The terminal device (300) according to claim 28 or 29, configured to:transmit a fourth message (540) to the network device (100) , the fourth message (540) indicating data collected before the revocation of the user consent.31.The terminal device (300) according to any one of claims 23 to 30, configured to:receive a fifth message (550) from the network device (100) after having transmitted the fourth message (540) , the fifth message (550) indicating an ACK of correctly received data in the fourth message (540) or a NACK of incorrectly received data in the fourth message (540) ;delete collected data stored in the terminal device (300) when the fifth message (550) indicates the ACK; andretransmit the fourth message (540) to the network device (100) when the fifth message (550) indicates the NACK, orrestart collecting data based on the third message (530) when the fifth message (550) indicates the NACK.32.The terminal device (300) according to any one of claims 21 to 31, configured to:transmit a sixth message (560) to the network device (100) , the sixth message (560) indicating data collection and reporting resources of the terminal device (300) .33.The terminal device (300) according to claim 32, wherein the data collection and reporting resources comprises any of: a memory size, a maximum data size, a maximum storage time, a power level description, and a power saving setting.34.The terminal device (300) according to any one of claims 21 to 33, configured to:transmit a seventh message (570) to the network device (100) , the seventh message (570) indicating an error event during the data collection.35.The terminal device (300) according to claim 34, wherein the seventh message (570) indicates data collected until the error event during the data collection.36.A method (200) for a network device (100) , the method (200) comprises:receiving (202) a first message (510) from a server (600) , the first message (510) indicating a request for data;determining (204) a data report (R) according to a reporting configuration and based on data (D) collected by at least one terminal device (300) in a set of terminal devices (300a, 300b, ..., 300n) ; andtransmitting (206) a second message (520) to the server (600) , the second message (520) indicating the data report (R) .37.A method (400) for a terminal device (300) , the method (400) comprising:receiving (402) a third message (530) from a network device (100) , the third message (530) indicating a request for data based on a data collection configuration; andstart collecting (404) data based on the third message (530) .38.A computer program with a program code for performing a method according to claim 36 or 37 when the computer program runs on a computer.
