Information receiving and sending method, performance data determination method, entity and medium

Abstract

The invention discloses an information receiving and sending method, a performance data determination method, an entity and a medium. The information receiving method is applied to a first communication entity, and the method comprises: receiving a first request message sent by a second communication entity, the first request message comprising a distinguishable name DN of the second communication entity; and storing the DN of the second communication entity in a configuration file of the second communication entity, and sending a first feedback message to the second communication entity.

Description

Technical Field

[0001] This application relates to the field of communication technology, such as methods for receiving and sending information, methods for determining performance data, entities, and media. Background Technology

[0002] With the continuous development of communication technology, the management and collection of node-level performance is an important research direction for energy conservation in future communication networks. In the current network architecture, the management and exposure of performance data are mostly limited to Operations, Administration, and Maintenance (OAM) and are relatively coarse-grained. There is no standardized method for exposing fine-grained energy consumption information of individual Network Functions (NFs) to authorized network elements. This not only limits the accurate monitoring and optimization of the performance of specific nodes, but also makes it difficult to meet increasingly stringent energy conservation and emission reduction requirements. Summary of the Invention

[0003] This application provides an information receiving method applied to a first communication entity, the method comprising:

[0004] Receive a first request message sent by a second communication entity, the first request message including the identifiable name (DN) of the second communication entity;

[0005] The DN of the second communication entity is stored in the configuration file of the second communication entity, and a first feedback message is sent to the second communication entity.

[0006] This application provides an information sending method applied to a second communication entity, the method comprising:

[0007] Send a first request message to a first communication entity, the first request message including the identifiable name (DN) of the second communication entity;

[0008] Receive the first feedback message sent by the first communication entity.

[0009] This application provides a method for determining performance data, applied to a third communication entity, the method comprising:

[0010] Send a second request message to the first communication entity. The second request message is used to request a query of the services of the second communication entity.

[0011] The system receives a second feedback message sent by a first communication entity. The second feedback message includes a configuration file of at least one second communication entity. The configuration file includes a distinguishable name (DN) of the second communication entity, and the DN of the second communication entity is used to determine the performance data of the second communication entity.

[0012] This application provides a communication entity, including a processor; the processor is used to implement the method of any of the above embodiments when executing a computer program.

[0013] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the method of any of the above embodiments.

[0014] Further details regarding the above embodiments and other aspects of this application, as well as their implementations, are provided in the accompanying drawings, detailed description, and claims. Attached Figure Description

[0015] Figure 1 This is a schematic diagram of a core network architecture provided in one embodiment;

[0016] Figure 2 This is a flowchart illustrating an information receiving method provided in one embodiment;

[0017] Figure 3 This is a flowchart illustrating an information sending method provided in one embodiment;

[0018] Figure 4 This is a flowchart illustrating a method for determining performance data according to one embodiment;

[0019] Figure 5 Example 1 provides an interactive flowchart of information transmission.

[0020] Figure 6 Example 2 provides an interactive flowchart of a method for determining performance data;

[0021] Figure 7 Example 3 provides an interactive flowchart of a method for determining performance data;

[0022] Figure 8 Example 4 provides an interactive flowchart of a method for determining performance data;

[0023] Figure 9 Example 5 provides an interactive flowchart of a method for determining performance data;

[0024] Figure 10 This is a schematic diagram of the structure of an information receiving device provided in one embodiment;

[0025] Figure 11 This is a schematic diagram of the structure of an information transmission device provided in one embodiment;

[0026] Figure 12 This is a schematic diagram of a performance data determination device provided in one embodiment;

[0027] Figure 13 This is a schematic diagram of the structure of a communication entity provided in one embodiment. Detailed Implementation

[0028] It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application. The embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0029] Currently, green and low-carbon development has become an important direction in the field of communication technology. How to optimize the energy efficiency management of communication networks to reduce energy consumption is a key issue of concern in the industry. As a core component of communication network management, the OAM system is responsible for tasks such as operation monitoring, configuration management, performance evaluation, and troubleshooting, and generates a large amount of data related to network operation status and service performance while performing these tasks.

[0030] However, existing OAM system data collection and processing are primarily limited to internal systems, with limited data openness and sharing capabilities. For third-party network elements, obtaining performance data from individual nodes is crucial for implementing energy-saving strategies and management optimization. However, exposing OAM system-collected data to external network elements typically requires these external network elements to possess a management object database compatible with the OAM system. This not only increases the configuration complexity of external network elements but also raises operational costs.

[0031] The information receiving method, information transmitting method, and performance data determination method provided in this application can be applied to various wireless communication systems, such as 5th-generation (5G) systems, 5G New Radio (NR) systems, and new communication systems emerging in future communication development, such as 6th-generation (6G) systems. Optionally, the information receiving method, information transmitting method, and performance data determination method can be applied to the core network of a communication system.

[0032] Figure 1 This is a schematic diagram of a core network architecture provided in one embodiment. For example... Figure 1As shown, the User Equipment (UE) connects to the core network's network functions via the Radio Access Network (RAN). The RAN manages radio resources, transmits user data received through the N3 interface to the UE, and transmits user data from the UE through the N3 interface. The RAN maps Quality of Service (QoS) traffic between Dedicated Radio Bearer (DRB) and Protocol Data Unit (PDU) sessions.

[0033] The Access and Mobility Management Function (AMF) includes the following functions: registration management, connection management, reachability management, and mobility management. This function also performs access authentication and authorization. The AMF is a Non-Access Stratum (NAS) secure terminal that forwards SM NAS, etc., between the UE and the Session Management Function (SMF).

[0034] SMF includes the following functions: session establishment, modification, and release; UE network protocol (Internet Protocol, IP) address allocation and management (including optional authorization functions); selection and control of User Plane Functions (UPFs); and downlink data notification. SMF is associated with and controls the UPF through the N4 interface. SMF provides the UPF with Packet Detection Rules (PDRs) instructing how to detect user data traffic; it also provides Forwarding Action Rules (FARs), QoS Enforcement Rules (QERs), and Usage Reporting Rules (URRs) instructing the UPF how to perform user data traffic forwarding, QoS processing, and usage reporting on user data traffic detected using PDRs.

