WO2023174287A1 - 一种时延分析方法及装置 - Google Patents

一种时延分析方法及装置 Download PDF

Info

Publication number
WO2023174287A1
WO2023174287A1 PCT/CN2023/081381 CN2023081381W WO2023174287A1 WO 2023174287 A1 WO2023174287 A1 WO 2023174287A1 CN 2023081381 W CN2023081381 W CN 2023081381W WO 2023174287 A1 WO2023174287 A1 WO 2023174287A1
Authority
WO
WIPO (PCT)
Prior art keywords
delay
analysis
transmission
data
information
Prior art date
Application number
PCT/CN2023/081381
Other languages
English (en)
French (fr)
Inventor
黄谢田
曹龙雨
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2023174287A1 publication Critical patent/WO2023174287A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0677—Localisation of faults
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition

Definitions

  • the present application relates to the field of communication technology, and in particular, to a delay analysis method and device.
  • 5G fifth generation
  • CPE customer premises equipment
  • CPE can be used as a terminal device to connect to access network equipment through wireless technology to obtain wireless network services; on the other hand, it can be used as a wireless access point to provide services for other terminal devices, such as programmable Logic controller (programmable logic controller, PLC), camera, etc., provide wireless access function.
  • programmable Logic controller programmable logic controller, PLC
  • the CPE can provide forwarding services for data packets of multiple communication services. If a data packet of a communication service has a large delay problem, for example, the CPE has an uplink problem when forwarding video backhaul services. Packets are lost or out of order, but data packets of other communication services are transmitted normally.
  • the final diagnostic analysis result may be that the CPE has no abnormal problems, which will lead to inaccurate fault diagnosis analysis results.
  • This application provides a delay analysis method and device to improve the accuracy of delay analysis and improve the accuracy of delay fault location.
  • the present application provides a delay analysis method, which can be used to implement the function of the delay data analysis entity side.
  • the embodiments of the present application are not limited to the specific execution subject of the method. Taking this method applied to the delay data analysis entity as an example, in this method, the delay data analysis entity receives business information and analysis rule information from the delay data requesting entity; wherein the business information is used to indicate the waiting time.
  • the analysis rule information is used to indicate the analysis rules used to perform delay analysis on the communication services;
  • the delay data analysis entity obtains multiple delay measurements of data packets of the communication services Data, wherein each piece of delay measurement data indicates the transmission duration of at least one transmission stage of the data packet of the communication service in the transmission path;
  • the delay data analysis entity is based on the analysis rules and the plurality of delays The measured data obtains a delay analysis result;
  • the delay analysis result is used to indicate a transmission stage in which a delay failure exists in the communication service in the transmission path.
  • communication services include but are not limited to: video services (such as video surveillance backhaul services), remote Control the business.
  • the transmission path can be a path between the user premises equipment and the UPF, that is, the data packet of the communication service is transmitted between the user premises equipment and the user plane function (UPF), where the user premises equipment can be The terminal equipment to which this communication service belongs provides wireless access functions.
  • UPF user plane function
  • the analysis rules are configured by the delay data requesting entity to the delay data analysis entity.
  • the delay measurement data of each transmission stage of the communication service in the transmission path can be analyzed. Analysis is performed to determine whether there is a delay fault in each transmission stage of the communication service. Therefore, the results of the delay analysis are more accurate and the delay fault can be accurately located.
  • it is based on delay measurement data analysis at a finer granularity (i.e., service granularity). In this way, if fault diagnosis analysis is required, delay analysis at the granularity of the communication service can be performed based on the delay measurement data of the communication service. This can overcome the problem of inaccurate performance data analysis results based solely on wireless network air interfaces, and compared with device-level delay analysis, the above technical solution improves the accuracy of delay analysis.
  • the transmission stage corresponds to a first delay threshold
  • the first rule includes: for any transmission stage in the transmission path, if the delay measurement data corresponding to the transmission stage in the plurality of delay measurement data is greater than or equal to the third delay measurement data corresponding to the transmission stage.
  • a delay threshold then the communication service has a delay fault in the transmission phase; if the corresponding delay measurement data in the plurality of delay measurement data in the transmission phase is less than the corresponding delay measurement data in the transmission phase
  • a delay threshold then there is no delay failure in the communication service during the transmission phase.
  • the first delay threshold is indicated by the analysis rule information; or the first delay threshold is the history of the transmission phase corresponding to the first delay threshold. Determined by delay measurement data; or, the first delay threshold is configured by the knowledge management entity.
  • the transmission stage corresponds to a second delay threshold
  • the second rule includes: for any transmission stage in the transmission path, if the delay measurement data corresponding to the transmission stage in the plurality of delay measurement data is consistent with the communication service in the transmission path If the ratio of the total delay in is greater than or equal to the second delay threshold corresponding to the transmission stage, then the communication service has a delay fault in the transmission stage; if the transmission stage is in the multiple delay If the ratio of the corresponding delay measurement data in the measurement data to the total delay is less than the second delay threshold corresponding to the transmission stage, then there is no delay fault in the communication service during the transmission stage.
  • the second delay threshold is indicated by the analysis rule information; or the second delay threshold is configured by the knowledge management entity.
  • the latency data requesting entity may also send one or more of the following information to the latency data analysis entity:
  • Analysis type information of communication services Analysis granularity information of communication services; data flow direction information; analysis time information; identification information of measurement equipment; threshold information.
  • the analysis type information is used to indicate the requested delay analysis type.
  • the delay analysis type may be "E2E delay analysis”.
  • the delay analysis type indicated by the analysis type information is "E2E delay analysis”
  • There may also be other types of delay analysis including but not limited to: coverage problem analysis, communication service experience analysis, network slicing load analysis, fault prediction, MDA-assisted energy saving, etc.
  • the analysis granularity information is used to indicate the granularity of delay analysis.
  • the granularity of delay analysis may be "business-level (or service flow)" delay analysis.
  • the granularity of delay analysis may also exist at other granularities, such as network slice-level delay analysis.
  • the analysis granularity information can also be indicated by the analysis type information.
  • the delay analysis type indicated by the analysis type information is "Business Level E2E Delay Analysis” or "Business Flow E2E Delay Analysis”
  • the delay measurement data of data packets in the E2E transmission path, and the analysis granularity is "service level (or service flow)".
  • the data flow direction information is used to indicate the transmission direction of the data packets of the communication service that needs to be analyzed, and may be at least one of uplink and downlink.
  • the analysis time information is used to indicate the time to perform delay analysis on the communication service, that is, to indicate in which time period to perform delay analysis on the communication service or at which time to start delay analysis on the communication service.
  • the analysis time information includes: at least one of analysis start time, analysis end time, and analysis duration.
  • the time indicated by the analysis time information may be before the time to determine the delay analysis of the communication service. That is to say, the delay data requesting device may request to analyze the historical delay measurement data of the communication service, so that the time delay can be performed. Delay measurement data for delay analysis comes from a wider range of sources, which can improve the accuracy of delay analysis.
  • the identification information of the measurement device is used to indicate a device that measures delay measurement data of data packets of the communication service.
  • the measurement device may include at least one of an access network device, a UPF, or a CPE.
  • the threshold information is used to indicate the first delay threshold or the second delay threshold corresponding to each transmission stage in the transmission path of the communication service.
  • the method further includes: The delay data analysis entity sends root cause request information and delay analysis results to the knowledge management entity.
  • the root cause request information is used to request root causes corresponding to the M transmission stages where delay faults exist; the delay data analysis entity receives data from all
  • the root cause indication information of the knowledge management entity is used to indicate the root cause of the delay failure in each of the M transmission stages.
  • the root cause of the delay fault is queried through the knowledge management entity, and the root cause can be determined quickly and efficiently.
  • the transmission stage in which the delay analysis result indicates that there is a delay failure includes one or more of the following: wireless access network transmission stage; core network transmission stage; transmission network transmission stage; user premises equipment Transmission phase; air interface transmission phase.
  • the method further includes: The delay data analysis entity sends fault resolution request information to the knowledge management entity, the fault resolution request information includes the delay analysis result, and the fault resolution request information is used to request resolution of the delay faults in the M transmission stages. ; The delay data analysis entity receives fault solution information from the knowledge management entity, and the fault solution information includes network configuration actions for solving delay faults in the M transmission stages and/or for Network configuration parameters that solve the delay failure of the M transmission stages.
  • the delay fault can be quickly solved by querying the fault solution information of the delay fault through the knowledge management entity.
  • the method further includes: The delay data analysis entity sends at least one of the following information to the delay data requesting entity: the delay analysis result; root cause indication information, and the root cause indication information is used to indicate each of the M transmission stages.
  • the root causes of delay faults in the M transmission stages; fault solution information, the fault solution information includes the network used to solve the delay faults in the M transmission stages Configure actions and/or network configuration parameters for solving delay failures in the M transmission stages.
  • this application provides a delay analysis method, which can be used to implement functions on the entity side of delay data requesting.
  • the embodiments of this application are not limited to the specific execution subject of this method.
  • the delay data requesting entity determines service information and analysis rule information; wherein the service information is used to indicate the communication service to be delayed analyzed;
  • the analysis rule information is used to indicate the analysis rules used to perform delay analysis on the communication service;
  • the delay data requesting entity sends the service information and the analysis rule information to the delay data analysis entity; the delay
  • the data requesting entity receives a delay analysis result from the delay data analysis entity, and the delay analysis result is used to indicate a transmission stage in which a delay failure exists in the transmission path of the communication service.
  • the transmission stage corresponds to a first delay threshold
  • the first rule includes: for any transmission stage in the transmission path, if the delay measurement data corresponding to the transmission stage in the plurality of delay measurement data is greater than or equal to the first time delay corresponding to the transmission stage, delay threshold, then the communication service has a delay fault in the transmission phase; if the corresponding delay measurement data in the plurality of delay measurement data in the transmission phase is less than the first time corresponding to the transmission phase delay threshold, then there is no delay fault in the communication service during the transmission phase.
  • the first delay threshold is indicated by the analysis rule information; or the first delay threshold is the history of the transmission phase corresponding to the first delay threshold. Determined by delay measurement data; or, the first delay threshold is configured by the knowledge management entity.
  • the transmission stage corresponds to a second delay threshold
  • the second rule includes: for any transmission stage in the transmission path, if the delay measurement data corresponding to the transmission stage in the plurality of delay measurement data is consistent with the delay measurement data of the communication service in the transmission path If the ratio of the total delay is greater than or equal to the second delay threshold corresponding to the transmission phase, then the communication service has a delay fault in the transmission phase; if the multiple pieces of delay measurement data in the transmission phase If the ratio of the corresponding delay measurement data to the total delay is less than the second delay threshold corresponding to the transmission stage, then there is no delay fault in the communication service during the transmission stage.
  • the second delay threshold is indicated by the analysis rule information; or the second delay threshold is configured by the knowledge management entity.
  • the transmission stage in which the delay analysis result indicates that there is a delay failure includes one or more of the following: wireless access network transmission stage; core network transmission stage; transmission network transmission stage; user premises equipment Transmission phase; air interface transmission phase.
  • the method further includes:
  • the delay data requesting entity receives at least one of the following information from the delay data analysis entity: root cause indication information.
  • the root cause indication information is used to indicate the existence of each transmission stage in the M transmission stages.
  • the root cause of the delay fault includes network configuration actions used to solve the delay fault of the M transmission stages and/or used to solve the delay of the M transmission stages Faulty network configuration parameters.
  • the method further includes: the delay data requesting entity generating a solution based on at least one of the delay analysis results, the root cause indication information and the fault solution information. Indication information of delay failure of the communication service in the M transmission stages.
  • embodiments of the present application provide a delay data analysis entity, which has the function of realizing the first aspect.
  • the delay data analysis entity includes modules or units or means that perform the steps involved in the first aspect.
  • the functions, units or means can be implemented by software, or by hardware, or by hardware. Execute the corresponding software implementation.
  • the delay data analysis entity includes a processing unit and a communication unit, where the communication unit can be used to send and receive signals to achieve communication between the delay data analysis entity and other devices; the processing unit Can be used to perform some internal operations of this latency data analysis entity.
  • the communication unit is used to receive service information and analysis rule information from the delay data requesting entity; wherein the service information is used to indicate the communication service to be delayed analyzed; the analysis The rule information is used to indicate the analysis rules used for delay analysis; obtain multiple pieces of delay measurement data of the data packet of the communication service, wherein each piece of delay measurement data indicates that the data packet of the communication service is in the transmission path The transmission duration of at least one transmission phase; a processing unit configured to obtain a delay analysis result based on the analysis rules and the plurality of delay measurement data; the delay analysis result is used to indicate that the communication service is in the The transmission phase where there is a delay fault in the transmission path.
  • the delay data analysis entity includes a processor and may also include a transceiver, the transceiver is used to send and receive signals, and the processor executes program instructions to complete any possibility in the first aspect.
  • the delay data analysis entity may also include one or more memories, the memories being used to couple with the processor, and the memories may store necessary computer programs or instructions to implement the functions involved in the first aspect.
  • the processor can execute the computer program or instructions stored in the memory. When the computer program or instructions are executed, the delay data analysis entity implements any possible design or implementation in the first aspect. method.
  • the delay data analysis entity includes a processor, and the processor can be coupled to a memory.
  • the memory may store necessary computer programs or instructions to implement the functions involved in the first aspect.
  • the processor can execute the computer program or instructions stored in the memory. When the computer program or instructions are executed, the delay data analysis entity implements any possible design or implementation in the first aspect. method.
  • the delay data analysis entity includes a processor and an interface circuit, wherein the processor is configured to communicate with other devices through the interface circuit and execute any possible design or implementation in the first aspect. method within the method.
  • inventions of the present application provide a delay data request entity.
  • the delay data request entity has the function of implementing the above second aspect.
  • the delay data request entity includes performing the steps involved in the above second aspect.
  • the modules, units or means of the steps, the functions, units or means can be implemented by software, or implemented by hardware, or can also be implemented by hardware executing corresponding software.
  • the delay data requesting entity includes a processing unit and a communication unit, where the communication unit can be used to send and receive signals to achieve communication between the delay data requesting entity and other devices; the processing unit Can be used to perform some internal operations of the delay data request entity.
  • the processing unit is configured to determine service information and analysis rule information; wherein the service information is used to indicate the communication service to be analyzed for delay; and the analysis rule information is used to indicate delay analysis.
  • the adopted analysis rules a communication unit for sending the business information and the analysis rule information to the delay data analysis entity; receiving the delay analysis results from the delay data analysis entity, the delay analysis results used to indicate the The communication service has a transmission phase with delay failure in the transmission path.
  • the delay data request entity includes a processor, and may also include a transceiver, the transceiver is used to send and receive signals, and the processor executes program instructions to complete any possibility in the second aspect above.
  • the delay data request entity may also include one or more memories, the memory being used to couple with the processor, and the memory may store the necessary computer programs or instructions to implement the functions involved in the second aspect.
  • the processor can execute the computer program or instructions stored in the memory. When the computer program or instructions are executed, the delay data requesting entity implements any possible design or implementation in the second aspect. method.
  • the latency data request entity includes a processor, and the processor can be coupled to the memory.
  • the memory may store necessary computer programs or instructions to implement the functions related to the second aspect above.
  • the processor can execute the computer program or instructions stored in the memory. When the computer program or instructions are executed, the delay data requesting entity implements any possible design or implementation in the second aspect. method.
  • the delay data request entity includes a processor and an interface circuit, wherein the processor is configured to communicate with other devices through the interface circuit and execute any possible design or implementation in the second aspect. method within the method.
  • the processor can be implemented by hardware or software.
  • the processor can be a logic circuit, an integrated circuit, etc.; when implemented by software,
  • the processor may be a general-purpose processor implemented by reading software code stored in memory.
  • the above processors may be one or more, and the memories may be one or more.
  • the memory can be integrated with the processor, or the memory can be provided separately from the processor. During the specific implementation process, the memory and the processor can be integrated on the same chip, or they can be respectively provided on different chips. The embodiments of this application do not limit the type of memory and the arrangement method of the memory and the processor.
  • embodiments of the present application provide a communication system, which includes the delay data analysis entity provided in the third aspect and the delay data requesting entity provided in the fourth aspect.
  • a sixth aspect provides a computer-readable storage medium for storing a computer program, the computer program including instructions for executing the method in the first aspect or any possible implementation of the first aspect.
  • a computer-readable storage medium for storing a computer program.
  • the computer program includes instructions for executing the method in the second aspect or any possible implementation of the second aspect.
  • a computer program product includes: computer program code.
  • the computer program code When the computer program code is run on a computer, it causes the computer to execute the above first aspect or any one of the first aspects. Methods in possible implementations.
  • a computer program product includes: computer program code.
  • the computer program code When the computer program code is run on a computer, it causes the computer to execute any one of the above second aspect and the second aspect. Methods in possible implementations.
  • the present application provides a chip.
  • the chip includes a processor.
  • the processor is coupled to a memory and is used to read and execute a software program stored in the memory to implement the above first to second aspects. any possible design approach.
  • Figure 1 is a schematic diagram of a network architecture suitable for embodiments of the present application.
  • FIG. 2 is a schematic diagram of another network architecture suitable for embodiments of the present application.
  • Figure 3 is a schematic flow chart of a delay analysis method provided by an embodiment of the present application.
  • Figure 4 is a schematic flow chart of a delay analysis method provided by an embodiment of the present application.
  • Figure 5 is a schematic flow chart of a delay analysis method provided by an embodiment of the present application.
  • Figure 6 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • Figure 7 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • the technical solution provided by this application can be applied to various communication systems, such as: new radio (new radio, NR) system, long term evolution (long term evolution, LTE) system, etc.
  • the technical solution provided by this application can also be applied to future communication systems, such as the sixth generation mobile communication system.
  • Terminal equipment It can be called user equipment (UE), mobile device, user terminal, terminal, wireless communication equipment, user agent or user device, etc.
  • the terminal device may be a device that provides voice/data to users, for example, a handheld device with wireless connection function, a vehicle-mounted device, etc.
  • some examples of terminal devices are: mobile phones, tablets, laptops, PDAs, PLCs, cameras, mobile internet devices (MID), wearable devices, virtual reality (VR) ) equipment, augmented reality (AR) equipment, wireless terminals in industrial control, wireless terminals in self-driving, wearable devices, terminal equipment in 5G networks or future evolutions
  • Terminal equipment in a public land mobile communication network public land mobile network, PLMN
  • PLMN public land mobile network
  • the device used to realize the function of the terminal device may be a terminal device; it may also be a device capable of supporting the terminal device to realize the function, such as a chip system, a hardware circuit, a software module, or a hardware circuit plus a software module.
  • the device can be installed in the terminal equipment or can be used in conjunction with the terminal.
  • the technical solution provided by the present disclosure will be described below by taking the device for realizing the functions of the terminal device as a terminal device as an example.
  • User premises equipment can also be called industry terminal equipment. On the one hand, it can be used as a terminal equipment to connect to access network equipment through wireless technology to obtain wireless network services; on the other hand, it can be used as a wireless access point to provide other terminal equipment (such as PLC, camera, etc.) provide wireless access function.
  • the embodiment of this application mainly takes the user premises equipment as CPE as an example for illustrative description. Other user premises equipment similar to CPE is also applicable to the embodiment of this application.
  • Radio access network (RAN) equipment also known as access network equipment, can provide authorized users in a specific area with the function of accessing communication networks. Specifically, it can include the 3rd generation partnership program (3rd generation partnership program). Wireless network devices in project, 3GPP) networks may also include access points in non-3GPP (non-3GPP) networks.
  • 3rd generation partnership program 3rd generation partnership program
  • the access network equipment may be a base station (base station), an evolved base station (evolved NodeB, eNodeB), a transmission reception point (TRP), a next generation base station (next generation NodeB, gNB) in the 5G mobile communication system, Access network equipment in the open radio access network (O-RAN), next-generation base stations in the sixth generation (6G) mobile communication system, future mobile A base station in a communication system or an access node in a wireless fidelity (WiFi) system, etc.; or the access network device can be a module or unit that completes some functions of the base station, for example, it can be a centralized unit (central unit, CU), distributed unit (DU), centralized unit control plane (CU control plane, CU-CP) module, or centralized unit user plane (CU user plane, CU-UP) module.
  • This disclosure does not limit the specific technology and specific equipment form used by the access network equipment.
  • abnormal events may refer to abnormal events at business granularity.
  • Abnormal events at business granularity include: video freezes corresponding to communication services, or control delay abnormalities corresponding to communication services, etc.
  • the video freeze corresponding to the communication service may be: when the communication service is a video backhaul service, the video played by the video service server corresponding to the communication service appears to be blurry or stuck.
  • the abnormal control delay corresponding to the communication service may be: when the communication service is a remote control service, the control command sent by the control service server corresponding to the communication service to the terminal device has a large delay in reaching the terminal device (for example, greater than the average data transmission delay) Or the terminal device takes a long time to respond after receiving the command (such as greater than the average response time), etc.
  • Delay analysis can refer to analyzing whether there is a delay fault during the transmission process of data packets or data flows of communication services, and when it is determined that a delay fault exists, determining the specific information of the delay fault, such as determining the root cause of the delay fault. and troubleshooting information, etc.
  • Delay failure refers to a failure that causes the delay of the communication service to be too high/large and does not meet the delay requirements of the communication service. For example, if the delay requirement of the communication service is less than or equal to the preset threshold, if the communication service If the service delay is greater than the preset threshold, a delay failure occurs.
  • the network architecture applicable to this application is briefly introduced.
  • Figure 1 it is a schematic diagram of the network architecture applicable to the embodiment of this application.
  • the network architecture shown in Figure 1 can be applied to communication business scenarios under 5G toB.
  • the terminal device when the terminal device is a camera, the user premises equipment (the user premises equipment is a CPE in Figure 1 as an example) can provide video surveillance backhaul services for one or more cameras;
  • the terminal device is a PLC
  • the user premises equipment can provide access and data transmission functions for the remote control service flow of the PLC.
  • Other cases will not be explained one by one. Among them, it can be understood that only three terminal devices, namely terminal device 1 to terminal device 3, are shown in FIG. 1.
  • the embodiment of the present application does not limit the number of terminal devices.
  • the core network side can include a variety of core network elements, such as access and mobility management function (AMF), session management function (SMF), Network exposure function (NEF) and user plane function (UPF), etc.
  • AMF access and mobility management function
  • SMF session management function
  • NEF Network exposure function
  • UPF user plane function
  • the definitions and functions of the above-mentioned core network elements can be referred to the descriptions in the 3GPP standard specifications, and will not be described again here.
  • the above network architecture may also include other possible entities, which will not be described again here.
  • the 3GPP logical management architecture includes two types of management systems, namely the network management system (NMS) and the element management system (EMS).
  • EMS can include functional entities that manage network elements of wireless networks (such as gNB, gNB-CU-CP, gNB-CU-UP, gNB-DU, etc.), and NMS can include functions for operators to implement cross-domain network management.
  • entity such as gNB, gNB-CU-CP, gNB-CU-UP, gNB-DU, etc.
  • EMS can include functions for operators to implement cross-domain network management.
  • EMS may be used to manage network elements within a certain area, and NMS can manage multiple areas within the management scope of EMS.
  • EMS is used for network element management of the wireless network domain, and NMS can manage both the wireless network domain and the core network domain.
  • the network architecture can include management data analytics (MDA) management service (MnS) consumer entities, MDA MnS producer entities, knowledge management (KM) entities and data Manage service producer entities, etc.
  • MDA MnS management data analytics
  • MDA MnS management service
  • KM knowledge management
  • MDA MnS management service
  • the producer entity can perform delay analysis to determine whether there is a delay failure, etc., and provide the analysis results to the MDA MnS consumer entity for decision-making or further analysis.
  • the functions of the MDA MnS producer entity can be realized through the management data analytics function (MDAF).
  • MDAF management data analytics function
  • the MDA MnS consumer entity can request the MDA MnS producer to perform delay analysis.
  • the functions of the MDA MnS consumer entity can be realized through the wireless terminal equipment management function (wireless terminal equipment management function, WTEMF).
  • WTEMF can provide online registration, parameter configuration, performance management, fault management and other operations for terminal equipment connected to user premises equipment (such as CPE).
  • CPE user premises equipment
  • WTEMF can serve as the MDA MnS consumer entity and request the MDA MnS producer entity to perform delay analysis. For example, it can determine whether there is a delay fault based on the analysis results, and determine the execution of operations to solve the delay fault.
  • the data management service producer entity can be used to collect delay measurement data from user premises equipment, access network equipment, UPF, etc., and provide it to the MDA MnS producer entity.
  • Knowledge management entities can be used to provide knowledge query functions or problem analysis functions for other management entities (such as MDA MnS producer entities).
  • Knowledge management entities can include knowledge bases, which store knowledge data that deal with various problems. For example: Network maintenance and communication business experts continue to accumulate experience in the process of dealing with fault problems, forming a large number of cases, instructions, fault trees and other knowledge data. These knowledge data can be imported into the knowledge base to locate and model fault root causes. For probabilistic graph reasoning problems based on problem graphs, the root cause of a failure can be determined through numerical causal reasoning.
  • MDA MnS producer entity, MDA MnS consumer entity, KM entity and data management service producer entity can be deployed in the network management system (network management system, NMS) or network element management system (element management system, EMS).
  • NMS network management system
  • EMS network element management system
  • Data management service producer entity and knowledge management entity are optional entity modules. It can be understood that each entity in the NMS/EMS can be deployed as an independent entity, or multiple entities can be integrated or deployed as one entity (that is, one entity can implement the functions of multiple entities).
  • the entities described in the embodiments of this application can also be called functional entities or network elements.
  • the above-mentioned entities can be either network elements in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (eg, cloud platform).
  • a platform eg, cloud platform
  • the above entity can be implemented by one device, or can be implemented by multiple devices together, or can be a functional module in one device, which is not specifically limited in the embodiments of this application.
  • an end-to-end (E2E) network can be formed from the service server to the user premises equipment.
  • the transmission path in the E2E network can be divided into multiple transmission stages.
  • Figure 2 it is a schematic diagram of another network architecture suitable for embodiments of the present application.
  • An E2E network is formed between the user premises equipment and the UPF.
  • the transmission path between the user premises equipment and the UPF can be divided into the following five transmission stages:
  • User premises equipment transmission stage air interface transmission stage; wireless access network transmission stage; transmission network transmission stage; core network transmission stage.
  • the user premises equipment transmission stage may refer to the stage in which data packets of communication services are transmitted or processed within the user premises equipment.
  • the transmission duration of the data packet of the communication service in the transmission phase of the user premises equipment is: the duration from the time when the user premises equipment receives the data packet to the time when the user premises equipment sends the data packet.
  • the air interface transmission stage may refer to the stage in which communication service data packets are transmitted between user premises equipment and access network equipment.
  • the transmission duration of data packets of communication services in the air interface transmission phase is: the duration from the time when the user premises equipment sends the data packet to the time when the access network equipment receives the data packet, or, when the access network equipment sends data The length of time between the time of the packet and the time when the customer premises equipment receives the data packet.
  • the radio access network transmission stage may refer to the stage in which data packets of communication services are transmitted or processed within the access network equipment.
  • the transmission duration of a communication service data packet in the wireless access network transmission phase is: the duration from the time the access network device receives the data packet to the time the access network device sends the data packet.
  • the transmission network transmission stage may refer to the stage in which data packets of communication services are transmitted between the UPF and the access network equipment.
  • the transmission duration of communication service data packets in the transmission network transmission phase is: the duration from the time when the UPF sends the data packet to the time when the access network device receives the data packet, or, when the access network device sends the data packet The duration between the time of and the time when UPF receives the data packet.
  • the core network transmission stage may refer to the stage in which communication service data packets are transmitted or processed within the UPF.
  • the transmission duration of communication service data packets in the core network transmission phase is: the duration from the time when the UPF receives the data packet to the time when the UPF sends the data packet.
  • the network fault management mechanisms defined in the 3GPP standards are mainly aimed at fault management of network equipment and do not support the management of terminal equipment faults. Therefore, in the traditional delay fault analysis method, the entities in the EMS cannot accurately locate the fault point where the delay fault actually occurs, resulting in the inability to quickly locate the delay fault and reducing the stability of the network.
  • a large number of user premises equipment (such as CPE, etc.) will be deployed in the private network of the enterprise campus.
  • the CPE serves as a wireless access point, it can provide data packets for multiple communication services. Providing forwarding services. If a communication service data packet has a large delay problem, for example, the CPE experiences uplink packet loss or disorder when forwarding the video backhaul service, but the data packets of other communication services are transmitted normally. If the traditional delay fault analysis method is followed, the average delay of data packets of all communication services on the CPE is counted, and the real data packet delay of each communication service flow is averaged.
  • the final diagnostic analysis result may be that the CPE There are no abnormal problems, which will lead to inaccurate fault diagnosis and analysis results. Therefore, in this case, it is impossible to locate the actual abnormal fault point simply by analyzing the air interface problem of the wireless network.
  • this application proposes a solution that can perform statistics on delay measurement data based on the communication service flow granularity, and perform delay fault analysis on each transmission stage based on the delay measurement data at the communication service flow granularity, thereby supporting implementation E2E delay fault delimitation.
  • each function or network element in Figures 1 to 2 such as MDA MnS producer entity, MDA MnS consumer entity, AMF, SMF, UPF and other functions or network elements, can be understood as being used to implement different functions.
  • Network elements can be independent devices, or they can be integrated into the same device to implement different functions. They can be network elements in hardware devices, software functions running on dedicated hardware, or platforms ( For example, a virtualization function instantiated on a cloud platform). This application does not limit the specific form of the above network elements.
  • the delay data request entity can be the MDA MnS consumer entity in Figure 1
  • the delay data analysis entity can be is the MDA MnS producer entity in Figure 1.
  • the delay data requesting entity can instruct the delay data analysis entity to obtain the delay measurement data of the data packets of the communication service at each transmission stage in the transmission path, thereby determining whether there is a delay in the communication service at each transmission stage in the transmission path. Fault.
  • the network side determines that an abnormal event occurs in the communication service, it analyzes the real-time delay measurement data of the communication service, that is, post-event analysis.
  • the delay measurement data of the communication service is obtained.
  • the time period before and/or the time when the abnormal event occurs is monitored. Or perform delay analysis on the delay measurement data for a later period of time, which are described below.
  • FIG. 3 it is a schematic diagram of a delay analysis method provided by an embodiment of the present application.
  • the method includes:
  • the delay data requesting entity can perform measurement configuration, specifically:
  • the delay data requesting entity sends a measurement identifier to the measurement device.
  • the delay data requesting entity can send multiple measurement identifiers.
  • the specific number of measurement identifiers is not limited.
  • One measurement identifier is used to associate with one communication service.
  • the data of a communication service can be transmitted through communication service data flow (data flow), and a communication service can correspond to one or more communication service data flows.
  • communication services may include but are not limited to: video communication services (such as video surveillance backhaul services), remote control communication services, etc.
  • video communication services such as video surveillance backhaul services
  • remote control communication services can include smart mine remote control communication services, robot inspection services, and unmanned overhead crane services.
  • smart port smart tally business etc.
  • the measurement identifier which can also be called a coloring identifier, is used to associate with the communication service to be analyzed for delay, and can be used to identify the communication service to be measured.
  • the measurement identifier may be a special character or data, or the measurement identifier may be an identifier of the communication service associated with it (such as an Internet Protocol (IP) 5-tuple of the communication service).
  • IP Internet Protocol
  • the measurement device may be a device included in the transmission path of the communication service.
  • the transmission path of the communication service is from the user premises equipment to the UPF
  • the measurement device may include one or more of the following : UPF, access network equipment, or user premises equipment (such as CPE).
  • the transmission path of the communication service may include multiple transmission stages.
  • the transmission path of the communication service may include the following transmission stages: radio access network transmission stage; Core network transmission stage; transmission network transmission stage; user premises equipment transmission stage; air interface transmission stage.
  • the specific meaning of each of the above transmission stages can be referred to the previous description, and will not be described again here.
  • the delay data request entity sends the measurement identification to the measurement device, which may include: delay data request The entity directly sends the measurement identifier to the measurement device, or may include a delay data requesting entity sending the measurement identifier to the measurement device through other devices. This application is not limited to this.
  • the measurement device after the measurement device obtains the measurement identification, it can associate the measurement identification with the communication service.
  • Associating the measurement identifier with the communication service may also be replaced by associating the measurement identifier with the data packet of the communication service, or may be replaced by using the measurement identifier to color the data packet of the communication service.
  • the measurement device associates the measurement identifier with the communication service, or the measurement device dyes the data packets of the communication service. Then, when the measurement device needs to measure the delay measurement data of the communication service, it can measure the delay according to the measurement identifier. Accurately identify the data packets of the communication service to be measured.
  • different measurement equipment can measure the delay measurement data of communication service data packets at different transmission stages.
  • the user premises equipment when the transmission direction of communication service data packets is the uplink direction, the user premises equipment can measure the delay measurement data of the communication service data packets in the transmission phase of the user premises equipment, and the access network equipment can measure the delay measurement data of the communication service.
  • UPF can measure the delay measurement data of communication service data packets in the core network transmission stage and transmission network transmission stage; the transmission of communication service data packets
  • the user premises equipment When the direction is the downlink direction, the user premises equipment can measure the delay measurement data of the communication service data packets in the user premises equipment transmission phase and the air interface transmission phase.
  • the access network equipment can measure the communication service data packets in the wireless access network transmission phase.
  • UPF can measure the delay measurement data of the communication service data packets in the core network transmission phase.
  • One possible implementation method is to fill in (or add) a measurement identifier in the data packet of the communication service (such as the header field of the data packet). This application does not limit how to specifically associate measurement identifiers with communication services.
  • the delay data requesting entity can also send one or more of the following information to the measurement device: the identification of the communication service, the CPE identification corresponding to the communication service, or the identification of the terminal device.
  • the above one or more pieces of information and the measurement identifier and/or the measurement indication may be carried in the same signaling, or may be carried in different signaling, without limitation. The above information is described in detail below.
  • the identifier of the communication service can be used to identify (or identify) the communication service.
  • the identification of the communication service is the IP 5-tuple.
  • the identifier of the communication service may include: source IP address, source port, destination IP address, destination port, and the layer4 protocol.
  • the CPE identifier can be used to identify (or identify) the CPE, which is located in the transmission path of the communication service.
  • the CPE is the CPE accessed by the terminal device to which the communication service belongs.
  • the CPE identification can be any of the following: the CPE's equipment serial number (ESN), the CPE's IP address, the CPE's globally unique temporary user identification (globally unique temporary UE identity, GUTI), etc.
  • the identifier of the terminal device can be used to identify (or identify) the device to which the communication service belongs.
  • the above information may be collectively referred to as measurement information, or may also be referred to as a coloring policy (ColoredPolicy). That is to say, the measurement information may include at least one of: a measurement identifier, a data packet type of the communication service associated with the measurement identifier, an identifier of the communication service, a CPE identifier corresponding to the communication service, and an identifier of the terminal device.
  • the delay data requesting entity can first configure the measurement information, and then send the measurement information to the measurement device. Alternatively, other devices may configure the measurement information and then send the measurement information to the delay data requesting entity, and then the delay data requesting entity sends the measurement information to the measurement device.
  • S302 to S304 can be executed.
  • the delay data request entity sends a create data collection task request message to the data collection service producer entity.
  • the create data collection task request message is used to request the data collection service producer entity to create a data collection task.
  • the data collection task is used to collect data from the measurement device. Collect measured delay data of communication service data packets at each transmission stage in the transmission path.
  • the data collection service producer entity can be access network equipment, UPF, CPE, or the data management service producer entity described above.
  • the request message for creating a data collection task may include task configuration information corresponding to the data collection task.
  • the task configuration information may include one or more of the following information:
  • Measurement business information measurement indicator information; identification information of measurement equipment; data flow direction information.
  • the measurement service information is used to indicate the communication service that needs to be measured. It may be an identifier of the communication service that needs to be measured, or it may be a measurement identifier associated with the communication service.
  • the measurement indicator information is used to indicate the key performance indicator (KPI) for measuring the communication service.
  • KPI key performance indicator
  • the KPI may indicate that the delay measurement data of which transmission stages of the data packets of the communication service need to be measured in the transmission path.
  • the identification information of the measurement device is used to indicate a device that measures delay measurement data of data packets of the communication service.
  • the measurement device may include at least one of an access network device, a UPF, or a CPE.
  • the data flow direction information is used to indicate the transmission direction of the data packet that needs to be measured, and the transmission direction may include at least one of uplink and downlink.
  • a data collection task can be configured for a communication service, and a data collection task can also be assigned a task ID.
  • the task identifier can be assigned by the data management service producer entity or by the delay data requesting entity. This application is not limited to this.
  • the task ID of a communication service data collection task can uniquely identify the data collection task.
  • the data collection service producer entity sends a create data collection task response message to the delay data request entity.
  • the creation data collection task response message may include the task ID corresponding to the data collection task.
  • S304 The data collection service producer entity obtains delay measurement data from the measurement device.
  • the information included in the request message to create a data collection task is shown in Table 1.
  • the data management service producer entity can instruct the access network equipment, UPF and CPE to report the data packets transmitted in the uplink direction of the video backhaul service and transmit them in each transmission stage indicated by the measurement indicator information. Input delay measurement data.
  • the data management service producer entity obtains these delay measurement data, it can store the delay measurement data.
  • the delay data requesting entity determines the service information and analysis rule information.
  • the service information is used to indicate the communication service to be analyzed for delay.
  • the service information may be an identifier of the communication service to be analyzed for delay, or may be a measurement identifier associated with the communication service. It can be understood that if a data collection task is created in advance for the communication service to be delayed analyzed, the service information may also be a task identifier of the data collection task for the communication service.
  • the analysis rule information is used to indicate the analysis rules used for delay analysis.
  • the business server when the business server determines that an abnormal event occurs in the communication service, the business server can send a maintenance test request message to the delay data requesting entity.
  • the maintenance test request message includes the identification of the communication service.
  • the maintenance test request message can be used Yu requests maintenance testing of the communication service corresponding to the identifier.
  • maintenance testing may refer to collecting network performance data (such as delay measurement data) related to communication services, and analyzing network performance based on the collected network performance data to identify whether there are faults in the network.
  • the delay data requesting entity can determine the communication service to be analyzed for delay according to the identification of the communication service.
  • delay data requesting entity can also determine the communication service to be delayed analyzed through other methods, and this application is not limited to this.
  • the analysis rule indicated by the analysis rule information may be the first rule or the second rule.
  • the specific content of the first rule and the second rule please refer to the following:
  • the first rule may include: for any transmission stage in the transmission path of the communication service, if the delay measurement data corresponding to the transmission stage is greater than or equal to the first delay threshold corresponding to the transmission stage, then the communication service is in the transmission stage. There is a delay fault in the communication service; if the delay measurement data corresponding to the transmission stage is less than the first delay threshold corresponding to the transmission stage, then the communication service does not have a delay fault in the transmission stage.
  • the second rule may include: for any transmission stage in the transmission path of the communication service, if the ratio of the delay measurement data corresponding to the transmission stage to the total delay of the communication service in the transmission path is greater than or equal to the transmission stage If the corresponding second delay threshold is the corresponding second delay threshold, the communication service has a delay fault in the transmission stage; if the ratio of the delay measurement data corresponding to the transmission stage to the total delay of the communication service in the transmission path is less than the transmission If the second delay threshold corresponding to the stage is reached, then the communication service does not have a delay fault in the transmission stage.
  • this application does not limit how the delay data requesting entity specifically determines which analysis rule to adopt.
  • the delay data requesting entity may indicate that the first A rule is used to perform delay analysis; if the transmission duration of each transmission stage of the data packet in the transmission path is similar (for example, the transmission duration of the data packet in the two transmission stages differs within 10%), the delay data requesting entity can indicate that the data packet is used The second rule performs delay analysis.
  • the first delay threshold corresponding to each transmission stage in the transmission path of the communication service may be determined by the delay data requesting entity. .
  • the first delay threshold corresponding to each transmission stage in the transmission path of the communication service can be determined based on the historical delay measurement data of each transmission stage, and the specific determination process is not limited.
  • the first delay threshold corresponding to each transmission stage may be an agreed default value.
  • the first delay threshold corresponding to each transmission stage can be configured by the knowledge management entity.
  • the delay data analysis entity can send a delay threshold request message to the knowledge management entity.
  • the delay threshold request message includes analysis rule information.
  • the delay threshold request message can be used to request the configuration of a delay threshold corresponding to the analysis rule information;
  • the knowledge management entity may indicate to the delay data analysis entity the first delay threshold corresponding to each transmission stage in the transmission path of the communication service.
  • the second delay threshold corresponding to each transmission stage in the transmission path of the communication service may be determined by the delay data requesting entity. .
  • the second delay threshold corresponding to each transmission stage may be an agreed default value.
  • the second delay threshold corresponding to each transmission stage can be configured by the knowledge management entity. Specifically, the delay data analysis entity can send a delay threshold request message to the knowledge management entity.
  • the delay threshold request message Including analysis rule information, the delay threshold request message can be used to request the configuration of a delay threshold corresponding to the analysis rule information; accordingly, if the analysis rule information indicates the second rule, the knowledge management entity can indicate the communication service to the delay data analysis entity The second delay threshold corresponding to each transmission stage in the transmission path.
  • the delay data requesting entity sends business information and analysis rule information to the delay data analysis entity.
  • the delay data analysis entity receives the business information and analysis rule information from the delay data requesting entity.
  • the delay data requesting entity can also send one or more of the following information to the delay data analysis entity:
  • Analysis type information of communication services Analysis granularity information of communication services; data flow direction information; analysis time information; identification information of measurement equipment; threshold information.
  • the analysis type information is used to indicate the requested delay analysis type.
  • the delay analysis type may be "E2E delay analysis”.
  • the delay analysis type indicated by the analysis type information is "E2E delay analysis”
  • There may also be other types of delay analysis including but not limited to: coverage problem analysis, communication service experience analysis, network slicing load analysis, fault prediction, MDA-assisted energy saving, etc.
  • the analysis granularity information is used to indicate the granularity of delay analysis.
  • the granularity of delay analysis may be "business-level (or service flow)" delay analysis.
  • the granularity of delay analysis may also exist at other granularities, such as network slice-level delay analysis.
  • the analysis granularity information can also be indicated by the analysis type information.
  • the delay analysis type indicated by the analysis type information is "Business Level E2E Delay Analysis” or "Business Flow E2E Delay Analysis”
  • the delay measurement data of data packets in the E2E transmission path, and the analysis granularity is "service level (or service flow)".
  • the data flow direction information is used to indicate the transmission direction of the data packets of the communication service that needs to be analyzed, and may be at least one of uplink and downlink.
  • the analysis time information is used to indicate the time to perform delay analysis on the communication service, that is, to indicate in which time period to perform delay analysis on the communication service or at which time to start delay analysis on the communication service.
  • the analysis time information includes: at least one of analysis start time, analysis end time, and analysis duration.
  • the identification information of the measurement device is used to indicate a device that measures delay measurement data of data packets of the communication service.
  • the measurement device may include at least one of an access network device, a UPF, or a CPE.
  • the threshold information is used to indicate the first delay threshold or the second delay threshold corresponding to each transmission stage in the transmission path of the communication service.
  • the delay data analysis entity obtains multiple pieces of delay measurement data of data packets of the communication service.
  • Each piece of delay measurement data indicates at least one transmission stage of the data packet of the communication service in the transmission path.
  • transmission duration may be a path between the customer premises equipment and the UPF.
  • the delay data analysis entity can obtain the delay measurement data through the data collection service producer entity.
  • the following process can be included:
  • Implementation method 1 The data collection service producer entity obtains real-time delay measurement data:
  • the delay data analysis entity sends a data request message to the data collection service producer entity.
  • the data request message may include one or more of the following information:
  • Measurement business information measurement indicator information; identification information of measurement equipment; data flow direction information; measurement time information; and reporting cycle information.
  • the data collection service producer entity can be access network equipment, UPF, CPE, or the data management service producer entity described above.
  • the measurement service information is used to indicate the communication service that needs to be measured.
  • the measurement service information may be an identifier of the communication service to be analyzed for delay, or may be a measurement identifier associated with the communication service.
  • the measurement indicator information is used to indicate the key performance indicator (KPI) for measuring the communication service.
  • KPI key performance indicator
  • the KPI may indicate that the delay measurement data of which transmission stages of the data packets of the communication service need to be measured in the transmission path.
  • the identification information of the measurement device is used to indicate a device that measures delay measurement data of data packets of the communication service.
  • the measurement device may include at least one of an access network device, a UPF, or a CPE.
  • the data flow direction information is used to indicate the transmission direction of the data packet that needs to be measured, and the transmission direction may include at least one of uplink and downlink.
  • the measurement time information is used to indicate the time at which the data packets of the communication service are measured, that is, in which time period the data packets of the communication service are measured or at which time the data packets of the communication service are measured.
  • the measurement time information may be determined based on the analysis time information. For example, the time indicated by the measurement time information may be located after the time indicated by the analysis time information. For example, the time indicated by the analysis time information is T0, and the delay data analysis entity can measure data packets transmitted after T0 through the measurement time information indication.
  • the measurement time information includes: at least one of measurement start time, measurement end time, and measurement duration.
  • the reporting cycle information is used to indicate the cycle in which the data management service producer entity reports measurement delay data.
  • the data request message may also include other information, so no examples will be given here.
  • the data management service producer entity obtains the delay measurement data from the measurement device according to the data request message.
  • the information included in the data request message may be as shown in Table 2.
  • the data management service producer entity can obtain the delay measurement data of the data packets transmitted in the upstream direction of the video backhaul service from the access network equipment, UPF and CPE.
  • the obtained delay measurement data The data is the data at each transmission stage indicated by the measurement indicator information, and these delay measurement data are obtained by measuring the data packets of the video backhaul service between time T1 and time T2 by the access network equipment, UPF and CPE.
  • the delay measurement data corresponding to each transmission stage indicates the transmission duration, which can be determined based on the transmission duration of Y data packets in the transmission phase, Y is an integer greater than 0.
  • the measurement device may measure the transmission duration of Y data packets, and the measurement device may report the transmission duration of the Y data packets to the data management service producer entity.
  • the data management service producer entity can use the average of the Y transmission durations (or the median transmission duration of the Y transmission durations) as the transmission duration of the communication service in this transmission stage.
  • the data management service producer entity The transmission duration indicated by the reported delay measurement data is the average transmission duration of the Y data packets (or the median transmission duration of the Y transmission durations).
  • S403a The data management service producer entity sends multiple pieces of delay measurement data to the delay data analysis entity.
  • Implementation method two The data collection service producer entity has pre-stored the corresponding delay measurement data according to the data collection task of the communication service.
  • S401b The delay data analysis entity sends a data request message to the data collection service producer entity.
  • the information included in the data request message can implement the measurement task configuration message in manner 1, that is, the data request message can include one or more of the following information:
  • the data request message can include one or more of the following information:
  • Task identification corresponding to the communication service ; measurement time information; reporting cycle information.
  • the data collection service producer entity can determine at least one of the following information corresponding to the communication service based on the task identification: business information; measurement indicator information; identification information of the measurement equipment; and data flow direction information.
  • the time indicated by the measurement time information in the data request message in this step can be before the time to determine the delay analysis of the communication service. That is to say, the data request message can request to obtain the determination time.
  • Delay measurement data i.e., historical delay measurement data
  • the measurement time information is used to indicate measuring the delay measurement data of data packets transmitted between time T1 and time T2, and determining that the time for delay analysis of the communication service is T0. At this time, T1 may be located before T0.
  • S402b The data management service producer entity sends multiple pieces of delay measurement data to the delay data analysis entity.
  • the data management service producer entity has pre-stored the delay measurement data, so it can directly send the delay measurement data to the delay data analysis entity.
  • the delay measurement data of data packets of the communication service can be measured and stored in advance, so that when delay analysis of the communication service is required, the delay measurement data can be obtained in time and the efficiency of the delay analysis can be improved.
  • the delay data analysis entity can also obtain delay measurement data through other methods, and this application is not limited to this.
  • the delay data analysis entity obtains delay analysis results based on analysis rules and multiple pieces of delay measurement data.
  • the delay analysis result is used to indicate the transmission stage when the communication service has delay failure in the transmission path.
  • latency failure can also be replaced by latency issue.
  • the analysis rule may be the first rule or the second rule.
  • the delay data analysis entity can determine that the communication service has a delay fault in the transmission stage; if the corresponding delay measurement data in the multiple delay measurement data of the transmission stage is less than the transmission stage Corresponding to the first delay threshold, the delay data analysis entity can determine that there is no delay fault in the communication service during this transmission stage.
  • the delay analysis results may also include information such as the number or proportion of delay measurement data corresponding to each transmission stage that is greater than or equal to the first delay threshold corresponding to the transmission stage.
  • the delay analysis result may also include fault level information, and the fault level information is used to indicate the fault level of the transmission phase where delay faults exist.
  • the fault level can indicate the severity of the delay fault.
  • the fault level can include first-level faults and second-level faults. The severity of the first-level fault is higher than the severity of the second-level fault.
  • the fault level of the transmission stage is based on at least two pieces of delay measurement data. The number or proportion of delay measurement data that is greater than or equal to the first delay threshold corresponding to the transmission stage is determined.
  • the fault level is a first-level fault; if this If the number of delay measurement data in at least two pieces of delay measurement data that is greater than or equal to the first delay threshold corresponding to the transmission stage is less than the preset number, the fault level is a secondary fault.
  • the delay data analysis entity can determine that the communication service has a delay fault in the transmission stage; if the transmission stage is in multiple If the ratio of the corresponding delay measurement data in the delay measurement data to the total delay of the communication service in the transmission path is less than the second delay threshold corresponding to the transmission stage, the delay data analysis entity can determine the communication service There are no delay faults during this transmission phase.
  • the total delay of the communication service in the transmission path can be determined based on the delay measurement data of each transmission stage of the communication service in the transmission path, or can be reported to the delay data analysis by the data management service producer entity entity.
  • the delay analysis results may also include the delay measurement data corresponding to each transmission stage, which is greater than or equal to the second delay corresponding to the transmission stage. Information such as the quantity or proportion of threshold delay measurement data.
  • the delay analysis results may also include fault level information.
  • the transmission stage corresponds to at least two pieces of delay measurement data among multiple pieces of delay measurement data, for example, if the at least two pieces of delay measurement data are greater than or If the proportion of delay measurement data equal to the second delay threshold corresponding to the transmission stage is greater than or equal to the preset proportion, the fault level is a first-level failure; if at least two pieces of delay measurement data are greater than or equal to the transmission stage If the proportion of the delay measurement data corresponding to the second delay threshold is less than the preset proportion, the fault level is a secondary fault.
  • the analysis rules are configured by the delay data requesting entity to the delay data analysis entity.
  • the time of each transmission stage of the communication service in the transmission path can be analyzed.
  • the delay measurement data is analyzed to determine whether there is a delay fault in each transmission stage of the communication service. Therefore, the results of the delay analysis are more accurate and the delay fault can be accurately located.
  • the delay data analysis entity determines that the communication service has a delay fault in at least one transmission stage in the transmission path, the delay data analysis entity can also query the knowledge management entity for the root cause of the delay fault.
  • the fault resolution method can be specifically shown in Figure 5, which is a schematic diagram of a delay analysis method provided by the embodiment of the present application.
  • the delay data analysis entity sends root cause request information and delay analysis results to the knowledge management entity.
  • the delay analysis result indicates that the communication service has delay faults in M transmission stages in the transmission path, and M is an integer greater than 0; the root cause request information is used to request M delay faults. The root cause corresponding to the transmission stage.
  • the knowledge management entity sends root cause indication information to the delay data analysis entity.
  • the root cause indication information is used to indicate the root cause of the delay fault in each of the M transmission stages.
  • the knowledge management entity can include a root cause knowledge graph (or it can also be called a root cause fault tree).
  • the root cause knowledge graph includes information such as the correspondence between delay faults and root causes in each transmission stage.
  • the knowledge management entity can be based on The root cause knowledge graph determines the root cause of the delay failure in each of the M transmission stages.
  • the knowledge management entity can also determine the root cause of the delay failure in each transmission stage through other transmissions. This application does not limit how the knowledge management entity determines the root cause.
  • the knowledge management entity can also send the root cause knowledge graph to the delay data analysis entity, and the delay data analysis entity determines the root cause of the delay fault based on the root cause knowledge graph.
  • This application is not limited to this.
  • S503 The delay data analysis entity sends fault resolution request information to the knowledge management entity.
  • the fault resolution request information is used to request resolution of delay faults in M transmission stages.
  • S501 and S502 can be sent through one message, or they can be sent through different messages respectively.
  • the execution order of S501 and S502 is not limited. They can be executed at the same time or one after another.
  • the fault resolution request information may also include the delay analysis results.
  • S504 The knowledge management entity sends fault solution information to the delay data analysis entity.
  • the fault solution information includes at least one of the following information:
  • Network configuration actions used to solve the delay failure of the M transmission stages ; network configuration parameters used to solve the delay failure of the M transmission stages.
  • the network configuration action may refer to an action performed to configure the device in the network, and the network configuration parameter may refer to the parameters set to configure the device in the network.
  • the network configuration action can be: restart the CPE; when it is determined that the root cause of the delay failure is partial bandwidth part (BWP) switching due to a false alarm of downlink control information (DCI), the network configuration action can be: : Turn off the BWP switching function of the access network equipment, or the network configuration parameter can be: the value of the parameter "BWP switching of the access network equipment" is "off”.
  • the knowledge management entity may include information such as the correspondence between the root causes of delay failures in each transmission stage and network configuration actions, and the correspondence between the root causes of delay failures in each transmission stage and network configuration parameters.
  • the knowledge management entity Therefore, the fault solution information can be determined based on the above corresponding relationship.
  • the corresponding relationship between the root causes of delay failures and network configuration actions/or network configuration parameters in each transmission stage included in the knowledge management entity can be as shown in Table 3.
  • the knowledge management entity can determine the root cause corresponding to each transmission stage and the network configuration actions/or network configuration parameters based on the above corresponding relationship.
  • the delay data analysis entity sends at least one of delay analysis results, root cause indication information, and fault solution information to the delay data requesting entity.
  • the delay data analysis entity can also send other information to the delay data requesting entity, such as sending at least one of the following information:
  • Business information analysis type information of communication services; analysis granularity information of communication services; data flow direction information; analysis time information; identification information of measurement equipment.
  • the delay data requesting entity generates instruction information for solving delay faults in the M transmission stages of the communication service in the transmission path based on at least one of the delay analysis results, root cause indication information, and fault solution information.
  • the delay data requesting entity can deliver the instruction information to the network configuration action and /or the device corresponding to the network configuration parameter, for example, delivered to at least one of the access network device, CPE, or UPF.
  • the instruction information generated by the delay data requesting entity can instruct these devices to perform network configuration actions and/or follow the network configuration. Configure the configuration parameters to solve the delay failure of M transmission stages.
  • the delay data requesting entity may display the indication information to the operator in a visual interface, and the operator executes the network configuration action and/or the configuration command of the network configuration parameters indicated by the indication information.
  • the network configuration actions and/or network configuration parameters indicated by the indication information generated by the delay data request entity may be implemented in the following ways:
  • the delay data analysis entity sends the delay analysis results to the delay data requesting entity without sending root cause indication information and fault solution information
  • the delay data requesting entity can As a result, the root causes of delay faults in the M transmission phases are determined, and network configuration actions and/or network configuration parameters for solving the delay faults in the M transmission phases are determined based on the root causes of the delay faults in the M transmission phases.
  • the specific determination method is not limited.
  • the delay data requesting entity may request root causes of M transmission stages, network configuration actions, and/or network configuration parameters from the knowledge management device.
  • the root cause of the delay fault can be determined through manual troubleshooting.
  • the delay data requesting entity determines the network configuration action or network configuration parameters of the delay fault based on the determined root cause and manual experience.
  • the root cause indication information and the fault solution information can also be determined through other methods, which will not be described again here.
  • the network configuration actions and/or network configuration parameters indicated by the instruction information generated by the delay data analysis entity are determined by the delay data analysis entity based on the delay analysis results.
  • the delay data requesting entity can determine the solution based on the root cause indication information.
  • Network configuration actions and/or network configuration parameters for delay failures in the M transmission stages may request fault resolution information from the knowledge management device.
  • the delay data requesting entity determines network configuration actions and/or network configuration parameters for the delay fault based on root cause indication information and/or human experience.
  • the network configuration actions and/or network configuration parameters indicated by the indication information generated by the delay data analysis entity are determined by the delay data analysis entity based on the root cause indication information.
  • the delay data analysis entity sends fault solution information to the delay data requesting entity
  • the delay data requesting entity can directly send the network configuration action and/or network configuration indicated by the fault solution information.
  • Parameters serve as network configuration actions and/or network configuration parameters used to solve latency problems.
  • the network configuration actions and/or network configuration parameters indicated by the instruction information generated by the delay data analysis entity are determined by the delay data analysis entity based on the fault solution information.
  • the delay data analysis entity sends delay analysis results, root cause indication information and fault solution information to the delay data requesting entity
  • the delay data requesting entity can send the delay analysis result, root cause indication information and fault solution information according to the root cause indication information and /Or manual experience determines to correct the network configuration action and/or network configuration parameters indicated by the fault solution information, and delivers the corrected network configuration action and/or network configuration parameters to the corresponding device.
  • the network configuration actions and/or network configuration parameters indicated by the instruction information generated by the delay data analysis entity are determined by the delay data analysis entity based on fault solution information and/or manual experience.
  • CPE serves as a wireless access point to provide services for three terminal devices, where CPE is terminal device 1.
  • CPE is terminal device 1.
  • the application server detects the video freeze returned by the terminal device 1, so the application server sends a maintenance test request message to the delay data requesting entity, and in the maintenance test request The message carries the identity of the terminal device 1 or the identity of the video surveillance backhaul service.
  • the delay data request entity requests the delay data analysis entity to perform delay analysis on the video surveillance backhaul service. Specifically, it can send business information, analysis rule information, communication service analysis type information, and communication service analysis to the delay data analysis entity. Granularity information, data flow direction information, analysis time information, measurement device identification information, threshold information, etc.
  • the delay data analysis entity may determine based on the above information that it is necessary to perform delay analysis on the video surveillance backhaul service of the terminal device 1 .
  • the delay data analysis entity can obtain multiple pieces of delay measurement data from the data collection service producer entity.
  • the multiple pieces of delay measurement data are obtained by measurements of CPE, UPF, and access network equipment.
  • the delay data analysis entity performs delay analysis based on multiple pieces of measurement data, thereby determining that there is a delay failure in the CPE transmission phase of the video surveillance backhaul service.
  • the delay data analysis entity can determine through the knowledge management entity that the root cause of the delay failure may be uplink packet loss or disorder when the CPE transmits the video backhaul service.
  • the delay data analysis entity can determine, through the knowledge management entity, that the network configuration action contained in the root cause fault solution information is: restart the CPE.
  • the delay data analysis entity can return the fault solution information to the delay data requesting entity.
  • the delay data requesting entity can thus send instruction information to the CPE based on the fault solution information.
  • the instruction information is used to instruct the CPE to perform the following configuration actions: restart the CPE.
  • the application server detects that the video returned by the terminal device 1 is stuck, so the application server sends a maintenance test request message to the delay data requesting entity, and
  • the maintenance test request message carries the identity of the terminal device 1 or the identity of the video surveillance backhaul service.
  • the delay data requesting entity requests delay analysis of each communication service in the CPE from the delay data analysis entity. Specifically, the delay data requesting entity may instruct the delay data analysis entity to perform delay analysis between time T1 and time T2. All communication services are analyzed for delay, and time T0 is between time T1 and time T2.
  • the delay data analysis entity can determine the need to perform delay analysis on all communication services based on the above information.
  • the delay data analysis entity can obtain multiple pieces of delay measurement data from the data collection service producer entity.
  • the multiple pieces of delay measurement data are obtained by measurements of CPE, UPF, and access network equipment.
  • the delay data analysis entity performs delay analysis based on multiple pieces of measurement data, and can determine that only the video surveillance backhaul service has delay problems, and other communication services have no delay problems. Specifically, it can be determined that the video surveillance backhaul service has a delay failure during the CPE transmission stage.
  • the delay data analysis entity can determine through the knowledge management entity that the root cause of the delay failure may be uplink packet loss or disorder when the CPE transmits the video backhaul service.
  • the delay data analysis entity can determine, through the knowledge management entity, that the network configuration action contained in the root cause fault solution information is: restart the CPE.
  • the delay data analysis entity can return the fault solution information to the delay data requesting entity.
  • the delay data requesting entity can thus send instruction information to the CPE based on the fault solution information.
  • the instruction information is used to instruct the CPE to perform the following configuration actions: restart the CPE.
  • each step in the above-mentioned Figures 3 to 5 is only an exemplary description and is not strictly limited.
  • the size of the serial numbers of the above-mentioned processes does not mean the order of execution.
  • the execution order of each process should be determined by its functions and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application.
  • dyeing processing is mentioned many times, which means dyeing data packets, or associating data packets with measurement identifiers.
  • embodiments of the present application also provide corresponding devices, and the devices include modules for executing corresponding modules in each of the above method embodiments.
  • the module can be software, hardware, or a combination of software and hardware. It can be understood that the technical features described in the above method embodiments are also applicable to the following device embodiments.
  • FIG. 6 is a schematic block diagram of a communication device provided by an embodiment of the present application.
  • the communication device 600 includes a communication unit 610 and a processing unit 620.
  • the communication unit 610 can implement corresponding communication functions, and the communication unit 610 can also be a communication interface or a communication unit.
  • the processing unit 620 can implement corresponding processing functions, such as processing instructions and/or data.
  • the communication device 600 may also include a storage unit, which may be used to store instructions and/or data, and the processing unit 620 may read the instructions and/or data in the storage unit, so that the device implements The aforementioned method embodiments.
  • the communication device 600 can be used to perform the actions performed by the delay data requesting entity or the delay data analysis entity in the above method embodiment.
  • the communication unit 610 in the communication device 600 is used to perform the above method embodiment.
  • the processing unit 620 is configured to perform operations related to the transmission and reception of the delay data requesting entity or the delay data analysis entity side in the above method embodiments.
  • the communication device 600 is used to perform the actions performed by the delay data analysis entity in the above method embodiment:
  • a communication unit configured to receive business information and analysis rule information from the delay data requesting entity; wherein the business information is used to indicate the communication service to be analyzed; the analysis rule information is used to indicate the need for the communication Analysis rules used for delay analysis of the service; Obtain multiple pieces of delay measurement data of the data packets of the communication service, wherein each piece of delay measurement data indicates at least one of the transmission paths of the data packets of the communication service. The transmission duration of the transmission phase;
  • a processing unit configured to obtain a delay analysis result based on the analysis rules and the plurality of delay measurement data; the delay analysis result is used to indicate that the communication service has a delay fault in the transmission path stage.
  • the communication device 600 is used to perform what the delay data requesting entity performs in the above method embodiment. Actions:
  • a processing unit configured to determine service information and analysis rule information; wherein the service information is used to indicate the communication service to be analyzed for delay; and the analysis rule information is used to indicate the method used to perform delay analysis on the communication service. analysis rules;
  • a communication unit configured to send the business information and the analysis rule information to the delay data analysis entity; receive the delay analysis results from the delay data analysis entity, and the delay analysis results are used to indicate the communication There is a delay failure in the transmission phase of the service in the transmission path.
  • the processing unit 620 and the communication unit 610 can also perform other functions.
  • the processing unit 620 and the communication unit 610 can also perform other functions.
  • Figure 7 shows a communication device provided by an embodiment of the present application.
  • the communication device shown in Figure 7 can be an implementation of a hardware circuit of the communication device shown in Figure 6.
  • the communication device can be adapted to the flow chart shown above to perform the functions of the delay data requesting entity or the delay data analysis entity in the above method embodiment.
  • FIG. 7 shows only the main components of the communication device.
  • the communication device 700 includes a processor 710 and an interface circuit 720 .
  • the processor 710 and the interface circuit 720 are coupled to each other.
  • the interface circuit 720 can be a transceiver, a pin, or an input-output interface.
  • the communication device 700 may also include a memory 730 for storing instructions executed by the processor 710 or input data required for the processor 710 to run the instructions or data generated after the processor 710 executes the instructions. Alternatively, some or all of memory 730 may be located in processor 710.
  • the processor 710 is used to implement the functions of the above-mentioned processing unit 620
  • the interface circuit 720 is used to implement the functions of the above-mentioned communication unit 610.
  • processor in the embodiment of the present application may be a central processing unit, or other general-purpose processor, digital signal processor, application-specific integrated circuit or other programmable logic device, transistor logic device, hardware component or any combination thereof.
  • a general-purpose processor can be a microprocessor or any conventional processor.
  • the memory in the embodiment of the present application may be random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, register, hard disk, in a portable hard disk or any other form of storage media well known in the art.
  • the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component
  • the memory storage module
  • memories described herein are intended to include, but are not limited to, these and any other suitable types of memories.
  • embodiments of the present application may be provided as methods, systems, or computer program products. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment that combines software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, etc.) having computer-usable program code embodied therein.
  • a computer-usable storage media including, but not limited to, disk storage, optical storage, etc.
  • These computer program instructions may also be stored in a computer-readable memory that causes a computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction means, the instructions
  • the device implements the functions specified in a process or processes of the flowchart and/or a block or blocks of the block diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请提供一种时延分析方法及装置，其中方法包括：时延数据分析实体接收来自于时延数据请求实体的业务信息以及分析规则信息；时延数据分析实体获取通信业务的数据包的多条时延测量数据，其中，每一条时延测量数据指示通信业务的数据包在传输路径中的至少一个传输阶段的传输时长；时延数据分析实体基于分析规则以及多条时延测量数据得到时延分析结果；时延分析结果用于指示存在时延故障的传输阶段。通过上面的方法，分析规则是由时延数据请求实体向时延数据分析实体配置的，通过分析规则可以对通信业务在传输路径中的各个传输阶段的时延测量数据进行分析，从而确定通信业务在每个传输阶段是否存在时延故障，能够准确的对时延故障进行定位。

