CN112564953B

CN112564953B - Method, device and equipment for managing remote equipment of office

Info

Publication number: CN112564953B
Application number: CN202011372468.5A
Authority: CN
Inventors: 卢国梁
Original assignee: Raisecom Technology Co Ltd
Current assignee: Raisecom Technology Co Ltd
Priority date: 2020-11-30
Filing date: 2020-11-30
Publication date: 2023-04-07
Anticipated expiration: 2040-11-30
Also published as: CN112564953A

Abstract

The invention provides a method, a device and equipment for managing remote equipment of a central office, wherein the method comprises the following steps: receiving data of adding, modifying or deleting local or remote equipment at a mobile terminal/PC terminal, and storing the data to a mobile terminal/PC terminal database; when the current same-database processing mode that the mobile terminal and the PC terminal share one database is determined, responding to the page refreshing operation of the PC terminal/the mobile terminal, and synchronizing the data in the current database to the PC terminal/the mobile terminal; and when the current different-database processing mode that the mobile terminal and the PC terminal do not share one database is determined, the data is sent to a PC terminal/mobile terminal data analyzer through the message middleware, and the data analyzed by the PC terminal/mobile terminal data analyzer is sent to the PC terminal/mobile terminal database. The method of the invention can realize the management of the remote equipment of the office through the PC end and the mobile end at the same time, and improve the timeliness of the equipment management and the accuracy of the fault location.

Description

Method, device and equipment for managing remote equipment of office

Technical Field

The present invention relates to the field of network management, and in particular, to a method, an apparatus, and a device for managing a remote device.

Background

With the continuous enlargement of network scale in recent years, base stations and equipment are increased, and how to make the management of local-side equipment and remote-side equipment become efficient and convenient in order to ensure that the network can operate stably, at high speed and safely becomes a mainstream direction of network management of manufacturers at present.

The office device generally refers to a device provided in an office providing network access, and the remote device is connected to the office device through a medium such as an optical fiber. In the prior art, the network management mode generally adopts two modes:

1) A network manager of a Client-Server (C/S) architecture, i.e., a Client-Server two-layer structure, needs to install a Client for the network manager on each Server;

2) The webmaster of the B/S (Browser/Server) architecture, i.e. the Browser-Server structure, only needs to deploy a webmaster Server on one Server, or deploy a webmaster Server on a cloud platform, and a client can access the webmaster Server through a Browser.

However, in the current webmaster based on the B/S architecture, the remote device of the management bureau basically accesses the webmaster server on the browser of the PC by manual work, and inputs device information in batch on the webmaster server to achieve the purpose of managing the device resources, but the batch input management method can cause untimely device management and the problem that the PC cannot accurately locate the faulty device when the device is faulty. In order to solve the above problems, it is urgently needed to add a mobile terminal to the network management based on the B/S architecture for information entry and fault location processing, and perform remote device management via a PC terminal and the mobile terminal, so as to improve timeliness of device management and accuracy of fault location.

Disclosure of Invention

The invention provides a scheme for managing local remote equipment, which solves the problems that the equipment management is not timely in the network management based on a B/S framework at present, and a PC (personal computer) end cannot accurately position the fault equipment when the equipment fails.

In a first aspect, the present invention provides a method for managing a remote device, where the method includes:

receiving data of adding, modifying or deleting local or remote equipment at a mobile terminal/PC terminal, and storing the data to a mobile terminal/PC terminal database;

when the current same-database processing mode that the mobile terminal and the PC terminal share one database is determined, responding to the page refreshing operation of the PC terminal/the mobile terminal, and synchronizing the data in the current database to the PC terminal/the mobile terminal;

and when the current different-database processing mode that the mobile terminal and the PC terminal do not share one database is determined, the data is sent to a PC terminal/mobile terminal data analyzer through the message middleware, and the data analyzed by the PC terminal/mobile terminal data analyzer is sent to the PC terminal/mobile terminal database.

Optionally, sending the data to the PC-side/mobile-side data parser through message middleware, including:

when the data transmission is determined to fail, feeding the data back to the mobile terminal/PC terminal, and determining whether the mobile terminal/PC terminal conducts data rollback after exporting the data;

determining that data rollback is not performed, temporarily storing data failed to be sent to a failed data temporary storage area until detection data is successfully sent through a message middleware and a data analyzer, calling the data failed to be sent out from the failed data temporary storage area, and retransmitting the data to a PC (personal computer) end/a mobile end;

and determining to perform data rollback, emptying related data of a mobile terminal/PC terminal database after performing data rollback on the PC terminal/mobile terminal data parser, and feeding back a message of data transmission failure to the mobile terminal/PC terminal.

Optionally, sending the data parsed by the PC end/mobile end data parser to a PC end/mobile end database, including:

when the failure of sending the data to the PC end/mobile end database is determined, controlling the PC end/mobile end data parser to send the parsed data to the mobile end/PC end through message middleware in a preset message format, and determining whether the mobile end/PC end conducts data rollback after exporting the parsed data;

and determining to perform data rollback, emptying the related data of the database of the PC end/the mobile end after emptying the related data of the database of the PC end/the mobile end, and feeding back a message of data transmission failure to the mobile end/the PC end.

Optionally, before receiving the data added, modified or deleted by the mobile terminal/PC terminal, the method further includes:

logging in with one of a plurality of preset identities, wherein the authorities for managing the remote equipment of the office corresponding to different identities are different.

Optionally, the preset multiple identities include: the method comprises the steps that a first user identity and a second user identity are logged in through a mobile terminal or a PC terminal, and a third user identity and a fourth user identity are logged in through the PC terminal;

