Fault detection method for a slave device and electronic device

Abstract

The application provides a fault detection method of a slave station device and an electronic device. The method comprises the following steps: a UPF network element receives a first data frame sent by a master station device, determines a first addressing type of each slave station device according to command information in the first data frame, generates first record information according to a first address value, a preset count value and the first addressing type, sends the first data frame to each slave station device, receives a returned second data frame, determines a second addressing type of each slave station device according to command information in the second data frame, generates second record information according to a second address value, an updated count value and the second addressing type, sends the first record information and the second record information to a network management server, and performs fault detection on each slave station device according to the preset count value and the updated count value when the first addressing type and the second addressing type are consistent and the first address value and the second address value are consistent.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of communication, in particular to a fault detection method of a slave device and an electronic device. BACKGROUND

[0002] EtherCAT (Ethernet for Control Automation Technology) usually has the characteristic of "scan and use", scanning the network, starting the system, and all components are running, and in most cases, no parameters need to be set.

[0003] In the related art, for an EtherCAT network, the Working Counter (WKC) is the only diagnostic information periodically sent back to the master device together with the process data, wherein the WKC is incremented every time a slave device specified in a data packet is passed, so that whether the EtherCAT network is faulty can be determined based on the WKC.

[0004] However, the above method can only determine that a fault has occurred in the EtherCAT network, but cannot determine which slave device has failed, which makes it difficult to quickly analyze and identify network faults. SUMMARY

[0005] Therefore, the embodiments of the present application provide a fault detection method of a slave device and an electronic device to realize fault detection of the slave device.

[0006] In a first aspect, the embodiments of the present application provide a fault detection method of a slave device, applied to a UPF network element, and the method comprises:

[0007] receiving a first data frame sent by a master device, wherein the first data frame comprises a first address value of each slave device, a preset value, and command information;

[0008] determining a first addressing type of each slave device according to the command information in the first data frame, and generating first record information of each slave device according to the first address value, the preset value, and the first addressing type;

[0009] sending the first data frame to each slave device, so that each slave device executes a command corresponding to the command information, and updates the preset value;

[0010] receiving a second data frame returned by each slave device after executing the command, wherein the second data frame comprises a second address value of each slave device, an updated count value, and the command information;

[0011] determining a second addressing type of the slave device according to the command information in the second data frame, and generating second record information of the slave device according to the second address value, the updated count value and the second addressing type;

[0012] sending the first record information and the second record information to a network management server, so that the network management server performs fault detection on the slave device according to the preset count value and the updated count value when the first addressing type and the second addressing type are consistent and the first address value and the second address value are consistent.

[0013] In an optional implementation, the generating the first record information of the slave device according to the first address value, the preset count value and the first addressing type comprises:

[0014] generating the first record information according to the first address value, the preset count value, the first addressing type and a first data direction corresponding to the first data frame, the first data direction being a data direction from the master device to the UPF network element;

[0015] The generating the second record information of the slave device according to the second address value, the updated count value and the second addressing type comprises:

[0016] generating the second record information according to the second address value, the updated count value, the second addressing type and a second data direction corresponding to the second data frame, the second data direction being a data direction from the slave device to the UPF network element, and the network management server is further configured to perform fault detection on the slave device according to the preset count value and the updated count value when the first data direction and the second data direction match.

[0017] In an optional implementation, the method further comprises:

[0018] obtaining a session identifier of a PDU session established by the slave device and the UPF network element through a terminal device after the slave device establishes the PDU session with the UPF network element;

[0019] The generating the first record information of the slave device according to the first address value, the preset count value and the first addressing type comprises:

[0020] generating the first record information according to the first address value, the preset count value, the first addressing type and the session identifier;

[0021] The generating the second record information of the slave devices according to the second address value, the updated count value and the second addressing type comprises:

[0022] The generating the second record information according to the second address value, the updated count value, the second addressing type and the session identifier, the network management server is further configured to perform fault detection on the slave devices according to the preset count value and the updated count value when the session identifier in the first record information is consistent with the session identifier in the second record information.

[0023] In an optional embodiment, the method further comprises:

[0024] The session identifier is sent to the network management server, so that the network management server acquires the device identifier of the terminal device according to the session identifier.

[0025] In a third aspect, the embodiments of the present application further provide a fault detection method of a slave device, applied to a network management server, and the method comprises:

[0026] The first record information and the second record information sent by the UPF network element are received, the first record information comprises a first address value, a preset count value and a first addressing type of each slave device, and the second record information comprises a second address value, an updated count value and a second addressing type of each slave device.

[0027] If the first addressing type and the second addressing type are consistent, and the first address value and the second address value are consistent, then fault detection is performed on the slave devices according to the preset count value and the updated count value.

[0028] In an optional embodiment, the performing fault detection on the slave devices according to the preset count value and the updated count value comprises:

[0029] A first data direction corresponding to a first data frame is acquired from the first record information, and a second data direction corresponding to a second data frame is acquired from the second record information, the first data frame is a data frame sent by a master device to the UPF network element, and the second data frame is a data frame sent by the slave devices to the UPF network element.

[0030] If the first data direction and the second data direction match, then fault detection is performed on the slave devices according to the preset count value and the updated count value.

[0031] In an optional implementation, the fault detection of the slave devices according to the preset count value and the updated count value comprises:

[0032] obtaining a session identifier of a PDU session from the first record information and obtaining the session identifier from the second record information, the session identifier being an identifier of a PDU session established by the slave devices through a terminal device and the UPF network element;

[0033] if the session identifier in the first record information is consistent with the session identifier in the second record information, performing fault detection of the slave devices according to the preset count value and the updated count value.

[0034] In an optional implementation, the method further comprises:

[0035] receiving a session identifier sent by the UPF network element, the session identifier being an identifier of a PDU session established by the slave devices through a terminal device and the UPF network element;

[0036] sending a device identifier query request to a NEF network element, the device identifier query request comprising the session identifier, so that the NEF network element queries a device identifier of the terminal device through a SMF network element;

[0037] receiving the device identifier sent by the NEF network element;

[0038] updating the first record information and the second record information according to the device identifier.

[0039] In an optional implementation, the method further comprises:

[0040] if the slave devices have no fault, updating the first record information and the second record information according to a connection relationship between the slave devices and a terminal device.

[0041] In a third aspect, the embodiments of the present application further provide an electronic device, comprising a processor, a memory and a bus, the memory stores machine readable instructions executable by the processor, when the electronic device is running, the processor and the memory communicate through the bus, the processor executes the machine readable instructions to execute the method of any one of the first aspect.

