Measuring method and measuring device

Abstract

The present application provides a measurement method and a measurement device, which can be used in various communication fields, such as 5G, 6G, 5GtoB, end-to-end, device-to-device, machine-to-machine, vehicle-to-everything, Internet of Things and other fields. The method includes: a management device sends a measurement identifier to a measurement device, and the measurement identifier is used to associate with a target service to be measured, and the target service is a service corresponding to a data flow passing through an industry terminal (such as CPE); the management device sends a measurement indication to the measurement device, and the measurement indication is used to indicate the measurement of the performance indicators of the target service associated with the measurement identifier, wherein the performance indicators of the target service are associated with abnormal events (or faults) of the target service. Thus, the measurement device can quickly identify the service data packets to be measured based on whether the service has an associated measurement identifier, and realize performance data statistics based on a finer granularity (i.e., service granularity), thereby improving the accuracy of fault diagnosis and analysis.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and more specifically, to a measurement method and a measurement device. Background Art

[0002] In mobile networks, operators are network communication service providers, mainly responsible for network construction and daily operation and maintenance management. Network operation and maintenance management includes network configuration management, performance management and fault management. Among them, fault management is one of the key and difficult points of operator network management. At present, the network fault management mechanism defined in the 3rd Generation Partnership Project (3GPP) standard is mainly aimed at fault management of network equipment.

[0003] However, in some scenarios, such as the fifth generation (5G) toB scenario, a large number of industry terminals, such as customer-premises equipment (CPE), will be deployed in the network. Taking CPE as an example, CPE can be used as a terminal device to connect to the access network device through wireless technology to obtain wireless network services; on the other hand, it can be used as a wireless access point to provide wireless access functions for other terminal devices (such as PLC, cameras, etc.). So for scenarios where similar industry terminals are deployed, how to perform measurements for fault diagnosis and analysis is a problem that needs to be solved. Summary of the invention

[0004] The present application provides a measurement method and a measurement device, which measure performance data based on a finer granularity (ie, a service granularity), and then perform fault diagnosis and analysis based on the measured performance data.

[0005] In the first aspect, the embodiment of the present application provides a measurement method. The method can be executed by a communication device, or can also be executed by a component (such as a chip or circuit) of the communication device, without limitation, and for ease of description, the following is described by taking the execution by a management device as an example.

[0006] The method may include: a management device sends a measurement identifier to a measuring device, the measurement identifier is used to associate with a target service to be measured, the target service is a service corresponding to a data flow passing through an industry terminal; the management device sends a measurement indication to the measuring device, the measurement indication is used to indicate measurement of a performance indicator of the target service associated with the measurement identifier, the performance indicator of the target service is associated with an abnormal event of the target service.

[0007] As an example, an industry terminal can be used as a terminal device to connect to an access network device through wireless technology to obtain wireless network services, or as a wireless access point to provide wireless access functions for other terminal devices. In one possible scenario, the industry terminal is, for example, customer-premises equipment (CPE).

[0008] The target service is the service corresponding to the data flow passing through the industry terminal, or it can be understood that the target service is the service to be measured on the industry terminal. As an example, the target service can be the service corresponding to the data flow sent to the application terminal through the industry terminal, or the service corresponding to the data flow sent by the application terminal through the industry terminal.

[0009] As an example, the target service includes, but is not limited to: a video service (such as a video surveillance backhaul service) and a remote control command service.

[0010] Based on the above technical solution, the management device can send a measurement identifier to the measuring device for associating the target service to be measured in the service corresponding to the data flow passing through the industry terminal, and the management device can also send a measurement instruction to the measuring device to indicate the performance indicator of the target service associated with the measurement identifier to be measured. Thus, the measuring device can quickly identify the service data packet to be measured based on whether the service has an associated measurement identifier, and realize the statistics of performance data based on a finer granularity (i.e., service granularity). In this way, if fault diagnosis and analysis is required, abnormal fault diagnosis and analysis of service granularity can be performed based on the performance data of the service. Thus, the problem of inaccurate performance data analysis results based solely on the wireless network air interface can be overcome, and compared with the device-level fault diagnosis and analysis, the above technical solution improves the accuracy of fault diagnosis and analysis. For example, if the measuring device performs device-level fault diagnosis and analysis, the statistics are the average performance indicators of all services on the measuring device. Then, even if the performance indicators of some services on the measuring device are abnormal, since the real performance indicators of each service will be averaged, the final diagnostic analysis result may be that the measuring device has no abnormal problem, which leads to inaccurate fault diagnosis and analysis results and difficulty in locating faults. Therefore, the above technical solution can also overcome the above problem of inaccurate performance data analysis results based on the device level.

[0011] In combination with the first aspect, in some implementations of the first aspect, the method further includes: the management device configuring a measurement identifier for the target service.

[0012] Based on the above technical solution, the management device can configure a measurement identifier for the target service. In this way, the management device configures the measurement identifier and then sends it to the measurement device, avoiding the signaling overhead caused by other devices configuring the measurement identifier and sending it to the management device, and then the management device sending the measurement identifier to the measurement device.

[0013] In combination with the first aspect, in certain implementations of the first aspect, the method also includes: the management device sends one or more of the following information to the measurement device: the data packet type of the target service associated with the measurement identifier, the identifier of the target service, the user premises equipment identifier corresponding to the target service, or the identifier of the terminal device.

[0014] For example, the one or more pieces of information and the measurement identifier may be carried in the same signaling. In this way, the one or more pieces of information and the measurement identifier may be carried in the same signaling for transmission, which not only saves signaling overhead, but also facilitates the measurement device to obtain the measurement identifier and the one or more pieces of information based on the one signaling.

[0015] For example, the one or more pieces of information and the measurement identifier may be carried in different signaling. In this way, the one or more pieces of information and the measurement identifier may be carried in different signaling for transmission, so that the measurement identifier and the one or more pieces of information do not need to be bundled in one signaling for transmission, thereby making the transmission more flexible.

[0016] For example, the data packet type of the target service associated with the measurement identifier, that is, the data packet type that needs to be associated with the measurement identifier (or needs to be processed), includes, for example: an uplink data packet and / or a downlink data packet. As an example, the management device can determine the data packet type that needs to be associated with the measurement identifier based on an abnormal event of the target service.

[0017] For example, the identifier of the target service can be used to identify (or recognize) the target service. The identifier of the target service can be an IP 5-tuple.

[0018] For example, the user premises equipment identifier corresponding to the target service, such as the CPE identifier (CPE Id), can be used to identify (or recognize) the CPE. As an example, the CPE Id can be any of the following: the electronic serial number (equipment serial number, ESN) of the CPE, the IP address of the CPE, the globally unique temporary UE identity (globally unique temporary UE identity, 5G-GUTI) of the CPE, etc.

[0019] For example, the identifier of the terminal device (such as DeviceId) can be used to identify (or recognize) the device to which the target service occurs or the device where the abnormal event occurs.

[0020] In combination with the first aspect, in some implementations of the first aspect, the management device sends a measurement identifier to the measurement device, including: after the management device receives a maintenance request for maintenance testing of a target service, the management device sends the measurement identifier to the measurement device; or after the management device receives a monitoring request for monitoring a performance indicator of the target service, the management device sends the measurement identifier to the measurement device; or after the management device monitors that a terminal device is online, the management device sends the measurement identifier to the measurement device.

[0021] Based on the above technical solution, the timing or triggering condition for the management device to send the measurement identifier to the measuring device (or configure the measurement identifier for the target service) can be very flexible. For example, the management device can send the measurement identifier to the measuring device after receiving a request to perform maintenance on the target service. In this way, the measurement identifier can be configured for the service that needs maintenance according to the actual situation, and the measurement identifier can be sent to avoid the overhead caused by sending the measurement identifier of the service that is not necessary for maintenance. For another example, the management device can send the measurement identifier to the measuring device after receiving a request to monitor the performance indicators of the target service. In this way, the impact of the delay in transmitting the measurement identifier on data collection can be reduced, so that the collected data is the network status performance data when the network failure occurs, and the accuracy of fault diagnosis and analysis can be improved. For another example, the management device can send the measurement identifier to the measuring device after learning that the terminal device is online. In this way, the impact of the delay in transmitting the measurement identifier on data collection can be reduced, so that the collected data is the network status performance data when the network failure occurs, and the accuracy of fault diagnosis and analysis can be improved.

[0022] In combination with the first aspect, in some implementations of the first aspect, the method further includes: the management device receiving address information of the measuring device.

[0023] For example, the management device receives feedback from the measuring device on whether to associate the measurement identifier with the target service, and the feedback information includes address information of the measuring device.

[0024] Based on the above technical solution, the management device can also receive the address of the measuring device, which can be used to implement the routing of the subsequent management device sending related messages to the measuring device.

[0025] In combination with the first aspect, in certain implementations of the first aspect, the management device sends a measurement indication to the measuring device, including: after the management device receives a maintenance request for performing maintenance on a target service, the management device sends a measurement indication to the measuring device; or, after the management device receives a monitoring request for monitoring a performance indicator of the target service, the management device sends a measurement indication to the measuring device.

[0026] Based on the above technical solution, the timing or triggering condition for the management device to send a measurement indication to the measuring device can be very flexible. For example, the management device can send a measurement indication to the measuring device after receiving a request to perform maintenance on the target service. In this way, the performance data of the service that needs maintenance can be measured according to the actual situation, avoiding the overhead caused by measuring the performance data of the service that is not necessary to be maintained. For another example, the management device can send a measurement indication to the measuring device after receiving a request to monitor the performance indicators of the target service. In this way, data collection can be performed in advance, so that the collected data is the network status performance data when the network failure occurs, thereby improving the accuracy of fault diagnosis and analysis.

[0027] In combination with the first aspect, in certain implementations of the first aspect, after the management device receives a monitoring request to monitor the performance indicators of the target service, it sends a measurement indication to the measuring device; the method also includes: the management device sends a measurement result cache indication of the target service and / or a cache time of the measurement result of the target service to the measuring device.

[0028] The measurement result cache indication of the target service is used to indicate to cache the performance data of the measurement statistics.

[0029] The cache time of the measurement result of the target service indicates the time information (such as the time length) for locally caching the performance data of the measurement statistics.

[0030] Based on the above technical solution, the management device may also send a measurement result cache indication of the target service to the measurement device, so that the measurement device may temporarily not report the measurement result based on the measurement result cache indication, and cache the measurement result. Alternatively, the management device may also send a cache time of the measurement result of the target service to the measurement device, so that the measurement device may cache the measurement result based on the cache time of the measurement result, thereby avoiding insufficient storage space caused by caching the measurement result of the target service all the time.

[0031] In combination with the first aspect, in some implementations of the first aspect, the method further includes: the management device sends a measurement result reporting indication to the measurement device, where the measurement result reporting indication is used to indicate reporting of the measurement result of the target service in the target time period.

[0032] Based on the above technical solution, the management device sends a measurement result reporting instruction to the measurement device, so that the measurement device can report the measurement result of the target service in the target time period based on the measurement result reporting instruction.

[0033] In combination with the first aspect, in certain implementations of the first aspect, the method also includes: the management device sends one or more of the following information to the measuring device: performance indicators of the target service, maintenance and measurement task identifiers, measurement identifiers, measurement time of the target service, measurement methods of the measuring device, or addresses of the measuring device.

[0034] The measurement time of the target service indicates information related to the measurement time. For example, the measurement time of the target service includes: the measurement method of the device performing data measurement, the measurement start time, the measurement end time, etc.

[0035] The measurement method of the measuring device refers to the method in which the device that performs data measurement performs measurement, and may include, for example, real-time measurement, delayed measurement, etc.

[0036] Based on the above technical solution, the management device sends one or more of the following information to the measuring device: performance indicators of the target service, maintenance task identifier, measurement identifier, measurement time of the target service, measurement method of the measuring device, or address of the measuring device, so that the measuring device can measure the target service based on one or more of the above information.

[0037] In combination with the first aspect, in certain implementations of the first aspect, the maintenance request includes one or more of the following information: an abnormal event of the target service, an identifier of the terminal device, or an identifier of the target service.

[0038] Based on the above technical solution, the maintenance request may include one or more of the following information: abnormal events of the target service, the identification of the terminal device, or the identification of the target service, so as to facilitate the management device to make relevant decisions. For example, the management device may determine the performance index of the target service based on the abnormal events of the target service, or determine the data packet type of the target service to be measured, etc.

[0039] In combination with the first aspect, in some implementations of the first aspect, the method further includes: the management device sending the performance indicator of the target service to the measurement device.

[0040] Based on the above technical solution, the management device may also send the performance indicator of the target service to the measurement device, and then the measurement device performs measurement based on the performance indicator.

[0041] In combination with the first aspect, in some implementations of the first aspect, the method further includes: the management device determines a performance indicator of the target business according to an abnormal event of the target business and / or a business type to which the target business belongs.

[0042] Based on the above technical solution, the management device can determine the performance indicators of the target business according to the abnormal events of the target business and / or the business type to which the target business belongs, so that more appropriate performance indicators can be determined according to the actual situation of the fault or the type of business, thereby enabling fault analysis to be performed based on more accurate performance indicators.

[0043] In combination with the first aspect, in certain implementations of the first aspect, the abnormal event of the target service includes at least one of the following: video freeze corresponding to the target service, or abnormal control delay corresponding to the target service.

[0044] In combination with the first aspect, in certain implementation methods of the first aspect, the performance indicator of the target service includes at least one of the following: the number of uplink packet data convergence protocol packet losses, the number of downlink packet data convergence protocol packet losses, the uplink air interface transmission delay, the downlink air interface transmission delay, the number of packet data convergence protocol packets whose uplink air interface transmission delay is greater than a first threshold, the downlink packet user plane function network element processing delay, the downlink packet terminal equipment processing delay, the downlink packet wireless access network network element equipment processing delay, the number of downlink N3 interface data packets whose delay is greater than a second threshold, or the downlink N3 interface data packet transmission delay.

[0045] Based on the above technical solution, the performance indicator of the target business may include at least one of the above items, and specifically, may be determined according to the abnormal event of the target business and / or the business type to which the target business belongs. Further, in practical applications, a more appropriate performance indicator may be selected from at least one of the above items for measurement according to the actual situation.

[0046] In combination with the first aspect, in some implementations of the first aspect, the measurement device includes one or more of the following: a core network element device, a radio access network device, or a user premises equipment corresponding to the target service.

[0047] In a second aspect, an embodiment of the present application provides a measurement method. The method may be performed by a communication device, or may be performed by a component (such as a chip or circuit) of the communication device, without limitation, and for ease of description, the following description is given by taking the measurement device as an example.

[0048] The method may include: a measuring device receives a measurement identifier from a management device, the measurement identifier is used to associate with a target business to be measured, the target business is a business corresponding to a data flow passing through an industry terminal; the measuring device associates the measurement identifier with the target business; the measuring device measures a performance indicator of the target business associated with the measurement identifier, the performance indicator of the target business is associated with an abnormal event of the target business.

[0049] Based on the above technical solution, after the measuring device receives the measurement identifier from the management device, it can associate the measurement identifier with the target service to be measured in the service corresponding to the data flow passing through the industry terminal, and then measure the performance index of the target service associated with the measurement identifier. Therefore, the measuring device can quickly identify the service data packet to be measured based on whether the service has an associated measurement identifier, and realize the statistics of performance data based on a finer granularity (i.e., service granularity). In this way, if fault diagnosis and analysis is required, abnormal fault diagnosis and analysis of service granularity can be performed based on the performance data of the service. Thus, the problem of inaccurate performance data analysis results based solely on the wireless network air interface can be overcome, and compared with the device-level fault diagnosis and analysis, the above technical solution improves the accuracy of fault diagnosis and analysis. For example, if the measuring device performs device-level fault diagnosis and analysis, the statistics are the average performance indicators of all services on the measuring device. Even if the performance indicators of some services on the measuring device are abnormal, since the real performance indicators of each service will be averaged, the final diagnostic analysis result may be that the measuring device has no abnormal problem, which leads to inaccurate fault diagnosis and analysis results and difficulty in locating faults. Therefore, through the above technical solution, the problem of inaccurate performance data analysis results based on the device level can also be overcome.

[0050] In combination with the second aspect, in certain implementations of the second aspect, the method also includes: the measuring device receives one or more of the following information from the management device: the data packet type of the target service associated with the measurement identifier, the identifier of the target service, the user premises equipment identifier corresponding to the target service, or the identifier of the terminal device.

[0051] In combination with the second aspect, in some implementations of the second aspect, the measuring device associating the measurement identifier with the target service includes: the measuring device adding the measurement identifier to a data packet of the target service.

[0052] In combination with the second aspect, in some implementations of the second aspect, the method further includes: the measuring device sending address information of the measuring device.

[0053] In combination with the second aspect, in certain implementations of the second aspect, the method also includes: a measuring device receives a measurement indication from a management device, the measurement indication is used to indicate measurement of a performance indicator of a target service associated with a measurement identifier; the measuring device measures the performance indicator of the target service associated with the measurement identifier, including: in response to the measurement indication, the measuring device measures the performance indicator of the target service associated with the measurement identifier.

