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 receiving a data collection request, and acquiring a candidate device list on the basis of the data collection request, wherein the data collection request comprises at least one of the following: a device identifier, a data type, a data format, and a data collection area; and collecting data from a first device, wherein the first device includes at least one device in the candidate device list. That is, the first network element dynamically screens the candidate device list on the basis of the data collection request to collect data from devices in the candidate device list, thereby improving the efficiency and accuracy of data collection, while also avoiding invalid participation of irrelevant devices and optimizing the utilization of network resources.

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] During the data collection process, due to the different data capabilities of different devices, the types and formats of the collected data also differ, resulting in redundant data that does not meet the requirements, thus making the accuracy of data collection relatively low.

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

[0005] 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:

[0006] Receive a data collection request, and obtain a candidate device list based on the data collection request. The data collection request includes at least one of the following: device identifier, data type, data format, and data collection area.

[0007] Data is collected from a first device, which includes at least one device from the candidate device list.

[0008] 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:

[0009] The system receives a first request sent by a first network element. The first request is used to obtain a list of candidate devices. The first request includes at least one of the following: device identifier, data type, data format, and data collection area.

[0010] Based on the first request and the data capability information of at least one second device stored, the candidate device list is determined from the at least one second device;

[0011] A first response message is sent to the first network element. The first response message includes the candidate device list. The first response message is used by the first network element to collect data from a first device. The first device includes at least one device in the candidate device list.

[0012] 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:

[0013] Receive a third request sent by a third network element, wherein the third request includes data capability information of the second device;

[0014] A second request is sent to a fifth network element according to the third request; the fifth network element includes a first network element and / or a second network element, the second request includes data capability information of the second device, the second request is used to request the fifth network element to store the data capability information of the second device, the data capability information stored by the fifth network element is used to determine a candidate device list, and the candidate device list is used by the first network element to collect data.

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

[0016] A third request is sent to a fourth network element; the third request includes data capability information of the second device, and the third request is used to instruct the fourth network element to send a second request to a fifth network element, the fifth network element including a first network element and / or a second network element, the second request being used to request the fifth network element to store the data capability information of the second device, the data capability information stored by the fifth network element being used to determine a candidate device list, and the candidate device list being used by the first network element to collect data.

[0017] According to a fifth aspect of the embodiments of this disclosure, a communication method is provided, performed by a first device, the method comprising:

[0018] The system receives a first connection establishment request from a first network element and sends a first connection establishment response message to the first network element. The first connection establishment request is used to request the establishment of a connection with the first device; different first devices correspond to different first connection establishment requests. The first connection establishment request includes at least one of the following: the device identifier of the first device, the address of the first network element, and information about the data to be collected. The first connection establishment response message includes at least one of the following: the connection establishment result, and the address of the first device. Alternatively,

[0019] The system receives a fourth connection establishment request sent by a third network element and sends a fourth connection establishment response message to the third network element. The fourth connection establishment request is used to request the establishment of a connection with the first device. Different first devices correspond to different fourth connection establishment requests. The fourth connection establishment response message includes at least one of the following: connection establishment result and the address of the first device.

[0020] According to a sixth aspect of the embodiments of this disclosure, a communication method is provided, executed by a terminal, the method comprising:

[0021] The system receives a third connection establishment request sent by a first network element. The third connection establishment request is used to request the establishment of a connection with the terminal. The third connection establishment request includes at least one of the following: the device identifier of the first device, the address of the first network element, and information about the data to be collected.

[0022] A third connection establishment response message is sent to the first network element, the third connection establishment response message including at least one of the following: connection establishment result, address of the first device.

[0023] According to a seventh aspect of the present disclosure, a communication device is provided that can be used to perform the methods described in optional implementations of the first, second, third, fourth, fifth, or sixth aspects.

[0024] According to an eighth aspect of the present disclosure, a communication system is provided, including a first network element, a second network element, a third network element, a fourth network element, a first device, and a terminal, 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, the fourth network element is configured to perform the method described in the optional implementation of the third aspect, the third network element is configured to perform the method described in the optional implementation of the fourth aspect, the first device is configured to perform the method described in the optional implementation of the fifth aspect, and the terminal is configured to perform the method described in the optional implementation of the sixth aspect.

[0025] According to a ninth 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, third, fourth, fifth, or sixth aspect.

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

[0027] The technical solution provided in this disclosure can produce the following beneficial effects: A first network element receives a data collection request, obtains a candidate device list based on the data collection request, the data collection request including at least one of the following: device identifier, data type, data format, and data collection area; and collects data from a first device, the first device including at least one device in the candidate device list. In other words, the first network element dynamically filters the candidate device list based on the data collection request and collects data from the devices in the candidate device list, improving the efficiency and accuracy of data collection, while also avoiding the invalid participation of irrelevant devices and optimizing network resource utilization.

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

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

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

[0031] Figure 1B is a schematic diagram of a data collection and reporting architecture according to an embodiment of the present disclosure.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0047] Figure 6C is a schematic diagram of the structure of the third network element proposed in an embodiment of this disclosure.

[0048] Figure 6D is a schematic diagram of the structure of the fourth network element proposed in an embodiment of this disclosure.

[0049] Figure 6E is a schematic diagram of the structure of the first device proposed in an embodiment of this disclosure.

[0050] Figure 6F is a schematic diagram of the structure of the terminal proposed in the embodiment of this disclosure.

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

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

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

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

[0055] Receive a data collection request, and obtain a candidate device list based on the data collection request. The data collection request includes at least one of the following: device identifier, data type, data format, and data collection area.

[0056] Data is collected from a first device, which includes at least one device from the candidate device list.

[0057] In the above embodiments, the first network element dynamically filters the candidate device list based on the data collection request and collects data from the devices in the candidate device list, which improves the efficiency and accuracy of data collection, while also avoiding the invalid participation of irrelevant devices and optimizing the utilization of network resources.

[0058] In conjunction with some embodiments of the first aspect, in some embodiments, obtaining the candidate device list according to the data collection request includes:

[0059] Send a first request to the second network element; the first request is used to obtain the candidate device list, and the first request includes at least one of the following: device identifier, data type, data format, and data collection area;

[0060] The system receives a first response message sent by the second network element, the first response message including the candidate device list.

[0061] In the above embodiments, the first network element obtains a list of matching candidate devices by sending a second request to the second network element, thereby achieving efficient and accurate device screening, ensuring that data is collected only for devices that meet the requirements, and significantly reducing network signaling overhead and resource consumption.

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

[0063] Send a first connection establishment request to the first device; wherein, the first connection establishment request is used to request to establish a connection with the first device, different first devices correspond to different first connection establishment requests, and the first connection establishment request includes at least one of the following: the device identifier of the first device, the address of the first network element, and information about the data to be collected;

[0064] The device receives a first connection establishment response message sent by the first device, the first connection establishment response message including at least one of the following: connection establishment result, address of the first device.

[0065] In the above embodiments, the first network element dynamically establishes a connection with the first device through personalized parameters (such as the device identifier of the first device, the address of the first network element, and the information of the data to be collected), thereby improving the targeting and reliability of data collection, reducing redundant communication, and optimizing resource allocation.

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

[0067] Send a second connection establishment request to the third network element. The second connection establishment request is used to request to establish a connection with the third network element. The second connection establishment request includes at least one of the following: the device identifier of the first device, the address of the first network element, and information about the data to be collected.

[0068] The system receives a second connection establishment response message sent by the third network element. The second connection establishment response message includes at least one of the following: connection establishment result and the address of the first device.

[0069] In the above embodiments, the first network element establishes a cross-network element data channel by sending a second connection establishment request to the third network element and receiving a response, thereby ensuring the reliability and integrity of the end-to-end data collection link.

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

[0071] A third connection establishment request is sent to the terminal. The third connection establishment request is used to request to establish a connection with the terminal. The third connection establishment request includes at least one of the following: the device identifier of the first device, the address of the first network element, and information about the data to be collected.

[0072] The terminal sends a third connection establishment response message, which includes at least one of the following: connection establishment result, and the address of the first device.

[0073] In the above embodiments, by sending a connection establishment request to the terminal and receiving a response, the dynamic establishment of device connections and precise matching of data collection are achieved, reducing invalid communication and improving data transmission efficiency.

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

[0075] The first network element receives a second request sent by a fourth network element. The second request includes data capability information of the second device. The second request is used to request the first network element to store the data capability information.

[0076] Store the data capability information of the second device.

[0077] In the above embodiments, by receiving and storing the second device data capability information forwarded by the fourth network element, centralized management and dynamic updating of device data capability information are achieved, providing data support for accurate matching of data collection and resource allocation, while improving the decision-making efficiency of the network side.

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

[0079] The device identifier of the second device;

[0080] The device functions of the second device;

[0081] The equipment type of the second device;

[0082] The types of data that the second device can collect;

[0083] The second device can collect data in the following formats;

[0084] The terminal identifier associated with the second device;

[0085] User consent information, which is used to determine whether the user needs to authorize the purpose of using the data collected by the second device;

[0086] The address of the second device.

[0087] In the above embodiments, by storing second device data capability information that includes multiple dimensions such as device identifier, device function, data type, and user authorization, precise management of device capabilities is achieved, thereby improving the accuracy and efficiency of data collection tasks.

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

[0089] A second response message is sent to the fourth network element, the second response message including the storage result of the data capability information of the second device.

[0090] In the above embodiments, by feeding back the storage results of data capability information to the fourth network element, the reliability and consistency of data capability information updates are improved.

[0091] In conjunction with some embodiments of the first aspect, in some embodiments, the collection of data from the first device includes:

[0092] Receive data sent by the first device; or,

[0093] Receive data collected from the first device by a third network element or terminal.

[0094] In the above embodiments, the first network can directly receive data sent by the first device, or forward data collected from the first device through a third network element or terminal, which improves the efficiency of data collection and simplifies the management complexity of the first network element in data collection, while enhancing the flexibility and coverage of data collection.

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

[0096] The system receives a first request sent by a first network element. The first request is used to obtain a list of candidate devices. The first request includes at least one of the following: device identifier, data type, data format, and data collection area.

[0097] Based on the first request and the data capability information of at least one second device stored, the candidate device list is determined from the at least one second device;