the authority for managing the remote device of the office corresponding to the different identities comprises:

the first user identity enjoys the assigned usage rights;

the third user identity enjoys the management authority of allocating the use authority to the first user identity;

the fourth user identity shares the authority shared by the first user identity and the third user identity and has the management authority for distributing the authority to the first user identity or the third user identity;

the second user identity enjoys full usage and management rights, as well as development rights.

Optionally, determining that the current processing mode is in the same-library processing mode or the different-library processing mode includes:

acquiring protocol modes of a mobile terminal and a PC terminal, judging whether the protocol modes of the mobile terminal and the PC terminal are consistent, if not, determining that the mobile terminal and the PC terminal are currently in a different-library processing mode, otherwise, determining that the mobile terminal and the PC terminal are currently in the same-library processing mode;

when the current same-library processing mode is determined, judging whether the data in the current database reaches a preset quantity threshold value, and switching the same-library processing mode to the different-library processing mode when the data exceeds the preset quantity threshold value.

Optionally, switching the same-library processing mode to the different-library processing mode includes:

synchronizing the data of the PC end/the mobile end in the mobile end/PC end database to the PC end/the mobile end database in real time through the trigger of the currently used mobile end/PC end database, and switching the same-database processing mode into the different-database processing mode; or

And distributing the PC end/mobile end data in the currently used mobile end/PC end database to the PC end/mobile end database, restarting a server, and switching the same-base processing mode into the different-base processing mode.

Optionally, the method further comprises:

responding to a push request of a PC end, receiving push information sent by the PC end after adding, modifying or deleting local end equipment or remote end equipment;

and pushing the pushing information to a mobile terminal through an information pushing frame, wherein the information pushing frame is an information pushing frame of an IOS (operating system of android/mobile).

Optionally, pushing the push information to the mobile terminal through a message push framework includes:

storing the push information through a mobile push background component of the message push frame, and sending the push information to a task scheduling component of the message push frame;

receiving and reading the push information through the task scheduling component, and periodically sending push tasks to be executed in the push information to an initiating push component of the message push framework;

receiving the push task through the push initiating component, decomposing a task request in the push task, sending the task request to a standard message content analyzing component of the message push framework, and reporting a pushed log and an identifier to a message push webpage management platform of a PC (personal computer) end;

and analyzing the received task request into standard message content through the standard message content analyzing component, and then sending the standard message content to the mobile terminal.

In a second aspect, the present invention provides an apparatus for managing a remote device, including a memory and a processor, wherein:

the memory is used for storing a computer program;

the processor is used for reading the program in the memory and executing the following steps:

Optionally, the sending, by the processor, the data to the PC end/mobile end data parser through message middleware includes:

Optionally, the sending, by the processor, the data analyzed by the PC end/mobile end data analyzer to a PC end/mobile end database includes:

and after determining to perform data rollback and emptying the related data of the database of the PC end/the mobile end, the related data of the database of the mobile end/the PC end and feeding back a message of data transmission failure to the mobile end/the PC end.

Optionally, before the processor receives data of the mobile terminal/PC terminal to add, modify, or delete the local terminal or the remote terminal, the method further includes:

the first user identity enjoys the assigned usage rights;

Optionally, the determining, by the processor, that the current processing mode is in the same-library processing mode or the different-library processing mode includes:

Optionally, the switching, by the processor, the same-library processing mode to the different-library processing mode includes:

Optionally, the processor is further configured to:

responding to a push request of a PC (personal computer) end, receiving push information sent by the PC end after adding, modifying or deleting local end equipment or remote end equipment;

Optionally, the pushing information to the mobile terminal by the processor through a message pushing framework includes:

In a third aspect, the present invention provides an apparatus for managing a remote device in an office, including:

the data receiving unit is used for receiving the data of the local end or remote end equipment added, modified or deleted by the mobile end/PC end and storing the data to a mobile end/PC end database;

the same-database data synchronization unit is used for responding to the page refreshing operation of the PC end/the mobile end when the same-database processing mode that the mobile end and the PC end share one database is determined to be present, and synchronizing the data in the current database to the PC end/the mobile end;

and the different-database data synchronization unit is used for sending the data to a PC end/mobile end data analyzer through the message middleware and sending the data analyzed by the PC end/mobile end data analyzer to the PC end/mobile end database when determining that the mobile end and the PC end do not share one database at present.

Optionally, the sending, by the heterogeneous database data synchronization unit, the data to the PC end/mobile end data parser through message middleware includes:

Optionally, the sending, by the different-database data synchronization unit, the data analyzed by the PC end/mobile end data analyzer to the PC end/mobile end database includes:

Optionally, before the data receiving unit receives data of the mobile terminal/PC terminal added, modified or deleted local terminal or remote terminal device, the method further includes:

logging in with one of a plurality of preset identities, wherein the authorities corresponding to different identities for the management of the remote-end equipment of the office are different.

the first user identity enjoys the assigned usage rights;

Optionally, the determining, by the same-library data synchronization unit, that the current database is in the same-library processing mode or the different-library processing mode includes:

Optionally, the determining, by the different-library data synchronization unit, that the current processing mode is in the same-library processing mode or the different-library processing mode includes:

Optionally, the switching the same-library processing mode to the different-library processing mode by the same-library data synchronization unit includes:

Optionally, the data receiving unit is further configured to:

Optionally, the pushing the push information to the mobile end by the data receiving unit through a message pushing frame includes:

In a fourth aspect, the present invention provides a computer program medium having a computer program stored thereon, which when executed by a processor, performs the steps of a method for office remote device management as provided in the first aspect above.

