CN117792647A

CN117792647A - User-level data management method, device, communication equipment and readable storage medium

Info

Publication number: CN117792647A
Application number: CN202211154186.7A
Authority: CN
Inventors: 袁雁南; 鲍炜; 金巴·迪·阿达姆·布巴卡
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2022-09-21
Filing date: 2022-09-21
Publication date: 2024-03-29
Also published as: WO2024061207A1

Abstract

The application discloses a user-level data management method, a device, communication equipment and a readable storage medium, which belong to the technical field of wireless communication, and the user-level data management method comprises the following steps: the user equipment performs a first operation comprising at least one of: transmitting first authorization information, wherein the first authorization information is used for indicating that the collection of the data of the first user is allowed or not allowed, and/or indicating that the storage of the data of the first user is allowed or not allowed; and sending second authorization information, wherein the second authorization information is used for indicating whether the data of the first user is allowed or not allowed to be provided.

Description

User-level data management method, device, communication equipment and readable storage medium

Technical Field

The application belongs to the technical field of wireless communication, and particularly relates to a user-level data management method, a device, communication equipment and a readable storage medium.

Background

The existing user-level data collection is triggered and collected by network-level functions such as a core network, a wireless access network or a network manager and the like according to the needs, and the data is collected to a network-level node. The collected data is mainly data generated by users in the mobile communication network and is mainly used for network service optimization and the like. In the existing minimization of drive test user consent (MDT user present), data collection, storage and use by the network is agreed at the same time, i.e. the data collected by the network is completely determined by the network how to store and use.

Future user-level data may include, in addition to data in existing communication procedures, data perceived in the sense of general integration, data calculated in the computing service, and so on. On the one hand, the data is richer, and on the other hand, some data is more relevant to the security privacy of the user. Therefore, how to meet the demand of users on data, rather than how to store and use collected data, which is decided by the network, is a problem to be solved.

Disclosure of Invention

The embodiment of the application provides a management method, a device, communication equipment and a readable storage medium for user-level data, which can solve the problem that the existing network decides how to store and use collected data and does not meet the requirement of users on the data.

In a first aspect, a method for managing user-level data is provided, including:

the user equipment performs a first operation comprising at least one of:

transmitting first authorization information, wherein the first authorization information is used for indicating that the collection of the data of the first user is allowed or not allowed, and/or indicating that the storage of the data of the first user is allowed or not allowed;

and sending second authorization information, wherein the second authorization information is used for indicating whether the data of the first user is allowed or not allowed to be provided.

In a second aspect, a method for managing user-level data is provided, including:

the first node performs a second operation comprising at least one of:

determining whether to collect data of a first user or not according to authorization of user equipment of the first user and/or subscription information of the first user, or whether to collect the data of the first user and store the data of the first user to a second node;

and determining whether to provide the data of the first user according to second authorization information and/or subscription information of the first user, which are sent by the user equipment of the first user, wherein the second authorization information is used for indicating whether to allow or not allow the first node to provide the data of the first user.

In a third aspect, a method for managing user-level data is provided, including:

the second node performs a third operation, the third operation comprising at least one of:

determining whether to store data of a first user according to authorization of user equipment of the first user and/or subscription information of the first user;

and determining whether to provide the data of the first user according to the second authorization information and/or the subscription information of the first user sent by the user equipment of the first user.

In a fourth aspect, there is provided a management apparatus for user-level data, comprising:

an execution module for executing a first operation, the first operation comprising at least one of:

In a fifth aspect, there is provided a management apparatus for user-level data, including:

an execution module for performing a second operation, the second operation comprising at least one of:

In a sixth aspect, there is provided a management apparatus for user-level data, including:

an execution module for performing a third operation, the third operation comprising at least one of:

In a seventh aspect, there is provided a user equipment comprising a processor and a memory storing a program or instructions executable on the processor, which when executed by the processor, performs the steps of the method according to the first aspect.

In an eighth aspect, there is provided a user equipment comprising a processor and a communication interface, wherein the processor is configured to perform a first operation, the first operation comprising at least one of:

In a ninth aspect, a communications device is provided, the network side device comprising a processor and a memory storing a program or instructions executable on the processor, which when executed by the processor implement the steps of the method as described in the first or second aspect.

In a tenth aspect, a communication device is provided, comprising a processor and a communication interface, wherein the processor is configured to perform a second operation, the second operation comprising at least one of:

In an eleventh aspect, a communication device is provided, including a processor and a communication interface, wherein the processor is configured to perform a third operation, the third operation including at least one of:

In a twelfth aspect, there is provided a readable storage medium having stored thereon a program or instructions which when executed by a processor implement the steps of the method of the first, second or third aspects.

In a thirteenth aspect, there is provided a chip comprising a processor and a communication interface coupled to the processor, the processor being for running a program or instructions to implement the method of the first, second or third aspects.

In a fourteenth aspect, there is provided a computer program/program product stored in a storage medium, the computer program/program product being executable by at least one processor to perform the steps of the method according to the first, second or third aspects.

In the embodiment of the application, the user authorizes the collection, storage and/or use of the user-level data, but the network decides how to store and use the collected user-level data, so that the requirement of the user on the self data is met, and the control degree of the user on the self data is improved.

Drawings

Fig. 1 is a block diagram of a wireless communication system to which embodiments of the present application are applicable;

FIG. 2 is a schematic diagram of NWDAF collection data;

FIG. 3 is a schematic diagram of the NWDAF providing data analysis results;

FIG. 4 is a flowchart of a method for managing user-level data according to an embodiment of the present application;

FIG. 5 is a second flow chart of a method for managing user-level data according to an embodiment of the present disclosure;

FIG. 6 is a third flow chart of a method for managing user-level data according to an embodiment of the present disclosure;

fig. 7 and 8 are schematic flow diagrams of a method for managing user-level data according to embodiment 1 of the present application;

fig. 9 and 10 are schematic flow diagrams of a method for managing user-level data according to embodiment 2 of the present application;

fig. 11 is a flow chart of a method for managing user-level data according to embodiment 3 of the present application;

fig. 12 is one of schematic structural diagrams of a management device for user-level data according to an embodiment of the present application;

FIG. 13 is a second schematic diagram of a user-level data management device according to an embodiment of the present disclosure;

FIG. 14 is a third schematic diagram of a management device for user-level data according to an embodiment of the present application;

fig. 15 is a schematic structural diagram of a communication device according to an embodiment of the present application;

fig. 16 is a schematic hardware structure of a user equipment according to an embodiment of the present application;

fig. 17 is a schematic diagram of a hardware structure of a network side device according to an embodiment of the present application;

fig. 18 is a second schematic hardware structure of the network side device according to the embodiment of the present application.

Detailed Description

Technical solutions in the embodiments of the present application will be clearly described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application are within the scope of the protection of the present application.

The terms first, second and the like in the description and in the claims, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the terms so used are interchangeable under appropriate circumstances such that the embodiments of the application are capable of operation in sequences other than those illustrated or otherwise described herein, and that the terms "first" and "second" are generally intended to be used in a generic sense and not to limit the number of objects, for example, the first object may be one or more. Furthermore, in the description and claims, "and/or" means at least one of the connected objects, and the character "/" generally means a relationship in which the associated object is an "or" before and after.

It is noted that the techniques described in embodiments of the present application are not limited to long term evolution (Long Term Evolution, LTE)/LTE evolution (LTE-Advanced, LTE-a) systems, but may also be used in other wireless communication systems, such as code division multiple access (Code Division Multiple Access, CDMA), time division multiple access (Time Division Multiple Access, TDMA), frequency division multiple access (Frequency Division Multiple Access, FDMA), orthogonal frequency division multiple access (Orthogonal Frequency Division Multiple Access, OFDMA), single carrier frequency division multiple access (Single-carrier Frequency Division Multiple Access, SC-FDMA), and other systems. The terms "system" and "network" in embodiments of the present application are often used interchangeably, and the techniques described may be used for both the above-mentioned systems and radio technologies, as well as other systems and radio technologies. The following description describes a New air interface (New Radio, N for purposes of illustrationR) systems, and NR terminology is used in much of the description below, these techniques are also applicable to applications other than NR system applications, such as generation 6 (6) ^th Generation, 6G) communication system.

Fig. 1 shows a block diagram of a wireless communication system to which embodiments of the present application are applicable. The wireless communication system includes a terminal 11 and a network device 12. The terminal 11 may be a mobile phone, a tablet (Tablet Personal Computer), a Laptop (Laptop Computer) or a terminal-side Device called a notebook, a personal digital assistant (Personal Digital Assistant, PDA), a palm top, a netbook, an ultra-mobile personal Computer (ultra-mobile personal Computer, UMPC), a mobile internet appliance (Mobile Internet Device, MID), an augmented reality (augmented reality, AR)/Virtual Reality (VR) Device, a robot, a Wearable Device (weather Device), a vehicle-mounted Device (VUE), a pedestrian terminal (PUE), a smart home (home Device with a wireless communication function, such as a refrigerator, a television, a washing machine, or a furniture), a game machine, a personal Computer (personal Computer, PC), a teller machine, or a self-service machine, and the Wearable Device includes: intelligent wrist-watch, intelligent bracelet, intelligent earphone, intelligent glasses, intelligent ornament (intelligent bracelet, intelligent ring, intelligent necklace, intelligent anklet, intelligent foot chain etc.), intelligent wrist strap, intelligent clothing etc.. Note that, the specific type of the terminal 11 is not limited in the embodiment of the present application. The network-side device 12 may comprise an access network device or a core network device, wherein the access network device 12 may also be referred to as a radio access network device, a radio access network (Radio Access Network, RAN), a radio access network function or a radio access network element. Access network device 12 may include a base station, a WLAN access point, a WiFi node, or the like, which may be referred to as a node B, an evolved node B (eNB), an access point, a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a basic service set (Basic Service Set, BSS), an extended service set (Extended Service Set, ESS), a home node B, a home evolved node B, a transmission and reception point (Transmitting Receiving Point, TRP), or some other suitable terminology in the art, and the base station is not limited to a particular technical vocabulary so long as the same technical effect is achieved, and it should be noted that in the embodiments of the present application, only a base station in an NR system is described as an example, and the specific type of the base station is not limited. The core network device may include, but is not limited to, at least one of: core network nodes, core network functions, mobility management entities (Mobility Management Entity, MME), access mobility management functions (Access and Mobility Management Function, AMF), session management functions (Session Management Function, SMF), user plane functions (User Plane Function, UPF), policy control functions (Policy Control Function, PCF), policy and charging rules function units (Policy and Charging Rules Function, PCRF), edge application service discovery functions (Edge Application Server Discovery Function, EASDF), unified data management (Unified Data Management, UDM), unified data repository (Unified Data Repository, UDR), home subscriber server (Home Subscriber Server, HSS), centralized network configuration (Centralized network configuration, CNC), network storage functions (Network Repository Function, NRF), network opening functions (Network Exposure Function, NEF), local NEF (or L-NEF), binding support functions (Binding Support Function, BSF), application functions (Application Function, AF), and the like. In the embodiment of the present application, only the core network device in the NR system is described as an example, and the specific type of the core network device is not limited.