[0098] A first response message is sent to the first network element. The first response message includes the candidate device list. The first response message is used by the first network element to collect data from a first device. The first device includes at least one device in the candidate device list.

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

[0100] The system receives a second request sent by a fourth network element. The second request includes data capability information of the second device. The second request is used to request the fourth network element to store the data capability information.

[0101] Store the data capability information of the second device.

[0102] In the above embodiments, by receiving and storing the second device data capability information forwarded by the fourth network element, centralized management and dynamic updating of device data capability information are achieved, providing data support for accurate matching of data collection and resource allocation, while improving the decision-making efficiency of the network side.

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

[0104] The device identifier of the second device;

[0105] The device functions of the second device;

[0106] The equipment type of the second device;

[0107] The types of data that the second device can collect;

[0108] The second device can collect data in the following formats;

[0109] The terminal identifier associated with the second device;

[0110] User consent information, which is used to determine whether the user needs to authorize the purpose of using the data collected by the second device;

[0111] The address of the second device.

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

[0113] A second response message is sent to the fourth network element, the second response message including the storage result of the data capability information of the second device.

[0114] In the above embodiments, by feeding back the storage results of data capability information to the fourth network element, the reliability and consistency of data capability information updates are improved.

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

[0116] Receive a third request sent by a third network element, wherein the third request includes data capability information of the second device;

[0117] A second request is sent to a fifth network element according to the third request; the fifth network element includes a first network element and / or a second network element, the second request includes data capability information of the second device, the second request is used to request the fifth network element to store the data capability information of the second device, the data capability information stored by the fifth network element is used to determine a candidate device list, and the candidate device list is used by the first network element to collect data.

[0118] In the above embodiments, through the collaboration of the third network element and the fifth network element, dynamic storage and centralized management of the data capability information of the second device are realized, providing real-time and reliable data support for the accurate generation of the candidate device list, thereby optimizing the efficiency and accuracy of the first network element data collection.

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

[0120] The device identifier of the second device;

[0121] The device functions of the second device;

[0122] The equipment type of the second device;

[0123] The types of data that the second device can collect;

[0124] The second device can collect data in the following formats;

[0125] The terminal identifier associated with the second device;

[0126] User consent information, which is used to determine whether the user needs to authorize the purpose of using the data collected by the second device;

[0127] The address of the second device.

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

[0129] The system receives a second response message sent by the fifth network element, the second response message including the storage result of the data capability information of the second device.

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

[0131] A third response message is sent to the third network element according to the second response message, and the third response message includes the storage result of the data capability information of the second device.

[0132] In the above embodiments, by feeding back the storage results of the data capability information of the fifth network element to the third network element, the integrity and reliability of the data capability information update are ensured.

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

[0134] Determine whether the third request or the third network element is allowed to request the storage of the data capability information of the second device.

[0135] In the above embodiments, by verifying the third request or the third network element, the legitimacy of the data capability information storage request is ensured, unauthorized access or tampering is prevented, thereby ensuring the security of network data.

[0136] Fourthly, embodiments of this disclosure propose a communication method executed by a third network element, the method comprising:

[0137] A third request is sent to a fourth network element; the third request includes data capability information of the second device, and the third request is used to instruct the fourth network element to send a second request to a fifth network element, the fifth network element including a first network element and / or a second network element, the second request being used to request the fifth network element to store the data capability information of the second device, the data capability information stored by the fifth network element being used to determine a candidate device list, and the candidate device list being used by the first network element to collect data.

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

[0139] The device identifier of the second device;

[0140] The device functions of the second device;

[0141] The equipment type of the second device;

[0142] The types of data that the second device can collect;

[0143] The second device can collect data in the following formats;

[0144] The terminal identifier associated with the second device;

[0145] User consent information, which is used to determine whether the user needs to authorize the purpose of using the data collected by the second device;

[0146] The address of the second device.

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

[0148] The third response message sent by the fourth network element is received, and the third response message includes the storage result of the data capability information of the second device.

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

[0150] The system receives a second connection establishment request sent by the first network element. The second connection establishment request is used to request the establishment of a connection with the third network element. The second connection establishment request includes at least one of the following: the device identifier of the first device, the address of the first network element, and information about the data to be collected.

[0151] Establish a connection with the first network element according to the second connection request.

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

[0153] A fourth connection establishment request is sent to the first device according to the second connection establishment request. The fourth connection establishment request is used to request to establish a connection with the first device. Different first devices correspond to different fourth connection establishment requests.

[0154] The system receives a fourth connection establishment response message sent by the first device, the fourth connection establishment response message including at least one of the following: connection establishment result, address of the first device;

[0155] According to the fourth connection establishment response message, a second connection establishment response message is sent to the first network element. The second connection establishment response message includes at least one of the following: connection establishment result, address of the first device.

[0156] In the above embodiments, by establishing a connection between the third network element and the first device, indirect communication between the first network element and the first device is realized, thereby improving the flexibility of data transmission.

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

[0158] Receive data sent by the first device;

[0159] Send the data from the first device to the first network element.

[0160] Fifthly, embodiments of this disclosure provide a communication method executed by a first device, the method comprising:

[0161] The system receives a first connection establishment request from a first network element and sends a first connection establishment response message to the first network element. The first connection establishment request is used to request the establishment of a connection with the first device; different first devices correspond to different first connection establishment requests. The first connection establishment request includes at least one of the following: the device identifier of the first device, the address of the first network element, and information about the data to be collected. The first connection establishment response message includes at least one of the following: the connection establishment result, and the address of the first device. Alternatively,

[0162] The system receives a fourth connection establishment request sent by a third network element and sends a fourth connection establishment response message to the third network element. The fourth connection establishment request is used to request the establishment of a connection with the first device. Different first devices correspond to different fourth connection establishment requests. The fourth connection establishment response message includes at least one of the following: connection establishment result and the address of the first device.

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

[0164] The data from the first device is sent to the first network element or the third network element.

[0165] Sixthly, embodiments of this disclosure provide a communication method executed by a terminal, the method comprising:

[0166] The system receives a third connection establishment request sent by a first network element. The third connection establishment request is used to request the establishment of a connection with the terminal. The third connection establishment request includes at least one of the following: the device identifier of the first device, the address of the first network element, and information about the data to be collected.

[0167] A third connection establishment response message is sent to the first network element, the third connection establishment response message including at least one of the following: connection establishment result, address of the first device.

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

[0169] Collect data from the first device;

[0170] Send the data collected from the first device to the first network element.

[0171] In a seventh aspect, 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 an optional implementation of the first aspect.

[0172] Eighthly, 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 first network element may be used to execute an optional implementation of the second aspect.

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

[0174] In a tenth 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 perform an optional implementation of the third aspect.

[0175] In one aspect, embodiments of this disclosure provide a first device, which may include at least one of a transceiver module and a processing module; wherein the first device may be used to perform an optional implementation of the fifth aspect.

[0176] In a twelfth aspect, embodiments of this disclosure provide a terminal that may include at least one of a transceiver module and a processing module; wherein the terminal may be used to perform an optional implementation of the sixth aspect.

[0177] In a thirteenth aspect, 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.

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

[0179] In the fifteenth aspect, embodiments of this disclosure provide a third network element, which may include one or more processors; wherein the third network element may be used to perform an optional implementation of the fourth aspect.

[0180] In a sixteenth aspect, embodiments of this disclosure provide 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.

[0181] In a seventeenth aspect, embodiments of this disclosure provide a first device that may include one or more processors; wherein the first device may be used to perform an optional implementation of the fifth aspect.

[0182] In the eighteenth aspect, embodiments of this disclosure provide a terminal that may include one or more processors; wherein the terminal may be used to execute an optional implementation of the sixth aspect.

[0183] In a nineteenth aspect, embodiments of this disclosure provide a communication system that may include: a first network element, a second network element, a third network element, a fourth network element, a first device, and a terminal; 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, the third network element is configured to perform the method described in the optional implementation of the fourth aspect, the fourth network element is configured to perform the method described in the optional implementation of the third aspect, the first device is configured to perform the method described in the optional implementation of the fifth aspect, and the terminal is configured to perform the method described in the optional implementation of the sixth aspect.

[0184] In a twentieth 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 the optional implementations of the first, second, third, fourth, fifth, or sixth aspects.

[0185] In a twentieth 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 the optional implementations of the first, second, third, fourth, fifth, or sixth aspects.

[0186] In a twentieth aspect, embodiments of this disclosure provide a computer program that, when run on a computer, causes the computer to perform the methods described in the optional implementations of the first, second, third, fourth, fifth, or sixth aspects.

[0187] In a twentieth 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, third, fourth, fifth, or sixth aspects.

[0188] It is understood that the aforementioned first network element, second network element, third network element, fourth network element, first device, terminal, 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.

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

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

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

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

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

[0194] 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" and the like can be used interchangeably.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0211] 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, a network device 102, and a first device 103.

[0212] In some embodiments, terminal 101 includes, but is not limited to, 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.

[0213] In some embodiments, the first device 103 is not a 3GPP (Third Generation Partnership Project) device, meaning it is a non-3GPP device and does not support 3GPP. It should be understood that a non-3GPP device is a communication device that connects to the core network without using access technologies defined by the 3GPP standard. In some embodiments, the non-3GPP device may use other wireless or wired technologies for access and integrate with the 3GPP core network through a gateway.

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

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

[0216] In some embodiments, the access network device is a base station. Optionally, the base station may be, for example, a macro base station, a micro base station (also called a small station), a relay station, an access point, a 5 / 6G base station or a future base station, a satellite, a Transmitting and Receiving Point (TRP), a Transmitting Point (TP), a mobile switching center, or other equipment that performs base station functions in a communication system, etc., and this disclosure does not specifically limit this type of device. For ease of description, in all embodiments of this disclosure, the apparatus that provides wireless communication functions for terminal devices is collectively referred to as a network device or a base station.

[0217] In some embodiments, the access network device is a core network device. Optionally, the core network device can be a single device, including a first network element, a second network element, etc., or it can be multiple devices or a group of devices, each including all or part of the first network element, the second network element, etc. Network elements can be virtual or physical. The core network includes, for example, at least one of the Evolved Packet Core (EPC), 5G / 6G Core Network (5G CN / 6G CN), and Next Generation Core (NGC).

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

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

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