[0035] The UPF includes the following functions: serving as an anchor point for movement within / between Radio Access Technology (RAT), packet routing and forwarding, traffic usage reporting, user plane QoS processing, downlink packet buffering, and downlink data notification triggering. The GTP-U tunnel is used for the N3 interface between the RAN and the UPF. The GTP-U tunnel operates on a per-PDU session basis. For downlink traffic, the UPF binds the downlink traffic to the QoS traffic within the PDU session's GTP-U tunnel using the FAR received from the SMF. For uplink traffic, the RAN transmits user plane traffic to the QoS stream recognized by the UE.

[0036] The Policy Control Function (PCF) provides QoS policy rules to control plane functions for enforcement. The PCF translates Application Function (AF) requests into Policy and Charging Control (PCC) rules applicable to PDU sessions.

[0037] Unified Data Management (UDM) performs tasks such as generating 3GPP Authentication and Key Agreement (AKA) credentials, authorizing access based on subscription data, managing UE service element registration (e.g., storing AMF for UEs and SMF for UE PDU sessions), and subscription management. UDM accesses the Unified Data Repository (UDR) to retrieve UE subscription data and store the UE context in the UDR. UDM and UDR can be deployed together.

[0038] The information receiving method provided in this application embodiment can be applied to the first communication entity, the information sending method can be applied to the second communication entity, and the performance data determination method can be applied to the third communication entity. The first communication entity can be a Network Repository Function (NRF), the second communication entity can be an NF, and the third communication entity can be an Energy Information Function (EIF) or a Network Data Analytics Function (NWDAF), or other 5G core network (5GC) elements with data collection and / or subscription needs. Additionally, the fourth communication entity mentioned in this application embodiment can be an OAM.

[0039] In this application embodiment, an information receiving method, an information sending method, a performance data determination method, a communication entity, and a storage medium are provided. By extending the registration parameters of the communication entity and converting the identity identifier of the communication entity, performance monitoring of a single communication entity (such as an NF) can be achieved, thereby realizing more efficient network node energy efficiency management and laying the foundation for the low-carbon deployment of future networks.

[0040] The following describes the information receiving method, the information sending method, the method for determining performance data, the communication entity, and its technical effects.

[0041] Figure 2 This is a flowchart illustrating an information receiving method according to one embodiment. Figure 2 As shown, the method provided in this embodiment is applicable to a first communication entity. For example, the first communication entity may be an NRF. The method includes the following steps.

[0042] S210. Receive a first request message sent by the second communication entity, the first request message including the DN of the second communication entity.

[0043] In one embodiment, a first communication entity can receive registration requests from at least one second communication entity, meaning the number of second communication entities can be one or more. The second communication entity can be an NF (Network Functional Entity).

[0044] The first request message can be a registration request message, used to request registration from the first communication entity so that the second communication entity can have service capabilities. For example, the first request message can be an Nnrf_NFManagement_NFRegisterRequest message.

[0045] The first request message includes the Distinguished Name (DN) of the second communication entity. The DN of the second communication entity can also be referred to as the Managed Object Instance (MOI) DN of the second communication entity. The DN of the second communication entity is allocated and distributed to each second communication entity by the fourth communication entity, which can be the OAM (Operational Information Management Entity).

[0046] In one embodiment, the first request message may include, in addition to the DN of the second communication entity, at least one of the following: the instance ID of the second communication entity, the type of the second communication entity, the Public Land Mobile Network Identifier (PLMN ID) under the Public Land Mobile Network (PLMN), the PLMN ID and Network Identifier (NID) under the Stand-Alone Non-Public Network (SNPN), the network slice related identifier, the fully qualified domain name (FQDN) or IP address of the second communication entity.

[0047] S220. Store the DN of the second communication entity in the configuration file of the second communication entity, and send the first feedback message to the second communication entity.

[0048] After receiving the first request message from the second communication entity, the first communication entity can store the second communication entity's DN in the second communication entity's profile and mark the second communication entity as available. A first feedback message is then sent to the second communication entity.

[0049] The first feedback message is used to indicate that the registration of the second communication entity has been accepted. For example, the first feedback message could be an Nnrf_NFManagement_NFRegister response message.

[0050] By carrying the DN of the second communication entity during the registration process of the second communication entity to the first communication entity, the registration parameters in the NRF are extended, and the identity of the NF is transformed.

[0051] Optionally, the first communication entity may also respond to a query request from the third communication entity by sending the DN of the second communication entity to the third communication entity, so that the third communication entity can determine the performance data of the second communication entity. The third communication entity may be an EIF or an NWDAF.

[0052] Specifically, after step S220 is executed, the first communication entity can also receive a second request message sent by the third communication entity, which is used to request a query of the services of the second communication entity; and send a second feedback message to the third communication entity, which includes at least one configuration file of the second communication entity, including the DN of the second communication entity, which is used to determine the performance data of the second communication entity. This simplifies the process of the NF extracting data from the OAM system and reduces the complexity of network operation and maintenance.

[0053] In one embodiment, the second request message includes the instance ID of the second communication entity or the DN of the second communication entity.

[0054] Figure 3 This is a flowchart illustrating an information sending method provided in one embodiment. For example... Figure 3 As shown, the method provided in this embodiment is applicable to a second communication entity. For example, the second communication entity may be an NF. The method includes the following steps.

[0055] S310. Send a first request message to the first communication entity, the first request message including the DN of the second communication entity.

[0056] Before the second communication entity can provide services, it needs to request registration. Specifically, the first request message can be a registration request message, used to request registration from the first communication entity. The first communication entity can be an NRF. The first request message can be an Nnrf_NFManagement_NFRegister Request message.

[0057] The first request message includes the DN of the second communication entity, which can also be referred to as the MOIDN of the second communication entity. The DN of the second communication entity is allocated and distributed to each second communication entity by the fourth communication entity. The fourth communication entity can be the OAM. That is, before step S310 is executed, the second communication entity can receive the DN allocated by the fourth communication entity.

[0058] In one embodiment, the first request message may include, in addition to the DN of the second communication entity, at least one of the following: the instance ID of the second communication entity, the type of the second communication entity, the PLMNID under the PLMN, the PLMN ID and NID under the SNPN, the network slice related identifier, and the FQDN or IP address of the second communication entity.

[0059] S320: Receive the first feedback message sent by the first communication entity.

[0060] The first feedback message is sent by the first communication entity to the second communication entity after the first communication entity marks the second communication entity as available, i.e., after registration is completed.

[0061] The first feedback message is used to indicate that the registration of the second communication entity has been accepted. For example, the first feedback message could be an Nnrf_NFManagement_NFRegister response message.

