Fault detection method of slave station equipment and electronic equipment

Abstract

The invention provides a fault detection method of slave station equipment and electronic equipment, and the method comprises the steps that a UPF network element receives a first data frame sent by master station equipment, determines a first addressing type of each slave station equipment according to command information in the first data frame, and determines a fault of each slave station equipment according to a first address value, a pre-designed numerical value and the first addressing type; generating first record information, sending a first data frame to each slave station device, receiving a returned second data frame, determining a second addressing type of each slave station device according to command information in the second data frame, generating second record information according to a second address value, the updated count value and the second addressing type, and sending the second record information to the slave station device. And sending the first record information and the second record information to a network management server, and when the first addressing type is consistent with the second addressing type and the first address value is consistent with the second address value, performing fault detection on each slave station device according to the pre-designed numerical value and the updated count value. And fault detection of slave station equipment is realized.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a fault detection method for a slave station device and an electronic device. Background Art

[0002] Ethernet control automation technology (EtherCAT) usually has the characteristics of "scan and use". Scan the network, start the system, and all components will be running. In most cases, no parameters need to be set.

[0003] In the related art, for the EtherCAT network, Working Counter (WKC) is the only diagnostic information that is periodically sent back to the master device together with the process data (ProcessData), wherein WKC increases each time it passes through a slave device specified in a data message, so based on WKC it can be determined whether the EtherCAT network is faulty.

[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 network fault analysis and identification difficult to implement quickly. Summary of the invention

[0005] In view of this, an embodiment of the present application provides a fault detection method and electronic device for a slave station device to implement fault detection for the slave station device.

[0006] In a first aspect, an embodiment of the present application provides a fault detection method for a slave device, which is applied to a UPF network element, and the method includes:

[0007] Receive a first data frame sent by a master station device, wherein the first data frame includes: a first address value, a pre-designed value, and command information of each slave station device;

[0008] Determine the 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 pre-designed value and the first addressing type;

[0009] Sending the first data frame to each of the slave station devices, so that each of the slave station devices executes the command corresponding to the command information and updates the pre-designed value;

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

[0011] Determine the second addressing type of each slave station device according to the command information in the second data frame, and generate second record information of each slave station device according to the second address value, the updated count value and the second addressing type;

[0012] The first record information and the second record information are sent to a network management server, so that the network management server performs fault detection on each slave station device according to the pre-designed value and the updated count value when the first addressing type is consistent with the second addressing type and the first address value is consistent with the second address value.

[0013] In an optional implementation manner, generating the first record information of each slave station device according to the first address value, the pre-designed value and the first addressing type includes:

[0014] Generate the first record information according to the first address value, the pre-designed value, the first addressing type, and the first data direction corresponding to the first data frame, where the first data direction is the data direction from the master station device to the UPF network element;

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

[0016] The second record information is generated 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, the second data direction being the data direction from each slave station device to the UPF network element, and the network management server is also used to perform fault detection on each slave station device according to the pre-designed value and the updated count value when the first data direction and the second data direction match.

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

[0018] After each slave station device establishes a PDU session with the UPF network element through the terminal device, obtaining a session identifier of the PDU session;

[0019] The step of generating the first record information of each slave station device according to the first address value, the pre-designed value and the first addressing type includes:

[0020] generating the first record information according to the first address value, the pre-designed value, the first addressing type, and the session identifier;

[0021] The step of generating the second record information of each slave station device according to the second address value, the updated count value and the second addressing type includes:

[0022] The second record information is generated according to the second address value, the updated count value, the second addressing type and the session identifier. The network management server is also used to perform fault detection on each slave station device according to the pre-designed 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 obtains the device identifier of the terminal device according to the session identifier.

[0025] In a third aspect, an embodiment of the present application further provides a fault detection method for a slave device, which is applied to a network management server, and the method includes:

[0026] Receive first record information and second record information sent by the UPF network element, wherein the first record information includes: a first address value, a pre-designed value, and a first addressing type of each slave station device, and the second record information includes: a second address value, an updated count value, and a second addressing type of each slave station device;

[0027] If the first addressing type is consistent with the second addressing type, and the first address value is consistent with the second address value, fault detection is performed on each slave station device according to the pre-designed value and the updated count value.

[0028] In an optional implementation, the performing fault detection on each slave device according to the pre-designed value and the updated count value includes:

[0029] Acquire a first data direction corresponding to a first data frame from the first record information, and acquire 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 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;

[0030] If the first data direction matches the second data direction, fault detection is performed on each slave station device according to the pre-designed value and the updated count value.

[0031] In an optional implementation, the performing fault detection on each slave device according to the pre-designed value and the updated count value includes:

[0032] Acquire a session identifier of the PDU session from the first record information, and acquire the session identifier from the second record information, where the session identifier is an identifier of the PDU session established between each slave station device and the UPF network element through the terminal device;

[0033] If the session identifier in the first record information is consistent with the session identifier in the second record information, fault detection is performed on each slave station device according to the pre-designed value and the updated count value.

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

[0035] Receive a session identifier sent by the UPF network element, where the session identifier is an identifier of a PDU session established between each slave device and the UPF network element through a terminal device;

[0036] Sending a device identification query request to the NEF network element, wherein the device identification query request includes: the session identification, so that the NEF network element queries the device identification of the terminal device through the SMF network element;

[0037] Receiving the device identification sent by the NEF network element;

[0038] The first record information and the second record information are updated according to the device identification.

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

[0040] If there is no fault in each of the slave station devices, the first record information and the second record information are updated according to the connection relationship between each of the slave station devices and the terminal device.

[0041] In a third aspect, an embodiment of the present application further provides an electronic device, comprising: a processor, a memory and a bus, wherein the memory stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor communicates with the memory through the bus, and the processor executes the machine-readable instructions to execute any one of the methods described in the first aspect.

[0042] The present application provides a fault detection method and electronic device for a slave station device, the method comprising: 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 pre-designed 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 the 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 when the first addressing type and the second addressing type are consistent, and the first address value and the second address value are consistent, performs fault detection on each slave station device according to the pre-designed value and the updated count value. Fault detection of the slave station device is realized. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0044] Figure 1 A schematic diagram of the architecture of a fault detection system for a slave device provided in an embodiment of the present application;