The following describes the related art point in the embodiment of the present application.

1. 5G network data analysis service

Referring to fig. 2 and 3, the network data analysis function (Network Data Analytics Function, NWDAF) is one of the 5G core network control plane (5 GC) network functions, and may interact with different entities according to different purposes, for example, at least one of the following may be performed:

collecting data based on event subscriptions provided by AMF, SMF, PCF, UDM, AF (directly or through NEF) or OAM (operations, administration, maintenance);

using a data collection coordination function (Data Collection Coordination Function, DCCF) for analysis and data collection;

retrieving information from a data store (e.g., retrieving UDR of user related information via UDM);

storing and retrieving information from a molecular data storage function (Analytics Data Repository Function, ADRF);

analyzing and data collecting from the message frame adaptation function (Messaging Framework Adaptor Function, MFAF);

retrieving information about NFs (e.g., retrieving information related to NFs from NRF);

providing an analysis to the consumer according to the demand;

providing a consumer with a large amount of data.

In fig. 2, the NMDAF obtains data from NF through DCCF or MFAF, and in fig. 3, the NF obtains data analysis result from NMDAF through DCCF or MFAF.

2. User consent treatment in minimization of drive tests (Minimization of Drive-Test, MDT)

MDT, whether signaling-based or management-based, requires user consent to be obtained prior to activation. Once user consent is obtained through the UDM, collection of MDT data is activated and the network can store and use the MDT data as needed. Thus, existing MDT user consent agrees to collect, store, use and share. The user-level data, once collected, is somewhat uncontrolled by the user, resulting in the situation that most users will not agree to resemble MDT data collection. With the wide demand for user-level data use in the future, user-level data collection and storage is inevitable, and user-level data belongs to a main right space fully mastered by a user. The core network, the wireless access network, the network management system and the like are all service nodes at the network level, and a user cannot control autonomously as required.

The following describes in detail, with reference to the attached drawings, a method, an apparatus, a communication device, and a readable storage medium for managing user-level data provided by the embodiments of the present application through some embodiments and application scenarios thereof.

Referring to fig. 4, an embodiment of the present application provides a method for managing user-level data, including:

Step 41: a User Equipment (UE), which may also be referred to as a terminal, performs a first operation including at least one of:

That is, the first authorization information is used for authorization of collection and/or storage of user-level data, and the second authorization information is used for authorization of use of user-level data (provided to a third node, which is a node for requesting data, which may also be referred to as a data requester node).

In some embodiments, optionally, the first authorization information is used to indicate that the collection of the data of the first user is allowed, and if the first authorization information is not sent, it indicates that the collection of the data of the first user is not allowed.

In some embodiments, optionally, the first authorization information may indicate permission or non-permission to collect the data of the first user, when the first authorization information indicates permission, the collection of the data of the first user may be performed, and when the first authorization information indicates non-permission, the collection of the data of the first user may not be performed.

Optionally, the sending the first authorization information is sending the first authorization information to a node authorized to collect and/or store the data of the first user. May be sent directly or through other network functions.

Optionally, the sending the second authorization information is sending the first authorization information to a node authorized to collect and/or store the data of the first user. May be sent directly or through other network functions.

Optionally, the indication that the collection of the data of the first user is allowed or not allowed may carry an identification of a specific node authorized to collect the data of the first user (for example, when the user designates the node), or may not carry the identification, for example, when the data of the first user is collected by a predetermined shared network function (for example, AMF, etc.).

Optionally, the indication that the data of the first user is allowed or not allowed to be stored may or may not carry an identification of a specific node authorized to store the data of the first user (e.g., when the user designates the node), for example, when the data of the first user is stored by a predetermined shared network function (e.g., NRF, etc.).

Optionally, the indication of permission or non-permission to provide the data of the first user may or may not carry an identification of a specific node authorized to collect and/or store the data of the first user (e.g., when the user designates the node), or may not carry the data (e.g., when the data of the first user is collected and/or stored by a predetermined shared network function).

In this embodiment, optionally, the data of the first user includes at least one of the following:

1) Data generated by one or more user devices of the first user;

optionally, the one or more user devices of the first user include at least one of: cell phones, watches, glasses, haptic devices, etc. The user equipment may use either 3GPP access to send the data of the first user or non-3GPP access. The 3GPP access includes 4G (LTE), 5G (NR), 6G, etc., and the non-3GPP access includes WLAN, bluetooth (Bluetooth), wired network, etc. The data provided by the user equipment may include two types: one is user data related to the access network provided by a modem in the user equipment, such as downlink reference signal received power (Reference Signal Received Power, RSRP), downlink reference signal received quality (Reference Signal Received Quality, RSRQ), channel state information (Channel State Information, CSI), time delay, angle and/or doppler etc. provided by a 4G modem, 5Gmodem and/or Wi-Fi processor etc., and the other is user data provided by other modules or application functions in the user equipment, such as GPS module, some APP, location information provided by a gyroscope and/or a camera, user experience data (such as quality of experience (Quality of Experience, qoE) of video service), rotation rate (radian/s) and/or picture etc. around the x, y and z axes of the device.

2) Data generated by the network function and associated with the first user identification;

the network functions include a radio access network function and/or a core network function, and the data associated with the first user identity generated by the network function is, for example, measurement data of a user level defined in a protocol, such as uplink RSRP, RSRQ, uplink throughput and/or downlink throughput, etc.

3) The application function generates data associated with the first user identification.

The application function mainly refers to an application function deployed on an application service provider server, and potentially available user data comprises position information, browse records, video content classification and the like according to different application functions.

In this embodiment of the present application, optionally, the first user identifier includes an identifier of the first user and/or an identifier of a user equipment of the first user.

In an embodiment of the present application, optionally, the first user identifier includes at least one of:

1) Mobile station international subscriber identity (Mobile Station International Subscriber Directory Number, MSISDN, commonly known as mobile phone number);

2) International mobile subscriber identity (International Mobile Subscriber Identity, IMSI);

3) A user permanent identifier (Subscription Permanent Identifier, SUPI);

4) A user privacy identifier (Subscription Concealed Identifier, sui), which is a protective privacy identifier containing a hidden SUPI;

5) Globally unique temporary UE identity (Globally Unique Temporary Identifier, GUTI), 5G is referred to as 5G GUTI;

6) A permanent equipment identifier (Permanent Equipment Identifier, PEI), which defines the PEI used to enter the 5G system for the 3GPP UE, must be assigned an international mobile equipment identity (international mobile equipment identity, IMEI, commonly referred to as handset serial number) or MEISV format if the UE supports at least one 3GPP access technology (i.e. NG-RAN/5G, e-UTRAN/4G, UTRAN/3G, geran/EDGE/2.5G).

7) A general public user identifier (Generic Public Subscription Identifier, GPSI). GPSI is required to handle EGPP users in different Data Networks (DNs) outside the 3GPP system. The 3GPP system associates between a user data memory pool GPSI and a corresponding SUPI. May be the aforementioned MSISDN, external IP address, etc.

8) The RAN UE NGAP ID, uniquely identifying the UE on the NG interface in the gNB, should be unique in the logical NG-RAN node. Corresponding to this in 4G is eNB UE S1AP ID.

9) AMF UE NGAP ID, is used for identifying UE in AMF. Corresponding to this in 4G is MME UE S1AP ID.

10 6G network subscriber identity (permanent identity like IMSI or SUPI).

11 Temporary identities within the radio access network, such as RA-RNTI, TC-RNTI, C-RNTI, CS-RNTI, MSC-RNTI, etc., for use when the radio access network device provides data. In this embodiment of the present application, when the user-level data is stored in the second node, if the data corresponds to a temporary identifier, the association is converted to the foregoing certain persistent identifier, so that the data adopting different user identifiers is easy to identify in the second node, and the situation that which UE is unable to be identified after the temporary identifier is changed is avoided.

12 A temporary mobile subscriber identity (Temporary Mobile Subscriber Identities, TMSI);

13 Packet temporary mobile subscriber identity (Packet-Temporary Mobile Subscriber Identities, P-TMIS);

14 An account number such as an application function account number apple ID, a WeChat account number, etc.;

15 A) name;

16 An identification number;

17 Passport number).

In this embodiment of the present application, optionally, the first operation further includes:

the first configuration information (which may also be referred to as data collection configuration information) is transmitted.

Optionally, the first configuration information is sent to a node for collecting data of the first user.

Wherein the first configuration information includes at least one of:

1) A data collection identifier for indicating the collection of data of the first user;

2) Data collection information comprising at least one of: parameter list to be collected, triggering condition of data collection, sampling rate of data collection;

in this embodiment, optionally, the parameter list to be collected may be represented by a character type, or may be identified by a predefined parameter or a parameter list identifier.

In this embodiment of the present application, optionally, the triggering condition of data collection may be any case (once accepted, any case always needs to report the subscribed data in the time before modification or deletion), or the effective time (for example, in a specified time interval, for example, from a month of a year to a month of a year), or by a character type or a predefined triggering condition, for example, the UE moves to be in a certain geographical location area, the cell physical resource block (Physical Resource Block, PRB) utilization is greater than 50%, the UE handover success rate is lower than 90%, or the like.

In the embodiment of the application, optionally, the sampling rate of data collection refers to how often data is collected.

3) Indication information of a second node, wherein the second node is a node authorized to store the data of the first user;

an implicit second node indicates that the storage node where the scheme is data is the collection node (first node) of the data.

An explicit second node indication scheme is to explicitly represent the second node in the first configuration information, e.g. in the form of a second node identity, another way of representing the second node in the form of a transport layer address (Transport Layer Address) and a port number (port).

The second node scheme of the preset parameters is to determine the second node according to the preset parameters of the data provider, for example, if the parameters to be stored are position information, the corresponding second node is identified as a, and if the parameters to be stored are uplink throughput and uplink channel information, the corresponding second node is identified as B.

4) A data trusted attestation indication for indicating whether a trusted attestation of the first user's data needs to be provided;

in an embodiment of the present application, optionally, the data trust attestation indication may include at least one of: for indicating whether a network function is required to provide a trusted proof of data of the first user, and for indicating whether a node receiving data of the first user is required to provide a trusted proof of the first user. The nodes that receive the data of the first user include nodes that collect the data of the first user.

In this embodiment, if the data trusted proving indication is used to indicate that the network function is required to provide the trusted proving of the data of the first user, two ways may be included: the data of the first user is directly provided by a trusted network function, and the other one is that the user equipment and/or the application function reports the data of the first user to the network function, the network function performs a recheck on the data of the first user, and if the recheck result shows that the data of the first user is trusted, the network function can add a trusted label to the data of the first user and provide the data of the first user to the user equipment and/or the application function and/or a node for collecting and/or storing the data of the first user.