[0062] By carrying the DN of the second communication entity during the registration process of the second communication entity to the first communication entity, the registration parameters in the NRF are extended, and the identity of the NF is transformed.

[0063] Figure 4 This is a flowchart illustrating a method for determining performance data according to one embodiment. Figure 4 As shown, the method provided in this embodiment is applicable to a third communication entity. For example, the third communication entity can be an EIF or an NWDAF, or other 5GC network elements with data collection and / or subscription requirements. An EIF can be deployed independently or embedded within an NWDAF as a logical functional block of the NWDAF. When an EIF is embedded within an NWDAF, the third communication entity is the NWDAF. The method includes the following steps.

[0064] S410. Send a second request message to the first communication entity. The second request message is used to request a query service from the second communication entity.

[0065] In scenarios where a third communication entity retrieves performance data, the third communication entity needs to send a second request message to the first communication entity to request a query for the second communication entity's service. For example, the second request message could be an Nnrf_NFDiscovery_Request message.

[0066] In one embodiment, the second request message includes the instance ID of the second communication entity or the DN of the second communication entity.

[0067] S420. Receive a second feedback message sent by the first communication entity. The second feedback message includes a configuration file of at least one second communication entity. The configuration file includes the DN of the second communication entity. The DN of the second communication entity is used to determine the performance data of the second communication entity.

[0068] In one embodiment, the configuration file of at least one second communication entity included in the second feedback message is determined by the first communication entity after authorizing the Nnrf_NFDiscovery_Request information, and is the configuration file of the second communication entity that is allowed to be discovered by the third communication entity.

[0069] In one embodiment, the configuration file of the second communication entity may further include at least one of the following: the instance ID of the second communication entity, the type of the second communication entity, the PLMN ID under the PLMN, the PLMNID and NID under the SNPN, the network slice related identifier, and the FQDN or IP address of the second communication entity.

[0070] In one alternative implementation, when the second request message includes the instance ID of the second communication entity, the configuration file of the second communication entity includes at least its DN. The third communication entity can subsequently initiate the collection / subscription of performance data using the DN of the second communication entity.

[0071] For example, a method for a third communication entity to initiate the collection / subscription of performance data using the DN of the second communication entity may include: sending a third request message to a fourth communication entity, the third request message being used to request the creation of a performance measurement task, the third request message including the DN of the second communication entity and reporting indication information, the reporting indication information being used to indicate the reporting format of the data that the third communication entity expects to receive; and receiving a third feedback message sent by the fourth communication entity.

[0072] When the reporting instruction information indicates that the third communication entity expects to receive data in streaming format, the third communication entity, after establishing a streaming connection with the fourth communication entity, receives streaming data units sent by the fourth communication entity. The streaming data units include the performance data of the second communication entity corresponding to the DN of the second communication entity.

[0073] When the reporting instruction information indicates that the third communication entity expects to receive data in file data format, the third communication entity, after subscribing to the file from the fourth communication entity, receives a notification file sent by the fourth communication entity. The notification file includes the performance data of the second communication entity corresponding to the DN of the second communication entity.

[0074] For example, a method for a third communication entity to initiate the collection / subscription of performance data using the DN of the second communication entity may include: sending a fourth request message to a fourth communication entity, the fourth request message being used for subscription information, the fourth request message including the DN of the second communication entity; receiving first subscription information sent by the fourth communication entity, the first subscription information including at least one of the following: performance data of the second communication entity corresponding to the DN of the second communication entity, and a threshold notification related to the performance data of the second communication entity corresponding to the DN of the second communication entity.

[0075] In another optional implementation, when the second request message includes the DN of the second communication entity, the configuration file of the second communication entity includes at least the DN of the second communication entity and the instance ID of the second communication entity corresponding to the DN. Thus, the third communication entity can match the performance data corresponding to the previously acquired DN of the second communication entity based on the correspondence between the instance ID and the DN of the second communication entity.

[0076] For example, before step S410 is executed, the third communication entity may send a fifth request message to the fourth communication entity. The fifth request message is used to subscribe to information and includes the instance ID of the second communication entity. The third communication entity may receive second subscription information sent by the fourth communication entity. The second subscription information includes at least one of the following: performance data of the second communication entity corresponding to the DN of the second communication entity corresponding to the instance ID of the second communication entity, and a threshold notification related to the performance data of the second communication entity corresponding to the DN of the second communication entity corresponding to the instance ID of the second communication entity.

[0077] Below are some examples illustrating the method provided in this application. In the examples below, the first communication entity is NRF, the second communication entity is NF, the third communication entity is NWDAF, and the fourth communication entity is OAM. Optionally, the third communication entity can also be EIF.

[0078] Example 1

[0079] Figure 5 This is an interactive flowchart of information transmission provided in Example 1. For example... Figure 5 As shown, the steps include the following.

[0080] S501 and NF send the first request message to NRF.

[0081] The first request message can be a registration request message, used to request registration with the NRF. The first request message can be an Nnrf_NFManagement_NFRegister Request message. The first request message carries relevant parameters configured by OAM, including the NF DN.

[0082] Optionally, the relevant parameters may also include at least one of the following: NF instance ID, NF type, PLMN ID under PLMN, PLMN ID and NID under SNPN, network slice related identifier, NF FQDN or IP address.

[0083] S502, NRF receives the first request information sent by NF.

[0084] S503 and NRF store the NF DN in the NF configuration file.

[0085] Optionally, the NRF can also mark the NF as available.

[0086] S504 and NRF send the first feedback message to NF.

[0087] The first feedback message indicates that the NF registration has been accepted. The first feedback message can be an Nnrf_NFManagement_NFRegister response message.

[0088] The S505 and NF receive the first feedback message sent by the NRF.

[0089] Example 2

[0090] Assume that NWDAF stores a list of NFs, which includes the NF instanceIDs of the NFs for which performance data needs to be collected. Figure 6 This is an interactive flowchart illustrating a method for determining performance data, as provided in Example 2. Figure 6 As shown, the steps include the following.

[0091] S601, NWDAF sends a second request message to NRF.

[0092] The second request message is used to request a query for the NF service. The second request message can be an Nnrf_NFDiscovery_Request message. In Example 2, the second request message includes the NF instance ID from the NF list.

