FTTR-based downlink equipment control method and device, equipment and medium

Abstract

The FTTR-based downstream equipment control method and apparatus, equipment and medium provided in the present application relate to the field of network equipment control technology. In the present application, first, in response to the online event and / or offline event of the downstream equipment, the downstream equipment monitoring list is updated; secondly, in response to the downstream equipment query operation performed by the target equipment control user, the device information of at least one downstream equipment is extracted from the current downstream equipment monitoring list, and the device information of at least one downstream equipment is displayed and processed through the target downstream equipment control page; then, in response to the downstream equipment control operation performed by the target equipment control user on the target downstream equipment control page based on the device information of at least one downstream equipment, the corresponding downstream equipment control processing is performed. Based on the above content, the problem of relatively low reliability of downstream equipment control existing in the prior art can be improved.

Description

Technical Field

[0001] The present application relates to the technical field of network equipment management and control, and in particular to a method and apparatus, equipment and medium for managing and controlling downstream equipment based on FTTR. Background Art

[0002] FTTR (Fiber to The Room) technology is an innovative solution for deploying internal networks in homes and small businesses. It uses optical fiber to replace traditional network cables, extends optical fiber to each independent space, and achieves seamless interconnection with the main home gateway by deploying optical network terminal devices. Among them, the gateway device generally has a large number of terminal devices hanging down, such as mobile phones, computers, set-top boxes, etc. However, in the existing technology, there is a relatively low reliability in controlling the hanging devices. Summary of the invention

[0003] In view of this, the purpose of the present application is to provide a method and apparatus, equipment and medium for controlling downstream equipment based on FTTR, so as to improve the problem of relatively low reliability of the control of downstream equipment existing in the prior art.

[0004] To achieve the above objectives, this application adopts the following technical solutions:

[0005] A method for controlling a downstream device based on FTTR is applied to a gateway device. The method for controlling a downstream device based on FTTR includes:

[0006] Monitoring the online event of any one of the hanging devices in the local area network where the gateway device is located, and / or monitoring the online event of any one of the hanging devices in the local area network where the gateway device is located, and after monitoring the online event of any one of the hanging devices and / or the offline event of any one of the hanging devices, in response to the online event and / or the offline event, updating the pre-built hanging device monitoring list to form a current hanging device monitoring list, wherein the hanging device monitoring list has device information of each hanging device;

[0007] In response to a downstream device query operation performed by a target device control user, device information of at least one downstream device is extracted from a current downstream device monitoring list, and the device information of the at least one downstream device is displayed through a target downstream device control page, so that the target device control user can obtain the device information of the at least one downstream device from the target downstream device control page;

[0008] In response to a downstream device control operation performed by the target device control user on the target downstream device control page based on the device information of the at least one downstream device, corresponding downstream device control processing is performed on the at least one downstream device.

[0009] In a preferred embodiment of the present application, in the above-mentioned FTTR-based downstream device control method, in response to the target device control user performing a downstream device control operation on the target downstream device control page based on the device information of the at least one downstream device, the step of performing corresponding downstream device control processing on at least one of the downstream devices includes:

[0010] In response to the target device control user performing a down-hung device control operation on the target down-hung device control page based on the device information of the at least one down-hung device, performing user abnormality identification processing on the target device control user to obtain a corresponding user abnormality identification result, wherein the user abnormality identification result is used to reflect whether the target device control user has an abnormality;

[0011] When the user abnormality identification result reflects that there is no abnormality in the target device control user, performing a hanging device control process corresponding to the hanging device control operation on at least one of the hanging devices;

[0012] When the user abnormality identification result reflects that the target device control user has an abnormality, it is determined not to perform a downstream device control process corresponding to the downstream device control operation on at least one of the downstream devices.

[0013] In a preferred embodiment of the present application, in the above-mentioned FTTR-based downstream device control method, in response to the downstream device control operation performed by the target device control user on the target downstream device control page based on the device information of the at least one downstream device, the step of performing user abnormality identification processing on the target device control user to obtain the corresponding user abnormality identification result includes:

[0014] In response to the target device control user performing a downstream device control operation on the target downstream device control page based on the device information of the at least one downstream device, determining whether the target device control user performs a downstream device control operation for the first time;

[0015] When the target device control user performs a downlink device control operation for the first time, obtaining a user abnormality identification result for indicating that the target device control user has no abnormality;

[0016] When the target device control user is not performing a down-link device control operation for the first time, obtaining first operation behavior information of the target device control user performing a down-link device control operation and second operation behavior information of the target device control user performing a down-link device query operation;

[0017] The first operation behavior information and the second operation behavior information are subjected to behavior feature analysis and processing to obtain corresponding user abnormality recognition results.

[0018] In a preferred embodiment of the present application, in the above-mentioned FTTR-based downstream device control method, the step of performing behavioral feature analysis on the first operation behavior information and the second operation behavior information to obtain the corresponding user abnormality identification result includes:

[0019] Extracting first local information corresponding to the currently performed downstream device control operation from the first operation behavior information, and extracting second local information corresponding to the currently performed downstream device query operation from the second operation behavior information, and, based on the first local information and the second local information, forming a corresponding target operation behavior sequence, wherein the target operation behavior sequence includes each action performed by the target device control user and the corresponding time;

[0020] Extracting historical first partial information corresponding to each historically performed downstream device control operation from the first operation behavior information, and extracting historical second partial information corresponding to each historically performed downstream device query operation from the second operation behavior information, and forming a corresponding historical operation behavior sequence based on each of the historical first partial information and the corresponding historical second partial information, respectively, to obtain at least one corresponding historical operation behavior sequence;

[0021] The target operation behavior sequence and the at least one historical operation behavior sequence are compared and analyzed to obtain a corresponding user abnormality identification result, wherein, when the target operation behavior sequence and the at least one historical operation behavior sequence match, the user abnormality identification result is used to characterize that there is no abnormality in the target device control user, and when the target operation behavior sequence and the at least one historical operation behavior sequence do not match, the user abnormality identification result is used to characterize that there is an abnormality in the target device control user.

[0022] In a preferred embodiment of the present application, in the above-mentioned FTTR-based downstream device control method, when the user abnormality identification result reflects that there is no abnormality in the target device control user, the step of performing downstream device control processing corresponding to the downstream device control operation on at least one of the downstream devices includes:

[0023] When the user abnormality identification result reflects that there is no abnormality in the target device control user,

[0024] generating a downstream device control rule for performing a downstream device control process corresponding to the downstream device control operation on at least one of the downstream devices, so that an access state of at least one of the downstream devices is configured as a target access state, wherein the access state at least includes whether access is allowed, a time period for which access is allowed, and a data transmission speed during access;