5) Tamper-proof indication, which is used for indicating whether the data provider needs to perform tamper-proof processing on the reported data of the first user and/or indicating whether the data of the first user needs to be subjected to tamper-proof processing;

the data provider comprises user equipment, application functions and/or network functions.

Wherein, indicating whether tamper-proof processing is required for the received data of the first user means: indicating whether a node for collecting data of the first user needs tamper-proof processing of the received data of the first user.

6) And the indication of the data reporting mode is used for indicating the mode of reporting the data of the first user by the data provider.

Optionally, the data reporting mode includes at least one of the following: reporting in a certain time period, reporting in data of a certain length, reporting in the fastest reporting frequency of a data provider, and not exceeding a certain time at a maximum time interval.

The indication modes of the data reporting modes comprise:

an explicit indication scheme of the data reporting mode is that a mode for indicating the data reporting, such as periodic reporting, is displayed in the first configuration information.

The indication scheme of the data reporting mode of the preset parameter is to determine the data reporting mode according to the preset parameter of the data provider, for example, the data reporting mode corresponds to the data reporting receiver one by one, the potential scheme can be that the second node receiving the position information is reporting periodically, and the second node receiving the uplink throughput and the uplink channel information is reporting with a certain data length.

In this embodiment of the present application, optionally, the first operation further includes: the second configuration information (which may also be referred to as data storage configuration information) is transmitted.

Optionally, the second configuration information is sent to a node for storing the data of the first user.

Wherein the second configuration information includes at least one of:

1) A data storage table indication;

for example, it may include: a name of the data storage table (e.g., real-time location storage table) and/or a data storage table identifier (e.g., table I), etc.

2) A data storage duration;

i.e. the length of time the data is saved. Data exceeding the set data storage period will be deleted.

3) Data storage size;

i.e. the size of the space in which the data is stored. Beyond the set data storage size, no new data will be stored.

in an embodiment of the present application, optionally, the data trust attestation indication may include at least one of: for indicating whether a network function is required to provide a trusted proof of data of the first user, and for indicating whether a node receiving data of the first user is required to provide a trusted proof of the first user. The nodes that receive the data of the first user include nodes that store the data of the first user.

5) And the tamper-proof indication is used for indicating whether the data provider is required to conduct tamper-proof processing on the reported data of the first user and/or indicating whether the data of the first user is required to conduct tamper-proof processing.

Wherein, indicating whether tamper-proof processing is required for the received data of the first user means: indicating whether a node for storing the data of the first user needs tamper-proof processing of the received data of the first user. In this embodiment of the present application, optionally, the second authorization information (may also be referred to as authorization configuration information) includes at least one of the following:

1) Indication information of permission or non-permission to provide data;

allowing or disallowing the provision of data may include allowing or disallowing the provision of data to the third node. I.e. indicating the specific receiving node.

2) An authorization type, the authorization type comprising at least one of: authorization based on subscription information, authorization based on request and feedback, authorization based on credentials;

3) An authorization credential; such as a verification code, a two-dimensional code, a token, etc.

4) The validity duration of the authorization ticket.

The validity duration of the authorization credential may be an absolute or relative time, such as 15 minutes after the credential is received by the first node (the node authorized for data collection) or the second node (the node authorized for data storage), or a time period in the future.

In this embodiment of the present application, optionally, the first operation further includes: to send third configuration information (which may also be referred to as data usage configuration information).

Optionally, third configuration information is sent to a node for collecting data of the first user and/or a node for storing data of the first user.

The third configuration information includes at least one of:

1) An identification of a third node, the third node being a data requestor node;

the third node is a node for receiving data, and the identifier of the third node may adopt network function identifier, IP address and/or port number, user-specified credential, etc.

2) An indication of whether to encrypt the provided data of the first user;

optionally, an encryption algorithm configuration and a key (key) configuration may be included in the indication of whether to encrypt the provided data of the first user.

3) An indication of whether to integrity protect the provided data of the first user;

optionally, the indication of whether to provide integrity protection for the data of the first user further includes an integrity protection algorithm configuration and a key (key) configuration.

4) An indication of whether a digital signature is to be added to the provided data of the first user;

optionally, the indication of whether to add a digital signature to the provided data of the first user further includes a digital signature algorithm configuration.

Digital signature is to prevent data from being tampered with

5) An indication of whether to desensitize the provided data of the first user;

optionally, the indication of whether to desensitize the data provided by the first user may further include a desensitization rule, for example, that the phone number is sensitive information.

Desensitization is to desensitize defined sensitive data (configuring desensitization rules) and not output sensitive data.

6) An indication of whether or not to add a data watermark to the provided data of said first user.

A data watermark refers to the insertion of special data into data or the processing of parts of data (e.g. adding a random number of a small specific feature to some data) when the data is provided to a data consumer, without affecting the use of the data and being a feature specific to the data consumer, and then when the data is leaked, it can be determined which data consumer has leaked according to the special data feature.

In this embodiment of the present application, optionally, the method for managing user-level data further includes: the user equipment transmits the data of the first user.

In this embodiment of the present application, optionally, the sending, by the user equipment, data of the first user includes:

the user equipment performs tamper-proof processing on the data of the first user;

the user equipment sends tamper-resistant processed data and/or tamper-resistant related information, wherein the tamper-resistant related information comprises at least one item of:

an instruction to tamper-proof the data of the first user;

a tamper-resistant manner;

checking the position;

a digital signature;

and verifying parameters.

Optionally, the node for collecting the data of the first user and/or the node for storing the data of the first user send the tamper-proof processed data and/or tamper-proof related information.

In an embodiment of the present application, optionally, the tamper-proof manner includes at least one of the following:

1) And performing authority management on the data, and setting the data as unmodified data.

2) And adding a data check bit to the data, wherein the data check bit is used for ensuring the integrity of the data in the transmission process, and calculating the original data by adopting a specified algorithm to obtain a check value. When the receiving party receives the data, the same checking algorithm is adopted to calculate the original data, and if the calculation result is consistent with the received checking value, the data checking is correct. If not, indicating that the data is tampered with or is transmitted in error. The check algorithm includes parity check, checksum, cyclic redundancy check (Cyclic redundancy check, CRC), longitudinal redundancy check (Longitudinal Redundancy Check, LRC), information group check code (Block Check Character, BCC), etc.

Cyclic Redundancy Check (CRC) is a commonly used method in mobile communication systems, and is a hash function for generating a short fixed-bit verification code according to data such as network data packets or computer files, and is mainly used for detecting or checking errors that may occur after data transmission or storage. The CRC parameter model includes the following information:

NAME: parameter model name.

WIDTH: width, i.e., the bit width of the generated CRC data, e.g., CRC-8, the generated CRC is 8 bits.

POLY: the hexadecimal polynomial omits the most significant 1, e.g., x8+x2+x+1, binary 1 0000 0111, omits the most significant 1, and converts to hexadecimal 0x07.

INIT: the CRC initial value is consistent with the WIDTH bit WIDTH.

REFIN: true or false, before performing the calculation, whether the original data is flipped, such as the original data: 0x34 = 00110100, if REFIN is true, 0010 1100 = 0x2c after flipping.

REFOUT: true or false, after the operation is completed, whether the obtained CRC value is flipped, e.g., the calculated CRC value: 0x 97= 1001 0111, if REFOUT is true, 11101001=0xe9 after flipping.

Xoout: and performing exclusive OR operation on the calculation result and the parameter to obtain a final CRC value which is consistent with the WIDTH of the WIDTH bit.

Calculating the correct CRC value requires knowledge of the parametric model. In some embodiments, the network function may calculate a CRC based on the data of the first user as a check value to store together, the parameter value of the CRC being known only to the network function and not to the user or user device. If the user needs the network to provide a trust attestation to the user data requiring party, the network provides specific parameters required for calculating CRC, the user data requiring party calculates CRC according to the CRC parameters, and if the CRC parameters are consistent, the user data requiring party indicates that the data is trusted.