The method, the device and the equipment for managing the local remote equipment have the following beneficial effects that:

a mobile terminal is added in a webmaster based on a Browser/Server/APP (Browser/Server/APP) architecture for information entry and equipment management, the Browser-Server-mobile terminal APP is expanded into the Browser/Server/APP architecture, information entry and equipment management can be performed through a PC (personal computer) side webmaster, information entry and equipment management can also be performed through manual entry and two-dimensional code scanning and other modes by the mobile terminal, data sharing and real-time interconnection of the mobile terminal and the PC side are achieved, local remote equipment management is performed through the PC side and the mobile terminal, and timeliness of equipment management and accuracy of fault location are improved.

Drawings

Fig. 1 is a schematic diagram of a system for managing remote devices in an office according to an embodiment of the present invention;

fig. 2 is a flowchart of a method for server-to-office remote device management according to an embodiment of the present invention;

fig. 3 is a schematic diagram of a remote device of a mobile management office in a co-located repository processing mode according to an embodiment of the present invention;

fig. 4 is a schematic diagram of a remote device of a PC-side central office in a co-repository processing mode according to an embodiment of the present invention;

fig. 5 is a schematic diagram of a remote device of a mobile management office in a heterogeneous library processing mode according to an embodiment of the present invention;

fig. 6 is a schematic diagram of a remote device of a PC-side central office in a heterogeneous library processing mode according to an embodiment of the present invention;

FIG. 7 is a diagram illustrating a method for performing no data rollback according to an embodiment of the present invention;

fig. 8 is a schematic diagram illustrating data rollback performed when data transmission of a remote device of a mobile management office fails according to an embodiment of the present invention;

fig. 9 is a schematic diagram illustrating data rollback performed when data transmission of a remote device of a PC-side management office fails according to an embodiment of the present invention;

fig. 10 is a schematic diagram illustrating data rollback performed when a remote device of a mobile management office fails to send to a database of a PC according to an embodiment of the present invention;

fig. 11 is a schematic diagram illustrating data rollback performed when a remote device at a PC-side management office fails to send a database at a mobile side according to an embodiment of the present invention;

fig. 12 is a schematic diagram illustrating a PC pushing information to a mobile terminal through a message pushing framework according to an embodiment of the present invention;

FIG. 13 is a block diagram of a server according to an embodiment of the present invention;

fig. 14 is a schematic diagram of an apparatus for managing a local remote device according to an embodiment of the present invention;

fig. 15 is a schematic diagram of an apparatus for managing a remote device in a central office according to an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

It should be noted that the embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.

Hereinafter, some terms in the embodiments of the present disclosure are explained to facilitate understanding by those skilled in the art.

(1) The term "Software Development Kit" (SDK) in embodiments of the present disclosure refers to a collection of related documents, paradigms, and tools that assist in developing a certain class of Software.

(2) In the embodiments of the present disclosure, the term "Application Programming Interface" refers to a predefined function or a convention for linking different components of a software system, and is used to provide a set of routines that an Application program and a developer can access based on certain software or hardware without accessing source code or understanding details of internal working mechanisms.

(3) The term "rollback" in the embodiments of the present disclosure refers to an action of restoring a program or data to a last correct state when the program or data is processed incorrectly, and the rollback includes types of program rollback and data rollback.

(4) In the embodiment of the present disclosure, the term "filtering mechanism" is used to intercept request and response information of a user side and filter the information, and the filtering mechanism does not process a result and only performs auxiliary operations, that is, the filtering mechanism does not process a request and only passes or rejects the request.

(5) In the embodiments of the present disclosure, the term "local device" refers to a device provided by a local side that provides network access, and the remote device is connected to the local device through a medium such as an optical fiber.

To make the objects, technical solutions and advantages of the present disclosure clearer, the present disclosure will be described in further detail with reference to the accompanying drawings, and it is apparent that the described embodiments are only a part of the embodiments of the present disclosure, rather than all embodiments. All other embodiments, which can be derived by one of ordinary skill in the art from the embodiments disclosed herein without making any creative effort, shall fall within the scope of protection of the present disclosure.

In the prior art, the network management mode generally adopts two modes:

However, in the current webmaster based on the B/S architecture, the remote device of the management bureau basically accesses the webmaster server on the browser of the PC by manual work, and inputs device information in batch on the webmaster server to achieve the purpose of managing the device resources, but the batch input management method can cause untimely device management and the problem that the PC cannot accurately locate the faulty device when the device is faulty.

Based on the above problems, embodiments of the present invention provide a method, an apparatus, and a device for managing remote local devices, which can add a mobile terminal to the network management based on the B/S architecture for information entry and fault location processing, and perform remote local device management through a PC terminal and the mobile terminal, so as to improve timeliness of device management and accuracy of fault location. The following provides an implementation manner of a method, an apparatus, and a device for managing remote devices in an office according to an embodiment of the present invention.

Example 1

As shown in fig. 1, an embodiment of the present invention provides a schematic diagram of a system for managing a local remote device, where the system includes:

the PC side 101 is configured to add, modify, or delete the office side or the remote side device, so as to manage the office side or the remote side device, and send data of the office side or the remote side device to the server.

As an optional implementation manner, when the PC is used for device management, an operator may manually enter device information of the remote device of the office in a single or batch manner, when the information is entered, the PC transmits data to the server, the server stores the data in the database and then uniformly pushes the message to the mobile terminal, and at this time, the mobile terminal only needs to be refreshed to ensure that the data is consistent with the data of the PC.