[0221] In some embodiments, the first network element 1021 is used to collect data, such as a data collection function (DCF), a network data analytics function (NWDAF), a location management function (LMF), a data collection coordination function (DCCF), a data connectivity application framework (DCAF), or a sensing function, etc. The name is not limited to these, and it can also be other network elements that implement similar functions.

[0222] In some embodiments, the second network element 1022 is used for data storage / management, such as a User Data Repository (UDR), User Data Management (UDM), Network Repository Function (NRF), or AMF. The name is not limited to these, and it may also be other network elements that implement similar functions.

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

[0224] In some embodiments, the fourth network element 1024 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.

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

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

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

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

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

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

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

[0232] 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 NWDAF, or outside a trusted domain, such as an event consumer function in an Application Service Provider.

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

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

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

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

[0237] In some embodiments, when a non-3GPP device connects to a UE, the UE can bind a non-3GPP device identifier to the non-3GPP device for services requiring differentiation of Quality of Service (QoS) between the non-3GPP devices. This binding enables the communication system to distinguish traffic generated by different non-3GPP devices connected through the same UE.

[0238] In some embodiments, how the UE identifies a non-3GPP device and binds the non-3GPP device identifier to the non-3GPP device is implementation-specific.

[0239] In some embodiments, at any given time, a non-3GPP device identifier can only be bound to one non-3GPP device.

[0240] In some embodiments, non-3GPP device identifier information is stored in the UDR and includes non-3GPP device identifier and QoS information.

[0241] In some embodiments, NF registration in NRF does not support the ability to store / manage data of non-3GPP devices, and UDM / UDR does not support the ability to store / manage data of non-3GPP devices.

[0242] 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 embodiments of the present disclosure relate to a communication method, which includes:

[0243] Step S2101: The third network element sends a third request to the fourth network element.

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

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

[0246] In some embodiments, the third request may include data capability information of the second device.

[0247] In some embodiments, the third request may also be referred to as a "device data capability registration request", etc.

[0248] In some embodiments, the second device is a non-3GPP device.

[0249] In some embodiments, the data capability information may include at least one of the following:

[0250] The equipment identification of the second device;

[0251] The equipment functions of the second device;

[0252] The equipment type of the second device;

[0253] The types of data that the second device can collect;

[0254] The second device can collect data in the following formats:

[0255] The terminal identifier associated with the second device;

[0256] User consent information, which is used to determine whether user authorization is required for the purpose of using the data collected by the second device;

[0257] The address of the second device.

[0258] In some embodiments, the device identifier may also be referred to as the device ID, such as the International Mobile Equipment Identity (IMEI) or device identifier, which is assigned by the network, UE, or service provider.

[0259] In some embodiments, the device function may be a function possessed by a second device, such as a camera or a sensor.

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

[0261] In some embodiments, the device type is a non-3GPP device.

[0262] 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 second device can provide may be determined according to the device functions of the second device. For example, if the device functions of the second device include a camera, the data type may be video data; if the device functions of the second device include a sensor, the data type may be sensing data.

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

[0264] In some embodiments, the terminal identifier associated with the second device may be the identifier of a terminal connected to the second device.

[0265] In some embodiments, the user consent information may indicate the purpose for which the user needs to authorize the use of the data collected by the second device, i.e., authorization from the second device is required when using the data collected by the second device; the user consent information may also indicate the purpose for which the user does not need to authorize the use of the data collected by the second device, i.e., authorization from the second device is not required when using the data collected by the second device.

[0266] In some embodiments, the consent information may be used to indicate whether the user needs to authorize the use of each type of data collected by the second device, or to indicate whether the user needs to authorize the use of all data collected by the second device.

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

[0268] In some embodiments, the address of the second device may be the Internet Protocol Address (IP) address or the Media Access Control Address (MAC) address of the second device.

[0269] Step S2102: The fourth network element sends a second request to the fifth network element based on the third request.

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

[0271] In some embodiments, the third request is used to instruct the fourth network element to send a second request to the fifth network element.

[0272] In some embodiments, the fifth network element includes the first network element and / or the second network element.

[0273] In some embodiments, the first network element may be, for example, a DCF, and the second network element may be, for example, an NRF, a UDR, or a UDM.

[0274] In some embodiments, the second request is used to request the fifth network element to store the data capability information of the second device.

[0275] In some embodiments, the second request includes data capability information of the second device. In some embodiments, after receiving the third request sent by the third network element, the fourth network element may send a second request to the first network element to request the first network element to store the data capability information of the second device; after receiving the third request sent by the third network element, the fourth network element may also send a second request to the second network element to request the second network element to store the data capability information of the second device.

[0276] In some embodiments, after receiving a third request from a third network element, the fourth network element can determine whether the third request or the third network element is allowed to request the storage of data capability information of the second device.

[0277] For example, the fourth network element can verify the third request. If the verification passes, it determines that the third request is allowed to request the storage of the second device's data capability information. This can intercept illegal requests and improve the security of the network element. As another example, the fourth network element can verify the permissions of the third network element. If the verification passes, it determines that the third network element is allowed to request the storage of the second device's data capability information. This can prevent unauthorized network elements (such as compromised or forged third network elements) from illegally storing or tampering with the second device's data capability information, thereby protecting data integrity.

[0278] In some embodiments, if the fourth network element determines that the third request and / or the third network element is permitted to request the storage of data capability information of the second device, it sends a second request to the first network element and / or the second network element.

[0279] In some embodiments, steps S2103 and S2104 can be omitted if the fourth network element does not send a second request to the first network element; steps S2105 and S2106 can be omitted if the fourth network element does not send a second request to the second network element.

[0280] In some embodiments, the fourth network element may send a second request to the first network element and / or the second network element according to the protocol agreement or dynamic instructions.

[0281] Step S2103: The first network element stores the data capability information of the second device.

[0282] In some embodiments, after receiving the second request sent by the fourth network element, the first network element may store the data capability information of the second device.

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

[0284] In some embodiments, the second response message includes the storage result of the data capability information of the second device.

[0285] In some embodiments, after the first network element stores the data capability information of the second device, it can send the second response message to the fourth network element to inform the fourth network element whether the data capability information of the second device has been stored.

[0286] Step S2105: The second network element stores the data capability information of the second device.

[0287] In some embodiments, after receiving a second request from a fourth network element, the second network element may store the data capability information of the second device.

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

[0289] In some embodiments, the second response message includes the storage result of the data capability information of the second device.

[0290] In some embodiments, after storing the data capability information of the second device, the second network element can send the second response message to the fourth network element to inform the fourth network element whether the data capability information of the second device has been stored.

[0291] Step S2107: The fourth network element sends a third response message to the third network element based on the second response message.

[0292] In some embodiments, after receiving the second response message sent by the first network element, the fourth network element may send a third response message to the third network element based on the second response message, informing the third network element whether the data capability information of the second device has been stored.

[0293] In some embodiments, after receiving the second response message sent by the second network element, the fourth network element may send a third response message to the third network element based on the second response message, informing the third network element whether the data capability information of the second device has been stored.

[0294] In some embodiments, after receiving the second response message sent by the first network element and the second response message sent by the second network element, the fourth network element may combine the two second response messages and send a third response message to the third network element, informing the third network element of the storage results of the data capability information of the second device by the first network element and the second network element.

[0295] In some embodiments, the data capability information of the second device may also be pre-configured in the first network element and / or the second network element, in which case some or all of the steps in steps S2101 to S2107 may be omitted.

[0296] Step S2108: The first network element receives a data collection request.

[0297] In some embodiments, the data collection request may be sent by an internal or external consumer.

[0298] Step S2109: The first network element sends a first request to the second network element.

[0299] In some embodiments, when a first network element determines that data needs to be collected from a first device based on a data collection request, it can obtain a candidate device list. This candidate device list is used by the first network element to select a suitable device for data collection. Optionally, the candidate device list is determined from at least one second device. It should be understood that the candidate device list includes at least one second device.

[0300] In some embodiments, the data collection request may include at least one of the following: device identifier, data type, data format, and area for data collection.

[0301] In some embodiments, the first network element may send a first request to the second network element to obtain the candidate device list.

[0302] In some embodiments, the first request may include at least one of the following: device identifier, data type, data format, and area for collecting data.

[0303] In some embodiments, the first network element may also determine the candidate device list from at least one second device based on the data capability information of at least one second device stored therein, in which case steps S2109 to S2111 may be omitted.

[0304] In some embodiments, the first network element may determine the second device that matches the received data collection request based on the data capability information of at least one second device stored in the network, thereby obtaining the candidate device list.

[0305] For example, if the data collection request includes a device identifier, the first network element can select a second device from at least one second device that has the same device identifier as indicated by the data collection request, based on the stored data capability information of at least one second device, to obtain the candidate device list; if the data collection request includes a data type, the first network element can select a second device from at least one second device that can support the data type indicated by the data collection request, based on the stored data capability information of at least one second device, to obtain the candidate device list; if the data collection request includes a data collection area, the first network element can select a second device from at least one second device within the area indicated by the data collection request, based on the stored data capability information of at least one second device, to obtain the candidate device list.

[0306] Step S2110: The second network element determines a candidate device list from at least one second device based on the first request and the data capability information of at least one second device stored therein.

[0307] In some embodiments, after receiving a first request from a first network element, the second network element can determine a second device that matches the received first request based on the data capability information of at least one second device stored therein, and obtain the candidate device list.

[0308] For example, if the first request includes a device identifier, the first device can select a second device with the same device identifier as indicated by the first request from at least one second device based on the stored data capability information of at least one second device, thus obtaining the candidate device list; if the first request includes a data type, the first device can select a second device capable of supporting the data type indicated by the first request from at least one second device based on the stored data capability information of at least one second device, thus obtaining the candidate device list; if the first request includes a data collection area, the first device can select a second device within the area indicated by the first request from at least one second device based on the stored data capability information of at least one second device, thus obtaining the candidate device list.

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

[0310] In some embodiments, the first response message may include the list of candidate devices.

[0311] In some embodiments, after the second network element determines the candidate device list, it can send a first response message to the first network element so that the first network element can obtain the candidate device list.

[0312] Step S2112: The first network element sends a first connection establishment request to the first device.

[0313] In some embodiments, the first device may include at least one device from the candidate device list.

