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

Abstract

A communication method, a communication device, a communication system, a storage medium, and a program product. The method comprises: a first network element receives at least one of a first request, a second request, and a third request sent by a second network element, wherein the first request is used for requesting to store data capability information of a terminal, the second request is used for requesting to update the data capability information of the terminal, the third request is used for requesting to delete the data capability information of the terminal, and the data capability information is used for indicating information related to data that can be provided by the terminal. That is to say, the first network element stores the data capability information of the terminal on the basis of the first request sent by the second network element, updates the data capability information of the terminal on the basis of the second request sent by the second network element, and deletes the data capability information of the terminal on the basis of the third request sent by the second network element. Therefore, the problem of being unable to manage data capability information of a terminal in an existing network architecture is solved, and data sharing between network elements is achieved, thereby improving the performance of the communication system.

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 the current network architecture, the Access and Mobility Management Function (AMF), the Unified Data Repository (UDR), and the Unified Data Management (UDM) are key network functions responsible for user equipment access, mobility management, and user data storage. 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 embodiments of this disclosure, a communication method is provided, executed by a first network element, the method comprising:

[0005] The system receives at least one of the following from the second network element: a first request, a second request, and a third request; the first request is used to request the storage of the terminal's data capability information, the second request is used to request the updating of the terminal's data capability information, and the third request is used to request the deletion of the terminal's data capability information.

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

[0007] Send at least one of the following to the first network element: a first request, a second request, and a third request, wherein the first request is used to request the first network element to store the data capability information of the terminal, the second request is used to request the first network element to update the data capability information of the terminal, and the third request is used to request the first network element to delete the data capability information of the terminal, wherein the data capability information is used to indicate information related to the data that the terminal can provide.

[0008] According to a third aspect of the embodiments of this disclosure, a communication method is proposed, executed by a fourth network element, the method comprising:

[0009] Send at least one of the following to the second network element: a fifth request, a sixth request, and a seventh request; wherein, the fifth request is used to instruct the second network element to send a first request to the first network element, the first request being used to request the first network element to store the terminal's data capability information; the sixth request is used to instruct the second network element to send a second request to the first network element, the second request being used to request the first network element to update the terminal's data capability information; the seventh request is used to instruct the second network element to send a third request to the first network element, the third request being used to request the first network element to delete the terminal's data capability information, the data capability information being used to indicate information related to the data that the terminal can provide.

[0010] According to a fourth aspect of the present disclosure, a communication method is provided for a communication system, the communication system including a first network element and a second network element, the method comprising:

[0011] The second network element sends at least one of the following to the first network element: a first request, a second request, and a third request. The first request is used to request the storage of the terminal's data capability information. The second request is used to request the updating of the terminal's data capability information. The third request is used to request the deletion of the terminal's data capability information. The data capability information is used to indicate information related to the data that the terminal can provide.

[0012] According to a fifth 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.

[0013] According to a sixth aspect of the present disclosure, a communication system is provided, including a first network element, a second network element, and a fourth network element, wherein the first network element is configured to perform the method described in the optional implementation of the first aspect, the second network element is configured to perform the method described in the optional implementation of the second aspect, and the fourth network element is configured to perform the method described in the optional implementation of the third aspect.

[0014] According to a seventh 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.

[0015] According to an eighth 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.

[0016] The technical solution provided in this disclosure can produce the following beneficial effects: A first network element receives at least one of the following from a second network element: a first request, a second request, and a third request; the first request is used to request the storage of the terminal's data capability information, the second request is used to request the updating of the terminal's data capability information, and the third request is used to request the deletion of the terminal's data capability information, wherein the data capability information is used to indicate information related to the data that the terminal can provide. In other words, the first network element stores the terminal's data capability information according to the first request sent by the second network element, updates the terminal's data capability information according to the second request sent by the second network element, and deletes the terminal's data capability information according to the third request sent by the second network element. This solves the problem of not being able to manage the terminal's data capability information in the existing network architecture, realizes data sharing between network elements, and thus improves the performance of the communication system.

[0017] 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

[0018] 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.

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

[0020] Figure 1B is a schematic diagram of a data collection and reporting architecture 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 2C is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure.

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

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

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

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

[0028] Figure 4A is a schematic diagram of a receipt collection service according to an embodiment of the present disclosure.

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

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

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

[0032] Figure 5C is a schematic diagram of the structure of the fourth network element proposed in an embodiment of this disclosure.

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

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

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

[0036] In a first aspect, embodiments of this disclosure propose a communication method executed by a first network element, the method comprising:

[0037] The system receives at least one of the following from a second network element: a first request, a second request, and a third request; the first request is for requesting the storage of the terminal's data capability information, the second request is for requesting the updating of the terminal's data capability information, and the third request is for requesting the deletion of the terminal's data capability information, wherein the data capability information is used to indicate information related to the data that the terminal can provide.

[0038] In the above embodiments, the second network element can request the first network element to store, update, and delete the terminal's data capability information, which solves the problem of not being able to manage the terminal's data capability information in the existing network architecture, realizes data sharing between network elements, and thus improves the performance of the communication system.

[0039] In conjunction with some embodiments of the first aspect, in some embodiments, the data capability information includes at least one of the following:

[0040] The device functions of the terminal;

[0041] The data types that the terminal can provide;

[0042] The terminal can provide the following data formats;

[0043] User consent information, which indicates whether the user needs to authorize the purpose of using the data provided by the terminal;

[0044] Data transmission capability, which includes user plane transmission and / or control plane transmission.

[0045] In the above embodiments, by storing the device functions, data types, data formats, user authorization information, and transmission capabilities of the terminal, the problem of low service efficiency caused by the lack of data capability information of the terminal in the existing network architecture is solved.

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

[0047] According to the first request, the data capability information of the terminal is stored, wherein the first request includes the user permanent identifier SUPI of the terminal and the data capability information of the terminal;

[0048] According to the second request, update the stored data capability information of the terminal, wherein the second request includes the terminal's SUPI and the data capability information that needs to be updated;

[0049] According to the third request, the stored data capability information of the terminal is deleted. The third request includes the terminal's SUPI, or the terminal's SUPI and the data capability information to be deleted.

[0050] In the above embodiments, the first network element stores the terminal's data capability information according to the first request sent by the second network element, updates the terminal's data capability information according to the second request sent by the second network element, and deletes the terminal's data capability information according to the third request sent by the second network element. This solves the problem of not being able to manage the terminal's data capability information in the existing network architecture, realizes data sharing between network elements, and thus improves the performance of the communication system.

[0051] In conjunction with some embodiments of the first aspect, in some embodiments, the storage of the terminal's data capability information includes:

[0052] Determine the type of data capability information of the terminal;

[0053] Based on the type of data capability information of the terminal, the data capability information of the terminal is stored in the corresponding data capability table; wherein, different types of data capability information correspond to different data capability tables.

[0054] In the above embodiments, data management efficiency is improved by classifying and storing the data capability information of the terminal.

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

[0056] The system receives a fourth request sent by the second network element, the fourth request being used to obtain the SUPI of the terminal, the fourth request including the terminal identifier of the terminal;

[0057] Send a first response message to the second network element, the first response message including the SUPI of the terminal.

[0058] In the above embodiments, the second network element can obtain the SUPI of the terminal from the first network element through the terminal identifier, which simplifies the SUPI acquisition process and improves system performance.

[0059] In conjunction with some embodiments of the first aspect, in some embodiments, the terminal identifier includes at least one of the following: General Public Subscriber Identifier (GPSI), International Mobile Subscriber Identifier (IMSI), Network Access Identifier (NAI), and Subtended Subscriber Identifier (SUCI).

[0060] In the above embodiments, flexible matching of multiple terminal identifiers with SUPI can be supported, improving the efficiency and reliability of user identifier management. In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0061] Send at least one of the following to the second network element: a second response message, a third response message, and a fourth response message, wherein the second response message includes the storage result of the data capability information, the third response message includes the update result of the data capability information, and the fourth response message includes the deletion result of the data capability information.

[0062] In the above embodiments, feeding back the storage, update, or deletion results of data capability information to the second network element can ensure the reliability of data synchronization and enhance the collaborative management capabilities between different network elements.

[0063] In conjunction with some embodiments of the first aspect, in some embodiments, the data capability information stored in the first network element is used by the third network element to select the terminal for data collection.

[0064] In the above embodiments, the stored terminal data capability information can be shared with a third network element, enabling the third network element to select a suitable terminal for data collection based on the terminal's data capability information, thereby improving the efficiency and accuracy of data collection.

[0065] Secondly, this disclosure provides a communication method executed by a second network element, the method comprising:

[0066] Send at least one of the following to the first network element: a first request, a second request, and a third request; the first request is used to request the first network element to store the terminal's data capability information, the second request is used to request the first network element to update the terminal's data capability information, and the third request is used to request the first network element to delete the terminal's data capability information, wherein the data capability information is used to indicate information related to the data that the terminal can provide.

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