[0045] Figure 2 Schematic diagram of the process of the fault detection method of the slave station device provided in the embodiment of the present application Figure 1 ;

[0046] Figure 3 Schematic diagram of the process of the fault detection method of the slave station device provided in the embodiment of the present application Figure 2 ;

[0047] Figure 4 Schematic diagram of the process of the fault detection method of the slave station device provided in the embodiment of the present application Figure 3 ;

[0048] Figure 5 Schematic diagram of the process of the fault detection method of the slave station device provided in the embodiment of the present application Figure 4 ;

[0049] Figure 6 A schematic diagram of the structure of a fault detection device for a slave device provided in an embodiment of the present application Figure 1 ;

[0050] Figure 7 A schematic diagram of the structure of a fault detection device for a slave device provided in an embodiment of the present application Figure 2 ;

[0051] Figure 8 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0052] To make the purpose, technical scheme and advantages of the embodiments of the present application clearer, the technical scheme in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all of the embodiments. The components of the embodiments of the present application generally described and shown in the drawings here 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 application claimed for protection, but merely represents the 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 making creative work belong to the scope of protection of the present application.

[0053] First, the professional terms involved in this application are explained:

[0054] EtherCAT (Ethernet for Control Automation Technology) is a real-time Ethernet communication protocol used to achieve high-performance, real-time data transmission and control in industrial automation and control systems. It was 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, while the slave device is responsible for transmitting data on the data ring network. The master device can be a computer, industrial computer, PLC, etc. It is connected to the EtherCAT network through the EtherCAT interface. The master device sends and receives data frames and processes the data of the slave device. The slave device can be a sensor, actuator, drive, 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. Communication problems in EtherCAT networks are typically caused by the following reasons: the machine stops working, or the data values ​​received by the control project (control program) are obviously inconsistent with the measured values.

[0057] Error types in EtherCAT networks include:

[0058] 1. Hardware Error

[0059] (1) The physical medium is interrupted or the network topology changes unexpectedly, and the data frame does not reach all slave devices or return to the master device (for example, the cable is damaged, the interface is loose, the slave is restarted 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 Errors

[0062] (1) During 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) A slave device that was operating normally detected an error during operation (such as synchronization frame loss, watchdog timeout, etc.).

[0064] In the related art, Working Counter (WKC) is the only diagnostic information that is periodically sent back to the master together with process data. Process data can be understood as data returned from the slave device to the master device. Each data message in an EtherCAT data frame ends with a 16-bit. WKC will increase every time it passes through a slave device specified in a data message. The data message is a command message sent from the master device to multiple slave devices. The increment principle is as follows:

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

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

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

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

[0069] In the process of judging whether there is an error in the EtherCAT network, the master device can mark the WcState information of each slave of the Sync Unit. If the verification is successful (that is, WKC is valid), WcState is 0, and if the verification fails (that is, WKC is invalid), WcState is 1. Each Sync Unit shares the same WcState mark. Any unsuccessful reading and writing of any slave device will cause the entire data message to be invalid. The unsuccessful reading and writing is caused by the failure of the slave device to successfully increase the WKC, which may be because the data frame has not arrived physically, or because the slave device is not in the operating point (OP) state and other possible reasons.