[0314] In some embodiments, after the first network element determines a list of candidate devices or receives a list of candidate devices sent by the second network element, it can select one or more devices from the list of candidate devices and send a first connection establishment request to the selected one or more devices to request to establish a connection with the selected one or more devices.

[0315] For example, the first network element can send a first connection establishment request to any one or more devices in the candidate device list, and different devices can correspond to different first connection establishment requests.

[0316] In some embodiments, the first connection establishment request may include at least one of the following: the device identifier of the first device, the address of the first network element, and information about the data to be collected.

[0317] In some embodiments, the information of the data to be collected may include, for example, the data type, data format, and data volume.

[0318] Step S2113: The first device sends a first connection establishment response message to the first network element.

[0319] In some embodiments, after receiving a first connection establishment request sent by a first network element, the first device can establish a connection with the first network element and send a first connection establishment response message to the first network element.

[0320] In some embodiments, the first connection establishment response message includes at least one of the following: connection establishment result, address of the first device.

[0321] In some embodiments, the connection establishment result can be either a successful connection or a connection failure.

[0322] Step S2114: The first device sends its data to the first network element.

[0323] In some embodiments, after the first device successfully establishes a connection with the first network element, the first device can send the collected data to the first network element according to the address of the first network element.

[0324] Using the above method, the first network element and the second network element can store the data capability information of non-3GPP equipment according to the instructions, realizing the secure storage of the data capability information of non-3GPP equipment. Furthermore, the first network element can match the first device that collects data based on the stored data capability information of the second device, establish a connection with the first device, and obtain the data collected by the first device, thereby improving the accuracy of the data collection process and reducing invalid signaling interactions and resource waste.

[0325] The methods involved in the embodiments of this disclosure may include at least one of the steps S2101 to S2114 described above. For example, step S2101 may be implemented as an independent embodiment, step S2102 may be implemented as an independent embodiment, step S2103 may be implemented as an independent embodiment, step S2105 may be implemented as an independent embodiment, step S2108 may be implemented as an independent embodiment, step S2109 may be implemented as an independent embodiment, step S2112 may be implemented as an independent embodiment, step S2114 may be implemented as an independent embodiment, step S2101 + step S2102 may be implemented as an independent embodiment, step S2102 + step S2103 may be implemented as an independent embodiment, step S2109 + step S2110 may be implemented as an independent embodiment, and step S2112 + step S2113 + step S2114 may be implemented as an independent embodiment, but are not limited thereto.

[0326] In some embodiments, the order of any two steps S2101 to S2114 can be interchanged or they can be performed simultaneously. For example, the order of steps S2103 and S2105 can be interchanged or they can be performed simultaneously, as can the order of steps S2104 and S2106, and the order of steps S2103 and S2105 can be interchanged or they can be performed simultaneously.

[0327] In some embodiments, steps S2101 to S2114 are optional, and one or more of these steps may be omitted or substituted in different embodiments. For example, some or all of the steps in steps S2101 to S2107 may be omitted.

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

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

[0330] Step S2201: The third network element sends a third request to the fourth network element.

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

[0332] Step S2202: The fourth network element sends a second request to the fifth network element based on the third request.

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

[0334] Step S2203: The first network element stores the data capability information of the second device.

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

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

[0337] The optional implementation of step S2204 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.

[0338] Step S2205: The second network element stores the data capability information of the second device.

[0339] The optional implementation of step S2205 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.

[0340] Step S2206: The second network element sends a second response message to the fourth network element.

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

[0342] Step S2207: The fourth network element sends a third response message to the third network element based on the second response message.

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

[0344] In some embodiments, the data capability information of the second device may also be pre-configured in the first network element and / or the second network element, in which case some or all of the steps in steps S2201 to S2207 may be omitted.

[0345] Step S2208: The first network element receives a data collection request.

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

[0347] Step S2209: The first network element sends a first request to the second network element.

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

[0349] In some embodiments, the first network element may also determine the candidate device list from at least one second device based on the data capability information of at least one second device stored therein, in which case steps S2209 to S2211 may be omitted.

[0350] Step S2210: The second network element determines a candidate device list from at least one second device based on the first request and the data capability information of at least one second device stored therein.

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

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

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

[0354] Step S2212: The first network element sends a second connection establishment request to the third network element.

[0355] In some embodiments, the second connection establishment request is used to request the establishment of a connection with a third network element.

[0356] In some embodiments, the second connection establishment request includes at least one of the following: the device identifier of the first device, the address of the first network element, and information about the data to be collected.

[0357] In some embodiments, the information of the data to be collected may include, for example, the data type, data format, and data volume.

[0358] In some embodiments, the first device may be a device selected by the first network element from a list of candidate devices. For example, after the first network element determines the list of candidate devices or receives a list of candidate devices sent by the second network element, it may select one or more devices from the list of candidate devices to obtain the first device.

[0359] In some embodiments, after the first network element selects the first device, it may send a second connection establishment request to the third network element, and carry the device identifier of the first device in the second connection establishment request.

[0360] Step S2213: The third network element establishes a connection with the first network element according to the second connection request.

[0361] In some embodiments, after receiving a second connection establishment request sent by a first network element, a third network element may establish a connection with the first network element.

[0362] Step S2214: The third network element sends a fourth connection establishment request to the first device based on the second connection establishment request.

[0363] In some embodiments, after receiving a second connection establishment request sent by a first network element, a third network element may send a fourth connection establishment request to the first device according to the device identifier of the first device indicated by the second connection establishment request. Different devices may correspond to different fourth connection establishment requests.

[0364] In some embodiments, the fourth connection establishment request is used to request the establishment of a connection with the first device.

[0365] In some embodiments, the fourth connection establishment request includes at least one of the following: the device identifier of the first device, the address of the third network element, and information about the data to be collected.

[0366] Step S2215: The first device sends a fourth connection establishment response message to the third network element.

[0367] In some embodiments, after receiving a fourth connection establishment request sent by a third network element, the first device can establish a connection with the third network element and send a fourth connection establishment response message to the third network element after the connection is established.

[0368] In some embodiments, the fourth connection establishment response message includes at least one of the following: connection establishment result, address of the first device.

[0369] In some embodiments, the connection establishment result can be either a successful connection or a connection failure.

[0370] Step S2216: The third network element sends a second connection establishment response message to the first network element based on the fourth connection establishment response message.

[0371] In some embodiments, after receiving the fourth connection establishment response message sent by the first device, the third network element may send a second connection establishment response message to the first network element based on the fourth connection establishment response message.

[0372] In some embodiments, the second connection establishment response message includes at least one of the following: connection establishment result, address of the first device, and the second connection establishment response message informs the first network element of the connection establishment result between the third network element and the first device.

[0373] In some embodiments, the connection establishment result can be either a successful connection or a connection failure.

[0374] Step S2217: The first device sends its data to the third network element.

[0375] In some embodiments, after the first device successfully establishes a connection with the third network element, it can send the collected data to the first network element according to the address of the third network element.

[0376] Step S2218: The third network element sends the data from the first device to the first network element.

[0377] In some embodiments, after receiving data sent by the first device, the third network element can send the data of the first device back to the first network element according to the address of the first network element.

[0378] Using the above method, the first network element and the second network element can store the data capability information of non-3GPP equipment according to the instructions, realizing the secure storage of the data capability information of non-3GPP equipment. Furthermore, the first network element can match the first device that collects data based on the stored data capability information of the second device, and establish a connection with the first device through the third network element to obtain the data collected by the first device, thereby improving the accuracy of the data collection process and reducing invalid signaling interactions and resource waste.

[0379] The methods involved in the embodiments of this disclosure may include at least one of the steps S2201 to S2218 described above. For example, step S2201 can be implemented as an independent embodiment, step S2202 can be implemented as an independent embodiment, step S2203 can be implemented as an independent embodiment, step S2205 can be implemented as an independent embodiment, step S2208 can be implemented as an independent embodiment, step S2209 can be implemented as an independent embodiment, step S2212 can be implemented as an independent embodiment, step S2214 can be implemented as an independent embodiment, step S2201 + step S2202 can be implemented as an independent embodiment, step S2202 + step S2203 can be implemented as an independent embodiment, step S2209 + step S2210 can be implemented as an independent embodiment, and step S2212 + step S2213 + step S2214 can be implemented as an independent embodiment, but are not limited thereto.

[0380] In some embodiments, the order of any two steps S2201 to S2218 can be interchanged or they can be executed simultaneously. For example, the order of steps S2203 and S2205 can be interchanged or they can be executed simultaneously, as can the order of steps S2204 and S2206, and the order of steps S2203 and S2205 can be interchanged or they can be executed simultaneously.

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

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

[0383] 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 embodiments of the present disclosure relate to a communication method, which includes:

[0384] Step S2301: The third network element sends a third request to the fourth network element.

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

[0386] Step S2302: The fourth network element sends a second request to the fifth network element based on the third request.

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

[0388] Step S2303: The first network element stores the data capability information of the second device.

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

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

[0391] The optional implementation of step S2304 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.

[0392] Step S2305: The second network element stores the data capability information of the second device.

[0393] The optional implementation of step S2305 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.

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

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

[0396] Step S2307: The fourth network element sends a third response message to the third network element based on the second response message.

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

[0398] In some embodiments, the data capability information of the second device may also be pre-configured in the first network element and / or the second network element, in which case some or all of the steps in steps S2301 to S2307 may be omitted.

[0399] Step S2308: The first network element receives a data collection request.

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

[0401] Step S2309: The first network element sends a first request to the second network element.

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

[0403] In some embodiments, the first network element may also determine the candidate device list from at least one second device based on the data capability information of at least one second device stored therein, in which case steps S2309 to S2311 may be omitted.

[0404] Step S2310: The second network element determines a candidate device list from at least one second device based on the first request and the data capability information of at least one second device stored therein.

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

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

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

[0408] Step S2312: The first network element sends a third connection establishment request to the terminal.

[0409] In some embodiments, the third connection establishment request is used to request the establishment of a connection with the terminal.

[0410] In some embodiments, the third connection establishment request includes at least one of the following: the device identifier of the first device, the address of the first network element, and information about the data to be collected.

[0411] In some embodiments, the information of the data to be collected may include, for example, the data type, data format, and data volume.