[0068] The network receives at least one of the following from the fourth network element: a fifth request, a sixth request, and a seventh request; the fifth request is used to instruct the second network element to send the first request to the first network element, the sixth request is used to instruct the second network element to send the second request to the first network element, and the seventh request is used to instruct the second network element to send the third request to the first network element.

[0069] In the above embodiments, the fourth network element can instruct the first network element to store, update, and delete data capability information through the second network element, which solves the problem of not being able to manage the data capability information of terminals in the existing network architecture, realizes data sharing between network elements, and thus improves the performance of the communication system.

[0070] In conjunction with some embodiments of the second aspect, in some embodiments, the fifth request includes the terminal identifier of the terminal and the data capability information of the terminal, wherein the terminal identifier is used by the second network element to obtain the user permanent identifier (SUPI) of the terminal;

[0071] The sixth request includes the terminal identifier of the terminal and the data capability information that needs to be updated;

[0072] The seventh request includes the terminal identifier of the terminal, or the terminal identifier of the terminal and the data capability information to be deleted.

[0073] In conjunction with some embodiments of the second aspect, in some embodiments,

[0074] The first request includes the user permanent identifier (SUPI) of the terminal and the data capability information of the terminal;

[0075] The second request includes the terminal's SUPI and the data capability information that needs to be updated;

[0076] The third request includes the terminal's SUPI, or the terminal's SUPI and the data capability information to be deleted.

[0077] In conjunction with some embodiments of the second aspect, in some embodiments, the data capability information includes at least one of the following:

[0078] The device functions of the terminal;

[0079] The data types that the terminal can provide;

[0080] The terminal can provide the following data formats;

[0081] User consent information, which indicates whether the user needs to authorize the purpose of using the data provided by the terminal;

[0082] Data transmission capability, which includes user plane transmission and / or control plane transmission.

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

[0084] A fourth request is sent to the first network element, the fourth request being used to obtain the SUPI of the terminal, the fourth request including the terminal identifier of the terminal;

[0085] The terminal receives a first response message sent by the first network element, the first response message including the SUPI of the terminal.

[0086] In conjunction with some embodiments of the second aspect, in some embodiments, the terminal identifier includes at least one of the following: General Public Subscriber Identifier (GPSI), International Mobile Subscriber Identifier (IMSI), Network Access Identifier (NAI), and Subtitling Identifier (SUCI).

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

[0088] The system receives at least one of the following from the first network element: a second response message, a third response message, and a fourth response message; the second response message includes the storage result of the data capability information, the third response message includes the update result of the data capability information, and the fourth response message includes the deletion result of the data capability information.

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

[0090] Send at least one of the following to the fourth network element: a fifth response message, a sixth response message, and a seventh response message; the fifth response message includes the storage result of the data capability information, the sixth response message includes the update result of the data capability information, and the seventh response message includes the deletion result of the data capability information.

[0091] In the above embodiments, the storage results, update results, or deletion results of the terminal's data capability information can be fed back to the fourth network element to ensure the integrity and reliability of cross-network data synchronization and improve network collaborative management capabilities.

[0092] Thirdly, this disclosure provides a communication method executed by a fourth network element, the method comprising:

[0093] Send at least one of the following to the second network element: a fifth request, a sixth request, and a seventh request; wherein, the fifth request is used to instruct the second network element to send a first request to the first network element, the first request being used to request the first network element to store the terminal's data capability information; the sixth request is used to instruct the second network element to send a second request to the first network element, the second request being used to request the first network element to update the terminal's data capability information; the seventh request is used to instruct the second network element to send a third request to the first network element, the third request being used to request the first network element to delete the terminal's data capability information, the data capability information being used to indicate information related to the data that the terminal can provide.

[0094] In conjunction with some embodiments of the third aspect, in some embodiments,

[0095] The fifth request includes the terminal identifier of the terminal and the data capability information of the terminal. The terminal identifier is used by the second network element to obtain the user permanent identifier (SUPI) of the terminal.

[0096] The sixth request includes the terminal identifier of the terminal and the data capability information that needs to be updated;

[0097] The seventh request includes the terminal identifier of the terminal, or the terminal identifier of the terminal and the data capability information to be deleted.

[0098] In conjunction with some embodiments of the third aspect, in some embodiments, the terminal identifier includes at least one of the following: General Public Subscriber Identifier (GPSI), International Mobile Subscriber Identifier (IMSI), Network Access Identifier (NAI), and Subtitling Identifier (SUCI).

[0099] In conjunction with some embodiments of the third aspect, in some embodiments, the data capability information includes at least one of the following:

[0100] The device functions of the terminal;

[0101] The data types that the terminal can provide;

[0102] The terminal can provide the following data formats;

[0103] User consent information, which indicates whether the user needs to authorize the purpose of using the data provided by the terminal;

[0104] Data transmission capability, which includes user plane transmission and / or control plane transmission.

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

[0106] The network receives at least one of the following from the second network element: a fifth response message, a sixth response message, and a seventh response message, wherein the fifth response message includes the storage result of the data capability information, the sixth response message includes the update result of the data capability information, and the seventh response message includes the deletion result of the data capability information.

[0107] Fourthly, embodiments of this disclosure provide a communication method for a communication system, the communication system including a first network element and a second network element, the method comprising:

[0108] The second network element sends at least one of the following to the first network element: the first request, the second request, and the third request, wherein the first request is used to request the storage of the terminal's data capability information, the second request is used to request the updating of the terminal's data capability information, and the third request is used to request the deletion of the terminal's data capability information, wherein the data capability information is used to indicate information related to the data that the terminal can provide.

[0109] Fifthly, embodiments of this disclosure propose a first network element, which may include at least one of a transceiver module and a processing module; wherein the first network element may be used to execute the optional implementation of the first aspect.

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

[0111] In a seventh aspect, embodiments of this disclosure propose a fourth network element, which may include at least one of a transceiver module and a processing module; wherein the fourth network element may be used to execute the optional implementation of the third aspect.

[0112] Eighthly, embodiments of this disclosure provide a first network element, which may include one or more processors; wherein the first network element may be used to execute an optional implementation of the first aspect.

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

[0114] In a tenth aspect, embodiments of this disclosure propose a fourth network element, which may include one or more processors; wherein the fourth network element may be used to execute an optional implementation of the third aspect.

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

[0116] In a twelfth aspect, 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.

[0117] In a thirteenth 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.

[0118] In a fourteenth 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.

[0119] In a fifteenth 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.

[0120] It is understood that the aforementioned first network element, second network element, fourth network element, communication equipment, 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.

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

[0122] 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. In all embodiments of this disclosure, unless otherwise specified or logically conflicting, the terminology and / or descriptions between the embodiments are consistent and can be mutually referenced. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0123] 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.

[0124] 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.

[0125] In the embodiments disclosed herein, "multiple" refers to two or more.

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

[0127] 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 whether there is a branch B); in some embodiments, B (execute B regardless of whether there is a branch A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, both A and B are executed. The same applies when there are more branches such as A, B, C, etc.

[0128] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execute A regardless of whether a branch B exists); in some embodiments, B (execute B regardless of whether a branch A exists); 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, and C.

[0129] 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.

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

[0131] In some embodiments, terms such as "time / frequency" and "time-frequency domain" refer to the time domain and / or frequency domain.

[0132] In some embodiments, terms such as “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “when…”, “if…”, etc. can be used interchangeably. These descriptions all refer to the device making a corresponding action under certain objective circumstances. They do not necessarily limit the time, nor do they require the device to make a judgment action when implementing it, nor do they mean that there must be other limitations.

[0133] 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”.

[0134] 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 element,” “network function,” “network device,” “function,” “node,” “unit,” “section,” “system,” “network,” “chip,” “chip system,” “entity,” and “subject” are interchangeable.

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

[0136] 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.

[0137] 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.

[0138] In some embodiments, access network devices, core network devices, or network devices can be replaced by 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 by 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, and uplink link, downlink, etc., can be replaced with sidelink link.

[0139] 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.

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

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

[0142] 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.

[0143] Figure 1A is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure. As shown in Figure 1A, the communication system 100 may include a terminal 101 and a network device 102.

[0144] In some embodiments, terminal 101 includes, for example, at least one of the following: mobile phone, wearable device, Internet of Things device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, and wireless terminal device in smart home, but is not limited thereto.

[0145] In some embodiments, network device 102 may include at least one of access network device and core network device.

[0146] In some embodiments, the access network device is, for example, a node or device that connects a terminal to a wireless network. The access network device may include at least one of the following in a 5G communication system: evolved Node B (eNB), next-generation eNB (ng-eNB), next-generation Node B (gNB), node B (NB), home node B (HNB), home evolved node B (HeNB), radio backhaul device, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in a 6G communication system, open RAN, cloud RAN, base station in other communication systems, and access node in a Wi-Fi system, but is not limited thereto.

[0147] In some embodiments, the technical solutions of this disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within access network devices involved in the embodiments of this disclosure can be transformed into internal interfaces of Open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.