[0093] S602 and NRF receive the second request message sent by NWDAF and look up the configuration file of the corresponding NF based on the NF instance ID.

[0094] After receiving the second request message sent by NWDAF, NRF authorizes the second request message and looks up the configuration file of the corresponding NF based on the NFinstance ID.

[0095] Optionally, the NRF can also determine whether to allow the NWDAF to discover the NFs it requires, based on the type of the NWDAF. If the NRF finds NFs whose configuration files contain NFs that the NWDAF is not allowed to discover, then the configuration files of these disallowed NFs will not be sent to the NWDAF in subsequent steps.

[0096] S603 and NRF send a second feedback message to NWDAF.

[0097] The second feedback message includes at least one NF configuration file, which is an NF configuration file that is allowed to be discovered by NWDAF and matches the internal policies of NRF. The NF configuration file includes at least an NF DN, which is used to determine the performance data of the NF.

[0098] Optionally, the NF configuration file may also include at least one of the following: NF instance ID, NF type, PLMN ID under PLMN, PLMN ID and NID under SNPN, network slice related identifier, NF FQDN or IP address.

[0099] S604, NWDAF receives the second feedback message sent by NRF.

[0100] S605 and NWDAF send a third request message to OAM.

[0101] Specifically, NWDAF sends a third request message to the NF measurement job control service producer in OAM to request the creation of a performance measurement task. For example, the third request message could be a CreateMeasurementJob_Request message.

[0102] The third request message includes an iOC instance list (iOCInstanceList), which contains the NF DNs of the NFs that NWDAF needs to collect and reporting indication information. The reporting indication information indicates the reporting format of the data that NWDAF expects to receive. In Example 2, the reporting indication information indicates that the reporting format of the data that NWDAF expects to receive is streaming data format.

[0103] Optionally, the iOC instance list may also include at least one of the following: a measurement category list, a granularity period, a stream target, and some optional parameters related to the acquisition time. The stream target specifies the target of the streaming data transmission (i.e., set to NWDAF in Example 2).

[0104] S606, OAM receives the third request message sent by NWDAF.

[0105] S607. For the NF required for NWDAF acquisition, OAM determines whether a new measurement data collection task needs to be created.

[0106] If it is not necessary to create a new measurement data collection task, proceed directly to step S608 below; if it is necessary to create a new measurement data collection task, proceed to step S608 below after creating the new measurement data collection task.

[0107] The specific methods for creating a new measurement data collection task may include: the OAM sending a collection performance data request message to the corresponding NF; and the OAM receiving a collection performance data feedback message from the corresponding NF.

[0108] S608 and OAM send a third feedback message to NWDAF.

[0109] The third feedback message is a response to the request to create a performance measurement task. For example, the third feedback message can be an Nnrf_NFDiscovery_Response message. The third feedback message can include at least one of the following: task ID (indicating the name of the measurement task instance), unsupported list, and status.

[0110] S609 and NWDAF receive the third feedback message sent by OAM.

[0111] S610, NWDAF, and OAM establish a streaming connection.

[0112] Specifically, the method for NWDAF and OAM to establish a streaming connection may include: NWDAF receiving a streaming connection establishment request message sent by OAM, which requests the establishment of a streaming connection. The streaming connection establishment request message carries a producerId and a stream information list (streamInfoList). The streamInfoList includes the task ID created in the previous steps. NWDAF then sends a streaming connection establishment feedback message to OAM, which carries a connectionId and a status.

[0113] S611, OAM sends streaming data units to NWDAF.

[0114] The streaming data unit carries the connectionId and streamingData, and includes the payload of the report transmitted via streaming. This determines the performance data of the NF corresponding to the NF DN.

[0115] The performance data may include, but is not limited to, at least one of the following indicators: power consumption, carbon emissions, and the proportion of renewable energy used.

[0116] S612, NWDAF receives the streaming data unit sent by OAM.

[0117] Example 3

[0118] Assume that NWDAF stores a list of NFs, which includes the NF instanceIDs of the NFs for which performance data needs to be collected. Figure 7 This is an interactive flowchart illustrating a method for determining performance data, as provided in Example 3. Figure 7 As shown, the steps include the following.

[0119] S701 and NWDAF send a second request message to NRF.

[0120] The second request message is used to request a query for the NF service. The second request message can be an Nnrf_NFDiscovery_Request message. In Example 3, the second request message includes the NF instance ID from the NF list.

[0121] S702 and NRF receive the second request message sent by NWDAF and look up the configuration file of the corresponding NF based on the NF instance ID.

[0122] After receiving the second request message sent by NWDAF, NRF authorizes the second request message and looks up the configuration file of the corresponding NF based on the NFinstance ID.

[0123] Optionally, the NRF can also determine whether to allow the NWDAF to discover the NFs it requires, based on the type of the NWDAF. If the NRF finds NFs whose configuration files contain NFs that the NWDAF is not allowed to discover, then the configuration files of these disallowed NFs will not be sent to the NWDAF in subsequent steps.

[0124] S703 and NRF send a second feedback message to NWDAF.

[0125] The second feedback message includes at least one NF configuration file, which is an NF configuration file that is allowed to be discovered by NWDAF and matches the internal policies of NRF. The NF configuration file includes at least an NF DN, which is used to determine the performance data of the NF.

[0126] Optionally, the NF configuration file may also include at least one of the following: NF instance ID, NF type, PLMN ID under PLMN, PLMN ID and NID under SNPN, network slice related identifier, NF FQDN or IP address.

[0127] S704 and NWDAF receive the second feedback message sent by NRF.

[0128] S705 and NWDAF send a third request message to OAM.

[0129] Specifically, NWDAF sends a third request message to the NF measurement job control service producer in OAM to request the creation of a performance measurement task. For example, the third request message could be a CreateMeasurementJob_Request message.

[0130] The third request message includes an iOC instance list (iOCInstanceList), which contains the NF DNs of the NFs that NWDAF needs to collect and reporting indication information. The reporting indication information indicates the reporting format of the data that NWDAF expects to receive. In Example 3, the reporting indication information indicates that the reporting format of the data that NWDAF expects to receive is file data format.

[0131] Optionally, the iOC instance list may also include at least one of the following: a measurement category list, a granularity period, and some optional parameters related to the acquisition time. The granularity period specifies the reporting period information for the acquired data files.

[0132] S706, OAM receives the third request message sent by NWDAF.