[0042] The application provides a fault detection method of a slave station device and an electronic device. The method comprises the following steps: a UPF network element receives a first data frame sent by a master station device, determines a first addressing type of each slave station device according to command information in the first data frame, generates first record information according to a first address value, a preset value and the first addressing type, sends the first data frame to each slave station device, receives a second data frame returned, determines a second addressing type of each slave station device according to command information in the second data frame, generates second record information according to a second address value, an updated count value and the second addressing type, sends the first record information and the second record information to a network management server, and performs fault detection on each slave station device according to the preset value and the updated count value when the first addressing type and the second addressing type are consistent and the first address value and the second address value are consistent. The fault detection on the slave station device is realized. BRIEF DESCRIPTION OF DRAWINGS

[0043] In order to more clearly illustrate the technical solutions of the embodiments of the application, the drawings needed to be used in the embodiments will be briefly introduced as follows. It should be understood that the following drawings only show some of the embodiments of the application, and therefore should not be regarded as a limitation on the scope. For those skilled in the art, other related drawings can also be obtained without creative labor on the basis of these drawings.

[0044] Figure 1 The architecture schematic diagram of the fault detection system of the slave station device provided by the embodiments of the application is shown in the figure.

[0045] Figure 2 The flowchart of the fault detection method of the slave station device provided by the embodiments of the application is shown in the figure. Figure One

[0046] Figure 3 The flowchart of the fault detection method of the slave station device provided by the embodiments of the application is shown in the figure. Figure Two

[0047] Figure 4 The flowchart of the fault detection method of the slave station device provided by the embodiments of the application is shown in the figure. Figure Three

[0048] Figure 5 The flowchart of the fault detection method of the slave station device provided by the embodiments of the application is shown in the figure. Figure Four

[0049] Figure 6 The structure schematic diagram of the fault detection device of the slave station device provided by the embodiments of the application is shown in the figure. Figure One

[0050] Figure 7 The structure schematic diagram of the fault detection device of the slave station device provided by the embodiments of the application is shown in the figure.​​​​​Figure Two ;

[0051] Figure 8 The structural schematic diagram of an electronic device provided by an embodiment of the present application is shown. DETAILED DESCRIPTION

[0052] In order to make the objectives, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be described below in connection with the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. The components of the embodiments of the present application described and shown in the drawings herein can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the claimed present application, but only represents selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without creative work fall within the scope of the present application.

[0053] First, the professional terms involved in the present application are described:

[0054] EtherCAT (Ethernet for Control Automation Technology) is a real-time Ethernet communication protocol used in industrial automation and control systems to achieve high-performance, real-time data transmission and control. It is developed and standardized by the EtherCAT Technology Group (ETG).

[0055] EtherCAT communication adopts a master-slave architecture, in which a master device is responsible for the management and control of the entire EtherCAT network, and a slave device is responsible for transmitting data on the data ring network. Among them, the master device can be a computer, industrial computer, PLC, etc., which is connected to the EtherCAT network through an EtherCAT interface. The master device sends and receives data frames and processes data from slave devices. The slave device can be a sensor, actuator, driver, etc. Each slave device has a unique device address and exchanges data with the master device in real time through EtherCAT communication.

[0056] EtherCAT usually has the feature of "scan and use", scan the network, start the system, and all components are running. In most cases, no parameters need to be set. The communication problem of the EtherCAT network is typically caused by the following reasons: the machine stops working, or the data value received by the control project (control program) is obviously inconsistent with the measured value.

[0057] The error types in the EtherCAT network include:

[0058] 1. Hardware error

[0059] (1) The data frame does not reach all slave devices or does not return to the master device due to unexpected change of physical media interruption or network topology (e.g. cable damage, loose interface, slave device restart during operation, etc.).

[0060] (2) The data frame reaches all slave devices, but the correct bit sequence is destroyed (e.g. EMC interference, wrong device, etc.).

[0061] 2. Software error

[0062] (1) In the initialization phase, the parameters sent by the master device are incorrect or do not conform to the expected slave type or topology (e.g. process data length / configuration, unsupported cycle time, etc.).

[0063] (2) The slave device in normal operation detects an error during operation (e.g. synchronization frame loss, watchdog timeout, etc.).

[0064] In the related art, the Working Counter (WKC) is the only diagnostic information periodically returned to the master station together with the process data. The process data can be understood as the data returned by the slave device to the master device. Each data packet in an EtherCAT data frame has a 16-bit end, and the WKC is incremented by one for each slave device specified in the data packet sent by the master device to multiple slave devices. The principle of increment is as follows:

[0065] Read-only command (xRD): if the memory of the slave device is readable, then WKC+1.

[0066] Write-only command (xWR): if the memory of the slave device is writable, then WKC+1.

[0067] Read+Write command (xRW): if the memory of the slave device is readable WKC+1 and writable WKC+2, and if both reading and writing are successful, then WKC+3.

[0068] The master device judges whether there is an error in the EtherCAT network by checking the WKC value of the returned data packet (i.e. process data packet). If the current value of the WKC in the data packet returned to the master device is consistent with the expected value, then the WKC is valid, and the process data in the data packet can be forwarded to the control program (such as PLC, NC). If the current value of the WKC in the data packet returned to the master device is not consistent with the expected value, then the WKC is invalid, and the process data in the data packet is discarded.

[0069] In the process of determining whether there is an error in the EtherCAT network, the master station device can mark the WcState information of the slave station of each synchronization unit Sync Unit, and if the verification is successful (i.e., WKC is valid), WcState is 0, and if the verification fails (i.e., WKC is invalid), WcState is 1. Each synchronization unit Sync Unit shares the same WcState mark, and any unsuccessful read and write of the slave station device will cause the entire data message to be invalid. Unsuccessful read and write is caused by the slave station device failing to successfully add WKC, which may be due to the physical data frame not arriving, or because the slave station device is not in the operating point (OP) state and other possible reasons.

[0070] As can be seen, the WKC in EtherCAT currently only supports immediate detection of communication errors, and does not provide communication error analysis capabilities. Specifically, the EtherCAT master station device can only determine that a fault has occurred in the network, but cannot determine which EtherCAT slave station device has a problem. This makes it difficult to quickly analyze and identify network faults.

[0071] Based on this, the present application constructs a fault detection method for a slave station device, which can quickly identify the EtherCAT slave station device that has a fault in the EtherCAT network.