When the PC side finds a fault, the fault information is sent to the server, and the server pushes the fault information to the mobile side in a notification bar manner to assist users of the mobile side to find and locate the fault.

A server 102, configured to receive data of a local end device or a remote end device added, modified, or deleted by a mobile terminal/PC, and store the data in a mobile terminal/PC database; when the current same-database processing mode that the mobile terminal and the PC terminal share one database is determined, responding to the page refreshing operation of the PC terminal/the mobile terminal, and synchronizing the data in the current database to the PC terminal/the mobile terminal; and when the current different-database processing mode that the mobile terminal and the PC terminal do not share one database is determined, the data is sent to a PC terminal/mobile terminal data analyzer through the message middleware, and the data analyzed by the PC terminal/mobile terminal data analyzer is sent to the PC terminal/mobile terminal database.

When adding, modifying or deleting local side or far-end equipment, the mobile terminal receives data of the local side or far-end equipment added, modified or deleted by the mobile terminal and stores the data into a mobile terminal database; when the current same-database processing mode that the mobile terminal and the PC terminal share one database is determined, responding to the page refreshing operation of the PC terminal, and synchronizing the data in the current database to the PC terminal; and when the current abnormal database processing mode that the mobile terminal and the PC terminal do not share one database is determined, the data is sent to a PC terminal data parser through a message middleware, and the data parsed by the PC terminal data parser is sent to the PC terminal database.

When adding, modifying or deleting local side or remote side equipment, the PC side receives data of adding, modifying or deleting local side or remote side equipment, and stores the data to a PC side database; when the current same-database processing mode that the mobile terminal and the PC terminal share one database is determined, responding to the page refreshing operation of the mobile terminal, and synchronizing the data in the current database to the mobile terminal; and when determining that the current mobile terminal and the PC terminal are in a different-database processing mode without sharing one database, sending the data to a mobile terminal data analyzer through the message middleware, and sending the data analyzed by the mobile terminal data analyzer to the mobile terminal database.

The mobile terminal 103 is configured to add, modify, or delete the local-side or remote-side device, so as to manage the local-side or remote-side device, and send data of the added, modified, or deleted local-side or remote-side device to the server.

As an optional implementation manner, when the mobile terminal is used for device management, a person holding the mobile terminal may perform information entry or fault location processing on local side devices and remote side devices in a machine room or on site.

It should be noted that, when information is entered, the entered content includes basic information of the device, such as a device model, manufacturer information, a device name, a machine room location, notes, and the like, and a longitude and latitude location, and the entered mode includes manual entry and code scanning entry.

When the mobile terminal personnel confirms the entry information or the failure processing, the data is transmitted to the server through the mobile terminal.

The Mobile terminal refers to any intelligent device that can implement information entry and positioning and communicate with a server, and may 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 a Wireless communication function, a computing device or other processing device connected to a Wireless modem, a vehicle-mounted device, a wearable device, a Mobile station in a 5G Network or a subscription device in a Public Land Mobile Network (PLMN) Network for future evolution, and the like.

An embodiment of the present invention provides a flowchart of a method for server-to-office remote device management, as shown in fig. 2, the method includes:

step S201, receiving data of adding, modifying or deleting local or remote equipment by the mobile terminal/PC terminal, and storing the data to a mobile terminal/PC terminal database;

and adding, modifying or deleting local side or remote side equipment by the mobile side/PC side, and sending the data of the added, modified or deleted local side or remote side equipment to the server.

The PC side can manually input the data of the adding, modifying or deleting local side or remote side equipment in a single or batch mode; the mobile terminal can enter the data of the adding, modifying or deleting local terminal or remote terminal equipment through manual entry or code scanning entry.

The server receives the data of the local side or remote side equipment added, modified or deleted by the mobile side, and stores the data into a mobile side database; the server receives the data of the local side or remote side equipment added, modified or deleted by the PC side, and stores the data to the PC side database.

Step S202, when the current same-database processing mode that the mobile terminal and the PC terminal share one database is determined, responding to the page refreshing operation of the PC terminal/the mobile terminal, and synchronizing the data in the current database to the PC terminal/the mobile terminal;

the same database processing mode is that the mobile terminal and the PC terminal share one database, wherein the shared database may be a mobile terminal database or a PC terminal database.

When the current same-database processing mode is determined, responding to the page refreshing operation of the PC end, and synchronizing the data in the current database to the PC end; and when the current same-database processing mode is determined, responding to the page refreshing operation of the mobile terminal, and synchronizing the data in the current database to the mobile terminal.

Step S203, when the current different-database processing mode that the mobile terminal and the PC terminal do not share one database is determined, the data is sent to a PC terminal/mobile terminal data analyzer through the message middleware, and the data analyzed by the PC terminal/mobile terminal data analyzer is sent to the PC terminal/mobile terminal database.

The different-database processing mode is that the mobile terminal and the PC terminal do not share one database, the mobile terminal uses the mobile terminal database, the PC terminal uses the PC terminal database, and the mobile terminal database and the PC terminal database can be deployed on the same server or different servers.

In the different-database processing mode, the mobile terminal and the PC terminal respectively use corresponding databases, so that message middleware is added, and data synchronization between the mobile terminal database and the PC terminal database is realized through the message middleware.

When the current abnormal database processing mode is determined, sending the data of the local or remote equipment added, modified or deleted by the mobile terminal to a PC terminal data analyzer through a message middleware, and sending the data analyzed by the PC terminal data analyzer to a PC terminal database; and when the current different-base processing mode is determined, sending the data of the local side or remote side equipment added, modified or deleted by the PC side to a mobile side data analyzer through a message middleware, and sending the data analyzed by the mobile side data analyzer to a mobile side database.