[0054] In combination with the second aspect, in certain implementations of the second aspect, the method also includes: the measuring device receives a measurement result cache indication of the target service and / or a cache time of the measurement result of the target service from the management device; the measuring device caches the measurement result of the target service according to the measurement result cache indication of the target service and / or the cache time of the measurement result of the target service.

[0055] In combination with the second aspect, in certain implementations of the second aspect, the method also includes: within a preset time period, if the measuring device receives a measurement result reporting indication from the management device, the measuring device reports the measurement result of the target time period to the management device, wherein the measurement result reporting indication is used to indicate the reporting of the measurement result of the target service in the target time period; or, within the preset time period, if the measuring device does not receive a measurement result reporting indication from the management device, the measuring device deletes the cached measurement result of the target service in the target time period.

[0056] In combination with the second aspect, in certain implementations of the second aspect, the method also includes: the measuring device receives one or more of the following information from the management device: performance indicators of the target service, maintenance task identifier, measurement identifier, measurement time of the target service, measurement method of the measuring device, or address of the measuring device.

[0057] The beneficial effects of the second aspect and each possible design can be referred to the relevant description of the first aspect and will not be elaborated here.

[0058] In a third aspect, an embodiment of the present application provides a measurement method. The method may be performed by a communication device, or may be performed by a component (such as a chip or circuit) of the communication device, without limitation. For ease of description, the following description is given by taking the execution by a network element management device as an example.

[0059] The method may include: a network element management device receives a measurement indication from a management device, the measurement indication is used to instruct the measurement device to measure performance indicators of a target service associated with a measurement identifier, wherein the target service is a service corresponding to a data flow passing through an industry terminal, the performance indicators of the target service are associated with abnormal events of the target service, and the measurement identifier is used to associate with the target service to be measured; and the network element management device forwards the measurement indication to the measurement device.

[0060] In combination with the third aspect, in certain implementations of the third aspect, the method also includes: the network element management device receives the address of the user premises equipment corresponding to the target service from the management device; the network element management device determines the address of the measurement device based on the address of the user premises equipment corresponding to the target service.

[0061] In a fourth aspect, an embodiment of the present application provides a measurement method. The method may be executed by a communication device, or may be executed by a component (such as a chip or circuit) of the communication device, without limitation. For ease of description, the following is an example of execution by an application server.

[0062] The method may include: an application server detecting that an abnormal event occurs in a target service corresponding to a data flow passing through an industry terminal; and the application server sending a maintenance request for performing maintenance on the target service to a management device.

[0063] In combination with the fourth aspect, in certain implementations of the fourth aspect, the method further includes: the application server also sends one or more of the following information to the management device: an abnormal event of the target service, an identifier of the terminal device, or an identifier of the target service.

[0064] In combination with the fourth aspect, in certain implementations of the fourth aspect, before the application server sends a maintenance request to the management device to perform maintenance on the target service, the method also includes: the application server sends a monitoring request to the management device to monitor the performance indicators of the target service.

[0065] In a fifth aspect, an embodiment of the present application provides a communication device. The device is used to execute the methods provided in the first to fourth aspects above. Specifically, the device may include a unit and / or module, such as a processing unit and / or a communication unit, for executing the method provided in any one of the above implementations of the first to fourth aspects.

[0066] In one implementation, the device is a communication device (such as a management device or a measurement device). When the device is a communication device, the communication unit may be a transceiver or an input / output interface; the processing unit may be at least one processor. Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0067] In another implementation, the device is a chip, a chip system or a circuit used in a communication device (such as a management device or a measurement device). When the device is a chip, a chip system or a circuit used in a communication device, the communication unit may be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit on the chip, the chip system or the circuit; the processing unit may be at least one processor, a processing circuit or a logic circuit.

[0068] In a sixth aspect, an embodiment of the present application provides a communication device. The device includes: a memory for storing programs; and at least one processor for executing computer programs or instructions stored in the memory to execute the method provided in any one of the above implementations of the first to fourth aspects.

[0069] In one implementation, the apparatus is a communication device (such as a management device or a measurement device).

[0070] In another implementation, the apparatus is a chip, a chip system or a circuit used in a communication device (such as a management device or a measurement device).

[0071] In a seventh aspect, an embodiment of the present application provides a processor for executing the methods provided in the above aspects.

[0072] For the operations such as sending and acquiring / receiving involved in the processor, unless otherwise specified, or unless they conflict with their actual function or internal logic in the relevant description, they can be understood as operations such as processor output, reception, input, etc., or as sending and receiving operations performed by the radio frequency circuit and antenna, and this application does not limit this.

[0073] In an eighth aspect, an embodiment of the present application provides a computer-readable storage medium. The computer-readable medium stores a program code for execution by a device, the program code including a method for executing any one of the above implementations of the first to fourth aspects.

[0074] In a ninth aspect, an embodiment of the present application provides a computer program product comprising instructions. When the computer program product is run on a computer, the computer is caused to execute the method provided in any one of the above implementations of the first to fourth aspects.

[0075] In a tenth aspect, an embodiment of the present application provides a chip. The chip includes a processor and a communication interface, and the processor reads instructions stored in a memory through the communication interface to execute the method provided by any one of the above implementations of the first to fourth aspects.

[0076] Optionally, as an implementation method, the chip also includes a memory, in which a computer program or instructions are stored, and the processor is used to execute the computer program or instructions stored in the memory. When the computer program or instructions are executed, the processor is used to execute the method provided in any one of the above-mentioned implementation methods of the first to fourth aspects.

[0077] In an eleventh aspect, an embodiment of the present application provides a communication system, which includes one or more of the above management device, measurement device, network element management device, and application server. BRIEF DESCRIPTION OF THE DRAWINGS

[0078] Figure 1 It is a schematic diagram of a network architecture applicable to an embodiment of the present application.

[0079] Figure 2is another schematic diagram of a network architecture applicable to an embodiment of the present application.

[0080] Figure 3 It is a schematic diagram of a network architecture provided according to an embodiment of the present application.

[0081] Figure 4 is another schematic diagram of a network architecture according to an embodiment of the present application.

[0082] Figure 5 It is a schematic diagram of a measurement method provided in an embodiment of the present application.

[0083] Figure 6 It is a schematic flow chart of a measurement method provided in one embodiment of the present application.

[0084] Figure 7 It is a schematic flow chart of a measurement method provided in another embodiment of the present application.

[0085] Figure 8 It is a schematic flow chart of a measurement method provided in one embodiment of the present application.

[0086] Fig. 9 is a schematic block diagram of a measuring device provided according to an embodiment of the present application.

[0087] Fig.10 is another schematic block diagram of a measuring device provided according to an embodiment of the present application.

[0088] Fig.11 It is a schematic diagram of a chip system provided according to an embodiment of the present application. DETAILED DESCRIPTION

[0089] The technical solution in this application will be described below in conjunction with the accompanying drawings.

[0090] The technical solution provided in this application can be applied to various communication systems, such as: fifth generation (5th generation, 5G) or new radio (new radio, NR) system, long term evolution (long term evolution, LTE) system, LTE frequency division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD) system, etc. The technical solution provided in this application can also be applied to future communication systems, such as the sixth generation mobile communication system. The technical solution provided in this application can also be applied to end to end (end to end, E2E), device to device (device to device, D2D) communication, vehicle to everything (vehicle-to-everything, V2X) communication, machine to machine (machine to machine, M2M) communication, machine type communication (machine type communication, MTC), and Internet of things (Internet of things, IoT) communication system or other communication systems.

[0091] First, a brief introduction to the network architecture applicable to this application is as follows.

[0092] Figure 1 It is a schematic diagram of a network architecture applicable to an embodiment of the present application.

[0093] like Figure 1 As shown, the network architecture takes the 5G toB scenario E2E network as an example. As an example, the network architecture may include but is not limited to: application terminals, customer-premises equipment (CPE), radio access network (RAN) equipment, core network equipment, and service servers.

[0094] Below Figure 1 A brief introduction to each device shown in FIG.

[0095] 1. Application terminal: can be called user equipment (UE), terminal equipment, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent or user device. This application uniformly uses terminal equipment to describe, that is, the terminal equipment described in this application can be replaced by application terminal.