[0070] It can be seen that WKC in EtherCAT currently only supports immediate detection of communication errors, but does not provide communication error analysis capabilities. Specifically, the EtherCAT master device can only provide WKC to determine if a fault has occurred in the network, but cannot determine which EtherCAT slave 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 slave devices, which can quickly identify EtherCAT slave devices that have faults in an EtherCAT network.

[0072] Before introducing the present application, the application scenario of the embodiment of the present application is first described. The technical solution of the embodiment of the present application can be applied to various communication systems, such as: the fifth generation (5th generation, 5G) communication system or the future new radio access technology (new radio access technology, NR), etc.

[0073] Figure 1 A schematic diagram of the architecture of a fault detection system for a slave device provided in an embodiment of the present application is shown in FIG. Figure 1 As shown, the system architecture may include:

[0074] 1. User equipment (UE): It can also be called user equipment, terminal, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless communication device, user agent or user device. UE can also be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a 5G network or a terminal device in a public land mobile network (PLMN) to be evolved in the future, etc. It can also be an end device, a logical entity, an intelligent device, such as a mobile phone, an intelligent terminal and other terminal devices, or a server, a gateway, a base station, a controller and other communication devices, or an Internet of Things device, such as a sensor, an electric meter, a water meter and other Internet of Things (IoT) devices. The embodiments of the present application are not limited to this.

[0075] 2. Access network (Radio access network, AN): Provides network access functions for authorized users in a specific area, and can use transmission tunnels of different qualities according to the user level, business requirements, etc. The access network can be an access network that uses different access technologies. There are currently two types of wireless access technologies: 3rd Generation Partnership Project (3GPP) access technology (such as the wireless access technology used in 3G, 4G or 5G systems) and non-3GPP access technology. 3GPP access technology refers to access technology that complies with 3GPP standards and specifications. The access network that uses 3GPP access technology is called a radio access network (Radio Access Network, RAN), where the access network equipment in the 5G system is called the next generation Node Base station (next generation Node Base station, gNB). Non-3GPP access technology refers to access technology that does not comply with 3GPP standards and specifications, for example, air interface technology represented by access points (APs) in wifi.

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

[0077] The access network equipment may include equipment in the access network that communicates with the wireless terminal over the air interface through one or more sectors. The access network system may be used to convert received air frames to and from Internet Protocol (IP) packets, acting as a router between the wireless terminal and the rest of the access network, which may include an IP network. The wireless access network system may also coordinate the management of attributes of the air interface. It should be understood that the access network equipment includes but is not limited to: evolved NodeB (eNB), Radio Network Controller (RNC), Node B (NB), Base Station Controller (BSC), Base Transceiver Station (BTS), home base station (for example, Home evolved NodeB, or HomeNodeB, HNB), baseband unit (BBU), access point (AP) in wireless fidelity (WIFI) system, wireless relay node, wireless backhaul node, transmission point (TRP or transmission point, TP), etc., and can also be a gNB in ​​5G, such as NR, system, or a transmission point (TRP or TP), one or a group of (including multiple antenna panels) antenna panels of a base station in a 5G system, or, it can also be 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, the gNB may include a centralized unit (CU) and a DU. The gNB may also include a radio unit (RU). The CU implements some functions of the gNB, and the DU implements some functions of the gNB, for example, the CU implements the functions of the radio resource control (RRC) and packet data convergence protocol (PDCP) layers, and the DU implements the functions of the radio link control (RLC), media access control (MAC) and physical (PHY) layers. Since the information of the RRC layer will eventually become the information of the PHY layer, or be converted from the information of the PHY layer, therefore, under this architecture, high-level signaling, such as RRC layer signaling, can also be considered to be sent by the DU, or by the DU+CU. It can be understood that the access network device can be a CU node, a DU node, or a device including a CU node and a DU node. In addition, the CU may be classified as an access network device in a radio access network (RAN), or the CU may be classified as an access network device in a core network (CN), and no limitation is made here.

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

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

[0081] 5. User Plane Function (UPF) network element, whose main functions include: packet routing and forwarding, quality of service (QoS) flow mapping, session point for interconnection between external PDU and data network, packet routing and forwarding, for example, supporting uplink classifier to route service flow to data network instance, supporting branch point to support multi-host PDU session, packet inspection, for example, application flow detection based on service data flow template and optional PFD received from SMF, user plane partial policy rule implementation, for example, gating, redirection, traffic steering, lawful interception (UP collection), traffic usage reporting, QoS processing in user plane, for example, upload (UL) / download (DL) rate implementation, 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 one or more "end markers" to the source NG-RAN node.

