Data acquisition method, related equipment and medium

Abstract

The invention discloses a data acquisition method, related equipment and a medium. The data acquisition method applied to the PINE equipment in the PIN comprises the following steps: sending a data acquisition request for requesting to acquire target data to PEMC equipment in the PIN; wherein the target data is stored in at least one piece of PEGC equipment of the PIN; the target data is acquired by the at least one PEGC device from a network server in advance; the PEMC device is used for determining a target PEGC device from the at least one PEGC device and forwarding the data acquisition request to the target PEGC device; and receiving the target data sent by the target PEGC device. By means of the method, waste of network resources caused by the fact that the PINE device frequently obtains the target data through the 5GC can be reduced.

Description

Technical Field

[0001] This application relates to the technical field of personal Internet of Things networks, and particularly to a data acquisition method, related devices and media. Background Art

[0002] In the personal Internet of Things, when a PIN element device needs to establish connections with the control plane and user plane of the core network of the fifth-generation mobile communication system, it then establishes a data transmission channel between the data plane of its application layer and the server of a third-party service provider through the above, and then can obtain service data provided by the third-party service provider through the above data transmission channel. However, in the above data transmission process, it is very easy to cause waste of network resources, reduce the utilization rate of data transmission resources, and may even cause network congestion and paralysis in severe cases. Summary of the Invention

[0003] Based on the above technical problems, the embodiments of this application provide a data acquisition method, related devices and media.

[0004] The technical solution provided by the embodiments of this application is as follows:

[0005] The embodiments of this application provide a data acquisition method, which is applied to the PINE device in the PIN; the method includes:

[0006] Sending a data acquisition request for requesting to obtain target data to the PEMC device in the PIN; wherein, the target data is stored in at least one PEGC device of the PIN; the target data is pre-obtained from a network server by the at least one PEGC device; the PEMC device is used to determine a target PEGC device from the at least one PEGC device and forward the data acquisition request to the target PEGC device;

[0007] Receiving the target data sent by the target PEGC device.

[0008] In some embodiments, the sending a data acquisition request for requesting to obtain target data to the PEMC device in the PIN includes:

[0009] Obtaining a first identifier of the PINE device;

[0010] Generating the data acquisition request based on the first identifier;

[0011] Sending the data acquisition request to the PEMC device; wherein, the PEMC device is used to perform an authentication operation on the PINE device based on the first identifier, and forward the data acquisition request to the target PEGC device when the result of the authentication operation is authentication passed.

[0012] In some embodiments, the network server includes an AF device; before sending a data acquisition request for acquiring target data to the PEMC device in the PIN, the method further includes:

[0013] Receiving a broadcast message sent by the PEMC device; wherein the broadcast message is used to indicate that the at least one PEGC device has acquired the target data from the AF device.

[0014] An embodiment of the present application further provides a data acquisition method, which is applied to a target PEGC device in the PIN; the method includes:

[0015] Receiving a data acquisition request for acquiring target data sent by the PEMC device in the PIN; wherein the target PEGC device is determined by the PEMC device from at least one PEGC device included in the PIN; at least one of the at least one PEGC device stores the target data previously acquired from the network server; the data acquisition request is sent by the PINE device in the PIN to the PEMC device;

[0016] Sending the target data to the PINE device.

[0017] In some embodiments, the network server includes an AF device; before sending the target data to the PINE device, the method further includes:

[0018] Receiving a first address sent by the AF device; wherein the first address includes a storage address of the target data;

[0019] Acquiring the target data from the AF device based on the first address.

[0020] In some embodiments, after acquiring the target data from the AF device based on the first address, the method further includes:

[0021] Sending status information indicating that the target PEGC device has acquired the target data to the PEMC device, for the PEMC device to send a broadcast message to the PINE device based on the status information; wherein the broadcast message is used to indicate that the target PEGC device has acquired the target data from the AF device.

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

[0023] Receiving a data update message for indicating an update of the target data;

[0024] Update the target data based on the second address included in the data update message; wherein, the second address includes the storage address of the updated target data.

[0025] In some embodiments, the network server includes an AF device; the receiving a data update message for indicating an update of the target data includes:

[0026] Receive the data update message from an AMF network element; wherein, the data update message is sent by the AF device to the AMF network element via an NEF network element.

[0027] An embodiment of the present application further provides a data acquisition method, which is applied to a PEMC device in a PIN; the method includes:

[0028] Receive a data acquisition request for requesting to acquire target data sent by a PINE device in the PIN;

[0029] Determine a target PEGC device from at least one PEGC device included in the PIN; wherein, the target data pre-acquired from a network server is stored in the at least one PEGC device;

[0030] Forward the data acquisition request to the target PEGC device for the target PEGC device to send the target data to the PINE device.

[0031] In some embodiments, before receiving the data acquisition request for requesting to acquire target data sent by the PINE device in the PIN, the method further includes:

[0032] Receive status information that the at least one PEGC device has acquired the target data;

[0033] Generate a broadcast message based on the status information; wherein, the broadcast message is used to indicate that the at least one PEGC device has acquired the target data from the network server;

[0034] Send the broadcast message to the PINE device in the PIN.

[0035] In some embodiments, before receiving the data acquisition request for requesting to acquire target data sent by the PINE device in the PIN, the method further includes:

[0036] Send an address acquisition request to the AF device for the AF device to determine a first address storing the target data and send the first address to the at least one PEGC device; wherein, the first address is used for the at least one PEGC device to acquire the target data.

[0037] In some embodiments, sending the address acquisition request to the AF device includes:

[0038] Obtain a first service parameter; wherein, the first service parameter at least includes a service type; the first service parameter is associated with the PEMC device;

[0039] Generate the address acquisition request based on the first service parameter;

[0040] Send the address acquisition request to the AMF network element, so that the AMF network element determines, based on a second service parameter and the first service parameter, to forward the address acquisition request to the AF device via the NEF network element; wherein, the second service parameter includes service parameters stored in the UDM network element and associated with the AF device.

[0041] In some embodiments, the first service parameter is determined by the OSS network element and sent to the UDM network element.

[0042] In some embodiments, the second service parameter includes service type identifiers of at least one service; the service type identifiers are sent by the AF device to the NRF network element through the NEF network element.

[0043] In some embodiments, sending the address acquisition request to the AF device includes:

[0044] Obtain a second identifier of the at least one PEGC device;

[0045] Generate the address acquisition request based on the second identifier;

[0046] Send the address acquisition request to the AF device, so that the AF device sends the first address to the at least one PEGC device based on the second identifier.

[0047] In some embodiments, determining the target PEGC device from at least one PEGC device included in the PIN includes:

[0048] Determine a first identifier of the PINE device based on the data acquisition request;

[0049] Perform an authentication operation on the PINE device based on the first identifier to obtain an authentication result;

[0050] If the authentication result indicates that the PINE device passes authentication, determine the target PEGC device from the at least one PEGC device.

[0051] The embodiment of the present application also provides a PINE device, which includes a first processor and a first memory; wherein, a first computer program is stored in the first memory; when the first computer program is executed by the first processor, it can implement the data acquisition method applied to the PINE device as described in any one of the foregoing.

[0052] The embodiment of the present application also provides a PEGC device, which includes a second processor and a second memory; wherein, a second computer program is stored in the second memory; when the second computer program is executed by the second processor, it can implement the data acquisition method applied to the PEGC device as described in any one of the foregoing.

[0053] The embodiment of the present application also provides a PEMC device, which includes a third processor and a third memory; wherein, a third computer program is stored in the third memory; when the third computer program is executed by the third processor, it can implement the data acquisition method applied to the PEMC device as described in any one of the foregoing.

[0054] The embodiment of the present application also provides a computer-readable storage medium, in which a fourth computer program is stored; when the fourth computer program is executed by the processor of an electronic device, it can implement the data acquisition method as described in any one of the foregoing.

[0055] For the data acquisition method applied to the PINE device provided by the embodiment of the present application, before the PINE device sends a data acquisition request to request the acquisition of target data, at least one PEGC device in the PIN pre-gets the target data from the network server. Thus, through the above operations, the unified acquisition of the target data is achieved in terms of the PIN granularity; and by sending the target data from the target PEGC device to the PINE device, the pressure on the network resources of the 5GC caused by the PINE device frequently acquiring the target data through the 5GC can be reduced, and then the network resource utilization rate of the 5GC can be improved, and the short-distance data transmission resources in the PIN can be fully utilized; at the same time, the PINE device sends a data acquisition request to the PEMC device, and the PEMC device determines the target PEGC device and forwards the data acquisition request to the target PEGC device, thereby achieving the isolation between at least one PEGC device and the PINE device during the operation of determining the target PEGC device, and the management capabilities of the PEMC device for at least one PEGC device and the PINE device can also be fully utilized, thereby improving the stability and robustness of the process of acquiring the target data.

[0056] In the case where the target data is an AI model, through the above method, the frequency of the PINE device frequently obtaining the AI model through the 5GC can be reduced. Furthermore, the burden on the 5GC network resources caused by the PINE device frequently obtaining the AI model can be reduced, thereby improving the resource utilization rate of the 5GC network and also improving the network resource utilization rate in the PIN. Description of the Drawings

[0057] Figure 1A It is a schematic structural diagram of the PIN network architecture in 3GPP;

[0058] Figure 1B It is a schematic flowchart of the process for the terminal device to register to the PIN;

[0059] Figure 2 It is a schematic flowchart of the data acquisition method applied to the PINE device provided by the embodiment of the present application;

[0060] Figure 3 It is a schematic flowchart of the process for the PINE device to obtain the AI model provided by the embodiment of the present application;

[0061] Figure 4 It is a schematic flowchart of the process for the PEMC device to send broadcast information provided by the embodiment of the present application;

[0062] Figure 5 It is a schematic flowchart of the data acquisition method applied to the target PEGC device provided by the embodiment of the present application;