[0096] The terminal device may be a device that provides voice / data to users, for example, a handheld device or a vehicle-mounted device with a wireless connection function. At present, some examples of terminals are: mobile phones, tablet computers, laptop computers, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, wearable devices, terminal devices in 5G networks or future evolved public land mobile communication networks (public land mobile The embodiments of the present application do not limit this.

[0097] As an example but not limitation, in the embodiments of the present application, the terminal device may also be a wearable device. Wearable devices may also be referred to as wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also powerful functions achieved through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include full-featured, large-sized, and fully or partially independent of smartphones, such as smart watches or smart glasses, as well as devices that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various types of smart bracelets and smart jewelry for vital sign monitoring.

[0098] In addition, in the embodiments of the present application, the terminal device may also be a terminal device in an IoT system. IoT is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network of human-machine interconnection and object-to-object interconnection. It can be understood that the terminal device in the embodiments of the present application may be a terminal for realizing a certain application, such as a terminal with a camera function, a terminal capable of data transmission, and so on.

[0099] like Figure 1 As shown, the terminal device may be, for example, a camera or a programmable logic controller (PLC).

[0100] In the embodiment of the present application, the device for realizing the function of the terminal device can be the terminal device, or it can be a device that can support the terminal device to realize the function, such as a chip system or a chip, which can be installed in the terminal device. In the embodiment of the present application, the chip system can be composed of a chip, or it can include a chip and other discrete devices.

[0101] 2. CPE: On the one hand, it can be used as a terminal device to connect to the access network device through wireless technology to obtain wireless network services; on the other hand, it can be used as a wireless access point to provide wireless access functions for other terminal devices (such as PLC, cameras, etc.).

[0102] It should be noted that the embodiments of the present application are mainly illustrated by taking CPE as an example, and are not limited to this. Other industry terminals similar to CPE are also applicable to the embodiments of the present application. Industry terminals can be used as terminal devices to connect to access network devices through wireless technology to obtain wireless network services, and can also be used as wireless access points to provide wireless access functions for other terminal devices.

[0103] 3. RAN equipment: It can provide authorized users in a specific area with access to the communication network. It can include wireless network equipment in the 3rd generation partnership project (3GPP) network and access points in non-3GPP networks. For the convenience of description, RAN equipment is used below.

[0104] RAN equipment can use different wireless access technologies. There are currently two types of wireless access technologies: 3GPP access technology (for example, the wireless access technology used in the third generation (3rd generation, 3G), fourth generation (4th generation, 4G) or 5G systems) and non-3GPP (non-3GPP) access technology. 3GPP access technology refers to access technology that complies with 3GPP standard specifications. For example, the access network equipment in the 5G system is called the next generation NodeBase station (gNB) or RAN equipment. Non-3GPP access technology may include air interface technology represented by access points (APs) in wireless fidelity (WiFi), worldwide interoperability for microwave access (WiMAX), code division multiple access (CDMA), etc. RAN equipment can allow terminal devices and 3GPP core networks to interconnect and communicate using non-3GPP technologies.

[0105] RAN equipment is responsible for radio resource management, quality of service (QoS) management, data compression and encryption, etc. on the air interface side. RAN equipment provides access services for terminal devices, and then completes the forwarding of control signals and user data between terminal devices and the core network.

[0106] RAN equipment may also be referred to as network equipment. RAN equipment may be, for example, a base station. A base station may broadly cover the following various names, or be replaced with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmission point (TRP), transmission point (TP), master station, auxiliary station, multi-standard wireless (motor slide retainer, MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station may be a macro base station, a micro base station, a relay node, a donor node, or the like, or a combination thereof. The base station may also refer to a communication module, modem or chip used to be set in the aforementioned equipment or device. The base station may also be a mobile switching center and a device that performs the base station function in D2D, V2X, and M2M communications, a network-side device in a 6G network, and a device that performs the base station function in a future communication system. The base station may support networks with the same or different access technologies. The embodiments of the present application do not limit the specific technology and specific device form used by the network equipment.

[0107] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move based on the location of the mobile base station. In other examples, a helicopter or drone can be configured to act as a device that communicates with another base station.

[0108] In some deployments, the network device mentioned in the embodiments of the present application may be a device including a CU, or a DU, or a device including a CU and a DU, or a control plane CU node (central unit control plane (central unit-control plane, CU-CP)) and a user plane CU node (central unit user plane (central unit-user plane, CU-UP)) and a DU node.

[0109] The network equipment and terminal equipment can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on the water surface; they can also be deployed on aircraft, balloons and satellites in the air. The embodiments of the present application do not limit the scenarios in which the network equipment and terminal equipment are located.

[0110] 4. Core network equipment: As an example, the core network equipment (or network elements in the core network) may include any of the following but not limited to: network slice selection function (NSSF), authentication server function (AUSF), unified data management (UDM), network exposure function (NEF), network storage function (NFrepository function, NRF), policy control function (PCF), application function (AF), access and mobility management function (AMF), session management function (SMF), user plane function (UPF), network data analytics function (NWDAF). As an example, the functions of the above core network network elements are as follows.

[0111] AMF: Mainly used for access control, mobility management, registration and deregistration, etc. For example, in the embodiment of the present application, AMF may be responsible for the authentication and mobility management functions of CPE.

[0112] SMF: Mainly used for user plane network element selection, user plane network element redirection, Internet Protocol (IP) address allocation for terminal devices, and session establishment, modification and release and QoS control. For example, in an embodiment of the present application, SMF may be responsible for session management of user plane data transmission of CPE, including session creation, deletion, and modification.

[0113] UPF: Mainly used for receiving and forwarding user plane data. For example, UPF can receive user plane data from DN and send the user plane data to the terminal device through the AN device. UPF can also receive user plane data from the terminal device through the AN device and forward it to the DN.

[0114] NEF: Mainly used to securely open the services and capabilities provided by 3GPP network functions to the outside world.

[0115] PCF: A unified policy framework mainly used to guide network behavior and provide policy rule information for control plane network elements (such as AMF, SMF, etc.).

[0116] AF: Mainly used to provide services to the 3GPP network, such as interacting with the PCF for policy control.

[0117] NSSF: Mainly used for network slice selection.

[0118] UDM: Mainly used for UE subscription data management, including storage and management of UE identification, UE access authorization, etc.

[0119] AUSF: Mainly used for user authentication, etc.

[0120] NRF: Mainly used to store description information of network function entities and the services they provide.

[0121] NWDAF: Mainly used for intelligent analysis of network status and other data.

[0122] 5. Service server: refers to a computer system that can provide certain services to other devices. For example, a video service server can provide video services (such as playing videos); for another example, a control service server can send control commands to terminal devices, etc.

[0123] like Figure 1 As shown in the figure, the CPE itself is connected to the RAN device (such as gNB) as a common terminal through wireless technology, and the RAN device is connected to the service server through the core network. In addition, the CPE can also be used as a wireless access point to provide wireless access functions for other terminals (such as PLC, camera, etc.), so that an E2E network can be formed from the service server to the application terminal.

[0124] Figure 2 is another schematic diagram of a network architecture applicable to an embodiment of the present application.

[0125] Figure 2 The network architecture shown in the figure is applicable to the business scenarios under 5G toB. In the business scenarios under 5G toB, CPE can provide video surveillance backhaul services for one or more cameras, and can also provide access and data transmission functions for the remote control command business flow of PLC. Among them, cameras and PLC belong to Figure 1 The application terminal (or terminal device) in the Figure 2Only the camera and PLC are shown in the figure, and the embodiment of the present application is not limited thereto. The CPE may also be other application terminals (such as Figure 2 The box where the ellipsis is located may represent other application terminals) providing wireless access functions. Figure 2 As shown, CPE can provide data transmission of service flows for cameras (such as camera 1 and camera 2) and PLC. For example, CPE can provide data transmission of flow1 for camera 1, CPE can provide data transmission of flow2 for camera 2, and CPE can provide data transmission of flow3 for PLC. Figure 2 For the introduction of each network element, please refer to the previous description and will not be repeated here.

[0126] Figure 3 It is a schematic diagram of a network architecture provided according to an embodiment of the present application.

[0127] The embodiment of the present application provides a management architecture for the integration of wireless terminal operation and maintenance, which mainly introduces the wireless terminal equipment management function (WTEMF) into the logical management architecture of 3GPP to realize the management of terminal equipment and support integrated deployment with the network management system. Figure 3 As shown, the network architecture may include but is not limited to: a cross domain management system, a radio network domain management (RAN domain management) system (ie, a RAN domain management system), and a core network (CN) domain management (CN domain management) system.

[0128] Among them, the cross-domain management system may include the functional entity of the operator to implement cross-domain network management. Figure 3 As shown, the cross-domain management system can manage the wireless network domain management system and the core network domain management system at the same time. The wireless network domain management system may include functional entities that manage network elements of the wireless network (such as gNB, gNB-CU-CP, gNB-CU-UP, gNB-DU, etc.). The core network domain management system may include functional entities that manage network elements of the core network. Taking 5G as an example, Figure 3As shown, the core network domain management system can manage the 5G core control plane network function (5G core control plane network function, 5GC CNF) and the user plane function (UPF). 5GC CNF may include network elements of the control plane function of the 5G core network, such as AMF, SMF, NEF, NWDAF, etc. The above systems may include multiple management functions that provide specific operation and maintenance management tasks, such as the configuration management function that provides network parameter configuration management service (network provisioning management service), the performance management function that provides network performance management service (performance assurance management service), and so on.

[0129] Among them, WTEMF can be used for CPE management. For example, WTEMF can be used to provide online registration, parameter configuration, performance management, fault management and other functions for terminal devices connected to CPE. Figure 3 As shown, WTEMF can be deployed in the RAN domain management system and / or the cross-domain network management system. For example, if WTEMF is deployed in the cross-domain network management system, WTEMF can manage CPE through the element management system (EMS). The "cross-domain WTEMF" involved in this application can be understood as a WTEMF integrated with the cross-domain management system or a WTEMF deployed in the cross-domain management system, and the "domain WTEMF" involved in this application can be understood as a WTEMF integrated with the RAN domain management system or a WTEMF deployed in the RAN domain management system.

[0130] Figure 4 is another schematic diagram of a network architecture applicable to an embodiment of the present application.

[0131] like Figure 4 As shown, WTEMF can be deployed independently, which can be understood as not being integrated with the management system, or it can be understood as Figure 3 The cross-domain WTEMF and domain WTEMF in the network are unified. As an example, the network architecture may include but is not limited to: CPE, RAN, WTEMF, AMF, SMF, NEF, NWDAF, UPF. For the description of each network element, refer to the previous description and will not be repeated here.

[0132] It should be understood that the above-mentioned network architecture applied to the embodiments of the present application is only an illustrative architecture, and the network architecture applicable to the embodiments of the present application is not limited to this. Any network architecture that can realize the functions of the above-mentioned network elements is applicable to the embodiments of the present application.

[0133] It should also be understood that Figures 1 to 4 The functions or network elements in, such as WTEMF, AMF, SMF, UPF, PCF, UDM, NSSF, AUSF and other functions or network elements, can be understood as network elements used to implement different functions, for example, they can be combined into network slices as needed. These network elements can be independent devices, or they can be integrated into the same device to implement different functions, or they can be network elements in hardware devices, or they can be software functions running on dedicated hardware, or they can be virtualized functions instantiated on a platform (for example, a cloud platform). This application does not limit the specific form of the above network elements.

[0134] It should also be understood that the above naming is only defined for the convenience of distinguishing different functions and should not constitute any limitation to this application. This application does not exclude the possibility of using other naming in 6G networks and other future networks. For example, in a 6G network, some or all of the above network elements may use the terminology in 5G, or may use other names, etc.

[0135] In mobile networks, operators are network communication service providers, mainly responsible for network construction and daily operation and maintenance management. Network operation and maintenance management includes network configuration management, performance management, and fault management. Among them, fault management is one of the key and difficult points of operator network management. At present, the main functions of network fault management include fault information query, fault reporting, fault information clearing, etc. However, when the network management system receives the network fault alarm reporting information, it is unable to determine the network fault point where the fault occurs (such as it is unable to determine whether it is a network element fault or a link fault, and it is also unable to determine whether it is a wireless access network element device fault or a core network element device fault). In order to locate the specific link where the fault occurs, operators usually arrange operation and maintenance management engineers to capture packets on site at different network element nodes or segmented links of the network, and perform fault analysis and location based on the captured packet data.

[0136] In some scenarios, such as Figure 1 In the 5G toB scenario shown, a large number of industry terminals (such as CPE, PLC, etc.) will be deployed in the private network of the enterprise park. Failures of such industry terminals similar to CPE often appear in the form of abnormal network failures. For example, CPE memory leaks (for example, the dynamically allocated heap memory in the program is not released or cannot be released by the program for some reason), resulting in the base station physical resource block (PRB) utilization rate reaching 100%. In this case, the network management system will detect a network failure caused by congestion at the wireless network air interface. However, this network failure is not a problem with the wireless network itself, but is caused by a CPE failure. Therefore, for this situation, simply analyzing the wireless network air interface problem may not be able to locate the actual abnormal fault point.

[0137] Currently, the network fault management mechanism defined in the 3rd Generation Partnership Project (3GPP) standard is mainly aimed at the fault information management of network equipment, and does not support the management of terminal equipment faults.

[0138] In order to solve the fault management of E2E network in 5G to B scenario, one solution in the prior art is to collect performance data of network and terminal and perform device-level fault diagnosis and analysis on the network and terminal. Figure 2 Taking the architecture shown as an example, suppose that at a certain time period or time, the backhaul video of camera 1 freezes, and other services on the CPE are normal, and suppose that the cause of the service problem of camera 1 is the uplink packet loss or disorder of the video backhaul service flow of flow1. For the above abnormal situation, according to the existing technology, the uplink packet loss data (such as the number of packet losses or the packet loss rate) at the CPE terminal granularity can be counted, that is, the average number of packet losses or the packet loss rate of the data packets of all service flows on the CPE (such as including flow1, flow2, and flow3) are counted. Since the average number of packet losses or the packet loss rate of the data packets of all service flows on the CPE is counted, the actual number of packet losses or the packet loss rate of the data packets of each service flow will be averaged, and the final diagnostic analysis result may be that there is no abnormal problem with the CPE, which will lead to inaccurate E2E fault diagnosis and analysis results and difficulty in locating the fault.

[0139] In view of this, the present application proposes a solution that can be based on a finer granularity (i.e., business granularity, such as Figure 2 The performance data is counted at the flow granularity in the flow diagram, and abnormal fault diagnosis and analysis is performed based on the performance data of the business, thereby overcoming the problem of inaccurate performance data analysis results based on the device level, thereby supporting the implementation of E2E fault demarcation and positioning processing.

[0140] To facilitate understanding of the embodiments of the present application, the terms involved in the present application are first briefly explained.

[0141] 1. Maintenance and testing: Based on business needs, network performance data is collected, and network performance is analyzed based on the collected network performance data to evaluate the network performance status and identify abnormal fault problems in the network. For example, it includes the network domain where the fault problem occurs (i.e., fault delimitation, such as terminal, wireless, transmission, and core network failures) and the specific root cause of the fault (i.e., fault location). The maintenance and testing described in the embodiments of the present application mainly focuses on fault delimitation and location analysis based on network performance data. It can be understood that the above is an exemplary description, and as long as it involves the method of measuring network performance data using the embodiments of the present application, it falls within the protection scope of the embodiments of the present application. For example, the maintenance and testing mentioned in the embodiments of the present application can also be temporary testing, etc.

[0142] 2. Abnormal events: can be understood as failures, such as failures at the service granularity. In an embodiment of the present application, abnormal events may refer to abnormal events at the service granularity. Abnormal events at the service granularity may include at least one of the following: video freezes corresponding to one or more services, or control delay anomalies corresponding to one or more services. Among them, video freezes corresponding to one or more services may be: the video played by the video service server has a distorted screen or freezes. The control delay anomaly corresponding to one or more services may be that the control command sent by the control service server to the terminal device reaches the terminal device for a long time (such as 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).

[0143] 3. Business: It can be divided by session granularity, for example, one session can correspond to one business. Business data can be transmitted through business flows. Figure 2 For example, the data of the target business can be transmitted through flow1 between CPE and camera 1, or the data of the target business can be transmitted through flow2 between CPE and camera 2, or the data of the target business can be transmitted through flow3 between CPE and PLC.

[0144] It can be understood that the term "and / or" in this article is only a description of the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0145] The above briefly explains the terms involved in this application, which will not be repeated in the following embodiments.

[0146] The following will describe in detail the method provided by the embodiment of the present application in conjunction with the accompanying drawings. The embodiment provided by the present application can be applied to the above Figures 1 to 4 The network architecture shown is not limited.

[0147] The various embodiments provided in the present application will be described in detail below with reference to the accompanying drawings.

[0148] Figure 5 is a schematic diagram of a measurement method 500 provided in an embodiment of the present application. The method 500 may include the following steps.

[0149] 510. The management device sends a measurement identifier to the measurement device, wherein the measurement identifier is used to associate with a target service to be measured, and the target service is a service corresponding to a data flow passing through an industry terminal.

[0150] Accordingly, the measuring device receives the measurement identification.

[0151] The target service is the service corresponding to the data flow passing through the industry terminal, or it can be understood that the target service is the service to be measured on the industry terminal. As an example, the target service can be the service corresponding to the data flow sent to the application terminal through the industry terminal, or the service corresponding to the data flow sent by the application terminal through the industry terminal.

[0152] As an example, the target service includes, but is not limited to: a video service (such as a video surveillance backhaul service) and a remote control command service.

[0153] The measurement identifier, which may also be called a coloring identifier, is used to associate with the target service to be measured and can be used to identify the service to be measured. As an example, the measurement identifier may be, for example, a special character or data, or the measurement identifier may also be an identifier of the target service (such as an IP5 tuple of the target service). Optionally, the method 500 further includes: the management device configures the measurement identifier for the target service. By associating the measurement identifier with the service to be measured, the service data packet to be measured associated with the measurement identifier can be quickly identified.

[0154] The management device is a device that can be used to manage the terminal device. As an example, the management device can be used to implement online registration, parameter configuration, performance management, fault management and other functions of the terminal device. In the embodiment of the present application, the management device can also be used to configure a measurement identifier for the target service, instruct the measurement device to perform measurement, etc. As an example, the management device can be the WTEMF described above.

[0155] The measuring device may be a device that associates a measurement identifier with a target service, or a device that measures the target service. As an example, the measuring device includes one or more of the following: a core network element device (such as UPF), a radio access network device (RAN), or a user premises equipment (such as CPE) corresponding to the target service.

[0156] It can be understood that the names of management device and measurement device are for distinction, and their names do not limit the protection scope of the embodiments of the present application. For example, the management device can also be called the first device without loss of generality, and the measurement device can also be called the second device without loss of generality.

[0157] It can be understood that the management device sending the measurement identifier to the measurement device may include: the management device directly sending the measurement identifier to the measurement device, or the management device sending the measurement identifier to the measurement device through other devices. Figures 6 to 8 A possible flow is shown.

[0158] Optionally, the method 500 further includes: the measuring device associating the measurement identifier with the target service.

[0159] Associating the measurement identifier and the target service may also be replaced by associating the measurement identifier and the data packet of the target service, or may also be replaced by coloring the data packet of the target service using the measurement identifier. As an example, coloring the data packet may refer to: filling (or adding) the measurement identifier in the data packet (such as the header field). In an embodiment of the present application, the measuring device associates the measurement identifier and the target service, or the measuring device performs coloring on the data packet of the target service, and then when the measuring device needs to measure the performance data of the target service, the target service data packet associated with the measurement identifier can be quickly identified.

[0160] There are many ways to associate the measurement identifier with the target service. One possible implementation is to fill (or add) the measurement identifier in the data packet (such as the header field) of the target service. Figures 6 to 8 The possible flow shown is described in detail.

[0161] 520. The management device sends a measurement instruction to the measurement device. The measurement instruction is used to instruct to measure a performance indicator of a target service associated with the measurement identifier. The performance indicator of the target service is associated with an abnormal event of the target service.

[0162] The measurement indication and the measurement identifier may be carried in the same signaling, or may be carried in different signalings without restriction. If the measurement indication and the measurement identifier are carried in the same signaling for transmission, it can not only save signaling overhead, but also facilitate the measurement device to measure the performance indicators of the target service associated with the measurement identifier carried in the signaling based on the one signaling. If the measurement indication and the measurement identifier are carried in different signalings for transmission, the measurement indication and the measurement identifier do not need to be bound in one signaling for transmission, so that the transmission is more flexible. For example, the management device can first send the measurement identifier to the measurement device, and then send the measurement indication.

[0163] As an example, the measurement identifier can also implement the function of measurement indication, and the measurement identifier can be used to indicate the measurement of the performance indicator of the target service associated with the measurement identifier. For example, the management device sends the measurement identifier to the measurement device; after receiving the measurement identifier, the measurement device associates the measurement identifier with the target service based on the measurement identifier, and measures the performance indicator of the target service associated with the measurement identifier.

[0164] Among them, the performance indicator of the target business is used to represent the indicator for measuring the target business. In an embodiment of the present application, performance data collection can be performed on a specified key performance indicator (KPI), and then fault analysis can be performed based on the collected performance data. Optionally, the management device determines the performance indicator of the business based on the abnormal event of the business and / or the business type to which the business belongs.

[0165] As an example, the performance indicator of the target service includes at least one of the following: the number of uplink packet data convergence protocol packet losses, the number of downlink packet data convergence protocol packet losses, the uplink air interface transmission delay, the downlink air interface transmission delay, the number of packet data convergence protocol packets with uplink air interface transmission delay greater than the first threshold, the downlink packet user plane function network element processing delay, the downlink packet terminal equipment processing delay, the downlink packet wireless access network network element equipment processing delay, the number of downlink N3 interface data packets with delay greater than the second threshold, or the downlink N3 interface data packet transmission delay. The thresholds involved in the embodiments of the present application, such as the first threshold or the second threshold, may be pre-configured, or may be specified by the protocol, or may be pre-agreed, and there is no limitation on this. In addition, the first threshold or the second threshold may be a specific value, or may be a range of values, and there is no limitation on this.

[0166] As an example, the abnormal event of the target service includes at least one of the following: video freeze corresponding to the target service, or abnormal control delay corresponding to the target service.

[0167] Based on the above technical solution, the management device can send a measurement identifier for associating with the target service to be measured to the measuring device, and the management device can also send a measurement instruction to the measuring device to indicate that the performance indicator of the target service associated with the measurement identifier is measured. Thus, the measuring device can quickly identify the service data packet to be measured based on whether the service has an associated measurement identifier, and realize the statistics of performance data based on a finer granularity (i.e., service granularity). In this way, if fault diagnosis and analysis is required, abnormal fault diagnosis and analysis of service granularity can be performed based on the performance data of the service. Thus, the problem of inaccurate performance data analysis results based solely on the wireless network air interface can be overcome, and compared with the device-level fault diagnosis and analysis, the above technical solution improves the accuracy of fault diagnosis and analysis. For example, if the measuring device performs device-level fault diagnosis and analysis, the statistics are the average performance indicators of all services on the measuring device. Even if the performance indicators of some services on the measuring device are abnormal, since the real performance indicators of each service will be averaged, the final diagnostic analysis result may be that the measuring device has no abnormal problem, which leads to inaccurate fault diagnosis and analysis results and difficulty in locating faults. Therefore, through the above technical solution, the problem of inaccurate performance data analysis results based on the device level can also be overcome.

[0168] Optionally, the method 500 further includes: the management device sends one or more of the following information to the measurement device: a data packet type of a target service associated with the measurement identifier, an identifier of the target service, a CPE identifier corresponding to the target service, or an identifier of the terminal device. The one or more of the above information and the measurement identifier and / or the measurement indication may be carried in the same signaling or in different signaling without limitation.

[0169] Among them, the data packet type of the target service associated with the measurement identifier indicates the data packet type that needs to be associated with the measurement identifier (or the data packet type that needs to be processed). The data packet type may include: an uplink data packet and / or a downlink data packet. In one possible implementation, the management device may determine the data packet type that needs to be associated with the measurement identifier based on the abnormal event of the target service. For example, if the abnormal event of the target service is video freeze, then the data packet type that needs to be associated with the measurement identifier may be an uplink data packet. For another example, if the abnormal event of the target service is that the control delay is too large, then the data packet type that needs to be associated with the measurement identifier may be a downlink data packet.

[0170] The identifier of the target service can be used to identify (or recognize) the target service. As an example, the identifier of the target service is an IP 5-tuple. Figure 2Taking the scenario shown as an example, assuming that the target service is flow1, the identifier of the target service may include the IP 5-tuple of flow1, that is, the following information corresponding to flow1: source IP address, source port, destination IP address, destination port, and the layer 4 protocol.

[0171] The CPE identifier (CPE Id) can be used to identify (or recognize) the CPE. As an example, the CPE Id can be any of the following: the equipment serial number (ESN) of the CPE, the IP address of the CPE, the globally unique temporary UE identity (GUTI) of the CPE, etc.

[0172] Among them, the identifier of the terminal device (such as DeviceId) can be used to identify (or recognize) the device to which the target service belongs or the device where the abnormal event occurs.

[0173] The above information can be collectively referred to as measurement information, or can also be referred to as a colored policy (ColoredPolicy). That is, the measurement information may include: a measurement identifier, a data packet type of a target service associated with the measurement identifier, an identifier of the target service, a CPE identifier corresponding to the target service, and at least one of an identifier of a terminal device. In a possible implementation, the management device may 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 management device, and then the management device sends the measurement information to the measurement device.

[0174] Regarding the use of the above information, Figures 6 to 8 The possible flow shown is described in detail.

[0175] Optionally, in step 510, the management device sends the measurement identifier to the measurement device, which may include the following situations.

[0176] In the first possible scenario, after receiving a maintenance request for the target service, the management device sends a measurement identifier to the measurement device. Based on this scenario, the management device can send a measurement identifier to the measurement device when it learns that the target service needs to be maintained. The maintenance request can be used to request maintenance of the service where an abnormal event occurs. Optionally, the maintenance request includes one or more of the following information: the abnormal event of the target service, the identifier of the terminal device, or the identifier of the target service. Figure 6 A detailed description of the possible flow is shown.

[0177] The second possible scenario is that after receiving a monitoring request to monitor the performance indicators of the target service, the management device sends a measurement identifier to the measuring device. Based on this scenario, the management device can send a measurement identifier to the measuring device when it learns that the performance indicators of the target service need to be monitored. Among them, the monitoring request can be used to request monitoring of the performance indicators of certain services. It can be understood that the maintenance request is used in scenarios where abnormal events have already occurred in the service, and the monitoring request is used in scenarios where abnormal events have not yet occurred in the service. Optionally, the monitoring request includes one or more of the following information: the service type of the target service, the identifier of the terminal device, or the identifier of the target service. Regarding this scenario, it will be discussed later in conjunction with Figure 7 A detailed description of the possible flow is shown.

[0178] The third possible scenario includes: after the management device detects that the terminal device is online, it sends a measurement identifier to the measurement device. Based on this scenario, the management device can send a measurement identifier to the measurement device after learning that the terminal device is online or after the terminal device transmits data of the target service. Figure 8 A detailed description of the possible flow is shown.

[0179] Optionally, the measuring device feeds back to the management device whether the measurement identifier and the target service have been associated. The measuring device can feed back to the management device the configuration result of the measurement identifier and the measurement information, so that the management device can send the measurement instruction when the measuring device has successfully associated the measurement identifier and the target service.

[0180] Optionally, if the measuring device has successfully associated the measurement identifier and the target service, or successfully configured the measurement identifier and measurement information, the management device may also receive the address of the measuring device, which can be used to implement the routing of subsequent management devices sending related messages to the measuring device.

[0181] Optionally, in step 520, the management device sends a measurement instruction to the measurement device, which may include the following situations.

[0182] As a first possible situation, after receiving a maintenance test request for the target service, the management device sends a measurement instruction to the measurement device. Based on this situation, when the management device learns that the target service needs to be maintained, it can send a measurement instruction to the measurement device so that the measurement device can measure the performance indicator of the target service associated with the measurement identifier.

[0183] Optionally, in this case, the management device also sends one or more of the following information to the measuring device: a measurement result reporting indication of the target service, performance indicators of the target service, a maintenance task identifier, a measurement identifier, a measurement time of the target service, a measurement method of the measuring device, or an address of the measuring device.

[0184] The target service measurement result reporting indication is used to indicate reporting the target service measurement result. For example, if the measuring device receives the measurement indication and the measurement result reporting indication, the measuring device measures the performance indicator of the target service according to the measurement indication, and reports the measurement result according to the measurement result reporting indication.

[0185] The target service measurement time refers to information related to the time when the measuring device measures the performance indicator of the target service. As an example, the target service measurement time includes: measurement start time, measurement end time, and the like.

[0186] The measurement mode of the measuring device refers to the measurement mode performed by the device performing data measurement, and may include, for example, real-time measurement, delayed measurement, etc. For example, if the measuring device receives a measurement instruction and the measurement mode performed by the device performing data measurement, and the measurement mode performed by the device performing data measurement is real-time measurement, the measuring device immediately starts to measure the performance indicator of the target service according to the measurement instruction and the measurement mode performed by the device performing data measurement.

[0187] As an example, the first possible situation and the first possible scenario mentioned above can be used in combination. For example, for example, the management device receives a maintenance and measurement request for maintenance and measurement of the target service. Based on the maintenance and measurement request, the management device sends a measurement identifier to the measuring device; the measuring device associates the measurement identifier with the target service; after the management device learns that the measuring device has successfully associated the measurement identifier with the target service, it sends a measurement indication to the measuring device; the measuring device measures the performance indicators of the target service based on the measurement indication. For another example, the management device receives a maintenance and measurement request for maintenance and measurement of the target service. Based on the maintenance and measurement request, the management device sends a measurement identifier and a measurement indication to the measuring device; the measuring device associates the measurement identifier with the target service, and after successfully associating the measurement identifier with the target service, it measures the performance indicators of the target service. The above is an exemplary description, and the embodiments of the present application are not limited thereto. For example, the management device receives a maintenance and measurement request for maintenance and measurement of the target service. The management device first sends a measurement identifier to the measuring device, and then the management device sends a measurement indication to the measuring device.

[0188] As another example, the first possible scenario and the second possible scenario mentioned above can also be used in combination. For example, the management device receives a monitoring request for monitoring a target service, and based on the monitoring request, the management device sends a measurement identifier to a measuring device; the measuring device associates the measurement identifier with the target service; after the management device learns that the measuring device has successfully associated the measurement identifier with the target service, it may temporarily not send a measurement indication to the measuring device; the management device receives a maintenance request for maintenance and measurement of the target service, and based on the maintenance and measurement request, the management device sends a measurement indication to the measuring device; the measuring device measures the performance indicator of the target service based on the measurement indication.

[0189] As another example, the first possible situation and the third possible situation mentioned above can also be used in combination. For example, after the management device detects that the terminal device is online, it sends a measurement identifier to the measuring device; the measuring device associates the measurement identifier with the target service; after the management device learns that the measuring device has successfully associated the measurement identifier with the target service, it may temporarily not send a measurement instruction to the measuring device; the management device receives a maintenance request for the target service, and based on the maintenance request, the management device sends a measurement instruction to the measuring device; the measuring device measures the performance indicators of the target service based on the measurement instruction.

[0190] As a second possible situation, after receiving a monitoring request for monitoring the target service, the management device sends a measurement instruction to the measurement device. Based on this situation, when the management device learns that the performance indicator of the target service needs to be monitored, it can send a measurement instruction to the measurement device so that the measurement device can measure the performance indicator of the target service associated with the measurement identifier.

[0191] Optionally, in this case, the management device also sends one or more of the following information to the measuring device: performance indicators of the target service, measurement identifier, measurement time of the target service, address of the measuring device, measurement result cache indication of the target service, measurement method of the measuring device, or cache time of the measurement result of the target service.

[0192] The target service measurement result cache indication is used to indicate caching of the performance data of the measurement statistics. For example, if the measurement device receives the measurement indication and the measurement result cache indication, the measurement device measures the performance indicator of the target service according to the measurement indication and caches the measurement result according to the measurement result cache indication.

[0193] Among them, the cache time of the measurement result of the target service represents the time information (such as the length of time) for locally caching the performance data of the measurement statistics. For example, if the measuring device receives a measurement indication and a cache time of the measurement result, the measuring device measures the performance indicator of the target service according to the measurement indication, and caches the measurement result for a certain time according to the cache time of the measurement result. As an example, if the measuring device has not received a measurement result reporting indication from the management device within a preset period of time (such as before the cache time times out), the measuring device deletes the cached measurement result, thereby saving storage space.

[0194] As an example, the above-mentioned second possible situation and the second possible scenario can be used in combination. For example, for example, the management device receives a monitoring request for monitoring the target service, and based on the monitoring request, the management device sends a measurement identifier to the measuring device; the measuring device associates the measurement identifier with the target service; after the management device learns that the measuring device has successfully associated the measurement identifier with the target service, it sends a measurement indication to the measuring device; the measuring device measures the performance indicators of the target service based on the measurement indication. For another example, the management device receives a monitoring request for monitoring the target service, and based on the monitoring request, the management device sends a measurement identifier and a measurement indication to the measuring device; the measuring device associates the measurement identifier with the target service, and after successfully associating the measurement identifier with the target service, it measures the performance indicators of the target service.

[0195] As another example, the second possible situation and the third possible situation mentioned above can be used in combination. For example, after the management device detects that the terminal device is online, it sends a measurement identifier to the measuring device; the measuring device associates the measurement identifier with the target service; after the management device learns that the measuring device has successfully associated the measurement identifier with the target service, it may temporarily not send a measurement indication to the measuring device; the management device receives a monitoring request for monitoring the target service, and based on the monitoring request, the management device sends a measurement indication to the measuring device; the measuring device measures the performance indicators of the target service based on the measurement indication.

[0196] Regarding the second possible situation, combined with Figure 8 A detailed description of the possible flow is shown.

[0197] It can be understood that the above two possible situations are exemplary descriptions, and the embodiments of the present application are not limited thereto. For example, the management device may also send a measurement indication to the measurement device after receiving feedback from the measurement device that the measurement identifier and the target service have been successfully associated. Based on this situation, the management device may send a measurement indication to the measurement device when it is known that the measurement device has successfully associated the measurement identifier and the target service, so that the measurement device can measure the performance indicator of the target service associated with the measurement identifier.

[0198] For ease of understanding, the following uses the industry terminal as CPE and combines Figures 6 to 8 Here is a possible flow that applies to the above scenario. As an example, Figures 6 to 8 The embodiments can be applied to the above Figures 1 to 4 In the network architecture shown. For example, Figures 6 to 8 The CPE in Figures 1 to 4 The CPE in the network architecture shown; for example, Figures 6 to 8 RAN in the Figure 1 , Figure 3 ,as well as Figure 4 RAN equipment in the network architecture shown, or Figures 6 to 8 RAN in the Figure 2 gNB in ​​the network architecture shown; for example, Figures 6 to 8 AMF, SMF, NEF, and UPF are available Figures 1 to 4 The core network device in the network architecture shown; for example, Figures 6 to 8 WTEMF in can be used Figure 3 to Figure 4 In the possible process shown below, it is assumed that a measurement identifier (or coloring identifier) ​​and measurement information (or coloring strategy) are configured for the target service, the management device is WTEMF, and the measurement devices include UPF, RAN, and CPE.

[0199] Figure 6 It is a schematic flow chart of a measurement method provided in one embodiment of the present application. Figure 6 The method 600 shown may be applicable to the first possible scenario in the above method 500 . Figure 6 The illustrated method 600 may include the following steps.

[0200] 601: The application server detects a target service failure.

[0201] The application server detects a target service failure, which may be the case when the application server detects an abnormal event that occurs in the target service.

[0202] As an example, an application server such as Figure 2 The video server or control server in the system.

[0203] Service failures may include, for example, video freezes, screen distortion, and large control delays.

[0204] For example, Figure 2 For example, the control server detects that the data transmission delay is large. The control server knows that the data is transmitted by flow3 between CPE and PLC based on the IP address of the data with large transmission delay. Therefore, it can be determined that the service failure corresponds to flow3 between CPE and PLC. For the specific method of detecting service failure by the application server, reference can be made to the prior art, which is not limited by the embodiments of the present application.

[0205] If the application server detects a service failure, the application server can initiate a maintenance request for the corresponding service to WTEMF in order to trigger WTEMF to measure the performance of the specified service and diagnose the network failure based on the service performance data analysis.

[0206] For example, for video freezes and screen distortion problems: the uplink packet loss of the video service can be measured and counted, such as measuring the packet loss of the air interface link and the N3 link, so as to identify the faulty network link. The N3 link represents the N3 interface link between the RAN and the UPF. For example, by measuring the packet loss of the uplink packet data convergence protocol (PDCP) packet (i.e., the data message of the air interface link) and the uplink general packet radio service (GPRS) tunneling protocol user plane (GTPU) (i.e., the data message of the N3 link), the status of each segmented link of the video service can be determined, thereby assisting in network fault demarcation.

[0207] For another example, regarding the remote control delay problem: by measuring and counting the transmission delay of the downlink packets of the remote control service, including the transmission delay of the air interface link and the N3 link, the status of each segmented link of the remote control service can be determined, the faulty network link can be identified, and network fault demarcation can be assisted.

[0208] The above is an example. For specific operations of diagnosing network failures based on business performance data analysis, reference may be made to the prior art and no limitation is imposed on this.

[0209] 602. The application server sends a maintenance request to WTEMF.

[0210] The application server detects a target service failure, so the application server sends a maintenance request to WTEMF.

[0211] Optionally, the maintenance request includes one or more of the following information: an identifier of a device where an abnormal event occurs (DeviceId), the abnormal event, or an identifier of a target service.

[0212] Among them, DeviceId can be used to identify (or recognize) the device where the abnormal event occurs. DeviceId can be, for example, the ID of the device, such as camera ID, PLC ID, etc., or it can also be the serial number of the device, etc., without limitation. For example, for an application server, the ID of the device can be obtained through the IP address of the data transmitted between the application server and the device where the abnormal event occurs.

[0213] Among them, the abnormal event, or maintenance problem type (eventType), can be used to identify the event type of business abnormality. For example, the abnormal event is video freezing. For another example, the abnormal event is large control delay.

[0214] The target service identifier may be used to identify the target service in which an abnormality occurs. In the following embodiments, the target service identifier is an IP 5-tuple as an example for illustrative description.

[0215] In a possible implementation, the application server sends a maintenance request to the WTEMF by calling the management service (MnS) provided by the WTEMF. As an example, the management service provided by the WTEMF can refer to the definition in Table 1.

[0216] Table 1

[0217]

[0218] The task creation operation in Table 1 may be recorded as a diagnostics task creation operation (DiagnosticsJob_Create Operation), or may be recorded as a maintenance task creation operation.

[0219] The status in Table 1 indicates the status, that is, the result of the diagnosis. In one possible case, the status is success, which means that the fault diagnosis analysis is successful; in another possible case, the status is failure, which means that the fault diagnosis analysis fails.

[0220] The DiagnosticsJob Id in Table 1 represents a diagnostics job identifier (DiagnosticsJob Id). For example, the application server may send a maintenance request to WTEMF, and the maintenance request is used to perform a fault diagnosis analysis on an abnormal event of the target business. Then, the fault diagnosis analysis on the abnormal event may be considered as a diagnostics task (or maintenance task).

[0221] The output in Table 1 indicates the result of the maintenance request fed back by WTEMF to the application server. For example, after the application server sends the maintenance request to WTEMF, WTEMF performs some operations (such as steps 603-625 in the embodiment of the present application) to perform fault diagnosis and analysis on the abnormal event corresponding to the maintenance request; after the fault diagnosis and analysis, the result of the maintenance request is fed back to the application server.

[0222] It is understood that Table 1 is only an exemplary description, and the embodiments of the present application are not limited thereto. For example, the management service provided by WTEMF may also be a management service with other names. For another example, Table 1 may also include more parameters.

[0223] 603, WTEMF configures measurement information.

[0224] Optionally, if the maintenance request in step 602 includes DeviceId, the WTEMF may determine the identifier (CPE Id) of the CPE to which the terminal identified by DeviceId is connected based on the DeviceId. Wherein, CPE Id is an identifier for identifying the CPE. As an example, CPE Id may be any of the following: ESN of the CPE, IP address of the CPE, 5G-GUTI of the CPE, etc.

[0225] Optionally, if the measurement request in step 602 includes eventType, WTEMF can determine based on the eventType: the KPI of the target service that needs to be measured, and / or the type of data packet that needs to be associated with the measurement identifier. Among them, the type of data packet that needs to be associated with the measurement identifier can also be the type of data packet that needs to be colored (such as can be recorded as a colored type (ColoredType)), and the following is explained by taking the type of data packet that needs to be colored as an example. As an example, the type of data packet that needs to be colored includes, for example: an uplink data packet and / or a downlink data packet. Among them, the correspondence between eventType and the KPI of the target service can be shown in Table 2.

[0226] Table 2

[0227]

[0228] Among them, the number of downlink air interface large delay packets, for example, may include: the number of packets whose downlink air interface delay is greater than a certain threshold. The number of downlink N3 large delay packets, for example, may include: the number of packets whose downlink N3 delay is greater than a certain threshold. Taking Table 1 as an example, for example, if the maintenance request includes eventType, and eventType is video freeze, then WTEMF may determine to measure one or more of the following based on the eventType: the number of uplink PDCP packet losses or the number of uplink GTPU packet losses. For another example, if the maintenance request includes eventType, and eventType is too large control delay, then WTEMF may determine to measure one or more of the following based on the eventType: the number of downlink air interface large delay packets, the number of downlink N3 large delay packets, the downlink air interface transmission delay, the downlink N3 transmission delay, the downlink packet UPF processing delay, the downlink packet CPE processing delay, or the downlink packet RAN processing delay.

[0229] In step 603, WTEMF may allocate a measurement identifier (such as FlowId) for the target service and configure the measurement information of the target service (such as ColoredPolicy). The measurement identifier is used to identify the target service, such as a special character or data, or the identifier of the target service (such as the IP5 tuple of the target service), without limitation. As an example, the relevant parameters of the measurement information may be shown in Table 3.

[0230] Table 3

[0231]

[0232] Among them, the parameter attribute is "M", which means that the parameter is mandatory; the parameter attribute is "CM", which means that the parameter is conditionally mandatory. As shown in Table 3, for DeviceId, it is conditionally mandatory. For example, if uplink packet loss occurs, such as service failures such as video freeze and screen distortion, DeviceId is mandatory.

[0233] It can be understood that the measurement information may include: ULpacketcoloredInfo and / or DLpacketcoloredInfo. For example, WTEMF may determine whether the measurement information includes ULpacketcoloredInfo, DLpacketcoloredInfo, or both ULpacketcoloredInfo and DLpacketcoloredInfo based on the abnormal event of the target service. For example, if the abnormal event of the target service is video freeze, then the measurement information includes ULpacketcoloredInfo. For another example, if the abnormal event of the target service is too large a control delay, then the measurement information includes DLpacketcoloredInfo.

[0234] 604. WTEMF sends a measurement information configuration request to NEF.

[0235] The measurement information configuration request may carry measurement information. The content of the measurement information may refer to Table 3.

[0236] WTEMF can trigger the core network to start the control plane signaling process by calling the control plane service interface of NEF to configure the measurement information of the target service to each related network element in the network.

[0237] In a possible implementation, the measurement information configuration request may be an Nnef interface application policy creation request (Nnef_ApplyPolicy_Create request) of the NEF. It should be understood that information exchange may be performed between various network elements based on a service-based interface. For example, the Nnef interface is a service-based interface for interaction between the NEF and other network elements. The message transmitted between the NEF and other network elements based on the Nnef interface may be, for example, the above-mentioned Nnef_ApplyPolicy_Create request message. Therefore, in an embodiment of the present application, the input parameters of the Nnef_ApplyPolicy_Create request may be enhanced to support the transmission of the policy parameters in Table 3.

[0238] The above is an exemplary description, and the embodiments of the present application are not limited thereto. For example, a new NEF service interface may also be defined to implement configuration of measurement information.

[0239] 605, NEF sends a session management (SM) modification request to SMF.

[0240] The SM modification request may carry measurement information.

[0241] After NEF receives the measurement information about the target service sent by WTEMF, it can send the measurement information of the target service to other network elements through the PDU session modification process of the core network. For example, similar to the PDU session modification process triggered by QoS policy update, after NEF receives the measurement information about the target service sent by WTEMF, it triggers the PDU session modification process and configures the measurement information of the target service to each relevant network element in the network.

[0242] In a possible implementation, the SM modification request may be a Nsmf interface PDU session update session management context request (Nsmf_PDUSession_UpdateSMContext request) of the SMF. In an embodiment of the present application, the input parameters of the Nsmf_PDUSession_UpdateSMContext request may be enhanced to support the transmission of the policy parameters in Table 3, as shown in Table 4.

[0243] Table 4

[0244]

[0245] The input parameters in Table 4 are optional parameters. The input parameter ColoredPolicy in Table 4 can refer to Table 3.

[0246] The output in Table 4 indicates the configuration result of the SMF feeding back the measurement information to the NEF, and this output corresponds to step 615.

[0247] It should be noted that the parameters shown in Table 4 are for exemplary purposes only, and the input parameters of the Nsmf_PDUSession_UpdateSMContext request may also include other parameters, which are not limited.

[0248] 606, SMF distributes and configures the measurement information.

[0249] After receiving the measurement information of the target service from NEF, SMF can trigger the PDU session modification process to achieve the distribution and configuration of the measurement information.

[0250] For example, SMF can distribute policies based on the value of ColoredType in the measurement information. For example: if the value of ColoredType is UL, the corresponding ULpacketcoloredInfo can be sent to CPE through non-accessstratum (NAS) signaling; if the value of ColoredType is DL, the corresponding DLpacketcoloredInfo can be sent to UPF through N4 interface signaling; if the value of ColoredType includes DL and UL, the corresponding DLpacketcoloredInfo can be sent to UPF through N4 interface signaling, and the corresponding ULpacketcoloredInfo can be sent to CPE through NAS signaling.

[0251] 607, SMF sends an N4 session modification request to UPF.

[0252] If the value of ColoredType includes DL, the method 600 may include steps 607-608. In step 607, the SMF sends DLpacketcoloredInfo to the UPF. The DLpacketcoloredInfo may be carried in an N4 session modification request (N4 session modification request) of the N4 interface.

[0253] The N4 session modification request includes DLpacketcoloredInfo (refer to Table 3, ie, including the target service identifier IP 5-tuple and the measurement identifier FlowId).

[0254] After receiving the N4 session modification request, the UPF processes the target service according to the measurement information, or performs coloring processing on the data packets of the target service, or configures the measurement information.

[0255] In one example, UPF determines whether to process the target service according to the measurement information based on whether the N4 session modification request carries information #1. Information #1 is used to indicate that the target service is processed according to the measurement information. For example, if the N4 session modification request includes DLpacketcoloredInfo and information #1, after receiving the N4 session modification request, UPF determines to process the target service according to the measurement information.

[0256] In another example, the UPF determines whether to process the target service according to the measurement information based on whether the N4 session modification request carries DLpacketcoloredInfo. For example, if the N4 session modification request includes DLpacketcoloredInfo, the UPF determines to process the target service according to the measurement information after receiving the N4 session modification request.

[0257] In another example, the UPF determines whether to process the target service according to the measurement information based on the value of information #1 carried in the N4 session modification request. As an example, information #1 is 1 bit, and the value range of information #1 is: 0, 1. If the value of information #1 is "1", it can be considered that information #1 is used to indicate that the target service is processed according to the measurement information; if the value of information #1 is "0", it can be considered that information #1 is used to indicate that the target service does not need to be processed according to the measurement information.

[0258] The above description is for exemplary purposes only, and the embodiments of the present application are not limited thereto.

[0259] Assuming that after receiving the N4 session modification request, the UPF determines to process the target service according to the measurement information, then when the UPF receives the downlink data packet of the target service, it can process the downlink data packet of the target service based on the measurement information.

[0260] The processing (or coloring) of the data packet (such as the downlink data packet of the target service) by UPF mainly refers to: UPF adds a measurement identifier to the data packet. For example, when UPF receives the downlink data packet of the target service identified by IP 5-tuple in the measurement information, it performs QoS marking (QoS marking), such as adding a QoS Flow identifier (QoS flow identifier, QFI), and further, performs coloring on the downlink data packet (such as GTPU packet), and then sends the downlink data packet after coloring to RAN through the N3 interface. Among them, coloring the downlink data packet means associating the downlink data packet and the measurement identifier, that is, filling (or adding) the measurement identifier in the downlink data packet (such as the header field). Taking the downlink data packet as a GTPU packet as an example, as shown in Table 5, the measurement identifier (FlowId) can be filled in the reserved bit of the GTPU header (that is, the field corresponding to 12Octet). In this way, when the target service needs to be measured later, it can be determined to measure the GTPU packet based on the measurement identifier of the GTPU header.

[0261] Table 5

[0262]

[0263] 608. UPF sends an N4 session modification response to SMF.

[0264] In a possible implementation, UPF sends an N4 session modification response (N4 sessionModification response) of the N4 interface to SMF, and the N4 session modification response is used to feedback the configuration result of the measurement information to SMF (such as measurement information configuration success or measurement information configuration success failure). Further, optionally, if the measurement information configuration fails, the reason for the configuration failure can also be fed back.

[0265] 609, SMF sends a session modification request to AMF.

[0266] If the ColoredType value includes UL, the method 600 may include steps 609 to 614, that is, the SMF sends ULpacketcoloredInfo to the AMF, and the ULpacketcoloredInfo may be carried in the session modification request. In this way, the SMF may send the ULpacketcoloredInfo to the CPE through the AMF.

[0267] The session modification request includes ULpacketcoloredInfo (refer to Table 3, i.e., including CPE Id, Device Id, target service identifier IP 5-tuple, and measurement identifier FlowId). Optionally, the session modification request includes information #1. Information #1 can refer to the description in step 607, except that step 607 describes the situation of the downlink data packet, and step 609 describes the situation of the uplink data packet, which is not repeated here for brevity.

[0268] In a possible implementation, the session modification request in step 609 may be the Namf interface communication N1N2 information transmission (Namf_Communication_N1N2MessageTransfer) of AMF.

[0269] 610. AMF sends an N2 session modification request to RAN.

[0270] In one possible implementation, AMF sends an N2 session modification request (such as PDU sessionresource modify request) of the N2 interface to the RAN.

[0271] The N2 session modification request includes ULpacketcoloredInfo. Optionally, the N2 session modification request includes information #1.

[0272] Optionally, the N2 session modification request includes information #2, and information #2 is used to instruct the RAN to perform processing operations on the data packet during the data forwarding process of the specified service (such as the target service). Information #2 can be carried in the N2 session modification request, or can be sent by the AMF to the RAN alone, or can be carried in other signaling sent by the AMF to the RAN, without limitation. For example, the AMF sends information #2 to the RAN, and after the RAN receives the information #2, it performs some processing operations on the specified data packet during the forwarding process of the specified data packet, wherein the specified data packet refers to a data packet carrying a measurement identifier.

[0273] For example, RAN receives a downlink data packet of a target service, and the downlink data packet includes a measurement identifier. RAN's processing operation on the downlink data packet may include: before forwarding the downlink data packet through a data radio bearer (DRB), the downlink PDCP packet is dyed based on the measurement identifier in the reserved bit of the GTPU packet header. For example, after UPF sends the dyed downlink data packet (such as a GTPU packet) to RAN through the N3 interface, RAN can directly copy the measurement identifier in the GTPU packet header and fill it into the extended bit of the PDCP packet header (it is necessary to extend the PDCP packet header field and use the newly added extension field to fill the measurement identifier). RAN can send the dyed data packet to CPE through the air interface DRB. The above operation can occur after step 607, that is, after UPF fills the measurement identifier in the downlink data packet of the target service.

[0274] For another example, the RAN receives an uplink data packet of a target service, and the uplink data packet includes a measurement identifier. The RAN's processing operation on the uplink data packet may include: the RAN colors the uplink GTPU packet based on the measurement identifier in the extended bit of the uplink PDCP packet header. For example, after the CPE sends the colored uplink data packet (such as a PDCP packet) to the RAN through the air interface DRB, the RAN may directly copy the measurement identifier in the uplink PDCP packet header and fill it into the reserved bit of the uplink GTPU packet header. The RAN may send the colored data packet to the UPF via the N3 interface. The above operation may occur after step 611, that is, after the CPE fills the measurement identifier in the uplink data packet of the target service.

[0275] It should be understood that the N2 session modification request may not include information #2, that is, the RAN can implement the processing of the above-mentioned data packet based on internal function implementation, and the AMF does not need to instruct the RAN to perform corresponding processing through explicit information elements.

[0276] 611. RAN sends an RRC reconfiguration message to CPE.

[0277] The RRC reconfiguration message includes ULpacketcoloredInfo. Optionally, if the N2 session modification request in step 610 includes information #1, the RRC reconfiguration message also includes information #1.

[0278] After receiving the RRC reconfiguration message, the CPE processes the target service according to the measurement information, or performs coloring processing on the data packets of the target service, or configures the measurement information.

[0279] In one example, the CPE determines whether to process the target service according to the measurement information based on whether the RRC reconfiguration message carries information #1. In another example, the CPE determines whether to process the target service according to the measurement information based on whether the RRC reconfiguration message carries ULpacketcoloredInfo. In another example, the CPE determines whether to process the target service according to the measurement information based on the value of information #1 carried in the RRC reconfiguration message. For details, please refer to the description in step 607, which is not repeated here for brevity.

[0280] Assuming that the CPE determines to process the target service according to the measurement information after receiving the RRC reconfiguration message, when the CPE receives the uplink data packet of the target service, it can process the uplink data packet of the target service based on the measurement information.

[0281] The processing (or coloring) of the data packet (such as the uplink data packet of the target service) by the CPE mainly refers to: the CPE adds a measurement identifier to the data packet. For example, when the CPE receives the uplink data packet of the target service from the industry application terminal identified by the IP 5-tuple or DeviceId in the measurement information, it performs QoS marking (such as adding a QFI mark), and further, performs coloring processing on the uplink data packet (such as the PDCP packet), and then sends the colored uplink data packet to the RAN through the air interface DRB. Among them, the uplink data packet is subjected to coloring processing, that is, the uplink data packet and the measurement identifier are associated, that is, the measurement identifier is filled (or added) in the uplink data packet (such as the header field). Taking the uplink data packet as PDCP as an example, as shown in Table 6, an extension field (that is, the field corresponding to 3Octet) can be added, the header field of PDCP can be extended, and the measurement identifier can be filled in the newly added extension field. In this way, when the target service needs to be measured later, it can be determined to measure the PDCP packet based on the measurement identifier of the PDCP header.

[0282] Table 6

[0283]

[0284] In Table 6, R represents a reserved bit, and MAC-I represents an integrity protection key.

[0285] 612. The CPE sends an RRC reconfiguration completion message to the RAN.

[0286] After the CPE completes the measurement information configuration of the target service, it may feed back the configuration result of the measurement information (such as measurement information configuration success or measurement information configuration success failure) to the RAN through an RRC reconfiguration complete message.

[0287] 613. RAN sends an N2 session modification response to AMF.

[0288] After RAN receives the configuration result of the measurement information fed back by CPE, it can forward the configuration result of the measurement information fed back by CPE (such as measurement information configuration success or measurement information configuration success failure) to AMF through N2 session modification request response (such as PDUsession resource modify response).

[0289] 614. AMF sends a session modification response to SMF.

[0290] The AMF forwards the configuration result of the measurement information fed back by the CPE to the SMF (such as measurement information configuration success or measurement information configuration success failure).

[0291] The session modification response can be the SMF's Nsmf interface PDU session update session management context response (Nsmf_PDUSession_UpdateSMContextresponse), or it can also be the SMF's Nsmf interface PDU session session management context status notification (Nsmf_PDUSession_SMContextStatusNotify), and there is no restriction on this.

[0292] Through the above steps 607-614, each relevant network element (such as CPE, UPF and RAN) can complete the configuration of measurement information. It can be understood that if the ColoredType value only includes DL, steps 607-608 can be executed, and steps 609-614 do not need to be executed; if the ColoredType value only includes UL, steps 609-614 can be executed, and steps 607-608 do not need to be executed; if the ColoredType value includes UL and DL, steps 607-614 can be executed, and there is no strict order between steps 607-608 and steps 609-614.

[0293] 615. SMF sends an SM modification response to NEF.

[0294] The SMF feeds back to the NEF the configuration result of the measurement information of the target service, such as the measurement information configuration result (such as measurement information configuration success or measurement information configuration success failure) of any one or more of the following network elements: CPE, RAN, or UPF.

[0295] In a possible implementation, the SM modification response may be an Nsmf interface PDU session update session management context response (Nsmf_PDUSession_UpdateSMContext response) of the SMF.

[0296] Optionally, the SM modification response may include the addresses of the following network elements: CPE, UPF and RAN. The address can be used for the subsequent routing of the WTEMF to send maintenance and measurement task configuration related messages to these network elements. The above address is an optional cell parameter. For example, if the SM modification response does not include the above address, the WTEMF may select the EMS that manages the UPF (or the EMS corresponding to the UPF) and the EMS that manages the RAN (or the EMS corresponding to the RAN) based on the location information of the CPE (such as the route tracking area identifier or the cell identifier, etc.). The EMS that manages the UPF can query the address of the UPF based on the location information of the CPE, and send corresponding maintenance and measurement task configuration related messages to the UPF; the EMS that manages the RAN can query the address of the RAN based on the location information of the CPE, and send corresponding maintenance and measurement task configuration related messages to the RAN.

[0297] 616. NEF sends a measurement information configuration response to WTEMF.

[0298] The measurement information configuration response includes the configuration result of the measurement information of the target service, such as the measurement information configuration result (such as measurement information configuration success or measurement information configuration success failure) of any one or more of the following network elements: CPE, RAN, or UPF. Optionally, the measurement information configuration response includes the addresses of the following network elements: CPE, UPF, and RAN.

[0299] The above steps 601-616 are about the process of triggering the generation of measurement information and measurement information configuration for the target service to be tested after the WTEMF receives the maintenance and testing request. The following describes the process of triggering the WTEMF to configure the performance measurement task for the target service and report the measurement results for the network element and terminal after completing the measurement information configuration in conjunction with steps 617-625.

[0300] After completing the configuration of the measurement information for the target service, such as after WTEMF receives the configuration result of the measurement information of the target service, WTEMF initiates the maintenance and measurement task for the target service. For example, WTEMF allocates a maintenance and measurement task identifier and decomposes the maintenance and measurement task, that is, WTEMF initiates the performance KPI measurement task configuration (or also called measurement task creation) of the colored data packets for the target service to CPE, RAN and UPF. Among them, the performance KPI measurement task configuration initiated by WTEMF for the colored data packets of the target service to CPE can be referred to step 617, and the performance KPI measurement task configuration initiated by WTEMF for the colored data packets of the target service to RAN and UPF respectively can be referred to steps 618-621.

[0301] 617, CPE configuration, maintenance and testing tasks.

[0302] As an example, WTEMF can directly initiate the configuration of the maintenance and measurement task for CPE. The configuration process of WTEMF for the maintenance and measurement task of CPE can be implemented based on the measurement task configuration process for CPE in the terminal equipment performance management. For this, reference can be made to the prior art, and the embodiments of the present application are not limited.

[0303] 618, WTEMF sends a maintenance task configuration request to EMS.

[0304] As an example, the WTEMF may configure the performance measurement tasks for the RAN and UPF through the EMS corresponding to the RAN (e.g., recorded as EMS-RAN) and the EMS corresponding to the UPF (e.g., recorded as EMS-CN). In one possible implementation, if the measurement information configuration response returned in step 616 includes the addresses of the following network elements: CPE, UPF, or RAN, then the WTEMF may determine the EMS-RAN based on the address of the RAN and determine the EMS-CN based on the address of the UPF. In another possible implementation, the WTEMF may determine the EMS-RAN and EMS-CN based on the location information of the CPE (e.g., routing tracking area identifier or cell identifier, etc.).

[0305] After WTEMF determines EMS-RAN and EMS-CN, it can send maintenance and testing task configuration requests to EMS-RAN and EMS-CN. Figure 6 For the convenience of description, only one EMS is shown, and this EMS is used as an example for exemplary explanation. It can be understood that the EMS can represent the EMS corresponding to the RAN, or can also represent the EMS corresponding to the UPF.

[0306] In a possible implementation manner, the maintenance and measurement task configuration request may be a measurement task creation request (CreateMeasJob request) of a performance assurance MnS of the EMS.

[0307] Optionally, the maintenance and measurement task configuration request includes one or more of the following information: measurement indication, maintenance and measurement task identifier (JobId), service-level KPI, measurement identifier (used to identify the measurement object), information #3, measurement time of the target service, CPE location, UPF address, RAN address, target stream (streamTarget), measurement result reporting method, or reporting period, etc.

[0308] The measurement indication is used to indicate that the performance indicator of the target service associated with the measurement identifier is measured. The measurement indication is an optional information element. For example, the maintenance and measurement task configuration request may not include the measurement indication. In this case, the maintenance and measurement task configuration request itself has the function of indicating that the performance indicator of the target service associated with the measurement identifier is measured.

[0309] The measurement time of the target service may include: measurement start time and measurement end time.

[0310] The information #3, or data measurement indication, may be used to indicate the data measurement mode of the network element performing the data measurement. The data measurement mode includes real-time measurement, delayed measurement, etc. In the embodiment shown in method 600, the information #3 may be used to indicate the real-time measurement.

[0311] Among them, the CPE location, UPF address, and RAN address are optional information elements. If the UPF address and RAN address are not carried in step 616, the CPE location information may be carried in step 618; if the UPF address or RAN address is carried in step 616, the UPF address or RAN address may be carried in step 618, and the CPE location information may not be carried.

[0312] Wherein, streamTarget is used to indicate the address used for reporting streamData. For example, the measuring device obtains the address used for reporting streamData through the streamTarget included in the maintenance task configuration request, and then can send the measurement result to WTEMF through a streamData message, such as a report streamData message.

[0313] The measurement result reporting mode is used to indicate a mode for reporting the measurement result. As an example, the measurement result reporting mode may include streaming-based reporting and file-based reporting.

[0314] The reporting period is used to indicate the period of reporting the measurement result. As an example, the reporting period is 1 minute, that is, the measurement result is reported once every 1 minute.

[0315] Among them, the service-level KPI is related to the measured network element and eventType. For example, different network elements can measure different KPIs. As an example, Table 7 shows the correspondence between different measured network elements and KPIs. For another example, different eventTypes have different corresponding KPIs, as shown in Table 2. Therefore, the KPIs of the target services shown in Table 2 are measured by different network elements respectively. Therefore, in the process of configuring the maintenance and measurement tasks, the KPIs of the target services measured by different network elements can be configured differently, as shown in Table 7.

[0316] For example, the KPIs that UPF can measure include uplink GTPU packet loss, downlink N3 large delay packet number, downlink N3 transmission delay, and downlink packet UPF processing delay. If eventType is a video surveillance card segment problem, then according to Table 2, it is necessary to measure the uplink PDCP packet loss number and the uplink GTPU packet loss number. Therefore, for the KPI of the target service configured by UPF, only the uplink GTPU packet loss number can be configured.

[0317] Table 7

[0318]

[0319] It can be understood that Table 7 is an exemplary description and the embodiments of the present application are not limited thereto.

[0320] 619, EMS determines UPF or RAN based on the CPE location.

[0321] As mentioned earlier, Figure 6 For simplicity, only one EMS is used. Specifically, if Figure 6 The EMS shown in FIG. 6 is EMS-RAN, then in step 619, EMS-RAN determines the RAN based on the location of the CPE; if Figure 6 The EMS shown in is EMS-CN, then in step 619, EMS-CN determines the UPF based on the location of the CPE.

[0322] For example, if the maintenance task configuration request in step 618 includes CPE location information, but does not include UPF address and RAN address, EMS-RAN can query the address information of RAN serving the location based on the location of CPE, and EMS-CN can query the address information of UPF serving the location based on the location of CPE. In a possible implementation, EMS-RAN can determine the address of RAN by means of DNS query or by querying the context information of network element devices stored locally in EMS-RAN, and EMS-CN can determine the address of UPF by means of DNS query or by querying the context information of network element devices stored locally in EMS-CN.

[0323] It can be understood that if the maintenance task configuration request in step 618 includes the UPF address and the RAN address, step 619 may not be performed.

[0324] 620, UPF and RAN configuration maintenance and testing tasks.

[0325] After EMS-RAN determines RAN based on the location of CPE, it can configure maintenance and testing tasks with RAN; after EMS-CN determines UPF based on the location of CPE, it can configure maintenance and testing tasks with UPF. Figure 6The EMS shown in FIG. 6 is EMS-RAN, then in step 620, EMS-RAN and RAN configure maintenance and testing tasks; if Figure 6 The EMS shown in FIG. 6 is EMS-CN. Then, in step 620, EMS-CN and UPF configure maintenance and testing tasks.

[0326] The embodiments of the present application do not limit the interaction between EMS and network elements. A possible implementation method is that the implementation of the configuration and maintenance tasks between EMS-RAN and RAN can refer to the configuration and maintenance tasks between WTEMF and EMS-RAN; the implementation of the configuration and maintenance tasks between EMS-CN and UPF can refer to the configuration and maintenance tasks between WTEMF and EMS-CN.

[0327] For example, EMS-CN can configure the performance measurement task for UPF through the CreateMeasJob request operation of performance assurance MnS. The configured information includes: maintenance and measurement task identifier, service-level KPI, measurement identifier, information #3, CPE location, RAN address, streamTarget (streamData reporting address), measurement result reporting method, reporting period, measurement start time, measurement end time, etc. After UPF completes the maintenance and measurement task configuration, it can also feedback the configuration result of the maintenance and measurement task to EMS-CN through the CreateMeasJob response of performance assurance MnS (such as maintenance and measurement task configuration success, and maintenance and measurement task configuration failure). If the maintenance and measurement task configuration fails, the CreateMeasJob response can also carry the reason for the failure. Optionally, the CreateMeasJob response can also carry the maintenance and measurement task identifier.

[0328] For another example, EMS-RAN can configure the performance measurement task for RAN through the CreateMeasJobrequest operation of performance assurance MnS. Specifically, the following information can be configured for RAN: maintenance and measurement task identifier, service-level KPI, measurement identifier, information #3, CPE location, UPF address, streamTarget (streamData reporting address), measurement result reporting method, reporting period, measurement start time, measurement end time, etc. After RAN completes the maintenance and measurement task configuration, it can also feedback the configuration result of the maintenance and measurement task to EMS-RAN through the CreateMeasJobresponse of performance assurance MnS (such as maintenance and measurement task configuration success, and maintenance and measurement task configuration failure). If the maintenance and measurement task configuration fails, the CreateMeasJob response can also carry the reason for the failure. Optionally, the CreateMeasJob response can also carry the maintenance and measurement task identifier.

[0329] For details about each information, please refer to the description in the previous step 618, which will not be repeated here.

[0330] 621, EMS feeds back the configuration result of the maintenance and testing task to WTEMF.

[0331] For example, after EMS-RAN receives the configuration result of the maintenance and measurement task fed back by RAN, it can forward the configuration result of the maintenance and measurement task to WTEMF through the CreateMeasJob response of the performanceassurance MnS.

[0332] For another example, after EMS-CN receives the configuration result of the maintenance and measurement task fed back by UPF, it can forward the configuration result of the maintenance and measurement task to WTEMF through the CreateMeasJob response of the performanceassurance MnS.

[0333] 622, UPF reports the measurement result to WTEMF.

[0334] UPF can report the measurement results to WTEMF through EMS-CN.

[0335] If the information #3 in step 620 is used to indicate that the method of data measurement is real-time measurement, the UPF immediately starts to measure the data packet with the measurement identifier (i.e., the data packet of the target service), obtains the measurement result of the data packet with the measurement identifier, and reports the above measurement result according to the reporting period and the measurement result reporting method. For example, if the measurement result reporting method in the maintenance and measurement task configuration request in step 618 is based on file reporting, the UPF reports the measurement result based on file. For another example, if the measurement result reporting method in the maintenance and measurement task configuration request in step 618 is based on stream reporting, the UPF reports the measurement result through reportStreamData. It can be understood that in the embodiment of the present application, the measurement result is for the measurement data of a certain service (i.e., the target service).

[0336] Optionally, the measurement result includes: a maintenance and measurement task identifier, a start time of data measurement statistics, an end time of data measurement statistics, a result of data measurement, and other information.

[0337] 623, RAN reports the measurement result to WTEMF.

[0338] RAN reports the measurement results to WTEMF through EMS-RAN.

[0339] Step 623 is similar to step 622 and will not be described again here.

[0340] 624, CPE reports the measurement result to WTEMF.

[0341] Step 624 is similar to step 622 and will not be described again here.

[0342] 625, WTEMF performs fault location analysis based on the measurement results.

[0343] Based on the maintenance and measurement task identifier, WTEMF can associate the data for the same maintenance and measurement task together, so that joint diagnosis and analysis can be performed based on the data reported by CPE, RAN and UPF. For example, WTEMF can select the data reported by CPE, RAN and UPF in the same time interval based on the start time and end time of the data measurement statistics (that is, data time synchronization can be completed), and perform joint diagnosis and analysis based on the time-synchronized data reported by CPE, RAN and UPF. One possible way is to first perform a delimitation analysis on the network fault, and then perform a fault location analysis. For example, if the delimitation analysis result is a CPE fault, a CPE fault location analysis can be performed based on performance data such as the device status data of the CPE; if the delimitation analysis result is a non-CPE fault, EMS-CN can be triggered to perform a fault location analysis of the UPF, and EMS-RAN can perform a fault location analysis of the RAN. WTEMF can perform maintenance and measurement delimitation and location analysis based on artificial intelligence (AI) machine learning algorithms, or traditional policy rules, which is not limited in the embodiments of the present application.

[0344] by Figure 2 Taking the scenario shown as an example, it is assumed that in a certain time period or moment, the return video of camera 1 is stuck, and other services on the CPE are normal, and it is assumed that the cause of the service problem of camera 1 is the uplink packet loss or disorder of the video return service flow of flow1. As described above, if a device-level fault diagnosis and analysis is performed, the average number of packet losses or packet loss rates of data packets of all service flows (such as flow1, flow2, and flow3) on the CPE are counted, and the number of packet losses or packet loss rates of the actual data packets of each service flow are averaged, so the final diagnosis and analysis result may be that there is no abnormal problem with the CPE, which leads to inaccurate fault diagnosis and analysis results. Through the embodiment of the present application, the measurement data based on which WTEMF performs fault location analysis is the measurement data of a finer-grained service (i.e., the target service), rather than the measurement data of all services, so the accuracy of fault diagnosis and analysis can be improved. Taking CPE as an example, the measurement data based on which WTEMF performs fault location analysis is the measurement data of the target service on the CPE, rather than the average value of the measurement data of all services on the CPE, so the accuracy of fault diagnosis and analysis can be improved.

[0345] For example, in step 601, the application server detects that the video of camera 1 is stuck, and in step 602, the application server sends a maintenance request to WTEMF, and carries the ID of camera 1 in the maintenance request; WTEMF configures measurement information for the service of camera 1 (or flow1), and sends the measurement information to CPE, UPF, and RAN; CPE, UPF, and RAN perform coloring processing on the data packets of flow1 according to the measurement information (such as adding a measurement identifier to the data packets of flow1); further, if CPE, UPF, and RAN receive the maintenance task of WTEMF, they can measure the colored data packets (such as data packets with measurement identifiers), that is, measure the colored data packets of flow1, and report the measurement data to WTEMF; then WTEMF performs fault analysis based on the reported measurement data. For example, WTEMF can perform joint diagnosis and analysis based on the measurement data of the dyed data packets of flow1 reported by CPE, UPF, and RAN, and then it can be concluded that the cause of the business problem of camera 1 is the uplink packet loss or disorder of the video return service flow of flow1; for another example, WTEMF first delimits the network fault and the result of the delimitation analysis is the CPE fault, and then WTEMF directly diagnoses and analyzes based on the measurement data of the dyed data packets of flow1 reported by CPE, and then it can be concluded that the cause of the business problem of camera 1 is the uplink packet loss or disorder of the video return service flow of flow1; for another example, WTEMF first delimits the network fault and the result of the delimitation analysis is the CPE fault, and then WTEMF initiates the measurement task configuration for the dyed data packets of flow1 to CPE, and then performs diagnosis and analysis based on the measurement data of the dyed data packets of flow1 reported by CPE, and then it can be concluded that the cause of the business problem of camera 1 is the uplink packet loss or disorder of the video return service flow of flow1. It can be understood that this is a simple exemplary description, and the specific description can refer to the description of each step in method 600.

[0346] Combination of the above Figure 6The steps 601-625 shown in the figure introduce the scenario that after receiving the maintenance and measurement request, WTEMF triggers the generation of measurement information for the service to be maintained and measured and configures the measurement information. After completing the measurement information configuration, WTEMF triggers the configuration of the performance measurement task for the service to be maintained and measured and the reporting of the measurement results for the network element and the terminal. Based on the above embodiment, the WTEMF function is enhanced to support the maintenance and measurement function of the service granularity, such as including the determination of maintenance and measurement performance KPI, the allocation of measurement identifiers, the configuration of measurement information, fault diagnosis and analysis, etc., and the service-level measurement information configuration is extended and enhanced in the session modification process. UPF, RAN and CPE enhance the support for the coloring processing function of the data packet, and when collecting measurement data, UPF, RAN and CPE only need to measure the colored data packets (such as data packets with measurement identifiers), so as to realize the network performance data collection for specific services and realize the rapid fault demarcation and positioning of the end-to-network collaboration.

[0347] Figure 7 It is a schematic flow chart of a measurement method provided in another embodiment of the present application. Figure 7 The method 700 shown may be used in the second possible scenario of the method 500 described above. Figure 7 The illustrated method 700 may include the following steps.

[0348] 701, after WTEMF detects that the terminal device is online, it configures measurement information.

[0349] After WTEMF detects that the terminal equipment (such as camera, PLC, etc.) connected to CPE is deployed and put into operation, it obtains the service identification of the terminal equipment from CPE and configures measurement information for the service of the terminal equipment. For distinction, the service for which measurement information is configured is recorded as the target service.

[0350] For example, WTEMF can determine the performance KPI of the target service to be measured and the type of data packet to be dyed according to the type of terminal device. At the same time, WTEMF can assign a measurement identifier FlowId to the target service and generate measurement information of the target service (see Table 3).

[0351] Steps 702-714 are similar to steps 604-616 and are not described again here.

[0352] After completing the configuration of the measurement information for the target service, if WTEMF receives the configuration result of the measurement information for the target service, WTEMF initiates the configuration of the maintenance and measurement task for the target service. For example, WTEMF allocates the maintenance and measurement task identifier and decomposes the maintenance and measurement task, that is, WTEMF initiates the performance KPI measurement task configuration of the colored data packet for the target service to CPE, RAN and UPF respectively.

[0353] 715, CPE configuration, maintenance and testing tasks.

[0354] As an example, WTEMF can directly initiate the configuration of the maintenance and measurement task for CPE. The configuration process of WTEMF for the maintenance and measurement task of CPE can be implemented based on the measurement task configuration process for CPE in the terminal equipment performance management. For this, reference can be made to the prior art, and the embodiments of the present application are not limited.

[0355] 716, WTEMF sends a maintenance task configuration request to EMS.

[0356] Step 716 is similar to step 618 , except that, in the embodiment shown in method 700 , the information # 3 may be used to indicate a delay measurement.

[0357] Steps 717-719 are similar to steps 619-621 and are not described again here.

[0358] After the above steps 701-719, the measurement equipment (i.e., CPE, RAN, and UPF) can first complete the measurement information configuration and maintenance task configuration, and data measurement can be temporarily not started. This can reduce the impact of the processing delay of the measurement information configuration and maintenance task configuration on data collection, so that the collected data is the network status performance data when the network fault occurs, and improve the accuracy of fault diagnosis and analysis.

[0359] 720. The application server detects a target service failure.

[0360] If the application server detects a service failure, the application server can initiate a maintenance request for the corresponding service to WTEMF in order to trigger WTEMF to measure the performance of the specified service and diagnose the network failure based on the service performance data analysis.

[0361] Step 720 is similar to step 601 and will not be described again here.

[0362] 721, the application server sends a maintenance request to WTEMF.

[0363] Optionally, the maintenance request includes one or more of the following information: DeviceId, abnormal event, or target service identifier.

[0364] Step 721 is similar to step 602 and will not be described again here.

[0365] 722. WTEMF sends a maintenance task activation request to NEF.

[0366] The maintenance and measurement task activation request includes a maintenance and measurement task identifier and a CPEId. Optionally, the maintenance and measurement task activation request includes a measurement indication, which is used to indicate that the performance indicator of the target service associated with the measurement identifier is measured. The measurement indication is an optional information element. For example, the maintenance and measurement task activation request may not include a measurement indication, in which case the maintenance and measurement task activation request itself has the function of indicating that the performance indicator of the target service associated with the measurement identifier is measured.

[0367] WTEMF can trigger the core network to start the control plane signaling process by calling the control plane service interface of NEF to activate the maintenance and measurement tasks configured on each relevant network element in the network, that is, trigger each relevant network element to start relevant KPI measurement statistics for the colored data packets of the target service.

[0368] In a possible implementation, the maintenance and testing task activation request may be Nnef_ApplyPolicy_Createrequest. In an embodiment of the present application, the input parameters of Nnef_ApplyPolicy_Create request may be enhanced to include the maintenance and testing task identifier and CPE Id. The above is an exemplary description, and the embodiment of the present application is not limited thereto. For example, a new NEF service interface may also be defined to implement the activation of the maintenance and testing task.

[0369] 723. NEF sends a maintenance and testing task activation request to SMF.

[0370] After NEF receives the maintenance and measurement task activation request sent by WTEMF, NEF can initiate the PDU session modification signaling process to SMF by calling the Nsmf_PDUSession service of SMF, that is, sending the maintenance and measurement task activation request to SMF through Nsmf_PDUSession_UpdateSMContext request or Nsmf_PDUSession_StatusNotify. For example, in an embodiment of the present application, the input parameters of Nsmf_PDUSession_UpdateSMContext request can be enhanced to include the maintenance and measurement task identifier and CPE Id.

[0371] 724. SMF sends a maintenance task activation request to UPF.

[0372] For example, when SMF receives a maintenance task activation request from NEF, SMF can activate UPF to start executing the maintenance task through N4 session modification request of N4 interface. For example, in an embodiment of the present application, the input parameters of N4 session modification request can be enhanced to include maintenance task identifier and CPE Id.

[0373] 725. SMF sends a maintenance and testing task activation request to AMF.

[0374] For example, SMF receives a maintenance and measurement task activation request from NEF. SMF can send the maintenance and measurement task activation request to AMF by calling the Namf_Communication_N1N2MessageTransfer service of AMF. The message element parameters include the maintenance and measurement task identifier and CPE Id.

[0375] 726. AMF sends a maintenance and testing task activation request to RAN and CPE.

[0376] The AMF sends a maintenance task activation request to the RAN and CPE respectively based on the N2 interface signaling (such as trace start) and the air interface RRC message (such as RRC reconfiguration message). The information element parameters of the message include the maintenance task identifier and CPE Id.

[0377] 727, measurement result reporting and fault diagnosis and analysis.

[0378] After receiving the maintenance task activation request, CPE, UPF and RAN immediately start to measure and count the relevant performance KPIs of the target service, and report the measurement and statistical results to WTEMF, which performs fault maintenance and diagnostic analysis. For the description of the measurement and statistical result reporting and diagnostic analysis process, refer to steps 622-625, which will not be repeated here.

[0379] Combination of the above Figure 7 The steps 701-727 shown in the figure introduce the scenario in which the measurement information configuration and the maintenance and measurement task configuration are completed after the terminal device is online, and the maintenance and measurement task is activated after the WTEMF receives the abnormal event report from the application server. Based on the above embodiment, the measurement information configuration and the maintenance and measurement task configuration are completed after the terminal device is online, and data measurement can be temporarily not started. When the WTEMF receives the abnormal event report from the application server, the maintenance and measurement task is quickly activated through the signaling plane, thereby reducing the impact of the processing delay of the measurement information configuration and the maintenance and measurement task configuration on data collection, so that the collected data is the network status performance data when the network failure occurs, and the accuracy of fault diagnosis and analysis is improved.

[0380] Figure 8 It is a schematic flow chart of a measurement method provided in another embodiment of the present application. Figure 8 The method 800 shown may be used in the third possible scenario of the method 500 described above. Figure 8 The illustrated method 800 may include the following steps.

[0381] 801: The application server detects that the service has started.

[0382] When the application server starts to send and receive service data, the application server may trigger performance KPI monitoring of a designated service (eg, recorded as a target service), such as the application server sending a monitoring request to WTEMF.

[0383] 802. The application server sends a monitoring request to WTEMF.

[0384] Optionally, the monitoring request includes: target service identifier, DeviceId, information #4, and target service type. Information #4, for example, may also be referred to as a KPI monitoring indication, which is used to indicate that KPI monitoring of the service needs to be performed. The target service type may include, for example, video monitoring, control instructions, etc.

[0385] In a possible implementation manner, the application server sends a monitoring request to WTEMF by calling an interface service of WTEMF.

[0386] 803, WTEMF configures measurement information.

[0387] For example, WTEMF can determine the performance KPI type of the service to be measured (as shown in Table 2) and the type of data packets to be colored according to the target service type. At the same time, WTEMF can assign a measurement identifier FlowId to the target service and configure the measurement information ColoredPolicy of the target service (as shown in Table 3).

[0388] Steps 804-816 are similar to steps 604-616 and will not be repeated here.

[0389] After completing the measurement information configuration for the target service, such as after WTEMF receives the configuration result of the measurement information of the target service, WTEMF initiates the maintenance and measurement task for the target service. For example, WTEMF allocates the maintenance and measurement task identifier and decomposes the maintenance and measurement task, that is, WTEMF initiates the performance KPI measurement task configuration of the colored data packet for the target service to CPE, RAN and UPF.

[0390] 817, CPE configuration, maintenance and testing tasks.

[0391] As an example, WTEMF can directly initiate the configuration of maintenance and measurement tasks for CPE. The configuration process of WTEMF for CPE maintenance and measurement tasks can be implemented based on the measurement task configuration process for CPE in terminal equipment performance management. Optionally, during the configuration process, a measurement result cache indication and a cache time of the measurement results can also be added to the configuration information. Among them, the measurement result cache indication is used to indicate the local caching of the performance data of the measurement statistics. The cache time of the measurement result is used to indicate the time information (such as the time length) for the local caching of the performance data of the measurement statistics.

[0392] 818, WTEMF sends a maintenance and testing task configuration request to EMS.

[0393] Step 818 is similar to step 618, except that, in the embodiment shown in method 800, the maintenance task configuration request also includes a measurement result cache indication and a measurement result cache time. The measurement result cache indication is used to indicate that the performance data of the measurement statistics is cached locally, and the measurement result cache time is used to indicate the time information (such as the time length) of the local cache of the performance data of the measurement statistics.

[0394] Among them, regarding the cache time of the measurement results, the cache time of the measurement results of each network element can be the same or different, and there is no restriction. For example, the cache time of the measurement results sent by WTEMF to CPE is T1, the cache time of the measurement results sent by WTEMF to EMS-CN (that is, the EMS corresponding to UPF) is also T1, and the cache time of the measurement results sent by WTEMF to EMS-RAN (that is, the EMS corresponding to RAN) is also T1.

[0395] 819, EMS determines UPF or RAN based on the CPE location.

[0396] Step 819 is similar to step 619 and will not be repeated here.

[0397] 820, UPF and RAN configuration maintenance and testing tasks.

[0398] Step 820 is similar to step 620, except that, in the embodiment shown in method 800, the maintenance and measurement task configuration request also includes a measurement result cache indication and a measurement result cache time.

[0399] CPE, RAN and UPF perform KPI measurement statistics of target services according to the maintenance task configuration, and cache the measurement results locally according to the cache time of the measurement results. If the cache time of the measurement results times out and the measurement results have not been requested to be reported (i.e., no measurement result reporting request has been received), the cached measurement results can be deleted to save storage space.

[0400] 821, EMS feeds back the results of maintenance and testing task configuration to WTEMF.

[0401] Step 821 is similar to step 621 and will not be repeated here.

[0402] After the above steps 801-821, the measuring equipment (i.e., CPE, RAN, and UPF) can first complete the measurement information configuration and maintenance task configuration, and start data measurement. This can ensure that the collected performance data is relevant data when the abnormal event occurs as much as possible, which can improve the accuracy of fault diagnosis and analysis.

[0403] 822. The application server detects a target service failure.

[0404] If the application server detects a target service failure, the application server may initiate a maintenance request for the target service to WTEMF in order to trigger WTEMF to perform performance measurement on the specified target service and diagnose the network failure based on the performance data analysis of the target service.

[0405] 823. The application server sends a maintenance request to WTEMF.

[0406] Optionally, the maintenance request includes one or more of the following information: DeviceId, abnormal event, target service identifier, or time when the abnormal event occurs (ProblemTime).

[0407] Step 823 is similar to step 602 and will not be described again here.

[0408] 824. WTEMF sends a measurement result reporting instruction to NEF.

[0409] The measurement result reporting indication, for example, may also be called a data reporting request, and is used to indicate reporting of the measurement result.

[0410] It can be understood that the measurement result reporting indication in method 800 can be used to indicate the reporting of previously obtained measurement results (i.e., measurements have been performed before and the measurement results have been cached). In this way, it can be ensured as much as possible that the collected performance data is relevant data when an abnormal event occurs, which can improve the accuracy of fault diagnosis and analysis. Different from method 800, the maintenance task activation request in method 700 can be used to indicate the start of measurement. In this way, unnecessary measurements can be avoided, such as measuring a service when the service is not faulty. As an example, in actual communications, different solutions can be selected according to different scenarios or actual needs. For example, for services that are more prone to failure, the solution of method 800 can be adopted; for another example, for services that are not prone to failure, the solution of method 600 or method 700 can be adopted.

[0411] Optionally, the measurement result reporting indication includes: maintenance and measurement task identifier, CPEId, target service identifier, KPI, and data time (dataTime).

[0412] Among them, KPI can refer to Table 7 to request different KPIs for different network elements. Among them, the data time is used to indicate the collection time period corresponding to the reported measurement data. It can be understood that the collection time period corresponding to the reported measurement data must include ProblemTime. For example, the data time is T2, which can represent: requesting to report the data measured T2 minutes before and after the ProblemTime moment, where T2 is a number greater than 0.

[0413] WTEMF can trigger the core network to start the control plane signaling process by calling the control plane service interface of NEF to trigger each related network element to report the relevant KPI measurement statistics of the cached target service.

[0414] In a possible implementation, the measurement result reporting indication may be Nnef_ApplyPolicy_Createrequest. In an embodiment of the present application, Nnef_ApplyPolicy_Create request may be enhanced to include a maintenance task identifier, a CPE ID, a target service identifier, a KPI, and a data time. The above is an exemplary description, and the embodiment of the present application is not limited thereto. For example, a new NEF service interface may also be defined.

[0415] 825, NEF forwards the measurement result reporting indication to SMF.

[0416] After NEF receives the measurement result reporting indication sent by WTEMF, NEF initiates the PDU session modification signaling process to SMF by calling the Nsmf_PDUSessionservice service of SMF, that is, sending the measurement result reporting indication to SMF through Nsmf_PDUSession_UpdateSMContext request or Nsmf_PDUSession_StatusNotify, and enhancing the input parameters of Nsmf_PDUSession_UpdateSMContext request to include maintenance task identifier, CPE ID, target service identifier, KPI, and data time.

[0417] 826, SMF forwards the measurement result reporting indication to UPF.

[0418] After SMF receives the measurement result reporting indication from NEF, SMF can trigger UPF to start reporting maintenance data through N4 sessionModification request of N4 interface. In the embodiment of the present application, the input parameters of N4sessionModification request can be enhanced to include maintenance task identifier, CPE ID, target service identifier, KPI, and data time.

[0419] 827, SMF forwards the measurement result reporting indication to AMF.

[0420] SMF sends a maintenance measurement result reporting indication to AMF by calling AMF's Namf_Communication_N1N2MessageTransfer service.

[0421] 828, AMF forwards the measurement result reporting indication to RAN and CPE.

[0422] The AMF sends measurement result reporting instructions to the RAN and CPE respectively based on N2 interface signaling (such as trace start) and air interface RRC messages (such as RRC reconfiguration messages).

[0423] 829, measurement result reporting and fault diagnosis and analysis.

[0424] After receiving the measurement result reporting instruction, CPE, UPF and RAN report the measurement results to WTEMF. For example, CPE, UPF and RAN identify the measurement task according to the maintenance and measurement task identifier in the measurement result reporting instruction, identify the target service according to the target service identifier, and report the measurement data collected in the corresponding time period according to the data time. After receiving the reported measurement results, WTEMF can perform fault maintenance and measurement diagnosis and analysis. For the relevant description of the measurement statistics result reporting and diagnosis and analysis process, please refer to steps 622-625, which will not be repeated here.

[0425] Combination of the above Figure 8 The steps 801-829 shown in the figure introduce the scenario of performing data collection when the service starts, and reporting the data of a period of time before and after the abnormal event occurs when the monitored abnormal event occurs. Based on the above embodiment, data collection is performed when the service starts, and it is not reported to WTEMF temporarily, but cached locally for a period of time. When the abnormal event is detected, the measurement data of a period of time before and after the abnormal event occurs is requested to be reported, and then the maintenance fault diagnosis and analysis is performed. In this way, it can be ensured that the collected performance data is the relevant data when the abnormal event occurs, which can improve the accuracy of fault diagnosis and analysis.

[0426] It can be understood that the Figures 6 to 8 The examples are only for the convenience of those skilled in the art to understand the embodiments of the present application, and are not intended to limit the embodiments of the present application to the specific scenarios illustrated. Figures 6 to 8 Obviously, various equivalent modifications or changes can be made, and such modifications or changes also fall within the scope of the embodiments of the present application. Figures 6 to 8 The target business can be replaced by one or more businesses.

[0427] It is also understandable that the above Figures 6 to 8 The steps in the above are only exemplary and are not strictly limited. Figure 6 For example, if only the downlink data packet is dyed, steps 609-614 may not be performed; if only the uplink data packet is dyed, steps 607-608 may not be performed. Figure 6 For example, if WTEMF only initiates the performance KPI measurement task configuration of the colored data packet for the target service to CPE, steps 618-621 and steps 622-623 may not be executed; if WTEMF only initiates the performance KPI measurement task configuration of the colored data packet for the target service to RAN and UPF, steps 617 and 624 may not be executed. In addition, the size of the sequence number of each process above does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application.

[0428] It can also be understood that some optional features in the embodiments of the present application may not depend on other features in some scenarios, or may be combined with other features in some scenarios, without limitation.

[0429] It can also be understood that the solutions in the various embodiments of the present application can be used in reasonable combination, and the explanations or descriptions of the various terms appearing in the embodiments can be mutually referenced or explained in the various embodiments, without limitation.

[0430] It can also be understood that the sizes of the various digital serial numbers in the embodiments of the present application do not mean the order of execution, but are only distinguished for the convenience of description and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0431] It can also be understood that some message names are involved in the various embodiments of the present application, such as session modification request, monitoring request, maintenance request, etc., and their naming does not limit the protection scope of the embodiments of the present application.

[0432] It can also be understood that in some of the above embodiments, the coloring process is mentioned multiple times, which means that the data packet is subjected to coloring process, or in other words, the data packet is associated with a measurement identifier.

[0433] It can also be understood that in some of the above embodiments, measurement results and measurement data are sometimes used interchangeably, and both are used to represent measured data.

[0434] It can also be understood that in the above-mentioned method embodiments, the methods and operations implemented by the terminal device can also be implemented by components that can be formed by the terminal device (such as chips or circuits); in addition, the methods and operations implemented by the network device can also be implemented by components that can be formed by the network device (such as chips or circuits), without limitation.

[0435] Corresponding to the methods given in the above-mentioned method embodiments, the embodiments of the present application also provide corresponding devices, which include modules for executing the corresponding methods in the above-mentioned 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-mentioned method embodiments are also applicable to the following device embodiments.

[0436] Fig. 9 9 is a schematic block diagram of a measuring device provided in an embodiment of the present application. The device 900 includes a transceiver unit 910 and a processing unit 920. The transceiver unit 910 can implement corresponding communication functions, and the transceiver unit 910 can also be a communication interface or a communication unit. The processing unit 920 can implement corresponding processing functions, such as processing instructions and / or data.

[0437] In a possible implementation, the device 900 may further include a storage unit, which may be used to store instructions and / or data, and the processing unit 920 may read the instructions and / or data in the storage unit so that the device implements the aforementioned method embodiment.

[0438] The device 900 can be used to execute the actions performed by the communication device (such as a management device or a measuring device) in the above method embodiments. In this case, the device 900 can be a communication device or a component that can be configured on a communication device. The transceiver unit 910 is used to execute the transceiver-related operations on the communication device side in the above method embodiments, and the processing unit 920 is used to execute the processing-related operations on the communication device side in the above method embodiments.

[0439] As a design, the apparatus 900 is used to execute the actions performed by the management device (such as WTEMF) in the above method embodiment.

[0440] In a possible implementation, the transceiver unit 910 is used to send a measurement identifier to a measuring device, where the measurement identifier is used to associate with a target service to be measured, where the target service is a service corresponding to a data flow passing through an industry terminal; the transceiver unit 910 is also used to send a measurement indication to the measuring device, where the measurement indication is used to indicate that a performance indicator of the target service associated with the measurement identifier is measured, where the performance indicator of the target service is associated with an abnormal event of the target service. Optionally, the processing unit 920 is used to configure a measurement identifier for the target service.

[0441] In one example, the transceiver unit 910 is further configured to send one or more of the following information to the measurement device: a data packet type of a target service associated with the measurement identifier, an identifier of the target service, an identifier of a user premises equipment corresponding to the target service, or an identifier of a terminal device.

[0442] In another example, the transceiver unit 910 is specifically used to send a measurement identifier to a measuring device after receiving a maintenance request for performing maintenance on a target service; or, after receiving a monitoring request for monitoring a performance indicator of a target service, send a measurement identifier to the measuring device; or, after monitoring that a terminal device is online, send a measurement identifier to the measuring device.

[0443] In another example, the transceiver unit 910 is further configured to receive address information of a measuring device.

[0444] In another example, the transceiver unit 910 is specifically configured to send a measurement instruction to a measurement device after receiving a maintenance request for performing maintenance on a target service; or send a measurement instruction to a measurement device after receiving a monitoring request for monitoring a performance indicator of a target service.

[0445] In another example, the transceiver unit 910 is further configured to send a measurement result cache indication of the target service and / or a cache time of the measurement result of the target service to the measurement device.

[0446] In another example, the transceiver unit 910 is further configured to send a measurement result reporting indication to the measurement device, where the measurement result reporting indication is used to instruct reporting of the measurement result of the target service in the target time period.

[0447] In another example, the transceiver unit 910 is further used to send one or more of the following information to the measuring device: performance indicators of the target service, maintenance task identifiers, measurement identifiers, measurement time of the target service, measurement methods of the measuring device, or addresses of the measuring device.

[0448] In another example, the maintenance request includes one or more of the following information: an abnormal event of the target service, an identifier of the terminal device, or an identifier of the target service.

[0449] The device 900 can implement the steps or processes executed by the management device (such as WTEMF) in the method embodiment according to the embodiment of the present application. The device 900 may include a method for executing Figures 5 to 8 Furthermore, each unit in the device 900 and the above-mentioned other operations and / or functions are respectively for implementing Figures 5 to 8 The corresponding process of the method embodiment in the management device in.

[0450] It should be understood that the specific process of each unit executing the above corresponding steps has been described in detail in the above method embodiment, and for the sake of brevity, it will not be repeated here.

[0451] As another design, the apparatus 900 is used to execute the actions performed by the measuring device (such as CPE, such as UPF, and such as RAN) in the above method embodiments.

[0452] In one possible implementation, a transceiver unit 910 is used to receive a measurement identifier from a management device, where the measurement identifier is used to associate with a target service to be measured, where the target service is a service corresponding to a data flow passing through an industry terminal; a processing unit 920 is used to associate the measurement identifier with the target service; and the processing unit 920 is further used to measure performance indicators of the target service associated with the measurement identifier, where the performance indicators of the target service are associated with abnormal events of the target service.

[0453] In one example, the transceiver unit 910 is further configured to receive one or more of the following information from the management device: a data packet type of a target service associated with a measurement identifier, an identifier of the target service, an identifier of a user premises equipment corresponding to the target service, or an identifier of a terminal device.

[0454] In another example, the processing unit 920 is specifically configured to add a measurement identifier to a data packet of the target service.

[0455] In another example, the transceiver unit 910 is further configured to send address information of the measuring device.

[0456] In another example, the transceiver unit 910 is further used to receive a measurement indication from a management device, where the measurement indication is used to indicate measurement of performance indicators of a target service associated with the measurement identifier; the processing unit 920 is specifically used to measure the performance indicators of the target service associated with the measurement identifier in response to the measurement indication.

[0457] In another example, the transceiver unit 910 is also used to receive a measurement result cache indication of the target service and / or a cache time of the measurement result of the target service from the management device; the processing unit 920 is also used to cache the measurement result of the target service according to the measurement result cache indication of the target service and / or the cache time of the measurement result of the target service.

[0458] In another example, the transceiver unit 910 is also used to report the measurement results of the target time period to the management device if a measurement result reporting indication is received from the management device within a preset time period, wherein the measurement result reporting indication is used to indicate reporting the measurement results of the target service in the target time period; or, if no measurement result reporting indication is received from the management device within the preset time period, the processing unit 920 is used to delete the cached measurement results of the target service in the target time period.

[0459] In another example, the transceiver unit 910 is further configured to receive one or more of the following information from the management device: performance indicators of the target service, maintenance task identifiers, measurement identifiers, measurement time of the target service, measurement methods of the measurement device, or addresses of the measurement device.

[0460] The apparatus 900 may implement the steps or processes executed by the measuring device (such as CPE, UPF, or RAN) in the method embodiment according to the embodiment of the present application. The apparatus 900 may include a method for executing Figures 5 to 8 Furthermore, each unit in the device 900 and the above-mentioned other operations and / or functions are respectively for implementing Figures 5 to 8 The corresponding process of the method embodiment in the measuring device in.

[0461] It should be understood that the specific process of each unit executing the above corresponding steps has been described in detail in the above method embodiment, and for the sake of brevity, it will not be repeated here.

[0462] It should also be understood that the device 900 here is embodied in the form of a functional unit. The term "unit" here may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (e.g., a shared processor, a proprietary processor, or a group processor, etc.) and a memory for executing one or more software or firmware programs, a merged logic circuit, and / or other suitable components that support the described functions. In an optional example, those skilled in the art will understand that the device 900 may be specifically a communication device (e.g., a management device, or a measuring device) in the above-mentioned embodiments, and may be used to execute the various processes and / or steps corresponding to the communication device (e.g., a management device, or a measuring device) in the above-mentioned method embodiments. To avoid repetition, it will not be repeated here.

[0463] In addition, the processing unit 920 in the above embodiment can be implemented by at least one processor or processor-related circuit. The transceiver unit 910 can be implemented by a transceiver or a transceiver-related circuit. The storage unit can be implemented by at least one memory.

[0464] It should be pointed out that Fig. 9 The device in the embodiment may be a network element or device in the foregoing embodiment, or may be a chip or a chip system, such as a system on chip (SoC). The transceiver unit may be an input / output circuit or a communication interface; the processing unit may be a processor or a microprocessor or an integrated circuit integrated on the chip. This is not limited here.

[0465] Fig.10 The device 1000 includes a processor 1010, the processor 1010 is coupled to a memory 1020, the memory 1020 is used to store computer programs or instructions and / or data, and the processor 1010 is used to execute the computer programs or instructions and / or data stored in the memory 1020, so that the method in the above method embodiment is executed.

[0466] In a possible implementation, the device 1000 includes one or more processors 1010.

[0467] Alternatively, if Fig.10 As shown, the device 1000 also includes a memory 1020 .

[0468] In a possible implementation, the memory 1020 included in the device 1000 may be one or more.

[0469] In a possible implementation, the memory 1020 may be integrated with the processor 1010 or provided separately.

[0470] Alternatively, if Fig.10 As shown, the device 1000 further includes a transceiver 1030. The transceiver 1030 may be used to receive and / or send signals. For example, the processor 1010 is used to control the transceiver 1030 to receive and / or send signals.

[0471] As a solution, the apparatus 1000 is used to implement the operations performed by the communication device (such as a management device or a measurement device) in the above method embodiment.

[0472] For example, the processor 1010 is used to implement the processing-related operations performed by the management device (such as WTEMF) in the above method embodiment, and the transceiver 1030 is used to implement the sending and receiving-related operations performed by the management device (such as WTEMF) in the above method embodiment.

[0473] For example, the processor 1010 is used to implement the processing-related operations performed by the measuring device (such as CPE, UPF, or RAN) in the above method embodiments, and the transceiver 1030 is used to implement the transceiver-related operations performed by the measuring device (such as CPE, UPF, or RAN) in the above method embodiments.

[0474] Fig.11 It is a schematic diagram of a chip provided according to an embodiment of the present application. The chip 1100 (or it may also be referred to as a processing system, or it may also be referred to as a chip system) includes a processor 1110, and the processor may be a processor or a microprocessor or an integrated circuit integrated on the chip. Optionally, the chip 1100 may also include a communication interface 1120, and the communication interface 1120 may also be an input-output circuit, or an input / output interface. When the chip 1100 is a chip system or a processing system, the device on which the chip 1100 is installed may implement the method and function of the embodiment of the present application. For example, the processor 1110 may be a processing circuit in a chip system or a processing system, and realizes the control of the device on which the chip system or the processing system is installed. It may also be coupled to a storage unit, and call instructions in the storage unit, so that the device may implement the method and function of the embodiment of the present application. The communication interface 1120 may be an input-output circuit in a chip system or a processing system, and output the information processed by the chip system, or input the data or signaling information to be processed into the chip system for processing.

[0475] As a solution, the apparatus 1100 is used to implement the operations performed by the communication device (such as a management device or a measurement device) in the above method embodiments.

[0476] For example, the processor 1110 is used to implement the processing-related operations performed by the management device (such as WTEMF) in the above method embodiment, and the communication interface 1120 is used to implement the sending and receiving-related operations performed by the management device (such as WTEMF) in the above method embodiment.

[0477] For example, the processor 1110 is used to implement the processing-related operations performed by the measuring device (such as CPE, UPF, or RAN) in the above method embodiments, and the communication interface 1120 is used to implement the sending and receiving related operations performed by the measuring device (such as CPE, UPF, or RAN) in the above method embodiments.

[0478] An embodiment of the present application further provides a computer-readable storage medium on which are stored computer instructions for implementing the method executed by a communication device (such as a management device or a measurement device) in the above method embodiment.

[0479] An embodiment of the present application also provides a computer program product including instructions, which, when executed by a computer, enables the computer to implement the method performed by a communication device (such as a management device or a measurement device) in the above method embodiment.

[0480] An embodiment of the present application further provides a communication system, which includes one or more of the management device, the measurement device, the network element management device (such as EMS), and the application server in the above embodiment.

[0481] For example, the communication system includes the management device (such as WTEMF) and the measurement device in the above embodiments.

[0482] The explanation of the relevant contents and beneficial effects of any of the above-mentioned devices can be referred to the corresponding method embodiments provided above, which will not be repeated here.

[0483] It should be understood that the processor mentioned in the embodiments of the present application may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0484] It should also be understood that the memory mentioned in the embodiments of the present application may be a volatile memory and / or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM). For example, RAM can be used as an external cache. By way of example and not limitation, RAM may include the following forms: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0485] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) can be integrated into the processor.

