CN112910884B - Method for realizing interaction between APK and ACS through packaging TR069 message - Google Patents
Method for realizing interaction between APK and ACS through packaging TR069 message Download PDFInfo
- Publication number
- CN112910884B CN112910884B CN202110122248.5A CN202110122248A CN112910884B CN 112910884 B CN112910884 B CN 112910884B CN 202110122248 A CN202110122248 A CN 202110122248A CN 112910884 B CN112910884 B CN 112910884B
- Authority
- CN
- China
- Prior art keywords
- apk
- acs
- equipment
- terminal
- message
- 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
- 238000000034 method Methods 0.000 title claims abstract description 127
- 230000003993 interaction Effects 0.000 title claims description 38
- 238000004806 packaging method and process Methods 0.000 title claims description 10
- 238000004891 communication Methods 0.000 claims abstract description 32
- 230000002452 interceptive effect Effects 0.000 claims abstract description 20
- 230000007246 mechanism Effects 0.000 claims abstract description 18
- 230000008569 process Effects 0.000 claims description 43
- 238000012545 processing Methods 0.000 claims description 25
- 230000006870 function Effects 0.000 claims description 20
- 238000012544 monitoring process Methods 0.000 claims description 9
- 238000003745 diagnosis Methods 0.000 claims description 8
- 230000004044 response Effects 0.000 claims description 8
- 230000008859 change Effects 0.000 claims description 6
- 230000001960 triggered effect Effects 0.000 claims description 5
- 238000012536 packaging technology Methods 0.000 claims description 3
- 238000005538 encapsulation Methods 0.000 abstract description 4
- 238000007726 management method Methods 0.000 description 66
- 238000010586 diagram Methods 0.000 description 14
- 239000011230 binding agent Substances 0.000 description 8
- 239000003795 chemical substances by application Substances 0.000 description 7
- 238000012360 testing method Methods 0.000 description 6
- 239000000344 soap Substances 0.000 description 4
- 238000011161 development Methods 0.000 description 3
- 230000007547 defect Effects 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 238000009434 installation Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- FFBHFFJDDLITSX-UHFFFAOYSA-N benzyl N-[2-hydroxy-4-(3-oxomorpholin-4-yl)phenyl]carbamate Chemical compound OC1=C(NC(=O)OCC2=CC=CC=C2)C=CC(=C1)N1CCOCC1=O FFBHFFJDDLITSX-UHFFFAOYSA-N 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 239000000463 material Substances 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 238000013024 troubleshooting Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/26—Special purpose or proprietary protocols or architectures
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/133—Protocols for remote procedure calls [RPC]
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computing Systems (AREA)
- Computer Security & Cryptography (AREA)
- Computer And Data Communications (AREA)
Abstract
The utility model provides a realize interactive method of APK and ACS through encapsulation TR069 message, TR069 is application layer network management technical protocol, APK is the tall and erect application of ann end, the ACS is the automatic configuration server side, in APK end and ACS end, APK is encapsulated into TR069 message in the APK end, the APK end includes APK customer end and APK server side, the ACS end passes through the APK customer end with AIDL communication mechanism between the APK server side calls the RPC method of APK server side by the encapsulation of TR069 protocol realizes the unified management to APK terminal equipment on the application software layer.
Description
Technical Field
The invention relates to the technical field of APK management supporting installation of terminal equipment of a communication android system, in particular to a method for realizing interaction of APK and ACS by packaging TR069 messages, wherein TR069 is an application layer network management technical protocol, APK is an android application end, ACS is an automatic configuration server end, APK in the APK end is packaged into TR069 messages in the APK end and the ACS end, the APK end comprises an APK client and an APK server end, and the ACS end calls an RPC method packaged by the TR069 protocol of the APK server end through an AIDL communication mechanism between the APK client and the APK server end to realize unified management of the APK terminal equipment in an application software layer.
Background
TR069 is fully called CPE WAN management Protocol, namely a peripheral terminal management Protocol, and APK is fully called Android Package, namely Android system application. With the great development of home networks, a plurality of services such as home broadband, IPTV, IMS voice and the like are continuously online in China, the home broadband network is obviously increased, and the terminal management ACS adopts a TR069 protocol to remotely and centrally manage user end equipment such as a gateway, a router, terminal equipment and the like in the home network from a network side. In the framework defined by TR069, two types of logical devices are mainly included, namely, managed user equipment and an administration server (ACS), in a home network environment, devices that need to be configured and managed from the network side are generally devices directly related to an operator service, such as a home gateway, a terminal device, a router, an IP phone terminal, and the like. And all the configuration, diagnosis, upgrade and other work related to the user equipment are completed by the unified management server ACS.
For the user equipment, the TR069 mainly performs the following four operations: one is automatic configuration of user equipment and dynamic service configuration. For the ACS, each user equipment may mark itself in the protocol (for example, model, version, etc.), and according to a settable rule, the ACS may issue a configuration to a certain specific user equipment, or may issue a configuration to a certain group of user equipments. The CPE can automatically request the configuration information in the ACS after the startup, and the ACS can also actively initiate the configuration at any required time. The function of zero configuration installation of the user equipment can be realized through the function, or the dynamic change of the service parameters can be controlled from the network side. And secondly, managing software and firmware of the user equipment. The protocol of TR-069 provides the functionality of managing and downloading software, firmware in a user equipment. The ACS may recognize the version number of the user equipment, decide whether to remotely update the software version of the user equipment, and know whether to succeed after the update is completed. For example, when the user equipment needs to load new software to realize a new service function, or when the current software has bugs which must be repaired, remote management upgrading of the user equipment can be realized through the function. And thirdly, monitoring the state and the performance of the user equipment. TR069 defines a means for the ACS to monitor the status and performance of the user equipment. The method comprises a plurality of general performance parameters which can reflect the working state of the current user equipment. In addition, standard syntax is provided and the operator can define additional parameters. And fourthly, diagnosing the communication fault. TR-069 also defines the capability of the user terminal to self-diagnose and report, for example, under the indication of ACS, the user terminal can check the connectivity, bandwidth, etc. between the user terminal and the network service providing point by ping or other means, and the detection result is returned to ACS. Therefore, the operator can simply position the equipment fault declared by the user through remote operation and correspondingly process the equipment fault.
Through the development of the TR069 protocol, the invention is based on the TR069 protocol and encapsulated into an APK mode in the terminal equipment, thereby realizing the service configuration, remote operation, rom upgrade, parameter acquisition, performance monitoring, equipment log collection and fault information matching of the terminal. The above implementation modes are communicated with each other through apk plus a bottom application API interface and an AIDL self-development protocol. The terminal equipment manufacturers are numerous, and the terminal equipment is managed through a TR069 protocol, so that the terminal equipment manufacturers are required to be matched with each other vigorously; the TR069 message is packaged by a general APK, so that interaction with terminal management ACS is realized, and the management of the terminal is completed; the APK is adapted to terminal equipment manufacturers, and only the APK is required to be installed into terminal equipment of each manufacturer, and then network access is carried out, so that terminal management can be achieved.
The Service of the APK can use the NaNoHttpd as a Tomcat server for the self-initiating Service to receive Http requests from the TR 069. OkHttp sends a request to the ACS to realize Http intercommunication between TR069 and Apk in CPE. The interactive RPC of data between intercommunications packages the xml format of the soap, the CPE client acquires interface data of the CPE server and data of a callback interface through the AIDL interface, an Inform message in the RPC format is packaged to the ACS, the ACS returns corresponding reply information through the Inform information, the online condition of the CPE terminal is judged, and if the information is online, a corresponding instruction can be issued to control the CPE terminal. The CPE terminal analyzes the instruction, calls an instruction interface of the server, returns corresponding data, and displays the data by the page, thereby completing the interactive process completed once and realizing the interaction between the CPE terminal and the ACS information.
The CPE equipment manufacturers to be managed by each large operator are numerous, software versions, models and the like are different, unified management cannot be realized in the existing terminal management mode, when the terminal function of the terminal equipment is changed, the manufacturers are required to cooperate with modification and debugging, then version upgrading is carried out, the debugging and upgrading period is long, APK application management terminal equipment supporting a TR069 protocol is not introduced, and a remote management protocol of installing TR069-APK in the terminal equipment is not introduced. The prior art has the following defects: 1) The terminal information is configured in a manual mode, manual configuration is slow, and data are inaccurate. 2) The data information of the terminals cannot be managed and configured in a unified mode, and the inventor thinks that the unified management and the data configuration information operation can be realized by supporting a TR069 protocol through the APK. 3) Manual single equipment configuration and fault diagnosis increase the cost of manpower and material resources and take a long time. 4) The inventor thinks that unified management, configuration and fault diagnosis capability can be realized by installing the APK application supporting TR069 on the terminal equipment, and the problem that the terminal which cannot be manually configured and managed carries out automatic comparison check sum zero configuration is solved.
Disclosure of Invention
Aiming at the defects or shortcomings in the prior art, the invention provides a method for realizing interaction between an APK and an ACS (auto configuration server) by packaging a TR069 message, wherein the TR069 is an application layer network management technical protocol, the APK is an android application end, the ACS is an automatic configuration server, APK in the APK end is packaged into the TR069 message in the APK end and the ACS end, the APK end comprises an APK client and an APK server, and the ACS end calls an RPC method packaged by the TR069 protocol of the APK server through an AIDL (aid message handling) communication mechanism between the APK client and the APK server to realize unified management on APK terminal equipment in an application software layer.
The technical solution of the invention is as follows:
the utility model provides a realize APK and ACS interactive method through encapsulation TR069 message which characterized in that, includes APK end and ACS end, APK is packaged into TR069 message in the APK end, the APK end includes APK customer end and APK service end, the ACS end passes through the APK customer end with AIDL communication mechanism between the APK service end calls the RPC method of APK service end by TR069 agreement realizes the unified management to APK terminal equipment at the application software layer.
The unified management includes a combination of one or more of: information acquisition, parameter configuration, performance monitoring, performance alarm and fault diagnosis.
The method comprises the steps of automatically identifying the terminal equipment report management request INFORM message through a TR069 message packaging technology, automatically establishing a terminal equipment registration authentication flow, realizing unified authentication management of the terminal equipment by utilizing a TR069 protocol, and analyzing and injecting the INFORM message in the flow by an RPC method through interaction between ACS and APK, so that the terminal terminals of different terminal equipment of an operator can be subjected to classified management.
The method comprises the steps of realizing interaction between the ACS and the terminal equipment through an AIDL interface; the method comprises the steps that APK application packaged as TR069 information is installed on terminal equipment, and the terminal equipment and ACS are registered and authenticated; the existing TR069 protocol is utilized to be packaged into an effective RPC method, so that all function acquisition information interaction of the terminal equipment is realized; and calling a communication protocol between the ACS and the APK to realize management and service processing of the terminal equipment or management application of 5G interconnection.
The method comprises a logic call processing flow for realizing the interaction of the APK and the ACS among the ACS, the APK client and the APK server, wherein the logic call processing flow comprises the following steps: step A1, an ACS initiates an interactive process with an APK, and the ACS issues a command aiming at a specified terminal to an APK client side which packages the APK into a TR069 message; step A2, the APK client receives the command of the ACS and then calls an RPC method of the APK server by using an AIDL communication mechanism to transmit the command to the APK server; step A3, the APK server executes the command to operate the appointed terminal, and returns an execution result to the APK client by using an AIDL communication mechanism; step A4, the APK client reports an execution result to the ACS by adopting a TR069 protocol; and step A5, the ACS finishes the flow.
The ACS and APK interactive connection process comprises the following steps: step B1, ACS initiates Http connection to APK; step B2, APK returns 200 representing connection OK or 204 representing connection failure; step B3, the APK reports the connection request of the terminal restart; step B4, the ACS returns a request reply of the terminal restarting; step B5, the APK sends an empty packet to the ACS; step B6, the ACS issues an instruction to the APK; step B7, the APK sends an instruction reply to the ACS; and 8, sending a null packet to the APK by the ACS to end the interactive connection process.
The method comprises the following steps of a starting-up information reporting flow between an APK and an ACS: step C1, APK equipment is accessed to the ACS for the first time, or the flow is triggered when the APK equipment is restarted; step C2, ACS replies the message; step C3, the ACS issues the STUN server parameter; c4, the APK equipment replies a parameter setting result; step C5, the APK equipment sends UDP heartbeat; c6, the ACS replies BIND RESPONSE and takes the external UDP ConnectAddress of the equipment; step C7, APK equipment reports 4VALUE CHANGE and carries NATDelected and UDPConnectionRequestAddress; and C8, the ACS replies the message and stores the STUN information reported by the equipment in a storage mode.
The method comprises the following steps of adopting a device state refreshing flow between the APK and the ACS: step D1, ACS sends UDP request to APK equipment; d2, returning 6CONNECTION REQUEST by the APK equipment; d3, the ACS replies an inform response; d4, sending a GetRPCSmethods acquisition equipment support method by the ACS; step D5, the APK equipment replies to GetRPMethodsResponse.
The ACS sends a business operation flow to the APK by adopting the following steps: step E1, the ACS sends a UDP request to the APK; step E2, the APK equipment reports 6CONNECTION REQUEST; step E3, ACS replies the message; step E4, the ACS issues RESULT =2, which indicates that the service is ready to be issued; step E5, the APK equipment replies to SetParameterValueResponse; step E6, the ACS sends a UDP request; step E7, the APK equipment reports 6CONNECTION REQUEST; step E8, ACS replies the message; step E9, the ACS issues service parameters; step E10, the APK equipment replies SetParameterValueResponse; step E11, the ACS sends a UDP request; step E12, the APK equipment reports 6CONNECTION REQUEST; step E13, the ACS issues RESULT =0, which indicates that the service is successfully issued; step E14, the APK device replies to SetParameterValuesResponse.
The invention has the following technical effects: the invention relates to a method for realizing interaction between APK and ACS by packaging TR069 messages, which can be used for installing APK applications supporting TR069 on terminal equipment to automatically realize unified management, realizing automatic discovery of a terminal through a TR069 template, automatically allocating hardware versions of terminal model software versions to perform warehousing processing, performing auditing operation on the warehoused equipment, performing TR069 message packaging on the terminal to butt the APK of the terminal after the completion of the execution, realizing remote operation on the terminal equipment, performing service zero configuration on the equipment, performing remote fault processing on the equipment, realizing remote packet capturing processing on the terminal through the TR069 message, analyzing information data of the terminal INFORM message, performing comparison processing and returning equipment authentication interaction, thereby effectively improving the management number and zero configuration quality of the terminal equipment.
The invention can realize the following characteristics: (1) The AIDL is realized by installing an apk packaged into TR069 by a terminal, and a bridge is erected between the client of the process A and the server of the process B by the Binder and the Service Manager of the system kernel, so that the client can obtain an agent of the server, and the method defined by the server is called by the agent, thereby achieving the purpose of inter-process communication. (2) Through the TR069 protocol unified management terminal of AIDL, the registered terminals are automatically identified and classified, and the method is quicker and more accurate than manual processing. (3) By means of the method for packaging TR069 messages through APK, automatic authentication interaction on the terminal can be achieved, and service and remote operation results can be rapidly issued. (4) By constructing an RPC method passed by TR069, the management terminal is wide and the service processing capacity is strong. (5) By automatically discovering and managing after establishing the terminal management authentication flow, unified management of terminal equipment and automatic service zero configuration without manual intervention are realized. (6) The management of the terminal is interactively completed with a terminal management system through the APK and the AIDL, the terminal equipment which is connected to the network only needs to download the latest version to be installed in a shop, if the function is updated, only the APK needs to be updated, time-consuming projects such as version upgrading of the terminal equipment in the whole network are avoided, and projects such as version upgrading of the terminal equipment needing a plurality of terminal equipment manufacturers to cooperate with debugging and modifying functions are avoided.
Drawings
FIG. 1 is a schematic diagram of a logic call processing flow involved in implementing a method for implementing interaction between an APK and an ACS by encapsulating a TR069 message. Fig. 1 includes three main bodies for executing an APK and ACS interactive process or interactive software, that is, an ACS (Automatic configuration server), an APK client (client APP, APK, android Package, android application), and an APK server (server APP). Fig. 1 includes the following steps: step 1, the ACS initiates an interactive process with the APK, and the ACS issues a command (adopting a TR069 protocol) aiming at a specified terminal to an APK client which packages the APK into a TR069 (Technical Report069 protocol) message; step 2, the APK client receives the command of the ACS and then transfers the command to the APK server by using an AIDL (Android Interface definition language) communication mechanism to Call an RPC (Remote Procedure Call Protocol) method of the APK server; step 3, the APK server executes the command to operate the appointed terminal, and returns an execution result to the APK client by using an AIDL communication mechanism; step 4, the APK client reports an execution result to the ACS by adopting a TR069 protocol; and 5, the ACS finishes the interactive flow.
Fig. 2 is a schematic diagram of the aid dl communication mechanism referred to in fig. 1. Fig. 2 includes that a process a and a process B communicate with each other through a Linux kernel process (Binder driver) and a Service Manager process (Service Manager), wherein an aid l establishes a "bridge" between a client of the process a and a server of the process B through the Binder and the Service Manager of the system kernel, so that the client can obtain an agent of the server, and a method defined by the server is called through the agent, thereby achieving an inter-process communication purpose. The Client in the process A is connected with the Proxy through the Manager, the Proxy is connected with the Binder driver in the Linux kernel process, the Binder driver is connected with the Service Manager in the Service Manager process, and the Service in the process B is connected with the Service Manager through the Stub.
FIG. 3 is a diagram illustrating the relationship between an operating system and a process. In FIG. 3, process 1 and process 2 are included, entering the System respectively.
Fig. 4 is a schematic diagram of the ACS and APK interconnection flow. FIG. 4 includes step 1, ACS initiates Http connection to APK; step 2, APK returns to 200 (connection OK) or 204 (connection failure); step 3, APK reports 6 (terminal restart) connection request; step 4, the ACS returns to the request reply of 6 (terminal restart); step 5, APK sends an empty packet to ACS; step 6, the ACS issues an instruction to the APK; step 7, the APK sends an instruction reply to the ACS; and 8, sending an empty packet to the APK by the ACS to finish the interactive connection process.
Fig. 5 is a schematic diagram illustrating a process of reporting boot information between an APK and an ACS. Fig. 5 includes step 1, where the APK device first accesses the ACS, or when the APK device is restarted, the process is triggered (the device reports 0BOOT or 1BOOT, for example, the device reports 0BOOT for the first time); step 2, ACS replies the message (for example, the platform replies InformResponse); step 3, sending the STUN server parameters by the ACS; step 4, the APK device replies the result of the setting parameters (the device replies SetParameterValueResponse); step 5, the APK equipment sends UDP heartbeat (the equipment initiates UDP BIND RESQUEST); 6, the ACS replies BIND RESPONSE and carries the external UDP ConnectAddress of the equipment; step 7, APK equipment reports 4VALUE CHANGE and carries NATDelected and UDPConnectionRequestAddress; and 8, ACS replies a message (platform replies InformResponse), and the STUN information reported by the equipment is stored in a database.
FIG. 6 is a flow diagram illustrating a device state refresh between an APK and an ACS. FIG. 6 includes step 1, ACS sends UDP request to APK device; step 2, returning 6CONNECTION REQUEST by APK equipment; step 3, the ACS replies InformResponse; step 4, an ACS issues a GetRPCSmethods (method for acquiring equipment support); step 5, APK equipment replies to GetRPCSMethodsResponse.
Fig. 7 is a schematic diagram of the operation flow of ACS issuing service to APK. FIG. 7 includes step 1, ACS sends UDP request to APK; step 2, the APK equipment reports 6CONNECTION REQUEST; step 3, ACS reply message (InformResponse); step 4, ACS issues RESULT =2, which indicates that the service is ready to be issued; step 5, the APK equipment replies SetParameterValueResponse; step 6, the ACS sends a UDP request; step 7, APK equipment reports 6CONNECTION REQUEST; step 8, ACS reply message (InformResponse); step 9, ACS sends down service parameters (voice parameters); step 10, the APK equipment replies SetParameterValueResponse; step 11, ACS sends UDP request; step 12, APK equipment reports 6CONNECTION REQUEST; step 13, the acs issues RESULT =0, which indicates that the service is successfully issued; step 14, apk device replies SetParameterValuesResponse.
Detailed Description
The invention is described below with reference to the figures (fig. 1-7) and examples.
Fig. 1 is a schematic diagram of a logic call processing flow involved in implementing a method for implementing the interaction between an APK and an ACS by encapsulating a TR069 message according to the present invention. Fig. 2 is a schematic diagram of the aid dl communication mechanism referred to in fig. 1. FIG. 3 is a diagram illustrating the relationship between an operating system and a process. Fig. 4 is a schematic diagram of ACS and APK interconnection flow. Fig. 5 is a schematic diagram illustrating a process of reporting boot information between an APK and an ACS. FIG. 6 is a flow diagram illustrating a device state refresh between an APK and an ACS. Fig. 7 is a schematic diagram of the operation flow of ACS issuing service to APK. Referring to fig. 1 to 7, a method for realizing interaction between APK and ACS by encapsulating TR069 messages, comprising an APK terminal and an ACS terminal, wherein the APK is encapsulated as TR069 messages in the APK terminal, the APK terminal comprises an APK client and an APK server, the ACS terminal passes through the APK client and an aid communication mechanism between the APK servers calls an RPC method encapsulated by a TR069 protocol of the APK server to realize unified management of APK terminal equipment on an application software layer. The unified management includes a combination of one or more of: information acquisition, parameter configuration, performance monitoring, performance alarm and fault diagnosis. The management request INFORM message reported by the terminal equipment is automatically identified by a TR069 message packaging technology, the terminal equipment registration authentication flow is automatically established, the unified authentication management of the terminal equipment is realized by utilizing a TR069 protocol, and the information message in the flow is analyzed and injected by an RPC method through the interaction between the ACS and the APK, so that the classified management of the terminal terminals of manufacturers, numbers, types, software versions and hardware versions of different terminal equipment of an operator is met. The method comprises the steps of realizing interaction between the ACS and the terminal equipment through an AIDL interface; the method comprises the steps that APK application packaged as TR069 information is installed on terminal equipment, and the terminal equipment and ACS are registered and authenticated; the existing TR069 protocol is utilized to be packaged into an effective RPC method, so that all function acquisition information interaction of the terminal equipment is realized; and calling a communication protocol between the ACS and the APK to realize management and service processing of the terminal equipment or management application of 5G interconnection.
The method comprises a logic call processing flow for realizing the interaction of the APK and the ACS among the ACS, the APK client and the APK server, wherein the logic call processing flow comprises the following steps: step A1, an ACS initiates an interactive process with an APK, and the ACS issues a command aiming at a specified terminal to an APK client side which packages the APK into a TR069 message; step A2, the APK client receives the command of the ACS and then calls an RPC method of the APK server by using an AIDL communication mechanism to transmit the command to the APK server; step A3, the APK server executes the command to operate the appointed terminal, and returns an execution result to the APK client by using an AIDL communication mechanism; step A4, the APK client reports an execution result to the ACS by adopting a TR069 protocol; and step A5, the ACS finishes the flow. The ACS and APK interactive connection process comprises the following steps: step B1, ACS initiates Http connection to APK; step B2, APK returns 200 representing connection OK or 204 representing connection failure; step B3, the APK reports the connection request of the terminal restart; step B4, the ACS returns a request reply of the terminal restart; step B5, the APK sends an empty packet to the ACS; step B6, the ACS issues an instruction to the APK; step B7, the APK sends an instruction reply to the ACS; and 8, sending a null packet to the APK by the ACS to end the interactive connection process. The method comprises the following steps of a starting-up information reporting flow between an APK and an ACS: step C1, APK equipment is accessed to the ACS for the first time, or the flow is triggered when the APK equipment is restarted; step C2, ACS replies the message; step C3, the ACS issues the STUN server parameter; c4, the APK equipment replies a parameter setting result; step C5, the APK equipment sends UDP heartbeat; c6, the ACS replies BIND RESPONSE and takes the external UDP ConnectAddress of the equipment; step C7, APK equipment reports 4VALUE CHANGE and carries NATDelected and UDPConnectionRequestAddress; and C8, the ACS replies the message and stores the STUN information reported by the equipment in a storage mode. The method comprises the following steps of refreshing the device state between the APK and the ACS: step D1, ACS sends UDP request to APK equipment; d2, returning 6CONNECTION REQUEST by the APK equipment; d3, the ACS replies an inform response; d4, sending a GetRPCHouds acquisition device support method by the ACS; at step D5, the APK device replies getpcmethodresponse. The ACS sends a business operation flow to the APK by adopting the following steps: step E1, the ACS sends a UDP request to the APK; step E2, the APK equipment reports 6CONNECTION REQUEST; step E3, ACS replies the message; step E4, the ACS issues RESULT =2, which indicates that the service is ready to be issued; step E5, the APK equipment replies SetParameterValueResponse; step E6, the ACS sends a UDP request; step E7, the APK equipment reports 6CONNECTION REQUEST; step E8, ACS replies the message; step E9, the ACS issues service parameters; step E10, the APK equipment replies to SetParameterValueResponse; step E11, the ACS sends a UDP request; step E12, the APK equipment reports 6CONNECTION REQUEST; step E13, the ACS issues RESULT =0, which indicates that the service is successfully issued; step E14, the APK device replies to SetParameterValuesResponse.
A method for interacting with a terminal management system by using APK package TR069 information automatically identifies the INFORM information reported by a terminal through a package TR069 information technology, automatically establishes an equipment registration authentication flow, realizes unified authentication management of the terminal by using a TR069 protocol, and analyzes and injects the INFORM information in the flow by an RPC method through interaction between ACS and APK. The terminal terminals of different terminal manufacturers, operating numbers, types, software versions and hardware versions of operators are managed in a classified mode, and an automatic function is achieved.
The management of the terminal is interactively completed with a terminal management system through the APK and the AIDL, the terminal equipment which is connected to the network only needs to download the latest version to be installed in a shop, if the function is updated, only the APK needs to be updated, time-consuming projects such as version upgrading of the terminal equipment in the whole network are avoided, and projects such as version upgrading of the terminal equipment needing a plurality of terminal equipment manufacturers to cooperate with debugging and modifying functions are avoided.
The Service of the APK can use the NaNoHttpd as a Tomcat server for the self-start Service to receive an Http request from TR 069. OkHttp sends a request to the ACS to realize the Http intercommunication between TR069 and Apk in CPE. The interactive RPC of the data between the intercommunications is packaged in the xml format of the soap, the CPE client side obtains interface data of the CPE server and data of the callback interface through the AIDL interface, the Inform message in the RPC format is packaged to the ACS, the ACS returns corresponding reply information through the info information, the online condition of the CPE terminal is judged, and if the information is online, a corresponding instruction can be issued to control the CPE terminal. The CPE terminal analyzes the instruction, calls an instruction interface of the server, returns corresponding data, and displays the data by the page, thereby completing the interactive process completed once and realizing the interaction between the CPE terminal and the ACS information.
The invention relates to calling an external tool comprising: (1) OkHttp tool: HTTP is a way for modern application networks. As a way of exchanging data and media. Efficient execution of HTTP can make transport content loading faster and save bandwidth; the APK acquires the basic information of the box and the data information returned by the operation through the AIDL interface, packages the basic information and the data information into a SOAP format, sends the SOAP format to the ACS in the form of an Inform through the OkHttp, and the ACS replies the APK through the Inform response, so that the purpose of information interaction is achieved. (2) NanoHTTPD tool: the NanoHttpd only realizes the simplest and most common functions as a light-weight HttpServer. Embedding the NanoHttpd into the APK as a server, receiving an HTTP request from the ACS, and interacting strictly according to an RPC method of TR 069. (3) protocol flow: the interaction of information between the ACS and the CPE is mainly completed. (4) use of UDP protocol in APK: the APK acquires UDP request information from the ACS through UDP, analyzes a request head and a request body, sends UDP information to reply the ACS after finishing checking data, and sends a corresponding instruction to the ACS through OkHttp to finish information interaction.
The invention is to install APK application supporting TR069 on terminal equipment, automatically realize unified management, realize terminal automatic discovery through a TR069 template, automatically allocate terminal model software version hardware version to carry out warehousing processing, carry out auditing operation on warehoused equipment, carry out TR069 message encapsulation on a terminal to dock APK of the terminal after the execution is finished, realize remote operation on the terminal equipment, carry out service zero configuration on the equipment, carry out remote fault processing on the equipment, realize remote packet capturing processing on the terminal through the TR069 message, analyze information data of an INFORM message of the terminal, and carry out comparison processing and return connection equipment authentication interaction. Therefore, the management quantity and the zero configuration quality of the terminal equipment are effectively improved.
A method for interacting with a terminal management system through APK packaging TR069 information is characterized in that a registered terminal is automatically identified and authenticated through a TR069 technical period, the hardware version of a software version of a terminal manufacturer model is automatically identified and classified, and channel information for carrying out safe automatic configuration management on CPE by an ACS (automatic configuration server) is established by utilizing terminal remote management based on a TR069 protocol. The method mainly realizes the functions of information acquisition, parameter configuration, performance monitoring, performance alarm and fault diagnosis of the terminal equipment.
The CPE realizes a terminal remote management function in an application software layer, wherein the terminal remote management APP realizes a TR069 protocol and receives and executes a service instruction issued by an ACS server; and the terminal remote management agent APP provides required bottom system functions for the client through an AIDL communication mechanism.
A bridge is erected between the client of the process A and the server of the process B by using the AIDL through the Binder and the Service Manager of the system kernel, so that the client can obtain an agent of the server, and the method defined by the server is called through the agent, thereby achieving the purpose of inter-process communication, and realizing the communication between the CPE and the ACS to achieve the unified authentication and management of the terminal.
The ACS issues instructions to the designated CPE through the ACS. And the CPE client APP receives the ACS instruction and calls a tr069 protocol-encapsulated RPC method of the server APP through AIDL. And the server side APP executes the command operation and returns an execution success result to the client side APP. And the client APP reports the result to the ACS, and the process is ended.
And the APK package TR069 protocol message is used for interacting with a terminal management system to complete the unified management, unified authentication, unified zero configuration and remote fault diagnosis processing capability of the terminal. The method is characterized in that the specific embodiment of the invention partially describes a full-automatic unified management authentication flow method for realizing terminal management.
According to the application, the AIDL is achieved through the fact that the terminal is provided with the apk packaged as TR069, a bridge is erected between the client side of the process A and the server side of the process B through the Binder and the Service Manager of the system kernel, the client side can obtain a proxy of the server side, and the method defined by the server side is called through the proxy, so that the purpose of inter-process communication is achieved.
According to the application proposal, the TR069 protocol of AIDL is used for uniformly managing the terminals, automatically identifying the registered terminals and classifying the registered terminals, so that the method is quicker and more accurate than manual processing.
According to the application proposal, the automatic authentication interaction of the terminal can be rapidly issued with the service and remote operation results by the method of packaging TR069 messages by APK.
According to the application proposal, by constructing an RPC method passed by TR069, the management terminal is wide and the service processing capacity is strong.
According to the proposal, the unified management of the terminal equipment and the automatic service zero configuration without manual intervention are realized by automatically discovering and managing after establishing the terminal management authentication flow.
The management of the terminal is interactively completed with a terminal management system through the APK and the AIDL, the terminal equipment which is connected to the network only needs to download the latest version to be installed in a shop, if the function is updated, only the APK needs to be updated, time-consuming projects such as version upgrading of the terminal equipment in the whole network are avoided, and projects such as version upgrading of the terminal equipment needing a plurality of terminal equipment manufacturers to cooperate with debugging and modifying functions are avoided.
1.1, aid dl communication mechanism referring to fig. 2 and fig. 3: in the android system, an AIDL is used to define a programming interface which is approved when a client and a service use inter-process communication (IPC) communicate with each other. On Android, one process typically cannot access the memory of another process. A process needs to break down its objects into primitives that the operating system can recognize and group the objects into objects that cross boundaries. Writing code to perform this grouping operation is a tedious task, so Android uses AIDL to implement inter-process communication of different applications APP. The AIDL builds a bridge between the client of the process A and the server of the process B through the Binder and the Service Manager of the system kernel, so that the client can obtain a proxy of the server, and the proxy calls the method defined by the server, thereby achieving the purpose of inter-process communication.
1.2, aid service scenario example referring to fig. 1, restart of a remote terminal device is a typical application scenario in daily operation and maintenance, and is often used for a service center to assist a user in remote troubleshooting. And (I) the telephone operator service issues an instruction to the appointed terminal equipment through the ACS. And (II) the client APP of the terminal equipment receives the ACS instruction and calls the RPC method of the server APP through the AIDL. And thirdly, the server side APP executes the terminal equipment operation command and returns an execution success result to the client side APP. And (IV) the client APP reports the result to the ACS, and the process is ended.
1.3, the AIDL is used in the APK, and the information acquisition and operation of the terminal are realized mainly through the AIDL interface design. The interface for acquiring information comprises: acquiring manufacturer information; (II) acquiring a unique manufacturer identifier; (III) acquiring the product type; (IV) acquiring a serial number; (V) acquiring the current time (NTP synchronization); (VI) acquiring device description and copyright statement (defining different types); (VII) acquiring a model name; (eighth), acquiring a boot time stamp of the time; (nine) acquiring the date and time of first use; tenth, acquiring a hardware version of the terminal equipment; acquiring a software version of the terminal equipment; twelfth, acquiring additional hardware version information of the terminal equipment; (thirteen) acquiring additional software version information of the terminal equipment; (fourteen) acquiring an NTP server; (fifteen) acquiring a DNS server address; (sixteen) acquiring the WLAN network interface distribution address type; (seventeen) acquiring the type of the address allocated by the LAN network interface; (eighteen) acquiring a LAN IP address; (nineteenth) obtaining a WLAN IP address; (twenty) acquiring a Lan MAC address; (twenty-one) acquiring a WLan MAC address; (twenty two) acquiring a Bluetooth device MAC address; (twenty three), acquiring a user account; (twenty-four) obtaining a card number; (twenty five) acquiring the DRMkeyid; (twenty six) acquiring a service authentication URL; (twenty seven) acquiring a TR069 network management URL; (twenty eight) acquiring a portal address; (twenty-nine) acquiring television-related information; (thirty) acquiring the SOC temperature; (thirty-one) obtains a running program list. The following functional operation interfaces may also be included: (thirty-two) restart; (thirty-three) factory settings are restored; (thirty-four) setting terminal equipment information; (thirty-five) acquiring a zero configuration state; (thirty-six) setting a zero configuration state; (thirty-seven) setting the designated network interface information; (thirty-eight) download upgrade files (unused); (forty) installing an upgrade file; (forty one) intercepting the current screen; (forty two) deleting the file; (forty-three) sending a message to an external device (to be determined); (forty five) setting remote controller keys for monitoring; (forty-seven) setting a performance alarm threshold; (forty-nine) setting performance monitoring starting; (fifty) setting performance monitoring parameters; (fifty-two) setting ping test parameters; (fifty three) initiate a ping test; (fifty-five) setting traceroute test parameters; (fifty-six) initiate the traceroute test; (sixty one) two-layer network test parameters are set (to be determined, ONU cooperation is needed); (sixty two) starting a two-layer network test (pending); (sixty-four) starting log capture; (sixty-six) register a callback interface; (sixty-seven) a reverse registration callback interface.
1.4 Interactive flow design of APK and ACS
1.4.1, a starting-up information reporting flow, refer to fig. 5.
The first step is as follows: the equipment accesses the ACS for the first time, or the flow is triggered when the equipment is restarted (the equipment reports 0BOOT or 1 BOOT);
the second step is that: an ACS reply message;
the third step: the ACS issues STUN server parameters;
the fourth step: the equipment replies a parameter setting result;
the fifth step: the device sends a UDP heartbeat (UDP BIND request);
and a sixth step: the ACS replies BIND RESPANSE and carries the external UDP ConnectAddress of the equipment;
the seventh step: the equipment reports 4VALUE CHANGE and carries NATDelected and UDPConnectionRequestAddress;
eighth step: and the ACS replies the message and stores the STUN information reported by the equipment in a storage mode.
1.4.2, device state refresh flow, refer to fig. 6.
The first step is as follows: the ACS sends a UDP request;
the second step: the equipment returns 6CONNECTION REQUEST;
the third step: ACS replies InformResponse;
the fourth step: an ACS issues a GetRPCHongs (method for acquiring equipment support);
the fifth step: the device replies to getpcmethoddsresponse.
1.4.3, the ACS issues a service operation to the device, referring to fig. 7.
The first step is as follows: ACS sends UDP request;
the second step: the equipment reports 6CONNECTION REQUEST;
the third step: an ACS reply message;
the fourth step: the ACS issues RESULT =2, which indicates that the service is ready to be issued;
the fifth step: the device replies SetParameterValuesResponse;
and a sixth step: ACS sends UDP request;
the seventh step: the equipment reports 6CONNECTION REQUEST;
eighth step: an ACS reply message;
the ninth step: ACS sends down service parameters (voice parameters);
the tenth step: the device replies SetParameterValuesResponse;
the eleventh step: ACS sends UDP request;
the twelfth step: the equipment reports 6CONNECTION REQUEST;
and a thirteenth step of: the ACS issues RESULT =0, which indicates that the service is successfully issued;
the fourteenth step is that: the device replies SetParameterValuesResponse.
The embodiment of the technical scheme of the invention comprises the following contents: 1. and the interaction between the ACS and the terminal equipment is realized through the AIDL interface. 2. And the terminal and the ACS perform registration authentication by using the APK application packaged as the TR069 message on the terminal. 3. The existing TR069 protocol is utilized to be packaged into an effective RPC method, and all function acquisition information interaction of the terminal is realized. 4. The communication protocol between the ACS and the APK is called, management and service processing of all terminals are achieved, and the technical scheme is a progressive breakthrough, so that management application of interconnection of intelligent terminals and 5G at a user side is achieved.
The original code realized by the technical scheme of the invention is extracted as follows:
those skilled in the art will appreciate that the invention may be practiced without these specific details. It is pointed out here that the above description is helpful for the person skilled in the art to understand the invention, but does not limit the scope of protection of the invention. Any such equivalents, modifications and/or omissions as may be made without departing from the spirit and scope of the invention may be resorted to.
Claims (5)
1. A method for realizing interaction between an APK and an ACS by packaging a TR069 message is characterized by comprising an APK end and an ACS end, wherein the APK in the APK end is packaged into the TR069 message, the APK end comprises an APK client and an APK server, and the ACS end calls an RPC method packaged by a TR069 protocol of the APK server through an AIDL communication mechanism between the APK client and the APK server to realize unified management on APK terminal equipment in an application software layer;
the unified management includes a combination of one or more of: information acquisition, parameter configuration, performance monitoring, performance alarming and fault diagnosis;
the method comprises the steps of automatically identifying the information of a management request reported by the terminal equipment through a TR069 message packaging technology, automatically establishing a terminal equipment registration authentication flow, realizing unified authentication management of the terminal equipment by utilizing a TR069 protocol, and analyzing and injecting the information message in the flow by an RPC method through interaction between an ACS and an APK, so that classified management of terminal terminals of manufacturers, numbers, types, software versions and hardware versions of different terminal equipment of an operator is met;
the method comprises the steps of realizing interaction between the ACS and the terminal equipment through an AIDL interface; the method comprises the steps that APK application packaged as TR069 information is installed on terminal equipment, and the terminal equipment and ACS are registered and authenticated; the existing TR069 protocol is utilized to be packaged into an effective RPC method, so that all function acquisition information interaction of the terminal equipment is realized; calling a communication protocol between the ACS and the APK to realize management and service processing of the terminal equipment or management application of 5G interconnection;
the method comprises a logic call processing flow for realizing the interaction of the APK and the ACS among the ACS, the APK client and the APK server, wherein the logic call processing flow comprises the following steps: step A1, an ACS initiates an interactive process with an APK, and the ACS issues a command aiming at a specified terminal to an APK client side which packages the APK into a TR069 message; step A2, the APK client receives the command of the ACS and then calls an RPC method of the APK server by using an AIDL communication mechanism to transmit the command to the APK server; step A3, the APK server executes the command to operate the appointed terminal, and returns an execution result to the APK client by using an AIDL communication mechanism; step A4, the APK client reports an execution result to the ACS by adopting a TR069 protocol; and step A5, the ACS finishes the flow.
2. The method for realizing interaction between APK and ACS by encapsulating TR069 messages according to claim 1, comprising an ACS and APK interworking connection procedure that includes the steps of: step B1, ACS initiates Http connection to APK; step B2, APK returns 200 representing connection OK or 204 representing connection failure; step B3, the APK reports the connection request of the terminal restart; step B4, the ACS returns a request reply of the terminal restart; step B5, the APK sends an empty packet to the ACS; step B6, the ACS issues an instruction to the APK; step B7, the APK sends an instruction reply to the ACS; and 8, sending a null packet to the APK by the ACS to end the interactive connection process.
3. The method for realizing interaction between the APK and the ACS by encapsulating the TR069 message as claimed in claim 1, comprising a boot information reporting procedure between the APK and the ACS, the boot information reporting procedure comprising the steps of: step C1, APK equipment is accessed to the ACS for the first time, or the flow is triggered when the APK equipment is restarted; c2, replying a message by the ACS; step C3, the ACS issues the STUN server parameter; c4, the APK equipment replies a parameter setting result; step C5, the APK equipment sends UDP heartbeat; c6, the ACS replies BIND RESPONSE and carries the external UDP ConnectAddress of the equipment; step C7, APK equipment reports 4VALUE CHANGE and carries NATDelected and UDPConnectionRequestAddress; and C8, the ACS replies the message and stores the STUN information reported by the equipment in a storage mode.
4. The method for realizing the interaction between the APK and the ACS by encapsulating the TR069 message according to claim 1, comprising a device state refresh flow between the APK and the ACS, which comprises the following steps: step D1, the ACS sends a UDP request to the APK equipment; d2, returning 6CONNECTION REQUEST by the APK equipment; d3, the ACS replies an inform response; d4, sending a GetRPCHouds acquisition device support method by the ACS; step D5, the APK equipment replies to GetRPMethodsResponse.
5. The method for realizing interaction between the APK and the ACS by encapsulating the TR069 message according to claim 1, comprising the step of sending a service operation flow to the APK by the ACS, wherein the service operation flow comprises the following steps: step E1, the ACS sends a UDP request to the APK; step E2, the APK equipment reports 6CONNECTION REQUEST; step E3, ACS replies the message; step E4, the ACS issues RESULT =2, which indicates that the service is ready to be issued; step E5, the APK equipment replies to SetParameterValueResponse; step E6, the ACS sends a UDP request; step E7, the APK equipment reports 6CONNECTION REQUEST; step E8, ACS replies the message; step E9, the ACS issues service parameters; step E10, the APK equipment replies SetParameterValueResponse; step E11, the ACS sends a UDP request; step E12, the APK equipment reports 6CONNECTION REQUEST; step E13, the ACS issues RESULT =0, which indicates that the service is successfully issued; step E14, the APK device replies to SetParameterValuesResponse.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110122248.5A CN112910884B (en) | 2021-01-28 | 2021-01-28 | Method for realizing interaction between APK and ACS through packaging TR069 message |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110122248.5A CN112910884B (en) | 2021-01-28 | 2021-01-28 | Method for realizing interaction between APK and ACS through packaging TR069 message |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112910884A CN112910884A (en) | 2021-06-04 |
| CN112910884B true CN112910884B (en) | 2023-04-18 |
Family
ID=76120092
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110122248.5A Active CN112910884B (en) | 2021-01-28 | 2021-01-28 | Method for realizing interaction between APK and ACS through packaging TR069 message |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112910884B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113242521B (en) * | 2021-07-13 | 2021-10-19 | 深圳市艾伯通信有限公司 | TR 069-based message optimization processing method and system |
| CN114172786A (en) * | 2021-12-03 | 2022-03-11 | 中国电信集团系统集成有限责任公司 | Method and device for dynamically adjusting network monitoring threshold based on TR069 protocol and NETCONF protocol |
| CN115103042B (en) * | 2022-05-07 | 2024-01-05 | 深圳市广和通无线股份有限公司 | System based on CPE wide area network management protocol and wireless communication module |
| CN118200195B (en) * | 2024-05-13 | 2024-07-23 | 湖南天冠电子信息技术有限公司 | Method for monitoring network connection state of network equipment based on TR069 protocol |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2009149416A1 (en) * | 2008-06-05 | 2009-12-10 | 3Tera, Inc. | Automated filer technique for use in virtualized appliances and applications |
| CN104184618A (en) * | 2014-08-12 | 2014-12-03 | 烽火通信科技股份有限公司 | Android terminal and method for realizing TR069 network management agent |
| CN106302618A (en) * | 2015-06-11 | 2017-01-04 | 阿里巴巴集团控股有限公司 | Long-range control method, remote server, management equipment and terminal |
| WO2017211235A1 (en) * | 2016-06-06 | 2017-12-14 | 中兴通讯股份有限公司 | Client device management method and system, automatic configuration server, and storage medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104734893B (en) * | 2015-04-02 | 2018-02-27 | 重庆邮电大学 | A kind of TR069 protocol managerial approach towards WIA PA networks |
-
2021
- 2021-01-28 CN CN202110122248.5A patent/CN112910884B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2009149416A1 (en) * | 2008-06-05 | 2009-12-10 | 3Tera, Inc. | Automated filer technique for use in virtualized appliances and applications |
| CN104184618A (en) * | 2014-08-12 | 2014-12-03 | 烽火通信科技股份有限公司 | Android terminal and method for realizing TR069 network management agent |
| CN106302618A (en) * | 2015-06-11 | 2017-01-04 | 阿里巴巴集团控股有限公司 | Long-range control method, remote server, management equipment and terminal |
| WO2017211235A1 (en) * | 2016-06-06 | 2017-12-14 | 中兴通讯股份有限公司 | Client device management method and system, automatic configuration server, and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| TR069协议实现研究;孟德峰等;《中国新通信》;20081205(第23期);第30-35页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112910884A (en) | 2021-06-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112910884B (en) | Method for realizing interaction between APK and ACS through packaging TR069 message | |
| US20190179726A1 (en) | Monitoring method and apparatus of server, and storage medium | |
| CN109918061B (en) | Cross-platform interface middleware implementation method and device based on android system | |
| CN102158370B (en) | Automated testing method and system | |
| US8819202B1 (en) | Service configuration and deployment engine for provisioning automation | |
| US9331953B2 (en) | Device management method, middleware, and machine-to-machine communications platform, device, and system | |
| JP2009545039A (en) | Methods, systems, and terminals for maintaining capability management objects and managing capabilities | |
| CN104618437B (en) | A kind of adaptation method that interface is set with android terminal device systems | |
| EP2184903A1 (en) | Method and device for automatically installing an applciation | |
| CN105959302B (en) | A kind of terminal management system and method | |
| EP2701059A1 (en) | Method and apparatus for loading application program | |
| CN101799751A (en) | Method for building monitoring agent software of host machine | |
| CN102790781A (en) | Middleware, M2M (machine-to-machine) system with industrial application middleware and application method of system | |
| WO2021057605A1 (en) | Device management method, device, system and device, and storage medium | |
| CN112084008A (en) | Method for rapidly deploying cloud pipe system based on container technology | |
| CN115357308B (en) | Docker-based edge Internet of things agent device, system and application method | |
| KR20190048769A (en) | Cloud-Based Terminal Integrating Management System Using OTA Technique of IoT Terminal Over LPWA Network | |
| CN114327519A (en) | Implementation method and device for installing application on intelligent POS equipment | |
| CN101895441B (en) | Service debugging device and method for JAVA application of terminal of Internet of things | |
| WO2023169097A1 (en) | 5g message terminal identification method, service platform and storage medium | |
| CN105024847A (en) | Network management system of a single-server multi-network-equipment adapter, and a configuration, start, and operation method of the single-server multi-network-equipment adapter | |
| CN114244678B (en) | Multi-protocol alarm equipment access method and system | |
| CN112448854B (en) | Kubernetes complex network policy system and implementation method thereof | |
| CN108243038A (en) | A kind of method and apparatus of service call | |
| CN113965546A (en) | Method for setting tenant special DNS server for application by container cloud platform |
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 |