[0063] Figure 6 It is a schematic flowchart of the synchronization process of the update status of the AI model provided by the embodiment of the present application;

[0064] Figure 7 It is a schematic flowchart of the data acquisition method applied to the PEMC device provided by the embodiment of the present application;

[0065] Figure 8 It is a schematic flowchart of the process for setting the subscribed service type for the PEMC device provided by the embodiment of the present application;

[0066] Figure 9 It is a schematic flowchart of the AF registration process provided by the embodiment of the present application;

[0067] Figure 10 It is a schematic flowchart of the process for obtaining the AI model provided by the embodiment of the present application;

[0068] Figure 11 It is a schematic structural diagram of the PINE device provided by the embodiment of the present application;

[0069] Figure 12 It is a schematic structural diagram of the target PEGC device provided by the embodiment of the present application;

[0070] Figure 13 A schematic diagram of the structure of the PEMC device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0071] The technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application.

[0072] It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0073] The fifth generation mobile communication system (5 th As a new generation of mobile communication system with large bandwidth, low latency, high reliability and wide connection, 5G provides the necessary network infrastructure support for vertical industries. At the same time, vertical industries have widely deployed local area networks and the Internet of Things (IoT) including Wi-Fi, Bluetooth, Zigbee, Long Range Radio (Lora) and wired networks. In this case, based on cost and user usage habits, vertical industries may not be able to completely replace the existing network connection architecture with 5G networks in the short term. Therefore, the network connections of various vertical industries need to maintain the coexistence of 5G networks and other types of networks for a long time. In this case, if the terminals of the 5G network are in a state of network connection isolation from the terminals of other network connection formats, the goal of 5G Internet of Everything will not be achieved, so the integration of 5G and other types of networks is imperative.

[0074] On the other hand, in various scenarios corresponding to vertical industry technology fields with smaller spatial capacity such as medical care, education, home, and industrial control production, the types of devices that need to share data and information through the network are diverse, and there are many types of operating systems for various devices, and their network access methods are also different. Therefore, compared with traditional IoT devices, the stability of the operating status of the devices used in the above scenarios is relatively weak. For example, the battery capacity, communication distance, and signal transmission power of the devices used in the above scenarios are all weaker than the corresponding parameters of the IoT devices; and, in the above scenarios, user platform traffic is usually transmitted in an environment with smaller spatial capacity. Therefore, it is difficult to connect the devices in the above scenarios through IoT.

[0075] In this case, the Personal IoT Network (PIN) came into being. PIN can realize functions such as intelligent identification, positioning, tracking, supervision, and management of devices in the above scenarios, and can uniformly integrate the digital information between devices and items in the above scenarios, thereby enhancing the management of various devices.

[0076] The terminal devices connected to the PIN are called PIN Element (PINE) devices. Usually, the battery capacity, communication distance, signal transmission power, etc. of PINE devices are weaker than the corresponding parameters of IoT devices; moreover, the user plane traffic is usually forwarded in an environment with a small spatial capacity, so that PINE devices including smartphones and other management devices can receive notifications of events occurring in the PIN.

[0077] In practical applications, PINE devices can use various non-3GPP-based wireless technologies such as Wireless Local Area Network (WLAN), Z-Wave, Zigbee, Bluetooth, etc. to communicate within the PIN to allow users to interact and control. And because the user plane traffic generated by PINE devices is small, traditional cellular operators do not need to specifically reserve resources in the network for IoT devices, thus saving bandwidth resources. At the same time, the traffic generated by PINE devices can be stored in the devices managed by the PIN, thereby improving the convenience of traffic data management.

[0078] Figure 1A It is a schematic diagram of the PIN network architecture in 3GPP. As Figure 1A shown, PIN s1 establishes a data transmission connection with the PIN application server s3 through the 5th Generation Mobile Communication Technology Core (5G) s2; where: th Generation Mobile Communication Technology Core, 5G)s2 establishes a data transmission connection with the PIN application server s3; where:

[0079] The PEGC device can provide data connections between other PINE devices and the 5G network for them, or provide relays for data transmission between different PINE devices. In practical applications, the PEGC device passes through the 5th Generation Mobile Communication Technology Core (5 thThe AMF network element, NEF network element, Authentication Server Function (AUSF), Network Repository Function (NRF), Session Management Function (SMF) network element, Policy Control Function (PCF) network element, Unified Data Management (UDM) network element, Unified Data Repository (UDR) network element, User Plane Function (UPF) network element, and Radio Access Network (RAN) in the 5th Generation Core (5GC) s2 implement data transmission with the PIN application server s3.

[0080] Moreover, the 5GC system has a mechanism to identify PIN and PINE devices. A PIN should at least include a PIN Element with Gateway Capability (PEGC) device with gateway function and a PIN Elements with Management Capability (PEMC) device with management ability. Among them, the PEGC device can provide wireless connections for other PINE devices to enter and exit the 5G network, or provide relay for communication between PINE devices; the PEMC device manages the behavior of each PINE device and the access rights of PINE devices through the identification list of PINE devices stored in it. In practical applications, the identification list stored in the PEMC device may include the following data:

[0081] The unique identifier of the PINE device within the PIN;

[0082] The network connection types supported by the PINE device;

[0083] The identifier of the application running in the PINE device;

[0084] The metadata associated with event types, event identifiers, timestamps, etc. in the PINE device;

[0085] The security credentials of the PINE device, etc.

[0086] Figure 1B The schematic diagram of the process for registering a terminal device to the PIN is as Figure 1B shown, and this process may include the following steps:

[0087] Step A1: Send a PIN setting request.

[0088] In practical applications, the PIN Application Function (AF) 101 sends a PIN setting request to the P-Network Function (NF) 104 through the NEF 102 and the UDM 103. This request is used to create a PIN network within the 5GC, and the request contains the identification information of the selected PEMC device.

[0089] Step A2: Obtain PEMC device information.

[0090] In practical applications, after receiving the PIN setting request, the P-NF 104 sends a request to the UDM 103 to obtain the information of the selected PEMC device, in order to check whether the terminal device corresponding to the PEMC device has the PINE management function; according to the protocol regulations, only the terminal device with the PINE management function can be allowed to register as a PEMC device.

[0091] Step A3: Create a PIN to obtain a PIN identifier.

[0092] When the P-NF 104 receives that the terminal device has the PINE management ability sent by the UDM 103, if it does not request a PIN identifier from the PIN AF 101, it creates a PIN and generates a PIN identifier.

[0093] Step A4: Send a PIN creation indication message.

[0094] The UDM 103 can send the created PIN message and the PIN identifier to the PEMC device 107 through the AMF 105 and the RAN 106 at the same time.

[0095] Step A5: Discover the PEGC device and send the PIN identifier and the PEGC device identifier.

[0096] The PEMC device 107 can discover the existence of the PEGC device 108 through the Prose Discovery mechanism and establish a Prose Direct communication as the transport layer; after the transport layer is established, the PEGC device 108 sends the PIN addition request together with the PIN identifier and the PEGC device identifier to the PEMC device 107.

[0097] Step A6: Send a PEGC authentication and authorization request.

[0098] The PEMC device 107 sends an authentication authorization request for enabling the PEGC device with the PIN through the Non-Access (NAS) layer. This request contains the identity of the PEGC device, the PIN identifier, and the PEGC device identifier.

[0099] Step A7: Determine whether the PEGC device has gateway functionality.

[0100] The P-NF 104 obtains the relevant configuration parameters of the terminal device from the UDM 103 to determine whether the terminal device supports gateway functionality.

[0101] Step A8: Request to add the PEGC device identifier to the PIN identifier.

[0102] After the P-NF 104 receives the reply message from the UDM 103 confirming that the terminal device has gateway functionality, the P-NF 104 updates the PIN context and adds the PEGC device identifier to the PIN identifier.

[0103] Step A9: Send the authentication authorization result.

[0104] The P-NF 104 sends the authentication authorization result of the PEGC device 108 to the PEMC device 107 through the AMF 105.

[0105] Step A10: Send the authorization confirmation result.

[0106] The P-NF 104 sends to the PEGC device 108 that it is authorized to be the gateway device of the PIN.

[0107] The prerequisite for the above process to be executable is that the PEMC device with PINE management functionality and the PEGC device with gateway functionality have been pre-registered and passed in the 5GC.

[0108] Through the above process, the terminal device with gateway functionality can join the PIN.

[0109] On the other hand, the PIN has been widely used in scenarios such as medical, education, home, and industry. In the above scenarios, the PEMC device can manage the communication of PINE devices within a limited area. In this way, through the PEGC device, the PINE devices in the PIN can be connected to the 5GC and receive 5GC messages.

[0110] For example, in the scenario of an intelligent ward, the devices carried or worn by patients can discover each other with the devices in the intelligent ward. At this time, a 5G smartphone can be used as a PEMC device, and a 5G intelligent hospital bed in the ward can be configured as a PEGC device to build a PIN network in the intelligent ward; while the wearable devices of patients and the devices in the ward can be used as PINE devices, and the data interaction between these devices can be connected to the 5G network through the PEGC device and then transmitted to the data center device of the hospital.

[0111] For another example, in the scenario of intelligent health care, a 5G tablet or computer can be used as a PEMC device, and various types of intelligent monitoring, treatment, and rehabilitation devices such as intelligent wearable devices, intelligent blood oxygen meters, intelligent sphygmomanometers, intelligent body fat scales, and rehabilitation trainers can be used as PINE devices. The PEMC device can uniformly manage and control the above PINE devices, and a 5G terminal or gateway device can be used as a PEGC device to obtain data from the hospital server through the 5G network.

[0112] At the same time, the development of emerging technologies such as edge computing and artificial intelligence (AI) has promoted the terminal devices in various industries and application scenarios to have powerful computing capabilities. In the medical application scenario based on PIN, PINE devices including smartphones, ambulances, and robots are also increasingly using AI models to replace traditional algorithms including speech recognition, image recognition, and video processing to implement the calculation and processing of medical data.

[0113] In related technologies, PIN can at least support the following AI operation or model solutions through 5GC:

[0114] The first solution: Split the AI operation or model into multiple levels, with some levels deployed on the terminal device side and some levels deployed on the network side. The purpose of this solution is to offload the computationally intensive and energy-intensive parts of the AI model in the application scenario to the network side, while retaining the parts of the AI model for privacy-sensitive and latency-sensitive data on the terminal device side; moreover, after the operation of the AI model part on the terminal device is completed, the intermediate data obtained from the operation can be sent to the network side for the network side to perform the remaining data processing process of the AI model, and the network side can also feedback the final data processing result to the terminal device.

[0115] The second solution: Distributed AI model. This solution is a balanced solution between the diversification of AI models and the limited storage resources of PINE devices. In this solution, the AI model is not pre-loaded on the PINE device side, but is downloaded from the network side when AI calculation needs to be performed.

[0116] The third solution: AI federated learning based on 5G. In this solution, the cloud server trains a global AI model by aggregating the local models partially trained by each terminal device; and, in each training iteration, the PINE device downloads the AI model in the intermediate state from the AI server and trains the AI model in the intermediate state using local training data; after the training is completed, the PINE device sends the temporarily trained AI model to the cloud server through the 5G uplink transmission channel for the cloud server to aggregate the temporarily trained AI models from each PINE device and update the global model, and finally distribute the updated global model to the PINE device so that the PINE device can perform the next iteration training.

[0117] In the above scenario, the cloud server needs to distribute the AI model to the PINE device, and currently, each PINE device needs to establish connections with the control plane and user plane of the 5GC before it can establish a data plane transmission channel with the cloud server through the application layer to perform the download operation of the AI model. And, in actual applications, when the PINE device needs to download a large amount of data to be downloaded, it needs to perform in the above manner.

[0118] However, in the above solution, although the PINE device can obtain the data to be downloaded, the process of obtaining the data to be downloaded will increase the resource load of the signaling plane and user plane of the 5G network; and, in some scenarios, the data to be downloaded required by different PINE devices may be the same. Thus, obtaining the data to be downloaded in terms of the PINE device granularity causes a large amount of repeated transmission of the data to be downloaded in the 5G network, resulting in waste of network resources, and thus it is very easy to reduce the utilization rate of network resources, and in severe cases, it may even lead to network congestion and paralysis.

[0119] To solve the above technical problems, the embodiments of the present application provide a data acquisition method, related devices and media.

[0120] The embodiments of the present application first provide a data acquisition method for a PINE device applied to PIN.

[0121] In one implementation, the PINE device may include a mobile terminal device; exemplarily, the mobile terminal device may include a smart phone, a notebook computer, etc., and may also include movable electronic devices in scenarios such as smart wards, smart education, and smart elderly care.

[0122] Figure 2 For the flow diagram of the data acquisition method for the PINE device provided by the embodiments of the present application, as Figure 2 shown, the flow may include the following steps:

[0123] Step 201: Send a data acquisition request for the target data to the PEMC device in the PIN.

[0124] Among them, the target data is stored in at least one PEGC device in the PIN; the target data is pre-obtained from the network server by at least one PEGC device; the PEMC device is used to determine the target PEGC device from at least one PEGC device and forward the data acquisition request to the target PEGC device.

[0125] In one implementation, the target data may include at least one of video data, text data, image data, and executable file data; for example, the executable file data may include an installation target file of an application program, etc.

[0126] In one implementation, the target data may include a data module capable of implementing at least one business data processing operation; for example, the data volume of the target data may be greater than or equal to a preset threshold; for example, the above data module may implement at least one data processing algorithm; for example, the above data module may include an AI model, and correspondingly, the data acquisition request may include a module identifier of the AI model; for example, the above data module may include some levels of the AI model, and correspondingly, the data acquisition request may include a level identifier of the above partial levels.

[0127] For example, the AI model identifier may be represented by at least one of a number, a bitmap, and a string; for example, when the AI model identifier is represented by a number, "1" may represent model 1, and "3" may represent model 3; for another example, when the AI model identifier is represented by a bitmap, "0000" may represent model 1, and "0010" may represent model 2; for another example, when the AI model is represented by a string, the AI model may be "AI model 1" or "AI model 3".

[0128] For example, the above level identifier may be represented by a number, a bitmap, a string, etc.; for example, when the level identifier is represented by a number, "1, 5, 8, 17" represents the 1st, 5th, 8th, and 17th layers of the AI model; for another example, when the level identifier is represented by a bitmap, "00000000, 00000101, 00001000, 00010001" may represent the 1st, 5th, 8th, and 17th layers of the AI model; for another example, when the level identifier is represented by a string, [1-17] may represent the 1st to 17th layers of the AI model.

[0129] In one embodiment, the network server may store at least one type of target data and be capable of responding to a first request for obtaining the target data sent by the PEGC device, and sending the target data to the PEGC device; Exemplarily, the PEGC device may send the first request through the 5GC, and the network server may send the target data to the PEGC device through the 5GC.

[0130] In one embodiment, the PIN may include at least one PEGC device; Exemplarily, in the case where the PIN includes multiple PEGC devices, at least some of the multiple PEGC devices may store the target data.

[0131] In one embodiment, the PINE device may send a data acquisition request to the PEMC device through the network connection in the PIN; Exemplarily, after at least one PEGC device obtains the target data, it may send the status information of the obtained target data to the PEMC device for the PEMC device to update the device status information it manages based on the device identifier of at least one PEGC device.

[0132] In one embodiment, after the PEMC device receives the data acquisition request sent by the PINE device, it can determine the PEGC device with the lowest load status among at least one PEGC device as the target PEGC device according to the identifier of the target data requested by the PINE and the above status information in combination with the load status of at least one PEGC device; Exemplarily, if the PIN only includes one PEGC device, then this PEGC device may be the target PEGC device.

[0133] Step 202, receive the target data sent by the target PEGC device.

[0134] In one embodiment, after the target PEGC device receives the data acquisition request, it may send the target data to the PINE device when the identifier of the target data included in the data acquisition request matches the identifier of the target data it stores.

[0135] Exemplarily, the identifier of the target data may include at least one of the name, address, and number of the target data, and the embodiments of the present application do not limit this.

[0136] As can be seen from the above, in the data acquisition method applied to the PINE device provided by the embodiments of the present application, before the PINE device sends a data acquisition request to request the acquisition of target data, at least one PEGC device in the PIN pre-gets the target data from the network server. Thus, through the above operations, the unified acquisition of the target data is achieved at the PIN granularity; and by sending the target data from the target PEGC device to the PINE device, the pressure on the network resources of the 5GC caused by the PINE device frequently acquiring the target data through the 5GC can be reduced, and then the network resource utilization rate of the 5GC can be improved, and the short-distance data transmission resources in the PIN can be fully utilized; at the same time, the PINE device sends a data acquisition request to the PEMC device, and the PEMC device determines the target PEGC device from at least one PEGC device and forwards the data acquisition request to the target PEGC device, so as to achieve the isolation between at least one PEGC device and the PINE device during the operation of determining the target PEGC device, and the management capabilities of the PEMC device for the PEGC device and the PINE device can also be fully utilized, thereby improving the stability and robustness of the process of acquiring the target data.

[0137] In the case where the target data is an AI model, through the above method, the frequency of the PINE device frequently acquiring the AI model through the 5GC can be reduced, and then the burden on the 5GC network resources caused by the PINE device frequently acquiring the AI model can be reduced, thereby improving the network resource utilization rate of the 5GC and also improving the network resource utilization rate in the PIN.

[0138] Based on the foregoing embodiments, in the data acquisition method applied to the PINE device provided by the embodiments of the present application, sending a data acquisition request for requesting the acquisition of target data to the PEMC device in the PIN can be implemented through the following steps:

[0139] Step B1: Obtain the first identifier of the PINE device.

[0140] In one implementation, the first identifier may include the device number registered by the PINE device in the PIN, and may also include the device identification code of the PINE device.

[0141] In one embodiment, the first identifier may include, but is not limited to, at least one of a Mobile Station Integrated Services Digital Network (MSISDN) identifier of a PINE device, an International Mobile Subscriber Identity (IMSI), a Subscription Permanent Identifier (SUPI), an Internet Protocol (IP) address, and a Media Access Control Address (MAC).

[0142] Step B2: Generate a data acquisition request based on the first identifier.

[0143] In one embodiment, the data acquisition request can be generated in any of the following ways:

[0144] Obtain the data identifier of the target data, and fill the first identifier and the data identifier into the specified fields of the request data packet, thereby generating a data acquisition request.

[0145] Based on the target data being an AI model or executable code for implementing service processing, the service type identifier corresponding to the target data can be determined, and the service type identifier, the first identifier, and the data identifier of the target data are filled into the specified fields of the request data packet, thereby generating a data acquisition request; wherein, the service type identifier may include the type of service processing function that the target data can implement.

[0146] Exemplarily, the service type identifier can be represented by a bitmap or a string; for example, when the service type identifier is represented by a bitmap, "0000" can represent the smart ward service, "0001" can represent the emergency ambulance service, and "0010" can represent the smart health care service; for another example, when the service type identifier is represented by a string, it can be represented by "SmartWard", "Intelligent Ambulance", and "Smart Health Care", etc.

[0147] Step B3: Send the data acquisition request to the target PEMC device.

[0148] Wherein, the PEMC device is used to perform an authentication operation on the PINE device based on the first identifier, and forward the data acquisition request to the PEGC device when the result of the authentication operation is authentication passed.

[0149] Exemplarily, in the case where the authentication operation performed by the PEMC device on the PINE device based on the first identifier fails, the data acquisition request may not be sent to the target PEGC device.

[0150] In one implementation, the PEMC device may authenticate and authorize the device identity of the PINE device based on the first identifier to obtain the result of the authentication operation.

[0151] In one implementation, based on the target data being an AI model or executable code for implementing business processing, after the PEMC device authenticates and authorizes the device identity of the PINE device based on the first identifier to obtain the result of the authentication operation, it may further determine whether the service type identifier in the data acquisition request is consistent with the service type identifier of the target data stored in the target PEGC device. If the two service type identifiers are consistent, the data acquisition request is forwarded to the target PEGC device. If the two service type identifiers are inconsistent, the data acquisition request may not be forwarded to the target PEGC device, and a reply message at least including "the service type identifier of the target data requested by the PINE device is not the service type identifier supported by PIN" is replied to the PINE device, and the data acquisition request may also be forwarded to the 5GC for the PINE device to obtain the target data from the network server.

[0152] Figure 3 The flowchart of the PINE device obtaining the AI model provided by the embodiments of this application is as Figure 3 shown, and this process may include the following steps:

[0153] Step 301, Request the AI model.

[0154] Exemplarily, the PINE device 109 may send a data acquisition request for requesting the AI model to the PEMC device 107.

[0155] Step 302, Forward to the PEGC device.

[0156] Exemplarily, after the PEMC device authenticates and authorizes the device identity of the PINE device based on the first identifier to obtain the result of the authentication operation, if it is determined that the service type identifier of the AI model requested by the PINE device is the same as the service type identifier of the target data stored in the PEGC device, the data acquisition request may be forwarded to the PEGC device.

[0157] Exemplarily, the PEGC device determined by the PEMC to receive the data acquisition request may be the target PEGC device in the foregoing embodiments.

[0158] Step 303, Send the AI model to the PINE device.

[0159] Exemplarily, after the target PEGC device obtains a data forwarding request, it can send the AI model to the PINE device based on the first identifier.

[0160] As can be seen from the above, in the data acquisition method applied to the PINE device provided by the embodiments of the present application, the PINE device obtains the first identifier of the PINE device, generates and sends a data acquisition request to the PEMC device based on the first identifier, so that the PEMC device can perform an authentication operation on the PINE device based on the first identifier, and forward the data acquisition request to the target PEGC device when the result of the authentication operation is successful authentication. In this way, through the above operations, the security of the operation of the PINE device to obtain target data can be improved, and the risk probability of the data resources in the PIN caused by any device in the PEMC device and the target PEGC device responding to the data acquisition request sent by the PIN can be reduced.

[0161] Based on the foregoing embodiments, in the data acquisition method applied to the PINE device provided by the embodiments of the present application, the network server includes an AF device.

[0162] In one implementation, the AF device may include a server device storing at least one type of target data; exemplarily, the AF device may include a physical machine device or a virtual machine device; exemplarily, the AF device may be a PIN-AF.

[0163] Correspondingly, in the data acquisition method applied to the PINE device provided by the embodiments of the present application, before sending a data acquisition request for requesting to obtain target data to the PEMC device in the PINE, the following operations may also be performed:

[0164] Obtain the broadcast message sent by the PEMC device.

[0165] Among them, the broadcast message is used to indicate that at least one PEGC device has obtained the target data from the AF device.

[0166] In one implementation, the broadcast message may include an identifier list of the PEGC device carrying the target data, and may also include a service type identifier corresponding to the target data carried by each PEGC device.

[0167] In one implementation, the identifier of the PEGC device may include at least one of MSISDN, IMSI, IP address, and MAC address.

[0168] In one implementation, after the PEMC device receives the status information sent by at least one PEGC device indicating that it has obtained the target data, it may generate the above status information based on the service type identifier of the target data and the device identifier of at least one PEGC device storing the target data.

[0169] In one implementation, the broadcast information may include indication information that at least one PEGC device in the PIN to which the PEMC device belongs has obtained the target data.

[0170] Figure 4 The flowchart shows the process of the PEMC device provided by the embodiment of the present application for sending broadcast information. It should be noted that in Figure 4 , the process of sending the broadcast message is described by taking the target data as an AI model as an example. As Figure 4 shown, the process may include the following steps:

[0171] Step 401: Send a second request to obtain the address of the AI model.

[0172] Exemplarily, the PEMC device may send a second request to the AMF 105 to request to obtain the address of the AI model.

[0173] Exemplarily, the PEMC device may determine the service type identifier based on the service processing requirements of the PINE device or at least one PEGC device it manages, and may also determine the service type identifier in response to the user's input operation, and generate a second request based on the service type identifier.

[0174] Exemplarily, the second request may further include a third identifier of the PEMC device and a second identifier of at least one PEGC device.

[0175] Exemplarily, the third identifier may include at least one of MSISDN, IMSI, IP address, and MAC address.

[0176] Step 402: Send a third request to obtain the subscribed service type of the PEMC device.

[0177] Exemplarily, after receiving the second request, the AMF 105 may send a third request to the UDM 103 to request to obtain the service type identifier subscribed in advance by the PEMC device 107 based on the third identifier carried in the second request.

[0178] Exemplarily, the third request may include the third identifier of the PEMC device 107.

[0179] Exemplarily, after receiving the third request, the UDM 103 may determine the service type identifier subscribed in advance by the PEMC device 107 that it stores based on the third identifier, and send the service type identifier to the AMF 105.

[0180] Exemplarily, if the service type identifier sent by the UDM 103 is the same as the service type identifier carried in the second request, the AMF 105 executes step 403; otherwise, if the two service type identifiers are different, step 403 may not be executed, and a reply message containing at least the "unsigned service type identifier" is returned to the PEMC device 107.

[0181] Step 403: Request to obtain the AI model.

[0182] Exemplarily, the AMF 105 sends a request to obtain the AI model to the AF 110 through the NEF 102.

[0183] Step 404: Send the address of the AI model to the PEGC device.

[0184] Exemplarily, after receiving the request to obtain the AI model, the AF 110 can obtain the third identifier of the PEMC device from the request and determine the address of the AI model pre-signed by the PEMC device based on the third identifier; the AF 110 can be the AF device in the foregoing embodiments.

[0185] Exemplarily, the AF 110 can trigger the Nnef_ParameterProvision_Update service and send the address of the AI model to at least one PEGC device in the PIN based on the second identifier of the PEGC device through the parameter configuration update process; the configuration parameters in the parameter configuration update process can include the data shown in Table 1.

[0186] Among them, the PEGC ID can be the second identifier of at least one PEGC device.

[0187] Table 1

[0188] Configuration parameters [PEGC ID, Address of the AI model]

[0189] Step 405: Send a notification message.

[0190] Exemplarily, the PEGC device can send a notification message to the PEMC device.

[0191] Exemplarily, after receiving the address of the AI model, the PEGC device can download and save the AI model based on the address of the AI model, and then send a notification message of "AI model download completed" to the PEMC.

[0192] Step 406: Send a broadcast message.

[0193] Exemplarily, after receiving the notification message, the PEMC device may generate and send a broadcast message to the PINE device 109 in the PIN, so that the PINE device 109 can send a data acquisition request to the PEMC device when it needs to obtain the AI model.

[0194] Exemplarily, the above broadcast message may include indication information that the AI model associated with the service type identifier subscribed by the PEMC device has been successfully downloaded to the PEGC device.

[0195] As can be seen from the above, in the data acquisition method applied to the PINE device provided in the embodiment of the present application, the network server includes an AF device. In this way, through the converged network architecture between the AF device and the 5GC, at least one PEGC pre-obtains the target data from the AF device, thereby improving the stability and flexibility of target data acquisition; and, before the PINE device sends a data acquisition request, the PEMC device first sends a broadcast message indicating that at least one PEGC device has obtained the target data from the AF device, realizing the synchronization of the state information that at least one PEGC device has obtained the target data among the devices in the PIN, thereby improving the stability of the PINE device to obtain the target data from the target PEGC device.

[0196] Based on the foregoing embodiments, the embodiment of the present application further provides a data acquisition method applied to a target PEGC device in the PIN. Figure 5 It is a schematic flowchart of the data acquisition method applied to the target PEGC device provided in the embodiment of the present application. As Figure 5 shown, the process may include the following steps:

[0197] Step 501, receive a data acquisition request for requesting to obtain target data sent by the PEMC device in the PIN.

[0198] Among them, the target PEGC device is determined by the PEMC device from at least one PEGC device included in the PIN; at least one PEGC device stores at least the target data pre-obtained from the network server; the data acquisition request is sent by the PINE device in the PIN to the PEMC device.

[0199] Step 502, send the target data to the PINE device.

[0200] As can be seen from the above, in the data acquisition method applied to the target PEGC device provided by the embodiments of the present application, the target data pre-acquired from the network server is stored in the target PEGC device, and the target PEGC device can receive a data acquisition request for requesting to acquire the target data sent by the PEMC device in the PIN, and send the target data to the PINE device. In this way, through the above operations, the PINE device in the PIN can acquire the target data from the PEGC device in the PIN, thereby reducing the waste of network resources caused by the PINE device frequently acquiring the target data from the network side through the 5GC; moreover, by at least one PEGC device pre-acquiring the target data from the network server, a new process for acquiring the target data from the network server at the PIN granularity is provided; at the same time, the PINE device in the PIN can acquire the target data from the target PEGC device, thereby making full use of the network resources of the PIN and improving the acquisition efficiency of the target data.

[0201] Based on the foregoing embodiments, in the data acquisition method applied to the target PEGC device provided by the embodiments of the present application, the network server includes an AF device.

[0202] Correspondingly, before sending the target data to the PINE device, the following operations may further be performed:

[0203] Receive a first address sent by the AF device; acquire the target data from the AF device based on the first address.

[0204] Wherein, the first address includes the storage address of the target data.

[0205] In one implementation manner, the first address may include the storage address of the target data in the AF device; exemplarily, the first address may be embodied by a Uniform Resource Locator (URL).

[0206] In one implementation manner, at least one PEGC device including the target PEGC device may send an address acquisition request to the PEMC device, and the PEMC device sends the address acquisition request to the AF device; exemplarily, the PEMC device may send the address acquisition request to the AF device through network elements such as the AMF in the 5GC; exemplarily, the address acquisition request may include a request for requesting the address of the target data.

[0207] In one implementation manner, when the target data is an AI model, the address of the AI model may be acquired through the process provided in the foregoing embodiments.

[0208] As can be seen from the above, in the data acquisition method applied to the target PEGC device provided by the embodiments of the present application, before the target PEGC device sends the target data to the PINE device, it first receives the first address indicating the storage address of the target data sent by the AF device, and obtains the target data from the AF device based on the first address. In this way, through the above operations, the stability of the target PEGC device providing the target data for the PINE device can be improved.

[0209] Based on the foregoing embodiments, in the data acquisition method applied to the target PEGC device provided by the embodiments of the present application, after obtaining the target data from the AF device based on the first address, the following steps may further be included:

[0210] Send the status information that the target PEGC device has obtained the target data to the PEMC device, so that the PEMC device can send a broadcast message to the PINE device based on the status information.

[0211] Wherein, the broadcast message is used to indicate that the target PEGC device has obtained the target data from the AF device.

[0212] In one implementation manner, at least one PEGC device may send the status information to the PEMC device, and the broadcast message may indicate that at least one PEGC device has obtained the target data.

[0213] In one implementation manner, the above status information may include information such as the service type identifier of the target data, the storage address of the target data, and the acquisition time of the target data.

[0214] As can be seen from the above, in the data acquisition method applied to the target PEGC device provided by the embodiments of the present application, after the target PEGC device obtains the target data, it sends the status information that it has obtained the target data to the PEMC device, and the PEMC device sends the indication information that the target PEGC device has obtained the target data to the PINE device. In this way, through the above process, the synchronization of the state that the target PEGC device has obtained the target data among the target PEGC device, the PEMC device, and the PINE device is realized.

[0215] Based on the foregoing embodiments, the data acquisition method applied to the target PEGC device provided by the embodiments of the present application may further include the following steps:

[0216] Receive a data update message for indicating the update of the target data, and update the target data based on the second address included in the data update message.

[0217] Wherein, the second address includes the storage address of the updated target data.

[0218] In one embodiment, the data update message may include information such as the time of the target data update, the storage address of the updated target data, the similarities and differences between the updated target data and the target data, and the advantages of the updated target data in terms of service processing, etc.

[0219] In one embodiment, at least one PEGC device including the target PEGC device may obtain a data update message from a 5GC network element.

[0220] In one embodiment, at least one PEGC device including the target PEGC device may download the updated target data from the storage address indicated by the second address, so as to update the target data.

[0221] In one embodiment, after at least one PEGC device including the target PEGC device updates the target data, an update message of the target data update may also be sent to the PEMC device, so that the PEMC device can send a broadcast message indicating that the target data has been updated to the PINE device in the PIN, thereby realizing the synchronization of the update status of the target data among at least one PEGC device, the PEMC device, and the PINE device.

[0222] In the case where the target data is an AI model, in the related art, the PINE device needs to update the AI model by pre-installing a customized application, loading a specified applet, or obtaining the server URL of the AI model in advance and accessing it through a browser. Obviously, the above-mentioned update operation of the AI model is inefficient and the operation process is cumbersome; moreover, when the server address of the AI model is updated or the AI model is updated, it is also difficult for the PINE device to obtain it in real time, resulting in the PINE device being unable to obtain the updated AI model in real time.

[0223] However, in the data acquisition method applied to the target PEGC device provided by the embodiments of the present application, the target PEGC device can receive a data update message for indicating the update of the target data, and update the target data based on the second address included in the data update message. In this way, through the above process, the PINE device in the PIN does not need to participate in the target data update process, but only needs to obtain the updated target data from the PINE device when it needs to obtain the target data, thereby simplifying the operation process of the PINE device for updating the target data; moreover, through the above operation, the update operation of the target data at the PIN granularity is realized, thereby reducing the pressure on network resources generated by the PINE device performing the update operation of the target data.

[0224] Based on the foregoing embodiments, in the data acquisition method applied to the target PEGC device provided by the embodiments of the present application, the network server includes an AF device.

[0225] Correspondingly, receiving a data update message for indicating the update of target data can be implemented in the following ways:

[0226] Receive a data update message from the AMF network element.

[0227] Among them, the data update message is sent from the AF device to the AMF network element via the NEF network element.

[0228] Taking the target data as an AI model as an example, Figure 6 This is a schematic diagram of the synchronization process of the update status of the AI model provided by the embodiment of the present application. As Figure 6 shown, this process may include the following steps:

[0229] Step 601, send an update notification.

[0230] Exemplarily, when AF 110 detects an update of the AI model, it can send an update notification to NEF 102 to indicate the update status of the AI model; exemplarily, the update configuration information carried in the above update notification includes, but is not limited to, the second identifier of at least one PEGC device and the storage address of the updated AI model, that is, the second address.

[0231] Exemplarily, after at least one PEGC device establishes an AI model transfer link with the AF, it can obtain the AI model; exemplarily, since at least one PEGC device cannot know in real time whether the AF updates the AI model on its side, therefore, an update notification of the AI model can be sent by the AF for managing the AI model.

[0232] Step 602, forward the update notification.

[0233] Exemplarily, after receiving the update notification message sent by the AF, the NEF updates the configuration information of the AF, and queries the AMF associated with the second identifier according to the second identifier of at least one PEGC device, and then forwards the update notification to the above AMF.

[0234] Step 603, forward the update notification to the PEGC device.

[0235] Exemplarily, after receiving the update notification, AMF 105 can forward the update notification message to at least one PEGC device according to the second identifier of the PEGC device.

[0236] Exemplarily, after receiving the update notification, at least one PEGC device can decide whether to download the updated AI model according to its own status.

[0237] As can be seen from the above, in the data acquisition method for the target PEGC device provided by the embodiments of the present application, when the network server includes an AF device, the PEGC device receives a data update message from the AMF network element, and the data update message is sent by the AF device to the AMF network element via the NEF network element. In this way, through the above process, on the basis of making full use of the data transmission architecture between the network elements in the 5GC and at least one PEGC device including the target PEGC device, the efficient and stable transmission of the data update message is achieved; moreover, in the above process, at least one PEGC device and the PINE device do not need to actively obtain the data update message, but the network elements in the 5GC trigger the active sending of the data update message, so as to simplify the process for the devices in the PIN to obtain the data update message.

[0238] Based on the foregoing embodiments, the embodiments of the present application further provide a data acquisition method for a PEMC device applied to a PIN. Figure 7 It is a schematic flowchart of the data acquisition method for a PEMC device provided by the embodiments of the present application. As Figure 7 shown, the method may include the following steps:

[0239] Step 701, receive a data acquisition request for requesting to obtain target data sent by a PINE device in the PIN.

[0240] Step 702, determine a target PEGC device from at least one PEGC device included in the PIN.

[0241] Among them, the target data pre-obtained from the network server is stored in at least one PEGC device.

[0242] In one implementation manner, the PIN may include at least one PEGC device; exemplarily, the target data may be stored in at least some of the PEGC devices in the PIN.

[0243] In one implementation manner, the PEMC device may determine the target PEGC device according to the status message it pre-receives.

[0244] Step 703, forward the data acquisition request to the target PEGC device for the target PEGC device to send the target data to the PINE device.

[0245] As can be seen from the above, in the data acquisition method applied to the PEMC device provided by the embodiment of the present application, after the PEMC device receives a data acquisition request, it can determine a target PEGC device from at least one PEGC device, and the at least one PEGC device stores target data previously obtained from a network server, and forwards the data acquisition request to the target PEGC device for the target PEGC device to send the target data to the PINE device. In this way, in the above process, by pre-obtaining the target data from the network server by at least one PEGC device, the target data is obtained from the network server at the PIN granularity, thereby reducing the resource waste caused by the PINE device obtaining the target data from the network server; and, by the PEMC device forwarding the data acquisition request and the target PEGC device sending the target data to the PINE device, the network resources in the PIN can be fully utilized, and the network resource utilization rate in the PIN can be improved.

[0246] Based on the foregoing embodiment, in the data acquisition method applied to the PEMC device provided by the embodiment of the present application, before receiving a data acquisition request for requesting to obtain target data sent by a PINE device in a PIN, the following operations may further be performed:

[0247] Receive status information that at least one PEGC device has obtained target data; generate a broadcast message based on the status information; and send the broadcast message to the PINE device in the PIN.

[0248] Wherein, the broadcast message is used to indicate that at least one PEGC device has obtained the target data from the network server.

[0249] As can be seen from the above, in the data acquisition method applied to the PEMC device provided by the embodiment of the present application, after the PEMC device receives the status information that at least one PEGC device has obtained the target data, it generates a broadcast message based on the status information for indicating that at least one PEGC device has obtained the target data from the network server, and sends the broadcast message to the PINE device in the PIN. In this way, through the above operations, the synchronization of the status that the PEGC device, the PEMC device, and the PINE device in the PIN have obtained the target data from the network server is realized, thereby improving the efficiency of the subsequent PEMC device to determine the PEGC device storing the target data and the PINE device to obtain the target data.

[0250] Based on the foregoing embodiment, in the data acquisition method applied to the PEMC device provided by the embodiment of the present application, the network server includes an AF device.

[0251] Correspondingly, before receiving a data acquisition request for requesting to obtain target data sent by a PINE device in a PIN, the following operations may further be performed:

[0252] Send an address acquisition request to the AF device for the AF device to determine a first address storing target data and send the first address to at least one PEGC device.

[0253] Wherein, the first address is used for the PEGC device to acquire target data.

[0254] In one implementation, the above address acquisition request can be automatically generated by the PEMC device, or can be generated by the PEMC device in response to a user instruction, or can also be generated by the PEMC device in response to a request from at least one PEGC device to request an address for acquiring target data. The embodiments of the present application do not make any limitation thereto.

[0255] As can be seen from the above, in the data acquisition method applied to the PEMC device provided by the embodiments of the present application, before the PEMC device receives a data acquisition request for requesting target data sent by the PINE device, an address acquisition request is first sent to the AF device for the AF device to determine a first address storing target data and send the first address to at least one PEGC device for at least one PEGC device to acquire target data based on the first address. Thus, through the above operations, the management role of the PEMC device in the PIN is fully utilized, and the control of whether at least one PEGC device acquires target data by the PEMC device is realized.

[0256] Based on the foregoing embodiments, in the data acquisition method applied to the PEMC device provided by the embodiments of the present application, sending an address acquisition request to the AF device can be implemented in the following manner:

[0257] Obtain a first service parameter; generate an address acquisition request based on the first service parameter; send the address acquisition request to the AMF network element for the AMF network element to determine, based on a second service parameter and the first service parameter, to forward the address acquisition request to the AF device via the NEF network element.

[0258] Wherein, the first service parameter includes at least a service type; the first service parameter is associated with the PEMC device; the second service parameter includes service parameters stored in the UDM network element and associated with the AF device.

[0259] In one implementation, the service type can be reflected by the service type identifier in the foregoing embodiments.

[0260] In one implementation, the service type may include the type of service data that the PEMC device can or expects to implement or the type of service processing operation.

[0261] In one embodiment, the first service parameter can be stored in the storage space of the PEMC device or in the network element of the 5GC.

[0262] In one embodiment, the first service parameter can be determined by the PEMC device in response to a user input operation.

[0263] In one embodiment, the first service parameter can include at least one service type.

[0264] In one embodiment, the first service parameter can be added to a specified position of the request data packet to generate an address acquisition request.

[0265] In one embodiment, the second service parameter can include a set of service types pre-set or configured by the AF device for the PEMC device; exemplarily, the second service parameter can be pre-set for the PEMC device by a network element in the 5GC and stored in the UDM network element.

[0266] In one embodiment, after receiving the address acquisition request, the AMF network element can parse the address acquisition request to obtain the first service parameter, and can also determine whether to send the address acquisition request to the NEF network element based on the matching degree between the first service parameter and the second service parameter, for the NEF network element to send the address acquisition request to the AF device; exemplarily, if the first service parameter matches the second service parameter, the address acquisition request is sent to the NEF network element, and if the first service parameter does not match the second service parameter, the address acquisition request may not be sent to the NEF network element, and at the same time, a reply message indicating that the first service parameter does not match the second service parameter is sent to the PEMC device.

[0267] As can be seen from the above, in the data acquisition method applied to the PEMC device provided by the embodiments of the present application, after obtaining the first service parameter including at least the service type, an address acquisition request is generated based on the first service parameter and sent to the AMF network element, for the AMF network element to determine, based on the second service parameter and the first service parameter, to forward the address acquisition request to the AF device via the NEF network element, and the second service parameter includes the service parameters associated with the PEMC device stored in the UDM network element. In this way, through the above operations, it is possible to realize the transparent transmission of the address acquisition request between the PEMC device and the AF device on the basis of making full use of the data transmission architecture in the 5GC, thereby improving the stability of the address acquisition request transmission; and, since the AMF network element determines to forward the address acquisition request to the AF device via the NEF network element based on the second service parameter and the first service parameter, the security of the address acquisition request forwarding can be improved.

[0268] Based on the foregoing embodiments, in the data acquisition method applied to PEMC devices provided in the embodiments of the present application, the first service parameter is determined by the Operation Support Systems (OSS) network element and sent to the UDM network element.

[0269] Figure 8 FIG. is a schematic flowchart of setting a subscribed service type for a PEMC device provided in the embodiments of the present application. As Figure 8 shown, the process may include the following steps:

[0270] Step 801, configure the subscribed service type of the PEMC device.

[0271] Exemplarily, the subscribed service type may include the type of service processing process that the PEMC device can implement or the type of service data that the PEMC device can process.

[0272] Exemplarily, the subscribed service type may be the first service parameter in the foregoing embodiments.

[0273] Exemplarily, the operator configures the subscribed service type of the PEMC device through OSS111 and sends the subscribed service type to the UDM.

[0274] Exemplarily, the OSS may send the subscribed service type to the UDM in the form of configuration information.

[0275] Exemplarily, the configuration information may be as shown in Table 2, where the PEMC ID may be the third identifier of the PEMC device.

[0276] Table 2

[0277] Subscription service types of the PEMC device [PEMC ID, Service type identifier]

[0278] Exemplarily, the subscribed service type may include at least one of smart ward, body area network, smart home, smart elderly care, and smart education.

[0279] Step 802, send the subscribed service type to the UDM.

[0280] Exemplarily, after receiving the configuration information, the UDM may obtain the third identifier and the subscribed service type of the PEMC from the configuration information, and update or set the configuration information of the PEMC device it manages based on the above information.

[0281] As can be seen from the above, in the data acquisition method applied to PEMC devices provided in the embodiments of the present application, the first service parameter is determined by the OSS network element and sent to the UDM network element. In this way, the control of the operation of setting the first service parameter through the OSS is realized, and moreover, through the above setting method, the flexibility of the operation of setting the first service parameter can be improved.

[0282] Based on the foregoing embodiments, in the data acquisition method applied to the PEMC device provided by the embodiments of the present application, the second service parameter includes a service type identifier of at least one service; the service type identifier is sent by the AF device to the Network Repository Function (NRF) network element through the NEF network element.

[0283] In one implementation, the second service parameter may be a set of service type identifiers determined by the AF device and associated with the PEMC device.

[0284] In one implementation, the second service parameter may include a set of service type identifiers associated with the target data that the AF device associated with the PEMC device can provide.

[0285] Figure 9 It is a schematic diagram of the AF registration process provided by the embodiments of the present application. As Figure 9 shown, this process may include the following steps:

[0286] Step 901, send a registration request.

[0287] Exemplarily, the AF may send a registration request to the NRF 112 through the Nnrf_NFManagement_NFRegister service.

[0288] Exemplarily, the above registration request may include a service registration request that the AF can send to the NEF 102; Exemplarily, the service registration request may include parameters such as the identifier of the AF, the service type identifier corresponding to the AI model that the AF can provide, the service provider identifier of the AI model, etc., and the identifier of the PEMC device associated with the above service type identifier.

[0289] Exemplarily, the identifier of the AF may include at least one of a Generic Public Subscription Identifier (GPSI), MSISDN, IMSI, IP address, and MAC address.

[0290] Exemplarily, the service type identifier corresponding to the AI model that the AF can provide may be the second service parameter in the foregoing embodiments.

[0291] Exemplarily, the above service provider identifier can be represented by numbers, bitmaps, strings, etc.; for example, when using numbers to represent the service provider identifier, "1" can represent AI service provider A, and "2" can represent AI service provider B; for another example, when using bitmaps to represent the service provider identifier, "0000" can represent AI service provider A, and "0001" can represent AI service provider B; for still another example, when using strings to represent the service provider identifier, the service provider identifier can be "AI server 1" or "AI server 2".

[0292] Step 902: Verify AF.

[0293] Exemplarily, after receiving the registration request, NEF 102 can obtain the identifier of AF from the registration request and verify whether AF is authorized by the 5GC based on the identifier of AF. If AF is authorized by the 5GC, step 903 is executed. If AF is not authorized by the 5GC, a reply message at least including "Unauthorized, cannot be registered" is returned to AF.

[0294] Step 903: Forward the registration request.

[0295] Exemplarily, NEF can forward the registration request to NRF 112.

[0296] Step 904: Update the configuration file.

[0297] Exemplarily, after receiving the registration request forwarded by NEF, NRF 112 can parse the registration request to obtain parameters including the identifier of AF, the service type identifier corresponding to the AI model that AF can provide, and the service provider identifier of the AI model, etc., and update the configuration files related to the AF device and the PEMC device based on the above parameters, and at the same time mark the target data or AI model provided by AF and its corresponding service as available status.

[0298] Step 905: Return the registration request response result.

[0299] Exemplarily, NRF 112 can return a registration request response result indicating that the registration request has been accepted to AF.

[0300] As can be seen from the above, in the data acquisition method applied to the PEMC device provided by the embodiment of the present application, the second service parameter includes the service type identifier of at least one service, and the service type identifier is sent by the AF device to the NRF network element through the NEF network element. In this way, by pre-setting the second service parameter by the AF device, conditions are provided for the AMF network element to determine whether to forward the address acquisition request to the AF device when the PEMC device sends an address acquisition request; moreover, by setting the second service parameter by the AF device, the accuracy of the second service parameter can be improved.

[0301] Based on the foregoing embodiments, in the data acquisition method applied to the PEMC device provided by the embodiment of the present application, sending an address acquisition request to the AF device can be implemented in the following manner:

[0302] Obtain the second identifier of at least one PEGC device; generate an address acquisition request based on the second identifier; send the address acquisition request to the AF device for the AF device to send the first address to at least one PEGC device based on the second identifier.

[0303] In one implementation, the PEMC device can obtain the second identifier of at least one PEGC device based on the device identifier list it manages; exemplarily, the above identifier list may include the PINE device in the PIN where the PEMC device is located and the set of identifiers of at least one PEGC device.

[0304] In one implementation, after receiving the data acquisition request, the AF device can parse the data acquisition request to obtain the second identifier, and send the first address to at least one PEGC device based on the second identifier.

[0305] As can be seen from the above, in the data acquisition method applied to the PEMC device provided by the embodiment of the present application, the PEMC device obtains the second identifier of at least one PEGC device, generates an address acquisition request based on the second identifier, and then sends the address acquisition request to the AF device for the AF device to send the first address to at least one PEGC device based on the second identifier. In this way, through the above operations, the efficiency of at least one PEGC device to obtain the first address can be improved.

[0306] Based on the foregoing embodiments, in the data acquisition method applied to the PEMC device provided by the embodiment of the present application, determining the target PEGC device from at least one PEGC device included in the PIN can be implemented in the following manner:

[0307] Determine the first identifier of the PINE device based on the data acquisition request; perform an authentication operation on the PINE device based on the first identifier to obtain an authentication result; if the authentication result indicates that the PINE device passes the authentication, determine the target PEGC device from at least one PEGC device.

[0308] Exemplarily, if the authentication result indicates that the PINE device fails the authentication, the operation of determining the target PEGC device may not be performed.

[0309] In one implementation, the data acquisition request may carry a first identifier. In this way, the PEMC device can obtain the first identifier by parsing the data acquisition request.

[0310] As can be seen from the above, in the data acquisition method applied to the PEMC device provided by the embodiments of the present application, after the PEMC device receives the data acquisition request, it first determines the first identifier of the PINE device that sends the data acquisition request, and performs an authentication operation on the PINE device based on the first identifier to obtain an authentication result. And when the authentication result indicates that the PINE device passes the authentication, a target PEGC device is determined from at least one PEGC device. In this way, through the above operations, the control of the operation of determining the target PEGC device is realized, thereby improving the security of the process of the PINE device sending a data acquisition request and obtaining target data in the PIN.

[0311] Figure 10 It is a schematic flow diagram of obtaining an AI model provided by the embodiments of the present application, as Figure 10 shown, this process may include the following steps:

[0312] Step 1001, configure the subscribed service type of the PEMC device.

[0313] Exemplarily, the subscribed service type of the PEMC device may be configured through the OSS, and the service type identifier corresponding to the subscribed service type is determined. Then, the UDM configures the above service type identifier in the configuration file based on the identifier of the PEMC device or the identifier of the PIN.

[0314] Exemplarily, the subscribed service type of the PEMC device may be the first service parameter in the foregoing embodiments.

[0315] Step 1002, the AF sends a registration application to the 5GC.

[0316] Exemplarily, through the method provided by the foregoing embodiments, the service type identifier of the service type provided by the AF, that is, the second service parameter, may be registered through the NRF network element.

[0317] Exemplarily, the order of step 1001 and step 1002 may be adjusted, or they may be performed in parallel. The embodiments of the present application do not limit this.

[0318] Step 1003, the PEMC device sends an address acquisition request to the AF.

[0319] Exemplarily, the PEMC device may send an address acquisition request to the AF through the 5GC 1001 to request the storage address of the AI model, i.e., the first address; Exemplarily, the AF may send the first address to the PEGC device in the PIN to which the PEMC device belongs; Exemplarily, the above PEGC device may be specified in the address acquisition request.

[0320] Step 1004, the PINE device sends a data acquisition request to the PEMC device.

[0321] Exemplarily, the PINE device may send a data acquisition request for the AI model to be acquired to the PEMC device. The PEMC device determines the PEGC device storing the AI model and forwards the above data acquisition request to the PEGC device, and then the PEGC device sends the AI model to the PINE device.

[0322] Step 1005, the AF sends an AI model update notification to the PEGC device.

[0323] Exemplarily, if the AF updates the AI model, it may send an AI model update notification to at least one PEGC device for at least one PEGC device to obtain the updated AI model.

[0324] In the above process, through the mutual cooperation of the 5GC, the PEGC device in the PIN, the PEMC device, and the AF, the acquisition and update of the AI model from the AF with the PIN as the granularity are realized, so that the waste of network resources caused by the frequent acquisition of the AI model by the PINE device in the PIN can be reduced, and the network resources of the PIN can be fully utilized.

[0325] In practical applications, with the sharp increase in Internet of Things devices, the management requirements for Internet of Things devices in various scenarios have emerged as the times require; at the same time, the application of PIN in application scenarios such as medical care, education, home, and industry has also put forward new requirements for the sinking management of terminal devices. On the other hand, with the development of technologies such as AI, edge computing, and cloud computing, it has promoted terminal devices to be combined with the above various technologies to improve their computing power, so that they can perform business computing, analysis, and processing in diverse scenarios, resulting in the sinking of AI models becoming an inevitable trend. Under the condition that the target data is an AI model, the data acquisition method provided by the embodiments of the present application can improve the efficiency of the PINE device in the PIN to obtain the AI model under the condition of reducing the network resource occupancy rate of the 5GC, thus laying a foundation for improving the operation efficiency of the PINE device.

[0326] Based on the foregoing embodiments, the embodiments of the present application further provide a PINE device, Figure 11 which is a schematic structural diagram of the PINE device provided by the embodiments of the present application, as Figure 11As shown, the PINE device 109 may include a first processor 1101 and a first memory 1102; wherein, a first computer program is stored in the first memory 1102, and when the first computer program is executed by the first processor 1101, it can implement the data acquisition method applied to the PINE device as described in any of the previous paragraphs.

[0327] Based on the foregoing embodiments, the embodiments of the present application further provide another PINE device, which may include:

[0328] A first transceiver module, configured to send a data acquisition request for requesting to acquire target data to the PEMC device in the PIN; wherein, the target data is stored in at least one PEGC device of the PIN; the target data is pre-acquired from a network server by at least one PEGC device; the PEMC device is configured to determine a target PEGC device from at least one PEGC device and forward the data acquisition request to the target PEGC device;

[0329] The first transceiver module is further configured to receive the target data sent by the target PEGC device.

[0330] In some embodiments, the PINE device further includes a first acquisition module and a first processing module; wherein:

[0331] The first acquisition module is configured to acquire a first identifier of the PINE device;

[0332] The first processing module is configured to generate a data acquisition request based on the first identifier;

[0333] The first transceiver module is configured to send the data acquisition request to the PEMC device; wherein, the PEMC device is configured to perform an authentication operation on the PINE device based on the first identifier, and in the case that the result of the authentication operation is authentication passed, forward the data acquisition request to the target PEGC device.

[0334] In some embodiments, the network server includes an AF device;

[0335] The first transceiver module is configured to receive a broadcast message sent by the PEMC device; wherein, the broadcast message is used to indicate that at least one PEGC device has acquired the target data from the AF device.

[0336] Based on the foregoing embodiments, the embodiments of the present application further provide a target PEGC device Figure 12 is a schematic structural diagram of the target PEGC device provided by the embodiments of the present application, as Figure 12As shown, the target PEGC device 12 may include a second processor 1201 and a second memory 1202; wherein, a second computer program is stored in the second memory 1202, and when the second computer program is executed by the second processor 1201, it can implement the data acquisition method applied to the PEGC device as described in any of the previous paragraphs.

[0337] Based on the foregoing embodiments, an embodiment of the present application further provides a target PEGC device, including:

[0338] A second transceiver module, configured to receive a data acquisition request for requesting to acquire target data sent by a PEMC device in the PIN; wherein, the target PEGC device is determined by the PEMC device from at least one PEGC device included in the PIN; at least one PEGC device stores at least the target data pre-acquired from a network server; the data acquisition request is sent by a PINE device in the PIN to the PEMC device;

[0339] The second transceiver module is further configured to send the target data to the PINE device.

[0340] In some embodiments, the network server includes an AF device;

[0341] The second transceiver module is configured to receive a first address sent by the AF device; wherein, the first address includes the storage address of the target data;

[0342] The second transceiver module is further configured to acquire the target data from the AF device based on the first address.

[0343] In some embodiments, the second transceiver module is configured to send the status information that the target PEGC device has acquired the target data to the PEMC device, so that the PEMC device can send a broadcast message to the PINE device based on the status information; wherein, the broadcast message is used to indicate that the target PEGC device has acquired the target data from the AF device.

[0344] In some embodiments, the second transceiver module is configured to receive a data update message for indicating the update of the target data; update the target data based on a second address included in the data update message; wherein, the second address includes the storage address of the updated target data.

[0345] In some embodiments, the second transceiver module is configured to receive a data update message from an AMF network element; wherein, the data update message is sent by the AF device to the AMF network element via the NEF network element.

[0346] Based on the foregoing embodiments, an embodiment of the present application further provides a PEMC device Figure 13 is a schematic structural diagram of the PEMC device provided by an embodiment of the present application, as Figure 13As shown, the PEMC device 107 may include a third processor 1301 and a third memory 1302; wherein, a third computer program is stored in the third memory 1302, and when the third computer program is executed by the third processor 1301, it can implement the data acquisition method applied to the PEMC device as described in any of the previous paragraphs.

[0347] Based on the foregoing embodiments, the embodiments of the present application further provide another PEMC device, including:

[0348] A third transceiver module, configured to receive a data acquisition request for requesting to acquire target data sent by a PINE device in the PIN;

[0349] A second processing module, configured to determine a target PEGC device from at least one PEGC device included in the PIN; wherein, the target data pre-acquired from a network server is stored in at least one PEGC device;

[0350] A third transceiver module, configured to forward the data acquisition request to the target PEGC device for the target PEGC device to send the target data to the PINE device.

[0351] In some embodiments, the third transceiver module is configured to receive status information that at least one PEGC device has acquired the target data;

[0352] A second processing module, configured to generate a broadcast message based on the status information; wherein, the broadcast message is used to indicate that at least one PEGC device has acquired the target data from the network server;

[0353] A third transceiver module, configured to send the broadcast message to the PINE device in the PIN.

[0354] In some embodiments, the network server includes an AF device;

[0355] A third transceiver module, configured to send an address acquisition request to the AF device for the AF device to determine a first address where the target data is stored and send the first address to the PEGC device; wherein, the first address is used for the PEGC device to acquire the target data.

[0356] In some embodiments, the PEMC device further includes a second acquisition module, configured to acquire a first service parameter; wherein, the first service parameter at least includes a service type; the first service parameter is associated with the PEMC device;

[0357] A second processing module, configured to generate an address acquisition request based on the first service parameter;

[0358] A third transceiver module, configured to send an address acquisition request to an AMF network element, so that the AMF network element determines, based on the second service parameter and the first service parameter, to forward the address acquisition request to an AF device via the NEF network element; wherein, the second service parameter includes service parameters stored in the UDM network element and associated with the AF device.

[0359] In some embodiments, the first service parameter is determined by an OSS network element and sent to the UDM network element.

[0360] In some embodiments, the second service parameter includes service type identifiers of at least one service; the service type identifiers are sent by the AF device to the NRF network element via the NEF network element.

[0361] In some embodiments, a second acquisition module is configured to acquire second identifiers of at least one PEGC device;

[0362] A second processing module is configured to generate an address acquisition request based on the second identifiers;

[0363] The third transceiver module is configured to send the address acquisition request to the AF device, so that the AF device sends a first address to at least one PEGC device based on the second identifiers.

[0364] In some embodiments, the second processing module is configured to determine a first identifier of a PINE device based on a data acquisition request; perform an authentication operation on the PINE device based on the first identifier to obtain an authentication result; if the authentication result indicates that the PINE device passes the authentication, determine a target PEGC device from at least one PEGC device.

[0365] Based on the foregoing embodiments, an embodiment of the present application further provides a computer-readable storage medium, in which a fourth computer program is stored. When the fourth computer program is executed by a processor of an electronic device, it can implement the data acquisition method provided in any previous embodiment.

[0366] The descriptions of the above embodiments tend to emphasize the differences between the embodiments. Their similarities or similarities can be referred to each other. For the sake of brevity, they will not be repeated herein.

[0367] The methods disclosed in the method embodiments provided by the present application can be arbitrarily combined without conflict to obtain new method embodiments.

[0368] The features disclosed in the product embodiments provided by the present application can be arbitrarily combined without conflict to obtain new product embodiments.

[0369] The features disclosed in the method or device embodiments provided by the present application can be arbitrarily combined without conflict to obtain new method embodiments or device embodiments.

[0370] It should be noted that the above computer-readable storage medium may be a read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), ferromagnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM), etc.; it may also be various electronic devices including one or any combination of the above memories, such as mobile phones, computers, tablet devices, personal digital assistants, etc.