The following gives specific embodiments of the server in the same-library processing mode or the different-library processing mode:

embodiment 1: and the same library processing mode.

As shown in fig. 3, an embodiment of the present invention provides a schematic diagram of a remote device of a mobile management office in a co-pool processing mode.

The mobile terminal adds, modifies or deletes local terminal or far-end equipment without sending message to the PC terminal, the PC terminal does not sense the operation of the mobile terminal, and the latest data can be synchronized by default when the PC terminal interface is refreshed.

As shown in fig. 4, an embodiment of the present invention provides a schematic diagram of a remote device of a PC-side central office in a peer-to-peer library processing mode.

The PC side adds, modifies or deletes local side or far-end equipment without sending information to the mobile side, and the mobile side does not sense the operation of the PC side and can synchronize the latest data by default when the interface of the mobile side is refreshed.

Embodiment 2: and (5) processing modes of different libraries.

As shown in fig. 5, an embodiment of the present invention provides a schematic diagram of a remote device of a mobile management office in a heterogeneous library processing mode.

The server receives the data of the local side or remote side equipment added, modified or deleted by the mobile side, and stores the data into a mobile side database; the server sends the data to a PC end data parser through message middleware, the PC end data parser parses the data to generate parsed data, the server sends the parsed data to a PC end database, and when a PC end interface is refreshed, the latest data in the PC end database is synchronized to the PC end.

As an optional implementation manner, the PC automatically synchronizes data in the PC database, which is not described in detail in the following embodiments.

As shown in fig. 6, an embodiment of the present invention provides a schematic diagram of a remote device of a PC-side central office in a heterogeneous library processing mode.

The server receives data of adding, modifying or deleting local side or remote side equipment from the PC side, and stores the data to a database of the PC side; the server sends the data to a mobile terminal data analyzer through message middleware, the mobile terminal data analyzer analyzes the data to generate analyzed data, the server sends the analyzed data to a mobile terminal database, and when a mobile terminal interface is refreshed, the latest data in the mobile terminal database is synchronously sent to the mobile terminal.

As an optional implementation manner, the mobile terminal automatically synchronizes the data in the mobile terminal database, which is not described in detail in the following embodiments.

The server (1) sends the data to the PC end/mobile end data parser through message middleware; (2) Sending the data analyzed by the PC terminal/mobile terminal data analyzer to a PC terminal/mobile terminal database; there may be a failure, and subsequent processing is required after the failure of the operation, and specific embodiments of the failure of the operation are given below.

Embodiment mode 2-1: and sending the data failure to a PC end/mobile end data analyzer through message middleware.

As an optional implementation manner, sending the data to the PC-side/mobile-side data parser through message middleware includes:

it should be noted that when it is determined that the data transmission of the adding, modifying, or deleting local or remote device at the mobile terminal fails, the data of the adding, modifying, or deleting local or remote device at the mobile terminal is fed back to the mobile terminal, and it is determined whether the mobile terminal performs data rollback after exporting the data; and when determining that the data transmission of the local side or the remote side equipment added, modified or deleted by the PC side fails, feeding back the data of the local side or the remote side equipment added, modified or deleted by the PC side to the PC side, and determining whether the data is rolled back after the data is exported by the PC side.

(1) Determining that data rollback is not performed, temporarily storing data failed to be sent to a failed data temporary storage area until detection data is successfully sent through a message middleware and a data analyzer, calling the data failed to be sent out from the failed data temporary storage area, and retransmitting the data to a PC (personal computer) end/a mobile end;

as shown in fig. 7, an embodiment of the present invention provides a schematic diagram without data rollback.

It should be noted that when it is determined that data rollback is not performed, the PC sends a failure message to the mobile terminal through the mobile terminal data parser, at this time, it may occur that only the PC database has data, the mobile terminal database has no data, the message records that the data is not rolled back temporarily but needs to be temporarily stored, the data that failed to be sent is temporarily stored in a failure data temporary storage area until the detection data is successfully sent through the message middleware and the data parser, the data that failed to be sent is called out from the failure data temporary storage area, and the data is sent to the mobile terminal again; the mobile terminal sends a failure message to the PC terminal through the PC terminal data parser, at this time, the situation that only the mobile terminal database has data and the PC terminal database does not have data occurs, the message records that the data is not rolled back temporarily but needs to be stored temporarily, the data which fails to be sent is temporarily stored in a failure data temporary storage area until the detection data is successfully sent through the message middleware and the data parser, the data which fails to be sent is called out in the failure data temporary storage area, and the data are sent to the PC terminal again.

As an optional implementation manner, the sending of the probe data by the message middleware and the data parser is successful, and the sending of the interactive data information by the data parser and the message middleware is successful.

(2) And determining to perform data rollback, emptying related data of a mobile terminal/PC terminal database after performing data rollback on the PC terminal/mobile terminal data parser, and feeding back a message of data transmission failure to the mobile terminal/PC terminal.

As shown in fig. 8, an embodiment of the present invention provides a schematic diagram of data rollback when data transmission of a remote device of a mobile management office fails.

The server receives the data of the local side or remote side equipment added, modified or deleted by the mobile side, and stores the data to the mobile side database; the server sends the data failure to a PC end data parser through message middleware; and determining to perform data rollback, performing data rollback on the PC side data parser, emptying related data in the mobile side database, and feeding back a message of data transmission failure to the mobile side.