[0082] 6. Policy Control Function (PCF) network element supports a unified policy framework and manages network behavior, provides policy rules to network entities, and accesses subscription information of the Universal Data Repository (UDR). PCF can only access UDRs 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.

[0083] 7. Network Exposure Function (NEF) network element. Its main functions include: 3GPP network elements present their capabilities to other network elements through NEF; NEF stores relevant information in UDR and can also obtain relevant information from UDR. NEF can only access UDR of the same PLMN; NEF provides corresponding security guarantees to ensure the security of external applications to 3GPP network, conversion of relevant information within and outside 3GPP, such as conversion of AF-Service-Identifier and data network name (DNN) and S-NSSAI within 5G core network. In particular, network and user sensitive information must be hidden from external network elements; NEF can obtain relevant information of other network elements by accessing UDR. NEF can only access UDR of the same PLMN.

[0084] 8. Network function (NF) repository function (NRF) network element, whose main functions include: 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 the requester, maintaining the characteristics of available network element instances and the service capabilities they support. Among them, the characteristic parameters of a network element mainly include: network element instance identity document (Identity document, ID), network element type, PLMN, and related IDs of network slices, such as single network slice selection assistance information (Single Network Slice Selection Assistance Information, S-NSSAI), network slice instance identifier (Network Slice Instance IDentifier, NSIID), network element IP or domain name, network element capability information, supported service capability name, etc.

[0085] 9. Unified Data Manager (UDM) network element, whose main functions are: generating 3GPP authentication certificates / authentication parameters, storing and managing permanent user IDs of the 5G system, such as Subscription Permanent Identifier (SUPI), subscription information management, downlink short message service (Mobile originate-Short Messaging Service, MT-SMS) delivery, SMS management, and user service network element registration management, such as AMF and SMF that currently provide services to the terminal.

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

[0087] 11. Application function (AF) network element, which is used to perform data routing affected by applications, access network open function network elements, or interact with the policy framework for policy control.

[0088] 12. The Network Slice Selection Function (NSSF) network element is used to manage network slice related information.

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

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

[0091] It should be understood that the above-mentioned architecture applied to the embodiment of the present application is only an example of a network architecture described from the perspective of a traditional point-to-point architecture and a service-oriented architecture, and the network architecture applicable to the embodiment of the present application is not limited thereto, and any network architecture that can realize the functions of the above-mentioned network elements is applicable to the embodiment of the present application. It should be understood that the above-mentioned network elements can communicate with each other through a preset interface, which will not be repeated here.

[0092] It should also be understood that Figure 1 The network elements used to implement different functions in the core network shown in the figure can be combined into network slices as needed. These core network network elements can be independent devices or integrated into the same device to implement different functions, which is not limited in this application.

[0093] It should be understood that the above naming is only used to distinguish different functions, and does not mean that these network elements are independent physical devices. This application does not limit the specific form of the above network elements. For example, they can be integrated in the same physical device, or they can be different physical devices. In addition, the above naming is only for the convenience of distinguishing different functions, and should not constitute any limitation on this application. This application does not exclude the possibility of using other names in 5G 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 other names may be used. A unified explanation is given here, and no further details are given below.

[0094] It should also be understood that Figure 1 The interface name between the network elements is only an example. The interface name in the specific implementation may be other names, and this application does not specifically limit this. In addition, the name of the message (or signaling) transmitted between the above network elements is only an example and does not constitute any limitation on the function of the message itself.

[0095] In addition, the system architecture also includes: slave devices (i.e. EtherCAT slave devices), master devices (i.e. EtherCAT master devices), and gateway management servers, wherein the slave devices access the 5G network through the terminal devices, and the master devices access the 5G network through the UPF network elements. The terminal devices establish Ethernet-type PDU sessions with the UPF network elements. The UPF network elements track the interaction messages between the master devices and the slave devices, identify the connection relationship between the slave devices and the terminal devices, and record the count value (WKC) in the interaction messages. The network management server reads the count value in the interaction message from the UPF network element, and determines whether the slave device has a fault according to a pre-set operation process.

[0096] The fault detection method for the slave station device provided by the present application is described below in conjunction with several specific embodiments.

[0097] Figure 2 Schematic diagram of the process of the fault detection method of the slave station device provided in the embodiment of the present application Figure 1 ,like Figure 2 As shown, the method may include:

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

[0099] The first data frame includes: a first address value of each slave device, a pre-designed value, and command information.

[0100] The first data frame may be a downlink data frame, and the UPF network element extracts the EtherCAT sub-message from the first data frame, and reads the first address value, pre-designed value, and command information of each slave device from the EtherCAT sub-message. The first address value is the address value of each slave device in the EtherCAT sub-message of the first data frame, and the pre-designed value may be a default count value (i.e., WKC). This embodiment does not specifically limit the specific value of the pre-designed value.