[0371] It should be noted that in this article, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, but also includes other elements not explicitly listed, or further includes elements inherent to such process, method, article or device. Without more limitations, an element defined by the statement "including one..." does not exclude the existence of another identical element in the process, method, article or device including that element.

[0372] The serial numbers of the embodiments of the present application above are only for description and do not represent the superiority or inferiority of the embodiments.

[0373] Through the description of the above embodiments, those skilled in the art can clearly understand that the above embodiment methods can be implemented by means of software plus necessary general hardware nodes. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disc) and includes several instructions to enable a terminal device (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of the present application.

[0374] This application is described with reference to the flowcharts and / or block diagrams of methods, apparatuses (systems), and computer program products according to embodiments of the present application. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, as well as the combination of flows and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to generate a machine, such that the instructions executed by the processor of the computer or other programmable data processing devices generate a means for implementing the functions specified in one or more flows of the flowchart and / or one or more blocks of the block diagram.

[0375] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, such that the instructions stored in the computer-readable memory generate a manufactured article including an instruction means that implements the functions specified in one or more flows of the flowchart and / or one or more blocks of the block diagram.

[0376] These computer program instructions can also be loaded onto a computer or other programmable data processing device, such that a series of operation steps are executed on the computer or other programmable device to generate a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more flows of the flowchart and / or one or more blocks of the block diagram.

[0377] The above are only the preferred embodiments of the present application, and do not limit the patent scope of the present application. Any equivalent structural or equivalent process transformation made by using the specification and drawings of the present application, or directly or indirectly applied in other related technical fields, shall be equally included in the patent protection scope of the present application.

Claims

1. A data acquisition method, characterized in that, The method is applied to the PINE device in the PIN; the method includes: Sending a data acquisition request for requesting to acquire target data to the PEMC device in the PIN; wherein, the target data is stored in at least one PEGC device of the PIN; the target data is pre-acquired from a network server by the at least one PEGC device; the PEMC device is configured to determine a target PEGC device from the at least one PEGC device and forward the data acquisition request to the target PEGC device; Receiving the target data sent by the target PEGC device.

2. The method according to claim 1, characterized in that The sending a data acquisition request for requesting to acquire target data to the PEMC device in the PIN includes: Obtaining a first identifier of the PINE device; Generating the data acquisition request based on the first identifier; Sending the data acquisition request to the PEMC device; wherein, the PEMC device is configured to perform an authentication operation on the PINE device based on the first identifier, and forward the data acquisition request to the target PEGC device when the result of the authentication operation is authentication passed.

3. The method according to claim 1, wherein The network server includes an AF device; before sending a data acquisition request for requesting to acquire target data to the PEMC device in the PIN, the method further includes: Receiving a broadcast message sent by the PEMC device; wherein, the broadcast message is used to indicate that the at least one PEGC device has acquired the target data from the AF device.

4. A data acquisition method, characterized in that, The method is applied to the target PEGC device in the PIN; the method includes: Receiving a data acquisition request for requesting to acquire target data sent by the PEMC device in the PIN; wherein, the target PEGC device is determined by the PEMC device from at least one PEGC device included in the PIN; at least the target data pre-acquired from a network server is stored in the at least one PEGC device; the data acquisition request is sent from the PINE device in the PIN to the PEMC device; Sending the target data to the PINE device.

5. The method according to claim 4, wherein The network server includes an AF device; before sending the target data to the PINE device, the method further includes: Receiving a first address sent by the AF device; wherein, the first address includes a storage address of the target data; Acquiring the target data from the AF device based on the first address.

6. The method according to claim 5, wherein After acquiring the target data from the AF device based on the first address, the method further includes: Sending status information indicating that the target PEGC device has acquired the target data to the PEMC device, for the PEMC device to send a broadcast message to the PINE device based on the status information; wherein, the broadcast message is used to indicate that the target PEGC device has acquired the target data from the AF device.

7. The method according to claim 4, wherein The method further includes: Receiving a data update message for indicating an update of the target data. Update the target data based on the second address included in the data update message; wherein, the second address includes the storage address of the updated target data.

8. The method according to claim 7, wherein The network server includes an AF device; the receiving the data update message for indicating the update of the target data includes: Receiving the data update message from an AMF network element; wherein, the data update message is sent by the AF device to the AMF network element via an NEF network element.

9. A data acquisition method, characterized in that, The method is applied to a PEMC device in a PIN; the method includes: Receiving a data acquisition request for requesting to acquire target data sent by a PINE device in the PIN; Determining a target PEGC device from at least one PEGC device included in the PIN; wherein, the target data pre-acquired from a network server is stored in the at least one PEGC device; Forwarding the data acquisition request to the target PEGC device for the target PEGC device to send the target data to the PINE device.

10. The method according to claim 9, characterized in that Before receiving the data acquisition request for requesting to acquire target data sent by the PINE device in the PIN, the method further includes: Receiving status information that the at least one PEGC device has acquired the target data; Generating a broadcast message based on the status information; wherein, the broadcast message is used to indicate that the at least one PEGC device has acquired the target data from the network server; Sending the broadcast message to the PINE device in the PIN.

11. The method according to claim 9, wherein The network server includes an AF device; before receiving the data acquisition request for requesting to acquire target data sent by the PINE device in the PIN, the method further includes: Sending an address acquisition request to the AF device for the AF device to determine a first address storing the target data and send the first address to the at least one PEGC device; wherein, the first address is used for the at least one PEGC device to acquire the target data.

12. The method according to claim 11, wherein The sending the address acquisition request to the AF device includes: Acquiring a first service parameter; wherein, the first service parameter at least includes a service type; the first service parameter is associated with the PEMC device; Generating the address acquisition request based on the first service parameter; Sending the address acquisition request to an AMF network element for the AMF network element to determine, based on a second service parameter and the first service parameter, to forward the address acquisition request to the AF device via an NEF network element; wherein, the second service parameter includes service parameters stored in a UDM network element and associated with the AF device.

13. The method according to claim 12, wherein The first service parameter is determined and sent to the UDM network element by an OSS network element.

14. The method according to claim 12, wherein The second service parameter includes service type identifiers of at least one service; the service type identifiers are sent by the AF device to an NRF network element through an NEF network element.

15. The method according to claim 11, wherein The sending the address acquisition request to the AF device includes: Acquiring a second identifier of the at least one PEGC device; Generating the address acquisition request based on the second identifier; Send the address acquisition request to the AF device for the AF device to send the first address to the at least one PEGC device based on the second identifier.

16. The method according to claim 9, characterized in that, Determining the target PEGC device from at least one PEGC device included in the PIN includes: Determining a first identifier of the PINE device based on the data acquisition request; Performing an authentication operation on the PINE device based on the first identifier to obtain an authentication result; If the authentication result indicates that the PINE device passes authentication, determine the target PEGC device from the at least one PEGC device.

17. A PINE device, characterized in that, The PINE device includes a first processor and a first memory; wherein, a first computer program is stored in the first memory; when the first computer program is executed by the first processor, it can implement the data acquisition method according to any one of claims 1 to 3.

18. A target PEGC device, characterized in that, The target PEGC device includes a second processor and a second memory; wherein, a second computer program is stored in the second memory; when the second computer program is executed by the second processor, it can implement the data acquisition method according to any one of claims 4 to 8.

19. A PEMC device, characterized in that, The PEMC device includes a third processor and a third memory; wherein, a third computer program is stored in the third memory; when the third computer program is executed by the third processor, it can implement the data acquisition method according to any one of claims 9 to 16.

20. A computer-readable storage medium, characterized in that, A fourth computer program is stored in the storage medium; when the fourth computer program is executed by a processor of an electronic device, it can implement the data acquisition method according to any one of claims 1 to 3, 4 to 8, or 9 to 16.

Images