[0025] Based on the downstream device control rule, corresponding downstream device control processing is performed on at least one of the downstream devices.

[0026] In a preferred embodiment of the present application, in the above-mentioned FTTR-based downstream device control method, the online event of any downstream device in the local area network where the gateway device is located is monitored, and / or the online event of any downstream device in the local area network where the gateway device is located is monitored, and after monitoring the online event of any downstream device and / or the offline event of any downstream device, in response to the online event and / or the offline event, the pre-built downstream device monitoring list is updated to form the current downstream device monitoring list, including:

[0027] Receive a DHCP Discover packet sent by any dynamic down-link device, and forward the DHCP Discover packet to the DHCP server, so that the DHCP server feeds back a corresponding DHCP Offer packet in response to the DHCP Discover packet, and, after receiving the DHCP Offer packet, forward the DHCP Offer packet to the dynamic down-link device, so that the dynamic down-link device feeds back a DHCP Request packet in response to the presence of an available IP address in the DHCP Offer packet, and after receiving the DHCP Request packet, forward the DHCP Request packet to the DHCP server, so that the DHCP server feeds back a DHCP Ack packet in response to the DHCP Request packet, and, after receiving the feedback DHCP Ack packet, forward the feedback DHCP Ack packet to the dynamic down-link device, so as to determine that the allocation of the IP address is completed and that an online event occurs on the dynamic down-link device;

[0028] After monitoring that an online event of any hanging device occurs, in response to the online event, the pre-built hanging device monitoring list is updated to form a current hanging device monitoring list, so that the hanging device exists in the current hanging device monitoring list;

[0029] Receive a DHCP Release packet sent by any dynamically connected device, and determine that the dynamically connected device has an offline event;

[0030] After monitoring the offline event of any hanging device, in response to the offline event, the pre-built hanging device monitoring list is updated to form the current hanging device monitoring list, so that the offline status information of the hanging device exists in the current hanging device monitoring list.

[0031] In a preferred embodiment of the present application, in the above-mentioned FTTR-based downstream device control method, after monitoring the occurrence of an online event of any downstream device, in response to the online event, the pre-built downstream device monitoring list is updated to form a current downstream device monitoring list, so that the downstream device exists in the current downstream device monitoring list, including:

[0032] After monitoring that an online event of any of the downstream devices occurs, in response to the online event, determining whether the downstream device exists in a pre-built downstream device monitoring list;

[0033] When the downstream device exists in the downstream device monitoring list, the online time of the downstream device is recorded in the downstream device monitoring list to complete the update of the downstream device monitoring list and form the current downstream device monitoring list;

[0034] When the downstream device does not exist in the downstream device monitoring list, the DHCP Discover packet is parsed to obtain first field data and second field data in the DHCP Discover packet, and a joint analysis is performed based on the first field data and the second field data to determine the device type information of the downstream device, and the online time of the downstream device and the device type information are recorded in the downstream device monitoring list to complete the update of the downstream device monitoring list and form a current downstream device monitoring list.

[0035] The present application also provides a FTTR-based downstream device control device, which is applied to a gateway device. The FTTR-based downstream device control device includes:

[0036] A device monitoring list updating module is used to monitor the online event of any hanging device in the local area network where the gateway device is located, and / or to monitor the online event of any hanging device in the local area network where the gateway device is located, and after monitoring the online event of any hanging device and / or the offline event of any hanging device, in response to the online event and / or the offline event, update the pre-built hanging device monitoring list to form a current hanging device monitoring list, wherein the hanging device monitoring list has device information of each hanging device;

[0037] The device control page display module is used to extract the device information of at least one hanging device from the current hanging device monitoring list in response to the hanging device query operation performed by the target device control user, and display the device information of the at least one hanging device through the target hanging device control page, so that the target device control user can obtain the device information of the at least one hanging device from the target hanging device control page;

[0038] The device control processing module is used to respond to the target device control user's downstream device control operation on the target downstream device control page based on the device information of the at least one downstream device, and perform corresponding downstream device control processing on at least one of the downstream devices.

[0039] On the basis of the above, the present application also provides a gateway device, including:

[0040] Memory for storing computer programs;

[0041] The processor connected to the memory is used to execute the computer program stored in the memory to implement the above-mentioned FTTR-based downstream equipment management and control method.

[0042] On the basis of the above, the present application also provides a computer-readable storage medium, in which a computer program is stored, and when the computer program is run, each step of the above-mentioned FTTR-based downstream equipment control method is executed.

[0043] The FTTR-based downstream device control method and apparatus, equipment and medium provided in the present application firstly update the downstream device monitoring list in response to the online event and / or offline event of the downstream device; secondly, in response to the downstream device query operation performed by the target device control user, extract the device information of at least one downstream device from the current downstream device monitoring list, and display the device information of at least one downstream device through the target downstream device control page; then, in response to the downstream device control operation performed by the target device control user on the target downstream device control page based on the device information of at least one downstream device, perform corresponding downstream device control processing. Based on the above content, since the target device control user can realize the control and processing of the downstream device at the gateway device, and the basis for the control and processing is still the device information of the downstream device directly obtained from the gateway device, the reliability of the control and processing can be fully guaranteed, thereby improving the relatively low reliability of the downstream device control in the prior art. Based on this, especially in application scenarios such as FTTR, different device control users generally have large differences in control requirements. Therefore, the conventional technical solution for device control based on fixed configuration is difficult to meet the actual needs of different device control users, making it difficult to effectively utilize the resources of the gateway device. Therefore, the solution based on the present application can also improve the effective utilization of resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] In order to make the above-mentioned objects, features and advantages of the present application more obvious and easy to understand, preferred embodiments are specifically cited below and described in detail with reference to the attached drawings.

[0045] Figure 1 A structural block diagram of a gateway device provided in an embodiment of the present application.

[0046] Figure 2 A flowchart of a method for controlling a downstream device based on FTTR is provided in accordance with an embodiment of the present application.

[0047] Figure 3 A schematic diagram of the target device control page provided in an embodiment of the present application.

[0048] Figure 4 A block diagram of a FTTR-based downstream equipment control device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0049] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution 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, not all of the embodiments. The components of the embodiments of the present application described and shown in the drawings here can be arranged and designed in various different configurations.

[0050] Therefore, the following detailed description of the embodiments of the present application provided in the accompanying drawings is not intended to limit the scope of the present application for which protection is sought, but merely represents selected embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without creative work are within the scope of protection of the present application.

[0051] like Figure 1 As shown, an embodiment of the present application provides a gateway device, wherein the gateway device may include a memory, a processor, and a FTTR-based downstream device control device.