[0072] Before introducing the present application, first, the application scenario of the embodiments of the present application is described. The technical solutions of the embodiments of the present application can be applied to various communication systems, for example, a fifth generation (5th generation, 5G) communication system or a future new radio access technology (new radio access technology, NR) and the like.

[0073] Figure 1 The architecture schematic diagram of the fault detection system for the slave station device provided by the embodiments of the present application is shown in FIG. 1, which can include: Figure 1

[0074] ​1. User Equipment (UE): Also known as user equipment, terminal, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless communication equipment, user agent, or user device. UE can also be a cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, vehicle-mounted device, wearable device, terminal equipment in a 5G network, or terminal equipment in a future evolved public land mobile network (PLMN), etc. It can also be an end device, logical entity, smart device, such as a mobile phone, smart terminal, or other terminal equipment; or a server, gateway, base station, controller, or other communication equipment; or an Internet of Things (IoT) device, such as a sensor, electricity meter, water meter, etc. This application's embodiments do not limit this.

[0075] 2. Radio Access Network (AN): Provides network access functionality to authorized users in a specific area and can use transmission tunnels of different quality depending on the user's level and service requirements. Access networks can employ different access technologies. Currently, there are two types of radio access technologies: 3rd Generation Partnership Project (3GPP) access technologies (such as those used in 3G, 4G, or 5G systems) and non-3GPP access technologies. 3GPP access technologies refer to access technologies that conform to 3GPP standards and specifications. Access networks using 3GPP access technologies are called Radio Access Networks (RANs). In 5G systems, access network equipment is called next-generation NodeBase stations (gNBs). Non-3GPP access technologies refer to access technologies that do not conform to 3GPP standards and specifications, such as air interface technologies represented by access points (APs) in Wi-Fi.

[0076] An access network that implements access network functions based on wireless communication technology can be referred to as a radio access network (RAN), where NG-RAN represents a 5G access network. A radio access network can manage radio resources to provide access services for terminals, and further complete the forwarding of control signals and user data between terminals and a core network.

[0077] An access network device can include a device in an access network that communicates with wireless terminals over one or more sectors on an air interface. An access network system can be used to convert received air frames to Internet Protocol (IP) packets, as a router between wireless terminals and the rest of the access network, which can include an IP network. A wireless access network system can also coordinate management of properties of the air interface. It should be understood that an access network device includes, but is not limited to, an evolved NodeB (eNB), a radio network controller (RNC), a Node B (NB), a base station controller (BSC), a base transceiver station (BTS), a home base station (e.g., a Home eNodeB, or Home NodeB, HNB), a baseband unit (BBU), an access point (AP) in a wireless fidelity (WIFI) system, a wireless relay node, a wireless backhaul node, a transmission and reception point (TRP or TP), etc., and can also be a gNB or a transmission point (TRP or TP) in a 5G, e.g., NR, system, one or a group of (including multiple antenna panels) antenna panels of a base station in a 5G system, or a network node constituting a gNB or a transmission point, such as a baseband unit (BBU) or a distributed unit (DU), etc.

[0078] In some deployments, a gNB can include a centralized unit (CU) and a DU. A gNB can also include a radio unit (RU). The CU implements part of the functionality of the gNB and the DU implements part of the functionality of the gNB, e.g., the CU implements the radio resource control (RRC), packet data convergence protocol (PDCP) layer functionality, and the DU implements the radio link control (RLC), media access control (MAC), and physical (PHY) layer functionality. Since the information at the RRC layer eventually becomes, or evolves from, information at the PHY layer, high layer signaling, such as RRC layer signaling, can also be considered as being transmitted by the DU, or by the DU + CU, under this architecture. It can be understood that an access network device can be a CU node, or a DU node, or a device including a CU node and a DU node. In addition, the CU can be divided into an access network device in a radio access network (RAN), or the CU can be divided into an access network device in a core network (CN), which is not limited here.

[0079] 3. Access and Mobility Management Function (AMF) network element, which is the termination point of RAN signaling interface (N2) and the termination point of MM message interface (N1) of non-access stratum (NAS) signaling. Main functions include: encryption and integrity protection of NAS message, responsible for registration, access, mobility management, authentication, short message, etc.

[0080] 4. Session Management Function (SMF) network element, the termination point for SM messages of NAS messages, main functions include: session establishment, modification, release, UE Internet Protocol Address (IP) allocation management, Dynamic Host Configuration Protocol (DHCP) function, Address Resolution Protocol (ARP) proxy or Internet Protocol Version 6 (IPv6) neighbor request proxy in the scenario of Ethernet Protocol Data Unit (PDU), selection and control of User Port Function (UPF) for a session, collection of charging data and support of charging interface, decision of session and service continuity mode (SSC) of a session, downlink data indication.

[0081] 5. User Plane Function (UPF) network element, main functions include: data packet routing and forwarding, quality of service (QoS) flow mapping, external PDU and data network interconnection session point, packet routing and forwarding, for example, support of uplink classifier to route traffic flows to instances of data network, support of branching point to support multi-host PDU session, data packet inspection, for example, application flow detection based on service data flow template and optional PFD received from SMF, user plane part policy rule implementation, for example, gating, redirection, traffic steering, lawful interception (UP collection), traffic usage reporting, QoS handling of user plane, for example, upload (UL) / download (DL) rate enforcement, reflective QoS marking in DL), uplink traffic verification (for example, service data flow (SDF) to QoS flow mapping), transport level packet marking in uplink and downlink, downlink packet buffering and downlink data notification triggering, sending and forwarding of one or more “end markers” to the source NG-RAN node.

[0082] 6. Policy Control Function (PCF) network element, supporting unified policy framework and managing network behavior, providing policy rules to network entities, accessing subscription information of Universal Data Repository (UDR), PCF can only access UDR of the same Public Land Mobile Network (PLMN), and can also be used for packet routing and forwarding, or quality of service (QoS) processing of user plane data, etc.

[0083] 7. Network Exposure Function (NEF) network element, main functions including: 3GPP network elements present their capabilities to other network elements through NEF, NEF stores relevant information into UDR and can also obtain relevant information from UDR, wherein NEF can only access UDR of the same PLMN, NEF provides corresponding security guarantee to ensure the security of external applications to 3GPP network, conversion of 3GPP internal and external related information, such as conversion of AF-Service-Identifier and Data Network Name (DNN) in 5G core network, S-NSSAI, etc., especially network and user sensitive information must be hidden from external network elements, NEF can obtain relevant information of other network elements by accessing UDR, and NEF can only access UDR of the same PLMN.