[0412] In some embodiments, the first device may be a device selected by the first network element from a list of candidate devices. For example, after the first network element determines the list of candidate devices or receives a list of candidate devices sent by the second network element, it may select one or more devices from the list of candidate devices to obtain the first device.

[0413] In some embodiments, after the first network element selects the first device, it may send a third connection establishment request to the terminal and carry the device identifier of the first device in the third connection establishment request.

[0414] Step S2313: The terminal sends a third connection establishment response message to the first network element.

[0415] In some embodiments, after receiving a third connection establishment request sent by a first network element, the terminal can establish a connection with the first network element.

[0416] Step S2314: The terminal collects data from the first device.

[0417] In some embodiments, the first device may establish a connection with a terminal and connect to the core network through the terminal.

[0418] In some embodiments, when the first device is connected to the terminal, the terminal can bind the device identifier of the first device to a non-3GPP service so that the network can distinguish between different non-3GPP devices connected through the same terminal.

[0419] In some embodiments, the terminal may collect data from a first connected device.

[0420] Step S2315: The terminal sends the data collected from the first device to the first network element.

[0421] In some embodiments, after the terminal collects data from the first device, it sends the data from the first device to the first network element.

[0422] Using the above method, the first network element and the second network element can store the data capability information of non-3GPP equipment according to the instructions, realizing the secure storage of the data capability information of non-3GPP equipment. Furthermore, the first network element can match the first device that collects data based on the stored data capability information of the second device, and obtain the data collected by the first device through the terminal, which improves the accuracy of the data collection process, while also reducing invalid signaling interactions and resource waste.

[0423] The methods involved in the embodiments of this disclosure may include at least one of the steps S2301 to S2315 described above. For example, step S2301 can be implemented as an independent embodiment, step S2302 can be implemented as an independent embodiment, step S2303 can be implemented as an independent embodiment, step S2305 can be implemented as an independent embodiment, step S2308 can be implemented as an independent embodiment, step S2309 can be implemented as an independent embodiment, step S2312 can be implemented as an independent embodiment, step S2314 can be implemented as an independent embodiment, step S2301 + step S2302 can be implemented as an independent embodiment, step S2302 + step S2305 can be implemented as an independent embodiment, step S2309 + step S2310 can be implemented as an independent embodiment, step S2312 + step S2313 can be implemented as an independent embodiment, and step S2314 + step S2315 can be implemented as an independent embodiment, but are not limited thereto.

[0424] In some embodiments, the order of any two steps S2301 to S2315 can be interchanged or they can be performed simultaneously. For example, the order of steps S2303 and S2305 can be interchanged or they can be performed simultaneously, as can the order of steps S2304 and S2306, and the order of steps S2303 and S2305 can be interchanged or they can be performed simultaneously.

[0425] In some embodiments, steps S2301 to S2315 are optional, and one or more of these steps may be omitted or substituted in different embodiments. For example, some or all of the steps in steps S2301 to S2307 may be omitted.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0442] 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:

[0443] Step S3101: Receive the second request.

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

[0445] Step S3102: Store the data capability information of the second device.

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

[0447] Step S3103: Send the second response message.

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

[0449] Step S3104: Receive data collection request.

[0450] The optional implementation of step S3104 can be found in the optional implementation of step S2108 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0451] Step S3105: Send the first request.

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

[0453] Step S3106: Receive the first response message.

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

[0455] Step S3107: Send the first connection establishment request.

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

[0457] Step S3108: Receive the first connection establishment response message.

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

[0459] Step S3109: Receive data from the first device.

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

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

[0462] 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:

[0463] Step S3201: Receive the second request.

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

[0465] Step S3202: Store the data capability information of the second device.

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

[0467] Step S3203: Send the second response message.

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

[0469] Step S3204: Receive data collection request.

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

[0471] Step S3205: Send the first request.

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

[0473] Step S3206: Receive the first response message.

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

[0475] Step S3207: Send a second connection establishment request.

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

[0477] Step S3208: Receive the second connection establishment response message.

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

[0479] Step S3209: Receive data from the first device.

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

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

[0482] 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, which can be executed by a first network element. The method may include:

[0483] Step S3301: Receive the second request.

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

[0485] Step S3302: Store the data capability information of the second device.

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

[0487] Step S3303: Send the second response message.

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

[0489] Step S3304: Receive data collection request.

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

[0491] Step S3305: Send the first request.

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

[0493] Step S3306: Receive the first response message.

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

[0495] Step S3307: Send a third connection establishment request.

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

[0497] Step S3308: Receive the third connection establishment response message.

[0498] The optional implementation of step S3308 can be found in the optional implementation of step S2313 in Figure 2C, and other related parts in the embodiment involved in Figure 2C, which will not be repeated here.

[0499] Step S3309: Receive data collected from the first device.

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

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

[0502] 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:

[0503] Step S3401: Receive the second request.

[0504] The optional implementation of step S3401 can be found in the optional implementation of step S2402 in Figure 2D, and other related parts in the embodiments involved in Figure 2D, which will not be repeated here.

[0505] Step S3402: Store the data capability information of the second device.

[0506] The optional implementation of step S3402 can be found in the optional implementation of step S2403 in Figure 2D, and other related parts in the embodiments involved in Figure 2D, which will not be repeated here.

[0507] Step S3403: Send the second response message.

[0508] The optional implementation of step S3403 can be found in the optional implementation of step S2404 in Figure 2D, and other related parts in the embodiments involved in Figure 2D, which will not be repeated here.

[0509] Step S3404: Receive data collection request.

[0510] The optional implementation of step S3404 can be found in the optional implementation of step S2408 in Figure 2D, and other related parts in the embodiments involved in Figure 2D, which will not be repeated here.

[0511] Step S3405: ​​Obtain the candidate device list according to the data collection request.

[0512] In some embodiments, the first network element may determine the second device that matches the received data collection request based on the data capability information of at least one second device stored in the network, thereby obtaining the candidate device list.

[0513] For example, if the data collection request includes a device identifier, the first network element can select a second device from at least one second device that has the same device identifier as indicated by the data collection request, based on the stored data capability information of at least one second device, to obtain the candidate device list; if the data collection request includes a data type, the first network element can select a second device from at least one second device that can support the data type indicated by the data collection request, based on the stored data capability information of at least one second device, to obtain the candidate device list; if the data collection request includes a data collection area, the first network element can select a second device from at least one second device within the area indicated by the data collection request, based on the stored data capability information of at least one second device, to obtain the candidate device list.

[0514] Step S3406: Collect data from the first device.

[0515] The optional implementation of step S3406 can be found in the optional implementations of steps S2112 to S2114 in Figure 2A, steps S2212 to S2218 in Figure 2B, steps S2312 to S2315 in Figure 2C, and other related parts in the embodiments involved in Figures 2A, 2B, and 2C, which will not be repeated here.

[0516] In some embodiments, the first network element may also establish a channel to the User Plane Function (UPF) to forward data from the first device via the UPF.

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

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

[0519] Step S3501: Receive data request.

[0520] The optional implementation of step S3501 can be found in the optional implementations of step S2108 in Figure 2A, step S2208 in Figure 2B, and step S2308 in Figure 2C, as well as other related parts in the embodiments involved in Figures 2A, 2B, and 2C, which will not be repeated here.

[0521] Step S3502: Obtain the candidate device list according to the data collection request.

[0522] The optional implementation of step S3502 can be found in the optional implementations of steps S2109 to S2111 in Figure 2A, steps S2209 to S2211 in Figure 2B, steps S2309 to S2311 in Figure 2C, and other related parts in the embodiments involved in Figures 2A, 2B, and 2C, which will not be repeated here.

[0523] Step S3503: Collect data from the first device.

[0524] The optional implementation of step S3503 can be found in the optional implementations of steps S2112 to S2114 in Figure 2A, steps S2212 to S2218 in Figure 2B, steps S2312 to S2315 in Figure 2C, and other related parts in the embodiments involved in Figures 2A, 2B, and 2C, which will not be repeated here.

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

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

[0527] Step S3601: Receive the second request.

[0528] The optional implementation of step S3601 can be found in the optional implementations of step S2102 in Figure 2A, step S2202 in Figure 2B, and step S2302 in Figure 2C, as well as other related parts in the embodiments involved in Figures 2A, 2B, and 2C, which will not be repeated here.

[0529] Step S3602: Store the data capability information of the second device.

[0530] The optional implementation of step S3602 can be found in the optional implementations of step S2103 in Figure 2A, step S2203 in Figure 2B, and step S2303 in Figure 2C, as well as other related parts in the embodiments involved in Figures 2A, 2B, and 2C, which will not be repeated here.

[0531] Step S3603: Send the second response message.

[0532] The optional implementation of step S3603 can be found in the optional implementations of step S2104 in Figure 2A, step S2204 in Figure 2B, and step S2304 in Figure 2C, as well as other related parts in the embodiments involved in Figures 2A, 2B, and 2C, which will not be repeated here.

[0533] In some embodiments, obtaining the candidate device list according to the data collection request includes:

[0534] Send a first request to the second network element; the first request is used to obtain the candidate device list, and the first request includes at least one of the following: device identifier, data type, data format, and data collection area;

[0535] The system receives a first response message sent by the second network element, the first response message including the candidate device list.

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

[0537] Send a first connection establishment request to the first device; wherein, the first connection establishment request is used to request to establish a connection with the first device, different first devices correspond to different first connection establishment requests, and the first connection establishment request includes at least one of the following: the device identifier of the first device, the address of the first network element, and information about the data to be collected;

[0538] The device receives a first connection establishment response message sent by the first device, the first connection establishment response message including at least one of the following: connection establishment result, address of the first device.

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

[0540] Send a second connection establishment request to the third network element. The second connection establishment request is used to request to establish a connection with the third network element. The second connection establishment request includes at least one of the following: the device identifier of the first device, the address of the first network element, and information about the data to be collected.

[0541] The system receives a second connection establishment response message sent by the third network element. The second connection establishment response message includes at least one of the following: connection establishment result and the address of the first device.

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

[0543] A third connection establishment request is sent to the terminal. The third connection establishment request is used to request to establish a connection with the terminal. The third connection establishment request includes at least one of the following: the device identifier of the first device, the address of the first network element, and information about the data to be collected.