[0486] It should also be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0487] Those of ordinary skill in the art will appreciate that the units and steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of protection of this application.

[0488] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0489] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to implement the solution provided by the present application.

[0490] In addition, each functional unit in each embodiment of the present application may be integrated into one unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0491] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. For example, the computer can be a personal computer, a server, or a network device, etc. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that contains one or more available media integrations. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state disk (SSD)). For example, the aforementioned available medium may include, but is not limited to, various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0492] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A measurement method, characterized in that: include: The management device sends a measurement identifier to the measurement device, where the measurement identifier is used to associate with a target service to be measured, where the target service is a service corresponding to a data flow passing through an industry terminal; The management device sends a measurement indication to the measurement device, where the measurement indication is used to instruct to measure a performance indicator of the target service associated with the measurement identifier, where the performance indicator of the target service is associated with an abnormal event of the target service; The management device sending the measurement identifier to the measurement device includes: After receiving the maintenance and testing request for performing maintenance and testing on the target service, the management device sends the measurement identifier to the measuring device; or, After receiving the monitoring request for monitoring the performance indicator of the target service, the management device sends the measurement identifier to the measurement device; or, After the management device detects that the terminal device is online, the management device sends the measurement identifier to the measurement device.

2. The method according to claim 1, characterized in that The method further comprises: The management device sends one or more of the following information to the measurement device: The data packet type of the target service associated with the measurement identifier, the identifier of the target service, the user premises equipment identifier corresponding to the target service, or the identifier of the terminal equipment.