It should be noted that, the mobile terminal receives the message that the data transmission fails, and retransmits the data of the add, modify, or delete office or remote device until the data synchronization succeeds, and synchronizes the latest data in the PC database to the PC terminal when the PC interface is refreshed.

As shown in fig. 9, an embodiment of the present invention provides a schematic diagram of data rollback when data transmission of a remote device of a PC-side management office fails.

The server receives data of adding, modifying or deleting local side or remote side equipment from the PC side, and stores the data to a database of the PC side; the server fails to send the data to a mobile terminal data analyzer through message middleware; and determining to perform data rollback, performing data rollback on the mobile terminal data parser, emptying related data of a PC terminal database, and feeding back a message of data transmission failure to the PC terminal.

It should be noted that, the PC receives the message that the data transmission fails, and retransmits the data of the add, modify, or delete office or remote device until the data synchronization succeeds, and when the mobile interface is refreshed, synchronizes the latest data in the mobile database to the mobile.

Embodiment mode 2 to 2: and sending the data analyzed by the PC terminal/mobile terminal data analyzer to a PC terminal/mobile terminal database to fail.

As an optional implementation manner, sending the data parsed by the PC-side/mobile-side data parser to a PC-side/mobile-side database includes:

it should be noted that when it is determined that the sending to the PC database fails, the PC data parser is controlled to send the parsed data to the mobile terminal in a preset message format through a message middleware, and it is determined whether the mobile terminal performs data rollback after exporting the parsed data; and when the failure of sending the data to the mobile terminal database is determined, controlling the mobile terminal data analyzer to send the analyzed data to the PC terminal in a preset message format through message middleware, and determining whether the data rollback is carried out after the analyzed data is exported by the PC terminal.

(1) Determining that data rollback is not performed, temporarily storing data failed to be sent to a failed data temporary storage area until detection data are successfully sent through a message middleware and a data analyzer, calling the data failed to be sent out from the failed data temporary storage area, and retransmitting the data to a PC (personal computer) end/a mobile end;

it should be noted that the operation not performing data rollback is the same as the operation not performing data rollback in the above embodiment 2-1, and details thereof are not repeated here.

(2) And determining to perform data rollback, emptying the related data of the database of the mobile terminal/PC after emptying the related data of the database of the PC terminal/PC terminal, and feeding back a message of data sending failure to the mobile terminal/PC terminal.

As shown in fig. 10, an exemplary view of performing data rollback when the remote device of the ms fails to send to the PC database is provided in the embodiment of the present invention.

The server receives the data of the local side or remote side equipment added, modified or deleted by the mobile side, and stores the data into a mobile side database; the server sends the data to a PC end data parser through message middleware, the PC end data parser parses the data to generate parsed data, and the server fails to send the data parsed by the PC end data parser to a PC end database; and determining to perform data rollback, emptying the related data of the database of the PC terminal, emptying the related data of the database of the mobile terminal, and feeding back a message of data transmission failure to the mobile terminal.

As shown in fig. 11, an exemplary view of performing data rollback when the remote device of the PC-side management office fails to send to the mobile-side database is provided in the embodiment of the present invention.

The server receives the data of the local side or remote side equipment added, modified or deleted by the PC side, and stores the data to the database of the PC side; the server sends the data to a mobile terminal data analyzer through message middleware, the mobile terminal data analyzer analyzes the data to generate analyzed data, and the server fails to send the analyzed data to a mobile terminal database; and after determining to perform data rollback and emptying the relevant data of the mobile terminal database, emptying the relevant data of the PC terminal database and feeding back a message of data transmission failure to the PC terminal.

It should be noted that, the PC receives the message that the data transmission fails, and retransmits the data of the adding, modifying, or deleting local or remote device until the data synchronization succeeds and the mobile interface is refreshed, and synchronizes the latest data in the mobile database to the mobile.

As an optional embodiment, determining that the current processing mode is the same-library processing mode or the different-library processing mode includes:

It should be noted that the same-library processing mode is applicable to the case where the amount of data in the mobile terminal/PC database is small or the effect of tightly coupling the data of the mobile terminal and the data of the PC terminal is expected to be achieved; correspondingly, the different-database processing mode is suitable for the situation that the data quantity in the mobile terminal database and the PC terminal database is large or the effect of decoupling the data of the mobile terminal and the data of the PC terminal is expected to be achieved.

The database operation mode adopted by the server may be set to be a same-library processing mode or a different-library processing mode in advance, or may be dynamically switched according to the above-described embodiment.

As an optional implementation mode, the database working mode adopted by the server can also be designed to be manually configured, so that technicians can change the database working mode at any time according to actual requirements.

It should be noted that the protocol mode of the mobile terminal and the PC terminal can be developed and set according to actual requirements, and is written in the configuration file in advance.

As an optional implementation manner, switching the same-library processing mode to the different-library processing mode includes:

It should be noted that, when the mobile terminal database is used as the database in the same-library processing mode, the data of the PC terminal in the mobile terminal database is synchronized to the PC terminal database in real time by using a hot-switch manner through the trigger of the currently used mobile terminal database, and the same-library processing mode is switched to the different-library processing mode; when the PC-end database is used as the database of the same-library processing mode, the data of the mobile terminal in the PC-end database is synchronized to the mobile-end database in real time by using a hot switching mode through the trigger of the currently used PC-end database, and the same-library processing mode is switched to the different-library processing mode.

The hot-switch method is not required to be restarted, and the switching of the database operation mode is completed while the operation of the server is not interrupted.