Description

一种时延分析方法及装置
相关申请的交叉引用
本申请要求在2022年03月17日提交中国专利局、申请号为202210264917.7、申请名称为“一种时延分析方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种时延分析方法及装置。
背景技术
随着移动网络性能的提高，移动网络的应用场景也越来越多。随着移动网络的应用场景的增多，传统的时延故障分析方法确定的时延故障与实际的时延故障不匹配，不能够准确定位出实际发生时延故障的故障点。举例来说，第五代(5th generation，5G)网络的一个重要应用场景是5G面向企业(to business，to B)场景，在5G toB场景下，企业园区的私有网络中会部署大量的用户驻地设备(customer premises equipment，CPE)，CPE一方面可作为终端设备，通过无线技术连接到接入网设备以获得无线网络服务；另一方面可作为无线接入点，为其他终端设备，如可编程逻辑控制器(programmable logic controller，PLC)、摄像头等，提供无线接入功能。其中，如果CPE作为无线接入点时，可以为多个通信业务的数据包提供转发服务，如果一个通信业务的数据包出现时延较大的问题，例如CPE在转发视频回传业务时出现上行丢包或乱序，但是其他通信业务的数据包传输正常。按照传统的时延故障分析方法，最终的诊断分析结果可能是CPE没有异常问题，进而导致故障诊断分析结果不准确。
综上可知，传统的时延故障分析方法不能够准确定位出实际发生时延故障的故障点，从而导致无法快速对时延故障进行定位。
发明内容
本申请提供一种时延分析方法及装置，用以提高时延分析精确度，提高时延故障定位的准确度。
第一方面，本申请提供一种时延分析方法，该方法可以用于实现时延数据分析实体侧的功能，本申请实施例不限该方法的具体执行主体。以该方法应用于时延数据分析实体为例，在该方法中，时延数据分析实体接收来自于时延数据请求实体的业务信息以及分析规则信息；其中，所述业务信息用于指示待时延分析的通信业务；所述分析规则信息用于指示对所述通信业务进行时延分析所采用的分析规则；所述时延数据分析实体获取所述通信业务的数据包的多条时延测量数据，其中，每一条时延测量数据指示所述通信业务的数据包在传输路径中的至少一个传输阶段的传输时长；所述时延数据分析实体基于所述分析规则以及所述多条时延测量数据得到时延分析结果；所述时延分析结果用于指示所述通信业务在所述传输路径中存在时延故障的传输阶段。
作为示例，通信业务例如包括但不限于：视频类业务(如视频监控回传业务)，远程 控制业务。
作为示例，该传输路径可以为用户驻地设备至UPF之间的路径，即通信业务的数据包在用户驻地设备至用户面功能(user plane function，UPF)之间传输，其中该用户驻地设备可以为该通信业务所属的终端设备提供无线接入功能。
通过上面的方法，在进行时延分析时，分析规则是由时延数据请求实体向时延数据分析实体配置的，通过分析规则可以对通信业务在传输路径中的各个传输阶段的时延测量数据进行分析，从而确定通信业务在每个传输阶段是否存在时延故障，因此时延分析的结果更准确，能够准确的对时延故障进行定位。进一步的，在进行时延分析时，是基于较细粒度(即业务粒度)的时延测量数据分析。这样，若需要进行故障诊断分析，则可以基于通信业务的时延测量数据进行通信业务粒度的时延分析。从而可以克服单纯基于无线网络空口的性能数据分析结果不准的问题，而且相比于进行设备级的时延分析，上述技术方案提高时延分析的准确性。
在一种可能的设计中，所述分析规则信息指示的所述分析规则为第一规则时，对于所述传输路径中的任一传输阶段，所述传输阶段对应第一时延阈值；
所述第一规则包括：对于所述传输路径中的任一传输阶段，如果所述传输阶段在所述多条时延测量数据中对应的时延测量数据大于或等于所述传输阶段对应的第一时延阈值，则所述通信业务在所述传输阶段中存在时延故障；如果所述传输阶段在所述多条时延测量数据中对应的时延测量数据小于所述传输阶段对应的第一时延阈值，则所述通信业务在所述传输阶段中不存在时延故障。
在一种可能的设计中，所述第一时延阈值为所述分析规则信息指示的；或者，所述第一时延阈值为根据所述第一时延阈值对应的所述传输阶段的历史时延测量数据确定的；或者，所述第一时延阈值为知识管理实体配置的。
在一种可能的设计中，所述分析规则信息指示的所述分析规则为第二规则时，对于所述传输路径中的任一传输阶段，所述传输阶段对应第二时延阈值；
所述第二规则包括：对于所述传输路径中的任一传输阶段，如果所述传输阶段在所述多条时延测量数据中对应的时延测量数据与所述通信业务在所述传输路径中的总时延的比值大于或等于所述传输阶段对应的第二时延阈值，则所述通信业务在所述传输阶段中存在时延故障；如果所述传输阶段在所述多条时延测量数据中对应的时延测量数据与所述总时延的比值小于所述传输阶段对应的第二时延阈值，则所述通信业务在所述传输阶段中不存在时延故障。
在一种可能的设计中，所述第二时延阈值为所述分析规则信息指示的；或者，所述第二时延阈值为知识管理实体配置的。
作为示例，时延数据请求实体还可以向时延数据分析实体发送以下一项或多项信息：
通信业务的分析类型信息；通信业务的分析粒度信息；数据流方向信息；分析时间信息；测量设备的标识信息；阈值信息。
其中，分析类型信息，用于指示请求的时延分析类型，本申请中，时延分析类型可以为“E2E时延分析”。分析类型信息指示的时延分析类型为“E2E时延分析”时，表示需要分析通信业务的数据包在E2E传输路径中的时延测量数据。时延分析类型还可能存在其他类型，例如包括但不限于：覆盖问题分析、通信业务体验分析、网络切片负载分析、故障预测、MDA辅助节能等。
其中，分析粒度信息，用于指示时延分析的粒度，本申请中，时延分析的粒度可以为“业务级(或业务流)”时延分析。时延分析的粒度还可能存在其他粒度，例如网络切片级时延分析。
其中，分析粒度信息也可以通过分析类型信息指示，例如，分析类型信息指示的时延分析类型为“业务级E2E时延分析”或“业务流E2E时延分析”时，表示需要分析通信业务的数据包在E2E传输路径中的时延测量数据，并且分析粒度为“业务级(或业务流)”。
其中，数据流方向信息，用于指示需要分析的通信业务的数据包的传输方向，可以为上行和下行中的至少一项。
其中，分析时间信息，用于指示对通信业务进行时延分析的时间，即指示在哪个时间段对通信业务进行时延分析或哪个时间开始对通信业务进行时延分析。作为示例，分析时间信息包括：分析开始时间、分析结束时间以及分析时长中的至少一项。其中，分析时间信息指示的时间，可以位于确定对通信业务进行时延分析的时间之前，也就是说，时延数据请求设备可以请求对通信业务的历史时延测量数据进行分析，从而使得进行时延分析的时延测量数据的来源更广泛，可以提高时延分析的准确性。其中，测量设备的标识信息，用于指示测量通信业务的数据包的时延测量数据的设备，测量设备可以包括接入网设备、UPF或CPE中的至少一个。其中，阈值信息，用于指示通信业务的传输路径中的每个传输阶段对应的第一时延阈值或第二时延阈值。
在一种可能的设计中，如果所述时延分析结果指示所述通信业务在所述传输路径中的M个传输阶段存在时延故障，M为大于0的整数，所述方法还包括：时延数据分析实体向知识管理实体发送根因请求信息以及时延分析结果，根因请求信息用于请求存在时延故障的所述M个传输阶段对应的根因；时延数据分析实体接收来自所述知识管理实体的根因指示信息，根因指示信息用于指示所述M个传输阶段中每个传输阶段存在时延故障的根因。
上面的方法中，通过知识管理实体查询时延故障的根因，可以快速高效的确定根因。
在一种可能的设计中，所述时延分析结果指示存在时延故障的传输阶段包括以下一项或多项：无线接入网传输阶段；核心网传输阶段；传输网传输阶段；用户驻地设备传输阶段；空口传输阶段。
在一种可能的设计中，如果所述时延分析结果指示所述通信业务在所述传输路径中的M个传输阶段存在时延故障，M为大于0的整数，所述方法还包括：所述时延数据分析实体向知识管理实体发送故障解决请求信息，所述故障解决请求信息包含所述时延分析结果，所述故障解决请求信息用于请求解决所述M个传输阶段的时延故障；所述时延数据分析实体接收来自所述知识管理实体的故障解决方法信息，所述故障解决方法信息包含用于解决所述M个传输阶段的时延故障的网络配置动作和/或用于解决所述M个传输阶段的时延故障的网络配置参数。
上面的方法中，通过知识管理实体查询时延故障的故障解决方法信息，可以快速的解决时延故障。
在一种可能的设计中，如果所述时延分析结果指示所述通信业务在所述传输路径中的M个传输阶段存在时延故障，M为大于0的整数，所述方法还包括：所述时延数据分析实体向所述时延数据请求实体发送以下至少一项信息：所述时延分析结果；根因指示信息，所述根因指示信息用于指示所述M个传输阶段中每个传输阶段存在时延故障的根因；故障解决方法信息，所述故障解决方法信息包含用于解决所述M个传输阶段的时延故障的网络 配置动作和/或用于解决所述M个传输阶段的时延故障的网络配置参数。
第二方面，本申请提供一种时延分析方法，该方法可以用于实现时延数据请求实体侧的功能，本申请实施例不限该方法的具体执行主体。以该方法应用于时延数据请求实体为例，在该方法中，时延数据请求实体确定业务信息以及分析规则信息；其中，所述业务信息用于指示待时延分析的通信业务；所述分析规则信息用于指示对所述通信业务进行时延分析所采用的分析规则；所述时延数据请求实体向时延数据分析实体发送所述业务信息以及所述分析规则信息；所述时延数据请求实体接收来自所述时延数据分析实体的时延分析结果，所述时延分析结果用于指示所述通信业务在传输路径中存在时延故障的传输阶段。
在一种可能的设计中，所述分析规则信息指示的所述分析规则为第一规则时，对于所述传输路径中的任一传输阶段，所述传输阶段对应第一时延阈值；所述第一规则包括：对于所述传输路径中的任一传输阶段，如果所述传输阶段在所述多条时延测量数据中对应的时延测量数据大于或等于所述传输阶段对应的第一时延阈值，则所述通信业务在所述传输阶段中存在时延故障；如果所述传输阶段在所述多条时延测量数据中对应的时延测量数据小于所述传输阶段对应的第一时延阈值，则所述通信业务在所述传输阶段中不存在时延故障。
在一种可能的设计中，所述第一时延阈值为所述分析规则信息指示的；或者，所述第一时延阈值为根据所述第一时延阈值对应的所述传输阶段的历史时延测量数据确定的；或者，所述第一时延阈值为知识管理实体配置的。
在一种可能的设计中，所述分析规则信息指示的所述分析规则为第二规则时，对于所述传输路径中的任一传输阶段，所述传输阶段对应第二时延阈值；所述第二规则包括：对于所述传输路径中的任一传输阶段，如果所述传输阶段在所述多条时延测量数据中对应的时延测量数据与所述通信业务在所述传输路径中的总时延的比值大于或等于所述传输阶段对应的第二时延阈值，则所述通信业务在所述传输阶段中存在时延故障；如果所述传输阶段在所述多条时延测量数据中对应的时延测量数据与所述总时延的比值小于所述传输阶段对应的第二时延阈值，则所述通信业务在所述传输阶段中不存在时延故障。
在一种可能的设计中，所述第二时延阈值为所述分析规则信息指示的；或者，所述第二时延阈值为知识管理实体配置的。
在一种可能的设计中，所述时延分析结果指示存在时延故障的传输阶段包括以下一项或多项：无线接入网传输阶段；核心网传输阶段；传输网传输阶段；用户驻地设备传输阶段；空口传输阶段。
在一种可能的设计中，如果所述时延分析结果指示所述通信业务在所述传输路径中的M个传输阶段存在时延故障，M为大于0的整数，所述方法还包括：
所述时延数据请求实体接收来自所述时延数据分析实体的以下至少一项信息：根因指示信息，所述根因指示信息用于指示所述M个传输阶段中每个传输阶段存在时延故障的根因；故障解决方法信息，所述故障解决方法信息包含用于解决所述M个传输阶段的时延故障的网络配置动作和/或用于解决所述M个传输阶段的时延故障的网络配置参数。
在一种可能的设计中，所述方法还包括：所述时延数据请求实体根据所述时延分析结果、所述根因指示信息以及所述故障解决方法信息中的至少一项生成解决所述通信业务在所述M个传输阶段的时延故障的指示信息。
可以理解地，上述第二方面所描述的方法与上述第一方面所描述的方法相对应，因此， 第二方面所描述的方法中相关技术特征的有益效果可以参照第一方面，具体不再赘述。
第三方面，本申请实施例提供一种时延数据分析实体，所述时延数据分析实体具备实现上述第一方面的功能。比如，所述时延数据分析实体包括执行上述第一方面所涉及的步骤的模块或单元或手段(means)，所述功能或单元或手段可以通过软件实现，或者通过硬件实现，也可以通过硬件执行相应的软件实现。
在一种可能的设计中，所述时延数据分析实体包括处理单元、通信单元，其中，通信单元可以用于收发信号，以实现该时延数据分析实体和其它装置之间的通信；处理单元可以用于执行该时延数据分析实体的一些内部操作。
具体地，在一个实施例中，通信单元，用于接收来自于时延数据请求实体的业务信息以及分析规则信息；其中，所述业务信息用于指示待时延分析的通信业务；所述分析规则信息用于指示时延分析所采用的分析规则；获取所述通信业务的数据包的多条时延测量数据，其中，每一条时延测量数据指示所述通信业务的数据包在传输路径中的至少一个传输阶段的传输时长；处理单元，用于基于所述分析规则以及所述多条时延测量数据得到时延分析结果；所述时延分析结果用于指示所述通信业务在所述传输路径中存在时延故障的传输阶段。
在一种可能的设计中，所述时延数据分析实体包括处理器，还可以包括收发器，所述收发器用于收发信号，所述处理器执行程序指令，以完成上述第一方面中任意可能的设计或实现方式中的方法。其中，所述时延数据分析实体还可以包括一个或多个存储器，所述存储器用于与处理器耦合，所述存储器可以保存实现上述第一方面涉及的功能的必要计算机程序或指令。所述处理器可执行所述存储器存储的计算机程序或指令，当所述计算机程序或指令被执行时，使得所述时延数据分析实体实现上述第一方面中任意可能的设计或实现方式中的方法。
在一种可能的设计中，所述时延数据分析实体包括处理器，处理器可以用于与存储器耦合。所述存储器可以保存实现上述第一方面涉及的功能的必要计算机程序或指令。所述处理器可执行所述存储器存储的计算机程序或指令，当所述计算机程序或指令被执行时，使得所述时延数据分析实体实现上述第一方面中任意可能的设计或实现方式中的方法。
在一种可能的设计中，所述时延数据分析实体包括处理器和接口电路，其中，处理器用于通过所述接口电路与其它装置通信，并执行上述第一方面中任意可能的设计或实现方式中的方法。
第四方面，本申请实施例提供一种时延数据请求实体，所述时延数据请求实体具备实现上述第二方面的功能，比如，所述时延数据请求实体包括执行上述第二方面所涉及的步骤的模块或单元或手段，所述功能或单元或手段可以通过软件实现，或者通过硬件实现，也可以通过硬件执行相应的软件实现。
在一种可能的设计中，所述时延数据请求实体包括处理单元、通信单元，其中，通信单元可以用于收发信号，以实现该时延数据请求实体和其它装置之间的通信；处理单元可以用于执行该时延数据请求实体的一些内部操作。
具体地，在一个实施例中，处理单元，用于确定业务信息以及分析规则信息；其中，所述业务信息用于指示待时延分析的通信业务；所述分析规则信息用于指示时延分析所采用的分析规则；通信单元，用于向时延数据分析实体发送所述业务信息以及所述分析规则信息；接收来自所述时延数据分析实体的时延分析结果，所述时延分析结果用于指示所述 通信业务在传输路径中存在时延故障的传输阶段。
在一种可能的设计中，所述时延数据请求实体包括处理器，还可以包括收发器，所述收发器用于收发信号，所述处理器执行程序指令，以完成上述第二方面中任意可能的设计或实现方式中的方法。其中，所述时延数据请求实体还可以包括一个或多个存储器，所述存储器用于与处理器耦合，所述存储器可以保存实现上述第二方面涉及的功能的必要计算机程序或指令。所述处理器可执行所述存储器存储的计算机程序或指令，当所述计算机程序或指令被执行时，使得所述时延数据请求实体实现上述第二方面中任意可能的设计或实现方式中的方法。
在一种可能的设计中，所述时延数据请求实体包括处理器，处理器可以用于与存储器耦合。所述存储器可以保存实现上述第二方面涉及的功能的必要计算机程序或指令。所述处理器可执行所述存储器存储的计算机程序或指令，当所述计算机程序或指令被执行时，使得所述时延数据请求实体实现上述第二方面中任意可能的设计或实现方式中的方法。
在一种可能的设计中，所述时延数据请求实体包括处理器和接口电路，其中，处理器用于通过所述接口电路与其它装置通信，并执行上述第二方面中任意可能的设计或实现方式中的方法。
可以理解地，上述第三方面至第四方面中，处理器可以通过硬件来实现也可以通过软件来实现，当通过硬件实现时，该处理器可以是逻辑电路、集成电路等；当通过软件来实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现。此外，以上处理器可以为一个或多个，存储器可以为一个或多个。存储器可以与处理器集成在一起，或者存储器与处理器分离设置。在具体实现过程中，存储器可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请实施例对存储器的类型以及存储器与处理器的设置方式不做限定。
第五方面，本申请实施例提供一种通信系统，该通信系统包括上述第三方面所提供的时延数据分析实体和上述第四方面所提供的时延数据请求实体。
第六方面，提供了一种计算机可读存储介质，用于存储计算机程序，该计算机程序包括用于执行第一方面或第一方面中任一种可能实现方式中的方法的指令。
第七方面，提供了一种计算机可读存储介质，用于存储计算机程序，该计算机程序包括用于执行第二方面或第二方面中任一种可能实现方式中的方法的指令。
第八方面，提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序代码，当所述计算机程序代码在计算机上运行时，使得计算机执行上述第一方面或第一方面中任一种可能实现方式中的方法。
第九方面，提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序代码，当所述计算机程序代码在计算机上运行时，使得计算机执行上述第二方面及第二方面中任一种可能实现方式中的方法。
第十方面，本申请提供一种芯片，所述芯片包括处理器，所述处理器与存储器耦合，用于读取并执行所述存储器中存储的软件程序，以实现上述第一方面至第二方面的任一种可能的设计中的方法。
本申请的这些方面或其它方面在以下实施例的描述中会更加简明易懂。
附图说明
图1为适用于本申请实施例的网络架构的示意图；
图2为适用于本申请实施例的另一网络架构的示意图；
图3为本申请实施例提供的一种时延分析方法流程示意图；
图4为本申请实施例提供的一种时延分析方法流程示意图；
图5为本申请实施例提供的一种时延分析方法流程示意图；
图6为本申请实施例提供的一种通信装置结构示意图；
图7为本申请实施例提供的一种通信装置结构示意图。
具体实施方式
下面结合说明书附图对本申请实施例做详细描述。
本申请提供的技术方案可以应用于各种通信系统，例如：新无线(new radio，NR)系统、长期演进(long term evolution，LTE)系统等。本申请提供的技术方案还可以应用于未来的通信系统，如第六代移动通信系统。
为便于理解本申请实施例，首先对本申请中涉及到的术语做简单说明。
终端设备：可以称用户设备(user equipment，UE)、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置等。终端设备可以是一种向用户提供语音/数据的设备，例如，具有无线连接功能的手持式设备、车载设备等。目前，一些终端设备的举例为：手机(mobile phone)、平板电脑、笔记本电脑、掌上电脑、PLC、摄像头、移动互联网设备(mobile internet device，MID)、可穿戴设备，虚拟现实(virtual reality，VR)设备、增强现实(augmented reality，AR)设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、可穿戴设备，5G网络中的终端设备或者未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的终端设备等，本申请实施例对此并不限定。
在本申请中，用于实现终端设备的功能的装置可以是终端设备；也可以是能够支持终端设备实现该功能的装置，例如芯片系统、硬件电路、软件模块、或硬件电路加软件模块，该装置可以被安装在终端设备中或可以与终端匹配使用。为了便于描述，下文以用于实现终端设备的功能的装置是终端设备为例，描述本公开提供的技术方案。
用户驻地设备，也可以称为行业终端设备，一方面可作为终端设备，通过无线技术连接到接入网设备以获得无线网络服务；另一方面可作为无线接入点，为其他终端设备(如PLC，摄像头等)提供无线接入功能。本申请实施例主要以用户驻地设备为CPE为例进行示例性说明，类似于CPE的其他用户驻地设备也适用于本申请实施例。
无线接入网(radio access network，RAN)设备，也可以称为接入网设备，可以为特定区域的授权用户提供接入通信网络的功能，具体可以包括第三代合作伙伴计划(3rd generation partnership project，3GPP)网络中无线网络设备也可以包括非3GPP(non-3GPP)网络中的接入点。接入网设备可以是基站(base station)、演进型基站(evolved NodeB，eNodeB)、发送接收点(transmission reception point，TRP)、5G移动通信系统中的下一代基站(next generation NodeB，gNB)、开放无线接入网(open radio access network，O-RAN)中的接入网设备、第六代(6th generation，6G)移动通信系统中的下一代基站、未来移动 通信系统中的基站或无线保真(wireless fidelity，WiFi)系统中的接入节点等；或者接入网设备可以是完成基站部分功能的模块或单元，例如，可以是集中式单元(central unit，CU)、分布式单元(distributed unit，DU)、集中单元控制面(CU control plane，CU-CP)模块、或集中单元用户面(CU user plane，CU-UP)模块。本公开中对接入网设备所采用的具体技术和具体设备形态不做限定。
异常事件：在本申请实施例中，异常事件可以是指业务粒度的异常事件。业务粒度的异常事件如包括：通信业务对应的视频卡顿、或通信业务对应的控制时延异常等。其中，通信业务对应的视频卡顿可以是：通信业务为视频回传业务时，通信业务对应的视频业务服务器播放的视频出现花屏或卡顿现象。通信业务对应的控制时延异常可以是：通信业务为远程控制业务时，通信业务对应的控制业务服务器给终端设备发送的控制命令到达终端设备的时延较大(如大于数据传输平均时延)或终端设备接收到命令后响应时间长(如大于平均响应时长)等。
时延分析，可以是指分析通信业务的数据包或数据流在传输过程中是否存在时延故障，以及确定存在时延故障时，确定时延故障的具体信息，例如确定时延故障的根因以及故障解决方法信息等。
时延故障，是指导致通信业务的时延偏高/偏大，不满足通信业务对时延的要求的故障，例如，如果通信业务的时延要求为小于或等于预设阈值，如果该通信业务的时延大于该预设阈值，则认为出现时延故障。
首先简单介绍适用于本申请的网络架构，如图1所示，为适用于本申请实施例的网络架构的示意图。图1所示的网络架构，可适用于5G toB下的通信业务场景。在5G toB下的通信业务场景中，当终端设备为摄像头时，用户驻地设备(图1中以用户驻地设备为CPE为例)可以为一个或多个摄像头(camera)提供视频监控回传业务；当终端设备为PLC时，用户驻地设备可以为PLC的远程控制业务流提供接入和数据传输功能，其它情况不再逐一举例说明。其中，可以理解，图1中仅示出了3个终端设备，即终端设备1至终端设备3，本申请实施例对终端设备的数量并不限定。
图1的网络架构中，核心网侧可以包括多种核心网网元，例如可以包括接入和移动性管理功能(access and mobility management function，AMF)，会话管理功能(session management function，SMF)，网络开放功能(network exposure function，NEF)以及用户面功能(user plane function，UPF)等。上述核心网网元的定义和功能可以参照3GPP标准规范中的描述，在此不再赘述。此外，尽管未示出，上述网络架构中还可以包括其它可能的实体，在此不再赘述。
进一步的，如图1所示，3GPP逻辑管理架构中包括两类管理系统，即网络管理系统(network management system，NMS)和网元管理系统(element management system，EMS)。其中，EMS可包括对无线网络的网元(如gNB，gNB-CU-CP，gNB-CU-UP，gNB-DU等)进行管理的功能实体，NMS可包括运营商实现跨域网络管理的功能实体。举例来说，EMS可能用于某一片区域内的网元进行管理，NMS可以对多个EMS管理范围内的区域进行管理。或者，EMS用于无线网络域的网元管理，NMS可以同时管理无线网络域和核心网域。
如图1所示，该网络架构可以包括管理数据分析(management data analytics，MDA)管理服务(Management Service，MnS)消费者实体，MDA MnS生产者实体，知识管理(knowledge management，KM)实体以及数据管理服务生产者实体等。其中，MDA MnS 生产者实体可以进行时延分析，确定是否存在时延故障等，并将分析结果提供给MDA MnS消费者实体，用于决策或者进一步分析。其中，MDA MnS生产者实体的功能可以通过管理数据分析功能(management data analytics function，MDAF)来实现。
MDA MnS消费者实体可以请求MDA MnS生产者进行时延分析。本申请中，MDA MnS消费者实体的功能可以通过无线终端设备管理功能(wireless terminal equipment management function，WTEMF)来实现。WTEMF可以实现对用户驻地设备(例如CPE)上所连接的终端设备提供上线注册、参数配置、性能管理、故障管理等操作。本申请中，WTEMF可以作为MDA MnS消费者实体请求MDA MnS生产者实体进行时延分析，例如，可以根据分析结果确定是否存在时延故障，以及确定执行解决时延故障的操作。
数据管理服务生产者实体可以用于从用户驻地设备、接入网设备以及UPF等收集时延测量数据，并提供给MDA MnS生产者实体。
知识管理实体可以用于为其它管理实体(如MDA MnS生产者实体)提供知识查询功能或问题分析功能。知识管理实体可以包含知识库，知识库中存储了处理各种问题的知识数据。例如：网络维护通信业务专家在处理故障问题过程中，不断进行经验积累，形成了大量的案例、指导书、故障树等知识数据，可以将这些知识数据导入知识库，将故障根因定位建模为基于问题图谱的概率图推理问题，从而能够通过数值因果推理确定故障的根因。
MDA MnS生产者实体，MDA MnS消费者实体，KM实体以及数据管理服务生产者实体可以部署在网络管理系统(network management system，NMS)或网元管理系统(element management system，EMS)中。数据管理服务生产者实体和知识管理实体为可选实体模块。可以理解，NMS/EMS中的各个实体可以分别作为独立实体部署，或者也可以多个实体集成或部署为一个实体(即由一个实体来实现多个实体的功能)。
本申请实施例中所述的实体(比如图1、图2中所述的实体)也可以称为功能实体或网元。上述实体既可以是硬件设备中的网络元件，也可以是在专用硬件上运行的软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。可选的，上述实体可以由一个设备实现，也可以由多个设备共同实现，还可以是一个设备内的一个功能模块，本申请实施例对此不作具体限定。
在5G toB下的通信业务场景中，当用户驻地设备为终端设备提供无线接入功能时，从业务服务器到用户驻地设备可以形成一个端到端(end to end，E2E)网络。本申请中，E2E网络中的传输路径可以划分为多个传输阶段。如图2所示，为适用于本申请实施例的另一网络架构的示意图。用户驻地设备到UPF之间形成一个E2E网络，用户驻地设备到UPF之间的传输路径可以划分为以下5个传输阶段：
用户驻地设备传输阶段；空口传输阶段；无线接入网传输阶段；传输网传输阶段；核心网传输阶段。
其中，用户驻地设备传输阶段，可以是指通信业务的数据包在用户驻地设备内部传输或处理的阶段。通信业务的数据包在用户驻地设备传输阶段中的传输时长为：从用户驻地设备接收到数据包的时刻至用户驻地设备将该数据包发出的时刻之间的时长。
空口传输阶段，可以是指通信业务的数据包在用户驻地设备至接入网设备之间传输的阶段。通信业务的数据包在空口传输阶段中的传输时长为：从用户驻地设备发送数据包的时刻至接入网设备接收到该数据包的时刻之间的时长，或者，从接入网设备发送数据包的时刻至用户驻地设备接收到该数据包的时刻之间的时长。
无线接入网传输阶段，可以是指通信业务的数据包在接入网设备内部传输或处理的阶段。通信业务的数据包在无线接入网传输阶段中的传输时长为：从接入网设备接收到数据包的时刻至接入网设备将该数据包发出的时刻之间的时长。
传输网传输阶段，可以是指通信业务的数据包在UPF至接入网设备之间传输的阶段。通信业务的数据包在传输网传输阶段中的传输时长为：从UPF发送数据包的时刻至接入网设备接收到该数据包的时刻之间的时长，或者，从接入网设备发送数据包的时刻至UPF接收到该数据包的时刻之间的时长。
核心网传输阶段，可以是指通信业务的数据包在UPF内部传输或处理的阶段。通信业务的数据包在核心网传输阶段中的传输时长为：从UPF接收到数据包的时刻至UPF将该数据包发出的时刻之间的时长。
目前3GPP标准上定义的网络故障管理机制主要都是针对网络设备的故障管理，不支持对终端设备故障的管理。因此传统的时延故障分析方法中，EMS中的实体不能够准确定位出实际发生时延故障的故障点，从而导致无法快速对时延故障进行定位，降低网络的稳定性。
举例来说，如图1所示的5G toB场景，企业园区的私有网络中会部署大量的用户驻地设备(如CPE等)，CPE作为无线接入点时，可以为多个通信业务的数据包提供转发服务，如果一个通信业务的数据包出现时延较大的问题，例如CPE在转发视频回传业务时出现上行丢包或乱序，但是其他通信业务的数据包传输正常。如果按照传统的时延故障分析方法，统计的是CPE上所有通信业务的数据包的平均时延，每个通信业务流的真实的数据包的时延被平均，最终的诊断分析结果可能是CPE没有异常问题，进而导致故障诊断分析结果不准确。因此，对于这种情况，单纯通过无线网络空口问题分析，无法定位出实际发生异常的故障点。
有鉴于此，本申请提出一种方案，可以基于通信业务流粒度进行时延测量数据的统计，并基于通信业务流粒度的时延测量数据对各个传输阶段进行时延故障分析，从而可支持实现E2E的时延故障定界。
应理解，上述应用于本申请实施例的网络架构仅是举例说明的架构，适用本申请实施例的网络架构并不局限于此，任何能够实现上述各个网元的功能的网络架构都适用于本申请实施例。
还应理解，图1至图2中的各功能或者网元，如MDA MnS生产者实体、MDA MnS消费者实体、AMF、SMF、UPF等功能或者网元，可以理解为用于实现不同功能的网元，这些网元可以各自独立的设备，也可以集成于同一设备中实现不同的功能，或者可以是硬件设备中的网络元件，也可以是在专用硬件上运行的软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能，本申请对于上述网元的具体形态不作限定。
还应理解，上述命名仅为便于区分不同的功能而定义，不应对本申请构成任何限定。本申请并不排除在6G网络以及未来其它的网络中采用其他命名的可能。例如，在6G网络中，上述各个网元中的部分或全部可以沿用5G中的术语，也可能采用其他名称等。
可以理解，本申请中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的 技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
上面对本申请中涉及到的术语做了简单说明，下文实施例中不再赘述。
下文将结合附图详细说明本申请实施例提供的方法。本申请提供的实施例可以应用于上述图1至图2所示的网络架构中，不作限定。
下面将结合附图详细说明本申请提供的各个实施例。
本申请中，以时延数据分析实体与时延数据请求实体之间的交互为例进行说明，其中，时延数据请求实体可以为图1中的MDA MnS消费者实体，时延数据分析实体可以为图1中的MDA MnS生产者实体。
本申请中，时延数据请求实体可以指示时延数据分析实体获取通信业务的数据包在传输路径中各个传输阶段的时延测量数据，从而确定通信业务在传输路径中各个传输阶段是否存在时延故障。第一种可能的场景中，网络侧确定通信业务出现异常事件时，通过获取通信业务实时的时延测量数据进行分析，即事后分析。第二种可能的场景中，在对通信业务进行时延分析之前，就开始获取通信业务的时延测量数据，当监测到通信业务出现异常事件时，再对异常事件发生时刻前一段时间和/或后一段时间的时延测量数据进行时延分析，下面分别进行描述。
如图3所示，为本申请实施例提供的一种时延分析方法的示意图，该方法包括：
在一个示例中，在执行本申请之前，时延数据请求实体可以进行测量配置，具体的：
S301：时延数据请求实体向测量设备发送测量标识。
其中，时延数据请求实体可以发送多个测量标识，测量标识的具体数量并不限定，一个测量标识用于与一个通信业务进行关联。一个通信业务的数据可以通过通信业务数据流(data flow)来传输，一个通信业务可以对应一个或多个通信业务数据流。
本申请中，通信业务可以包括但不限于：视频类通信业务(如视频监控回传业务)，远程控制类通信业务等，通信业务的具体内容，本申请对此并不限定。例如，视频类业务可以是智慧港口视频监控业务、智慧矿井巷道监控业务、智慧矿井综采面监控业务等，远程控制类业务可以是智慧矿井遥控通信业务、机器人巡检业务、无人天车业务、智慧港口智能理货业务等。
本申请中，测量标识，也可以称为染色标识，用于与待时延分析的通信业务进行关联，可用于识别待测量的通信业务。作为示例，测量标识例如可以是一个特殊的字符或数据，或者，测量标识也可以是与其关联的通信业务的标识(如该通信业务的因特网协议(internet protocol，IP)5元组)。
本申请中，测量设备可以为通信业务的传输路径中包括的设备，例如，以E2E场景为例，通信业务的传输路径为从用户驻地设备至UPF，那么测量设备可以包括以下一项或多项：UPF、接入网设备、或用户驻地设备(如CPE)。
本申请中，通信业务的传输路径可以包括多个传输阶段，例如，通信业务的传输路径为从用户驻地设备至UPF，那么通信业务的传输路径可以包括以下传输阶段：无线接入网传输阶段；核心网传输阶段；传输网传输阶段；用户驻地设备传输阶段；空口传输阶段。上述各个传输阶段的具体含义可以参考前面的描述，在此不再赘述。
可以理解地，时延数据请求实体向测量设备发送测量标识，可以包括：时延数据请求 实体直接向测量设备发送测量标识，也可以包括时延数据请求实体通过其他设备向测量设备发送测量标识，本申请对此并不限定。
本申请中，测量设备获取到测量标识之后，可以关联测量标识和通信业务。
关联测量标识和通信业务，也可以替换为关联测量标识和通信业务的数据包，或者也可以替换为利用测量标识对通信业务的数据包进行染色处理。在本申请实施例中，测量设备通过关联测量标识和通信业务，或者测量设备通过对通信业务的数据包进行染色处理，进而在测量设备需要测量通信业务的时延测量数据时，可以根据测量标识准确的将待测量的通信业务的数据包识别出来。
结合上面的描述，不同测量设备可以测量通信业务的数据包在不同传输阶段的时延测量数据。以E2E场景为例，通信业务的数据包的传输方向为上行方向时，用户驻地设备可以测量通信业务的数据包在用户驻地设备传输阶段的时延测量数据，接入网设备可以测量通信业务的数据包在无线接入网传输阶段和空口传输阶段的时延测量数据，UPF可以测量通信业务的数据包在核心网传输阶段和传输网传输阶段的时延测量数据；通信业务的数据包的传输方向为下行方向时，用户驻地设备可以测量通信业务的数据包在用户驻地设备传输阶段和空口传输阶段的时延测量数据，接入网设备可以测量通信业务的数据包在无线接入网传输阶段和传输网传输阶段的时延测量数据，UPF可以测量通信业务的数据包在核心网传输阶段的时延测量数据。
关联测量标识和通信业务，可以有很多实现方式。一种可能的实现方式，可以在通信业务的数据包中(如数据包的包头字段)填充(或者称添加)测量标识。本申请对具体如何关联测量标识和通信业务并不限定。
可以理解地，时延数据请求实体还可以向测量设备发送以下一项或多项信息：通信业务的标识、通信业务对应的CPE标识、或终端设备的标识。上述一项或多项信息与测量标识和/或测量指示可以携带于同一信令中，也可以携带于不同信令中，不予限制。下面对上述信息进行详细描述。
其中，通信业务的标识，可用于标识(或者识别)通信业务。作为示例，通信业务的标识为IP 5元组。例如，通信业务的标识可以包括：源IP(source IP)地址、源端口(source port)、目标IP(destination IP)地址、目标端口(destination port)、4层通信协议(the layer4protocol)。
其中，CPE标识，可用于标识(或者识别)CPE，该CPE位于该通信业务的传输路径中，该CPE为通信业务所属的终端设备接入的CPE。作为示例，CPE标识可以为以下任一项：CPE的设备序列号码(equipment serial number，ESN)、CPE的IP地址、CPE的全球唯一临时用户标识(globally unique temporary UE identity，GUTI)等。
其中，终端设备的标识，可用于标识(或者识别)通信业务所属的设备。
在一个示例中，上述信息可以统称为测量信息，或者也可以称为染色策略(ColoredPolicy)。也就是说，测量信息可以包括：测量标识、关联测量标识的通信业务的数据包类型、通信业务的标识、通信业务对应的CPE标识、以及终端设备的标识中的至少一项。一种可能的实现方式，时延数据请求实体可以先配置该测量信息，然后再向测量设备发送该测量信息。或者，也可以是其他设备配置该测量信息，然后再向时延数据请求实体发送该测量信息，进而时延数据请求实体向测量设备发送该测量信息。
在一个示例中，如果在对通信业务进行时延分析之前，就开始测量通信业务的时延测 量数据，可以执行S302至S304。
S302：时延数据请求实体向数据收集服务生产者实体发送创建数据收集任务请求消息，创建数据收集任务请求消息用于请求数据收集服务生产者实体创建数据收集任务，数据收集任务用于从测量设备收集通信业务的数据包在传输路径中各个传输阶段的测量时延数据。
其中，数据收集服务生产者实体可以是接入网设备、UPF、CPE，也可以是前面描述的数据管理服务生产者实体。
其中，创建数据收集任务请求消息中可以包括数据收集任务对应的任务配置信息，任务配置信息可以包括以下一项或多项信息：
测量业务信息；测量指标信息；测量设备的标识信息；数据流方向信息。
下面分别对上述信息进行详细描述。
其中，测量业务信息，用于指示需要测量的通信业务，可以为需要测量的通信业务的标识，也可以为与通信业务关联的测量标识。
其中，测量指标信息，用于指示对通信业务进行测量的关键性能指标(key performance indicator，KPI)。本申请中，KPI可以指示需要测量通信业务的数据包在传输路径中哪些传输阶段的时延测量数据。
其中，测量设备的标识信息，用于指示测量通信业务的数据包的时延测量数据的设备，测量设备可以包括接入网设备、UPF或CPE中的至少一个。
其中，数据流方向信息，用于指示需要测量的数据包的传输方向，传输方向可以包括上行和下行中的至少一项。
可选地，可以为一个通信业务配置一个数据收集任务，一个数据收集任务还可以分配一个任务标识。该任务标识可以为数据管理服务生产者实体分配的，也可以为时延数据请求实体分配的，本申请对此并不限定。一个通信业务的数据收集任务的任务标识，可以唯一标识该数据收集任务。
S303：数据收集服务生产者实体向时延数据请求实体发送创建数据收集任务响应消息。
可选地，如果数据管理服务生产者实体分配任务标识，创建数据收集任务响应消息中可以包括数据收集任务对应的任务标识。
S304：数据收集服务生产者实体从测量设备获取时延测量数据。
举例来说，创建数据收集任务请求消息包括的信息如表1所示。
表1
数据管理服务生产者实体根据表1中所示的信息，可以指示接入网设备，UPF以及CPE上报视频回传业务在上行方向传输的数据包，在测量指标信息指示的各个传输阶段传 输的时延测量数据。数据管理服务生产者实体获取到这些时延测量数据时，可以存储这些时延测量数据。
S305：时延数据请求实体确定业务信息以及分析规则信息。
其中，业务信息用于指示待时延分析的通信业务，例如业务信息可以为待时延分析的通信业务的标识，也可以为与通信业务关联的测量标识。可以理解的，如果预先为待时延分析的通信业务创建了数据收集任务，业务信息还可以为该通信业务的数据收集任务的任务标识。
分析规则信息用于指示时延分析所采用的分析规则。
在一个示例中，业务服务器确定通信业务发生异常事件等情况时，业务服务器可以向时延数据请求实体发送维测请求消息，该维测请求消息包括通信业务的标识，该维测请求消息可以用于请求对该标识对应的通信业务进行维测。其中，维测可以是指，采集通信业务相关的网络性能数据(例如时延测量数据)，并基于采集的网络性能数据对网络性能进行分析，识别网络是否存在故障问题。
时延数据请求实体接收到维测请求消息后，根据通信业务的标识，可以确定待时延分析的通信业务。
可以理解地，以上只是示例，时延数据请求实体也可以通过其他方式确定待时延分析的通信业务，本申请对此并不限定。
本申请中，分析规则信息指示的分析规则可以为第一规则或者第二规则，关于第一规则和第二规则的具体内容可以参考如下：
第一规则可以包括：对于通信业务的传输路径中的任一传输阶段，如果该传输阶段对应的时延测量数据大于或等于该传输阶段对应的第一时延阈值，则通信业务在该传输阶段中存在时延故障；如果该传输阶段对应的时延测量数据小于该传输阶段对应的第一时延阈值，则通信业务在该传输阶段中不存在时延故障。
第二规则可以包括：对于通信业务的传输路径中的任一传输阶段，如果该传输阶段对应的时延测量数据与该通信业务在该传输路径中的总时延的比值大于或等于该传输阶段对应的第二时延阈值，则该通信业务在该传输阶段中存在时延故障；如果该传输阶段对应的时延测量数据与该通信业务在该传输路径中的总时延的比值小于该传输阶段对应的第二时延阈值，则该通信业务在该传输阶段中不存在时延故障。
可以理解地，时延数据请求实体具体如何确定采用哪种分析规则，本申请对此并不限定。在一个示例中，如果数据包在传输路径中各个传输阶段的传输时长相差较大(例如数据包在两个传输阶段的传输时长相差50％)的情况下，时延数据请求实体可以指示采用第一规则进行时延分析；如果数据包在传输路径中各个传输阶段的传输时长相近(例如数据包在两个传输阶段的传输时长相差10％以内)的情况下，时延数据请求实体可以指示采用第二规则进行时延分析。
可以理解地，第一时延阈值可能存在多种实现方式，第一种实现方式中，通信业务的传输路径中每个传输阶段对应的第一时延阈值，可以为时延数据请求实体确定的。
第二种实现方式中，通信业务的传输路径中每个传输阶段对应的第一时延阈值，可以根据每个传输阶段的历史时延测量数据确定的，具体确定过程并不限定。
第三种实现方式中，每个传输阶段对应的第一时延阈值可以为约定的默认值。
第四种实现方式中，每个传输阶段对应的第一时延阈值可以由知识管理实体配置，具 体的，时延数据分析实体可以向知识管理实体发送时延阈值请求消息，时延阈值请求消息包括分析规则信息，时延阈值请求消息可以用于请求配置与分析规则信息对应的时延阈值；相应的，如果分析规则信息指示第一规则，知识管理实体可以向时延数据分析实体指示通信业务的传输路径中每个传输阶段对应的第一时延阈值。
可以理解地，第二时延阈值可能存在多种实现方式，第一种实现方式中，通信业务的传输路径中每个传输阶段对应的第二时延阈值，可以为时延数据请求实体确定的。第二种实现方式中，每个传输阶段对应的第二时延阈值可以为约定的默认值。第三种实现方式中，每个传输阶段对应的第二时延阈值可以由知识管理实体配置，具体的，时延数据分析实体可以向知识管理实体发送时延阈值请求消息，时延阈值请求消息包括分析规则信息，时延阈值请求消息可以用于请求配置与分析规则信息对应的时延阈值；相应的，如果分析规则信息指示第二规则，知识管理实体可以向时延数据分析实体指示通信业务的传输路径中每个传输阶段对应的第二时延阈值。
S306：时延数据请求实体向时延数据分析实体发送业务信息以及分析规则信息，相应的，时延数据分析实体接收来自于时延数据请求实体的业务信息以及分析规则信息。
可以理解地，时延数据请求实体还可以向时延数据分析实体发送以下一项或多项信息：
通信业务的分析类型信息；通信业务的分析粒度信息；数据流方向信息；分析时间信息；测量设备的标识信息；阈值信息。
下面分别对上述信息进行详细描述。
其中，分析类型信息，用于指示请求的时延分析类型，本申请中，时延分析类型可以为“E2E时延分析”。分析类型信息指示的时延分析类型为“E2E时延分析”时，表示需要分析通信业务的数据包在E2E传输路径中的时延测量数据。时延分析类型还可能存在其他类型，例如包括但不限于：覆盖问题分析、通信业务体验分析、网络切片负载分析、故障预测、MDA辅助节能等。
其中，分析粒度信息，用于指示时延分析的粒度，本申请中，时延分析的粒度可以为“业务级(或业务流)”时延分析。时延分析的粒度还可能存在其他粒度，例如网络切片级时延分析。
其中，分析粒度信息也可以通过分析类型信息指示，例如，分析类型信息指示的时延分析类型为“业务级E2E时延分析”或“业务流E2E时延分析”时，表示需要分析通信业务的数据包在E2E传输路径中的时延测量数据，并且分析粒度为“业务级(或业务流)”。
其中，数据流方向信息，用于指示需要分析的通信业务的数据包的传输方向，可以为上行和下行中的至少一项。
其中，分析时间信息，用于指示对通信业务进行时延分析的时间，即指示在哪个时间段对通信业务进行时延分析或哪个时间开始对通信业务进行时延分析。作为示例，分析时间信息包括：分析开始时间、分析结束时间以及分析时长中的至少一项。
其中，测量设备的标识信息，用于指示测量通信业务的数据包的时延测量数据的设备，测量设备可以包括接入网设备、UPF或CPE中的至少一个。
其中，阈值信息，用于指示通信业务的传输路径中的每个传输阶段对应的第一时延阈值或第二时延阈值。
S307：时延数据分析实体获取通信业务的数据包的多条时延测量数据。
其中，每一条时延测量数据指示通信业务的数据包在传输路径中的至少一个传输阶段 的传输时长。在一个示例中，该传输路径可以为用户驻地设备至UPF之间的路径。
本申请中，时延数据分析实体可以通过数据收集服务生产者实体获取时延测量数据。在一个示例中，如图4所示，时延数据分析实体通过数据收集服务生产者实体获取时延测量数据时，可以包括以下流程：
实现方式一，数据收集服务生产者实体获取实时的时延测量数据：
S401a：时延数据分析实体向数据收集服务生产者实体发送数据请求消息，数据请求消息可以包括以下一项或多项信息：
测量业务信息；测量指标信息；测量设备的标识信息；数据流方向信息；测量时间信息；上报周期信息。
其中，数据收集服务生产者实体可以是接入网设备、UPF、CPE，也可以是前面描述的数据管理服务生产者实体。
其中，测量业务信息，用于指示需要测量的通信业务，测量业务信息可以为待时延分析的通信业务的标识，也可以为与该通信业务关联的测量标识。
其中，测量指标信息，用于指示对通信业务进行测量的关键性能指标(key performance indicator，KPI)。本申请中，KPI可以指示需要测量通信业务的数据包在传输路径中哪些传输阶段的时延测量数据。
其中，测量设备的标识信息，用于指示测量通信业务的数据包的时延测量数据的设备，测量设备可以包括接入网设备、UPF或CPE中的至少一个。
其中，数据流方向信息，用于指示需要测量的数据包的传输方向，传输方向可以包括上行和下行中的至少一项。
其中，测量时间信息，用于指示对通信业务的数据包进行测量的时间，即指示在哪个时间段对通信业务的数据包进行测量或哪个时间开始对通信业务的数据包进行测量。测量时间信息可以根据分析时间信息确定，例如测量时间信息指示的时间可以位于分析时间信息指示的时间之后。例如，分析时间信息指示的时间为T0，时延数据分析实体可以通过测量时间信息指示对T0之后传输的数据包进行测量。作为示例，测量时间信息包括：测量开始时间、测量结束时间以及测量时长中的至少一项。
其中，上报周期信息，用于指示数据管理服务生产者实体上报测量时延数据的周期。
以上只是示例，数据请求消息还可能包括其他信息，在此不再逐一举例说明。
S402a：数据管理服务生产者实体根据数据请求消息从测量设备获取时延测量数据。
在一个示例中，数据请求消息包括的信息可以如表2所示。
表2