3. The method according to claim 1, characterized in that The method further comprises: The management device receives the address information of the measuring device.

4. The method according to any one of claims 1 to 3, characterized in that The management device sending a measurement instruction to the measurement device includes: After receiving the maintenance and measurement request for performing maintenance and measurement on the target service, the management device sends the measurement instruction to the measurement device; or, After receiving the monitoring request for monitoring the performance indicator of the target service, the management device sends the measurement instruction to the measurement device.

5. The method according to claim 4, characterized in that After receiving the monitoring request for monitoring the performance indicator of the target service, the management device sends the measurement instruction to the measurement device; The method further comprises: The management device sends a measurement result cache indication of the target service and / or a cache time of the measurement result of the target service to the measurement device.

6. The method according to claim 5, characterized in that The method further comprises: The management device sends a measurement result reporting instruction to the measurement device, where the measurement result reporting instruction is used to instruct reporting of the measurement result of the target service in a target time period.

7. The method according to claim 6, characterized in that The method further comprises: The management device sends one or more of the following information to the measuring device: a performance indicator of the target service, a maintenance task identifier, the measurement identifier, a measurement time of the target service, a measurement mode of the measuring device, or an address of the measuring device.

8. The method according to any one of claims 1 to 3, characterized in that The maintenance request includes one or more of the following information: an abnormal event of the target service, an identifier of the terminal device, or an identifier of the target service.