[0084] 8. Network function (NF) repository function (NRF) network element, main functions including: supporting service discovery function, that is, receiving service discovery request (NF-Discovery-Request) sent by network element, and then providing discovered network element information to requester, maintaining characteristics of available network element instances and their supported service capabilities, wherein the characteristic parameters of a network element mainly include: network element instance identity document (ID), network element type, PLMN, related ID of network slice, such as Single Network Slice Selection Assistance Information (S-NSSAI), Network Slice Instance IDentifier (NSIID), IP or domain name of network element, capability information of network element, and supported service capability name, etc.

[0085] 9. Unified Data Manager (UDM) network element, main functions include: generating 3GPP authentication credentials / authentication parameters, storing and managing permanent user IDs of 5G system, such as Subscription Permanent Identifier (SUPI), subscription information management, Mobile originate-Short Messaging Service (MT-SMS) delivery, SMS management, service network element registration management of users, such as AMF, SMF, etc. currently providing services for terminals.

[0086] 10. Authentication Server Function (AUSF) network element, supporting authentication of 3GPP access and authentication of trusted non-3GPP (untrusted non-3GPP) access.

[0087] 11. Application function (AF) network element, used for data routing of application influence, access network exposure function network element, or interacting with a policy framework for policy control, etc.

[0088] 12. The Network Slice Selection Function (NSSF) network element, used for managing network slice related information.

[0089] It should be noted that the N1 interface is a reference point between the UE and the AMF network element; the N2 interface is a reference point between the NG-RAN and the AMF network element, used for sending NAS messages, etc.; the N3 interface is a reference point between the NG-RAN and the UPF entity, used for transmitting user plane data, etc.; the N4 interface is a reference point between the SMF network element and the UPF network element, used for transmitting information such as tunnel identification information of N3 connection, data buffering indication information, and downlink data notification message, etc.

[0090] The Nnef interface is a service access interface provided by the AMF network element to the outside; the Nnrf interface is a service access interface provided by the NRF network element to the outside; the Npef interface is a service access interface provided by the PCF network element to the outside; the Nudm interface is a service access interface provided by the UDM network element to the outside; the Naf interface is a service access interface provided by the AF network element to the outside; the Nausf interface is a service access interface provided by the AUSF network element to the outside; the Namf interface is a service access interface provided by the AMF network element to the outside; the Nsmf interface is a service access interface provided by the SMF network element to the outside; and the Nnssf interface is a service access interface provided by the NSSF network element to the outside.

[0091] It should be understood that the above-mentioned network architecture applied to the embodiments of the present application is only a network architecture described from the perspective of the traditional point-to-point architecture and the service-oriented architecture, and the network architecture applicable to the embodiments of the present application is not limited thereto. Any network architecture capable of realizing the functions of the above-mentioned network elements is applicable to the embodiments of the present application. It should be understood that the above-mentioned network elements can communicate with each other through a pre-set interface, which will not be described here.

[0092] It should also be understood that the network elements shown in the core network in the above-mentioned embodiments can be combined into network slices as needed. These core network network elements can be independent devices or can be integrated into the same device to realize different functions, which are not limited by the present application. Figure 1

[0093] It should be understood that the above-mentioned names are only used to distinguish different functions and do not represent that these network elements are independent physical devices. The specific form of the above-mentioned network elements is not limited by the present application, for example, they can be integrated into the same physical device or can be different physical devices. In addition, the above-mentioned names are only used to distinguish different functions and should not constitute any limitation on the present application. The present application does not exclude the possibility of using other names in 5G networks and future other networks. For example, in a 6G network, part or all of the above-mentioned network elements can use the terms in 5G or other names. A unified description is made here and will not be described below.

[0094] It should also be understood that the interface names between the network elements in the above-mentioned embodiments are only examples, and the names of the interfaces in the specific implementation can be other names, which are not limited by the present application. In addition, the names of the messages (or signaling) transmitted between the above-mentioned network elements are also only examples, and the functions of the messages themselves are not limited. Figure 1

[0095] In addition, the system architecture further includes a slave device (i.e. an EtherCAT slave device), a master device (i.e. an EtherCAT master device), and a gateway management server. The slave device accesses the 5G network through a terminal device, the master device accesses the 5G network through a UPF network element, the terminal device and the UPF network element establish an Ethernet type PDU session, the UPF network element tracks the interactive messages between the master device and the slave device, identifies the connection relationship between the slave device and the terminal device, and records the count value (WKC) in the interactive messages, the network management server reads the count value in the interactive messages from the UPF network element, and judges whether the slave device has a fault according to a pre-set operation process.

[0096] The slave device fault detection method provided by the present application will be described below in combination with several specific embodiments.

[0097] ​​Figure 2 Flowchart of the fault detection method of the slave device provided by the embodiment of the present application Figure One As shown in the method can include: Figure 2

[0098] S101, the UPF network element receives the first data frame sent by the master device.

[0099] The first data frame includes: the first address value of each slave device, the preset design value and the command information.

[0100] Wherein, the first data frame can be a downlink data frame, the UPF network element extracts the EtherCAT sub-message from the first data frame, and reads the first address value, the preset design value and the command information from the EtherCAT sub-message. Wherein, the first address value is the address value of each slave device in the EtherCAT sub-message of the first data frame, the preset design value can be the default count value (i.e. WKC), and the specific value of the preset design value is not particularly limited in this embodiment.

[0101] The command information is used to indicate the command issued by the master device to each slave device, and the command information can be in the form of command code. The command can be, for example, a data read command (Read-only command), a data write command (Write-only command), or a data read-write command (Read+Write command). The read command is used to read the specified data from the memory of the slave device, the data write command is used to write the specified data into the memory of the slave device, and the data read-write command is used to read a specified data from the memory of the slave device and write another specified data into the memory of the slave device. For different slave devices, the command information can be different or the same, which is not particularly limited in this embodiment.

[0102] S102, the UPF network element determines the first addressing type of each slave device according to the command information in the first data frame, and generates the first record information of each slave device according to the first address value, the preset design value and the first addressing type.

[0103] Wherein, the addressing type is used to indicate the addressing type corresponding to the address value, which is divided into node address and logical address. The node address is the address allocated to the slave device as a node in advance, and the logical address is the address of the preset register in the slave device.