[0101] The command information is used to indicate the command sent by the master device to each slave device. The command information may be in the form of a command code. The command may be, for example, a data read command (Read-only command), a data write command (Write-only command), or a data read and write command (Read+Write command). The read command is used to indicate reading specified data from the memory of the slave device, the data write command is used to write specified data into the memory of the slave device, and the data read and 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 may be different or the same, and this embodiment does not specifically limit this.

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

[0103] Among them, 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 pre-assigned to the slave device as a node, and the logical address is the address of the preset register in the slave device.

[0104] The UPF network element can query the mapping relationship between the command information and the addressing type according to the command information in the first data frame, and determine the first addressing address of each slave station device, wherein the first addressing type is the address type of the slave station device determined according to the command information in the first record information, and generate the first record information of each slave station device according to the first address value, the pre-designed value and the first addressing type, the first record information includes: the first address value, the pre-designed value and the first addressing type, and the specific form of the first record information can be <first addressing type, first address value, pre-designed value>.

[0105] S103. The UPF network element sends a first data frame to each slave station device, so that each slave station device executes the command corresponding to the command information and updates the pre-designed value.

[0106] The UPF network element sends a first data frame to each slave station device. Each slave station device obtains the command information corresponding to its own address information from the first data frame according to its own address information, executes the command corresponding to the command information, and updates the pre-designed value according to the command type of the command. The count values ​​after update may be different for different command types. For example, for a data read command, the pre-designed value is increased by one, and for a data write command, the pre-designed value is increased by one. For data read and write commands, if the memory of the slave station device is readable, the pre-designed value is increased by one; if the memory of the slave station device is writable, the pre-designed value is increased by two; if both reading and writing are successful, the pre-designed value is increased by three.

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

[0108] After executing the command, each slave device may return a second data frame to the UPF network element, wherein the second data frame includes: the second address value of each slave device, the updated count value and the command information. One slave device may correspond to one second data frame.

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

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

[0111] S105. The UPF network element determines the second addressing type of each slave station device according to the command information in the second data frame, and generates second record information of each slave station 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 station device, wherein the second addressing address is the address type of the slave station device determined according to the command information in the second record information, and generates the second record information of each slave station device 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] S106. 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. 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 pre-designed value and the first addressing type of each slave station device; the second record information includes: the second address value, the updated count value and the second addressing type of each slave station device.

[0115] S107: If the first addressing type is consistent with the second addressing type, and the first address value is consistent with the second address value, the network management server performs fault detection on each slave station device according to the pre-designed 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 station device. Therefore, the count difference can be calculated based on the pre-designed value in the first record information and the updated count value in the second record information, and fault detection can be performed on the slave station device based on the count difference.

[0117] If the count difference is not equal to the increase value corresponding to the command type, it means that the slave device has not updated the pre-designed value, and it can be identified that a fault has occurred in the slave device. An alarm can also be sent to the network administrator for troubleshooting. If the count difference is equal to the increase value corresponding to the command type, it means that the slave device has updated the pre-designed value, and it is determined that there is no fault in the slave device. The increase value corresponding to the command type can be, for example, plus one, plus two, or plus three.

[0118] In this embodiment, it is possible to perform fault detection on slave devices in the EtherCAT network without modifying existing slave devices and master devices, so as to identify slave devices with faults in the EtherCAT network.

[0119] Figure 3 Schematic diagram of the process of the fault detection method of the slave station device provided in the embodiment of the present application Figure 2 ,like Figure 3 As shown, in an optional implementation manner, the above step S102 generates first record information of each slave device according to the first address value, the pre-designed value and the first addressing type, including:

[0120] S201. Generate first record information according to a first address value, a pre-designed value, a first addressing type, and a first data direction corresponding to a first data frame.

[0121] The first data direction is the data direction from the main station device to the UPF network element, that is, the downlink direction. The first record information includes: a first address value, a pre-designed value, a first addressing type and a first data direction. The specific form of the first record information can be <downlink, first addressing type, first address value, pre-designed value>.

[0122] The above step S105, generating second record information of each slave device according to the second address value, the updated count value and the second addressing type, includes:

[0123] S202: Generate 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 each slave station device to the UPF network element, that is, the uplink direction. The first record information includes: a second address value, a pre-designed value, a second addressing type and a second data direction. The specific form of the second record information can be <uplink, second addressing type, second address value, updated count value>.

[0125] Accordingly, in the above step S107, the network service manager performs fault detection on each slave device according to the pre-designed value and the updated count value, including:

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