It should be noted that, when the mobile terminal database is used as the database in the same-library processing mode, the data of the PC terminal in the currently used mobile terminal database is allocated to the PC terminal database in a cold-switching manner, and the server is restarted to switch the same-library processing mode to the different-library processing mode; when a PC database is used as a database of the same-library processing mode, the data of a mobile terminal in the currently used PC database is distributed to a mobile terminal database in a cold switching mode, a server is restarted, and the same-library processing mode is switched to the different-library processing mode.

It should be noted that, in the cold switching manner, the system needs to be restarted, and the data in the same library is allocated to the different library through the newly added data migration module, and the processing mode of the same library is switched to the processing mode of the different library; or merging the data of the different libraries into the same library, and switching the different library processing mode into the same library processing mode.

As an optional implementation manner, before receiving the data added, modified or deleted by the mobile terminal/PC terminal, the method further includes:

The preset plurality of identities include: the method comprises the steps that a first user identity and a second user identity are logged in through a mobile terminal or a PC terminal, and a third user identity and a fourth user identity are logged in through the PC terminal;

it should be noted that the first user identity is a constructor, the second user identity is a superuser, the third user identity is an operator, and the fourth user identity is a monitoring person.

the first user identity has the assigned use authority, namely, the constructor only has the assigned authority;

the third user identity enjoys the management authority of distributing the use authority for the first user identity, namely, an operator can distribute the authority of the constructor to which the operator belongs, is used for being in butt joint with the constructor and only exists at the PC end;

the fourth user identity shares the authority shared by the first user identity and the third user identity and has the management authority for distributing the authority to the first user identity or the third user identity, namely, a monitoring person can share all module authorities of an operator and a constructor and can distribute the authority to the operator or the constructor;

the second user identity enjoys all the use authority and the management authority and the development authority, namely the super user enjoys all the authority and the developer authority.

As an optional implementation, the permissions corresponding to different identities are separated by a filtering mechanism.

As an optional implementation manner, the server is further configured to:

It should be noted that, in the development and operation process of the mobile application, the message pushing is a very important user reaching means, and interaction with the user can be formed by the message pushing, which further improves the product use degree.

As an optional implementation manner, the message Push framework is constructed based on a homing pigeon (TPNS), and a Push Service of the homing pigeon is quickly accessed and started to be used in a SDK integration and API call manner.

It should be noted that the push scene of the push information includes notification bar information, in-application information and accurate grouping information push, and high-value information is timely transmitted to a user in need through the push scene, so that the retention rate and the activity of the user are effectively improved.

As an optional implementation manner, the message pushing framework is added into a background service of the server, and an interface is reserved at the PC end to access a web management console, so that a developer can conveniently perform pushing message management, pushing data viewing, and pushing debugging.

As an optional implementation manner, pushing the push information to the mobile end through a message push framework includes:

As shown in fig. 12, an embodiment of the present invention provides a schematic diagram of a PC pushing information to a mobile terminal through a message pushing framework.

The server may implement the method for managing the remote device through corresponding software, where the software may be specifically divided into several following components in terms of function, as shown in fig. 13, an embodiment of the present invention provides a component schematic diagram of a server, including:

the mobile pushing background component 1301 is used for storing pushing information pushed by a PC (personal computer) end and sending the pushing information to the task scheduling component;

the task scheduling component 1302 is configured to receive and read the push information, and periodically send a push task to be executed in the push information to the initiating push component;

initiating a pushing component 1303, configured to receive the pushing task, decompose a task request in the pushing task, send the task request to a component for analyzing standard message content, and report a pushed log and an identifier to a message pushing web page management console at a PC end;

a standard message content analyzing component 1304, configured to analyze the received task request into standard message content, and then send the standard message content to the mobile terminal;

the PC database 1305 is configured to store data of the PC or data of the PC and the mobile terminal;

the PC data parser 1306 is configured to parse data sent by the mobile terminal through the message middleware, and send the parsed data to the PC/mobile terminal database through the message middleware;

a mobile terminal database 1307 for storing the data of the mobile terminal or storing the data of the mobile terminal and the PC terminal;

a mobile terminal data parser 1308, configured to parse data sent by the PC terminal through the message middleware, and send the parsed data to the mobile terminal/PC terminal database through the message middleware;

message middleware 1309 is used for receiving data and forwarding the data.

A failure data buffer 1310 for temporarily storing data that has failed to be transmitted.

Example 2

An embodiment of the present invention provides a device 1400 for managing a remote device in a central office, which includes a memory 1401 and a processor 1402, as shown in fig. 14, where:

the memory is used for storing a computer program;

and determining to perform data rollback, emptying the related data of the database of the mobile terminal/PC after emptying the related data of the database of the PC terminal/PC terminal, and feeding back a message of data sending failure to the mobile terminal/PC terminal.

Optionally, before the processor receives data of the mobile terminal/PC terminal to add, modify, or delete the local terminal or the remote terminal device, the method further includes:

The preset plurality of identities comprises: the method comprises the steps that a first user identity and a second user identity are logged in through a mobile terminal or a PC terminal, and a third user identity and a fourth user identity are logged in through the PC terminal;

the first user identity enjoys the assigned usage rights;

Optionally, the processor is further configured to:

and pushing the pushing information to a mobile terminal through an information pushing framework, wherein the information pushing framework is an information pushing framework of an IOS (operating system).

An embodiment of the present invention provides an apparatus for managing remote local equipment, as shown in fig. 15, including:

a data receiving unit 1501, configured to receive data of adding, modifying, or deleting local or remote devices at a mobile terminal/PC terminal, and store the data in a mobile terminal/PC terminal database;