[0104] ​The UPF network element can query a mapping relationship between the command information and the addressing type according to the command information in the first data frame, determine a first addressing address of each slave device, wherein the first addressing type is an address type of the slave device determined according to the command information in the first record information, and generate the first record information of each slave device according to the first address value, the preset design value and the first addressing type, the first record information including the first address value, the preset design value and the first addressing type, and the specific form of the first record information can be <first addressing type, first address value, preset design value>.

[0105] In S103, the UPF network element sends the first data frame to each slave device, so that each slave device executes a command corresponding to the command information and updates the preset design value.

[0106] The UPF network element sends the first data frame to each slave device, each slave device acquires command information corresponding to its own address information from the first data frame according to its own address information, executes a command corresponding to the command information, and updates the preset design value according to the command type of the command, wherein the updated count value can be different for different command types, for example, for a data read command, the preset design value is incremented by one, for a data write command, the preset design value is incremented by one, for a data read-write command, if the memory of the slave device is readable, the preset design value is incremented by one, if the memory of the slave device is writable, the preset design value is incremented by two, and if both reading and writing are successful, the preset design value is incremented by three.

[0107] In S104, the UPF network element receives a second data frame returned by each slave device after executing the command.

[0108] Each slave device can return a second data frame to the UPF network element after executing the command, the second data frame including a second address value of each slave device, an updated count value and command information. One slave device can correspond to one second data frame.

[0109] The second data frame can be an uplink data frame, and the UPF network element extracts an EtherCAT sub-packet from the second data frame after receiving the second data frame of each slave device, and reads the second address value, the updated count value and the command information of each slave device from the EtherCAT sub-packet. The second address value is the address value of each slave device in the EtherCAT sub-packet of the second data frame.

[0110] It is worth noting that when reading data from the memory of the slave device, the read data can also be encapsulated in the second data frame, and the UPF network element forwards the read data in the second data frame to the master device, and when writing data to the memory of the slave device, the indication information of the successful writing can also be encapsulated in the second data frame, and the UPF network element forwards the indication information of the successful writing to the master device.

[0111] The UPF network element determines the second addressing type of each slave device according to the command information in the second data frame, and generates the second record information of each slave device according to the second address value, the updated count value and the second addressing type.

[0112] The UPF network element queries the mapping relationship between the command information and the addressing type according to the command information in the second data frame, and determines the second addressing address of each slave device, wherein the second addressing address is the address type of the slave device determined according to the command information in the second record information, and the second record information of each slave device is generated according to the second address value, the updated count value and the second addressing type, the second record information includes the second address value, the updated count value and the second addressing type, and the specific form of the second record information can be <second addressing type, second address value, updated count value>.

[0113] The UPF network element sends the first record information and the second record information to the network management server.

[0114] The UPF network element sends the first record information and the second record information to the network management server, and the network management server can receive the first record information and the second record information sent by the UPF network element, the first record information includes the first address value, the preset count value and the first addressing type of each slave device, and the second record information includes the second address value, the updated count value and the second addressing type of each slave device.

[0115] If the first addressing type and the second addressing type are consistent, and the first address value and the second address value are consistent, the network management server performs fault detection on each slave device according to the preset count value and the updated count value.

[0116] If the first addressing type and the second addressing type are consistent, and the first address value and the second address value are consistent, it means that the first record information and the second record information received by the network management server are for the same slave device, so the count difference value can be calculated according to the preset count value in the first record information and the updated count value in the second record information, and the slave device can be fault detected according to the count difference value.

[0117] If the count difference value is not equal to the increase value corresponding to the command type, it means that the slave device does not update the preset count value, so the slave device can be identified as faulty, and an alarm can be sent to the network administrator for troubleshooting, if the count difference value is equal to the increase value corresponding to the command type, it means that the slave device updates the preset count value, so it is determined that the slave device has no fault, wherein the increase value corresponding to the command type can be one, two or three.

[0118] In the embodiment, the slave device in the EtherCAT network can be detected for fault without modifying the existing slave device and master device, so as to identify the slave device with fault in the EtherCAT network.

[0119] Figure 3 Flowchart of the fault detection method of the slave device provided in the embodiment Figure Two As shown in the optional embodiment, the step S102 comprises: Figure 3

[0120] S201, generating the first record information according to the first address value, the preset value, the first addressing type and the first data direction corresponding to the first data frame.

[0121] The first data direction is the data direction from the master device to the UPF network element, i.e. the downlink direction, and the first record information comprises the first address value, the preset value, the first addressing type and the first data direction, and the specific form of the first record information can be <downlink, first addressing type, first address value, preset value>.

[0122] The step S105 comprises:

[0123] S202, generating the second record information according to the second address value, the updated count value, the second addressing type and the second data direction corresponding to the second data frame.

[0124] The second data direction is the data direction from the slave device to the UPF network element, i.e. the uplink direction, and the first record information comprises the second address value, the preset value, the second addressing type and the second data direction, and the specific form of the second record information can be <uplink, second addressing type, second address value, updated count value>.

[0125] Correspondingly, the step S107 comprises:

[0126] S203, the network service manager obtains the first data direction corresponding to the first data frame from the first record information and the second data direction corresponding to the second data frame from the second record information.

[0127] S204, if the first data direction and the second data direction match, the network service manager detects the slave device for fault according to the preset value and the updated count value. ​

[0128] The network service manager obtains a first data direction corresponding to the first data frame from the first record information and a second data direction corresponding to the second data frame from the second record information, wherein the first data frame is a data frame sent by the master station device to the UPF network element, and the second data frame is a data frame sent by each slave station device to the UPF network element.

[0129] If the first data direction and the second data direction match, the first addressing type and the second addressing type are consistent, and the first address value and the second address value are consistent, then the fault detection of each slave station device is performed according to the pre-designed count value and the updated count value, wherein the first data direction and the second data direction match can be understood as the first data direction is uplink and the second data direction is downlink, and the direction matches.

[0130] That is, the network management server determines that the first record information and the second record information are uplink and downlink direction record information based on the first data direction and the second data direction, and determines that the first record information and the second record information are for the same slave station device based on the first address value and the second address value, and the first addressing type and the second addressing type, so that the count difference value can be calculated according to the pre-designed count value in the first record information and the updated count value in the second record information, and the slave station device can be fault detected according to the count difference value.

[0131] In this embodiment, when the slave station device is further fault detected based on the first data direction and the second data direction, the accuracy of fault detection is improved.

[0132] Figure 4 Flowchart of the fault detection method of the slave station device provided in the embodiments of the present application Figure Three As shown in the optional embodiment, the method can further include: Figure 4