[0148] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.

[0149] In some embodiments, network device 102 includes at least one of a first network element 1021, a second network element 1022, a third network element 1023, and a fourth network element 1024. Any one or more of the first network element 1021, the second network element 1022, the third network element 1023, and the fourth network element 1024 may be part of an access network device or a core network device, or may be independent of the access network device or the core network device; this disclosure does not limit this.

[0150] In some embodiments, the first network element 1021 is used for data storage / management, such as a UDR or UDM, and the name is not limited to these. It can also be other network elements that implement similar functions.

[0151] In some embodiments, the second network element 1022 is a network element with open network capabilities, or a network element that can provide authentication, authorization, data format conversion and privacy protection functions, such as a Network Exposure Function (NEF). The name is not limited to this, and it can also be other network elements that implement similar functions.

[0152] In some embodiments, the third network element 1023 is used to collect data, such as a data collection function (DCF). The name is not limited to this, and it can also be other network elements that implement similar functions.

[0153] In some embodiments, the fourth network element 1024 is used to convert third-party application requirements into network-recognizable policy requests, or to execute business logic, such as an application function (AF) or an application server (AS), the names of which are not limited thereto, and it may also be other network elements that implement similar functions.

[0154] 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.

[0155] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1A, or to some of the main bodies, but are not limited thereto. The main bodies shown in FIG1A are examples. The communication system may include all or some of the main bodies in FIG1A, or it may include other main bodies outside of FIG1A. 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.

[0156] 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).

[0157] In some embodiments of this disclosure, the data acquisition function can be deployed inside or outside a trusted domain, and it is responsible for managing the configuration state and reporting of data acquisition. When its configuration state changes, the data acquisition function updates the set of network function (NF) profiles available in the Network Function Registration Framework (NRF).

[0158] Figure 1B is a schematic diagram of a data collection and reporting architecture according to an embodiment of the present disclosure. As shown in Figure 1B, the data collection function provides data collection and reporting configuration to the Direct Data Collection Client through reference point R2, to the Indirect Data Collection Client through reference point R3, and to the Application Server (AS) instance through reference point R4, and receives data reports from these reference points respectively.

[0159] In some embodiments, the data collection function processes the received data reports according to processing instructions in its configuration state. Processing activities include, but are not limited to, report format conversion, data normalization, report domain-specific data anonymization, and data (de)aggregation to generate reports that can be exposed as events.

[0160] In some embodiments, the data collection function processes the received data reports according to processing instructions in its configuration state. Processing activities include, but are not limited to, report format conversion, data normalization, report domain-specific data anonymization, and data (de)aggregation to generate reports that can be disclosed as events.

[0161] In some embodiments, the data collection function is responsible for making the processed UE data available to event notification subscribers, whether within a trusted domain, such as the Network Data Analytics Function (NWDAF), or outside a trusted domain, such as an event consumer function in an Application Service Provider.

[0162] In some embodiments, as shown in FIG1B, the direct data collection client is responsible for collecting relevant data in the UE and sending data reports to the data collection AF via reference point R2.

[0163] In some embodiments, as shown in FIG1B, the UE application shares relevant data with the direct data collection client through reference point R7, which can be achieved through a combination of application design, application configuration of R8 and / or application configuration of R7.

[0164] In some embodiments, as shown in Figure 1B, the Application Server (AS) instance can collect data and report it to the data collection function via reference point R4, whether it is inside or outside the trusted domain.

[0165] In some embodiments, NWDAF is the primary consumer of processed UE data.

[0166] In some embodiments, AMF / UDR / UDM does not support storing UE data capability information.

[0167] Figure 2A is an interactive schematic diagram illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 2A, the present disclosure relates to a communication method, which includes the following steps:

[0168] Step S2101: The fourth network element sends a fifth request to the second network element.

[0169] In some embodiments, the second network element can receive a fifth request. For example, the second network element can receive a fifth request sent by a fourth network element. As another example, the second network element can also receive a fifth request sent by other entities.

[0170] In some embodiments, the second network element may be, for example, NEF, and the fourth network element may be, for example, AF / AS.

[0171] In some embodiments, the fifth request may include the terminal's terminal identifier and the terminal's data capability information.

[0172] In some embodiments, the terminal identifier may include at least one of the following: Generic Public Subscription Identifier (GPSI), International Mobile Subscriber Identity (IMSI), Network Access Identifier (NAI), or Subscription Concealed Identifier (SUCI).

[0173] In some embodiments, the fifth request may be used to request data capability information of the storage terminal. Optionally, the data capability information of the storage terminal may be understood as the data capability information of the terminal created in the terminal's subscription / configuration file.

[0174] In some embodiments, the name of the fifth request is not limited, and may be, for example, "UE_dataCapa_provisioning_create request", "data capability information creation request", "data capability information storage request", etc.

[0175] In some embodiments, when a terminal needs to register data capability information, it can send the fifth request to the second network element through the fourth network element.

[0176] Step S2102: The second network element sends a fourth request to the first network element.

[0177] In some embodiments, the first network element may be, for example, a UDM / UDR.

[0178] In some embodiments, after receiving the fifth request sent by the fourth network element, the second network element may send the fourth request to the first network element.

[0179] In some embodiments, the fourth request is used to obtain the terminal's Subscription Permanent Identifier (SUPI).

[0180] In some embodiments, the fourth request includes the terminal identifier of the terminal.

[0181] In some embodiments, if the terminal is identified as GPSI, the fourth request may be, for example, Nudm_SDM-Get(GPSI).

[0182] In some embodiments, the name of the fourth request is not limited, such as "Nudm_SDM-Get request", "SUPI acquisition request", etc.

[0183] In some embodiments, the second network element can determine the SUPI corresponding to the terminal identifier indicated in the fourth request by using a pre-stored mapping relationship between terminal identifiers and SUPIs. For example, the second network element can determine the SUPI corresponding to the GPSI indicated in the fourth request by using a pre-stored mapping relationship between GPSI and SUPIs.

[0184] Step S2103: The first network element sends a first response message to the second network element.

[0185] In some embodiments, after the first network element determines the SUPI of the terminal according to the fourth request, it may send a first response message to the second network element.

[0186] In some embodiments, the first response message may include the terminal's SUPI.

[0187] Step S2104: The second network element sends a first request to the first network element.

[0188] In some embodiments, the first request is used to indicate the data capability information of the first network element storage terminal.

[0189] In some embodiments, the first request may include the terminal's SUPI and the terminal's data capability information.

[0190] In some embodiments, the data capability information includes at least one of the following:

[0191] Terminal device functions;

[0192] The data types that the terminal can provide;

[0193] The data formats that the terminal can provide;

[0194] User consent information, which indicates whether user authorization is required for the purpose of using data provided by the terminal;

[0195] Data transmission capability, which includes user plane transmission and / or control plane transmission.

[0196] In some embodiments, the device functions may be those of the terminal, such as cameras and sensors.

[0197] In some embodiments, device functionality may also be referred to as “device capability”, “device capability”, etc.

[0198] In some embodiments, the data type may include at least one of the following: video data, sensing data, and location data. The data type that the terminal can provide can be determined according to the device functions of the terminal. For example, if the device functions of the terminal include a camera, the data type may be video data; if the device functions of the terminal include a sensor, the data type may be sensing data.

[0199] In some embodiments, the data format can be determined based on the data type, for example, it can be 3K or 4K.

[0200] In some embodiments, the user consent information may indicate the purpose of using the data provided by the terminal that requires user authorization, i.e., authorization from the terminal is required when using the data provided by the terminal; the user consent information may also indicate the purpose of using the data provided by the terminal that does not require user authorization, i.e., authorization from the terminal is not required when using the data provided by the terminal.

[0201] In some embodiments, the consent information may be used to indicate whether the user needs to authorize the purpose of use of each type of data provided by the terminal, or to indicate whether the user needs to authorize the purpose of use of all data provided by the terminal.

[0202] In some embodiments, the purpose of using the data may include, for example, model training, model inference, model performance monitoring, etc.

[0203] For example, the terminal's data capability information may include: camera, video data, data format, user consent information, control plane transmission, and user plane transmission; as another example, the terminal's data capability information may include: sensor, sensing data, data format, user consent information, and control plane transmission.

[0204] In some embodiments, after receiving the first response message sent by the first network element, the second network element may send a first request to the first network element to request the first network element to store the data capability information of the terminal.

[0205] It should be noted that the second network element can also obtain the terminal's SUPI through other methods of related technologies, in which case steps S2102 to S2103 can be omitted.

[0206] It should also be noted that the second network element can also send a first request to the first network element based on the request of other entities, in which case step S2104 can be omitted.

[0207] Step S2105: The first network element stores the data capability information of the terminal.

[0208] In some embodiments, after receiving a first request from a second network element, the first network element may store the data capability information indicated by the first request.

[0209] In some embodiments, when the first network element stores the terminal's data capability information, it can bind the terminal's SUPI with the terminal's data capability information to ensure that the data capability information is accurately associated with a specific user and avoid confusion.