[0133] S707. For the NF required for NWDAF acquisition, OAM determines whether a new measurement data collection task needs to be created.

[0134] If it is not necessary to create a new measurement data collection task, proceed directly to step S708 below; if it is necessary to create a new measurement data collection task, proceed to step S708 below after creating the new measurement data collection task.

[0135] The specific methods for creating a new measurement data collection task may include: the OAM sending a collection performance data request message to the corresponding NF; and the OAM receiving a collection performance data feedback message from the corresponding NF.

[0136] S708 and OAM send a third feedback message to NWDAF.

[0137] The third feedback message is a response to the request to create a performance measurement task. For example, the third feedback message can be an Nnrf_NFDiscovery_Response message. The third feedback message can include at least one of the following: task ID (indicating the name of the measurement task instance), unsupported list, and status.

[0138] S709 and NWDAF receive the third feedback message sent by OAM.

[0139] S710 and NWDAF subscribe to files from OAM.

[0140] Specifically, the method for NWDAF to subscribe to files from OAM can include: NWDAF sending a subscription request message to OAM, which may be notifyFileReady information, and carrying parameters such as the notification sending address (i.e., the NWDAF address) and the required filtering conditions. NWDAF then receives a subscription feedback message from OAM, which carries the subscriptionId and status.

[0141] S711, OAM sends a notification file to NWDAF.

[0142] Once the file is ready, it becomes available, at which point OAM sends a notification file to NWDAF. The notification file includes the performance data of the NF corresponding to the NF DN.

[0143] Optionally, the notification file may also include at least one of the following: notification name, notification type, fileInfoList and other parameters, where fileInfoList includes file location, file format and other file-related information, as well as jobId information related to the data collection task.

[0144] S712 and NWDAF receive notification files sent by OAM.

[0145] Example 4

[0146] Assume that the NWDAF stores a list of NFs, which includes the NF instanceIDs of the NFs for which performance data needs to be collected. NWDAF subscription can occur before or after the creation of a data measurement task. Example 4 describes an example where NWDAF subscription occurs before the creation of a data measurement task. Figure 8 This is an interactive flowchart illustrating a method for determining performance data, as provided in Example 4. Figure 8 As shown, the steps include the following.

[0147] S801 and NWDAF send a second request message to NRF.

[0148] The second request message is used to request a query for the NF service. The second request message can be an Nnrf_NFDiscovery_Request message. In Example 4, the second request message includes the NF instance ID from the NF list.

[0149] S802 and NRF receive the second request message sent by NWDAF and look up the configuration file of the corresponding NF based on the NF instance ID.

[0150] After receiving the second request message sent by NWDAF, NRF authorizes the second request message and looks up the configuration file of the corresponding NF based on the NFinstance ID.

[0151] Optionally, the NRF can also determine whether to allow the NWDAF to discover the NFs it requires, based on the type of the NWDAF. If the NRF finds NFs whose configuration files contain NFs that the NWDAF is not allowed to discover, then the configuration files of these disallowed NFs will not be sent to the NWDAF in subsequent steps.

[0152] S803 and NRF send a second feedback message to NWDAF.

[0153] The second feedback message includes at least one NF configuration file, which is an NF configuration file that is allowed to be discovered by NWDAF and matches the internal policies of NRF. The NF configuration file includes at least an NF DN, which is used to determine the performance data of the NF.

[0154] Optionally, the NF configuration file may also include at least one of the following: NF instance ID, NF type, PLMN ID under PLMN, PLMN ID and NID under SNPN, network slice related identifier, NF FQDN or IP address.

[0155] S804 and NWDAF receive the second feedback message sent by NRF.

[0156] S805 and NWDAF send a fourth request message to OAM.

[0157] Specifically, NWDAF sends a fourth request message to the performance data exposure service producer in OAM to request subscription information (such as subscribing to performance data, subscribing to threshold notifications related to performance data, etc.). The fourth request message can be PerformanceData_Subscribe information, and it includes the NF DN of the NF that NWDAF needs to collect.

[0158] Optionally, the fourth request message may also carry data reporting mode information and data notification sending address. For example, the data reporting mode information is used to indicate that the data reporting mode is periodic reporting, and the data reporting mode information includes reporting cycle information.

[0159] S806, OAM receives the fourth request message sent by NWDAF.

[0160] After receiving the fourth request message, the performance data exposure service producer in OAM can also send a fourth feedback message to NWDAF.

[0161] Additionally, for the performance data exposure service producer in OAM, the required NF and time granularity for NWDAF can be checked to determine if there is performance data that meets the criteria.

[0162] If there is performance data that meets the criteria, proceed directly to step S807 below; if there is no performance data that meets the criteria, proceed to step S807 below after requesting the creation of a measurement data collection task and obtaining the measurement results.

[0163] Specifically, the method by which OAM creates new measurement data collection tasks and obtains measurement results can include: the performance data exposure service producer (NF measurement job control service consumer) in OAM sends a CreateMeasurementJob_Request to the NF measurement job control service producer in OAM to request the creation of a measurement task. The CreateMeasurementJob_Request carries a list of iOC instances (iOCInstanceList, including the NF DNs of the NFs to be collected by NWDAF), a measurementCategoryList, reporting instructions (reportingMethod), and granularityPeriod. If the data is reported in file format, the reportingPeriod is specified, along with the file reporting and storage location being the performance data exposure service producer.

[0164] Upon receiving the CreateMeasurementJob_Request, the NF measurement job control service producer checks the NF that NWDAF requires to collect data to determine whether a new measurement data collection task needs to be created. If a new measurement data collection task needs to be created, the NF measurement job control service producer sends a performance data collection request message to the corresponding NF and receives a performance data collection feedback message from the corresponding NF. The NF measurement job control service producer sends an Nnrf_NFDiscovery_Response to the performance data exposure service producer (NF measurement job control service consumer). The Nnrf_NFDiscovery_Response can include at least one of the following: jobID (indicating the measurement task instance name), unsupported list, or status. The performance data exposure service producer receives the performance collection files / stream data collected by the NF.

[0165] S807 and OAM process performance to collect file / stream data and extract the performance data required for NWDAF.

[0166] Specifically, in OAM, the performance data exposure service producer processes performance data collection files / streams and extracts the performance data required by NWDAF.

[0167] S808 and OAM send the first subscription information to NWDAF.

[0168] The first subscription information includes at least one of the following: performance data of the NF corresponding to the NF DN, and threshold notifications related to the performance data of the NF corresponding to the NF DN.

