CN108282219B - Long link switching processing method for data communication of vehicle satellite positioning system - Google Patents
Long link switching processing method for data communication of vehicle satellite positioning system Download PDFInfo
- Publication number
- CN108282219B CN108282219B CN201810097923.1A CN201810097923A CN108282219B CN 108282219 B CN108282219 B CN 108282219B CN 201810097923 A CN201810097923 A CN 201810097923A CN 108282219 B CN108282219 B CN 108282219B
- Authority
- CN
- China
- Prior art keywords
- current
- vehicle
- database
- link
- data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B7/00—Radio transmission systems, i.e. using radiation field
- H04B7/14—Relay systems
- H04B7/15—Active relay systems
- H04B7/185—Space-based or airborne stations; Stations for satellite systems
- H04B7/1851—Systems using a satellite or space-based relay
- H04B7/18517—Transmission equipment in earth stations
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B7/00—Radio transmission systems, i.e. using radiation field
- H04B7/14—Relay systems
- H04B7/15—Active relay systems
- H04B7/185—Space-based or airborne stations; Stations for satellite systems
- H04B7/1853—Satellite systems for providing telephony service to a mobile station, i.e. mobile satellite service
- H04B7/18558—Arrangements for managing communications, i.e. for setting up, maintaining or releasing a call between stations
Abstract
The invention discloses a long link switching processing method for data communication of a vehicle satellite positioning system, which comprises the following steps: s1, the vehicle-mounted mobile terminal establishes a link with the current server, S2, the current server obtains the vehicle ID of the vehicle-mounted mobile terminal, generates a current link record code corresponding to the current link and caches the current link record code in the memory of the current server, S3, the current server establishes a connection with the database, and the database updates vehicle data at the same time; s4, the current server periodically acquires data periodically reported from the vehicle-mounted mobile terminal; s5, when the link is disconnected, the current server sends a vehicle state updating request to the database, and the updating request contains the current link record code cached by the current server; s6, the database checks whether the current link record code is consistent and updates the data. The method uses double keywords and different keywords on different occasions, avoids dirty data, and reduces database write operation by using the record ID as state transition.
Description
Technical Field
The invention relates to the field of telecommunication, in particular to a long link switching processing method for data communication of a vehicle satellite positioning system.
Background
Most of the mobile terminals are in a mobile state during use, and the terminals may be reconnected to the TCP link due to reasons such as no signal, base station handover, etc., and the old link of the server may be normally closed or in an offline state. The status update processing for the single version is simple: the state is updated as long as the old link is replaced by the new link, and no update conflict exists. But the processing for a cluster of servers is relatively complex: it cannot guarantee that the newly connected TCP link is allocated to the original server (presence of load balancing, IP handoff, etc.), so that there may be a timeout release for the original server, and the new link is already connected to another server, e.g., the cluster link of fig. 1 recovers the mobile terminal state update on the r.
The simplest method is to report the synchronous updating state of the data according to the real-time period, but the problem is that the period of the periodic reporting number is about 30 seconds at most, the terminal state is updated too frequently, and the terminal state is not updated every time, only needs to be updated under specific conditions, and in addition, the real-time updating is not suggested in consideration of the system performance. How to solve the problem is that headache and foot pain are treated by a frequent solution, namely, the state of the mobile terminal is updated only in real time when a conflict period exists, for example, within a specified time (1, which is determined according to timeout time and a cycle reported by a cycle) after an "xx connection request", and the state of the mobile terminal is updated only after the cycle report is received, theoretically, the problem is not solved, and only when the cycle reported by the cycle is adjusted, the 1 time may also need to be adjusted; in addition, the coupling degree between the functional modules is high, and the later operation and maintenance difficulty is high.
Disclosure of Invention
The invention aims to overcome the defects of the prior art, provides a long link switching processing method for data communication of a vehicle satellite positioning system, reduces the operation of frequently updating the vehicle state and improves the service performance. Dirty data is avoided, and guarantee is provided for server lateral expansion.
The technical scheme adopted by the invention is as follows:
a long link switching processing method for data communication of a vehicle satellite positioning system comprises the following steps:
s1, the vehicle-mounted mobile terminal establishes a link with the current server,
s2, the current server obtains the vehicle ID of the vehicle-mounted mobile terminal, generates the current link record code corresponding to the current link and caches the current link record code in the memory of the current server, and each link corresponds to a different current link record code;
s3, when the current link is connected with the current server for the first time, the current server establishes connection with the database and the database updates the vehicle state data; the vehicle data includes a vehicle ID, a current link record code, and a vehicle status;
s4, the current server periodically acquires data periodically reported from the vehicle-mounted mobile terminal and stores the data;
s5, when the link is disconnected, the current server sends a vehicle state updating request to the database, and the updating request contains the current link record code cached by the current server;
s6, the database detects whether the current link record code cached by the current server is consistent with the current link record code of the corresponding data list in the database;
when detecting that the current link record codes of the current server are consistent, the database receives vehicle state updating data sent by the current server, and the database updates data in a data list;
and when detecting that the current link record codes of the current server are inconsistent, the database refuses to receive the vehicle state updating data sent by the current server, and the data in the current data list is kept unchanged.
Further, the vehicle ID of the in-vehicle mobile terminal is unique in step S2, and is not changed every time of linking; each link corresponds to a current link record code, and the current link record code of the same link is unique and unchangeable.
The specific steps of updating the vehicle data in the database in step S3 are:
s3-1, the database inquires whether a corresponding data list exists based on the vehicle ID,
s3-2, when the database has a corresponding data list, updating the current link record code and the vehicle state of the corresponding data list;
and S3-3, when the corresponding data list does not exist in the database, creating a corresponding new data list and writing the vehicle data.
In step S4, when the current server receives a normal link disconnection request during the period of periodically acquiring data reported from the vehicle-mounted mobile terminal, the current link record code cached in the memory of the current server is kept as a keyword, and the vehicle state data in the updated database is marked as "offline".
In step S4, when the current server acquires the periodic data, the current link record code cached in the memory of the current server is kept as a keyword, and the vehicle state data in the updated database is marked as "offline"; and the current server does not acquire the periodic updating data overtime, keeps the current link record code cached in the memory of the current server unchanged, and does not update the vehicle state in the database.
When the vehicle status in the data list is updated to "offline" in step S6, the method further includes the following steps:
s6-1, the database returns an update result to the current server, which normally indicates that the vehicle is not on line and abnormally indicates that the vehicle is on line;
and S6-2, the current server clears the current link record code cached in the memory of the server.
By adopting the technical scheme, the invention has the following advantages: (1) the double keywords are used, different keywords are used in different occasions, and dirty data are avoided. Setting a vehicle ID (key), a current link recording code (key) and a vehicle state when the vehicle state of the database is designed, wherein the primary key is the vehicle ID or the current link recording code; the current link record code is UUID and will change, the vehicle ID does not change. (2) Unique state transitions-state transitions using the current linking record code. When the connection request authentication passes each time, a unique current link record code is produced, the 'vehicle ID, the record ID and the vehicle state' in the database are updated to be current 'vehicle ID, record ID and online' by taking the 'vehicle ID' as an updating condition, and the data are updated when existing and inserted when not existing; meanwhile, the current link record code is stored in a cache memory of the server (used when being released). (3) Database write operations are reduced. When the connection is released normally or overtime, the current link record code is taken as an updating condition, the consistency of the updated data is compared with the current link record code stored in the database, the state of the vehicle in the database is updated to be offline when the comparison is consistent, and then the server is informed to delete the current link record code data cached in the memory; if the current link record codes are consistent, the updating fails, which indicates that the original record has been updated by the new connection request, i.e. the current state is the latest state. (4) Connection request, connection release (link timeout or received link close) are in one-to-one correspondence, and once a connection request is covered by a new connection request, the old connection release will fail (not update the state) because the old connection release has no correspondence with the new connection, so that it can maintain the latest state.
Drawings
The invention is described in further detail below with reference to the accompanying drawings and the detailed description;
FIG. 1 is a diagram illustrating an update status of a mobile terminal in a vehicle according to the prior art;
FIG. 2 is a schematic flow chart of a long link handover processing method for data communication of a vehicle satellite positioning system according to the present invention;
FIG. 3 is a diagram illustrating the application of the present invention to scenario 1;
FIG. 4 is a diagram illustrating the application of the present invention to scenario 2;
FIG. 5 is a diagram illustrating a state of the present invention applied to scenario 3;
fig. 6 is a diagram illustrating a state where the present invention is applied to scenario 4.
Detailed Description
As shown in one of fig. 2 to 6, the present invention discloses a long link handover processing method for data communication of a vehicle satellite positioning system, which comprises the following steps:
s1, the vehicle-mounted mobile terminal establishes a link with the current server,
s2, the current server obtains the vehicle ID of the vehicle-mounted mobile terminal, generates the current link record code corresponding to the current link and caches the current link record code in the memory of the current server, and each link corresponds to a different current link record code;
s3, when the current link is connected with the current server for the first time, the current server establishes connection with the database and the database updates the vehicle state data; the vehicle data includes a vehicle ID, a current link record code, and a vehicle status;
s4, the current server periodically acquires data periodically reported from the vehicle-mounted mobile terminal and stores the data;
s5, when the link is disconnected, the current server sends a vehicle state updating request to the database, and the updating request contains the current link record code cached by the current server;
s6, the database detects whether the current link record code cached by the current server is consistent with the current link record code of the corresponding data list in the database;
when detecting that the current link record codes of the current server are consistent, the database receives vehicle state updating data sent by the current server, and the database updates data in a data list;
and when detecting that the current link record codes of the current server are inconsistent, the database refuses to receive the vehicle state updating data sent by the current server, and the data in the current data list is kept unchanged.
In step S2, the vehicle ID of the in-vehicle mobile terminal is unique, and the vehicle ID of the in-vehicle mobile terminal is not changed every time of linking; each link corresponds to a current link record code, and the current link record code of the same link is unique and unchangeable.
The specific steps of updating the vehicle data in the database in step S3 are:
s3-1, the database inquires whether a corresponding data list exists based on the vehicle ID,
s3-2, when the database has a corresponding data list, updating the current link record code and the vehicle state of the corresponding data list;
and S3-3, when the corresponding data list does not exist in the database, creating a corresponding new data list and writing the vehicle data.
In step S4, when the current server receives a normal link disconnection request during the period of periodically acquiring data reported from the vehicle-mounted mobile terminal, the current link record code cached in the memory of the current server is kept as a keyword, and the vehicle state data in the updated database is marked as "offline".
In step S4, when the current server acquires the periodic data, the current link record code cached in the memory of the current server is kept as a keyword, and the vehicle state data in the updated database is marked as "offline"; and the current server does not acquire the periodic updating data overtime, keeps the current link recording code cached in the memory of the current server unchanged, and does not update the vehicle state in the data.
When the vehicle status in the data list is updated to "offline" in step S6, the method further includes the following steps:
s6-1, the database returns an update result to the current server, which normally indicates that the vehicle is not on line and abnormally indicates that the vehicle is on line;
and S6-2, the current server clears the current link record code cached in the memory of the server.
The following is a detailed description of different working scenarios:
1) scene 1: normally disconnecting the mobile terminal:
as shown in fig. 3, when the vehicle-mounted mobile terminal establishes a socket connection with the current server, the current recording code corresponding to the link is generated, and the current link is specifically UUID 1;
when a normal link disconnection request is received during the period that the current server periodically acquires data periodically reported from the vehicle-mounted mobile terminal, the socket is closed, the current link recording code cached in the memory of the current server is kept as a primary keyword, and the vehicle state data in the updated database is marked as off-line.
Specifically, when the consistency of the current recording code is detected during updating of the database, the UUID1 cached by the current server is not changed and is equal to the UUID recorded in the database, the additional determination condition UUID is the same, and the database successfully updates the vehicle state to be offline.
2) Scene 2: new and old links are assigned to the same server and the server does not detect the old link broken (hit):
as shown in fig. 4, when an old link is abnormal or a base station is switched, and a vehicle-mounted mobile terminal reestablishes a link with a current server (the same server) used by the old link, the current server generates a new current recording code corresponding to the new link, specifically, the current link is UUID2, and the current recording code is cached in a memory of the current server;
further, the current server is connected with a database, and the database updates vehicle data; the vehicle data comprises a vehicle ID, a current link record code and a vehicle state, and as the vehicle-mounted mobile terminal of the same vehicle is connected again and updates the database, the vehicle ID is consistent with that of the old link, and the database is stored in a data list corresponding to the vehicle ID; when the vehicle data is updated by the data, replacing the old current recording code (UUID 1) in the data list with the new current recording code (UUID 2);
when the current server periodically acquires data periodically reported from the vehicle-mounted mobile terminal through a new link, the database normally updates the vehicle state data as the UUID2 cached in the memory of the server is consistent with the UUID data recorded in the database;
in this scenario, although the UUID2 indicated by the ninthly in fig. 4 is different from the UUID1, when a new link is established on the vehicle-mounted mobile terminal, the database update data is updated according to the vehicle ID, and the current recording code UUID is not further determined, so that the database update is normally OK (this is called a prompt interruption, and the user cannot perceive that the link is broken).
3) Scene 3: new and old links are assigned to different servers, and when the new link is established, the server used by the old link does not detect the old link disconnection (momentary disconnection):
as shown in fig. 5, the new and old links are assigned to different servers, and when the new link is established, the server used by the old link does not detect the old link disconnection (snapshot); when the vehicle-mounted mobile terminal establishes a new link, the new server is connected with the database for updating, because the updated data of the database is updated according to the vehicle ID when the vehicle-mounted mobile terminal is on-line and the new link is established, the current recording code UUID is not further added with a judgment condition, the database is normally updated, and the UUID in the database is updated into the UUID2 corresponding to the new link.
After a new link is established, because an old link is disconnected, when an old server periodically acquires data periodically reported from a vehicle-mounted mobile terminal, the old server detects that the acquired periodic update data is overtime, keeps a current link record code UUID1 cached in an internal memory of the old server unchanged, and simultaneously marks vehicle state data in the periodic update data as off-line; the old server establishes a connection with the database and sends an update data request,
and the database carries out consistency detection on the current recording codes, and at the moment, because the current recording codes of the database corresponding to the vehicle ID are changed into the newly linked current recording codes UUID2, the database detects that the current recording codes are inconsistent, and the database rejects the data update requested by the old server.
In this scenario, although the processing of the flow ninthly in fig. 5 is not in the same server as the flow ③, the updating of the database state is not affected; the UUID1 of the old link timeout at flow r is the same as the UUID1 of flow c, but is different from the UUID after updating the database in flow n, and since the additional determination condition during periodically updating data is that the UUID is the same, the data of the old server is not updated, and the state of the mobile terminal is not changed.
4) Scene 4: new and old links are assigned to different servers, and before the new link is established, the old server detects the old link being broken (momentary break):
as shown in fig. 6, before the new link is established, the old server detects the old link is broken, the process of the procedure (1) is the same as the scene 1, the vehicle status data in the database is normally updated to be offline,
when a new link is established later, the current server generates a corresponding new current recording code for the new link, specifically, the current link is UUID2, and the current link is cached in the memory of the current server;
further, the current server is connected with a database, and the database updates vehicle data; the vehicle data comprises a vehicle ID, a current link record code and a vehicle state, and as the vehicle-mounted mobile terminal of the same vehicle is connected again and updates the database, the vehicle ID is consistent with that of the old link, and the database is stored in a data list corresponding to the vehicle ID; when the data updates the vehicle data, the new current recording code (UUID 2) is substituted for the old current recording code (UUID 1) in the data list, and the vehicle status is updated to "on-line"; the data is periodically updated through the new link thereafter, and the process is normal.
According to the invention, who is online processes offline, the link record codes UUID are simply used to correspond to each other, so that the problem that the link record codes are overtime processed into offline after being online again in an overtime period is solved, in addition, no additional unnecessary processing is added, and the performance of the server is optimized; in addition, the invention only processes the steps which need to be processed for the service processing, does not add extra complex logic processing, and the processing performance of the server reaches the best.
By adopting the technical scheme, the invention has the following advantages: (1) the double keywords are used, different keywords are used in different occasions, and dirty data are avoided. Setting a vehicle ID (key), a current link recording code (key) and a vehicle state when the vehicle state of the database is designed, wherein the primary key is the vehicle ID or the current link recording code; the current link record code is UUID and will change, the vehicle ID does not change. (2) Unique state transitions-state transitions using the current linking record code. When the connection request authentication passes each time, a unique current link record code is produced, the 'vehicle ID, the record ID and the vehicle state' in the database are updated to be current 'vehicle ID, record ID and online' by taking the 'vehicle ID' as an updating condition, and the data are updated when existing and inserted when not existing; meanwhile, the current link record code is stored in a cache memory of the server (used when being released). (3) Database write operations are reduced. When the connection is released normally or overtime, the current link record code is taken as an updating condition, the consistency of the updated data is compared with the current link record code stored in the database, the state of the vehicle in the database is updated to be offline when the comparison is consistent, and then the server is informed to delete the current link record code data cached in the memory; if the current link record codes are consistent, the updating fails, which indicates that the original record has been updated by the new connection request, i.e. the current state is the latest state. (4) Connection request, connection release (link timeout or received link close) are in one-to-one correspondence, and once a connection request is covered by a new connection request, the old connection release will fail (not update the state) because the old connection release has no correspondence with the new connection, so that it can maintain the latest state.
Claims (6)
1. A long link switching processing method for data communication of a vehicle satellite positioning system is characterized by comprising the following steps: which comprises the following steps:
s1, the vehicle-mounted mobile terminal establishes a link with the current server,
s2, the current server obtains the vehicle ID of the vehicle-mounted mobile terminal, generates the current link record code corresponding to the current link and caches the current link record code in the memory of the current server, and each link corresponds to a different current link record code;
s3, when the current link is connected with the current server for the first time, the current server establishes connection with the database and updates the vehicle state data in the database by taking the vehicle ID as a main key; the vehicle state data includes a vehicle ID, a current link record code, and a vehicle state;
s4, the current server periodically acquires data periodically reported from the vehicle-mounted mobile terminal and stores the data;
s5, when the link is disconnected, the current server sends a vehicle state updating request to the database by taking the current link recording code as a main key, wherein the updating request comprises the current link recording code cached by the current server;
s6, the database detects whether the current link record code cached by the current server is consistent with the current link record code of the corresponding data list in the database;
when detecting that the current link record codes of the current server are consistent, the database receives vehicle state updating data sent by the current server, and the database updates data in a data list;
and when detecting that the current link record codes of the current server are inconsistent, the database refuses to receive the vehicle state updating data sent by the current server, and the data in the current data list is kept unchanged.
2. The method of claim 1, wherein the method further comprises the steps of: in step S2, the vehicle ID of the in-vehicle mobile terminal is unique, and the vehicle ID of the in-vehicle mobile terminal is not changed every time of linking; each link corresponds to a current link record code, and the current link record code of the same link is unique and unchangeable.
3. The method of claim 1, wherein the method further comprises the steps of: the specific steps of updating the vehicle state data by the database in step S3 are:
s3-1, the database inquires whether a corresponding data list exists on the basis of the vehicle ID;
s3-2, when the database has a corresponding data list, updating the current link record code and the vehicle state of the corresponding data list;
and S3-3, when the corresponding data list does not exist in the database, creating a corresponding new data list and writing the vehicle state data.
4. The method of claim 1, wherein the method further comprises the steps of: in step S4, when the current server receives a normal link disconnection request during the period of periodically acquiring data reported from the vehicle-mounted mobile terminal, the current link record code cached in the memory of the current server is kept as a keyword, and the vehicle state data in the updated database is marked as "offline".
5. The method of claim 1, wherein the method further comprises the steps of: in step S4, when the current server acquires the periodic data, the current link record code cached in the memory of the current server is kept as a keyword, and the vehicle state data in the updated database is marked as "offline"; and the current server does not acquire the periodic updating data overtime, keeps the current link record code cached in the memory of the current server unchanged, and does not update the vehicle state in the database.
6. The method of claim 1, wherein the method further comprises the steps of: when the vehicle status in the data list is updated to "offline" in step S6, the method further includes the following steps:
s6-1, the database returns an update result to the current server, which normally indicates that the vehicle is not on line and abnormally indicates that the vehicle is on line;
and S6-2, the current server clears the current link record code cached in the memory of the server.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810097923.1A CN108282219B (en) | 2018-01-31 | 2018-01-31 | Long link switching processing method for data communication of vehicle satellite positioning system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810097923.1A CN108282219B (en) | 2018-01-31 | 2018-01-31 | Long link switching processing method for data communication of vehicle satellite positioning system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108282219A CN108282219A (en) | 2018-07-13 |
| CN108282219B true CN108282219B (en) | 2021-06-29 |
Family
ID=62807237
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810097923.1A Active CN108282219B (en) | 2018-01-31 | 2018-01-31 | Long link switching processing method for data communication of vehicle satellite positioning system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108282219B (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101286889A (en) * | 2008-05-23 | 2008-10-15 | 杭州华三通信技术有限公司 | Method and device for state recording |
| CN102281310A (en) * | 2010-06-12 | 2011-12-14 | 厦门雅迅网络股份有限公司 | Method for monitoring on-line state of vehicle-mounted global positioning system (GPS) terminal in real time |
| KR20130022100A (en) * | 2011-08-24 | 2013-03-06 | 한국전자통신연구원 | System for synchronizing state information of vehicle and method thereof |
| CN104750740A (en) * | 2013-12-30 | 2015-07-01 | 北京新媒传信科技有限公司 | Data renewing method and device |
| CN105338096A (en) * | 2015-11-17 | 2016-02-17 | 北京奇虎科技有限公司 | Vehicle state detection method and device |
| CN106160945A (en) * | 2016-08-12 | 2016-11-23 | 福建富士通信息软件有限公司 | Communication data packets method for packing and system for vehicle satellite alignment system |
| CN107368366A (en) * | 2016-05-11 | 2017-11-21 | 厦门雅迅网络股份有限公司 | The distortion of vehicle presence solves method and its system |
-
2018
- 2018-01-31 CN CN201810097923.1A patent/CN108282219B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101286889A (en) * | 2008-05-23 | 2008-10-15 | 杭州华三通信技术有限公司 | Method and device for state recording |
| CN102281310A (en) * | 2010-06-12 | 2011-12-14 | 厦门雅迅网络股份有限公司 | Method for monitoring on-line state of vehicle-mounted global positioning system (GPS) terminal in real time |
| KR20130022100A (en) * | 2011-08-24 | 2013-03-06 | 한국전자통신연구원 | System for synchronizing state information of vehicle and method thereof |
| CN104750740A (en) * | 2013-12-30 | 2015-07-01 | 北京新媒传信科技有限公司 | Data renewing method and device |
| CN105338096A (en) * | 2015-11-17 | 2016-02-17 | 北京奇虎科技有限公司 | Vehicle state detection method and device |
| CN107368366A (en) * | 2016-05-11 | 2017-11-21 | 厦门雅迅网络股份有限公司 | The distortion of vehicle presence solves method and its system |
| CN106160945A (en) * | 2016-08-12 | 2016-11-23 | 福建富士通信息软件有限公司 | Communication data packets method for packing and system for vehicle satellite alignment system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108282219A (en) | 2018-07-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11388005B2 (en) | Connected gateway server system for real-time vehicle control service | |
| CN106209447B (en) | The fault handling method and device of distributed caching | |
| EP1560395A1 (en) | System and method for session reestablishment between client terminal and server | |
| US7912858B2 (en) | Data synchronization method | |
| US20100042715A1 (en) | Method and systems for redundant server automatic failover | |
| US11892922B2 (en) | State management methods, methods for switching between master application server and backup application server, and electronic devices | |
| WO2005039220A1 (en) | Data migration method, system and node | |
| CN108282219B (en) | Long link switching processing method for data communication of vehicle satellite positioning system | |
| US7366156B2 (en) | Context synchronization method in mobile communication system | |
| CN112039966A (en) | Method, program and system for updating online state of client based on ActiveMQ | |
| JP2017536759A (en) | Method and apparatus for self-healing after disconnection of base station | |
| US20040045010A1 (en) | Distributed object controlling method and its carrying out system | |
| CN108924096B (en) | Information synchronization method and device | |
| CN108270876B (en) | Method for realizing proxy server in signal system | |
| CN113904909B (en) | Network environment change self-adaption method and system of distributed agent management system | |
| US20070239872A1 (en) | Network device and information synchronization method thereof | |
| CN117480067A (en) | Electric vehicle charge management and client device | |
| CN1996904A (en) | Implementation method for the alarm collection of the terminal supporting dynamic address | |
| CN115190005B (en) | Redis-based high availability method of double-host system | |
| KR20020052778A (en) | Method for management of memory back up in back up HLR | |
| KR20010065409A (en) | Master machine selecting method in distribution type intelligent network system | |
| CN115809273A (en) | Alarm data acquisition method and device, electronic equipment and storage medium | |
| CN112506696A (en) | Method for preventing request between modules from being lost | |
| CN117714013A (en) | Main and standby double-system communication system | |
| CN111176895A (en) | CDP technology for data storage and data disaster recovery |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |