Communication method, communication device, communication system, storage medium and program product

Abstract

The present disclosure relates to a communication method, a communication device, a communication system, a storage medium and a program product. The method comprises: receiving first information, wherein the first information is used for indicating that at least one user consent is revoked, and different user consents are used for authorizing different data processing purposes; and stopping a data processing purpose related to the at least one user consent. That is, when a user consent is revoked, a first network function may stop a data processing purpose associated with the revoked user consent, thereby avoiding misuse of user-sensitive data.

Description

Communication methods, communication equipment, communication systems, storage media and software products Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a communication method, communication device, communication system, storage medium, and program product. Background Technology

[0002] In wireless communication systems, with the consent of the relevant users, network entities can collect input data to build artificial intelligence (AI) / machine learning (ML) models and train localization models based on AI / ML. With the consent of the relevant users, network entities can collect input data and use this data to evaluate the performance of AI / ML localization models, thereby achieving performance monitoring of the AI / ML localization models. Summary of the Invention

[0003] This disclosure provides a communication method, communication device, communication system, storage medium, and program product.

[0004] According to a first aspect of the present disclosure, a communication method is provided, executed by a first network function, the method comprising:

[0005] Receive first information; wherein the first information is used to indicate that at least one user's consent has been revoked, and different user consents are used to authorize different data processing purposes;

[0006] Stop data processing for purposes related to the consent of the at least one user.

[0007] According to a second aspect of the embodiments of this disclosure, a communication method is provided, executed by a third network function, the method comprising:

[0008] The system receives a third message from a second network function and sends a first message to a first network function based on the third message; wherein the third message indicates that at least one user's consent has been revoked, different user consents are used to authorize different data processing purposes, and the first message indicates that the first network function should cease data processing purposes related to the at least one user's consent; or...

[0009] The system receives a second message sent by the first network function; the second message is used to instruct the third network function to stop collecting data related to a first identifier for the first network function, the first identifier including a user identifier and / or a terminal identifier.

[0010] According to a third aspect of the embodiments of this disclosure, a communication method is provided, executed by a second network function, the method comprising:

[0011] Send a first message to a first network function; wherein the first message is used to indicate that at least one user's consent has been revoked, different user consents are used to authorize different data processing purposes, and the first message is used to instruct the first network function to cease the data processing purpose associated with the at least one user's consent; or...

[0012] Send a third message to a third network function, the third message being used to indicate that at least one user's consent has been revoked, the third message being used to instruct the third network function to send the first message to the first network function.

[0013] According to a fourth aspect of the embodiments of this disclosure, a communication device is provided that can be used to perform the methods described in optional implementations of the first, second, or third aspects.

[0014] According to a fifth aspect of the present disclosure, a communication system is provided, including a first network function, a second network function, and a third network function, wherein the first network function is configured to perform a method as described in an optional implementation of the first aspect, the third network function is configured to perform a method as described in an optional implementation of the second aspect, and the second network function is configured to perform a method as described in an optional implementation of the third aspect.

[0015] According to a sixth aspect of the present disclosure, a storage medium is provided that stores instructions that, when executed on a communication device, cause the communication device to perform a method as described in an optional implementation of the first, second, or third aspect.

[0016] According to a seventh aspect of the present disclosure, a program product is provided, comprising at least one of a program and instructions, wherein the program and instructions, when executed by a communication device, implement the method described in an optional implementation of the first, second, or third aspect.

[0017] The technical solution provided in this disclosure can produce the following beneficial effects: receiving first information; wherein, the first information is used to indicate that at least one user's consent has been revoked, and different user consents are used to authorize different data processing purposes; stopping the data processing purposes related to the at least one user's consent. That is, the first network function can stop the data processing purposes related to the revoked user consent when the user's consent is revoked, thereby avoiding the misuse of the user's sensitive data.

[0018] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0019] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the accompanying drawings required for the description of the embodiments are introduced below. The following drawings are only some embodiments of this disclosure and do not impose specific limitations on the protection scope of this disclosure.

[0020] Figure 1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.

[0021] Figure 2A is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure.

[0022] Figure 2B is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure.

[0023] Figure 3 is a flowchart illustrating a communication method according to an embodiment of the present disclosure.

[0024] Figure 4A is an interactive schematic diagram of a communication method proposed in an embodiment of this disclosure.

[0025] Figure 4B is an interactive schematic diagram of a communication method proposed in an embodiment of this disclosure.

[0026] Figure 5A is a schematic diagram of the structure of a first network function proposed in an embodiment of this disclosure.

[0027] Figure 5B is a schematic diagram of the structure of a second network function proposed in an embodiment of this disclosure.

[0028] Figure 5C is a schematic diagram of the structure of a third network function proposed in an embodiment of this disclosure.

[0029] Figure 6A is a schematic diagram of the structure of the communication device proposed in an embodiment of this disclosure.

[0030] Figure 6B is a schematic diagram of the chip structure proposed in an embodiment of this disclosure. Detailed Implementation

[0031] This disclosure provides a communication method, communication device, communication system, storage medium, and program product.

[0032] In a first aspect, embodiments of this disclosure provide a communication method executed by a first network function, the method comprising:

[0033] Receive first information; wherein the first information is used to indicate that at least one user's consent has been revoked, and different user consents are used to authorize different data processing purposes;

[0034] Stop data processing for purposes related to the consent of the at least one user.

[0035] In the above embodiments, the first network function can stop data processing related to the revoked user consent when the user consent is revoked, thereby avoiding the misuse of sensitive user data.

[0036] In conjunction with some embodiments of the first aspect, in some embodiments, receiving the first information includes:

[0037] The system receives the first information sent by the second network function. The first information is used to indicate that at least one user consent associated with the first identifier has been revoked. The first information includes at least one of the following: at least one user consent information and the first identifier. The user consent information is used to indicate that the user consent has been revoked. Different user consent information corresponds to different data processing purposes. The first identifier includes a user identifier and / or a terminal identifier.

[0038] In the above embodiments, the second network function can indicate to the first network function that the user's consent has been revoked, so that the first network function can stop the data processing purpose related to the revoked user consent, thereby avoiding the misuse of the user's sensitive data.

[0039] In conjunction with some embodiments of the first aspect, in some embodiments, the first information indicates that all data processing purposes related to the first identifier are no longer permitted, and a second information is sent to a third network function, the second information being used to instruct the third network function to stop collecting data related to the first identifier for the first network function.

[0040] In the above embodiments, if all data processing purposes related to the first identifier are no longer permitted, the first network function may instruct the third network function to stop collecting data related to the first identifier for the first network function, thereby ensuring the compliance of data processing.

[0041] In conjunction with some embodiments of the first aspect, in some embodiments, the second information includes at least one of the following: the first identifier and a data collection stop indication, wherein the data collection stop indication is used to indicate the cessation of collecting data related to the first identifier for the first network function.

[0042] In the above embodiments, the second information includes a first identifier and a data collection stop instruction, which can accurately instruct the third network function to stop collecting data related to the first identifier for the first network function, ensuring that the data collection activity can be stopped accurately and efficiently according to the instruction, and maintaining the standardization and controllability of the data processing process.

[0043] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0044] The system receives a confirmation message from the third network function, indicating that the third network function has stopped collecting data related to the first identifier for the first network function.

[0045] In the above embodiments, the first network function can clearly know that data collection has stopped as required, ensuring the correct execution of data processing and enhancing the traceability and reliability of the data processing process.

[0046] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0047] The system receives a first subscription request sent by the third network function, the first subscription request being used to subscribe to the second information.

[0048] In the above embodiments, the first network function receives a first subscription request sent by the third network function for subscribing to the second information, so that the third network function's subscription request for the second information can be communicated and received.

[0049] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0050] The system receives a first cancellation request sent by the third network function, the first cancellation request being used to unsubscribe from the second information.

[0051] In the above embodiments, the first network function receives a first cancellation request sent by the third network function to unsubscribe from the second information, which can respond promptly to the third network function's subscription change requirements for the second information, flexibly adjust the information interaction relationship, and improve the flexibility and adaptability of data interaction management.

[0052] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0053] Send a second subscription request to the second network function, the second subscription request being used to subscribe to a notification of revocation of user consent associated with the first identifier.

[0054] In the above embodiments, the first network function sends a second subscription request to the second network function for subscribing to a user consent revocation notification related to the first identifier, thereby enabling timely acquisition of information on the revocation of a specific user's consent.

[0055] In conjunction with some embodiments of the first aspect, in some embodiments, receiving the first information includes:

[0056] The system receives the first information sent by the third network function. The first information is used to indicate that at least one user consent associated with the first identifier has been revoked. The first information includes at least one of the following: at least one user consent information and the first identifier. The user consent information is used to indicate that the user consent has been revoked. Different user consent information corresponds to different data processing purposes. The first identifier includes a user identifier and / or a terminal identifier.

[0057] In the above embodiments, the third network function can indicate to the first network function that the user's consent has been revoked, so that the first network function can stop the data processing purpose related to the revoked user consent, thereby avoiding the misuse of the user's sensitive data.

[0058] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0059] A third subscription request is sent to the third network function, the third subscription request being used to subscribe to the first information.

[0060] In the above embodiments, the first network function sends a third subscription request to the third network function for subscribing to the first information, thereby enabling timely acquisition of information indicating that the user has agreed to withdraw.

[0061] In conjunction with some embodiments of the first aspect, in some embodiments, a second cancellation request is sent to the third network function, the second cancellation request being used to unsubscribe from the first information.

[0062] In the above embodiments, the first network function can send a second cancellation request to the third network function to unsubscribe from the first information. In this way, the third network function can respond promptly to the first network function's request for changes in the subscription of the first information, flexibly adjust the information interaction relationship, and improve the flexibility and adaptability of data interaction management.

[0063] In conjunction with some embodiments of the first aspect, in some embodiments, the data processing purpose includes at least one of the following: model training, model performance monitoring, model inference, model transmission, and model openness.

[0064] In the above embodiments, the purpose of data processing is clearly defined, including at least one of model training, model performance monitoring, model inference, model transmission, and model sharing. This clearly defines the specific scope of data processing, provides an accurate basis for controlling data processing based on user consent, and ensures the orderliness and compliance of data processing.

[0065] Secondly, embodiments of this disclosure propose a communication method executed by a third network function, the method comprising:

[0066] The system receives a third message from a second network function and sends a first message to a first network function based on the third message; wherein the third message indicates that at least one user's consent has been revoked, different user consents are used to authorize different data processing purposes, and the first message indicates that the first network function should cease data processing purposes related to the at least one user's consent; or...

[0067] The system receives a second message sent by the first network function; the second message is used to instruct the third network function to stop collecting data related to a first identifier for the first network function, the first identifier including a user identifier and / or a terminal identifier.

[0068] In the above embodiments, the third network function receives a third message from the second network function indicating that at least one user's consent has been revoked, and accordingly sends a first message to the first network function instructing it to stop processing data related to the user's consent, or receives a second message from the first network function instructing the third network function to stop collecting data related to the identifier. This enables effective transmission and interaction of information between different network functions, accurately controls the purpose of data processing and data collection activities based on changes in the user's consent status, and avoids the misuse of sensitive user data.

[0069] In conjunction with some embodiments of the second aspect, in some embodiments, the first information is used to indicate that at least one user consent associated with the first identifier has been revoked, the first information includes at least one of the following: at least one user consent information, the first identifier, the user consent information being used to indicate that the user consent has been revoked, different user consent information corresponding to different data processing purposes, and the first identifier including a user identifier and / or a terminal identifier.

[0070] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0071] Stop collecting data for the data processing purposes indicated by the at least one user's consent.

[0072] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0073] Receive a third subscription request sent by the first network function, the third subscription request being used to subscribe to the first information.

[0074] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0075] Receive a second cancellation request sent by the first network function, the second cancellation request being used to unsubscribe from the first information.

[0076] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0077] A fourth subscription request is sent to the second network function, the fourth subscription request being used to subscribe to a user consent revocation notification associated with the first identifier.

[0078] In the above embodiments, the third network function sends a fourth subscription request to the second network function to subscribe to the user consent withdrawal notification related to the first identifier, so as to obtain key information on the specific user's consent withdrawal in a timely manner, thereby making reasonable adjustments to the relevant business processes based on the information, ensuring that data processing activities conform to the user's wishes, and avoiding the misuse of the user's sensitive data.

[0079] In conjunction with some embodiments of the second aspect, in some embodiments, the second information includes at least one of the following: the first identifier and a data collection stop indication, wherein the data collection stop indication is used to indicate the cessation of collecting data related to the first identifier for the first network function.

[0080] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0081] Stop collecting data related to the first identifier for the first network function.

[0082] In conjunction with some embodiments of the second aspect, in some embodiments, a confirmation message is sent to the first network function, the confirmation message indicating that the third network function has stopped collecting data related to the first identifier for the first network function.

[0083] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0084] Send a first subscription request to the first network function, the first subscription request being used to subscribe to the second information.

[0085] In conjunction with some embodiments of the second aspect, in some embodiments, a first cancellation request is sent to the first network function, the first cancellation request being used to unsubscribe from the second information.

[0086] In conjunction with some embodiments of the second aspect, in some embodiments, the data processing purpose includes at least one of the following: model training, model performance monitoring, model inference, model transmission, and model openness.

[0087] Thirdly, embodiments of this disclosure propose a communication method executed by a second network function, the method comprising:

[0088] Send a first message to a first network function; wherein the first message is used to indicate that at least one user's consent has been revoked, different user consents are used to authorize different data processing purposes, and the first message is used to instruct the first network function to cease the data processing purpose associated with the at least one user's consent; or...

[0089] Send a third message to a third network function, the third message being used to indicate that at least one user's consent has been revoked, the third message being used to instruct the third network function to send the first message to the first network function.

[0090] In the above embodiments, the second network function can effectively transmit user consent revocation information between different network functions by sending a first message to the first network function indicating that at least one user's consent has been revoked and for the purpose of stopping related data processing, or by sending a third message to the third network function indicating that at least one user's consent has been revoked and instructing it to send the first message to the first network function. This allows for precise control of the data processing purpose of the first network function based on changes in the user's consent status, thereby avoiding the misuse of sensitive user data.

[0091] In conjunction with some embodiments of the third aspect, in some embodiments, the first information is used to indicate that at least one user consent associated with the first identifier has been revoked, the first information includes at least one of the following: at least one user consent information, the first identifier, the user consent information being used to indicate that the user consent has been revoked, different user consent information corresponding to different data processing purposes, and the first identifier including a user identifier and / or a terminal identifier.

[0092] In conjunction with some embodiments of the third aspect, in some embodiments, a second subscription request sent by the first network function is received, the second subscription request being used to subscribe to a user consent revocation notification associated with a first identifier, the first identifier including a user identifier and / or a terminal identifier.

[0093] In conjunction with some embodiments of the third aspect, in some embodiments, a fourth subscription request is received from the third network function, the fourth subscription request being used to subscribe to a user consent revocation notification associated with a first identifier, the first identifier including a user identifier and / or a terminal identifier.

[0094] In conjunction with some embodiments of the third aspect, in some embodiments, the data processing purpose includes at least one of the following: model training, model performance monitoring, model inference, model transmission, and model openness.

[0095] Fourthly, embodiments of this disclosure propose a first network function, which may include at least one of a transceiver module and a processing module; wherein the first network function may be used to perform an optional implementation of the first aspect.

[0096] Fifthly, embodiments of this disclosure propose a third network function, which may include at least one of a transceiver module and a processing module; wherein the third network function may be used to perform an optional implementation of the second aspect.

[0097] In a sixth aspect, embodiments of this disclosure propose a second network function, which may include at least one of a transceiver module and a processing module; wherein the second network function may be used to perform an optional implementation of the third aspect.

[0098] In a seventh aspect, embodiments of this disclosure provide a first network function, which may include one or more processors; wherein the first network function may be used to perform an optional implementation of the first aspect.

[0099] In an eighth aspect, embodiments of this disclosure provide a third network function, which may include one or more processors; wherein the third network function may be used to perform an optional implementation of the second aspect.

[0100] In a ninth aspect, embodiments of this disclosure provide a second network function, which may include one or more processors; wherein the second network function may be used to perform an optional implementation of the third aspect.

[0101] In a tenth aspect, embodiments of this disclosure provide a communication system that may include: a first network function, a second network function, and a third network function; wherein the first network function is configured to perform the method described in the optional implementation of the first aspect, the third network function is configured to perform the method described in the optional implementation of the second aspect, and the second network function is configured to perform the method described in the optional implementation of the third aspect.

[0102] Eleventhly, embodiments of this disclosure provide a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the method as described in an optional implementation of the first, second, or third aspect.

[0103] In a twelfth aspect, embodiments of this disclosure provide a program product that, when executed by a communication device, causes the communication device to perform the method as described in an optional implementation of the first, second, or third aspect.

[0104] In a thirteenth aspect, embodiments of this disclosure provide a computer program that, when run on a computer, causes the computer to perform the methods described in an optional implementation of the first, second, or third aspect.

[0105] In a fourteenth aspect, embodiments of this disclosure provide a chip or chip system. The chip or chip system includes processing circuitry configured to perform the methods described in optional implementations of the first, second, or third aspects.

[0106] It is understood that the aforementioned first network function, second network function, third network function, communication device, communication system, storage medium, program product, computer program, chip or chip system can all be used to execute the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0107] This disclosure provides a communication method, communication device, communication system, storage medium, and program product. In some embodiments, the terms "information transmission method" and "information processing method," "communication method," etc., can be used interchangeably; the terms "information transmission device" and "information processing device," "communication device," "communication equipment," etc., can be used interchangeably; and the terms "information processing system," "communication system," etc., can be used interchangeably.

[0108] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0109] In each of the disclosed embodiments, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of the embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0110] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0111] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.

[0112] In some embodiments, "multiple" can refer to two or more.

[0113] In some embodiments, the terms “at least one of”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.

[0114] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of B); in some embodiments, B (execute B regardless of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, A and B (both A and B are executed). The same applies when there are more branches such as A, B, C, etc.

[0115] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execution of A regardless of B); in some embodiments, B (execution of B regardless of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, C, etc.

[0116] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

[0117] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0118] In some embodiments, the terms “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “if…”, “if…”, etc., can be used interchangeably.

[0119] In some embodiments, the terms “greater than,” “greater than or equal to,” “not less than,” “more than,” “more than or equal to,” “not less than,” “higher than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably, as can the terms “less than,” “less than or equal to,” “not greater than,” “less than,” “less than or equal to,” “not more than,” “lower than,” “lower than or equal to,” “not higher than,” and “below”.

[0120] In some embodiments, devices, etc., may be interpreted as physical or virtual, and their names are not limited to those described in the embodiments. Terms such as “device,” “equipment,” “circuit,” “network function,” “network element,” “node,” “function,” “unit,” “section,” “system,” “network,” “chip,” “chip system,” “entity,” and “subject” can be used interchangeably.

[0121] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).

[0122] In some embodiments, the terms "Access Network Device (AN Device)," "Radio Access Network Device (RAN Device)," "Base Station (BS)," "Radio Base Station," "Fixed Station," "Node," "Access Point," "Transmission Point (TP)," "Reception Point (RP)," "Transmission / Reception Point (TRP)," "Panel," "Antenna Panel," "Antenna Array," "Cell," "Macro Cell," "Small Cell," "Femto Cell," "Pico Cell," "Sector," "Cell Group," "Serving Cell," "Carrier," "Component Carrier," and "Bandwidth Part (BWP)" can be used interchangeably.

[0123] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", "subscriber station", "mobile unit", "subscriber unit", "wireless unit", "remote unit", "mobile device", "wireless device", "wireless communication device", "remote device", "mobile subscriber station", "access terminal", "mobile terminal", "wireless terminal", "remote terminal", "handset", "user agent", "mobile client", and "client" can be used interchangeably.

[0124] In some embodiments, access network devices, core network devices, or network devices can be replaced with terminals. For example, embodiments of this disclosure can also be applied to structures where communication between access network devices, core network devices, or network devices and terminals is replaced with communication between multiple terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel or direct channel, and uplink link, downlink, etc., can be replaced with sidelink link or direct link.

[0125] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, core network device, or network device may also be configured to have all or some of the functions of the terminal.

[0126] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

[0127] In some embodiments, data, information, etc., may be obtained with the user's consent.

[0128] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0129] Figure 1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure. As shown in Figure 1, the communication system 100 may include a first network function 101, a second network function 102, and a third network function 103.

[0130] In some embodiments, the first network function 101 is a network function with data processing capabilities, such as a network data analytics function (NWDAF). The name is not limited to this, and it may also be other network functions that implement similar functions.

[0131] In some embodiments, the second network function 102 is a network function with data storage / management capabilities, such as a User Data Repository (UDR) or User Data Management (UDM), and the name is not limited thereto. It may also be other network functions that implement similar functions.

[0132] In some embodiments, the third network function 103 is a network function with location management function or a network function with data collection function, such as a location management function (LMF) or a data collection network function. The name is not limited to these, and it may also be other network functions that implement similar functions.

[0133] In some embodiments, the terminal may include at least one of, but is not limited to, a mobile phone, a wearable device, an Internet of Things device, a car with communication capabilities, a smart car, a tablet computer, a computer with wireless transceiver capabilities, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, and a wireless terminal device in a smart home.

[0134] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.

[0135] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1, or to some of the main bodies, but are not limited thereto. The main bodies shown in FIG1 are examples. The communication system may include all or some of the main bodies in FIG1, or may include other main bodies outside of FIG1. ​​The number and form of each main body are arbitrary. Each main body may be physical or virtual. The connection relationship between the main bodies is an example. The main bodies may not be connected or may be connected. The connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

[0136] The embodiments disclosed herein can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G New Radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0137] In some embodiments of this disclosure, training an AI / ML-based positioning model means that network entities (e.g., RAN devices, NWDAF, LMF) collect input data (i.e., location-related measurement data) to construct the AI / ML model with the consent of the relevant user. Performance monitoring of an AI / ML-based positioning model refers to a network entity collecting input data and using this data to evaluate the performance of the AI / ML positioning model with the consent of the relevant user. Specifically, user consent indicates that the user authorizes the collection of UE data for the purpose of AI / ML positioning model training or performance monitoring.

[0138] In some embodiments, a user may temporarily withdraw their consent related to AI / ML model training or performance monitoring. However, if the network entity cannot promptly cease the ongoing AI / ML model training, AI / ML model performance monitoring, or data collection procedures when the user withdraws their consent, it may lead to the misuse of the user's sensitive data.

[0139] Figure 2A is an interactive schematic diagram illustrating a communication method according to an embodiment of the present disclosure. This method can be executed by the aforementioned communication system. As shown in Figure 2A, the method may include:

[0140] Step S2101: The first network function sends a second subscription request to the second network function.

[0141] In some embodiments, the second network function may receive a second subscription request. For example, the second network function may receive a second subscription request sent by the first network function. As another example, the second network function may also receive a second subscription request sent by another entity.

[0142] In some embodiments, the first network function may be NWDAF.

[0143] In some embodiments, the first network function may be an NWDAF that includes a Model Training Logical Function (MTLF), which can subscribe to input data and perform model training or model performance monitoring based on the input data.

[0144] In some embodiments, when the first network function determines that model training or model performance monitoring is required, it may obtain user consent from the second network function.

[0145] For example, the first network function can determine, based on an internal trigger or a request sent by LMF, whether to train an AI / ML model using LMF-based AI / ML localization, or to perform performance monitoring of an AI / ML model using LMF-based AI / ML localization.

[0146] In some embodiments, the second network function may be UDM / UDR.

[0147] In some embodiments, when a first network function needs to obtain data related to a first identifier, it may send a first request to a second network function to obtain user consent. The first request may include at least one of the following: the first identifier, and the purpose of data processing.

[0148] In some embodiments, the first identifier may include a user identifier and / or a terminal identifier. For example, the first identifier may be a UE ID or a user ID, and the UE ID may be, for example, a Subscription Permanent Identifier (SUPI).

[0149] In some embodiments, if the first identifier is a UE ID, the data associated with the first identifier is the data collected by the UE corresponding to the UE ID; if the first identifier is a user ID, the data associated with the first identifier may include the data collected from the user corresponding to the user ID.

[0150] In some embodiments, the data processing purpose indicates the purpose for which the first network function uses data associated with the first identifier.

[0151] In some embodiments, the data processing purpose includes at least one of the following: model training, model performance monitoring, model inference, model transfer, and model openness.

[0152] In some embodiments, model transfer involves transferring a trained model and its associated data from one network function to another. For example, a first network function can transfer a trained AI / ML model and data associated with a first identifier to other network functions.

[0153] In some embodiments, model openness involves making the trained model and its associated data available to other network functions so that these functions can use the open model and associated data. For example, a first network function can make its trained AI / ML model and data associated with a first identifier available to other network functions, which can then use the AI / ML model and the data associated with the first identifier.

[0154] For example, the first network function can use data associated with the first identifier for model training, the first network function can also use data associated with the first identifier for model performance monitoring, and the first network function can also use data associated with the first identifier for model inference.

[0155] In some embodiments, the data processing purpose may also be referred to as "purpose", "data use purpose", etc., and this disclosure does not limit it.

[0156] In some embodiments, the results of obtaining user consent may differ depending on the data processing purpose. For example, the user may consent to use data related to the first identifier for model training, in which case the first network function can obtain user consent related to the data processing purpose of model training; as another example, the user may not consent to use data related to the first identifier for model performance monitoring, in which case the first network function cannot obtain user consent related to the data processing purpose of model performance monitoring.

[0157] In some embodiments, after obtaining user consent, the first network function may send a second subscription request to the second network function.

[0158] In some embodiments, the second subscription request is used to subscribe to a notification of revocation of user consent associated with the first identifier. The second subscription request may be, for example, Nudm_SDM_Subscribe / Nudr_DM_Subscribe.

[0159] In some embodiments, if the first network function has not obtained the user's consent, the user consent revocation notification associated with the first identifier may not be subscribed to, and step S2101 may be omitted.

[0160] Step S2102: The third network function sends a first subscription request to the first network function.

[0161] In some embodiments, the first network function may receive a first subscription request. For example, the first network function may receive a first subscription request sent by a third network function. As another example, the first network function may also receive a first subscription request sent by another entity.

[0162] In some embodiments, the third network function may be an LMF, which can collect input data from the Radio Access Network (RAN) and / or the UE.

[0163] In some embodiments, after the first network function sends a second subscription request to the second network function, it may send a second request to the third network function to subscribe to data from the third network function. This second request may, for example, be Nlmf_DataExposure_Subscribe.

[0164] The second request may include at least one of the following: a first identifier, user consent check information, and a target address, wherein the user consent check information is used to indicate that user consent has been checked and user consent has been granted, and the target address is the address of the first network function.

[0165] In some embodiments, the third network function may subscribe to data collection cessation information from the first network function, so that the third network function can promptly stop data collection after the user consent associated with the first network function is revoked.

[0166] In some embodiments, after receiving a second request from a first network function, a third network function may send a first subscription request to the first network function. This first subscription request may, for example, be N. NWDAF _DataCollectionStop_Subscribe.

[0167] In some embodiments, the first subscription request is used to subscribe to second information, which may be used to instruct a third network function to stop collecting data related to the first identifier for the first network function.

[0168] In some embodiments, the first subscription request may include the first identifier.

[0169] In some embodiments, the third network function may collect data related to the first identifier and send the collected data related to the first identifier to the first network function.

[0170] In some embodiments, the third network function may send data related to the first identifier to the first network function based on the target address.

[0171] For example, the third network function can call Nlmf_DataExposure_Notify to send the collected data related to the first identifier to the first network function.

[0172] In some embodiments, the first network function may use the data associated with the first identifier for related data processing purposes, such as model training or model performance monitoring using the data associated with the first identifier.

[0173] In some embodiments, the third network function may not subscribe to the data collection stop information from the first network function. In this case, the first network function may actively send the data collection stop information to the third network function, or the third network function may learn from other network functions whether all user consents related to the first network function have been revoked, so as to stop collecting data for the first network function. In this case, step S2102 can be omitted.

[0174] Step S2103: The second network function sends the first information to the first network function.

[0175] In some embodiments, the first network function may receive first information. For example, the first network function may receive first information sent by a second network function. As another example, the first network function may also receive first information sent by other entities.

[0176] In some embodiments, if a user withdraws their consent, the second network function may send a first message to the first network function.

[0177] In some embodiments, the first information is used to indicate that at least one user's consent has been revoked, with different user consents used to authorize different data processing purposes.

[0178] In some embodiments, the first information is used to indicate that at least one user consent associated with the first identifier has been revoked. The first information may include at least one of the following: at least one user consent information and the first identifier. The user consent information is used to indicate that the user consent has been revoked, and different user consent information corresponds to different data processing purposes.

[0179] In some embodiments, a user may revoke all user consents. For example, all user consents related to the first identifier may be revoked, meaning that the use of data related to the first identifier is not permitted.

[0180] In some embodiments, a user may withdraw partial user consent.

[0181] For example, a user may revoke the user's consent to the first network function, and for example, the first network function may no longer be permitted to use data related to the first identifier for all data processing purposes, that is, the first network function may no longer use data related to the first identifier.

[0182] For example, a user may revoke user consent for certain data usage purposes granted to the first network function. For instance, if the data processing purposes requested by the first network function when it previously obtained user consent included model training, model performance monitoring, and model inference, the user may revoke user consent for model performance monitoring, meaning that the first network function cannot use data related to the first identifier for model performance monitoring.

[0183] In some embodiments, the first identifier may include an identifier, for example, the first identifier is UE1, and at least one user consent includes user consent related to UE1. The first information may be used to indicate that at least one user consent related to UE1 has been revoked.

[0184] In some embodiments, the first identifier may include multiple identifiers. For example, the first identifier may include UE1 and UE2, and at least one user consent may include user consent related to UE1 and UE2. The first information may be used to indicate that at least one user consent related to UE1 and UE2 has been revoked.

[0185] In some embodiments, at least one user consent may include a user consent, i.e., a first message indicating that a user consent has been withdrawn. In this case, the first message may include a user consent message. For example, each time a second network function receives a message indicating that a user consent has been withdrawn, it sends the first message to the first network function, the first message including the received message indicating that the user consent has been withdrawn.

[0186] In some embodiments, user consent information may include user consent and user consent purpose, meaning that each user consent purpose (or data usage purpose) corresponds to a user consent, and the user consent can indicate whether the user permits the user to consent to the data usage purpose. For example, if the user consent purpose / data usage purpose is model inference, the user consent can indicate that model inference is permitted by the user; as another example, if the user consent purpose / data usage purpose is model training, the user consent can indicate that model training is not permitted by the user.

[0187] In some embodiments, the user consent value includes "user has consented" and "user has not consented". For example, after the second network function receives a message indicating that the user's consent has been revoked, the user consent information value is "user has not consented".

[0188] In some embodiments, at least one user consent may also include multiple user consents, i.e., the first information indicates that multiple user consents have been withdrawn. In this case, the first information may include multiple user consent information. For example, after the second network function continuously receives multiple user consent information indicating that user consent has been withdrawn, it sends the first information to the first network function, which includes the received multiple user consent information.

[0189] In some embodiments, after receiving the first information sent by the second network function, the first network function may unsubscribe from the user's consent to withdraw the subscription.

[0190] Step S2104: The first network function stops data processing for purposes related to at least one user's consent.

[0191] In some embodiments, after receiving a first message from a second network function, the first network function stops the data processing purpose indicated by the first message for each user to agree to.

[0192] For example, if the first information indicates that the user's consent related to model training has been revoked, then the first network function stops model training.

[0193] In some embodiments, the first information is used to indicate that at least one user consent associated with a first identifier has been revoked. The first information includes at least one user consent information and a first identifier, and the first network function stops performing at least one user consent-related data processing purpose through the data associated with the first identifier.

[0194] For example, if at least one user consent information indicates that the user consent for model training and model inference requested by the first network function has been revoked, and the first identifier is UE1, then the first network function stops using data related to UE1 for model training and model inference.

[0195] For example, if at least one user consent information includes a first user consent information and a second user consent information, the first user consent information indicates that the user consent for model inference requested by the first network function has been revoked, and the first identifier corresponding to the first user consent information is UE1, the second user consent information indicates that the user consent for model disclosure requested by the first network function has been revoked, and the first identifier corresponding to the second user consent information is UE2, then the first network function stops using data related to UE1 for model inference and stops using data related to UE2 for model disclosure.

[0196] For example, if the first user consent information indicates that the user consent for the model opening requested by the first network function has been revoked, and the first identifier corresponding to the first user consent information is UE1, then the first network function stops performing model opening related to UE1. For example, it stops opening models belonging to UE1.

[0197] For example, if the first user consent information indicates that the user consent for the model transmission requested by the first network function has been revoked, and the first identifier corresponding to the first user consent information is UE1, then the first network function stops performing model transmission related to UE1. For example, it stops transmitting models belonging to UE1.

[0198] Step S2105: The first network function sends the second information to the third network function.

[0199] In some embodiments, the second information may include at least one of the following: a first identifier and a data collection stop instruction, the data collection stop instruction being used to indicate that data related to the first identifier is stopped for the first network function.

[0200] In some embodiments, if the first information indicates that all data processing purposes related to the first identifier are no longer permitted, the first network function may send a second information to the third network function to instruct the third network function to stop collecting data related to the first identifier for the first network function.

[0201] In some embodiments, "all data processing purposes related to the first identifier are no longer permitted" can be understood as all user consents for all data processing purposes related to the first identifier for the first network function being withdrawn, that is, all user consents requested by the first network function related to the first identifier being revoked.

[0202] In some embodiments, after receiving the first information sent by the second network function, if the first network function determines that all data processing purposes related to the first identifier are no longer permitted, it may send the second information to the third network function. For example, if the data processing purposes related to the first identifier requested by the first network function include model inference and model performance monitoring, and the first information indicates that both model inference and model performance monitoring are no longer permitted, then the first network function may send the second information to the third network function.

[0203] In some embodiments, if the first information indicates that some data processing purposes related to the first identifier and the first network function have been revoked, the first network function may not send the second information to the third network function. The second network function may continue to collect data related to the first identifier for the first network function so that the first network function can perform other permitted data processing purposes based on the collected data. For example, if the data processing purposes related to the first identifier requested by the first network function include model inference and model performance monitoring, and the first information indicates that model inference is no longer permitted, the first network function may not send the second information to the third network function, and the first network function can perform model performance monitoring based on the collected data related to the first identifier.

[0204] In some embodiments, the first network function can also deselect data from the third network function via Nlmf_DataExposure_UnSubscribe.

[0205] Step S2106: The third network function sends a first cancellation request to the first network function.

[0206] In some embodiments, the first cancellation request is used to unsubscribe from the second information.

[0207] In some embodiments, the first cancellation request may include a first identifier so that the third network function can unsubscribe from the second information associated with the first identifier.

[0208] In some embodiments, if a third network function receives the second information sent by a first network function and determines that it has subscribed to the second information from the first network function, it sends the first cancellation request to the first network function.

[0209] In some embodiments, the first cancellation request may be N NWDAF_DataCollectionStop_UnSubscribe.

[0210] It should be noted that if the third network function does not execute step S2102, then step S2106 can be omitted.

[0211] Step S2107: The third network function stops collecting data related to the first identifier for the first network function.

[0212] In some embodiments, after receiving the second information sent by the first network function, the third network function may stop collecting data related to the first identifier for the first network function.

[0213] In some embodiments, after the third network function stops collecting data related to the first identifier for the first network function, it may continue to collect data related to the first identifier for other network functions.

[0214] Step S2108: The third network function sends a confirmation message to the first network function.

[0215] In some embodiments, the confirmation message indicates that the third network function has stopped collecting data related to the first identifier for the first network function.

[0216] In some embodiments, after the third network function stops collecting data related to the first identifier for the first network function, it may send the confirmation information to the first network function.

[0217] Using the above method, the second network function can instruct the first network function that the user's consent has been revoked. When the user's consent is revoked, the first network function can stop the data processing purpose related to the revoked user consent, thereby avoiding the misuse of the user's sensitive data.

[0218] The methods involved in the embodiments of this disclosure may include at least one of the steps S2101 to S2108 described above. For example, step S2101 can be implemented as an independent embodiment, step S2102 can be implemented as an independent embodiment, step S2103 can be implemented as an independent embodiment, step S2107 can be implemented as an independent embodiment, step S2101 + step S2103 can be implemented as an independent embodiment, step S2103 + step S2104 can be implemented as an independent embodiment, step S2102 + step S2105 can be implemented as an independent embodiment, step S2105 + step S2106 can be implemented as an independent embodiment, step S2105 + step S2107 can be implemented as an independent embodiment, step S2105 + step S2108 can be implemented as an independent embodiment, step S2102 + step S2103 + step S2104 can be implemented as an independent embodiment, and step S2105 + step S2106 + step S2107 can be implemented as an independent embodiment, but are not limited thereto.

[0219] In some embodiments, the order of any two steps S2101 to S2108 can be interchanged or they can be performed simultaneously. For example, the order of steps S2104 and S2105 can be interchanged or they can be performed simultaneously, and the order of steps S2106 and S2107 can be interchanged or they can be performed simultaneously. This disclosure does not limit the scope of the embodiments.

[0220] In some embodiments, steps S2101 to S2108 are optional, and one or more of these steps may be omitted or substituted in different embodiments. For example, steps S2102 and S2107 may be omitted.

[0221] In some embodiments, other alternative implementations may be described before or after the specification corresponding to FIG2A.

[0222] Figure 2B is an interactive schematic diagram illustrating a communication method according to an embodiment of the present disclosure. This method can be executed by the aforementioned communication system. As shown in Figure 2B, the method may include:

[0223] Step S2201: The first network function sends a third subscription request to the third network function.

[0224] In some embodiments, a third network function may receive a third subscription request. For example, a third network function may receive a third subscription request sent by a first network function. As another example, a third network function may also receive a third subscription request sent by other entities.

[0225] In some embodiments, the third network function may be an LMF, which can collect input data from the RAN and / or UE.

[0226] In some embodiments, the first network function may be NWDAF.

[0227] In some embodiments, the first network function may be an NWDAF that includes MTLF, which can subscribe to input data and perform model training or model performance monitoring based on the input data.

[0228] In some embodiments, the first network function may determine, based on an internal trigger or a request sent by the LMF, whether to train an AI / ML model using LMF-based AI / ML localization, or to perform performance monitoring of the AI / ML model using LMF-based AI / ML localization.

[0229] In some embodiments, when a first network function determines that model training or model performance monitoring is required, it may send a request to the Network Repository Function (NRF) to discover a third network function. For example, the first network function may invoke the Nnrf_NFDiscovery_Request service operation to send a request to the NRF to discover a third network function, the service operation including the Area of ​​Interest (AoI) and the Nlmf_DataExposure service as discovery parameters.

[0230] In some embodiments, the first network function may send a third request to the third network function to subscribe to or unsubscribe from input data from the third network function.

[0231] For example, the first network function can subscribe to input data from the LMF by calling the Nlmf_DataExposure_Subscribe service operation and unsubscribe from input data from the LMF by calling the Nlmf_DataExposure_UnSubscribe service operation.

[0232] In some embodiments, the third request may include an AoI and a target address to request input data from a third network function, the target address being the address of the first network function.

[0233] In some embodiments, the third request may also include a data processing purpose.

[0234] In some embodiments, the data processing purpose includes at least one of the following: model training, model performance monitoring, model inference, model transfer, and model openness.

[0235] In some embodiments, the third network function obtains user consent information from the second network function for data processing purposes.

[0236] In some embodiments, model transfer involves transferring a trained model and its associated data from one network function to another. For example, a first network function can transfer a trained AI / ML model and its input data to other network functions.

[0237] In some embodiments, model openness involves sharing a trained model and its associated data with other network functions so that these functions can utilize the open model and data. For example, a first network function can share a trained AI / ML model and its input data with other network functions, allowing them to use the AI / ML model and input data.

[0238] For example, the first network function can use the input data for model training, the first network function can also use the input data for model performance monitoring, and the first network function can also use the input data for model inference.

[0239] In some embodiments, the data processing purpose may also be referred to as "purpose", "data use purpose", etc., and this disclosure does not limit it.

[0240] In some embodiments, the third subscription request is used to subscribe to the first information.

[0241] In some embodiments, the first information is used to indicate that at least one user's consent has been revoked, with different user consents used to authorize different data processing purposes.

[0242] In some embodiments, the third subscription request can be N LMF _UserConsentStatus_Subscribe.

[0243] In some embodiments, the third subscription request may include a first identifier for subscribing to a notification of revocation of user consent associated with the first identifier.

[0244] In some embodiments, the first network function may not subscribe to the user consent revocation notification from the third network function. In this case, the third network function may proactively send the first information to the first network function, or the first network function may learn from other network functions whether the user consent of the first network function has been revoked in order to stop the data processing purpose related to the user consent. In this case, step S2201 can be omitted.

[0245] Step S2202: The third network function sends a fourth subscription request to the second network function.

[0246] In some embodiments, the second network function may receive a fourth subscription request. For example, the second network function may receive a fourth subscription request sent by a third network function. As another example, the second network function may also receive a fourth subscription request sent by other entities.

[0247] In some embodiments, the second network function may be UDM / UDR.

[0248] In some embodiments, a third network function may send a fourth request to a second network function in accordance with a third subscription request sent by a first network function to obtain user consent. For example, the third network function may send the fourth request to the second network function in accordance with the data usage purpose and a first identifier sent by the first network function.

[0249] In some embodiments, the third network function may send an AoI to the Access and Mobility Management Function (AMF) to obtain a first identifier.

[0250] In some embodiments, after obtaining user consent, the third network function may send a fourth subscription request to the second network function.

[0251] In some embodiments, the fourth subscription request is used to subscribe to a notification of revocation of user consent associated with the first identifier.

[0252] In some embodiments, the fourth subscription request may be Nudm_SDM_Subscribe / Nudr_DM_Subscribe.

[0253] In some embodiments, a third network function may collect input data from the RAN and / or UE after obtaining user consent.

[0254] In some embodiments, if a third network function obtains the user's consent related to the first identifier, it may collect data related to the first identifier and send the collected data to the first network function.

[0255] In some embodiments, the data sent by the third network function to the first network function includes the first identifier.

[0256] In some embodiments, if the third network function does not obtain the user's consent associated with the first identifier, it will not collect data associated with the first identifier.

[0257] In some embodiments, if the third network function does not obtain the user's consent associated with the first identifier, it may not need to subscribe to the user consent revocation notification associated with the first identifier, and step S2202 may be omitted.

[0258] Step S2203: The second network function sends third information to the third network function.

[0259] In some embodiments, the third network function can receive third information. For example, the third network function can receive third information sent by the second network function. As another example, the third network function can also receive third information sent by other entities.

[0260] In some embodiments, the third information is used to indicate that at least one user's consent has been revoked.

[0261] In some embodiments, if a user withdraws their consent, the second network function may send third information to the third network function.

[0262] In some embodiments, the third information is used to instruct a third network function to send the first information to a first network function.

[0263] In some embodiments, the third information may include a first identifier.

[0264] In some embodiments, the third information may include at least one of the following: at least one user consent information and a first identifier, wherein the user consent information is used to indicate that the user's consent has been withdrawn, and different user consent information corresponds to different data processing purposes.

[0265] In some embodiments, a user may revoke all user consents. For example, all user consents related to the first identifier may be revoked, meaning that the use of data related to the first identifier is not permitted.

[0266] In some embodiments, a user may withdraw partial user consent.

[0267] For example, a user may revoke the user's consent to the first network function, and for example, the first network function may no longer be permitted to use data related to the first identifier for all data processing purposes, that is, the first network function may no longer use data related to the first identifier.

[0268] For example, a user may revoke the user's consent to the third network function, and for example, the third network function may no longer be permitted to collect data related to the first identifier, and the third network function may no longer collect data related to the first identifier.

[0269] For example, a user may revoke user consent for certain data usage purposes granted to the first network function. For instance, if the data processing purposes requested by the first network function when it previously obtained user consent included model training, model performance monitoring, and model inference, the user may revoke user consent for model performance monitoring, meaning that the first network function cannot use data related to the first identifier for model performance monitoring.

[0270] In some embodiments, the first identifier may include an identifier, for example, the first identifier is UE1, and at least one user consent includes user consent related to UE1. The third information may be used to indicate that at least one user consent related to UE1 has been revoked.

[0271] In some embodiments, the first identifier may include multiple identifiers. For example, the first identifier may include UE1 and UE2, and at least one user consent may include user consent related to UE1 and UE2. The third information may be used to indicate that at least one user consent related to UE1 and UE2 has been revoked.

[0272] In some embodiments, at least one user consent may include a user consent whereby a third message indicates that a user consent has been withdrawn. In this case, the third message may include a user consent message. For example, each time a second network function receives a user consent message indicating that a user consent has been withdrawn, it sends a third message to a third network function, the third message including the received user consent message.

[0273] In some embodiments, at least one user consent may also include multiple user consents, i.e., the third information indicates that multiple user consents have been withdrawn. In this case, the first and third information may include multiple user consent information. For example, after the second network function continuously receives multiple user consent information indicating that user consent has been withdrawn, it sends the first information to the third network function, which includes the received multiple user consent information.

[0274] In some embodiments, the third information may further include a first identifier indicating that all user consents associated with the first identifier have been revoked.

[0275] In some embodiments, the third information may be the same as or different from the first information, and this disclosure does not limit this.

[0276] Step S2204: The third network function stops collecting data for at least one data processing purpose as indicated by user consent.

[0277] In some embodiments, after receiving a third message from the second network function, the third network function stops the data collection related to each user's consent as indicated by the third message.

[0278] For example, if the third information indicates that the user's consent related to model training has been revoked, then the third network function stops collecting data for model training.

[0279] In some embodiments, the third information includes at least one user consent information and a first identifier, and the third network function stops collecting data from the first identifier for data processing purposes related to at least one user consent.

[0280] For example, if at least one user consent information indicates that the user consent for model training and model inference requested by the first network function has been revoked, and the first identifier is UE1, then the third network function stops collecting data from UE1 for model training and model inference by the first network function.

[0281] For example, if at least one user consent information includes a first user consent information and a second user consent information, the first user consent information indicating that the user consent for model inference requested by the first network function has been revoked, and the first identifier corresponding to the first user consent information is UE1, the second user consent information indicating that the user consent for model disclosure requested by the first network function has been revoked, and the first identifier corresponding to the second user consent information is UE2, then the third network function stops collecting data from UE1 for model inference of the first network function and stops collecting data from UE2 for model disclosure of the first network function.

[0282] For example, if the first user consent information indicates that the user consent for the model opening requested by the first network function has been revoked, and the first identifier corresponding to the first user consent information is UE1, then the first network function stops performing model opening related to UE1. For example, it stops opening models belonging to UE1.

[0283] For example, if the first user consent information indicates that the user consent for the model transmission requested by the first network function has been revoked, and the first identifier corresponding to the first user consent information is UE1, then the first network function stops performing model transmission related to UE1. For example, it stops transmitting models belonging to UE1.

[0284] In some embodiments, if at least one user consent includes all user consents related to the first identifier, the third network function may stop collecting data related to the first identifier.

[0285] In some embodiments, if the third information includes a first identifier, the third network function may stop collecting data associated with the first identifier.

[0286] Step S2205: The third network function sends the first information to the first network function.

[0287] In some embodiments, the first information is used to indicate that at least one user's consent has been revoked, with different user consents used to authorize different data processing purposes.

[0288] In some embodiments, the first information is used to indicate that at least one user consent associated with the first identifier has been revoked. The first information may include at least one of the following: at least one user consent information and the first identifier. The user consent information is used to indicate that the user consent has been revoked, and different user consent information corresponds to different data processing purposes.

[0289] In some embodiments, a user may revoke all user consents. For example, all user consents related to the first identifier may be revoked, meaning that the use of data related to the first identifier is not permitted.

[0290] In some embodiments, a user may withdraw partial user consent.

[0291] For example, a user may revoke the user's consent to the first network function, and for example, the first network function may no longer be permitted to use data related to the first identifier for all data processing purposes, that is, the first network function may no longer use data related to the first identifier.

[0292] For example, a user may revoke user consent for certain data usage purposes granted to the first network function. For instance, if the data processing purposes requested by the first network function when it previously obtained user consent included model training, model performance monitoring, and model inference, the user may revoke user consent for model performance monitoring, meaning that the first network function cannot use data related to the first identifier for model performance monitoring.

[0293] In some embodiments, the first identifier may include an identifier, for example, the first identifier is UE1, and at least one user consent includes user consent related to UE1. The first information may be used to indicate that at least one user consent related to UE1 has been revoked.

[0294] In some embodiments, the first identifier may include multiple identifiers. For example, the first identifier may include UE1 and UE2, and at least one user consent may include user consent related to UE1 and UE2. The first information may be used to indicate that at least one user consent related to UE1 and UE2 has been revoked.

[0295] In some embodiments, at least one user consent may include a user consent, i.e., a first message indicating that a user consent has been withdrawn. In this case, the first message may include a user consent message. For example, each time a second network function receives a user consent message indicating that a user consent has been withdrawn, it sends a first message to the first network function, the first message including the received user consent message.

[0296] In some embodiments, at least one user consent may also include multiple user consents, i.e., the first information indicates that multiple user consents have been withdrawn. In this case, the first information may include multiple user consent information. For example, after the second network function continuously receives multiple user consent information indicating that user consent has been withdrawn, it sends the first information to the first network function, which includes the received multiple user consent information.

[0297] Step S2206: The first network function sends a second cancellation request to the third network function.

[0298] In some embodiments, the second cancellation request is used to unsubscribe from the first information.

[0299] In some embodiments, after receiving the first information sent by the third network function, the first network function may send a second cancellation request to the third network function to cancel the user's consent to the revocation notification, that is, to cancel the subscription to the first information.

[0300] In some embodiments, if the first network function determines that all user consents related to the first identifier have been revoked, it sends a second cancellation request to the third network function.

[0301] In some embodiments, if the first network function confirms that all user consents related to the first identifier have been revoked, a second cancellation request is sent to the third network function.

[0302] In some embodiments, the second cancellation request may be N LMF _UserConsentStatus_UnSubscribe.

[0303] In some embodiments, the second cancellation request may include a first identifier.

[0304] It should be noted that if the third network function does not execute step S2201, then step S2206 can be omitted.

[0305] Step S2207: The first network function stops data processing for purposes related to at least one user's consent.

[0306] In some embodiments, after receiving a first message sent by a third network function, the first network function stops the data processing purpose indicated by the first message for each user to agree to.

[0307] For example, if the first information indicates that the user's consent related to model training has been revoked, then the first network function stops model training.

[0308] In some embodiments, the first information is used to indicate that at least one user consent associated with a first identifier has been revoked. The first information includes at least one user consent information and a first identifier, and the first network function stops performing at least one user consent-related data processing purpose through the data associated with the first identifier.

[0309] For example, if at least one user consent information indicates that the user consent for model training and model inference requested by the first network function has been revoked, and the first identifier is UE1, then the first network function stops using data related to UE1 for model training and model inference.

[0310] For example, if at least one user consent information includes a first user consent information and a second user consent information, the first user consent information indicates that the user consent for model inference requested by the first network function has been revoked, and the first identifier corresponding to the first user consent information is UE1, the second user consent information indicates that the user consent for model disclosure requested by the first network function has been revoked, and the first identifier corresponding to the second user consent information is UE2, then the first network function stops using data related to UE1 for model inference and stops using data related to UE2 for model disclosure.

[0311] For example, if the first user consent information indicates that the user consent for the model opening requested by the first network function has been revoked, and the first identifier corresponding to the first user consent information is UE1, then the first network function stops performing model opening related to UE1. For example, it stops opening models belonging to UE1.

[0312] For example, if the first user consent information indicates that the user consent for the model transmission requested by the first network function has been revoked, and the first identifier corresponding to the first user consent information is UE1, then the first network function stops performing model transmission related to UE1. For example, it stops transmitting models belonging to UE1.

[0313] Using the above method, the third network function can instruct the first network function that the user's consent has been revoked. When the user's consent is revoked, the first network function can stop the data processing related to the revoked user consent, thereby avoiding the misuse of the user's sensitive data.

[0314] The methods involved in the embodiments of this disclosure may include at least one of steps S2201 to S2207 described above. For example, step S2201 can be implemented as an independent embodiment, step S2202 can be implemented as an independent embodiment, step S2203 can be implemented as an independent embodiment, step S2204 can be implemented as an independent embodiment, step S2205 can be implemented as an independent embodiment, step S2207 can be implemented as an independent embodiment, step S2201 + step S2202 can be implemented as an independent embodiment, step S2202 + step S2203 can be implemented as an independent embodiment, and step S22... Step S2204 can be implemented as an independent embodiment, as can step S2205, step S2206, step S2205, step S2207, step S2201, step S2202, step S2203, step S2203, step S2205, step S2207, but are not limited thereto.

[0315] In some embodiments, the order of any two steps S2201 to S2207 can be interchanged or they can be performed simultaneously. For example, the order of steps S2204 and S2205 can be interchanged or they can be performed simultaneously, and the order of steps S2206 and S2207 can be interchanged or they can be performed simultaneously. This disclosure does not limit the scope of the embodiments.

[0316] In some embodiments, steps S2201 to S2207 are optional, and one or more of these steps may be omitted or substituted in different embodiments. For example, steps S2201 and S2206 may be omitted.

[0317] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0318] In some embodiments, the terms "codebook," "codeword," and "precoding matrix" can be used interchangeably. For example, a codebook can be a collection of one or more codewords / precoding matrices.

[0319] In some embodiments, the terms "uplink", "uplink", and "physical uplink" can be used interchangeably, as can the terms "downlink", "downlink", and "physical downlink", as well as the terms "sidelink", "sidelink", "sidelink communication", "sidelink communication", "direct connection", "direct link", "direct communication", and "direct link communication".

[0320] In some embodiments, the terms “downlink control information (DCI),” “downlink (DL) assignment,” “DL DCI,” “uplink (UL) grant,” and “UL DCI” can be used interchangeably.

[0321] In some embodiments, terms such as "physical downlink shared channel (PDSCH)" and "DL data" can be used interchangeably, as can terms such as "physical uplink shared channel (PUSCH)" and "UL data".

[0322] In some embodiments, the terms “radio”, “wireless”, “radio access network (RAN)”, “access network (AN)”, and “RAN-based” can be used interchangeably.

[0323] In some embodiments, the terms "search space", "search space set", "search space configuration", "search space set configuration", "control resource set (CORESET)", and "CORESET configuration" can be used interchangeably.

[0324] In some embodiments, the terms "synchronization signal (SS)," "synchronization signal block (SSB)," "reference signal (RS)," "pilot," and "pilot signal" can be used interchangeably.

[0325] In some embodiments, terms such as “moment,” “point in time,” “time,” and “time location” can be used interchangeably, as can terms such as “duration,” “segment,” “time window,” “window,” and “time.”

[0326] In some embodiments, the terms "component carrier (CC)," "cell," "frequency carrier," and "carrier frequency" can be used interchangeably.

[0327] In some embodiments, the terms “resource block (RB)”, “physical resource block (PRB)”, “sub-carrier group (SCG)”, “resource element group (REG)”, “PRB pair”, “RB pair”, “resource element (RE)”, and “sub-carrier” can be used interchangeably.

[0328] In some embodiments, terms such as wireless access scheme and waveform can be used interchangeably.

[0329] In some embodiments, the terms "precoding", "precoder", "weight", "precoding weight", "quasi-co-location (QCL)", "transmission configuration indication (TCI) status", "spatial relation", "spatial domain filter", "transmission power", "phase rotation", "antenna port", "antenna port group", "layer", "the number of layers", "rank", "resource", "resource set", "resource group", "beam", "beam width", "beam angle", "antenna", "antenna element", and "panel" can be used interchangeably.

[0330] In some embodiments, the terms “frame”, “radio frame”, “subframe”, “slot”, “sub-slot”, “mini-slot”, “symbol”, “symbol”, and “transmission time interval (TTI)” can be used interchangeably.

[0331] In some embodiments, "acquire," "get," "obtain," "receive," "transmit," "bidirectional transmission," and "send and / or receive" can be used interchangeably and can be interpreted as receiving from other entities, acquiring from protocols, acquiring from higher layers, obtaining through self-processing, or autonomous implementation. Protocols include, for example, at least one of the 3GPP protocol, Wi-Fi protocol, and audio and / or video protocols.

[0332] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transfer,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.

[0333] In some embodiments, terms such as "certain," "preset," "default," "set," "indicated," "a certain," "any," and "first" can be used interchangeably. "Certain A," "preset A," "default A," "set A," "indicated A," "a certain A," "any A," and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.

[0334] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values ​​(e.g., a comparison with a predetermined value), but is not limited thereto.

[0335] In some embodiments, "not expecting to receive" can be interpreted as not receiving on time domain resources and / or frequency domain resources, or as not performing subsequent processing on the data and / or instructions received; "not expecting to send" can be interpreted as not sending, or as sending but not expecting the receiver to respond to the sent content.

[0336] In some embodiments, if an arrow in the interaction diagram representing the sending of information, signaling, etc. from one subject to another passes through other subjects, it can be interpreted as the information being forwarded from one subject to another via other subjects, or it can be interpreted as the information being sent from one subject to another without passing through other subjects.

[0337] Figure 3 is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 3, the present disclosure relates to a communication method that can be executed by a first network function. The method may include:

[0338] Step S3101: Receive the first information.

[0339] The optional implementation of step S3101 can be found in the optional implementation of step S2103 in Figure 2A, step S2205 in Figure 2B, and other related parts in the embodiments involved in Figures 2A and 2B, which will not be repeated here.

[0340] Step S3102: Stop data processing for purposes related to at least one user's consent.

[0341] The optional implementation of step S3102 can be found in the optional implementation of step S2104 in Figure 2A, step S2207 in Figure 2B, and other related parts in the embodiments involved in Figures 2A and 2B, which will not be repeated here.

[0342] In some embodiments, receiving the first information includes:

[0343] The system receives the first information sent by the second network function. The first information is used to indicate that at least one user consent associated with the first identifier has been revoked. The first information includes at least one of the following: at least one user consent information and the first identifier. The user consent information is used to indicate that the user consent has been revoked. Different user consent information corresponds to different data processing purposes. The first identifier includes a user identifier and / or a terminal identifier.

[0344] In some embodiments, the first information indicates that all data processing purposes related to the first identifier are no longer permitted, and a second information is sent to a third network function, the second information being used to instruct the third network function to stop collecting data related to the first identifier for the first network function.

[0345] In some embodiments, the second information includes at least one of the following: the first identifier and a data collection stop indication, wherein the data collection stop indication is used to indicate that data related to the first identifier is stopped for the first network function.

[0346] In some embodiments, the method further includes:

[0347] The system receives a confirmation message from the third network function, indicating that the third network function has stopped collecting data related to the first identifier for the first network function.

[0348] In some embodiments, the method further includes:

[0349] The system receives a first subscription request sent by the third network function, the first subscription request being used to subscribe to the second information.

[0350] In some embodiments, the method further includes:

[0351] The system receives a first cancellation request sent by the third network function, the first cancellation request being used to unsubscribe from the second information.

[0352] In some embodiments, the method further includes:

[0353] Send a second subscription request to the second network function, the second subscription request being used to subscribe to a notification of revocation of user consent associated with the first identifier.

[0354] In some embodiments, receiving the first information includes:

[0355] The system receives the first information sent by the third network function. The first information is used to indicate that at least one user consent associated with the first identifier has been revoked. The first information includes at least one of the following: at least one user consent information and the first identifier. The user consent information is used to indicate that the user consent has been revoked. Different user consent information corresponds to different data processing purposes. The first identifier includes a user identifier and / or a terminal identifier.

[0356] In some embodiments, the method further includes:

[0357] A third subscription request is sent to the third network function, the third subscription request being used to subscribe to the first information.

[0358] In some embodiments, a second cancellation request is sent to the third network function, the second cancellation request being used to unsubscribe from the first information.

[0359] In conjunction with some embodiments of the first aspect, in some embodiments, the data processing purpose includes at least one of the following: model training, model performance monitoring, model inference, model transmission, and model openness.

[0360] In some embodiments, this disclosure enables network entities to promptly halt ongoing AI / ML model training, AI / ML model performance monitoring, or data collection processes when the corresponding user consent is revoked.

[0361] In some embodiments, NWDAF includes MTLF, which can subscribe to input data (i.e., data related to location measurements) for training AI / ML models for AI / ML localization based on LMF or for monitoring the performance of AI / ML models.

[0362] Example 1: NWDAF obtains user consent information from UDM / UDR.

[0363] In some embodiments, FIG4A is an interactive schematic diagram of a communication method proposed in this disclosure. As shown in FIG4A, the method may include:

[0364] Step S4101: NWDAF is determined to be an AI / ML model based on LMF for localization training or to perform performance monitoring on the AI / ML model.

[0365] In some embodiments, the NWDAF containing MTLF determines to train an AI / ML model for LMF-based AI / ML localization based on a request from LMF or an internal trigger, or the NWDAF containing MTLF determines to perform performance monitoring of the AI / ML model for LMF-based AI / ML localization.

[0366] Step S4102a: Obtain user consent via NWDAF.

[0367] In some embodiments, to obtain input data related to a specific UE, NWDAF sends the UE ID and purpose (i.e., model training or model performance monitoring) to UDM / UDR to obtain user consent information.

[0368] Step S4102b: NWDAF sends a notification of changes agreed upon by the user to the UDM / UDR subscription.

[0369] In some embodiments, if user consent is obtained, NWDAF subscribes to the UDM / UDR via Nudm_SDM_Subscribe / Nudr_DM_Subscribe for a change notification regarding the user's subscription data type "User Consent", and then proceeds to step S4103.

[0370] In some embodiments, NWDAF will not subscribe to input data associated with a UE without the consent of the user associated with that UE.

[0371] Step S4103: NWDAF subscribes to or unsubscribes from input data from LMF.

[0372] In some embodiments, the NWDAF subscribes to or unsubscribes from input data from the LMF by invoking the Nlmf_DataExposure_Subscribe / Nlmf_DataExposure_UnSubscribe service operations. To obtain input data relevant to a specific UE, the NWDAF should include the UE ID, user consent check information (i.e., an indication that user consent has been checked and granted), and the notification target address when requesting input data from the LMF.

[0373] Method 1:

[0374] Step S4104: LMF subscribes to data collection stop information from NWDAF.

[0375] In some embodiments, LMF invokes NNWDAF The _DataCollectionStop_Subscribe service operation subscribes to data collection stop information from NWDAF.

[0376] In some embodiments, in order to subscribe to data collection stop information related to a specific UE, the request sent by the LMF to the NWDAF should include the UE ID (e.g., SUPI) and / or event identifier (EventID) and data collection stop.

[0377] Step S4105: LMF collects data.

[0378] In some embodiments, the LMF collects data related to the received UE ID from the RAN / UE.

[0379] Step S4106: LMF sends the collected data to NWDAF.

[0380] In some embodiments, LMF sends the collected data samples to NWDAF by calling the Nlmf_DataExposure_Notify service operation, and then NWDAF trains AI / ML models or performs AI / ML model performance monitoring based on these data samples.

[0381] In step S4107a, the UDM / UDR instructs the NWDAF that all user consents related to a specific UE have been revoked.

[0382] In some embodiments, the UDM / UDR instructs the NWDAF that all user consents related to a specific UE be revoked (i.e., the user revokes consent for all purposes requested by the NWDAF). For example, the UDM / UDR may invoke N... UDM _SDM_Notification / N UDR The _DM_Notification indicates that NWDAF has revoked all user consents related to the specific UE. NWDAF will then cease using data related to that UE (e.g., model training, model monitoring).

[0383] Step S4107b: NWDAF notifies LMF to stop collecting data related to a specific UE.

[0384] In some embodiments, the NWDAF sends a data collection stop notification to the LMF, which may include the UE ID and a data collection stop instruction (i.e., instructing the LMF to stop collecting data related to a specific UE). For example, the NWDAF may call N... NWDAF _DataCollectionStop_Notify notifies LMF.

[0385] In some embodiments, if the LMF receives a data collection stop instruction, the LMF will call N NWDAF The _DataCollectionStop_UnSubscribe service operation cancels the subscription to data collection stop information from NWDAF. The LMF includes the UE ID in the service operation request.

[0386] Step S4108: LMF stops data collection related to a specific UE.

[0387] In some embodiments, if a data collection stop notification is received related to a specific UE (received UE ID), the LMF will stop data collection related to that UE.

[0388] Step S4109: LMF sends confirmation information to NWDAF.

[0389] In some embodiments, the confirmation message indicates that data collection associated with the UE ID has ceased.

[0390] Method 2:

[0391] Step S4104: LMF collects data.

[0392] In some embodiments, the LMF collects data related to the received UE ID from the RAN / UE.

[0393] Step S4105: LMF sends the collected data to NWDAF.

[0394] In some embodiments, LMF sends the collected data samples to NWDAF by calling the Nlmf_DataExposure_Notify service operation, and then NWDAF trains AI / ML models or performs AI / ML model performance monitoring based on these data samples.

[0395] In step S4106a, the UDM / UDR instructs the NWDAF that all user consents related to a specific UE have been revoked.

[0396] In some embodiments, the UDM / UDR instructs the NWDAF to revoke all user consents related to a specific UE. The NWDAF then ceases data use related to that UE (e.g., model training, model monitoring). For example, the UDM / UDR may invoke N... UDM _SDM_Notification / N UDR _DM_Notification indicates that all user consents associated with a specific UE have been revoked by NWDAF.

[0397] Step S4106b: NWDAF notifies LMF to stop collecting data related to a specific UE.

[0398] In some embodiments, the NWDAF sends the UE ID and a data collection stop instruction to the LMF (i.e., instructs the LMF to stop collecting data related to a specific UE).

[0399] Step S4107: LMF stops data collection related to a specific UE.

[0400] In some embodiments, if a data collection stop instruction is received related to a specific UE (received UE ID), the LMF will stop data collection related to that UE.

[0401] Step S4108: LMF sends confirmation information to NWDAF.

[0402] In some embodiments, the confirmation message indicates that data collection associated with the UE ID has ceased.

[0403] Example 2: LMF obtains user consent information from UDM / UDR.

[0404] In some embodiments, FIG4B is an interactive schematic diagram of a communication method proposed in this disclosure. As shown in FIG4B, the method may include:

[0405] Step S4201: NWDAF is determined to be an AI / ML model based on LMF for localization training or to perform performance monitoring on the AI / ML model.

[0406] In some embodiments, the NWDAF including MTLF determines, based on a request from LMF or an internal trigger, whether to train an AI / ML model for LMF-based AI / ML localization, or to perform performance monitoring of the AI / ML model for LMF-based AI / ML localization.

[0407] Step S4202: NWDAF sends a request to NRF to discover LMF.

[0408] In some embodiments, the NWDAF sends a request to the NRF to discover the LMF by invoking the Nnrf_NFDiscovery_Request service operation (step S4202a). This service operation includes the AoI (Region of Interest) and the Nlmf_DataExposure service as discovery parameters. The NRF sends an Nnrf_NFDiscovery_Request Response to the NWDAF (step S4202b).

[0409] Step S4203: NWDAF subscribes to or unsubscribes from input data from LMF.

[0410] In some embodiments, NWDAF subscribes to or unsubscribes from input data from the LMF by invoking the Nlmf_DataExposure_Subscribe / Nlmf_DataExposure_UnSubscribe service operations. NWDAF includes the Region of Interest (AoI) and the notification target address to request input data from the LMF. NWDAF also includes data collection purposes (i.e., model training or model performance monitoring).

[0411] Method 1

[0412] Step S4204: NWDAF subscribes to user consent status information from LMF.

[0413] In some embodiments, NWDAF is invoked by N LMF The _UserConsentStatus_Subscribe service subscribes to user consent status information from the LMF. To subscribe to user consent status information related to a specific UE, the request sent to the LMF should include the UE ID (e.g., SUPI) and / or event identifier (EventID) and the user consent status.

[0414] Step S4205: LMF obtains user consent information.

[0415] In some embodiments, the LMF requests user consent information from the UDM / UDR based on the purpose and the UE ID. This purpose is provided by the NWDAF in step S4203. The LMF obtains the UE ID by sending the region of interest to the AMF.

[0416] Step S4206: LMF subscribes to the UDM / UDR for user-agreed change notifications.

[0417] In some embodiments, if user consent is granted, the LMF subscribes to the UDM / UDR via Nudm_SDM_Subscribe / Nudr_DM_Subscribe for a change notification regarding the user's subscription data type "User Consent", and then proceeds to step S4207.

[0418] In some embodiments, the LMF will not collect input data related to a UE without the consent of the user associated with that UE.

[0419] Step S4207: LMF collects data.

[0420] In some embodiments, the LMF collects input data related to the UE ID from the UE / RAN.

[0421] Step S4208: LMF sends the collected data to NWDAF.

[0422] In some embodiments, the LMF sends the collected data to the NWDAF, including the UE ID.

[0423] In step S4209, the UDM / UDR instructs the LMF that all user consents related to a specific UE have been revoked.

[0424] In some embodiments, the UDM / UDR instructs the LMF that user consent related to a specific UE and a specific purpose has been revoked. The LMF then stops the data collection procedures related to that UE and that purpose. For example, the UDM / UDR may invoke N... UDM _SDM_Notify / N UDR _DM_Notify indicates that LMF's user consent related to a specific UE and a specific purpose has been revoked.

[0425] Step S4210: LMF notifies NWDAF of the UE ID and the purpose of the revocation.

[0426] In some embodiments, the LMF notifies the NWDAF UE ID and the purpose of the revocation (i.e., model training or model performance monitoring). For example, the LMF can be communicated via N... LMF _UserConsentStatus_Notify notifies NWDAF.

[0427] In some embodiments, for a particular UE, if all purposes requested by NWDAF are revoked, NWDAF will invoke N... LMF The _UserConsentStatus_UnSubscribe service operation unsubscribes from the LMF, providing user consent status information. NWDAF includes the UE ID in the service operation request.

[0428] Step S4211: NWDAF stops using input data associated with a specific UE to perform data processing purposes.

[0429] In some embodiments, if user consent associated with a particular UE and a particular purpose is revoked, NWDAF will cease using input data associated with that UE to perform that purpose (i.e., model training or model performance monitoring).

[0430] Method 2

[0431] Step S4204: LMF obtains user consent information.

[0432] In some embodiments, the LMF requests user consent information from the UDM / UDR based on the purpose and the UE ID. This purpose is provided by the NWDAF in step S4203. The LMF obtains the UE ID by sending the region of interest to the AMF.

[0433] Step S4205: LMF subscribes to the UDM / UDR for user-agreed change notifications.

[0434] In some embodiments, if user consent is granted, the LMF subscribes to the UDM / UDR via Nudm_SDM_Subscribe / Nudr_DM_Subscribe for a change notification regarding the user's subscription data type "User Consent", and then proceeds to step S4206.

[0435] In some embodiments, the LMF will not collect input data related to a UE without the consent of the user associated with that UE.

[0436] Step S4206: LMF collects data.

[0437] In some embodiments, the LMF collects input data related to the UE ID from the UE / RAN.

[0438] Step S4207: LMF sends the collected data to NWDAF.

[0439] In some embodiments, the LMF sends the collected data to the NWDAF, including the UE ID.

[0440] In step S4208, the UDM / UDR instructs the LMF that all user consents related to a specific UE have been revoked.

[0441] In some embodiments, the UDM / UDR instructs the LMF that user consent related to a specific UE and a specific purpose has been revoked. The LMF then stops the data collection procedures related to that UE and that purpose.

[0442] Step S4209: LMF sends a user consent status indication to NWDAF.

[0443] In some embodiments, the LMF sends the UE ID and the purpose of the revocation (i.e., model training or model performance monitoring) to the NWDAF.

[0444] In some embodiments, for a specific UE, if all purposes requested by the NWDAF are revoked, the NWDAF unsubscribes from the LMF's user consent status information by invoking the NLMF_UserConsentStatus_UnSubscribe service operation. The NWDAF includes the UE ID in the service operation request.

[0445] Step S4210: NWDAF stops using input data associated with a specific UE to perform data processing purposes.

[0446] In some embodiments, if user consent associated with a particular UE and a particular purpose is revoked, NWDAF will cease using input data associated with that UE to perform that purpose (i.e., model training or model performance monitoring).

[0447] In some embodiments, NWDAF includes at least one of the following:

[0448] If the UDM / UDR instructs the NWDAF that all user consents related to a certain UE have been revoked (i.e., the user has revoked consent for all purposes requested by the NWDAF), the NWDAF should be able to notify the LMF of the relevant UE ID and a data collection cessation instruction (i.e., instruct the LMF to stop collecting data related to that UE);

[0449] If the UDM / UDR instructs the NWDAF that all user consents associated with a UE have been revoked, the NWDAF should be able to send the UE ID and a data collection stop instruction to the LMF (i.e., instructing the LMF to stop collecting data associated with that UE);

[0450] NWDAF should be able to call N LMF The _UserConsentStatus_Subscribe service operation subscribes to user consent status information from the LMF. In order to subscribe to user consent status information related to a specific UE, the request sent to the NWDAF should include the UE ID (e.g., SUPI).

[0451] For a specific UE, if all purposes requested by NWDAF are revoked, NWDAF should be able to call N LMF The _UserConsentStatus_UnSubscribe service operation unsubscribes from the LMF's user consent status information. NWDAF should include the UE ID in the service operation request.

[0452] If user consent associated with a specific UE and a specific purpose is revoked, NWDAF should be able to stop using input data associated with that UE to perform that purpose (i.e., model training or model performance monitoring).

[0453] In some embodiments, the LMF includes at least one of the following:

[0454] LMF should be able to call N NWDAFThe _DataCollectionStop_Subscribe service operation subscribes to data collection stop information from NWDAF. In order to subscribe to data collection stop information related to a specific UE, the request sent to NWDAF should include the UE ID (e.g., SUPI).

[0455] If the LMF receives a data collection stop instruction, the LMF should be able to call N NWDAF The _DataCollectionStop_UnSubscribe service operation cancels the data collection stop information from NWDAF. The LMF should include the UE ID in the service operation request.

[0456] If the UDM / UDR instructs the NWDAF that all user consents associated with a UE have been revoked, the NWDAF should be able to send the UE ID and a data collection stop instruction to the LMF (i.e., instructing the LMF to stop collecting data associated with that UE);

[0457] If a data collection stop instruction is received related to a specific UE, the LMF should be able to stop data collection related to that UE;

[0458] The LMF should be able to send an acknowledgment message to the NWDAF indicating that data collection associated with the UE ID has ceased;

[0459] If the UDM / UDR instructs the LMF that user consent related to a certain UE and a specific purpose has been revoked, the LMF should be able to notify the NWDAF of the relevant UE ID and the purpose of the revocation (i.e., model training or model performance monitoring);

[0460] If the UDM / UDR instructs the LMF that user consent related to a certain UE and specific purpose has been revoked, the LMF should be able to send the UE ID and the purpose of the revocation (i.e., model training or model performance monitoring) to the NWDAF.

[0461] In some embodiments of this disclosure, a communication system is provided, which may include a first network function, a second network function, and a third network function. The first network function can execute the communication method executed by the first network function in the foregoing embodiments of this disclosure; the second network function can execute the communication method executed by the second network function in the foregoing embodiments of this disclosure; and the third network function can execute the communication method executed by the third network function in the foregoing embodiments of this disclosure.

[0462] This disclosure also provides embodiments of apparatus for implementing any of the above methods. For example, an apparatus is provided that includes units or modules for implementing the steps performed by the first network function in any of the above methods. Furthermore, another apparatus is provided that includes units or modules for implementing the steps performed by the second network function in any of the above methods. Still another apparatus is provided that includes units or modules for implementing the steps performed by the third network function in any of the above methods.

[0463] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an Application-Specific Integrated Circuit (ASIC), and the functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), which can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0464] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a Graphics Processing Unit (GPU) (which can be understood as a microprocessor), or a Digital Signal Processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using an Application-Specific Integrated Circuit (ASIC) or a Programmable Logic Device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be hardware circuits designed for artificial intelligence, which can be understood as ASICs, such as Neural Network Processing Units (NPUs), Tensor Processing Units (TPUs), and Deep Learning Processing Units (DPUs).

[0465] Figure 5A is a schematic diagram of the structure of a first network function according to an embodiment of this disclosure. As shown in Figure 5A, the first network function 101 may include at least one of a transceiver module 5101, a processing module 5102, etc. In some embodiments, the transceiver module 5101 is configured to receive first information; wherein the first information is used to indicate that at least one user consent has been revoked, and different user consents are used to authorize different data processing purposes; the processing module 5102 is configured to stop the data processing purpose related to the at least one user consent. Optionally, the transceiver module 5101 may be used to perform at least one of the communication steps such as sending and / or receiving performed by the first network function 101 in any of the above methods (e.g., steps S2101, S2102, S2103, S2105, S2106, S2108, S2201, S2205, S2206, S3101, but not limited thereto), which will not be described in detail here. Optionally, the processing module 5102 may be used to perform at least one of the other steps (such as step S2104, step S2207, step S3102, but not limited thereto) performed by the first network function 101 in any of the above methods, which will not be elaborated here.

[0466] In some embodiments, receiving the first information includes:

[0467] The system receives the first information sent by the second network function. The first information is used to indicate that at least one user consent associated with the first identifier has been revoked. The first information includes at least one of the following: at least one user consent information and the first identifier. The user consent information is used to indicate that the user consent has been revoked. Different user consent information corresponds to different data processing purposes. The first identifier includes a user identifier and / or a terminal identifier.

[0468] In some embodiments, the first information indicates that all data processing purposes related to the first identifier are no longer permitted, and the transceiver module 5101 is further configured to send a second information to a third network function, the second information being used to instruct the third network function to stop collecting data related to the first identifier for the first network function.

[0469] In some embodiments, the second information includes at least one of the following: the first identifier and a data collection stop indication, wherein the data collection stop indication is used to indicate that data related to the first identifier is stopped for the first network function.

[0470] In some embodiments, the transceiver module 5101 is further configured to receive confirmation information sent by the third network function, the confirmation information indicating that the third network function has stopped collecting data related to the first identifier for the first network function.

[0471] In some embodiments, the transceiver module 5101 is further configured to receive a first subscription request sent by the third network function, the first subscription request being used to subscribe to the second information.

[0472] In some embodiments, the transceiver module 5101 is further configured to receive a first cancellation request sent by the third network function, the first cancellation request being used to unsubscribe from the second information.

[0473] In some embodiments, the transceiver module 5101 is further configured to send a second subscription request to the second network function, the second subscription request being used to subscribe to a user consent revocation notification associated with the first identifier.

[0474] In some embodiments, the transceiver module 5101 is further configured to receive the first information sent by a third network function. The first information is used to indicate that at least one user consent associated with a first identifier has been revoked. The first information includes at least one of the following: at least one user consent information and the first identifier. The user consent information is used to indicate that the user consent has been revoked. Different user consent information corresponds to different data processing purposes. The first identifier includes a user identifier and / or a terminal identifier.

[0475] In some embodiments, the transceiver module 5101 is further configured to send a third subscription request to the third network function, the third subscription request being used to subscribe to the first information.

[0476] In some embodiments, the transceiver module 5101 is further configured to send a second cancellation request to the third network function, the second cancellation request being used to unsubscribe from the first information.

[0477] In some embodiments, the data processing purpose includes at least one of the following: model training, model performance monitoring, model inference, model transfer, and model openness.

[0478] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, which may be separate or integrated. Optionally, the transceiver module may be interchangeable with a transceiver.

[0479] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module. Optionally, the processing module may be interchangeable with a processor.

[0480] Figure 5B is a schematic diagram of the structure of a second network function according to an embodiment of this disclosure. As shown in Figure 5B, the second network function 102 may include at least one of a transceiver module 5201, a processing module 5202, etc. In some embodiments, the transceiver module 5201 is configured to receive third information sent by the second network function, and send first information to a first network function according to the third information; wherein the third information is used to indicate that at least one user consent has been revoked, different user consents are used to authorize different data processing purposes, and the first information is used to instruct the first network function to stop the data processing purpose related to the at least one user consent; or, receive second information sent by the first network function; the second information is used to instruct the third network function to stop collecting data related to a first identifier for the first network function, the first identifier including a user identifier and / or a terminal identifier. Optionally, the transceiver module 5201 can be used to perform at least one of the communication steps (such as steps S2101, S2103, S2202, S2203, S3101, but not limited thereto) performed by the second network function 102 in any of the above methods, which will not be elaborated here. Optionally, the processing module 5202 can be used to perform at least one of the other steps performed by the second network function 102 in any of the above methods, which will not be elaborated here.

[0481] In some embodiments, the first information is used to indicate that at least one user consent associated with the first identifier has been revoked. The first information includes at least one of the following: at least one user consent information and the first identifier. The user consent information is used to indicate that the user consent has been revoked. Different user consent information corresponds to different data processing purposes. The first identifier includes a user identifier and / or a terminal identifier.

[0482] In some embodiments, the processing module 5202 is configured to stop collecting data for the data processing purpose indicated by the at least one user consent.

[0483] In some embodiments, the transceiver module 5201 is further configured to receive a third subscription request sent by the first network function, the third subscription request being used to subscribe to the first information.

[0484] In some embodiments, the transceiver module 5201 is further configured to receive a second cancellation request sent by the first network function, the second cancellation request being used to unsubscribe from the first information.

[0485] In some embodiments, the transceiver module 5201 is further configured to send a fourth subscription request to the second network function, the fourth subscription request being used to subscribe to a user consent revocation notification associated with the first identifier.

[0486] In some embodiments, the second information includes at least one of the following: the first identifier and a data collection stop indication, wherein the data collection stop indication is used to indicate that data related to the first identifier is stopped for the first network function.

[0487] In some embodiments, the processing module 5202 is further configured to stop collecting data related to the first identifier for the first network function.

[0488] In some embodiments, the transceiver module 5201 is further configured to send an acknowledgment message to the first network function, the acknowledgment message indicating that the third network function has stopped collecting data related to the first identifier for the first network function.

[0489] In some embodiments, the transceiver module 5201 is further configured to send a first subscription request to the first network function, the first subscription request being used to subscribe to the second information.

[0490] In some embodiments, the transceiver module 5201 is further configured to send a first cancellation request to the first network function, the first cancellation request being used to unsubscribe from the second information.

[0491] In some embodiments, the data processing purpose includes at least one of the following: model training, model performance monitoring, model inference, model transfer, and model openness.

[0492] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, which may be separate or integrated. Optionally, the transceiver module may be interchangeable with a transceiver.

[0493] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module. Optionally, the processing module may be interchangeable with a processor.

[0494] Figure 5C is a schematic diagram of the structure of a third network function according to an embodiment of this disclosure. As shown in Figure 5C, the third network function 103 may include at least one of a transceiver module 5301, a processing module 5302, etc. In some embodiments, the transceiver module 5301 is configured to send first information to a first network function; wherein the first information is used to indicate that at least one user's consent has been revoked, different user consents are used to authorize different data processing purposes, and the first information is used to instruct the first network function to stop the data processing purpose related to the at least one user's consent; or, to send third information to a third network function, the third information being used to indicate that at least one user's consent has been revoked, and the third information being used to instruct the third network function to send the first information to the first network function. Optionally, the transceiver module 5301 can be used to perform at least one of the communication steps such as sending and / or receiving performed by the third network function 103 in any of the above methods (e.g., steps S2102, S2105, S2106, S2108, S2201, S2202, S2203, S2205, S2206, S3101, but not limited thereto), which will not be elaborated here. Optionally, the processing module 5302 can be used to perform at least one of the other steps performed by the third network function 103 in any of the above methods (e.g., steps S2107, S2204, but not limited thereto), which will not be elaborated here.

[0495] In some embodiments, the first information is used to indicate that at least one user consent associated with the first identifier has been revoked. The first information includes at least one of the following: at least one user consent information and the first identifier. The user consent information is used to indicate that the user consent has been revoked. Different user consent information corresponds to different data processing purposes. The first identifier includes a user identifier and / or a terminal identifier.

[0496] In some embodiments, the transceiver module 5301 is further configured to receive a second subscription request sent by the first network function, the second subscription request being used to subscribe to a user consent revocation notification associated with a first identifier, the first identifier including a user identifier and / or a terminal identifier.

[0497] In some embodiments, the transceiver module 5301 is further configured to receive a fourth subscription request sent by the third network function, the fourth subscription request being used to subscribe to a user consent revocation notification associated with a first identifier, the first identifier including a user identifier and / or a terminal identifier.

[0498] In some embodiments, the data processing purpose includes at least one of the following: model training, model performance monitoring, model inference, model transfer, and model openness.

[0499] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, which may be separate or integrated. Optionally, the transceiver module may be interchangeable with a transceiver.

[0500] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module. Optionally, the processing module may be interchangeable with a processor.

[0501] Figure 6A is a schematic diagram of the structure of the communication device 6100 proposed in an embodiment of this disclosure. The communication device 6100 can be a network device (e.g., access network device, core network device, etc.), a terminal (e.g., user equipment, etc.), a chip, chip system, or processor supporting a first network function to implement any of the above methods, a chip, chip system, or processor supporting a second network function to implement any of the above methods, or a chip, chip system, or processor supporting a third network function to implement any of the above methods. The communication device 6100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0502] As shown in Figure 6A, the communication device 6100 includes one or more processors 6101. The processor 6101 can be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control communication devices (e.g., base stations, baseband chips, IoT devices, IoT device chips, DUs or CUs, etc.), execute programs, and process program data. The communication device 6100 is used to execute any of the above methods.

[0503] In some embodiments, the communication device 6100 further includes one or more memories 6102 for storing instructions. Optionally, all or part of the memories 6102 may also be located outside the communication device 6100.

[0504] In some embodiments, the communication device 6100 further includes one or more transceivers 6103. When the communication device 6100 includes one or more transceivers 6103, the transceivers 6103 perform at least one of the communication steps such as sending and / or receiving in the above method (e.g., steps S2101, S2102, S2103, S2105, S2106, S2108, S2201, S2202, S2203, S2205, S2206, S3101, but not limited thereto), and the processor 6101 performs at least one of other steps (e.g., steps S2104, S2107, S2204, S2207, S3102, but not limited thereto).

[0505] In some embodiments, a transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, etc., may be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., may be used interchangeably; and the terms receiver, receiving unit, receiver, receiving circuit, etc., may be used interchangeably.

[0506] In some embodiments, the communication device 6100 may include one or more interface circuits. Optionally, the interface circuit is connected to the memory 6102, and the interface circuit can be used to receive signals from the memory 6102 or other devices, and can be used to send signals to the memory 6102 or other devices. For example, the interface circuit can read instructions stored in the memory 6102 and send the instructions to the processor 6101.

[0507] The communication device 6100 described in the above embodiments may be a first device or an Internet of Things (IoT) device, but the scope of the communication device 6100 described in this disclosure is not limited thereto, and the structure of the communication device 6100 may not be limited by FIG. 6A. The communication device may be a standalone device or may be part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally, the IC collection may also include storage components for storing data and programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, IoT device, smart IoT device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, first device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0508] Figure 6B is a schematic diagram of the structure of chip 6200 according to an embodiment of this disclosure. For cases where the communication device 6100 can be a chip or a chip system, please refer to the schematic diagram of chip 6200 shown in Figure 6B, but it is not limited thereto.

[0509] Chip 6200 includes one or more processors 6201, which are used to perform any of the above methods.

[0510] In some embodiments, chip 6200 further includes one or more interface circuits 6203. Optionally, interface circuit 6203 is connected to memory 6202, and interface circuit 6203 can be used to receive signals from memory 6202 or other devices, and interface circuit 6203 can be used to send signals to memory 6202 or other devices. For example, interface circuit 6203 can read instructions stored in memory 6202 and send the instructions to processor 6201.

[0511] In some embodiments, the interface circuit 6203 performs at least one of the communication steps such as sending and / or receiving in the above method (e.g., steps S2101, S2102, S2103, S2105, S2106, S2108, S2201, S2202, S2203, S2205, S2206, S3101, but not limited thereto), and the processor 6201 performs at least one of other steps (e.g., steps S2104, S2107, S2204, S2207, S3102, but not limited thereto).

[0512] In some embodiments, the terms interface circuit, interface, transceiver pin, transceiver, etc., can be used interchangeably.

[0513] In some embodiments, chip 6200 further includes one or more memories 6202 for storing instructions. Optionally, all or part of the memories 6202 may be located outside of chip 6200.

[0514] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device 6100, cause the communication device 6100 to perform any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

[0515] This disclosure also provides a program product that, when executed by the communication device 6100, causes the communication device 6100 to perform any of the above methods. Optionally, the program product may be a computer program product.

[0516] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.

Claims

1. A communication method, characterized in that, Performed by a first network function, the method includes: Receive first information; wherein the first information is used to indicate that at least one user's consent has been revoked, and different user consents are used to authorize different data processing purposes; Stop data processing for purposes related to the consent of at least one user.

2. The method according to claim 1, characterized in that, The receipt of the first information includes: The system receives the first information sent by the second network function. The first information is used to indicate that at least one user consent associated with the first identifier has been revoked. The first information includes at least one of the following: at least one user consent information and the first identifier. The user consent information is used to indicate that the user consent has been revoked. Different user consent information corresponds to different data processing purposes. The first identifier includes a user identifier and / or a terminal identifier.

3. The method according to claim 2, characterized in that, The method further includes: The first message indicates that all data processing purposes related to the first identifier are no longer permitted, and a second message is sent to the third network function, the second message being used to instruct the third network function to stop collecting data related to the first identifier for the first network function.

4. The method according to claim 3, characterized in that, The second information includes at least one of the following: the first identifier and a data collection stop indication, wherein the data collection stop indication is used to indicate that data related to the first identifier is stopped for the first network function.

5. The method according to claim 3 or 4, characterized in that, The method further includes: The system receives a confirmation message from the third network function, indicating that the third network function has stopped collecting data related to the first identifier for the first network function.

6. The method according to any one of claims 3-5, characterized in that, The method further includes: The system receives a first subscription request sent by the third network function, the first subscription request being used to subscribe to the second information.

7. The method according to claim 6, characterized in that, The method further includes: The system receives a first cancellation request sent by the third network function, the first cancellation request being used to unsubscribe from the second information.

8. The method according to any one of claims 2-7, characterized in that, The method further includes: Send a second subscription request to the second network function, the second subscription request being used to subscribe to a user consent revocation notification associated with the first identifier.

9. The method according to claim 1, characterized in that, The receipt of the first information includes: The system receives the first information sent by the third network function. The first information is used to indicate that at least one user consent associated with the first identifier has been revoked. The first information includes at least one of the following: at least one user consent information and the first identifier. The user consent information is used to indicate that the user consent has been revoked. Different user consent information corresponds to different data processing purposes. The first identifier includes a user identifier and / or a terminal identifier.

10. The method according to claim 9, characterized in that, The method further includes: A third subscription request is sent to the third network function, the third subscription request being used to subscribe to the first information.

11. The method according to claim 10, characterized in that, The method further includes: A second cancellation request is sent to the third network function, the second cancellation request being used to unsubscribe from the first information.

12. The method according to any one of claims 1-11, characterized in that, The data processing objectives include at least one of the following: model training, model performance monitoring, model inference, model transmission, and model sharing.

13. A communication method, characterized in that, Performed by a third network function, the method includes: The system receives a third message from a second network function and sends a first message to a first network function based on the third message; wherein the third message indicates that at least one user's consent has been revoked, different user consents are used to authorize different data processing purposes, and the first message indicates that the first network function should cease data processing purposes related to the at least one user's consent; or... The system receives a second message sent by the first network function; the second message is used to instruct the third network function to stop collecting data related to a first identifier for the first network function, the first identifier including a user identifier and / or a terminal identifier.

14. The method according to claim 13, characterized in that, The first information is used to indicate that at least one user consent associated with the first identifier has been revoked. The first information includes at least one of the following: at least one user consent information and the first identifier. The user consent information is used to indicate that the user consent has been revoked. Different user consent information corresponds to different data processing purposes. The first identifier includes a user identifier and / or a terminal identifier.

15. The method according to claim 13 or 14, characterized in that, The method further includes: Stop collecting data for the data processing purposes indicated by the at least one user's consent.

16. The method according to any one of claims 13-15, characterized in that, The method further includes: Receive a third subscription request sent by the first network function, the third subscription request being used to subscribe to the first information.

17. The method according to claim 16, characterized in that, The method further includes: Receive a second cancellation request sent by the first network function, the second cancellation request being used to unsubscribe from the first information.

18. The method according to any one of claims 13-17, characterized in that, The method further includes: A fourth subscription request is sent to the second network function, the fourth subscription request being used to subscribe to a user consent revocation notification associated with the first identifier.

19. The method according to claim 13, characterized in that, The second information includes at least one of the following: the first identifier and a data collection stop indication, wherein the data collection stop indication is used to indicate that data related to the first identifier is stopped for the first network function.

20. The method according to claim 13 or 19, characterized in that, The method further includes: Stop collecting data related to the first identifier for the first network function.

21. The method according to claim 20, characterized in that, The method further includes: Send a confirmation message to the first network function, the confirmation message indicating that the third network function has stopped collecting data related to the first identifier for the first network function.

22. The method according to any one of claims 13, 19-21, characterized in that, The method further includes: Send a first subscription request to the first network function, the first subscription request being used to subscribe to the second information.

23. The method according to claim 22, characterized in that, The method further includes: Send a first cancellation request to the first network function, the first cancellation request being used to unsubscribe from the second information.

24. The method according to any one of claims 13-23, characterized in that, The data processing objectives include at least one of the following: model training, model performance monitoring, model inference, model transmission, and model sharing.

25. A communication method, characterized in that, Performed by a second network function, the method includes: Send a first message to a first network function; wherein the first message is used to indicate that at least one user's consent has been revoked, different user consents are used to authorize different data processing purposes, and the first message is used to instruct the first network function to cease the data processing purpose associated with the at least one user's consent; or... Send a third message to a third network function, the third message being used to indicate that at least one user's consent has been revoked, the third message being used to instruct the third network function to send the first message to the first network function.

26. The method according to claim 25, characterized in that, The first information is used to indicate that at least one user consent associated with the first identifier has been revoked. The first information includes at least one of the following: at least one user consent information and the first identifier. The user consent information is used to indicate that the user consent has been revoked. Different user consent information corresponds to different data processing purposes. The first identifier includes a user identifier and / or a terminal identifier.

27. The method according to claim 25 or 26, characterized in that, The method further includes: Receive a second subscription request sent by the first network function, the second subscription request being used to subscribe to a user consent revocation notification associated with a first identifier, the first identifier including a user identifier and / or a terminal identifier.

28. The method according to claim 25 or 26, characterized in that, The method further includes: The system receives a fourth subscription request sent by the third network function. The fourth subscription request is used to subscribe to a user consent revocation notification associated with a first identifier, whereby the first identifier includes a user identifier and / or a terminal identifier.

29. The method according to any one of claims 25-28, characterized in that, The data processing objectives include at least one of the following: model training, model performance monitoring, model inference, model transmission, and model sharing.

30. A communication device, characterized in that, The communication device is used to perform the communication method according to any one of claims 1-12, 13-24, and 25-29.

31. A communication system, characterized in that, The device includes a first network function, a second network function, and a third network function, wherein the first network function is configured to implement the communication method of any one of claims 1-12, the third network function is configured to implement the communication method of any one of claims 13-24, and the second network function is configured to implement the communication method of any one of claims 25-29.

32. A storage medium storing instructions, characterized in that, When the instruction is executed on the communication device, the communication device performs the communication method as described in any one of claims 1-12, 13-24, and 25-29.

33. A program product comprising at least one of a program and instructions, characterized in that, When at least one of the programs or instructions is executed by the communication device, it implements the steps of the method according to any one of claims 1-12, 13-24, and 25-29.

Images