[0133] S301, after each slave station device establishes a PDU session with the UPF network element through a terminal device, the UPF network element obtains the session identifier of the PDU session.

[0134] After each slave station device accesses the 5G network through a terminal, the terminal device establishes an Ethernet type PDU session with the UPF network element, wherein one slave station device corresponds to one PDU session, and the UPF obtains the session identifier (i.e. PDU SessionID) of the PDU session.

[0135] The above step S102 generates the first record information of each slave station device according to the first address value, the pre-designed count value and the first addressing type, including:

[0136] ​S302, the UPF network element generates first record information according to the first address value, the preset value, the first addressing type and the session identifier.

[0137] The first record information includes the first address value, the preset value, the first addressing type and the session identifier, and the first record information can further include a first data direction, and a specific form of the first record can be <PDU session identifier, [<uplink, first addressing type, first address value, preset value]>.

[0138] The step S105 generates second record information of each slave device according to the second address value, the updated count value and the second addressing type, including:

[0139] S303, the UPF network element generates second record information according to the second address value, the updated count value, the second addressing type and the session identifier.

[0140] The second record information includes the second address value, the preset value, the second addressing type and the session identifier, and the second record information can further include a second data direction, and a specific form of the first record can be <PDU session identifier, [<uplink, second addressing type, second address value, updated count value]>.

[0141] Correspondingly, in the step S107, the network service manager performs fault detection on each slave device according to the preset value and the updated count value, including:

[0142] S304, the network management server obtains the session identifier of the PDU session from the first record information, and obtains the session identifier from the second record information.

[0143] After the network management server receives the first record information and the second record information, the session identifier is read, and the local data record is updated with the session identifier as an index. If the local does not exist uplink record information and downlink record information indexed by the session identifier, it is directly created in the local, otherwise, in the matching record, the data record indexed by <data direction, addressing type, address value> is updated.

[0144] S305, if the session identifier in the first record information and the session identifier in the second record information are consistent, the network management server performs fault detection on each slave device according to the preset value and the updated count value.

[0145] The network management server obtains the session identifier of the PDU session from the first record information, and obtains the session identifier from the second record information, the session identifier being the identifier of the PDU session established by each slave device through the terminal device and the UPF network element, when the session identifier in the first record information and the session identifier in the second record information are consistent, the first addressing type and the second addressing type are consistent, and the first address value and the second address value are consistent, then according to the pre-designed value and the updated count value, the fault detection is performed on each slave device.

[0146] That is, the network management server further determines that the first record information and the second record information are for the same slave device based on the session identifier in the first record information and the session identifier in the second record information, the first address value and the second address value, and the first addressing type and the second addressing type, so the count difference value can be calculated according to the pre-designed value in the first record information and the updated count value in the second record information, and the fault detection is performed on the slave device according to the count difference value.

[0147] Among them, the network management server compares the uplink record information and the downlink record information with the same <addressing type, address> index in the local data record, if the count difference value is equal to the increase value corresponding to the command type, such as one, it is determined that the corresponding slave device does not exist fault, if the count difference value is 0, it is identified that the slave device with <addressing type, address value> as the source address exists fault, and an alarm is given to the network administrator.

[0148] In an optional embodiment, when the session identifier in the first record information and the session identifier in the second record information are consistent, the first data direction and the second data direction match, the first addressing type and the second addressing type are consistent, and the first address value and the second address value are consistent, the network service manager performs fault detection on each slave device according to the pre-designed value and the updated count value. The accuracy of fault detection is improved.

[0149] In this embodiment, when the fault detection of the slave device is further based on the session identifier, the accuracy of the fault detection is improved.

[0150] In an optional embodiment, the method can further include:

[0151] If each slave device does not exist fault, the network management server updates the first record information and the second record information according to the connection relationship between each slave device and the terminal device.

[0152] The network management server detects faults of each slave station device according to a count difference between the preset count value and the updated count value, and if each slave station device does not have a fault, it indicates that each slave station and the terminal device are in a connection relationship, and then the first record information and the second record information are updated according to the connection relationship between each slave station device and the terminal device. The updated first record information and the updated second record information both include indication information of the connection relationship.

[0153] The indication information can be a downlink flag, and the initial value is 0, indicating no connection. The downlink flag is set to 1 to indicate that each slave station device and the terminal device are in a connection relationship.

[0154] It is worth noting that the specific form of the record information can be [<PDU session identifier, SUPI, [<data direction, addressing type, address, WKC, downlink flag>]>], where [·] is a data record list, <·> is a data record entry, the initial value of <addressing type, address> is <Null, Null>, the initial value of WKC is -1, the initial value of SUPI (Subscription Permanent Identifier) is -1, and the initial value of data direction is Null. SUPI (Subscription Permanent Identifier) is the device identifier of the terminal device.

[0155] The specific form of the first record information can be [<PDU session identifier, SUPI, [<downlink, first addressing type, first address value, preset count value, downlink flag>]>], and the specific form of the second record information can be [<PDU session identifier, SUPI, [<uplink, second addressing type, second address value, updated count value, downlink flag>]>].

[0156] In this embodiment, the first record information and the second record information are updated according to the connection relationship between each slave station device and the terminal device, so that the updated first record information and the updated second record information cover the connection relationship, which is convenient for users to monitor and know the connection status of each slave station device and the terminal device under the corresponding record information.

[0157] Figure 5 Flowchart of the fault detection method of the slave station device provided in the embodiments of the present application Figure Four As shown in Figure 5 In an optional embodiment, the method can further include:

[0158] S401, the UPF network element sends a session identifier to the network management server.

[0159] S402, the network management server sends a device identifier query request to the NEF network element, so that the NEF network element queries the device identifier of the terminal device through the SMF network element.

[0160] S403, the network management server receives the device identifier sent by the NEF network element.

[0161] The UPF network element sends a session identifier to the network management server, the network management server receives the session identifier sent by the UPF network element, and sends a device identifier query request to the NEF network element, the device identifier query request including: the session identifier, the NEF network element forwards the device identifier query request to the SMF network element, the SMF network element obtains the device identifier (such as SUPI) of the terminal device by querying the local record, and returns to the NEF network element, and the NEF network element forwards the device identifier to the network management server.

[0162] Wherein, the session identifier is the identifier of the PDU session established by each slave device through the terminal device and the UPF network element.

[0163] It is worth noting that the above steps S401-S404 can be executed before the above step S101, or after S101, which is not particularly limited in the present embodiment.