数据管理服务生产者实体根据表2中所示的信息，可以从接入网设备，UPF以及CPE获取视频回传业务在上行方向传输的数据包的时延测量数据，其中获取到的时延测量数据为测量指标信息指示的各个传输阶段的数据，且这些时延测量数据为接入网设备，UPF以及CPE在时间T1至时间T2之间对视频回传业务的数据包测量获得的。
一种可能的实现方式中，对于传输路径中的每个传输阶段，每个传输阶段对应的时延测量数据指示传输时长，可以为根据Y个数据包在该传输阶段的传输时长确定的，Y为大于0的整数。
在一个示例中，对于传输路径中的每个传输阶段，测量设备可能会测量Y个数据包的传输时长，测量设备可以将这Y个数据包的传输时长上报至数据管理服务生产者实体。数据管理服务生产者实体可以将这Y个传输时长的平均值(或者Y个传输时长的中位传输时长)作为通信业务在该传输阶段的传输时长，在该情况下，数据管理服务生产者实体上报的时延测量数据指示的传输时长为这Y个数据包的传输时长的平均值(或者Y个传输时长的中位传输时长)。
S403a：数据管理服务生产者实体向时延数据分析实体发送多条时延测量数据。
实现方式二：数据收集服务生产者实体已经根据通信业务的数据收集任务，预先存储了相应的时延测量数据。
S401b：时延数据分析实体向数据收集服务生产者实体发送数据请求消息。
第一种可能的实现方式中，数据请求消息中包括的信息可以实现方式一中的测量任务配置消息，即数据请求消息可以包括以下一项或多项信息：
业务信息；测量指标信息；测量设备的标识信息；数据流方向信息；测量时间信息；上报周期信息。
数据请求消息中包括的其它信息的具体内容可以实现方式一中的描述，在此不再赘述。
第二种可能的实现方式中，如果数据收集服务生产者实体已经为通信业务创建了相应的数据收集任务，一个数据收集任务可以对应一个任务标识，那么数据请求消息可以包括以下一项或多项信息：
通信业务对应的任务标识；测量时间信息；上报周期信息。
数据收集服务生产者实体根据任务标识可以确定该通信业务对应的以下至少一项信息：业务信息；测量指标信息；测量设备的标识信息；数据流方向信息。
其中，和实现方式一的区别在于，该步骤中数据请求消息中的测量时间信息指示的时间，可以位于确定对通信业务进行时延分析的时间之前，也就是说，数据请求消息可以请求获取确定对通信业务进行时延分析的时间之前的时延测量数据(即历史时延测量数据)，从而使得进行时延分析的时延测量数据的来源更广泛，可以提高时延分析的准确性。举例来说，测量时间信息用于指示测量位于时间T1至时间T2之间传输的数据包的时延测量数据，确定对通信业务进行时延分析的时间为T0，此时T1可以位于T0之前。
S402b：数据管理服务生产者实体向时延数据分析实体发送多条时延测量数据。
在实现方式二中，数据管理服务生产者实体已经预先存储了时延测量数据，因此可以直接向时延数据分析实体发送时延测量数据。通过这种方法，可以实现提前测量并存储通信业务的数据包的时延测量数据，从而可以在需要对通信业务进行时延分析时，及时获取时延测量数据，提高时延分析的效率。
以上只是示例，时延数据分析实体还可以通过其他方式获取时延测量数据，本申请对此并不限定。
S308：时延数据分析实体基于分析规则以及多条时延测量数据得到时延分析结果。
其中，时延分析结果用于指示通信业务在传输路径中存在时延故障的传输阶段。本申请中，时延故障也可以替换为时延问题(latency issue)。
如前所述，本申请中，分析规则可以为第一规则或者第二规则。在一个示例中，如果分析规则为第一规则，对于通信业务的传输路径中的任一传输阶段，如果该传输阶段在多条时延测量数据中对应的时延测量数据大于或等于该传输阶段对应的第一时延阈值，时延数据分析实体则可以确定通信业务在该传输阶段中存在时延故障；如果该传输阶段在多条时延测量数据中对应的时延测量数据小于该传输阶段对应的第一时延阈值，时延数据分析实体则可以确定通信业务在该传输阶段中不存在时延故障。
可选地，对于通信业务的传输路径中的任一传输阶段，如果该传输阶段在多条时延测量数据中对应至少两条时延测量数据，则只要其中一条时延测量数据大于或等于该传输阶段对应的第一时延阈值，就可以确定该传输阶段存在时延故障。相应的，时延分析结果中还可以包括每个传输阶段对应的时延测量数据中，大于或等于该传输阶段对应的第一时延阈值的时延测量数据的数量或者比例等信息。
进一步可选地，时延分析结果中还可以包括故障等级信息，故障等级信息用于指示存在时延故障的传输阶段的故障等级。故障等级可以表示时延故障的严重程度，例如故障等级可以包括一级故障和二级故障，一级故障的严重程度比二级故障的严重程度高。举例来说，对于存在时延故障的任一传输阶段，如果该传输阶段在多条时延测量数据中对应至少两条时延测量数据，该传输阶段的故障等级根据至少两条时延测量数据中大于或等于该传输阶段对应的第一时延阈值的时延测量数据的数量或者比例确定。例如，如果这至少两条时延测量数据中大于或等于该传输阶段对应的第一时延阈值的时延测量数据的数量，大于或等于预设数量，则故障等级为一级故障；如果这至少两条时延测量数据中大于或等于该传输阶段对应的第一时延阈值的时延测量数据的数量，小于预设数量，则故障等级为二级故障。
在一个示例中，如果分析规则为第二规则，对于通信业务的传输路径中的任一传输阶段，如果该传输阶段在多条时延测量数据中对应的时延测量数据与该通信业务在该传输路径中的总时延的比值大于或等于该传输阶段对应的第二时延阈值，时延数据分析实体则可以确定该通信业务在该传输阶段中存在时延故障；如果该传输阶段在多条时延测量数据中对应的时延测量数据与该通信业务在该传输路径中的总时延的比值小于该传输阶段对应的第二时延阈值，时延数据分析实体则可以确定该通信业务在该传输阶段中不存在时延故障。
其中，该通信业务在该传输路径中的总时延，可以根据该通信业务在该传输路径中各个传输阶段的时延测量数据确定，也可以由数据管理服务生产者实体上报至时延数据分析实体。
可选地，对于通信业务的传输路径中的任一传输阶段，如果该传输阶段在多条时延测量数据中对应至少两条时延测量数据，则只要其中一条时延测量数据大于或等于该传输阶段对应的第二时延阈值，就可以确定该传输阶段存在时延故障。相应的，时延分析结果中还可以包括每个传输阶段对应的时延测量数据中，大于或等于该传输阶段对应的第二时延 阈值的时延测量数据的数量或者比例等信息。
进一步可选地，时延分析结果中还可以包括故障等级信息。举例来说，对于存在时延故障的任一传输阶段，如果该传输阶段在多条时延测量数据中对应至少两条时延测量数据，例如，如果这至少两条时延测量数据中大于或等于该传输阶段对应的第二时延阈值的时延测量数据的比例，大于或等于预设比例，则故障等级为一级故障；如果这至少两条时延测量数据中大于或等于该传输阶段对应的第二时延阈值的时延测量数据的比例，小于预设比例，则故障等级为二级故障。
通过上面的方法，在对通信业务进行时延分析时，分析规则是由时延数据请求实体向时延数据分析实体配置的，通过分析规则可以对通信业务在传输路径中的各个传输阶段的时延测量数据进行分析，从而确定通信业务在每个传输阶段是否存在时延故障，因此时延分析的结果更准确，能够准确的对时延故障进行定位。
进一步的，图3的流程中，如果时延数据分析实体确定通信业务在传输路径中的至少一个传输阶段存在时延故障，时延数据分析实体还可以向知识管理实体查询时延故障的根因以及故障解决方法，具体可以如图5所示，为本申请实施例提供的一种时延分析方法的示意图。
S501：时延数据分析实体向知识管理实体发送根因请求信息以及时延分析结果。
其中，所述时延分析结果指示所述通信业务在所述传输路径中的M个传输阶段存在时延故障，M为大于0的整数；根因请求信息用于请求存在时延故障的M个传输阶段对应的根因。
S502：知识管理实体向时延数据分析实体发送根因指示信息，根因指示信息用于指示M个传输阶段中每个传输阶段存在时延故障的根因。
其中，知识管理实体中可以包括根因知识图谱(或者也可以称为根因故障树)，根因知识图谱包括各个传输阶段的时延故障和根因的对应关系等信息，知识管理实体可以根据根因知识图谱确定M个传输阶段中每个传输阶段存在时延故障的根因。
当然，知识管理实体也可以通过其他发送确定每个传输阶段存在时延故障的根因，本申请对知识管理实体具体如何确定根因并不限定。
可选地，知识管理实体也可以将根因知识图谱发送至时延数据分析实体，由时延数据分析实体根据根因知识图谱确定时延故障的根因，本申请对此并不限定。
S503：时延数据分析实体向知识管理实体发送故障解决请求信息。
其中，故障解决请求信息用于请求解决M个传输阶段的时延故障。
S501和S502可以通过一条消息发送，也可以分别通过不同的消息发送。S501和S502的执行顺序并不限定，可以同时执行，也可以先后执行。
如果S501和S502通过不同的消息发送，且S502位于S501之前，故障解决请求信息还可以包含时延分析结果。
S504：知识管理实体向时延数据分析实体发送故障解决方法信息。
其中，故障解决方法信息包含以下至少一项信息：
用于解决M个传输阶段的时延故障的网络配置动作；用于解决所述M个传输阶段的时延故障的网络配置参数。
其中，网络配置动作可以是指对网络中的设备进行配置所执行的动作，网络配置参数可以是指对网络中的设备进行配置所设置的参数。例如，当确定时延故障的根因为CPE存 在内存泄露时，网络配置动作可以是：重启CPE；当确定时延故障的根因为下行控制信息(downlink control information，DCI)虚警导致部分带宽(bandwidth part，BWP)切换，网络配置动作可以是：关闭接入网设备BWP切换的功能，或者网络配置参数可以是：参数“接入网设备BWP切换”的取值为“关闭”。
知识管理实体具体如何确定故障解决方法信息，本申请对此并不限定。例如，知识管理实体中可以包括各个传输阶段的时延故障的根因和网络配置动作的对应关系，以及各个传输阶段的时延故障的根因和网络配置参数的对应关系等信息，知识管理实体从而可以根据上述对应关系确定故障解决方法信息。
举例来说，知识管理实体中包括的各个传输阶段的时延故障的根因、网络配置动/或网络配置参数的对应关系可以如表3所示。
表3
知识管理实体可以根据上述对应关系确定各个传输阶段对应的根因、以及网络配置动/或网络配置参数。
S505：时延数据分析实体向时延数据请求实体发送时延分析结果、根因指示信息以及故障解决方法信息中的至少一项。
可以理解地，时延数据分析实体还可以向时延数据请求实体发送其他信息，例如发送以下至少一项信息：
业务信息；通信业务的分析类型信息；通信业务的分析粒度信息；数据流方向信息；分析时间信息；测量设备的标识信息。
S506：时延数据请求实体根据时延分析结果、根因指示信息以及故障解决方法信息中的至少一项生成解决通信业务在传输路径中M个传输阶段的时延故障的指示信息。
本申请中，在一个示例中，时延数据请求实体可以将指示信息下发至网络配置动作和 /或网络配置参数对应的设备，例如下发至接入网设备、CPE、或UPF中的至少一项，时延数据请求实体生成的指示信息可以指示这些设备执行网络配置动作和/或按照网络配置参数进行配置，解决M个传输阶段的时延故障。
在另一个示例中，时延数据请求实体可以将指示信息以可视化界面显示给操作者，由操作者执行该指示信息指示的网络配置动作和/或网络配置参数的配置命令。
时延数据请求实体生成的指示信息所指示的网络配置动作和/或网络配置参数可能有以下几种实现方式：
第一种可能的实现方式中，如果时延数据分析实体向时延数据请求实体发送时延分析结果，没有发送根因指示信息以及故障解决方法信息，那么时延数据请求实体可以根据时延分析结果确定M个传输阶段时延故障的根因，并根据M个传输阶段时延故障的根因确定用于解决所述M个传输阶段的时延故障的网络配置动作和/或网络配置参数。具体确定方法并不限定，例如，时延数据请求实体可以向知识管理设备请求M个传输阶段的根因、网络配置动作和/或网络配置参数。再例如，对于存在时延故障的传输阶段，可以通过人工排查确定时延故障的根因，时延数据请求实体根据确定的根因以及人工经验确定时延故障的网络配置动作或网络配置参数。本申请中，也可以通过其他方式确定根因指示信息和故障解决方法信息，在此不再赘述。
在该实现方式中，时延数据分析实体生成的指示信息指示的网络配置动作和/或网络配置参数是时延数据分析实体根据时延分析结果确定的。
第二种可能的实现方式中，如果时延数据分析实体向时延数据请求实体发送时延分析结果，没有发送故障解决方法信息，那么时延数据请求实体可以根据根因指示信息确定用于解决所述M个传输阶段的时延故障的网络配置动作和/或网络配置参数。例如，时延数据请求实体可以向知识管理设备请求故障解决方法信息。再例如，时延数据请求实体根据根因指示信息和/或人工经验确定时延故障的网络配置动作和/或网络配置参数。
在该实现方式中，时延数据分析实体生成的指示信息指示的网络配置动作和/或网络配置参数是时延数据分析实体根据根因指示信息确定的。
第三种可能的实现方式中，如果时延数据分析实体向时延数据请求实体发送故障解决方法信息，那么时延数据请求实体可以直接将故障解决方法信息指示的网络配置动作和/或网络配置参数作为解决时延故障所使用的网络配置动作和/或网络配置参数。
在该实现方式中，时延数据分析实体生成的指示信息指示的网络配置动作和/或网络配置参数是时延数据分析实体根据故障解决方法信息确定的。
第四种可能的实现方式中，如果时延数据分析实体向时延数据请求实体发送时延分析结果、根因指示信息以及故障解决方法信息，那么时延数据请求实体可以根据根因指示信息和/或人工经验确定对故障解决方法信息指示的网络配置动作和/或网络配置参数进行修正，并将修正后的网络配置动作和/或网络配置参数下发至相应的设备。
在该实现方式中，时延数据分析实体生成的指示信息指示的网络配置动作和/或网络配置参数是时延数据分析实体根据故障解决方法信息和/或人工经验确定的。
结合前面的描述，以图1所示的5G toB场景为例，企业园区的私有网络中会部署大量的CPE，该CPE作为无线接入点为三个终端设备提供服务，其中CPE为终端设备1提供视频监控回传业务，还为终端设备2和终端设备3分别提供远程控制指令业务和数据传输业务。假如CPE在转发视频回传业务时出现上行丢包或乱序，但是其他通信业务的数据包 传输正常。
根据本申请提供的方法，一种可能的实现方式中，应用服务器检测到终端设备1回传的视频卡顿，因此应用服务器向时延数据请求实体发送维测请求消息，并且在该维测请求消息中携带终端设备1的标识或视频监控回传业务的标识。
时延数据请求实体向时延数据分析实体请求对视频监控回传业务进行时延分析，具体可以向时延数据分析实体发送业务信息、分析规则信息、通信业务的分析类型信息、通信业务的分析粒度信息、数据流方向信息、分析时间信息、测量设备的标识信息以及阈值信息等。
时延数据分析实体可以根据上述信息确定需要对终端设备1的视频监控回传业务进行时延分析。时延数据分析实体可以从数据收集服务生产者实体获取多条时延测量数据，该多条时延测量数据是CPE、UPF、以及接入网设备测量获得的。
进一步的，时延数据分析实体基于多条测量数据进行时延分析，进而可以确定视频监控回传业务在CPE传输阶段存在时延故障。
进一步的，时延数据分析实体可以通过知识管理实体确定时延故障的根因可能是CPE在传输视频回传业务时，出现上行丢包或乱序。
进一步的，时延数据分析实体可以通过知识管理实体确定该根因的故障解决方法信息包含的网络配置动作为：重新启动CPE。
进一步的，时延数据分析实体可以将该故障解决方法信息返回至时延数据请求实体。时延数据请求实体从而可以根据故障解决方法信息向CPE发送指示信息，该指示信息用于指示CPE执行以下为了配置动作：重新启动CPE。
根据本申请提供的方法，另一种可能的实现方式中，在时间T0，应用服务器检测到终端设备1回传的视频卡顿，因此应用服务器向时延数据请求实体发送维测请求消息，并且在该维测请求消息中携带终端设备1的标识或视频监控回传业务的标识。
时延数据请求实体向时延数据分析实体请求对CPE中的每一个通信业务进行时延分析，具体的，时延数据请求实体可以向时延数据分析实体指示对时间T1至时间T2之间的所有通信业务进行时延分析，时间T0位于时间T1至时间T2之间。
时延数据分析实体可以根据上述信息确定需要对所有通信业务进行时延分析。时延数据分析实体可以从数据收集服务生产者实体获取多条时延测量数据，该多条时延测量数据是CPE、UPF、以及接入网设备测量获得的。
进一步的，时延数据分析实体基于多条测量数据进行时延分析，进而可以确定只有视频监控回传业务出现时延问题，其它通信业务没有时延问题。具体的，可以确定视频监控回传业务在CPE传输阶段存在时延故障。
进一步的，时延数据分析实体可以通过知识管理实体确定时延故障的根因可能是CPE在传输视频回传业务时，出现上行丢包或乱序。
进一步的，时延数据分析实体可以通过知识管理实体确定该根因的故障解决方法信息包含的网络配置动作为：重新启动CPE。
进一步的，时延数据分析实体可以将该故障解决方法信息返回至时延数据请求实体。时延数据请求实体从而可以根据故障解决方法信息向CPE发送指示信息，该指示信息用于指示CPE执行以下为了配置动作：重新启动CPE。
可以理解，本申请实施例中的图3至图5中的例子仅仅是为了便于本领域技术人员理 解本申请实施例，并非要将本申请实施例限于例示的具体场景。本领域技术人员根据图3至图5的例子，显然可以进行各种等价的修改或变化，这样的修改或变化也落入本申请实施例的范围内。例如，上述图3至图5中通信业务可以替换为一个或多个通信业务。
还可以理解，上述图3至图5中各个步骤仅是示例性说明，对此不作严格限定。此外，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
还可以理解，本申请的各实施例中的一些可选的特征，在某些场景下，可以不依赖于其他特征，也可以在某些场景下，与其他特征进行结合，不作限定。
还可以理解，本申请的各实施例中的方案可以进行合理的组合使用，并且实施例中出现的各个术语的解释或说明可以在各个实施例中互相参考或解释，对此不作限定。
还可以理解，在本申请的各实施例中的各种数字序号的大小并不意味着执行顺序的先后，仅为描述方便进行的区分，不应对本申请实施例的实施过程构成任何限定。
还可以理解，在本申请的各实施例中涉及到一些消息名称，如维测请求消息等，其命名不对本申请实施例的保护范围造成限定。
还可以理解，在上述一些实施例中，多次提及进行染色处理，其表示的是对数据包进行染色处理，或者说将数据包与测量标识进行关联。
相应于上述各方法实施例给出的方法，本申请实施例还提供了相应的装置，所述装置包括用于执行上述各个方法实施例相应的模块。该模块可以是软件，也可以是硬件，或者是软件和硬件结合。可以理解的是，上述各方法实施例所描述的技术特征同样适用于以下装置实施例。
图6是本申请实施例提供的通信装置的示意性框图。该通信装置600包括通信单元610和处理单元620。通信单元610可以实现相应的通信功能，通信单元610还可以为通信接口或通信单元。处理单元620可以实现相应的处理功能，如处理指令和/或数据。
一种可能的实现方式，该通信装置600还可以包括存储单元，该存储单元可以用于存储指令和/或数据，处理单元620可以读取存储单元中的指令和/或数据，以使得装置实现前述方法实施例。
该通信装置600可以用于执行上文方法实施例中时延数据请求实体或时延数据分析实体所执行的动作，这时，该通信装置600中的通信单元610用于执行上文方法实施例中时延数据请求实体或时延数据分析实体侧的收发相关的操作，处理单元620用于执行上文方法实施例中时延数据请求实体或时延数据分析实体侧的处理相关的操作。
作为一种设计，该通信装置600用于执行上文方法实施例中时延数据分析实体所执行的动作：
通信单元，用于接收来自于时延数据请求实体的业务信息以及分析规则信息；其中，所述业务信息用于指示待时延分析的通信业务；所述分析规则信息用于指示对所述通信业务进行时延分析所采用的分析规则；获取所述通信业务的数据包的多条时延测量数据，其中，每一条时延测量数据指示所述通信业务的数据包在传输路径中的至少一个传输阶段的传输时长；
处理单元，用于基于所述分析规则以及所述多条时延测量数据得到时延分析结果；所述时延分析结果用于指示所述通信业务在所述传输路径中存在时延故障的传输阶段。
作为一种设计，该通信装置600用于执行上文方法实施例中时延数据请求实体所执行 的动作：
处理单元，用于确定业务信息以及分析规则信息；其中，所述业务信息用于指示待时延分析的通信业务；所述分析规则信息用于指示对所述通信业务进行时延分析所采用的分析规则；
通信单元，用于向时延数据分析实体发送所述业务信息以及所述分析规则信息；接收来自所述时延数据分析实体的时延分析结果，所述时延分析结果用于指示所述通信业务在传输路径中存在时延故障的传输阶段。
以上只是示例，处理单元620和通信单元610还可以执行其他功能，更详细的描述可以参考图3至图5所示的方法实施例中相关描述，这里不加赘述。
如图7所示为本申请实施例提供的通信装置，图7所示的通信装置可以为图6所示的通信装置的一种硬件电路的实现方式。该通信装置可适用于前面所示出的流程图中，执行上述方法实施例中时延数据请求实体或时延数据分析实体的功能。为了便于说明，图7仅示出了该通信装置的主要部件。
如图7所示，通信装置700包括处理器710和接口电路720。处理器710和接口电路720之间相互耦合。可以理解的是，接口电路720可以为收发器、管脚或输入输出接口。可选的，通信装置700还可以包括存储器730，用于存储处理器710执行的指令或存储处理器710运行指令所需要的输入数据或存储处理器710运行指令后产生的数据。可选地，存储器730的部分或全部可以位于处理器710中。
当通信装置700用于实现图3至图5所示的方法时，处理器710用于实现上述处理单元620的功能，接口电路720用于实现上述通信单元610的功能。
可以理解的是，本申请的实施例中的处理器可以是中央处理单元，还可以是其它通用处理器、数字信号处理器、专用集成电路或者其它可编程逻辑器件、晶体管逻辑器件，硬件部件或者其任意组合。通用处理器可以是微处理器，也可以是任何常规的处理器。
本申请的实施例中的存储器可以是随机存取存储器、闪存、只读存储器、可编程只读存储器、可擦除可编程只读存储器、电可擦除可编程只读存储器、寄存器、硬盘、移动硬盘或者本领域熟知的任何其它形式的存储介质中。
需要说明的是，当处理器为通用处理器、DSP、ASIC、FPGA或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件时，存储器(存储模块)可以集成在处理器中。
还需要说明的是，本文描述的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生 一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (23)

  1. 一种时延分析方法，其特征在于，包括：
    时延数据分析实体接收来自于时延数据请求实体的业务信息以及分析规则信息；其中，所述业务信息用于指示待时延分析的通信业务；所述分析规则信息用于指示对所述通信业务进行时延分析所采用的分析规则；
    所述时延数据分析实体获取所述通信业务的数据包的多条时延测量数据，其中，每一条时延测量数据指示所述通信业务的数据包在传输路径中的至少一个传输阶段的传输时长；
    所述时延数据分析实体基于所述分析规则以及所述多条时延测量数据得到时延分析结果；所述时延分析结果用于指示所述通信业务在所述传输路径中存在时延故障的传输阶段。
  2. 根据权利要求1所述的方法，其特征在于，所述分析规则信息指示的所述分析规则为第一规则时，对于所述传输路径中的任一传输阶段，所述传输阶段对应第一时延阈值；
    所述第一规则包括：对于所述传输路径中的任一传输阶段，如果所述传输阶段在所述多条时延测量数据中对应的时延测量数据大于或等于所述传输阶段对应的第一时延阈值，则所述通信业务在所述传输阶段中存在时延故障；如果所述传输阶段在所述多条时延测量数据中对应的时延测量数据小于所述传输阶段对应的第一时延阈值，则所述通信业务在所述传输阶段中不存在时延故障。
  3. 根据权利要求2所述的方法，其特征在于，所述第一时延阈值为所述分析规则信息指示的；
    或者，所述第一时延阈值为根据所述第一时延阈值对应的所述传输阶段的历史时延测量数据确定的；
    或者，所述第一时延阈值为知识管理实体配置的。
  4. 根据权利要求1所述的方法，其特征在于，所述分析规则信息指示的所述分析规则为第二规则时，对于所述传输路径中的任一传输阶段，所述传输阶段对应第二时延阈值；
    所述第二规则包括：对于所述传输路径中的任一传输阶段，如果所述传输阶段在所述多条时延测量数据中对应的时延测量数据与所述通信业务在所述传输路径中的总时延的比值大于或等于所述传输阶段对应的第二时延阈值，则所述通信业务在所述传输阶段中存在时延故障；如果所述传输阶段在所述多条时延测量数据中对应的时延测量数据与所述总时延的比值小于所述传输阶段对应的第二时延阈值，则所述通信业务在所述传输阶段中不存在时延故障。
  5. 根据权利要求4所述的方法，其特征在于，所述第二时延阈值为所述分析规则信息指示的；
    或者，所述第二时延阈值为知识管理实体配置的。
  6. 根据权利要求1至5任一所述的方法，其特征在于，如果所述时延分析结果指示所述通信业务在所述传输路径中的M个传输阶段存在时延故障，M为大于0的整数，所述方法还包括：
    所述时延数据分析实体向知识管理实体发送根因请求信息以及所述时延分析结果，所述根因请求信息用于请求存在时延故障的所述M个传输阶段对应的根因；
    所述时延数据分析实体接收来自所述知识管理实体的根因指示信息，所述根因指示信息用于指示所述M个传输阶段中每个传输阶段存在时延故障的根因。
  7. 根据权利要求1至6任一所述的方法，其特征在于，所述时延分析结果指示存在时延故障的传输阶段包括以下一项或多项：
    无线接入网传输阶段；核心网传输阶段；传输网传输阶段；用户驻地设备传输阶段；空口传输阶段。
  8. 根据权利要求1至7任一所述的方法，其特征在于，如果所述时延分析结果指示所述通信业务在所述传输路径中的M个传输阶段存在时延故障，M为大于0的整数，所述方法还包括：
    所述时延数据分析实体向知识管理实体发送故障解决请求信息，所述故障解决请求信息包含所述时延分析结果，所述故障解决请求信息用于请求解决所述M个传输阶段的时延故障；
    所述时延数据分析实体接收来自所述知识管理实体的故障解决方法信息，所述故障解决方法信息包含用于解决所述M个传输阶段的时延故障的网络配置动作和/或用于解决所述M个传输阶段的时延故障的网络配置参数。
  9. 根据权利要求1至8任一所述的方法，其特征在于，如果所述时延分析结果指示所述通信业务在所述传输路径中的M个传输阶段存在时延故障，M为大于0的整数，所述方法还包括：
    所述时延数据分析实体向所述时延数据请求实体发送以下至少一项信息：
    所述时延分析结果；
    根因指示信息，所述根因指示信息用于指示所述M个传输阶段中每个传输阶段存在时延故障的根因；
    故障解决方法信息，所述故障解决方法信息包含用于解决所述M个传输阶段的时延故障的网络配置动作和/或用于解决所述M个传输阶段的时延故障的网络配置参数。
  10. 一种时延分析方法，其特征在于，包括：
    时延数据请求实体确定业务信息以及分析规则信息；其中，所述业务信息用于指示待时延分析的通信业务，所述通信业务为面向企业的通信业务；所述分析规则信息用于指示对所述通信业务进行时延分析所采用的分析规则；
    所述时延数据请求实体向时延数据分析实体发送所述业务信息以及所述分析规则信息；
    所述时延数据请求实体接收来自所述时延数据分析实体的时延分析结果，所述时延分析结果用于指示所述通信业务在传输路径中存在时延故障的传输阶段。
  11. 根据权利要求10所述的方法，其特征在于，所述分析规则信息指示的所述分析规则为第一规则时，对于所述传输路径中的任一传输阶段，所述传输阶段对应第一时延阈值；
    所述第一规则包括：对于所述传输路径中的任一传输阶段，如果所述传输阶段在所述多条时延测量数据中对应的时延测量数据大于或等于所述传输阶段对应的第一时延阈值，则所述通信业务在所述传输阶段中存在时延故障；如果所述传输阶段在所述多条时延测量数据中对应的时延测量数据小于所述传输阶段对应的第一时延阈值，则所述通信业务在所述传输阶段中不存在时延故障。
  12. 根据权利要求11所述的方法，其特征在于，所述第一时延阈值为所述分析规则信 息指示的；
    或者，所述第一时延阈值为根据所述第一时延阈值对应的所述传输阶段的历史时延测量数据确定的；
    或者，所述第一时延阈值为知识管理实体配置的。
  13. 根据权利要求10所述的方法，其特征在于，所述分析规则信息指示的所述分析规则为第二规则时，对于所述传输路径中的任一传输阶段，所述传输阶段对应第二时延阈值；
    所述第二规则包括：对于所述传输路径中的任一传输阶段，如果所述传输阶段在所述多条时延测量数据中对应的时延测量数据与所述通信业务在所述传输路径中的总时延的比值大于或等于所述传输阶段对应的第二时延阈值，则所述通信业务在所述传输阶段中存在时延故障；如果所述传输阶段在所述多条时延测量数据中对应的时延测量数据与所述总时延的比值小于所述传输阶段对应的第二时延阈值，则所述通信业务在所述传输阶段中不存在时延故障。
  14. 根据权利要求13所述的方法，其特征在于，所述第二时延阈值为所述分析规则信息指示的；
    或者，所述第二时延阈值为知识管理实体配置的。
  15. 根据权利要求10至14任一所述的方法，其特征在于，所述时延分析结果指示存在时延故障的传输阶段包括以下一项或多项：
    无线接入网传输阶段；核心网传输阶段；传输网传输阶段；用户驻地设备传输阶段；空口传输阶段。
  16. 根据权利要求10至15任一所述的方法，其特征在于，如果所述时延分析结果指示所述通信业务在所述传输路径中的M个传输阶段存在时延故障，M为大于0的整数，所述方法还包括：
    所述时延数据请求实体接收来自所述时延数据分析实体的以下至少一项信息：
    根因指示信息，所述根因指示信息用于指示所述M个传输阶段中每个传输阶段存在时延故障的根因；
    故障解决方法信息，所述故障解决方法信息包含用于解决所述M个传输阶段的时延故障的网络配置动作和/或用于解决所述M个传输阶段的时延故障的网络配置参数。
  17. 根据权利要求16所述的方法，其特征在于，所述方法还包括：
    所述时延数据请求实体根据所述时延分析结果、所述根因指示信息以及所述故障解决方法信息中的至少一项生成解决所述通信业务在所述M个传输阶段的时延故障的指示信息。
  18. 一种时延数据分析实体，其特征在于，包括：
    通信单元，用于接收来自于时延数据请求实体的业务信息以及分析规则信息；其中，所述业务信息用于指示待时延分析的通信业务，所述通信业务为面向企业的通信业务；所述分析规则信息用于指示对所述通信业务进行时延分析所采用的分析规则；获取所述通信业务的数据包的多条时延测量数据，其中，每一条时延测量数据指示所述通信业务的数据包在传输路径中的至少一个传输阶段的传输时长；
    处理单元，用于基于所述分析规则以及所述多条时延测量数据得到时延分析结果；所述时延分析结果用于指示所述通信业务在所述传输路径中存在时延故障的传输阶段。
  19. 一种时延数据请求实体，其特征在于，包括：
    处理单元，用于确定业务信息以及分析规则信息；其中，所述业务信息用于指示待时延分析的通信业务，所述通信业务为面向企业的通信业务；所述分析规则信息用于指示对所述通信业务进行时延分析所采用的分析规则；
    通信单元，用于向时延数据分析实体发送所述业务信息以及所述分析规则信息；接收来自所述时延数据分析实体的时延分析结果，所述时延分析结果用于指示所述通信业务在传输路径中存在时延故障的传输阶段。
  20. 一种时延数据分析实体，其特征在于，包括处理器，所述处理器和存储器耦合，所述存储器中存储有计算机程序；所述处理器用于调用所述存储器中的计算机程序，使得所述时延数据分析实体执行如权利要求1至9任一所述的方法。
  21. 一种时延数据请求实体，其特征在于，包括处理器，所述处理器和存储器耦合，所述存储器中存储有计算机程序；所述处理器用于调用所述存储器中的计算机程序，使得所述时延数据请求实体执行如权利要求10至17任一所述的方法。
  22. 一种通信系统，其特征在于，所述通信系统包括如权利要求18或20所述的时延数据分析实体，以及如权利要求19或21所述的时延数据请求实体。
  23. 一种计算机可读存储介质，其特征在于，所述存储介质中存储有计算机程序或指令，当所述计算机程序或指令被计算机执行时，实现如权利要求1至9中任一项所述的方法，或如权利要求10至17中任一项所述方法。
PCT/CN2023/081381 2022-03-17 2023-03-14 一种时延分析方法及装置 WO2023174287A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210264917.7A CN116806035A (zh) 2022-03-17 2022-03-17 一种时延分析方法及装置
CN202210264917.7 2022-03-17

Publications (1)

Publication Number Publication Date
WO2023174287A1 true WO2023174287A1 (zh) 2023-09-21

Family

ID=88022322

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/081381 WO2023174287A1 (zh) 2022-03-17 2023-03-14 一种时延分析方法及装置

Country Status (2)

Country Link
CN (1) CN116806035A (zh)
WO (1) WO2023174287A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102959899A (zh) * 2011-05-30 2013-03-06 华为技术有限公司 一种网络传输特性分析方法、装置及系统
US20180131559A1 (en) * 2016-06-14 2018-05-10 TUPL, Inc. Fixed line resource management
CN108206753A (zh) * 2016-12-19 2018-06-26 华为技术有限公司 一种检测时延的方法、装置及系统
CN111030873A (zh) * 2019-12-24 2020-04-17 迈普通信技术股份有限公司 一种故障诊断方法及装置
CN111328086A (zh) * 2018-12-14 2020-06-23 中国移动通信集团河南有限公司 一种定位呼叫接通时延异常段的方法及系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102959899A (zh) * 2011-05-30 2013-03-06 华为技术有限公司 一种网络传输特性分析方法、装置及系统
US20180131559A1 (en) * 2016-06-14 2018-05-10 TUPL, Inc. Fixed line resource management
CN108206753A (zh) * 2016-12-19 2018-06-26 华为技术有限公司 一种检测时延的方法、装置及系统
CN111328086A (zh) * 2018-12-14 2020-06-23 中国移动通信集团河南有限公司 一种定位呼叫接通时延异常段的方法及系统
CN111030873A (zh) * 2019-12-24 2020-04-17 迈普通信技术股份有限公司 一种故障诊断方法及装置

Also Published As

Publication number Publication date
CN116806035A (zh) 2023-09-26

Similar Documents

Publication Publication Date Title
US10326640B2 (en) Knowledge base radio and core network prescriptive root cause analysis
US11122457B2 (en) Management apparatus and method to support WLAN offloading
JP7147063B2 (ja) ユーザアクセス制御方法、情報送信方法および装置
US9325568B2 (en) Technique for determining correlated events in a communication system
WO2018121237A1 (zh) 网络质量检测方法及装置
US20220150130A1 (en) Training method for application mos model, device, and system
CN111614563A (zh) 一种用户面路径的选择方法及装置
US20220217070A1 (en) Network OAM Method and Apparatus
US9407522B2 (en) Initiating data collection based on WiFi network connectivity metrics
US20170302539A1 (en) Method and apparatus for managing user quality of experience in network
CN114095956B (zh) 网络优化方法、装置及存储介质
WO2021093574A1 (zh) 网络质量检测方法、装置、网元设备、计算机设备和计算机可读介质
US20140280904A1 (en) Session initiation protocol testing control
US11336545B2 (en) Network device measurements employing white boxes
JP2022532731A (ja) スライスベースネットワークにおける輻輳回避
US11665531B2 (en) End to end troubleshooting of mobility services
CN113542050A (zh) 网络性能监控方法、装置及系统
WO2020063050A1 (zh) 数据传输方法及装置
US20160242140A1 (en) Automated equipment characterization from wireless network data
Laselva et al. Advancements of QoE assessment and optimization in mobile networks in the machine era
CN110958170B (zh) 一种网络互联方法和装置
KR20230029943A (ko) 정보 전달 방법, 장치, 저장 매체 및 전자 장치
US11652682B2 (en) Operations management apparatus, operations management system, and operations management method
CN110875825A (zh) 故障判决方法及装置
WO2023174287A1 (zh) 一种时延分析方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23769789

Country of ref document: EP

Kind code of ref document: A1