[0210] In some embodiments, the first network element may store the terminal's data capability information in the terminal's subscription data table. For example, the first network element may store the following data capability information in the terminal's subscription data table: camera, video data, data format, user consent information, control plane transmission, and user plane transmission; sensor, sensing data, data format, user consent information, and control plane transmission.

[0211] In some embodiments, different terminals may correspond to different subscription data tables, and the data capability information of each terminal may be stored in the corresponding subscription data table.

[0212] In some embodiments, each terminal's subscription data table can be bound to the terminal's SUPI so that the terminal's subscription data table can be found through the SUPI.

[0213] In some embodiments, the first network element may also store different types of data capability information in different data capability tables, thereby improving data management efficiency by classifying and storing the terminal's data capability information.

[0214] In some embodiments, the data capability table may be a sub-table of the subscription data table, used to store terminal-specific capability information.

[0215] In some embodiments, the first network element determines the type of data capability information of the terminal, and stores the data capability information of the terminal in the corresponding data capability table according to the type of data capability information of the terminal; wherein, different types of data capability information correspond to different data capability tables.

[0216] In some embodiments, the type of data capability information may include at least one of the following: perception data capability, video data capability, and location data capability.

[0217] For example, the first network element can store data capability information of type perception data capability in data capability table 1, data capability information of type video data capability in data capability table 2, and data capability information of type location data capability in data capability table 3. Taking location data capability as an example, the data capability information stored in table 3 may include location data and user consent for AI positioning model training / AI model performance monitoring.

[0218] In some embodiments, the data capability information of the terminal stored in the first network element can be used by the third network element to select the terminal for data collection.

[0219] In some embodiments, the third network element may be, for example, a DCF.

[0220] In some embodiments, when a third network element needs to collect data, it can obtain the data capability information of the terminal stored in the first network element, and select a suitable terminal for data collection based on the data capability information.

[0221] Step S2106: The first network element sends a second response message to the second network element.

[0222] In some embodiments, the second response message may include the storage result of the terminal's data capability information.

[0223] In some embodiments, after the first network element stores the data capability information of the terminal, it can send the second response message to the second network element to inform the second network element of the storage result of the data capability information.

[0224] Step S2107: The second network element sends a fifth response message to the fourth network element.

[0225] In some embodiments, the fifth response message may include the storage result of the terminal's data capability information.

[0226] In some embodiments, after receiving the second response message sent by the first network element, the second network element may send a fifth response message to the fourth network element to inform the fifth network element of the storage result of the data capability information.

[0227] It should be noted that if the second network element sends a first request to the first network element based on the request of other entities, step S2107 can be omitted.

[0228] Using the above method, the first network element stores the terminal's data capability information based on the first request sent by the second network element, which solves the problem that the existing network architecture cannot store the terminal's data capability information, realizes data sharing between network elements, and thus improves the performance of the communication system.

[0229] 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.

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

[0231] 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.

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

[0233] 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.

[0234] 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.

[0235] 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.

[0236] The communication method involved in the embodiments of this disclosure may include at least one of steps S2101 to S2107. For example, step S2104 may be implemented as a standalone embodiment, and step S2104+S2105 may be implemented as a standalone embodiment, but is not limited thereto.

[0237] In some embodiments, steps S2101 and S2107 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0238] In some embodiments, steps S2102 and S2103 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0239] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0240] Figure 2B is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 2B, the present disclosure relates to a communication method, which includes the following steps:

[0241] Step S2201: The fourth network element sends a sixth request to the second network element.

[0242] In some embodiments, the second network element can receive a sixth request. For example, the second network element can receive a sixth request sent by a fourth network element. As another example, the second network element can also receive a sixth request sent by other entities.

[0243] In some embodiments, the second network element may be, for example, NEF, and the fourth network element may be, for example, AF / AS.

[0244] In some embodiments, the sixth request may include the terminal's terminal identifier and data capability information that needs to be updated.

[0245] In some embodiments, the terminal identifier may include at least one of the following: GPSI, IMSI, NAI, SUCI.

[0246] In some embodiments, the sixth request may be used to request an update of the stored terminal's data capability information.

[0247] In some embodiments, the name of the sixth request is not limited, and may be, for example, "UE_dataCapa_provisioning_update request" or "data capability information update request".

[0248] In some embodiments, when a terminal needs to update its data capability information, it can send the sixth request to the second network element through the fourth network element.

[0249] Step S2202: The second network element sends a fourth request to the first network element.

[0250] In some embodiments, the first network element may be, for example, a UDM / UDR.

[0251] In some embodiments, after receiving the fifth request sent by the fourth network element, the second network element may send the fourth request to the first network element.

[0252] In some embodiments, the fourth request is used to obtain the SUPI of the terminal.

[0253] In some embodiments, the fourth request includes the terminal identifier of the terminal.

[0254] In some embodiments, if the terminal is identified as GPSI, the fourth request may be, for example, Nudm_SDM-Get(GPSI).

[0255] In some embodiments, the name of the fourth request is not limited, such as "Nudm_SDM-Get request", "SUPI acquisition request", etc.

[0256] In some embodiments, the second network element can determine the SUPI corresponding to the terminal identifier indicated in the fourth request by using a pre-stored mapping relationship between terminal identifiers and SUPIs. For example, the second network element can determine the SUPI corresponding to the GPSI indicated in the fourth request by using a pre-stored mapping relationship between GPSI and SUPIs.

[0257] Step S2203: The first network element sends a first response message to the second network element.

[0258] In some embodiments, after the first network element determines the SUPI of the terminal according to the fourth request, it may send a first response message to the second network element.

[0259] In some embodiments, the first response message may include the terminal's SUPI.

[0260] In some embodiments, the second network element may also obtain the terminal's SUPI through other methods of related technologies, in which case steps S2202 to S2203 may be omitted.

[0261] Step S2204: The second network element sends a second request to the first network element.

[0262] In some embodiments, the first network element may be, for example, a UDM / UDR.

[0263] In some embodiments, the second request is used to instruct the first network element to update the stored data capability information of the terminal.

[0264] In some embodiments, the second request may include the terminal's SUPI and data capability information that needs to be updated.

[0265] In some embodiments, the data capability information includes at least one of the following:

[0266] Terminal device functions;

[0267] The data types that the terminal can provide;

[0268] The data formats that the terminal can provide;

[0269] User consent information, which indicates whether user authorization is required for the purpose of using data provided by the terminal;

[0270] Data transmission capability, which includes user plane transmission and / or control plane transmission.

[0271] In some embodiments, the device functions may be those of the terminal, such as cameras and sensors.

[0272] In some embodiments, device functionality may also be referred to as “device capability”, “device capability”, etc.

[0273] In some embodiments, the data type may include at least one of the following: video data, sensing data, and location data. The data type that the terminal can provide can be determined according to the device functions of the terminal. For example, if the device functions of the terminal include a camera, the data type may be video data; if the device functions of the terminal include a sensor, the data type may be sensing data.

[0274] In some embodiments, the data format can be determined based on the data type, for example, it can be 3K or 4K.

[0275] In some embodiments, the user consent information may indicate the purpose of using the data provided by the terminal that requires user authorization, i.e., authorization from the terminal is required when using the data provided by the terminal; the user consent information may also indicate the purpose of using the data provided by the terminal that does not require user authorization, i.e., authorization from the terminal is not required when using the data provided by the terminal.

[0276] In some embodiments, the consent information may be used to indicate whether the user needs to authorize the purpose of use of each type of data provided by the terminal, or to indicate whether the user needs to authorize the purpose of use of all data provided by the terminal.

[0277] In some embodiments, the purpose of using the data may include, for example, model training, model inference, model performance monitoring, etc.

[0278] For example, the terminal's data capability information may include: camera, video data, data format, user consent information, control plane transmission, and user plane transmission; as another example, the terminal's data capability information may include: sensor, sensing data, data format, user consent information, and control plane transmission.

[0279] In some embodiments, after receiving the sixth request sent by the fourth network element, the second network element may send a second request to the first network element to request the first network element to update the terminal's data capability information.

[0280] It should be noted that the second network element can also send a second request to the first network element based on the request of other entities, in which case step S2204 can be omitted.

[0281] Step S2205: The first network element updates the stored terminal data capability information according to the second request.

[0282] In some embodiments, after receiving a second request from a second network element, the first network element can look up the data capability table of the storage terminal's data capability information according to the SUPI indicated by the second request, and update the data capability information in the data capability table to the data capability information that needs to be updated as indicated by the second request.

[0283] In some embodiments, updating the stored terminal data capability information can be understood as replacing the data capability information stored in the first network element with the data capability information that needs to be updated as indicated by the second request.