[0164] S404, the network management server updates the first record information and the second record information according to the device identifier.

[0165] After the network management server obtains the device identifier, it can be stored locally, and after receiving the first record information and the second record information sent by the UPF network element, the first record information and the second record information can be updated and stored according to the device identifier, and the updated first record information and the updated second record information include: the device identifier.

[0166] In the present embodiment, the connection relationship between the terminal device and the different slave devices is automatically identified without manual input, so that the updated first record information and the updated second record information correspond to the corresponding terminal device, which facilitates the user to monitor and know the terminal device under the corresponding record information.

[0167] On the basis of the above embodiment, the fault detection method of the slave device provided in the present application will be described in detail, which includes the following flow:

[0168] 1, after the network management server starts, the following record list is formed:

[0169] [PDU session identifier, SUPI, [<data direction, addressing type, address, WKC, downlink flag>]>].

[0170] Wherein, [·] is a data record list, and <·> is a data record entry. The PDU session identification is used to indicate the PDU session established by the UE and the local UPF, i.e. PDU Session ID. The addressing type is divided into node address and logical address, the address is an address value, the WKC is a Working Counter value, and the data direction is divided into uplink and downlink. The downlink flag indicates whether the EtherCAT slave device with <addressing type, address> as the source address is connected to the current terminal, if 1, it indicates that it is connected, if 0, it indicates that it is not connected, and the initial value of the flag is 0. The initial value of <addressing type, address> is <Null, Null>, the initial value of WKC is -1, the initial value of SUPI is -1, and the initial value of the data direction is Null.

[0171] 2. After the terminal establishes an Ether type PDU session with the UPF, the UPF informs the network management server of the PDU session identification.

[0172] 3. After receiving the PDU session identification from the UPF, the network management server updates the local record and informs the NEF network element, requiring to obtain the corresponding terminal identification, i.e. SUPI.

[0173] 4. The NEF network element forwards the query request from the network management server to the SMF network element.

[0174] 5. The SMF network element obtains the corresponding SUPI by querying the local record and returns it to the NEF network element.

[0175] 6. The NEF network element forwards the SUPI returned by the SMF network element to the network management server.

[0176] 7. After receiving the SUPI from the NEF, the network management server updates the local record.

[0177] 8. After receiving the downlink data frame from the EtherCAT master station, the UPF extracts the EtherCAT sub-packet therein and reads the command code, address value and WKC, and reports them to the network management server. The specific form is <PDU session identification, [<downlink, first addressing type, first address value, WKC]>.

[0178] 9. After receiving the uplink data frame from the EtherCAT slave station, the UPF extracts the EtherCAT sub-packet therein and reads the command code, sub-packet address and WKC, and reports them to the network management server. The specific form is <PDU session identification, [<uplink, second addressing type, second address value, WKC]>.

[0179] 10. The network management server receives the record information from the UPF network element, and updates the local data record with the PDU session identifier as the index.

[0180] 11. The network management server updates the local data record as follows: if there is no record indexed by the PDU session identifier in the local, the record is directly created in the local; otherwise, the data record indexed by the data direction, addressing type, and address is updated in the matching record.

[0181] 12. The network management server compares the uplink record information and the downlink record information with the same addressing type and address index. If the difference between the WKC in the uplink record information and the WKC in the downlink record information is 1, the network management server updates the downlink flag in the corresponding record (including the uplink record and the downlink record) to 1.

[0182] 13. In the data record updating process, the network management server monitors the uplink record information and the downlink record information with the same addressing type and address index and the downlink flag being 1. If the difference between the WKC in the uplink record information and the WKC in the downlink record information is 0, the network management server identifies that the EtherCAT slave station device with the addressing type and the address as the source address has a fault, and sends an alarm to the network administrator.

[0183] Figure 6 Structure of the slave station device fault detection apparatus provided by the embodiment of the application Figure One The apparatus can be integrated in the UPF network element.

[0184] As shown in Figure 6 The apparatus can include:

[0185] The receiving module 501 is configured to receive a first data frame sent by a master station device, and the first data frame includes a first address value of each slave station device, a preset count value, and command information.

[0186] The processing module 502 is configured to determine a first addressing type of each slave station device according to the command information in the first data frame, and generate first record information of each slave station device according to the first address value, the preset count value, and the first addressing type.

[0187] The sending module 503 is configured to send the first data frame to each slave station device, so that each slave station device executes a command corresponding to the command information and updates the preset count value.

[0188] The receiving module 501 is further configured to receive a second data frame returned by each slave station device after executing the command, and the second data frame includes a second address value of each slave station device, an updated count value, and command information.

[0189] The processing module 502 is further configured to determine a second addressing type of each slave device according to the command information in the second data frame, and generate second record information of each slave device according to the second address value, the updated count value and the second addressing type.

[0190] The sending module 503 is further configured to send the first record information and the second record information to the network management server, so that the network management server performs fault detection on each slave device according to the preset value and the updated count value when the first addressing type and the second addressing type are consistent, and the first address value and the second address value are consistent.

[0191] The description of the processing flow of each module in the device and the interaction flow between the modules can refer to the related description in the above method embodiments, and will not be described in detail here.

[0192] Figure 7 The structure diagram of the fault detection device of the slave device provided in the embodiment of the present application Figure Two The device can be integrated in the network management server.

[0193] As shown in Figure 7 , the device can include:

[0194] The receiving module 601 is configured to receive the first record information and the second record information sent by the UPF network element, the first record information including: the first address value of each slave device, the preset value and the first addressing type, and the second record information including: the second address value of each slave device, the updated count value and the second addressing type.

[0195] The detection module 602 is configured to perform fault detection on each slave device according to the preset value and the updated count value if the first addressing type and the second addressing type are consistent, and the first address value and the second address value are consistent.

[0196] The description of the processing flow of each module in the device and the interaction flow between the modules can refer to the related description in the above method embodiments, and will not be described in detail here.

[0197] Figure 8 The structure diagram of the electronic device provided in the embodiment of the present application, which can be integrated in the UPF network element or the network management server.

[0198] As shown in Figure 8As shown, the device can include a processor 701, a memory 702 and a bus 703, the memory 702 stores machine readable instructions executable by the processor 701, when the electronic device is running, the processor 701 communicates with the memory 702 through the bus 703, the processor 701 executes the machine readable instructions to perform the above method.