[0544] The terminal sends a third connection establishment response message, which includes at least one of the following: connection establishment result, and the address of the first device.

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

[0546] The first network element receives a second request sent by a fourth network element. The second request includes data capability information of the second device. The second request is used to request the first network element to store the data capability information.

[0547] Store the data capability information of the second device.

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

[0549] The device identifier of the second device;

[0550] The device functions of the second device;

[0551] The equipment type of the second device;

[0552] The types of data that the second device can collect;

[0553] The second device can collect data in the following formats;

[0554] The terminal identifier associated with the second device;

[0555] User consent information, which is used to determine whether the user needs to authorize the purpose of using the data collected by the second device;

[0556] The address of the second device.

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

[0558] A second response message is sent to the fourth network element, the second response message including the storage result of the data capability information of the second device.

[0559] In some embodiments, collecting data from the first device includes:

[0560] Receive data sent by the first device; or,

[0561] Receive data collected from the first device by a third network element or terminal.

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

[0563] Step S4101: Receive the second request.

[0564] The optional implementation of step S4101 can be found in the optional implementations of step S2102 in Figure 2A, step S2202 in Figure 2B, and step S2302 in Figure 2C, as well as other related parts in the embodiments involved in Figures 2A, 2B, and 2C, which will not be repeated here.

[0565] Step S4102: Store the data capability information of the second device.

[0566] The optional implementation of step S4102 can be found in the optional implementations of step S2105 in Figure 2A, step S2205 in Figure 2B, and step S2305 in Figure 2C, as well as other related parts in the embodiments involved in Figures 2A, 2B, and 2C, which will not be repeated here.

[0567] Step S4103: Send the second response message.

[0568] The optional implementation of step S4103 can be found in the optional implementations of step S2106 in Figure 2A, step S2206 in Figure 2B, and step S2306 in Figure 2C, as well as other related parts in the embodiments involved in Figures 2A, 2B, and 2C, which will not be repeated here.

[0569] Step S4104: Receive the first request.

[0570] The optional implementation of step S4104 can be found in the optional implementations of step S2109 in Figure 2A, step S2209 in Figure 2B, and step S2309 in Figure 2C, as well as other related parts in the embodiments involved in Figures 2A, 2B, and 2C, which will not be repeated here.

[0571] Step S4105: Determine a candidate device list from at least one second device based on the first request and the data capability information of at least one second device stored.

[0572] The optional implementation of step S4105 can be found in the optional implementations of step S2110 in Figure 2A, step S2210 in Figure 2B, and step S2310 in Figure 2C, as well as other related parts in the embodiments involved in Figures 2A, 2B, and 2C, which will not be repeated here.

[0573] Step S4106: Send the first response message.

[0574] The optional implementation of step S4106 can be found in the optional implementations of step S2111 in Figure 2A, step S2211 in Figure 2B, and step S2311 in Figure 2C, as well as other related parts in the embodiments involved in Figures 2A, 2B, and 2C, which will not be repeated here.

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

[0576] Figure 4B is a flowchart 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 that can be executed by a second network element. The method may include:

[0577] Step S4201: Receive the second request.

[0578] The optional implementation of step S4201 can be found in the optional implementations of step S2102 in Figure 2A, step S2202 in Figure 2B, and step S2302 in Figure 2C, as well as other related parts in the embodiments involved in Figures 2A, 2B, and 2C, which will not be repeated here.

[0579] Step S4202: Store the data capability information of the second device.

[0580] The optional implementation of step S4202 can be found in the optional implementations of step S2105 in Figure 2A, step S2205 in Figure 2B, and step S2305 in Figure 2C, as well as other related parts in the embodiments involved in Figures 2A, 2B, and 2C, which will not be repeated here.

[0581] Step S4203: Send the second response message.

[0582] The optional implementation of step S4203 can be found in the optional implementations of step S2106 in Figure 2A, step S2206 in Figure 2B, and step S2306 in Figure 2C, as well as other related parts in the embodiments involved in Figures 2A, 2B, and 2C, which will not be repeated here.

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

[0584] In some embodiments of this disclosure, it is proposed to register the data capability information (non-3GPP device identifier, device function, device type, data format, IP / MAC address) of non-3GPP devices to a 6G network without a UE (e.g., NRF, UDR / UDM, DCF), with the following enhancements: 1) DCF (data collection function) is used to discover and select non-3GPP devices as data source entities from NRF / UDR / UDM based on data collection service requests; 2) DCF uses the IP address of the registered non-3GPP device to establish a data connection between DCF and the non-3GPP device; or DCF establishes a data connection with AF / AS, and AF / AS establishes a data connection with the non-3GPP device.

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

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

[0587] 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 UE / NF data capabilities registered in the data capability management function (e.g., NRF, UDR / UDM, DCF).

[0588] In some embodiments, DCF also supports processing the collected data, such as coordinating different data collection service consumers that request 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.

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

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

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

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

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

[0594] Device type, such as UE, non-3GPP device, network function, or AF;

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

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

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

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

[0599] IP / MAC address / port information.

[0600] In some embodiments, NF data capability information includes the following parameters:

[0601] NF ID / Instance ID;

[0602] Data type;

[0603] Data format;

[0604] Data transmission capability, C and / or UP;

[0605] IP address / FQDN.

[0606] In some embodiments, non-3GPP device data capability information is defined as including the following parameters:

[0607] Device ID, such as IMEI or non-3GPP device identifier (e.g., assigned by the network, UE, or service provider);

[0608] Equipment capabilities;

[0609] Equipment type;

[0610] Data format;

[0611] Associated UE ID;

[0612] User consent information;

[0613] IP / MAC address;

[0614] In some embodiments, for data collection from non-3GPP devices without a UE, it is assumed that the non-3GPP device data capability is registered or pre-configured in a 6G network function (e.g., NRF, DCF, or UDR / UDM). The network function (DCF) can establish a data connection to the non-3GPP device and collect the required data from it. The following options are available:

[0615] As a network server, DCF can directly establish IP connections with non-3GPP devices;

[0616] DCF can establish IP connections to AF / AS, and AF / AS can establish data connections between AS / AF and non-3GPP devices.

[0617] The DCF establishes a channel to the UPF, and the UPF forwards data from / to non-3GPP devices.

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

[0619] Step S5201a: Pre-configure data capability information for non-3GPP devices.

[0620] In some embodiments, non-3GPP device data capability information is pre-configured in the core network functions responsible for storing and managing non-3GPP device data capabilities, such as NRF, UDR / UDM, or DCF.

[0621] In some embodiments, non-3GPP device data capability information includes at least one of the following: device ID, device function / capability, device type, data format, and IP / MAC address.

[0622] Step S5201b: AF sends a device data capability registration request to NEF.

[0623] In some embodiments, the data capability registration request includes data capability information for non-3GPP devices.

[0624] Step S5202: NEF sends a device data capability registration request to the network function responsible for storing / managing the data capabilities of non-3GPP devices.

[0625] In some embodiments, the NEF checks whether the data capability registration request or the AF is allowed to request such a service. If the data capability registration request or the AF is allowed to request such a service, the NEF sends the device data capability registration request to the network function (e.g., NRF, UDR / UDM, or DCF) responsible for storing / managing the data capabilities of non-3GPP devices.

[0626] Step S5203: The storage / management NF sends a response message including the result to the NEF.

[0627] Step S5204: NEF sends a response message including the result to AF / AS.

[0628] Step S5205: DCF determines which non-3GPP devices to collect data from based on data collection requests from internal or external consumers.

[0629] Step S5206: DCF sends a discovery and selection request to NRF / UDR / UDM.

[0630] In some embodiments, the request may include a non-3GPP device ID (optional), data type, data format, region, etc.

[0631] Step S5207: NRF / UDR / UDM sends a discovery and selection response to DCF.

[0632] In some embodiments, the discovery and selection response includes a list of candidate devices, such as non-3GPP devices or IP addresses.

[0633] Step S5208: The DCF sends a data connection establishment request directly to the AF or through the NEF to the AF, or through the AF to a non-3GPP device.

[0634] In some embodiments, DCF selects a list of candidate non-3GPP devices based on the conditions in the request message.

[0635] In some embodiments, the data connection establishment request includes a non-3GPP device ID, the DCF's IP address, a data collection instruction, and data information, such as a data format.

[0636] Step S5209: DCF receives data and establishes connection response.

[0637] In some embodiments, the data connection establishment response includes a result and an optional new IP address for a non-3GPP device.

[0638] In some embodiments, non-3GPP devices can upload data to the DCF.

[0639] 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, comprising units or modules for implementing the steps performed by the first network element in any of the above methods. Another apparatus is proposed, comprising units or modules for implementing the steps performed by the second network element in any of the above methods. Yet another apparatus is proposed, comprising units or modules for implementing the steps performed by the third network element in any of the above methods. Another apparatus is proposed, comprising units or modules for implementing the steps performed by the fourth network element in any of the above methods. Yet another apparatus is proposed, comprising units or modules for implementing the steps performed by the first device in any of the above methods. And yet another apparatus is proposed, comprising units or modules for implementing the steps performed by the terminal in any of the above methods.

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

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

[0642] Figure 6A is a schematic diagram of the structure of the first network element proposed in an embodiment of this disclosure. The first network element 6100 is used to perform any of the above methods. In some embodiments, as shown in Figure 6A, the first network element 6100 may include at least one of: a transceiver module 6101, a processing module 6102, etc. In some embodiments, the transceiver module is used to receive a data collection request, obtain a candidate device list according to the data collection request, the data collection request including at least one of the following: device identifier, data type, data format, and area for data collection; collect data from a first device, the first device including at least one device in the candidate device list. Optionally, the transceiver module is used to execute the communication steps such as sending and / or receiving performed by the first network element 6100 in any of the above methods (e.g., steps S2102, S2104, S2108, S2109, S2111, S2112, S2113, S2114, S2202, S2204, S2208, S2209, S2211, S2212, S2216, S2218, S2302, S2304, S2308, S2309, S2311, S2312, S2313, S2315, S3101, S3103, etc.). At least one of the following steps (but not limited to) is provided below: S3104, S3105, S3106, S3107, S3108, S3109, S3201, S3203, S3204, S3205, S3206, S3207, S3208, S3209, S3301, S3303, S3304, S3305, S3306, S3307, S3308, S3309, S3401, S3403, S3404, S3406, S3501, S3503, S3601, S3603, etc., which will not be elaborated further here. Optionally, the above processing module is used to execute at least one of the other steps executed by the first network element 6100 in any of the above methods (e.g., steps S2103, S2203, S2303, S3102, S3202, S3302, S3402, S3502, S3602, but not limited thereto), which will not be elaborated here.