[0284] In some embodiments, the data capability information to be updated may include all or part of the stored data capability information. For example, the second request may instruct the updating of all data capability information stored by the first network element, i.e., updating the subscription data table corresponding to the terminal, or it may instruct the updating of one or more data capability tables. For instance, if the second request instructs that the data capability information to be updated includes all data capability information stored by the first network element, then the first network element updates the subscription data table corresponding to the terminal; if the second request instructs that the data capability information to be updated includes data capability information corresponding to sensing data capabilities, then the first network element updates data capability table 1 corresponding to the terminal.

[0285] Step S2206: The first network element sends a third response message to the second network element.

[0286] In some embodiments, the third response message includes an update result of the terminal's data capability information.

[0287] In some embodiments, after the first network element updates the data capability information of the terminal, it can send the third response message to the second network element to inform the second network element of the update result of the data capability information.

[0288] Step S2207: The second network element sends a sixth response message to the fourth network element.

[0289] In some embodiments, the sixth response message may include the update result of the terminal's data capability information.

[0290] In some embodiments, after receiving the third response message sent by the first network element, the second network element may send a sixth response message to the fourth network element to inform the fifth network element of the update result of the data capability information.

[0291] It should be noted that if the second network element sends a second request to the first network element based on the request of other entities, step S2207 can be omitted.

[0292] Using the above method, the first network element updates the terminal's data capability information according to the second request sent by the second network element, thereby realizing data synchronization between network elements and improving the performance of the communication system.

[0293] The communication method involved in the embodiments of this disclosure may include at least one of steps S2201 to S2207. For example, step S2204 may be implemented as a standalone embodiment, and step S2204+S2205 may be implemented as a standalone embodiment, but is not limited thereto.

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

[0295] In some embodiments, steps S2202 and S2203 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0296] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0297] Figure 2C is an interactive schematic diagram illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 2C, the present disclosure relates to a communication method, which includes the following steps:

[0298] Step S2301: The fourth network element sends the seventh request to the second network element.

[0299] In some embodiments, the second network element can receive a seventh request. For example, the second network element can receive a seventh request sent by a fourth network element. As another example, the second network element can also receive a seventh request sent by other entities.

[0300] In some embodiments, the second network element may be, for example, NEF, and the fourth network element may be, for example, AF / AS.

[0301] In some embodiments, the seventh request may include the terminal identifier of the terminal, or the terminal identifier and data capability information to be deleted.

[0302] In some embodiments, if it is necessary to delete all stored data capability information, the seventh request may only include the terminal identifier; if it is necessary to delete some stored data capability information, the seventh request may include the terminal identifier and the data capability information to be deleted.

[0303] In some embodiments, the terminal identifier may include at least one of the following: GPSI, IMSI, NAI, SUCI.

[0304] In some embodiments, the seventh request may be used to request the deletion of stored terminal data capability information.

[0305] In some embodiments, the name of the seventh request is not limited, and may be, for example, "UE_dataCapa_provisioning_remove request", "data capability information deletion request", "data capability information removal request", etc.

[0306] In some embodiments, when a terminal needs to delete data capability information, it can send the seventh request to the second network element through the fourth network element.

[0307] Step S2302: The second network element sends a fourth request to the first network element.

[0308] In some embodiments, the first network element may be, for example, a UDM / UDR.

[0309] In some embodiments, after receiving the fifth request sent by the fourth network element, the second network element may send the fourth request to the first network element.

[0310] In some embodiments, the fourth request is used to obtain the SUPI of the terminal.

[0311] In some embodiments, the fourth request includes the terminal identifier of the terminal.

[0312] In some embodiments, if the terminal is identified as GPSI, the fourth request may be, for example, Nudm_SDM-Get(GPSI).

[0313] In some embodiments, the name of the fourth request is not limited, such as "Nudm_SDM-Get request", "SUPI acquisition request", etc.

[0314] In some embodiments, the second network element can determine the SUPI corresponding to the terminal identifier indicated in the fourth request by using a pre-stored mapping relationship between terminal identifiers and SUPIs. For example, the second network element can determine the SUPI corresponding to the GPSI indicated in the fourth request by using a pre-stored mapping relationship between GPSI and SUPIs.

[0315] Step S2303: The first network element sends a first response message to the second network element.

[0316] In some embodiments, after the first network element determines the SUPI of the terminal according to the fourth request, it may send a first response message to the second network element.

[0317] In some embodiments, the first response message may include the terminal's SUPI.

[0318] In some embodiments, the second network element may also obtain the terminal's SUPI through other methods of related technologies, in which case steps S2302 to S2303 may be omitted.

[0319] Step S2304: The second network element sends a third request to the first network element.

[0320] In some embodiments, the first network element may be, for example, a UDM / UDR.

[0321] In some embodiments, the third request is used to instruct the first network element to delete the stored data capability information of the terminal.

[0322] In some embodiments, the third request may include the terminal's SUPI, or the SUPI and data capability information to be deleted.

[0323] In some embodiments, the data capability information includes at least one of the following:

[0324] Terminal device functions;

[0325] The data types that the terminal can provide;

[0326] The data formats that the terminal can provide;

[0327] User consent information, which indicates whether user authorization is required for the purpose of using data provided by the terminal;

[0328] Data transmission capability, which includes user plane transmission and / or control plane transmission.

[0329] In some embodiments, the device functions may be those of the terminal, such as cameras and sensors.

[0330] In some embodiments, device functionality may also be referred to as “device capability”, “device capability”, etc.

[0331] In some embodiments, the data type may include at least one of the following: video data, sensing data, and location data. The data type that the terminal can provide can be determined according to the device functions of the terminal. For example, if the device functions of the terminal include a camera, the data type may be video data; if the device functions of the terminal include a sensor, the data type may be sensing data.

[0332] In some embodiments, the data format can be determined based on the data type, for example, it can be 3K or 4K.

[0333] In some embodiments, the user consent information may indicate the purpose of using the data provided by the terminal that requires user authorization, i.e., authorization from the terminal is required when using the data provided by the terminal; the user consent information may also indicate the purpose of using the data provided by the terminal that does not require user authorization, i.e., authorization from the terminal is not required when using the data provided by the terminal.

[0334] In some embodiments, the consent information may be used to indicate whether the user needs to authorize the purpose of use of each type of data provided by the terminal, or to indicate whether the user needs to authorize the purpose of use of all data provided by the terminal.

[0335] In some embodiments, the purpose of using the data may include, for example, model training, model inference, model performance monitoring, etc.

[0336] For example, the terminal's data capability information may include: camera, video data, data format, user consent information, control plane transmission, and user plane transmission; as another example, the terminal's data capability information may include: sensor, sensing data, data format, user consent information, and control plane transmission.

[0337] In some embodiments, after receiving the seventh request sent by the fourth network element, the second network element may send a third request to the first network element to request the first network element to delete the terminal's data capability information.

[0338] It should be noted that the second network element can also send a third request to the first network element based on the request of other entities, in which case step S2304 can be omitted.

[0339] Step S2305: The first network element deletes the stored terminal data capability information according to the third request.

[0340] In some embodiments, after receiving a third request from a second network element, the first network element can search the data capability table of the storage terminal's data capability information according to the SUPI indicated by the third request, and delete the data capability information in the data capability table.

[0341] In some embodiments, deleting the stored data capability information of a terminal can be understood as deleting the data capability information stored in the first network element, or deleting the subscription data table corresponding to the terminal.

[0342] In some embodiments, if the third request includes the terminal's SUPI but not the data capability information, the first network element can delete all stored data capability information, for example, it can delete the subscription data table corresponding to the terminal; if the third request includes the terminal's SUPI and the data capability information to be deleted, the first network element can delete the data capability information to be deleted indicated by the third request, for example, when the third request indicates the data capability information corresponding to the sensing data capability, it can delete the data capability table 1 corresponding to the terminal.

[0343] Step S2306: The first network element sends a fourth response message to the second network element.

[0344] In some embodiments, the fourth response message includes the result of deleting the terminal's data capability information.

[0345] In some embodiments, after the first network element deletes the terminal's data capability information, it can send the fourth response message to the second network element to inform the second network element of the deletion result of the data capability information.

[0346] Step S2307: The second network element sends a seventh response message to the fourth network element.

[0347] In some embodiments, the seventh response message may include the result of deleting the terminal's data capability information.

[0348] In some embodiments, after receiving the fourth response message sent by the first network element, the second network element may send a seventh response message to the fourth network element to inform the fifth network element of the deletion result of the data capability information.

[0349] It should be noted that if the second network element sends a third request to the first network element based on the request of other entities, step S2307 can be omitted.

[0350] Using the above method, the first network element deletes the terminal's data capability information based on the third request sent by the second network element, thereby deleting the terminal's data capability information as needed, realizing dynamic management of storage resources, and avoiding redundant data occupying storage resources.

[0351] The communication method involved in the embodiments of this disclosure may include at least one of steps S2301 to S2307. For example, step S2304 may be implemented as a standalone embodiment, and step S2304 + step S2305 may be implemented as a standalone embodiment, but is not limited thereto.

[0352] In some embodiments, steps S2301 and S2307 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0353] In some embodiments, steps S2302 and S2303 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0354] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

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