[0052] In detail, the memory and the processor are electrically connected directly or indirectly to achieve data transmission or interaction. For example, the memory and the processor can be electrically connected through one or more communication buses or signal lines. The FTTR-based downstream equipment control device includes at least one software function module stored in the memory in the form of software or firmware. The processor is used to execute an executable computer program stored in the memory, for example, the software function module included in the FTTR-based downstream equipment control device, etc., to implement the FTTR-based downstream equipment control method provided in the embodiment of the present application.

[0053] Optionally, the memory may be, but is not limited to, a random access memory (RAM), a read only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable read-only memory (EEPROM), etc.

[0054] Furthermore, the processor may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), a system on chip (SoC), etc.; it may also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

[0055] Understandably, Figure 1 The structure shown is for illustration only. The gateway device may also include Figure 1 More or fewer components as shown, or with Figure 1 The different configurations shown, for example, may also include a communication unit for exchanging information with other devices (such as down-hook devices, etc.).

[0056] Combination Figure 2 The embodiment of the present application also provides a method for controlling the downstream devices based on FTTR that can be applied to the above-mentioned gateway device. The method steps defined in the process related to the method for controlling the downstream devices based on FTTR can be implemented by the gateway device.

[0057] The following will Figure 2 The specific process shown is explained in detail.

[0058] Step S110, monitor the online event of any downstream device in the local area network where the gateway device is located, and / or monitor the online event of any downstream device in the local area network where the gateway device is located, and after monitoring the online event of any downstream device and / or the offline event of any downstream device, in response to the online event and / or the offline event, update the pre-built downstream device monitoring list to form the current downstream device monitoring list.

[0059] In an embodiment of the present application, the gateway device can monitor the online event of any hanging device in the local area network where the gateway device is located, and / or monitor the online event of any hanging device in the local area network where the gateway device is located, and after monitoring the online event of any hanging device and / or the offline event of any hanging device, in response to the online event and / or offline event, update the pre-constructed hanging device monitoring list to form the current hanging device monitoring list. The hanging device monitoring list contains the device information of each hanging device. That is to say, the hanging device monitoring list can be used to record the device information of each hanging device that has been online, and the specific content of the device information is not limited. For example, it can include but is not limited to basic device information such as MAC address, IP address, hanging device type, online time, offline time, and online duration.

[0060] Step S120, in response to the downstream device query operation performed by the target device control user, extract the device information of at least one downstream device from the current downstream device monitoring list, and display the device information of the at least one downstream device through the target downstream device control page, so that the target device control user can obtain the device information of the at least one downstream device from the target downstream device control page.

[0061] In an embodiment of the present application, the gateway device can respond to the query operation of the downstream device performed by the target device control user, extract the device information of at least one downstream device from the current downstream device monitoring list, and display the device information of the at least one downstream device through the target downstream device control page, so that the target device control user can obtain the device information of the at least one downstream device from the target downstream device control page. Exemplarily, the gateway device can display the device information of all the downstream devices in the current downstream device monitoring list through the target downstream device control page, and can also display the device information of some of the downstream devices in the current downstream device monitoring list through the target downstream device control page, for example, it can display the device information of the downstream device selected by the target device control user.

[0062] Step S130, in response to the target device control user performing a downstream device control operation on the target downstream device control page based on the device information of the at least one downstream device, performing corresponding downstream device control processing on the at least one downstream device.

[0063] In an embodiment of the present application, the gateway device can respond to the target device control user's downstream device control operation on the target downstream device control page based on the device information of the at least one downstream device, and perform corresponding downstream device control processing on at least one of the downstream devices, such as performing corresponding downstream device control processing on the downstream device selected by the target device control user, so that the control processing of the device can match the needs of the target device control user.

[0064] Based on the above content, since the target device control user can realize the control and processing of the downstream device at the gateway device, and the basis for the control and processing is still the device information of the downstream device directly obtained from the gateway device, the reliability of the control and processing can be fully guaranteed, thereby improving the relatively low reliability of the downstream device control in the prior art. Based on this, especially in application scenarios such as FTTR, different device control users generally have large differences in control requirements. Therefore, the conventional technical solution for device control based on fixed configuration is difficult to meet the actual needs of different device control users, making it difficult to effectively utilize the resources of the gateway device. Therefore, the solution based on the present application can also improve the effective utilization of resources.

[0065] First, it should be noted that for step S110, the specific method of updating the pre-built monitoring list of downstream devices in response to online events and / or offline events is not limited and can be selected according to actual needs.

[0066] For example, in an alternative implementation, in order to improve the reliability of updating the downstream device monitoring list and make the information representation of the current downstream device monitoring list more comprehensive, the above-mentioned step S110 can further include step S111, step S112, step S113 and step S114, and the specific content of each step is described as follows.

[0067] Step S111, receiving a DHCP Discover packet sent by any dynamic down-link device, and forwarding the DHCP Discover packet to the DHCP server, so that the DHCP server feeds back a corresponding DHCP Offer packet in response to the DHCP Discover packet, and, after receiving the DHCP Offer packet, forwarding the DHCP Offer packet to the dynamic down-link device, so that the dynamic down-link device feeds back a DHCP Request packet in response to the presence of an available IP address in the DHCP Offer packet, and after receiving the DHCP Request packet, forwarding the DHCP Request packet to the DHCP server, so that the DHCP server feeds back a DHCP Ack packet in response to the DHCP Request packet, and, after receiving the feedback DHCP Ack packet, forwarding the feedback DHCP Ack packet to the dynamic down-link device, so as to determine that the allocation of the IP address is completed and determine that an online event occurs for the dynamic down-link device.

[0068] In an embodiment of the present application, a DHCP Discover packet sent by any dynamic downstream device can be received, and the DHCP Discover packet can be forwarded to a DHCP server, so that the DHCP server feeds back a corresponding DHCP Offer packet in response to the DHCP Discover packet, and, after receiving the DHCP Offer packet, the DHCP Offer packet is forwarded to the dynamic downstream device, so that the dynamic downstream device feeds back a DHCP Request packet in response to the presence of an available IP address in the DHCP Offer packet, and after receiving the DHCP Request packet, the DHCP Request packet is forwarded to the DHCP server, so that the DHCP server feeds back a DHCP Ack packet in response to the DHCP Request packet, and, after receiving the feedback DHCP Ack packet, the feedback DHCP Ack packet is forwarded to the dynamic downstream device, so as to determine that the allocation of the IP address is completed and that an online event occurs for the dynamic downstream device, that is, through this series of interactive operations, the allocation of IP addresses can be completed between the downstream device and the DHCP server, that is, the online of the downstream device is achieved.

[0069] Step S112, after monitoring the online event of any hanging device, in response to the online event, the pre-built hanging device monitoring list is updated to form a current hanging device monitoring list, so that the hanging device exists in the current hanging device monitoring list.