[0169] Optionally, the first subscription message also includes information such as the notification name and timestamp.

[0170] S809 and NWDAF receive the first subscription information sent by OAM.

[0171] Example 5

[0172] Assume that the NWDAF stores a list of NFs, which includes the NF instanceIDs of the NFs for which performance data needs to be collected. NWDAF subscription can occur before or after the creation of a data measurement task. Example 5 describes an example where NWDAF subscription occurs before the creation of a data measurement task. Figure 9 This is an interactive flowchart illustrating a method for determining performance data, as provided in Example 5. Figure 9 As shown, the steps include the following.

[0173] S901 and NWDAF send a fifth request message to OAM.

[0174] Specifically, NWDAF sends a fifth request message to the performance data exposure service producer in OAM to request subscription information (such as subscribing to performance data, subscribing to threshold notifications related to performance data, etc.). The fifth request message can be PerformanceData_Subscribe information, and it includes the NF instance ID of the NF that NWDAF needs to collect.

[0175] Optionally, the fifth request message may also carry data reporting mode information, data notification sending address, monitoring period, etc. For example, the data reporting mode information may specify that a report should be made when a threshold is reached, and specify the threshold.

[0176] S902, OAM receives the fifth request message sent by NWDAF.

[0177] After receiving the fifth request message, the performance data exposure service producer in OAM can also send a fifth feedback message to NWDAF.

[0178] Additionally, for the performance data exposure service producer in OAM, the corresponding NF DN can be queried based on the NF instance ID, and the NF required by NWDAF can be checked based on the NF DN to determine if there is a performance collection task that meets the subscription request.

[0179] If there is a performance collection task that matches the subscription request, proceed directly to step S903 below; if there is no performance collection task that matches the subscription request, proceed to step S903 below after requesting the creation of a measurement data collection task.

[0180] Specifically, the method for OAM to create a new measurement data collection task may include: the performancedata exposure service producer (NF measurement job control service consumer) in OAM sends a CreateMeasurementJob_Request to the NF measurement job control service producer in OAM to request the creation of a measurement task. The CreateMeasurementJob_Request carries an iOC instance list (iOCInstanceList, including the NF DN of the NF to be collected by NWDAF), a measurementCategoryList, and reporting instructions (reportingMethod), etc.

[0181] Upon receiving the CreateMeasurementJob_Request, the NF measurement job control service producer checks the NFs required for NWDAF data collection to determine if a new measurement data collection task needs to be created. If a new measurement data collection task needs to be created, the NF measurement job control service producer sends a performance data collection request message to the corresponding NF and receives a performance data collection feedback message from the corresponding NF. The NF measurement job control service producer sends an Nnrf_NFDiscovery_Response to the performance dataexposure service producer (NF measurement job control service consumer). The Nnrf_NFDiscovery_Response can include at least one of the following: jobID (indicating the measurement task instance name), unsupported list, or status.

[0182] S903 and OAM send a performance measurement data monitoring request message to NF.

[0183] Optionally, if the fifth request message requests to subscribe to a threshold notification related to performance data, the performance measurement data monitoring request message will also carry the set performance data threshold.

[0184] S904 and NF receive performance measurement data monitoring request messages sent by OAM.

[0185] S905 and NF send performance measurement data monitoring feedback messages to OAM.

[0186] If the fifth request message requests a subscription to a threshold notification related to performance data, then NF will send a performance measurement data monitoring feedback message to OAM when the threshold is exceeded.

[0187] S906 and OAM receive performance measurement data monitoring feedback messages sent by NF.

[0188] S907 and OAM send a second subscription message to NWDAF.

[0189] The second subscription information includes at least one of the following: performance data of the NF corresponding to the NF DN of the NF instance ID, and threshold notifications related to the performance data of the NF corresponding to the NF DN of the NF instance ID. It should be noted that although the performance data / threshold notifications related to the performance data included in the second subscription information are essentially the performance data / threshold notifications related to the performance data of the NF DN corresponding to the NF instance ID, the second subscription information only carries the NF DN and its corresponding performance data / threshold notifications. At this point, OAM is still unsure of the correspondence between the NF instance ID and the NF DN.

[0190] S908 and NWDAF receive the second subscription information sent by OAM.

[0191] Since NWDAF does not know the correspondence between NF instance ID and NF DN at the current moment, it cannot determine which NF's performance data included in the second subscription information belongs to. Therefore, steps S909-S912 need to be executed to match the performance data.

[0192] S909 and NWDAF send a second request message to NRF.

[0193] The second request message is used to request a query for the NF service. The second request message can be an Nnrf_NFDiscovery_Request message. In Example 5, the second request message includes the received NF DN.

[0194] The S910 and NRF receive the second request message sent by the NWDAF and look up the configuration file of the corresponding NF based on the NF DN.

[0195] After receiving the second request message sent by NWDAF, NRF authorizes the second request message and looks up the configuration file of the corresponding NF based on the NF DN.

[0196] Optionally, the NRF can also determine whether to allow the NWDAF to discover the NFs it requires, based on the type of the NWDAF. If the NRF finds NFs whose configuration files contain NFs that the NWDAF is not allowed to discover, then the configuration files of these disallowed NFs will not be sent to the NWDAF in subsequent steps.

[0197] S911 and NRF send a second feedback message to NWDAF.

[0198] The second feedback message includes at least one NF configuration file, which is an NF configuration file that is allowed to be discovered by NWDAF and matches the internal policies of NRF. The NF configuration file includes at least the NF DN and its corresponding NF instance ID.

[0199] Optionally, the NF configuration file may also include at least one of the following: the type of NF, the PLMN ID under the PLMN, the PLMN ID and NID under the SNPN, network slice related identifiers, and the NF's FQDN or IP address.

[0200] S912 and NWDAF receive the second feedback message sent by NRF and match the NFs in the NF list with their corresponding performance information according to the correspondence between NF DN and NF instance ID.

[0201] Figure 10 This is a schematic diagram of the structure of an information receiving device provided in one embodiment. This device can be configured in a first communication entity, such as... Figure 10 As shown, the device includes: a first receiving module 100, a storage module 101, and a first transmitting module 102.

[0202] The first receiving module 100 is configured to receive a first request message sent by the second communication entity, the first request message including the identifiable name DN of the second communication entity;