[0199] The embodiment of the present application further provides a computer readable storage medium, the computer readable storage medium stores a computer program, when the computer program is run by a processor, the processor executes the above method.

[0200] In the embodiment of the present application, when the computer program is run by the processor, the computer program can also execute other machine readable instructions to perform other methods as described in the embodiments. For specific method steps and principles, refer to the description of the embodiments, which will not be described in detail here.

[0201] In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method can be implemented by other means. The apparatus embodiment described above is only schematic, for example, the division of the units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units or components shown or discussed can be indirect coupling or communication connection through some communication interface, and can be electrical, mechanical or other forms.

[0202] The units described as separate components can or can not be physically separate, and the components shown as units can or can not be physical units, that is, they can be located in one place, or can be distributed on a plurality of network units. According to actual needs, part or all of the units can be selected to achieve the purpose of the embodiment.

[0203] In addition, each functional unit in the embodiments provided in the present application can be integrated in one processing unit, or each unit can exist physically, or two or more units can be integrated in one unit.

[0204] If the functions are implemented in the form of software function units and sold or used as independent products, they can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application essentially or the parts that contribute to the prior art or parts of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a number of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk or an optical disk, and various program code storage media.

[0205] It should be noted that similar reference numbers and letters represent similar items in the following drawings, so once an item is defined in one drawing, it does not need to be further defined and explained in subsequent drawings. In addition, the terms "first", "second", "third" and the like are only used to distinguish the description and cannot be understood as indicating or implying relative importance.

[0206] Finally, it should be noted that the above-described embodiments are only specific implementations of the present application, which are used to illustrate the technical solutions of the present application, but not to limit them. The protection scope of the present application is not limited thereto. Although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that any person skilled in the art can modify or easily think of changes to the technical solutions described in the foregoing embodiments within the technical scope disclosed by the present application, or make equivalent replacements to some of the technical features. These modifications, changes or replacements do not cause the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present application. They should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A failure detection method of a slave device, characterized by, The method applied to a UPF network element comprises: receiving a first data frame sent by a master station device, the first data frame comprising a first address value of each slave station device, a preset count value and command information; determining a first addressing type of each slave station device according to the command information in the first data frame, and generating first record information of each slave station device according to the first address value, the preset count value and the first addressing type; sending the first data frame to each slave station device to make each slave station device execute a command corresponding to the command information and update the preset count value; receiving a second data frame returned by each slave station device after executing the command, the second data frame comprising a second address value of each slave station device, an updated count value and the command information; determining a second addressing type of each slave station device according to the command information in the second data frame, and generating second record information of each slave station device according to the second address value, the updated count value and the second addressing type; sending the first record information and the second record information to a network management server to make the network management server perform fault detection on each slave station device according to the preset count value and the updated count value when the first addressing type and the second addressing type are consistent and the first address value and the second address value are consistent.

2. The method of claim 1, wherein, The first record information of each slave station device is generated according to the first address value, the preset count value and the first addressing type, comprising: generating the first record information according to the first address value, the preset count value, the first addressing type and a first data direction corresponding to the first data frame, the first data direction being a data direction from the master station device to the UPF network element; The second record information of each slave station device is generated according to the second address value, the updated count value and the second addressing type, comprising: generating the second record information according to the second address value, the updated count value, the second addressing type and a second data direction corresponding to the second data frame, the second data direction being a data direction from each slave station device to the UPF network element, and the network management server is further configured to perform fault detection on each slave station device according to the preset count value and the updated count value when the first data direction and the second data direction match.

3. The method of claim 1, wherein, The method further comprises: after each slave station device establishes a PDU session with the UPF network element through a terminal device, obtaining a session identifier of the PDU session; The first record information of each slave station device is generated according to the first address value, the preset count value and the first addressing type, comprising: generating the first record information according to the first address value, the preset count value, the first addressing type and the session identifier; The second record information of each slave station device is generated according to the second address value, the updated count value and the second addressing type, comprising: According to the second address value, the updated count value, the second addressing type and the session identifier, the second record information is generated, and the network management server is further configured to perform fault detection on the slave devices according to the preset count value and the updated count value when the session identifier in the first record information is consistent with the session identifier in the second record information.

4. The method of claim 3, wherein, The method further comprises: sending the session identifier to the network management server, so that the network management server acquires the device identifier of the terminal device according to the session identifier.

5. A failure detection method of a slave device, characterized by, The method applied to a network management server comprises: receiving first record information and second record information sent by a UPF network element, wherein the first record information comprises a first address value, a preset count value and a first addressing type of each slave device, and the second record information comprises a second address value, an updated count value and a second addressing type of each slave device; if the first addressing type and the second addressing type are consistent, and the first address value and the second address value are consistent, then performing fault detection on each slave device according to the preset count value and the updated count value.

6. The method of claim 5, wherein, The fault detection on each slave device according to the preset count value and the updated count value comprises: acquiring a first data direction corresponding to a first data frame from the first record information, and acquiring a second data direction corresponding to a second data frame from the second record information, wherein the first data frame is a data frame sent by a master device to the UPF network element, and the second data frame is a data frame sent by each slave device to the UPF network element; if the first data direction and the second data direction match, then performing fault detection on each slave device according to the preset count value and the updated count value.

7. The method of claim 6, wherein, The fault detection on each slave device according to the preset count value and the updated count value comprises: acquiring a session identifier of a PDU session from the first record information, and acquiring the session identifier from the second record information, wherein the session identifier is an identifier of a PDU session established by each slave device through a terminal device and the UPF network element; if the session identifier in the first record information is consistent with the session identifier in the second record information, then performing fault detection on each slave device according to the preset count value and the updated count value.

8. The method of claim 5, wherein, The method further comprises: receiving a session identifier sent by the UPF network element, wherein the session identifier is an identifier of a PDU session established by each slave device through a terminal device and the UPF network element; sending a device identifier query request to an NEF network element, wherein the device identifier query request comprises the session identifier, so that the NEF network element queries a device identifier of the terminal device through an SMF network element; receiving the device identifier sent by the NEF network element; updating the first record information and the second record information according to the device identifier.

9. The method of claim 6, wherein, The method further comprises: If the slave devices are not faulty, the first record information and the second record information are updated according to the connection relationship between the slave devices and the terminal device.

10. An electronic device, comprising: Comprise: A processor, a memory and a bus, the memory stores machine readable instructions executable by the processor, when the electronic device is running, the processor and the memory communicate through the bus, the processor executes the machine readable instructions to execute the method of any one of claims 1 to 9.

Images