[0356] Step S3101: Receive the first request.

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

[0358] Optionally, the first message may be received during the transmission of the first PUSCH.

[0359] Step S3102: Store the data capability information of the terminal according to the first request.

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

[0361] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

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

[0363] Step S3201: Receive the second request.

[0364] The optional implementation of step S3201 can be found in the optional implementation of step S2204 in Figure 2B, and other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0365] Optionally, the first message may be received during the transmission of the first PUSCH.

[0366] Step S3202: Update the stored terminal data capability information according to the second request.

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

[0368] In some embodiments, after the first network element stores the data capability information of the terminal, the stored data capability information can be updated. After executing the embodiment shown in FIG3A, the embodiment shown in FIG3B can be executed. For example, after executing steps S3101 and S3102, steps S3201 and S3202 are executed.

[0369] It should be noted that the embodiments disclosed herein do not limit the number of times or the time for updating data capability information. It should be understood that the embodiments shown in Figure 3B can be executed multiple times at any time after the embodiment shown in Figure 3A is executed.

[0370] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

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

[0372] Step S3301: Receive the third request.

[0373] The optional implementation of step S3301 can be found in the optional implementation of step S2304 in Figure 2C, and other related parts in the embodiments involved in Figure 2C, which will not be repeated here.

[0374] Optionally, the first message may be received during the transmission of the first PUSCH.

[0375] Step S3302: Delete the stored terminal data capability information according to the third request.

[0376] The optional implementation of step S3302 can be found in the optional implementation of step S2305 in Figure 2C, and other related parts in the embodiments involved in Figure 2C, which will not be repeated here.

[0377] In some embodiments, after the first network element stores the data capability information of the terminal, the stored data capability information can be deleted, and the embodiment shown in FIG3C can be executed after executing the embodiment shown in FIG3A. For example, steps S3301 and S3302 are executed after steps S3101 and S3102.

[0378] In some embodiments, after the first network element updates the terminal's data capability information, the updated data capability information can be deleted, and the embodiment shown in FIG3C can be executed after executing the embodiment shown in FIG3B. For example, steps S3301 and S3302 are executed after steps S3201 and S3202.

[0379] In some embodiments, after the first network element stores and updates the terminal's data capability information, the updated data capability information can be deleted. After executing the embodiments shown in FIG3A and FIG3B, the embodiment shown in FIG3C can be executed. For example, after executing steps S3101, S3102, S3201, and S3202, steps S3301 and S3302 are executed.

[0380] It should be noted that the embodiments disclosed herein do not limit the number of times or the time for deleting data capability information. For example, the first network element may delete all data capability information of the terminal at once, or it may delete part of the data capability information of the terminal at once. It should be understood that the embodiment shown in Figure 3C may be executed multiple times at any time after executing the embodiment shown in Figure 3A and / or the embodiment shown in Figure 3B.

[0381] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

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

[0383] Step S3401: Receive at least one of the following: first request, second request, and third request.

[0384] In some embodiments, the first network element may receive a first request and, after storing the terminal's data capability information according to the first request, receive a second request.

[0385] In some embodiments, the first network element may receive a first request and, after storing the terminal's data capability information according to the first request, receive a third request.

[0386] In some embodiments, the first network element may receive a second request, update the terminal's data capability information according to the second request, and then receive a third request.

[0387] It should be noted that the above receiving order is an illustrative example, and the present disclosure does not limit the order and number of the first network element receiving the first request, the second request, and the third request.

[0388] In some embodiments, the data capability information includes at least one of the following:

[0389] The device functions of the terminal;

[0390] The data types that the terminal can provide;

[0391] The terminal can provide the following data formats;

[0392] User consent information, which indicates whether the user needs to authorize the purpose of using the data provided by the terminal;

[0393] Data transmission capability, which includes user plane transmission and / or control plane transmission.

[0394] In some embodiments, the method further includes at least one of the following:

[0395] According to the first request, the data capability information of the terminal is stored, wherein the first request includes the user permanent identifier SUPI of the terminal and the data capability information of the terminal;

[0396] According to the second request, update the stored data capability information of the terminal, wherein the second request includes the terminal's SUPI and the data capability information that needs to be updated;

[0397] According to the third request, the stored data capability information of the terminal is deleted. The third request includes the terminal's SUPI, or the terminal's SUPI and the data capability information to be deleted.

[0398] In some embodiments, the storage of the terminal's data capability information includes:

[0399] Determine the type of data capability information of the terminal;

[0400] Based on the type of data capability information of the terminal, the data capability information of the terminal is stored in the corresponding data capability table; wherein, different types of data capability information correspond to different data capability tables.

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

[0402] Send at least one of the following to the second network element: a second response message, a third response message, and a fourth response message, wherein the second response message includes the storage result of the data capability information, the third response message includes the update result of the data capability information, and the fourth response message includes the deletion result of the data capability information.

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

[0404] The system receives a fourth request sent by the second network element, the fourth request being used to obtain the SUPI of the terminal, the fourth request including the terminal identifier of the terminal;

[0405] Send a first response message to the second network element, the first response message including the SUPI of the terminal.

[0406] In some embodiments, the terminal identifier includes at least one of the following: General Public Subscriber Identifier (GPSI), International Mobile Subscriber Identifier (IMSI), Network Access Identifier (NAI), and Subtitling Identifier (SUCI).

[0407] In some embodiments, the data capability information stored in the first network element is used by the third network element to select the terminal for data collection.

[0408] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0409] In some embodiments of this disclosure, it is proposed to extend the UDM / UDR to manage UE data capability information (including data type, data format, user consent instructions for data collection, etc.) so that the DCF (Data Collection Function) can discover and select appropriate data sources (e.g., UEs with the required data capabilities). It is also proposed to enhance the extended AF provisioning service to provide UE data capability information to the UDR / UDM.

[0410] Figure 4A is a schematic diagram of a receipt collection service framework according to an embodiment of the present disclosure. As shown in Figure 4A, a new data collection function is defined for collecting and managing different types of data from different data source entities (e.g., UE, NWDAF, Location Management Function (LMF), UDM, AF, Analytical Data Repository Function (ADRF), etc.). In Figure 4A, SMF stands for Session Management Function.

[0411] In some embodiments, the DCF can support the collection and transmission of data via control plane and user plane connections, and also supports the transmission of collected data to data consumers (e.g., third parties, NFs, UEs) via control plane / user plane connections.

[0412] In some embodiments, when a data collection service request is received from a data collection service consumer (e.g., AF, NF, etc.), the DCF supports the discovery and selection of data source entities (e.g., UE, NWDAF, LMF, UDM) based on the data collection service request and the data capabilities registered in the UDM / UDR (on the UE / AF side).

[0413] In some embodiments, DCF also supports processing of the collected data, such as coordinating different data collection service consumers requesting the same data, thus avoiding wasting resources on transmitting the same data repeatedly, and also supports data format conversion, data normalization, domain-specific anonymization of data, data aggregation, etc.

[0414] In some embodiments, DCF supports a user consent mechanism to ensure data privacy. This mechanism can be at a more granular level, such as user consent by data type or by consumer ID / name.

[0415] In some embodiments, UE data capabilities are used to indicate what types of data the UE / device can generate or provide, such as camera, video data, formats [3K, 4K]; sensor, sensor data, formats [].

[0416] In some embodiments, UE data capability information is defined to include the following parameters:

[0417] UE ID (e.g., SUPI, GPSI, device identifier, etc.);

[0418] Device capabilities, such as cameras and sensors;

[0419] Data types, such as video data, sensor data, and location data;

[0420] Data format, such as 3K, 4K;

[0421] User consent indicates whether user consent is required for the purpose of using each or all data.

[0422] Data transmission capabilities, including the user plane (UP) and / or control plane (CP);

[0423] IP / MAC address / port information.

[0424] In some embodiments, an example of UE data capability information stored in the UDR / UDM is as follows:

[0425] Method 1: Stored in the UE subscription data table:

[0426] Data capability information includes:

[0427] Camera, video data, data format [3K, 4K], user-agreed instructions, UP and CP transmission capabilities, preferred UP connection.

[0428] Sensors, sensed data, data format, user consent instructions, CP transmission capabilities.

[0429] Method 2: Store in a dedicated data capability table:

[0430] Table 1. Data perception capabilities;

[0431] Table 2 Video Data Capabilities;

[0432] Table 3 Location data capabilities;

[0433] UE-1, Location Capabilities, Location Data, User Consent for AI Positioning Model Training / AI Model Performance Monitoring.

[0434] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0435] Figure 4B is an interactive schematic diagram illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 4B, the present disclosure relates to a communication method, which includes:

[0436] Step S4200: The UE registers its data capabilities with the AF / AS through the application layer.

[0437] Step S4201: AF / AS sends a UE_dataCapa_provisioning_create request to NEF.

[0438] In some embodiments, the UE_dataCapa_provisioning_create request includes the UE ID (i.e., GPSI) and UE data capability information.