3) The digital signature scheme is a method of storing a message signature in an electronic form by adding a digital signature to data. A complete digital signature scheme should consist of two parts: signature algorithms and verification algorithms. One potential way is that the transmitting end performs hash operation (e.g., MD 5) on the data of the first user to obtain a digital digest, and then the transmitting end encrypts the digital digest with a private key and an asymmetric encryption algorithm to obtain a digital signature. The receiving end decrypts the digital signature by using the public key of the sending end to obtain a digital abstract 1, and performs the same hash operation on the received data of the first user to obtain a digital abstract 2. If the two digital digests agree, then the data is considered not tampered with. The Hash algorithm MD5 message digest algorithm described by way of example above belongs to the class of Hash algorithms. The MD5 algorithm operates on an incoming message of any length to produce a 128-bit message digest. The main characteristics of the MD5 include irreversibility (namely, the MD5 values of the same data are certainly the same, the MD5 values of different data are different, so that it is very difficult to find out that two different data have the same MD5 value, the length of the MD5 value calculated by data with any length is fixed), easy calculation (the MD5 value is easy to calculate by original data), anti-modification (any modification is carried out on the original data, even if only one byte is modified, the obtained MD5 values have great difference), and weak anti-collision (the original data and the MD5 values are known, so that it is very difficult to find out data with the same MD5 value (namely, fake data). In the digital signature process, a pair of public key and private key are arranged, the public key is used for encryption before transmission, any person can decrypt the digital signature by using the public key, but a person who does not grasp the private key cannot encrypt the decrypted file back to the original state, so that the digital signature can not be tampered.

In some embodiments of the present application, a user may not designate a node that specifically performs collection, storage, and/or provision when authorizing collection, storage, and/or provision of user-level data, but rather authorize public network functions to perform collection, storage, and/or provision of user-level data.

In some embodiments, a user may also designate a particular node when authorizing the collection, storage and/or provision of user-level data, the designated node being authorized to perform the collection, storage and/or provision of user-level data.

That is, in some embodiments, optionally, the first authorization information is used to indicate that the first node is allowed or not allowed to collect the data of the first user, or indicate that the second node is allowed or not allowed to store the data of the first user, or allow or not allow the first node to collect the data of the first user, and store the collected data of the first user to the second node.

Optionally, when the first authorization information is used to indicate that the first node is allowed to collect the data of the first user, or the first node is allowed to collect the data of the first user and store the collected data of the first user to the second node, the first operation further includes: transmitting first configuration information to the first node, the first configuration information including at least one of:

A data collection identifier for indicating the collection of data of the first user;

data collection information comprising at least one of: parameter list to be collected, triggering condition of data collection, sampling rate of data collection;

indication information of a second node, wherein the second node is a node authorized to store the data of the first user;

a data trusted attestation indication for indicating whether a trusted attestation of the first user's data needs to be provided;

tamper-proof indication, which is used for indicating whether the data provider needs tamper-proof processing on the reported data of the first user and/or indicating whether the first node needs tamper-proof processing on the received data of the first user;

and the indication of the data reporting mode is used for indicating the mode of reporting the data of the first user by the data provider.

Optionally, when the first authorization information is used to indicate that the second node is allowed to store the data of the first user, or the first node is allowed to collect the data of the first user and store the collected data of the first user to the second node, the first operation further includes: transmitting second configuration information to a second node, the second configuration information including at least one of:

A data storage table indication;

a data storage duration;

data storage size;

and the tamper-proof indication is used for indicating whether the data provider is required to conduct tamper-proof processing on the reported data of the first user and/or indicating whether the second node is required to conduct tamper-proof processing on the received data of the first user.

Optionally, the first authorization information is used to instruct a first node to collect data of the first user, or instruct a second node to store the data of the first user, or when the first node is allowed to collect the data of the first user and store the collected data of the first user to the second node, the first operation further includes:

transmitting third configuration information to the first node and/or the second node, wherein the third configuration information comprises at least one of the following:

an identification of a third node, the third node being a data requestor node;

an indication of whether to encrypt the provided data of the first user;

an indication of whether to integrity protect the provided data of the first user;

An indication of whether a digital signature is to be added to the provided data of the first user;

an indication of whether to desensitize the provided data of the first user;

an indication of whether or not to add a data watermark to the provided data of said first user.

Optionally, the first authorization information is used to instruct a first node to collect data of the first user, or instruct a second node to store the data of the first user, or when the first node is allowed to collect the data of the first user and store the collected data of the first user to the second node, the user-level data management method further includes: the user equipment sends the data of the first user to the first node and/or the second node.

In some embodiments, optionally, the sending, by the user equipment, the data of the first user includes:

the user equipment sends tamper-resistant processed data and/or tamper-resistant related information to the first node and/or the second node, wherein the tamper-resistant related information comprises at least one item of:

an instruction to tamper-proof the data of the first user;

A tamper-resistant manner;

checking the position;

a digital signature;

and verifying parameters.

In this embodiment of the present application, optionally, the method for managing user-level data further includes: the user equipment transmits capability information when accessing to a network, wherein the capability information comprises at least one of the following items:

whether collection of data of a first user with a first node is supported;

whether the second node is used for storing the data of the first user is supported;

whether the provision of data of the first user with the first node is supported;

whether the provision of data of the first user with the second node is supported;

an identification of the first node; for a network function to communicate with the first node;

and the identification of the second node. For network functions to communicate with the second node.

In this embodiment, optionally, the capability information may be sent through a registration management message or the like.

In this embodiment, optionally, the sending the first authorization information includes: the user equipment sends a creation request or a registration request, wherein the creation request is used for requesting to create the first node and/or the second node, the registration request is used for registering the first node and/or the second node, and the creation request or the registration request comprises the first authorization information.

In this embodiment of the present application, optionally, the first node may be a network node or a non-network node, and only the first user and/or the device authorized by the first user may perform data collection configuration on the first node. The non-network node refers to a radio access network node or a core network node (such as a transport layer function AMF/SMF/UPF, a service layer IMS function, etc.), and is an application function, an application server, a user private device, etc. outside the network.

In this embodiment of the present application, optionally, the second node may be a network node or a non-network node, and only the first user and/or the device authorized by the first user may perform operations such as data storage configuration, writing, reading, deleting and/or modifying on the second node. Alternatively, the second node may be provided in combination with the first node. The non-network node refers to a radio access network node or a core network node (such as a transport layer function AMF/SMF/UPF, a service layer IMS function, etc.), and is an application function, an application server, a user private device, etc. outside the network.

In this embodiment of the present application, optionally, the third node may be a user device of the first user or other devices authorized by the first user.

Referring to fig. 5, an embodiment of the present application further provides a method for managing user-level data, including:

step 51: the first node performs a second operation comprising at least one of:

In this embodiment of the present application, optionally, the first node may be a network node or a non-network node. The non-network node refers to a radio access network node or a core network node (such as a transport layer function AMF/SMF/UPF, a service layer IMS function, etc.), and is an application function, an application server, a user private device, etc. outside the network.

In some embodiments, the first node may determine whether to collect the data of the first user according to the authorization of the user device of the first user, in some embodiments, the first node may determine whether to collect the data of the first user according to the subscription information of the first user, and in some embodiments, the first node may also determine whether to collect the data of the first user by combining the subscription information of the first user with the authorization of the user device of the first user.

In some embodiments, the first node may determine whether to provide the data of the first user according to the authorization of the user equipment of the first user, in some embodiments, the first node may determine whether to provide the data of the first user according to the subscription information of the first user, and in some embodiments, the first node may also determine whether to provide the data of the first user in combination with the subscription information of the first user and the authorization of the user equipment of the first user.

In the embodiment of the application, the first node collects, stores and/or uses the user-level data according to the user authorization and/or the user subscription information, instead of the network deciding how to store and use the collected user-level data, the requirement of the user on the self data is met, and the control degree of the user on the self data is improved.

data generated by one or more user devices of the first user;

data generated by the network function and associated with the first user identification;

data generated by the application function and associated with the first user identification;

wherein the first user identification comprises an identification of the first user and/or an identification of a user device of the first user.

In this embodiment of the present application, optionally, the second operation further includes:

collecting data of the first user according to first configuration information and/or subscription information of the first user sent by user equipment of the first user, or collecting the data of the first user and storing the data of the first user to a second node;

wherein the first configuration information includes at least one of:

3) Indication information of the second node;

in an embodiment of the present application, optionally, the data trust attestation indication may include at least one of: for indicating whether a network function is required to provide a trusted proof of data of the first user, and for indicating whether a node collecting data of the first user is required to provide a trusted proof of the first user.

In this embodiment, optionally, if the data trusted proof indicates that the trusted proof of the data of the first user needs to be provided, the method further includes at least one of the following:

The first node collects data of the first user from a trusted network function and adds a trusted proof to the collected data of the first user; the data of the first user collected from the network function comprises, for example, at least one of: location information of a user provided by a positioning function in a network, throughput information of a user level, uplink channel information of the user level, and the like.

The first node compares the data of the first user collected from the user equipment or the network external function of the first user with the data of the first user collected from the trusted network function, and if the comparison result indicates that the data of the first user collected from the user equipment or the network external function of the first user is matched with the data of the first user collected from the trusted network function, adds a trusted proof for the data of the first user collected from the user equipment or the network external function of the first user. For example, the user equipment reports the GPS position information, the first node acquires the GPS information of the user equipment from the network side, compares whether the GPS information reported by the user equipment is consistent with the GPS data acquired from the network side, and if so, adds a trusted proof for the GPS position information reported by the user equipment.

In this embodiment, optionally, the first node may also request other network functions to perform a verification step of the trusted proof of the data.

In this embodiment of the present application, optionally, if the tamper-proof indication indicates that tamper-proof processing needs to be performed on the received data of the first user; the method further comprises the steps of:

the first node performs tamper-proof processing on the received data of the first user;

the first node sends the tamper-proof processed data of the first user and/or tamper-proof related information to the second node and/or the third node, wherein the tamper-proof related information comprises at least one item of:

an instruction to tamper-proof the data of the first user;

a tamper-resistant manner;

checking the position;

a digital signature;

and verifying parameters.

In the above embodiment, the first node performs tamper-resistant processing on the received data of the first user, and in other embodiments of the present application, the data provider (user equipment and/or a network function and/or a network external function) may also perform tamper-resistant processing on the data provided to the first node.

In this embodiment of the present application, optionally, if the tamper-proof indication indicates that the data provider needs to tamper-proof the reported data of the first user;

The method further comprises the steps of:

the first node receives the tamper-resistant processed data of the first user sent by the data provider and/or receives tamper-resistant related information sent by the data provider, and the tamper-resistant related information comprises at least one item of information:

an instruction to tamper-proof the data of the first user;

a tamper-resistant manner;

checking the position;

a digital signature;

and verifying parameters.

In this embodiment, optionally, the second authorization information includes at least one of the following:

an authorization type, the authorization type comprising at least one of: authorization based on subscription information, authorization based on request and feedback, authorization based on credentials;

an authorization credential;

the validity duration of the authorization ticket.

providing the data of the first user to the third node according to third configuration information and/or subscription information of the first user, which are sent by the user equipment of the first user;

wherein the third configuration information includes at least one of:

an identification of a third node, the third node being a data requestor node;

an indication of whether to encrypt the provided data of the first user;

an indication of whether to desensitize the provided data of the first user;

In the above embodiment, the first node provides the data of the first user to the third node according to the third configuration information. In other examples of the present application, the first node may further provide the data of the first user to the third node according to subscription information of the first user.

In this embodiment, optionally, before the first node provides the data of the first user to the third node, the method may further include: and receiving a data request sent by the third node, wherein the data request carries the first user identifier and the required data. And the first node provides the data of the first user for the third node based on the data request according to third configuration information and/or subscription information of the first user, which are sent by the user equipment of the first user.

In this embodiment, optionally, after the first node receives the data request sent by the third node, if the first node is not authorized to provide data to other nodes, and/or the third configuration information (data use configuration information) is not received yet, authorization and/or the third configuration information may be requested from the user equipment.

Referring to fig. 6, an embodiment of the present application further provides a method for managing user-level data, including:

step 61: the second node performs a third operation, the third operation comprising at least one of:

and determining whether to provide the data of the first user according to second authorization information and/or subscription information of the first user, which are sent by the user equipment of the first user, wherein the second authorization information is used for indicating whether to allow or not allow a second node to provide the data of the first user.

In the embodiment of the application, the second node stores and/or uses the user-level data according to the user authorization and/or the user subscription information, rather than the network determining how to store and use the collected user-level data, so that the requirement of the user on the self data is met, and the control degree of the user on the self data is improved.

data generated by one or more user devices of the first user;

In this embodiment of the present application, optionally, the third operation further includes:

storing data of the first user sent by the user equipment of the first user and/or a first node according to second configuration information and/or subscription information of the first user sent by the user equipment of the first user;

wherein the first node is a node authorized to collect data of the first user;

the second configuration information includes at least one of:

a data storage table indication;

a data storage duration;

data storage size;

and the tamper-proof indication is used for indicating whether the data provider is required to conduct tamper-proof processing on the reported data of the first user and/or indicating whether the data of the first user is required to conduct tamper-proof processing.

the second node adding a trust attestation to the data from the first user of the trusted network function;

the second node compares the data of the first user collected from the user equipment or the network external function of the first user with the data of the first user from the trusted network function, and if the comparison result indicates that the data of the first user from the user equipment or the network external function of the first user is matched with the data of the first user from the trusted network function, adds a trusted proof for the data of the first user from the user equipment or the network external function of the first user.

In this embodiment, optionally, the second node may also request other network functions to perform a verification step of the trusted proof of the data.

In this embodiment of the present application, optionally, if the tamper-proof indication indicates that tamper-proof processing needs to be performed on the received data of the first user;

the method further comprises the steps of:

The second node performs tamper-proof processing on the received data of the first user;

the second node sends the tamper-resistant processed data of the first user to the third node and/or sends tamper-resistant related information to the third node, wherein the tamper-resistant related information comprises at least one item of:

an instruction to tamper-proof the data of the first user;

a tamper-resistant manner;

checking the position;

a digital signature;

and verifying parameters.

the method further comprises the steps of:

the second node receives the tamper-resistant processed data of the first user sent by the data provider and/or the first node, and/or receives tamper-resistant related information sent by the data provider and/or the first node, wherein the tamper-resistant related information comprises at least one item of information:

an instruction to tamper-proof the data of the first user;

a tamper-resistant manner;

checking the position;

a digital signature;

and verifying parameters.

an authorization credential;

the validity duration of the authorization ticket.

wherein the third configuration information includes at least one of:

an identification of a third node, the third node being a data requestor node;

an indication of whether to encrypt the provided data of the first user;

an indication of whether to desensitize the provided data of the first user;

In this embodiment, optionally, before the second node provides the data of the first user to the third node, the method may further include: and receiving a data request sent by the third node, wherein the data request carries the first user identifier and the required data. And the second node provides the data of the first user for the third node based on the data request according to third configuration information and/or subscription information of the first user, which are sent by the user equipment of the first user.

In this embodiment, optionally, after the second node receives the data request sent by the third node, if the second node is not authorized to provide data to other nodes, and/or the third configuration information (data use configuration information) is not received yet, authorization and/or the third configuration information may be requested from the user equipment.

In embodiments of the present application, optionally, the user-level data includes both data generated in the mobile communication network and data generated in the non-mobile communication network.

In the above embodiments of the present application, the collection, storage and/or use of user-level data needs to be supported, and the user needs to have stronger control over data use/sharing by supporting user triggering as required, that is, user agreeing to data collection and decoupling from user-level data storage, use/sharing. Second, user-level data collection, storage, and/or use requires support for the data collector (e.g., network function) to endorse user-level data and provide its endorsement history data as needed by the user to prove the user's perspective. And finally, collecting, storing and/or using the user-level data, wherein the data is required to be supported to be stored and used by a receiving node (a second node can be a functional node in a network or a functional node outside the network) appointed by a user.

The method for user-level data in the embodiment of the application is applicable to the following scenes:

scene 1: at present, mobile communication network data are widely used for digital treatment (such as epidemic situation flow regulation, civil affairs/criminal case investigation). Currently, the above-mentioned mobile communication network user-level data is generally collected and provided by a mobile operator in the network operation and maintenance process, so that the digital governance adopts the data with lower precision generated in the mobile network operation process to make preliminary judgment in consideration of the existing business mode (social public welfare property, no data payment process) and user privacy and other factors. For example, epidemic streaming typically employs information such as cell access, camping, etc. of User Equipment (UE) in a mobile network. Considering that most of the regional cells have frequencies of 3.5GHz and below, especially 700M and 1800M cells, the data precision is poor (partial distance deviation can reach 1 km) due to the large cell coverage radius. This part of the data is used for preliminary screening, which neither multiplexes existing network functions nor involves high-precision user data, but the potential problem is that part of the users may be misjudged due to lower-precision data (e.g. the location of the user is judged to be at risk without a space-time intersection with the confirmed cases of infectious disease). Therefore, the preparation information can be proved through higher-precision data from the perspective of the user, so that on one hand, the influence of inconvenient travel and the like caused by misjudgment of the user is reduced, and on the other hand, the administrative treatment cost of communities and the like can be saved. In summary, the present scenario mainly solves the problem that user data authorized by a user is collected in advance and trusted for proving, and when the user needs to use, the user can apply for and provide accurate information for proving the user. Then the user-level data in this scenario is collected and stored, trusted proof is made, used when needed, etc. to provide a corresponding solution. For example, one potential way is that the operator provides user-level data collection and storage under user authorization, and the user can purchase the service on demand (e.g., when a business trip to a location, to avoid failing to return due to potential epidemic risks, the user-level data collection and storage service can be applied to be opened during the business trip to collect accurate location information of the user). The user-level data collection and storage are completely controlled by a user (for example, a business trip finds an infection diagnosis case, the user finds that no space-time intersection exists between the user and a confirmed case after checking an accurate position track of the user, and the data can be obtained.

Scene 2: the existing part of mobile communication network data sharing or use is shared by a mode that the private of a user is not protected by data. Or the user authorizes the network to collect data and authorizes the data to be used at the same time, so that the network function shares or uses the collected data. For example, currently, the data of the communication trip card of the user is generally requested by the user from the operator, and the user shares the screenshot information of the communication trip card to the party requiring the communication trip card in other manners (such as WeChat, etc.). In the process, the data sharing of the communication travel card is not provided with a data protection scheme, and the other party can re-share the travel card to other people to cause data leakage and the like. In summary, the present scenario mainly solves how user data is safely shared to a user designated authorized party, and reduces risk of data leakage. For example, one potential approach is for the user to send communication trip card data usage authorization credentials to the communication trip card demander, which sends the data usage authorization credentials to the operator-provided user-level data collection and storage function, which can feed back whether there is a risk to the communication trip card demander in order to reduce the risk of data leakage. Alternatively, the communication trip card demander may provide data rules (e.g., whether to go to any of A, B, C or D, etc.), and the operator provided user-level data collection and storage function feeds back whether to wait results based on the rules.

Scene 3: industry digitization and data-based technical schemes bring convenience to life, such as map path planning and navigation based on real-time road conditions. At the same time, there is also a potential data risk. A potential solution to balance the aforementioned convenience/benefits and risks is for the user to fully autonomously decide whether to provide data or whether the data is rendered. In view of the time value spent by different users providing the required data and the differentiated requirements of the users on privacy, the present scenario needs to address the data requirements of the users that can obtain the data consumers, and then the users can collect the data according to the requirements and provide the data to the data consumers in a contracted manner and at a price. For example, one potential means for a data consumer to send a data request to an operator, the operator to a potential user-level data-providing function. If the user is willing to provide data, the operator provided user level data collection and storage function collects data according to the data requirements and sends it to the user demander. The data protection method (such as whether encryption, integrity protection, digital signature addition, desensitization, and data watermark addition) of the data interaction process is configured by the user.

The following describes a method for managing user-level data according to the present application in connection with a specific application scenario.

Example 1

In this embodiment, the first node and the second node are both network functions.

If the first node and the second node are also user-level network functions, rather than multi-user shared network functions (e.g., existing AMF, SMF, UPF, etc.), then the user-level first node and second node need to be established based on the user's authorization and request. This embodiment may be used to meet the requirements of scenario 1 described above.

As shown in fig. 7, the following is briefly described for the case of user authorization data collection, configuration data collection, and data use. The UDM (unified data management entity) in fig. 7 is a network function node responsible for user authorization/authentication information management in 5G, but may be another name.

The management method of the user-level data in the embodiment of the application comprises the following steps:

step 1a: a user sends a first node and/or a second node creation request to a first network function node through UE (user equipment) according to requirements;

in this embodiment of the present application, the creation request includes first authorization information, that is, the information is used to instruct the first node to collect data of the first user and store the collected data of the first user in the second node.

In this embodiment of the present application, the first network function node may be an AMF or a data plane function, where the data plane is a protocol plane newly added on the basis of a Control Plane (CP) and a User Plane (UP) and is used for supporting at least one of data collection, data distribution, data security, data privacy, data analysis and data preprocessing. The data plane may also be another name. The data plane may be terminated either by a core network data plane function or by a radio access network data plane function.

Step 1b: the first network function node creates the first node and/or the second node according to the request and feeds back a creation response. The creation response includes a creation success or a creation failure, and if the creation fails, optionally includes a failure cause.

In other embodiments of the present application, step 1a and step 1b may not be performed, but the first network function node may create the first node and/or the second node based on the user subscription information indication.

Step 2: the UE transmits data collection configuration information (i.e., the first configuration information in the above-described embodiment) to the first node.

Step 3: the first node performs user-level data collection based on the data collection configuration information.

If the user equipment performs tamper-proof processing on the reported data, the user equipment needs to send tamper-proof related information to the first node, wherein the tamper-proof related information comprises at least one item of information:

an indication that tamper-resistant processing was performed on the data;

a tamper-resistant manner;

checking the position;

a digital signature;

and verifying parameters.

In other embodiments of the present application, step 2 may optionally be omitted, and the first node may perform user-level data collection based on the user subscription information indication.

Step 4a: the first node stores the collected user-level data to the second node.

In this embodiment, optionally, the first node may collect configuration information and/or subscription information of the user based on the data, and send the collected user data to the second node for storage.

Step 4b: the first node sends the collected user-level data to the data consumer (i.e., the third node in the above embodiment).

In this embodiment, optionally, before the first node sends the collected user-level data to the data consumer, the method further includes: the data usage configuration information (i.e., the third configuration information in the above embodiment) sent by the user equipment is received. The first node sends the collected user-level data to the data consumer according to the data usage configuration information.

In this embodiment of the present application, the first node may also send the collected user-level data to the data consumer based on the subscription information of the user.

In the embodiment of the present application, if a trust attestation indicating the provided data is required, the first node needs to indicate whether the data is considered trusted.

Optionally, to prevent the data from being tampered, the first node may perform tamper-resistant processing on the data. If the first node performs tamper-resistant processing on the data, the first node needs to indicate tamper-resistant related information, where the tamper-resistant related information includes at least one item of:

an indication that tamper-resistant processing was performed on the data;

a tamper-resistant manner;

checking the position;

a digital signature;

and verifying parameters.

As shown in fig. 8, a brief description is given below of the data request situation triggered by the data service consumer, assuming that the user-level data in the previous example has been stored at the second node.

The user-level data management method of the embodiment of the application further comprises the following steps:

step 0: the UE, upon accessing the network, transmits capability information (e.g., via a registration management message (Registration Management procedures)) including at least one of:

whether the collection of user-level data by the first node is supported;

Whether the second node is used for storing the user-level data is supported;

whether the provision of user-level data by the first node is supported;

whether the provision of user-level data using the second node is supported;

an identification of the first node;

and the identification of the second node.

Step 1: the data consumer sends a data request to a first network function node (e.g., AMF). The data request carries the user identification and the required data.

The data consumer may be a user device, a network function, or an application function, etc.

Step 2: the first network function node selects the second node based on the user identification and/or the required data etc.

Step 3: the first network function node sends a data request to the second node.

Step 4: the second node may determine whether to provide data based on the user subscription information and/or based on data usage configuration information sent by the UE, and send a data response. The data response may include the desired data or a rejection, and if rejected, optionally a rejection reason.

If the second node performs tamper-proof processing, the second node needs to send tamper-proof related information when sending data, and the tamper-proof related information comprises at least one item of:

An indication that tamper-resistant processing was performed on the data;

a tamper-resistant manner;

checking the position;

a digital signature;

and verifying parameters.

The verification parameters are, for example, parameter values in a CRC parameter model corresponding to a CRC method, and the digital signature method corresponds to a public key and MD5.

The above embodiment takes one user equipment as an example, and is applicable to a case of a plurality of user equipments. Further, the first node and the second node may be combined as one functional node.

Example 2

In this embodiment, the first node and the second node are both core network service layer functions of the mobile communication system like an IP multimedia system (IP Multimedia Subsystem, IMS). Taking the 5G system as an example, IMS is a protocol defined by voice (VoIMS) and Short Message (SMS) provided to operators over the core network and radio access network communication transport functions. The IMS-like functionality in the first node and the second node network has the advantage that it can interact with the user in real time, e.g. by means of short messages or voice telephony, etc., which further contributes to increased controllability and flexibility in the user experience.

As shown in fig. 9, the method for managing user-level data according to the embodiment of the present application further includes:

Whether the collection of user-level data by the first node is supported;

whether the second node is used for storing the user-level data is supported;

whether the provision of user-level data by the first node is supported;

whether the provision of user-level data using the second node is supported;

an identification of the first node;

and the identification of the second node.

Step 1: after the UE accesses the network, the first node and/or the second node are registered based on UP (user plane) (such as PDU session), i.e. a registration request of the first node and/or the second node is sent to the network. The registration request carries the first authorization information in the above embodiment. If the first node and/or the second node is a user level function, the network needs to create a user level first node and second node.

In other embodiments, the data to be collected may be authorized in the subscription information of the user.

Steps 3a and 3b: the first node collects data based on the data collection configuration information and/or subscription information, the collected data potentially including user-level data reported by the UE and/or the second network function.

The second network function may be a network function such as amf\smf and a base station, etc. that may provide user-level data, or may be a user plane function.

an indication that tamper-resistant processing was performed on the data;

a tamper-resistant manner;

checking the position;

a digital signature;

and verifying parameters.

As shown in fig. 10, the following is briefly described for a data request case triggered by a data service consumer (i.e., a third node, for example, UE1 or AF), assuming that the user-level data of UE2 in the previous example is already stored in the second node. This embodiment may be used to meet the requirements of scenario 2.

step 1: the UE1 sends a data request to the second node, where the data request carries the UE2 identifier and the required data.

Unlike example 1, the following is: because the second node is similar to the IMS network function, the data request is sent to the second node through the User Plane (UP) of the mobile network, and the user plane function and the radio access network function of the core network transport the data without parsing and processing. Alternatively, the UE2 identity may be a temporary identity (e.g., a 6-digit authentication code, or a two-dimensional code, etc.) that UE2 sends to UE 1. Optionally, the temporary identifier may also have an authorization function, and the UE2 sends the temporary identifier and the valid time to the second node, where the information of the UE1 and the information of the UE2 received by the second node may determine whether to provide the requested data. If the temporary identity is used for authorization, then the authorization configuration interaction in step 2 and step 3 is not required.

Step 2: if the second node is a second node dedicated to the UE2, the network side needs to select the corresponding second node according to the identity of the UE 2. If the second node does not have the required user authorization (i.e., the first authorization information) and/or data usage configuration information, the second node may send an authorization and/or data usage configuration request to UE2, including the UE1 identity and the required data. The authorization or data usage configuration request may also be interacted with by a user via a short message or voice phone, etc.

Step 3: the UE2 sends authorization information and/or data usage configuration information to the second node.

Step 4: if the second node is a second node special for the UE2, optionally, a dedicated user plane channel can be established for the second nodes of the UE1 and the UE2 according to the data use requirement, so that the performance and the safety of data transmission are ensured.

Step 5: the second node sends the required data to UE1.

Example 3:

in the embodiment of the application, the first node is a network function and the second node is an IMS-like function or a network external function.

This embodiment focuses on the case where data collection is separated from data storage/use. If the second node is an IMS-like function, the storage and use functions of the user-level data are similar to the existing voice/short messages provided by the operator. If the second node is a network external function, the storage and use of user-level data functions like the existing voice/short messages provided by the internet company. Therefore, the present embodiment will explain two cases of the second node together.

whether the collection of user-level data by the first node is supported;

whether the second node is used for storing the user-level data is supported;

whether the provision of user-level data by the first node is supported;

whether the provision of user-level data using the second node is supported;

an identification of the first node;

and the identification of the second node.

in this embodiment of the present application, the creation request includes first authorization information.

If the subscription information or data collection configuration information of the user indicates that the trusted proof/data review and/or tamper resistant processing is performed. If the data is provided by a network external function (e.g. GPS information reported by the UE), the first node (or the first node may request other network functions) needs to review the required network internal data (e.g. UE location information provided by the location management function LMF, serving cell location information of the UE, etc.) from the collected data decision data. The correctness/trustworthiness of the data outside the network is re-checked using the data inside the network, and if the data reported outside the network is re-checked, a verification passing tag or a trusted tag is added to the data (i.e. indicating that the data is trusted).

Step 4: the first node stores the collected user-level data to the second node.

Step 5: when the data consumer (e.g., user equipment, network function or Application Function (AF), etc.) needs the data, the data may be requested from the second node.

Step 6: if the first node performs tamper-proof processing when transmitting data to the second node, a data consumer needs to transmit a request for tamper-proof related information to the first node (or other network functions) to obtain the tamper-proof related information.

Step 7: if the second node does not have the required user authorization (i.e., first authorization information) and/or data usage configuration information, the second node may send an authorization and/or data usage configuration request to the UE. The UE sends authorization information and/or data usage configuration information to the second node.

Step 8: the second node sends a data response to the data consumer.

Example 4

In this embodiment of the present application, the first node is a network function.

In embodiment 1, the network function provides a trusted proof and tamper-proof processing, such as digital signature, is performed on the trusted proof data. The main difference between this embodiment and embodiments 1, 2, 3 is that the network functions (including the radio access network functions and the core network) do not participate in the verification of the trust attestation; the user equipment and the network function respectively conduct tamper-proof processing on the reported data, and the data consumer automatically verifies whether the data is credible or not.

In this embodiment, it is assumed that the first node is a network function gNB, and the second node is a function authorized by the user, which may be a network function, or may be a core network service layer IMS function or a network external function.

step 1: the UE sends data a to be stored to the gcb to the second node, for example, through RRC message sending, where the data a may be sent to the gcb through a container (container);

step 2: the UE sends data collection configuration information to the gNB, indicating data collection operations of the gNB.

For example, the data in the container in step 1 is sent to the second node by an RRC message, which indicates that the gNB needs to provide the location information of the UE (e.g., serving cell), or the uplink measurement quantity of the gNB (e.g., uplink arrival angle, reference signal time difference, uplink reference signal received power, etc.), or the gNB may send the obtained user data to the second node based on the measured location information and the time corresponding to the location information, etc., and because the gNB provides the network side data corresponding to the time when receiving the data a sent by the UE, the data a sent by the UE is associated with the network side data, so as to perform correctness verification of any data, or the data a is used as the label data of the network side data, etc.

The data in the Container may include a UE digital signature. The data signature is used for ensuring that the data is not tampered, other tamper-proof modes can be adopted, and the embodiment takes digital signature as an example;

and the gNB carries out digital signature on the data provided by the gNB, and endorses the association relation between the data A sent by the UE and the data provided by the gNB.

Step 3: the gNB sends the content in the RRC message container of the UE and the data (containing signature) provided by the gNB to a second node, and the second node stores the received two parts of data;

step 4: providing the stored data to the consumer by the second node according to the user authorization;

this embodiment has the following features:

1) The network function does not endorse the authenticity of the user data, and only endorses the authenticity of the network provided data;

2) The data consumer is responsible for verifying the user signature and the network function signature, and confirming that the information is not changed; the consumer is responsible for determining whether the data and data provider (user/network function, etc.) are trusted.

3) The network function does not need to analyze the data transmitted by the data provider (such as the UE), and the data provider (such as the UE) can encrypt at will.

In addition to the above embodiments, the first node may also be an IMS-like function, and the second node is a network external function. The first node is an IMS-like function that is more conducive to collecting IMS-generated data and interacting with external AFs. The interaction flow is similar to that of embodiment 2, and will not be described again.

In addition to the above embodiments, the first node may also be a network external function and the second node a network function. The first node is a network external function (such as user-specified user equipment (e.g., personal computer or server, etc.)) and facilitates the user to provide more user-level data. The second node is helpful to meet the requirement of the mobile communication network on the user-level data when the second node is a network function, and meets the requirement of the network function on the data under the data authorization of the user based on the user-level data stored by the second node. The interaction flow is similar to that of embodiment 1, and will not be described again.

In addition to the above embodiments, the first node and the second node may be both external functions of the network, and may be generally equivalent to a certain application function respectively. In this embodiment, the interaction between the user equipment and the first node/second node belongs to the application layer message. If the user needs to collect user-level data inside the network, the first node needs to interact with functions inside the network responsible for collecting and providing data, and obtain the user-level data inside the required network.

According to the user-level data management method, the execution main body can be the user-level data management device. In the embodiment of the present application, a method for executing user-level data management by a user-level data management device is taken as an example, and the user-level data management device provided in the embodiment of the present application is described.

Referring to fig. 12, the embodiment of the present application further provides a management apparatus 120 for user-level data, including:

an execution module 121, configured to execute a first operation, where the first operation includes at least one of:

transmitting first authorization information, wherein the first authorization information is used for indicating that the collection of the data of a first user is allowed or not allowed, and/or indicating that the storage of the data of the first user is allowed or not allowed;

Optionally, the data of the first user includes at least one of:

data generated by one or more user devices of the first user;

Optionally, the first operation further includes:

transmitting first configuration information, wherein the first configuration information comprises at least one of the following:

tamper-proof indication, which is used for indicating whether the data provider needs to perform tamper-proof processing on the reported data of the first user and/or indicating whether the data of the first user needs to be subjected to tamper-proof processing;

Optionally, the first operation further includes:

transmitting second configuration information, wherein the second configuration information comprises at least one of the following:

a data storage table indication;

A data storage duration;

data storage size;

Optionally, the second authorization information includes at least one of:

an authorization credential;

the validity duration of the authorization ticket.

Optionally, the first operation further includes:

transmitting third configuration information, wherein the third configuration information comprises at least one of the following:

an identification of a third node, the third node being a data requestor node;

an indication of whether to encrypt the provided data of the first user;

An indication of whether to desensitize the provided data of the first user;

Optionally, the first authorization information is used to instruct the first node to allow or not allow the first node to collect the data of the first user, or instruct the second node to allow or not allow the second node to store the data of the first user, or allow or not allow the first node to collect the data of the first user and store the collected data of the first user to the second node.

Optionally, the management device 120 of user-level data further includes:

the first sending module is used for sending capability information when the network is accessed, and the capability information comprises at least one of the following:

whether collection of data of a first user with a first node is supported;

an identification of the first node;

and the identification of the second node.

Optionally, the sending the first authorization information includes: and sending a creation request or a registration request, wherein the creation request is used for requesting to create the first node and/or the second node, the registration request is used for registering the first node and/or the second node, and the creation request or the registration request comprises the first authorization information.

Optionally, the management device 120 of user-level data further includes:

and the second sending module is used for sending the data of the first user.

Optionally, the second sending module is configured to perform tamper-proof processing on the data of the first user; transmitting tamper-resistant processed data and/or tamper-resistant related information, wherein the tamper-resistant related information comprises at least one item of:

an instruction to tamper-proof the data of the first user;

a tamper-resistant manner;

checking the position;

a digital signature;

and verifying parameters.

The management device for user-level data in the embodiments of the present application may be an electronic device, for example, an electronic device with an operating system, or may be a component in an electronic device, for example, an integrated circuit or a chip. The electronic device may be a terminal, or may be other devices than a terminal. By way of example, terminals may include, but are not limited to, the types of terminals 11 listed above, other devices may be servers, network attached storage (Network Attached Storage, NAS), etc., and embodiments of the application are not specifically limited.

The user-level data management device provided in the embodiment of the present application can implement each process implemented by the method embodiment of fig. 4, and achieve the same technical effects, so that repetition is avoided, and no further description is provided herein.

Referring to fig. 13, the embodiment of the present application further provides a device 130 for managing user-level data, including:

an execution module 131, configured to execute a second operation, where the second operation includes at least one of:

In the embodiment of the application, the user-level data is collected, stored and/or used according to the user authorization and/or the user subscription information, rather than the network determining how to store and use the collected user-level data, the requirement of the user on the self data is met, and the control degree of the user on the self data is improved.

Optionally, the data of the first user includes at least one of:

data generated by one or more user devices of the first user;

Optionally, the second operation further includes:

wherein the first configuration information includes at least one of:

indication information of the second node;

Optionally, if the data trusted attestation indication indicates that trusted attestation of the data of the first user needs to be provided, the management device 130 of user-level data further includes at least one of:

a first adding module, configured to collect data of the first user from a trusted network function, and add a trusted proof to the collected data of the first user;

and the second adding module is used for comparing the data of the first user collected from the user equipment or the network external function of the first user with the data of the first user collected from the trusted network function, and if the comparison result indicates that the data of the first user collected from the user equipment or the network external function of the first user is matched with the data of the first user collected from the trusted network function, adding a trusted proof for the data of the first user collected from the user equipment or the network external function of the first user.

Optionally, if the tamper-proof indication indicates that tamper-proof processing is required to be performed on the received data of the first user;

the user-level data management apparatus 130 further includes:

the tamper-proof processing module is used for tamper-proof processing of the received data of the first user;

the sending module is used for sending the tamper-resistant processed data of the first user and/or tamper-resistant related information to the second node and/or the third node, and the tamper-resistant related information comprises at least one item of:

an instruction to tamper-proof the data of the first user;

a tamper-resistant manner;

checking the position;

a digital signature;

and verifying parameters.

Optionally, if the tamper-proof indication indicates that the data provider needs tamper-proof processing on the reported data of the first user;

the user-level data management apparatus 130 further includes:

the receiving module is used for receiving the tamper-proof processed data of the first user sent by the data provider and/or receiving tamper-proof related information sent by the data provider, and the tamper-proof related information comprises at least one item of information:

an instruction to tamper-proof the data of the first user;

A tamper-resistant manner;

checking the position;

a digital signature;

and verifying parameters.

Optionally, the second authorization information includes at least one of:

an authorization credential;

the validity duration of the authorization ticket.

Optionally, the second operation further includes:

providing the data of the first user to a third node according to third configuration information and/or subscription information of the first user, which are sent by user equipment of the first user;

wherein the third configuration information includes at least one of:

an identification of a third node, the third node being a data requestor node;

an indication of whether to encrypt the provided data of the first user;

an indication of whether to desensitize the provided data of the first user;

The management device for user-level data in the embodiments of the present application may be an electronic device, for example, an electronic device with an operating system, or may be a component in an electronic device, for example, an integrated circuit or a chip.

The user-level data management device provided in the embodiment of the present application can implement each process implemented by the method embodiment of fig. 5, and achieve the same technical effects, so that repetition is avoided, and no further description is provided herein.

Referring to fig. 14, the embodiment of the present application further provides a management apparatus 140 for user-level data, including:

an execution module 141 for executing a third operation, the third operation comprising at least one of:

In the embodiment of the application, the user-level data is stored and/or used according to the user authorization and/or the user subscription information, rather than the network determining how to store and use the collected user-level data, the requirement of the user on the self data is met, and the control degree of the user on the self data is improved.

Optionally, the data of the first user includes at least one of:

data generated by one or more user devices of the first user;

Optionally, the third operation further includes:

wherein the first node is a node authorized to collect data of the first user;

the second configuration information includes at least one of:

a data storage table indication;

a data storage duration;

data storage size;

Optionally, if the data trusted attestation indication indicates that trusted attestation of the data of the first user needs to be provided, the management device 140 of the user-level data further includes at least one of:

a first adding module for adding a trusted attestation to data from the first user of a trusted network function;

and the second adding module is used for comparing the data of the first user collected by the user equipment or the network external function of the first user with the data of the first user of the trusted network function, and adding a trusted proof for the data of the first user of the user equipment or the network external function of the first user if the comparison result indicates that the data of the first user of the user equipment or the network external function of the first user is matched with the data of the first user of the trusted network function.

the management device 140 of user-level data further includes:

the tamper-proof processing module is used for tamper-proof processing of the data of the first user;

the sending module is used for sending the tamper-resistant processed data of the first user to the third node and/or sending tamper-resistant related information to the third node, and the tamper-resistant related information comprises at least one item:

An instruction to tamper-proof the data of the first user;

a tamper-resistant manner;

checking the position;

a digital signature;

and verifying parameters.

the management device 140 of user-level data further includes:

the receiving module is used for receiving the tamper-resistant processed data of the first user sent by the data provider and/or the first node and/or receiving tamper-resistant related information sent by the data provider and/or the first node, wherein the tamper-resistant related information comprises at least one item of information:

an instruction to tamper-proof the data of the first user;

a tamper-resistant manner;

checking the position;

a digital signature;

and verifying parameters.

Optionally, the second authorization information includes at least one of:

an authorization credential;

the validity duration of the authorization ticket.

Optionally, the third operation further includes:

Wherein the third configuration information includes at least one of:

an identification of a third node, the third node being a data requestor node;

an indication of whether to encrypt the provided data of the first user;

an indication of whether to desensitize the provided data of the first user;

The user-level data management device provided in the embodiment of the present application can implement each process implemented by the method embodiment of fig. 6, and achieve the same technical effects, so that repetition is avoided, and no further description is provided herein.

As shown in fig. 15, the embodiment of the present application further provides a communication device 150, including a processor 151 and a memory 152, where the memory 152 stores a program or an instruction that can be executed on the processor 151, for example, when the communication device 150 is a user device, the program or the instruction is executed by the processor 151 to implement the steps of the above-mentioned embodiment of the method for managing user-level data applied to the user device, and achieve the same technical effects. When the communication device 150 is the first node, the program or the instruction, when executed by the processor 151, implements the steps of the above-described embodiment of the method for managing user-level data applied to the first node, and can achieve the same technical effects. When the communication device 150 is the second node, the program or the instruction, when executed by the processor 151, implements the steps of the above-described embodiment of the method for managing user-level data applied to the second node, and the same technical effects can be achieved, so that repetition is avoided and detailed description is omitted.

The embodiment of the application also provides user equipment, which comprises a processor and a communication interface, wherein the processor is used for executing a first operation, and the first operation comprises at least one of the following steps:

The embodiment of the user equipment corresponds to the embodiment of the method at the user equipment side, and each implementation process and implementation manner of the embodiment of the method can be applied to the embodiment of the user equipment, and the same technical effects can be achieved. Specifically, fig. 16 is a schematic hardware structure of a user equipment for implementing an embodiment of the present application.

The user equipment 160 includes, but is not limited to: at least some of the components of the radio frequency unit 161, the network module 162, the audio output unit 163, the input unit 164, the sensor 165, the display unit 166, the user input unit 167, the interface unit 168, the memory 169, and the processor 1610.

Those skilled in the art will appreciate that the user device 160 may also include a power source (e.g., a battery) for powering the various components, which may be logically connected to the processor 1610 by a power management system to perform functions such as managing charging, discharging, and power consumption by the power management system. The user equipment structure shown in fig. 16 does not constitute a limitation of the user equipment, and the user equipment may include more or less components than illustrated, or may combine some components, or may be arranged in different components, which will not be described herein.

It should be appreciated that in embodiments of the present application, the input unit 164 may include a graphics processing unit (Graphics Processing Unit, GPU) 1641 and a microphone 1642, with the graphics processor 1641 processing image data of still pictures or video obtained by an image capture device (e.g., a camera) in a video capture mode or an image capture mode. The display unit 166 may include a display panel 1661, and the display panel 1661 may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like. The user input unit 167 includes at least one of a touch panel 1671 and other input devices 1672. Touch panel 1671, also known as a touch screen. Touch panel 1671 may include two parts, a touch detection device and a touch controller. Other input devices 1672 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and so forth, which are not described in detail herein.

In this embodiment of the present application, after receiving downlink data from the network side device, the radio frequency unit 161 may transmit the downlink data to the processor 1610 for processing; in addition, the radio frequency unit 161 may send uplink data to the network side device. Typically, the radio frequency unit 161 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.

The memory 169 may be used to store software programs or instructions as well as various data. The memory 169 may mainly include a first memory area storing programs or instructions and a second memory area storing data, wherein the first memory area may store an operating system, application programs or instructions (such as a sound playing function, an image playing function, etc.) required for at least one function, and the like. Further, the memory 169 may include volatile memory or nonvolatile memory, or the memory 169 may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM), static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (ddr SDRAM), enhanced SDRAM (Enhanced SDRAM), synchronous DRAM (SLDRAM), and Direct RAM (DRRAM). Memory 169 in embodiments of the present application include, but are not limited to, these and any other suitable types of memory.

Processor 1610 may include one or more processing units; optionally, processor 1610 integrates an application processor that primarily handles operations related to operating systems, user interfaces, applications, etc., and a modem processor that primarily handles wireless communication signals, such as a baseband processor. It will be appreciated that the modem processor described above may not be integrated into the processor 1610.

Wherein the processor 1610 is configured to perform a first operation, where the first operation includes at least one of:

Optionally, the data of the first user includes at least one of:

data generated by one or more user devices of the first user;

Optionally, the first operation further includes:

a data storage table indication;

a data storage duration;

data storage size;

Optionally, the second authorization information includes at least one of:

an authorization credential;

the validity duration of the authorization ticket.

Optionally, the first operation further includes:

an identification of a third node, the third node being a data requestor node;