[0203] Storage module 101 is configured to store the DN of the second communication entity in the configuration file of the second communication entity;

[0204] The first sending module 102 is configured to send a first feedback message to the second communication entity.

[0205] The information receiving device provided in this embodiment is for implementing... Figure 2 The information receiving method of the embodiment shown is similar in principle and technical effect to the information receiving device provided in this embodiment, and will not be repeated here.

[0206] In one embodiment, the first receiving module 100 is further configured to receive a second request message sent by a third communication entity, the second request message being used to request a query service from the second communication entity;

[0207] The first sending module 102 is further configured to send a second feedback message to a third communication entity. The second feedback message includes a configuration file of at least one second communication entity. The configuration file includes the DN of the second communication entity, and the DN of the second communication entity is used to determine the performance data of the second communication entity.

[0208] In one embodiment, the second request message includes the instance ID of the second communication entity or the DN of the second communication entity.

[0209] Figure 11 This is a schematic diagram of an information transmission device provided in one embodiment. This device can be configured in a second communication entity, such as... Figure 11 As shown, the device includes: a second transmitting module 200 and a second receiving module 201.

[0210] The second sending module 200 is configured to send a first request message to the first communication entity, the first request message including the identifiable name DN of the second communication entity;

[0211] The second receiving module 201 is configured to receive the first feedback message sent by the first communication entity.

[0212] The information sending device provided in this embodiment is for implementing... Figure 3 The information sending method of the illustrated embodiment and the information sending device provided in this embodiment are similar in principle and technical effect to those of the above embodiments, and will not be repeated here.

[0213] Figure 12 This is a schematic diagram of a performance data determination device provided in one embodiment. This device can be configured in a third communication entity, such as... Figure 12 As shown, the device includes a third transmitting module 300 and a third receiving module 301.

[0214] The third sending module 300 is configured to send a second request message to the first communication entity. The second request message is used to request a query service from the second communication entity.

[0215] The third receiving module 301 is configured to receive a second feedback message sent by the first communication entity. The second feedback message includes a configuration file of at least one second communication entity. The configuration file includes a distinguishable name (DN) of the second communication entity. The DN of the second communication entity is used to determine the performance data of the second communication entity.

[0216] The performance data determination device provided in this embodiment is for implementing... Figure 4 The performance data determination method of the embodiment shown is similar in principle and technical effect to the performance data determination device provided in this embodiment, and will not be repeated here.

[0217] In one embodiment, the second request message includes the instance ID of the second communication entity or the DN of the second communication entity.

[0218] In one embodiment, when the second request message includes the instance ID of the second communication entity,

[0219] The third sending module 300 is also configured to send a third request message to the fourth communication entity. The third request message is used to request the creation of a performance measurement task. The third request message includes the DN of the second communication entity and reporting indication information. The reporting indication information is used to indicate the reporting format of the data that the third communication entity expects to receive.

[0220] The third receiving module 301 is also configured to receive a third feedback message sent by the fourth communication entity.

[0221] In one embodiment, when the reporting indication information indicates that the third communication entity expects to receive data in a streaming data format, the third receiving module 301 is further configured to receive a streaming data unit sent by the fourth communication entity after establishing a streaming connection with the fourth communication entity. The streaming data unit includes the performance data of the second communication entity corresponding to the DN of the second communication entity.

[0222] In one embodiment, when the reporting indication information indicates that the third communication entity expects to receive data in a file data format, the third receiving module 301 is further configured to receive a notification file sent by the fourth communication entity after subscribing to the file from the fourth communication entity. The notification file includes the performance data of the second communication entity corresponding to the DN of the second communication entity.

[0223] In one embodiment, when the second request message includes the instance ID of the second communication entity,

[0224] The third sending module 300 is also configured to send a fourth request message to the fourth communication entity. The fourth request message is used to subscribe to information and includes the DN of the second communication entity.

[0225] The third receiving module 301 is further configured to receive first subscription information sent by the fourth communication entity. The first subscription information includes at least one of the following: performance data of the second communication entity corresponding to the DN of the second communication entity, and a threshold notification related to the performance data of the second communication entity corresponding to the DN of the second communication entity.

[0226] In one embodiment, when the second request message includes the DN of the second communication entity, the configuration file also includes the instance ID of the second communication entity corresponding to the DN of the second communication entity.

[0227] In one embodiment, the third sending module 300 is further configured to send a fifth request message to the fourth communication entity. The fifth request message is used to subscribe to information and includes the instance ID of the second communication entity.

[0228] The third receiving module 301 is further configured to receive second subscription information sent by the fourth communication entity. The second subscription information includes at least one of the following: performance data of the second communication entity corresponding to the DN of the second communication entity corresponding to the instance ID of the second communication entity, and a threshold notification related to the performance data of the second communication entity corresponding to the DN of the second communication entity corresponding to the instance ID of the second communication entity.

[0229] This application also provides a communication entity, including a processor, which is configured to implement the method provided in any embodiment of this application when executing a computer program. The communication entity in this embodiment can be a first communication entity, a second communication entity, or a third communication entity.

[0230] Figure 13 This is a schematic diagram of the structure of a communication entity provided in one embodiment. For example... Figure 13 As shown, the communication entity includes a processor 60, a memory 61, and a communication interface 62; the number of processors 60 in the communication entity can be one or more. Figure 13 Taking a processor 60 as an example; the processor 60, memory 61, and communication interface 62 in the communication entity can be connected via a bus or other means. Figure 13 Taking the bus connection as an example, a bus can refer to one or more of several bus architectures, including a memory bus or memory controller, a peripheral bus, a graphics acceleration port, a processor, or a local bus that uses any of the various bus architectures.

[0231] The memory 61, as a computer-readable storage medium, can be configured to store software programs, computer-executable programs, and modules, such as the program instructions / modules corresponding to the methods in the embodiments of this application. The processor 60 executes at least one functional application and data processing of the communication entity by running the software programs, instructions, and modules stored in the memory 61, thereby implementing the methods described above.

[0232] Memory 61 may include a program storage area and a data storage area. The program storage area may store the operating system and applications required for at least one function; the data storage area may store data created based on terminal usage. Furthermore, memory 61 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device. In some instances, memory 61 may include memory remotely located relative to processor 60, which can be connected to a communication entity via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, networks, mobile communication networks, and combinations thereof.

[0233] Communication interface 62 can be configured to receive and send data.