[0127] S204: If the first data direction matches the second data direction, the network service manager performs fault detection on each slave station device according to the pre-designed value and the updated count value.

[0128] The network service manager obtains the first data direction corresponding to the first data frame from the first record information, and obtains the 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 matches the second data direction, 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 each slave station device based on the pre-designed value and the updated count value, wherein the first data direction and the second data direction match, which can be understood as the first data direction is uplink and the second data direction is downlink, then the directions match.

[0130] That is to say, the network management server determines that the first record information and the second record information are record information in the uplink and downlink directions respectively 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. Therefore, the count difference can be calculated based on the pre-designed numerical value in the first record information and the updated count value in the second record information, and fault detection can be performed on the slave station device based on the count difference.

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

[0132] Figure 4 Schematic diagram of the process of the fault detection method of the slave station device provided in the embodiment of the present application Figure 3 ,like Figure 4 As shown, in an optional implementation, the method may further include:

[0133] S301. After each slave station device establishes a PDU session with the UPF network element through the 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 the terminal, the terminal device establishes an Ethernet type PDU session with the UPF network element, where one slave station device corresponds to one PDU session, and the UPF obtains the session identifier of the PDU session (ie, PDU SessionID).

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

[0136] S302. The UPF network element generates first record information according to the first address value, the pre-designed value, the first addressing type, and the session identifier.

[0137] The first record information includes: the first address value, the pre-designed value, the first addressing type, and the session identifier. The first record information may also include the first data direction. The specific form of the first record may be <PDU session identifier, [<uplink, first addressing type, first address value, pre-designed value>]>.

[0138] In the above step S105, according to the second address value, the updated count value, and the second addressing type, second record information of each slave device is generated, 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 pre-designed value, the second addressing type, and the session identifier. The second record information may also include the second data direction. The specific form of the first record may be <PDU session identifier, [<uplink, second addressing type, second address value, updated count value>]>.

[0141] Correspondingly, in the above step S107, the network service manager performs fault detection on each slave device according to the pre-designed 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 receiving the first record information and the second record information, the network management server reads the session identifier and updates the local data record with the session identifier as the index. If there is no uplink record information and downlink record information indexed by the session identifier locally, it directly creates them locally. Otherwise, in the matching record, it updates the data record indexed by <data direction, addressing type, address value>.

[0144] S305. If the session identifier in the first record information is the same as the session identifier in the second record information, the network management server performs fault detection on each slave device according to the pre-designed 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 is the identifier of the PDU session established between each slave station device and the UPF network element through the terminal device. When the session identifier in the first record information is consistent with the session identifier in the second record information, the first addressing type is consistent with the second addressing type, and the first address value and the second address value are consistent, fault detection is performed on each slave station device based on the pre-designed numerical value and the updated count value.

[0146] That is to say, the network management server further determines that the first record information and the second record information are for the same slave station 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. Therefore, the count difference can be calculated according to the pre-designed numerical value in the first record information and the updated count value in the second record information, and fault detection can be performed on the slave station device based on the count difference.