[0643] Figure 6B is a schematic diagram of the structure of the second network element proposed in an embodiment of this disclosure. The second network element 6200 is used to perform any of the above methods. In some embodiments, as shown in Figure 6B, the second network element 6200 may include at least one of: a transceiver module 6201, a processing module 6202, etc. In some embodiments, the transceiver module is used to receive a first request sent by a first network element, the first request being used to obtain a candidate device list, the first request including at least one of the following: device identifier, data type, data format, and data collection area; the processing module is used to determine the candidate device list from the at least one second device according to the first request and the data capability information of at least one second device stored therein; the transceiver module is further used to send a first response message to the first network element, the first response message including the candidate device list, the first response message being used by the first network element to collect data from a first device, the first device including at least one device in the candidate device list. Optionally, the transceiver module is used to perform at least one of the communication steps such as sending and / or receiving performed by the second network element 6200 in any of the above methods (e.g., steps S2102, S2106, S2109, S2111, S2202, S2206, S2209, S2211, S2302, S2306, S2309, S2311, S4101, S4103, S4104, S4106, S4201, S4203, but not limited thereto), which will not be elaborated here. Optionally, the above processing module is used to execute at least one of the other steps executed by the second network element 6200 in any of the above methods (e.g., steps S2105, S2110, S2205, S2210, S2305, S2310, S4102, S4105, S4202, but not limited thereto), which will not be elaborated here.

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

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

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

[0647] Figure 6C is a schematic diagram of the structure of the third network element proposed in an embodiment of this disclosure. The third network element 6300 is used to perform any of the above methods. In some embodiments, as shown in Figure 6C, the third network element 6300 may include at least one of a transceiver module 6301, a processing module 6302, etc. In some embodiments, the transceiver module is used to send a third request to a fourth network element; the third request includes data capability information of the second device, and the third request is used to instruct the fourth network element to send a second request to a fifth network element, the fifth network element including a first network element and / or a second network element, the second request being used to request the fifth network element to store the data capability information of the second device, the data capability information stored by the fifth network element being used to determine a candidate device list, and the candidate device list being used by the first network element to collect data. Optionally, the transceiver module is used to perform at least one of the communication steps (e.g., steps S2101, S2107, S2201, S2207, S2214, S2215, S2216, S2217, S2218, S2301, S2307, but not limited thereto) performed by the third network element 6300 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 (e.g., step S2213, but not limited thereto) performed by the third network element 6300 in any of the above methods, which will not be elaborated here.

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

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

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

[0651] Figure 6D is a schematic diagram of the structure of the fourth network element proposed in an embodiment of this disclosure. The fourth network element 6400 is used to perform any of the above methods. In some embodiments, as shown in Figure 6D, the fourth network element 6400 may include at least one of a transceiver module 6401, a processing module 6402, etc. In some embodiments, the transceiver module is used to receive a third request sent by a third network element, the third request including data capability information of a second device; and to send a second request to a fifth network element according to the third request; the fifth network element includes a first network element and / or a second network element, the second request including data capability information of the second device, the second request being used to request the fifth network element to store the data capability information of the second device, the data capability information stored by the fifth network element being used to determine a candidate device list, the candidate device list being used by the first network element to collect data. Optionally, the transceiver module described above is used to perform at least one of the communication steps (e.g., steps S2101, S2102, S2104, S2106, S2107, S2201, S2202, S2204, S2206, S2207, S2301, S2302, S2304, S2306, S2307, but not limited thereto) performed by the fourth network element 6400 in any of the above methods, which will not be elaborated here. Optionally, the processing module described above is used to perform at least one of the other steps performed by the fourth network element 6400 in any of the above methods, which will not be elaborated here.

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

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

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

[0655] Figure 6E is a schematic diagram of the structure of the first device proposed in an embodiment of this disclosure. The first device 6500 is used to perform any of the above methods. In some embodiments, as shown in Figure 6E, the first device 6500 may include at least one of: a transceiver module 6501, a processing module 6502, etc. In some embodiments, the transceiver module is used to receive a first connection establishment request sent by a first network element and send a first connection establishment response message to the first network element; wherein, the first connection establishment request is used to request to establish a connection with the first device, different first devices correspond to different first connection establishment requests, and the first connection establishment request includes at least one of the following: the device identifier of the first device, the address of the first network element, and information on the data to be collected; the first connection establishment response message includes at least one of the following: the connection establishment result, and the address of the first device; or, receiving a fourth connection establishment request sent by a third network element and sending a fourth connection establishment response message to the third network element; wherein, the fourth connection establishment request is used to request to establish a connection with the first device, different first devices correspond to different fourth connection establishment requests, and the fourth connection establishment response message includes at least one of the following: the connection establishment result, and the address of the first device. Optionally, the transceiver module is used to perform at least one of the communication steps (e.g., steps S2112, S2113, S2114, S2214, S2215, S2217, S2312, S2313, S2314, but not limited thereto) performed by the first device 6500 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 first device 6500 in any of the above methods, which will not be elaborated here.

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

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

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

[0659] Figure 6F is a schematic diagram of the terminal structure proposed in an embodiment of this disclosure. Terminal 6600 is used to execute any of the above methods. In some embodiments, as shown in Figure 6F, terminal 6600 may include at least one of: transceiver module 6601, processing module 6602, etc. In some embodiments, the transceiver module is used to receive a third connection establishment request sent by a first network element, the third connection establishment request being used to request the establishment of a connection with the terminal, the third connection establishment request including at least one of the following: the device identifier of the first device, the address of the first network element, and information about the data to be collected; and to send a third connection establishment response message to the first network element, the third connection establishment response message including at least one of the following: connection establishment result, and the address of the first device. Optionally, the transceiver module is used to execute at least one of the communication steps (e.g., steps S2312, S2313, S2314, S2315, but not limited thereto) performed by terminal 6600 in any of the above methods, which will not be elaborated further here. Optionally, the above processing module is used to perform at least one of the other steps executed by terminal 6600 in any of the above methods, which will not be elaborated here.

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

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

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

[0663] Figure 7A is a schematic diagram of the structure of the communication device 7100 proposed in an embodiment of this disclosure. The communication device 7100 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 7100 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.

[0664] As shown in Figure 7A, the communication device 7100 is used to execute any of the above methods. In some embodiments, the communication device 7100 includes one or more processors 7101. The processor 7101 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 7100 is used to execute any of the above methods. Optionally, one or more processors 7101 are used to invoke instructions to cause the communication device 7100 to execute any of the above methods.

[0665] In some embodiments, the communication device 7100 further includes one or more transceivers 7102. When the communication device 7100 includes one or more transceivers 7102, the transceivers 7102 perform communication steps such as sending and / or receiving in the above method (e.g., steps S2101, S2102, S2104, S2106, S2107, S2108, S2109, S2111, S2112, S2113, S2114, S2201, S2202, S2204, S2206, S2208, S2209, S2211, S2212, ...). Step S2214, Step S2215, Step S2216, Step S2217, Step S2218, Step S2301, Step S2302, Step S2304, Step S2306, Step S2307, Step S2308, Step S2309, Step S2311, Step S2312, Step S2313, Step S2314, Step S2315, Step S3101, Step S3103, Step S3104, Step S3105, Step S3106, Step S3107, Step S3108, Step S3109, Step S3201, Step Step S3203, Step S3204, Step S3205, Step S3206, Step S3207, Step S3208, Step S3209, Step S3301, Step S3303, Step S3304, Step S3305, Step S3306, Step S3307, Step S3308, Step S3309, Step S3401, Step S3403, Step S3404, Step S3406, Step S3501, Step S3503, Step S3601, Step S3603, Step S4101, Step S4103, Step S4104, Step At least one of steps S4106, S4201, and S4203 (but not limited thereto), processor 7101 executes at least one of other steps (e.g., steps S2103, S2105, S2110, S2203, S2205, S2210, S2303, S2305, S2310, S3102, S3202, S3302, S3402, S3502, S3602, S4102, S4105, and S4202, but not limited thereto). In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated together.Optionally, terms such as transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, and interface can be used interchangeably; terms such as transmitter, transmitter unit, transmitter, and transmitter circuit can be used interchangeably; and terms such as receiver, receiver unit, receiver, and receiver circuit can be used interchangeably.

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

[0667] The communication device 7100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 7100 described in this disclosure is not limited thereto, and the structure of the communication device 7100 may not be limited by FIG. 7A. The communication device may be a standalone device or may be part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally, the IC collection may also include storage components for storing data, 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.

[0668] Figure 7B is a schematic diagram of the structure of the chip 7200 according to an embodiment of this disclosure. For cases where the communication device 7100 can be a chip or a chip system, the schematic diagram of the chip 7200 shown in Figure 7B can be referenced, but is not limited thereto.

[0669] Chip 7200 includes one or more processors 7201. Chip 7200 is used to perform any of the above methods.

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

[0671] In some embodiments, the interface circuit 7202 performs communication steps such as sending and / or receiving in the above method (e.g., steps S2101, S2102, S2104, S2106, S2107, S2108, S2109, S2111, S2112, S2113, S2114, S2201, S2202, S2204, S2206, etc.). Steps S2208, S2209, S2211, S2212, S2214, S2215, S2216, S2217, S2218, S2301, S2302, S2304, S2306, S2307, S2308, S2309, S2311, S2312, S2313, S2314, S2208, S2209, S2311, S2312, S2313, S2314, S2209, S2208, S2209 ... 2315, Step S3101, Step S3103, Step S3104, Step S3105, Step S3106, Step S3107, Step S3108, Step S3109, Step S3201, Step S3203, Step S3204, Step S3205, Step S3206, Step S3207, Step S3208, Step S3209, Step S3301, Step S3303, Step S3304, Step S3 Steps S305, S3306, S3307, S3308, S3309, S3401, S3403, S3404, S3406, S3501, S3503, S3601, S3603, S4101, S4103, S4104, S4106, S4201, S4203 (but not limited to these) are performed by the interface circuit 7202. The interface circuit 7202 performing the communication steps such as sending and / or receiving in the above method refers to, for example, the interface circuit 7202 performing data and / or instruction interaction between the processor 7201, chip 7200, memory 7203, or transceiver device. In some embodiments, the processor 7201 performs at least one of other steps (e.g., steps S2103, S2105, S2110, S2203, S2205, S2210, S2303, S2305, S2310, S3102, S3202, S3302, S3402, S3502, S3602, S4102, S4105, S4202, but not limited thereto).

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

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

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