[0234] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the methods provided in any embodiment of this application.

[0235] The computer storage medium in this application embodiment can be any combination of one or more computer-readable media. The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. For example, a computer-readable storage medium can be, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. Computer-readable storage media include (a non-exhaustive list): electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), electrically erasable, programmable read-only memory (EPROM), flash memory, optical fiber, portable compact disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this application, the computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0236] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, the data signals carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit programs for use by or in conjunction with an instruction execution system, apparatus, or device.

[0237] Program code contained on a computer-readable medium may be transmitted using any suitable medium, including but not limited to wireless, wire, optical fiber, radio frequency (RF), or any suitable combination thereof.

[0238] Computer program code for performing the operations of this disclosure can be written in one or more programming languages ​​or a combination of programming languages, including object-oriented programming languages ​​(such as Java, Smalltalk, C++, Ruby, and Go) and conventional procedural programming languages ​​(such as the "C" language or similar programming languages). The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network (including a Local Area Network (LAN) or a Wide Area Network (WAN)), or it can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0239] This invention also provides a computer program product, including a computer program that, when executed by a processor, implements the method provided in any embodiment of this invention.

[0240] In implementing the computer program product, computer program code for performing the operations of this invention can be written in one or more programming languages ​​or a combination thereof. Programming languages ​​include object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as C or similar languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0241] Those skilled in the art will understand that the term user terminal encompasses any suitable type of wireless user equipment, such as mobile phones, portable data processing devices, portable web browsers, or vehicle-mounted mobile stations.

[0242] Generally, the various embodiments of this application can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. For example, some aspects can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device, although this application is not limited thereto.

[0243] Embodiments of this application can be implemented by executing computer program instructions through the data processor of a mobile device, for example, in a processor entity, or through hardware, or through a combination of software and hardware. The computer program instructions can be assembly instructions, Instruction Set Architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, status setting data, or source code or object code written in any combination of one or more programming languages.

[0244] Any block diagram of logical flow in the accompanying drawings of this application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions. The computer program may be stored in memory. The memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as, but not limited to, read-only memory (ROM), random access memory (RAM), optical storage devices and systems (Digital Multifunction Discs, DVDs, or CDs), etc. Computer-readable media may include non-transitory storage media. The data processor may be of any type suitable to the local technical environment, such as, but not limited to, general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), and processors based on multi-core processor architectures.

Claims

1. An information receiving method, characterized in that, Applied to a first communication entity, the method includes: Receive a first request message sent by a second communication entity, the first request message including the identifiable name (DN) of the second communication entity; The DN of the second communication entity is stored in the configuration file of the second communication entity, and a first feedback message is sent to the second communication entity.

2. The method according to claim 1, characterized in that, The method further includes: Receive a second request message sent by a third communication entity, the second request message being used to request a query of the second communication entity's service; A second feedback message is sent to the third communication entity. The second feedback message includes a configuration file of at least one second communication entity, the configuration file including the DN of the second communication entity, the DN of the second communication entity being used to determine the performance data of the second communication entity.

3. The method according to claim 2, characterized in that, The second request message includes the instance ID of the second communication entity or the DN of the second communication entity.

4. A method for sending information, characterized in that, Applied to a second communication entity, the method includes: Send a first request message to a first communication entity, the first request message including the identifiable name (DN) of the second communication entity; Receive the first feedback message sent by the first communication entity.

5. A method for determining performance data, characterized in that, Applied to a third communication entity, the method includes: Send a second request message to the first communication entity, the second request message being used to request a query of the services of the second communication entity; The system receives a second feedback message sent by the first communication entity. The second feedback message includes a configuration file of at least one second communication entity. The configuration file includes a identifiable name (DN) of the second communication entity, and the DN of the second communication entity is used to determine the performance data of the second communication entity.

6. The method according to claim 5, characterized in that, The second request message includes the instance ID of the second communication entity or the DN of the second communication entity.

7. The method according to claim 6, characterized in that, When the second request message includes the instance ID of the second communication entity, after receiving the second feedback message sent by the first communication entity, the method further includes: A third request message is sent to a fourth communication entity. The third request message is used to request the creation of a performance measurement task. The third request message includes the DN of the second communication entity and reporting indication information. The reporting indication information is used to indicate the reporting format of the data that the third communication entity expects to receive. Receive the third feedback message sent by the fourth communication entity.

8. The method according to claim 7, characterized in that, When the reporting indication information indicates that the third communication entity expects to receive data in a streaming data format, the method further includes: After establishing a stream connection with the fourth communication entity, the system receives stream data units sent by the fourth communication entity, the stream data units including performance data of the second communication entity corresponding to the DN of the second communication entity.

9. The method according to claim 7, characterized in that, When the reporting indication information indicates that the third communication entity expects to receive data in a file data format, the method further includes: After subscribing to the file with the fourth communication entity, a notification file is received from the fourth communication entity, the notification file including the performance data of the second communication entity corresponding to the DN of the second communication entity.

10. The method according to claim 6, characterized in that, When the second request message includes the instance ID of the second communication entity, after receiving the second feedback message sent by the first communication entity, the method further includes: Send a fourth request message to a fourth communication entity, the fourth request message being used to subscribe to information, the fourth request message including the DN of the second communication entity; The system receives first subscription information sent by the fourth communication entity, the first subscription information including at least one of the following: performance data of the second communication entity corresponding to the DN of the second communication entity, and a threshold notification related to the performance data of the second communication entity corresponding to the DN of the second communication entity.

11. The method according to claim 6, characterized in that, When the second request message includes the DN of the second communication entity, the configuration file also includes the instanceID of the second communication entity corresponding to the DN of the second communication entity.

12. The method according to claim 11, characterized in that, Before sending the second request message to the first communication entity, the method further includes: Send a fifth request message to the fourth communication entity. The fifth request message is used to subscribe to information and includes the instance ID of the second communication entity. The system receives second subscription information sent by the fourth communication entity, the second subscription information including at least one of the following: performance data of the second communication entity corresponding to the DN of the second communication entity corresponding to the instance ID of the second communication entity, and a threshold notification related to the performance data of the second communication entity corresponding to the DN of the second communication entity corresponding to the instance ID of the second communication entity.

13. A communication entity, characterized in that, include: processor; The processor is configured to implement the method as described in any one of claims 1-12 when executing a computer program.

14. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1-12.

Images