[0439] Step S4202: NEF obtains the UE's SUPI by providing a GPSI request to UDM.

[0440] Step S4203: NEF sends a UE_dataCapa_provisioning_create request to UDM / UDR.

[0441] In some embodiments, the UE_dataCapa_provisioning_create request is used to create UE data capability information in the UE's subscription / profile, including SUPI and UE data capability information.

[0442] Step S4204: UDM / UDR stores UE data capability information.

[0443] Optionally, UDM / UDR can classify UE data capabilities into different types, for example, storing UE location data capabilities in a location entity table.

[0444] Step S4205: UDR / UDM sends a UE_dataCapa_provisioning_create response to NEF.

[0445] In some embodiments, the UE_dataCapa_provisioning_create response includes the storage result.

[0446] Step S4206: NEF sends the stored results to AF / AS.

[0447] Step S4207: When the DCF determines to start the data collection service based on the data collection service request, the DCF discovers and selects an appropriate UE with the required data capabilities.

[0448] For example, DCF determines which area to collect sensing data by selecting UEs with sensing data capabilities in a specific area.

[0449] In some embodiments, the UE data capability update is provided by AF. The difference between the UE data capability update steps and the steps S4200 to S4207 described above is that UE_dataCapa_provisioning_create in steps S4201, S4203, and S4205 is replaced with UE_dataCapa_provisioning_update request, which will not be described in detail here.

[0450] In some embodiments, the UE data capability is removed through AF provisioning service. The difference between the step of removing the UE data capability and the steps S4200 to S4207 described above is that UE_dataCapa_provisioning_create in steps S4201, S4203, and S4205 is replaced with UE_dataCapa_provisioning_remove request, which will not be described in detail here.

[0451] 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.

[0452] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0453] This disclosure also proposes an apparatus (also referred to as a communication device, etc.) for implementing any of the above methods. For example, an apparatus is proposed that includes units or modules for implementing the steps performed by the first network element in any of the above methods. Furthermore, another apparatus is proposed that includes units or modules for implementing the steps performed by the second network element in any of the above methods. Still another apparatus is proposed that includes units or modules for implementing the steps performed by the fourth network element in any of the above methods.

[0454] 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). 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). Taking a field-programmable gate array (FPGA) as an example, it 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.

[0455] 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. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a Neural Network Processing Unit (NPU), a Tensor Processing Unit (TPU), or a Deep Learning Processing Unit (DPU).

[0456] Figure 5A is a schematic diagram of the structure of the first network element proposed in an embodiment of this disclosure. The first network element 5100 is used to perform any of the above methods. In some embodiments, as shown in Figure 5A, the first network element 5100 may include at least one of: a transceiver module 5101, a processing module 5102, etc. In some embodiments, the transceiver module is used to receive at least one of the following sent by the second network element: a first request, a second request, and a third request; the first request is used to request storage of the terminal's data capability information, the second request is used to request updating the terminal's data capability information, and the third request is used to request deletion of the terminal's data capability information, wherein the data capability information is used to indicate information related to the data that the terminal can provide. Optionally, the transceiver module is used to execute at least one of the communication steps (e.g., steps S2102, S2103, S2104, S2106, S2202, S2203, S2204, S2206, S2302, S2303, S2304, S2306, S3101, S3201, S3301, S3401, but not limited thereto) performed by the first network element 5100 in any of the above methods, which will not be elaborated here. Optionally, the processing module is used to execute at least one of the other steps (e.g., steps S2105, S2205, S2305, S3102, S3202, S3302, but not limited thereto) performed by the first network element 5100 in any of the above methods, which will not be elaborated here.

[0457] Figure 5B is a schematic diagram of the structure of the second network element proposed in an embodiment of this disclosure. The second network element 5200 is used to perform any of the above methods. In some embodiments, as shown in Figure 5B, the second network element 5200 may include at least one of: a transceiver module 5201, a processing module 5202, etc. In some embodiments, the transceiver module is used to send at least one of the following to the first network element: a first request, a second request, and a third request; the first request is used to request the first network element to store the data capability information of the terminal, the second request is used to request the first network element to update the data capability information of the terminal, and the third request is used to request the first network element to delete the data capability information of the terminal, wherein the data capability information is used to indicate information related to the data that the terminal can provide. Optionally, the transceiver module is used to perform at least one of the communication steps (e.g., steps S2101, S2102, S2103, S2104, S2106, S2107, S2201, S2202, S2203, S2204, S2206, S2207, S2301, S2302, S2303, S2304, S2306, S2307, but not limited thereto) performed by the second network element 5200 in any of the above methods, which will not be elaborated here. Optionally, the processing module is used to perform at least one of the other steps performed by the second network element 5200 in any of the above methods, which will not be elaborated here.

[0458] Figure 5C is a schematic diagram of the structure of the fourth network element proposed in an embodiment of this disclosure. The fourth network element 5300 is used to perform any of the above methods. In some embodiments, as shown in Figure 5C, the fourth network element 5300 may include at least one of: a transceiver module 5301, a processing module 5302, etc. In some embodiments, the transceiver module is used to send at least one of the following to the second network element: a fifth request, a sixth request, and a seventh request; wherein, the fifth request is used to instruct the second network element to send a first request to the first network element, the first request being used to request the first network element to store the terminal's data capability information; the sixth request is used to instruct the second network element to send a second request to the first network element, the second request being used to request the first network element to update the terminal's data capability information; the seventh request is used to instruct the second network element to send a third request to the first network element, the third request being used to request the first network element to delete the terminal's data capability information, the data capability information being used to indicate information related to the data that the terminal can provide. Optionally, the transceiver module is used to perform at least one of the communication steps (e.g., steps S2101, S2107, S2201, S2207, S2301, S2307, but not limited thereto) performed by the fourth network element 5300 in any of the above methods, which will not be elaborated here. Optionally, the processing module is used to perform at least one of the other steps performed by the fourth network element 5300 in any of the above methods, which will not be elaborated here.

[0459] 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.

[0460] 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.

[0461] In some embodiments, the processing module can be replaced by the processor, and the transceiver module can be replaced by the transceiver.

[0462] 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 that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing 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.

[0463] As shown in Figure 6A, the communication device 6100 is used to execute any of the above methods. In some embodiments, the communication device 6100 includes one or more processors 6101. The processor 6101 may be a general-purpose processor or a special-purpose processor, such as a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 6100 is used to execute any of the above methods. Optionally, one or more processors 6101 are used to invoke instructions to cause the communication device 6100 to execute any of the above methods.

[0464] In some embodiments, the communication device 6100 further includes one or more transceivers 6102. When the communication device 6100 includes one or more transceivers 6102, the transceivers 6102 perform communication steps such as sending and / or receiving in the above method (e.g., steps S2101, S2102, S2103, S2104, S2106, S2107, S2201, S2202, S2203, S2204, S2206, S2207, S2301, ...). At least one of steps S2302, S2303, S2304, S2306, S2307, S3101, S3201, S3301, and S3401 (but not limited thereto) is performed, and the processor 6101 executes at least one of other steps (e.g., steps S2105, S2205, S2305, S3102, S3202, and S3302, but not limited thereto). In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver device, transceiver circuit, interface circuit, and interface can be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit can be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit can be used interchangeably.

[0465] In some embodiments, the communication device 6100 further includes one or more memories 6103 for storing data and / or instructions. Optionally, one or more processors 6101 are used to invoke instructions stored in the memory 6103 to cause the communication device 6100 to perform any of the above methods. Optionally, all or part of the memory 6103 may also be located outside the communication device 6100. In an optional embodiment, the communication device 6100 may include one or more interface circuits 6104. Optionally, the interface circuit 6104 is connected to the memory 6103 and can be used to receive data and / or instructions from the memory 6103 or other devices, and can be used to send data and / or instructions to the memory 6103 or other devices. For example, the interface circuit 6104 can read data and / or instructions stored in the memory 6103 and send the data and / or instructions to the processor 6101.

[0466] The communication device 6100 described in the above embodiments may be a network device or a terminal, 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 a 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, programs and / or instructions; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0467] 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.

[0468] Chip 6200 includes one or more processors 6201. Chip 6200 is used to perform any of the methods described above.

[0469] In some embodiments, chip 6200 further includes one or more interface circuits 6202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 6200 further includes one or more memories 6203 for storing data and / or instructions. Optionally, all or part of the memories 6203 may be located outside of chip 6200. Optionally, interface circuit 6202 is connected to memory 6203, and interface circuit 6202 can be used to receive data and / or instructions from memory 6203 or other devices, and interface circuit 6202 can be used to send data and / or instructions to memory 6203 or other devices. For example, interface circuit 6202 can read data and / or instructions stored in memory 6203 and send the data and / or instructions to processor 6201.