An indication of whether to encrypt the provided data of the first user;

an indication of whether to desensitize the provided data of the first user;

Optionally, the radio frequency unit 161 is configured to send capability information when accessing the network, where the capability information includes at least one of the following:

whether collection of data of a first user with a first node is supported;

an identification of the first node;

and the identification of the second node.

Optionally, the radio frequency unit 161 is configured to send data of the first user.

Optionally, the radio frequency unit 161 is configured to perform tamper-proof processing on the data of the first user; transmitting tamper-resistant processed data and/or tamper-resistant related information, wherein the tamper-resistant related information comprises at least one item of:

an instruction to tamper-proof the data of the first user;

a tamper-resistant manner;

checking the position;

a digital signature;

and verifying parameters.

The embodiment of the application also provides network side equipment, which comprises a processor and a communication interface, wherein the processor is used for executing a second operation, and the second operation comprises at least one of the following steps:

Alternatively, the processor is configured to perform a third operation, where the third operation includes at least one of:

The network side device embodiment corresponds to the method embodiment executed by the first node or the second node, and each implementation process and implementation manner of the method embodiment are applicable to the network side device embodiment and can achieve the same technical effect.

The embodiment of the application also provides network side equipment. As shown in fig. 17, the network-side device 170 includes: an antenna 171, a radio frequency device 172, a baseband device 173, a processor 174, and a memory 175. The antenna 171 is connected to a radio frequency device 172. In the uplink direction, the radio frequency device 172 receives information via the antenna 171, and transmits the received information to the baseband device 173 for processing. In the downlink direction, the baseband device 173 processes information to be transmitted, and transmits the processed information to the radio frequency device 172, and the radio frequency device 172 processes the received information and transmits the processed information through the antenna 171.

The method performed by the network-side device in the above embodiment may be implemented in the baseband apparatus 173, and the baseband apparatus 173 includes a baseband processor.

The baseband apparatus 173 may, for example, include at least one baseband board, where a plurality of chips are disposed, as shown in fig. 17, where one chip, for example, a baseband processor, is connected to the memory 175 through a bus interface, so as to call a program in the memory 175 to perform the network device operation shown in the above method embodiment.

The network-side device may also include a network interface 176, such as a common public radio interface (common public radio interface, CPRI).

Specifically, the network side device 170 of the embodiment of the present invention further includes: instructions or programs stored in the memory 175 and executable on the processor 174, the processor 174 invokes the instructions or programs in the memory 175 to perform the methods performed by the modules shown in fig. 13 or 14 to achieve the same technical result, and are not repeated here.

Specifically, the embodiment of the application also provides network side equipment. As shown in fig. 18, the network side device 180 includes: a processor 181, a network interface 182, and a memory 183. The network interface 182 is, for example, a common public radio interface (common public radio interface, CPRI).

Specifically, the network side device 180 of the embodiment of the present invention further includes: instructions or programs stored in the memory 183 and executable on the processor 181, the processor 181 invokes the instructions or programs in the memory 183 to perform the methods performed by the modules shown in fig. 13 or 14, and achieve the same technical effects, and are not repeated here.

The embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or the instruction is executed by a processor, the program or the instruction implements each process of the above-mentioned user-level data management method embodiment, and the same technical effects can be achieved, so that repetition is avoided, and no further description is given here.

Wherein the processor is a processor in the terminal described in the above embodiment. The readable storage medium includes computer readable storage medium such as computer readable memory ROM, random access memory RAM, magnetic or optical disk, etc.

The embodiment of the application further provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled with the processor, and the processor is configured to run a program or an instruction, implement each process of the above user-level data management method embodiment, and achieve the same technical effect, so that repetition is avoided, and no further description is provided here.

It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, or the like.

The embodiments of the present application further provide a computer program/program product, where the computer program/program product is stored in a storage medium, and the computer program/program product is executed by at least one processor to implement each process of the above-mentioned user-level data management method embodiment, and the same technical effects can be achieved, so that repetition is avoided, and details are not repeated herein.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Furthermore, it should be noted that the scope of the methods and apparatus in the embodiments of the present application is not limited to performing the functions in the order shown or discussed, but may also include performing the functions in a substantially simultaneous manner or in an opposite order depending on the functions involved, e.g., the described methods may be performed in an order different from that described, and various steps may also be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solutions of the present application may be embodied essentially or in a part contributing to the prior art in the form of a computer software product stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk), comprising several instructions for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method described in the embodiments of the present application.

The embodiments of the present application have been described above with reference to the accompanying drawings, but the present application is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those of ordinary skill in the art without departing from the spirit of the present application and the scope of the claims, which are also within the protection of the present application.

Claims

1. A method of managing user-level data, comprising:

the user equipment performs a first operation comprising at least one of:

2. The method of claim 1, wherein the first user's data comprises at least one of:

data generated by one or more user devices of the first user;

3. The method of claim 1, wherein the first operation further comprises:

4. The method of claim 1, wherein the first operation further comprises:

a data storage table indication;

a data storage duration;

data storage size;

5. The method of claim 1, wherein the second authorization information comprises at least one of:

an authorization credential;

the validity duration of the authorization ticket.

6. The method of claim 1, wherein the first operation further comprises:

An identification of a third node, the third node being a data requestor node;

an indication of whether to encrypt the provided data of the first user;

an indication of whether to desensitize the provided data of the first user;

7. The method of claim 1, wherein the step of determining the position of the substrate comprises,

the first authorization information is used for indicating that the first node is allowed or not allowed to collect the data of the first user, or indicating that the second node is allowed or not allowed to store the data of the first user, or allowing or not allowing the first node to collect the data of the first user and storing the collected data of the first user to the second node.

8. The method as recited in claim 7, further comprising:

the user equipment transmits capability information when accessing to a network, wherein the capability information comprises at least one of the following items:

whether collection of data of a first user with a first node is supported;

an identification of the first node;

and the identification of the second node.

9. The method of claim 7, wherein the transmitting the first authorization information comprises:

the user equipment sends a creation request or a registration request, wherein the creation request is used for requesting to create the first node and/or the second node, the registration request is used for registering the first node and/or the second node, and the creation request or the registration request comprises the first authorization information.

10. The method as recited in claim 1, further comprising:

the user equipment transmits the data of the first user.

11. The method of claim 10, wherein the user device transmitting the data of the first user comprises:

An instruction to tamper-proof the data of the first user;

a tamper-resistant manner;

checking the position;

a digital signature;

and verifying parameters.

12. A method of managing user-level data, comprising:

the first node performs a second operation comprising at least one of:

13. The method of claim 12, wherein the first user's data comprises at least one of:

data generated by one or more user devices of the first user;

14. The method of claim 12, wherein the second operation further comprises:

wherein the first configuration information includes at least one of:

indication information of the second node;

15. The method of claim 14, wherein if the data attestation indication indicates that attestation of data of the first user is required to be provided, the method further comprises at least one of:

the first node collects data of the first user from a trusted network function and adds a trusted proof to the collected data of the first user;

the first node compares the data of the first user collected from the user equipment or the network external function of the first user with the data of the first user collected from the trusted network function, and if the comparison result indicates that the data of the first user collected from the user equipment or the network external function of the first user is matched with the data of the first user collected from the trusted network function, adds a trusted proof for the data of the first user collected from the user equipment or the network external function of the first user.

16. The method of claim 14, wherein if the tamper-evident indication indicates that tamper-evident processing of the received data of the first user is required;

The method further comprises the steps of:

the first node sends tamper-proof processed data of the first user and/or tamper-proof related information to the second node and/or a third node, wherein the tamper-proof related information comprises at least one item of:

an instruction to tamper-proof the data of the first user;

a tamper-resistant manner;

checking the position;

a digital signature;

and verifying parameters.

17. The method of claim 14, wherein if the tamper-evident indication indicates that the data provider is required to tamper-evident the reported data of the first user;

the method further comprises the steps of:

an instruction to tamper-proof the data of the first user;

a tamper-resistant manner;

checking the position;

a digital signature;

and verifying parameters.

18. The method of claim 12, wherein the second authorization information comprises at least one of:

an authorization credential;

the validity duration of the authorization ticket.

19. The method of claim 12, wherein the second operation further comprises:

wherein the third configuration information includes at least one of:

an identification of a third node, the third node being a data requestor node;

an indication of whether to encrypt the provided data of the first user;

an indication of whether to desensitize the provided data of the first user;

20. A method of managing user-level data, comprising:

and determining whether to provide the data of the first user according to second authorization information and/or subscription information of the first user, which are sent by the user equipment of the first user, wherein the second authorization information is used for indicating whether to allow or not allow the second node to provide the data of the first user.

21. The method of claim 20, wherein the first user's data comprises at least one of:

data generated by one or more user devices of the first user;

22. The method of claim 20, wherein the third operation further comprises:

Wherein the first node is a node authorized to collect data of the first user;

the second configuration information includes at least one of:

a data storage table indication;

a data storage duration;

data storage size;

23. The method of claim 22, wherein if the data attestation indication indicates that attestation of data of the first user is required to be provided, the method further comprises at least one of:

24. The method of claim 22, wherein if the tamper-evident indication indicates that tamper-evident processing of the received data of the first user is required;

the method further comprises the steps of:

the second node sends the tamper-resistant processed data of the first user to a third node and/or sends tamper-resistant related information to the third node, wherein the tamper-resistant related information comprises at least one item of:

an instruction to tamper-proof the data of the first user;

a tamper-resistant manner;

checking the position;

a digital signature;

and verifying parameters.

25. The method of claim 22, wherein if the tamper-evident indication indicates that the data provider is required to tamper-evident the reported data of the first user;

the method further comprises the steps of:

An instruction to tamper-proof the data of the first user;

a tamper-resistant manner;

checking the position;

a digital signature;

and verifying parameters.

26. The method of claim 20, wherein the second authorization information comprises at least one of:

an authorization credential;

the validity duration of the authorization ticket.

27. The method of claim 20, wherein the third operation further comprises:

wherein the third configuration information includes at least one of:

an identification of a third node, the third node being a data requestor node;

an indication of whether to encrypt the provided data of the first user;

An indication of whether to desensitize the provided data of the first user;

28. A management device for user-level data, comprising:

29. A management device for user-level data, comprising:

30. A management device for user-level data, comprising:

31. A communication device comprising a processor and a memory storing a program or instructions executable on the processor, the program or instructions implementing the steps of the method of managing user-level data according to any one of claims 1 to 11 when executed by the processor, or the steps of the method of managing user-level data according to any one of claims 12 to 19 when executed by the processor, or the steps of the method of managing user-level data according to any one of claims 20 to 27 when executed by the processor.

32. A readable storage medium, wherein a program or instructions is stored on the readable storage medium, which when executed by a processor, implements the method of managing user-level data according to any one of claims 1 to 11, or the steps of the method of managing user-level data according to any one of claims 12 to 19, or the steps of the method of managing user-level data according to any one of claims 20 to 27.