[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 is equal to the increase value corresponding to the command type, such as one, it is determined that the corresponding slave station device has no fault. If the count difference is 0, it is identified that the slave station device with <addressing type, address value> as the source address has a fault, and an alarm is sent to the network administrator.

[0148] In an optional implementation, when the session identifier in the first record information is consistent with the session identifier in the second record information, 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 station device according to the pre-designed value and the updated count value, thereby improving the accuracy of fault detection.

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

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

[0151] If there is no fault in each slave station device, the network management server updates the first record information and the second record information according to the connection relationship between each slave station device and the terminal device.

[0152] The network management server performs fault detection on each slave device according to the count difference between the pre-designed value and the updated count value. If there is no fault in each slave device, it indicates that each slave and the terminal device are in a connected relationship. Then, according to the connection relationship between each slave device and the terminal device, the first record information and the second record information are updated. The updated first record information and the updated second record information both include the indication information of this connection relationship.

[0153] Among them, the indication information can be a下联标志 (downlink flag). The initial value of 0 indicates not connected. The downlink flag is set to 1 to indicate that each slave device and the terminal device are in a connected relationship.

[0154] It should be noted 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 values of <addressing type, address> are <Null, Null>, the initial value of WKC is -1, the initial value of SUPI is -1, the initial value of the data direction is Null, and 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, pre-designed 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, according to the connection relationship between each slave device and the terminal device, the first record information and the second record information are updated, so that the updated first record information and the updated second record information cover this connection relationship, which is convenient for users to monitor and know the connection status of each slave device and the terminal device under the corresponding record information.

[0157] Figure 5 Schematic flow of the fault detection method for the slave device provided by the embodiment of the present application Figure 4 , such as Figure 5 shown. In an alternative embodiment, the method may 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 includes: 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 it to the NEF network element. 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 should be noted that the above steps S401 - S404 can be executed before the above step S101 or after S101. This embodiment does not make special limitations on this.

[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. After receiving the first record information and the second record information sent by the UPF network element, it can update and store the first record information and the second record information according to the device identifier. The updated first record information and the updated second record information include: the device identifier.

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

[0167] On the basis of the above embodiment, the following details the fault detection method for the slave device provided by this application. This method includes the following processes:

[0168] 1. After the network management server is started, the following record list is formed:

[0169] [<PDU session identifier, SUPI, [<data direction, addressing type, address, WKC,下联标志>]]].

[0170] Among them, [·] is the data record list, and <·> is the data record entry. The PDU session identifier is used to identify the PDU session established between the UE and the local UPF, that is, the PDU Session ID. The addressing type is divided into node address and logical address, the address is the address value, the WKC is the Working Counter value, and the data direction is divided into uplink and downlink. The下联 flag indicates whether the EtherCAT slave device with <addressing type, address> as the source address is connected to the current terminal. If it is 1, it means connected; if it is 0, it means not connected. The initial value of this 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 Ethernet-type PDU session with the UPF, the UPF notifies the network management server of the PDU session identifier.

[0172] 3. After the network management server receives the PDU session identifier from the UPF, it updates the local record and notifies the NEF network element, requesting to obtain the corresponding terminal identifier, that is, the 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 the network management server receives the SUPI from the NEF, it updates the local record.

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

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

[0179] 10. After receiving the record information from the UPF network element, the network management server uses the PDU session identifier as an index to update the local data record.

[0180] 11. The method for the network management server to update the local data record is as follows: if there is no record indexed by the PDU session identifier locally, it is directly created locally. Otherwise, in the matching record, the data record indexed by <data direction, addressing type, address> is updated.

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

[0182] 13. During the data record update process, the network management server monitors the upstream record information and downstream record information with the same <addressing type, address> index and the downstream link flag as 1. If the difference between the WKC in the upstream record information and the WKC in the downstream record information is 0, the network management server recognizes that the EtherCAT slave device with <addressing type, address> as the source address has a fault and alerts the network administrator.

[0183] Figure 6 A schematic diagram of the structure of a fault detection device for a slave device provided in an embodiment of the present application Figure 1 , the device can be integrated in the UPF network element.

[0184] like Figure 6 As shown, the device may include:

[0185] The receiving module 501 is used to receive a first data frame sent by a master station device, wherein the first data frame includes: a first address value, a pre-designed value and command information of each slave station device;

[0186] The processing module 502 is used to determine the 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 pre-designed value and the first addressing type;

[0187] The sending module 503 is used to send a first data frame to each slave station device, so that each slave station device executes a command corresponding to the command information and updates a pre-designed value;

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

[0189] The processing module 502 is further used to determine the 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 also used to send the first record information and the second record information to the network management server, so that 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 network management server performs fault detection on each slave station device according to the pre-designed value and the updated count value.

[0191] For descriptions of the processing flow of each module in the device and the interaction flow between each module, reference may be made to the relevant descriptions in the above method embodiment, which will not be described in detail here.

[0192] Figure 7 A schematic diagram of the structure of a fault detection device for a slave device provided in an embodiment of the present application Figure 2 , the device can be integrated into a network management server.

[0193] like Figure 7 As shown, the device may include:

[0194] The receiving module 601 is used to receive the first record information and the second record information sent by the UPF network element, wherein the first record information includes: the first address value, the pre-designed value and the first addressing type of each slave station device, and the second record information includes: the second address value, the updated count value and the second addressing type of each slave station device;

[0195] The detection module 602 is used to perform fault detection on each slave device according to a pre-designed value and an updated count value if the first addressing type is consistent with the second addressing type and the first address value is consistent with the second address value.

[0196] For descriptions of the processing flow of each module in the device and the interaction flow between each module, reference may be made to the relevant descriptions in the above method embodiment, which will not be described in detail here.

[0197] Figure 8 This is a structural diagram of an electronic device provided in an embodiment of the present application, which can be integrated in a UPF network element or a network management server.

[0198] like Figure 8As shown, the device may 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, and the processor 701 executes the machine-readable instructions to perform the above method.

[0199] An embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the processor executes the above method.

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

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

[0202] 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 achieve the purpose of the solution of this embodiment.

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

[0204] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: 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.

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

[0206] Finally, it should be noted that the above-described embodiments are only specific implementation methods of the present application, which are used to illustrate the technical solutions of the present application, rather than to limit them. The protection scope of the present application is not limited thereto. Although the present application is described in detail with reference to the above-mentioned embodiments, ordinary technicians in the field should understand that any technician familiar with the technical field can still modify the technical solutions recorded in the above-mentioned embodiments within the technical scope disclosed in the present application, or can easily think of changes, or make equivalent replacements for some of the technical features therein; and these modifications, changes or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application. They should all be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope of the claims.

Claims

1. A fault detection method for a slave device, characterized in that: Applied to a UPF network element, the method comprises: Receive a first data frame sent by a master station device, wherein the first data frame includes: a first address value, a pre-designed value, and command information of each slave station device; Determine the 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 pre-designed value and the first addressing type; Sending the first data frame to each of the slave station devices, so that each of the slave station devices executes the command corresponding to the command information and updates the pre-designed value; receiving a second data frame returned by each slave station device after executing the command, wherein the second data frame includes: a second address value of each slave station device, an updated count value, and the command information; Determine the second addressing type of each slave station device according to the command information in the second data frame, and generate second record information of each slave station device according to the second address value, the updated count value and the second addressing type; The first record information and the second record information are sent to a network management server, so that the network management server performs fault detection on each slave station device according to the pre-designed value and the updated count value when the first addressing type is consistent with the second addressing type and the first address value is consistent with the second address value.

2. The method according to claim 1, characterized in that The step of generating the first record information of each slave station device according to the first address value, the pre-designed value and the first addressing type includes: Generate the first record information according to the first address value, the pre-designed value, the first addressing type, and the first data direction corresponding to the first data frame, where the first data direction is the data direction from the master station device to the UPF network element; The step of generating the second record information of each slave station device according to the second address value, the updated count value and the second addressing type includes: The second record information is generated 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, the second data direction being the data direction from each slave station device to the UPF network element, and the network management server is also used to perform fault detection on each slave station device according to the pre-designed value and the updated count value when the first data direction and the second data direction match.

3. The method according to claim 1, characterized in that The method further comprises: After each slave station device establishes a PDU session with the UPF network element through the terminal device, obtaining a session identifier of the PDU session; The step of generating the first record information of each slave station device according to the first address value, the pre-designed value and the first addressing type includes: generating the first record information according to the first address value, the pre-designed value, the first addressing type, and the session identifier; The step of generating the second record information of each slave station device according to the second address value, the updated count value and the second addressing type includes: The second record information is generated according to the second address value, the updated count value, the second addressing type and the session identifier. The network management server is also used to perform fault detection on each slave station device according to the pre-designed 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 according to claim 3, characterized in that The method further comprises: The session identifier is sent to the network management server, so that the network management server obtains the device identifier of the terminal device according to the session identifier.

5. A fault detection method for a slave device, characterized in that: Applied to a network management server, the method comprises: Receive first record information and second record information sent by the UPF network element, wherein the first record information includes: a first address value, a pre-designed value, and a first addressing type of each slave station device, and the second record information includes: a second address value, an updated count value, and a second addressing type of each slave station device; If the first addressing type is consistent with the second addressing type, and the first address value is consistent with the second address value, fault detection is performed on each slave station device according to the pre-designed value and the updated count value.

6. The method according to claim 5, characterized in that The performing fault detection on each slave station device according to the pre-designed value and the updated count value comprises: Acquire a first data direction corresponding to a first data frame from the first record information, and acquire 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 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; If the first data direction matches the second data direction, fault detection is performed on each slave station device according to the pre-designed value and the updated count value.

7. The method according to claim 6, characterized in that The performing fault detection on each slave station device according to the pre-designed value and the updated count value comprises: Acquire a session identifier of the PDU session from the first record information, and acquire the session identifier from the second record information, where the session identifier is an identifier of the PDU session established between each slave station device and the UPF network element through the terminal device; If the session identifier in the first record information is consistent with the session identifier in the second record information, fault detection is performed on each slave station device according to the pre-designed value and the updated count value.

8. The method according to claim 5, characterized in that The method further comprises: Receive a session identifier sent by the UPF network element, where the session identifier is an identifier of a PDU session established between each slave device and the UPF network element through a terminal device; Sending a device identification query request to the NEF network element, wherein the device identification query request includes: the session identification, so that the NEF network element queries the device identification of the terminal device through the SMF network element; Receiving the device identification sent by the NEF network element; The first record information and the second record information are updated according to the device identification.

9. The method according to claim 6, characterized in that The method further comprises: If there is no fault in each of the slave station devices, the first record information and the second record information are updated according to the connection relationship between each of the slave station devices and the terminal device.

10. An electronic device, characterized in that: include: A processor, a memory and a bus, wherein the memory stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor communicates with the memory via the bus, and the processor executes the machine-readable instructions to perform the method described in any one of claims 1 to 9.

Images