9. The method according to claim 6, characterized in that The maintenance request includes one or more of the following information: an abnormal event of the target service, an identifier of a terminal device, or an identifier of the target service.

10. A measurement method, characterized in that: include: The measuring device receives a measurement identifier from the management device, where the measurement identifier is used to associate with a target service to be measured, where the target service is a service corresponding to a data flow passing through an industry terminal; The measuring device associates the measurement identifier with the target service; The measuring device measures a performance indicator of the target service associated with the measurement identifier, where the performance indicator of the target service is associated with an abnormal event of the target service; The measuring device receives the measurement identifier from the management device, including: In a case where the management device receives a maintenance and measurement request for performing maintenance and measurement on the target service, the measurement device receives a measurement identifier from the management device; or, In a case where the management device receives a monitoring request for monitoring the performance indicator of the target service, the measurement device receives a measurement identifier from the management device; or, When the management device detects that the terminal device is online, the measurement device receives a measurement identifier from the management device.

11. The method according to claim 10, characterized in that The method further comprises: The measuring device receives one or more of the following information from the management device: The data packet type of the target service associated with the measurement identifier, the identifier of the target service, the user premises equipment identifier corresponding to the target service, or the identifier of the terminal equipment.

12. The method according to claim 10, characterized in that The measuring device associating the measurement identifier with the target service includes: The measuring device adds the measurement identifier to the data packet of the target service.