[0070] In an embodiment of the present application, after an online event of any hanging device is monitored, in response to the online event, a pre-constructed hanging device monitoring list is updated to form a current hanging device monitoring list, so that the hanging device exists in the current hanging device monitoring list, that is, the online event of the hanging device is recorded.

[0071] Step S113: receiving a DHCP Release packet sent by any dynamically connected device, and determining that an offline event occurs to the dynamically connected device.

[0072] In an embodiment of the present application, a DHCP Release packet sent by any dynamically connected device can be received, and it can be determined that the dynamically connected device has an offline event. Exemplarily, after receiving the DHCPRelease packet, the gateway device can also forward the DHCP Release packet to the DHCP server, so that the DHCP server releases the IP address currently allocated to the dynamically connected device based on the DHCP Release packet.

[0073] Step S114, after monitoring the offline event of any hanging device, in response to the offline event, the pre-built hanging device monitoring list is updated to form the current hanging device monitoring list, so that the offline status information of the hanging device exists in the current hanging device monitoring list.

[0074] In an embodiment of the present application, after monitoring the offline event of any downstream device, the pre-constructed downstream device monitoring list is updated in response to the offline event to form a current downstream device monitoring list, so that the current downstream device monitoring list contains the offline status information of the downstream device, and can also record information such as the online duration before the offline event.

[0075] It is understandable that, in the above step S112, the specific method of updating the pre-built monitoring list of downstream devices in response to the online event is not limited and can be selected according to actual needs.

[0076] For example, in an alternative implementation, in order to further improve the reliability of updating the monitoring list of the connected devices, the above step S112 may further include the following contents:

[0077] First, after monitoring the occurrence of an online event of any hanging device, in response to the online event, it can be determined whether the hanging device exists in a pre-built hanging device monitoring list. For example, generally speaking, it will not exist only when it goes online for the first time;

[0078] Secondly, when the hanging device exists in the hanging device monitoring list, the online time of the hanging device this time can be recorded in the hanging device monitoring list to complete the update of the hanging device monitoring list and form the current hanging device monitoring list;

[0079] Furthermore, when the downstream device does not exist in the downstream device monitoring list, the DHCPDiscover packet can be parsed to obtain the first field data and the second field data in the DHCP Discover packet, and a joint analysis can be performed based on the first field data and the second field data to determine the device type information of the downstream device, and the online time of the downstream device and the device type information can be recorded in the downstream device monitoring list to complete the update of the downstream device monitoring list and form the current downstream device monitoring list.

[0080] Exemplarily, the basic information of the downstream device can be extracted through option 12 hostName and option 60 VendorClassID in the DHCP Discover packet. Specifically, the type can be determined through special fields. For example, if the hostName field contains the strings android, RedMI, meizu, IQoo, Galaxy, iPhone, Honor, Mate, and JER-AN, the type of the downstream device is determined to be phone. If the VendorclassID contains android, the type of the downstream device is determined to be phone. If the hostName field contains pad, the type of the downstream device is determined to be Pad. If the hostName field contains the strings ubuntu, MacBook, micro, PC, and DESKTOP, or the vendorClassID contains the MSFT string, the type of the downstream device is determined to be PC. If the hostName field contains the ROUTER string, the type of the downstream device is determined to be ROUTER. The device connected through the other wan connection is a set-top box device, and the device type is STB.

[0081] In addition, during the monitoring process, the MAC address of each downstream device can be used to count the upstream and downstream traffic of the specified downstream device. On the gateway device, the data whose source MAC address is the MAC address of the downstream device is counted as upstream data, and the data whose destination MAC address is the MAC address of the downstream device is counted as downstream data, and the data packets are counted. The global variables are accumulated and stored, and the final data is the upstream and downstream traffic of the specified downstream device. It is saved to the flash after power failure, and the traffic statistics exist in an accumulated manner after power-on.

[0082] In addition, for the downstream device, it can also be determined whether it is a wireless relay router communicating with the gateway device. If it is a wireless relay router, it is necessary to determine the downstream device of the wireless relay router that is actually communicating with the gateway device at this time, and modify its repeatAt to the router mac address accordingly. repeatAt is used to mark whether it is a downstream device of the wireless relay router, which is convenient for the subsequent offline control of the downstream devices of the wireless relay router. When the gateway device receives the arp (address resolution protocol) message of the downstream device, it will determine whether the current device is in the downstream device monitoring list. If it is not in the downstream device list, the downstream device monitoring list needs to be updated.

[0083] In addition, for the bridged devices, the kernel sends messages to the application layer when detecting the online and offline events, so as to process them through the netlink (communication mechanism between the kernel and the user space application layer) event message. The application layer listens to the netlink event in the lanhost process (managing the network status of the host (lanhost) in the local area network, including the online and offline of the device), and executes the online process when receiving the corresponding online process, and executes the offline process when receiving the corresponding offline process.

[0084] In addition, for wired devices going offline and wireless devices in mesh networking WDS (Wireless Distribution System, a wireless network bridging method that allows multiple wireless routers to be connected to expand the network. In the mesh network structure, this method can help achieve seamless network coverage) going offline, you can poll brctlshowmacs br0 every 1 minute to make them go offline (for wired network cards connected to routers, downstream devices under routers going offline, and wireless devices in mesh networking wds going offline, brctl is a tool for Linux bridging configuration, which can be used to set and view the status of the bridge. The command brctl showmacs br0 will display all MAC addresses and their properties bound to the specified bridge br0).

[0085] In addition, for wl type (usually refers to wireless LAN devices, here specifically refers to devices running in wireless networks, such as wireless routers or wireless interfaces in wireless access points) wireless devices going offline, the wireless process (a background program running in a wireless router or network system) monitors the wireless device offline event and sends a message CMS_MSG_SET_WIRELESS_OFFLINE to the lanhost process (this message contains detailed information about the offline device, such as device identification, offline time, etc.) to make it go offline.

[0086] In addition, for the offline of the downstream devices in the EasyMesh network with frequency, the Mesh network can identify the offline of the device through the IEEE 1905.1 message, and send the message CMS_MSG_SET_MESH_HOSTENTRY_OFFLINE (a message or command used in the Mesh network management system to indicate that a specific Mesh device has been offline) to the lanhost process to make the downstream device offline (Note: There is no IEEE 1905.1 message in the EasyMesh network without frequency, and the device can only be offline through brctl showmacs br0. If you need to check the MAC address table of the bridge (for example, use the command brctl showmacs br0) to identify the device that is no longer active).

[0087] On the second aspect, it should be noted that for step S130, the specific method of performing corresponding downstream device control processing on at least one of the downstream devices is not limited and can be selected according to actual needs.