a database-sharing data synchronization unit 1502, configured to determine that the current database is in a database-sharing processing mode in which the mobile terminal and the PC terminal share one database, respond to a page refresh operation of the PC terminal/the mobile terminal, and synchronize data in the current database to the PC terminal/the mobile terminal;

the different-base data synchronization unit 1503 is configured to send the data to a PC-side/mobile-side data parser through a message middleware when determining that the current different-base processing mode is in which the mobile side and the PC side do not share one database, and send the data parsed by the PC-side/mobile-side data parser to the PC-side/mobile-side database.

determining that data rollback is not performed, temporarily storing data failed to be sent to a failed data temporary storage area until detection data are successfully sent through a message middleware and a data analyzer, calling the data failed to be sent out from the failed data temporary storage area, and retransmitting the data to a PC (personal computer) end/a mobile end;

the first user identity enjoys the assigned usage rights;

Optionally, the determining, by the different-library data synchronization unit, that the current processing mode is the same-library processing mode or the different-library processing mode includes:

And distributing the PC end/mobile end data in the currently used mobile end/PC end database to the PC end/mobile end database, restarting a server, and switching the same-library processing mode into the different-library processing mode.

Optionally, the data receiving unit is further configured to:

The present invention also provides a computer program medium, on which a computer program is stored, which when executed by a processor, implements the steps of a method for remote device management provided in embodiment 1 above.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and the division of the modules, for example, is merely a logical functional division, in actual implementations, there may be additional divisions, for example, multiple modules or components may be combined or may be integrated into another system, or some features may be omitted, or not implemented. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or modules, and may be in an electrical, mechanical or other form.

The modules described as separate parts may or may not be physically separate, and parts displayed as modules may or may not be physical modules, may be located in one place, or may be distributed on a plurality of network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment.

In addition, functional modules in the embodiments of the present application may be integrated into one processing module, or each of the modules may exist alone physically, or two or more modules are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. The integrated module, if implemented in the form of a software functional module and sold or used as a stand-alone product, may be stored in a computer readable storage medium.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product.

The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that a computer can store or a data storage device, such as a server, a data center, etc., that is integrated with one or more available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid State Disk (SSD)), among others.

The technical solutions provided by the present application are introduced in detail, and the present application applies specific examples to explain the principles and embodiments of the present application, and the descriptions of the above examples are only used to help understand the method and the core ideas of the present application; meanwhile, for a person skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and so forth) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

1. A method for managing devices at a remote location, comprising:

acquiring protocol modes of a mobile terminal and a PC terminal, judging whether the protocol modes of the mobile terminal and the PC terminal are consistent, if not, determining that the mobile terminal and the PC terminal are currently in a different-library processing mode, otherwise, determining that the mobile terminal and the PC terminal are currently in the same-library processing mode; when the same-library processing mode is determined to be currently in, judging whether the data in the current database reaches a preset quantity threshold value, and switching the same-library processing mode to the different-library processing mode when the preset quantity threshold value is determined to be exceeded;

when the current heterogeneous database processing mode that the mobile terminal and the PC terminal do not share one database is determined, when the data transmission is determined to fail, the data is fed back to the mobile terminal/PC terminal, and whether the data is rolled back after the data is exported by the mobile terminal/PC terminal is determined; determining that data rollback is not performed, temporarily storing data failed to be sent to a failed data temporary storage area until detection data is successfully sent through a message middleware and a data analyzer, calling the data failed to be sent out from the failed data temporary storage area, and retransmitting the data to a PC (personal computer) end/a mobile end; determining to perform data rollback, emptying relevant data of a mobile terminal/PC terminal database after performing data rollback on the PC terminal/mobile terminal data parser, and feeding back a message of data transmission failure to the mobile terminal/PC terminal; when the failure of sending the data to the PC end/mobile end database is determined, controlling the PC end/mobile end data analyzer to send the analyzed data to the mobile end/PC end through message middleware in a preset message format, and determining whether the data rollback is carried out after the analyzed data is exported by the mobile end/PC end; determining that data rollback is not performed, temporarily storing data failed to be sent to a failed data temporary storage area until detection data is successfully sent through a message middleware and a data analyzer, calling the data failed to be sent out from the failed data temporary storage area, and retransmitting the data to a PC (personal computer) end/a mobile end; and determining to perform data rollback, emptying the related data of the database of the PC end/the mobile end after emptying the related data of the database of the PC end/the mobile end, and feeding back a message of data transmission failure to the mobile end/the PC end.

2. The method according to claim 1, before receiving the data added, modified or deleted by the mobile terminal/PC terminal, further comprising:

3. The method of claim 2, wherein the preset plurality of identities comprise: the method comprises the steps that a first user identity and a second user identity are logged in through a mobile terminal or a PC terminal, and a third user identity and a fourth user identity are logged in through the PC terminal;

the first user identity enjoys the assigned usage rights;

4. The method of claim 1, wherein switching the same-bank processing mode to the different-bank processing mode comprises:

5. The method of claim 1, further comprising:

6. The method of claim 5, wherein pushing the push information to the mobile end through a message push framework comprises:

receiving the push task through the initiating push component, decomposing a task request in the push task, sending the task request to a standard message content analyzing component of the message push framework, and reporting a pushed log and an identifier to a message push webpage management console of a PC (personal computer) end;

7. An apparatus for managing a device at a remote location, comprising a memory and a processor, wherein:

the memory is used for storing a computer program;

the processor is used for reading the program in the memory and executing the method for managing the remote equipment of the central office according to any one of claims 1 to 6.

8. A computer program medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method for remote device management for offices as claimed in any one of claims 1 to 6.