13. The method according to any one of claims 10 to 12, characterized in that The method further comprises: The measuring device sends address information of the measuring device.

14. The method according to any one of claims 10 to 12, characterized in that The method further comprises: The measuring device receives a measurement instruction from the management device, where the measurement instruction is used to instruct to measure a performance indicator of the target service associated with the measurement identifier; The measuring device measures the performance indicator of the target service associated with the measurement identifier, including: In response to the measurement indication, the measurement device measures the performance indicator of the target service associated with the measurement identifier.

15. The method according to any one of claims 10 to 12, characterized in that The method further comprises: The measuring device receives a measurement result cache indication of the target service and / or a cache time of the measurement result of the target service from the management device; The measurement device caches the measurement result of the target service according to the measurement result cache indication of the target service and / or the cache time of the measurement result of the target service.

16. The method according to claim 15, characterized in that The method further comprises: Within a preset time period, if the measuring device receives a measurement result reporting indication from the management device, the measuring device reports the measurement result of the target time period to the management device, wherein the measurement result reporting indication is used to indicate reporting the measurement result of the target service in the target time period; or, If the measuring device does not receive the measurement result reporting instruction from the management device within the preset time period, the measuring device deletes the cached measurement result of the target service in the target time period.

17. The method according to claim 16, characterized in that The method further comprises: The measuring device receives one or more of the following information from the management device: a performance indicator of the target service, a maintenance task identifier, the measurement identifier, a measurement time of the target service, a measurement method of the measuring device, or an address of the measuring device.

18. A measuring device, characterized in that: The method comprises means for implementing the method as claimed in any one of claims 1 to 17.

19. A measuring device, characterized in that: include: A processor, configured to execute computer instructions stored in the memory so that the apparatus performs: a method as claimed in any one of claims 1 to 17.

20. A computer-readable storage medium, characterized in that: include: The computer-readable storage medium stores a computer program; when the computer program is executed by one or more processors, the device including the processor executes the method according to any one of claims 1 to 17.

21. A computer program product, characterized in that The computer program product comprises instructions for performing the method of any one of claims 1 to 17.

22. A communication system, characterized in that: include: Management equipment and measuring equipment, The management device is used to perform the method according to any one of claims 1 to 9, The measuring device is used to perform the method according to any one of claims 10 to 17.

Images