[0675] 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: Receive a data collection request, and obtain a candidate device list based on the data collection request. The data collection request includes at least one of the following: device identifier, data type, data format, and data collection area. Data is collected from a first device, which includes at least one device from the candidate device list.

2. The method of claim 1, wherein, The step of obtaining the candidate device list according to the data collection request includes: Send a first request to the second network element; the first request is used to obtain the candidate device list, and the first request includes at least one of the following: device identifier, data type, data format, and data collection area; The system receives a first response message sent by the second network element, the first response message including the candidate device list.

3. The method according to claim 1 or 2, characterized in that, The method further includes: Send a first connection establishment request to the first device; wherein, the first connection establishment request is used to request to establish a connection with the first device, different first devices correspond to different first connection establishment requests, and the first connection establishment request includes at least one of the following: the device identifier of the first device, the address of the first network element, and information about the data to be collected; The device receives a first connection establishment response message sent by the first device, the first connection establishment response message including at least one of the following: connection establishment result, address of the first device.

4. The method according to claim 1 or 2, characterized in that, The method further includes: Send a second connection establishment request to the third network element. The second connection establishment request is used to request to establish a connection with the third network element. The second connection establishment request includes at least one of the following: the device identifier of the first device, the address of the first network element, and information about the data to be collected. The system receives a second connection establishment response message sent by the third network element. The second connection establishment response message includes at least one of the following: connection establishment result and the address of the first device.

5. The method according to claim 1 or 2, characterized in that, The method further includes: A third connection establishment request is sent to the terminal. The third connection establishment request is used to request to establish a connection with the terminal. The third connection establishment request includes at least one of the following: the device identifier of the first device, the address of the first network element, and information about the data to be collected. The terminal sends a third connection establishment response message, which includes at least one of the following: connection establishment result, and the address of the first device.

6. The method according to any one of claims 1 to 5, characterized in that, The method further includes: The first network element receives a second request sent by a fourth network element. The second request includes data capability information of the second device. The second request is used to request the first network element to store the data capability information. Store the data capability information of the second device.

7. The method of claim 6, wherein, The data capability information includes at least one of the following: The device identifier of the second device; The device functions of the second device; The equipment type of the second device; The types of data that the second device can collect; The second device can collect data in the following formats; The terminal identifier associated with the second device; User consent information, which is used to determine whether the user needs to authorize the purpose of using the data collected by the second device; The address of the second device.

8. The method according to claim 6 or 7, characterized in that, The method further includes: A second response message is sent to the fourth network element, the second response message including the storage result of the data capability information of the second device.

9. The method according to any one of claims 1 to 8, characterized in that, The data collected from the first device includes: Receive data sent by the first device; or, Receive data collected from the first device by a third network element or terminal.

10. A communication method characterized by comprising: The method, executed by the second network element, includes: The system receives a first request sent by a first network element. The first request is used to obtain a list of candidate devices. The first request includes at least one of the following: device identifier, data type, data format, and data collection area. Based on the first request and the data capability information of at least one second device stored, the candidate device list is determined from at least one second device; A first response message is sent to the first network element. The first response message includes the candidate device list. The first response message is used by the first network element to collect data from a first device. The first device includes at least one device in the candidate device list.

11. The method of claim 10, wherein, The method further includes: The system receives a second request sent by a fourth network element. The second request includes data capability information of the second device. The second request is used to request the fourth network element to store the data capability information. Store the data capability information of the second device.

12. The method of claim 11, wherein, The data capability information includes at least one of the following: The device identifier of the second device; The device functions of the second device; The equipment type of the second device; The types of data that the second device can collect; The second device can collect data in the following formats; The terminal identifier associated with the second device; User consent information, which is used to determine whether the user needs to authorize the purpose of using the data collected by the second device; The address of the second device.

13. The method according to claim 11 or 12, characterized in that, The method further includes: A second response message is sent to the fourth network element, the second response message including the storage result of the data capability information of the second device.

14. A communication method, comprising: The method, executed by the fourth network element, includes: Receive a third request sent by a third network element, wherein the third request includes data capability information of the second device; A second request is sent to a fifth network element according to the third request; the fifth network element includes a first network element and / or a second network element, the second request includes data capability information of the second device, the second request is used to request the fifth network element to store the data capability information of the second device, the data capability information stored by the fifth network element is used to determine a candidate device list, and the candidate device list is used by the first network element to collect data.

15. The method according to claim 14, characterized in that, The data capability information includes at least one of the following: The device identifier of the second device; The device functions of the second device; The equipment type of the second device; The types of data that the second device can collect; The second device can collect data in the following formats; The terminal identifier associated with the second device; User consent information, which is used to determine whether the user needs to authorize the purpose of using the data collected by the second device; The address of the second device.

16. The method according to claim 14 or 15, characterized in that, The method further includes: The system receives a second response message sent by the fifth network element, the second response message including the storage result of the data capability information of the second device.

17. The method according to claim 16, characterized in that, The method further includes: A third response message is sent to the third network element according to the second response message, and the third response message includes the storage result of the data capability information of the second device.

18. The method according to any one of claims 14-17, characterized in that, The method further includes: Determine whether the third request or the third network element is allowed to request the storage of the data capability information of the second device.

19. A communication method, characterized in that, The method, executed by a third network element, includes: A third request is sent to a fourth network element; the third request includes data capability information of the second device, and the third request is used to instruct the fourth network element to send a second request to a fifth network element, the fifth network element including a first network element and / or a second network element, the second request being used to request the fifth network element to store the data capability information of the second device, the data capability information stored by the fifth network element being used to determine a candidate device list, and the candidate device list being used by the first network element to collect data.

20. The method according to claim 19, characterized in that, The data capability information includes at least one of the following: The device identifier of the second device; The device functions of the second device; The equipment type of the second device; The types of data that the second device can collect; The second device can collect data in the following formats; The terminal identifier associated with the second device; User consent information, which is used to determine whether the user needs to authorize the purpose of using the data collected by the second device; The address of the second device.

21. The method according to claim 19 or 20, characterized in that, The method further includes: The third response message sent by the fourth network element is received, and the third response message includes the storage result of the data capability information of the second device.

22. The method according to any one of claims 19-21, characterized in that, The method further includes: The system receives a second connection establishment request sent by the first network element. The second connection establishment request is used to request the establishment of a connection with the third network element. The second connection establishment request includes at least one of the following: the device identifier of the first device, the address of the first network element, and information about the data to be collected. Establish a connection with the first network element according to the second connection request.

23. The method according to claim 22, characterized in that, The method further includes: A fourth connection establishment request is sent to the first device according to the second connection establishment request. The fourth connection establishment request is used to request to establish a connection with the first device. Different first devices correspond to different fourth connection establishment requests. The system receives a fourth connection establishment response message sent by the first device, the fourth connection establishment response message including at least one of the following: connection establishment result, address of the first device; According to the fourth connection establishment response message, a second connection establishment response message is sent to the first network element. The second connection establishment response message includes at least one of the following: connection establishment result, address of the first device.

24. The method according to claim 23, characterized in that, The method further includes: Receive data sent by the first device; Send the data from the first device to the first network element.

25. A communication method, characterized in that, Performed by a first device, the method includes: The system receives a first connection establishment request from a first network element and sends a first connection establishment response message to the first network element. The first connection establishment request is used to request the establishment of a connection with the first device; different first devices correspond to different first connection establishment requests. The first connection establishment request includes at least one of the following: the device identifier of the first device, the address of the first network element, and information about the data to be collected. The first connection establishment response message includes at least one of the following: the connection establishment result, and the address of the first device. Alternatively, The system receives a fourth connection establishment request sent by a third network element and sends a fourth connection establishment response message to the third network element. The fourth connection establishment request is used to request the establishment of a connection with the first device. Different first devices correspond to different fourth connection establishment requests. The fourth connection establishment response message includes at least one of the following: connection establishment result and the address of the first device.

26. The method according to claim 25, characterized in that, The method further includes: The data from the first device is sent to the first network element or the third network element.

27. A communication method, characterized in that, The method, executed by a terminal, includes: The system receives a third connection establishment request sent by a first network element. The third connection establishment request is used to request the establishment of a connection with the terminal. The third connection establishment request includes at least one of the following: the device identifier of the first device, the address of the first network element, and information about the data to be collected. A third connection establishment response message is sent to the first network element, the third connection establishment response message including at least one of the following: connection establishment result, address of the first device.

28. The method according to claim 27, characterized in that, The method further includes: Collect data from the first device; Send the data collected from the first device to the first network element.

29. A communication device, characterized in that, The communication device is used to perform the communication method according to any one of claims 1-9, 10-13, 14-18, 19-24, 25-26, and 27-28.

30. A communication system, characterized in that, The device includes a first network element, a second network element, a third network element, a fourth network element, a first device, and a terminal. The first network element is configured to implement the communication method according to any one of claims 1-9; the second network element is configured to implement the communication method according to any one of claims 10-13; the fourth network element is configured to implement the communication method according to any one of claims 14-18; the third network element is configured to implement the communication method according to any one of claims 19-24; the first device is configured to implement the communication method according to any one of claims 25-26; and the terminal is configured to implement the communication method according to any one of claims 27-28.

31. A storage medium storing instructions, characterized in that, When the instructions are executed on the communication device, the communication device performs the communication method as described in any one of claims 1-9, 10-13, 14-18, 19-24, 25-26, and 27-28.

32. A program product comprising at least one of a program and instructions, characterized in that, When at least one of the programs or instructions is executed by the communication device, it implements the steps of the method according to any one of claims 1-9, 10-13, 14-18, 19-24, 25-26, and 27-28.

Images