[0470] In some embodiments, the interface circuit 6202 performs at least one of the communication steps such as sending and / or receiving in the above-described method (e.g., steps S2101, S2102, S2103, S2104, S2106, S2107, S2201, S2202, S2203, S2204, S2206, S2207, S2301, S2302, S2303, S2304, S2306, S2307, S3101, S3201, S3301, S3401, but not limited thereto). The interface circuit 6202 performing the communication steps such as sending and / or receiving in the above-described method refers, for example, to the interface circuit 6202 performing data and / or instruction interaction between the processor 6201, the chip 6200, the memory 6203, or the transceiver device. In some embodiments, the processor 6201 performs at least one of other steps (e.g., steps S2105, S2205, S2305, S3102, S3202, S3302, but not limited thereto).

[0471] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0472] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device, cause the communication device 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.

[0473] This disclosure also proposes a program product, including a program and / or instructions, which, when executed by a communication device, cause the communication device to perform any of the above methods. Optionally, the program product is a computer program product. Optionally, the program product is stored on the storage medium.

[0474] 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 by comprising: The method, executed by the first network element, includes: The system receives at least one of the following from a second network element: a first request, a second request, and a third request; the first request is for requesting the storage of the terminal's data capability information, the second request is for requesting the updating of the terminal's data capability information, and the third request is for requesting the deletion of the terminal's data capability information, wherein the data capability information is used to indicate information related to the data that the terminal can provide.

2. The method of claim 1, wherein, The data capability information includes at least one of the following: The device functions of the terminal; The data types that the terminal can provide; The terminal can provide the following data formats; User consent information, which indicates whether the user needs to authorize the purpose of using the data provided by the terminal; Data transmission capability, which includes user plane transmission and / or control plane transmission.

3. The method according to claim 1 or 2, characterized in that, The method further includes at least one of the following: According to the first request, the data capability information of the terminal is stored, wherein the first request includes the user permanent identifier SUPI of the terminal and the data capability information of the terminal; According to the second request, update the stored data capability information of the terminal, wherein the second request includes the terminal's SUPI and the data capability information that needs to be updated; According to the third request, the stored data capability information of the terminal is deleted. The third request includes the terminal's SUPI, or the terminal's SUPI and the data capability information to be deleted.

4. The method of claim 3, wherein, The data storage capability information of the terminal includes: Determine the type of data capability information of the terminal; Based on the type of data capability information of the terminal, the data capability information of the terminal is stored in the corresponding data capability table; wherein, different types of data capability information correspond to different data capability tables.

5. The method according to claim 3 or 4, characterized in that, The method further includes: The system receives a fourth request sent by the second network element, the fourth request being used to obtain the SUPI of the terminal, the fourth request including the terminal identifier of the terminal; Send a first response message to the second network element, the first response message including the SUPI of the terminal.

6. The method of claim 5, wherein, The terminal identifier includes at least one of the following: General Public Subscriber Identifier (GPSI), International Mobile Subscriber Identifier (IMSI), Network Access Identifier (NAI), and Subtitling Identifier (SUCI).

7. The method according to any one of claims 1 to 6, characterized in that, The method further includes: Send at least one of the following to the second network element: a second response message, a third response message, and a fourth response message, wherein the second response message includes the storage result of the data capability information, the third response message includes the update result of the data capability information, and the fourth response message includes the deletion result of the data capability information.

8. The method according to any one of claims 1 to 7, characterized in that, The data capability information stored in the first network element is used by the third network element to select the terminal for data collection.

9. A communication method characterized by comprising: The method, executed by the second network element, includes: Send at least one of the following to the first network element: a first request, a second request, and a third request; the first request is used to request the first network element to store the terminal's data capability information, the second request is used to request the first network element to update the terminal's data capability information, and the third request is used to request the first network element to delete the terminal's data capability information, wherein the data capability information is used to indicate information related to the data that the terminal can provide.

10. The method of claim 9, wherein, The method further includes: The network receives at least one of the following from the fourth network element: a fifth request, a sixth request, and a seventh request; the fifth request is used to instruct the second network element to send the first request to the first network element, the sixth request is used to instruct the second network element to send the second request to the first network element, and the seventh request is used to instruct the second network element to send the third request to the first network element.

11. The method according to claim 10, characterized in that, The fifth request includes the terminal identifier of the terminal and the data capability information of the terminal. The terminal identifier is used by the second network element to obtain the user permanent identifier (SUPI) of the terminal. The sixth request includes the terminal identifier of the terminal and the data capability information that needs to be updated; The seventh request includes the terminal identifier of the terminal, or the terminal identifier of the terminal and the data capability information to be deleted.

12. The method according to any one of claims 9-11, characterized in that, The first request includes the terminal's SUPI and the terminal's data capability information; The second request includes the terminal's SUPI and the data capability information that needs to be updated; The third request includes the terminal's SUPI, or the terminal's SUPI and the data capability information to be deleted.

13. The method according to claims 9-12, characterized by, The data capability information includes at least one of the following: The device functions of the terminal; The data types that the terminal can provide; The terminal can provide the following data formats; User consent information, which indicates whether the user needs to authorize the purpose of using the data provided by the terminal; Data transmission capability, which includes user plane transmission and / or control plane transmission.

14. The method according to claim 12 or 13, characterized in that, The method further includes: A fourth request is sent to the first network element, the fourth request being used to obtain the SUPI of the terminal, the fourth request including the terminal identifier of the terminal; The terminal receives a first response message sent by the first network element, the first response message including the SUPI of the terminal.

15. The method according to claim 11 or 14, characterized in that, The terminal identifier includes at least one of the following: General Public Subscriber Identifier (GPSI), International Mobile Subscriber Identifier (IMSI), Network Access Identifier (NAI), and Subtitling Identifier (SUCI).

16. The method according to any one of claims 9-15, characterized in that, The method further includes: The system receives at least one of the following from the first network element: a second response message, a third response message, and a fourth response message; the second response message includes the storage result of the data capability information, the third response message includes the update result of the data capability information, and the fourth response message includes the deletion result of the data capability information.

17. The method of claim 16, wherein, The method further includes: Send at least one of the following to the fourth network element: a fifth response message, a sixth response message, and a seventh response message; the fifth response message includes the storage result of the data capability information, the sixth response message includes the update result of the data capability information, and the seventh response message includes the deletion result of the data capability information.

18. A method of communication, comprising: The method, executed by the fourth network element, includes: Send at least one of the following to the second network element: a fifth request, a sixth request, and a seventh request; wherein, the fifth request is used to instruct the second network element to send a first request to the first network element, the first request being used to request the first network element to store the terminal's data capability information; the sixth request is used to instruct the second network element to send a second request to the first network element, the second request being used to request the first network element to update the terminal's data capability information; the seventh request is used to instruct the second network element to send a third request to the first network element, the third request being used to request the first network element to delete the terminal's data capability information, the data capability information being used to indicate information related to the data that the terminal can provide.

19. The method according to claim 18, characterized in that, The fifth request includes the terminal identifier of the terminal and the data capability information of the terminal. The terminal identifier is used by the second network element to obtain the user permanent identifier (SUPI) of the terminal. The sixth request includes the terminal identifier of the terminal and the data capability information that needs to be updated; The seventh request includes the terminal identifier of the terminal, or the terminal identifier of the terminal and the data capability information to be deleted.

20. The method of claim 19, wherein, The terminal identifier includes at least one of the following: General Public Subscriber Identifier (GPSI), International Mobile Subscriber Identifier (IMSI), Network Access Identifier (NAI), and Subtitling Identifier (SUCI).

21. The method according to any one of claims 18-20, characterized by, The data capability information includes at least one of the following: The device functions of the terminal; The data types that the terminal can provide; The terminal can provide the following data formats; User consent information, which indicates whether the user needs to authorize the purpose of using the data provided by the terminal; Data transmission capability, which includes user plane transmission and / or control plane transmission.

22. The method according to any one of claims 18-21, characterized by, The method further includes: The network receives at least one of the following from the second network element: a fifth response message, a sixth response message, and a seventh response message, wherein the fifth response message includes the storage result of the data capability information, the sixth response message includes the update result of the data capability information, and the seventh response message includes the deletion result of the data capability information.

23. A communication method for a communication system, the communication system comprising a first network element, a second network element, the method comprising: The method includes: The second network element sends at least one of the following to the first network element: a first request, a second request, and a third request. The first request is used to request the storage of the terminal's data capability information. The second request is used to request the updating of the terminal's data capability information. The third request is used to request the deletion of the terminal's data capability information. The data capability information is used to indicate information related to the data that the terminal can provide.

24. A communications device, characterized by The communication device is configured to perform the communication method of any one of claims 1-8, 9-17, 18-22.

25. A communication system, characterized by The communication device is configured to perform the communication method of any one of claims 1-8, 9-17, 18-22.

26. A storage medium, the storage medium storing instructions, wherein, The program, instructions, when executed by the communication device, cause the communication device to perform the communication method of any one of claims 1-8, 9-17, 18-22.

27. A program product comprising at least one of a program, instructions, characterized in that The program, instructions, when executed by the communication device, cause the communication device to perform the communication method of any one of claims 1-8, 9-17, 18-22.

Images