[0088] For example, in an alternative implementation, in order to ensure the reliability and security of the downstream equipment management and control processing, the above-mentioned step S130 may further include step S131, step S132 and step S133, and the specific content of each step is described as follows.

[0089] Step S131, in response to the target device control user performing a downstream device control operation on the target downstream device control page based on the device information of the at least one downstream device, performing user abnormality identification processing on the target device control user to obtain a corresponding user abnormality identification result.

[0090] In an embodiment of the present application, in response to the target device control user performing a down-hung device control operation on the target down-hung device control page based on the device information of the at least one down-hung device, the target device control user may be subjected to user abnormality identification processing to obtain a corresponding user abnormality identification result. The user abnormality identification result is used to reflect whether the target device control user has an abnormality (such as an illegal user, etc.).

[0091] Step S132: When the user abnormality identification result reflects that there is no abnormality in the target device control user, a hanging device control process corresponding to the hanging device control operation is performed on at least one of the hanging devices.

[0092] In the embodiment of the present application, when the user abnormality identification result reflects that the target device control user is not abnormal, the at least one hanging device can be subjected to hanging device control processing corresponding to the hanging device control operation. That is to say, when the target device control user is not abnormal, corresponding processing can be performed based on the needs of the target device control user.

[0093] Step S133: when the user abnormality identification result reflects that the target device control user has an abnormality, determine not to perform the downstream device control processing corresponding to the downstream device control operation on at least one of the downstream devices.

[0094] In an embodiment of the present application, when the user abnormality identification result reflects that the target device control user has an abnormality, it can be determined not to perform the hanging device control processing corresponding to the hanging device control operation on at least one of the hanging devices. In other words, when the target device control user has an abnormality, the needs of the target device control user may not be met. It is understandable that in an alternative implementation, it is sufficient to not perform the corresponding hanging device control processing. In another alternative implementation, on the basis of not performing the corresponding hanging device control processing, corresponding alarm information can also be generated for alarm processing.

[0095] It can be understood that, in the above-mentioned step S131, the specific method of performing user abnormality identification processing on the target device management and control user is not limited and can be selected according to actual needs.

[0096] For example, in an alternative implementation, in order to improve the reliability of user abnormality identification, the above-mentioned step S131 may further include step S131a, step S131b, step S131c and step S131d, and the specific content of each step is described as follows.

[0097] Step S131a, in response to the target device control user performing a downstream device control operation on the target downstream device control page based on the device information of the at least one downstream device, determining whether the target device control user performs a downstream device control operation for the first time.

[0098] In an embodiment of the present application, in response to the target device control user performing a downstream device control operation on the target downstream device control page based on the device information of the at least one downstream device, it is determined whether the target device control user is performing a downstream device control operation for the first time.

[0099] Step S131b: when the target device control user performs a downlink device control operation for the first time, a user abnormality identification result is obtained to indicate that there is no abnormality in the target device control user.

[0100] In the embodiment of the present application, when the target device control user performs the down-link device control operation for the first time, a user abnormality identification result is obtained to characterize that the target device control user has no abnormality. Generally speaking, the first down-link device control operation is generally performed by a normal device control user, and therefore, it can be directly determined that there is no abnormality.

[0101] Step S131c, when the target device control user is not performing a downstream device control operation for the first time, obtain first operation behavior information of the target device control user performing a downstream device control operation and second operation behavior information of the target device control user performing a downstream device query operation.

[0102] In the embodiment of the present application, when the target device control user does not perform the down-hook device control operation for the first time, the first operation behavior information of the target device control user performing the down-hook device control operation and the second operation behavior information of the target device control user performing the down-hook device query operation are obtained. In other words, for down-hook device control operations other than the first time, the corresponding operation behavior information can be analyzed to determine whether it belongs to a normal device control user, for example, other family members, such as children, etc.

[0103] Step S131d: Perform behavior feature analysis on the first operation behavior information and the second operation behavior information to obtain corresponding user abnormality recognition results.

[0104] In the embodiment of the present application, the first operation behavior information and the second operation behavior information may be subjected to behavior feature analysis and processing to obtain corresponding user abnormality identification results.

[0105] It can be understood that, in the above step S131d, the specific manner of performing behavior feature analysis on the first operation behavior information and the second operation behavior information is not limited. For example, in an alternative implementation, the above step S131d may include:

[0106] First, the first local information corresponding to the currently performed downstream device control operation can be extracted from the first operation behavior information, and the second local information corresponding to the currently performed downstream device query operation can be extracted from the second operation behavior information, and based on the first local information and the second local information, a corresponding target operation behavior sequence is formed, wherein the target operation behavior sequence includes each action performed by the target device control user and the corresponding time (such as 10:24:59 on August 29, 2024 - setting to prohibit the downstream device A from accessing the Internet every Monday, 10:25:02 on August 29, 2024 - setting to prohibit the downstream device A from accessing the Internet between 12-14 o'clock, 10:25:15 on August 29, 2024 - click to save the settings);

[0107] Secondly, extracting historical first partial information corresponding to each hanging device control operation performed historically from the first operation behavior information, and extracting historical second partial information corresponding to each hanging device query operation performed historically from the second operation behavior information, and respectively forming a corresponding historical operation behavior sequence based on each of the historical first partial information and the corresponding historical second partial information, so as to obtain at least one corresponding historical operation behavior sequence;

[0108] Then, the target operation behavior sequence and the at least one historical operation behavior sequence may be compared and analyzed to obtain a corresponding user abnormality identification result, wherein when the target operation behavior sequence and the at least one historical operation behavior sequence match, the user abnormality identification result is used to characterize that the target device control user does not have an abnormality, and when the target operation behavior sequence and the at least one historical operation behavior sequence do not match, the user abnormality identification result is used to characterize that the target device control user has an abnormality; illustratively, for each historical operation behavior sequence, the sequence similarity between the historical operation behavior sequence and the target operation behavior sequence may be calculated (for example, the similarity between the durations of the same actions (from the start time of the action to the start time of the next action) may be calculated as the corresponding sequence similarity, wherein the smaller the difference, the greater the sequence similarity, and the specific mapping relationship may be configured according to actual needs), and then the corresponding maximum sequence similarity may be determined, and if the historical operation behavior sequence corresponding to the sequence similarity has not been determined to have an abnormality in history, the corresponding user abnormality identification result is also that there is no abnormality; if the historical operation behavior sequence corresponding to the sequence similarity has been determined to have an abnormality in history, the corresponding user abnormality identification result is also that there is an abnormality.

[0109] It can be understood that, in the above step S132, the specific manner of performing the hanging device control processing corresponding to the hanging device control operation on at least one of the hanging devices is not limited. For example, in an alternative implementation, the above step S132 may include:

[0110] First, when the user abnormality identification result reflects that there is no abnormality in the target device control user, a downstream device control rule is generated for performing downstream device control processing corresponding to the downstream device control operation on at least one of the downstream devices, so that the access state of at least one of the downstream devices is configured as the target access state, wherein the access state at least includes whether access is allowed, the time period for allowing access, and the data transmission speed during access, or in other words, it can also be configured as follows: Figure 3 On the target device management page shown, determine whether to blacklist the specified device, whether to allow access to the Internet, and fill in the control time period and week. After setting, the blacklisted device cannot access the Internet during the specified time period on the specified week.

[0111] Secondly, based on the downstream device control rule, corresponding downstream device control processing may be performed on at least one of the downstream devices.

[0112] Based on the above content, the corresponding functions of controlling the hanging devices and the display of basic information can be realized on the FTTR grid device according to the needs of different groups of people. For different hanging devices, the control specifies the time period when a certain device can access the Internet, the time period when it cannot access the Internet, the speed limit, and other basic functional operations and page display issues, so as to facilitate the query of the specific online and offline status of the hanging devices, so as to better control and manage children's Internet access according to the information of the hanging devices.

[0113] In addition, by limiting the upstream and downstream speeds of designated downstream devices in Mbps / s, the Internet traffic of the devices can be well controlled to achieve the purpose of limiting the speed of different downstream devices. Among them, for bridged downstream devices, the bridge downstream speed limit is marked in the postrouting chain of the nat (network address translation) table (the POSTROUTING chain processes data packets sent from the local machine and processes them before the data packets leave the host. At this step, packets returning from the Internet to the local network (downlink data) can be processed and marked for speed limiting), and the bridge upstream speed limit is marked in the BROUTING chain of the broute table. Routing is marked in the forward chain of the mangle table (the mangle table is used to modify the service type or other IP header information of network data packets, while the forward chain processes data packets that pass through the router but are not the final destination. Marking data packets in this chain allows subsequent traffic control tools to apply speed limit rules based on these marks). Through the Policyer (usually used to perform rate limiting to ensure that network traffic does not exceed the preset threshold) or TC (Traffic Control, TC is a tool in the Linux kernel that controls and manages the queuing and sending of packets on the outgoing network interface. TC can control bandwidth allocation more finely and implement complex queuing algorithms and traffic shaping strategies) speed limit to limit the upstream and downstream speeds of the connected PC (computer).

[0114] Combination Figure 4 The embodiment of the present application also provides a FTTR-based down-hung device control device applicable to the above-mentioned gateway device. The FTTR-based down-hung device control device includes a device monitoring list update module, a device control page display module and a device control processing module.

[0115] The device monitoring list update module is used to monitor the online events of any hanging device in the local area network where the gateway device is located, and / or to monitor the online events of any hanging device in the local area network where the gateway device is located, and after monitoring the online event of any hanging device and / or the offline event of any hanging device, in response to the online event and / or offline event, update the pre-built hanging device monitoring list to form the current hanging device monitoring list, wherein the hanging device monitoring list has the device information of each hanging device. In the embodiment of the present application, the device monitoring list update module can be used to execute Figure 2 As shown in step S110, the relevant contents of the device monitoring list updating module can refer to the above description of step S110.

[0116] The device control page display module is used to respond to the downstream device query operation performed by the target device control user, extract the device information of at least one downstream device from the current downstream device monitoring list, and display the device information of the at least one downstream device through the target downstream device control page, so that the target device control user can obtain the device information of the at least one downstream device from the target downstream device control page. In the embodiment of the present application, the device control page display module can be used to perform Figure 2 As shown in step S120, for the relevant content of the device management and control page display module, please refer to the previous description of step S120.

[0117] The device control processing module is used to respond to the target device control user performing a down-hung device control operation on the target down-hung device control page based on the device information of the at least one down-hung device, and perform corresponding down-hung device control processing on at least one of the down-hung devices. Figure 2 As shown in step S130, for the relevant content of the device control processing module, please refer to the description of step S130 in the previous text.

[0118] In an embodiment of the present application, corresponding to the above-mentioned FTTR-based downstream device control method applied to the gateway device, a computer-readable storage medium is also provided, in which a computer program is stored, and when the computer program is run, each step of the FTTR-based downstream device control method is executed.

[0119] Among them, the steps executed when the aforementioned computer program is running will not be described one by one here, and reference can be made to the previous explanation of the FTTR-based downstream equipment control method.

[0120] To summarize, the FTTR-based downstream device control method and apparatus, equipment and medium provided in the present application firstly updates the downstream device monitoring list in response to online events and / or offline events of the downstream device; secondly, in response to the downstream device query operation performed by the target device control user, extracts the device information of at least one downstream device from the current downstream device monitoring list, and displays the device information of at least one downstream device through the target downstream device control page; then, in response to the downstream device control operation performed by the target device control user on the target downstream device control page based on the device information of at least one downstream device, performs corresponding downstream device control processing. Based on the above content, since the target device control user can realize the control and processing of the downstream device at the gateway device, and the basis for the control and processing is still the device information of the downstream device directly obtained from the gateway device, the reliability of the control and processing can be fully guaranteed, thereby improving the relatively low reliability of the downstream device control in the prior art. Based on this, especially in application scenarios such as FTTR, different device control users generally have large differences in control requirements. Therefore, the conventional technical solution for device control based on fixed configuration is difficult to meet the actual needs of different device control users, making it difficult to effectively utilize the resources of the gateway device. Therefore, the solution based on the present application can also improve the effective utilization of resources.

[0121] In several embodiments provided in the embodiments of the present application, it should be understood that the disclosed device and method can also be implemented in other ways. The device and method embodiments described above are merely schematic, for example, the flowcharts and block diagrams in the accompanying drawings show the possible architecture, functions and operations of the device, method and computer program product according to multiple embodiments of the present application. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of a code, and the module, a program segment or a part of a code contains one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of boxes in the block diagram and / or flowchart can be implemented with a dedicated hardware-based system that performs a specified function or action, or can be implemented with a combination of dedicated hardware and computer instructions.

[0122] In addition, the functional modules in the various embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.

[0123] If the function is implemented in the form of a software function module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially 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, including several instructions to enable a computer device (which can be a personal computer, electronic device, or network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program code. It should be noted that in this article, the term "include", "include" or any other variant thereof is intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements includes not only those elements, but also includes other elements that are not explicitly listed, or also includes elements inherent to such process, method, article or device. Without more constraints, an element defined by the phrase "comprising a..." does not exclude the existence of other identical elements in the process, method, article or apparatus comprising the element.

[0124] The above description is only the preferred embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A method for controlling and managing downstream equipment based on FTTR, characterized in that: Applied to a gateway device, the FTTR-based downstream device control method includes: Monitoring the online event of any one of the hanging devices in the local area network where the gateway device is located, and / or monitoring the online event of any one of the hanging devices in the local area network where the gateway device is located, and after monitoring the online event of any one of the hanging devices and / or the offline event of any one of the hanging devices, in response to the online event and / or the offline event, updating the pre-built hanging device monitoring list to form a current hanging device monitoring list, wherein the hanging device monitoring list has device information of each hanging device; In response to a downstream device query operation performed by a target device control user, device information of at least one downstream device is extracted from a current downstream device monitoring list, and the device information of the at least one downstream device is displayed through a target downstream device control page, so that the target device control user can obtain the device information of the at least one downstream device from the target downstream device control page; In response to a downstream device control operation performed by the target device control user on the target downstream device control page based on the device information of the at least one downstream device, performing corresponding downstream device control processing on the at least one downstream device; Among them, in response to the target device control user performing a downstream device control operation on the target downstream device control page based on the device information of the at least one downstream device, the step of performing corresponding downstream device control processing on at least one downstream device includes: In response to the target device control user performing a down-hung device control operation on the target down-hung device control page based on the device information of the at least one down-hung device, performing user abnormality identification processing on the target device control user to obtain a corresponding user abnormality identification result, wherein the user abnormality identification result is used to reflect whether the target device control user has an abnormality; When the user abnormality identification result reflects that there is no abnormality in the target device control user, performing a hanging device control process corresponding to the hanging device control operation on at least one of the hanging devices; When the user abnormality identification result reflects that the target device control user has an abnormality, determining not to perform a hanging device control process corresponding to the hanging device control operation on at least one of the hanging devices; Among them, in response to the target device control user performing a down-hung device control operation on the target down-hung device control page based on the device information of the at least one down-hung device, performing user abnormality identification processing on the target device control user to obtain a corresponding user abnormality identification result includes: In response to the target device control user performing a downstream device control operation on the target downstream device control page based on the device information of the at least one downstream device, determining whether the target device control user performs a downstream device control operation for the first time; When the target device control user performs a downlink device control operation for the first time, obtaining a user abnormality identification result for indicating that the target device control user has no abnormality; When the target device control user is not performing a down-link device control operation for the first time, obtaining first operation behavior information of the target device control user performing a down-link device control operation and second operation behavior information of the target device control user performing a down-link device query operation; Performing behavior feature analysis on the first operation behavior information and the second operation behavior information to obtain corresponding user abnormality recognition results; The step of performing behavior feature analysis on the first operation behavior information and the second operation behavior information to obtain corresponding user abnormality recognition results includes: Extracting first local information corresponding to the currently performed downstream device control operation from the first operation behavior information, and extracting second local information corresponding to the currently performed downstream device query operation from the second operation behavior information, and, based on the first local information and the second local information, forming a corresponding target operation behavior sequence, wherein the target operation behavior sequence includes each action performed by the target device control user and the corresponding time; Extracting historical first partial information corresponding to each historically performed downstream device control operation from the first operation behavior information, and extracting historical second partial information corresponding to each historically performed downstream device query operation from the second operation behavior information, and forming a corresponding historical operation behavior sequence based on each of the historical first partial information and the corresponding historical second partial information, respectively, to obtain at least one corresponding historical operation behavior sequence; The target operation behavior sequence and the at least one historical operation behavior sequence are compared and analyzed to obtain a corresponding user abnormality recognition result, wherein when the target operation behavior sequence and the at least one historical operation behavior sequence match, the user abnormality recognition result is used to characterize that the target device control user does not have an abnormality, and when the target operation behavior sequence and the at least one historical operation behavior sequence do not match, the user abnormality recognition result is used to characterize that the target device control user has an abnormality; wherein, for each historical operation behavior sequence, the sequence similarity between the historical operation behavior sequence and the target operation behavior sequence is calculated, including calculating the similarity between the durations of the same actions as the corresponding sequence similarity, wherein the smaller the difference, the greater the sequence similarity, and the corresponding maximum sequence similarity is determined, and if the historical operation behavior sequence corresponding to the sequence similarity has not been determined to have an abnormality in history, then the corresponding user abnormality recognition result is also that there is no abnormality; if the historical operation behavior sequence corresponding to the sequence similarity has been determined to have an abnormality in history, then the corresponding user abnormality recognition result is also that there is an abnormality; The FTTR-based downstream equipment control method further includes: For the downstream device, determine whether it is a wireless relay router communicating with the gateway device. If it is a wireless relay router, determine the downstream device of the wireless relay router communicating with the gateway device, and modify its repeatAt to the router mac address accordingly, where repeatAt is used to mark whether it is a downstream device of the wireless relay router.

2. The method for controlling and managing downlink equipment based on FTTR according to claim 1, characterized in that: The step of performing a down-hung device control process corresponding to the down-hung device control operation on at least one of the down-hung devices when the user abnormality identification result reflects that the target device control user does not have an abnormality includes: When the user abnormality identification result reflects that there is no abnormality in the target device control user, generating a downstream device control rule for performing a downstream device control process corresponding to the downstream device control operation on at least one of the downstream devices, so that an access state of at least one of the downstream devices is configured as a target access state, wherein the access state at least includes whether access is allowed, a time period for which access is allowed, and a data transmission speed during access; Based on the downstream device control rule, corresponding downstream device control processing is performed on at least one of the downstream devices.

3. The method for controlling the FTTR-based downstream equipment according to any one of claims 1 to 2, characterized in that: The step of monitoring the online event of any one of the hanging devices in the local area network where the gateway device is located, and / or monitoring the online event of any one of the hanging devices in the local area network where the gateway device is located, and after monitoring the online event of any one of the hanging devices and / or the offline event of any one of the hanging devices, in response to the online event and / or the offline event, updating the pre-built hanging device monitoring list to form the current hanging device monitoring list includes: Receive a DHCP Discover packet sent by any dynamic down-link device, and forward the DHCP Discover packet to the DHCP server, so that the DHCP server feeds back a corresponding DHCP Offer packet in response to the DHCP Discover packet, and, after receiving the DHCP Offer packet, forward the DHCP Offer packet to the dynamic down-link device, so that the dynamic down-link device feeds back a DHCP Request packet in response to the presence of an available IP address in the DHCP Offer packet, and after receiving the DHCP Request packet, forward the DHCP Request packet to the DHCP server, so that the DHCP server feeds back a DHCP Ack packet in response to the DHCP Request packet, and, after receiving the feedback DHCP Ack packet, forward the feedback DHCP Ack packet to the dynamic down-link device, so as to determine that the allocation of the IP address is completed and that an online event occurs on the dynamic down-link device; After monitoring that an online event of any hanging device occurs, in response to the online event, the pre-built hanging device monitoring list is updated to form a current hanging device monitoring list, so that the hanging device exists in the current hanging device monitoring list; Receive a DHCP Release packet sent by any dynamically connected device, and determine that the dynamically connected device has an offline event; After monitoring the offline event of any hanging device, in response to the offline event, the pre-built hanging device monitoring list is updated to form the current hanging device monitoring list, so that the offline status information of the hanging device exists in the current hanging device monitoring list.

4. The method for controlling and managing downlink equipment based on FTTR according to claim 3 is characterized in that: After monitoring the occurrence of an online event of any hanging device, in response to the online event, updating the pre-built hanging device monitoring list to form a current hanging device monitoring list, so that the hanging device exists in the current hanging device monitoring list, includes: After monitoring that an online event of any of the downstream devices occurs, in response to the online event, determining whether the downstream device exists in a pre-built downstream device monitoring list; When the downstream device exists in the downstream device monitoring list, the online time of the downstream device is recorded in the downstream device monitoring list to complete the update of the downstream device monitoring list and form the current downstream device monitoring list; When the downstream device does not exist in the downstream device monitoring list, the DHCP Discover packet is parsed to obtain first field data and second field data in the DHCP Discover packet, and a joint analysis is performed based on the first field data and the second field data to determine the device type information of the downstream device, and the online time of the downstream device and the device type information are recorded in the downstream device monitoring list to complete the update of the downstream device monitoring list and form a current downstream device monitoring list.

5. A FTTR-based down-hung equipment control device, characterized in that: Applied to a gateway device, the FTTR-based downstream device control device includes: A device monitoring list updating module is used to monitor the online event of any hanging device in the local area network where the gateway device is located, and / or to monitor the online event of any hanging device in the local area network where the gateway device is located, and after monitoring the online event of any hanging device and / or the offline event of any hanging device, in response to the online event and / or the offline event, update the pre-built hanging device monitoring list to form a current hanging device monitoring list, wherein the hanging device monitoring list has device information of each hanging device; The device control page display module is used to extract the device information of at least one hanging device from the current hanging device monitoring list in response to the hanging device query operation performed by the target device control user, and display the device information of the at least one hanging device through the target hanging device control page, so that the target device control user can obtain the device information of the at least one hanging device from the target hanging device control page; A device control processing module, configured to respond to a down-hung device control operation performed by the target down-hung device control user on the target down-hung device control page based on the device information of the at least one down-hung device, and perform corresponding down-hung device control processing on at least one of the down-hung devices; The step of performing corresponding downstream device control processing on at least one of the downstream devices in response to the target downstream device control user performing a downstream device control operation on the target downstream device control page based on the device information of the at least one downstream device includes: In response to the target device control user performing a down-hung device control operation on the target down-hung device control page based on the device information of the at least one down-hung device, performing user abnormality identification processing on the target device control user to obtain a corresponding user abnormality identification result, wherein the user abnormality identification result is used to reflect whether the target device control user has an abnormality; When the user abnormality identification result reflects that there is no abnormality in the target device control user, performing a hanging device control process corresponding to the hanging device control operation on at least one of the hanging devices; When the user abnormality identification result reflects that the target device control user has an abnormality, determining not to perform a hanging device control process corresponding to the hanging device control operation on at least one of the hanging devices; Among them, in response to the target device control user performing a down-hung device control operation on the target down-hung device control page based on the device information of the at least one down-hung device, performing user abnormality identification processing on the target device control user to obtain a corresponding user abnormality identification result includes: In response to the target device control user performing a downstream device control operation on the target downstream device control page based on the device information of the at least one downstream device, determining whether the target device control user performs a downstream device control operation for the first time; When the target device control user performs a downlink device control operation for the first time, obtaining a user abnormality identification result for indicating that the target device control user has no abnormality; When the target device control user is not performing a down-link device control operation for the first time, obtaining first operation behavior information of the target device control user performing a down-link device control operation and second operation behavior information of the target device control user performing a down-link device query operation; Performing behavior feature analysis on the first operation behavior information and the second operation behavior information to obtain corresponding user abnormality recognition results; The performing behavior feature analysis on the first operation behavior information and the second operation behavior information to obtain corresponding user abnormality recognition results includes: Extracting first local information corresponding to the currently performed downstream device control operation from the first operation behavior information, and extracting second local information corresponding to the currently performed downstream device query operation from the second operation behavior information, and, based on the first local information and the second local information, forming a corresponding target operation behavior sequence, wherein the target operation behavior sequence includes each action performed by the target device control user and the corresponding time; Extracting historical first partial information corresponding to each historically performed downstream device control operation from the first operation behavior information, and extracting historical second partial information corresponding to each historically performed downstream device query operation from the second operation behavior information, and forming a corresponding historical operation behavior sequence based on each of the historical first partial information and the corresponding historical second partial information, respectively, to obtain at least one corresponding historical operation behavior sequence; The target operation behavior sequence and the at least one historical operation behavior sequence are compared and analyzed to obtain a corresponding user abnormality recognition result, wherein when the target operation behavior sequence and the at least one historical operation behavior sequence match, the user abnormality recognition result is used to characterize that the target device control user does not have an abnormality, and when the target operation behavior sequence and the at least one historical operation behavior sequence do not match, the user abnormality recognition result is used to characterize that the target device control user has an abnormality; wherein, for each historical operation behavior sequence, the sequence similarity between the historical operation behavior sequence and the target operation behavior sequence is calculated, including calculating the similarity between the durations of the same actions as the corresponding sequence similarity, wherein the smaller the difference, the greater the sequence similarity, and the corresponding maximum sequence similarity is determined, and if the historical operation behavior sequence corresponding to the sequence similarity has not been determined to have an abnormality in history, then the corresponding user abnormality recognition result is also that there is no abnormality; if the historical operation behavior sequence corresponding to the sequence similarity has been determined to have an abnormality in history, then the corresponding user abnormality recognition result is also that there is an abnormality; The FTTR-based downstream equipment control device further includes other modules for: For the downstream device, determine whether it is a wireless relay router communicating with the gateway device. If it is a wireless relay router, determine the downstream device of the wireless relay router communicating with the gateway device, and modify its repeatAt to the router mac address accordingly, where repeatAt is used to mark whether it is a downstream device of the wireless relay router.

6. A gateway device, characterized in that: include: Memory for storing computer programs; A processor connected to the memory is used to execute the computer program stored in the memory to implement the FTTR-based downstream equipment management and control method as described in any one of claims 1-4.

7. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is run, the FTTR-based downstream equipment control method according to any one of claims 1 to 4 is executed.

Images