CN114302499B - ACS and base station exception message processing method based on TR069 protocol - Google Patents
ACS and base station exception message processing method based on TR069 protocol Download PDFInfo
- Publication number
- CN114302499B CN114302499B CN202111533262.0A CN202111533262A CN114302499B CN 114302499 B CN114302499 B CN 114302499B CN 202111533262 A CN202111533262 A CN 202111533262A CN 114302499 B CN114302499 B CN 114302499B
- Authority
- CN
- China
- Prior art keywords
- acs
- cpe
- message
- request
- repeated
- 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
- 238000003672 processing method Methods 0.000 title claims abstract description 7
- 238000000034 method Methods 0.000 claims abstract description 17
- 230000005540 biological transmission Effects 0.000 claims abstract description 11
- 230000008569 process Effects 0.000 claims abstract description 7
- 230000002159 abnormal effect Effects 0.000 claims description 41
- 230000007704 transition Effects 0.000 claims description 29
- 238000012545 processing Methods 0.000 claims description 12
- 239000000344 soap Substances 0.000 claims description 10
- 238000004458 analytical method Methods 0.000 claims description 5
- 230000004044 response Effects 0.000 claims description 3
- 238000004891 communication Methods 0.000 abstract description 12
- 229920006235 chlorinated polyethylene elastomer Polymers 0.000 description 55
- 230000005856 abnormality Effects 0.000 description 9
- 238000004364 calculation method Methods 0.000 description 5
- 230000002452 interceptive effect Effects 0.000 description 4
- 230000003993 interaction Effects 0.000 description 3
- 238000005457 optimization Methods 0.000 description 3
- 238000012423 maintenance Methods 0.000 description 2
- 239000011159 matrix material Substances 0.000 description 2
- 238000012795 verification Methods 0.000 description 2
- 206010010947 Coordination abnormal Diseases 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000000136 cloud-point extraction Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000008030 elimination Effects 0.000 description 1
- 238000003379 elimination reaction Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000008439 repair process Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
An ACS and base station exception message processing method based on TR069 protocol comprises the following steps: when each CPE initiates a primary network connection establishment request to the ACS, the ACS verifies the connection request and judges whether the request sent by the corresponding CPE is repeated or not, and then the connection request is processed and a database is updated according to the judging result; when each CPE sends a message request to the ACS, the ACS judges whether the request sent by the corresponding CPE is repeated or not, and processes the message request and updates a database according to the judging result; the ACS periodically analyzes the probability of subsequent repeated requests sent by each CPE according to the database information. The problem of anomaly in repeated transmission between ACS and 5G base station and the problem of communication pressure between devices due to repeated transmission are often generated by the above-described improvement.
Description
Technical Field
The invention relates to the technical field of abnormal message processing, in particular to an ACS and base station abnormal message processing method based on a TR069 protocol.
Background
Repeated transmission abnormal conditions caused by message interaction backlog and abnormal transmission often occur between ACS and 5G base stations in the current 5G network, and repeated session deduplication problems caused by network abnormality or misoperation also often occur in the transmission process of the TR069 protocol, so that when the 5G base stations and base station equipment are easily interacted, repeated messages are excessive, and the system is blocked or crashed. Therefore, a method for processing abnormal information of ACS and base station based on TR069 protocol is needed, which can perform buffer optimization and anti-duplication processing on the interactive information communication verification mechanism of primary communication between ACS and base station; performing cache optimization on interactive message content of multiple communications between ACS and base station, and performing anti-duplication processing on the message; it is also desirable to predict in advance the likelihood of an abnormal situation occurring at a later stage base station, even if the equipment at which the abnormal base station may occur is modified for repair.
Disclosure of Invention
Aiming at the defects in the prior art, the invention provides an ACS and base station exception message processing method based on a TR069 protocol.
In order to achieve the above purpose, the present invention adopts the following technical scheme:
an ACS and base station exception message processing method based on TR069 protocol comprises the following steps:
When each CPE initiates a primary network connection establishment request to the ACS, the ACS verifies the connection request and judges whether the request sent by the corresponding CPE is repeated or not, and then the connection request is processed and a database is updated according to the judging result;
when each CPE sends a message request to the ACS, the ACS judges whether the request sent by the corresponding CPE is repeated or not, and processes the message request and updates a database according to the judging result;
the ACS periodically analyzes the probability of repeated requests sent by each CPE later according to the database information.
In order to optimize the technical scheme, the specific measures adopted further comprise:
Further, when each CPE initiates a network connection request to the ACS for the first time, the ACS verifies the connection request and determines whether the request sent by the corresponding CPE is repeated, and then processes the connection request and updates the specific content of the database according to the determination result:
When CPE initiates a request for initially establishing network connection to ACS, invoking RPC format command inform+ '0 BOOTSTRAP' in TR069 protocol, and sending request message instruction to ACS;
ACS analyzes the request message instruction to obtain the content of '0 BOOTSTRAP', and then verifies that the corresponding CPE sends a request for initially establishing network connection;
the ACS acquires the url address of the corresponding CPE in the request message and stores the url address and the self-stored cache identifier: the url@0BOOTSTRAP is compared, wherein the cache identity is: the url@0BOOTSTRAP contains the url address of the relevant CPE;
If the url address of the corresponding CPE is not matched with the url address of the relevant CPE in the cache identifier, judging that the corresponding CPE does not send repeated initial network connection establishment requests, and replying a response instruction to the CPE by the ACS to enable the corresponding CPE to be connected with the ACS through cwmp protocols; the ACS acquires url address generation cache identification corresponding to the CPE and stores the url address generation cache identification into an ACS cache;
If the url address of the corresponding CPE is matched with the url address of the related CPE in the cache identifier, judging that the corresponding CPE sends a repeated initial network connection establishment request, and ending the connection session by an ACS reply empty message;
The ACS feeds back the repeated initial network connection establishment request or the initial network connection establishment request normally sent to the database.
Further, when each CPE sends a message request to the ACS, the ACS determines whether the request sent by the corresponding CPE is repeated, and processes the message request and updates the specific content of the database according to the determined result:
when CPE sends a message request to ACS, the message is encapsulated through SOAP package;
The ACS receives and parses the message, obtains EventCode, deviceId two tag values and generates a message identifier: the deviceID@EventCode@0 is then stored in an ACS cache;
If the same message identifier exists in the ACS cache, judging that the message is repeatedly sent, and updating the tail number of the message identifier just generated to be 1, namely the deviceID@EventCode@1; the ACS sends a null message instruction to the CPE to end the message session;
If the same message identifier does not exist in the ACS cache, judging that the message is not repeatedly sent, further normally receiving a message request, and setting the tail number of the message identifier to be 0;
the ACS feeds back the repeated message request or normal message request to the database.
Further, the ACS periodically cleans up the message identifier with the last digit of 1 to release the ACS cache space.
Further, the ACS periodically analyzes the specific content of the probability of repeated sending requests in the later period of each CPE according to the database information:
Defining the conditions of repeatedly sending the initial network connection establishment request and the repeatedly sending message as abnormal, and defining the conditions of normally sending the initial network connection establishment request and the normally sending message as normal;
The ACS acquires the probability a of abnormal conditions, the probability b of normal conditions, the probability c of transition to normal in the next period in the abnormal conditions, the probability d of transition to abnormal in the next period in the abnormal conditions, the probability e of transition to abnormal in the next period in the normal conditions and the probability f of transition to normal in the next period in the normal conditions corresponding to CPE in the previous period through database analysis; wherein a+b=1, c+d=1, e+f=1;
and calculating the probability g=a×d+b×e of abnormal situations of the corresponding CPE in the next period.
The beneficial effects of the invention are as follows:
1. the application has the actual situation of processing the abnormal message twice, once when the abnormal operation of repeated transmission (repeated transmission of the primary connection or repeated transmission of the message) is encountered in daily use, the communication resource is prevented from being wasted through anti-repetition processing. The second time is to store the abnormal operation condition in the database in daily use and predict the fault probability of CPE periodically, so as to effectively find and locate the CPE caused by hidden abnormal reasons to send repeated instructions to ACS, reduce the processing pressure of ACS server and improve the network operation and maintenance efficiency.
2. And a distinguishing number is added at the tail of the message identifier so as to better judge which message identifiers are repeated, facilitate later deletion and increase ACS cache space.
3. By analyzing the RPC method of the interactive information between the ACS and the base station, the problem of repeated session duplication elimination caused by message interaction backlog and abnormal transmission or misoperation in the transmission process of the TR069 protocol is solved fundamentally, the excessive root cause of repeated information under abnormal conditions is solved, the interactive information is smoother, meanwhile, the buffer and identification comprehensive judgment optimization technology is adopted to reduce the message interaction backlog caused by the repeated information between the ACS and the base station, so that the pressure of ACS processing information is reduced, and the ACS communication efficiency is improved.
Drawings
Fig. 1 is a schematic diagram of calculating a next-period failure probability of a CPE according to an embodiment of the present invention.
Detailed Description
The invention will now be described in further detail with reference to the accompanying drawings.
The application mainly comprises the following steps:
Step one, when a CPE (base station) initiates the first establishment of network connection to an ACS through program execution, the CPE calls a command inform+ '0 BOOTSTRAP' in an RPC format of the TR069 protocol, and sends a request instruction to the ACS. After the ACS analyzes the RPC message information and obtains 0BOOTSTRAP in the RPC request message of the Inform, the format of the RPC request message and the cache identification format is as follows: and comparing the url@0BOOTSTRAP of the CPE, and if the url@0BOOTSTRAP is not matched, giving an information response instruction to the CPE by the ACS server, and creating success through cwmp protocol connection. Meanwhile, a buffer identification is generated by the url address of the CPE and the corresponding RPC command inform+ '0 BOOTSTRAP', and the url address and the corresponding RPC command inform+ '0 BOOTSTRAP' are stored in an ACS buffer together. If the matching is successful, the ACS sends an empty request message to the CPE to end the session request. The advantages are that: the method reduces the repeated instruction sent to the ACS by the CPE due to the abnormality, reduces the processing pressure of the ACS server and improves the network operation and maintenance efficiency. It should be noted that the initial connection request may also be sent by mistake and may have been actually connected because of excessive backlog of device information or other external reasons.
Step two, after receiving the RPC request message of successful verification of the ACS, the CPE starts to issue a message to the ACS, the message content is encapsulated by using a SOAP package, and the SOAP comprises XML format data consisting of a SOAP head part and a SOAP body part. And after the ACS receives the message, analyzing the message, obtaining EventCode, deviceId tag values in the SOAP body part of the XML file in the RPC format, generating a message identifier and storing the message identifier in an ACS cache. If the same message identification is in the cache, namely, the deviceID@EventCode@0, the last bit 0 is updated to be 1, meanwhile, if the matching is successful, the message retransmission is comprehensively judged, and the ACS sends a null message instruction to inform the base station equipment of ending the session. Otherwise, the last bit is updated to 0.
Wherein 0 represents that no message identifier is stored in the cache, and 1 represents that the message identifier is stored in the cache.
Step three, refer to fig. 1. The ACS acquires the probability a of abnormal conditions, the probability b of normal conditions, the probability c of transition to normal in the next period in the abnormal conditions, the probability d of transition to abnormal in the next period in the abnormal conditions, the probability e of transition to abnormal in the next period in the normal conditions and the probability f of transition to normal in the next period in the normal conditions corresponding to CPE in the previous period through database analysis; wherein a+b=1, c+d=1, e+f=1;
and calculating the probability g=a×d+b×e of abnormal situations of the corresponding CPE in the next period.
The specific calculation mode of the probability a of the abnormality of the corresponding CPE in the previous period is as follows: the ACS obtains the number of times of abnormality occurrence of the corresponding CPE in the previous period through the database, and divides the number of times of abnormality occurrence by the total number of times of communication of the corresponding CPE in the previous period to obtain the abnormality occurrence probability a of the corresponding CPE.
The specific calculation mode of the probability b of the normal occurrence of the corresponding CPE in the previous period is as follows: the ACS obtains the number of times of occurrence of the normal corresponding CPE in the previous period through the database, and divides the number of times of occurrence of the normal corresponding CPE in the previous period by the total number of times of communication of the corresponding CPE in the previous period to obtain the probability b of occurrence of the normal corresponding CPE.
The specific calculation method of the occurrence probability c (transition probability of the next period) of the next transition to be normal in the abnormal condition in the previous period is as follows: the occurrence probability x (total abnormal condition times/total communication times) of the total abnormal condition in the history (the previous period and the past period) is known through a database; obtaining the occurrence probability a of the abnormal situation in the previous period (the number of times of the abnormal situation in the previous period/the total communication number of times of the previous period) through a historical database; calculating the occurrence probability c of the next transition to normal in the occurrence of an abnormal condition in the previous period, wherein c=s+ (x-a); where s is a threshold value, and since c+d=1, d can be obtained.
For example, the total anomaly probability x=30% =0.3, the last anomaly a=28% =0.28, and the transition to the normal condition is 2% =0.02, and the transition probability c=22% =0.22, and d=1-22% =0.78 is obtained from the 2% +20% (threshold s) of the transition. The threshold s is preset, and a specific threshold is selected for the transition difference value (the difference value is 2% in this example) in different regions, so as to ensure that the transition probability is smaller than 1 and larger than 0.
The specific calculation method of the occurrence probability e (transition probability of the next period) that the next transition to the abnormality in the normal condition occurs in the previous period is as follows: the total normal condition occurrence probability x' (total normal condition times/total communication times) in history (last period and past period) is known through a database; obtaining the occurrence probability b of the normal condition in the previous period (the number of normal conditions in the previous period/the total communication number in the previous period) through a historical database; calculating the occurrence probability e, e=s '+ (x' -b) of the occurrence of the transition to the abnormality next time in the normal condition in the previous period; where s' is a threshold value, since e+f=1, f can be obtained.
For example, the total normal probability x '=70% =0.7, the previous period normal probability b=72% =0.72, and the transition to the anomaly is 2% =0.02, and the transition probability e=32% =0.32, and f=1-32% =0.68 is obtained from the 2% +30% (threshold s') of the transition. Wherein the threshold s' is preset and a specific threshold is selected for the transition difference value (in this case, the difference value is 2%) in different regions, so as to ensure that the transition probability is smaller than 1 and larger than 0.
To sum up, in the next period, the probability g=0.28×0.78+0.72×0.32= 0.4488 of occurrence of abnormality of the corresponding CPE. And the relevant data of other CPEs are obtained by the same method.
The application adopts the idea of a Markov chain algorithm. The Markov transfer matrix method model formula is as follows: x (k+1) =x (k) ×p; x (k) represents a state vector of the trend analysis and prediction object at time t=k, P represents a one-step transition probability matrix, and X (k+1) represents a state vector of the trend analysis and prediction object at time t=k+1.
By the technical scheme, whether the network connection request is established for the first time or not is judged continuously, and whether the message sending judgment is repeated or not is judged continuously, so that the database is updated, the fault probability of the corresponding CPE can be predicted continuously according to the updating and the calculation of the data, and further, the fault probability is found in advance and solved in advance.
With respect to the present application, the explanation of the related concepts is as follows:
ACS: auto-Configuration Server (auto configuration server);
CPE: customer Premise Equipment (user terminal equipment, here CPE, equivalent to a 5G small base station);
CWMP: CPE WAN MANAGEMENT Protocol (user terminal equipment wide area network management Protocol);
RPC: remote Procedure Call (remote procedure call);
SOAP: simple Object Access Protocol (simple object access protocol);
SSL: secure Socket Layer (secure sockets layer);
TLS: transport Layer Security (secure transport layer);
URL: uniform Resource Location (uniform resource location);
XML: extensible Markup Language (extensible markup language).
EventCode: the corresponding TR069 protocol RPC format XML file SOAP body part- > < Event > - > < EventStruct > where the event_code of the Event has a "0BOOTSTRAP", which indicates that the reason for the session initiation is the first installation of the CPE or the URL of the ACS has changed. After the network manager receives the registration flow, the network manager executes the registration flow. 0bootstra may represent a first handshake.
DeviceId: the corresponding TR069 protocol RPC format XML file SOAP body part- > < Event > - > < EventStruct > contains a tag: manufactucer, OUI, productClass (for identifying a product or product type), serialNumber.
It should be noted that the terms like "upper", "lower", "left", "right", "front", "rear", and the like are also used for descriptive purposes only and are not intended to limit the scope of the invention in which the invention may be practiced, but rather the relative relationship of the terms may be altered or modified without materially altering the teachings of the invention.
The above is only a preferred embodiment of the present invention, and the protection scope of the present invention is not limited to the above examples, and all technical solutions belonging to the concept of the present invention belong to the protection scope of the present invention. It should be noted that modifications and adaptations to the invention without departing from the principles thereof are intended to be within the scope of the invention as set forth in the following claims.
Claims (4)
1. The ACS and base station exception message processing method based on the TR069 protocol is characterized by comprising the following steps:
When each CPE initiates a primary network connection establishment request to the ACS, the ACS verifies the connection request and judges whether the request sent by the corresponding CPE is repeated or not, and then the connection request is processed and a database is updated according to the judging result;
when each CPE sends a message request to the ACS, the ACS judges whether the request sent by the corresponding CPE is repeated or not, and processes the message request and updates a database according to the judging result;
the ACS periodically analyzes the probability of repeated transmission requests in the later period of each CPE according to the database information, specifically:
Defining the conditions of repeatedly sending the initial network connection establishment request and the repeatedly sending message as abnormal, and defining the conditions of normally sending the initial network connection establishment request and the normally sending message as normal;
The ACS acquires the probability a of abnormal conditions, the probability b of normal conditions, the probability c of transition to normal in the next period in the abnormal conditions, the probability d of transition to abnormal in the next period in the abnormal conditions, the probability e of transition to abnormal in the next period in the normal conditions and the probability f of transition to normal in the next period in the normal conditions corresponding to CPE in the previous period through database analysis; wherein a+b=1, c+d=1, e+f=1;
and calculating the probability g=a×d+b×e of abnormal situations of the corresponding CPE in the next period.
2. The method for processing abnormal messages between ACS and base station based on TR069 protocol according to claim 1, wherein when each CPE initiates a first network connection establishment request to ACS, ACS verifies the connection request and determines whether the request sent by the corresponding CPE is repeated, and then processes the connection request and updates the specific contents of the database according to the result of the determination:
When CPE initiates a request for initially establishing network connection to ACS, invoking RPC format command inform+ '0 BOOTSTRAP' in TR069 protocol, and sending request message instruction to ACS;
ACS analyzes the request message instruction to obtain the content of '0 BOOTSTRAP', and then verifies that the corresponding CPE sends a request for initially establishing network connection;
the ACS acquires the url address of the corresponding CPE in the request message and stores the url address and the self-stored cache identifier: url@0 BOOTSTRAP, wherein the cache identity: the url@0 BOOTSTRAP contains the url address of the relevant CPE;
If the url address of the corresponding CPE is not matched with the url address of the relevant CPE in the cache identifier, judging that the corresponding CPE does not send repeated initial network connection establishment requests, and replying a response instruction to the CPE by the ACS to enable the corresponding CPE to be connected with the ACS through cwmp protocols; the ACS acquires url address generation cache identification corresponding to the CPE and stores the url address generation cache identification into an ACS cache;
If the url address of the corresponding CPE is matched with the url address of the related CPE in the cache identifier, judging that the corresponding CPE sends a repeated initial network connection establishment request, and ending the connection session by an ACS reply empty message;
The ACS feeds back the repeated initial network connection establishment request or the initial network connection establishment request normally sent to the database.
3. The method for processing abnormal messages between ACS and base station based on TR069 protocol according to claim 1, wherein when each CPE sends a message request to ACS, ACS judges whether the request sent by the corresponding CPE is repeated, and processes the message request and updates the specific contents of the database according to the judged result:
when CPE sends a message request to ACS, the message is encapsulated through SOAP package;
The ACS receives and parses the message, obtains EventCode, deviceId two tag values and generates a message identifier: the deviceID@EventCode@0 is then stored in an ACS cache;
If the same message identifier exists in the ACS cache, judging that the message is repeatedly sent, and updating the tail number of the message identifier just generated to be 1, namely the deviceID@EventCode@1; the ACS sends a null message instruction to the CPE to end the message session;
If the same message identifier does not exist in the ACS cache, judging that the message is not repeatedly sent, further normally receiving a message request, and setting the tail number of the message identifier to be 0;
the ACS feeds back the repeated message request or normal message request to the database.
4. The method for processing abnormal messages between ACS and base station based on TR069 protocol according to claim 3, wherein said ACS periodically cleans up the message identifier with the last digit of 1 to release ACS buffer space.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111533262.0A CN114302499B (en) | 2021-12-15 | 2021-12-15 | ACS and base station exception message processing method based on TR069 protocol |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111533262.0A CN114302499B (en) | 2021-12-15 | 2021-12-15 | ACS and base station exception message processing method based on TR069 protocol |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114302499A CN114302499A (en) | 2022-04-08 |
| CN114302499B true CN114302499B (en) | 2024-04-16 |
Family
ID=80968559
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111533262.0A Active CN114302499B (en) | 2021-12-15 | 2021-12-15 | ACS and base station exception message processing method based on TR069 protocol |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114302499B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115243297B (en) * | 2022-09-20 | 2022-12-13 | 深圳市艾伯通信有限公司 | Base station opening method and system based on TR069 protocol |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1567776A (en) * | 2003-07-10 | 2005-01-19 | 华为技术有限公司 | Method for processing RRC connection request message |
| KR20120126452A (en) * | 2011-05-11 | 2012-11-21 | 주식회사 케이티 | Mobile communication system for protecting duplicated call processing and call processing method |
| CN108848054A (en) * | 2018-05-03 | 2018-11-20 | 京信通信系统（中国）有限公司 | Network device registration method, apparatus, computer equipment and storage medium |
| CN108881209A (en) * | 2018-06-11 | 2018-11-23 | 京信通信系统（中国）有限公司 | Long-range processing method, apparatus and system |
| CN112333202A (en) * | 2020-11-25 | 2021-02-05 | 国网山东省电力公司信息通信公司 | TR069 protocol-based IMS access network equipment remote centralized monitoring method and system |
-
2021
- 2021-12-15 CN CN202111533262.0A patent/CN114302499B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1567776A (en) * | 2003-07-10 | 2005-01-19 | 华为技术有限公司 | Method for processing RRC connection request message |
| KR20120126452A (en) * | 2011-05-11 | 2012-11-21 | 주식회사 케이티 | Mobile communication system for protecting duplicated call processing and call processing method |
| CN108848054A (en) * | 2018-05-03 | 2018-11-20 | 京信通信系统（中国）有限公司 | Network device registration method, apparatus, computer equipment and storage medium |
| CN108881209A (en) * | 2018-06-11 | 2018-11-23 | 京信通信系统（中国）有限公司 | Long-range processing method, apparatus and system |
| CN112333202A (en) * | 2020-11-25 | 2021-02-05 | 国网山东省电力公司信息通信公司 | TR069 protocol-based IMS access network equipment remote centralized monitoring method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114302499A (en) | 2022-04-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101388903B (en) | Mobile enterprise IT standardization management platform | |
| CN112087334B (en) | Alarm root cause analysis method, electronic device and storage medium | |
| CN114302499B (en) | ACS and base station exception message processing method based on TR069 protocol | |
| CN101848107B (en) | SNMP (Simple Network Management Protocol) network element and communication method of SNMP network element and proprietary protocol network element | |
| US20160142247A1 (en) | Local network and method of updating a device in a local network | |
| CN113835911B (en) | Intranet penetration agent method, system, host and computer readable storage medium | |
| US20240012699A1 (en) | Method and Apparatus for Improving Message Processing Efficiency of Flash Channel Controller | |
| CN114297444A (en) | Network fault analysis method based on RESET message | |
| CN108011870B (en) | A kind of remote software online upgrading information automatic identification management method | |
| CN110417876A (en) | Node server and main control device in session method, distributed system | |
| CN110912766B (en) | Communication network multi-plane data consistency checking method | |
| CN114500237B (en) | Communication method and system | |
| CN106936630A (en) | A kind of whole bag upgrade method of many card insert type equipment and upgrade-system | |
| CN113873033B (en) | Intelligent edge computing gateway platform with fault-tolerant function | |
| US20060206593A1 (en) | Use of discovery scanning and method of IP only communication to identify owners and administrators of network attached devices | |
| CN113727138A (en) | HLS intranet source returning method | |
| CN114217932A (en) | Third-party docking exception handling method and system | |
| CN111314448B (en) | Data communication system and method adapted based on CPA field protection | |
| WO2016176910A1 (en) | Tr-069 message processing method and apparatus | |
| CN111478941A (en) | Mock automatic operation method and device, computer equipment and storage medium | |
| WO2024037345A1 (en) | Fault processing method and apparatus, and storage medium | |
| WO2021259286A1 (en) | Slice service processing method and apparatus, network device, and readable storage medium | |
| CN109361779A (en) | The management method of domain name and system, node server in distributed system | |
| CN112565403B (en) | Application node self-isolation method and device and electronic equipment | |
| CN109218052A (en) | Network management, device, system, storage medium and computer equipment |
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 |